HK1228148B - User state reminding method and device in video communication - Google Patents

Description

User status reminder method and device in video communication

Technical Field

The present application relates to the field of communication technology, and in particular to a method and device for reminding user status in video communication.

Background Art

When multiple users are in different locations, such as between company headquarters and branch offices, video conferencing can eliminate geographical limitations. Traditional video conferencing requires specialized video and communication equipment, which is not only expensive but also requires fixed installation in places like conference rooms, which still has significant limitations.

In the related art, it is proposed to configure a video communication function on portable electronic devices such as mobile phones and tablets, so that users can use the video communication function almost anywhere, thereby improving the flexibility of use.

Summary of the Invention

In view of this, the present application provides a method and device for user status reminder in video communication, which can enable users participating in video communication to understand each other's status changes at any time, so as to make timely adjustments to the video communication process and content.

To achieve the above objectives, this application provides the following technical solutions:

According to a first aspect of the present application, a method for reminding a user of a status in a video communication is proposed, comprising:

During the video communication between the current user and other users, a mid-communication event is detected;

A reminder message regarding the mid-communication event is sent to the other user, where the reminder message is used to indicate whether the current user has a response requirement to the mid-communication event.

According to a second aspect of the present application, a method for reminding a user of a status in a video communication is proposed, comprising:

During a video communication between the current user and another user, a reminder message about the other user is received, the reminder message being used to indicate whether the other user has a response requirement to a mid-communication event;

According to the reminder message, the display content of the video window corresponding to the other user in the video communication page is adjusted.

According to a third aspect of the present application, a user status reminder device in video communication is proposed, comprising:

The monitoring unit detects a mid-communication event during a video communication between the current user and other users;

A sending unit is configured to send a reminder message regarding the mid-communication event to the other users, wherein the reminder message is used to indicate whether the current user has a response requirement for the mid-communication event.

According to a fourth aspect of the present application, a user status reminder device in video communication is proposed, comprising:

a receiving unit, which receives a reminder message about the other user during a video communication between the current user and the other user, wherein the reminder message is used to indicate whether the other user has a response requirement to a mid-communication event;

The adjusting unit adjusts the display content of the video window corresponding to the other user in the video communication page according to the reminder message.

It can be seen from the above technical solution that this application determines whether the current user has a response requirement for the mid-communication event when a mid-communication event is monitored during the video communication process, and then sends a reminder message to other users participating in the video communication, so that other users can promptly understand the current user's participation status in the video communication, such as whether the current user is temporarily unable to participate in the video communication due to the need to respond to the mid-communication event, so that other users can make timely adjustments to the video communication process and content.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flowchart of a method for reminding user status in video communication based on one user, provided by an exemplary embodiment of the present application.

FIG2 is a flowchart of a method for reminding a user status in a video communication based on a user on the other side, provided by an exemplary embodiment of the present application.

FIG3 is a flow chart of a method for reminding user status in video communication provided by an exemplary embodiment of the present application.

4A-12 are schematic diagrams of an interface for user status reminder in video communication provided by an exemplary embodiment of the present application.

FIG13 is a flowchart of another method for reminding user status in video communication provided by an exemplary embodiment of the present application.

FIG14 is a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application.

FIG15 is a block diagram of a user status reminder device in video communication based on one user, provided by an exemplary embodiment of the present application.

FIG16 is a schematic structural diagram of another electronic device provided by an exemplary embodiment of the present application.

FIG17 is a block diagram of a device for reminding user status in video communication based on a user on the other side, provided by an exemplary embodiment of the present application.

DETAILED DESCRIPTION

In related technologies, when users A, B, C, etc. participate in a video communication, if user A receives a call from user D during the video communication, then user A will not be able to participate in the video communication. However, since users B, C, etc. are not aware that user A is on a call, users B, C, etc. may cause user A to miss important communication content during the normal process of promoting the video communication, and even affect the subsequent execution of related communication content.

