Method for managing public data dictionary, server, remote repository and storage medium

Abstract

The application discloses a public data dictionary management method, a server, a remote warehouse and a storage medium. The management method comprises the following steps: sending a copy request instruction of a public dictionary warehouse to a remote warehouse; receiving a copy of the public dictionary warehouse sent by the remote warehouse; modifying the public data dictionary in the copy of the public dictionary warehouse to obtain a modified public data dictionary; sending a merging request to the remote warehouse; receiving an approval result of the merging request sent by the remote warehouse; and in the case that the approval result is an approval passing result, merging the modified public data dictionary into the remote warehouse to update the public dictionary warehouse of the remote warehouse. The application can reduce the possibility of resource waste caused by compilation failure of other modules when the server modifies the public data dictionary.

Description

Technical Field

[0001] This application relates to the field of data dictionary management technology, specifically to a management method for a public data dictionary, a server, a remote repository, and a storage medium. Background Technology

[0002] Data dictionaries are a common data storage format in Simulink. They provide the ability to store data types, parameters, and signals in a database file. Module development often involves the interaction of various data types; therefore, to simplify the development process, common data is stored in a common data dictionary, allowing each module to load this common data at runtime. However, if a module needs to modify common data in the common data dictionary during development, it may cause other modules using that common data to fail to compile, resulting in wasted resources. Therefore, existing technologies suffer from the problem of resource waste in other modules during development due to individual modules modifying common data. Summary of the Invention

[0003] The purpose of this application is to provide a management method, server, remote repository, and storage medium for a public data dictionary, in order to solve the problem in the prior art where the modification of public data by individual modules leads to resource waste in other modules during development.

[0004] To achieve the above objectives, a first aspect of this application provides a method for managing a public data dictionary, applied to a server, the server communicating with a remote repository, the remote repository including a public dictionary repository, the management method comprising:

[0005] Send a copy request command for the public dictionary repository to the remote repository;

[0006] Receive a copy of the public dictionary repository sent from the remote repository;

[0007] Modify the public data dictionary in the copy of the public dictionary repository to obtain the modified public data dictionary;

[0008] Send a merge request to the remote repository;

[0009] Receive the approval result of the merge request sent by the remote warehouse;

[0010] If the approval result is "approved", the modified public data dictionary will be merged into the remote repository to update the public dictionary repository in the remote repository.

[0011] In this embodiment of the application, the remote repository further includes a model repository, and before receiving the approval result of the merge request sent by the remote repository, it also includes:

[0012] Send a copy request command for the model repository to the remote repository;

[0013] Receive a copy of the model repository sent from the remote repository;

[0014] Models in the model repository are compiled via pipeline based on a copy of the public dictionary repository;

[0015] Determine the compilation results of the models in the copy of the model repository;

[0016] Send the compilation results to the remote repository.

[0017] In this embodiment of the application, the management method further includes:

[0018] Determine whether to modify the model in the copy of the model repository;

[0019] If a model in a copy of the model repository is modified, determine the modified model;

[0020] Upload the modified model to the remote repository to update the model repository in the remote repository.

[0021] In this embodiment of the application, the management method further includes:

[0022] Determine whether modifications to the public data dictionary comply with preset management permissions;

[0023] If the modifications to the public data dictionary comply with the preset management permissions, the modified public data dictionary is obtained, and a merge request is sent to the remote repository.

[0024] Modifications to the public data dictionary are not permitted if they do not comply with the preset management permissions.

[0025] In this embodiment of the application, the management method further includes:

[0026] If the approval result is "approval failed", stop sending merge requests.

[0027] A second aspect of this application provides a method for managing a public data dictionary, applied to a remote repository that communicates with a server. The remote repository includes a public dictionary repository. The management method includes:

[0028] Receive a copy request command from the server for the public dictionary repository;

[0029] Send a copy of the public dictionary repository to the server;

[0030] Receive the merge request sent by the server;

[0031] Send the approval result of the merge request to the server;

[0032] Receive the server's merge operation;

[0033] Update the public dictionary repository based on the merge operation;

[0034] The merge operation is the process by which the server merges the modified public data dictionary into the remote repository when the approval result is approved. The modified public data dictionary is obtained by the server modifying the public data dictionary in the copy of the public dictionary repository.

