Geometric modeling kernel data management method, device, equipment, medium and CAD modeling method

Abstract

A geometry modeling kernel data management method, device, equipment, medium and CAD modeling method, relating to the field of CAD technology, the data management method comprising: in response to a modeling operation interface calling instruction of an upper-layer application, constructing a modeling session context in a geometry modeling kernel, for managing modeling operation interface configuration data and / or modeling algorithm interface configuration data corresponding to a user of the upper-layer application; wherein the modeling operation interface configuration is configured to maintain global modeling operation configuration set in the modeling session context, the modeling algorithm interface configuration is configured to maintain local operation configuration under a current calculation state, and the local operation configuration is passed in calling between modeling algorithm interfaces; in response to a modeling algorithm interface calling instruction, managing modeling result data associated with the modeling session context based on a pre-set model database. The application avoids repeated development of upper-layer applications of a CAD application system and data interference or conflict of multi-user concurrent requests.

Description

Technical Field

[0001] This invention relates to the field of CAD technology, and in particular to a geometric modeling kernel data management method, apparatus, device and medium, and CAD modeling method. Background Technology

[0002] The geometric modeling kernel is a core component of CAD application systems. In related technologies, the system adopts a stateless kernel architecture, where the CAD application software (such as SolidWorks and AutoCAD) acts as the upper-level caller, using the geometric modeling kernel to generate model data by calling its internal modeling algorithm interfaces, thereby completing the creation, editing, and management of 3D models and model data. Its limitations are: For each call to a modeling algorithm interface, the kernel does not maintain a customized operation configuration (including modeling accuracy, tolerance, and units) or the result data object generated by the modeling algorithm interface for the upper-layer caller. Instead, it maintains a globally unified operation configuration and directly returns the generated result data object to the upper-layer caller after the interface call. In other words, the kernel is not responsible for the subsequent management of these result data objects. The upper-layer caller needs to receive, store, and manage all model data returned by the kernel.

[0003] The advantage of this management model is that it simplifies the kernel's own logic, allowing the kernel to focus on maintaining the geometric modeling algorithm functionality. However, it has the following disadvantages: In multi-user collaborative design application scenarios, such as cloud-based collaborative CAD application systems, multiple CAD application software (upper-level applications) share the same geometric modeling kernel: First, every CAD application needs to perform the same low-level management tasks: maintaining accuracy and tolerance configurations, querying and managing the lifecycle of model objects, storing operation history, and handling serialization (serialization / deserialization operation interfaces). This results in a large amount of repetitive development work.

[0004] Second, the geometric modeling kernel will face concurrent requests from multiple users. These concurrent requests from different users may interfere with or conflict with each other. For example, different users may have different requirements for modeling accuracy and tolerance, but the kernel only has one global accuracy / tolerance variable. When an error occurs in the modeling operation, its diagnostic data may also be confused.

[0005] In related technologies, multi-threaded control schemes are used to handle concurrent requests in order to solve the problem of data interference or conflict. However, the algorithm mechanism for achieving concurrent modification and effective isolation of global model data by multiple threads is complex. Summary of the Invention

[0006] This invention provides a geometric modeling kernel data management method, device, equipment, and medium, as well as a CAD modeling method, which solves the problems of repetitive development of upper-level applications in CAD application systems and data interference or conflict caused by concurrent requests from multiple users.

[0007] To achieve the above objectives, this application adopts the following technical solution: Firstly, a geometric modeling kernel data management method is provided, including: In response to the modeling operation interface call command of the upper layer application, a modeling session context is constructed in the geometric modeling kernel; the modeling session context is used to manage the modeling operation interface configuration data and / or modeling algorithm interface configuration data corresponding to the user of the upper layer application; The modeling operation interface is configured to maintain the global modeling operation configuration set in the modeling session context, and the modeling algorithm interface is configured to maintain the local operation configuration in the current computing state, and pass the local operation configuration in the calls between modeling algorithm interfaces; In response to the modeling algorithm interface call command, the modeling result data associated with the modeling session context is managed based on the preset model database.

[0008] Furthermore, the modeling session context includes a first data structure, which includes: User identifier, serving as a unique identifier for the caller of the modeling operation interface; Session identifier, used to mark the caller's invocation process to the geometry modeling kernel; The first modeling operation configuration includes configuration items for calling the modeling operation interface; The second modeling operation configuration includes configuration items for calling the modeling algorithm interface; Database identifier, which is the database ID associated with the modeling session context; Activity status flags are used to identify the current state of the modeling session context, whether it is active or inactive; A context list pointer that points to the next modeling session context.

