Session processing method and device, electronic equipment, storage medium and program product

Abstract

The invention provides a session processing method. The method comprises the following steps: displaying a session interface for a session between a first account and a second account, responding to a call instruction triggered based on the session interface, displaying a call waiting interface used for indicating to wait for the second account to accept a call request, the call request being used for requesting to carry out an audio call or a video call with the second account, and when at least one of the first account number and the second account number is abnormal, cancelling the display of the call waiting interface and displaying call abnormity prompt information which is used for prompting that the first account number cannot perform the audio call or the video call with the second account number. According to the method and the device, the audio call function and the video call function of the abnormal account number can be limited, and the safety of the account number without the abnormal account number is improved.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a session processing method, device, electronic device, storage medium, and program product. Background Art

[0002] With the development of technology, instant messaging has become increasingly common in people's daily lives, greatly facilitating their daily lives. However, malicious users may use instant messaging products to conduct malicious activities. Related technologies often misidentify accounts that engage in malicious activities as legitimate, resulting in a lack of functionality restrictions on malicious accounts and reduced security for legitimate accounts. Summary of the Invention

[0003] Embodiments of the present application provide a conversation processing method, apparatus, electronic device, computer-readable storage medium, and computer program product, which can limit the audio call function and video call function of accounts with abnormalities and improve the security of accounts without abnormalities.

[0004] The technical solution of the embodiment of the present application is implemented as follows:

[0005] This embodiment of the present application provides a session processing method, the method comprising:

[0006] Displaying a conversation interface between the first account and the second account;

[0007] In response to a call instruction triggered based on the conversation interface, displaying a call waiting interface for indicating waiting for the second account to accept the call request;

[0008] The call request is used to request an audio call or a video call with the second account;

[0009] When at least one of the first account and the second account has an abnormality, canceling the display of the call waiting interface and displaying a call abnormality prompt message;

[0010] The call abnormality prompt information is used to prompt that the first account cannot make an audio call or a video call with the second account.

[0011] An embodiment of the present application provides a session processing device, which includes:

[0012] A display module, configured to display a conversation interface between the first account and the second account;

[0013] The display module is further configured to display a call waiting interface for waiting for the second account to accept the call request in response to a call instruction triggered based on the conversation interface;

[0014] The call request is used to request an audio call or a video call with the second account;

[0015] A prompt module, configured to cancel display of the call waiting interface and display call abnormality prompt information when at least one of the first account and the second account has an abnormality;

[0016] The call abnormality prompt information is used to prompt that the first account cannot make an audio call or a video call with the second account.

[0017] An embodiment of the present application provides an electronic device, wherein the terminal includes:

[0018] a memory for storing computer-executable instructions;

[0019] The processor is configured to implement the session processing method provided in the embodiment of the present application when executing the computer-executable instructions stored in the memory.

[0020] An embodiment of the present application provides a computer-readable storage medium storing a computer program or computer-executable instructions for implementing the session processing method provided in the embodiment of the present application when executed by a processor.

[0021] An embodiment of the present application provides a computer program product, including a computer program or computer-executable instructions. When the computer program or computer-executable instructions are executed by a processor, the session processing method provided in the embodiment of the present application is implemented.

[0022] The embodiments of the present application have the following beneficial effects:

[0023] In an embodiment of the present application, when an abnormality occurs in at least one of the first account and the second account, a call request from the first account to make an audio call or a video call with the second account can be blocked, that is, the audio call function and the video call function of the account with the abnormality are restricted. In addition, a call abnormality prompt message can be displayed to remind both the account with the abnormality and the account without the abnormality, thereby improving the security of the account without the abnormality. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 This is a structural diagram of a session processing system provided in an embodiment of the present application;

[0025] Figure 2 is a structural diagram of an electronic device provided in an embodiment of the present application;

[0026] Figure 3 This is a first flow chart of the session processing method provided in an embodiment of the present application;

[0027] Figure 4This is a first schematic diagram of a conversation interface provided in an embodiment of the present application;

[0028] Figure 5 is a schematic diagram of a call waiting interface provided in an embodiment of the present application;

[0029] Figure 6 Schematic diagram of an abnormal prompt window provided in an embodiment of the present application;

[0030] Figure 7 This is a second schematic diagram of the conversation interface provided in an embodiment of the present application;

[0031] Figure 8 This is a first schematic diagram of an abnormality details interface of a first account provided in an embodiment of the present application;

[0032] Figure 9 This is a second schematic diagram of the abnormality details interface of the first account provided in an embodiment of the present application;

[0033] Figure 10 is a schematic diagram of an auxiliary restriction removal page provided in an embodiment of the present application;

[0034] Figure 11A This is a first schematic diagram of the self-service restriction removal interface provided in an embodiment of the present application;

[0035] Figure 11B This is a second schematic diagram of the self-service restriction removal interface provided in an embodiment of the present application;

[0036] Figure 11C This is a third schematic diagram of the self-service restriction removal interface provided in an embodiment of the present application;

[0037] Figure 12 This is a third schematic diagram of a conversation interface provided in an embodiment of the present application;

[0038] Figure 13 This is a fourth schematic diagram of a conversation interface provided in an embodiment of the present application;

[0039] Figure 14 This is a third schematic diagram of the abnormality details interface of the first account provided in an embodiment of the present application;

[0040] Figure 15 is a schematic diagram of a video call interface provided in an embodiment of the present application;

[0041] Figure 16 This is a fifth schematic diagram of a conversation interface provided in an embodiment of the present application;

[0042] Figure 17 This is a second flow chart of the session processing method provided in an embodiment of the present application;

[0043] Figure 18This is a third flow chart of the session processing method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solutions and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limiting this application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0045] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0046] In the following description, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0047] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0048] Unless otherwise defined, all technical and scientific terms used in the embodiments of the present application have the same meanings as those commonly understood by those skilled in the art. The terms used in the embodiments of the present application are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0049] In this application, the facial (or other biometric) recognition technology involved, when the above embodiments of this application are applied to specific products or technologies, the relevant data collection, use and processing processes should comply with national laws and regulations. Before collecting facial information, the information processing rules should be informed and the target object's separate consent should be obtained. The facial information should be processed strictly in accordance with the requirements of laws and regulations and personal information processing rules, and technical measures should be taken to ensure the security of relevant data.

[0050] The collection and processing of relevant data in this application should be strictly in accordance with the requirements of relevant national laws and regulations when applied in practice, and the informed consent or separate consent of the personal information subject should be obtained. Subsequent data use and processing should be carried out within the scope of authorization of laws and regulations and the personal information subject.

[0051] Before further describing the embodiments of the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0052] 1) Malicious groups: groups that use Internet technology to carry out malicious acts (violating laws and regulations or platform-related rules) in ways prohibited by laws and platforms.

[0053] 2) Malicious accounts: Accounts used by malicious groups to commit illegal acts on the platform, that is, accounts used by malicious users to commit malicious acts.

[0054] 3) Normal account: An account used by ordinary users to operate on the platform, that is, an account used by users who do not commit malicious acts.

[0055] 4) Audio and video calls: Voice calls or video calls initiated through the platform's capabilities.

[0056] 5) Freeze: The full name is to freeze the account, which will kick the account offline and restrict login.

[0057] 6) Restrictions on all social functions: Restrictions on all social functions (such as conversations, sending location information, posting status updates, etc.) used by users on social platforms to ensure that they cannot reach other users through the platform;

[0058] Embodiments of the present application provide a conversation processing method, apparatus, electronic device, computer-readable storage medium, and computer program product, which can limit the audio call function and video call function of accounts with abnormalities, and can also display call abnormality reminder information, thereby improving the security of accounts without abnormalities.

[0059] See also Figure 1 , Figure 1 This is a schematic diagram of the architecture of a session processing system 100 provided in an embodiment of the present application. To support a session processing application, terminals (terminal 400-1 and terminal 400-2 are shown as examples) are connected to a server 200 via a network 300. Network 300 can be a wide area network (WAN), a local area network (LAN), or a combination of the two. Server 200 is connected to a database 500. Server 200 and database 500 can be connected directly or indirectly via wired or wireless communication, which is not limited in the present embodiment.

[0060] Terminal 400-1 and terminal 400-2 can be provided with a client that supports conversations. The client can be a client with conversation functions or a dedicated client dedicated to conversations. Taking the example that both terminal 400-1 and terminal 400-2 are provided with instant messaging clients, terminal 400-1 can log in to the first account based on the instant messaging client, and terminal 400-2 can log in to the second account based on the instant messaging client.

[0061] Terminal 400-1 is configured to display, on graphical interface 410-1, a conversation interface for a conversation between a first account and a second account. In response to a call instruction triggered based on the conversation interface, graphical interface 410-1 displays a call waiting interface indicating that the user is waiting for the second account to accept the call request. The call request is used to request an audio or video call with the second account.

[0062] While terminal 400-1 displays the call waiting interface, terminal 400-1 can send a call request carrying the first account and the second account to server 200. Server 200 can obtain the abnormal account from database 500 and match the abnormal account with the first account and the second account respectively to obtain an abnormal result.

[0063] If an anomaly occurs in at least one of the first and second accounts, server 200 may send a call request blocking instruction and a call anomaly prompt to terminal 400-1. Terminal 400-1 may then cancel the call waiting interface on graphical interface 410-1 and display the call anomaly prompt instead. Terminal 400-2 will not receive the call request, and graphical interface 410-2 will not display the call confirmation page for accepting the call request from the first account. The call anomaly prompt indicates that the first account cannot make an audio or video call with the second account.

[0064] In some embodiments, the server 200 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Terminals 400-1 and 400-2 may be various types of user terminals such as laptops, tablet computers, desktop computers, set-top boxes, mobile devices (e.g., mobile phones, portable music players, personal digital assistants, dedicated messaging devices, portable gaming devices), smart phones, smart speakers, smart watches, smart TVs, and in-vehicle terminals, but are not limited thereto.

[0065] The following describes an electronic device for executing a session processing method provided by an embodiment of the present application. The electronic device can be implemented as a terminal or a server. The specific description of the terminal and the server can be found in the above content and will not be repeated here.

[0066] See also Figure 2 , Figure 2 is a structural diagram of an electronic device provided in an embodiment of the present application, Figure 2 The electronic device shown includes: at least one processor 410, a memory 450, at least one network interface 420 and a user interface 430. The various components in the electronic device are coupled together via a bus system 440. It is understood that the bus system 440 is used to achieve connection and communication between these components. In addition to including a data bus, the bus system 440 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 440 is not shown in FIG. Figure 2 Various buses are labeled as bus system 440 .

