Video call method and electronic device

Abstract

A video call method and an electronic device, relating to the technical field of terminals. The method comprises: adding a first user as a friend; making a video call with the first user; when a first condition is satisfied, detecting whether there is a risk of face swapping for the face of the first user in the video call, and upon detecting that there is a risk of face swapping, displaying a first prompt; when a second condition is satisfied, displaying a second prompt for detecting a risk of face swapping; in response to a detection confirmation operation on the second prompt, detecting whether there is a risk of face swapping, and prompting a detection process; and after a detection result is obtained, displaying a third prompt, the detection result comprising that there is a risk of face swapping or there is no risk of face swapping. In this way, when different conditions are satisfied, face swapping detection can be triggered in different manners, thereby providing different detection experiences.

Description

A video call method and electronic device

[0001] This application claims priority to Chinese Patent Application No. 202410841170.6, filed with the State Intellectual Property Office of China on June 26, 2024, entitled "A Video Call Method and Electronic Device", and to Chinese Patent Application No. 202411044507.7, filed with the State Intellectual Property Office of China on July 30, 2024, entitled "A Video Call Method and Electronic Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to a video call method and electronic device. Background Technology

[0003] Mobile phones, tablets, and other electronic devices typically offer video calling functionality. For example, if an electronic device has a social chat application installed, it can provide video calling capabilities through that application.

[0004] During video calls, both parties can see each other's faces, making it easier to verify each other's identities and build mutual trust. However, some individuals with ulterior motives exploit this vulnerability. They use artificial intelligence (AI) face-swapping technology to replace the face of the person on the other end of the video call with that of a familiar face, such as a relative, friend, or superior, to gain the other party's trust. They then make requests for money transfers or payments, which can easily lead to financial losses and a negative user experience. Summary of the Invention

[0005] This application provides a video call method and an electronic device that can detect the risk of face swapping during video calls. Furthermore, it can trigger face swapping detection and provide prompts in different ways under different conditions, thereby providing different detection experiences.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] Firstly, this application provides a video call method applied to an electronic device, specifically: adding a first user as a friend, such as through a social chat application, where the first friend can be any added friend; and then conducting a video call with the first user. It should be understood that a video call with the first user is essentially an electronic device establishing a video call with a device logged into the first user's account.

[0008] Specifically, if the first condition (the detection condition in the active detection section below) is met, the system detects whether there is a risk of face swapping on the face of the first user in the video call. If a face swapping risk is detected, a first prompt (prompt e in the section below) is displayed. In other words, if the first condition is met, the system actively detects whether there is a risk of face swapping and provides a prompt when such a risk is detected. Therefore, the active detection method does not affect the video call except when a face swapping risk is detected.

[0009] In this process, if the second condition is met (as indicated by prompts g or h below), a second prompt for detecting face-swapping risk is displayed (as indicated by prompts g or h below). In response to a confirmation operation on the second prompt (such as triggering a detection control), the system checks for face-swapping risk and displays the detection process. After obtaining the detection result, a third prompt (as indicated by prompt j below) is displayed, indicating whether face-swapping risk exists or not. In other words, if the second condition is met, a prompt for detecting face-swapping risk can be displayed first, and then the passive detection for face-swapping risk is triggered only after user confirmation. During the passive detection process, the system displays the detection progress, such as showing the animation of the detection in progress, and provides prompts regardless of whether there is a risk or not. Therefore, in the passive detection method, both the detection process and the detection result are visible, allowing users to understand the detection process and result after confirming the detection.

[0010] The first and second conditions mentioned above differ; generally, the first condition has lower requirements, while the second condition has higher requirements. In other words, the first condition is easier to meet, while the second condition is more difficult. Therefore, in most cases, automatic detection can be used to detect face-swapping risks, minimizing the impact on video calls. In a few cases, passive detection can be used to detect face-swapping risks, allowing users to understand the detection process and results.

[0011] In summary, by adopting this application, face-swapping detection and prompts can be triggered in different ways under different conditions, thereby providing different detection experiences. For example, in the active detection method, there is no risk of face-swapping, while in the passive detection method, there is awareness throughout the process.

[0012] In one possible design approach of the first aspect, the first condition or the second condition includes at least one of the following:

[0013] The time difference between adding the first user as a friend and the start of the video call is within the first duration (duration 5 or 6 as shown below), meaning the first user is a friend added within a short period of time.

[0014] The first user is the first friend added. For example, the first friend added after an electronic device installs a chat application.

[0015] The video call is the first video call with the first user.

[0016] The video call is initiated by the first user.

[0017] The first user is in the detection list of the electronic device (list 1 below). The detection list records the list of the first number of users recently added by the electronic device (number 1 below). That is, the first user is one of the certain number of friends recently added by the electronic device.

[0018] Electronic devices may pose risks, such as receiving risky information, receiving overseas calls, downloading unknown applications and performing actions such as entering bank account numbers, transferring funds, or sharing screens.

[0019] In other words, electronic devices can detect or alert users to face-swapping risks in video calls, thereby improving the targeting of face-swapping detection and avoiding a large number of invalid detections.

[0020] In one possible design of the first aspect, the aforementioned display of the first prompt includes: if the video call has not ended when a face-swapping risk is detected, displaying the first prompt on the video call interface, the first prompt including a re-detection control and / or a screen recording control; if the video call has ended when a face-swapping risk is detected, displaying the first prompt on the interface after the video call ends, the first prompt not including the re-detection control and the screen recording control.

[0021] In this way, whenever a face-swapping risk is detected, the first warning will be displayed, indicating the presence of face-swapping risk. Furthermore, since re-detection and screen recording cannot be performed after the video call ends, if the video call has ended when a face-swapping risk is detected, re-detection and screen recording controls will not be provided in the first warning to avoid providing invalid controls.

[0022] In one possible design approach of the first aspect, the detection result indicates no risk of face swapping. After obtaining the detection result, a third prompt is displayed, including: if the video call is still ongoing when the detection result is obtained, a third prompt is displayed on the video call interface, including a re-detection control and / or a screen recording control. If the video call has ended when the detection result is obtained, a third prompt is displayed on the interface after the video call ends, excluding the re-detection control and screen recording control. For details, please refer to the aforementioned explanation of the first prompt; it will not be repeated here.

[0023] In one possible design approach of the first aspect, a prompt including a re-detection control is displayed on the video call interface (such as the first or third prompt mentioned above). This includes displaying the prompt with the re-detection control on the video call interface if the number of times the video call is checked for face-swapping risk does not exceed the first count (count 1 in the following text). This avoids malicious detection targeting the same video call.

[0024] In one possible design approach of the first aspect, if the number of times the video call is checked for the risk of face swapping exceeds the first count, a prompt without a re-detection control is displayed on the video call interface.

[0025] In one possible design of the first aspect, after the video call interface displays a prompt including a re-detection control (also including the first or third prompt mentioned above), the method further includes: in response to the triggering operation of the re-detection control, detecting whether there is a risk of face swapping, and prompting the detection process; and after obtaining the detection result, displaying a fourth prompt, the detection result including whether there is a risk of face swapping or not.

[0026] In other words, the triggering operation of the re-detection control can also trigger passive detection, such as prompting the detection process and displaying a prompt indicating whether there is a risk of face swapping or not.

[0027] In one possible design approach of the first aspect, after the prompt including the screen recording control is displayed on the video call interface, the method further includes: in response to a triggering operation of the screen recording control, recording the screen of the video call interface until the video call ends, then ending the recording and saving the recorded video. This allows for the saving of screen recordings of video calls with potential face-swapping risks, which can be used as evidence when necessary, or for updating face-swapping detection models, etc.

[0028] In one possible design approach of the first aspect, the method further includes: displaying a message indicating that the detection was incomplete if the second condition is met and the face of the first user is not detected; or, displaying a message indicating that the detection was incomplete on the video call termination screen if the second condition is met and the video call ends before an image frame for detection is acquired. In other words, in the passive detection method, for abnormal situations such as failure to detect a face or failure to acquire an image frame that prevent detection from being completed, a message indicating that the detection was incomplete can be displayed, allowing the user to clearly understand the existence of an anomaly.

[0029] Conversely, if the first condition is met and no face is detected, or if the video call ends before an image frame is acquired, no notification of incomplete detection will be displayed. In other words, in the active detection method, no notification will be displayed for abnormal situations such as no face detection or no image frame acquisition that prevent detection from being completed, to avoid interfering with the user.

[0030] In one possible design approach of the first aspect, the detection process is indicated by displaying at least one of the following: a prompt to start detection (e.g., "Start Detection"), a prompt that is detecting (e.g., "Detection in progress"), and a detection animation.

[0031] In one possible design approach of the first aspect, the second condition includes a first sub-condition and a second sub-condition. When the second condition is met, a second prompt indicating the risk of face-swapping is displayed, including: when the first sub-condition (as in prompt g below) is met, displaying the second prompt indicating the risk of face-swapping (as in prompt g below), where the first sub-condition includes having the face-swapping detection switch on the electronic device enabled; when the second sub-condition (as in prompt h below) is met, displaying a second prompt indicating that the face-swapping detection function is enabled and detected (as in prompt h below), where the second sub-condition includes having the face-swapping detection switch on the electronic device disabled.

[0032] Furthermore, the first sub-condition has lower requirements, while the second sub-condition has higher requirements. In other words, the first sub-condition is easier to meet, while the second sub-condition is more difficult. In practice, electronic devices have risk protection enabled by default, which corresponds to enabling the face-swapping detection function by default. If the face-swapping detection switch is off, meaning the face-swapping detection function is not enabled, it indicates that the user has likely manually disabled the face-swapping detection function. In this case, the second sub-condition can prompt the user to enable the face-swapping detection function at a lower frequency, avoiding frequent prompts for unnecessary functions and causing user annoyance. However, when the face-swapping detection function is enabled, the first sub-condition can prompt the user to use the face-swapping detection function to detect face-swapping risks at a slightly higher frequency, thereby increasing the usage rate of the face-swapping detection function.

[0033] In one possible design approach of the first aspect, after displaying a second prompt to enable the face-swapping detection function and perform the detection, in response to a confirmation detection operation on the second prompt, detecting whether there is a face-swapping risk includes: in response to a confirmation detection operation on the second prompt, enabling the face-swapping detection function and detecting whether there is a face-swapping risk.

[0034] If a user performs a confirmation check on the second prompt, it indicates that the user wants to use the face-swapping detection function to detect the risk of face-swapping. Accordingly, the face-swapping detection function can be enabled and used to detect the risk of face-swapping to meet the user's needs.

[0035] In one possible design approach of the first aspect, displaying a second prompt regarding the risk of face-swapping includes: When the second prompt is displayed for the first to Nth times, it is displayed in card form, including a description of the face-swapping detection function and / or a confirmation control (such as the detection control, activation and detection control, etc., described below). When the second prompt is displayed for the (N+1)th time, it is displayed in capsule form, excluding the description of the face-swapping detection function and the confirmation control. Here, N is a natural number greater than 1, such as N = 3.

[0036] This allows the user to be shown the details of the prompt during the first few displays of the second prompt, so that the user understands the content of the prompt. When the second prompt is displayed again, a capsule is shown to the user, reducing the impact on the call.

[0037] In one possible design approach of the first aspect, in response to the detection of a face-swapping risk, such as displaying a prompt indicating a face-swapping risk (the aforementioned first prompt or the third prompt displayed after detecting a face-swapping risk), the following response strategy can be used to make users aware of the face-swapping risk.

[0038] Strategy 1 (corresponding to Response Strategy 1 below): After displaying a warning about the risk of face swapping on the video call interface, continue displaying the warning until the video call ends. This way, the risk of face swapping is consistently displayed throughout the video call.

[0039] Unlike Strategy 1 above, in cases where no face-swapping risk is detected, such as after displaying a third prompt indicating no face-swapping risk, the third prompt can be canceled after its designated display time has elapsed for the specified duration. In other words, the prompt will not continuously indicate no face-swapping risk but will automatically cancel its display, thus avoiding interference with the user.

[0040] Strategy 2 (corresponding to Response Strategy 3 below), after displaying a warning about the risk of face swapping on the video call interface, also includes: displaying a detection record entry (as mentioned in Notification 2 below) after the video call ends. In response to the triggering of the detection record entry, the detection record for face swapping risk detection is displayed. This provides a quick access point to the face swapping detection record interface after a face swapping risk is detected and the video call ends, allowing users to view the risk record.

[0041] Strategy 3 (corresponding to Response Strategy 2 below) further includes the following method after displaying a face-swapping risk warning on the video call interface: In response to a swipe-down gesture in the video call interface to access the pull-down notification center, display the pull-down notification center, which includes a first notification (notification 1 below), the content of which is consistent with the third warning. This allows the face-swapping risk warning to continue even after entering the pull-down notification center.