[0009] Furthermore, the model database includes a second data structure; the second data structure includes: A database handle is the object that the database operates on. It is used to open the corresponding database and obtain the database operation handle by using the database identifier. The model data segment is used to store the model result data created by the modeling algorithm interface; Discrete data segment is used to store the discretized triangular facet data corresponding to the model data; The data attribute section is used to store business data associated with the model data; The context configuration section is used to store the configuration data generated by the model.

[0010] Furthermore, the modeling session context is associated with the model database through the database identifier.

[0011] Furthermore, the geometric modeling kernel data management method also includes a modeling session context switching step: Perform a logout operation on the current modeling session context. The logout operation includes a submission operation of model-related data based on a first data structure and a model database closing operation based on a second data structure. Set the modeling session context state to an inactive state. Based on the first data structure, the activation operation of the modeling session context to be switched is performed, including opening the database through the database identifier and obtaining the database operation handle, reading the model-related data into memory, and setting the modeling session context state to the active state.

[0012] Furthermore, the geometric modeling kernel data management method also includes the step of creating a branch modeling session context: Create a new modeling session context; Copy the modeling operation configuration of the parent modeling session context; Create the corresponding model database for the new branch modeling session context; Copy the data from the model database associated with the parent modeling session context to the new model database; Perform a switch from the parent modeling session context to the branch modeling session context.

[0013] Secondly, a geometric modeling kernel data management device is provided, comprising: The modeling session context construction module is used to construct a modeling session context in the geometric modeling kernel in response to the modeling operation interface call instructions of the upper layer application; the modeling session context is used to manage the modeling operation interface configuration data and / or modeling algorithm interface configuration data corresponding to the user of the upper layer application; The modeling operation interface is configured to maintain the global modeling operation configuration set in the modeling session context, and the modeling algorithm interface is configured to maintain the local operation configuration in the current computing state, and pass the local operation configuration in the calls between modeling algorithm interfaces; The model database management module is used to respond to modeling algorithm interface call commands and manage the modeling result data associated with the modeling session context based on a preset model database.

[0014] Thirdly, a CAD modeling method is provided, which uses the geometric modeling kernel data management method described in the first aspect for modeling, including: Determine the number of users who will be collaboratively executing the business, or divide the set of models to be processed into batches; Create a corresponding modeling session context for each user, or for each batch of models to be processed; Within any modeling session context, perform the respective modeling operations and interface calls.

[0015] Fourthly, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, performs the steps of the method as described in the first aspect.

[0016] Fifthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first aspect. Attached Figure Description

[0017] Figure 1 A schematic flowchart illustrating a geometric modeling kernel data management method provided in an embodiment of this application; Figure 2 A schematic diagram of a geometric modeling algorithm framework based on variable modeling operation configuration provided in an embodiment of this application; Figure 3 A schematic diagram of a first data structure for modeling session context provided in an embodiment of this application; Figure 4 This is a schematic diagram of the second data structure of a model database provided in an embodiment of this application; Figure 5 A schematic flowchart illustrating a modeling session context switching method provided in this application embodiment; Figure 6 A schematic flowchart illustrating the creation of a branch modeling session context provided in this application embodiment; Figure 7 This is a schematic flowchart illustrating a parallel modeling session context operation provided in an embodiment of this application. Detailed Implementation

[0018] To further illustrate the technical means and effects adopted by the present invention to achieve its intended purpose, the technical solutions in the embodiments of this application are clearly described. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art are within the scope of protection of this application.

[0019] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0020] The steps described in the specification and the flowcharts in the accompanying drawings of this invention are not necessarily strictly executed according to the step numbers; the execution order of the method steps can be changed. Furthermore, certain steps can be omitted, multiple steps can be combined into one step, and / or one step can be broken down into multiple steps.

[0021] This specification provides a geometric modeling kernel data management system, and also relates to a geometric modeling kernel data management method, a CAD modeling method, a geometric modeling kernel data management device, a computer device, and a computer-readable storage medium. The following describes each of these in detail with reference to the accompanying drawings and preferred embodiments.

[0022] Please see Figure 1-2 This application provides a geometric modeling kernel data management method, such as... Figure 1-2 As shown, it includes: Step S1: In response to the modeling operation interface call command of the upper layer application, a modeling session context is constructed in the geometric modeling kernel; the modeling session context is used to manage the modeling operation interface configuration data and / or modeling algorithm interface configuration data corresponding to the user of the upper layer application; The modeling operation interface is configured to maintain the global modeling operation configuration set in the modeling session context, and the modeling algorithm interface is configured to maintain the local operation configuration in the current computing state, and the local operation configuration is passed in the calls between modeling algorithm interfaces.