[0067] The processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0068] The user interface 430 includes one or more output devices 431 that enable presentation of media content, including one or more speakers and / or one or more visual display screens. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0069] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard drives, optical drives, etc. The memory 450 may optionally include one or more storage devices that are physically remote from the processor 410.

[0070] The memory 450 includes volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM), and the volatile memory may be a random access memory (RAM). The memory 450 described in the embodiments of the present application is intended to include any suitable type of memory.

[0071] In some embodiments, the memory 450 can store data to support various operations, examples of which include programs, modules, and data structures, or a subset or superset thereof, as exemplified below.

[0072] Operating system 451, including system programs for processing various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, and driver layer, which are used to implement various basic services and process hardware-based tasks;

[0073] A network communication module 452 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 420. Exemplary network interfaces 420 include Bluetooth, Wi-Fi, and Universal Serial Bus (USB);

[0074] a presentation module 453 for enabling presentation of information via one or more output devices 431 (e.g., a display screen, a speaker, etc.) associated with the user interface 430 (e.g., a user interface for operating peripheral devices and displaying content and information);

[0075] The input processing module 454 is configured to detect one or more user inputs or interactions from one of the one or more input devices 432 and to translate the detected inputs or interactions.

[0076] In some embodiments, the apparatus provided in the embodiments of the present application may be implemented in software. Figure 2 The diagram shows a session processing device 455 stored in memory 450. This device can be software in the form of a program or plug-in, and includes the following software modules: a display module 4551 and a prompt module 4552. These modules are logical and can be arbitrarily combined or further separated according to the functions they implement. The functions of each module will be described below.

[0077] In some embodiments, the electronic device can implement the session processing method provided in the embodiment of the present application by running various computer executable instructions or computer programs. For example, the computer executable instructions can be microprogram-level commands, machine instructions or software instructions. The computer program can be a native program or software module in the operating system; it can be a native application (APPlication, APP), that is, a program that needs to be installed in the operating system to run, such as an instant messaging APP; it can also be a small program that can be embedded in any APP, that is, a program that can be run only by downloading it to a browser environment. In short, the above-mentioned computer executable instructions can be instructions in any form, and the above-mentioned computer program can be an application, module or plug-in in any form.

[0078] See also Figure 3 , Figure 3 This is a first flow chart of the session processing method provided in the embodiment of the present application, which will be combined with Figure 3 The steps shown are used for illustration. The session processing method provided in the embodiment of the present application can be implemented by the server or the terminal alone, or by the server and the terminal in collaboration. The following description will be made using the implementation by the terminal alone as an example.

[0079] In step 101, a conversation interface between a first account and a second account is displayed.

[0080] In actual implementation, the terminal is provided with a client that supports conversations. The client can be a client with conversation functions, such as an education client, a video client, etc., or a proprietary client dedicated to conversations, such as an instant messaging (IM) client, etc. When the user opens the client on the terminal and the terminal runs the client, the login interface corresponding to the client can be displayed.

[0081] The user can enter the first account and the password corresponding to the first account on the login interface, so that the terminal can log in to the first account based on the client, and then display the friend list interface corresponding to the first account, or display the conversation list interface of the conversation with the first account.

[0082] The friend list interface may display at least one other account. The conversation list interface may display at least one conversation selection box for conversing with other accounts, wherein the account selected by the user from the other accounts with which the conversation is to be conducted is the second account.

[0083] In response to a selection operation on the friend list interface or the conversation list interface, a conversation interface for the first account and the second account can be displayed on the terminal corresponding to the first account. When the number of second accounts is 1, the conversation interface is a conversation interface for a one-to-one conversation between the first account and the second account.

[0084] The conversation interface may include a conversation information area and a conversation message area. The conversation information area may display content corresponding to the second account. The content corresponding to the second account may consist of at least one of a string, a nickname, and a note set by the first account for the second account, where the string uniquely identifies the second account. The conversation message area is used to display conversation messages between the first account and the second account.

[0085] If there are multiple second accounts, the conversation interface is a group conversation interface for the first account and multiple second accounts. The conversation information area can display the content corresponding to the group, which can include the name of the group corresponding to the first and second accounts, and can also include notes set by the first account for the conversation group.

[0086] See also Figure 4 , Figure 4 The first schematic diagram of the conversation interface provided in the embodiment of the present application is shown in FIG. Figure 4 In the example, the number of the second account is 1, and the second account can be displayed in the session information area 401 of the session interface. Through step 101, the session interface can be displayed so that various instructions triggered based on the session interface can be responded to later.

[0087] In step 102, in response to a call instruction triggered based on the conversation interface, a call waiting interface is displayed for indicating waiting for the second account to accept the call request.

[0088] In some embodiments, the conversation interface may include a call control, which may include a video call control and a voice call control. Figure 4 In the example, the conversation interface may further display a video call control 402 and a voice call control 403 .

[0089] The call instruction may include a video call instruction and an audio call instruction. The video call control may be used to trigger the video call instruction, and the voice call control may be used to trigger the audio call instruction. The call request is used to request an audio call or a video call with the second account.

[0090] The call waiting interface can display areas such as session details, call status notifications, and call operation guides. If the number of second accounts is one, the session details display area can display the second account's avatar and content corresponding to the second account. If there are multiple second accounts, the session details display area can display avatars for multiple second accounts, or images captured in real time by the image capture devices of the terminals corresponding to the multiple second accounts.

[0091] The call status prompt area is used to display the call status of the first account and the second account. In some embodiments, the call status prompt area can be displayed in the form of bubbles or scrolling. The specific setting can be based on actual usage needs and is not specifically limited here.

[0092] The call operation guidance area guides users through call operations and includes microphone, hang-up, and speaker controls. The microphone control is used to turn the microphone on or off, the hang-up control is used to hang up an audio or video call, and the speaker control is used to turn the speaker on or off.

[0093] The area corresponding to the microphone control is the microphone status display area, which can be used to display the current status of the microphone. The area corresponding to the speaker control is the speaker status display area, which can be used to display the current status of the speaker.

[0094] In some embodiments, in response to an audio call instruction from a voice call control displayed on a conversation interface, a call waiting interface is displayed, indicating that the user is waiting for a second account to accept the call request. For the call waiting interface corresponding to the audio call instruction, the session details display area, call status prompt area, and call operation guidance area are displayed above the interface background of the call waiting interface, which is a pre-set background.

