A remote multi-person handwriting implementation method and client and server

By introducing the server-side checksum encapsulation mechanism in remote writing technology, the problem of multi-person operation is solved, and the interaction and fluency of remote multi-person collaborative writing is achieved, ensuring the correctness of data sequence and operation.

CN114629884BActive Publication Date: 2024-12-03TONGCAI AUDIO VISUAL TECH (SHANGHAI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210103325.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-01-27
Publication Date
2024-12-03
Estimated Expiration
2042-01-27

AI Technical Summary

Technical Problem

The existing remote writing technology cannot support multiple people to operate simultaneously, resulting in the inability to implement interactive and collaborative writing.

Method used

By obtaining the writing handwriting data of each client, packaging and sending it to the server, the server performs verification and encapsulation and returns it to the client. The client restores and displays the handwriting according to the server number, and passes through local number and element verification Tables ensure data order and operation priority, avoiding data disorders and conflicts.

Benefits of technology

It realizes the writing function of remote multiple people simultaneously operating, ensuring the correct data order, avoiding confusion caused by packet loss and delay, and improving operation experience and fluency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114629884B_ABST
    Figure CN114629884B_ABST
Patent Text Reader

Abstract

The invention discloses a remote multi-person handwriting realization method and a client and a server, and relates to the technical field of computer application software. The method comprises: obtaining handwriting data of operating users of each client i, i=1, 2, ...; packaging the handwriting data to obtain handwriting data packets of each client i, and sending the handwriting data packets to a server; the server is used to obtain N handwriting data packets sent by the client i, N≥2; verifying each handwriting data packet according to a local number in each handwriting data packet, adding a server number to each handwriting data packet after the verification, encapsulating each handwriting data packet containing the server number, and sending the handwriting data packet containing the server number to each client i. The invention can solve the problem that remote handwriting cannot be operated by multiple people at the same time.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of computer application software, and in particular to a remote multi-person handwriting implementation method, a client end, and a server end. Background Art

[0002] At present, remote handwriting has become more and more common, especially in conference software, which has a whiteboard handwriting function. The following two methods of implementing remote writing have appeared in the market:

[0003] One is to transmit via video, directly recording the picture and transmitting it. This method is relatively traditional. Its advantage is that the picture is relatively accurate when the network bandwidth is very good, but its disadvantage is that it does not support multi-person operation and writing, and can only be displayed.

[0004] The second is to package and transmit the handwriting data. This method solves the problem that other people cannot operate, but it only supports single-person operation, not multi-person operation, and there is no interactive operation. Summary of the invention

[0005] Based on this, it is necessary to provide a remote multi-person handwriting implementation method and a client and server to address the above technical issues, so as to solve the problem in the prior art that remote handwriting cannot be operated by multiple people at the same time.

[0006] Based on the above purpose, a method for implementing remote multi-person handwriting includes:

[0007] Obtain handwriting data of the operating user of each client i, i=1, 2, ...; pack the handwriting data to obtain a handwriting data packet of each client i, the handwriting data packet including a local number, an action type, and detailed content; send the handwriting data packet to the server;

[0008] The server is used to obtain N handwriting data packets sent by the client i, where N≥2; verify each handwriting data packet according to the local number in each handwriting data packet, add the server number to each handwriting data packet after the verification, encapsulate each handwriting data packet containing the server number, and send the handwriting data packet containing the server number to each client i;

[0009] Each client i is used to restore and display the operation handwriting according to the handwriting data packet containing the server number.

[0010] The above method has the following beneficial effects:

[0011] The server verifies the handwriting data packet, adds the server number, encapsulates the handwriting data packets containing the server number, and sends the handwriting data packets containing the server number to each client; the client receives the re-encapsulated handwriting data packet pushed by the server, which can solve the problem that remote handwriting cannot be operated by multiple people at the same time.

[0012] Optionally, verifying each handwriting data packet using the local number in each handwriting data packet includes:

[0013] Obtaining the record number in the set user data table, where the record number is the local number of the handwriting data packet last operated by the user;

[0014] Optionally, it is determined whether the local number and the record number are continuous, and if so, the verification is considered to be successful.

[0015] The effect is that the user data table can ensure that the user handwriting data packets received by the server are in the correct order, and avoid the confusion of handwriting data packets caused by packet loss and delay.

[0016] Optionally, the handwriting data packet further includes an operation element, and the server is further configured to verify each handwriting data packet according to the operation element in each handwriting data packet, including:

[0017] Obtain a set element verification table, in which the element numbers currently occupied are stored, obtain the number of the operating element in the handwriting data packet, and if the number of the operating element is recorded in the element verification table, determine that the verification is passed.

[0018] The effect is: by checking the element inspection table, it is possible to determine whether the users are consistent, and then assign the user's operation priority to avoid multiple people operating the same element at the same time, causing data disorder.

[0019] Optionally, the handwriting data packet also includes a user identity and an operation version number.

[0020] Optionally, after receiving the handwriting data packet pushed by the server, each client i parses the handwriting data packet and obtains the operating user of the handwriting data packet according to the user identity identifier of the handwriting data packet;

[0021] When the operating user of the handwriting data packet is inconsistent with the operating user of the current client, it is determined whether the operating elements of the handwriting data packet sent from the server conflict with the operating elements of the handwriting data packet cached in the current client. If a conflict occurs, the current client performs a withdrawal operation, returns to the node where the elements have not changed, and performs handwriting operations according to the handwriting data packet sent by the server.

[0022] The effect is: by checking whether the operators are the same, it can avoid multiple people operating the same element at the same time, causing operation conflicts.

[0023] Optionally, sending the handwriting data packet to the server includes: caching the handwriting data packet, adding it to a sending queue, and sending it to the server one by one.

[0024] The effect is: through data caching, network pressure can be reduced and the smoothness of writing for multiple people can be increased without affecting the display effect.

[0025] Based on the above purpose, a client is proposed, the client comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor implements the following steps when executing the computer program:

[0026] Acquire handwriting data of the operating user of the current client, package the handwriting data, and obtain a handwriting data packet of the current client, wherein the handwriting data packet includes a local number, an action type, and detailed content; and send the handwriting data packet to the server;

[0027] Receive a handwriting data packet containing a server number sent by the server, and restore and display the handwriting according to the handwriting data packet containing the server number.

[0028] The above client has the following beneficial effects:

[0029] The client collects data within a reasonable range, packages the handwriting data packets according to a reasonable data packet structure, and caches the handwriting data packets and sends them at intervals, which can effectively ensure the handwriting display effect and transmission smoothness.

[0030] Optionally, after receiving the handwriting data packet of the current client, the handwriting data packet is cached and sent to the server at set intervals.

[0031] The effect is: when sending handwriting data packets, the network pressure is reduced as much as possible without affecting the display effect.

[0032] Based on the above purpose, a server is proposed, which includes: receiving N handwriting data packets sent by each client i, N≥2, i=1,2,...; verifying each handwriting data packet according to the local number in each handwriting data packet, adding the server number to each handwriting data packet after the verification, encapsulating each handwriting data packet containing the server number, and sending the handwriting data packet containing the server number to each client i.

[0033] The above service end has the following beneficial effects:

[0034] The server performs necessary data processing to eliminate most errors and redundant data. The client caches the sent data, and local operations can continue without any lag due to delayed verification, effectively improving the local operation experience.

[0035] Optionally, verifying each handwriting data packet according to the local number in each handwriting data packet includes:

[0036] Obtaining the record number in the set user data table, where the record number is the local number of the handwriting data packet last operated by the user;

[0037] Determine whether the local number and the record number are continuous. If they are continuous, the verification is determined to be successful.

[0038] The effect is: ensuring that the user's handwriting data packets received by the server are in the correct order, and preventing the handwriting data packets from being disordered due to packet loss or delay. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0040] Figure 1 is a flow chart of a method for implementing remote multi-person handwriting provided in one embodiment of the present invention;

[0041] Figure 2 This is a flow chart of data transmission by a client provided in one embodiment of the present invention;

[0042] Figure 3 It is a diagram showing the structure of a handwriting data packet of a client provided in one embodiment of the present invention;

[0043] Figure 4 is a service-side processing flow chart provided in one embodiment of the present invention;

[0044] Figure 5 It is a structural diagram of a handwriting data packet of a server provided in an embodiment of the present invention;

[0045] Figure 6 is a client receiving process flow chart provided in one embodiment of the present invention;

[0046] Figure 7 is a client structure diagram provided in one embodiment of the present invention;

[0047] Figure 8 It is a server structure diagram provided in one embodiment of the present invention. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0049] Embodiment 1

