WO2020024495A1

WO2020024495A1 - Whiteboard operation method, device and system, whiteboard device and medium

Info

Publication number: WO2020024495A1
Application number: PCT/CN2018/118480
Authority: WO
Inventors: 张龙华
Original assignee: 广州视源电子科技股份有限公司; 广州视臻信息科技有限公司
Priority date: 2018-08-02
Filing date: 2018-11-30
Publication date: 2020-02-06
Also published as: CN109324745A; CN109324745B

Abstract

The present invention relates to a whiteboard operation method, device and system, a whiteboard device and a storage medium, which are applied to the field of whiteboard devices. The method comprises: detecting an operation event occurring at a first whiteboard; if a target of the operation event is a page element, applying for an element lock of the target element; and after applying for the element lock of the target element, displaying a result of an operation for the target element on the first whiteboard, wherein the target element is a page element towards which the operation event is directed, and the target element does not belong to currently operating page elements of an operation event of a second whiteboard. The first whiteboard and the second whiteboard belong to the same shared meeting, and pages displayed on the first whiteboard and the second whiteboard are the same, thereby being able to achieve the effect of a plurality of users simultaneously operating the whiteboard at multiple whiteboard terminals which participate in the shared meeting. The embodiments of the present invention solve the problem of low efficiency when multiple people operate a whiteboard in a shared meeting, and avoids operation conflicts when multiple people operate the whiteboard.

Description

Whiteboard operation method, device, system, whiteboard equipment and medium

Technical field

The present invention relates to the technical field of whiteboards, and in particular, to a method, a device, a system, a whiteboard device, and a storage medium for operating a whiteboard in a shared conference.

Background technique

The electronic whiteboard (referred to as whiteboard for short) is equivalent to a particularly large electronic writing board. Generally, a special whiteboard software is needed to support it. Users can use their fingers or a stylus to write and draw on the whiteboard display. The content written by the user is displayed, and the display content can be electronically erased. In addition, the whiteboard can also be network-connected to mobile phones, PCs, or other external devices and used in classroom teaching, live demonstrations, or remote conferences.

In the process of implementing the present invention, the inventors found that the prior art has the following problems. In a remote conference scenario, multiple whiteboards can synchronize content. When two or more users write on their whiteboards at the same time, there may be many People operate the same whiteboard element or the same whiteboard page at the same time, which leads to operation conflicts. In this regard, the general treatment method is: when a user (such as "Xiao Ming") writes on the whiteboard in the meeting, the current whiteboard page is locked, and other users cannot perform local whiteboards during "Xiao Ming" writing Content operations. Therefore, there is a problem that a whiteboard operation cannot be performed simultaneously in a multi-person conference.

Summary of the invention

Based on this, it is necessary to provide a method, a device, a system, a whiteboard device, and a storage medium for sharing a whiteboard operation in a conference for a problem that the whiteboard operation cannot be performed simultaneously in a multi-person conference in the existing manner.

According to a first aspect of the present invention, a method for operating a whiteboard in a shared conference is provided, including:

Detecting an operation event occurring on the first whiteboard;

If the target of the operation event is a page element, apply for an element lock of the target element;

After applying for the element lock of the target element, the operation result of the target element is displayed on the first whiteboard;

The target element is a page element targeted by the operation event, and the target element does not belong to a page element that is being operated by the operation event of the second whiteboard;

The first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed on the first whiteboard and the second whiteboard are the same.

In one of the embodiments, it further includes:

If the target of the operation event is a page, apply for a page lock of the target page;

After applying for the page lock of the target page, the operation result of the target page is displayed on the first whiteboard;

The target page is a page displayed by the first whiteboard when the operation event occurs, and the target page does not belong to a page that is being operated by the operation event of the second whiteboard.

In one embodiment, if the target of the operation event is a page element, applying for an element lock of the target element includes:

If the target of the operation event is a page element, sending an element lock application to the server of the shared conference;

The element lock application carries an element identifier of a target element;

The element lock application is used to trigger the server to query whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier, and if it does not belong, assign the element lock of the target element to the first whiteboard.

In one embodiment, the sending an element lock application to the server of the shared conference includes:

Determining an event type of the operation event;

If it is an event type for adding an element, generate an element identifier of the target element, and send an element lock application to the server;

If it is an event type of modifying an element or deleting an element, obtain the element identifier of the target element, and send an element lock application to the server.

In one embodiment, the assigning the element lock of the target element to the first whiteboard further includes:

Sending a message that the element lock application of the target element is successful to the first whiteboard;

and / or,

The element lock of the target element is set to an allocated state.

In one embodiment, the element lock application also carries a conference code of the shared conference;

The element lock application is also used to trigger the server to save the element lock allocation information of the target element corresponding to the conference code.

In one of the embodiments, it further includes:

When the operation event corresponding to the target element ends, sending an element unlocking application to the server;

The element unlock application is used to trigger the server to set the element lock of the target element to an unassigned state.

In one embodiment, when the target of the operation event is a whiteboard page, the method further includes:

Send a page lock request for the target page to the server;

The page lock application carries a page identifier of a target page;

The page lock application is used to trigger the server to query whether the target page belongs to the page that is being operated by the operation event of the second whiteboard according to the page identifier, and if it does not belong, assign the page lock of the target page to the first whiteboard.

In one embodiment, after the page lock of the target page is allocated to the first whiteboard, the method further includes:

Sending a message that the page lock application of the target page is successful to the first whiteboard;

and / or,

The page lock of the target page is set to an allocated state.

In one embodiment, the page lock application further carries a conference code of the shared conference;

The page lock application is also used to trigger the server to save page lock allocation information of a target page corresponding to the conference code.

In one of the embodiments, it further includes:

When the operation event corresponding to the target page ends, sending a page unlock application to the server;

The page unlock application is used to trigger the server to set the page lock of the target page to an unallocated state.

In one of the embodiments, it further includes:

Synchronize operation results generated by the operation events displayed in the first whiteboard to the second whiteboard.

In one embodiment, the step of synchronizing the operation result generated by the operation event displayed on the first whiteboard to the second whiteboard includes:

Acquiring the changed whiteboard content in the first whiteboard; the changed whiteboard content is generated by the operation event;

Sending content data corresponding to the changed whiteboard content to a server, so that the second whiteboard obtains the content data through the server, so that the whiteboard content of the second whiteboard changes similarly;

or,

Obtaining screenshot information of the first whiteboard;

Sending the screenshot information to the server, so that the second whiteboard obtains the screenshot information through the server, so that the second whiteboard displays the screenshot information.

In one embodiment, the operation result generated by the operation event includes one or more of the following:

Page elements increase, page elements decrease, page element position changes, page element form changes, page movement, page zoom, page turning.

In one embodiment, the element includes at least one of a handwriting and an image displayed on a whiteboard page.

In one embodiment, the target element does not belong to a page element that is being operated by an operation event of the second whiteboard, including: the page lock of the page where the target element is located, and the element lock of the target element are not assigned to the second whiteboard;

The target page does not belong to the page being operated by the operation event of the second whiteboard, and includes: the page lock of the target page and the element lock of each element in the target page are not allocated to the second whiteboard.

According to a second aspect of the present invention, a method for sharing a whiteboard operation in a sharing conference is provided, including:

Receiving an element lock application sent by the first whiteboard; the element lock application is issued when a whiteboard operation event occurs on the first whiteboard in a sharing conference, and the target of the operation event is a page element; the element lock application is in progress An element identifier carrying a target element; the target element is a page element targeted by the operation event;

Querying whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier; if not, assigning an element lock of the target element to the first whiteboard;

In one of the embodiments, it further includes:

Receiving a page lock application sent by the first whiteboard; the page lock application is issued when a whiteboard operation event occurs on the first whiteboard and the target of the operation event is a whiteboard page; the page lock application carries the page lock application A page identifier of a target page; the target page is a page displayed by the first whiteboard when the operation event occurs;

Querying whether the target page belongs to the page being operated by the operation event of the second whiteboard according to the page identifier, and if it does not, assign a page lock of the target page to the first whiteboard;

A message that the page lock application of the target page is successful is sent to the first whiteboard.

The element lock of the target element is set to an allocated state.

In one embodiment, the step of setting the element lock of the target element to an allocated state further includes:

Receiving an element unlocking application sent by the first whiteboard; the element unlocking application is issued when an operation event corresponding to the target element on the first whiteboard ends; the element unlocking application carries an element identifier of the target element;

The element lock of the target element is set to an unassigned state according to the element identification.

In one embodiment, the querying whether the target element belongs to a page element that is being operated by the operation event of the second whiteboard according to the element identification, and further includes:

If it belongs, a message that the element lock application of the target element fails is sent to the first whiteboard, and the message is used to shield the operation event of the first whiteboard.

In one of the embodiments, the assigning the page lock of the target page to the first whiteboard further includes:

The page lock of the target page is set to an allocation state.

In one embodiment, the step of setting the page lock of the target page to an allocated state further includes:

Receiving a page unlock application sent by the first whiteboard; the page unlock application is issued when an operation event corresponding to the target page on the first whiteboard ends; the page unlock application carries a page identifier of the target page;

The page lock of the target page is set to an unallocated state according to the page identifier.

In one embodiment, the querying whether the target page belongs to a page that is being operated by the operation event of the second whiteboard according to the page identifier, and further includes:

If it does not, send a message to the first whiteboard that the page lock application of the target page has failed, and the message is used to shield the operation event of the first whiteboard.

