Incremental updating method and system for layout file and electronic equipment

Abstract

The invention relates to the technical field of circuit layout design, in particular to a layout file incremental updating method and system and electronic equipment, and the method comprises the following steps: obtaining a set membership between a newly-added layout unit and each layout unit in a first layout file and layout data of the newly-added layout unit, and generating a unique identifier of the newly-added layout unit; wherein the newly added layout unit is a newly added layout unit of the client; packaging the layout data, the set membership and the unique identifier of the newly-added layout unit and the unique identifiers of other layout units associated with the set membership of the newly-added layout unit into a newly-added data file; and uploading the newly added data file to a server, sending the newly-added data file to the server side, so that the server side combines the newly-added data file to a second layout file according to unique identifiers of other layout units associated with the set membership of the newly-added layout unit in the newly-added data file and a unique identifier of a layout unit in the second layout file stored in the server side. According to the method, the newly-added layout unit is packaged into the file, incremental updating and file combination of the layout file are achieved in the mode that the unique identifier is used for matching, the situation that the non-updated part in the layout file is repeatedly uploaded and the upload time of the layout file is consumed is avoided, and the circuit layout design efficiency of the quantum chip is improved.

Description

Technical Field

[0001] This invention relates to the field of circuit layout design technology, and in particular to an incremental update method, system, and electronic device for layout files. Background Technology

[0002] With technological advancements and progress in circuit design, the number of components in circuits is increasing, leading to a greater variety of component patterns in circuit layouts. This places increasingly higher demands on EDA (Electronic Design Automation) software during layout design. When the circuit layout design of a quantum chip becomes complex, the amount of data contained in the corresponding layout file also increases. During end-to-end data updates of the layout file, most existing chip design software does not support storing cells as independent files. Instead, they typically use a full update method for layout file transmission, resulting in the repeated uploading of unupdated portions. This leads to a significant amount of unnecessary time being consumed during end-to-end transmission of the layout file, directly impacting the efficiency of quantum chip circuit layout design. Summary of the Invention

[0003] This invention provides an incremental update method, system, and electronic device for layout files, which solves the problem that unupdated parts of layout files are repeatedly uploaded, causing a large amount of unnecessary time to be consumed during end-to-end transmission of the layout file, thereby directly affecting the circuit layout design efficiency of quantum chips.

[0004] This specification provides an embodiment of an incremental update method for a layout file, including:

[0005] Obtain the parent-child relationship between the newly added map unit and each map unit in the first map file, the map data of the newly added map unit, and generate a unique identifier for the newly added map unit; wherein, the newly added map unit is a map unit newly added by the client;

[0006] The layout data, parent-child relationships, unique identifiers of the newly added layout unit, and the unique identifiers of other layout units associated with the parent-child relationships of the newly added layout unit are encapsulated into a new data file;

[0007] The newly added data file is uploaded to the server so that the server can combine the newly added data file into the second map file based on the unique identifiers of other map units associated with the parent-child relationship of the newly added map units in the newly added data file and the unique identifiers of the map units in the second map file stored on the server. The first map file and the second map file are map files with the same data but different storage locations.

[0008] Optionally, the server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationships of the layout units in the new data file and the unique identifiers of the layout units in the second layout file stored on the server, including:

[0009] The server receives the newly added data file and matches the unique identifiers of other map units associated with the parent-child relationship of the newly added map unit in the newly added data file based on the unique identifiers of each map unit in the second map file, to obtain a matching first data file; wherein, the second map file includes data files of each map unit, and the first data file is at least one;

[0010] The server combines the newly added data file and the first data file to update the map file.

[0011] Optionally, the server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationship of the layout units in the new data file and the unique identifiers of the layout units in the second layout file stored on the server, further including:

[0012] The server receives the newly added data file and constructs placeholders that have a parent-child relationship with the newly added data file based on the number of unique identifiers of other map units associated with the parent-child relationship of the newly added map unit in the newly added data file; wherein, the placeholders are used to represent the parent node and / or child node of the data file, and there is at least one placeholder;