[0050] See also Figure 1 , is a flow chart of a method for implementing remote multi-person handwriting provided by Embodiment 1 of the present invention. As shown in the figure, the method may include the following steps:

[0051] Step S101, obtain the handwriting data of the operating user of each client i, i=1, 2,...; pack the handwriting data to obtain the handwriting data packet of each client i, the handwriting data packet includes the local number, action type, and detailed content; send the handwriting data packet to the server.

[0052] Step S102: The server is used to obtain N handwriting data packets sent by the client i, N≥2; verify each handwriting data packet according to the local number in each handwriting data packet, add the server number to each handwriting data packet after the verification, encapsulate each handwriting data packet containing the server number, and send the handwriting data packet containing the server number to each client i.

[0053] Step S103: Each client i is used to restore and display the operation handwriting according to the handwriting data packet containing the server number.

[0054] See also Figure 2 , is a flow chart of client sending provided by an embodiment of the present invention, as shown in the figure, the method may include the following steps:

[0055] The client includes a client handwriting collection module, a client packaging module, a client cache module, and a client packaging and sending module. The client handwriting collection module is responsible for collecting writing handwriting data. The recording of writing handwriting includes the pen-putting stage, the moving stage, and the pen-lifting stage. When the pen is put down, the client collects the pen-putting point data once. During the subsequent pen movement process, the moving point data is collected at intervals. When the pen is lifted, the client collects the pen-lifting point data once. The handwriting data collected by the client includes: handwriting size, handwriting color, handwriting point position, handwriting pressure value, and handwriting pen tip data.