According to a third aspect of the present invention, a method for operating a whiteboard in a shared conference is provided, including:

The first whiteboard detects an operation event of the whiteboard, and if the target of the operation event is a page element, an element lock application is sent to the server to apply for an element lock of the target element; the element lock application carries an element identifier of the target element The target element is a page element targeted by the operation event;

The server receives the element lock application, and inquires whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier; if it does not, assigns the element lock of the target element to the first whiteboard, and The first whiteboard sends a message that the element lock application of the target element is successful;

The first whiteboard receives the message that the element lock application is successful, and displays the operation result of the target element on the first whiteboard;

In one of the embodiments, it further includes:

The server inquires, according to the element identifier, that the target element belongs to a page element that is being operated by an operation event of the second whiteboard, and sends a message that the element lock application of the target element fails to the first whiteboard;

The first whiteboard receives the message that the element lock application fails, and shields the operation event.

According to a fourth aspect of the present invention, a whiteboard operating device in a sharing conference is provided, including:

An event detection module, configured to detect an operation event occurring on the first whiteboard;

An element lock application module, configured to apply for an element lock of a target element if the target of the operation event is a page element;

An element operation module, configured to display the operation result of the target element on the first whiteboard after applying for the element lock of the target element;

In one of the embodiments, it further includes:

A page lock application module, configured to apply for a page lock of a target page if the target of the operation event is a page;

A page operation module, configured to display the operation result of the target page on the first whiteboard after applying for a page lock of the target page;

In one embodiment, the element lock application module includes:

An element lock application unit, configured to send an element lock application to the server of the shared conference if the target of the operation event is a page element;

The element lock application carries an element identifier of a target element;

In one of the embodiments, it further includes:

An element lock release module, configured to send an element unlocking application to a server when an operation event corresponding to the target element ends;

According to a fifth aspect of the present invention, a device for sharing a whiteboard operation in a conference is provided, including:

A lock application receiving module is configured to receive an element lock application sent by a first whiteboard; the element lock application is issued when a whiteboard operation event occurs on the first whiteboard in a sharing meeting, and the operation event is targeted for a page element The element lock application carries an element identifier of a target element; the target element is a page element targeted by the operation event;

A lock allocation module, configured to query whether the target element belongs to a page element being operated by an operation event of the second whiteboard according to the element identifier; if not, assign an element lock of the target element to the first whiteboard;

A lock feedback module, configured to send a message that the element lock application of the target element is successful to the first whiteboard;

In one embodiment, the lock application receiving module is further configured to receive a page lock application sent by the first whiteboard; the page lock application is a whiteboard operation event occurring on the first whiteboard, and a target of the operation event is Issued in the case of a whiteboard page; the page lock application carries a page identifier of the target page; the target page is a page displayed by the first whiteboard when the operation event occurs;

The lock allocation module is further configured to query whether the target page belongs to a page that is being operated by the operation event of the second whiteboard according to the page identifier, and if it does not belong, allocate a page lock of the target page to the first whiteboard;

The lock feedback module is further configured to send a message that the page lock application of the target page is successful to the first whiteboard.

According to a sixth aspect of the present invention, a whiteboard operating system in a shared conference is provided, including: a first whiteboard and a server;

The first whiteboard includes:

An event detection module for detecting an operation event of the whiteboard;

An element lock application module, configured to send an element lock application to the server if the target of the operation event is a page element; the element lock application carries an element identifier of the target element, and the target element is the target of the operation event. Page elements

And, an element operation module is configured to display the operation result of the target element on the first whiteboard after receiving the message that the element lock application is successful;

The server includes:

A lock application receiving module, configured to receive an element lock application sent by the first whiteboard;

And, a lock feedback module is configured to send a message that the element lock application of the target element is successful to the first whiteboard;

According to a seventh aspect of the present invention, there is provided a whiteboard device including a memory, a display screen having a touch function, and a processor, wherein the memory stores a computer program;

When the computer program is executed by the processor, the processor is caused to implement the following steps:

Detecting an operation event occurring on the first whiteboard;

According to an eighth aspect of the present invention, there is provided a server including a memory and a processor, and the memory stores a computer program;

Querying whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identification; if not, assigning the element lock of the target element to the first whiteboard;

According to a ninth aspect of the present invention, a computer storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the method for operating a whiteboard according to any one of the foregoing method embodiments is implemented.

Implementing the embodiment provided by the present invention, in a state where the whiteboard is participating in a sharing conference, if a whiteboard operation event occurs and the target of the operation event is a page element, and the element is not currently operated by other users on the whiteboard side, the element is obtained The element lock exclusively holds the operation right of the element, that is, the local whiteboard supports the operation event and displays the operation result of the element. At the same time, other users on the whiteboard side are prohibited from operating the element during this period. The effect of multiple users operating on different elements in the whiteboard at the same time, effectively avoiding conflicts.

Further, through some of these embodiments, when a whiteboard user wants to perform whiteboard page operations such as page turning and page movement, if the page is not operated by another whiteboard user, it can also be exclusive by applying for a page lock. The operation permissions of this page prevent other whiteboard users from performing operations on this page or element operations on this page during this period to avoid conflicts.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system architecture diagram applicable to a method for operating a whiteboard in an embodiment; FIG.

2 is a schematic flowchart of a method for implementing a whiteboard operation using a first whiteboard terminal as an example in an embodiment;

3 is a schematic diagram of page elements and pages in an embodiment;

4 is a schematic flowchart of a method for implementing a whiteboard operation using a first whiteboard terminal as an example in another embodiment;

5 is a schematic flowchart of a method for implementing a whiteboard operation using a shared conference system as an example in an embodiment;

6A is a schematic interaction diagram of an operation event for a page element in a sharing conference according to an embodiment;

FIG. 6B is a schematic diagram of an interaction result of an operation event for a page element in a sharing conference according to the embodiment of FIG. 6A; FIG.

7 is a schematic flowchart of a method for implementing a whiteboard operation using a shared conference system as an example in another embodiment;

8 is a schematic interaction diagram of an operation event for a page in a sharing conference according to an embodiment;

9 is a schematic flowchart of a method for implementing a whiteboard operation using a server as an example in an embodiment;

10 is a schematic flowchart of a method for implementing a whiteboard operation using a server as an example in another embodiment;

11 is a schematic structural diagram of a whiteboard operating device according to an embodiment;

FIG. 12 is a schematic structural diagram of a whiteboard operating device according to another embodiment; FIG.

13 is an internal structure diagram of an interactive smart tablet according to an embodiment;

FIG. 14 is an internal structure diagram of a server in an embodiment.

detailed description

In order to make the objectives, technical solutions, and advantages of the present invention clearer, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

Reference to "an embodiment" herein means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they independent or alternative embodiments that are mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

The method for operating a whiteboard in a shared conference provided in this application can be applied to the system architecture shown in FIG. 1; wherein the whiteboard device 102 communicates with one or more other whiteboard devices 102 through the server 104. The whiteboard device 102 may be an interactive smart tablet, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, a game console, a wearable device, a smart locomotive, Self-driving cars, smart home devices, or a combination of any of these devices. The whiteboard device 102 can be installed with various applications required by the user, such as writing applications, presentation applications, instant messaging applications, image editing applications, social applications, e-commerce applications, Search applications, browser applications, and more. Among them, writing applications such as electronic whiteboards and electronic blackboards, presentation applications such as wireless projection applications, and instant messaging applications such as video conference applications.

In some embodiments, when multiple whiteboard devices 102 are on the same local area network, the whiteboard device 102 may also directly communicate with and connect with other whiteboard devices 102 and use one of the multiple whiteboard devices 102 as a server; in this embodiment There is no need to set up a dedicated server.

It should be noted that the server mentioned in the following embodiments may be a dedicated server or a whiteboard device serving as a server role, which is determined according to a specific application scenario. Among them, the dedicated server can be set on the public network or the local area network.

In some embodiments, the whiteboard device 102 is described by taking an interactive smart tablet as an example. The interactive smart tablet may be an integrated device that uses touch technology to control the content displayed on the display tablet and implement human-computer interactive operations. It integrates one or more functions such as whiteboard function, projector, curtain, audio, TV and video conference terminal. The interactive smart flat screen is a touch screen, and the touch screen may include a capacitive screen, an electromagnetic screen, or an infrared screen. Generally speaking, the touch screen can receive a touch operation input by a user through a finger or an input device. Input devices include, but are not limited to: capacitive pens, electromagnetic pens, and / or infrared pens. The interactive smart tablet may establish a data connection with at least one other interactive smart tablet through a network. The communication method of the data connection is not limited in the embodiment, and may be a communication method such as a USB connection, the Internet, a local area network, Bluetooth, Wi-Fi, or a ZigBee protocol. Whiteboard applications installed in each interactive smart tablet are used to implement related functions of the whiteboard in the interactive smart tablet. Whiteboard-related functions include, but are not limited to, human-computer interaction such as writing, drawing, erasing, and moving.

In one embodiment, as shown in FIG. 2, a method for operating a whiteboard in a sharing conference is provided. The method is applied to an interactive smart tablet participating in a sharing conference as an example, and includes the following steps:

S110. An operation event occurring on the first whiteboard is detected.

The first whiteboard can be understood as a whiteboard application installed in any interactive smart tablet participating in a shared meeting; it can also be understood as any interactive smart tablet itself participating in a shared meeting, and the interactive smart tablet is in a whiteboard mode.