[0042] Strategy 4 (corresponding to Response Strategy 4 below) detects risky behavior within four time intervals after detecting the risk of face swapping (time interval 9 below), and displays a fifth warning indicating the risk of face swapping. Risky behaviors include entering a money transfer interface and receiving a website link from a friend in a video call with a potential face-swapping risk. This strengthens the warning after a risky behavior occurs.

[0043] In one possible design approach of the first aspect, the aforementioned second sub-condition also includes enabling the risk protection switch of the electronic device, with the face-swapping detection function being a sub-function of the risk protection. That is, the prompt to enable face-swapping detection will only appear when the risk protection switch is enabled but the face-swapping detection switch is disabled.

[0044] In one possible design approach of the first aspect, before adding the first user as a friend, the method further includes: if the third condition (as stated in prompt a below) is met, displaying a sixth prompt to enable the risk protection function (as stated in prompt a below). The third condition includes both the risk protection switch and the face-swapping detection switch being turned off; that is, the risk protection function is off, and correspondingly, the face-swapping detection function is also off. In other words, if neither of the risk protection functions is enabled, there will be no prompt to enable face-swapping detection and perform the detection; instead, a prompt to enable the risk protection function will be displayed.

[0045] Furthermore, in response to the sixth prompt, the risk protection settings interface is displayed, which includes a risk protection switch that is currently off. In response to turning the risk protection switch on, the risk protection function and the face-swapping detection function are enabled. In other words, even when risk protection is not enabled, a sixth prompt can provide a quick access to the risk protection settings interface, allowing for quick activation of the risk protection function and its face-swapping detection feature.

[0046] In one possible design approach of the first aspect, before adding the first user as a friend, the method further includes: if the fourth condition (the push condition indicated by prompt d below) is met, displaying a seventh prompt (prompt d below) to enable the face-swapping detection function. The fourth condition includes enabling the face-swapping detection switch, i.e., enabling the face-swapping detection function. Correspondingly, the risk protection function is also enabled.

[0047] Furthermore, in response to the seventh prompt, the face-swapping detection settings interface is displayed. This interface includes a face-swapping detection switch indicating its on / off state and a description of the face-swapping detection function. In other words, when face-swapping detection is enabled, a push notification (the seventh prompt) provides a quick access to the face-swapping detection settings interface, allowing users to quickly understand the function.

[0048] In one possible design approach of the first aspect, the face-swapping detection function is a sub-function of risk protection. Before adding the first user as a friend, the method further includes: enabling the face-swapping detection function in response to either enabling the risk protection switch in the settings application (i.e., the risk protection switch in the risk protection settings interface) or enabling the face-swapping detection switch.

[0049] In one possible design approach of the first aspect, enabling the face-swapping detection function in response to turning on the face-swapping detection switch in the settings application includes: if the risk protection switch is not enabled, displaying a prompt to enable risk protection in response to turning on the face-swapping detection switch. That is, if risk protection is not enabled, a prompt to enable risk protection will be displayed first before enabling face-swapping detection. In response to confirming the prompt to enable risk protection, both risk protection and face-swapping detection functions are enabled.

[0050] In one possible design approach of the first aspect, risk protection is provided by a system management service in the electronic device. In response to a confirmation operation prompting to enable risk protection, the risk protection and face-swapping detection functions are enabled, including: if the system management service is not enabled, in response to a confirmation operation prompting to enable risk protection, displaying a prompt to enable the system management service. That is, if the system management service is not enabled, enabling risk protection will first prompt to enable the system management service. In response to a confirmation operation prompting to enable the system management service, the system management service, risk protection, and face-swapping detection functions are enabled.

[0051] It's understandable that if the System Manager service is not enabled, in response to the activation of the risk protection switch in the settings app, a prompt to enable the System Manager service can be displayed first. Subsequently, in response to the confirmation prompt to enable the System Manager service, both the System Manager service and risk protection will be activated.

[0052] Secondly, this application also provides an electronic device including a display screen, a memory, and one or more processors. The display screen, memory, and processors are coupled. The memory stores computer program code, including computer instructions, which, when executed by the processor, cause the electronic device to perform the methods described in the first aspect and any of its possible designs.

[0053] Thirdly, this application provides a chip system applied to an electronic device including a display screen and a memory; the chip system includes one or more interface circuits and one or more processors; the interface circuits and processors are interconnected via lines; the interface circuits are used to receive signals from the memory of the electronic device and send signals to the processor, the signals including computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device performs the method as described in the first aspect and any of its possible design embodiments.

[0054] Fourthly, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform a method as described in the first aspect and any of its possible design embodiments.

[0055] Fifthly, this application provides a computer program product that, when run on a computer, causes the computer to perform a method as described in the first aspect and any of its possible design methods.

[0056] Understandably, the beneficial effects achieved by the electronic device of the second aspect, the chip system of the third aspect, the computer-readable storage medium of the fourth aspect, and the computer program product of the fifth aspect provided above can be referred to in light of the beneficial effects of the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0057] Figure 1A is a hardware structure diagram of a mobile phone provided in an embodiment of this application;

[0058] Figure 1B is one of the schematic diagrams of the interface for enabling face swap detection provided in the embodiments of this application;

[0059] Figure 2 is a second schematic diagram of the interface for enabling face-swapping detection provided in an embodiment of this application;

[0060] Figure 3 is a schematic diagram of the interface for enabling the system manager service provided in an embodiment of this application;

[0061] Figure 4 is a schematic diagram of the interface for understanding face-swapping detection details provided in an embodiment of this application;

[0062] Figure 5 is a schematic diagram of the interface for viewing face-swapping detection records provided in an embodiment of this application;

[0063] Figure 6 is a schematic diagram of the interface of the security settings provided in an embodiment of this application;

[0064] Figure 7 is a third schematic diagram of the interface for enabling face-swapping detection provided in an embodiment of this application;

[0065] Figure 8 is a schematic diagram of prompt a and its interface response provided in the embodiments of this application;

[0066] Figure 9 is a schematic diagram of the interface of the disappearance process of prompt a provided in the embodiment of this application;

[0067] Figure 10 is a schematic diagram of the prompt d and its interface response provided in the embodiment of this application;

[0068] Figure 11 is a schematic diagram of the active detection scheme provided in the embodiment of this application;

[0069] Figure 12 is a schematic diagram of the interface of the active detection scheme provided in the embodiment of this application;

[0070] Figure 13 is a schematic diagram of the interface for adding friends and starting a video call provided in an embodiment of this application;

[0071] Figure 14 is a schematic diagram of the interface prompting the use of face-swapping detection during a video call provided in an embodiment of this application;

[0072] Figure 15 is a schematic diagram of the interface prompting to enable face-swapping detection during a video call provided in an embodiment of this application;

[0073] Figure 16 is a schematic diagram of the passive detection scheme provided in the embodiment of this application;

[0074] Figure 17 is one of the interface diagrams of the passive detection scheme provided in the embodiments of this application;

[0075] Figure 18 is a second schematic diagram of the interface of the passive detection scheme provided in the embodiment of this application;

[0076] Figure 19 is a third schematic diagram of the interface of the passive detection scheme provided in the embodiments of this application;

[0077] Figure 20 is a fourth schematic diagram of the interface of the passive detection scheme provided in the embodiments of this application;

[0078] Figure 21 is the fifth schematic diagram of the interface of the passive detection scheme provided in the embodiment of this application;

[0079] Figure 22 is a sixth schematic diagram of the interface of the passive detection scheme provided in the embodiments of this application;

[0080] Figure 23 is one of the interface diagrams provided in the embodiments of this application for situations where there is a risk of face swapping;

[0081] Figure 24 is a second schematic diagram of the interface provided in this application embodiment for situations where there is a risk of face swapping;

[0082] Figure 25A is the third schematic diagram of the interface provided in the embodiment of this application for situations where there is a risk of face swapping;

[0083] Figure 25B is the fourth schematic diagram of the interface provided in the embodiment of this application for situations where there is a risk of face swapping;

[0084] Figure 26 is one of the schematic diagrams of the interface for disabling face-swapping detection provided in the embodiments of this application;

[0085] Figure 27 is a second schematic diagram of the interface for disabling face-swapping detection provided in an embodiment of this application;

[0086] Figure 28 is one of the interface diagrams of the detection model for face-swapping detection provided in the embodiments of this application;

[0087] Figure 29A is a second schematic diagram of the interface of the detection model for face-swapping detection provided in the embodiment of this application;

[0088] Figure 29B is a schematic diagram of the interface when there is insufficient storage space during the installation of face-swapping detection according to an embodiment of this application;

[0089] Figure 30 is a schematic diagram of the interface of the detection model for updating face swap detection provided in the embodiment of this application;

[0090] Figure 31 is a schematic diagram of the user interface for manually updating the detection model provided in an embodiment of this application;

[0091] Figure 32 is an entry diagram for the face-swapping detection function provided in the embodiments of this application. Detailed Implementation

[0092] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0093] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0094] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0095] The video call method provided in this application can be applied to video call scenarios. For example, an electronic device may have an application (APP) that supports video calls installed, such as WeChat. TM DingTalk TM Electronic devices can make video calls through these apps. The video call scenarios further include both actively initiating and joining a video call, and passively receiving and joining a video call.

[0096] In the aforementioned video call scenario, the video call method provided in this application embodiment can detect the risk of face swapping in the video call and provide a prompt.

[0097] It should be noted that this application does not limit the specific methods for detecting face-swapping risks. For example, an electronic device can detect the presence of face-swapping risks based on an AI model. As another example, an electronic device can detect the presence of face-swapping risks by comparing a face with a user's whitelist of faces. Yet another example, an electronic device can detect the presence of face-swapping risks by analyzing facial expressions and body movements.

[0098] For example, the aforementioned electronic devices can be mobile phones, tablets, desktops, laptops, handheld computers, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, as well as cellular phones, personal digital assistants (PDAs), augmented reality (AR) / virtual reality (VR) devices, and other electronic devices that can provide video calling functions, such as electronic devices with apps that support video calling installed. This application does not impose special limitations on the specific form of the electronic device. The following mainly uses a mobile phone as an example to illustrate the solution of this application.

[0099] Referring to Figure 1A, a mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0100] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the mobile phone. In other embodiments of this application, the mobile phone may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0101] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0102] In some embodiments, the mobile phone can complete the video call method through the processor 110, thereby detecting the risk of face swapping and providing a prompt during the video call.

[0103] The wireless communication function of a mobile phone can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0104] The mobile phone implements its display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0105] The display screen 194 is used to display images, videos, etc. In some embodiments, the mobile phone can display a video call interface, a warning message about the risk of face swapping, etc. on the display screen 194.

[0106] Mobile phones can achieve shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0107] Mobile phones can perform audio functions, such as music playback and recording, through components like the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0108] Button 190 may include a power button, volume buttons, etc. Button 190 may be a mechanical button or a touch button. The mobile phone can receive button input and generate key signal inputs related to the phone's user settings and function control. Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. Indicator 192 may be an indicator light, used to indicate charging status, battery level changes, or messages, missed calls, notifications, etc. SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the mobile phone.

[0109] The software system of a mobile phone can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application does not specifically limit this approach.

[0110] The video call method provided in this application can be implemented in a mobile phone with the above-described hardware and software structure. The video call method provided in this application will be further described in detail below with reference to the accompanying drawings.

[0111] In some embodiments, after detecting an event that enables face-swapping detection, the mobile phone can activate the face-swapping detection function. When face-swapping detection is enabled, the phone can detect the risk of face-swapping during video calls and provide a warning. Detecting an activation event indicates that the user has granted the necessary permissions and data for face-swapping detection. In this way, the phone can execute the appropriate permissions and obtain data with the user's permission.

[0112] The activation event can be an operation event such as confirming the activation of risk protection in the out-of-box experience (OOBE) (Method 1 below), an operation event of turning on the risk protection switch in the settings application (Method 2 below), an operation event of turning on the face-swapping detection switch in the settings application (Method 3 below), or an operation event of performing activation detection on prompt a prompt to activate risk protection (Method 4 below), etc. This application embodiment does not specifically limit this.

[0113] The following sections will provide a detailed explanation of the various activation events listed above and the process by which they trigger the face-swapping detection function.

[0114] Method 1: The activation event is the operation event in OOBE that confirms the activation of risk protection.

[0115] OOBE refers to the process of configuring a mobile phone during its first boot after leaving the factory, such as configuring the language, region, and network. OOBE can also be interpreted as a boot wizard or boot process.

[0116] In OOBE (Out-of-Body Environment), the phone typically has risk protection enabled by default. Risk protection offers various risk detection functions, such as risky call detection, risky information detection, and face-swapping detection. Enabling risk protection is equivalent to enabling multiple risk detection functions within the risk protection framework.

[0117] In OOBE, if the phone detects an operation event in which the user confirms the activation of risk protection, it indicates that the user supports enabling risk protection, and the phone can then enable risk protection, thereby activating the face-swapping detection function under risk protection.

