Table information updating method and device, equipment, medium and product

Abstract

The invention discloses a table information updating method and device, equipment, a medium and a product. The method comprises the steps of receiving a first editing operation for a first table, and obtaining a data adjustment type; wherein the data adjustment type is related to the first editing operation, and the first table is a table which can be collaboratively edited by at least two collaborative users; obtaining a data synchronization attribute of at least one online client based on the first query rate per second and the number of clients; and based on the data synchronization attribute of the at least one online client, performing content updating and displaying on the first table displayed by the at least one online client. According to the mode, the collaborative request for table synchronization is orderly processed, so that the effect of effective table synchronization is achieved.

Description

Technical Field

[0001] This article relates to the field of computer processing technology, and in particular to a method, apparatus, device, medium and product for updating table information. Background Technology

[0002] Currently, online forms allow multiple users to collaboratively edit simultaneously.

[0003] When a large number of users are collaborating on the same table of data, the backend interface may have limited processing capacity, which can restrict the synchronization of table data. Summary of the Invention

[0004] This paper provides a method, apparatus, device, medium, and product for updating table information to enable the orderly sending of collaborative requests to the backend interface, thereby improving data synchronization efficiency and the effect of collaborative scheduling.

[0005] Firstly, this paper provides a method for updating table information, which includes: Receive a first edit operation on a first table and obtain the data adjustment type; wherein, the data adjustment type is related to the first edit operation, and the first table is a table that can be collaboratively edited by at least two collaborating users; Based on the first query rate per second and the number of clients, data synchronization attributes of at least one online client are obtained; wherein, the first query rate per second is related to the data adjustment type, and the online client is a client that displays the first table online; Based on the data synchronization attributes of the at least one online client, the content of the first table displayed by the at least one online client is updated.

[0006] Secondly, this paper also provides a device for updating table information, the device comprising: A data adjustment type acquisition module is used to receive a first editing operation on a first table and obtain the data adjustment type; wherein, the data adjustment type is related to the first editing operation, and the first table is a table that can be collaboratively edited by at least two collaborating users; A data synchronization attribute acquisition module is used to obtain data synchronization attributes of at least one online client based on a first query rate per second and the number of clients; wherein, the first query rate per second is related to the data adjustment type, and the online client is a client information synchronization update module that displays a first table online, used to update and display the content of the first table displayed by the at least one online client based on the data synchronization attributes of the at least one online client.

[0007] Thirdly, this article also provides an electronic device, which includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the table information update method as described herein.

[0008] Fourthly, this document also provides a storage medium containing computer-executable instructions that, when executed by a computer processor, are used to perform the table information update method as described herein.

[0009] Fifthly, this document also provides a computer program product, including a computer program that, when executed by a processor, implements the table information updating method as described in any of the present documents.

[0010] The implementation method presented in this paper, upon receiving a first edit operation on a first table, can obtain the data adjustment type associated with the first edit operation, and then retrieve the first query rate per second that matches the data adjustment type. Based on the first query rate per second, the data synchronization attribute of at least one online client associated with the first table is determined. Based on the data synchronization attribute of each online client, the table update data associated with the first edit operation is synchronized to the corresponding online client. This solves the problem in existing technologies where, when the table information presented on the front-end interface changes, a collaborative request matching the number of clients needs to be generated. After processing the collaborative request based on the back-end interface, the changed data is synchronized to other online clients, resulting in multiple and frequent calls to the back-end interface. Furthermore, when the back-end interface has limited processing capacity, this leads to timeouts in collaborative request processing, preventing data synchronization. The new method combines the interface capabilities of the back-end interface and the number of online clients to collaboratively determine the data synchronization attribute of each online client. Specifically, it obtains the data synchronization time information of each online client within the delayed synchronization time range, and then performs data synchronization updates based on the data synchronization attribute, achieving an orderly synchronization of table data to other online clients.

[0011] It should be understood that the descriptions in this section are not intended to identify key or important features of this document, nor are they intended to limit its scope. Other features of this document will become readily apparent from the following description. Attached Figure Description

[0012] The above and other features, advantages, and aspects of the various implementations herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0013] Figure 1 This is a schematic diagram of the structure of the exemplary system provided in this article; Figure 2 This is a flowchart illustrating a method for updating table information provided in this article; Figure 3 This is a flowchart illustrating a method for updating table information provided in this article; Figure 4 This is a flowchart illustrating a method for updating table information provided in this article. Figure 5 This is a schematic diagram of the structure of a table information updating device provided in this article; Figure 6 This is a schematic diagram of the structure of an electronic device provided in this article. Detailed Implementation