In an embodiment, the page of the first whiteboard may include a writing area and a toolbar, and the toolbar contains whiteboard-related controls such as one of a pen, an eraser, a font, a color, and a plus / minus page control, or For a plurality of pages of the first whiteboard, refer to FIG. 3. The user can write in the writing area with a finger or a stylus pen. Correspondingly, the handwriting or added image of the user will be displayed in the writing area.

The state of the first whiteboard participating in the sharing meeting can be understood as the state in which the first whiteboard establishes a communication connection with at least one other whiteboard and shares the content of the whiteboard. Operation events that occur on the first whiteboard include, but are not limited to, events such as adding page elements (such as writing handwriting), deleting elements, erasing elements, adjusting element shape, moving elements, zooming pages, adding pages, subtracting pages, moving pages, and the like.

The second whiteboard is similar to the first whiteboard described above. It can also be understood as a whiteboard application installed in any interactive smart tablet in a shared meeting, or it can be any interactive smart tablet itself in a shared meeting. In whiteboard mode.

In an embodiment, the first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed by the first whiteboard and the second whiteboard are the same.

S120: If the target of the operation event is a page element, apply for an element lock of the target element;

The target element is a page element targeted by the current operation event.

With continued reference to FIG. 3, the entire whiteboard writing area can be understood as a whiteboard page, and the handwriting, images, etc. displayed in the writing area can be understood as page elements; where the handwriting can be a text handwriting, a symbol, or any other handwriting. The target of an operation event is a page element, which means that the object that the user wants to operate is a part of the page, but not the page itself. For example, when a user writes on a whiteboard, the target of the writing event is a new handwriting on the page. The corresponding target is a page element; when the user deletes the original graphic on the whiteboard page, the target of the deletion event is the graphic handwriting on the page, so the corresponding target is the page element; when the user moves the graphic in the page, the target of the operation event is moved It is a graphic on a page, so its corresponding target is a page element. When a user zooms in a graphic on a page, the target of the zoom-in operation event is a graphic on the page, so its corresponding target is a page element. When the user drags the page, the drag The target of a manipulation event is a page, so its corresponding target is a page.

S130. After applying for the element lock of the target element, displaying the operation result of the target element on the first whiteboard.

It should be noted that, only when the target element does not belong to a page element that is being operated by the operation event of the second whiteboard, an element lock of the target element can be applied for.

The element lock of an element can be understood as the exclusive operation right of the element. In the embodiment of the present invention, the element lock of each page element at the same time can only be assigned to a whiteboard user in a sharing meeting, for example, during participation Element 1 and Element 2 are displayed on the first whiteboard and the first whiteboard of the same sharing meeting. If the current user of the first whiteboard applies for the element lock of element 1, the element lock of element 1 is used. Cannot perform any operation on element 1; if the element lock of element 2 is not assigned at this time, the second whiteboard user has the opportunity to obtain the element lock of element 2 and, if it is successful, the second whiteboard user can access the element 2 operation, at this time the first whiteboard user cannot perform any operation on element 2; thus, the effect that multiple users corresponding to the first whiteboard and the second whiteboard can operate on different page elements at the same time; Waiting for other users to finish the operation before starting element writing, which improves the operation efficiency and helps to improve the effect of sharing meetings.

In an embodiment, the target element does not belong to the page element being operated by the operation event of the second whiteboard, including: the page lock of the page where the target element is located, and the element lock of the target element are not assigned to the second whiteboard. That is, the target element is not currently operated by other whiteboard users to avoid operation conflicts.

In an embodiment, the operation result generated by the operation event in step S130 includes one or more of the following: page elements increase, page elements decrease, page element position changes, and page element form changes.

In addition, under the above-mentioned element lock mechanism, a page lock mechanism is also provided. Correspondingly, referring to FIG. 4, in an embodiment, the method for operating a whiteboard in a shared conference may further include steps:

S140. If the target of the operation event is a page, apply for a page lock of the target page; the target page is the page displayed by the first whiteboard when the operation event occurs.

S150. After applying for a page lock of the target page, displaying the operation result of the target page on the first whiteboard.

It should be noted that the page lock of the target page can only be applied for if the target page does not belong to the page being operated by the operation event of the second whiteboard.

Among them, the page lock of a page can be understood as the exclusive operation right for the page. Compared with the element lock of the above elements, the page lock of the page has a larger granularity. The specific differences include: When any whiteboard user in a sharing meeting applies for an element lock of an element, other whiteboard users can also Operations on elements other than elements; however, when any whiteboard user in a sharing meeting gets a page lock on a page, other whiteboard users will not be allowed to perform any operations on that page and operations on elements on that page. That is, when the page lock of the page is assigned, only one user can operate the page in the shared meeting, and does not support multiple people to perform whiteboard operations at the same time.

In an embodiment, the target page does not belong to the page that is being operated by the operation event of the second whiteboard, including: the page lock of the target page and the element lock of each element in the target page are not assigned to the second whiteboard. That is, the target page is not currently operated by other whiteboard users to avoid operation conflicts.

In one embodiment, the operation result generated by the operation event in step 150 includes one or more of the following: page movement, page zoom, and page turning.

By setting element locks and page locks separately, different granularities can be locked for different whiteboard operation events. On the one hand, it is convenient for multiple people to perform whiteboard operations in a sharing meeting at the same time, and on the other hand, it is possible to avoid operation conflicts between each other.

Further, in order to ensure the effect of the shared conference, in some embodiments, the method for operating a whiteboard in a shared conference further includes steps:

After applying the element lock of the target element on the first whiteboard side, or after obtaining the page lock of the target page on the first whiteboard side, the operation result generated by the operation event displayed on the first whiteboard is synchronized to the first one participating in the same sharing conference. Two whiteboards, thereby synchronizing the display contents of whiteboards participating in the same shared meeting.

Referring to the above, the operation result generated by the operation event in this step may include one or more of the following: page element increase, page element decrease, page element position change, page element form change, page movement, page zoom, and page turning.

It should be noted that the second whiteboard and the first whiteboard cannot be whiteboard applications installed in the same interactive smart tablet, nor can they be the same interactive smart tablet in whiteboard mode.

In some embodiments, a method for achieving content synchronization between whiteboards in a shared meeting is, for example: obtaining the changed whiteboard content in the first whiteboard; the changed whiteboard content is generated by the operation event; and the changed whiteboard content is sent to the server. Content data, so that the second whiteboard acquires the content data through the server, so that the whiteboard content of the second whiteboard changes similarly. Since the first whiteboard and the second whiteboard only need to send and acquire related information of the changed whiteboard content, the data transmission and reception volume of the first whiteboard and the second whiteboard is reduced, which is beneficial to ensuring the display content of the first and second whiteboards. Time synchronization.

Specifically, for operation events for whiteboard page elements, the content synchronization between whiteboards in the sharing meeting is, for example: (1) the page content of the first whiteboard and the second whiteboard are the same (both empty or both have the same page content), Then detect the increase of page elements on the first whiteboard, acquire the added page element data, and send it to the second whiteboard. The second whiteboard further displays the added page elements on the first whiteboard based on the original page content; 2) The page content of the first whiteboard and the second whiteboard are the same, and then the page elements of the first whiteboard are detected to be reduced, and the reduced element data is obtained and sent to the second whiteboard. The second whiteboard is based on the original page content. Reduce the same page elements; (3) The page content of the first whiteboard and the second whiteboard are the same, and then detect that the position of an element in the first whiteboard moves, obtain the movement information of the element, and send it to the second whiteboard. Based on the original content, the whiteboard also moves the corresponding elements.

Specifically, for an operation event for an element, content synchronization between whiteboards in a sharing meeting is, for example: (1) the page content of the first whiteboard and the second whiteboard are the same, and then the page movement of the first whiteboard is detected to obtain the movement information of the page , Send it to the second whiteboard, and the second whiteboard moves the local page proportionally; (2) the page content of the first whiteboard and the second whiteboard are the same, and then the page zoom change of the first whiteboard is detected to obtain the page zoom Change the information and send it to the second whiteboard. The second whiteboard scales the local pages in equal proportions. (3) The page content of the first whiteboard and the second whiteboard are the same, and then the page turning of the first whiteboard is detected. To obtain the page turning information and send it to the second whiteboard, which performs the same page turning on the basis of the original page.

It can be understood that the above scenario is only a partial example of content synchronization between whiteboards in a shared conference, and should not be interpreted as a limited explanation of content synchronization between whiteboards in a shared conference.

In addition, during the realization of content synchronization between whiteboards in a shared meeting, the whiteboard main program can be used to detect changes in the whiteboard content on the first whiteboard. For example, the user has performed a writing operation in the writing area, or the user has written the original content. After the erasing operation, the main program of the whiteboard can detect that the content of the whiteboard on the first whiteboard has changed. The main program of the whiteboard can obtain the content data corresponding to the changed whiteboard content on the first whiteboard, deliver the content data to a preset software module, and the software module packages and sends the content data to the second whiteboard. The software module analyzes the content data and restores the content data that can be recognized by the second whiteboard main program. The second whiteboard main program can control the same changes in the whiteboard content displayed on the second whiteboard.

In some embodiments, the method for achieving content synchronization between whiteboards in a shared conference may also be: obtaining screenshot information of the first whiteboard, and sending the screenshot information to a server, so that the second whiteboard obtains the screenshot information through the server , So that the second whiteboard displays the screenshot information.