[0056] The client packaging module is responsible for organizing and packaging the handwriting data collected by the client. The handwriting data needs to be packaged according to a certain format, see Figure 3 , is the client handwriting data packet structure diagram. As shown in the figure, the packaged handwriting data packet contains user identification, local number, version number, action type, operation element, and detailed content.

[0057] The user identity is the current operating user, and the identity can be accurately determined by the server.

[0058] The local number is the sequence number of the writing handwriting data packets to which they are sent, for example: the writing handwriting pen-down data packet is locally numbered 1, the writing handwriting moving data packet is numbered 2, the writing handwriting moving data packet is numbered 3, and the writing handwriting lifting data packet is numbered 4. The entire writing handwriting process is numbered in sequence. The client must follow the sequence of data packets 1-4 to completely restore the writing handwriting. If the writing handwriting data packet is lost or in the wrong sequence, the writing handwriting cannot be accurately restored.

[0059] The version number is a mark for determining whether the current operation of the client is an approved version. For example, the current user performs a screen clearing operation on the client, and other clients are still operating on the old version because they have not received the writing handwriting data packet of that version. In this case, the data of the old version operation will not be recognized by the client. After the client receives the writing handwriting data packet of the latest version, the old version writing handwriting data packet will be discarded, and the data in the latest writing handwriting data packet will be processed.

[0060] The action type refers to various operations, such as pen lifting, moving, pen dropping, screen clearing, and page switching performed by the user on the client. The client marks the action type in the handwriting data packet as the corresponding action according to the user's different operation types.

[0061] The operation element is a specific element of the action type operation, for example, the operation element of moving a data packet is a moving handwriting element.

[0062] The detailed content is a detailed data packet. For example, the detailed content of the handwriting data packet of a moving action includes the size, color, position of the handwriting point, pressure value, and pen tip of the points during movement.

[0063] The client cache module caches the handwriting data packet completed by the client packaging module, waiting for secondary confirmation by the client or being sent to the server by the client packaging and sending module.

[0064] The client packaging and sending module is responsible for sending the completed handwriting data packet of the client to the server. The client packaging and sending module sends in the order of the local numbers. The client packaging and sending module does not send immediately. It will sort and package the data packets to be sent at regular intervals and send them. While minimizing network pressure without affecting the display effect, this can ensure the display effect and improve the fluency of remote writing.