[0118] Referring to Figure 1B, the risk protection configuration interface in OOBE is interface 101 shown in Figure 1B. The risk protection switch 1011 in interface 101 is on by default, meaning risk protection is enabled by default. The event that confirms enabling risk protection can be an event where the switch 1011 is not turned off, but a trigger operation is performed directly on the "Next" button 1012 in interface 101. In other words, even if the phone does not receive a user's operation to turn off switch 1011, the phone can confirm enabling risk protection in response to the user's trigger operation on the "Next" button 1012 in interface 101.

[0119] Of course, risk protection can also be disabled by default in OOBE, as shown by switch 1011 in interface 101 above, which can also be set to disabled by default. In this case, the operation event for enabling risk protection by default can be the operation event for turning on switch 1011. This article mainly uses enabling risk protection by default as an example.

[0120] Method 2: The activation event is the operation event of turning on the risk protection switch in the settings application.

[0121] The phone's settings app provides a risk protection setting 1. In one specific implementation, the phone further provides setting 1 within the security and / or privacy settings of the settings app.

[0122] Referring to Figure 2, the phone can display interface 201, which is the application interface for the settings app. The "Security" option 2011 in interface 201 is a security setting. In response to the user's triggering action on "Security" 2011, the phone can display interface 202. Interface 202 is the settings interface for the security settings. The "Risk Protection" option 2021 in interface 202 is setting 1 for risk protection. That is, setting 1 is provided within the security settings.

[0123] In the settings interface of the security settings shown in interface 202, "Risk Protection" 2021 is located in the area near the top of the interface and is larger than other settings such as "SOS Emergency Help" 2022 and "Emergency Warning Notification" 2023, so that setting 1 can be placed in a more conspicuous position.

[0124] The phone detects an operation event where the risk protection switch is turned on in setting 1. If a trigger operation is detected on the risk protection switch which is in a closed state, risk protection can be turned on, thereby enabling the face-swapping detection function under risk protection.

[0125] Referring to Figure 2, in response to the user's triggering of "Risk Protection" 2021, the phone can display interface 203, which is the risk protection settings interface. The "Risk Detection" switch 2031 in interface 203 is the risk protection switch. When the "Risk Detection" switch 2031 in interface 203 is in the off state, it indicates that risk protection is not enabled.

[0126] In response to the user's triggering of the "Risk Detection" switch 2031 in interface 203, the phone can enable risk protection. For example, after enabling risk protection, the phone can display interface 204, which is also the risk protection settings interface. Interface 204 also includes the "Risk Detection" switch 2031, and the "Risk Detection" switch 2031 in interface 204 is in the "on" state, indicating that risk protection has been enabled.

[0127] In one specific implementation, risk protection is provided by the system manager service in the mobile phone.

[0128] If the phone does not have the system manager service enabled, and detects an operation event of enabling the risk protection switch in setting item 1, the phone can first prompt the user to enable the system manager service (denoted as prompt b). In response to the user's operation of enabling the system manager service in prompt b, such as the triggering operation of the confirmation control in prompt b, the phone can enable the system manager service and further enable risk protection.

[0129] Referring again to Figure 2, when the System Manager service is not enabled, in response to the user's triggering of the "Risk Detection" switch 2031 in interface 203, the phone can display interface 205. Interface 205 adds a display prompt 2051 to the risk protection settings interface. Prompt 2051 is prompt a. For example, prompt 2051 includes the text "When enabling anti-fraud detection, the 'System Manager service' must be enabled simultaneously," prompting the user to enable the System Manager service. The "Agree" button 2052 in prompt 2051 is a control to confirm enabling the System Manager service. In response to the user's triggering of the "Agree" button 2052, the phone can enable the System Manager service and risk protection, as shown in interface 204.

[0130] In response to the user's action of canceling the system manager service in prompt b, such as the triggering of the confirmation cancellation control in prompt b (such as "Cancel" 2053 in interface 205), the phone can cancel the system manager service, and correspondingly, risk protection cannot be enabled.

[0131] If the phone has the system manager service enabled, and detects the operation event of turning on the risk protection switch in setting item 1, then risk protection can be enabled, as shown in the response process from interface 203 to interface 204 above.

[0132] Normally, the system manager service is enabled by default in OOBE. Alternatively, if the system manager service is not enabled, in response to starting the system manager service, the phone can display a prompt b to enable the system manager service. In response to the user's operation of prompt b, the phone can enable the system manager service.

[0133] Referring to Figure 3, when the System Manager service is not enabled, in response to the application launching the System Manager, the phone can display interface 301, with prompt 3011 (prompt b) in interface 301. Prompt 3011 indicates the various capabilities provided by the System Manager service, such as "the System Manager service provides notification management, battery management, privacy and security, application launch management, permission management, cleanup and acceleration, traffic management, harassment blocking, virus scanning, and risk protection functions." Furthermore, prompt 3011 includes an "Agree" control 3012 to enable the System Manager service. In response to the user's "Agree" 3012, the phone can enable the System Manager service.

[0134] In addition, the risk protection settings interface can also include settings for various risk detection functions, including the on / off status of the corresponding risk detection functions.

[0135] When risk protection is disabled, the default on / off state of various risk detection functions is off. For example, interface 203 includes: the setting "Risk Call Interception" 2032 for risk call detection, the setting "Risk Information Interception" 2033 for risk information detection, and the setting "AI Face Swap Reminder" 2034 for face swap detection, all of which are off.

[0136] With risk protection enabled, the on / off status of various risk detection functions is always "on" by default. For example, in interface 204, the on / off status of "Risk Call Interception" (2032), "Risk Information Interception" (2033), and "AI Face Swap Reminder" (2034) is all "on".

[0137] Furthermore, in response to a user's triggering of any risk detection function setting in the risk protection settings interface, the mobile phone can display the settings interface for that risk detection function.

[0138] For example, after risk protection is enabled, in response to the user's triggering operation on the "AI Face Swap Reminder" 2034 in interface 204 shown in Figure 2, the mobile phone can display interface 401 shown in Figure 4. Interface 401 is the settings interface for face swap detection. The "AI Face Swap Detection" 4011 in interface 401 is the face swap detection switch. Since risk protection is enabled at this time, the switch state of "AI Face Swap Detection" 4011 is on.

[0139] The face-swapping detection settings interface can also include a description of the face-swapping detection function, such as the text description in interface 401: "During video calls, the system can detect in real time whether the other party is an AI face-swapping device to prevent the risk of face-swapping," so that users can clearly understand the face-swapping detection function.

[0140] The face-swapping detection settings interface can also include a details entry, such as "Learn More" 4012 in interface 401. In response to the user's triggering of the details entry, the phone can display more detailed information about face-swapping detection, such as scenarios where face-swapping occurs and formulas to warn of face-swapping risks, allowing users to understand face-swapping detection in more detail. Referring again to Figure 4, in response to the user's triggering of "Learn More" 4012 in interface 401, the phone can display interface 402, which includes scenarios where face-swapping occurs 4021 and formulas to warn of face-swapping risks 4022, etc.

[0141] Additionally, the risk protection settings interface can also include protection records for various risk detection functions within a recent preset time period (such as 60 days or 1 month), including the number of risk occurrences. Referring to Figure 5, the phone can display interface 501 (the same as interface 204 mentioned earlier). Area 5011 of interface 501 records the protection records for face-swapping detection, such as a risk occurrence count of 0.

[0142] In response to a user's triggering operation on the protection record of any risk detection function, the mobile phone can display the detailed detection record of that risk detection function. Referring to Figure 5, in response to a user's triggering operation on area 5011 in interface 501, the mobile phone can display interface 502, which is the recording interface for face swapping detection, containing detailed detection records for face swapping. However, since the number of risk counts is 0 at this time, there are no detailed detection records in interface 502.

[0143] Therefore, it should be noted that the names and layouts of the settings items shown in Figures 2-5 are merely illustrative. In actual implementation, they are not limited to these examples. For instance, the settings interface for security settings can also be as shown in interface 601 of Figure 6, where "Risk Protection" 6011 is setting item 1 for risk protection. The layout of settings items in interface 601 differs significantly from that in interface 202 mentioned earlier; for example, the display position and size of "Risk Protection" 6011 in interface 601 are different from those of "Risk Protection" 2021 in interface 202.

[0144] Method 3: The activation event is the operation event of turning on the face-swapping detection switch in the settings application.

[0145] The phone offers a face-swapping detection setting (option 2). If the phone detects an operation that turns on the face-swapping detection switch in setting 2, such as a triggering operation on a switch that is currently off, the phone can enable face-swapping detection.

[0146] Referring to Figure 7, when risk protection is not enabled, the phone can display interface 701 (same as interface 203 mentioned above), where "AI Face Swap Reminder" 7011 is setting item 2. In response to the user's triggering of "AI Face Swap Reminder" 7011, the phone can display the face swap detection settings interface shown in interface 702, where the "AI Face Swap Detection" switch 7021 is the face swap detection switch. Since risk protection is not enabled at this time, the "AI Face Swap Detection" switch 7021 in interface 702 is in the off state. In response to the user's triggering of the "AI Face Swap Detection" switch 7021, the phone can enable face swap detection, such as displaying interface 703 (same as interface 401 mentioned above), where the "AI Face Swap Detection" switch 7021 is in the on state, indicating that face swap detection is enabled.

[0147] As explained above, the risk protection feature includes face-swapping detection. Therefore, if risk protection is not enabled on the phone, upon detecting an action triggered on setting 2, the phone can first prompt the user to enable risk protection (denoted as prompt c). In response to prompt c, the phone can then enable both risk protection and face-swapping detection.

[0148] Referring again to Figure 7, in response to the user's triggering operation on the "AI Face Swap Reminder" 7011 in interface 701, the phone can first display interface 704. The prompt 7041 in interface 704 is prompt c, which includes the text "When AI face swap detection is enabled, the 'Risk Detection' switch will be enabled simultaneously," prompting the user to enable risk protection. Prompt 7041 also includes an "Enable" control 7042 for enabling risk protection. Enabling risk protection can be a triggering operation on "Enable" 7042. In response to the user's triggering operation on "Enable" 7042, the phone can enable face swap detection, as shown in interface 703.

[0149] If risk protection is enabled on the phone, after detecting an operation event where the face-swapping detection switch is turned on in setting 2, the phone can enable face-swapping detection without displaying prompt c. It should be noted that face-swapping detection is enabled by default when risk protection is enabled; however, the phone can also independently disable face-swapping detection in response to a user's action of turning it off. Therefore, it is possible for risk protection to be enabled but face-swapping detection to be disabled. For details on how to independently disable face-swapping detection, please refer to the explanation of method 3 below; it will not be elaborated upon here.

[0150] Similar to Method 2 mentioned above, risk protection is provided by the system manager service in the phone. Based on this, if the phone does not have the system manager service enabled, and detects an operation event of enabling the face-swapping detection switch in Settings 2, the phone can first prompt the user to enable the system manager service (denoted as prompt d). In response to the user's operation of enabling the system manager service in prompt d, the phone can enable the system manager service and face-swapping detection.

[0151] Referring to Figure 7, when the System Manager service is not enabled, in response to the user's triggering operation on the "AI Face Swap Reminder" 7011 in interface 701, the phone can display interface 705, where prompt 7051 is prompt d. Prompt 7051 includes the text "When enabling face swap detection, the 'System Manager service' must be enabled simultaneously," prompting the user to enable the System Manager service. Prompt 7051 includes the "Agree" control 7052 for enabling the System Manager service; enabling the System Manager service can be a triggering operation on "Agree" 7052. In response to the user's triggering operation on "Agree" 7052, the phone can enable the System Manager service and face swap detection, as shown in interface 703.

[0152] If the phone's system manager service is enabled, and it detects the operation event of turning on the face-swapping detection switch in setting item 2, it can enable face-swapping detection without displaying prompt d, as shown in the response process from interface 702 to interface 703 above.

[0153] In practice, not enabling the system manager service also means that risk protection is not enabled. Therefore, when the system manager service is not enabled, the phone's response process can be interface 701, interface 705, interface 704, and interface 703, thus ensuring that face-swapping detection is enabled only when both the system manager service and risk protection are enabled. Conversely, even when the system manager service is enabled, risk protection may not be enabled. In this case, the phone's response process can also be interface 701, interface 704, and interface 703.

[0154] Method 4: The activation event is the operation event for performing the activation detection in response to the prompt to enable risk protection.

[0155] Without risk protection enabled, such as when switch 1011 in interface 101 is turned off in OOBE, the phone can push notification a to prompt the user to enable face-swapping detection. Referring to Figure 8, without risk protection enabled, the phone can display interface 801, where notification 8011 is notification a. Notification 8011 includes the text "Added 'AI Face-Swapping Detection' to detect AI face-swapping during video calls," indicating the addition of the face-swapping detection function. Notification 8011 also includes "Enable Risk Detection" 8012, prompting the user to enable risk protection; that is, notification 8011 can prompt the user to enable risk protection.