[0014] The implementations described herein will now be described in more detail with reference to the accompanying drawings. While some implementations of this document are shown in the drawings, it should be understood that this document can be implemented in various forms and should not be construed as limited to the implementations described herein. Rather, these implementations are provided to provide a more thorough and complete understanding of this document. It should be understood that the accompanying drawings and implementations are for illustrative purposes only and are not intended to limit the scope of this document.

[0015] It should be understood that the steps described in the method embodiments herein may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this document is not limited in this respect.

[0016] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one case" means "at least one case"; the term "another case" means "at least one additional case"; the term "some cases" means "at least some cases". Definitions of other terms will be given in the following description.

[0017] It should be noted that the concepts of "first" and "second" mentioned in this article are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions performed by these devices, modules or units or their interdependencies.

[0018] It should be noted that the terms "one" and "more" used in this document are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0019] The names of messages or information exchanged between multiple devices in the embodiments herein are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0020] It is understandable that before using the technical solutions disclosed in each scenario in this article, users should be informed of the type, scope of use, and usage scenarios of the personal information involved in this article in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0021] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as electronic devices, applications, servers, or storage media, that perform the operations described herein, based on the prompt message.

[0022] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose whether to "agree" or "disagree" to provide personal information to the electronic device.

[0023] It is understood that the above notification and user authorization process is merely illustrative and does not limit the implementation method described in this article. Other methods that comply with relevant laws and regulations may also be applied to the implementation method described in this article.

[0024] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0025] It should be noted that the collection, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solution described in this paper comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to maintain user personal information security and network security. The collection, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solution described in this paper are all conducted with the user's knowledge and consent, and comply with relevant privacy protection regulations.

[0026] Before introducing the specific implementation of the table information update method, we can first provide an example explanation of the relevant terms and application scenarios involved.

[0027] The first table can be understood as a table product containing tens of thousands or even tens of millions of rows. It can be an online table that multiple collaborating users can interact with. Each cell in the first table can be filled with specific data, and can also be linked to a corresponding database or call other tables. When creating and / or completing the creation of the first table, the user scope can be configured. For example, the user scope can specify which users have certain permissions, or select user information, etc., and the selected users can be designated as collaborating users. Collaborating users can interact with the first table through their respective terminal devices.

[0028] In one scenario, interactions with the first table could include: inserting cells, inserting rows of data, inserting columns of data, deleting data, modifying data in cells, adding filter conditions, deleting filter conditions, etc. Inserting cells, inserting rows of data, inserting columns of data, deleting data, and modifying data in cells can be understood as adjusting the data content; adding and deleting filter conditions can be understood as adjusting the view state of the first table. Typically, adjusting data content mainly involves synchronizing incremental information to the corresponding terminal devices, while adjusting the view state can be understood as a full adjustment, requiring the synchronization of all information in the view to the corresponding terminal devices.

[0029] Based on the above, in one scenario, the table information update method can be applied to determine how to synchronize the updated data of the first table to other online clients displaying the first table when any collaborative user makes an adjustment to the first table displayed on the front end.

[0030] The following describes in detail, with reference to the accompanying drawings, an exemplary system involving the table information updating method and the table information updating device; Figure 1 This is a schematic diagram of an exemplary system 100, which includes one or more clients 101, a communication network 102, and a server 103. The server 103 can run one or more services or software applications for a table information update method. Clients 101 and server 103 can communicate via the communication network 102. The server 103 can also provide other services or software applications, which can be used in virtual or non-virtual environments. Users operating client 101 can sequentially interact with server 103 via communication network 102 using applications in client 101 to request corresponding services from server 103.

[0031] One or more clients 101 may be mobile terminals, PCs, workstations, smart screen devices, self-service terminals, various messaging devices, handheld devices, etc. Such devices can run various types and versions of software applications and operating systems. Optionally, client 101 may be configured to execute one or more applications, which may include programs that create a first form and allow interaction with the first form.

[0032] The communication network 102 can be any type of network well known to those skilled in the art, and it can use any of a variety of protocols. For example, one or more communication networks 102 can be a local area network (LAN), Ethernet, the Internet, a virtual network, a wireless network, or other networks, etc. In one scenario, the table update data of the first table by the collaborating user on client 101 can be synchronized to server 103 based on the aforementioned communication network 102, thereby enabling server 103 to synchronize the table update data to other clients 101.

[0033] Server 103 may include one or more general-purpose computers. Server 103 can run any operating system and synchronize data from user operations on the first table on client 101 to other terminals. It should be noted that... Figure 1 The exemplary system shown can be configured and operated in various ways to enable the use of the provided table update method and / or table update apparatus.

[0034] Based on the above exemplary description, we can take the first editing operation of the first table by the collaborating user on the current terminal as an example. The first table is the first table mentioned above, and it can be displayed on the current terminal. Correspondingly, in the case of collaboration, the collaborating users on other terminals can also trigger the display of the first table.