[0065] Specifically, taking the example that the user writes the character "one" on the client to illustrate the detailed process of the client collecting, packaging, and caching the handwriting data in detail. When the user starts writing, the client begins to collect the handwriting data. The user identification and version number remain unchanged throughout the process of writing "one" completely. The local number at the start of writing is 1, the action type is marked as starting to write, the operation element is the point at the start of writing, and the detailed content includes the size, color, position of the handwriting point, pressure value, and pen tip data at the start of writing.

[0066] During the movement process, the local number starts from 2. The movement process of writing "one" is collected at regular intervals. Suppose the local number ends at 4 for the collection of the handwriting during the movement process. Then the local numbers of the data packets during the movement process are 2, 3, and 4. The version number remains unchanged. The action type is movement, the operation element is the handwriting element during movement, and the detailed content includes the size, color, position of the points during the movement process, pressure value, and pen tip data. When lifting the pen, the local number is 5, the version number remains unchanged, the action type is lifting the pen, the operation element is the specific element when lifting the pen, and the detailed content includes the size, color, position of the point when lifting the pen, pressure value, and pen tip data.

[0067] At this point, the client has completed the collection and packaging of the handwriting data for writing "one". The client cache module caches the handwriting data packet, waiting for secondary confirmation by the client or being sent to the server by the client packaging and sending module. The client packaging and sending module will send the handwriting data packet to the server at regular intervals in the order of the local numbers 1 - 5 of the data packets.

[0068] See Figure 4 , which is the server processing flow chart provided by the embodiment of the present invention. As shown in the figure, the method may include the following steps:

[0069] The server includes: a server preprocessing module, a server processing module, and a server push module. The server preprocessing module includes a user data table, an element locking table, and a version number processing module. The user data table is used to ensure that the order of the handwriting data packets received by the server is correct, to prevent data confusion caused by packet loss and delay, and to record the last normal data packet number of the user. For example, the client has sent handwriting data packets 1, 2, and 3, and only records the number of the last handwriting data packet 3. The element locking table refers to the data element currently being operated and the corresponding operator. In the process of multiple people operating at the same time, an element can only be operated by one person, otherwise confusion and data abnormality will occur. Only the current operator can perform the operation. After the current operator is released, others can operate.

[0070] After receiving the handwriting data packet, the server first checks the user data table to see if it is continuous with the last normal handwriting data packet number. If it is continuous, the server proceeds to the next step and updates the last handwriting data packet number in the user data table. If the handwriting data packet number is smaller than the number in the user data table, this handwriting data packet has been sent multiple times due to delays, etc., and the packet does not need to be processed and is discarded directly. If the handwriting data packet number is larger than the number in the user data table, there are still some data packets in the middle that have not been sent to the server in time due to network factors. The server caches the current packet and waits for the correct data packet to arrive. If a certain waiting time exceeds, the user will be actively informed that a data packet is lost and needs to be resent.

[0071] After the user data sequence is corrected, the element verification process is performed. After a simple unpacking, the current operation element number and user are obtained. The element verification table is checked to see if there is this element number. If it exists, check whether the user is consistent. If it is consistent, the next operation is carried out normally. If it is inconsistent, it means that there are other users operating this element and have operation priority. This data packet will be deemed invalid and discarded. If there is no such element number in the element verification table, there is no user currently operating, so this element number and user are increased. The version number of the data packet is verified, and the version number with a low version number is discarded, and the version number is updated according to the type of packet operation.

[0072] The handwriting data packet after the above verification will be added with the server number in the packet header and the handwriting data packet will be cached. Figure 5 , is a diagram of the complete data packet structure of the server provided by an embodiment of the present invention. Compared with the complete data packet of the client, the packet header adds a server number, and the operation sequence of all clients is executed according to the server number. The handwriting data packet with the server number is pushed to each server by the server push module.

[0073] See also Figure 6, is a client receiving process flow chart provided by an embodiment of the present invention, as shown in the figure, the method may include the following steps:

[0074] The client also includes: a client receiving module, a client secondary confirmation module, a client snatching module, a client withdrawing module, and a client withdrawing module. The client receiving module receives the handwriting data packet sent by the server, verifies the order of the handwriting data packet, and ensures the order of the handwriting data packet on the server. The client secondary confirmation module obtains the local user number. If the operation user in the handwriting data packet is himself, the previously cached data packet is searched, and the obtained handwriting data packet is marked as confirmed. Otherwise, a snatch judgment is made, and the client snatching module checks whether there is a conflict in the elements of the operation. If a conflict occurs, the cache module cache data is searched, and the client withdrawal module cancels the handwriting data packet that has not been confirmed twice, clears the handwriting, and the client restoration module restores the operation handwriting according to the handwriting data packet.