[0156] In response to the user's action of enabling risk detection on prompt 'a', the mobile phone can display the risk protection settings interface. In one specific implementation, prompt 'a' includes a control for enabling risk protection, such as "Enable Risk Detection" 8012 in interface 801, and the action of enabling detection can be a trigger operation on the control for enabling risk protection.

[0157] Referring again to Figure 8, the control for enabling risk protection is “Enable Risk Detection” 8012 in interface 801. In response to the user’s trigger operation on “Enable Risk Detection” 8012, the mobile phone can display interface 802 (the same as interface 203 mentioned above). Interface 802 is the risk protection settings interface.

[0158] After entering the risk protection settings interface, the phone can respond to the operation event of turning on the risk protection switch, thereby enabling risk protection and face-swapping detection. For details, please refer to the explanation in Method 2 above, which will not be repeated here.

[0159] Of course, if risk protection is enabled but face-swapping detection is disabled, in response to the user's action of enabling detection in prompt 'a', the risk protection settings interface displayed on the phone will show the risk protection switch as 'on' instead of 'off' as shown in interface 801. However, the face-swapping settings will also be 'off'. In this case, the phone can enable face-swapping detection in response to the action of enabling the face-swapping switch, as explained in Method 3 above, and will not be repeated here.

[0160] After displaying prompt 'a', the phone can cancel displaying prompt 'a' in response to an operation event that enables detection, or in response to a user's triggering operation on an area outside of prompt 'a', or in response to the display duration of prompt 'a' reaching a duration of 1 (e.g., 10 seconds).

[0161] Referring again to Figure 8, in response to the user's triggering operation of "Enable Risk Detection" 8012, the interface 802 displayed on the mobile phone no longer includes prompt 8011.

[0162] Furthermore, prompt 'a' can be in the form of a card as shown in prompt 8011 above. After the display duration of prompt 'a' reaches duration 2, such as after 5 seconds, the phone can first shrink prompt 'a' into capsule 1 to avoid interfering with the user's use of the phone. After the display duration of capsule 1 reaches duration 3, the phone can cancel the display of capsule 1, thereby canceling the display of prompt 'a'.

[0163] Taking duration 2 as 5 seconds and duration 3 as 10 seconds as examples, after the display duration of prompt 8011 in interface 801 reaches 5 seconds, the phone can shrink prompt 8011 into capsule 9011 in interface 901 as shown in Figure 9, that is, capsule 9011 is capsule 1. After the display duration of capsule 9011 reaches 10 seconds, the phone can cancel the display of capsule 9011, as shown in interface 902.

[0164] After the prompt a is collapsed into capsule 1, in response to the user's triggering operation on capsule 1, the phone can restore the display of prompt a. For example, in response to the user's triggering operation on capsule 9011 in interface 901, the phone can restore the display of interface 801 as shown in Figure 8.

[0165] Therefore, it should be noted that the above description of method four mainly uses the example of displaying prompt 'a' on the phone's home screen. In practice, the phone can also display prompt 'a' on other screens. For example, when the phone detects that the push conditions for prompt 'a' are met, it will display prompt 'a' on the phone's current screen.

[0166] This application embodiment exemplarily illustrates the push conditions for prompt a:

[0167] The first condition for the push notification is that the system detects access to the aforementioned setting item 1 without enabling risk protection.

[0168] When the phone detects access to Settings 1, such as the aforementioned interface 202, it can push notification a. This allows notification a to be pushed even when risk protection is not enabled, but the Risk Protection Settings 1 is viewed.

[0169] The second condition for pushing the notification is that a risk event has been detected.

[0170] Risk events include receiving risky phone calls, receiving risky information, receiving overseas phone calls, downloading unknown applications and performing actions such as entering bank account numbers, transferring money, and sharing screens.

[0171] When the phone detects a risk event, it sends a push notification (a). This allows the user to be promptly prompted to enable face-swapping detection when the phone faces security risks.

[0172] The third condition for the push notification is that face-swapping detection is not enabled, and the interval between the last time the notification is displayed is 4 days, such as 7 days, 20 days, or 60 days.

[0173] If the phone does not detect any operation event to enable face-swapping detection after displaying prompt 'a', it will not enable face-swapping detection. Subsequently, if face-swapping detection is not enabled and a considerable amount of time has passed since the last display of prompt 'a', the phone can display prompt 'a' again to remind the user.

[0174] In practice, the above-mentioned various push conditions can be combined.

[0175] For example, the phone can first display prompt 'a' after either push condition one or push condition two arrives, and then display prompt 'a' again after push condition three arrives.

[0176] For example, the phone can first display prompt a after either push condition one or push condition two arrives, and then display prompt a again when push condition three arrives and push condition one or push condition two is met.

[0177] Additionally, if risk protection is enabled in OOBE, the phone can push a notification with the option "d," which prompts the user to understand face-swapping detection. As explained earlier regarding Method 1, risk protection is enabled by default in OOBE. If risk protection is enabled in OOBE, the user is highly likely unaware of the risk protection and various risk detection functions. In this case, after OOBE completes, the phone can prompt the user with "d" to understand face-swapping detection.

[0178] Referring to Figure 10, with risk protection enabled in OOBE, the phone can then display interface 1001, with prompt 10011 being prompt d. Prompt 10011 includes the text "Added 'AI Face Swap Detection' to detect AI face swapping during video calls," indicating the addition of a face swap detection function. Furthermore, prompt 10011 also includes the text "Learn More" 10012, prompting the user to learn more about face swap detection. In other words, prompt 10011 can suggest learning about face swap detection.

[0179] In response to the user's action to "learn more" in prompt d, such as triggering the "learn more" control in prompt d, the phone can display the face-swapping detection settings interface for the user to understand face-swapping detection. Referring again to Figure 10, taking the "learn more" control as "learn more" 10012 in interface 1001 as an example, in response to the user's triggering action on "learn more" 10012, the phone can display interface 1002 (the same as interface 401 mentioned above), which is the face-swapping detection settings interface.

[0180] The phone can display an introduction to the face-swapping detection function in the settings interface. Furthermore, the face-swapping detection settings interface includes a details entry point to trigger the phone to display detailed information about face-swapping detection. This allows users to understand face-swapping detection. For details, please refer to the explanation in Method Two above; it will not be repeated here.

[0181] The disappearance, shrinking, and push conditions of prompt d can be referred to in the previous explanation of prompt a, which will not be repeated here.

[0182] After enabling face-swapping detection, the phone can perform face-swapping detection and provide a prompt during video calls.

[0183] Furthermore, the phone can perform face-swapping detection either actively or passively. Active detection means that detection can begin automatically without user intervention. Passive detection means that detection can begin passively based on user-triggered actions. These will be explained below:

[0184] Option 1: Active detection.

[0185] In response to the start of a video call, the phone can proactively begin face-swapping detection.

[0186] If a face-swapping risk is detected, the phone displays a warning (e) to indicate the risk, thus providing risk feedback. If no face-swapping risk is detected, no warning is displayed. This way, the phone only alerts when there is a risk of face-swapping, minimizing interference with video calls.

[0187] Referring to Figure 11, for the active detection method: In a risk-free scenario (i.e., no risk of face swapping), the user is completely unaware of the process before, during, and after detection. In a risky scenario (i.e., no risk of face swapping), the user is unaware of the process before and during detection; only after detection will the phone display a prompt "e" to provide risk feedback, at which point the user becomes aware of the process.

[0188] Upon detecting a risk of face-swapping, the phone can display a prompt 'e' on the video call interface. Referring to Figure 12, during a video call, the phone can display interface 1201. If a face-swapping risk is detected, the phone can display interface 1202, where prompt 'e' is displayed on interface 1202. Prompt 12021 includes the text "The other party is suspected of using AI face-swapping to impersonate someone," indicating the presence of a face-swapping risk.

[0189] Among them, prompt e can include information indicating that there is a security risk, such as the prompt text in prompt 12021, "The other party is suspected of using AI face-swapping to impersonate someone."

[0190] Furthermore, prompt e can also include information indicating the level of risk, such as the text "AI face-swapping probability 95%" in prompt 12021, used to indicate the level of risk.

[0191] Furthermore, prompt e can also include information instructing verification of the other party's identity, such as the text "Please be sure to verify the authenticity of their identity through other means" in prompt 12021, which is used to prompt for identity verification.

[0192] Furthermore, prompt e can also include an entry point for understanding face-swapping detection, such as the entry point "Learn more about the risks of AI face-swapping" 12022 in prompt 12021, which is used to trigger the display of the face-swapping detection settings interface. In response to the user's triggering operation of the entry point for understanding face-swapping detection, the phone can display the face-swapping detection settings interface, such as interface 401 mentioned above.

[0193] Furthermore, prompt 'e' can also include a re-detection control, such as "Re-detect" 12023 in prompt 12021, which triggers the phone to re-perform face-swapping detection. In response to the user's triggering of the re-detection control, the phone can re-perform face-swapping detection. It should be noted that when the phone triggers face-swapping detection due to the user's triggering of the re-detection control, this is a case of the phone passively performing face-swapping detection. This will be explained in detail in the section on passive face-swapping detection below, and will not be elaborated upon here.

[0194] Furthermore, prompt 'e' can also include screen recording controls, such as "Record and save video" 12024 in prompt 12021, which triggers the phone to record the screen of a video call. In response to the user's triggering of the screen recording controls, the phone can record the screen of the video call until the video call ends, at which point recording stops and the screen recording is saved to the phone.

[0195] In one possible implementation, the phone may have already ended the video call after detecting a risk of face-swapping. In this case, the phone could display a warning (e.g., "f") on the interface after the video call ends, indicating the risk of face-swapping.

[0196] Referring to Figure 12, during a video call, the phone can display interface 1201. After detecting a risk of face swapping and having exited the video call, the phone can display interface 1203. The prompt 12031 in interface 1203 is prompt f, which includes the text "The other party is suspected of using AI face swapping to impersonate someone," used to warn of the risk of face swapping.

[0197] Similar to prompt e, prompt f may also include information indicating the existence of a security risk, information indicating the degree of risk, etc.

[0198] The instructions provide information on verifying the other party's identity and accessing the face-swapping detection system. For details, please refer to the previous explanation regarding prompt e.

[0199] It should be noted that the "f" message is displayed only after the video call is exited. At this point, it is no longer possible to re-detect and record the video call screen. Consequently, the "f" message usually does not include controls for re-detection or screen recording.

[0200] Furthermore, prompt f may include a control to cancel the display, such as "OK" 12032 in prompt 12031, which is used to trigger the phone to cancel the display of prompt f. In response to the user's triggering operation of the control to cancel the display, the phone can cancel the display of control 6.

[0201] In one possible implementation, the phone can capture images from the video call for face-swapping detection. In some cases, the phone might not have captured the necessary images for detection before the video call ends. In this situation, the phone cannot obtain the detection result. However, considering that the phone is actively performing the detection, it will not indicate that the detection is incomplete, thus avoiding interference with the user.

[0202] In one possible implementation, the phone might not detect a face and therefore cannot obtain a detection result. Similarly, considering that the phone actively detects the face, it will not display a notification that no face was detected, thus avoiding interference with the user.

[0203] Furthermore, in response to the start of a video call, the phone can proactively begin detecting face-swapping risks if the detection conditions are met. This allows for targeted detection of face-swapping risks, rather than performing face-swapping detection for every video call, thereby reducing the phone's power consumption.

[0204] The following are some typical testing conditions:

[0205] Detection condition 1

[0206] The other party in the video call is a friend added within the last 5 hours. Specifically, for the same newly added friend, if a video call is made with that friend within 5 hours of adding them, the phone will perform face-swapping detection; if a video call is made with that friend after 5 hours of adding them, the phone will not perform face-swapping detection.

[0207] Referring to Figure 13, the phone can display interface 1301, which is the management interface for new friend request additions in the chat application. Interface 1301 includes Amy's friend request 13011. In response to the user's "accept" 13012 trigger action on the friend request 13011, the phone can add Amy as a friend. For example, after adding her and returning to the chat list interface, the phone can display interface 1302. Interface 1302 includes the conversation options 13021 for the newly added friend Amy.

[0208] Referring again to Figure 13, within 5 minutes of adding Amy as a friend, the phone receives a video invitation from Amy and displays interface 1303. Interface 1303 includes a call answering control 13031. In response to the user's triggering operation of the call answering control 13031, the phone can start a video call, as shown in interface 1201 in Figure 12. At this time, the phone can begin face-swapping detection.

[0209] Conversely, if you do not call Amy within 5 hours of adding her as a friend, but receive a video invitation from her after 5 hours, screen 1303 will still be displayed, and the phone will not perform face-swapping detection after the video call starts.