[0013] The server matches the unique identifiers of other map units associated with the parent-child relationships of the newly added map units in the newly added data file based on the unique identifiers of each map unit in the second map file, to obtain a matching second data file; wherein, the second map file includes data files of each map unit, and there is at least one second data file;

[0014] The server replaces the placeholder with the second data file to update the second layout file.

[0015] Optionally, the unique identifier for generating the newly added map unit includes:

[0016] Use the snowflake algorithm to generate unique identifiers for newly added map units.

[0017] Optionally, after combining the newly added data file into the second layout file, the method further includes:

[0018] The server displays the layout corresponding to the combined second layout file on the layout display interface based on the layout data of each layout unit in the combined second layout file.

[0019] Optionally, after combining the newly added data file into the second layout file, the method further includes:

[0020] The client obtains the layout data of the changed layout units in the first layout file; wherein, the changed layout unit is the layout unit whose layout data has changed; wherein, the first layout file includes data files for each layout unit;

[0021] The client updates the change data file based on the layout data of the changed layout unit; wherein, the change data file is the data file of the changed layout unit; the change data file includes the layout data of the changed layout unit, parent-child relationship, unique identifier, and unique identifiers of other layout units associated with the parent-child relationship of the changed layout unit;

[0022] The client uploads the updated change data file to the server.

[0023] The server matches the unique identifiers of the changed layout units in the changed data file with the unique identifiers of each layout unit in the second layout file to obtain a third data file with the same unique identifier; wherein, there is at least one third data file;

[0024] The server replaces the third data file with the modified data file.

[0025] Optionally, the layout data of the newly added layout unit includes one or more of the following: graphic, graphic coordinates, layout unit name, and layout unit reference data.

[0026] This specification provides an incremental update system for layout files, including: a client and a server;

[0027] The client obtains the parent-child relationship between the newly added layout unit and each layout unit in the first layout file, the layout data of the newly added layout unit, and generates a unique identifier for the newly added layout unit; wherein, the newly added layout unit is a layout unit newly added by the client;

[0028] The client encapsulates the layout data, parent-child relationship, unique identifier of the newly added layout unit, and the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit into a new data file;

[0029] The client uploads the newly added data file to the server;

[0030] The server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit in the new data file and the unique identifiers of the layout units in the second layout file stored by the server. The first layout file and the second layout file are layout files with the same data but different storage locations.

[0031] An electronic device includes a memory and a processor, the memory storing computer instructions, and the processor being configured to execute the computer instructions to perform the method described above.

[0032] A storage medium, characterized in that the storage medium stores computer instructions, the computer instructions being configured to execute the method described above at runtime.

[0033] Its beneficial effects are as follows: This application first obtains the parent-child relationship between the newly added layout unit and each layout unit in the first layout file, the layout data of the newly added layout unit, and generates a unique identifier for the newly added layout unit; wherein, the newly added layout unit is a layout unit newly added by the client; then, the layout data, parent-child relationship, unique identifier, and unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit are encapsulated into a new data file; finally, the new data file is uploaded to the server, so that the server combines the new data file into the second layout file according to the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit in the new data file and the unique identifiers of the layout units in the second layout file stored on the server. This application improves the efficiency of circuit layout design for quantum chips by encapsulating the newly added layout units into files and using unique identifiers for matching to achieve incremental updates and file combinations of layout files, avoiding the repeated uploading of unupdated parts of the layout file and the consumption of layout file upload time. Attached Figure Description

[0034] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0035] Figure 1 A schematic diagram illustrating the principle of an incremental update method for layout files provided in the embodiments of this specification;

[0036] Figure 2 This specification provides a schematic diagram of a server-side layout file as illustrated in the embodiments.

[0037] Figure 3 This specification provides a schematic diagram of an example of adding a new data file;

[0038] Figure 4 This specification provides a schematic diagram illustrating the combination of newly added data files and server-side layout files in the embodiments.