Therefore, the present application solves the above-mentioned problems in the related art by reminding the user status during the video communication process. To further illustrate the present application, the following embodiments are provided:

FIG1 is a flowchart of a method for reminding user status in video communication based on one user, provided by an exemplary embodiment of the present application. As shown in FIG1 , the method is applied to an electronic device of one user and may include the following steps:

Step 102: During the video communication between the current user and other users, a mid-communication event is detected.

Step 104: Send a reminder message about the mid-communication event to the other users, where the reminder message is used to indicate whether the current user has a response requirement to the mid-communication event.

In one embodiment, upon detecting a mid-communication event, it is possible to directly determine that the current user has a need to respond to the mid-communication event, without having to consider the current user's actual handling of the mid-communication event. For example, if the mid-communication event is a call event, as long as a call request is detected, it can be determined that the user has a need to make a call, without having to consider whether the user answered or hung up.

For example, based on the running state of the video communication application process, it is possible to identify whether there is a mid-communication event, thereby determining whether the current user has a need to respond to the mid-communication event, and sending a corresponding reminder message to other users. Specifically, when it is monitored that the video communication application process switches to the background running state, it is determined that the current user has a need to respond to the mid-communication event; when it is monitored that the video communication application process returns from the background running state to the foreground running state, it is determined that the current user does not have a need to respond to the mid-communication event.

In another embodiment, whether the current user has a response requirement to the mid-communication event can be determined based on the current user's processing operation on the mid-communication event, and a corresponding reminder message can be sent to the other user. Specifically, when the processing operation is a connection response operation for the mid-communication event, it is determined that the current user has a response requirement to the mid-communication event; and when the processing operation is a disconnection operation for the mid-communication event, it is determined that the current user does not have a response requirement to the mid-communication event.

Accordingly, FIG2 is a flowchart of a method for reminding a user status in a video communication based on the other user, provided by an exemplary embodiment of the present application. As shown in FIG2 , the method is applied to the electronic device of the other user and may include the following steps:

Step 202: During a video communication between a current user and another user, a reminder message about the other user is received, where the reminder message is used to indicate whether the other user has a response requirement to a mid-communication event.

Step 204: Adjust the display content of the video window corresponding to the other user in the video communication page according to the reminder message.

In this embodiment, when the other user has a response requirement for the mid-communication event, the user status information corresponding to the response requirement is shown in the video window; when the other user has no response requirement for the mid-communication event, the video screen of the other user is shown in the video window.

It can be seen from the above technical solution that this application determines whether the current user has a response requirement for the mid-communication event when a mid-communication event is monitored during the video communication process, and then sends a reminder message to other users participating in the video communication, so that other users can promptly understand the current user's participation status in the video communication, such as whether the current user is temporarily unable to participate in the video communication due to the need to respond to the mid-communication event, so that other users can make timely adjustments to the video communication process and content.

The following describes the technical solution of the present application in detail in conjunction with the interaction process between two users corresponding to the reminder operation in video communication. FIG3 is a flowchart of a method for reminding user status in video communication provided by an exemplary embodiment of the present application. As shown in FIG3, the method may include the following steps:

Step 302: User A initiates a conference creation request to the server.

In this embodiment, user A, user B, and user C each operate and communicate through an electronic device, such as a mobile phone or tablet, which is not limited in this application. The electronic device is installed with an application that can implement communication functions such as video communication to implement various communication operations such as video communication and phone calls in this application. Therefore, those skilled in the art should understand that, for ease of description, when describing "user A and user B communicate," it should actually mean that user A and user B communicate through their respective electronic devices.

For example, the aforementioned application can be an instant messaging application, such as "DingTalk" or other enterprise instant messaging applications (EIM). Then, users A, B, and C can implement corresponding application functions, such as video communication, by operating on the DingTalk function page. For ease of description and understanding, the following embodiments use "DingTalk" as an example to illustrate the technical solutions of this application for video communication scenarios in an enterprise environment, such as "video conferencing" scenarios.

