Collaborative design method, device and equipment for chip layout
By designing a model-view-remote agent architecture, we have enabled multi-user collaborative editing of quantum chip layouts, solving the problem that traditional EDA software cannot support simultaneous editing by multiple users, and improving the efficiency and cycle time of quantum chip design.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHANDONG YUNHAI GUOCHUANG CLOUD COMPUTING EQUIP IND INNOVATION CENT CO LTD
- Filing Date
- 2026-02-28
- Publication Date
- 2026-05-12
AI Technical Summary
Existing technologies cannot support simultaneous editing of quantum chip layouts by multiple users, resulting in long design cycles and low efficiency. Traditional EDA software cannot meet the requirements of quantum chip design.
It adopts a three-tier architecture design of model-view-remote agent, obtains and manages map data requests through the registration center node, realizes multi-person collaborative editing, and uses full-duplex communication links and version control mechanisms for incremental updates and conflict handling.
It enables multiple users to simultaneously edit the quantum chip layout, shortening the design cycle, improving design efficiency, and reducing network traffic and collisions.
Smart Images
Figure CN122021533A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of chip design technology, and in particular to a collaborative design method, apparatus and device for chip layout. Background Technology
[0002] With the development of quantum computing technology, traditional EDA (Electronic Design Automation) software can no longer specifically support quantum chip design and cannot quickly draw complex device structures.
[0003] In related technologies, quantum chip layout design mainly relies on engineers manually drawing circuit diagrams, using open-source tools or code to implement component placement and connections, which is inefficient and prone to errors. Traditional open-source design tools such as QLayout (a layout tool) only support basic layout drawing, lacking the component material library required for quantum chip layout, lacking electromagnetic simulation linkage capabilities, and requiring data to be exported to third-party software for verification. Because QLayout is an exclusive operation for GDS (Graphic Data System, integrated circuit design) files, due to the file locking mechanism, team collaboration only supports single-user exclusive editing of file-level resources, and cannot achieve unit-level parallel modification; for the layout design of large-scale quantum bits, if only one person performs the layout design, it will greatly extend the design cycle and reduce efficiency.
[0004] Therefore, how to support multiple people to edit the same chip layout simultaneously, thereby shortening the chip layout design cycle and improving efficiency, is an urgent problem to be solved. Summary of the Invention
[0005] The purpose of this invention is to provide a collaborative design method, apparatus, and device for chip layouts, which supports multiple people to simultaneously edit the same chip layout, thereby shortening the design cycle and improving efficiency of chip layouts.
[0006] To address the aforementioned technical problems, this invention provides a collaborative design method for chip layout, applied to a registration center node, comprising: Request the layout data of the worker node; According to the layout data request, target serialized scene data is sent to the working node so that the working node renders the target serialized scene data into a corresponding layout image; wherein, the target serialized scene data is a preset serialized scene model published by the data source node corresponding to the layout data request, and the preset serialized scene model is a scene model obtained by serializing the chip layout. When a change is detected in the target serialized scene data, incremental update data corresponding to the target serialized scene data is obtained, and the incremental update data is sent to each target working node to update the layout image rendered and displayed by the target working node; wherein, the target working node is the working node corresponding to the target serialized scene data.
[0007] On the other hand, the target serialized scene data is the scene data of the target layer region in the preset serialized scene model corresponding to the layout data request; wherein, the target layer region is the preset layer region corresponding to the layout data request, and the preset layer region is the area to be modified divided in the chip layout.
[0008] On the other hand, the target serialized scene data sent to the working node according to the layout data request includes: Based on the map identifier in the map data request, determine the target serialization scene model from the preset serialization scene model; Based on the node identity identifier in the map data request, the target serialized scene data is determined from a preset layer region in the target serialized scene model; wherein, the target serialized scene data is the preset layer region corresponding to the operation permission of the node identity identifier.
[0009] On the other hand, sending the incremental update data to each target working node includes: The incremental update data is serialized into differential data packets in binary format; The differential data packets are pushed to each of the target working nodes via a full-duplex communication link.
[0010] On the other hand, prior to the request to obtain the layout data of the working node, the process also includes: Based on the registration request of the working node, establish a connection and heartbeat detection mechanism with the working node.
[0011] On the other hand, the method also includes: Obtain the design operation request sent by the target working node; wherein, the design operation request includes the base version number of the target serialized scene data; According to the design operation request, the target serialization scene data is updated, the updated target serialization scene data is obtained, and the current version number of the target serialization scene data is updated.
[0012] On the other hand, before updating the target serialization scene data according to the design operation request, obtaining the updated target serialization scene data, and updating the current version number of the target serialization scene data, the method further includes: Based on the timestamp in the design operation request, detect whether there are conflicting operation requests; If not, then perform the steps of updating the target serialization scene data according to the design operation request, obtaining the updated target serialization scene data, and updating the current version number of the target serialization scene data; If so, the design operation request and the conflict operation request are merged to obtain a merge operation request; according to the merge operation request, the target serialization scene data is updated, the updated target serialization scene data is obtained, and the current version number of the target serialization scene data is updated.
[0013] On the other hand, the step of merging the design operation request and the conflicting operation request to obtain a merged operation request includes: The design operation request and the conflicting operation request are merged. If the merge is successful, the merge operation request will be obtained; If the merge fails, the step of merging the design operation request and the conflict operation request is executed before the number of conflict merging attempts reaches the threshold. When the number of conflict merging attempts reaches the threshold, a conflict processing failure message is sent to the target node.
[0014] This invention also provides a collaborative design method for chip layout, applied to a registration center node, comprising: The acquisition module is used to obtain layout data requests from working nodes; The sending module is used to send target serialized scene data to the working node according to the layout data request, so that the working node renders the target serialized scene data into a corresponding layout image; wherein, the target serialized scene data is a preset serialized scene model published by the data source node corresponding to the layout data request, and the preset serialized scene model is a scene model obtained by serializing the chip layout. The update module is used to obtain incremental update data corresponding to the target serialized scene data when it detects a change in the target serialized scene data, and send the incremental update data to each target working node to update the layout image rendered and displayed by the target working node; wherein, the target working node is the working node corresponding to the target serialized scene data.
[0015] Furthermore, the present invention also provides a collaborative design device for chip layout, comprising: Memory, used to store computer programs; A processor, used to implement the steps of the co-design method for chip layout as described above when executing the computer program.
[0016] This invention provides a collaborative design method for chip layout, applied to a registration center node, comprising: obtaining a layout data request from a worker node; sending target serialized scene data to the worker node according to the layout data request, so that the worker node renders the target serialized scene data into a corresponding layout image; wherein, the target serialized scene data is a preset serialized scene model published by a data source node corresponding to the layout data request, and the preset serialized scene model is a scene model obtained by serializing the chip layout; when a change is detected in the target serialized scene data, obtaining incremental update data corresponding to the target serialized scene data, and sending the incremental update data to each target worker node to update the layout image rendered and displayed by the target worker node; wherein, the target worker node is the worker node corresponding to the target serialized scene data.
[0017] As can be seen, this invention achieves multi-user collaborative design of chip layouts by sending target serialized scene data to worker nodes according to layout data requests, and employing a three-layer architecture of model-view-remote proxy. By acquiring the corresponding incremental update data when changes are detected in the target serialized scene data and sending the incremental update data to each target worker node, synchronous updates of the displayed content in the worker nodes are achieved. Furthermore, this invention also provides a collaborative design device and apparatus for chip layouts, which also possesses the aforementioned beneficial effects. Attached Figure Description
[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0019] Figure 1 A flowchart illustrating a collaborative design method for chip layout provided in an embodiment of the present invention; Figure 2 This is a partitioned diagram of a quantum chip layout provided in an embodiment of the present invention; Figure 3 This is a flowchart illustrating another collaborative design method for chip layout provided in an embodiment of the present invention; Figure 4This is a structural block diagram of a chip layout co-design device provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of a chip layout co-design device provided in an embodiment of the present invention. Detailed Implementation
[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0021] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a collaborative design method for chip layout provided in an embodiment of the present invention. The method is applied to a registration center node and may include: Step 101: Obtain the layout data request for the working node.
[0022] It is understood that the working nodes in this embodiment can be nodes used for chip layout design. In this embodiment, the registration center node can establish a connection with the registered working nodes and send the layout content to be designed by each working node to the working nodes for display.
[0023] Correspondingly, the worker nodes in this step can be worker nodes already registered on the registration center node. That is to say, this step may also include a worker node registration process, such as the registration center node receiving worker node registration requests; based on the worker node registration requests, establishing a connection and heartbeat detection mechanism with the worker node, so as to use the heartbeat detection mechanism to reconnect when the connection (or link) with the worker node is detected to be broken.
[0024] In this step, the layout data request can be a request for the layout image that the worker node needs to render and display. That is, the worker node sends a layout data request to the registry center node to obtain the corresponding data (i.e., target serialized scene data) returned by the registry center node for the corresponding layout image display, so that the chip designer can perform chip design on the displayed layout image.
[0025] Correspondingly, the specific content of the layout data request in this step can be set by the designer according to the practical scenario and user needs. For example, the layout data request may include a layout identifier to indicate the chip layout to be displayed by the working node; the layout data request may also include a node identity identifier and / or a region identifier to indicate the specific layer or region in the chip layout to be displayed by the working node. As long as the registration center node can determine the specific layout content to be displayed by the working node based on the layout data request, this embodiment does not impose any restrictions on this.
[0026] Step 102: Based on the layout data request, send the target serialized scene data to the worker node so that the worker node can render the target serialized scene data into the corresponding layout image; wherein, the target serialized scene data is the preset serialized scene model published by the data source node corresponding to the layout data request, and the preset serialized scene model is the scene model obtained by serializing the chip layout.
[0027] It is understood that in this embodiment, the data source (Source) node registered in the registration center node can serialize the chip layout (i.e., layout data model) into scene data (i.e., preset serialized scene model) and publish it to the registration center node so as to share the model with the worker nodes registered on the registration center node.
[0028] The chip layout can specifically refer to the quantum chip layout, which includes components such as qubit arrays, control circuits, and readout circuits.
[0029] Correspondingly, the method provided in this embodiment may also include a data source node registration process, such as a registration center node receiving registration requests from data source nodes; establishing a connection and heartbeat detection mechanism with worker nodes based on the registration requests, so as to periodically handle failed data source nodes using the heartbeat detection mechanism. When a new data source node registers with the registration center node, all worker nodes in the network can be notified to facilitate each worker node to obtain the new chip layout in a timely manner.
[0030] For example, in this embodiment, the chip layout can be shared across multiple endpoints (i.e., working nodes) based on the QRemoteObjectNode (remote object node) and QGraphicsView (graphics view) frameworks of PyQt5 (a graphical user interface framework); a three-layer architecture design of model-view-remote proxy is adopted.
[0031] Local Model Layer: QGraphicsScene manages graph item data and encapsulates serializable scene states through QAbstractItemModel. This involves converting the graph of the chip layout into data, describing it with parameters such as coordinates, position, and rotation. QGraphicsScene is used as a shared data source, and QRemoteObjectHost is exposed to the network.
[0032] View rendering layer: Each terminal (i.e., worker node) independently maintains a QGraphicsView instance, handling only local interaction and rendering to avoid network latency affecting UI (user node) responsiveness; dragging, scaling, and rotation of layout elements are implemented through the QGraphicsView framework. Only changing data parameters are passed to ensure consistent graphics rendering effects. Multiple QGraphicsViews act as observers, obtaining scene copies through QRemoteObjectNode (remote object node).
[0033] Remote proxy layer: QRemoteObjectNode (remote object node) publishes model data as Source nodes, and worker nodes synchronize the data stream through Replicas. Once a model data attribute is modified, it is automatically synchronized to all Replica nodes (i.e., worker nodes). Actions executed by Replica nodes are serialized into remote function calls, which can be implemented remotely from the Source nodes. The registry center node uses QRemoteObjectRegistryHost to centrally manage all nodes.
[0034] Accordingly, the target serialization scene data in this step can be a preset serialization scene model corresponding to the layout data request (i.e., the target serialization scene model), or a preset layer region required in the target serialization scene model. For example, in this embodiment, the preset serialization scene model can be divided according to layers / regions (such as QGraphicsScene) so that different working nodes can operate on different partitions. At the same time, the QRegion (region) component can be used to mark and divide the regions that need to be modified, such as... Figure 2 The system uses partitions 1 and 2 to reduce the scope of synchronization; it also uses resource locking mechanisms to protect shared resources and ensure the data security of modified graphical items.
[0035] In other words, the target serialization scene data in this step is the scene data of the target layer region in the preset serialization scene model corresponding to the layout data request; where the target layer region is the preset layer region corresponding to the layout data request, and the preset layer region is the area to be modified divided in the chip layout. Accordingly, the specific method for obtaining the target serialization scene data in this step can be set by the designer. For example, the target serialization scene model can be determined from the preset serialization scene model based on the layout identifier in the layout data request; or the target serialization scene data can be determined from the preset layer region in the target serialization scene model based on the node identity identifier in the layout data request; where the target serialization scene data is the preset layer region corresponding to the operation permission of the node identity identifier.
[0036] Step 103: When a change is detected in the target serialized scene data, the incremental update data corresponding to the target serialized scene data is obtained, and the incremental update data is sent to each target working node to update the layout image rendered and displayed by the target working node; wherein, the target working node is the working node corresponding to the target serialized scene data.
[0037] It is understandable that in this step, the registration center node can broadcast the change information (i.e., incremental update data) to all worker nodes displaying the corresponding content (i.e., target worker nodes) when it detects a change in a preset serialized scene model or a preset layer area within it (i.e., the target serialized scene data). This allows these worker nodes to perform local view update operations based on the change information. For example, the graphics rendering engine in the worker node can support multi-view synchronous preview, allowing real-time observation of the team members' modifications to the qubit array. The target worker nodes in this step can include the worker nodes from step 101.
[0038] Furthermore, in this step, the process of the registration center node sending incremental update data to each target worker node can serialize the incremental update data into binary format differential data packets; push the differential data packets to each target worker node through a full-duplex communication link; that is, use binary data format for transmission plus differential synchronization mechanism to reduce network transmission volume; and use WebSocket (a full-duplex communication protocol) protocol to achieve millisecond-level synchronization of nanometer-level precision modifications.
[0039] In other words, this embodiment can employ a registry center node management mechanism. The registry center node uses QRemoteObjectRegistryHost to uniformly manage all nodes. It centrally manages the connection information of multiple Source nodes (i.e., data source nodes), avoiding the redundant operation of each Replica node (i.e., worker node) connecting to all Source nodes individually. It automatically broadcasts object change signals (such as add / delete events) to notify all connected nodes to update their available object lists. Using a publish-subscribe pattern, when a new Source node connects to the registry center node for registration, it automatically notifies all nodes in the network. A built-in heartbeat detection mechanism periodically handles failed Source nodes. Graphical data serialization (i.e., the preset serialization scene model) uses binary data format for transmission with a differential synchronization mechanism to reduce network transmission volume.
[0040] Correspondingly, the specific method by which the registration center node listens for changes in the target serialized scene data in this step can be set by the designers according to the practical scenario and user needs. For example, it can determine that the target serialized scene data has changed based on the scene change signal sent by the data source node, and receive the corresponding incremental update data from the data source node. In other words, when the graphics in the scene change, the data source node triggers the sceneChanged signal, and publishes the specific change information of the scene (i.e., incremental update data) to all target worker nodes through the registration center node. The target worker nodes deserialize the acquired data and use the local signal slot mechanism to realize the automatic update of the local view.
[0041] For example, in this embodiment, a registration center node can be created, requiring the setting of an IP address accessible to all worker nodes. The node startup order is: first run the registration center node, then run the Source node, and finally run multiple worker nodes. During worker node initialization, a heartbeat detection mechanism is established between the worker node and the registration center node. The Source node serializes scenario data according to the layout data model (i.e., chip layout) and publishes its local layout data model (i.e., a preset serialized scenario model) for data model sharing (e.g., ...). Figure 3 (The process of sharing model data in the process). After adding, deleting, and modifying the layout design operations such as graphics in the Source node scene, all remote worker nodes are triggered to update.
[0042] Furthermore, the method provided in this embodiment may also include a chip layout update process. For example, the registration center node can obtain a design operation request sent by the target worker node; wherein the design operation request includes the base version number of the target serialized scene data; according to the design operation request, the target serialized scene data is updated, the updated target serialized scene data is obtained, and the current version number of the target serialized scene data is updated. That is, to avoid conflicts caused by multiple clients operating the layout simultaneously, this embodiment can adopt a version control management mechanism, incrementing the version number (e.g., version number + 1) after each successful layout modification. For example, version number control can be implemented using QAtomicInteger (atomic integer), incrementing the version number after each modification. Each time a worker node submits a design operation request, it needs to carry the base version number, i.e., which version the modification operation is based on, to facilitate conflict handling when the base versions are different during version merging. For example, the design operation request includes the base version number of the target serialized scene data, a timestamp, node identification (e.g., encoding ID), and graphic change information.
[0043] Correspondingly, this embodiment may also include a timestamp-based conflict detection mechanism to achieve the merging of conflicting operations. For example, before updating the target serialization scene data according to the design operation request, obtaining the updated target serialization scene data, and updating the current version number of the target serialization scene data, it is also possible to detect whether there are conflicting operation requests based on the timestamp in the design operation request (e.g., Figure 3 If no conflict is detected, then the steps of updating the target serialization scene data according to the design operation request, obtaining the updated target serialization scene data, and updating the current version number of the target serialization scene data are executed; if yes, the design operation request and the conflict operation request are merged to obtain a merge operation request; according to the merge operation request, the target serialization scene data is updated, the updated target serialization scene data is obtained, and the current version number of the target serialization scene data is updated.
[0044] Correspondingly, the aforementioned conflict operation requests can be requests to modify the target serialized scene data that have the same timestamp as or differ from the design operation requests within a preset time range (i.e., requests sent by other target working nodes). The specific method for merging the design operation requests and conflict operation requests can be set by the designer. For example, for detected text content conflicts, the Operational Transformation (OT) algorithm can be invoked for merging; for detected graphic transformation conflicts, merging is performed based on the merging rules of the graphic transformation matrix. In other words, in this embodiment, for text string data, QCollator (a string sorter that provides classes for string sorting and comparison) can be used for text conflict detection, and the OT (Operational Transformation) algorithm is used for text conflicts. The OT algorithm is a core algorithm used in collaborative editing systems, primarily to resolve conflicts when multiple users concurrently modify the same document, ensuring eventual consistency. For graphic-related data, graphic transformation operations based on QTransform (graphic matrix transformation, used for translation, rotation, scaling, and shearing operations or combination operations) can be automatically merged.
[0045] Correspondingly, the process of merging design operation requests and conflict operation requests to obtain a merged operation request can be performed on the design operation request and the conflict operation request. If the merge is successful, a merged operation request is obtained; if the merge fails, the step of merging the design operation request and the conflict operation request is executed before the number of conflict merging attempts reaches the threshold. When the number of conflict merging attempts reaches the threshold, a conflict handling failure message is sent to the target node. In other words, this embodiment can set a conflict handling compensation mechanism, which is triggered when conflict handling fails, and performs a 3-retry mechanism (i.e., the number of attempts threshold). If all 3 attempts fail, manual intervention is performed, and a pop-up message indicating the conflict handling failure message is displayed, allowing the user to choose "keep local" or "use remote" to perform data overwrite operations, thus realizing a design conflict handling scheme that is mainly automatic and supplemented by manual intervention.
[0046] Accordingly, this embodiment does not limit the specific selection of the target node. For example, the target node can be the target working node that sends the design operation request and / or the target working node that sends the conflict operation request, or it can be a preset management node.
[0047] Furthermore, in this embodiment, the registration center node can store layout data (such as preset serialized scene models) for all version numbers, enabling backtracking of layout data for all version numbers. It can also provide a data comparison function for different version numbers, providing a reference for users to select historical versions.
[0048] In this embodiment, the present invention achieves multi-person collaborative design of chip layout by sending target serialized scene data to the working nodes according to the layout data request and adopting a three-layer architecture design of model-view-remote proxy; by obtaining the incremental update data corresponding to the target serialized scene data when the target serialized scene data is detected to change, and sending the incremental update data to each target working node, the synchronous update of the content displayed in the working nodes is realized.
[0049] Corresponding to the above method embodiments, this invention also provides a chip layout collaborative design apparatus. The chip layout collaborative design apparatus described below and the chip layout collaborative design method described above can be referred to in correspondence.
[0050] Please refer to Figure 4 , Figure 4 This is a structural block diagram of a collaborative design device for chip layout provided in an embodiment of the present invention. The device is applied to a registration center node and may include: Module 10 is used to obtain layout data requests from working nodes; The sending module 20 is used to send target serialized scene data to the working node according to the layout data request, so that the working node renders the target serialized scene data into the corresponding layout image; wherein, the target serialized scene data is a preset serialized scene model published by the data source node corresponding to the layout data request, and the preset serialized scene model is a scene model obtained by serializing the chip layout. Update module 30 is used to obtain incremental update data corresponding to the target serialized scene data when a change is detected in the target serialized scene data, and send the incremental update data to each target working node to update the layout image rendered and displayed by the target working node; wherein, the target working node is the working node corresponding to the target serialized scene data. On the other hand, the target serialization scene data is the scene data of the target layer area in the preset serialization scene model corresponding to the layout data request; wherein, the target layer area is the preset layer area corresponding to the layout data request, and the preset layer area is the area to be modified divided in the chip layout.
[0051] On the other hand, the sending module 20 may include: The scenario determination submodule is used to determine the target serialized scenario model from the preset serialized scenario model based on the map identifier in the map data request; The region determination submodule is used to determine the target serialized scene data from the preset layer region in the target serialized scene model based on the node identity identifier in the map data request; wherein, the target serialized scene data is the preset layer region corresponding to the operation permission of the node identity identifier.
[0052] On the other hand, update module 30 may include: The binary submodule is used to serialize incremental update data into differential data packets in binary format; The push submodule is used to push differential data packets to each target working node via a full-duplex communication link.
[0053] On the other hand, the device may also include: The registration module is used to establish a connection and heartbeat detection mechanism with worker nodes based on their registration requests.
[0054] On the other hand, the device may also include: The operation acquisition module is used to acquire the design operation request sent by the target worker node; wherein, the design operation request includes the base version number of the target serialized scenario data; The operation update module is used to update the target serialized scene data according to the design operation request, obtain the updated target serialized scene data, and update the current version number of the target serialized scene data.
[0055] On the other hand, the device may also include: The conflict detection module is used to detect whether there are conflicting operation requests based on the timestamp in the design operation request; if there are no conflicting operation requests, it sends a start signal to the operation update module. The merge update module is used to merge the design operation request with the conflicting operation request if there are conflicting operation requests, to obtain a merge operation request; based on the merge operation request, the target serialized scene data is updated, the updated target serialized scene data is obtained, and the current version number of the target serialized scene data is updated.
[0056] On the other hand, the merge update module may include: The merge submodule is used to merge design operation requests and conflicting operation requests; if the merge is successful, a merge operation request is obtained. The compensation module is used to send a start signal to the merging module if the number of conflict merging attempts has not reached the threshold, and to send conflict processing failure information to the target node if the number of conflict merging attempts has reached the threshold.
[0057] In this embodiment, the present invention uses the sending module 20 to send target serialized scene data to the working nodes according to the layout data request, and adopts a three-layer architecture design of model-view-remote proxy to realize multi-person collaborative design of chip layout; when the update module 30 detects a change in the target serialized scene data, it obtains the incremental update data corresponding to the target serialized scene data and sends the incremental update data to each target working node to realize the synchronous update of the content displayed in the working nodes.
[0058] Corresponding to the above method embodiments, this invention also provides a chip layout collaborative design device. The chip layout collaborative design device described below and the chip layout collaborative design method described above can be referred to in correspondence.
[0059] Please refer to Figure 5 , Figure 5 This is a schematic diagram of a co-design device for chip layout provided in an embodiment of the present invention. The device may include: Memory D1 is used to store computer programs; Processor D2 is used to implement the steps of the co-design method for chip layout provided in the above method embodiments when executing a computer program.
[0060] In this embodiment, the chip layout collaborative design device can specifically be a node device that serves as a registration center, such as a computer device or a server.
[0061] Corresponding to the above method embodiments, this invention also provides a computer program product. The computer program product described below and the chip layout co-design method described above can be referred to and correspond to each other.
[0062] A computer program product includes a computer program / instructions that, when executed by a processor, implement the steps of the co-design method for chip layout provided in the above-described method embodiments.
[0063] Corresponding to the above method embodiments, this invention also provides a computer-readable storage medium. The computer-readable storage medium described below and the chip layout co-design method described above can be referred to in correspondence.
[0064] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the co-design method for chip layout as provided in the above method embodiments.
[0065] The computer-readable storage medium can specifically be a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, or any other readable storage medium capable of storing program code.
[0066] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatuses, devices, computer-readable storage media, and computer program products disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.
[0067] The foregoing has provided a detailed description of a collaborative design method, apparatus, and device for chip layout provided by this invention. Specific examples have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of this invention. It should be noted that those skilled in the art can make various improvements and modifications to this invention without departing from its principles, and these improvements and modifications also fall within the protection scope of this invention.
Claims
1. A collaborative design method for chip layout, characterized in that, Applied to registry center nodes, including: Request the layout data of the worker node; According to the layout data request, target serialized scene data is sent to the working node so that the working node renders the target serialized scene data into a corresponding layout image; wherein, the target serialized scene data is a preset serialized scene model published by the data source node corresponding to the layout data request, and the preset serialized scene model is a scene model obtained by serializing the chip layout. When a change is detected in the target serialized scene data, incremental update data corresponding to the target serialized scene data is obtained, and the incremental update data is sent to each target working node to update the layout image rendered and displayed by the target working node; wherein, the target working node is the working node corresponding to the target serialized scene data.
2. The co-design method for chip layout according to claim 1, characterized in that, The target serialized scene data is the scene data of the target layer region in the preset serialized scene model corresponding to the layout data request; wherein, the target layer region is the preset layer region corresponding to the layout data request, and the preset layer region is the area to be modified divided in the chip layout.
3. The co-design method for chip layout according to claim 2, characterized in that, The target serialized scene data sent to the working node according to the layout data request includes: Based on the map identifier in the map data request, determine the target serialization scene model from the preset serialization scene model; Based on the node identity identifier in the map data request, the target serialized scene data is determined from a preset layer region in the target serialized scene model; wherein, the target serialized scene data is the preset layer region corresponding to the operation permission of the node identity identifier.
4. The collaborative design method for chip layout according to claim 1, characterized in that, Sending the incremental update data to each target working node includes: The incremental update data is serialized into differential data packets in binary format; The differential data packets are pushed to each of the target working nodes via a full-duplex communication link.
5. The collaborative design method for chip layout according to claim 1, characterized in that, Before the request to obtain the layout data of the working node, the method further includes: Based on the registration request of the working node, establish a connection and heartbeat detection mechanism with the working node.
6. The co-design method for chip layout according to any one of claims 1 to 5, characterized in that, Also includes: Obtain the design operation request sent by the target working node; wherein, the design operation request includes the base version number of the target serialized scene data; According to the design operation request, the target serialization scene data is updated, the updated target serialization scene data is obtained, and the current version number of the target serialization scene data is updated.
7. The co-design method for chip layout according to claim 6, characterized in that, Before updating the target serialized scene data according to the design operation request, obtaining the updated target serialized scene data, and updating the current version number of the target serialized scene data, the method further includes: Based on the timestamp in the design operation request, detect whether there are conflicting operation requests; If not, then perform the steps of updating the target serialization scene data according to the design operation request, obtaining the updated target serialization scene data, and updating the current version number of the target serialization scene data; If so, the design operation request and the conflict operation request are merged to obtain a merge operation request; according to the merge operation request, the target serialization scene data is updated, the updated target serialization scene data is obtained, and the current version number of the target serialization scene data is updated.
8. The co-design method for chip layout according to claim 7, characterized in that, The step of merging the design operation request and the conflicting operation request to obtain a merged operation request includes: The design operation request and the conflicting operation request are merged. If the merge is successful, the merge operation request will be obtained; If the merge fails, the step of merging the design operation request and the conflict operation request is executed before the number of conflict merging attempts reaches the threshold. When the number of conflict merging attempts reaches the threshold, a conflict processing failure message is sent to the target node.
9. A collaborative design method for chip layout, characterized in that, Applied to registry center nodes, including: The acquisition module is used to obtain layout data requests from working nodes; The sending module is used to send target serialized scene data to the working node according to the layout data request, so that the working node renders the target serialized scene data into a corresponding layout image; wherein, the target serialized scene data is a preset serialized scene model published by the data source node corresponding to the layout data request, and the preset serialized scene model is a scene model obtained by serializing the chip layout. The update module is used to obtain incremental update data corresponding to the target serialized scene data when it detects a change in the target serialized scene data, and send the incremental update data to each target working node to update the layout image rendered and displayed by the target working node; wherein, the target working node is the working node corresponding to the target serialized scene data.
10. A collaborative design device for chip layout, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the co-design method for chip layout as described in any one of claims 1 to 8 when executing the computer program.