[0075] Embodiment 2

[0076] In the second embodiment, a client is provided, and its internal structure diagram can be as follows: Figure 7 As shown. The client includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the client is used to provide computing and control capabilities. The memory of the client includes a readable storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer-readable instructions. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in the readable storage medium. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer-readable instructions are executed by the processor, the following steps are implemented:

[0077] Acquire handwriting data of the operating user of the current client, package the handwriting data, and obtain a handwriting data packet of the current client, wherein the handwriting data packet includes a local number, an action type, and detailed content; and send the handwriting data packet to the server;

[0078] The manner in which the handwriting data packet is sent to the server is as follows: after obtaining the handwriting data packet of the current client, the handwriting data packet is cached and sent to the server at set intervals.

[0079] Receive a handwriting data packet containing a server number sent by a server, and restore and display the handwriting according to the handwriting data packet containing the server number.

[0080] The client program includes: a client handwriting collection module, a client packaging module, a client cache module, a client packaging and sending module, a client receiving module, a client secondary confirmation module, a client snatching module, a client withdrawal module, and a client restoration module. The client handwriting collection module obtains the handwriting data of the operating user of the current client. The client packaging module packages the handwriting data to obtain the handwriting data packet of the current client. The handwriting data packet includes a local number, an action type, and detailed content. The client packaging and sending module sends the handwriting data packet to the server.

[0081] The client receiving module receives the handwriting data packet containing the server number sent by the server, and parses the operator in the handwriting data packet. If they are consistent, the client secondary confirmation module confirms the cached handwriting data packet. If they are inconsistent, the client snatching module performs a snatching judgment, and the client withdrawing module performs a handwriting withdrawal operation. The client restoring module restores and displays the operation handwriting according to the handwriting data packet containing the server number.

[0082] Embodiment 3

[0083] In the third embodiment, a computer device is provided. The computer device is a server. Its internal structure diagram can be as follows: Figure 8 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a readable storage medium and an internal memory. The readable storage medium stores an operating system, computer-readable instructions and a database. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in the readable storage medium. The database of the computer device is used to store data involved in the remote multi-person handwriting implementation method. When the computer-readable instructions are executed by the processor, the following steps are implemented:

[0084] Receive N handwriting data packets sent by each client i, N≥2, i=1,2,…; verify each handwriting data packet according to the local number in each handwriting data packet, add the server number to each handwriting data packet after the verification, encapsulate each handwriting data packet containing the server number, and send the handwriting data packet containing the server number to each client i.

[0085] The checking of each handwriting data packet according to the local number in each handwriting data packet comprises:

[0086] Obtaining the record number in the set user data table, where the record number is the local number of the handwriting data packet last operated by the user;

[0087] Determine whether the local number and the record number are continuous. If they are continuous, the verification is determined to be successful.

[0088] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing related hardware through computer-readable instructions, and the computer-readable instructions can be stored in a non-volatile readable storage medium or a volatile readable storage medium. When the computer-readable instructions are executed, they may include the processes of the embodiments of the above-mentioned methods. Among them, any reference to 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 may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0089] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0090] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A method for realizing remote multi-person handwriting, characterized in that: The method comprises: Obtain handwriting data of the operating user of each client i, i=1,2,...; pack the handwriting data to obtain a handwriting data packet of each client i, the handwriting data packet including a local number, an action type, and detailed content; send the handwriting data packet to the server; The server is used to obtain N handwriting data packets sent by the client i, where N≥2; verify each handwriting data packet according to the local number in each handwriting data packet, add the server number to each handwriting data packet after the verification, encapsulate each handwriting data packet containing the server number, and send the handwriting data packet containing the server number to each client i; The handwriting data packet also includes an operation element, and the server is further used to verify each handwriting data packet according to the operation element in each handwriting data packet, including: Obtaining a set element verification table, wherein the element verification table stores the number of currently occupied elements, obtaining the number of the operating element in the handwriting data packet, and if the number of the operating element is recorded in the element verification table and is consistent with that of the user, determining that the verification is passed; if the number of the operating element is recorded in the element verification table and is inconsistent with that of the user, determining that other users are operating this element, determining that the handwriting data packet is invalid and discarding it; if the number of the operating element is not recorded in the element verification table, no user is currently operating, and adding the number of the operating element and the corresponding user in the element verification table; Each client i is used to restore and display the operation handwriting according to the handwriting data packet containing the server number; The handwriting data packet also includes a user identification and an operation version number; After receiving the handwriting data packet pushed by the server, each client i parses the handwriting data packet and obtains the operating user of the handwriting data packet according to the user identity identifier of the handwriting data packet; When the operating user of the handwriting data packet is inconsistent with the operating user of the current client, it is determined whether the operating elements of the handwriting data packet sent from the server conflict with the operating elements of the handwriting data packet cached in the current client. If a conflict occurs, the current client performs a withdrawal operation, returns to the node where the elements have not changed, and performs handwriting operations according to the handwriting data packet sent by the server.