As shown in Figure 4A, the function selection page provided by DingTalk provides a function icon and text description about "video conferencing"; of course, "video conferencing" can also be triggered in other ways. For example, in the "Work" tab shown in Figure 4B, a function icon about "video conferencing" is also provided. Then, when it is detected that user A triggers the "video conferencing" function icon in Figure 4A or Figure 4B, it can switch to the contact configuration page shown in Figure 5 to "invite contacts to video conferencing", for example, user A has invited user B and user C to participate in the video conference.

When it is detected that user A triggers the icon in the contact configuration page shown in Figure 5, other users can be further invited to join the video conference. If there is a limit on the number of participants in the video conference, assuming that the limit is to support a maximum of 5 people at a time, then as shown in Figure 5, a message such as "2 people can be invited" can be displayed below the icon, indicating that in addition to the currently confirmed user A (i.e., "me"), user B, and user C, 2 more users can be invited to join the current video conference. When it is detected that user A triggers the icon in the contact configuration page shown in Figure 5, the invited users can be removed.

After determining all contacts that need to be invited, when detecting that user A triggers the "click to initiate" operation at the bottom of the page shown in Figure 5, the electronic device can initiate a corresponding meeting creation request to the DingTalk server through DingTalk.

Step 304: Create a video conference.

In this embodiment, FIG6 shows a waiting page when creating a video conference according to an exemplary embodiment. At this time, user A can terminate the creation of this video conference by triggering “Cancel” in the upper left corner of the page.

After the video conference is successfully created, FIG7A shows the video conference page on the electronic device of user A. The background of the page is the video image captured by the camera of the electronic device of user A, and video windows corresponding to other conference participants such as user B and user C are shown at the bottom of the page. Each video window shows the video image captured by the camera of the electronic device of the corresponding user. The video conference page may also include other function buttons, such as "mute", "hands-free", "turn off camera", "switch camera", etc., to implement corresponding control functions. When the preset hiding operation of the current user is detected, such as a single click, double click or long press on the background area of the electronic device screen, the above function buttons shown in FIG7A can be hidden, so that the page display mode is switched from the normal mode shown in FIG7A to the hidden mode shown in FIG7B, so as to avoid the function buttons from blocking the video image, making it easier for the current user to view the video image. Among them, the video conferencing page does not necessarily use the video screen captured by the camera of the current user's electronic device. For example, when user A is detected selecting the video window of user B or user C shown in Figure 7A, the video screen in the selected video window can be configured as the background of the video conferencing page, and the selected video window can be configured to correspond to the current user, user A, so that the video screen captured by the camera of user A's own electronic device can be displayed in the video window.

Similarly, Figure 8 shows a video conferencing page on user C's electronic device, except that the page background is changed to the video image captured by the camera of user C's electronic device, and the bottom of the page shows video windows corresponding to other conference participants such as user A and user B. The layout of the entire video conferencing page is similar to Figure 7A and will not be repeated here.

Step 306: User A's electronic device detects a call request.

In this embodiment, if user A's electronic device detects a call request for itself while participating in the aforementioned video conference, this is equivalent to a communication event occurring midway through the video conference, i.e., a midway communication event. The type of midway communication event is not limited to a call; for example, the midway communication event can also be another video conference initiated by another user; in fact, this application does not restrict the type of midway communication event.

Of course, mid-communication events should be implemented using different communication methods than video conferencing to ensure that mid-communication events do not cause video conferencing interruptions. For example, when the mid-communication event is a call event, the call event is implemented through the CS (Circuit Switch) domain of mobile communications, while the video conferencing can be implemented through the PS (Packet Switch) domain of mobile communications or through a network such as Wi-Fi.

According to an exemplary embodiment of the present application, it is possible to determine whether the current user has a response requirement for the mid-communication event based on the current user's processing operation on the mid-communication event, and thus send a corresponding reminder message to other users. The following is a detailed description of this embodiment through steps 308-318 shown in Figure 3:

Step 308: User A's electronic device detects that the call is connected.