[0095] See also Figure 5 , Figure 5 A schematic diagram of a call waiting interface provided in an embodiment of the present application, in Figure 5 The area includes a conversation details display area 404, a call status prompt area 405, a call operation guide area ( Figure 5 (not numbered in the middle).

[0096] exist Figure 5 In the conversation details display area 404, the second account and the second account's avatar may be displayed. If the second account does not connect to the audio call, the call status between the first account and the second account indicated in the call status prompt area 405 may be "waiting for the other party to accept the invitation..."

[0097] When the second account connects the audio call, the call status between the first account and the second account indicated in the call status prompt area 405 may be "connected". If the duration of displaying "connected" is longer than the preset connection duration, the display of "connected" is canceled. The call duration ( Figure 4 not shown).

[0098] exist Figure 5 In the call operation guide area, a microphone control 406, a hang-up control 407, and a speaker control 408 may be included. In response to a microphone on instruction based on the microphone control 406, the area corresponding to the microphone control 406 may display that the microphone is on. In response to a speaker on instruction based on the speaker control 408, the area corresponding to the speaker control 408 may display that the speaker is on.

[0099] In response to a microphone off instruction based on the microphone control 406, the area corresponding to the microphone control 406 may display that the microphone is off. In response to a speaker off instruction based on the speaker control 408, the area corresponding to the speaker control 408 may display that the speaker is off.

[0100] In response to the hang-up instruction based on the hang-up control 407, the call status between the first account and the second account indicated in the call status prompt area 405 may be "hung up". When the time duration of displaying "hung up" is longer than the preset hang-up time duration, the display of "hung up" is cancelled and the call waiting interface is cancelled.

[0101] In some embodiments, in response to a video call instruction based on a video call control displayed on a session interface, a display is used to indicate waiting for the second account to accept the video call. For a call waiting interface corresponding to the video call instruction, a session details display area, a call status prompt area, and a call operation guide area are displayed on the real-time acquisition screen of the call waiting interface. The real-time acquisition screen is a screen captured by the image acquisition device corresponding to the terminal.

[0102] For the call waiting interface corresponding to the video call command, the specific contents of the session details display area, call status prompt area, and call operation guidance area are the same as those of the call waiting interface corresponding to the audio call command. For details, please refer to Figure 5 The corresponding description is not repeated here.

[0103] The conversation interface may include call controls, while the call waiting interface may include microphone controls, hang-up controls, and speaker controls. Call control operations can be performed using the appropriate controls based on actual usage needs. The call waiting interface also includes a microphone status display area, a speaker status display area, and a call status prompt area, allowing users to more intuitively understand the status of the corresponding areas, thereby improving the user experience.

[0104] In some embodiments, the user can control related functions of the conversation through voice commands. For example, a call request can be issued to the second account through voice commands. That is, the call command can be a command in voice form, and the terminal can obtain the voice command. When the voice command represents a call request to the second account, the terminal can display a call waiting interface for indicating waiting for the second account to accept the call request in response to the call command triggered based on the conversation interface.

[0105] For another example, the microphone and speaker can be controlled via voice commands. If the voice command indicates turning on the microphone, in response to the microphone on command on the call waiting page, the microphone of the terminal corresponding to the first account can be turned on, and the microphone status display area will indicate that the microphone is on. The microphone on command is a voice command.

[0106] In the case where the voice command indicates turning off the microphone, in response to the microphone turning off command on the call waiting page, the microphone of the terminal corresponding to the first account can be turned off, and the microphone status display area displays that the microphone is turned off. The microphone turning off command is a voice command.

[0107] If the voice command indicates turning on the speaker, in response to the speaker-on command on the call waiting page, the speaker of the terminal corresponding to the first account can be turned on, and the speaker status display area will display that the speaker is on. If the voice command indicates turning off the speaker, in response to the speaker-off command on the call waiting page, the speaker of the terminal corresponding to the first account can be turned off, and the speaker status display area will display that the speaker is off. The speaker-on command and the speaker-off command are voice commands.

[0108] For another example, if a voice command indicates a hang-up, in response to a hang-up command on the call waiting page, the call status of the first account and the second account indicated in the call status prompt area may be "Hanged Up." If the duration of the "Hanged Up" display exceeds the preset hang-up duration, the "Hanged Up" display is canceled, and the call waiting interface is also canceled. The hang-up command is a voice command.

[0109] The voice command can indicate a call request to a second account, turning the microphone on or off, turning the speaker on or off, or hanging up. Depending on the meaning of the voice command, the relevant functions of the conversation can be controlled. In this way, call control operations can be performed through voice commands.

[0110] Through step 102, call control operations can be performed using controls or voice commands, that is, call control operations can be performed in different ways. A call waiting interface can also be displayed, which includes a conversation details display area, a call status prompt area, and a call operation guidance area. Different areas can display different content, which can help users respond to information in a timely manner.

[0111] In some embodiments, Figure 3After step 102 shown, it is also possible to determine whether there is an abnormality in at least one of the first account and the second account. If there is no abnormality in both the first account and the second account, a call request can be sent to the terminal corresponding to the second account. If there is an abnormality in at least one of the first account and the second account, a call request can be executed. Figure 3 Step 103.

[0112] In some embodiments, a call request carrying the first account and the second account is sent to the server.

[0113] The call request is used by the server to obtain a pre-stored abnormal account number, match the pre-stored abnormal account number with the first account number and the second account number respectively, and determine the abnormal results of the first account number and the second account number based on the matching results.

[0114] In some embodiments, when the server receives a call request carrying a first account and a second account, it can obtain a pre-stored abnormal account, and then match the pre-stored abnormal account with the first account and the second account respectively, and determine the abnormal results of the first account and the second account based on the matching results.

[0115] If the first account number matches a pre-stored abnormal account number, it indicates that the first account number is abnormal. If the first account number does not match a pre-stored abnormal account number, it indicates that the first account number is not abnormal. If the second account number matches a pre-stored abnormal account number, it indicates that the second account number is abnormal. If the character string corresponding to the second account number does not match a pre-stored abnormal account number, it indicates that the second account number is not abnormal. In this way, the abnormal results of the first and second accounts can be determined based on the matching results.

[0116] In some embodiments, the server pre-stores all accounts corresponding to clients that support sessions. Abnormal accounts have pre-set abnormal identifiers. The server can obtain the account corresponding to the abnormal identifier, which is equivalent to obtaining the pre-stored abnormal account.

[0117] In some embodiments, if the server determines that an account has an abnormality, it may store the abnormal account as an abnormal account, and if it determines that the account does not have an abnormality, it may not store the non-abnormal account. In this way, after receiving a call request, the server can obtain the pre-stored abnormal account.

[0118] In some embodiments, the server may store a pre-trained anomaly recognition model, and the first account and the second account may be input into the pre-trained anomaly recognition model to obtain an anomaly recognition result, wherein the anomaly recognition result is used to indicate whether at least one of the first account and the second account has an anomaly.

[0119] The abnormal recognition result is essentially the same as the abnormal result. The steps performed for different situations corresponding to the abnormal recognition result are the same as the steps performed for different situations corresponding to the abnormal result. The following takes the abnormal result as an example to illustrate the steps performed for different situations corresponding to the abnormal result, and does not elaborate on the abnormal recognition result.

[0120] When the abnormal result indicates that there is no abnormality in both the first account and the second account, the server can send a call request to the terminal corresponding to the second account. When the second account accepts the call request, the call status of the first account and the second account indicated in the call status prompt area can be "connected". When the time duration of displaying "connected" is longer than the preset connection time duration, the display of "connected" is cancelled.

[0121] When the abnormal result indicates that there is an abnormality in the first account and there is no abnormality in the second account, or when the abnormal result indicates that there is an abnormality in the first account and there is an abnormality in the second account, or when the abnormal result indicates that there is no abnormality in the first account and there is an abnormality in the second account, that is, when the abnormal result indicates that there is an abnormality in at least one of the first account and the second account, the terminal corresponding to the first account can receive the instruction to block the call request and the call abnormality prompt information sent by the server.

[0122] In some embodiments, the terminal may store a pre-trained anomaly recognition model, and the first account and the second account may be input into the pre-trained anomaly recognition model to obtain an anomaly recognition result. The anomaly recognition result is used to indicate whether at least one of the first account and the second account is abnormal.

[0123] If the abnormal result indicates that there is no abnormality in either the first account or the second account, the terminal can send a call request to the server, and the server can then execute the corresponding steps when the abnormal result indicates that there is no abnormality in either the first account or the second account. Figure 3 Step 103.

[0124] In step 103, when at least one of the first account and the second account has an abnormality, the call waiting interface is canceled and a call abnormality prompt message is displayed.

[0125] If the call request is for an audio call with a second account, the call exception prompt message indicates that the first account cannot make an audio call with the second account. If the call request is for a video call with the second account, the call exception prompt message indicates that the first account cannot make a video call with the second account. In other words, the call exception prompt message indicates that the first account cannot make an audio or video call with the second account.

[0126] In some embodiments, the "displaying call abnormality prompt information" in the above step 103 can be implemented in the following way: displaying an abnormality prompt window in the conversation interface, and displaying the call abnormality prompt information through the abnormality prompt window.

[0127] See also Figure 6 , Figure 6 This is a schematic diagram of an abnormal prompt window provided in an embodiment of the present application. An abnormal prompt window 409 can be displayed on the conversation interface, and the call abnormality prompt information can be "There is a risk in the current conversation and the call cannot be made."

[0128] If the abnormality result indicates an abnormality in at least one of the first account and the second account, the server may send a pre-set call abnormality prompt message to the terminal corresponding to the first account. Upon receiving the call abnormality prompt message, the terminal corresponding to the first account displays an abnormality prompt window in the conversation interface and displays the call abnormality prompt message in the abnormality prompt window. In this way, the call abnormality information can be displayed in the abnormality prompt window, allowing the user to promptly understand the content of the call abnormality prompt message.

[0129] In some embodiments, after the abnormality prompt window is displayed in the conversation interface, the abnormality prompt window is canceled in response to a confirmation instruction triggered by the abnormality prompt window, wherein the confirmation instruction is used to indicate that the call abnormality prompt information has been obtained.

[0130] In some embodiments, the abnormal prompt window includes a determination control that can indicate that call abnormality prompt information has been obtained. In response to a determination instruction triggered based on the determination control displayed in the abnormal prompt window, the abnormal prompt window can be canceled.

[0131] Continue to see Figure 6 The abnormal prompt window 409 may include a confirmation control 411, and the confirmation control 411 is “I know.” In response to the confirmation instruction triggered by “I know,” the abnormal prompt window 409 may be canceled.

[0132] The method of canceling the display of the abnormal prompt window based on the confirmation instruction can ensure that the user has been informed of the abnormal reminder information by confirming the control. When it is determined that the user has been informed of the call abnormality prompt information, canceling the display of the abnormal prompt window can improve the user experience.

[0133] In some embodiments, after "canceling the call waiting interface" in step 103, an abnormality detail viewing portal is displayed. The abnormality detail viewing portal is used to guide users to view abnormality details corresponding to the abnormal account, where the abnormal account is an account with an abnormality between the first account and the second account.

[0134] If the exception result indicates an exception in at least one of the first account and the second account, the server may generate an exception details viewing portal and send the exception details viewing portal to the terminal corresponding to the first account. After receiving the exception details viewing portal, the terminal corresponding to the first account may display the exception details viewing portal on the conversation interface.

[0135] In some embodiments, see Figure 6 In the conversation interface, conversation log information 413 may be displayed in conversation message area 415 for displaying conversation messages. Conversation log information 413 indicates that the current call status is disconnected. Conversation log information 413 may include the first account's avatar and the text "Disconnected." Below conversation log information 413, an exception details viewing entry 412 may be displayed. The exception details viewing entry 412 may be labeled "Learn More."

[0136] An abnormality prompt window 409 pops up on the session interface displaying the session record information 413 and the abnormality detail viewing entrance 412, and displays "The current session is at risk and the call cannot be made" through the abnormality prompt window 409.

[0137] In some embodiments, after canceling the display of the abnormal prompt window, see Figure 7 , Figure 7 In the second schematic diagram of the conversation interface provided in an embodiment of the present application, a conversation message area 415 for displaying conversation messages in the conversation interface may display conversation log information 413. Conversation log information 413 specifically includes an avatar of the first account and "Not Connected." Below conversation log information 413, an exception details viewing entry 412 may be displayed. This entry reads "Learn More." This approach allows the user to view the exception details corresponding to the abnormal account, improving the user experience.

[0138] In some embodiments, after the abnormality detail viewing entrance is displayed, in response to a triggering operation on the abnormality detail viewing entrance, the abnormal account and abnormal function are displayed.

[0139] The abnormal function is a function that restricts abnormal accounts, and the triggering operation can be an operation such as a single click or double click to indicate viewing the abnormal details interface. For example, the abnormal details viewing entry can be clicked. In response to the triggering operation on the abnormal details viewing entry, the abnormal details interface is displayed. The abnormal details interface can include the abnormal account and abnormal function.

[0140] In some embodiments, the user can view the abnormality details entrance through voice commands, and the terminal corresponding to the first account can obtain the voice command. When the voice command represents the interface for viewing the abnormality details, the abnormal account and abnormal function are displayed in response to the trigger command for the abnormality details viewing entrance, wherein the trigger command is a command in voice form.

[0141] The abnormality details interface may include an abnormal account display area and an abnormal function display area. The abnormal account display area may display abnormal account information. If a first account has an abnormality, the abnormal account display area may display the first account's information. If a second account has an abnormality, the abnormal account display area may display the second account's information. Abnormal account information is information that can identify the abnormal account. For example, abnormal account information may be the account content corresponding to the abnormal account. The account content may consist of at least one of a string, an avatar, and a nickname. Without further limitation, string, avatar, and nickname constitute account information.

[0142] For example, see Figure 8 , Figure 8 This is a first schematic diagram of the abnormality details interface of the first account provided in an embodiment of the present application. The abnormality details interface may include an abnormal account display area 416, and the abnormal account display area 416 may display the avatar of the first account.

[0143] The abnormal function display area can display the functions restricted for abnormal accounts, see Figure 8 The abnormal details interface may also include an abnormal function display area 417, in which the functions restricted for abnormal accounts may be displayed. The restricted functions may include multiple functions, specifically including "group chat and dynamic sharing functions, all social scene functions, and contact-related functions." Figure 8 The restricted functions are only an example description and can be set according to actual conditions.

[0144] In the case where the abnormal function display area 417 includes functions such as group chat and status sharing, the abnormal account cannot perform group chat-related operations, such as creating a group chat and sending interactive messages in the group chat. The abnormal account also cannot perform status sharing-related operations, such as sending status in the status sharing area and interacting with the content displayed in the status area.

[0145] When the abnormal function display area 417 includes all social scene functions, the abnormal account cannot perform any interactive functions in social media or social networks, for example, cannot add friends, cannot initiate conversations with other accounts, etc.

[0146] In the case where the abnormal function display area 417 includes functions related to contacts, the abnormal account cannot perform any functions related to contacts, for example, cannot add contacts to group chats, cannot recommend contacts to other contacts, etc.

[0147] In some embodiments, in response to a trigger operation for viewing the abnormal details, a request for viewing the abnormal details with an abnormal account can be sent to the server. The server stores a pre-generated correspondence between candidate abnormal accounts and candidate abnormal functions. The server can determine the abnormal function corresponding to the abnormal account based on the abnormal account, and send the abnormal account and abnormal function to the terminal corresponding to the first account. In this way, the terminal corresponding to the first account can display the abnormal account and abnormal function. In this way, the abnormal account and abnormal function can be displayed, which can facilitate users to obtain abnormal details information about the inability to make audio calls or video calls, and can further improve the user experience.

[0148] In some embodiments, the call anomaly reminder includes information about the reason why the first account was unable to make an audio or video call with the second account. For example, the call anomaly reminder may read, "The current session is at risk; the call cannot be made." The reason information is pre-generated by the server based on the abnormal account, indicating the reason why the call could not be made. In this way, the call anomaly reminder, indicating the reason why the first account was unable to make an audio or video call with the second account, can be displayed, allowing the user to obtain the reason information.

[0149] In some embodiments, the reason information may be displayed as a weak reminder. For example, the reason information may be displayed as a weak reminder in the conversation message area of ​​the conversation interface. A weak reminder may be displayed using text with a smaller font size or a lower grayscale. The specific setting can be determined based on actual usage requirements and is not specifically limited here.

[0150] For example, see Figure 6 , a conversation message area 415 for displaying conversation messages in the conversation interface may display a reason information display area 414, where the reason information display area 414 is "the current conversation is at risk and the call cannot be made." For example, see Figure 7 , a reason information display area 414 may be displayed in the conversation message area 415 for displaying conversation messages in the conversation interface, and the reason information display area 414 may be “the current conversation is at risk and the call cannot be made”.

[0151] In some embodiments, the cause information and the exception details viewing entrance can be displayed simultaneously in the conversation message area. In this way, the user can be guided to understand the cause information and view the exception details information corresponding to the abnormal account.

[0152] In some embodiments, for each abnormal function, a restriction reason for restricting the abnormal function is displayed, and when the restriction reason includes a target behavior specification, a jump entry of the target behavior specification is displayed.

[0153] In some embodiments, for each abnormal function, the restriction reason for restricting the abnormal function can be displayed in the abnormal function display area. The restriction reason can include target behavior specifications, identity information abnormality, and age restriction.

[0154] If the restriction reason includes the target behavior specification, a jump entry to the target behavior specification may be displayed. The jump entry is used to guide users to view the content of the target behavior specification. The target behavior specification may be a behavior specification pre-set by the instant messaging application.

[0155] When a trigger operation for a jump entry is received, the content of the target behavior specification is displayed. In some embodiments, when a trigger operation for a jump entry is received, a target behavior specification acquisition request can be sent to a server, and the server can send the content of the target behavior specification to the terminal corresponding to the first account, and then the terminal corresponding to the first account can display the content of the target behavior specification.

[0156] For example, see Figure 8 The abnormal function display area 417 can display the functions restricted for abnormal accounts. For the restricted functions "group chat and dynamic sharing and other functions", the restriction reasons corresponding to "group chat and dynamic sharing and other functions" can be displayed below "group chat and dynamic sharing and other functions", and the font size corresponding to "group chat and dynamic sharing and other functions" is larger than the font size corresponding to the restriction reason. The restriction reason corresponding to "group chat and dynamic sharing and other functions" is: violation of the "Target Behavior Code".

[0157] For the restricted function "All social scene functions", "All social scene functions" can be displayed below the restriction reason corresponding to "Group chat and dynamic sharing and other functions". The restriction reason corresponding to "All social scene functions" is displayed below "All social scene functions", and the font size corresponding to "All social scene functions" is larger than the font size corresponding to the restriction reason. The restriction reason corresponding to "All social scene functions" is: violation of the "Target Behavior Code".

[0158] For the restricted function "Contact-related functions", the "Contact-related functions" can be displayed below the restriction reason corresponding to "All social scenario functions". The restriction reason corresponding to "Contact-related functions" is displayed below "Contact-related functions", and the font size corresponding to "Contact-related functions" is larger than the font size corresponding to the restriction reason. The restriction reason corresponding to "Contact-related functions" is: violation of the "Target Behavior Code".

[0159] The exception details interface can also display the jump entry 419 of the "Target Behavior Code". When a trigger operation is received for the jump entry 419, a target behavior code acquisition request can be sent to the server. The server can send the content of the target behavior code to the terminal corresponding to the first account, and then the content of the "Target Behavior Code" can be displayed.

[0160] For each abnormal function, the reason for the restriction can be displayed so that the user can understand the restriction reason. The jump entrance to the target behavior specification can also be displayed, and the content of the target behavior specification can be displayed so that the user can understand the content of the target behavior specification, thereby improving the user experience.

[0161] In some embodiments, when the abnormal account is the first account, at least one restriction removal function entrance is displayed, wherein the restriction removal function entrance is used to guide the removal of restrictions on abnormal functions, and different restriction removal function entrances correspond to different removal methods.

[0162] In some embodiments, the number of unrestriction function entrances may be pre-set. For example, the number of unrestriction function entrances may be two, specifically including a self-service unrestriction function entrance and an assisted unrestriction function entrance. The difference between the self-service unrestriction function entrance and the assisted unrestriction function entrance is that the assisted unrestriction function entrance requires customer service assistance to remove the function restriction, while the self-service unrestriction function entrance does not require customer service assistance.

[0163] See also Figure 8 If the abnormal account is the first account, the abnormal function display area 417 may display a self-service restriction removal function entry 421. The self-service restriction removal function entry 421 may be "Remove Restrictions" to guide the user to remove the restrictions on the abnormal function. The abnormality details interface may also display an auxiliary restriction removal function entry 418. The auxiliary restriction removal function entry 418 may be "Contact Customer Service" to guide the user to remove the restrictions on the abnormal function with the assistance of customer service.

[0164] The restriction removal function entrance may include a self-service restriction removal function entrance and an assisted restriction removal function entrance, which is equivalent to providing two different restriction removal function entrances. Users can use the corresponding method to remove restrictions on abnormal functions according to their actual needs.

[0165] See also Figure 8 The abnormal details interface can also display "Currently removable restrictions". "Currently removable restrictions" is located above the abnormal function display area 417, which is used to indicate that the abnormal function displayed in the abnormal function display area 417 can be removed.

[0166] See also Figure 9 , Figure 9 This is a second schematic diagram of the abnormality details interface of the first account provided in an embodiment of the present application. The abnormality details interface can also display "Unable to lift restrictions for the time being". "Unable to lift restrictions for the time being" is displayed above the abnormal function display area 417, which is used to indicate that the abnormal function displayed in the abnormal function display area 417 cannot be lifted at present. In this case, the abnormal function display area 417 also displays the current status of the abnormal account, specifically "Current status: Restrictions can be lifted after 2023.11.2011:00".

[0167] against Figure 9 In the corresponding case, the self-service restriction removal function entrance is not displayed, which means that the restriction on abnormal functions cannot be removed by self-service restriction removal. The restriction on abnormal functions can be removed with the assistance of customer service through the auxiliary restriction removal function entrance 418.

[0168] In some embodiments, abnormal functions correspond to different abnormal levels. Different abnormal levels have different entry points for removing restrictions. The number of entry points for removing restrictions can also be determined based on the number of types of abnormal levels. For example, if the number of abnormal functions is 4, the number of abnormal levels corresponding to the abnormal functions is 3, and the number of entry points for removing restrictions is 3.

[0169] For example, when the abnormality level is the lowest, the restriction removal function entry may be an entry for jumping to a restriction removal function in a standard commitment manner. When the abnormality level is the highest, the restriction removal function entry may be an auxiliary restriction removal function entry.

[0170] When the abnormality level is medium, the access point for lifting restrictions can be a jump to an access point that uses mobile phone number binding authentication to lift restrictions. The access point for lifting restrictions can also be a jump to an access point that uses friend authentication to lift restrictions.

[0171] Different abnormality levels correspond to different entrances to the restriction-releasing function, which can guide users to use different methods to remove restrictions on abnormal functions of different abnormality levels, thereby improving the user experience.

[0172] In response to the release trigger operation for the restriction release function entrance, the restriction release page is displayed. In some embodiments, in response to the release trigger operation for the auxiliary restriction release function entrance, the auxiliary restriction release page can be displayed.

[0173] The auxiliary restriction removal page may include an abnormal account information input area and a commitment collection area, wherein the abnormal account information input area is used to obtain information corresponding to the input abnormal account and the commitment collection area is used to collect the commitment made by the abnormal account to remove the abnormal account.

[0174] In response to the filling instruction for the abnormal account information input area, the content corresponding to the abnormal account information input area can be obtained. In response to the collection instruction for the commitment collection area, the content corresponding to the commitment collection area can be obtained.

[0175] The terminal can send the content corresponding to the abnormal account information input area and the content corresponding to the commitment collection area to the server. The server can assign the content corresponding to the abnormal account information input area and the content domain corresponding to the commitment collection area to the corresponding customer service, so that the customer service can review the content corresponding to the abnormal account information input area and the content corresponding to the commitment collection area to obtain the review results.

[0176] If the audit result indicates that the audit has passed, the server can delete the abnormal identification corresponding to the abnormal account, remove the function that restricts the abnormal account, and send the audit result to the terminal. If the audit result indicates that the audit has failed, the server can keep the abnormal identification corresponding to the abnormal account and keep the function that restricts the abnormal account. The server can send the audit result and the reason for failure to the terminal.

[0177] See also Figure 10 , Figure 10 This is a schematic diagram of an auxiliary restriction removal page provided in an embodiment of the present application. The auxiliary restriction removal page may include an abnormal account information input area 501 and a commitment collection area 502. In response to a fill instruction in abnormal account information input area 501, the corresponding content of abnormal account information input area 501 can be obtained. In response to a collection instruction in commitment collection area 502, the corresponding content of commitment collection area 502 can be obtained.

[0178] In response to the determination control ( Figure 10 The terminal may send the content corresponding to the abnormal account information input area 501 and the content corresponding to the commitment collection area 502 to the server according to the determination instruction (not numbered in the figure).

[0179] By responding to the release trigger operation for the auxiliary restriction release function entrance and displaying the auxiliary restriction release page, it is possible to release the restriction on abnormal functions through the release method corresponding to the auxiliary restriction release page.

[0180] In some embodiments, in response to a release triggering operation triggered on a self-service restriction removal function entrance, a self-service restriction removal page may be displayed.

[0181] The self-service restriction removal page may include a restriction removal method display area. The content displayed in the restriction removal display area varies depending on the restriction removal method. Restriction removal methods may include mobile phone number binding authentication, friend verification, and regulatory commitment.

[0182] If the restriction release method is the specification commitment method, the restriction release method display area may include a restriction reason sub-area, a specification to be read sub-area, and a restriction description sub-area. The restriction reason sub-area may include the reason for restricting the abnormal function. The specification to be read sub-area may include a display area for the specification to be read. The restriction description sub-area may include a description of the abnormal function.

[0183] The Restriction Reason sub-area may also display a Reason Acknowledgement control, which indicates that the reason for the restriction of the abnormal function has been learned. The Specifications to be Read sub-area may also display a Read Commitment control, which indicates that the specification has been read and that the user has committed to comply with it. The specification may be a target behavior specification. The Restriction Explanation sub-area may include a Commitment Acknowledgement control, which indicates that the user has learned the explanation for the restriction of the abnormal function and has committed to not engage in any behavior that would restrict the abnormal function.

[0184] See also Figure 11A , Figure 11A The first schematic diagram of the self-service restriction removal interface provided in the embodiment of the present application. The restriction removal method display area may include a restriction reason sub-area, a specification to be read sub-area, and a restriction description sub-area ( Figure 11A (not numbered in the middle).

[0185] The restriction reason sub-area displays "1. The behavior that violates the target behavior specification is xxx." The restriction reason sub-area also displays a reason acquisition control 503, which is used to indicate "I understand that the above behavior is a violation." In response to a confirmation operation triggered on reason acquisition control 503, reason acquisition control 503 may be displayed in a selected state.

[0186] The "Read the Target Code of Conduct, Comply with the Terms and Conditions, and Regulate Usage Behavior" sub-area is displayed. Also displayed in the "Read the Target Code of Conduct" sub-area is a "Read Commitment" control 504, which indicates "I have read and commit to comply." In response to a confirmation operation triggered on the "Read Commitment" control 504, the "Read Commitment" control 504 may be displayed in a selected state.

[0187] The restriction description sub-area displays "A will penalize the account that performs xxx, and will escalate the penalties for accounts that repeatedly perform the aforementioned behavior, including but not limited to: restricting function 1, restricting function 2, etc." The restriction description sub-area also displays an acknowledgement and commitment control 505, which indicates "I understand and promise not to violate the rules again." In response to a confirmation operation triggered on acknowledgement and commitment control 505, acknowledgement and commitment control 505 may be displayed in a selected state.

[0188] For example, a check mark may be placed in the box corresponding to the acknowledged commitment control 505 to indicate that the acknowledged commitment control 505 is in a selected state. Alternatively, the box corresponding to the acknowledged commitment control 505 may be filled in to indicate that the acknowledged commitment control 505 is in a selected state. Alternatively, the text description corresponding to the acknowledged commitment control 505 may be changed in color to indicate that the acknowledged commitment control 505 is in a selected state.

[0189] The text description corresponding to the acknowledgement and commitment control 505 is “I acknowledge and promise not to violate the rules again.” The manner in which the read commitment control 504 and the reason acquisition control 503 are displayed as selected is the same as the manner in which the acknowledgement and commitment control 505 is displayed as selected, and will not be repeated here.

[0190] When the reason acquisition control 503, the reading commitment control 504, and the acknowledgement commitment control 505 are all selected, in response to a confirmation operation triggered by the confirmation control displayed on the self-service restriction removal interface, a standard commitment request may be generated based on the selected reason acquisition control 503, the reading commitment control 504, and the acknowledgement commitment control 505. The terminal corresponding to the first account may send the standard commitment request to the server, and upon receiving the standard commitment request, the server may remove the restriction on the abnormal function.

[0191] In the case where the restriction removal method is the standard commitment method, it is possible to remove the restriction on abnormal functions through the standard commitment method.

[0192] If the restriction removal method is to bind a mobile phone number for authentication, the restriction removal method display area may include a first mobile phone number entry area and a function restriction removal instructions area. The first mobile phone number entry area is used to enter the mobile phone number bound to the first account. The function restriction removal instructions area explains how to remove function restrictions using the mobile phone number binding authentication method.

[0193] See also Figure 11B , Figure 11B The second schematic diagram of the self-service restriction removal interface provided in the embodiment of the present application. The restriction removal method display area may include the first mobile phone number filling area 506 and the function restriction removal description area ( Figure 11B The function restriction removal instructions area may display "Please enter your mobile phone number that can send and receive text messages to remove function restrictions."

[0194] In response to the filling operation triggered for the first mobile phone number filling area 506, the terminal corresponding to the first account can obtain the mobile phone number. In response to the confirmation instruction triggered for "next step", the verification code filling page can be displayed.

[0195] In response to the confirmation instruction triggered by "Next", the terminal corresponding to the first account can send the mobile phone number to the server, and the server can send a verification code to the terminal corresponding to the mobile phone number. After obtaining the verification code, the verification code can be filled in the verification code filling page.

[0196] In response to the confirmation operation triggered on the verification code filling page, a mobile phone number confirmation request can be generated based on the verification code. The terminal corresponding to the first account can send the mobile phone number confirmation request to the server. After receiving the confirmation request, the server can determine whether the verification code is consistent with the verification sent to the terminal corresponding to the first account. If they are consistent, the restriction on abnormal functions can be lifted.

[0197] In the event of inconsistency, the server may return verification failure information to the terminal corresponding to the first account, and the terminal corresponding to the first account may display the verification failure information.

[0198] When the restriction lifting method is the mobile phone number binding authentication method, the restriction on abnormal functions can be lifted by binding the mobile phone number authentication method.

[0199] If the restriction removal method is friend verification, the restriction removal method display area may include a verification requirements area and a second phone number field. The verification requirements area is used to describe the conditions that friends using the friend verification method must meet. The second phone number field is used to enter the friend's corresponding phone number.

[0200] See also Figure 11C , Figure 11CThis is a third schematic diagram of a self-service restriction removal interface provided in an embodiment of the present application. The restriction removal method display area may include a verification requirement description area 507 and a second mobile phone number filling area 508. The verification requirement description area 507 may include the conditions that the friend invited for verification must meet.

[0201] In response to the filling operation triggered for the second mobile phone number filling area 508, the terminal corresponding to the first account can obtain the mobile phone number. In response to the confirmation instruction triggered for "OK", the terminal corresponding to the first account can send the mobile phone number to the server, and the server can verify whether the account corresponding to the mobile phone number meets the conditions corresponding to the verification requirement description area 507.

[0202] If the conditions are met, the verification method can be sent to the terminal used by the account corresponding to the mobile phone number to complete the verification. If the conditions are not met, the reason for the non-satisfaction can be obtained and sent to the terminal corresponding to the first account, and the terminal corresponding to the first account can display the reason for the non-satisfaction.

[0203] If the terminal used by the account corresponding to the mobile phone number is fully verified based on the verification method, the server can lift the restriction on abnormal functions. In some embodiments, the verification method can be that the account corresponding to the mobile phone number sends a verification message to the first account, and if the first account receives the verification message, it means that the verification is successful.

[0204] When the restriction removal method is the friend verification method, the restriction on abnormal functions can be removed through the friend verification method.

[0205] By using the above-mentioned different methods of lifting restrictions on abnormal functions, the corresponding restriction lifting function entrance can be displayed while intercepting the call request, so that users can more efficiently submit complaints against abnormal accounts.

[0206] In some embodiments, when there is an abnormality in the first account and the reason information indicates that the first account is in a locked state, the lock duration corresponding to the first account is displayed, and an unlocking entry for unlocking the lock state is displayed.

[0207] The lockout duration starts when the first account is locked and ends when the first account is unlocked. During the lockout duration, the first account cannot make audio or video calls with other accounts. The unlocking entry provides instructions for unlocking the first account.

[0208] See also Figure 12 , Figure 12This is a third schematic diagram of a conversation interface provided in an embodiment of the present application. When an abnormality occurs in the first account and the reason information indicates that the first account is in a locked state, the conversation message area 415 may also display a lock duration display area 422 and a release entry 423.

[0209] The lock duration display area 422 may display “lock duration: 2023.11.21 10:00-2023.11.25.10:00”, that is, the lock duration is two days. To facilitate user understanding, the lock duration may display the time period corresponding to the lock state.

[0210] The reason information display area 414 may display "the first account is locked", or other text indicating that the first account is locked. The unlock entry 423 may display "unlock".

[0211] In response to the release trigger operation triggered by the release entry, a restriction release page can be displayed. The restriction release page is consistent with the restriction release page corresponding to the release restriction function entry, and will not be repeated here.

[0212] By displaying the locking time, the user can be easily informed of the locking time, and by displaying the unlocking entrance to unlock the state, the user can be easily unlocked, thereby improving the user experience.

[0213] In some embodiments, when there is an abnormality in the first account and the reason information indicates that there is an abnormality in the identity information corresponding to the first account, an identity verification prompt message and an identity verification entrance are displayed;

[0214] Among them, the identity verification prompt information is used to prompt to make an audio call or video call after the first account passes the identity verification, and the identity verification entrance is used to guide the identity verification for the first account.

[0215] See also Figure 13 , Figure 13 In the fourth schematic diagram of the conversation interface provided in an embodiment of the present application, when there is an anomaly in the first account and the reason information indicates an anomaly in the identity information corresponding to the first account, the reason information display area 414 may display "There is an anomaly in the identity information of the first account. Restrictions on the first account can be lifted after identity verification is passed." The phrase "Restrictions on the first account can be lifted after identity verification is passed" is an identity verification prompt.

[0216] The conversation message area 415 may also display an identity verification entry 424 , which may be configured as “Verify Identity”. It may also be configured as other text based on actual usage requirements.

[0217] In response to a trigger operation on identity verification entry 424, a self-service restriction removal interface corresponding to the mobile phone number authentication method can be displayed, and a self-service restriction removal interface corresponding to the friend authentication method can also be displayed. The real-time image captured by the image acquisition device can also be displayed to facilitate facial recognition. This is all reasonable.

[0218] The method of displaying the identity verification prompt information and the identity verification entrance in the conversation message area can guide the user to perform identity verification through the identity verification entrance.

[0219] In some embodiments, see Figure 14 , Figure 14 This is a third schematic diagram of the abnormality details interface for the first account provided in an embodiment of the present application. The abnormal function display area 417 can display the functions restricted for the abnormal account. For the "audio and video call function," the restriction reason corresponding to the "audio and video call function" can be displayed below the "audio and video call function." The font size corresponding to the "audio and video call function" is larger than the font size corresponding to the restriction reason. The restriction reason for the "audio and video call function" is "identity information abnormality." The audio and video call function refers to the function of making audio calls and the function of making video calls.

[0220] In the case of an abnormal identity information, the abnormality details interface may also display an identity verification prompt, specifically "After verifying your identity, you can lift the following restrictions." The abnormal function display area 417 may display a restriction lifting function entry 421, which may be "Identity Verification."

[0221] Displaying the identity verification prompt information and the identity verification entrance (i.e., the entrance to lift the restricted function) on the exception details interface can guide the user to perform identity verification through the identity verification entrance.

[0222] In some embodiments, when there are multiple second accounts and some of the second accounts have abnormalities, a call interface is displayed, wherein the call interface is used to indicate that a call is in progress with the second account that does not have the abnormality.

[0223] The call interface may include a video call interface and an audio call interface. If the call interface is a video call interface, the video call interface may include multiple images captured by the imaging device of the terminal corresponding to the second account without any abnormality, as well as images captured in real time by the terminal corresponding to the first account. The video call interface does not include images captured in real time by the imaging device of the terminal corresponding to the second account with any abnormality.

[0224] See also Figure 15 , Figure 15Schematic diagram of a video call interface provided in an embodiment of the present application. The video call interface may include an image 426 captured in real time by a terminal corresponding to a first account, and images captured by image devices of five terminals corresponding to second accounts without any abnormality ( Figure 15 Only an image 425 of the terminal corresponding to the second account without abnormality is shown in FIG. 425 . The description of the microphone control 406 , the hang-up control 407 and the speaker control 408 can be found in FIG. Figure 5 , I will not go into details here.

[0225] In some embodiments, the proportion of images captured in real time by the terminal corresponding to the first account in the video call interface can be greater than the proportion of images captured by the imaging device of the terminal corresponding to the second account, which is not experiencing any abnormalities. This setting is based on usage requirements and is not specifically limited here.

[0226] The method of displaying the video call interface of the ongoing call with the second account without any abnormality can facilitate the user to intuitively see the image that the user who joined the video call wants to share.

[0227] If the call interface is an audio call interface, the audio call interface can include multiple avatars corresponding to the second account without any abnormalities, as well as the avatar corresponding to the first account. The audio call interface does not include content corresponding to the second account with abnormalities, for example, it does not include the avatar of the second account with abnormalities. This makes it easier for users to view users who have joined the audio call.

[0228] If there are multiple second accounts and some of them have abnormalities, the abnormal second accounts cannot join the call, while the first account and the normal second accounts can make calls normally. In this way, the user experience can be further improved while ensuring the security of the first account and the normal second accounts.

[0229] In some embodiments, Figure 3 After step 103, if there is an abnormality in the second account, a message sending prompt is displayed.

[0230] The message sending prompt is used to prompt the second account to send an account abnormality prompt. If the second account has an abnormality, the server can generate a message sending prompt corresponding to the second account based on a pre-set template and send the message sending prompt to the terminal corresponding to the first account, so that the terminal can display the message sending prompt.

[0231] In response to a sending instruction for sending a message prompt information, an account abnormality prompt information is sent in the form of a text message.

[0232] In some embodiments, in response to an instruction to send a message prompt, the terminal corresponding to the first account can send an account abnormality prompt to the terminal corresponding to the second account in the form of a text message. In this way, the terminal corresponding to the second account can receive the account abnormality prompt and display the account abnormality prompt.

[0233] After the terminal corresponding to the first account sends the account abnormality prompt information, the account abnormality prompt information and the avatar corresponding to the first account can be combined into a conversation message, and the conversation message can be displayed in the conversation message areas corresponding to the terminal corresponding to the first account and the terminal corresponding to the second account.

[0234] In the event of an abnormality in the second account, an account abnormality prompt message is sent in the form of a text message. This allows the user corresponding to the second account to be informed of the account abnormality prompt message, and can further improve the user experience while ensuring the security of the first account.

[0235] In some embodiments, when there is an abnormality in the second account and there is a target relationship between the first account and the second account, the interface jumps from the conversation interface to the dialing interface.

[0236] Among them, the dialing interface includes the telephone number of the user corresponding to the second account, and the target relationship is the pre-bound relationship between the first account and the second account. For example, the target relationship can be a relative relationship, a couple relationship, a friend relationship, etc., which is not specifically limited here.

[0237] If there is an abnormality in the second account and there is a target relationship between the first account and the second account, the server can send a jump instruction carrying the mobile phone number of the second account to the terminal corresponding to the first account. Upon receiving the jump instruction, the terminal corresponding to the first account can jump to the dialing interface and fill in the mobile phone number of the second account in the dialing interface, so that the user can contact the user corresponding to the second account more quickly and conveniently.

[0238] In some embodiments, if an abnormality exists in the second account and the duration of the call abnormality prompt message displayed exceeds the target duration, the call abnormality prompt message is canceled and a resource transfer warning message is displayed instead. The resource transfer warning message is used to warn that an abnormality exists in the second account and that there is a risk of executing a resource transfer operation for the second account.

[0239] See also Figure 16 , Figure 16In the fifth schematic diagram of the conversation interface provided in the embodiment of the present application, when there is an abnormality in the second account and the duration of displaying the call abnormality prompt message is longer than the target duration, the call abnormality prompt message can be canceled and the resource transfer warning message 427 can be displayed in the conversation message area 415. The resource transfer warning message 427 is "There is a risk in the second account. Please carefully verify the identity of the other party and protect the security of the account."

[0240] In the event that an abnormality occurs in the second account, a resource transfer warning message is displayed to remind the user that there is a risk in executing the resource transfer operation for the second account.

[0241] In some embodiments, Figure 3 Prior to step 101, the behavior data of the first account is obtained and sent to the server. The behavior data is used by the server to perform an abnormality analysis on the first account and store the first account as an abnormal account if the analysis result indicates that the first account is abnormal.

[0242] The terminal corresponding to the first account can obtain the behavioral data of the first account and send the behavioral data to the server. The server can input the behavioral data of the first account and the pre-stored abnormality level of the first account into the pre-trained anomaly detection model to obtain a detection result that can characterize whether there is an abnormality in the first account.

[0243] If the detection result indicates that the first account is abnormal, the detection result also includes the reason for the abnormality. The server can add an abnormality identifier to the string corresponding to the first account so that the server can obtain the abnormal account from all pre-stored account numbers.

[0244] The server can also restrict the functions of the first account based on the abnormal reason (equivalent to taking measures against the first account), thereby obtaining the abnormal function. The server can store the abnormal account and abnormal function in correspondence, thereby obtaining a correspondence between the abnormal account and abnormal function. This can be used to send the abnormal account and abnormal function that the terminal wants to display to the terminal, thereby enabling the terminal to display the abnormal account and abnormal function.

[0245] The server can determine the text corresponding to the abnormal cause from pre-stored candidate abnormal causes and candidate texts based on the abnormal cause, and configure according to the text corresponding to the abnormal cause and the abnormal cause to obtain the restriction reason, wherein there is a corresponding relationship between the restriction reason and the abnormal function.

[0246] The server can also generate reason information based on the first account and a pre-stored template. Reason information can include various types, as detailed above and omitted here. In this way, the server can determine whether the first account is an abnormal account based on the behavioral data. If the first account is an abnormal account, it can obtain the restriction reason, abnormal function, and reason information, so that the corresponding information can be sent to the terminal corresponding to the first account, thereby facilitating the user to obtain the corresponding information.

[0247] In some embodiments, when the first account removes restrictions on abnormal functions through the restriction removal function entrance, the server can generate an appeal record based on all content corresponding to the first account removing restrictions and store the appeal record in the database.

[0248] Appeal records can be used to train anomaly detection models online to ensure their accuracy. Appeal records can also be used to determine the anomaly level corresponding to the first account. For example, if the restriction reason is the same and the restriction occurs multiple times, the anomaly level can be increased.

[0249] The handling strength of abnormal functions corresponding to different abnormal levels is different. In this way, it is possible to start from low-intensity handling and gradually transition to the highest-intensity handling, and to more smoothly transition the handling strength for abnormal accounts of different abnormal levels.

[0250] The lowest level of processing may be to limit only the audio and video call capabilities. As the abnormality level increases, the restriction of audio and video call capabilities can be combined with freezing, restriction of all social functions, and kicking off functions, thereby increasing the processing intensity.

[0251] That is to say, the session processing method provided in the embodiment of the present application will not restrict all functions of the account with abnormalities in all abnormal situations, but will only restrict some functions. This is equivalent to using a flexible restriction method to restrict the account with abnormalities, which can reduce potential customer risks.

[0252] When the detection results of the anomaly detection model again indicate that there is an anomaly in the first account, the corresponding anomaly cause can be compared with the anomaly cause stored in the appeal record to determine whether there is an anomaly in the first account. In this way, the accuracy of determining whether there is an anomaly in the first account can be further improved.

[0253] See also Figure 17 , Figure 17 A second flow chart of the session processing method provided in an embodiment of the present application.

[0254] Terminal 400 - 1 may execute steps 201 and 202 , and terminal 400 - 2 may execute steps 203 and 204 .

[0255] In step 201, behavioral data of a first account is obtained.

[0256] That is, the terminal 400 - 1 obtains the behavior data of the first account.

[0257] In step 202, the behavior data of the first account is sent.

[0258] That is, the terminal 400 - 1 sends the behavior data of the first account to the server 200 .

[0259] In step 203, the behavior data of the second account is obtained.

[0260] That is, terminal 400 - 2 obtains the behavior data of the second account.

[0261] In step 204, the behavior data of the second account is sent.

[0262] That is, the terminal 400 - 2 sends the behavior data of the second account to the server 200 .

[0263] In step 205 , the behavior data of the first account and the behavior data of the second account are detected to obtain a detection result.

[0264] After obtaining the behavior data of the first account and the behavior data of the second account, the server 200 may input the behavior data of the first account and the behavior data of the second account into a pre-trained anomaly detection model to obtain a detection result.

[0265] If the detection result indicates that the first account is abnormal, the first account can be stored as an abnormal account, and the corresponding abnormal function, restriction reason, and reason information can be obtained. If the second account is abnormal, the second account can be stored as an abnormal account, and the corresponding abnormal function, restriction reason, and reason information can be obtained.

[0266] Taking the example of a first account requesting an audio call with a second account, step 206 may be executed.

[0267] In step 206, a call request carrying the first account and the second account is sent.

[0268] Terminal 400-1 can display a conversation interface for the first account and the second account. In response to a call instruction triggered based on the conversation interface, it can display a call waiting interface for the second account to accept the call request, and send a call request carrying the first account and the second account to the server 200.

[0269] In step 207 , the pre-stored abnormal account number is matched with the first account number and the second account number respectively, and abnormal results of the first account number and the second account number are determined based on the matching results.

[0270] If the first account number matches a pre-stored abnormal account number, it indicates that there is an abnormality in the first account number. If the first account number does not match a pre-stored abnormal account number, it indicates that there is no abnormality in the first account number. If the second account number matches a pre-stored abnormal account number, it indicates that there is an abnormality in the second account number. If the character string corresponding to the second account number does not match a pre-stored abnormal account number, it indicates that there is no abnormality in the second account number.

[0271] In step 208 , if there is no abnormality in the first account and the second account, a call request is sent.

[0272] When there is no abnormality in the first account and the second account, the server 200 may send a call request to the terminal 400 - 2 . After receiving the call request, the terminal 400 - 2 may establish a call connection with the terminal 400 - 1 .

[0273] In step 209, when there is an abnormality in at least one of the first account and the second account, an instruction to block the call request and a call abnormality prompt message are sent.

[0274] When an abnormality occurs in at least one of the first account and the second account, the server 200 may send an instruction to block the call request and a call abnormality prompt message to the terminal 400-1. After receiving the instruction to block the call request and the call abnormality prompt message, the terminal 400-1 may cancel the display of the call waiting page and display the call abnormality prompt message.

[0275] In an embodiment of the present application, when an abnormality occurs in at least one of the first account and the second account, a call request from the first account to make an audio call or a video call with the second account can be blocked, that is, the audio call function and the video call function of the account with the abnormality are restricted. In addition, a call abnormality prompt message can be displayed to remind both the account with the abnormality and the account without the abnormality, thereby improving the security of the account without the abnormality.

[0276] The following describes an exemplary application of the embodiments of the present application in a practical application scenario.

[0277] See also Figure 18 , Figure 18 This is a schematic diagram of the third flow chart of the session processing method provided in an embodiment of the present application.

[0278] In step 301, the platform's risk control strategy identifies risk situations and marks the account for disposal.

[0279] When an abnormal account engages in risky behavior within the platform, that is, when an abnormal account engages in risky behavior through the client, the behavioral data of the abnormal account can be obtained and input into a pre-trained anomaly detection model to obtain detection results.

[0280] Risk control strategies identify risk situations by feeding behavioral data into a pre-trained anomaly detection model to generate detection results. If the detection results indicate an account is abnormal, the account can be flagged as abnormal and some functions of the account with the abnormality can be restricted (equivalent to marking the account for disposal).

[0281] In step 302, the interception text is configured to obtain interception reason 1, interception reason 2, etc.

[0282] The detection result includes the abnormal reason. The server can determine the corresponding text of the abnormal reason from the pre-stored candidate abnormal reasons and candidate texts according to the abnormal reason, and configure it according to the corresponding text and abnormal reason (equivalent to recording the reason for disposal and interception text configuration) to obtain the restriction reason. Among them, the restriction reason is "interception reason 1, interception reason 2".

[0283] In step 303, the audio and video request reaches the service backend.

[0284] If the abnormal account's audio and video call capabilities are connected to a normal account, the audio and video request can reach the service backend (equivalent to the terminal sending a call request containing both the abnormal account and the normal account to the server). After receiving the call request, the server can match the pre-stored abnormal account with the abnormal account and the normal account, and match the abnormal account with the pre-stored abnormal account.

[0285] In step 304, the interception reason is displayed according to the interception text.

[0286] If the server determines that there is an abnormality in the abnormal account, it can send an instruction to block the call request (equivalent to the call request being interrupted) and a call abnormality prompt message to the terminal corresponding to the abnormal account. If the user wants to view the abnormal details corresponding to the abnormal account, the terminal can send an abnormal details viewing request to the server. After receiving the abnormal details viewing request, the server can obtain the abnormal function and restriction reason (equivalent to the interception reason) corresponding to the abnormal account. After obtaining the abnormal function and restriction reason, the terminal can display the abnormal function and restriction reason so that the user can know the abnormal function and restriction reason (that is, the abnormal details information).

[0287] In step 305, the user sees the reason and chooses to accept or take further customer complaint path according to the page prompts.

[0288] After the user learns about the abnormal function and the reason for the restriction, he or she can choose to close the abnormal details page (equivalent to choosing to accept), or choose to lift the restriction on the abnormal function through the restriction removal entrance (equivalent to making a customer complaint). The corresponding content of the restriction removal entrance can be found in the corresponding instructions and will not be repeated here.

[0289] In step 306, the database stores the relevant records.

[0290] When the first account removes the restriction on the abnormal function through the restriction removal function entrance, the server can generate a complaint record (equivalent to a related record) based on all the content corresponding to the restriction removal by the first account, and store the complaint record in the database.

[0291] The following continues to describe the exemplary structure of the session processing device 455 provided in the embodiment of the present application implemented as a software module. In some embodiments, such as Figure 2 As shown, the software modules stored in the session processing device 455 of the memory 440 may include:

[0292] Display module 4551, used to display a conversation interface between the first account and the second account;

[0293] The display module 4551 is further configured to display a call waiting interface indicating waiting for the second account to accept the call request in response to a call instruction triggered based on the conversation interface;

[0294] The call request is used to request an audio call or a video call with the second account;

[0295] Prompt module 4552, configured to cancel display of the call waiting interface and display call abnormality prompt information when at least one of the first account and the second account has an abnormality;

[0296] The call abnormality prompt information is used to prompt that the first account cannot make an audio call or a video call with the second account.

[0297] In some embodiments, the prompt module 4552 is further configured to display an abnormality prompt window in the conversation interface, and display the call abnormality prompt information through the abnormality prompt window.

[0298] The conversation processing device may also include: a display cancellation module, which is used to cancel the display of the abnormal prompt window in response to a determination instruction triggered based on the abnormal prompt window after the call abnormal prompt information is displayed; wherein, the determination instruction is used to indicate that the call abnormal prompt information has been known.

[0299] In some embodiments, the display module 4551 is also used to display an exception details viewing entrance after the call waiting interface is canceled; wherein, the exception details viewing entrance is used to guide the viewing of the exception details information corresponding to the abnormal account, and the abnormal account is the account with the abnormality between the first account and the second account.

[0300] In some embodiments, the display module 4551 is also used to display the abnormal account and abnormal function in response to a trigger operation on the abnormal details viewing entrance after the abnormal details viewing entrance is displayed, wherein the abnormal function is a function for restricting the abnormal account.

[0301] In some embodiments, the display module 4551 is also used to display at least one restriction removal function entrance when the abnormal account is the first account; wherein, the restriction removal function entrance is used to guide the removal of restrictions on the abnormal function, and different restriction removal function entrances correspond to different removal methods.

[0302] In some embodiments, the display module 4551 is also used to display the restriction reason for each of the abnormal functions; when the restriction reason includes a target behavior specification, the jump entry of the target behavior specification is displayed; wherein, the jump entry is used to guide the viewing of the content of the target behavior specification; when a trigger operation for the jump entry is received, the content of the target behavior specification is displayed.

[0303] In some embodiments, the call abnormality reminder information includes information about the reason why the first account cannot make an audio call or a video call with the second account;

[0304] The display module 4551 is further configured to display the reason information in a weak reminder manner in a conversation message area in the conversation interface for displaying conversation messages.

[0305] In some embodiments, the display module 4551 is also used to display the lockout duration corresponding to the first account and display an unlocking entry for unlocking the lockout status when there is an abnormality in the first account and the reason information indicates that the first account is in a locked state; wherein, during the lockout duration, the first account cannot make audio calls or video calls with other accounts, and the unlocking entry is used to guide the unlocking of the lockout status of the first account.

[0306] In some embodiments, the display module 4551 is also used to display identity verification prompt information and identity verification entry when there is an abnormality in the first account and the reason information indicates that there is an abnormality in the identity information corresponding to the first account; wherein, the identity verification prompt information is used to prompt to make an audio call or video call after the first account passes the identity authentication, and the identity verification entry is used to guide the identity verification for the first account.

[0307] In some embodiments, the display interface 4551 is further used to display a call interface when there are multiple second accounts and some of the second accounts have abnormalities; wherein the call interface is used to indicate that a call is in progress with the second account that does not have any abnormalities.

[0308] In some embodiments, the display module 4551 is further configured to display a message sending prompt message when an abnormality occurs in the second account; wherein the message sending prompt message is configured to prompt the second account to send an account abnormality prompt message. In response to a sending instruction for the message sending prompt message, the account abnormality prompt message is sent as a text message.

[0309] In some embodiments, the session processing device may further include:

[0310] A jump module is used to jump from the conversation interface to the dialing interface when there is an abnormality in the second account and there is a target relationship between the first account and the second account; wherein the dialing interface includes the telephone number of the user corresponding to the second account.

[0311] In some embodiments, the display module 4551 is also used to cancel the display of the call abnormality prompt information and display the resource transfer warning information when there is an abnormality in the second account and the duration of displaying the call abnormality prompt information is greater than the target duration; wherein, the resource transfer warning information is used to warn that there is an abnormality in the second account and there is a risk of executing the resource transfer operation for the second account.

[0312] In some embodiments, the session processing device may further include:

[0313] a request sending module, configured to send the call request carrying the first account and the second account to the server after the call waiting interface for indicating waiting for the second account to accept the call request is displayed; wherein the call request is used by the server to obtain pre-stored abnormal account numbers, match the pre-stored abnormal account numbers with the first account and the second account respectively, and determine abnormal results for the first account and the second account based on the matching results.

[0314] The result receiving module is configured to receive an instruction to block the call request and the call abnormality prompt information sent by the server when the abnormal result indicates that at least one of the first account and the second account is abnormal.

[0315] In some embodiments, the session processing device may further include:

[0316] A data sending module is used to obtain behavioral data of the first account before displaying the conversation interface between the first account and the second account, and send the behavioral data of the first account to the server; wherein the behavioral data is used by the server to perform an abnormality analysis on the first account, and when the analysis result indicates that there is an abnormality in the first account, the first account is stored as an abnormal account.

[0317] In some embodiments, the session processing device may further include:

[0318] An input module is configured to input the first account and the second account into a pre-trained anomaly recognition model after a call waiting interface indicating waiting for the second account to accept a call request is displayed, to obtain an anomaly recognition result, wherein the anomaly recognition result is configured to indicate whether at least one of the first account and the second account has an anomaly.

[0319] An embodiment of the present application provides a computer program product, which includes computer-executable instructions. The computer-executable instructions are stored in a computer-readable storage medium. A processor of a terminal reads the computer-executable instructions from the computer-readable storage medium, and the processor executes the computer-executable instructions, so that the terminal executes the above-mentioned session processing method of the embodiment of the present application.

[0320] The embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions or computer programs are stored. When the computer-executable instructions or computer programs are executed by a processor, the processor will execute the session processing method provided by the embodiment of the present application, for example, Figure 3 The session processing method shown.

[0321] In some embodiments, the computer-readable storage medium may be a memory such as RAM, ROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

[0322] In some embodiments, computer-executable instructions may be in the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0323] As an example, computer-executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file that stores other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinating files (e.g., files storing one or more modules, subroutines, or code portions).

[0324] By way of example, computer-executable instructions may be deployed to be executed on one electronic device, or on multiple electronic devices located at one site, or on multiple electronic devices distributed across multiple sites and interconnected by a communication network.

[0325] In summary, the technical effects achieved by the embodiments of the present application are as follows:

[0326] The conversation processing method provided in the embodiment of the present application can cancel the display of the call waiting interface when there is an abnormality in at least one of the first account and the second account, which is equivalent to blocking the call request of the first account to make an audio call or a video call with the second account. It can block the call requests corresponding to all accounts with abnormalities, which is equivalent to restricting the audio call function and video call function of the account with abnormalities, and can also display call abnormality prompt information to remind the account with abnormalities and normal accounts (accounts without abnormalities), thereby improving the security of normal accounts.

[0327] The conversation processing method provided in the embodiment of the present application can start from low-intensity processing and gradually transition to the highest-intensity processing, and can more smoothly transition the processing intensity for abnormal accounts of different abnormal levels.

[0328] The session processing method provided in the embodiment of the present application will not restrict all functions of accounts with abnormalities in all abnormal situations, but will only restrict some functions. This is equivalent to using a flexible restriction method to restrict accounts with abnormalities, which can reduce potential customer risks.

[0329] The session processing method provided in the embodiment of the present application can intercept call requests while ensuring that users can quickly and directly access unblocking requests, so that users can more efficiently submit complaints about abnormal accounts.

[0330] The above description is merely an embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, and improvements made within the spirit and scope of the present application are included in the scope of protection of the present application.

Claims

1. A session processing method, It is characterized in that The method comprises: Displaying a conversation interface between the first account and the second account; In response to a call instruction triggered based on the conversation interface, displaying a call waiting interface for indicating waiting for the second account to accept the call request; The call request is used to request an audio call or a video call with the second account; When at least one of the first account and the second account is abnormal, canceling the call waiting interface and displaying call abnormality prompt information; The call abnormality prompt information is used to prompt that the first account cannot make an audio call or a video call with the second account.

2. The method according to claim 1, It is characterized in that The display of call abnormality prompt information includes: Displaying an abnormal prompt window in the conversation interface, and displaying the abnormal call prompt information through the abnormal prompt window; After displaying the call abnormality prompt information, the method further includes: In response to a determination instruction triggered based on the abnormal prompt window, canceling display of the abnormal prompt window; The confirmation instruction is used to indicate that the call abnormality prompt information has been obtained.

3. The method according to claim 1, It is characterized in that After canceling the display of the call waiting interface, the method further includes: Display the abnormal details viewing entrance; Among them, the abnormal details viewing entrance is used to guide the viewing of abnormal details information corresponding to the abnormal account, and the abnormal account is the account with the abnormality in the first account and the second account.

4. The method according to claim 3, It is characterized in that After displaying the abnormal details viewing entrance, the method further includes: In response to a trigger operation on the abnormal details viewing entrance, the abnormal account and abnormal function are displayed, wherein the abnormal function is a function that restricts the abnormal account.

5. The method according to claim 4, It is characterized in that The method further comprises: In the case where the abnormal account is the first account, displaying at least one restriction removal function entry; The restriction release function entry is used to guide the release of restrictions on the abnormal function, and different restriction release function entries correspond to different release methods.

6. The method according to claim 4, It is characterized in that The method further comprises: For each of the abnormal functions, displaying a restriction reason for restricting the abnormal function; In the case where the restriction reason includes a target behavior specification, displaying a jump entry of the target behavior specification; Wherein, the jump entry is used to guide the viewing of the content of the target behavior specification; When a trigger operation for the jump entry is received, the content of the target behavior specification is displayed.

7. The method according to claim 1, It is characterized in that The call abnormality reminder information includes information about the reason why the first account cannot make an audio call or a video call with the second account; The method further comprises: In the session message area for displaying session messages in the session interface, the reason information is displayed in a weak reminder manner.

8. The method according to claim 7, wherein, the method further includes: When the first account is abnormal and the reason information indicates that the first account is in a locked state, display the lock duration corresponding to the first account and display an unlocking entry for unlocking the locked state; Wherein, within the lock duration, the first account cannot make an audio call or a video call with other accounts, and the unlocking entry is used to guide the unlocking of the locked state of the first account.

9. The method according to claim 7, wherein, the method further includes: When the first account is abnormal and the reason information indicates that the identity information corresponding to the first account is abnormal, display an identity verification prompt message and an identity verification entry; Wherein, the identity verification prompt message is used to prompt to make an audio call or a video call after the first account passes the identity verification, and the identity verification entry is used to guide the identity verification for the first account.

10. The method according to claim 1, wherein, the method further includes: When the number of the second accounts is multiple and some of the second accounts are abnormal, display a call interface; Wherein, the call interface is used to indicate that a call is being made with the second accounts that are not abnormal.

11. The method according to claim 1, wherein, the method further includes: When the second account is abnormal, display a message sending prompt message; Wherein, the message sending prompt message is used to prompt to send an account abnormality prompt message to the second account; In response to a sending instruction for the message sending prompt message, send the account abnormality prompt message in the form of a text message.

12. The method according to claim 1, wherein, the method further includes: When the second account is abnormal and there is a target relationship between the first account and the second account, jump from the session interface to a dialing interface; Wherein, the dialing interface includes the phone number of the user corresponding to the second account.

13. The method according to claim 1, wherein, the method further includes: When the second account is abnormal and the duration of displaying the call abnormality prompt message is greater than a target duration, cancel the display of the call abnormality prompt message and display a resource transfer warning message; Wherein, the resource transfer warning message is used to warn that the second account is abnormal and there is a risk of executing a resource transfer operation for the second account.

14. The method according to claim 1, wherein, after displaying the call waiting interface for indicating waiting for the second account to accept the call request, the method further includes: Send the call request carrying the first account and the second account to the server; Among them, the call request is used for the server to obtain pre-stored abnormal accounts, match the pre-stored abnormal accounts with the first account and the second account respectively, and determine the abnormal results of the first account and the second account based on the matching results; In the case where the abnormal result indicates that at least one of the first account and the second account is abnormal, receive an instruction for blocking the call request and the call abnormal prompt information sent by the server.

15. The method according to claim 14, characterized in that, Before displaying the session interface for the first account and the second account to have a session, the method further includes: Obtain the behavior data of the first account, and send the behavior data of the first account to the server; Among them, the behavior data is used for the server to perform abnormal analysis on the first account, and when the analysis result indicates that the first account is abnormal, store the first account as an abnormal account.

16. The method according to claim 1, characterized in that, After displaying the call waiting interface for indicating waiting for the second account to accept the call request, the method further includes: Input the first account and the second account into a pre-trained abnormal recognition model to obtain an abnormal recognition result; Among them, the abnormal recognition result is used to indicate whether at least one of the first account and the second account is abnormal.

17. A session processing device, characterized in that, The device includes: A display module for displaying a session interface for the first account and the second account to have a session; The display module is further configured to, in response to a call instruction triggered based on the session interface, display a call waiting interface for indicating waiting for the second account to accept the call request; Among them, the call request is used to request an audio call or a video call with the second account; A prompt module for, in the case where at least one of the first account and the second account is abnormal, canceling the display of the call waiting interface and displaying call abnormal prompt information; Among them, the call abnormal prompt information is used to prompt that the first account cannot have an audio call or a video call with the second account.

18. An electronic device, characterized in that, The terminal includes: A memory for storing computer-executable instructions; A processor for, when executing the computer-executable instructions stored in the memory, implementing the session processing method according to any one of claims 1 to 16.

19. A computer-readable storage medium storing computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or the computer program are executed by a processor, the session processing method according to any one of claims 1 to 16 is implemented.

20. A computer program product including computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or the computer program are executed by a processor, the session processing method according to any one of claims 1 to 16 is implemented.

Images