Video conference annotation method, device, equipment and medium

Abstract

The invention discloses a video conference annotation method and device, equipment and a medium, and relates to the technical field of communication. The method is applied to a first conference participating device, and comprises the following steps: under the condition that a sharing mode is started, periodically sending a current conference interface displayed by the first conference participating device to a server, so that the server forwards the current conference interface to any second conference participating device; receiving first annotation data which is forwarded by the server and is sent by the third conference participating device; drawing a first annotation in the current conference interface according to the first annotation data to obtain an updated current conference interface; wherein the second conference participating equipment is the conference participating equipment, except the first conference participating equipment, in the conference participating equipment, and the second conference participating equipment comprises third conference participating equipment. According to the method, the debugging complexity can be reduced, and the comment display speed of each participating device can be increased.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a video conference annotation method, device, equipment and medium. Background Art

[0002] Video conferencing refers to a meeting in which users in two or more locations have face-to-face conversations through electronic devices and the Internet. During a video conference, users usually annotate the conference content.

[0003] The way to annotate conference content in traditional video conferences is usually as follows: after triggering the annotation function, the user draws annotations on the local canvas using a tool such as a mouse that matches the electronic device; the electronic device sends the annotation data of the annotation drawn by the user on the local canvas to the server; after receiving the annotation data, the server draws in the video stream according to the annotation data, and after drawing is completed, distributes the video stream to other users, who can then see the annotations drawn by the user.

[0004] However, in the traditional way of annotating the conference content in video conferencing, the front-end electronic device is only responsible for sending the annotation data, and the back-end server draws according to the annotation data. If the back-end server draws incorrectly, the front-end cannot know it, and can only query the log at the server. That is, the traditional way of annotating the conference content in video conferencing has the problem of complex troubleshooting. Summary of the invention

[0005] One purpose of the present application is to provide a new technical solution for video conference annotation.

[0006] According to a first aspect of the present application, a video conference annotation method is provided, which is applied to a first participant device, comprising:

[0007] When the sharing mode is turned on, the current conference interface displayed by the first conference participant device is periodically sent to the server, so that the server forwards the current conference interface to any second conference participant device;

[0008] receiving a first batch of injection data sent by a third participant device and forwarded by the server;

[0009] Drawing the first batch of annotations in the current conference interface according to the first batch of annotation data to obtain an updated current conference interface;

[0010] The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

[0011] Optionally, the receiving the first batch of registration data sent by the third conference participant device and forwarded by the server includes:

[0012] receiving the first batch of injection data sent by the third participant device and the device identifier of the third participant device forwarded by the server;

[0013] The first batch of annotation data and the device identification of the corresponding third participant device are added to the first preset mapping relationship.

[0014] Optionally, the method further comprises:

[0015] receiving a first batch of injection adjustment data and a device identifier of the fourth conference participant device sent by the fourth conference participant device and forwarded by the server, wherein the second conference participant device includes the fourth conference participant device;

[0016] Determine, according to the first batch of annotation adjustment data, the device identifier of the fourth conference participant device, and the first preset mapping relationship, whether the first batch of annotation data corresponding to the first batch of annotation adjustment data is sent by the fourth conference participant device to the first conference participant device;

[0017] If yes, the current conference interface is adjusted according to the first batch of injection adjustment data to obtain an updated current conference interface.

[0018] Optionally, the method further comprises:

[0019] receiving a first batch of injection adjustment data and a device identifier of the fourth conference participant device sent by the fourth conference participant device and forwarded by the server, wherein the second conference participant device includes the fourth conference participant device;

[0020] Determine, according to the first batch of annotation adjustment data, the device identifier of the fourth conference participant device, and the first preset mapping relationship, whether the first batch of annotation data corresponding to the first batch of annotation adjustment data is sent by the fourth conference participant device to the first conference participant device;

[0021] If yes, the current conference interface is adjusted according to the first batch of injection adjustment data to obtain an updated current conference interface.

[0022] Optionally, the method further comprises:

[0023] Obtaining second annotation adjustment data of the first conference participant device for any annotation in the current conference interface;

[0024] The current conference interface is adjusted according to the second annotation adjustment data to obtain an updated current conference interface.

[0025] Optionally, the method further comprises:

[0026] Get the second batch of annotation data;

[0027] A second annotation is drawn in the current conference interface according to the second annotation data to obtain an updated current conference interface.

[0028] Optionally, the receiving the first batch of registration data sent by the third conference participant device and forwarded by the server includes:

[0029] receiving the first batch of annotation data sent by the third conference participant device, the device identifier of the third conference participant device, and the annotation identifier of the first batch of annotation data forwarded by the server;

[0030] Adding the first batch of annotation data and the corresponding annotation identifier to the second preset mapping relationship corresponding to the device identifier of the third participating device;

[0031] The third participant device draws the transparent first batch of annotations on the transparent layer on the display interface of the third participant device according to the first batch of annotation data and generates corresponding annotation marks, and sends the first batch of annotation data and the annotation marks to the server.

[0032] Optionally, the method further comprises:

[0033] receiving the third annotation adjustment data sent by the third conference participant device, the device identifier of the third conference participant device, and the annotation identifier corresponding to the third annotation adjustment data and forwarded by the server;

[0034] Determine, from the second preset mapping relationship between the device identifier of the third conference participant device and the first batch of annotation data corresponding to the annotation identifier corresponding to the third annotation adjustment data;

[0035] According to the third annotation adjustment data and the first batch of annotation data corresponding to the annotation identifier corresponding to the third annotation adjustment data, the current conference interface is adjusted to obtain an updated current conference interface;

[0036] The device identification of the third conference participant device corresponds to the second preset mapping relationship according to the third annotation adjustment data.

[0037] According to a second aspect of the present application, a video conference annotation method is provided, which is applied to a server and includes:

[0038] Get the second batch of annotation data;

[0039] A second annotation is drawn in the current conference interface according to the second annotation data to obtain an updated current conference interface.

[0040] Optionally, forwarding the first batch of annotation data to the first conference participant device includes:

[0041] The first batch of annotation data and the device identification of the third participating device are forwarded to the first participating device.

[0042] Optionally, the method further comprises:

[0043] receiving a first batch of injection adjustment data sent by a fourth participant device, wherein the second participant device includes the fourth participant device;

[0044] The first batch of injection adjustment data sent by the fourth conference participant device and the device identification of the fourth conference participant device are forwarded to the first conference participant device.

[0045] Optionally, forwarding the first batch of annotation data to the first conference participant device includes:

[0046] The first batch of annotation data, the device identification of the third conference participant device, and the annotation identification corresponding to the first batch of annotation data are forwarded to the first conference participant device.

[0047] Optionally, the method further comprises:

[0048] Receiving third annotation adjustment data sent by the third conference participant device and an annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data;

[0049] The third annotation adjustment data, the annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data, and the device identifier of the third conference participant device are forwarded to the first conference participant device.

[0050] According to a third aspect of the present application, a video conference annotation device is provided, which is applied to a first participant device, including:

[0051] A first sending module, configured to periodically send the current conference interface displayed by the first conference participant device to the server when the sharing mode is turned on, so that the server forwards the current conference interface to any second conference participant device;

[0052] A first receiving module, used for receiving the first batch of injection data sent by the third conference participant device and forwarded by the server;

[0053] A first updating module, configured to draw the first batch of annotations in the current conference interface according to the first batch of annotation data, to obtain an updated current conference interface;

[0054] The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

[0055] According to a fourth aspect of the present application, a video conference annotation device is provided, which is applied to a server and includes:

[0056] A second receiving module is used to receive the current conference interface sent by the first participating device;

[0057] A first forwarding module, used for forwarding the current conference interface sent by the first conference participant device to any second conference participant device;

[0058] A third receiving module, used for receiving the first batch of injection data sent by the third participating device;

[0059] A second forwarding module, used for forwarding the first batch of injection data to the first conference participating device;

[0060] The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

[0061] According to a fifth aspect of the present application, an electronic device is provided, the electronic device being a first conference participant device, the electronic device comprising the apparatus as described in the third aspect; or,

[0062] The electronic device is a server, and the electronic device includes the device as described in the fourth aspect;

[0063] Alternatively, the electronic device is the server or the first participating device, including a memory and a processor, the memory is used to store computer instructions, and the processor is used to call the computer instructions from the memory to execute the method as described in any one of the first aspect and the second aspect.

[0064] According to a sixth aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method according to any one of the first aspect and the second aspect is implemented.

[0065] The present application provides a video conference annotation method, which is applied to a first participant device, including: when the sharing mode is turned on, periodically sending the current conference interface displayed by the first participant device to the server, so that the server forwards the current conference interface to any second participant device; receiving the first batch of annotation data sent by the third participant device and forwarded by the server; drawing the first batch of annotations in the current conference interface according to the first batch of annotation data to obtain an updated current conference interface; wherein the second participant device is a participant device other than the first participant device in the participant device, and the second participant device includes the third participant device. In this method, the first participant device centrally annotates and draws the first batch of annotation data corresponding to the annotation behavior initiated by the user of the third participant device on the third participant device. In this way, since the first participant device is a front-end device, it is possible to know whether the annotation drawing is wrong through the conference interface of the first participant device, which can reduce the complexity of troubleshooting. In addition, as a front-end device, the first participant device has better annotation drawing performance than the server, so that the annotation drawing speed can be improved by centrally performing annotation drawing through the first participant device, thereby improving the annotation display speed of each participant device. Furthermore, no matter which user of the third participating device initiates the annotation behavior, the first participating device will centrally perform the annotation and drawing, and all annotations and drawings will be concentrated on the current conference interface of the first participating device, reducing some of the transmission and drawing processes in traditional video conferencing, thereby further improving the annotation display speed of each participating device.

[0066] Other features and advantages of the present application will become apparent from the following detailed description of exemplary embodiments of the present application with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the application and, together with the description, serve to explain the principles of the application.

[0068] Figure 1 A hardware configuration of an electronic device for implementing video conference annotation is provided according to an embodiment of the present application. Figure 1 ;

[0069] Figure 2 A schematic diagram of a method for implementing video conference annotation according to an embodiment of the present application Figure 1 ;

[0070] Figure 3 A schematic diagram of a method for implementing video conference annotation according to an embodiment of the present application Figure 2 ;

[0071] Figure 4 A schematic diagram of a video conference annotation device according to an embodiment of the present application Figure 1 ;

[0072] Figure 5 A schematic diagram of a video conference annotation device according to an embodiment of the present application Figure 2 ;

[0073] Figure 6 The present invention provides a frame structure of a hardware configuration of an electronic device for implementing a video conference annotation method according to an embodiment of the present application. Figure 2 . DETAILED DESCRIPTION

[0074] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present application.

[0075] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present application, its application, or uses.

[0076] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0077] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0078] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0079] Figure 1 The present invention provides a frame structure of a hardware configuration of an electronic device for implementing a video conference annotation method according to an embodiment of the present application. Figure 1 .

[0080] The electronic device 1000 is a first conference participant device or a server. The first conference participant device may be a smart phone, a portable computer, a tablet computer, a PDA, etc. The server may be a cloud server, etc.

[0081] The electronic device 1000 may include a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, a display device 1500, an input device 1600, a speaker 1700, a microphone 1800, and the like. The processor 1100 may be a central processing unit CPU, a microprocessor MCU, and the like. The memory 1200 may include, for example, a ROM (read-only memory), a RAM (random access memory), a non-volatile memory such as a hard disk, and the like. The interface device 1300 may include, for example, a USB interface, an earphone interface, and the like. The communication device 1400 may, for example, be capable of wired or wireless communication. The display device 1500 may be, for example, a liquid crystal display screen, a touch display screen, and the like. The input device 1600 may include, for example, a touch screen, a keyboard, and the like. The user may input / output voice information through the speaker 1700 and the microphone 1800.

[0082] Despite Figure 1 Multiple devices are shown for the electronic device 1000, but the present application may only involve some of the devices, for example, the electronic device 1000 only involves the memory 1200 and the processor 1100.