[0039] Figure 5 This specification provides a schematic diagram of a newly added data file with placeholders, as illustrated in the embodiments.

[0040] Figure 6 This specification provides a schematic diagram of the newly added data files provided in the embodiments;

[0041] Figure 7 A schematic diagram of the data file E1 of the client layout unit E provided in the embodiments of this specification;

[0042] Figure 8 This specification provides a schematic diagram of the data file E2 after the layout data of the client layout unit E has changed, as shown in the embodiments of this specification.

[0043] Figure 9 This specification provides an example of a diagram showing the replacement of data file E2 in the layout file on the server.

[0044] Figure 10 A schematic diagram of an incremental update system structure for layout files provided in this specification embodiment;

[0045] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this specification;

[0046] Figure 12 This is a schematic diagram of a computer-readable storage medium provided for an embodiment of this specification. Detailed Implementation

[0047] The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0048] The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0049] It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of the invention.

[0050] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the invention or its application or use.

[0051] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

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

[0053] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0054] Currently, most chip design software on the market does not support storing layout units as independent files, and a few can only store results in small layout files. When the circuit layout design of a quantum chip is complex, the amount of data contained in the corresponding layout file also increases, causing the layout file to consume a lot of time during end-to-end transmission, directly affecting the circuit layout design efficiency of the quantum chip. To solve this technical problem, this application proposes an incremental update method, system, and electronic device for layout files.

[0055] Reference Figure 1 This specification provides a schematic diagram of an incremental update method for a layout file, comprising: S101: obtaining the parent-child relationship between the newly added layout unit and each layout unit in the first layout file, the layout data of the newly added layout unit, and generating a unique identifier for the newly added layout unit; wherein, the newly added layout unit is a layout unit newly added by the client; S102: encapsulating the layout data, parent-child relationship, unique identifier, and unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit into a new data file; S103: uploading the new data file to the server, so that the server combines the new data file into the second layout file according to the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit in the new data file and the unique identifiers of the layout units in the second layout file stored on the server, wherein, the first layout file and the second layout file are layout files with the same data but different storage locations.

[0056] In one alternative embodiment, such as Figure 2 As shown, assuming that the first layout file stored on the client and the second layout file stored on the server both contain data files A1 for layout unit A, B1 for layout unit B, C1 for layout unit C, D1 for layout unit D, and E1 for layout unit E, the client adds a new layout unit F1.

[0057] In order to upload the new layout unit F to the server and update the second layout file stored on the server, in practical applications, the client first obtains the parent-child relationship between the new layout unit F and each layout unit in the first layout file, the layout data of the new layout unit F, and generates a unique identifier X6 for the new layout unit F. Then, based on the parent-child relationship between the new layout unit F and each layout unit in the first layout file, the unique identifiers of other layout units associated with the parent-child relationship of the new layout unit F are determined. Assuming that the unique identifiers of other layout units associated with the parent-child relationship of the new layout unit F are X3, that is, the new layout unit F only has a parent node unique identifier X3 and no child node unique identifiers.

[0058] Next, the layout data, parent-child relationships, unique identifier X6, and unique identifiers X3 of other layout units associated with the parent-child relationships of the new layout unit F are encapsulated into a new data file F1 for the new layout unit F, such as... Figure 3 This diagram illustrates the creation of a new data file F1. F1 contains layout data for layout unit F, an identifier X6 for layout unit F, and a unique identifier X3 for the parent node. Finally, the client uploads the new data file F1 to the server. The server combines the new data file into a second layout file based on the unique identifiers X3 of other layout units associated with the parent-child relationship of the new layout unit F in F1, and the unique identifiers of the layout units in the second layout file stored on the server. The first and second layout files are layout files with identical data but stored in different locations. They are not limited to being stored separately on the client and server; they can also be shared between two servers or two clients, enabling updates from one server to another, or from one client to another. This method avoids the low file transfer efficiency caused by uploading the first layout file as a whole, reducing the incremental update time of the layout file. It should be noted that since the unique identifier is a 128-bit binary number, for ease of understanding, X is used as an example to represent the unique identifier here.