[0210] Typically, face-swapping risks occur during video calls with recently added friends. Therefore, the phone can perform face-swapping detection on video calls with recently added friends, thus increasing the likelihood of detecting video calls with face-swapping risks.

[0211] Detection condition 2

[0212] The first video call is with the other party in this video call. Specifically, for the same friend, if it is the first video call with that friend, the phone will perform face-swapping detection; if it is not the first video call with that friend, the phone will not perform face-swapping detection.

[0213] Typically, the risk of face-swapping occurs during the first video call with a friend. If there is no risk of face-swapping during the first call, it is highly unlikely that subsequent video calls with that friend will also be free of face-swapping risk. Therefore, a mobile phone can detect the risk of face-swapping during the first video call with a friend, thus enabling the detection of face-swapping risks in subsequent video calls with that friend.

[0214] Detection condition 3

[0215] The other party in the video call is in list 1, which records the number of most recently added friends (1). If the other party in the video call is in list 1, the phone performs face-swapping detection; if the other party is not in list 1, the phone does not perform face-swapping detection.

[0216] In practice, for newly added friends, the phone can store relevant information, such as name and location, in a specific area for face-swapping detection. Meanwhile, some users, due to the nature of their profession, may add a large number of friends in a short period, such as dozens in a single day. Consequently, the storage space required to store this information on the phone is substantial.

[0217] To address this, the phone can store information for a maximum of one friend. After storing information for one friend, if a new friend is added, the phone can delete the information stored in that specific area using a first-in, first-out (FIFO) approach before storing the new friend's information. Accordingly, "list 1" refers to the list of friends whose information is stored in that specific area. The phone can perform face-swapping detection on the stored friends. In this way, the phone consistently performs face-swapping detection on the most recently added friend (number of friends) while avoiding excessive storage space consumption.

[0218] Detection condition 4

[0219] The detection criteria for deepfake risk include the other party initiating the video call. Typically, individuals with ulterior motives will initiate video calls to gain the trust of the phone owner and then guide them to perform actions that could lead to financial loss or information leakage. Therefore, by performing deepfake detection on video calls initiated by the other party, the phone can more likely detect video calls with deepfake risk.

[0220] In one possible implementation, at least two of the above detection conditions can be combined. For example, detection conditions 1-4 can be combined to allow the phone to perform face-swapping detection during video calls initiated by newly added friends in list 1 within a duration of 5. As another example, detection conditions 2-4 can be combined to allow the phone to perform face-swapping detection during video calls initiated by newly added friends in list 1.

[0221] Of course, in actual implementation, the detection conditions for proactive detection are not limited to those listed above. For example, detection conditions may also include the presence of risk events on the mobile phone. For details, please refer to the explanation of push condition two above.

[0222] Option 2: Passive detection.

[0223] During a video call, the phone can passively initiate face-swapping detection based on the user's actions within the video call interface. This allows the phone to assess the potential for face-swapping based on the user's specific needs.

[0224] The possible scenarios for the detection operation include at least one of the following:

[0225] In scenario one, the detection operation is a user-triggered operation on the re-detection control in the aforementioned prompt e.

[0226] Taking prompt e as prompt 12021 in interface 1202 shown in Figure 12 above, and the re-detection control as "re-detection" 12023 in prompt 12021 as an example, the detection operation can be the user's trigger operation on "re-detection" 12023.

[0227] Scenario 2: With face-swapping detection enabled, the phone can display a "g" prompt on the video call screen to indicate the use of the face-swapping detection function. Correspondingly, the detection action can be the user's response to the "g" prompt.

[0228] In one specific implementation, the prompt g includes a detection control, and the detection operation can be a user-triggered operation on the detection control.

[0229] Referring to Figure 14, the phone can display interface 1401. In interface 1401, the switch for the "AI Face Swap Reminder" setting 14011 is set to "On," indicating that face swap detection is enabled. In this case, during a video call, the phone can display interface 1402, which is the video call interface. The prompt 14021 in interface 1402 is prompt g. Prompt 14021 includes the text "AI Face Swap Detection can detect whether the other party's face in the video is impersonating someone else" and "Detect Now" 14022, thus prompting the user to use face swap detection. "Detect Now" 14022 is a detection control; the detection operation can be triggered by the user's interaction with "Detect Now" 14022.

[0230] Furthermore, in addition to enabling face-swapping detection, the push conditions for notification g may also include one or more of the aforementioned push condition two, detection condition 1, detection condition 2, detection condition 3, and detection condition 4. This application does not impose specific limitations on this.

[0231] The phone can present different notifications in different formats on different occasions.

[0232] Specifically, when the above prompt g is displayed from the 1st to the Nth time (N>1, where N is an integer), the mobile phone can first present it in the form of a card, as shown in prompt 14021 in interface 1402 above. When the above prompt g is displayed for the N+1th time and thereafter, the mobile phone can first present it in the form of a capsule, as shown in capsule 14031 in interface 1403 above.

[0233] In this way, the phone can present the details of the prompt to the user during the first few times the prompt "g" is displayed, so that the user can clearly understand the content of the prompt. When the prompt "g" is displayed again, a capsule is presented to the user to reduce the impact on the call.

[0234] Furthermore, the card format and capsule format can be switched between each other.

[0235] Specifically, after the display duration of the card-shaped prompt g reaches a duration of 7 seconds, such as 5 seconds, the mobile phone can shrink the prompt g into a capsule form. Continuing to refer to Figure 14, after the display interface 1402 reaches 5 seconds, the mobile phone can shrink the prompt 14021 in interface 1402 into a capsule 14031 in interface 1403, that is, capsule 14031 is the shrunken prompt g.

[0236] In response to the user's click on the capsule-shaped prompt g, the mobile phone can expand the prompt g into a card format. Continuing to refer to Figure 14, after displaying interface 1403, in response to the user's click on capsule 14031, the mobile phone can expand capsule 14031 into prompt 14021 in interface 1402.

[0237] Scenario 3: When face-swapping detection is not enabled, the phone can display a prompt "h" on the video call interface to remind the user to enable and use the face-swapping detection function. Correspondingly, the detection action can be triggered by the user's response to the prompt "h".

[0238] In one specific implementation, the prompt 'h' includes an enable detection control, and the detection operation can be a user-triggered operation to enable the detection control.

[0239] Referring to Figure 15, the phone can display interface 1501. In interface 1501, the switch status of the "AI Face Swap Reminder" setting 15011 for face swap detection is "Not Enabled," indicating that face swap detection is not enabled. In this case, during a video call, the phone can display interface 1502, which is the video call interface. The prompt 15021 in interface 1502 is prompt h. Prompt 15021 includes the text "Enabling 'AI Face Swap Detection' can detect whether the other party's face in the video is impersonating someone else" and "Enable and Detect" 15022, thus prompting the user to enable and use face swap detection. The "Enable and Detect" 15022 is an enable / detection control, meaning the detection operation can be triggered by the user's action on "Enable and Detect" 15022.

[0240] Therefore, it's important to note that after enabling risk protection on the phone, multiple risk detection functions under risk protection will be enabled by default. Afterward, the user can individually disable one or more of these risk detection functions, such as disabling face-swapping detection. In this case, the situation shown in interface 1501 above will occur, meaning risk protection is enabled, but face-swapping detection is not. See the explanation of method 3 below for details; it will not be elaborated upon here. In this way, the phone can push a notification (h) even when the user disables face-swapping detection, specifically prompting the user to enable and use face-swapping detection.

[0241] It should be noted that if face-swapping detection is not enabled due to the lack of risk protection, i.e., both risk protection and face-swapping detection are not enabled, the phone will usually push the aforementioned prompt a, but will not push prompt h. For details, please refer to the relevant explanation of method four above, which will not be repeated here.

[0242] In addition, similar to the aforementioned notification g, the phone can present notification h in different formats (such as card format and capsule format) at different times. Furthermore, the card format and capsule format can be switched between each other. For details, please refer to the previous explanation of notification g, which will not be repeated here.

[0243] Furthermore, in addition to not enabling face-swapping detection, the conditions for pushing the notification h may also include one or more of the aforementioned push condition two, detection condition 1, detection condition 2, detection condition 3, and detection condition 4. This application does not impose specific limitations on this.

[0244] Generally, the conditions for pushing notifications for "h" are stricter than those for "g". This allows the phone to push notifications for "h" less frequently when face-swapping detection is disabled, reducing the impact on users; and to push notifications for "g" more frequently when face-swapping detection is enabled, increasing the usage rate of face-swapping detection.

[0245] Furthermore, the detection conditions that trigger the aforementioned proactive detection are usually more lenient than the push conditions for prompts h and g. This allows for more frequent triggering of proactive detection with lower perceptibility (visible only when a face-swapping risk is detected), while less frequent triggering of passive detection with higher perceptibility (visual display throughout) avoids excessive disruption to calls.

[0246] For example, a typical set of detection conditions for triggering active detection, push conditions for prompt g, and push conditions for prompt h are shown below:

[0247] The detection conditions that trigger active detection include the other party in the video call being a friend added within the last 5 minutes (i.e., detection condition 1), the first time having a video call with the other party in the video call (i.e., detection condition 2), and the other party in the video call being in list 1 (detection condition 3).

[0248] The push notification condition for g, in addition to the detection conditions that trigger active detection mentioned above, further includes the existence of security risks (i.e., push condition two).

[0249] The conditions for triggering the h notification include the existence of security risks (i.e., push condition two), the other party in the video call being the first friend added, the other party in the video call being a friend added within the last 6 hours, and the other party initiating the video call (i.e., detection condition four).

[0250] For example, a typical set of detection conditions for triggering active detection, push conditions for prompt g, and push conditions for prompt h are as follows:

[0251] The detection conditions that trigger active detection include the other party in the video call being a friend added within the last 5 minutes (i.e., detection condition 1) and the first time having a video call with the other party in the video call (i.e., detection condition 2).

[0252] The push notification condition for g, in addition to the detection conditions that trigger active detection mentioned above, further includes the existence of security risks (i.e., push condition two).

[0253] The conditions for triggering the h notification include the existence of security risks (i.e., push condition 2), the other party in the video call being a friend added within the last 5 minutes (i.e. detection condition 1), the first time engaging in a video call with the other party (i.e. detection condition 2), and the other party initiating the video call (i.e. detection condition 4).

[0254] In passive detection solutions, the mobile phone can provide a fully visual display in response to the detection operation, allowing users to clearly understand the detection process.

[0255] Referring to Figure 16, in the passive detection scheme: before detection, the phone can prompt the user to start the detection. During detection, the phone can display the detection process. After detection, the phone can provide feedback on the detection results. The visual presentation before and during detection allows the user to clearly perceive that the phone is detecting, giving them a sense of certainty. The visual presentation after detection allows the user to understand the risks of face-swapping, giving them a sense of control.

[0256] The response process before, during, and after detection is described below:

[0257] First, before detection. "Before detection" can be understood as the stage before the phone obtains the data used for face-swapping detection. For example, if the phone needs to obtain at least 10 frames of screenshots from a video call for face-swapping detection, then the period before obtaining these 10 frames falls under the "before detection" stage.

[0258] Before the test, the phone can display a prompt "i" to indicate when the test should begin.

[0259] Referring to Figure 17, in response to the detection operation, the mobile phone can display interface 1701, which is a video call interface. Capsule 17011 in interface 1701 is a prompt i, which includes the prompt text "Start Detection" to prompt the start of detection.

[0260] Second, during the detection process. This can be understood as the stage between when the phone obtains the data used for face-swapping detection and when the detection result is obtained.

[0261] During the test, the phone can display a prompt "j" and a test animation. The prompt "j" indicates that the test is in progress.

[0262] Referring again to Figure 17, after displaying interface 1701, the phone can then display interface 1702, which is also a video call interface. The capsule 17021 in interface 1702 is a prompt, containing the text "Detecting," indicating that detection is in progress. Additionally, interface 1702 also includes a detection animation showing a top-to-bottom scan (as indicated by the arrow in interface 1702).

[0263] It should be noted that the form of the detection animation can be diverse and is not limited to that shown in interface 1702. Furthermore, a single detection process can include multiple effects. For example, in addition to the top-to-bottom scanning detection animation in interface 1702, the animation shown in interface 1703, which scans the other party's face region (represented in a dot matrix form on face 17031 in the figure), can also be displayed.

[0264] Third, post-detection. Post-detection can be understood as the stage after the phone's detection results are obtained. These results include whether there is a risk of face-swapping or not.

[0265] After the test, the phone can display a notification "j", which indicates that the test is complete.

[0266] Referring again to Figure 17, after displaying interface 1702 and receiving the test results, the phone can then display interface 1704, which remains a video call interface. Capsule 17041 in interface 1704 is a prompt, containing the text "Detection Complete," indicating that the test is complete.