[0035] It should be noted that the collaborating users for the first table may include one or more, with some collaborating users not triggering the display of the first table and others triggering its display. If other clients have not yet displayed the first table, updates to the first table by collaborating users on the current terminal can be initially delayed in synchronization. Of course, when a collaborating user who has not yet displayed the first table triggers its display again, the updated first table can be shown. For clients that have already triggered the display of the first table, the method described in this document can be used to determine how to synchronize the table update data associated with the first edit operation to other clients.

[0036] Figure 2A flowchart of a table information update method is provided. The table update method is applicable to scenarios where the first table is edited and it is necessary to synchronize the data content associated with the editing operation to other online clients that display the first table. The table information update method can be implemented by a table information update device, and the table information synchronization update device can be integrated into a client or server that can realize human-computer interaction.

[0037] like Figure 2 As shown, the table update method includes the following steps: S210, Receive the first edit operation for the first table and obtain the data adjustment type.

[0038] The first table is a table that at least one collaborating user can collaboratively edit. The first table can be edited online by multiple collaborating users. When the first table is created or completed, user information or user permissions that allow access to or editing of the first table can be configured. For example, users with a certain permission level can be configured to access and edit the first table; users with that permission level can then act as collaborating users. Alternatively, specific users can be selected for multi-dimensional editing; these selected users can then be collaborating users.

[0039] In short, collaborating users are granted editable permissions by the creator / administrator of the primary table, enabling them to modify the table's content online with other users. This modification can include data, views, and fields, and changes are synchronized in real-time and traceable among collaborating members. When multiple users edit the same table simultaneously, changes are synchronized to the collaborators' interfaces, preventing version inconsistencies. Furthermore, in practical applications, it supports viewing the editing status of others; for example, while a collaborating user is editing, the system can directly view the cursor position and the cell being modified.

[0040] In this document, the first editing operation can be editing the data content of the first table. Optionally, data content editing can be CRUD operations on row data, column data, or cell data; data content editing can also include copying data content, adding comments, associating data with a specific user, and adding modification suggestions. The first editing operation can also be a table structure editing operation. Optionally, table structure editing operations can include field management, such as clicking the "+" in the list header to select field types, creating / copying / deleting data, or establishing linkages between tables. The first editing operation can also be condition setting, which involves operations on the entire view of the first table.

[0041] Based on the above, the first editing operation includes data adjustment operations on the first table and view adjustment operations on views related to the first table. In short, adjusting the data content of a field in the first table is a data adjustment operation; operations on conditions or related tables in the first table are view adjustment operations. The type of data adjustment varies depending on the specific first editing operation.

[0042] It should be noted that different types of editing operations can be pre-configured to correspond to different data adjustment types.

[0043] In this article, data adjustment types can include data content adjustment types and view adjustment types. Typically, the primary editing operation for data content adjustment types is adjusting the data content in the first table; in this case, to reduce data synchronization, adjustments can be made based on incremental data. View adjustment types mainly involve changes to the view state; in this case, all data in the first table needs to be adjusted.

[0044] Specifically, in the process of displaying the first table based on each client, we can take the current client triggering an operation on the first table as an example. When the first editing operation on the first table is detected, the data adjustment content related to the first editing operation can be obtained, and then the data adjustment type can be determined based on the data adjustment content.

[0045] S220. Based on the first query rate per second and the number of clients, obtain the data synchronization attribute of at least one online client.

[0046] In collaborative scenarios, when a collaborating user performs editing operations on the first table, the data needs to be synchronized to the backend interface on the server via the communication network, and then broadcast to other online clients by the backend interface on the server. This is to achieve visual communication between different clients. Figure 1 For consistency, data synchronization and updates need to be completed within a certain time frame.

[0047] Typically, the queries per second (QPS) rate of a server's backend interface constrains the real-time collaborative experience. QPS is a core performance metric that measures the number of query requests a server can process and respond to per second. It is used to evaluate query throughput and is a key basis for performance testing and capacity planning.

[0048] Backend interfaces that reconstruct views, such as those returning view structures by grouped trees, typically have high computational overhead and low QPS (Queries Per Second). Backend interfaces that return data based on differences in performance are more lightweight in terms of computation and transmission, resulting in higher QPS. When the number of online users is large, if the frontend sends all collaboration requests to the server's backend interface without control, backend interface queuing timeouts will occur, collaboration latency will become uncontrollable, and further, circuit breakers may be triggered, thus affecting collaboration reliability.

[0049] In other words, there are certain differences in QPS for different data adjustment types. The method for synchronously updating the first table can be determined based on the QPS of the backend interface used by different data adjustment types.