[0059] Optionally, the server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationship of the layout units in the new data file and the unique identifiers of the layout units in the second layout file stored by the server. This includes: the server receiving the new data file and matching the unique identifiers of other layout units associated with the parent-child relationship of the new layout units in the new data file with the unique identifiers of each layout unit in the second layout file to obtain a matching first data file; wherein, the second layout file includes data files of each layout unit, and the first data file is at least one; the server combines the new data file and the first data file to update the layout file.

[0060] In one alternative embodiment, such as Figure 4 As shown, the unique identifier of other layout units associated with the parent-child relationship of the newly added layout unit F in the newly added data file F1 is X3. Let X3 be the unique identifier of the parent node of the newly added layout unit F. Based on the unique identifier X1 of the parent node, the unique identifiers of each layout unit in the second layout file stored on the server are matched. The unique identifier X3 of the layout unit C in the data file C1 is matched. Finally, based on the matching result, the newly added data file F1 and the data file C1 are combined to realize the update of the second layout file. There is no need to manually combine the data files, which effectively improves the circuit layout design efficiency of quantum chips. At the same time, incremental updates of the layout file are realized, improving the update efficiency of the layout file.

[0061] Optionally, the server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationship of the layout units in the new data file and the unique identifiers of the layout units in the second layout file stored by the server. The method further includes: the server receiving the new data file and constructing placeholders with a parent-child relationship to the new data file based on the number of unique identifiers of other layout units associated with the parent-child relationship of the new layout units in the new data file; wherein the placeholders are used to represent the parent node and / or child node of the data file, and there is at least one placeholder; the server matching the unique identifiers of other layout units associated with the parent-child relationship of the new layout units in the new data file based on the unique identifiers of each layout unit in the second layout file to obtain a matching second data file; wherein the second layout file includes data files of each layout unit, and there is at least one second data file; and the server replacing the placeholders with the second data file to update the second layout file.

[0062] In one optional embodiment, the server receives a new data file containing a newly added layout unit, and constructs placeholders with parent-child relationships with the data file based on the number of unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit in the new data file; such as Figure 5 As shown, the unique identifier of other layout units associated with the parent-child relationship of layout unit F in the newly added data file F1 is X3. Let X3 be the unique identifier of the parent node. The server receives the data file F1 of the newly added layout unit F and constructs placeholders with parent-child relationships with the data file according to the number of unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit F in the newly added data file F1.

[0063] Since the newly added layout unit F only has the unique identifier X3 of its parent node, a parent node containing placeholders is constructed for the newly added data file F1. When the newly added data file F1 is uploaded to the server, the server will directly match the layout unit with the unique identifier X3 in the server's second layout file based on the unique identifier X3 of the parent node, that is, match the layout unit C in data file C1. Finally, based on this matching result, the placeholder of the parent node of data file F1 is replaced with that of data file C1, that is, as follows. Figure 6 As shown, when there is more than one new layout unit, there is also more than one new data file. The new data files can be uploaded to the server in parallel, avoiding the problem of low file transfer efficiency caused by uploading the layout file as a whole. This reduces the incremental update time of the layout file. At the same time, by using placeholders and matching unique identifiers, the layout file can be restored without manually combining data files, which effectively improves the circuit layout design efficiency of quantum chips.

[0064] In one alternative embodiment, encryption can be performed by setting a key in the placeholder to cover the replaced data file in the placeholder, prevent important design data from being stolen by unauthorized personnel, and improve the security of circuit layout data. It should be noted that the encryption method can be set according to the specific needs of the scenario and is not limited to key encryption.

[0065] Optionally, generating a unique identifier for the newly added map unit includes: generating a unique identifier for the newly added map unit using a snowflake algorithm.