[0267] It should be noted that in the passive detection scheme, the phone can display a prompt regardless of whether a face-swapping risk is detected or not, allowing the user to obtain all detection results.

[0268] The above description of the visualization before, during, and after testing primarily uses capsule-shaped prompts as an example, such as prompts h, i, and j, all of which are capsules. However, this is not a limitation in actual implementation.

[0269] For example, prompts h-j can also be in card form. Referring to Figure 18, prompt h can also be prompt 18011 in interface 1801, and prompt i can also be prompt 18021 in interface 1802.

[0270] Among them, the card-style prompt j can be divided into two cases: there is a risk of face swapping and there is no risk of face swapping.

[0271] Referring again to Figure 18, in cases where there is a risk of face swapping, the prompt j can be prompt 18031 in interface 1803, used to indicate the risk of face swapping. The specific content of prompt j in cases of face swapping risk is basically the same as that of prompt e mentioned earlier. For details, please refer to the relevant explanation of prompt e mentioned earlier, which will not be repeated here.

[0272] In one possible implementation, to avoid malicious detection, if the number of times the phone repeatedly performs face-swapping detection for the video call is less than the maximum (e.g., 3 times, 5 times, etc.), the phone can provide a re-detection control in a card-style prompt j, such as "Re-detect" 18032 in prompt 18031 of interface 1803. If the number of times the phone repeatedly performs face-swapping detection for the video call reaches the maximum, the phone may not provide a re-detection control in the card-style prompt j, such as prompt 18041 in interface 1804 not including a re-detection control.

[0273] Referring again to Figure 18, in the absence of face-swapping risk, prompt j can also be prompt 18051 in interface 1805. Prompt 18051 includes the text "No AI face-swapping risk detected," indicating that there is no face-swapping risk. Furthermore, in the absence of security risk, the card-style prompt j can also include controls for re-detection, screen recording, etc., and this application does not impose specific limitations on this.

[0274] In one specific implementation, the phone can default to presenting prompts h-j in capsule format. Subsequently, in response to the user's click on the capsule-style prompt, the phone can switch to presenting it in card format.

[0275] In another specific implementation, the mobile phone can present prompts h and i in capsule form by default, and prompt j in card form by default, so as to facilitate viewing the specific detection results.

[0276] If the detection result indicates no risk of face swapping, the phone can automatically shrink the card-style prompt j into a capsule form after the display duration reaches 8 seconds (e.g., 5 seconds). For example, the card prompt 19011 in interface 1901 of Figure 19 shrinks into capsule 19021 in interface 1902. Subsequently, after the capsule-style prompt j is displayed for 9 seconds (e.g., 5 seconds), the phone can automatically cancel the display of prompt j, such as automatically canceling the display of capsule 19021 in interface 1902 and displaying interface 1903. In this way, when there is no risk of face swapping, the phone can automatically shrink and then cancel the display of prompt j, avoiding any impact on call quality.

[0277] Of course, when displaying a card-style prompt j, in response to the user's swipe up on prompt j or tap on an area outside prompt j, the phone can also passively shrink prompt j into a capsule shape.

[0278] In one possible implementation, the phone may have already ended the video call when the detection result is received. In this case, the phone can display a notification "k" on the interface after the video call ends, such as the chat list, to indicate that the detection is complete.

[0279] Similar to the prompt j mentioned earlier, prompt k can also be in capsule or card form. Furthermore, the content of the card-form prompt k differs depending on whether there is a risk of face swapping or not. It can also further indicate the detection result, such as whether there is a risk of face swapping or not.

[0280] Referring to Figure 20, the phone receives the test results only after the video call ends, at which point interface 2001 can be displayed. The prompt 20011 in interface 2001 is a capsule-shaped prompt k. Prompt 20011 includes the text "Detection Completed," indicating that the detection has been completed.

[0281] In cases where there is a risk of face swapping, refer to Figure 20. After the video call ends, if the phone detects a face swapping risk, interface 2002 will be displayed. The prompt 20021 in interface 2002 is a card-style prompt k, containing the text "The other party is suspected of using AI face swapping to impersonate someone," indicating that the detection has been completed and the result confirms a face swapping risk.

[0282] If there is no risk of face swapping, continue referring to Figure 20. After the video call ends, if the phone detects that there is no risk of face swapping, it can display interface 2003. The prompt 20031 in interface 2003 is a card-style prompt k, which includes the prompt text "No AI face swapping risk detected," indicating that the detection has been completed and the detection result is that there is no risk of face swapping.

[0283] Regarding the specific content of hint k, please refer to the previous explanation of hint j; it will not be repeated here.

[0284] It should be noted that the "k" prompt is only displayed after the video call ends. At this point, it is no longer possible to re-detect and record the video call screen. Consequently, the "k" prompt usually does not include controls for re-detection or screen recording.

[0285] In one possible implementation, the phone can capture images from the video call for face-swapping detection. In some cases, the video call might end before the phone captures the necessary images for detection. In this situation, the phone cannot obtain a detection result. Furthermore, considering a passive detection approach, feedback needs to be provided to the user; the phone could indicate that the detection is incomplete. Similarly, the phone could display this notification in capsule or card format.

[0286] Referring to Figure 21, after the video call ends, before the phone has acquired the image for face-swapping detection, the phone can display the chat list interface shown in interface 2101. Interface 2101 includes prompt 21011, which contains the text "Detection incomplete," indicating that the detection is not yet complete. Alternatively, the phone can display the chat list interface shown in interface 2102, which includes prompt 21021, which contains the text "Incomplete," indicating that the detection is not yet complete.

[0287] In one possible implementation, the phone might not even detect the other person's face, in which case no detection result can be obtained. Furthermore, considering a passive detection approach, feedback needs to be provided to the user; the phone could also indicate that the detection was incomplete. Similarly, the phone could display a capsule or card-like notification indicating incomplete detection, and the card-like notification could further specify that the incomplete detection was due to the failure to detect a face.

[0288] It should be noted that if no face is detected during a video call, a notification can be displayed on the video call interface. If no face is detected after the video call ends, a notification can be displayed on the interface after the video call ends, such as the chat list interface.

[0289] Taking a video call interface prompt as an example, as shown in Figure 22, during a video call, if the phone detects that the other party's face is not present, the phone can display the video call interface shown in interface 2201. Interface 2201 includes prompt 22011, which includes the text "Detection incomplete," indicating that the detection was not completed. Alternatively, the phone can display the chat list interface shown in interface 2002, which includes prompt 22021, which includes the text "Incomplete," indicating that the detection was incomplete because no face was detected.

[0290] Regarding Scheme 1 and Scheme 2 above, if a face-swapping risk is detected, the mobile phone can adopt at least one of the following response strategies to make users aware of the face-swapping risk.

[0291] Response strategy one: During video calls, the phone does not remove the warning about the risk of face swapping, such as warning e in the active detection and warning j in the passive detection, and the same applies below. In this way, the phone can continuously display the risk of face swapping throughout the video call.

[0292] In the proactive detection solution, the phone can continuously display the prompt "e" during a video call.

[0293] In the passive detection scheme, during a video call, the phone can switch between a capsule-shaped prompt j and a card-shaped prompt j in response to user actions. However, the phone will always keep prompt j displayed. For example, in response to the user's swipe up on prompt j or tapping an area outside of prompt j, the phone can passively shrink prompt j into a capsule shape, but will continue to display prompt j in capsule form. This is unlike the scenario shown in Figure 19 above, where there is no risk of face swapping, where the phone actively shrinks prompt j from card to capsule shape and eventually cancels its display.

[0294] Of course, in response to the user's action of canceling the display, the phone can passively cancel the display of the warning about the risk of face swapping. This cancellation action can be a swipe up action on the warning, or a trigger action on an area other than the warning.

[0295] The second response strategy involves triggering a face-swapping risk warning during a video call. In response, the phone will access the notification center and display Notification 1, indicating that a face-swapping risk has been detected. This way, even after accessing the notification center, the phone will continue to display the face-swapping risk warning.

[0296] Taking a passive detection scheme as an example, referring to Figure 23, after detecting a risk of face swapping, the phone can display interface 2301, where prompt 23011 is prompt j. In response to the user's swipe-down operation on interface 2301, such as the swipe in the direction indicated by the arrow in interface 2301, the phone can display interface 2302. Interface 2302 is a pull-down notification center, which includes various notifications received by the phone (not shown in the figure). Notification 23021 is notification 1, which includes the text "The other party is suspected of using AI face swapping to impersonate someone," thus notifying the user that a face swapping risk has been detected.

[0297] In addition, the content in notification 1 can be consistent with the content in prompt j. For example, notification 1 can also include controls for re-detection, screen recording, etc., so that users can easily trigger re-detection, screen recording, etc. in the pull-down notification center.

[0298] The third response strategy involves the phone displaying Notification 2 on the screen after a video call ends, such as in the chat list. Notification 2 can again indicate that a face-swapping risk has been detected and provide an entry point to the detection record to view the risk information. In response to the user's triggering of the detection record entry, the phone can display the face-swapping detection record interface. Thus, after detecting a face-swapping risk and ending the video call, the phone provides a quick access to the face-swapping detection record interface so that the user can view the risk information.

[0299] Taking the passive detection scheme as an example, as shown in Figure 24, after detecting a face-swapping risk, the phone can display interface 2401, with prompt 24011 being prompt j. After ending the video call, the phone can display interface 2402, which includes prompt 24021, notification 2. Prompt 24021 includes the text "The other party in the video call is suspected of being impersonated by someone using AI face-swapping. Please verify their identity through other means," thus re-notifying the phone of the face-swapping risk. Prompt 24021 also includes "Learn More" 24022, which is the entry point for the detection record. In response to the user's triggering of "Learn More" 24022, the phone can display interface 2403, which is the face-swapping detection record interface, including detection record 24031.

[0300] Additionally, if Notification 2 is displayed on the screen after a video call ends, the phone can display Notification 2 in the pull-down notification center in response to the notification being accessed. This way, even when the phone enters the pull-down notification center, it can still provide a warning about the risk of face-swapping and offer a quick access to the face-swapping detection log.

[0301] Referring again to Figure 24, in response to the user's swipe-down action on interface 2402, the phone can display interface 2404. Interface 2404 is the pull-down notification center, which includes notification 24041, which is notification 2. The "Learn More" option 24042 within notification 24041 is the entry point for the detection record. In response to the user's triggering action on "Learn More" 24042, the phone can also display interface 2403.

[0302] The fourth response strategy is to provide a second warning about the risk of face-swapping within a 9-hour window (e.g., 12 hours, 24 hours) after detecting a face-swapping risk and then detecting related risky behavior. This strengthens the warning after a risky behavior occurs.

[0303] Among the associated risky behaviors are accessing money transfer interfaces and receiving website links from friends in video calls that may involve deepfakes.

[0304] Taking the passive detection scheme as an example, as shown in Figure 25A, after detecting a risk of face swapping, the phone can display interface 2501, with prompt 25011 (prompt j) in interface 2501. If the phone then enters the transfer interface within the following 9 hours, interface 2502 will be displayed. Interface 2502 includes the prompt text "The system detected a risk of AI face swapping in your recent video call; continuing the payment may result in financial loss," thus reiterating the risk of face swapping.

[0305] In addition, after detecting a face-swapping risk or when the risk level reaches a preset threshold, such as a probability of 80%, the phone can send the risk information to a protection device. For example, the phone can provide a settings entry for a protection device (e.g., in the risk protection settings interface) and send the risk information to the designated protection device.

[0306] Referring to Figure 25B, the mobile phone can display interface 2511, which is the risk protection settings interface. Interface 2511 includes "Send a message to the guardian" 25111 and "Remote guardian reminder" 25112. "Send a message to the guardian" 25112 is a toggle option to send face-swapping risk information to the guardian device. "Remote guardian reminder" 25112 is the settings entry for the guardian device. After the "Send a message to the guardian" 25112 switch is turned on, if the mobile phone detects face-swapping risk or the risk level of face-swapping reaches a preset level value, it can send risk information to the guardian device set in "Remote guardian reminder" 25112.

[0307] Furthermore, after receiving risk information, the protection device can display a risk warning. Referring again to Figure 25B, after receiving risk information, the protection device can display interface 2512, which includes risk warning 25121, indicating that it has received risk information about face-swapping.

[0308] Similar to enabling the face-swapping detection function mentioned earlier, users can also disable it once they no longer need it. Specifically, the phone can disable the face-swapping detection function after detecting an event indicating that it has been disabled. When the face-swapping detection function is disabled, the phone will no longer detect the risk of face-swapping and provide any warnings during video calls.

[0309] The shutdown event can be an operation event that disables risk protection settings in OOBE, an operation event that disables the risk protection switch in the settings application, or an operation event that disables the face-swapping detection switch in the settings application, etc. This application embodiment does not specifically limit this.

[0310] The following sections will explain in detail the process of triggering the face-swapping detection function for the various events listed above.