[0023] The modeling operation interface and the modeling algorithm interface are in a hierarchical calling relationship.

[0024] Step S2: In response to the modeling algorithm interface call command, manage the modeling result data associated with the modeling session context based on the preset model database.

[0025] This application proposes a novel geometric modeling kernel data management method. It manages data related to user modeling operation configurations through a modeling session context, and manages modeling result data through a model database associated with the context. To isolate modeling operations between different modeling sessions and avoid data conflicts caused by re-entry of geometric algorithm interfaces due to different modeling operation configuration items in multiple modeling sessions, this application constructs a geometric modeling algorithm framework based on variable modeling operation configurations. See [link to relevant documentation]. Figure 2 : First, the global modeling operation configuration is retrieved from the currently active modeling session context. Then, based on this global configuration, the modeling operation interface calls the modeling algorithm interfaces below it to complete the modeling operation. Each modeling algorithm interface generates a local operation configuration, which can be consistent with the global configuration or fine-tuned according to the needs of the current computation step. This local operation configuration is passed as a parameter when the user calls other modeling algorithm interfaces. Each modeling algorithm interface uses the local operation configuration passed to it for computation. In other words, at the data level, different model data are associated with different modeling operation configurations set in different modeling session contexts; at the computation level, each modeling algorithm interface under the modeling operation interface maintains its local operation configuration for the current computation state. Therefore, even if the global operation configuration is changed in another session, or another session is using a different global configuration, all steps within the current computation chain strictly follow the local operation configuration initialized by the current modeling operation interface, achieving perfect isolation. This ensures that even if each modeling session context is associated with different modeling operation configurations, these configuration items will not affect the output model result data of the modeling operation.

[0026] In practical applications, for large and complex 3D model data composed of multiple sub-models, the geometric modeling kernel can achieve multi-scale accuracy and local tolerance control of the model data: from the meter-level modeling granularity of large-scale scenes, such as factory models, to the micron / nanometer-level modeling granularity of small-scale models, such as mechanical parts, and can unify complex 3D model data for overall display, without the need to display them separately according to hierarchy / scale.

[0027] Further, see Figure 3 The modeling session context includes a defined first data structure, which includes: User identifier, serving as a unique identifier for the caller of the modeling operation interface; Session identifiers are used to mark the caller's process of calling the geometry modeling kernel, such as recording a complete call process. This process can be a single modeling interface call or multiple modeling interface calls.

[0028] The first modeling operation configuration includes configuration items for modeling operation interface calls, such as modeling accuracy, modeling tolerance, and modeling strategy settings.

[0029] The second modeling operation configuration includes configuration items for calling the modeling algorithm interface; Database identifier, which is the database ID associated with the modeling session context; Activity status flags are used to identify the current state of the modeling session context, whether it is active or inactive; A context list pointer that points to the next modeling session context.

[0030] Further, see Figure 4 The model database includes a defined second data structure; the second data structure includes: A database handle is the object that a database operates on. It is used to open the corresponding database and obtain the database's operation handle.

[0031] The model data segment is used to store the model result data created by the modeling algorithm interface. The model database is divided into different data segments, and the model data segment stores the model result data created by the modeling algorithm interface.

[0032] Discrete data segment is used to store the discretized triangular facet data corresponding to the model data; The data attribute section is used to store business data associated with the model data, such as the set of triangle facet identifiers corresponding to the model edges / faces, or user data associated with the model data, such as material, version, and other data associated with the model.

[0033] The context configuration section is used to store configuration data generated by the model, such as units, precision, and tolerance.

[0034] The modeling session context is associated with the model database through the database identifier.

[0035] See also some possible implementations. Figure 5 The geometric modeling kernel data management method further includes a modeling session context switching step: Step S301: Execute the deregistration operation of the current modeling session context. The deregistration operation includes the submission operation of model-related data based on the first data structure and the closing operation of the model database based on the second data structure, and set the modeling session context state to the inactive state. Step S302: Based on the first data structure, perform the activation operation of the modeling session context to be switched, including opening the database through the database identifier and obtaining the database operation handle, reading the model-related data into memory, and setting the modeling session context state to the active state.

[0036] like Figure 5 As shown, switching the modeling session context involves changing the state of the modeling session context, as well as opening and closing the database. In step S301, the current modeling session context is deactivated, including a commit operation for model-related data based on the first data structure and a close operation for the model database based on the second data structure, and the modeling session context state is set to inactive.