[0083] In the embodiment of the present application, the memory 1200 of the electronic device 1000 is used to store instructions, and the instructions are used to control the processor 1100 to execute the video conference annotation method provided in the embodiment of the present application.

[0084] In the above description, the technician can design instructions according to the scheme disclosed in this application. How instructions control the processor to operate is well known in the art, so it will not be described in detail here.

[0085] The present application provides a video conference annotation method, wherein the devices involved in the video conference include a server and multiple conference participating devices. In this embodiment, the server is in communication connection with the multiple conference participating devices, and the multiple conference participating devices include a first conference participating device and a second conference participating device other than the first conference participating device.

[0086] like Figure 2 As shown, the video conference annotation method provided in the present application and applied to the first participating device includes the following steps S210 to S230.

[0087] Step S210, when the sharing mode is turned on, periodically sending the current conference interface displayed by the first conference participant device to the server, so that the server forwards the current conference interface to any second conference participant device.

[0088] In this embodiment, for any participating device, a control for triggering a sharing mode, such as a "share screen" control, is displayed in the current conference interface of the participating device. When the user of the participating device triggers the aforementioned control, the sharing mode of the participating device is turned on, and the participating device becomes the first participating device. On this basis, the first participating device periodically sends the displayed current conference interface to the server, which is forwarded by the server to any second participating device, and the second participating device displays the current conference interface sent by the server. At this time, the first participating device shares its current conference interface with each second participating device.

[0089] It can be understood that when the meeting content corresponding to the current meeting interface of the first participating device changes, through the above-mentioned step S210, the meeting content of the current meeting interface shared by the first participating device and displayed by the second participating device also changes accordingly, that is, the meeting content corresponding to the current meeting interface of the first participating device and the meeting content of the current meeting interface shared by the first participating device and displayed by the second participating device change synchronously.

[0090] Corresponding to the above step S210, Figure 3 As shown, the video conference annotation method applied to the server provided by the present application includes the following steps S310 to S340.

[0091] Step S310: receiving a current conference interface sent by a first conference participant device.

[0092] Step S320: forwarding the current conference interface sent by the first conference participant device to any second conference participant device.

[0093] Step S330: receiving the first batch of registration data sent by the third participating device.

[0094] Step S340: forward the first batch of registration data to the first participating device.

[0095] In this embodiment, when the sharing mode is turned on, there is a situation where the user of the second conference participant device initiates an annotation behavior because he wants to add an annotation on the current conference interface. The second conference participant device on which the corresponding user initiates the annotation behavior on the current conference interface is recorded as the third conference participant device. Specifically, for a second conference participant device, when its user initiates the annotation behavior on the second conference participant device, the second conference participant device is the third conference participant device.

[0096] In one example, in a video conference, the server is in communication connection with conference device A, conference device B, and conference device C. Conference device A is the first conference device, conference device B and conference device C are the second conference devices, and when the user of conference device B initiates an annotation behavior on the conference interface of conference device B, conference device B becomes the third conference device.

[0097] Furthermore, the third participating device detects the user's annotation behavior and obtains the first batch of annotation data. The first batch of annotation data is used to describe the user's annotation behavior, including: annotation location, annotation trajectory, annotation color and other annotation attribute information. Furthermore, the third participating device sends the first batch of annotation data to the server. After receiving the first batch of annotation data sent by the third participating device, the server does not draw the first batch of annotation data, which is different from traditional video conferencing, but forwards the first batch of annotation data to the first participating device.

[0098] It should be noted that when the third participant device detects a user's annotation behavior, the annotation data detected within a preset time period is sent to the server as a first batch of annotation data. For example, when the user of the third participant device initiates an annotation behavior, the third participant device sends the annotation data detected every 10ms as a first batch of annotation data to the server when detecting the annotation behavior. That is to say, for one annotation behavior, there is at least one first batch of annotation data.

[0099] Corresponding to the above step S340, step S220 and step S230 are as follows.

[0100] Step S220: receiving the first batch of registration data sent by the third conference participant device and forwarded by the server.

[0101] Step S230, drawing the first batch of annotations in the current conference interface according to the first batch of annotation data to obtain an updated current conference interface.

[0102] In this embodiment, the first participating device parses the first batch of annotation data and draws the first batch of annotations in the current conference interface. At this time, the current conference interface is updated to include the first batch of annotations, and the user of the first participating device can view the annotations added by the user of the third participating device. Further, in combination with the above-mentioned step S210, when the next time to send the current conference interface displayed by the first participating device to the server is reached, the aforementioned updated current conference interface including the first batch of annotations is sent to the server. Further, in combination with the above-mentioned steps S310 and S320, the server forwards the aforementioned updated current conference interface including the first batch of annotations to any second participating device. At this time, after the second participating device displays the current conference interface forwarded by the server, the user can view the annotations added by the user of the third participating device through the second participating device.

[0103] In combination with the above content, it can be known that, in the case where the annotation behavior initiated by the user of the third participating device corresponds to multiple first batches of annotation data, the first participating device repeats the above steps S210 to S230, and the server repeats the above steps S310 to S340. Based on this, the user of the first participating device and the user of the second participating device can both view the video stream corresponding to the annotation behavior initiated by the user of the third participating device.

[0104] Based on the above content, it can be known that in the video conference annotation method provided by the present application, the first participating device centrally annotates and draws the first batch of annotation data corresponding to the annotation behavior initiated by the user of the third participating device on the third participating device. In this way, since the first participating device is a front-end device, it is possible to know whether the annotation drawing is wrong through the conference interface of the first participating device, which can reduce the complexity of troubleshooting. In addition, as a front-end device, the first participating device has better annotation drawing performance than the server. In this way, the annotation drawing speed can be increased by centrally performing annotation drawing through the first participating device, thereby increasing the annotation display speed of each participating device. In addition, no matter which user of the third participating device initiates the annotation behavior, the first participating device centrally performs annotation drawing, and all annotation drawings are concentrated on the current conference interface of the first participating device, which reduces part of the transmission and drawing process in traditional video conferencing, thereby further improving the annotation display speed of each participating device.