[0311] Method 1: The shutdown event is the operation event for disabling risk protection settings in OOBE.

[0312] In OOBE, the phone usually has risk protection enabled by default. If the phone detects an operation event in OOBE where the user turns off the risk protection settings, such as turning off the switch 1011 that is enabled by default in interface 101 in Figure 1B above, it means that the user does not support enabling risk protection and the phone can turn off risk protection.

[0313] Method 2, the shutdown event is the operation event of turning off the risk protection switch in the settings application.

[0314] The phone detects a trigger operation on the risk protection switch that is currently enabled, and can then disable risk protection, thereby disabling the face-swapping detection function under risk protection.

[0315] Referring to Figure 26, with risk protection enabled, the phone displays interface 2601, which is the risk protection settings interface. The risk protection switch 26011 in interface 2601 is enabled. In response to the user's triggering of the risk protection switch 26011 in interface 2601, the phone displays interface 2602. In interface 2602, the risk protection switch 26011 is disabled, meaning risk protection is turned off. At this time, the "AI Face Swap Reminder" setting 26021 in interface 2602 is not enabled, indicating that the face swap detection function is also disabled.

[0316] Furthermore, disabling risk protection will disable various risk detection functions under risk protection. Based on this, in response to the user's triggering of the risk protection switch (which is currently enabled), the phone can first display prompt 'm', such as prompt 26031 in interface 2603, to indicate that disabling risk protection will render various risk detection functions unavailable. In response to the user's confirmation of prompt 'm', such as the triggering of "Still Off" 26032 in prompt 26031, the phone will then disable risk protection, thereby disabling face-swapping detection, as shown in interface 2602 after disabling.

[0317] The third option is "Fang". The "close" event is the operation event for turning off the face-swapping detection switch in the settings application.

[0318] The phone detects a trigger operation on the face-swapping detection switch, which is currently enabled, and can disable face-swapping detection.

[0319] Referring to Figure 27, when the face-swapping detection function is enabled, the phone displays interface 2701, which is the face-swapping detection settings interface. The face-swapping detection switch 27011 in interface 2701 is in the enabled state. In response to the user's triggering operation on switch 27011 in interface 2701, the phone displays interface 2702. In interface 2702, the face-swapping detection switch 27011 is in the disabled state, meaning face-swapping detection is turned off.

[0320] It should be noted that using method 3 only disables the face-swapping detection function; the risk protection function remains enabled. This can result in situations where risk protection is on but face-swapping detection is off. For example, in the risk protection settings interface, the risk protection switch may be on, but the face-swapping detection setting may be off.

[0321] Referring again to Figure 27, in response to the triggering operation of the return control 27021 in interface 2702, the phone can display interface 2703 (the same as interface 1501 mentioned above). Interface 2703 is the risk protection settings interface. In interface 2703, the risk protection switch 27031 is in the on state, indicating that risk protection has been enabled, and the switch state of the face-swapping detection setting item "AI face-swapping reminder" 27032 is off, indicating that face-swapping detection is not enabled.

[0322] The aforementioned face-swapping detection function requires a face-swapping detection model. In some embodiments, the mobile phone can push a notification to download and install the detection model, prompting the user to download and install the face-swapping detection installation package. Subsequently, in response to the user's confirmation of the download and installation prompt, such as triggering a control to confirm the download and installation, the mobile phone downloads and installs the detection model, and then enables face-swapping detection.

[0323] Additionally, in response to the user's cancellation prompt during the download and installation process, the phone will neither download and install the detection model nor enable face-swapping detection. The cancellation action can be triggered by the user clicking the cancellation control in the download and installation prompt.

[0324] This application embodiment exemplarily describes several times when push download and installation prompts are sent:

[0325] Timing 1: When an operation event of turning on the risk protection switch in the settings app is detected, such as the operation event of turning on the risk protection switch in methods 2 and 4 above, the mobile phone can push a download and installation prompt.

[0326] For example, in response to the user's triggering operation of the risk protection switch in the risk protection settings interface, which is in the off state, as shown in interface 203 above, the mobile phone can turn on risk protection and display interface 2801 as shown in Figure 28. The prompt 28011 in interface 2801 is a download and installation prompt.

[0327] In prompt 28011, "Install and enable" 28012 is a control to confirm the download and installation. In response to the user's triggering operation of "Install and enable" 28012, the mobile phone can download and install the face-swapping detection model, and face-swapping detection will only be successfully enabled after the installation is completed, as shown in the previous interface 204.

[0328] It should be noted that in scenario 1, in response to the cancellation of the download and installation prompt, the phone can enable risk protection, but not the face-swapping detection under risk protection.

[0329] Referring again to Figure 28, interface 2801 also includes "Later" 28013, which is a control to cancel the download and installation. In response to the user's triggering operation of "Later" 28013, the phone can enable risk protection, but disable face-swapping detection under risk protection, as shown in the previous interface 2703.

[0330] Using timing 1, the mobile phone can prompt the user to download and install the detection model when risk protection is enabled, so that face-swapping detection can be successfully enabled after the detection model is installed, ensuring the availability of the face-swapping detection function after risk protection is enabled.

[0331] Timing 2: When risk protection is not enabled, if the system detects a triggering operation for setting item 2 of face-swapping detection in the settings application, such as the triggering operation for setting item 2 in the risk protection settings interface mentioned in Method 3 above, the phone can push a download and installation prompt.

[0332] For example, when risk protection is not enabled, in response to the user's triggering operation of the face-swapping detection setting item 2 in the risk protection settings interface, as shown in the interface 701 above, the mobile phone can display the interface 2802 shown in Figure 28, and the prompt 28021 in the interface 2802 is a download and installation prompt.

[0333] In prompt 28021, "Install and enable" 28022 is a control to confirm the download and installation. In response to the user's triggering operation of "Install and enable" 28022, the mobile phone can download and install the face-swapping detection model, and enable face-swapping detection after installation, as shown in the previous interface 703.

[0334] As explained in Method 3 above, when risk protection is not enabled, in response to the user's triggering of setting item 2 (face-swapping detection) in the risk protection settings interface, the phone can display prompt c. Upon confirming prompt c, the phone can enable risk protection. Based on this, the phone can then push a download and installation prompt. In this implementation, in response to the user's cancellation of the download and installation prompt, the phone will not enable face-swapping detection, but risk protection has been successfully enabled.

[0335] Using timing 2, the phone can prompt the user to download and install the detection model when entering the face-swapping detection settings interface, allowing for quick download, installation, and activation.

[0336] Timing 3: When risk protection is enabled but face-swapping detection is not enabled, if the system detects that the user has been triggered to enter the risk protection settings interface, the phone can push a download and installation prompt, such as displaying the above interface 2801.

[0337] Using timing 3, when risk protection is enabled but face-swapping detection is not, the phone can predict that the user is entering the risk protection settings interface to enable face-swapping detection, and can promptly prompt the user to download and install the detection model.

[0338] Timing 4: During a video call, without face-swapping detection enabled, the phone can push a download / installation notification. Further push notification timing can be consistent with the push conditions in method 4(a) above.

[0339] For example, during a video call, the mobile phone can display interface 2901 as shown in Figure 29A, where prompt 29011 is a download and installation prompt.

[0340] In scenario 4, to avoid interfering with calls, the phone can hide the download and installation controls by default in the download and installation prompt, such as in prompt 29011 in interface 2901, which does not include the download and installation controls. In response to a user's operation to expand the download and installation prompt, such as a click, the phone can display the download and installation controls in the prompt for user operation. Referring again to Figure 29A, in response to a user's click on prompt 29011 in interface 2901, the phone can display interface 2902, where the "Install and Open" 29021 from prompt 29011 in interface 2902 represents the download and installation controls.

[0341] Furthermore, considering that users may find it inconvenient to interact with download and installation prompts during video calls, in actual implementation, if the phone does not detect any user interaction with the download and installation prompts, the phone can continue to display the download and installation prompts during the video call and show the corresponding download and installation notification in the pull-down notification center. This allows users to trigger the download and installation detection model and enable face-swapping detection after ending the video call by pulling down the notification center.

[0342] Referring to Figure 29A, the phone can display interface 2903, which is a pull-down notification center. Interface 2903 includes download and installation notification 29031, which is used to notify the download and installation detection model.

[0343] Similarly, in response to a user's action of expanding the download and installation notification, such as clicking it, the phone can display the download and installation controls within the notification. Referring again to Figure 29A, in response to a user's click on the download and installation notification 29031 in interface 2903, the phone can display interface 2904, where the "Install and Open" 29041 in the download and installation notification 29031 represents the download and installation controls.

[0344] Using timing 4, the phone can push a download and installation prompt during a video call, making it easy to download, install, and apply the software to the current video call immediately.

[0345] Additionally, during the download and installation process, the phone can also display a notification that the download and installation is in progress. Taking the above-mentioned timing 1 as an example, continuing to refer to Figure 28, in response to the user's trigger operation of "Install and Start" 28012 on interface 2801, the phone can display interface 2803, which includes the prompt text "Downloading and installing in the background, you can check the progress in the notification bar," to indicate that the download and installation is in progress.

[0346] It should be noted that face-swapping detection is not yet successfully enabled during the download and installation process. For example, the switch for the "AI Face-Swapping Reminder" setting 28031 in interface 2803 is not enabled. At this time, the user cannot enable face-swapping detection through any operation, such as triggering the face-swapping detection switch. Therefore, in one specific implementation, the phone can only prompt that it is downloading and installing when it detects an intention to enable face-swapping detection, such as when it detects a user triggering a face-swapping detection setting or a user triggering a face-swapping detection switch that is currently disabled. This allows the user to clearly understand that a detection model is being downloaded and installed.

[0347] Taking the detection of a user's trigger operation on the face-swapping detection settings as an example, referring to Figure 28, in response to the user's trigger operation on "Install and Enable" 28012 in interface 2801, the phone can first display interface 2804. In interface 2804, the switch status corresponding to the face-swapping detection settings "AI Face-Swapping Reminder" 28031 is not enabled. At this time, in response to the user's trigger operation on "AI Face-Swapping Reminder" 28031 in interface 2804, the phone recognizes the intention to enable face-swapping detection and can display the above interface 2803, thereby prompting that it is downloading and installing.

[0348] Furthermore, the remaining storage space on the phone may be less than the target storage space required by the detection model. Therefore, in some embodiments, after displaying the download and installation prompt, in response to the user's confirmation of the download and installation prompt, the phone can detect whether the remaining storage space is greater than the target storage space required by the detection model. If the remaining storage space is greater than the target storage space, the phone can download the detection model and enable face-swapping detection. If the remaining storage space is less than the target storage space, the phone can display a prompt to clear storage space, thereby prompting the user to clear storage space.

[0349] For example, in response to a user's triggering operation of "Install and Open" 28022 on interface 2802, if the remaining storage space is detected to be greater than the target storage space, the phone can display interface 2803, i.e., download the detection model. Conversely, interface 2911 shown in Figure 29B, with prompt 29111 indicating the need to clear storage space. Prompt 29111 includes the text "Insufficient system storage space, unable to download and install...", thus prompting the user to clear storage space.

[0350] Furthermore, the prompt to clean up storage space can also indicate the size of the storage space to be cleaned up, such as "XX GB" in the prompt 29111 above.

[0351] Furthermore, the prompt to clean up storage space can also include a confirmation control, such as "Go to Cleanup" 29112 in the above prompt 29111. In response to the user's triggering of the confirmation control, the phone can clean up storage space, such as by accessing the system manager service to clean up storage space.

[0352] After clearing storage space, in response to the user's confirmation prompt to download and install again, the system will check again whether the remaining storage space is greater than the target storage space. Once the remaining storage space is found to be greater than the target storage space, the detection model can be downloaded and face-swapping detection can be started.

[0353] Understandably, the detection model for face-swapping detection may be updated. To ensure timely updates, the phone can push an update notification after the model is updated, prompting the user to update the face-swapping detection installation package. Subsequently, in response to the user's confirmation of the update notification, such as triggering a confirmation control, the phone updates the detection model.

[0354] The process of pushing update prompts and implementing the update response is similar to the process of pushing download and installation prompts and downloading and installing the detection model described above. The main difference is that the download and installation prompts are replaced with update prompts, and the control to confirm download and installation is replaced with the control to confirm update. This will not be elaborated further here.

[0355] For example, the update prompt could be prompt 30011 in interface 3001 shown in Figure 30. Prompt 30011 includes the prompt text "AI face-swapping detection model updates the following content, we recommend that you upgrade and experience it immediately...", used to prompt for updating the detection model. The "Update Now" button 30012 in prompt 30011 is a control to confirm the update.

[0356] The following is a brief explanation of the differences:

[0357] Updates are typically performed on phones that have enabled face-swapping detection, so update notifications should be sent after the phone has enabled face-swapping detection.