[0050] As mentioned above, the backend interfaces called differ depending on the data adjustment type, and consequently, the query per second (QPS) of these backend interfaces also varies. In this paper, the QPS of the backend interface that matches the data adjustment type is referred to as the first query per second.

[0051] In practical applications, the number of collaborating users associated with the first table can be multiple. These multiple collaborating users can trigger the display of the first table, or they can choose not to display it. Within the text, the displayed first table can be updated synchronously first.

[0052] In this paper, the client displaying the first table can be referred to as the online client. The data synchronization attribute for each online client can be determined based on the number of online clients. The data synchronization attribute determines when the content of the first table displayed on other online clients should be updated when the first table changes. In other words, the data synchronization attribute is the delayed synchronization attribute for synchronizing the data content corresponding to the first editing operation to other online clients. The data synchronization attribute can also be understood as a delay time; that is, the delay time for each online client can be determined separately.

[0053] Specifically, after obtaining the data adjustment type, the first query rate per second corresponding to that backend interface can be retrieved based on the backend interface corresponding to the data adjustment type. Based on the first query rate per second and the number of clients displaying the first table, the data synchronization attributes of each online client can be obtained.

[0054] S230. Based on the data synchronization attribute of at least one online client, update the content of the first table displayed by at least one online client.

[0055] For each online client, the corresponding data synchronization attributes are different, meaning that the timing of data synchronization varies.

[0056] This can be understood as follows: After determining the data synchronization attributes corresponding to each online client, the first table displayed on the online client can be updated based on the data synchronization attributes and the table update information corresponding to the first editing operation.

[0057] Based on the above approach, given the current number of collaborators N and the available access rate per second of the interface, the number of requests that can be processed per second, i.e., the number of data synchronized to the corresponding online terminals, is determined. By using random delays, the collaborative requests from N online terminals are evenly distributed within a time window, achieving the effect of adapting collaborative processing to backend capabilities. That is, each online client is treated as an independent collaborative task, generating a random delay within a time window, thereby enabling online clients to synchronize data according to the corresponding random delays. This macroscopically disperses the request time points, reducing the effect of instantaneous concurrency.

[0058] The implementation method presented in this paper, upon receiving a first edit operation on a first table, can obtain the data adjustment type associated with the first edit operation, and then retrieve the first query rate per second that matches the data adjustment type. Based on the first query rate per second, the data synchronization attribute of at least one online client associated with the first table is determined. Based on the data synchronization attribute of each online client, the table update data associated with the first edit operation is synchronized to the corresponding online client. This solves the problem in existing technologies where, when the table information presented on the front-end interface changes, a collaborative request matching the number of clients needs to be generated. After processing the collaborative request based on the back-end interface, the changed data is synchronized to other online clients. This results in multiple and frequent calls to the back-end interface, and when the back-end interface has limited processing capacity, the collaborative request processing times out, failing to achieve data synchronization—that is, the problem of limited table data synchronization. This method combines the interface capabilities of the back-end interface and the number of online clients to collaboratively determine the data synchronization attribute of each online client. Specifically, it determines the data synchronization time information of each online client within the delayed synchronization time range, and then performs data synchronization updates based on the data synchronization attribute, achieving the effect of orderly synchronizing table data to other online clients.

[0059] Based on the aforementioned implementation scenario, the statement "obtaining the data synchronization attribute of at least one online client based on the first query rate per second and the number of clients" can be further refined. For specific details, please refer to the detailed explanation in this article. Technical terms that are the same as or corresponding to those in the above scenario will not be repeated in this scenario.

[0060] like Figure 3 As shown, the steps provided by the table update method include: S310, Receive the first edit operation for the first table and obtain the data adjustment type.

[0061] In one scenario, where the first editing operation is related to the view information of the first table, the data adjustment type is related to the full collaborative adjustment type; wherein, the full collaborative adjustment type is related to the full update of the table data of the first table; where the first editing operation is related to at least part of the data content of the first table, the data adjustment type is related to the incremental collaborative adjustment type; wherein, the incremental collaborative adjustment type is related to the partial update of the data of the first table.

[0062] In the first editing operation, which involves filtering, sorting, grouping, and view labeling of the first table, the backend interface needs to obtain all the data in the first table to completely reconstruct the view grouping tree and synchronize the reconstructed view grouping tree to the online client for display. In this case, the view structure corresponding to the first table undergoes significant changes, or a complete reconstruction of the view corresponding to the first table may be required. This data adjustment type can be referred to as the first adjustment type, i.e., a full-scale collaborative adjustment type. When the first editing operation involves adding, deleting, or modifying cell data in the first table, only the incremental data needs to be adjusted; this can be considered the incremental adjustment data, i.e., the second adjustment type.