[0105] The present application provides a video conference annotation method, which is applied to a first participant device, including: when the sharing mode is turned on, periodically sending the current conference interface displayed by the first participant device to the server, so that the server forwards the current conference interface to any second participant device; receiving the first batch of annotation data sent by the third participant device and forwarded by the server; drawing the first batch of annotations in the current conference interface according to the first batch of annotation data to obtain an updated current conference interface; wherein the second participant device is a participant device other than the first participant device in the participant device, and the second participant device includes the third participant device. In this method, the first participant device centrally annotates and draws the first batch of annotation data corresponding to the annotation behavior initiated by the user of the third participant device on the third participant device. In this way, since the first participant device is a front-end device, it is possible to know whether the annotation drawing is wrong through the conference interface of the first participant device, which can reduce the complexity of troubleshooting. In addition, as a front-end device, the first participant device has better annotation drawing performance than the server, so that the annotation drawing speed can be improved by centrally performing annotation drawing through the first participant device, thereby improving the annotation display speed of each participant device. Furthermore, no matter which user of the third participating device initiates the annotation behavior, the first participating device will centrally perform the annotation and drawing, and all annotations and drawings will be concentrated on the current conference interface of the first participating device, reducing some of the transmission and drawing processes in traditional video conferencing, thereby further improving the annotation display speed of each participating device.

[0106] The present application provides a video conference annotation method, which is applied to a server, including: receiving a current conference interface sent by a first participant device; forwarding the current conference interface sent by the first participant device to any second participant device; receiving a first batch of annotation data sent by a third participant device; forwarding the first batch of annotation data to the first participant device; wherein the second participant device is a participant device other than the first participant device among the participant devices, and the second participant device includes the third participant device. In this method, the first participant device centrally annotates and draws the first batch of annotation data corresponding to the annotation behavior initiated by the user of the third participant device on the third participant device. In this way, since the first participant device is a front-end device, it is possible to know whether the annotation drawing is wrong through the conference interface of the first participant device, which can reduce the complexity of troubleshooting. In addition, as a front-end device, the first participant device has better annotation drawing performance than the server. In this way, centralized annotation drawing through the first participant device can increase the annotation drawing speed, thereby increasing the annotation display speed of each participant device. Furthermore, no matter which user of the third participating device initiates the annotation behavior, the first participating device will centrally perform the annotation and drawing, and all annotations and drawings will be concentrated on the current conference interface of the first participating device, reducing some of the transmission and drawing processes in traditional video conferencing, thereby further improving the annotation display speed of each participating device.

[0107] In one embodiment of the present application, when the server forwards the first batch of annotation data to the first conference participant device, it may also forward the device identification of the third conference participant device to the first conference participant device, so that the first conference participant device can determine which user of the second conference participant device added the first batch of annotations corresponding to the first batch of annotation data. In this regard, the above step S340 is specifically implemented by the following step S3400.

[0108] Step S3400: forwarding the first batch of registration data and the device identification of the third participating device to the first participating device.

[0109] In this embodiment, after receiving the first batch of annotation data sent by the third conference participant device, the server identifies the device identifier of the third conference participant device that sent the first batch of annotation data, and then forwards the first batch of annotation data and the device identifier of the third conference participant device to the first conference participant device at the same time.

[0110] Corresponding to the above step S3400, the above step S220 is specifically implemented through the following steps S2200 and S2201.

[0111] Step S2200: receiving the first batch of registration data sent by the third participant device and the device identification of the third participant device and forwarded by the server.

[0112] Step S2201: Add the first batch of registration data and the device identification of the corresponding third participant device to the first preset mapping relationship.

[0113] In this embodiment, a first preset mapping relationship is maintained in the first conference participant device, and a first batch of registration data and a corresponding device identifier of the third conference participant device are stored in the first preset mapping relationship.

[0114] In one embodiment of the present application, a user of any second conference participating device wants to modify the annotation added on the current conference interface. In this regard, the video conference annotation method applied to the server provided by the present application also includes the following steps S350 and S360.

[0115] Step S350: receiving a first batch of injection adjustment data sent by a fourth participant device, where the second participant device includes the fourth participant device.

[0116] In this embodiment, the fourth participating device is a participating device in which a user of the second participating device initiates an annotation adjustment behavior. The user of the second participating device initiates the annotation adjustment behavior, the second participating device is the fourth participating device, and the fourth participating device detects the annotation adjustment behavior initiated by the user to obtain the first batch of annotation adjustment data. Among them, the first batch of annotation adjustment data includes the first batch of annotation data of the adjusted first batch of annotations and the corresponding adjustment method, and the adjustment method can exemplarily include: at least one of deletion and modification. In the case where the adjustment method includes modification, the first batch of annotation adjustment data also includes the modification method. It can be understood that, such as the first batch of annotation data, one first batch of annotation adjustment behavior corresponds to at least one first batch of annotation adjustment data.

[0117] Step S360: forward the first batch of injection adjustment data sent by the fourth participant device and the device identifier of the fourth participant device to the first participant device.

[0118] In this embodiment, after receiving the first batch of registration adjustment data sent by the fourth conference participant device, the server identifies the device identification of the fourth conference participant device and then forwards the first batch of registration adjustment data sent by the fourth conference participant device and the device identification of the fourth conference participant device to the first conference participant device.

[0119] Regarding the above-mentioned steps S350 and S360, the video conference annotation method applied to the first participating device provided in the present application also includes the following steps S240 and S260.

[0120] Step S240: receiving the first batch of injection adjustment data and the device identification of the fourth participant device sent by the fourth participant device and forwarded by the server, wherein the second participant device includes the fourth participant device.

[0121] Step S250: determining whether the first batch of annotation data corresponding to the first batch of annotation adjustment data is sent by the fourth participant device to the first participant device according to the first batch of annotation adjustment data, the device identification of the fourth participant device and the first preset mapping relationship.

[0122] Step S260: If yes, adjust the current conference interface according to the first batch of registration adjustment data to obtain an updated current conference interface.