[0358] Accordingly, the timing of the aforementioned push notification for downloading and installing does not apply to push notifications for updates.

[0359] The timing 2 for the aforementioned push notification to download and install corresponds to timing 2A for the push notification to update: when the face-swapping detection function is enabled, and the phone detects the triggering of setting item 2 for face-swapping detection in the settings application, the phone can push an update notification.

[0360] The timing 3 for the aforementioned push notification to download and install corresponds to timing 3A for the push notification to update: when the face-swapping detection function is enabled, and the phone detects that the user has entered the risk protection settings interface, the phone can push an update notification.

[0361] The timing 3 for the push notification to download and install corresponds to timing 4A for the push notification to update: when face-swapping detection is enabled, the phone can push an update notification during a video call.

[0362] In addition, if face-swapping detection is enabled and the second push condition mentioned above is met, the phone can push an update notification on the current screen. For example, if the current screen is the home screen, the phone can display screen 3001 as shown in Figure 30, that is, display the update notification on the home screen.

[0363] Alternatively, users can manually update the detection model. In one specific implementation, the phone can provide a model update entry point within the voice assistant application. In response to the user's triggering of the model update entry point, the phone can detect whether an updated version is available and, if so, update the detection model.

[0364] Referring to Figure 31, the mobile phone can display the voice assistant application interface 3101. In response to the user's click on the control 31011 in interface 3101, the mobile phone can display interface 3102. Interface 3102 adds extended function entry points to interface 3101, with "Local Model Update" 31021 being the model update entry point. In response to the user's click on "Local Model Update" 31021, the mobile phone can display interface 3103. Interface 3103 provides multiple model options, such as "Large Language Model" 31031, "Image Understanding Large Model" 31032, and "Speech Large Model" 31033. The face-swapping detection model belongs to the Image Understanding Large Model category. In response to the user's selection of "Image Understanding Large Model" 31032, the mobile phone can display interface 3104. Interface 3104 includes a check update option, "Check Update" 31041, and an update log option, "Update Log" 31042. In response to the user's selection of "Check for Updates" 31041, the phone can detect if there is an updated detection model. During the detection process, the phone can display a "Checking" indicator in "Check for Updates" 31041 (not shown in the figure). After detecting an updated version, the phone can display interface 3105, which includes information about the new version, such as model name, model size, details, etc. Interface 3105 also includes a control to confirm the update, such as "Update Now" 31051. In response to the user's click on "Update Now" 31051, the phone can update the detection model. If interface 3106 is displayed during the update process, it will show "Updating...".

[0365] In addition, after configuring face-swapping detection in the phone, the phone can display the face-swapping detection function on multiple interfaces. Several possible display formats are listed below.

[0366] The mobile phone can introduce the face-swapping detection function in the "Mobile Phone Tips" app. For example, in the application interface of the "Mobile Phone Tips" app shown in Figure 32(a), a privacy and security option "Privacy and Security" 3201 can be provided. In response to the user's triggering operation of "Privacy and Security" 3201, the mobile phone can display the privacy and security tips page shown in Figure 32(b), which includes information such as the function introduction, settings and usage methods of the face-swapping detection function.

[0367] The mobile phone can present the detection records of face-swapping detection in a privacy report, thereby introducing the face-swapping detection function. For example, the mobile phone can display the privacy report page shown in Figure 32(c), which includes the detection record 3202 of face-swapping detection.

[0368] The phone can introduce the face-swapping detection function in the system manager service. For example, the phone can display the system manager service interface shown in Figure 32(d), which includes an introduction to the face-swapping detection function 3203.

[0369] This application also provides an electronic device, which may include a display screen, a memory, and one or more processors (such as a CPU, GPU, NPU, etc.). The display screen, memory, and processor are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform various functions or steps performed by the device in the above method embodiments.

[0370] This application also provides a chip system including at least one processor and at least one interface circuit. The processor and the interface circuit are interconnected via lines. For example, the interface circuit can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit can be used to send signals to other devices (e.g., the processor). Exemplarily, the interface circuit can read instructions stored in the memory and send the instructions to the processor. When the instructions are executed by the processor, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and this application does not specifically limit this.

[0371] This embodiment also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the image processing method described above.

[0372] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the image processing method described above.

[0373] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to cause the chip to execute the image processing methods in the above-described method embodiments.

[0374] In this embodiment, the electronic device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0375] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0376] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0377] The unit described as a separate component may or may not be physically separate. The component shown as a unit can be one physical unit or multiple physical units, that is, it can be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of the solution in this embodiment according to actual needs.

[0378] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0379] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0380] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of this application without departing from the spirit and scope of the technical solutions of this application.

Claims

1. A video call method, characterized in that, Applied to electronic devices, including: Add the first user as a friend; Video call with the first user; If the first condition is met, detect whether there is a risk of face swapping on the face of the first user in the video call; if a face swapping risk is detected, display the first prompt. If the second condition is met, a second prompt is displayed to detect the risk of face swapping. In response to the confirmation detection operation of the second prompt, the presence of face swapping risk is detected and the detection process is prompted. After obtaining the detection result, a third prompt is displayed. The detection result includes whether there is a risk of face swapping or whether there is no risk of face swapping. The first condition and the second condition are different.

2. The method according to claim 1, characterized in that, The first condition or the second condition includes at least one of the following: The time difference between the moment the first user is added as a friend and the start time of the video call is within a first duration. The first user is the first friend added; The video call is the first video call with the first user; The video call is a video call initiated by the first user. The first user is in the detection list of the electronic device, which records the first number of users recently added to the electronic device; as well as, The electronic device is subject to a risk event.

3. The method according to claim 1 or 2, characterized in that, The display of the first prompt includes: If the video call has not ended when a risk of face swapping is detected, the first prompt is displayed on the video call interface. The first prompt includes a re-detection control and / or a screen recording control. If the video call has ended when a risk of face swapping is detected, the first prompt will be displayed on the interface after the video call ends. The first prompt does not include the re-detection control or the screen recording control.

4. The method according to any one of claims 1-3, characterized in that, The test results indicate that there is no risk of face swapping. After receiving the test results, a third prompt will be displayed, including: If the video call has not ended when the detection result is obtained, the third prompt is displayed on the video call interface. The third prompt includes a re-detection control and / or a screen recording control. If the video call has ended when the detection result is obtained, the third prompt is displayed on the interface after the video call ends. The third prompt does not include the re-detection control or the screen recording control.

5. The method according to claim 3 or 4, characterized in that, The video call interface displays a prompt including a re-detection of controls, including: If the number of times the video call is checked for face-swapping risk does not exceed the first time, a prompt including a re-check control will be displayed on the video call interface.

6. The method according to claim 5, characterized in that, If the number of times the video call is checked for face-swapping risk exceeds the first number, a prompt without a re-detection control will be displayed on the video call interface.

7. The method according to any one of claims 3-6, characterized in that, After the video call interface displays a prompt including a re-detection control, the method further includes: In response to the triggering operation of the re-detection control, the system detects whether there is a risk of face swapping and prompts the detection process. After obtaining the detection result, a fourth prompt is displayed, and the detection result includes whether there is a risk of face swapping or not.

8. The method according to any one of claims 3-7, characterized in that, After displaying a prompt including screen recording controls on the video call interface, the method further includes: In response to a trigger operation on the screen recording control, the screen of the video call interface is recorded until the video call ends, at which point the recording ends and the recorded video is saved.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: If the second condition is met and the first user's face is not detected, a message indicating that the detection was incomplete is displayed; or, If the second condition is met, and the video call ends before the image frame of the video call used for detection is acquired, a prompt indicating that the detection was not completed is displayed on the interface for ending the video call. Specifically, if the first condition is met and no face is detected, or if the video call ends before an image frame is acquired, no message indicating that the detection is incomplete will be displayed.

10. The method according to any one of claims 1-9, characterized in that, The notification detection process includes: Display at least one of the following messages: a prompt to start detection, a prompt that is detecting, and a detection animation.

11. The method according to any one of claims 1-10, characterized in that, The second condition includes the first sub-condition and the second sub-condition; If the second condition is met, a second warning will be displayed indicating the risk of face swapping, including: If the first sub-condition is met, a second prompt indicating the risk of face swapping is displayed. The first sub-condition includes turning on the face swapping detection switch of the electronic device. If the second sub-condition is met, a second prompt will be displayed to enable the face-swapping detection function and perform detection. The second sub-condition includes turning off the face-swapping detection switch of the electronic device.

12. The method according to claim 11, characterized in that, After displaying the second prompt indicating that the face-swapping detection function is enabled and detection is initiated, in response to the confirmation detection operation of the second prompt, the system detects whether there is a risk of face-swapping, including: In response to the confirmation check operation of the second prompt, the face-swapping detection function is enabled and the risk of face-swapping is detected.

13. The method according to any one of claims 1-12, characterized in that, The second warning displayed to detect the risk of face swapping includes: When the second prompt is displayed from the 1st to the Nth time, the second prompt is displayed in the form of a card, which includes a description of the face-swapping detection function and / or a control to confirm the detection. When the second prompt is displayed for the N+1th time, the second prompt is displayed in capsule form, wherein the capsule-form second prompt does not include a function introduction of the face-swapping detection function or a control for confirming the detection; Where N is a natural number greater than 1.

14. The method according to any one of claims 1-13, characterized in that, The test results indicate that there is a risk of face swapping. The display of the third prompt includes: The third prompt is displayed on the video call interface and remains displayed until the video call ends.

15. The method according to any one of claims 1-13, characterized in that, The test results indicate that there is no risk of face swapping. After displaying the third prompt, the method further includes: After the third prompt has been displayed for a certain duration, the third prompt will be removed from display.

16. The method according to claim 14, characterized in that, After the third prompt is displayed on the video call interface, the method further includes: After the video call ends, a details entry will be displayed; In response to the triggering operation of the details entry, the detection record of face-swapping risk detection is displayed.

17. The method according to claim 14, characterized in that, After the third prompt is displayed on the video call interface, the method further includes: In response to the operation of swiping down to enter the pull-down notification center in the video call interface, the pull-down notification center is displayed, the pull-down notification center includes a first notification, the content of the first notification being consistent with the third prompt.

18. The method according to any one of claims 1-17, characterized in that, The test results indicate that there is a risk of face swapping. After displaying the third prompt, the method further includes: Within four hours after detecting the risk of face-swapping, a risky behavior was detected, and a fifth warning of face-swapping risk was displayed.

19. The method according to claim 11, characterized in that, The second sub-condition also includes turning on the risk protection switch of the electronic device, and the face-swapping detection function is a sub-function of risk protection.

20. The method according to any one of claims 1-19, characterized in that, Before adding the first user as a friend, the method further includes: If the third condition is met, a sixth prompt to enable the risk protection function will be displayed. The third condition includes the risk protection switch being turned off and the face-swapping detection switch being turned off. In response to the triggering operation of the sixth prompt, the risk protection settings interface is displayed, which includes a risk protection switch that is turned off. In response to the activation of the risk protection switch, the risk protection function and the face-swapping detection function are activated.

21. The method according to any one of claims 1-20, characterized in that, Before adding the first user as a friend, the method further includes: If the fourth condition is met, a seventh prompt will be displayed to enable the face-swapping detection function, wherein the fourth condition includes turning on the face-swapping detection switch. In response to the triggering operation of the seventh prompt, the face-swapping detection settings interface is displayed, which includes a face-swapping detection switch in the enabled state and a function description of the face-swapping detection function.

22. The method according to any one of claims 1-21, characterized in that, The face-swapping detection function is a sub-function of risk protection; Before adding the first user as a friend, the method further includes: In response to the activation of the risk protection switch or the face-swapping detection switch in the settings application, the face-swapping detection function is enabled.

23. The method according to claim 22, characterized in that, In response to the action of turning on the face-swapping detection switch in the settings app, enable the face-swapping detection function, including: If the risk protection switch is not turned on, a prompt to turn on the risk protection will be displayed in response to the operation of turning on the face swap detection switch; In response to the confirmation prompt to enable risk protection, the risk protection and face-swapping detection functions are enabled.

24. The method according to claim 23, characterized in that, The risk protection is provided by the system management service in the electronic device; The operation of confirming the prompt to enable risk protection, and enabling the risk protection and face-swapping detection functions, includes: If the System Manager service is not enabled, in response to the confirmation of the prompt to enable risk protection, a prompt to enable the System Manager service will be displayed. In response to the confirmation prompt to enable the system manager service, the system manager service, risk protection, and face-swapping detection functions are enabled.

25. An electronic device, characterized in that, include: A display screen, one or more processors, and one or more memories; the one or more processors are coupled to the display screen and the one or more memories; the one or more memories are used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the electronic device to perform the method as described in any one of claims 1-24.

26. A computer-readable storage medium storing computer instructions thereon, characterized in that, When the computer instructions are executed on the electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-24.

27. A computer program product comprising computer instructions, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-24.

Images