Specifically, for example, after detecting that the first whiteboard applies to obtain the element lock of the target element or the page lock of the target page, the screenshot information of the first whiteboard is obtained at a set interval, and the screenshot information includes all the information of the current page of the first whiteboard. , Sending the screenshot information to the server, thereby achieving synchronization of the display content between the first whiteboard and the second whiteboard.

According to the whiteboard operation method of the above embodiment, when multiple whiteboards participate in a shared conference together, the page content changes caused by the operation event of multiple people or one person on any whiteboard can be displayed synchronously on other whiteboards. For example, a local participant wrote a piece of text on the local whiteboard, and a remote participant wrote another piece of text on the remote whiteboard. The two ends of the text can be seen on the local whiteboard and the remote whiteboard, which solves the original shared meeting. The problem that multiple whiteboards do not support writing by multiple people at the same time point further improves the meeting effect.

Further, in the embodiment, in order to increase the participation of the conference user, the element lock of the target element or the page lock of the target page is not exclusive to a certain whiteboard user. When the whiteboard enjoying the element lock of the target element or the page lock of the target page When the corresponding operation event of the user ends, the element lock of the target element or the page lock of the target page will be actively released. Correspondingly, referring to FIG. 4 continuously, in one embodiment, the method for operating a whiteboard in a sharing conference may further include steps:

S160. When it is detected that the operation event corresponding to the target element ends, an element unlocking application is sent to the server.

The element unlocking application may carry an element identifier of the target element; the element unlocking application may trigger the server to reset the element lock of the target element to an unassigned state. After the element lock of the element is set to unassigned, any whiteboard user in the sharing meeting can apply for the element lock of the element.

S170. When it is detected that the operation event corresponding to the target page ends, send a page unlock application to the server.

Wherein, the page identification of the target page may be carried in the page unlocking application. Due to the exclusivity of the page lock of the page, the identification information of the first whiteboard may also be carried in the page unlocking application. The page unlock request triggers the server to reset the page lock of the target page to an unallocated state. After the page lock of the page is set to unassigned, any whiteboard user in the sharing meeting can apply for a page lock of the page.

In some examples, based on the whiteboard operation habits of ordinary users, when it is detected that the user ’s finger or stylus corresponding to an operation event leaves the whiteboard, or leaves the whiteboard for a set period of time, the operation event may be determined to be over. For example, for an operation event written on a whiteboard, when it is detected that the user ’s finger or the writing pen leaves the whiteboard for 1 second, the writing operation event may be determined to be over; for an operation event during zooming a whiteboard page, the user ’s finger is detected to be away For a whiteboard, it can be determined that the zoom operation event has ended.

By timely releasing the page lock of the page or the element lock of the element, it is convenient for multiple users who share the meeting to participate in the operation of the whiteboard, while avoiding operation conflicts with each other.

It should be noted that, in the embodiment, the first white board and the second white board are only used to distinguish objects, and should not be understood as limiting the identity of the object. For example, the first white board and the second white board may also exchange identities with each other. It can solve the problem that multiple whiteboards in the original shared meeting do not support writing by multiple people at the same time.

In addition, the above embodiment mainly introduces the operation method of the whiteboard in the sharing conference from the perspective of the first whiteboard. The second whiteboard corresponding to the first whiteboard may be one or multiple second whiteboards, and participate in the same shared meeting together. .

In addition, when the first whiteboard itself is used as a server for sharing a conference, the message interaction between the first whiteboard and the server in the foregoing embodiment may be correspondingly adjusted to be processed locally on the first whiteboard without sending and receiving related information through the network.

Further, based on the above embodiment, the local whiteboard, server, and remote whiteboard are used as examples to illustrate the implementation process of the whiteboard operation method in a shared conference from the perspective of multi-sided interaction. Among them, the local whiteboard and the remote whiteboard can be interactive smart tablets, and a whiteboard application is installed in the interactive smart tablet, and the whiteboard application is in a front-end running state. In this scenario, the following describes the method of operating the whiteboard in a shared conference through two examples in conjunction with FIG. 5 and FIG. 7.

Example 1: Page element operation event

L1, a writing event is detected on the local whiteboard side (the writing element S0 is taken as an example below).

L2. Generate an element identifier of the target element S0, and send a lock application for the element S0 to the server.

The element identifier may be an element ID. In the same whiteboard page, the ID of each element is unique.

It should be noted that for a handwriting, the whiteboard can be erased on the whiteboard with a line eraser. A point eraser is to erase some of the points, and a line eraser is to delete the entire line directly. The point-erasing method may cause a handwriting to be divided into multiple sub-segments. In some embodiments, for each sub-segment, it can be used as a new element respectively to generate a corresponding element identifier.

The element lock application can carry the element identifier of the target element S0; through the element lock application, the server can be triggered to query whether the element lock of the target element S0 is allocated based on the element identifier. If not, the element lock of the target element S0 is allocated to A local whiteboard, and sending a message that the operation lock application of the target element SO is successful to the local whiteboard.

In some embodiments, the element lock application also needs to carry the page identifier of the target page; the element lock application can trigger the server to first query whether the page lock of the target page is allocated based on the page identifier, and if not, further query Whether the element lock of the target element in the target page is allocated. This can not only accurately distinguish the element locks of elements in different pages, but also check whether the page where the target element is located is being operated by other users.

L3, on the server side, receives the element lock application for element S0 sent by the local whiteboard.

L4: Query whether the page lock of the page where the target element S0 is located and the element lock of the target element S0 are allocated according to the element identification carried in the element lock application. If both are not, assign the element lock of the target element S0 to the local whiteboard.

In some embodiments, the element lock application sent by the whiteboard may also carry the conference code of the shared conference; by using such an element lock application, the server may also be triggered to save the element lock allocation information of the element corresponding to the conference code. That is, when there are multiple whiteboard users performing element operations at the same time, the element lock allocation information of multiple elements corresponding to the conference code can be saved on the server at the same time.

L5: Send a message that the operation lock application of the target element S0 is successful to the local whiteboard.

In this embodiment, since the element S0 for the writing operation is a page element that needs to be added, if the current page is not locked, the element lock corresponding to the newly added element must belong to the unallocated state, so the local whiteboard can Apply element lock to element S0.

In some embodiments, after receiving the element lock of the target element, the server first queries whether the page lock of the target element's page is allocated, and if not, then queries whether the element lock of the target element is allocated, only the page of the page where the target element is located When neither the lock nor the element lock of the target element is allocated, the element lock of the target element is allocated to the local whiteboard that initiated the application. That is, if a user is currently performing a page operation, the page is in an exclusive state, and the user is not allowed to perform any element operation on the page.

L6. On the side of the local whiteboard, if a message that the element lock application of the target element S0 is successfully sent is received by the server, the current operation event is allowed to be executed, and the operation result of the target element S0 is displayed on the local whiteboard. In this embodiment, The writing handwriting of the element S0 is displayed.

L7. On the side of the local whiteboard, during writing of the element S0, the operation result generated by the operation event displayed on the local whiteboard is also synchronized to the remote whiteboard.

You can synchronize the display contents of multiple whiteboards in a shared meeting by writing and synchronizing.

L8. On the side of the remote whiteboard, an operation event B for element S0 is detected. For example, the operation event of moving S0.

L9. The remote whiteboard obtains the element identifier of the target element S0, and sends a lock application for the element S0 to the server.

L10. The server receives the lock request for element S0 sent by the remote whiteboard. It can be found that the element lock of the target element S0 has been assigned to the local whiteboard, so the element lock of element S0 can no longer be assigned to the remote whiteboard. A message that the element lock application of element S0 is successful is sent to the remote whiteboard.

In other embodiments, when the server finds that the element lock of the target element has been allocated, it may also send a message that the element lock application of the target element failed to the application whiteboard to prompt the whiteboard user that the element is currently inoperable.

L11, because the remote whiteboard cannot obtain the element lock of element S0, it shields the current operation event B.

Therefore, conflicts in which multiple people perform operations on the same page element at the same time are avoided.

In the above embodiment, the specific implementation manner of the whiteboard sending the element lock application to the server in the sharing conference includes the following two cases: determining the event type of the operation event; if it is an event type of adding an element, the element identifier of the target element is generated first , And then send an element lock application to the server; if it is an event type that modifies an element or deletes an element, it obtains the element identifier of the target element and sends an element lock application to the server.

Through the above embodiment, no matter what page elements other whiteboard users are operating in the sharing meeting, if a whiteboard user A wants to add an element to the whiteboard page, he always has this operation right, which will not cause conflicts when multiple people write at the same time . If user A is writing an element and another whiteboard user B wants to modify (move or erase) the element at this time, he cannot apply for the element lock of the element (user A has already occupied the element lock of the element), so User B cannot manipulate this element. However, if user A is writing an element and another whiteboard user B wants to write another element at this time, user B can apply for an element lock for the other element, so user B can perform another element writing operation. Since there is no need to wait until user A finishes writing, the writing efficiency is improved, and the conference effect of the shared meeting is improved.

In a specific example, as shown in FIG. 6A, when the first whiteboard and the second whiteboard participate in a sharing meeting, the user of the first whiteboard "Xiao Ming" writes "hello" (an element) on the whiteboard, so that "hello" "While the second whiteboard user" Little Red "draws a circle (another element) on the whiteboard, so he can get a round element lock. Based on the exclusivity of element lock, in the process of writing "hello" by "Xiao Ming", "Xiao Hong" on the side of the second whiteboard cannot perform any operation on the element "hello". "Xiao Ming" on the side of a white board cannot perform any operation on the circle.