[0035] In this embodiment of the application, the remote repository also includes a model repository, and before sending the approval result of the merge request to the server, it also includes:

[0036] Receive a copy request command for the model repository sent by the server;

[0037] Send a copy of the model repository to the server;

[0038] Receive the compilation results sent by the server;

[0039] The compilation result is determined by the server based on a copy of the public dictionary repository and by pipelined compilation of the model in the copy of the model repository.

[0040] A third aspect of this application provides a server, comprising:

[0041] The memory is configured to store instructions; and

[0042] The processor is configured to retrieve instructions from memory and, when executing instructions, to implement the aforementioned common data dictionary management method.

[0043] A fourth aspect of this application provides a remote warehouse, comprising:

[0044] The memory is configured to store instructions; and

[0045] The processor is configured to retrieve instructions from memory and, when executing instructions, to implement the aforementioned common data dictionary management method.

[0046] A fifth aspect of this application provides a machine-readable storage medium storing instructions that cause a machine to execute the aforementioned public data dictionary management method.

[0047] The above technical solution involves sending a copy request instruction for the public dictionary repository to a remote repository, and then receiving the copy of the public dictionary repository from the remote repository. The public data dictionary in the copy of the public dictionary repository is then modified to obtain the modified public data dictionary. A merge request is then sent to the remote repository, and the approval result of the merge request is received from the remote repository. Finally, if the approval result is successful, the modified public data dictionary is merged into the remote repository to update the public dictionary repository in the remote repository. This application, by merging the modified public data dictionary into the remote repository to update the public dictionary repository in the case of an approved result, can reduce the possibility of resource waste caused by other modules failing to compile when the public data dictionary is modified on the server.

[0048] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0049] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings:

[0050] Figure 1 The flowchart illustrating a method for managing a public data dictionary according to an embodiment of this application is shown schematically.

[0051] Figure 2 The flowchart illustrating a method for managing a public data dictionary according to another embodiment of this application is shown schematically;

[0052] Figure 3 The illustration schematically shows a timing diagram of a public data dictionary management method according to a specific embodiment of this application;

[0053] Figure 4 This schematic diagram illustrates a structural block diagram of a server according to an embodiment of the present application;

[0054] Figure 5 A schematic diagram of a remote warehouse according to an embodiment of this application is shown. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0056] It should be noted that if the embodiments of this application involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of the components in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indicators will also change accordingly.

[0057] Furthermore, if the embodiments of this application involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0058] Figure 1 A flowchart illustrating a method for managing a public data dictionary according to an embodiment of this application is shown schematically. Figure 1 As shown, one embodiment of this application provides a method for managing a public data dictionary, applied to a server. The server communicates with a remote repository, which includes a public dictionary repository. The management method may include the following steps:

[0059] Step 101: Send a copy request command for the public dictionary repository to the remote repository;

[0060] Step 102: Receive a copy of the public dictionary repository sent by the remote repository;

[0061] Step 103: Modify the public data dictionary in the copy of the public dictionary repository to obtain the modified public data dictionary;

[0062] Step 104: Send a merge request to the remote repository;

[0063] Step 105: Receive the approval result of the merge request sent by the remote warehouse;

[0064] Step 106: If the approval result is "approved", merge the modified public data dictionary into the remote repository to update the public dictionary repository in the remote repository.

[0065] In this embodiment, the server communicates with a remote repository. The remote repository includes a public dictionary repository and a model repository. First, the server can send a copy request instruction for the public dictionary repository to the remote repository, and then receive the copy of the public dictionary repository sent by the remote repository. To meet the server's development needs, the server can modify the public data dictionary in the copy of the public dictionary repository. When the server needs to modify the public data dictionary in the copy of the public dictionary repository, it modifies the public data dictionary in the copy of the public dictionary repository and obtains the modified public data dictionary. Further, since the server's permissions only include sharing copies of the public dictionary repository and modifying copies of the public dictionary repository, when the server needs to modify the public dictionary repository in the remote repository, it needs to send a merge request to the remote repository and then receive the approval result of the merge request sent by the remote repository. If the approval result is approved, the server can then merge the modified public data dictionary into the remote repository, thereby updating the public dictionary repository in the remote repository. It should be noted that the process of merging the modified public data dictionary into the remote repository means that the modified public data dictionary overwrites the original public data dictionary in the remote repository.