[0063] This can be understood as being able to obtain the table change information associated with the first editing operation, and based on this, the data adjustment type corresponding to the first editing operation can be determined.

[0064] For example, when the first editing operation involves filtering, sorting, grouping conditions, and view labeling information for the first table, the backend interface is typically GetViewGroup. In this case, the view structure changes significantly, and the computational and transmission costs are high; this type of data adjustment can be designated as the first adjustment type. When the first editing operation involves changing the content of cells in the first table, the corresponding backend interface could be GetViewDiff. In this case, the backend only returns the corresponding view differences, which mainly correspond to the modified cell content. Here, the computational and transmission costs are relatively low, and the corresponding data adjustment type is the second adjustment.

[0065] S320. Based on the first query rate per second, the number of clients, and the first change information, obtain the data synchronization attribute of at least one online client.

[0066] The first change information is related to the first editing operation on the first table. For example, if the data adjustment type corresponding to the first editing operation is the first adjustment type, then the first change information can be the table information of the entire first table; if the data adjustment type corresponding to the first editing operation is the second adjustment type, then the first change information can be the incremental information of the adjustment to the first table.

[0067] The reason and benefit of using the first change information as a reference factor to determine the online client data synchronization attributes in this paper is that the number of clients that can be processed per second can be determined based on the view hierarchy information or change depth information to which the first change information belongs.

[0068] The following details: "Based on the first query rate per second and the first change information, a first processing volume is obtained; wherein, the first processing volume is used to reflect the number of clients that can synchronize the first change information per second; based on the first processing volume and the number of clients, a delay time window is obtained; based on the delay time window and the first processing volume, the data synchronization attribute of at least one online client is obtained." The first processing capacity characterizes the number of clients that the backend interface can synchronize the first change information per second. The first processing capacity can be understood as the number of collaborative users that can be allowed per second, that is, the number of clients whose first change information is synchronized to the corresponding information. The delay time window is the time range within which all the first change information is synchronized to online clients. Correspondingly, the data synchronization attribute corresponds to a time point within the delay time window.

[0069] This can be understood as follows: Based on the first query rate per second and the first change information, the processing volume of information synchronization that can be handled per second can be obtained. Next, based on the first processing volume and the number of clients, the time frame within which a client base matching the number of clients can complete the synchronization of the first change information can be determined; this is the delay window for delayed information synchronization. Within this time window, a random delay is selected to determine the delayed synchronization time assigned to online clients, i.e., the data synchronization attribute.

[0070] For example, assume the data adjustment type is the first adjustment type, which corresponds to the full adjustment type that needs to be rebuilt in the level 3 complex view. The backend interface has a QPS of approximately 3, and the number of clients is N = 1000. Based on the first query rate of 3 and the level 3 complex view, the number of users that can collaborate per second can be determined (first processing volume P_dirty = 1). Based on the number of clients N = 1000 and the first processing volume P_dirty = 1, the collaboration requests of the 1000 clients can be evenly distributed over approximately 1000 seconds, i.e., the latency window is T_dirty = 1000 seconds. Based on the latency window [0, T_dirty = 1000 seconds] and the first processing volume P_dirty = 1, the number of clients that can be processed at each time point and the corresponding clients can be determined. The time point corresponding to this online client can be used as a data synchronization attribute.

[0071] Assume the data adjustment rationale is the second adjustment type, i.e., incremental collaborative adjustment. The QPS of the backend interface is approximately 100, and the number of clients is N = 1000. Based on the ratio of the first query rate per second of the backend interface to the processing efficiency of the first change information, the first processing volume is determined to be 100. Based on the ratio of the number of clients 1000 to the first processing volume 100, the time range T_dirty = 10 seconds for processing the collaborative requests corresponding to the first change information is determined, i.e., the delay time window is [0, T_dirty = 10 seconds]. The collaborative requests corresponding to the first change information can be randomly selected within this delay window. Within the delay time window, based on the first processing volume 100, the online clients corresponding to each second are randomly determined, and the time point corresponding to the online clients is used as the delay time attribute, i.e., the data synchronization attribute.

[0072] S330. For at least one online client, update the first table presented by the online client based on the online client's delayed update time and first change information.

[0073] Based on the above, the data synchronization attribute corresponding to each online client, i.e., the delayed update time information, can be determined. The starting point of the delayed time window can be either when the first edit operation is detected, or when the data synchronization attribute of each online client is determined. At any point in the delayed time window, the first table adjustment is performed on the associated online client, and the adjustment is mainly based on the first change information associated with the first edit operation.

[0074] For example, if at least two online clients need to be synchronized at each point in time within the delay time window, multiple incremental changes and / or full changes involved at the same point in time can be merged and then synchronized to other online clients.