During the writing process of "Xiao Ming" and "Xiao Hong", the display contents of the first white board and the second white board are simultaneously synchronized, and the corresponding display effects are shown in FIG. 6B.

This achieves that multiple users in multiple whiteboards participating in a sharing meeting can simultaneously write on the whiteboard without affecting the writing content of each other; since there is no need to wait for other users to finish writing before starting writing, the writing efficiency is improved, Conducive to improving the effectiveness of shared meetings.

Example 2: Page operation event

M1, on the local whiteboard side, a page operation event is detected (the page P0 is taken as an example below).

M2. Obtain a page identifier of page P0, and send a lock application for page P0 to the server.

The page lock application may carry a page identifier of the target page P0; the page identifier may be a page number, and different pages have different page numbers.

M3, on the server side, receives a page lock application for page P0 sent by the local whiteboard.

M4: Query whether the page lock of page P0 and the element lock of each element in the target page P0 are allocated according to the page identifier carried in the page lock application. If the query result is no, the page lock of the target page P0 is allocated to the originating application. Local whiteboard.

In some embodiments, the page lock application sent by the whiteboard also carries the conference code of the shared conference; such a page lock application can also trigger the server to save the page lock allocation information of the page corresponding to the conference code. That is, when the whiteboard includes multiple pages and multiple users perform operations on different pages, the server can also store page lock allocation information of multiple pages corresponding to the conference code at the same time.

M5: Send a message that the page lock application of the target page P0 is successful to the local whiteboard.

M6, on the side of the local whiteboard, after receiving the message that the page lock application for page P0 was successfully sent by the server, it can execute the page operation event on page P0 on the local whiteboard and display the page operation result.

M7, on the side of the local whiteboard, during the operation on page P0, the operation results displayed on the local whiteboard are also synchronized to the remote whiteboard.

You can synchronize the display contents of multiple whiteboards in a shared meeting by operating while synchronizing.

M8. On the side of the remote whiteboard, an operation event C is detected, for example, the operation event of modifying element S1 in page P0 is detected.

M9. The remote whiteboard obtains the element identifier of the target element S1, and sends a lock application for the element S1 to the server.

M10, the server receives the lock request for element S1 sent by the remote whiteboard, and can query that the page lock of the page P0 where the target element S1 is located has been assigned to the local whiteboard, so the element lock of element S1 cannot be assigned to the remote whiteboard , And it will not send a message that the element lock application of element S1 is successful to the remote whiteboard.

In other embodiments, the server may send a message indicating that the element lock application of element S1 has failed to the application whiteboard, so as to prompt the user on the whiteboard end that the element is currently inoperable or the current page is locked.

M11, because the remote whiteboard cannot obtain the element lock of element S1, it blocks the current operation event C.

According to the above embodiment, if a whiteboard user A is operating a whiteboard page at this time, no matter what page element whiteboard user B wishes to operate in the sharing meeting, he does not have this operation right, thus avoiding multiple people working on the same page at the same time Conflicting operations.

In a specific example, as shown in FIG. 8, when the first whiteboard and the second whiteboard participate in a sharing meeting, the user “Xiao Ming” of the first whiteboard performs a page move operation, which can obtain a page lock of the current page; based on the page lock The exclusiveness of "Xiao Ming" during the page move operation, the user on the second whiteboard side "Red" also wants to move the page, or write on the page, or want to modify the existing Element, however, these operations are not allowed. That is, after the user on the first whiteboard side obtains the page lock of the page, the user on the second whiteboard side is not allowed to perform any page operation or element operation on the page.

During the process of "Xiao Ming" moving the page, the display content of the first whiteboard and the second whiteboard are also synchronized. For example, "Xiao Ming" moves 30% of the horizontal length of the page to the left. Correspondingly, the page on the second whiteboard side will also be synchronized. Move 30% of the horizontal length to the left to synchronize the display content of the whiteboard. See Figure 8 for the corresponding display effect.

In one embodiment, as shown in FIG. 9, the method of displaying the content of the whiteboard is applied to a server as an example, and the execution subject of each step may be understood as a server or a corresponding processor in the server; the server is not only It can be a dedicated server or a whiteboard device that acts as a server. The steps of the method for whiteboard operation in a shared meeting in this embodiment include:

S410. Receive an element lock application sent by the first whiteboard.

The element lock application is issued when a whiteboard operation event occurs on the first whiteboard in a sharing meeting and the target of the operation event is a page element; the element lock application carries an element identifier of the target element; the target element A page element targeted by the operation event;

S420: Query whether the target element belongs to a page element that is being operated by the operation event of the second whiteboard according to the element identifier; if not, assign an element lock of the target element to the first whiteboard.

In an embodiment, the implementation of step S420 includes: querying whether the page lock of the page on which the target element is located and whether the element lock of the target element is assigned to the second whiteboard; if both are not, assigning the element lock of the target element to First whiteboard.

The element lock of an element can be understood as the exclusive operation right of the element. In the embodiment of the present invention, the element lock of each page element at the same time can only be assigned to a whiteboard user in a sharing meeting, for example, during participation Element 1 and Element 2 are displayed on the first whiteboard and the first whiteboard of the same sharing meeting. If the current user of the first whiteboard applies for the element lock of element 1, the element lock of element 1 is used. At this time, the second whiteboard user will Cannot perform any operation on element 1; if the element lock of element 2 is not assigned at this time, the second whiteboard user has the opportunity to obtain the element lock of element 2 and, if it is successful, the second whiteboard user can access the element 2 operation, the first whiteboard user cannot perform any operation on element 2 at this time; thus, the effect that multiple users corresponding to the first whiteboard and the second whiteboard can operate on different page elements at the same time is achieved.

Page locks are more granular than element locks. The specific differences include: when any whiteboard user in a shared meeting applies for an element lock on an element, other whiteboard users can also lock other elements on the whiteboard page. Perform operations; however, when any whiteboard user gets a page lock of a page in a sharing meeting, other whiteboard users will not be allowed to perform any operations on the page and operations on elements on the page. That is, when the page lock of the page is assigned, only one user can operate the page in the shared meeting, and does not support multiple people to perform whiteboard operations at the same time.

S430: Send a message that the element lock application of the target element is successful to the first whiteboard.

By assigning an element lock for each element, users do not need to wait for other users to finish the operation before writing elements, which improves the operation efficiency and helps to improve the effect of shared meetings

Further, referring to FIG. 9, in an embodiment, the steps of the method for operating a whiteboard in a shared conference further include:

S440: Receive an element unlocking application sent by the first whiteboard; the element unlocking application is issued when an operation event corresponding to the target element on the first whiteboard ends; the element unlocking application carries an element identifier of the target element;

The page identifier may be a page number, and different pages have different page numbers.

S450. Set the element lock of the target element to an unassigned state according to the element identifier.

After an element's element lock is set to unassigned, any whiteboard user in a sharing meeting can apply for the element's element lock. By timely releasing the element lock of the page or page element, it is convenient for multiple users sharing the meeting to participate in the operation of the whiteboard, while avoiding operation conflicts with each other.

In addition, in an embodiment, on the server side, after querying whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier, if the query result belongs, the target is sent to the first whiteboard. The message that the element lock application of the element failed, and the message is used to shield the operation event of the first whiteboard. That is, multiple whiteboard users cannot operate on the same page element at the same time, thereby avoiding operation conflicts.

Based on the above embodiment, in an embodiment, referring to FIG. 10, the steps of the method for sharing a whiteboard operation in a conference may further include:

S510: Receive a page lock application sent by the first whiteboard; the page lock application is issued when a whiteboard operation event occurs on the first whiteboard and the target of the operation event is a whiteboard page; the page lock application carries A page identifier of the target page; the target page is a page displayed by the first whiteboard when the operation event occurs;

S520: Query whether the target page belongs to a page that is being operated by the operation event of the second whiteboard according to the page identifier, and if it does not belong, assign a page lock of the target page to the first whiteboard;

In an embodiment, the implementation of S520 includes: querying the page lock of the target page and the element lock of each element in the target page according to the page identifier, and whether the element lock of the target page is assigned to the second whiteboard. The page lock assigned to the first whiteboard;

The page lock is more granular than the above-mentioned element lock. The specific differences include: When any whiteboard user in a shared meeting applies for an element lock on an element, other whiteboard users can also lock the element on the whiteboard page. Other whiteboard users perform operations; however, when any whiteboard user in a sharing meeting gets a page lock on a page, other whiteboard users will not be allowed to perform any operations on the page and operations on the elements on the page. That is, when the page lock of the page is assigned, only one user can operate the page in the shared meeting, and does not support multiple people to perform whiteboard operations at the same time.

S530. Send a message that the page lock application of the target page is successful to the first whiteboard.

In addition, in an embodiment, on the server side, after querying whether the target page belongs to the page being operated by the operation event of the second whiteboard according to the page identifier, if it does not belong, the page of the target page is sent to the first whiteboard A lock application failure message is used to shield the operation event of the first whiteboard. That is, multiple whiteboard users cannot operate on the same page at the same time, thereby avoiding operation conflicts.

Further, referring to FIG. 10, in an embodiment, the steps of the method for operating a whiteboard in a shared conference may further include:

S540: Receive a page unlock application sent by the first whiteboard; the page unlock application is issued when an operation event corresponding to the target page on the first whiteboard ends; the page unlock application carries a page identifier of the target page;

S550. Set the page lock of the target page to an unallocated state according to the page identifier.