[0037] In step S302, based on the first data structure, the activation operation of the modeling session context to be switched is performed, including opening the database through the database identifier and obtaining the database operation handle, reading the model-related data into memory, and setting the modeling session context state to the active state.

[0038] See also some possible implementations. Figure 6 The geometric modeling kernel data management method further includes the step of creating a branch modeling session context: Step S401: Create a new modeling session context; Step S402: Copy the modeling operation configuration of the parent modeling session context; Step S403: Create the corresponding model database for the new branch modeling session context; Step S404: Copy the data from the model database associated with the parent modeling session context to the new model database; Step S405: Perform a switch from the parent modeling session context to the branch modeling session context.

[0039] When creating a new model database associated with the new modeling session context, users can also choose not to use the overall copying of the model database, but instead use a strategy of using a basic model database plus incremental data storage.

[0040] Corresponding to the above-described geometric modeling kernel data management method embodiment, this application embodiment provides a CAD modeling method, which uses the above-described geometric modeling kernel data management method for modeling, including: Step 1: Determine the number of users who need to collaboratively execute the business, or divide the set of models to be processed into batches; Step 2: Create a corresponding modeling session context for each user, or for each batch of models to be processed; Step 3: In any modeling session context, execute the respective modeling operations and interface calls.

[0041] See Figure 7 For multi-user collaborative CAD modeling and design, as well as the loading or updating of complex large-scale parametric models, the upper-layer caller of the geometric modeling kernel can create multiple modeling session contexts according to machine configuration to improve the model calculation efficiency of CAD applications.

[0042] To address the need for multi-user collaborative modeling and design in CAD, this application's embodiments manage a modeling session context for each user. Model design data from different users is stored within their respective modeling contexts. Upper-level CAD applications based on a geometric modeling kernel can display model design data created by multiple users within their respective modeling session contexts in real time. Therefore, the method of this application can support multi-user collaborative CAD modeling and design. To address the need for users to continuously evolve their designs on CAD models, this application's solution manages a modeling session context for each CAD model design branch. Each modeling session context inherits the model design data from the previous modeling session context, and the CAD model design data version can be exported and saved from the associated modeling session context. This application's method supports users' multi-version, multi-branch CAD model design.

[0043] In parametric modeling, which requires a large number of model update calculations due to parameter adjustments, the method in this application manages a modeling session context for each model update calculation. Model update calculations in different modeling session contexts can be performed in parallel, thereby enabling the parallel creation of complex and large-scale CAD models.

[0044] Corresponding to the above embodiments of the geometric modeling kernel data management method, this application provides a geometric modeling kernel data management device, including: The modeling session context construction module is used to construct a modeling session context in the geometric modeling kernel in response to the modeling operation interface call instructions of the upper layer application; the modeling session context is used to manage the modeling operation interface configuration data and / or modeling algorithm interface configuration data corresponding to the user of the upper layer application; The modeling operation interface is configured to maintain the global modeling operation configuration set in the modeling session context, and the modeling algorithm interface is configured to maintain the local operation configuration in the current computing state, and pass the local operation configuration in the calls between modeling algorithm interfaces; The model database management module is used to respond to modeling algorithm interface call commands and manage the modeling result data associated with the modeling session context based on a preset model database.

[0045] The aforementioned geometric modeling kernel data management device implements the steps and processes of the aforementioned geometric modeling kernel data management method embodiment, and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0046] Corresponding to the above-described geometric modeling kernel data management method embodiments, this application provides an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps and processes of the above-described geometric modeling kernel data management method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0047] Memory can be used to store software programs and various data. Memory can primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area can store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, memory can include volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (Synchlink DRAM, SLDRAM), and direct memory bus RAM (DRRAM). The memory in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0048] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly handles operations related to the operating system, user interface, and applications, while the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor.

[0049] Corresponding to the above-described embodiments of the geometric modeling kernel data management method, this application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the steps and processes of the above-described geometric modeling kernel data management method embodiments and achieve the same technical effect. To avoid repetition, these will not be described again here.

[0050] The processor is the processor in the electronic device described in the above embodiments of this application. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0051] It should be noted that, in this document, 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 a process, method, article, or apparatus. Without further limitations, 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. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0052] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0053] It is understood that the embodiments of this application have been described above in conjunction with the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. As those skilled in the art will know, various changes or equivalent substitutions can be made to these features and embodiments without departing from the spirit and scope of the invention. Furthermore, those skilled in the art, under the guidance or instruction of this application, can modify these features and embodiments to adapt to specific situations and materials without departing from the spirit and scope of the invention. Therefore, this invention is not limited to the specific embodiments disclosed herein, and all embodiments falling within the scope of the claims of this application are within the protection scope of this invention.