[0075] It should be noted that in practical applications, a dual-interface channel can be established, prioritizing the incremental adjustment channel. A full reconstruction channel is then triggered when there are significant structural changes or when incremental adjustments cannot cover the changes, thus continuing table data synchronization based on the full adjustment type.

[0076] The implementation method presented in this paper, upon receiving a first edit operation on a first table, can obtain the data adjustment type associated with the first edit operation, and then retrieve the first query rate per second that matches the data adjustment type. Based on the first query rate per second, the data synchronization attribute of at least one online client associated with the first table is determined. Based on the data synchronization attribute of each online client, the table update data associated with the first edit operation is synchronized to the corresponding online client. This solves the problem in existing technologies where, when the table information presented on the front-end interface changes, a collaborative request matching the number of clients needs to be generated. After processing the collaborative request based on the back-end interface, the changed data is synchronized to other online clients, resulting in multiple and frequent calls to the back-end interface. Furthermore, when the back-end interface has limited processing capacity, this leads to timeouts in collaborative request processing, preventing data synchronization. The new method combines the interface capabilities of the back-end interface and the number of online clients to collaboratively determine the data synchronization attribute of each online client. Specifically, it obtains the data synchronization time information of each online client within the delayed synchronization time range, and then performs data synchronization updates based on the data synchronization attribute, achieving an orderly synchronization of table data to other online clients.

[0077] Figure 4 This is a schematic diagram of a table information update method provided in this paper. Based on the aforementioned embodiments, in the configuration phase and in the event of subsequent changes in the backend interface capabilities, the query rate per second corresponding to the backend interface can be adjusted, that is, the first query rate per second corresponding to the data adjustment type can be adjusted, and then the data synchronization attributes of at least one online client can be updated based on the adjusted first query rate per second. For the specific implementation, please refer to the detailed description of this embodiment. In this embodiment, the same or corresponding technical terms as those in the above embodiments will not be repeated.

[0078] like Figure 4 As shown, the method for updating table information includes the following steps: S410. In response to the reconfiguration operation of the first query rate per second, adjust the data synchronization attribute of at least one online client based on the adjusted second query rate per second.

[0079] In practical applications, if the access rate per second of the reconfigured backend interface is detected during the display of the first table, the access rate per second of the reconfigured interface can be used as the second access rate per second.

[0080] After receiving the second access rate per second, it is possible to continue to check whether the first table has been edited by collaborating users. If so, the data synchronization attributes of the online client can be re-determined based on the adjusted second query rate per second.

[0081] It should also be noted that, in the case of displaying other second tables, an event to reconfigure the second access rate per second can be received. In this case, the data synchronization attributes of the online client associated with the second table can be determined based on the second access rate per second.

[0082] The configured query rate per second is mostly stored in the configuration center, so the collaborative latency can be adjusted according to changes in backend capabilities without modifying the frontend code.

[0083] S420: Receive the second editing operation for the first table and obtain the data adjustment type.

[0084] Among them, the data adjustment type is related to the second editing operation, and the first table is a table that can be collaboratively edited by at least two collaborating users.

[0085] The second editing operation can be to adjust the data in the first table again, and this operation needs to be synchronized to the online client associated with the first table.

[0086] S430: Based on the second query rate per second and the number of clients, obtain the data synchronization attribute of at least one online client.

[0087] The second query rate per second is related to the data adjustment type, and the online client is the client that displays the first table online. This can be understood as the front-end editing operation corresponding to sending a collaborative request to the back-end, i.e., a data update request. Determining the data synchronization attributes of the collaborative request based on a dynamic adjustment mechanism can improve the effectiveness of sending collaborative requests to the back-end interface and the back-end interface's processing.

[0088] In practical applications, if the operation involves editing other tables, then the online client will be the client that displays those other tables.

[0089] This paper also fully utilizes the differentiated interface capabilities of different backend interfaces to determine the differentiated capabilities of the backend interfaces in processing the data generated by corresponding operations, thereby further shortening the collaborative convergence time and improving the efficiency of synchronization. Furthermore, this approach also ensures that the interface capabilities of the backend interfaces are fully utilized under high concurrency, thus protecting the stability of the backend interfaces and reducing timeouts and failures.

[0090] S440. Based on the data synchronization attribute of at least one online client, update the content of the first table displayed by at least one online client.

[0091] This can be understood as a way to configure backend interface capabilities, support the evolution of backend capabilities, and enable continuous collaborative experience optimization.