[0066] In one optional embodiment, this application uses the snowflake algorithm to generate unique identifiers for each layout unit. It should be noted that the method of generating unique identifiers for each layout unit is not limited to the snowflake algorithm, but can also be other algorithms that can generate unique identifiers, such as UUID (Universal Unique Identifier), etc. Generating unique identifiers provides convenience for the subsequent combination of data files.

[0067] Optionally, the layout data of the newly added layout unit includes one or more of the following: graphic, graphic coordinates, layout unit name, and layout unit reference data.

[0068] In one optional embodiment, the layout data is not limited to graphics, graphic coordinates, layout unit names, and layout unit reference data. It may also include data such as transformation matrices to ensure the integrity of the layout. The content included in the layout data here is only for illustrative purposes.

[0069] In one alternative embodiment, layout unit reference data is used to enable other layout units to reference the current layout unit, avoiding the repeated creation of the same layout unit and layout unit data file, thereby improving layout design efficiency.

[0070] Optionally, after combining the newly added data file into the second layout file, the method further includes: the server displays the layout corresponding to the combined second layout file on the layout display interface based on the layout data of each layout unit in the combined second layout file.

[0071] In one optional embodiment, the server displays the combined layout file corresponding to the layout on the layout display interface based on the graphics, graphic coordinates, layout unit names, layout unit reference data, etc. in the layout data, so that users can directly observe the layout and make subsequent layout modifications.

[0072] Optionally, the newly added data file of the newly added map unit can be uploaded to the server using the HTTP protocol.

[0073] In one optional embodiment, since the HTTP protocol is used for end-to-end communication, when uploading the new data file of the newly added layout unit to the server, an HTTP request header is generated. The request header contains information such as the file node type, file identifier, version information, and file byte length of the new data file. The file identifier is used to verify whether the new data file is a project file, the version information is used for compatibility after the version of the new data file is updated, and the file byte length is used to indicate the byte length of the new data file. In this application, since the types of new data files may be different, the server needs to parse the new data file according to the data file type. The server parses the data in the new data file and restores it by identifying the file node type in the request header, thereby realizing the upload of the new data file. At the same time, when there is more than one new data file, the new data files are uploaded in parallel, which further reduces the incremental update time of the layout file and avoids the problem of low file transfer efficiency caused by uploading the first layout file as a whole.

[0074] Optionally, after combining the newly added data files into the second layout file, the method further includes: the client obtaining layout data of the changed layout units in the first layout file; wherein the changed layout units are layout units whose layout data has changed; wherein the first layout file includes data files of each layout unit; the client updating the changed data file according to the layout data of the changed layout units; wherein the changed data file is the data file of the changed layout units; the changed data file includes the layout data of the changed layout units, parent-child relationships, unique identifiers, and unique identifiers of other layout units associated with the parent-child relationships of the changed layout units; the client uploading the updated changed data file to the server; the server matching the unique identifiers of the changed layout units in the changed data file with the unique identifiers of each layout unit in the second layout file to obtain a third data file with the same unique identifier; wherein the third data file is at least one; the server replacing the third data file with the changed data file.

[0075] In one alternative embodiment, such as Figure 7 As shown, assuming the layout data of layout unit E changes, the layout data of layout unit E in the first layout file will be updated simultaneously. If the layout data of layout unit E remains unchanged, it is denoted as m1. When the layout data m1 changes to layout data m2, the client will update the layout data of layout unit E in data file E1 to m2. The updated data file is then denoted as E2. Figure 8 As shown, the client then uploads the updated data file E2 to the server; as... Figure 2 As shown, the server matches the unique identifier of layout unit E in data file E2 with the unique identifiers of each layout unit in the second layout file to obtain data file E1 with the same unique identifier. Finally, the server replaces data file E1 with data file E2, i.e. Figure 9 As shown. This application uses a matching method with the same unique identifier to achieve end-to-end updates of layout units where layout data changes, reducing the incremental update time of layout files and avoiding the problem of low file transfer efficiency caused by uploading the first layout file as a whole.