After the page lock of the page is set to unassigned, any whiteboard user in the sharing meeting can apply for the page lock of the page or the element lock of each element on the page. By timely releasing the element lock of the page or page element, it is convenient for multiple users sharing the meeting to participate in the operation of the whiteboard, while avoiding operation conflicts with each other.

It should be understood that, for the foregoing method embodiments, although the steps in the flowchart are sequentially displayed according to the directions of the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless explicitly stated in this document, the execution of these steps is not strictly limited, and these steps can be performed in other orders. Moreover, at least a part of the steps in the flowchart of the method embodiment may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. These sub-steps Or the order of execution of the stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

Based on the same idea as the method for implementing a whiteboard operation on one side of the whiteboard device in the above embodiment, a whiteboard operation device is also provided herein.

In one embodiment, as shown in FIG. 11, the apparatus for operating a whiteboard in this embodiment includes:

An event detection module 601, configured to detect an operation event occurring on the first whiteboard;

An element lock application module 602, configured to apply for an element lock of a target element if the target of the operation event is a page element;

An element operation module 603, configured to display the operation result of the target element on the first whiteboard after applying for the element lock of the target element;

The target element is a page element targeted by the operation event, and the target element does not belong to a page element that is being operated by the operation event of the second whiteboard; the first whiteboard and the second whiteboard belong to the same shared conference, The first whiteboard and the second whiteboard display the same page.

In an embodiment, with continued reference to FIG. 11, the device further includes:

A page lock application module 604, configured to apply for a page lock of a target page if the target of the operation event is a page;

A page operation module 605, configured to display the operation result of the target page on the first whiteboard after applying for a page lock of the target page;

In an embodiment, the element lock application module 602 includes:

The element lock application carries an element identifier of a target element;

In an embodiment, the apparatus further includes:

In an embodiment, the page lock application module 604 further includes:

A page lock application unit, configured to send a page lock application of a target page to a server if the target of the operation event is a whiteboard page;

The page lock application carries a page identifier of a target page;

The page lock application is used to trigger the server to query the page lock of the target page and the element lock of each element in the target page according to the page identifier. If the query result is no, the page lock of the target page is allocated to the first page lock. A whiteboard, and a message that the page lock application of the target page is successful is sent to the first whiteboard.

In an embodiment, the apparatus further includes:

The page lock release module is used to send a page unlock request to the server when the operation event corresponding to the target page ends;

Based on the same idea as the method for implementing a whiteboard operation on the server side in the above embodiment, another whiteboard operation device is provided herein.

In one embodiment, as shown in FIG. 12, the whiteboard operating device of this embodiment includes:

A lock application receiving module 701 is configured to receive an element lock application sent by a first whiteboard; the element lock application is when a whiteboard operation event occurs on the first whiteboard in a sharing conference, and a target of the operation event is a page element Issued; the element lock application carries an element identifier of a target element; the target element is a page element targeted by the operation event;

A lock allocation module 702, configured to query whether the target element belongs to a page element that is being operated by an operation event of the second whiteboard according to the element identifier; if it does not, assign an element lock of the target element to the first whiteboard;

A lock feedback module 703, configured to send a message that the element lock application of the target element is successful to the first whiteboard;

In an embodiment, the lock application receiving module 701 is further configured to receive a page lock application sent by the first whiteboard; the page lock application is a whiteboard operation event occurring on the first whiteboard, and a target of the operation event is Issued in the case of a whiteboard page; the page lock application carries a page identifier of the target page; the target page is a page displayed by the first whiteboard when the operation event occurs;

The lock allocation module 702 is further configured to query whether the target page belongs to a page that is being operated by the operation event of the second whiteboard according to the page identifier, and if it does not belong, allocate a page lock of the target page to the first whiteboard;

The lock feedback module 703 is further configured to send a message that the page lock application of the target page is successful to the first whiteboard.

In an embodiment, the apparatus further includes:

The element unlocking receiving module is configured to receive an element unlocking application sent by the first whiteboard; the element unlocking application is issued when an operation event corresponding to the target element on the first whiteboard ends; the element unlocking application carries the target element Element identification

The lock allocation module is further configured to set the element lock of the target element to an unallocated state according to the element identifier.

In an embodiment, the apparatus further includes:

The page unlocking receiving module is configured to receive a page unlocking request sent by the first whiteboard; the page unlocking request is issued when an operation event corresponding to the target page on the first whiteboard ends; the page unlocking request carries a target page Page identification

The page lock allocation module is further configured to set the page lock of the target page to an unallocated state according to the page identifier.

For the specific limitation of the whiteboard operating device, refer to the foregoing limitation on the method of operating the whiteboard, which is not repeated here. Each module in the above whiteboard-operated device may be implemented in whole or in part by software, hardware, and a combination thereof. Each of the above modules may be embedded in the hardware in or independent of the processor in the interactive smart tablet, or may be stored in software in the memory of the interactive smart tablet, so that the processor can call and execute the operations corresponding to the above modules.

In addition, in the implementation of the example whiteboard-operated device described above, the logical division of each program module is merely an example. In actual applications, according to the requirements, for example, for the consideration of the configuration requirements of the corresponding hardware or the convenience of software implementation, the above The function allocation is completed by different program modules, that is, the internal structure of the device operated by the whiteboard is divided into different program modules to complete all or part of the functions described above.

In one embodiment, a whiteboard operating system in a shared conference is provided, including: a first whiteboard and a server;

The first whiteboard includes:

An event detection module for detecting an operation event of the whiteboard;

An element lock application module, configured to: if the target of the operation event is a page element, send an element lock application to the server to apply for an element lock of the target element; the element lock application carries an element identifier of the target element, the The target element is a page element targeted by the operation event;

And, an element operation module is configured to display the operation result of the target element on the first whiteboard after applying for the element lock of the target element;

The server includes:

In one embodiment, a whiteboard device is provided, and the whiteboard device may be an interactive smart tablet. The internal structure diagram of the whiteboard device may be as shown in FIG. 13, including a processor, a memory, a network interface, a display screen, and an input device connected through a system bus. The processor is used to provide computing and control capabilities. The memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory is a non-volatile storage medium. The operating system and the computer program run to provide the environment; the network interface is used to communicate with external devices through a network connection; the computer program is executed by the processor to implement a whiteboard operation method in a shared meeting; the display screen can be an LCD screen or Electronic ink display screen; the input device can be the touch layer covered on the display screen, or the keys, trackball or touchpad provided on the whiteboard device housing, or an external keyboard, touchpad, or mouse.

In one embodiment, a server is provided, which may be a professional shared conference server, or a whiteboard device serving as a server. The internal structure of the server can be shown in Figure 14. The server includes a processor, memory, network interface, and database connected via a system bus. The processor is used to provide computing and control capabilities. The memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory is a non-volatile storage medium. The operating system and the computer program running environment provide the environment; the database is used to store the related data of the whiteboard operation method in the shared meeting; the network interface is used to communicate with the external terminal through the network connection; the computer program is executed by the processor to achieve A method for operating a whiteboard in a shared meeting.

Those skilled in the art can understand that the structures shown in FIGS. 13 and 14 are only block diagrams of some structures related to the solution of the present application, and do not constitute a limitation on the whiteboard device and server to which the solution of the present application is applied. The whiteboard device and server may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

In one embodiment, a whiteboard device is provided, which includes a memory, a display screen with a touch function, and a processor. The memory stores a computer program. When the processor executes the computer program, the following steps can be implemented: :

An operation event occurred on the first whiteboard is detected; if the target of the operation event is a page element, an element lock of the target element is applied; after the element lock of the target element is applied, the operation result of the target element is displayed on the first whiteboard ;

In one embodiment, when the processor executes the computer program, the following steps can also be implemented: if the target of the operation event is a page, apply for a page lock on the target page; after applying for a page lock on the target page To display the operation result of the target page on the first whiteboard;

In one embodiment, when the processor executes the computer program, the following steps can also be implemented: if the target of the operation event is a page element, sending an element lock application to the server of the shared conference;

The element lock application carries an element identifier of the target element; the element lock application is used to trigger the server to query whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier, and if it does not belong, the The element lock of the target element is assigned to the first whiteboard.

In one embodiment, when the processor executes the computer program, the following steps can also be implemented:

Determine the event type of the operation event; if it is the event type of the added element, generate the element ID of the target element, and send an element lock application to the server; if it is the event type of the modified or deleted element, obtain the element ID of the target element, The server sends an element lock request.

In one embodiment, when the processor executes the computer program, the following steps can also be implemented: after assigning the element lock of the target element to the first whiteboard, sending the target element's A message that the element lock application is successful; and / or, setting the element lock of the target element to an allocated state.

In one embodiment, the element lock application further carries a conference code of the shared conference; the element lock application is further used to trigger the server to save the element lock allocation information of the target element corresponding to the conference code.

In one embodiment, when the processor executes the computer program, the following steps can also be implemented: when the operation event corresponding to the target element ends, sending an element unlock application to the server; the element unlock application is used for The server is triggered to set the element lock of the target element to an unassigned state.

In one embodiment, when the processor executes the computer program, the following steps can also be implemented: when the target of the operation event is a whiteboard page, sending a page lock application for the target page to the server; The page lock application carries the page identification of the target page;

In one embodiment, when the processor executes the computer program, the following steps can be further implemented: after the page lock of the target page is assigned to the first whiteboard, the target page is sent to the first whiteboard. A message that the page lock application is successful; and / or, setting the page lock of the target page to an allocated state.