[0092] The implementation method described in this article provides a configurable, evolvable, and collaborative mode-differentiated dynamic collaborative traffic control solution for large-scale online collaboration, especially when the access rate per second of the backend interface is limited. This allows for controlling a lower collaboration frequency for backend interfaces that reconstruct the complete view, preventing frequent access that could lead to ineffective request processing and consequently, failure to synchronize collaborative information. For backend interfaces with incremental differences, their query rate per second can be fully utilized to achieve collaborative information synchronization with lower latency. This method can control the collaboration synchronization latency of the first table within an acceptable range for any user scale and can adjust the overall collaboration effect through configuration as backend capabilities improve, achieving dynamic adaptation between collaborative processing and backend interface capabilities.

[0093] Figure 5 This is a schematic diagram of the structure of a media data processing device provided in this article, such as... Figure 5 As shown, the device includes: a data adjustment type acquisition module 510, a data synchronization attribute acquisition module 520, and an information synchronization update module 530.

[0094] The data adjustment type acquisition module 510 is used to receive a first editing operation on a first table and obtain a data adjustment type; wherein the data adjustment type is related to the first editing operation, and the first table is a table that can be collaboratively edited by at least two collaborating users; the data synchronization attribute acquisition module 520 is used to obtain the data synchronization attribute of at least one online client based on a first query rate per second and the number of clients; wherein the first query rate per second is related to the data adjustment type, and the online client is a client that displays the first table online; the information synchronization update module 530 is used to update and display the content of the first table displayed by the at least one online client based on the data synchronization attribute of the at least one online client.

[0095] Based on the above implementation, in one scenario, the data adjustment type acquisition module includes: A first type determination unit is configured to respond to a first editing operation related to the view information of the first table, wherein the data adjustment type is a first adjustment type; wherein the first adjustment type is related to a full update of the table data of the first table; or... The second type determination unit is configured to respond to a first editing operation that is related to at least a portion of the data content of the first table, wherein the data adjustment type is a second adjustment type; wherein the second adjustment type is related to a partial data update of the first table.

[0096] Based on the above implementation, in another scenario, the data synchronization attribute acquisition module is further configured to obtain the data synchronization attribute of the at least one online client based on the first query rate per second, the number of clients, and the first change information. The first change information is related to the first editing operation on the first table.

[0097] Based on the above implementation, in another scenario, the data synchronization attribute acquisition module includes: The first processing volume determination unit is used to obtain a first processing volume based on the first query rate per second and the first change information; wherein, the first processing volume is used to reflect the number of clients that can synchronize the first change information per second; The delay time window determination unit is used to obtain a delay time window based on the first processing volume and the number of clients; The synchronization attribute determination unit is used to obtain the data synchronization attributes of the at least one online client based on the delay time window and the first processing volume.

[0098] Based on the above implementation, in another scenario, the data synchronization attribute is used to characterize the delayed update time of the first table displayed by the online client. The information synchronization update module is also used to update the first table presented by the online client based on the delayed update time of the online client and the first change information.

[0099] In addition to the above implementation, in another scenario, the device further includes a reconfiguration module for adjusting the data synchronization attributes of at least one online client based on the adjusted second query rate per second in response to a reconfiguration operation on the first query rate per second.

[0100] The implementation method presented in this paper, upon receiving a first edit operation on a first table, can obtain the data adjustment type associated with the first edit operation, and then retrieve the first query rate per second that matches the data adjustment type. Based on the first query rate per second, the data synchronization attribute of at least one online client associated with the first table is determined. Based on the data synchronization attribute of each online client, the table update data associated with the first edit operation is synchronized to the corresponding online client. This solves the problem in existing technologies where, when the table information presented on the front-end interface changes, a collaborative request matching the number of clients needs to be generated. After processing the collaborative request based on the back-end interface, the changed data is synchronized to other online clients, resulting in multiple and frequent calls to the back-end interface. Furthermore, when the back-end interface has limited processing capacity, this leads to timeouts in collaborative request processing, preventing data synchronization. The new method combines the interface capabilities of the back-end interface and the number of online clients to collaboratively determine the data synchronization attribute of each online client. Specifically, it obtains the data synchronization time information of each online client within the delayed synchronization time range, and then performs data synchronization updates based on the data synchronization attribute, achieving an orderly synchronization of table data to other online clients.

[0101] The media data processing apparatus provided herein can execute any of the table information updating methods provided herein, and has the corresponding functional modules and beneficial effects of executing the methods.

[0102] It is worth noting that the various units and modules included in the above-mentioned device are divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this document.

[0103] Figure 6 This is a schematic diagram of the structure of an electronic device provided in this article. Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 602 or a program loaded from storage device 608 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0104] Typically, the following devices can be connected to I / O interface 605: input devices 606 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 607 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 608 including, for example, magnetic tapes, hard disks, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0105] Specifically, according to this document, the processes described in the above-referenced flowchart can be implemented as computer software programs. For example, this document includes a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In such a case, the computer program can be downloaded and installed from a network via communication device 609, or installed from storage device 608, or installed from ROM 602. When the computer program is executed by processing device 601, it performs the functions defined in the methods described herein.