[0076] This application first obtains the parent-child relationship between the newly added layout unit and each layout unit in the first layout file, as well as the layout data of the newly added layout unit, and generates a unique identifier for the newly added layout unit; wherein, the newly added layout unit is a layout unit newly added by the client; then, the layout data, parent-child relationship, unique identifier, and unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit are encapsulated into a new data file; finally, the new data file is uploaded to the server, so that the server combines the new data file into the second layout file according to the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit in the new data file and the unique identifiers of the layout units in the second layout file stored on the server. This application improves the efficiency of circuit layout design for quantum chips by encapsulating the newly added layout units into files and using unique identifiers for matching to achieve incremental updates and file combinations of layout files, avoiding the repeated uploading of unupdated parts of the layout file and the consumption of layout file upload time.

[0077] Reference Figure 10 This specification also provides an incremental update system for layout files, comprising: a client 1 and a server 2; the client 1 includes an information acquisition module 10, a data encapsulation module 11, and a file upload module 12, and the server 2 includes a file combination module 20;

[0078] The information acquisition module 10 is used to acquire the parent-child relationship between the newly added map unit and each map unit in the first map file, the map data of the newly added map unit, and generate a unique identifier for the newly added map unit; wherein, the newly added map unit is a map unit newly added by the client;

[0079] The data encapsulation module 11 is used to encapsulate the layout data, parent-child relationship, unique identifier of the newly added layout unit, and the unique identifier of other layout units associated with the parent-child relationship of the newly added layout unit into a new data file;

[0080] The file upload module 12 is used to upload the newly added data file to the server.

[0081] The file combination module 20 is used to combine the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationship of the new layout unit in the new data file and the unique identifiers of the layout units in the second layout file stored on the server. The first layout file and the second layout file are layout files with the same data but different storage locations.

[0082] Optionally, the file combination module 20 also includes:

[0083] A unique identifier matching unit is configured to receive the newly added data file and, based on the unique identifiers of each layout unit in the second layout file, match the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit in the newly added data file to obtain a matched first data file; wherein, the second layout file includes data files of each layout unit, and the first data file is at least one;

[0084] The file combination unit is used to combine the newly added data file and the first data file to update the layout file.

[0085] Optionally, the file combination module 20 also includes:

[0086] A placeholder construction unit is configured to receive the newly added data file and construct placeholders that have a parent-child relationship with the newly added data file based on the number of unique identifiers of other map units associated with the parent-child relationship of the newly added map unit in the newly added data file; wherein, the placeholders are used to represent the parent node and / or child node of the data file, and there is at least one placeholder;

[0087] A unique identifier matching unit is used to match the unique identifiers of other map units associated with the parent-child relationship of the newly added map units in the newly added data file based on the unique identifiers of each map unit in the second map file, to obtain a matched second data file; wherein, the second map file includes data files of each map unit, and there is at least one second data file;

[0088] A placeholder replacement unit is used to replace the placeholder with the second data file to update the second layout file.

[0089] Optionally, the information acquisition module 10 includes:

[0090] The unique identifier generation unit is used to generate unique identifiers for newly added map units using the snowflake algorithm.

[0091] Optionally, the server 2 further includes:

[0092] The layout display module is used to display the layout corresponding to the combined second layout file on the layout display interface based on the layout data of each layout unit in the combined second layout file.

[0093] Optionally, the system further includes:

[0094] The client obtains the layout data of the changed layout units in the first layout file; wherein, the changed layout unit is the layout unit whose layout data has changed; wherein, the first layout file includes data files for each layout unit;

[0095] The client updates the change data file based on the layout data of the changed layout unit; wherein, the change data file is the data file of the changed layout unit; the change data file includes the layout data of the changed layout unit, parent-child relationship, unique identifier, and unique identifiers of other layout units associated with the parent-child relationship of the changed layout unit;

[0096] The client uploads the updated change data file to the server.

[0097] The server matches the unique identifiers of the changed layout units in the changed data file with the unique identifiers of each layout unit in the second layout file to obtain a third data file with the same unique identifier; wherein, there is at least one third data file;