The page lock application also carries the conference code of the shared conference; the page lock application is also used to trigger the server to save the page lock allocation information of the target page corresponding to the conference code.

When the operation event corresponding to the target page ends, a page unlock request is sent to the server; the page unlock request is used to trigger the server to set the page lock of the target page to an unallocated state.

In one embodiment, when the processor executes the computer program, the following steps can also be implemented: synchronizing the operation result generated by the operation event displayed in the first whiteboard to other whiteboard devices in the shared conference .

Acquire the changed whiteboard content in the first whiteboard; the changed whiteboard content is generated by the operation event; and send content data corresponding to the changed whiteboard content to the server, so that other whiteboard devices can obtain the content data through the server To make the same changes in the whiteboard content of the other whiteboard devices;

or,

Acquiring screenshot information of a whiteboard device; sending the screenshot information to a server, so that other whiteboard devices obtain the screenshot information through the server, so that the other whiteboard device displays the screenshot information.

In an embodiment, a server is further provided, including a memory and a processor, where the memory stores a computer program; when the processor executes the computer program, the following steps can be implemented:

Receiving an element lock application sent by a whiteboard device; the element lock application is issued when a whiteboard operation event occurs on a whiteboard device in a shared conference, and the target of the operation event is a page element; the element lock application carries Element identification of a target element; the target element is a page element targeted by the operation event;

Querying whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier; if not, assigning the element lock of the target element to the first whiteboard; and sending the target element's The message that the element lock application is successful;

Receive a page lock application sent by a whiteboard device; the page lock application is issued when a whiteboard operation event occurs on the whiteboard device and the target of the operation event is a whiteboard page; the page lock application carries the target Page identification of the page; the target page is a page displayed by the whiteboard device when the operation event occurs;

Querying whether the target page belongs to a page that is being operated by the operation event of the second whiteboard according to the page identifier; if it does not, assign a page lock of the target page to the first whiteboard; and send the page of the target page to the first whiteboard Lock application success message.

Receiving an element unlocking application sent by the whiteboard device; the element unlocking application is issued when an operation event corresponding to the target element on the whiteboard device ends; the element unlocking application carries an element identifier of the target element;

In one embodiment, when the processor executes the computer program, the following steps can also be implemented: receiving a page unlock application sent by the whiteboard device; the page unlock application is corresponding to the target page on the whiteboard device Sent when the operation event ends; the page unlock application carries a page identifier of the target page; and sets the page lock of the target page to an unassigned state according to the page identifier.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: if the target of the operation event is a page, apply for a page lock of the target page; after applying for a page lock of the target page, on the first whiteboard Display the results of operations on the target page;

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: if the target of the operation event is a page element, sending an element lock application to the server of the shared conference;

In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: after the element lock of the target element is assigned to the first whiteboard, a message that the element lock application of the target element is successful is sent to the first whiteboard ; And / or, setting an element lock of the target element to an allocated state.

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: when the operation event corresponding to the target element ends, sending an element unlocking application to the server;

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: if the target of the operation event is a whiteboard page, sending a page lock application of the target page to the server;

The page lock application carries the page identifier of the target page; the page lock application is used to trigger the server to query the page lock of the target page and the element lock of each element in the target page according to the page identifier. If the query results are all No, assign a page lock of the target page to the whiteboard device, and send a message that the page lock application of the target page is successful to the whiteboard device.

In one embodiment, the page lock application also carries a conference code of the shared conference; the page lock application is further used to trigger the server to save page lock allocation information of a target page corresponding to the conference code.

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: when the operation event corresponding to the target page ends, sending a page unlock request to the server; the page unlock request is used to trigger the server to send the page unlock request The page lock of the target page is set to unallocated.

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: synchronizing the operation results generated by the operation events displayed on the whiteboard device to other whiteboard devices in the sharing conference.

Acquiring the changed whiteboard content in the whiteboard device; the changed whiteboard content is generated by the operation event; sending content data corresponding to the changed whiteboard content to a server, so that other whiteboard devices obtain the content data through the server, So that the same changes occur in the whiteboard content of the other whiteboard devices;

or,

In one embodiment, another computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

Receiving an element lock application sent by a whiteboard device; the element lock application is issued when a whiteboard operation event occurs on the whiteboard device in a sharing conference, and the target of the operation event is a page element; the element lock application carries Element identification of the target element; the target element is the page element targeted by the operation event; and querying whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identification; if not, the target is The element lock of the element is assigned to the first whiteboard; a message that the element lock application of the target element is successful is sent to the first whiteboard;

Receiving a page lock application sent by the whiteboard device; the page lock application is issued when a whiteboard operation event occurs on the whiteboard device and the target of the operation event is a whiteboard page; the page lock application carries the page lock application A page identifier of a target page; the target page is a page displayed by the whiteboard device when the operation event occurs;

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving an element unlocking application sent by the first whiteboard; the element unlocking application is when an operation event corresponding to the target element on the first whiteboard ends Issued; the element unlocking application carries an element identifier of a target element; and sets the element lock of the target element to an unassigned state according to the element identifier.

In an embodiment, when the computer program is executed by the processor, the following steps are further implemented: receiving a page unlock application sent by the first whiteboard; the page unlock application is when an operation event corresponding to the target page on the first whiteboard ends Issued; the page unlock application carries a page identifier of a target page; and sets a page lock of the target page to an unassigned state according to the page identifier.

A person of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by using a computer program to instruct related hardware. The computer program can be stored in a non-volatile computer-readable storage. In the medium, the computer program, when executed, may include the processes of the embodiments of the methods described above. Wherein, any reference to the memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Synchlink DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined. In order to make the description concise, all possible combinations of the technical features in the above embodiments have not been described. However, as long as there is no contradiction in the combination of these technical features, they should be It is considered to be the range described in this specification. The description of each of the foregoing embodiments has different focuses. For a part that is not described in detail in an embodiment, reference may be made to related descriptions in other embodiments.

The terms "including" and "having" and any variations thereof in the examples are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device containing a series of steps or (module) units is not limited to the listed steps or units, but optionally also includes steps or units not listed, or optional The ground also includes other steps or units inherent to these processes, methods, products or equipment.

The "plurality" mentioned in the examples means two or more. "And / or" describes the association relationship of the associated objects, and indicates that there can be three kinds of relationships. For example, A and / or B can mean that there are three cases in which A exists alone, A and B exist, and B exists alone. The character "/" generally indicates that the related objects are an "or" relationship.

The "first \ second" mentioned in the embodiment is only a difference between similar objects, and does not represent a specific ordering of objects. Understandably, "first \ second" can be interchanged with specific ones if allowed. Sequential or sequential. It should be understood that the objects of the "first \ second" distinction are interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than those illustrated or described herein.

The above embodiments only express several implementation manners of the present invention, but cannot be understood as limiting the scope of the invention patent. It should be noted that, for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the protection scope of this application patent shall be subject to the appended claims.

Claims

A method for operating a whiteboard in a shared conference, which includes:

Detecting an operation event occurring on the first whiteboard;

If the target of the operation event is a page element, apply for an element lock of the target element;

After applying for the element lock of the target element, the operation result of the target element is displayed on the first whiteboard;

The target element is a page element targeted by the operation event, and the target element does not belong to a page element that is being operated by the operation event of the second whiteboard;

The first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed on the first whiteboard and the second whiteboard are the same.
The method according to claim 1, further comprising:

If the target of the operation event is a page, apply for a page lock of the target page;

After applying for the page lock of the target page, the operation result of the target page is displayed on the first whiteboard;

The target page is a page displayed by the first whiteboard when the operation event occurs, and the target page does not belong to a page that is being operated by the operation event of the second whiteboard.
The method according to claim 1, wherein, if the target of the operation event is a page element, applying for an element lock of the target element comprises:

If the target of the operation event is a page element, sending an element lock application to the server of the shared conference;

The element lock application carries an element identifier of a target element;

The element lock application is used to trigger the server to query whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier, and if it does not belong, assign the element lock of the target element to the first whiteboard.
The method according to claim 3, wherein the sending an element lock application to the server of the shared conference comprises:

Determining an event type of the operation event;

If it is an event type for adding an element, generate an element identifier of the target element, and send an element lock application to the server;

If it is an event type of modifying an element or deleting an element, obtain the element identifier of the target element, and send an element lock application to the server.
The method according to claim 3, wherein the assigning the element lock of the target element to the first whiteboard further comprises:

Sending a message that the element lock application of the target element is successful to the first whiteboard;

and / or,

The element lock of the target element is set to an allocated state.
The method according to claim 5, wherein the element lock application further carries a conference code of the shared conference;

The element lock application is also used to trigger the server to save the element lock allocation information of the target element corresponding to the conference code.
The method according to claim 5, further comprising:

When the operation event corresponding to the target element ends, sending an element unlocking application to the server;

The element unlock application is used to trigger the server to set the element lock of the target element to an unassigned state.
The method according to claim 2, further comprising: when the target of the operation event is a whiteboard page:

Send a page lock request for the target page to the server;

The page lock application carries a page identifier of a target page;

The page lock application is used to trigger the server to query whether the target page belongs to the page that is being operated by the operation event of the second whiteboard according to the page identifier, and if it does not belong, assign the page lock of the target page to the first whiteboard.
The method according to claim 8, after assigning the page lock of the target page to the first whiteboard, further comprising:

Sending a message that the page lock application of the target page is successful to the first whiteboard;

and / or,

The page lock of the target page is set to an allocated state.
The method according to claim 9, wherein the page lock application further carries a conference code of the shared conference;