[0106] The names of messages or information exchanged between multiple devices in the embodiments herein are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0107] The electronic device provided herein and the table information updating method provided above belong to the same inventive concept. Technical details not described in detail herein can be found above, and the present invention has the same beneficial effects as the above.

[0108] This article provides a computer storage medium on which a computer program is stored, which, when executed by a processor, implements the table information update method provided above.

[0109] It should be noted that the computer-readable medium described above can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this document, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0110] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0111] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0112] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: Receive a first edit operation on a first table and obtain the data adjustment type; wherein, the data adjustment type is related to the first edit operation, and the first table is a table that can be collaboratively edited by at least two collaborating users; Based on the first query rate per second associated with the data adjustment type and the number of clients displaying the first table, obtain the data synchronization attribute of at least one online client; Based on the data synchronization attributes of the at least one online client, the content of the first table displayed by the at least one online client is updated.

[0113] Computer program code for performing the operations described herein may be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0114] The flowcharts and block diagrams in the accompanying figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various implementations described herein. In this respect, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the figures. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0115] The units described herein can be implemented in software or hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0116] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0117] In the context of this document, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0118] The above description is merely a preferred implementation and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure herein is not limited to technical solutions formed by specific combinations of the above-described technical features, but also includes other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed herein that have similar functions.

[0119] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Multitasking and parallel processing may be advantageous in certain contexts. Similarly, while some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this paper. Certain features described in the context of individual implementations can also be implemented in combination within a single implementation. Conversely, various features described in the context of a single implementation can also be implemented individually or in any suitable sub-combination in multiple scenarios.

[0120] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A method for updating table information, comprising: Receive a first edit operation on a first table and obtain the data adjustment type; wherein, the data adjustment type is related to the first edit operation, and the first table is a table that can be collaboratively edited by at least two collaborating users; Based on the first query rate per second and the number of clients, data synchronization attributes of at least one online client are obtained; wherein, the first query rate per second is related to the data adjustment type, and the online client is a client that displays the first table online; Based on the data synchronization attributes of the at least one online client, the content of the first table displayed by the at least one online client is updated.

2. The method according to claim 1, wherein receiving a first edit operation on the first table and obtaining the data adjustment type includes: In response to the first editing operation being related to the view information of the first table, the data adjustment type is a first adjustment type; wherein, the first adjustment type is related to a full update of the table data of the first table; or, In response to a first editing operation that relates to at least a portion of the data content of the first table, the data adjustment type is a second adjustment type; wherein the second adjustment type relates to a partial data update of the first table.

3. The method according to claim 1, wherein obtaining the data synchronization attribute of at least one online client based on the first query rate per second and the number of clients includes: Based on the first query rate per second, the number of clients, and the first change information, the data synchronization attributes of the at least one online client are obtained; The first change information is related to the first editing operation on the first table.

4. The method according to claim 3, wherein obtaining the data synchronization attributes of the at least one online client based on the first query rate per second, the number of clients, and the first change information includes: Based on the first query rate per second and the first change information, a first processing volume is obtained; wherein, the first processing volume is used to reflect the number of clients that can synchronize the first change information per second; Based on the first processing volume and the number of clients, a delay time window is obtained; Based on the delay time window and the first processing volume, the data synchronization attributes of the at least one online client are obtained.

5. The method according to any one of claims 1-4, wherein the data synchronization attribute is used to characterize the delayed update time of the first table displayed by the online client, and the step of updating the content of the first table displayed by the at least one online client based on the data synchronization attribute of the at least one online client includes: Based on the delayed update time and first change information of the online client, the first table presented by the online client is updated.

6. The method according to claim 1, further comprising: In response to the reconfiguration operation of the first query rate per second, adjust the data synchronization attributes of at least one online client based on the adjusted second query rate per second.

7. A form information updating device, comprising: A data adjustment type acquisition module is used to receive a first editing operation on a first table and obtain the data adjustment type; wherein, the data adjustment type is related to the first editing operation, and the first table is a table that can be collaboratively edited by at least two collaborating users; The data synchronization attribute acquisition module is used to obtain the data synchronization attributes of at least one online client based on a first query rate per second and the number of clients; wherein, the first query rate per second is related to the data adjustment type, and the online client is a client that displays the first table online; The information synchronization and update module is used to update and display the content of the first table displayed by the at least one online client based on the data synchronization attributes of the at least one online client.

8. An electronic device comprising: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the table information update method as described in any one of claims 1-6.

9. A storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the table information update method as described in any one of claims 1-6.

10. A computer program product comprising a computer program that, when executed by a processor, implements the table information updating method as described in any one of claims 1-6.

Images