[0098] The server replaces the third data file with the modified data file.

[0099] Optionally, the layout data of the newly added layout unit includes one or more of the following: graphic, graphic coordinates, layout unit name, and layout unit reference data.

[0100] Regarding the system in the above embodiments, the process of performing each step has been described in detail in the embodiments of the method, and will not be elaborated here.

[0101] Based on the same inventive concept, embodiments of this specification also provide an electronic device.

[0102] The following describes embodiments of the electronic device of the present invention, which can be considered as specific implementations of the methods and apparatus embodiments of the present invention described above. Details described in the embodiments of the electronic device of the present invention should be considered as supplements to the methods or apparatus embodiments described above; details not disclosed in the embodiments of the electronic device of the present invention can be implemented with reference to the methods or apparatus embodiments described above.

[0103] Reference Figure 11This is a schematic diagram of an electronic device provided as an embodiment of this specification. Refer to the following... Figure 11 The electronic device 300 according to this embodiment of the present invention will be described. Figure 11 The electronic device 300 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0104] like Figure 11 As shown, the electronic device 300 is presented in the form of a general-purpose computing device. The components of the electronic device 300 may include, but are not limited to: at least one processing unit 310, at least one storage unit 320, a bus 330 connecting different device components (including storage unit 320 and processing unit 310), a display unit 340, etc.

[0105] The storage unit stores program code that can be executed by the processing unit 310, causing the processing unit 310 to perform the steps described in the processing method section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 310 can perform, for example... Figure 1 The steps are shown.

[0106] The storage unit 320 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 3201 and / or a cache storage unit 3202, and may further include a read-only memory unit (ROM) 3203.

[0107] The storage unit 320 may also include a program / utility 3204 having a set (at least one) of program modules 3205, such program modules 3205 including but not limited to: operating devices, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0108] Bus 330 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0109] Electronic device 300 can also communicate with one or more external devices 400 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with the electronic device 300, and / or with any device that enables the electronic device 300 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 350. Furthermore, electronic device 300 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 360. Network adapter 360 can communicate with other modules of electronic device 300 via bus 330. It should be understood that, although... Figure 11 As not shown, other hardware and / or software modules may be used in conjunction with electronic device 300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID devices, tape drives, and data backup storage devices.

[0110] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described in this invention can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this invention can be embodied in the form of a software product, which can be stored in a computer-readable storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, or network device, etc.) to execute the method described above according to this invention. When the computer instructions are executed by a data processing device, the computer-readable medium is able to implement the method described above, i.e., as follows: Figure 1 The method shown.

[0111] Reference Figure 12 This is a schematic diagram of a computer-readable storage medium provided for an embodiment of this specification.

[0112] accomplish Figure 1The computer instructions of the method shown can be stored on one or more computer-readable media. A computer-readable medium can be a readable signal medium or a readable storage medium. A readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: an electrical connection having one or more wires, a portable 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 devices, magnetic storage devices, or any suitable combination thereof.

[0113] The computer-readable storage medium may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The readable storage medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution device, apparatus, or apparatus. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0114] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0115] In summary, this invention can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that in practice, general-purpose data processing devices such as microprocessors or digital signal processors (DSPs) can be used to implement some or all of the functions of some or all of the components according to the embodiments of the invention. The invention can also be implemented as a device or apparatus program (e.g., a computer program and computer program product) for performing part or all of the methods described herein. Such programs implementing the invention can be stored on a computer-readable medium or can take the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0116] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the present invention is not inherently related to any specific computer, virtual device, or electronic device, and various general-purpose devices can also implement the present invention. The above descriptions are merely specific embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

[0117] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.