[0123] Corresponding to the above step S260, if no, the first batch of registration adjustment data is ignored and no processing is performed on the current conference interface.

[0124] In this embodiment, after receiving the first batch of annotation adjustment data and the device identification of the fourth participant device forwarded by the server and sent by the fourth participant device, the first participant device parses the first batch of annotation adjustment data to determine the first batch of annotation data corresponding to the first batch of annotation adjustment data; according to the first batch of annotation data corresponding to the first batch of annotation adjustment data, the device identification of the third participant device corresponding to the matching first batch of annotation data is searched from the first preset mapping relationship maintained above, so as to determine whether the device identification of the fourth participant device is consistent with the device identification of the third participant device found; if yes, it is determined that the first batch of annotation data corresponding to the first batch of annotation adjustment data sent by the fourth participant device is the annotation data corresponding to the annotation behavior initiated by the user of the fourth participant device in history. At this time, the first participant device adjusts the current conference interface according to the adjustment method included in the first batch of annotation adjustment data in the current conference interface to obtain the updated current conference interface. The user of the first participant device can view the adjustment of the first batch of annotations corresponding to the annotation line initiated by the user of the fourth participant device on the current display interface. Further, in combination with the above step S210, when the next time to send the current conference interface displayed by the first participating device to the server arrives, the above updated current conference interface is sent to the server. Further, in combination with the above steps S310 and S320, the server forwards the above updated current conference interface to any second participating device, and the second participating device displays the current conference interface sent by the server. At this time, each second participating device can view the specific adjustments made by the user of the fourth participating device to the first batch of annotations corresponding to the annotation lines initiated by itself in the past on the current display interface.

[0125] In combination with the above content, it can be known that, in the case where the annotation adjustment behavior initiated by the user of the fourth participant device corresponds to multiple first batches of annotation adjustment data, the first participant device repeats the above steps S240 to S260, and the server repeats the above steps S310 and S320. Based on this, the user of the first participant device and the user of the second participant device can both view the video stream corresponding to the annotation adjustment behavior initiated by the user of the fourth participant device.

[0126] Through the above content, it can be achieved that when the user of the second conference participant device initiates the annotation adjustment behavior, that is, becomes the user of the fourth conference participant device, he can adjust the annotations he has initiated in the past, that is, the annotations added when he became the user of the third conference participant device in the past, but cannot adjust the annotations drawn by other users of the third conference participant devices in the past. In other words, the user of the second conference participant device can only adjust the first batch of annotations corresponding to the annotation behavior initiated by himself, but cannot adjust the first batch of annotations corresponding to the annotation behavior initiated by users of other second conference participants.

[0127] In one embodiment of the present application, the video conference annotation method provided by the present application and applied to the first participating device also includes the following step S270.

[0128] Step S270: adding an identification mark to the annotations of the conference device corresponding to the same device identifier in the current conference interface, where the identification mark is used to distinguish different conference devices.

[0129] Based on the above step S270, after the above steps S210, S310 and S320, the annotations contained in the current conference interface displayed by each participating device carry an identification mark, so that the corresponding user can know which participant added the annotations contained in the current conference interface.

[0130] In one embodiment of the present application, the first conference participant device also has an annotation function as a conference participant device. In this regard, the video conference annotation method applied to the first conference participant device provided by the present application also includes the following steps S280 and S290.

[0131] Step S280, obtaining second annotation data.

[0132] Step S290: Draw a second annotation in the current conference interface according to the second annotation data to obtain an updated current conference interface.

[0133] In this embodiment, the user of the first participating device initiates an annotation behavior on the conference interface, and the first participating device detects the user's annotation behavior to obtain second annotation data. The difference between the second annotation data and the first annotation data is that the first annotation data is the annotation data corresponding to the annotation behavior initiated by the user of the third participating device, while the second annotation data is the annotation data corresponding to the annotation behavior initiated by the user of the first participating device.

[0134] Further, the first conference participant device draws a second annotation on the current conference interface according to the second annotation data to obtain an updated current conference interface. Further, after the above steps S210, S310 and S320, the current conference interface displayed by each conference participant device includes the second annotation.

[0135] In one embodiment of the present application, the video conference annotation method provided by the present application and applied to the first participating device also includes the following steps S2100 and S2110.

[0136] Step S2100: Obtain second annotation adjustment data of the first conference participant device for any annotation in the current conference interface.

[0137] Step S2110: adjust the current conference interface according to the second annotation adjustment data to obtain an updated current conference interface.

[0138] In this embodiment, the second annotation adjustment data is the annotation adjustment data corresponding to the annotation adjustment behavior initiated by the user of the first conference participant device. The second annotation adjustment data includes the annotation data of the adjusted annotation (the first annotation data or the second annotation data) and the corresponding adjustment method, and the adjustment method can exemplarily include at least one of deletion and modification. In the case where the adjustment method includes modification, the second annotation adjustment data also includes the modification method.

[0139] Based on the above steps S2100 and S2110, it can be achieved that the user of the first participating device has the authority to adjust any annotation on the current conference interface.

[0140] In one embodiment of the present application, in order to distinguish which annotations on the current conference interface are added by its own user, the third participant device draws the transparent first batch of annotations on the upper transparent layer (e.g., transparent mask) of the current conference interface according to the first batch of annotation data and generates corresponding annotation identifiers (e.g., annotation IDs), and records the first batch of annotation data and its corresponding unique annotation identifier. Furthermore, the third participant device sends the first batch of annotation data and the annotation identifier of the first batch of annotation data to the server, which is forwarded by the server to the first participant device. In this regard, the above step S340 is specifically implemented by the following step S3401.

[0141] Step S3401: forwarding the first batch of annotation data, the device identifier of the third participant device, and the annotation identifier corresponding to the first batch of annotation data to the first participant device.

[0142] In this embodiment, after receiving the first batch of annotation data and the annotation identifier corresponding to the first batch of annotation data sent by the third conference participant device, the server identifies the device identifier of the third conference participant device that sent the first batch of annotation data. Afterwards, the first batch of annotation data, the annotation identifier corresponding to the first batch of annotation data, and the device identifier of the third conference participant device are simultaneously forwarded to the first conference participant device.