[0066] The above technical solution involves sending a copy request instruction for the public dictionary repository to a remote repository, and then receiving the copy of the public dictionary repository from the remote repository. The public data dictionary in the copy of the public dictionary repository is then modified to obtain the modified public data dictionary. A merge request is then sent to the remote repository, and the approval result of the merge request is received from the remote repository. Finally, if the approval result is successful, the modified public data dictionary is merged into the remote repository to update the public dictionary repository in the remote repository. This application, by merging the modified public data dictionary into the remote repository to update the public dictionary repository in the case of an approved result, can reduce the possibility of resource waste caused by other modules failing to compile when the public data dictionary is modified on the server.

[0067] In this embodiment of the application, the management method may further include:

[0068] Determine whether modifications to the public data dictionary comply with preset management permissions;

[0069] If the modifications to the public data dictionary comply with the preset management permissions, the modified public data dictionary is obtained, and a merge request is sent to the remote repository.

[0070] Modifications to the public data dictionary are not permitted if they do not comply with the preset management permissions.

[0071] Specifically, to ensure the quality of modifications to the public data dictionary, the server needs to determine whether the modifications comply with preset management permissions. These preset management permissions can be determined based on actual circumstances; they are the permission settings for whether the server should modify the public data dictionary according to modification instructions sent by the terminal. If the modifications to the public data dictionary comply with the preset management permissions, the server can obtain the modified public data dictionary and send a merge request to the remote repository. If the modifications to the public data dictionary do not comply with the preset management permissions, the server will not allow modification of the public data dictionary. This ensures the quality of modifications to the public data dictionary.

[0072] In this embodiment of the application, the management method may further include:

[0073] If the approval result is "approval failed", stop sending merge requests.

[0074] Specifically, when the server needs to modify the public dictionary repository in the remote repository, it needs to send a merge request to the remote repository and then receive the approval result of the merge request from the remote repository. If the approval result is unsuccessful, the server can stop sending merge requests to reduce resource waste.

[0075] In this embodiment of the application, the remote repository further includes a model repository, and before receiving the approval result of the merge request sent by the remote repository, it may also include:

[0076] Send a copy request command for the model repository to the remote repository;

[0077] Receive a copy of the model repository sent from the remote repository;

[0078] Models in the model repository are compiled via pipeline based on a copy of the public dictionary repository;

[0079] Determine the compilation results of the models in the copy of the model repository;

[0080] Send the compilation results to the remote repository.

[0081] Specifically, the remote repository includes a public dictionary repository and a model repository. The server can send a copy request command for the model repository to the remote repository and receive a copy of the model repository from the remote repository. Based on the copy of the public dictionary repository and the modified public data dictionary, the server can compile the models in the copy of the model repository through a pipeline and determine the compilation result of the models in the copy of the model repository, i.e., determine whether the models in the copy of the model repository have been compiled successfully. The pipeline is an executor that can compile the models in the copy of the model repository based on the copy of the public dictionary repository and the modified public data dictionary. After determining the compilation result of the models in the copy of the model repository, the server can send the compilation result to the remote repository so that the remote repository can use the compilation result to determine whether to approve the server's merge request.

[0082] In this embodiment of the application, the management method may further include:

[0083] Determine whether to modify the model in the copy of the model repository;

[0084] If a model in a copy of the model repository is modified, determine the modified model;

[0085] Upload the modified model to the remote repository to update the model repository in the remote repository.

[0086] Specifically, the remote repository includes a public dictionary repository and a model repository. The server can send a copy request command for the model repository to the remote repository and receive a copy of the model repository sent by the remote repository. The server can determine whether it needs to modify the models in the copy of the model repository. If it needs to modify the models in the copy of the model repository, the server determines the modified models and uploads the modified models to the remote repository to update the model repository of the remote repository.

[0087] Figure 2 A flowchart illustrating a method for managing a public data dictionary according to another embodiment of this application is shown schematically. Figure 2 As shown in another embodiment of this application, a method for managing a public data dictionary is provided, applied to a remote repository. The remote repository communicates with a server, and the remote repository includes a public dictionary repository. The management method may include the following steps:

[0088] Step 201: Receive the copy request instruction for the public dictionary repository sent by the server;

[0089] Step 202: Send a copy of the public dictionary repository to the server;

[0090] Step 203: Receive the merge request sent by the server;

[0091] Step 204: Send the approval result of the merge request to the server;

[0092] Step 205: Receive the merge operation from the server;

[0093] Step 206: Update the public dictionary repository based on the merge operation;

[0094] The merge operation is the process by which the server merges the modified public data dictionary into the remote repository when the approval result is approved. The modified public data dictionary is obtained by the server modifying the public data dictionary in the copy of the public dictionary repository.

[0095] In this embodiment, the remote repository communicates with the server. The remote repository includes a public dictionary repository and a model repository. First, the remote repository can receive a copy request instruction for the public dictionary repository sent by the server, and then send a copy of the public dictionary repository to the server. To meet the server's development needs, the server can modify the public data dictionary in the copy of the public dictionary repository. When the server needs to modify the public data dictionary in the copy of the public dictionary repository, it modifies the public data dictionary in the copy of the public dictionary repository and obtains the modified public data dictionary. Further, since the server's permissions only include sharing the copy of the public dictionary repository and modifying the copy of the public dictionary repository, the server needs to send a merge request to the remote repository when it needs to modify the public dictionary repository in the remote repository. The remote repository can receive the merge request sent by the server and determine the approval result of the merge request. If the approval result is approved, the remote repository can receive the merge operation from the server, and thus update the public dictionary repository according to the merge operation. The merge operation is the operation by which the server merges the modified public data dictionary into the remote repository when the approval result is approved. The modified public data dictionary is obtained by modifying the public data dictionary in the public dictionary repository copy on the server.

[0096] The above technical solution receives a copy request instruction for the public dictionary repository from the server, and then sends a copy of the public dictionary repository to the server. Subsequently, it receives a merge request from the server and sends the approval result of the merge request to the server. Finally, it receives the server's merge operation and updates the public dictionary repository according to the merge operation. This application can reduce the possibility of resource waste caused by other modules failing to compile when the server modifies the public data dictionary.

[0097] In this embodiment of the application, the remote repository further includes a model repository, and may further include the following before sending the approval result of the merge request to the server:

[0098] Receive a copy request command for the model repository sent by the server;

[0099] Send a copy of the model repository to the server;

[0100] Receive the compilation results sent by the server;

[0101] The compilation result is determined by the server based on a copy of the public dictionary repository and by pipelined compilation of the model in the copy of the model repository.

[0102] Specifically, the remote repository includes a public dictionary repository and a model repository. The remote repository can receive a copy request instruction for the model repository from the server and send a copy of the model repository to the server. Further, the remote repository can receive the compilation results sent by the server. The compilation results are determined by the server through pipelined compilation of the models in the copy of the model repository based on the copy of the public dictionary repository and the modified public data dictionary, including successful compilation results and compilation failure results. When the compilation result is successful, the remote repository can determine that the approval result of the merge request is approved. When the compilation result is a compilation failure, the remote repository can determine that the approval result of the merge request is rejected. This allows the remote repository to determine the approval result of the merge request.

[0103] Figure 3 The illustration schematically shows a timing diagram of a public data dictionary management method according to a specific embodiment of this application. For example... Figure 3 As shown, the server can send a copy request command for the public dictionary repository to the remote repository, and the remote repository can send a copy of the public dictionary repository to the server. The server modifies the public data dictionary in the copy of the public dictionary repository and determines whether the modification of the public data dictionary complies with preset management permissions. If the modification of the public data dictionary complies with the preset management permissions, the server obtains the modified public data dictionary and sends a merge request to the remote repository. Simultaneously, the server can send a copy request command for the model repository to the remote repository. The remote repository can send a copy of the model repository to the server. Based on the copy of the public dictionary repository, the server compiles the models in the copy of the model repository through a pipeline, determines the compilation result of the models in the copy of the model repository, and then sends the compilation result to the remote repository. The remote repository determines the approval result of the merge request based on the compilation result and sends the approval result to the server. If the approval result is negative, the server stops sending merge requests; if the approval result is positive, the server can merge the modified public data dictionary into the remote repository. The remote repository receives the merge operation from the server and updates the public dictionary repository accordingly.