[0118] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for incremental updating a map file, characterized in that, include: Obtain the parent-child relationship between the newly added map unit and each map unit in the first map file, the map data of the newly added map unit, and generate a unique identifier for the newly added map unit; wherein, the newly added map unit is a map unit newly added by the client; The layout data, parent-child relationships, unique identifiers of the newly added layout unit, and the unique identifiers of other layout units associated with the parent-child relationships of the newly added layout unit are encapsulated into a new data file; The newly added data file is uploaded to the server so that the server can combine the newly added data file into the second map file based on the unique identifiers of other map units associated with the parent-child relationship of the newly added map units in the newly added data file and the unique identifiers of the map units in the second map file stored on the server. The first map file and the second map file are map files with the same data but different storage locations.

2. The method as described in claim 1, characterized in that, The server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationships of the layout units in the new data file and the unique identifiers of the layout units in the second layout file stored on the server, including: The server receives the newly added data file and matches the unique identifiers of other map units associated with the parent-child relationship of the newly added map unit in the newly added data file based on the unique identifiers of each map unit in the second map file, to obtain a matching first data file; wherein, the second map file includes data files of each map unit, and the first data file is at least one; The server combines the newly added data file and the first data file to update the map file.

3. The method as described in claim 1, characterized in that, The server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationships of the layout units in the new data file and the unique identifiers of the layout units in the second layout file stored on the server. The method also includes: The server receives the newly added data file and constructs placeholders that have a parent-child relationship with the newly added data file based on the number of unique identifiers of other map units associated with the parent-child relationship of the newly added map unit in the newly added data file; wherein, the placeholders are used to represent the parent node and / or child node of the data file, and there is at least one placeholder; The server matches the unique identifiers of other map units associated with the parent-child relationships of the newly added map units in the newly added data file based on the unique identifiers of each map unit in the second map file, to obtain a matching second data file; wherein, the second map file includes data files of each map unit, and there is at least one second data file; The server replaces the placeholder with the second data file to update the second layout file.

4. The method as described in claim 1, characterized in that, The unique identifier for generating the newly added map unit includes: Use the snowflake algorithm to generate unique identifiers for newly added map units.

5. The method as described in claim 1, characterized in that, After combining the newly added data file into the second layout file, the method further includes: The server displays the layout corresponding to the combined second layout file on the layout display interface based on the layout data of each layout unit in the combined second layout file.

6. The method as described in claim 1, characterized in that, After combining the newly added data file into the second layout file, the method further includes: The client obtains the layout data of the changed layout units in the first layout file; wherein, the changed layout unit is the layout unit whose layout data has changed; wherein, the first layout file includes data files for each layout unit; The client updates the change data file based on the layout data of the changed layout unit; wherein, the change data file is the data file of the changed layout unit; the change data file includes the layout data of the changed layout unit, parent-child relationship, unique identifier, and unique identifiers of other layout units associated with the parent-child relationship of the changed layout unit; The client uploads the updated change data file to the server. The server matches the unique identifiers of the changed layout units in the changed data file with the unique identifiers of each layout unit in the second layout file to obtain a third data file with the same unique identifier; wherein, there is at least one third data file; The server replaces the third data file with the modified data file.

7. The method as described in claim 1, characterized in that, The layout data of the newly added layout unit includes one or more of the following: graphic, graphic coordinates, layout unit name, and layout unit reference data.

8. An incremental update system for map files, characterized in that... ,include: Client and server; The client obtains the parent-child relationship between the newly added layout unit and each layout unit in the first layout file, the layout data of the newly added layout unit, and generates a unique identifier for the newly added layout unit; wherein, the newly added layout unit is a layout unit newly added by the client; The client encapsulates the layout data, parent-child relationship, unique identifier of the newly added layout unit, and the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit into a new data file; The client uploads the newly added data file to the server; The server combines the new data file into the second layout file based on the unique identifiers of other layout units associated with the parent-child relationship of the newly added layout unit in the new data file and the unique identifiers of the layout units in the second layout file stored by the server. The first layout file and the second layout file are layout files with the same data but different storage locations.

9. An electronic device, characterized in that, The method includes a memory and a processor, wherein the memory stores computer instructions and the processor is configured to execute the computer instructions to perform the method according to any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium stores computer instructions that are configured to execute the method described in any one of claims 1 to 7 when run.

Images