[0143] Corresponding to the above step S3401, the above step S220 is specifically implemented through the following steps S2202 and S2203.

[0144] Step S2202: receiving the first batch of annotation data sent by the third conference participant device, the device identifier of the third conference participant device, and the annotation identifier of the first batch of annotation data, which are forwarded by the server.

[0145] Step S2203: Add the first batch of annotation data and the corresponding annotation identifier to the second preset mapping relationship corresponding to the device identifier of the third participating device.

[0146] In this embodiment, for any third conference participant device, when the third conference participant device sends the first batch of annotation data, the device identification of the third conference participant device, and the annotation identification of the first batch of annotation data to the first conference participant device via the server for the first time, the first conference participant device establishes a second preset mapping relationship corresponding to the device identification belonging to the third conference participant device, which reflects the corresponding relationship between the first batch of annotation data and the corresponding annotation identification. Further, the first batch of annotation data and the corresponding annotation identification are added to the second preset mapping relationship corresponding to the device identification of the third conference participant device.

[0147] When the third participating device sends the first batch of annotation data, the device identification of the third participating device and the annotation identification of the first batch of annotation data to the first participating device via the server not for the first time, the first participating device first searches for the corresponding second preset mapping relationship based on the device identification of the third participating device, and then adds the first batch of annotation data and the corresponding annotation identification to the aforementioned found second preset mapping relationship.

[0148] In one embodiment of the present application, with respect to the above-mentioned steps S3401, S2202 and S2203, there is a situation where the third participating device modifies the first batch of annotations added to itself in history. In this regard, the user of the third participating device initiates an annotation adjustment behavior. The third participating device detects the annotation adjustment behavior initiated by the user. If it is detected that the first batch of annotations corresponding to the aforementioned annotation adjustment behavior are not drawn on the transparent layer, it means that the first batch of annotations corresponding to the aforementioned annotation adjustment behavior are drawn by other third participating devices, and no response is made to the annotation adjustment behavior at this time. If it is detected that the first batch of annotations corresponding to the aforementioned annotation adjustment behavior are drawn on the transparent layer, the adjustment method corresponding to the annotation adjustment behavior is recorded as the third annotation adjustment data, and the corresponding first batch of annotations on the transparent layer are adjusted according to the third annotation adjustment data. Further, the annotation identifier corresponding to the first batch of annotations corresponding to the annotation adjustment behavior is identified. Further, the third annotation adjustment data and the annotation identifier of the first batch of annotations corresponding to the third annotation adjustment data are sent to the server to be forwarded by the server to the first participating device, and the first participating device updates the current conference interface. In this regard, the video conference annotation method applied to the server provided by the present application also includes the following steps S370 and S380.

[0149] Step S370: receiving third annotation adjustment data sent by the third conference participant device and an annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data.

[0150] Step S380: forward the third annotation adjustment data, the annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data, and the device identifier of the third conference participant device to the first conference participant device.

[0151] Corresponding to the above-mentioned steps S370 and S380, the video conference annotation method provided in the present application and applied to the first participating device also includes the following steps S2120 to S2150.

[0152] Step S2120: receiving the third annotation adjustment data sent by the third conference participant device, the device identifier of the third conference participant device, and the annotation identifier corresponding to the third annotation adjustment data, which are forwarded by the server.

[0153] Step S2130: Determine, from the second preset mapping relationship between the device identifier of the third conference participant device and the first batch of annotation data corresponding to the annotation identifier corresponding to the third annotation adjustment data.

[0154] In this embodiment, based on the above step S2130, the annotation mark corresponding to the third annotation adjustment data is used to locate which batch of annotations the third conference participant device has adjusted. This can avoid the problem that users of different third conference participants have added the same annotations in history, resulting in different third conference participants sending the same first batch of annotation data to the first conference participant device via the server, and the first conference participant device cannot distinguish the first batch of annotation data sent.

[0155] Step S2140: adjusting the current conference interface according to the third annotation adjustment data and the first batch of annotation data corresponding to the annotation mark corresponding to the third annotation adjustment data to obtain an updated current conference interface.

[0156] After the first batch of annotations adjusted by the third conference participant device is determined based on the above step S2130, the first batch of annotations is adjusted according to the adjustment method corresponding to the third annotation adjustment data to obtain an updated current conference interface.

[0157] In one example, when the adjustment mode corresponding to the third annotation adjustment data is deletion, the first batch of annotations added by the user of the third conference participant device is deleted based on the above step S2140.

[0158] Step S2140: updating the second preset mapping relationship between the device identifier of the third conference participant device and the second preset mapping relationship according to the third annotation adjustment data.

[0159] Through the above step S2140, the second preset mapping relationship maintained by the first conference participant device can be kept consistent with the annotation in the current conference interface.

[0160] In the case where the third annotation adjustment data is deleted, the device identifier of the third participating device is mapped to the second preset mapping relationship, and the third annotation adjustment data corresponding to the annotation identifier and the corresponding first batch of annotation data are deleted.

[0161] The present application also provides a video conference annotation device 400, which is applied to a first participant device, such as Figure 4 As shown, including:

[0162] The first sending module 410 is used to periodically send the current conference interface displayed by the first conference participant device to the server when the sharing mode is turned on, so that the server forwards the current conference interface to any second conference participant device;

[0163] The first receiving module 420 is used to receive the first batch of injection data sent by the third participating device and forwarded by the server;

[0164] A first drawing module 430 is used to draw the first batch of annotations in the current conference interface according to the first batch of annotation data to obtain an updated current conference interface;

[0165] The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

[0166] In one embodiment of the present application, the first receiving module 420 is specifically configured to:

[0167] receiving the first batch of injection data sent by the third participant device and the device identifier of the third participant device forwarded by the server;

[0168] The first batch of annotation data and the device identification of the corresponding third participant device are added to the first preset mapping relationship.