[0104] Figure 4 A schematic block diagram of a server according to an embodiment of this application is shown. Figure 4As shown in the illustration, this application provides a server that may include:

[0105] Memory 410 is configured to store instructions; and

[0106] Processor 420 is configured to retrieve instructions from memory 410 and, when executing instructions, to implement the aforementioned common data dictionary management method.

[0107] Specifically, in this embodiment of the application, the processor 420 can be configured to:

[0108] Send a copy request command for the public dictionary repository to the remote repository;

[0109] Receive a copy of the public dictionary repository sent from the remote repository;

[0110] Modify the public data dictionary in the copy of the public dictionary repository to obtain the modified public data dictionary;

[0111] Send a merge request to the remote repository;

[0112] Receive the approval result of the merge request sent by the remote warehouse;

[0113] If the approval result is "approved", the modified public data dictionary will be merged into the remote repository to update the public dictionary repository in the remote repository.

[0114] Furthermore, the processor 420 can also be configured as follows:

[0115] Send a copy request command for the model repository to the remote repository;

[0116] Receive a copy of the model repository sent from the remote repository;

[0117] Models in the model repository are compiled via pipeline based on a copy of the public dictionary repository;

[0118] Determine the compilation results of the models in the copy of the model repository;

[0119] Send the compilation results to the remote repository.

[0120] Furthermore, the processor 420 can also be configured as follows:

[0121] Determine whether to modify the model in the copy of the model repository;

[0122] If a model in a copy of the model repository is modified, determine the modified model;

[0123] Upload the modified model to the remote repository to update the model repository in the remote repository.

[0124] Furthermore, the processor 420 can also be configured as follows:

[0125] Determine whether modifications to the public data dictionary comply with preset management permissions;

[0126] If the modifications to the public data dictionary comply with the preset management permissions, the modified public data dictionary is obtained, and a merge request is sent to the remote repository.

[0127] Modifications to the public data dictionary are not permitted if they do not comply with the preset management permissions.

[0128] Furthermore, the processor 420 can also be configured as follows:

[0129] If the approval result is "approval failed", stop sending merge requests.

[0130] The above technical solution involves sending a copy request instruction for the public dictionary repository to a remote repository, and then receiving the copy of the public dictionary repository from the remote repository. The public data dictionary in the copy of the public dictionary repository is then modified to obtain the modified public data dictionary. A merge request is then sent to the remote repository, and the approval result of the merge request is received from the remote repository. Finally, if the approval result is successful, the modified public data dictionary is merged into the remote repository to update the public dictionary repository in the remote repository. This application, by merging the modified public data dictionary into the remote repository to update the public dictionary repository in the case of an approved result, can reduce the possibility of resource waste caused by other modules failing to compile when the public data dictionary is modified on the server.

[0131] Figure 5 A schematic diagram illustrating the structure of a remote warehouse according to an embodiment of this application is shown. Figure 5 As shown in the figure, this application embodiment provides a remote warehouse, which may include:

[0132] Memory 510 is configured to store instructions; and

[0133] Processor 520 is configured to retrieve instructions from memory 510 and, when executing instructions, to implement the aforementioned common data dictionary management method.

[0134] Specifically, in this embodiment of the application, the processor 520 can be configured to:

[0135] Receive a copy request command from the server for the public dictionary repository;

[0136] Send a copy of the public dictionary repository to the server;

[0137] Receive the merge request sent by the server;

[0138] Send the approval result of the merge request to the server;

[0139] Receive the server's merge operation;

[0140] Update the public dictionary repository based on the merge operation;

[0141] The merge operation is the process by which the server merges the modified public data dictionary into the remote repository when the approval result is approved. The modified public data dictionary is obtained by the server modifying the public data dictionary in the copy of the public dictionary repository.

[0142] Furthermore, the processor 520 can also be configured as follows:

[0143] Receive a copy request command for the model repository sent by the server;

[0144] Send a copy of the model repository to the server;

[0145] Receive the compilation results sent by the server;