2. The method according to claim 1, characterized in that The local number in each handwriting data packet verifies each handwriting data packet, including: Obtaining the record number in the set user data table, where the record number is the local number of the handwriting data packet last operated by the user; Determine whether the local number and the record number are continuous. If they are continuous, the verification is determined to be successful.

3. The method according to claim 1, characterized in that Sending the handwriting data packet to the server includes: caching the handwriting data packet, adding it to a sending queue, and sending it to the server one by one.

4. A server, characterized in that: The server includes a processor, a memory, and a computer program stored in the memory and running on the processor, and the processor implements the following steps when executing the computer program: Receive N handwriting data packets sent by each client i, N≥2, i=1,2,…; the handwriting data packets include a local number, an action type, and detailed content, verify each handwriting data packet according to the local number in each handwriting data packet, add a server number to each handwriting data packet after the verification, encapsulate each handwriting data packet containing the server number, and send the handwriting data packet containing the server number to each client i; The handwriting data packet also includes an operation element, and the server is further used to verify each handwriting data packet according to the operation element in each handwriting data packet, including: Obtaining a set element verification table, wherein the element verification table stores the number of currently occupied elements, obtaining the number of the operating element in the handwriting data packet, and if the number of the operating element is recorded in the element verification table and is consistent with that of the user, determining that the verification is passed; if the number of the operating element is recorded in the element verification table and is inconsistent with that of the user, determining that other users are operating this element, determining that the handwriting data packet is invalid and discarding it; if the number of the operating element is not recorded in the element verification table, no user is currently operating, and adding the number of the operating element and the corresponding user in the element verification table; Each client i is used to restore and display the operation handwriting according to the handwriting data packet containing the server number; The handwriting data packet also includes a user identification and an operation version number; After receiving the handwriting data packet pushed by the server, each client i parses the handwriting data packet and obtains the operating user of the handwriting data packet according to the user identity identifier of the handwriting data packet; When the operating user of the handwriting data packet is inconsistent with the operating user of the current client, it is determined whether the operating elements of the handwriting data packet sent from the server conflict with the operating elements of the handwriting data packet cached in the current client. If a conflict occurs, the current client performs a withdrawal operation, returns to the node where the elements have not changed, and performs handwriting operations according to the handwriting data packet sent by the server.

5. The server according to claim 4, characterized in that: The checking of each handwriting data packet according to the local number in each handwriting data packet comprises: Obtaining the record number in the set user data table, where the record number is the local number of the handwriting data packet last operated by the user; Determine whether the local number and the record number are continuous. If they are continuous, the verification is determined to be successful.

6. A client, characterized in that: The client comprises a processor, a memory, and a computer program stored in the memory and running on the processor, and when the processor executes the computer program, the following steps are implemented: Acquire handwriting data of the operating user of the current client, package the handwriting data, and obtain a handwriting data packet of the current client, wherein the handwriting data packet includes a local number, an action type, and detailed content; send the handwriting data packet to a server, wherein the server is a server as described in any one of claims 4 to 5; The handwriting data packet also includes an operation element; Receive a handwriting data packet containing a server number sent by a server, and restore and display the handwriting according to the handwriting data packet containing the server number.

7. The client according to claim 6, characterized in that: After obtaining the handwriting data packet of the current client, the handwriting data packet is cached and sent to the server at set intervals.