[0169] In one embodiment of the present application, a video conference annotation device 400 provided by the present application further includes:

[0170] a fourth receiving module, configured to receive the first batch of injection adjustment data sent by a fourth conference participant device and a device identifier of the fourth conference participant device and forwarded by the server, wherein the second conference participant device includes the fourth conference participant device;

[0171] A first determining module, configured to determine, according to the first batch of annotation adjustment data, the device identification of the fourth conference participant device, and the first preset mapping relationship, whether the first batch of annotation data corresponding to the first batch of annotation adjustment data is sent by the fourth conference participant device to the first conference participant device;

[0172] The second updating module is used to adjust the current conference interface according to the first batch of injection adjustment data to obtain an updated current conference interface when yes.

[0173] In one embodiment of the present application, a video conference annotation device 400 provided by the present application further includes:

[0174] The adding module is used to add an identification mark to the annotations of the conference participating devices corresponding to the same device identifier in the current conference interface, and the identification mark is used to distinguish different conference participating devices.

[0175] In one embodiment of the present application, a video conference annotation device 400 provided by the present application further includes:

[0176] A first acquisition module is used to acquire second annotation adjustment data of the first conference participant device for any annotation in the current conference interface;

[0177] The third updating module is used to adjust the current conference interface according to the second annotation adjustment data to obtain an updated current conference interface.

[0178] In one embodiment of the present application, a video conference annotation device 400 provided by the present application further includes:

[0179] A second acquisition module, used for acquiring second annotation data;

[0180] The fourth updating module is used to draw a second annotation in the current conference interface according to the second annotation data to obtain an updated current conference interface.

[0181] In one embodiment of the present application, the first receiving module 420 is specifically configured to:

[0182] receiving the first batch of annotation data sent by the third conference participant device, the device identifier of the third conference participant device, and the annotation identifier of the first batch of annotation data forwarded by the server;

[0183] The first batch of annotation data and the corresponding annotation identifier are added to the second preset mapping relationship corresponding to the device identifier of the third participating device.

[0184] In one embodiment of the present application, a video conference annotation device 400 provided by the present application further includes:

[0185] a sixth receiving module, configured to receive, by the server, third annotation adjustment data sent by the third conference participant device, a device identifier of the third conference participant device, and an annotation identifier corresponding to the third annotation adjustment data;

[0186] A second determining module is used to determine the first batch of annotation data corresponding to the annotation identifier corresponding to the third annotation adjustment data from the device identifier of the third conference participating device corresponding to the second preset mapping relationship;

[0187] A fifth updating module, configured to adjust the current conference interface according to the third annotation adjustment data and the first batch of annotation data corresponding to the annotation identifier corresponding to the third annotation adjustment data, to obtain an updated current conference interface;

[0188] The sixth updating module is used to update the second preset mapping relationship between the device identification of the third participating device and the second preset mapping relationship according to the third annotation adjustment data.

[0189] The present application also provides a video conference annotation device 500, which is applied to a server, such as Figure 5 As shown, including:

[0190] The second receiving module 510 is used to receive the current conference interface sent by the first participating device;

[0191] A first forwarding module 520, configured to forward the current conference interface sent by the first conference participant device to any second conference participant device;

[0192] The third receiving module 530 is used to receive the first batch of injection data sent by the third participating device;

[0193] A second forwarding module 540, configured to forward the first batch of injection data to a first conference participating device;

[0194] The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

[0195] In one embodiment of the present application, the first forwarding module 520 is specifically configured to:

[0196] The first batch of annotation data and the device identification of the third participating device are forwarded to the first participating device.

[0197] In one embodiment of the present application, the video conference annotation device 500 provided by the present application further includes:

[0198] a fifth receiving module, configured to receive a first batch of injection adjustment data sent by a fourth conference participant device, wherein the second conference participant device includes the fourth conference participant device;

[0199] The third forwarding module is used to forward the first batch of injection adjustment data sent by the fourth participant device and the device identification of the fourth participant device to the first participant device.

[0200] In one embodiment of the present application, the first forwarding module 520 is specifically configured to:

[0201] The first batch of annotation data, the device identification of the third conference participant device, and the annotation identification corresponding to the first batch of annotation data are forwarded to the first conference participant device.

[0202] In one embodiment of the present application, the video conference annotation device 500 provided by the present application further includes:

[0203] A seventh receiving module, configured to receive the third annotation adjustment data sent by the third conference participant device and the annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data;

[0204] The fourth forwarding module is used to forward the third annotation adjustment data, the annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data, and the device identifier of the third conference participant device to the first conference participant device.

[0205] The present application also provides an electronic device, the electronic device is a first conference participant device, and the electronic device includes any one of the above-mentioned video conference annotation devices 400 applied to the first conference participant device;

[0206] Alternatively, the electronic device is a server, and the electronic device includes any one of the above-mentioned video conference annotation devices 500 applied to the server;

[0207] Or, if Figure 6 As shown, the electronic device 600 is the server or the first participating device, including a memory 610 and a processor 620, the memory 610 is used to store computer instructions, and the processor 620 is used to call the computer instructions from the memory 610 to execute a method as described in any one of the above method embodiments.

[0208] The present application also provides a computer-readable storage medium having a computer program stored thereon, and the computer program, when executed by a processor, implements the method according to any one of the above method embodiments.

[0209] The present application may be a system, a method and / or a computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present application.

[0210] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media (a non-exhaustive list) include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium is not to be interpreted as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.

[0211] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.

[0212] The computer program instructions for performing the operation of the present application can be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. Computer-readable program instructions can be executed completely on a user's computer, partially on a user's computer, executed as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet). In some embodiments, by using the state information of a computer-readable program instruction to personalize an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA) or a programmable logic array (PLA), the electronic circuit can execute a computer-readable program instruction, thereby realizing various aspects of the present application.

[0213] Various aspects of the present application are described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0214] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0215] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0216] The flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a part of a module, program segment or instruction, and the part of the module, program segment or instruction contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart can be implemented by a dedicated hardware-based system that performs the specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions. It is well known to those skilled in the art that it is equivalent to implement it by hardware, implement it by software, and implement it by combining software and hardware.