[0146] The compilation result is determined by the server based on a copy of the public dictionary repository and by pipelined compilation of the model in the copy of the model repository.

[0147] The above technical solution receives a copy request instruction for the public dictionary repository from the server, and then sends a copy of the public dictionary repository to the server. Subsequently, it receives a merge request from the server and sends the approval result of the merge request to the server. Finally, it receives the server's merge operation and updates the public dictionary repository according to the merge operation. This application can reduce the possibility of resource waste caused by other modules failing to compile when the server modifies the public data dictionary.

[0148] This application also provides a machine-readable storage medium storing instructions that cause a machine to execute the above-described public data dictionary management method.

[0149] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0150] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0151] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0152] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0153] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0154] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0155] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0156] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0157] The above are merely embodiments of this application and are 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 management method of a public data dictionary, characterized by, The application is to a server that communicates with a remote repository, the remote repository including a public dictionary repository and a model repository, and the management method includes: Send a copy request instruction for the public dictionary repository to the remote repository; Receive a copy of the public dictionary repository sent by the remote repository; Modify the public data dictionary in the copy of the public dictionary repository to obtain the modified public data dictionary; Send a merge request to the remote repository; Receive the approval result of the merge request sent by the remote warehouse; If the approval result is approved, the modified public data dictionary will be merged into the remote repository to update the public dictionary repository of the remote repository; The process of receiving the approval result of the merge request sent by the remote warehouse includes, prior to the following: Send a copy request instruction for the model repository to the remote repository; Receive a copy of the model repository sent by the remote repository; Based on a copy of the public dictionary repository, models in the copy of the model repository are compiled via a pipeline; Determine the compilation results of the models in the copy of the model repository; The compilation result is sent to the remote repository. If the compilation result is successful, the remote repository determines that the approval result of the merge request is approved. If the compilation result is unsuccessful, the remote repository determines that the approval result of the merge request is unsuccessful.

2. The management method according to claim 1, characterized in that, The management method also includes: Determine whether to modify the model in the copy of the model repository; In the case of modifying a model in a copy of the model repository, determine the modified model; The modified model is uploaded to the remote repository to update the model repository in the remote repository.

3. The management method according to claim 1, characterized by, The management method also includes: Determine whether the modification to the public data dictionary complies with the preset management permissions; If the modification of the public data dictionary complies with the preset management permissions, the modified public data dictionary is obtained, and a merge request is sent to the remote repository; Modifications to the public data dictionary are not permitted if they do not comply with preset management permissions.

4. The management method according to claim 1, characterized by, The management method also includes: If the approval result is "approval failed", then stop sending the merge request.

5. A management method of a public data dictionary, characterized by, This method is applied to a remote repository that communicates with a server. The remote repository includes a public dictionary repository and a model repository. Receive a copy request instruction for the public dictionary repository sent by the server; Send a copy of the public dictionary repository to the server; Receive the merge request sent by the server; The approval result of the merge request is sent to the server; Receive the merge operation from the server; Update the public dictionary repository according to the merge operation; The merging operation is the operation by which the server merges the modified public data dictionary into the remote repository when the approval result is approved. The modified public data dictionary is obtained by the server after modifying the public data dictionary in the copy of the public dictionary repository. The step of sending the approval result of the merge request to the server further includes: Receive a copy request instruction for the model repository sent by the server; Send a copy of the model repository to the server; The server receives the compilation result sent by the server. If the compilation result is a successful compilation result, the server determines the approval result of the merge request as an approved result. If the compilation result is a failed compilation result, the server determines the approval result of the merge request as an unapproved result. The compilation result is determined by the server based on the copy of the public dictionary repository and by pipelined compilation of the models in the copy of the model repository.

6. A server, characterized by include: The memory is configured to store instructions; as well as A processor is configured to retrieve the instructions from the memory and, when executing the instructions, to implement the method for managing a public data dictionary according to any one of claims 1 to 4.

7. A remote repository, characterized by include: The memory is configured to store instructions; as well as The processor is configured to retrieve the instructions from the memory and, when executing the instructions, to implement the public data dictionary management method according to claim 5.

8. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores instructions for causing the machine to perform the management method of the public data dictionary according to any one of claims 1 to 5.

Images