In this embodiment, based on user A's handling of the mid-communication event, it is determined whether user A has a response requirement for the mid-communication event. For example, in the case of a call event, when the electronic device detects a call request and detects user A's answering operation, the call event is connected, and user A is deemed to have a response requirement for the call event.

In step 310 , the electronic device of user A sends a first reminder message to the server and terminates local related rendering.

Step 312: The server sends the first reminder message to user B, user C, etc.

In this embodiment, user A's electronic device can send a first reminder message to the server (when using DingTalk as an example, the server is the DingTalk server), and the server in turn informs user B, user C and other video conference participants, so that these participants know whether user A has a response requirement for the mid-communication event (such as the above-mentioned call event), and thus adjust the display content of the video window corresponding to user A in the video conference page of their own electronic device.

Take user C as an example. When there is a response demand, for the video window corresponding to user A in the video conference page as shown in Figure 8, user C's electronic device can display the user status information corresponding to the response demand in the video window (that is, switch the video screen in the video window to the user status information corresponding to the response demand), such as "on a call" or other content as shown in Figure 9, to prompt user C that user A is performing a mid-communication event of the "call" type and may be temporarily unable to participate in the video conference; similarly, other users such as user B can also view the relevant user status information on their own electronic devices. Then, when all participants in the video conference know that user A is handling a mid-communication event such as a "call", these users can avoid important content or directly pause the progress of the video conference until user A returns to the video conference, thereby preventing user A from missing relevant video conference content. Especially for more important corporate video conferencing scenarios, preventing user A from missing relevant meeting content and affecting the progress of related work has important corporate management significance.

In addition, for user A's electronic device, in order to ensure that user A responds normally to the mid-communication event, the electronic device can terminate the rendering operations related to the video conference while retaining the video conference, such as pausing the page display output of the video conference and the use of devices such as cameras and microphones, and instead perform rendering operations related to the mid-communication event, such as outputting the corresponding call page and using devices such as microphones.

Of course, although in the embodiment shown in Figure 3, the first reminder message mentioned above (and the second reminder message described below, etc.) needs to be forwarded by the server between user A and user B and user C, in fact, user A can obviously also send it directly to user B and user C through point-to-point communication without the need for forwarding by the server, and this application does not limit this.

In step 314, user A's electronic device detects that the call is disconnected.

In this embodiment, user A's response to the mid-communication event also includes a disconnection operation. Taking a call event as an example: after the electronic device detects the aforementioned connection response operation and connects the call, if it detects a disconnection operation by user A, the call event is disconnected and it is deemed that user A no longer has a need to respond to the call event.

In step 316, user A's electronic device sends a second reminder message to the server and resumes local related rendering.

Step 318: The server sends a second reminder message to user B, user C, etc.

In this embodiment, similar to steps 310-312, user A's electronic device can send a second reminder message to the server (when using DingTalk as an example, the server is the DingTalk server), and the server in turn informs user B, user C and other video conference participants, so that these participants know whether user A has a response requirement for the mid-communication event (such as the above-mentioned call event), and thus adjust the display content of the video window corresponding to user A in the video conference page of their own electronic device.

Still taking user C as an example. When there is no response demand, user C's electronic device can adopt the method shown in Figure 8, that is, in the video window corresponding to user A in the video conference page, the video screen of user A's electronic device is displayed; in particular, for the case where there is a response demand to no response demand, it should be understood that: user C's electronic device can be restored from the video conference page shown in Figure 9 (that is, the user status information corresponding to the response demand is displayed in the video window corresponding to user A) to the video conference page shown in Figure 8 (that is, the video screen from user A's electronic device is displayed in the video window corresponding to user A). Similarly, other users such as user B can also view the display or restoration of the relevant video screen on their own electronic devices.