The page lock application is also used to trigger the server to save page lock allocation information of a target page corresponding to the conference code.
The method according to claim 9, further comprising:

When the operation event corresponding to the target page ends, sending a page unlock application to the server;

The page unlock application is used to trigger the server to set the page lock of the target page to an unallocated state.
The method according to claim 2, further comprising:

Synchronize operation results generated by the operation events displayed in the first whiteboard to the second whiteboard.
The method according to claim 12, wherein the synchronizing an operation result generated by the operation event displayed on the first whiteboard to a second whiteboard comprises:

Acquiring the changed whiteboard content in the first whiteboard; the changed whiteboard content is generated by the operation event;

Sending content data corresponding to the changed whiteboard content to a server, so that the second whiteboard obtains the content data through the server, so that the whiteboard content of the second whiteboard changes similarly;

or,

Obtaining screenshot information of the first whiteboard;

Sending the screenshot information to the server, so that the second whiteboard obtains the screenshot information through the server, so that the second whiteboard displays the screenshot information.
The method according to claim 12, wherein the operation result generated by the operation event includes one or more of the following:

Page elements increase, page elements decrease, page element position changes, page element form changes, page movement, page zoom, page turning.
The method according to claim 1, wherein the element comprises at least one of a handwriting and an image displayed on a whiteboard page.
The method according to claim 2, wherein:

The target element does not belong to the page element being operated by the operation event of the second whiteboard, and includes: the page lock of the page where the target element is located, and the element lock of the target element are not assigned to the second whiteboard;

The target page does not belong to the page being operated by the operation event of the second whiteboard, and includes: the page lock of the target page and the element lock of each element in the target page are not allocated to the second whiteboard.
A method for operating a whiteboard in a shared conference, which includes:

Receiving an element lock application sent by the first whiteboard; the element lock application is issued when a whiteboard operation event occurs on the first whiteboard in a sharing conference, and the target of the operation event is a page element; the element lock application is in progress An element identifier carrying a target element; the target element is a page element targeted by the operation event;

Querying whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier; if not, assigning an element lock of the target element to the first whiteboard;

Sending a message that the element lock application of the target element is successful to the first whiteboard;

The first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed on the first whiteboard and the second whiteboard are the same.
The method according to claim 17, further comprising:

Receiving a page lock application sent by the first whiteboard; the page lock application is issued when a whiteboard operation event occurs on the first whiteboard and the target of the operation event is a whiteboard page; the page lock application carries the page lock application A page identifier of a target page; the target page is a page displayed by the first whiteboard when the operation event occurs;

Querying whether the target page belongs to the page being operated by the operation event of the second whiteboard according to the page identifier, and if it does not, assign a page lock of the target page to the first whiteboard;

A message that the page lock application of the target page is successful is sent to the first whiteboard.
The method according to claim 17, wherein the assigning the element lock of the target element to the first whiteboard further comprises:

The element lock of the target element is set to an allocated state.
The method according to claim 19, wherein after setting the element lock of the target element to an allocated state, the method further comprises:

Receiving an element unlocking application sent by the first whiteboard; the element unlocking application is issued when an operation event corresponding to the target element on the first whiteboard ends; the element unlocking application carries an element identifier of the target element;

The element lock of the target element is set to an unassigned state according to the element identification.
The method according to claim 17, wherein the querying whether the target element belongs to a page element that is being operated by the operation event of the second whiteboard according to the element identification, further comprising:

If it belongs, a message that the element lock application of the target element fails is sent to the first whiteboard, and the message is used to shield the operation event of the first whiteboard.
The method according to claim 18, wherein the assigning a page lock of the target page to the first whiteboard further comprises:

The page lock of the target page is set to an allocation state.
The method according to claim 22, wherein after setting the page lock of the target page to an allocated state, the method further comprises:

Receiving a page unlock application sent by the first whiteboard; the page unlock application is issued when an operation event corresponding to the target page on the first whiteboard ends; the page unlock application carries a page identifier of the target page;

The page lock of the target page is set to an unallocated state according to the page identifier.
The method according to claim 18, wherein the querying whether the target page belongs to a page on which an operation event of the second whiteboard is being operated according to the page identifier, further comprising:

If it does not, send a message to the first whiteboard that the page lock application of the target page has failed, and the message is used to shield the operation event of the first whiteboard.
A method for operating a whiteboard in a shared conference, which includes:

The first whiteboard detects an operation event of the whiteboard. If the target of the operation event is a page element, an element lock application is sent to the server; the element lock application carries an element identifier of the target element, and the target element is the The page element targeted by the operation event;

The server receives the element lock application, and inquires whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier; if it does not, assigns the element lock of the target element to the first whiteboard, and The first whiteboard sends a message that the element lock application of the target element is successful;

The first whiteboard receives the message that the element lock application is successful, and displays the operation result of the target element on the first whiteboard;

The first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed on the first whiteboard and the second whiteboard are the same.
The method according to claim 25, further comprising:

The server inquires, according to the element identifier, that the target element belongs to a page element that is being operated by an operation event of the second whiteboard, and sends a message that the element lock application of the target element fails to the first whiteboard;

The first whiteboard receives the message that the element lock application fails, and shields the operation event.
A whiteboard operating device in a sharing conference, which includes:

An event detection module, configured to detect an operation event occurring on the first whiteboard;

An element lock application module, configured to apply for an element lock of a target element if the target of the operation event is a page element;

An element operation module, configured to display the operation result of the target element on the first whiteboard after applying for the element lock of the target element;

The target element is a page element targeted by the operation event, and the target element does not belong to a page element that is being operated by the operation event of the second whiteboard;

The first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed on the first whiteboard and the second whiteboard are the same.
The apparatus according to claim 27, further comprising:

A page lock application module, configured to apply for a page lock of a target page if the target of the operation event is a page;

A page operation module, configured to display the operation result of the target page on the first whiteboard after applying for a page lock of the target page;

The target page is a page displayed by the first whiteboard when the operation event occurs, and the target page does not belong to a page that is being operated by the operation event of the second whiteboard.
The device according to claim 27, wherein the element lock application module comprises:

An element lock application unit, configured to send an element lock application to the server of the shared conference if the target of the operation event is a page element;

The element lock application carries an element identifier of a target element;

The element lock application is used to trigger the server to query whether the target element belongs to the page element being operated by the operation event of the second whiteboard according to the element identifier, and if it does not belong, assign the element lock of the target element to the first whiteboard.
The apparatus according to claim 27, further comprising:

An element lock release module, configured to send an element unlocking application to a server when an operation event corresponding to the target element ends;

The element unlock application is used to trigger the server to set the element lock of the target element to an unassigned state.
A device for sharing a whiteboard operation in a conference, comprising:

A lock application receiving module is configured to receive an element lock application sent by a first whiteboard; the element lock application is issued when a whiteboard operation event occurs on the first whiteboard in a sharing conference, and the target of the operation event is a page element The element lock application carries an element identifier of a target element; the target element is a page element targeted by the operation event;

A lock allocation module, configured to query whether the target element belongs to a page element being operated by an operation event of the second whiteboard according to the element identifier; if not, assign an element lock of the target element to the first whiteboard;

A lock feedback module, configured to send a message that the element lock application of the target element is successful to the first whiteboard;

The first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed on the first whiteboard and the second whiteboard are the same.
The device according to claim 31, wherein:

The lock application receiving module is further configured to receive a page lock application sent by the first whiteboard; the page lock application is issued when a whiteboard operation event occurs on the first whiteboard and the target of the operation event is a whiteboard page; The page lock application carries a page identifier of the target page; the target page is a page displayed by the first whiteboard when the operation event occurs;

The lock allocation module is further configured to query whether the target page belongs to a page that is being operated by the operation event of the second whiteboard according to the page identifier, and if it does not belong, allocate a page lock of the target page to the first whiteboard;

The lock feedback module is further configured to send a message that the page lock application of the target page is successful to the first whiteboard.
A whiteboard operating system in a shared conference, comprising: a first whiteboard and a server;

The first whiteboard includes:

An event detection module for detecting an operation event of the whiteboard;

An element lock application module, configured to send an element lock application to the server if the target of the operation event is a page element; the element lock application carries an element identifier of the target element, and the target element is the target of the operation event. Page elements

And, an element operation module is configured to display the operation result of the target element on the first whiteboard after receiving the message that the element lock application is successful;

The server includes:

A lock application receiving module, configured to receive an element lock application sent by the first whiteboard;

A lock allocation module, configured to query whether the target element belongs to a page element being operated by an operation event of the second whiteboard according to the element identifier; if not, assign an element lock of the target element to the first whiteboard;

And, a lock feedback module is configured to send a message that the element lock application of the target element is successful to the first whiteboard;

The first whiteboard and the second whiteboard belong to the same sharing conference, and the pages displayed on the first whiteboard and the second whiteboard are the same.
A whiteboard device includes a memory, a display screen with a touch function, and a processor. The memory stores a computer program. The memory is characterized in that:

When the processor executes the computer program, the steps of the method according to any one of claims 1 to 16 can be implemented.
A server includes a memory and a processor, and the memory stores a computer program;

When the processor executes the computer program, the steps of the method of any one of claims 17 to 24 can be performed.
A computer-readable storage medium having stored thereon a computer program, characterized in that when the computer program is executed by the processor, the processor causes the processor to implement the steps of the method according to any one of claims 1 to 16. Or the steps of the method of any one of claims 17 to 24.