[0217] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or technical improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the present application is defined by the appended claims.

Claims

1. A video conference annotation method, characterized in that: Applicable to the first participating device, including: When the sharing mode is turned on, the current conference interface displayed by the first conference participant device is periodically sent to the server, so that the server forwards the current conference interface to any second conference participant device; receiving a first batch of injection data sent by a third participant device and forwarded by the server; Drawing the first batch of annotations in the current conference interface according to the first batch of annotation data to obtain an updated current conference interface; The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

2. The method according to claim 1, characterized in that The receiving the first batch of registration data sent by the third conference participant device and forwarded by the server includes: receiving the first batch of injection data sent by the third participant device and the device identifier of the third participant device forwarded by the server; The first batch of annotation data and the device identification of the corresponding third participant device are added to the first preset mapping relationship.

3. The method according to claim 2, characterized in that The method further comprises: receiving a first batch of injection adjustment data and a device identifier of the fourth conference participant device sent by the fourth conference participant device and forwarded by the server, wherein the second conference participant device includes the fourth conference participant device; Determine, according to the first batch of annotation adjustment data, the device identifier of the fourth conference participant device, and the first preset mapping relationship, whether the first batch of annotation data corresponding to the first batch of annotation adjustment data is sent by the fourth conference participant device to the first conference participant device; If yes, the current conference interface is adjusted according to the first batch of injection adjustment data to obtain an updated current conference interface.

4. The method according to claim 2, characterized in that: The method further comprises: An identification mark is added to the annotations of the conference participating devices corresponding to the same device mark in the current conference interface, and the identification mark is used to distinguish different conference participating devices.

5. The method according to claim 1, characterized in that The method further comprises: Obtaining second annotation adjustment data of the first conference participant device for any annotation in the current conference interface; The current conference interface is adjusted according to the second annotation adjustment data to obtain an updated current conference interface.

6. The method according to claim 1, characterized in that The method further comprises: Get the second batch of annotation data; A second annotation is drawn in the current conference interface according to the second annotation data to obtain an updated current conference interface.

7. The method according to claim 1, characterized in that The receiving the first batch of registration data sent by the third conference participant device and forwarded by the server includes: receiving the first batch of annotation data sent by the third conference participant device, the device identifier of the third conference participant device, and the annotation identifier of the first batch of annotation data forwarded by the server; The first batch of annotation data and the corresponding annotation identifier are added to the second preset mapping relationship corresponding to the device identifier of the third participating device.

8. The method according to claim 7, characterized in that The method further comprises: receiving the third annotation adjustment data sent by the third conference participant device, the device identifier of the third conference participant device, and the annotation identifier corresponding to the third annotation adjustment data and forwarded by the server; Determine, from the second preset mapping relationship between the device identifier of the third conference participant device and the first batch of annotation data corresponding to the annotation identifier corresponding to the third annotation adjustment data; According to the third annotation adjustment data and the first batch of annotation data corresponding to the annotation identifier corresponding to the third annotation adjustment data, the current conference interface is adjusted to obtain an updated current conference interface; The device identification of the third conference participant device corresponds to the second preset mapping relationship according to the third annotation adjustment data.

9. A video conference annotation method, characterized in that: Applicable to servers, including: Receiving the current conference interface sent by the first participating device; Forwarding the current conference interface sent by the first conference participant device to any second conference participant device; Receive the first batch of injection data sent by the third participating device; Forwarding the first batch of injection data to the first participating device; The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

10. The method according to claim 9, characterized in that The forwarding of the first batch of injection data to the first conference participant device includes: The first batch of annotation data and the device identification of the third participating device are forwarded to the first participating device.

11. The method according to claim 10, characterized in that The method further comprises: receiving a first batch of injection adjustment data sent by a fourth participant device, wherein the second participant device includes the fourth participant device; The first batch of injection adjustment data sent by the fourth conference participant device and the device identification of the fourth conference participant device are forwarded to the first conference participant device.

12. The method according to claim 9, characterized in that The forwarding of the first batch of injection data to the first conference participant device includes: The first batch of annotation data, the device identification of the third conference participant device, and the annotation identification corresponding to the first batch of annotation data are forwarded to the first conference participant device.

13. The method according to claim 12, characterized in that The method further comprises: Receiving third annotation adjustment data sent by the third conference participant device and an annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data; The third annotation adjustment data, the annotation identifier of the first batch of annotation data corresponding to the third annotation adjustment data, and the device identifier of the third conference participant device are forwarded to the first conference participant device.

14. A video conference annotation device, characterized in that: Applicable to the first participating device, including: A first sending module, configured to periodically send the current conference interface displayed by the first conference participant device to the server when the sharing mode is turned on, so that the server forwards the current conference interface to any second conference participant device; A first receiving module, used for receiving the first batch of injection data sent by the third conference participant device and forwarded by the server; A first updating module, configured to draw the first batch of annotations in the current conference interface according to the first batch of annotation data, to obtain an updated current conference interface; The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

15. A video conference annotation device, characterized in that: Applicable to servers, including: A second receiving module is used to receive the current conference interface sent by the first participating device; A first forwarding module, used for forwarding the current conference interface sent by the first conference participant device to any second conference participant device; A third receiving module, used for receiving the first batch of injection data sent by the third participating device; A second forwarding module, used for forwarding the first batch of injection data to the first conference participating device; The second conference participant device is a conference participant device other than the first conference participant device, and the second conference participant device includes a third conference participant device.

16. An electronic device, characterized in that: The electronic device is a first conference participant device, and the electronic device includes the apparatus according to claim 14; or, The electronic device is a server, and the electronic device includes the device according to claim 15; Alternatively, the electronic device is the server or the first participating device, including a memory and a processor, the memory is used to store computer instructions, and the processor is used to call the computer instructions from the memory to execute the method as described in any one of claims 1-13.

17. A computer-readable storage medium, characterized in that: A computer program is stored thereon, which implements the method according to any one of claims 1 to 13 when executed by a processor.

Images