Furthermore, when the electronic device of user A ends the mid-communication event, that is, when it detects that the processing operation of user A for the mid-communication event is a disconnection operation for the mid-communication event, it can resume the rendering operations related to the video conference, including the display restoration of the video conference page, and the use of the camera and microphone, etc. In addition, after the mid-communication event ends, the electronic device of user A may also need to adjust the communication configuration for the video conference in order to provide the best communication effect. Then, for user B, user C, etc., during the process of user A's electronic device performing the above-mentioned processing operations, it may not be possible to immediately resume the display of the video screen of user A's electronic device. Therefore, as shown in FIG10 , information such as "Restoring" can be displayed in the video window corresponding to user A to prompt user B, user C, etc. to wait patiently.

It should be noted that:

When judging whether the current user (such as user A mentioned above) has a need to respond to the mid-communication event based on the processing operation of the current user (such as user A mentioned above), in addition to the hang-up operation for the connected call event shown in step 314, it is also possible to directly hang up the unconnected call event in step 308, that is, to perform a disconnect operation for the unconnected mid-communication event. The processing method that can be adopted at this time is: In one case, it can be determined that the current user has no need to respond to the mid-communication event, then the electronic device of the current user (taking user A as an example) can send a reminder message to other users participating in the video conference (taking user B and user C as examples) (similar to the second reminder message in steps 316-318, indicating that when In another case, since the current user's participation in the video conference is not affected (or the current user has no response requirement for the mid-communication event), the electronic devices of user B and user C display the video screen of user A's electronic device in the video window corresponding to user A in the video conference page, and since the electronic devices of user B and user C already display the video screen of user A's electronic device in the video window, it is equivalent to that no display change occurs. In another case, since it does not affect (or has a very small impact on) the current user's participation in the video conference, and as mentioned above, no display change actually occurs on the electronic devices of other users such as user B and user C, the corresponding mid-communication event can be ignored, and no reminder message about the response requirement is conveyed.

In addition, in the technical solution of the present application, the participants of the video conference can also manage the video conference. Taking the electronic device of user A, the initiator of the video conference, as an example, assuming that the electronic device detects that user A performs a preset user operation on the video conference page shown in Figure 7A, such as sliding the video conference page to the left, it can switch to the conference management page shown in Figure 11. As shown in Figure 11, user A can click on the "microphone" icon to the right of the icons of user B, user C, etc. to implement mute management of the corresponding users, and user A can also trigger the "mute all" function at the top of the page to mute all users at the same time.

User A can also add or remove users participating in the video conference through the conference management page shown in Figure 11. For example, when the number of participants in a video conference is limited to 5, since the conference management page shown in Figure 11 already includes 4 people, namely User A, User B, User C, and User D, "1 person can be invited" can be displayed below the icon, indicating that User A can add at most one user to the current video conference. As shown in Figure 12, User A can also call out the "Remove" button by, for example, sliding the management window corresponding to User D to the left, and when detecting that User A has triggered the "Remove" button, User D will be removed from the current video conference.

In the conference management page shown in Figures 11-12, when user D has not been successfully added to the video conference, for example, user D has not accepted the conference invitation or refused to join, a replay icon can be displayed in the relevant management window, that is, the icon located to the left of the "microphone" icon in Figures 11-12, so that when user A triggers the replay icon, a replay request can be initiated for user D to re-invite him to join the current video conference.

For non-initators such as user B and user C, depending on the actual configuration, they can have the same management permissions as user A, the initiator of the video conference, that is, realize the various management functions shown in Figures 11-12 and above; or, they can have only some of the management permissions of user A, such as only mute permissions, no invite or remove permissions; or, management permissions may not be assigned to non-initators.

FIG13 is a flowchart of another method for reminding user status in a video conference provided by an exemplary embodiment of the present application. As shown in FIG13 , the method may include the following steps:

Step 1302: User A initiates a conference creation request to the server.

Step 1304: Create a video conference.

Step 1306: User A's electronic device detects a call request.

In this embodiment, steps 1302-1306 may refer to steps 302-306 shown in FIG3 , and are not described again here.

According to an exemplary embodiment of the present application, it is possible to determine whether the current user has a response requirement for the mid-communication event based on the running status of the video conferencing application process, thereby sending a corresponding reminder message to other users. The following is a detailed description of this embodiment through steps 1308-1318 shown in Figure 13:

In step 1308, user A's electronic device switches the video conference application process to a background running state.

In this embodiment, when it is monitored that the application process of the video conference switches to the background running state, the application process may lose permissions for screen display, speaker playback, camera acquisition, etc., affecting the normal implementation of the video conference. Therefore, it can be determined that user A has a response requirement for the corresponding mid-communication event, regardless of whether user A performs a connection response operation, a disconnection operation, or does not process the mid-communication event.

In other words, when a mid-communication event is detected, as long as the mid-communication event causes the application process of the video conference to switch to the background running state, it is determined that the current user has a need to respond to the mid-communication event. For example, the mid-communication event may be a call event with permissions such as screen display and speaker playback. For some other types of mid-communication events, such as receiving emails and instant messaging messages in the background, since they will not cause the application process of the video conference to switch to the background running state, it can be determined that the current user does not have a need to respond to the mid-communication event.

In step 1310 , user A's electronic device sends a first reminder message to the server and terminates local related rendering.

Step 1312: The server sends the first reminder message to user B, user C, etc.

In this embodiment, steps 1310-1312 may refer to steps 310-312 shown in FIG3 , and are not described again here.

In step 1314, the electronic device of user A restores the video conference application process from the background running state to the foreground running state.

In this embodiment, when the application process of the video conference is restored to the foreground running state, it usually indicates that the corresponding mid-communication event is disconnected. For example, the mid-communication event may be disconnected due to a disconnection operation performed by the current user (direct disconnection when the call is not connected, or hanging up when the call is connected), or it may be automatically disconnected due to the current user not processing it or waiting timeout.

In other words, when it is monitored that the application process of the video conference is restored from the background running state to the foreground running state, it indicates that the video conference can normally use permissions such as screen display, speaker playback, camera acquisition, etc., and the mid-communication event does not have the above permissions and will not affect the normal implementation of the video conference. Therefore, it can be determined that the current user has no response requirements for the corresponding mid-communication event.

Step 1316: User A's electronic device sends a second reminder message to the server and resumes local related rendering.

Step 1318: The server sends a second reminder message to user B, user C, etc.

In this embodiment, steps 1316-1318 may refer to steps 310-312 shown in FIG3 , and are not described again here.

In addition, when the current user receives a reminder message from another user, in addition to adjusting the display content of the video window corresponding to the other user in the video communication page (or video conference page) (for example, switching the display between Figure 8 and Figure 9), the current user's electronic device can also perform the reminder operation in at least one of the following ways: vibration, flashing of the breathing light, presenting a breathing display of the video window corresponding to the other user (such as high-frequency edge scaling, content jitter, etc.), switching the video window of the other user with the background of the video communication page (for example, in Figure 9, the display content of the smaller video window of user A is switched to the larger background of the entire video communication page), etc.

Then, through the above-mentioned prompt operation, a higher intensity prompt can be provided to the current user without affecting the video communication process as much as possible, avoiding the display switching shown in Figures 8-9 from being ignored by the current user, helping the current user to pay attention to and understand the real-time status of other users, and ensuring that when other users have a response demand for mid-communication events, the current user can pause the advancement of the video communication in time, and when other users do not have a response demand for mid-communication events, even if the current user temporarily leaves due to suspending the video communication, he can resume the advancement of the video communication in time.

FIG14 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application. Referring to FIG14 , at the hardware level, the electronic device includes a processor 1402, an internal bus 1404, a network interface 1406, a memory 1408, and a non-volatile memory 1410, and may also include hardware required for other services. The processor 1402 reads the corresponding computer program from the non-volatile memory 1410 into the memory 1402 and then runs it, forming a user status reminder device in video communication at the logical level. Of course, in addition to software implementation, the present application does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

Please refer to FIG15 , in a software implementation, the user status reminder device in the video communication may include a monitoring unit 1502 and a sending unit 1504 .

The monitoring unit 1502 monitors a mid-communication event during a video communication between the current user and other users;

The sending unit 1504 sends a reminder message about the mid-communication event to the other users, where the reminder message is used to indicate whether the current user has a response requirement for the mid-communication event.

Optionally, the sending unit 1504 is specifically configured to:

According to the running state of the application process of the video communication, it is determined whether the current user has a response requirement for the mid-communication event, and a corresponding reminder message is sent to the other users.

Optional:

When it is detected that the video communication application process switches to a background running state, the sending unit 1504 determines that the current user has a response requirement for the mid-communication event;

When monitoring that the video communication application process is restored from the background running state to the foreground running state, the sending unit 1504 determines that the current user has no response requirement for the mid-communication event.

Optionally, the sending unit 1504 is specifically configured to:

According to the processing operation of the current user on the mid-communication event, it is determined whether the current user has a response requirement for the mid-communication event, and a corresponding reminder message is sent to the other users.

Optional:

When the processing operation is a connection response operation for the mid-communication event, the sending unit 1504 determines that the current user has a response requirement for the mid-communication event;

When the processing operation is a disconnection operation for the midway communication event, the sending unit 1504 determines that the current user has no response requirement for the midway communication event.

Optionally, also include:

The terminating unit 1506 , when the processing operation is a connection response operation for the mid-communication event, terminating the rendering operation related to the video communication;

The resuming unit 1508 resumes the rendering operation related to the video communication when the processing operation is a disconnection operation for the mid-communication event.

Optionally, the mid-communication event is a call event.

FIG16 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present application. Referring to FIG16 , at the hardware level, the electronic device includes a processor 1602, an internal bus 1604, a network interface 1606, a memory 1608, and a non-volatile memory 1610, and may also include hardware required for other services. The processor 1602 reads the corresponding computer program from the non-volatile memory 1610 into the memory 1602 and then runs it, forming a user status reminder device in video communication at the logical level. Of course, in addition to software implementation, the present application does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

Please refer to FIG17 , in a software implementation, the user status reminder device in the video communication may include a receiving unit 1702 and an adjusting unit 1704 .

The receiving unit 1702 receives a reminder message about the other user during a video communication between the current user and the other user, wherein the reminder message is used to indicate whether the other user has a response requirement to a mid-communication event;

The adjusting unit 1704 adjusts the display content of the video window corresponding to the other user in the video communication page according to the reminder message.

Optionally, the adjusting unit 1704 is specifically configured to:

When the other user has a response requirement for the mid-communication event, user status information corresponding to the response requirement is displayed in the video window;

When the other user has no response requirement for the midway communication event, the video screen of the other user is shown in the video window.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims (20)

1. A method for user status notification in video communication, characterized in that it includes: During the current video communication between the user and other users, an intermittent communication event was detected; Send a reminder message about the interrupted communication event to the other users. The reminder message is used to indicate whether the current user has a need to respond to the interrupted communication event. 2. The method according to claim 1, wherein sending a reminder message about the mid-communication event to the other users comprises: Based on the running status of the video communication application process, determine whether the current user has a need to respond to the mid-communication event, and send corresponding reminder messages to the other users. 3. The method according to claim 2, characterized in that, determining whether the current user has a response requirement to the mid-transmission communication event based on the running status of the video communication application process includes: When it is detected that the video communication application process has switched to background running state, it is determined that the current user has a response requirement for the mid-communication event; When it is detected that the video communication application process has resumed from background running state to foreground running state, it is determined that the current user does not have a response requirement for the mid-communication event. 4. The method according to claim 1, wherein sending a reminder message about the mid-communication event to the other users comprises: Based on the current user's handling of the mid-communication event, determine whether the current user has a response requirement for the mid-communication event, and send corresponding reminder messages to the other users. 5. The method according to claim 4, characterized in that, determining whether the current user has a response requirement for the mid-transmission communication event based on the current user's processing operation of the mid-transmission communication event includes: When the processing operation is a connection response operation for the mid-communication event, it is determined that the current user has a response requirement for the mid-communication event. When the processing operation is a disconnection operation for the mid-communication event, it is determined that the current user has no need to respond to the mid-communication event. 6. The method according to claim 5, characterized in that it further comprises: When the processing operation is a response operation to the mid-communication event, the rendering operation related to the video communication is suspended. When the processing operation is a disconnection operation in response to the mid-communication event, the rendering operation related to the video communication is resumed. 7. The method according to claim 1, wherein the mid-transmission communication event is a call event. 8. A method for user status notification in video communication, characterized in that it includes: During a video communication between the current user and another user, a reminder message is received regarding the other user. The reminder message is used to indicate whether the other user has a need to respond to an interrupted communication event. Based on the notification message, adjust the display content of the video window corresponding to the other user on the video communication page. When the other user has a response requirement for the mid-communication event, display the user status information corresponding to the response requirement in the video window; when the other user does not have a response requirement for the mid-communication event, display the video screen of the other user in the video window. 9. A user status reminder device in video communication, characterized in that it comprises: The monitoring unit detects mid-transmission communication events during the current user's video communication with other users; The sending unit sends a reminder message about the mid-transmission communication event to the other users. The reminder message is used to indicate whether the current user has a response requirement to the mid-transmission communication event. 10. The apparatus according to claim 9, wherein the transmitting unit is specifically used for: Based on the running status of the video communication application process, determine whether the current user has a need to respond to the mid-communication event, and send corresponding reminder messages to the other users. 11. The apparatus according to claim 10, characterized in that: When the video communication application process is detected to switch to background running state, the sending unit determines that the current user has a response requirement for the mid-communication event; When the video communication application process is detected to have resumed its foreground running state from the background, the sending unit determines that the current user does not have a response requirement for the mid-transmission communication event. 12. The apparatus according to claim 9, wherein the transmitting unit is specifically used for: Based on the current user's handling of the mid-communication event, determine whether the current user has a response requirement for the mid-communication event, and send corresponding reminder messages to the other users. 13. The apparatus according to claim 12, characterized in that: When the processing operation is a connection response operation for the mid-communication event, the sending unit determines that the current user has a response requirement for the mid-communication event; When the processing operation is a disconnection operation for the mid-communication event, the sending unit determines that the current user has no need to respond to the mid-communication event. 14. The apparatus according to claim 13, characterized in that it further comprises: The termination unit terminates the rendering operation related to the video communication when the processing operation is a connection response operation for the mid-communication event. The recovery unit, when the processing operation is a disconnection operation for the mid-communication event, restores the rendering operation related to the video communication. 15. The apparatus according to claim 9, wherein the mid-transmission communication event is a call event. 16. A user status reminder device in video communication, characterized in that it comprises: The receiving unit receives a reminder message about the other user during video communication between the current user and other users. The reminder message is used to indicate whether the other user has a need to respond to the mid-communication event. The adjustment unit adjusts the display content of the video window corresponding to the other user on the video communication page according to the reminder message. When the other user has a response requirement for the mid-communication event, the user status information corresponding to the response requirement is displayed in the video window; when the other user does not have a response requirement for the mid-communication event, the video screen of the other user is displayed in the video window. 17. An electronic device, characterized in that it comprises: processor; Memory used to store processor-executable instructions; The processor is configured to execute instructions to implement the method as described in any one of claims 1-7. 18. A computer-readable storage medium having stored thereon computer instructions, characterized in that, when executed by a processor, the instructions implement the steps of the method as claimed in any one of claims 1-7. 19. An electronic device, characterized in that it comprises: processor; Memory used to store processor-executable instructions; The processor is configured to execute instructions to implement the method as described in claim 8. 20. A computer-readable storage medium having stored thereon computer instructions, characterized in that, when executed by a processor, the instructions implement the steps of the method as claimed in claim 8.