Claims

1. A geometric modeling kernel data management method, characterized in that, include: In response to the modeling operation interface call commands of the upper layer application, a modeling session context is constructed in the geometric modeling kernel; The modeling session context is used to manage the modeling operation interface configuration data and / or modeling algorithm interface configuration data corresponding to the user of the upper-layer application; The modeling operation interface is configured to maintain the global modeling operation configuration set in the modeling session context, and the modeling algorithm interface is configured to maintain the local operation configuration in the current computing state, and pass the local operation configuration in the calls between modeling algorithm interfaces; In response to the modeling algorithm interface call command, the modeling result data associated with the modeling session context is managed based on the preset model database; The modeling session context includes a first data structure, which includes: User identifier, serving as a unique identifier for the caller of the modeling operation interface; Session identifier, used to mark the caller's invocation process to the geometry modeling kernel; The first modeling operation configuration includes configuration items for calling the modeling operation interface; The second modeling operation configuration includes configuration items for calling the modeling algorithm interface; Database identifier, which is the database ID associated with the modeling session context; Activity status flags are used to identify the current state of the modeling session context, whether it is active or inactive; A context list pointer that points to the next modeling session context.

2. The geometric modeling kernel data management method according to claim 1, characterized in that, The model database includes a second data structure; the second data structure includes: A database handle is the object that the database operates on. It is used to open the corresponding database and obtain the database operation handle by using the database identifier. The model data segment is used to store the model result data created by the modeling algorithm interface; Discrete data segment is used to store the discretized triangular facet data corresponding to the model data; The data attribute section is used to store business data associated with the model data; The context configuration section is used to store the configuration data generated by the model.

3. The geometric modeling kernel data management method according to claim 1, characterized in that, The modeling session context is associated with the model database through the database identifier.

4. The geometric modeling kernel data management method according to claim 1, characterized in that, The geometric modeling kernel data management method also includes a modeling session context switching step: Perform a logout operation on the current modeling session context. The logout operation includes a submission operation of model-related data based on a first data structure and a model database closing operation based on a second data structure, and set the modeling session context state to an inactive state. Based on the first data structure, the activation operation of the modeling session context to be switched is performed, including opening the database through the database identifier and obtaining the database operation handle, reading the model-related data into memory, and setting the modeling session context state to the active state.

5. The geometric modeling kernel data management method according to claim 4, characterized in that, The geometric modeling kernel data management method also includes the step of creating a branch modeling session context: Create a new modeling session context; Copy the modeling operation configuration of the parent modeling session context; Create the corresponding model database for the new branch modeling session context; Copy the data from the model database associated with the parent modeling session context to the new model database; Perform a switch from the parent modeling session context to the branch modeling session context.

6. A geometric modeling kernel data management device, characterized in that, include: The modeling session context building module is used to build a modeling session context in the geometric modeling kernel in response to modeling operation interface call commands from upper-layer applications. The modeling session context is used to manage the modeling operation interface configuration data and / or modeling algorithm interface configuration data corresponding to the user of the upper-layer application; The modeling operation interface is configured to maintain the global modeling operation configuration set in the modeling session context, and the modeling algorithm interface is configured to maintain the local operation configuration in the current computing state, and pass the local operation configuration in the calls between modeling algorithm interfaces; The model database management module is used to respond to modeling algorithm interface call instructions and manage the modeling result data associated with the modeling session context based on the preset model database. The modeling session context includes a first data structure, which includes: User identifier, serving as a unique identifier for the caller of the modeling operation interface; Session identifier, used to mark the caller's invocation process to the geometry modeling kernel; The first modeling operation configuration includes configuration items for calling the modeling operation interface; The second modeling operation configuration includes configuration items for calling the modeling algorithm interface; Database identifier, which is the database ID associated with the modeling session context; Activity status flags are used to identify the current state of the modeling session context, whether it is active or inactive; A context list pointer that points to the next modeling session context.

7. A CAD modeling method, characterized in that, Modeling is performed using the geometric modeling kernel data management method as described in claim 1, including: Determine the number of users who will be collaboratively executing the business, or divide the set of models to be processed into batches; Create a corresponding modeling session context for each user, or for each batch of models to be processed; Within any modeling session context, perform the respective modeling operations and interface calls.

8. An electronic device, characterized in that, The electronic device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the geometric modeling kernel data management method as described in any one of claims 1 to 4.

9. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the geometric modeling kernel data management method as described in any one of claims 1 to 4.

Images