Cross-domain data transmission system, transmission method and distribution method
The cross-domain data transmission system addresses data integrity and firewall issues by using a centralized exchange engine for real-time synchronization and encryption, improving efficiency and accuracy in large-scale equipment development.
Patent Information
- Application Number
- CN202411258413.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-09
- Publication Date
- 2024-12-03
AI Technical Summary
Current cross-domain data transmission models for large and complex equipment development face challenges in maintaining accurate data integrity and reducing designer workload due to frequent version changes and firewall restrictions, leading to inefficiencies and potential errors.
A cross-domain data transmission system utilizing a parent exchange engine server and sub-servers, enabling real-time data identification and synchronization across entities, with data encryption, compression, and centralized management to ensure seamless data sharing and distribution.
The system enhances data accuracy and reduces maintenance complexity by ensuring synchronized updates and secure, efficient data transmission, supporting digital prototype development and unified management across multiple units.
Smart Images

Figure CN119071288A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data transmission, and in particular to a cross-domain data transmission system, a transmission method and a distribution method. Background Art
[0002] The development of large and complex equipment requires the participation of multiple organizations in the upstream and downstream of the supply chain, and the collaborative work to efficiently complete the development of the entire equipment. During the development process, the overall design unit needs to issue electronic data models to downstream supporting units to facilitate downstream companies to complete the development of supporting products according to overall requirements. Therefore, the integration model based on cross-domain sharing can facilitate upstream and downstream users to use model data for design and manufacturing.
[0003] However, the current cross-domain collaboration model is mainly aimed at sending data from upstream to downstream. This model has the following adverse effects on the design and production of large and complex equipment:
[0004] The overall research and development enterprise is responsible for the formulation and demonstration of the overall plan, overall design quality control and risk management. Due to the characteristics of complex equipment such as multiple hierarchical structures and a large number of parts, the design and definition of specific subsystems and various lower-level components are usually the responsibility of non-overall departments. Therefore, during the design stage, the overall department cannot accurately control the complete model structure of complex equipment, and needs to adopt a "bottom-up" model. After the specific departments finalize the design, "data transmission and model distribution" is sent to the overall model.
[0005] During the development of large and complex equipment, the overall department and each sub-department need to conduct multiple demonstrations and reviews on the structure, which will involve the modification and change of the department structure. If the "top-down" data distribution model is still used, each change will involve changes in the overall structure. The huge amount of data will bring a huge burden to the work of designers. After the overall model version is changed, the upstream department needs to issue the latest version and structure to all subordinate departments in a timely manner. Frequent data interaction and version changes have a very adverse effect on the accurate grasp of data by various departments. Once an error occurs in the issuance process, resulting in a downstream department not getting the latest model or the latest version, it will have an irreparable and huge impact on future development.
[0006] Therefore, in order to meet the needs of production and development, it is necessary to adopt the form of "bottom-up" step-by-step data transmission and model distribution. The lower-level subsystems and parts are implemented by the departments responsible for this work. After the version is finalized, the model is released to the overall development enterprise through data interaction. Under the premise of ensuring that the top-level model structure and version remain unchanged, each department is responsible for improving the bottom-level design. This can ensure the accuracy and integrity of the model to the greatest extent, and can greatly reduce the work pressure of designers to maintain the model. Summary of the invention
[0007] In view of this, the present invention provides a cross-domain data transmission system, transmission method and distribution method, which can break through the firewall restrictions caused by the local area network, perform real-time identification and updating between the master and slave entities, and realize data sharing between the master and slave entities, thereby being more suitable for practical use.
[0008] In order to achieve the first objective above, the technical solution of the cross-domain data transmission system provided by the present invention is as follows:
[0009] The cross-domain data transmission system provided by the present invention comprises a parent exchange engine server and a plurality of sub-servers.
[0010] The multiple sub-servers exchange data with the parent switching engine server through transmission ports respectively, wherein the parent switching engine server belongs to a first entity, the multiple sub-servers belong to a second type of entity, and each entity in the second type of entity is subordinate to the first entity.
[0011] The cross-domain data transmission system provided by the present invention can also be further implemented by adopting the following technical measures.
[0012] Preferably, the IP segments and port numbers of the multiple sub-servers are controlled by the first entity.
[0013] Preferably, when the cross-domain data needs to be updated, the data of the parent switching engine server is updated so that the corresponding data in the multiple child servers can be updated synchronously.
[0014] Preferably, identifying that the data is updated comprises the following steps:
[0015] Acquire real-time data A1 of target data at a first moment T1 and real-time data A2 of target data at a second moment T2, wherein the second moment T2 is later than the first moment T1;
[0016] Comparing the real-time data A1 with the real-time data A2;
[0017] If the real-time data A2 has changed relative to the real-time data A1, it is considered that the target data has changed between the first time T1 and the second time T2, and the target data is data to be updated.
[0018] In order to achieve the above second purpose, the technical solution of the cross-domain data transmission method based on the cross-domain data transmission system provided by the present invention is as follows:
[0019] The cross-domain data transmission method provided by the present invention based on the cross-domain data transmission system provided by the present invention comprises the following steps:
[0020] Acquire data models of the multiple sub-servers and message contents of the multiple sub-servers;
[0021] Packing the data models of the multiple sub-servers to obtain data compression packages corresponding to the data models of the multiple sub-servers;
[0022] Encrypting data compression packages corresponding to the data models of the multiple sub-servers and message contents of the multiple sub-servers to obtain encrypted data;
[0023] The encrypted data is transmitted through the network and reaches the pre-processing end of the parent switching engine server;
[0024] At the pre-processing end of the mother switching engine server, the encrypted data is decrypted, and the data compression package is decompressed to obtain processed transmission data;
[0025] After the processed transmission data is received by the mother switching engine server, it can be calculated, analyzed and processed.
[0026] The cross-domain data transmission method provided by the present invention and based on the cross-domain data transmission system provided by the present invention can also be further implemented by adopting the following technical measures.
[0027] Preferably, the message content is in JSON format, including an initiator organization identifier, initiator information, a transmission data list, a model file download address, a receiver organization identifier, recipient information, and operation rationality.
[0028] Preferably, the data compression package corresponding to the data models of the multiple sub-servers includes:
[0029] Detailed attribute information, including 3D models, documents and other related object information, through which the object can be fully restored;
[0030] Detailed information about the relationship between models and between models and documents, which carries the complete relationship attributes between two objects. Through this attribute, after restoring the objects, the related objects can establish a complete relationship.
[0031] Attachment information, which contains the specific attribute information of the attachment, is used to restore the display information of the attachment in the system; it also contains the physical file. After the receiving system restores the object, the attachment information can be fully displayed. Click to view the attachment content.
[0032] Preferably, the data models of the multiple sub-servers and the message contents of the multiple sub-servers are audited security data.
[0033] In order to achieve the third objective above, the technical solution of the cross-domain data distribution method based on the cross-domain data transmission system provided by the present invention is as follows:
[0034] The cross-domain data distribution method provided by the present invention based on the cross-domain data transmission system provided by the present invention comprises the following steps:
[0035] The data sending sub-server determines the data to be distributed;
[0036] The parent switching engine server obtains the IP network segment and port number of the child server receiving the data;
[0037] The parent switching engine server sends the data to be distributed to the sub-server receiving the data according to the IP network segment and port number of the sub-server receiving the data.
[0038] The cross-domain data distribution method provided by the present invention based on the cross-domain data transmission system provided by the present invention can also be further implemented by adopting the following technical measures.
[0039] Preferably, the cross-domain data distribution method of the cross-domain data transmission system further comprises the following steps:
[0040] The parent switching engine server feeds back the data receiving result of the data receiving sub-server to the data sending sub-server.
[0041] The technical effects of the cross-domain data transmission system, transmission method and distribution method provided by the present invention are as follows:
[0042] 1. Meet the enterprise's requirements for digital prototype delivery
[0043] At present, in the equipment delivery process, what is provided is a document-based equipment product data package. The data is implicit in the document, and the computer cannot automatically identify and analyze the association. The document and drawings are difficult to visualize and rely on people to read and analyze. The efficiency is low and the work intensity is high. It cannot meet the requirements of digital operation and support of weapons and equipment under modern conditions. It is urgent to transform from the current delivery mode based on document data packages to a model-based digital equipment delivery mode, deliver digital models and support the analysis and interface access application of digital prototype models. The digital prototype system improves the digital delivery capability of equipment through digital means to meet the application goals of digital models in training and combat scenarios.
[0044] 2. Meet the enterprise's requirements for unified management of digital prototypes
[0045] The digital prototype system adopts model data transmission and model distribution that supports multi-source heterogeneous, cross-level and cross-unit, and uses unified data exchange data transmission and model distribution technology to establish digital prototype model data transmission and model distribution technology from single machine to subsystem, and subsystem to overall. It defines a digital prototype management plan that runs through the entire cycle from demand to design, process, production, assembly, testing, and on-orbit, and constructs complete digital prototype model data to meet the final delivery requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:
[0047] Figure 1 Develop the network connection topology diagram between the enterprise and its subsidiaries for the existing technology projects;
[0048] Figure 2 It is a topological diagram of a point-to-point data transmission mode in the prior art;
[0049] Figure 3 A topological diagram of a cross-domain data transmission system provided by an embodiment of the present invention;
[0050] Figure 4 A schematic diagram of the relationship between the IP and port configured by the administrator in the cross-domain data transmission system provided by the embodiment of the present invention;
[0051] Figure 5 A schematic diagram of a data transmission process of a cross-domain data transmission system provided in an embodiment of the present invention;
[0052] Figure 6 A schematic diagram of the relationship between data transmission and model distribution data packet structure involved in the cross-domain data transmission system provided in an embodiment of the present invention;
[0053] Figure 7 A processing flow from a data transmission request initiated by an initiating plant to data received by a receiving plant involved in a cross-domain data transmission system provided in an embodiment of the present invention;
[0054] Figure 8 A business flow chart of model distribution data transmission and model distribution involved in the cross-domain data transmission system provided in an embodiment of the present invention;
[0055] Fig. 9 A schematic diagram of signaling interaction between model distribution data transmission and model distribution involved in a cross-domain data transmission system provided in an embodiment of the present invention;
[0056] Fig.10 The model distribution data transmission and model distribution and reception involved in the cross-domain data transmission system provided for the embodiment of the present invention mainly involve the initiating unit starting the distribution process, internal review, the receiving unit receiving the cross-domain distribution task, and the functional business flow chart of the relevant links of the cross-domain distribution task;
[0057] Fig.11 A schematic diagram of signaling interaction between model distribution data transmission and model distribution involved in a cross-domain data transmission system provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0058] In order to solve the problems existing in the prior art, the present invention provides a cross-domain data transmission system, transmission method and distribution method, which can break through the firewall restrictions caused by the local area network, perform real-time identification and updating between the master and slave entities, and realize data sharing between the master and slave entities, thereby being more suitable for practical use.
[0059] Research and development requires collaboration between units at different levels. Digital prototype models are also generated by different units and managed in their respective business systems. The digital prototype management system needs to transmit data and distribute model data from single machines, subsystems, overall cross-units, and multi-field business systems of design, manufacturing, and testing to form a unified model product digital prototype data integration management system.
[0060] Based on the model data transmission mechanism and permission control mechanism between multiple levels and multiple subjects, it realizes the safe, reliable and efficient transmission of messages and data in a distributed and complex network environment, and carries out various collaborative businesses. The main technologies involved are:
[0061] (1) Multi-site data transmission and model distribution engine technology: Using technologies such as message middleware and multi-level link broadcast, we build a data transmission and model distribution engine for multi-source heterogeneous systems and data of research and development units at different levels, and realize unified exchange of different data of various application systems.
[0062] (2) Heterogeneous system data exchange model technology: Aiming at the different expressions of the same data in different application systems, research on data standards and specifications, master data and metadata technology, data mapping and conversion technology, to achieve data exchange and transmission in heterogeneous application environments, and open up data links for business collaboration.
[0063] (3) High-availability and high-performance switching technology: For multi-unit and multi-system data exchange, research on full-link monitoring of data flow and data breakpoint resumption technology to achieve highly reliable and high-performance switching.
[0064] (4) Exchange of multiple types of R&D models: Realize cross-system exchange of demand models, functional and logical models, multi-domain physical models, three-dimensional models, process models, and product structures. Support data exchange of change orders, technical notification orders / tolerance orders / material substitution orders / question orders before and after changes, and provide exchange capabilities for all business data in the R&D process.
[0065] In the prior art, the data transmission mode
[0066] For collaborative project development, each factory needs to undertake a part of the design and development tasks. The overall development enterprise is responsible for controlling the overall progress and quality of the model. Therefore, each factory needs to frequently sign the design documents, 3D models and structures online and distribute the models through the PLM system. After the process is controlled, the model needs to be issued, data is transmitted and the model distribution operations need to be carried out to the next level or the overall development enterprise.
[0067] Although each factory has a dedicated network connection, due to the isolation of their respective firewalls, they cannot actually access freely unless a specific port for network access is opened separately. With the increasing urgency of the requirements and necessity for the construction of digital prototype development platforms in various institutes, the existing collaborative environment of each unit can no longer meet the needs of model collaborative development.
[0068] If data is transmitted from factory A to factory B, not only do A and B need to be interconnected, but A and B also need to have their own firewalls to isolate them, and they also need to open network ports dedicated to data transmission. Although information exchange between the two factories can be achieved through "point-to-point", the following disadvantages are unavoidable during the development of large-scale models:
[0069] The first is the high maintenance cost. If there are many collaborating units, each unit needs to be configured, which puts a lot of workload on the administrator.
[0070] The second is the high complexity of the system. The original collaborative configuration requires the establishment of link relationships, basic data synchronization, model mapping, open networking, etc. for each collaborative unit. The configuration is complex and prone to errors.
[0071] In order to further explain the technical means and effects adopted by the present invention to achieve the predetermined invention purpose, the following is a detailed description of the cross-domain data transmission system, transmission method and distribution method proposed by the present invention, its specific implementation method, structure, features and effects in combination with the accompanying drawings and preferred embodiments. In the following description, different "one embodiment" or "embodiment" does not necessarily refer to the same embodiment. In addition, the features, structures, or characteristics of one or more embodiments may be combined in any suitable form.
[0072] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B. Specifically, it is understood that: A and B may be included at the same time, A may exist alone, or B may exist alone, and any of the above three situations may be met.
[0073] Cross-domain data transmission system
[0074] The cross-domain data transmission system provided by the present invention comprises a parent exchange engine server and a plurality of sub-servers.
[0075] The multiple sub-servers exchange data with the parent switching engine server through transmission ports respectively, wherein the parent switching engine server belongs to the first subject, the multiple sub-servers belong to the second type of subject, and each subject in the second type of subject is subordinate to the first subject.
[0076] The IP segments and port numbers of the multiple sub-servers are controlled by the first entity.
[0077] When the cross-domain data needs to be updated, the data of the parent exchange engine server is updated so that the corresponding data in the multiple child servers can be updated synchronously.
[0078] The updating of the identification data includes the following steps:
[0079] Acquire real-time data A1 of the target data at a first moment T1 and real-time data A2 of the target data at a second moment T2, wherein the second moment T2 is later than the first moment T1;
[0080] Compare real-time data A1 and real-time data A2;
[0081] If the real-time data A2 has changed relative to the real-time data A1, it is considered that the target data has changed between the first time T1 and the second time T2, and the target data is data to be updated.
[0082] Cross-domain data transmission method based on the cross-domain data transmission system provided by the present invention
[0083] The cross-domain data transmission method provided by the present invention based on the cross-domain data transmission system provided by the present invention comprises the following steps:
[0084] Obtain data models of multiple sub-servers and message contents of multiple sub-servers;
[0085] Packing the data models of the multiple sub-servers to obtain data compression packages corresponding to the data models of the multiple sub-servers;
[0086] Encrypting data compression packages corresponding to data models of multiple sub-servers and message contents of multiple sub-servers to obtain encrypted data;
[0087] The encrypted data is transmitted through the network and reaches the pre-processing end of the parent switching engine server;
[0088] At the pre-processing end of the mother switching engine server, the encrypted data is decrypted, and the data compression package is decompressed to obtain the processed transmission data;
[0089] After the processed transmission data is received by the mother switching engine server, it can be calculated, analyzed and processed.
[0090] Among them, the type of message content is in JSON format, including the initiator organization identification, initiator information, transmission data list, model file download address, receiving organization identification, recipient information, and operation rationality.
[0091] The data compression packages corresponding to the data models of the multiple sub-servers include:
[0092] Detailed attribute information, including 3D models, documents and other related object information, through which the object can be fully restored;
[0093] Detailed information about the relationship between models and between models and documents, which carries the complete relationship attributes between two objects. Through this attribute, after restoring the objects, the related objects can establish a complete relationship.
[0094] Attachment information, which contains the specific attribute information of the attachment, is used to restore the display information of the attachment in the system; it also contains the physical file. After the receiving system restores the object, the attachment information can be fully displayed. Click to view the attachment content.
[0095] Among them, the data models of multiple sub-servers and the message contents of multiple sub-servers are audited security data.
[0096] A cross-domain data distribution method based on the cross-domain data transmission system provided by the present invention
[0097] The cross-domain data distribution method provided by the present invention based on the cross-domain data transmission system provided by the present invention comprises the following steps:
[0098] The data sending sub-server determines the data to be distributed;
[0099] The main switching engine server obtains the IP network segment and port number of the child server receiving the data;
[0100] The parent switching engine server sends the data to be distributed to the sub-server receiving the data according to the IP network segment and port number of the sub-server receiving the data.
[0101] The cross-domain data distribution method of the cross-domain data transmission system further includes the following steps:
[0102] The parent exchange engine server feeds back the data receiving result of the sub-server receiving the data to the sub-server sending the data.
[0103] Example
[0104] Transmission mode used by digital prototype
[0105] Based on the coordination requirements of a network center, this network center can be at the institute level. Based on this center and the various factories under the institute, ports are opened. First, the complexity of network configuration between each factory and other places that require data transmission, model distribution and interaction can be greatly reduced. Second, the network center is at the institute level and belongs to the superior of each factory. It can coordinate management and distribution of security strategies, minimize openness, and minimize security risks. The collaboration of each unit with other units is automatically forwarded through the network center, regardless of whether it is inside or outside the institute. Each unit only needs to complete the establishment of a relationship with the network center, synchronize basic data, and map the unified model with the central domain. It only needs to open the network port to the center, which greatly simplifies the maintenance and complexity of the participating units. Unifying the complexity into a system in the central domain reduces the original N×N complexity to N+1, which is directly reduced by an order of magnitude.
[0106] The system administrator needs to deploy a set of exchange engine services in the central server that can transmit data and distribute models to each factory's IP and port, receive and forward messages sent by each factory, and then the data and messages of each factory can be communicated. Moreover, after the link is opened, the superior-subordinate relationship of each factory is no longer distinguished. As long as it is a business requirement and the IP and port are configured in the exchange service, data communication can be achieved.
[0107] Moreover, when the system administrator is performing equipment and network maintenance, he only needs to regularly update the switching engine server, without having to change the network configuration of each factory. This ensures network stability and data security. When adding factories, it can avoid the factories from opening firewalls and ports privately to the greatest extent. Submit the IP network segments and port numbers that need to be opened, and let the superior administrator enter and open the data uniformly:
[0108] Model data transmission and model distribution data package
[0109] Model transmission is the basic supporting function of the digital prototype model data transmission and model distribution module. It is mainly responsible for the inter-domain transmission of cross-domain data and models. The content of the transmission includes business data objects, various types of models and business data attachments. It provides two basic functions including message management and attachment transmission management. Business data attachments are encrypted during the transmission process. The following figure illustrates the transmission processing of collaborative data:
[0110] The data transmitted between domains can be roughly summarized as: "message + data packet file". The message type is in JSON format, and the main data includes the following parts:
[0111]
[0112]
[0113] The packet file records the following details of the transfer:
[0114] Detailed attribute information, which may include 3D models, documents and other related object information, can be used to fully restore the object.
[0115] Detailed information about the relationship between models and between models and documents. It carries the complete relationship attributes between two objects. Through this attribute, after restoring the objects, the related objects can establish a complete relationship.
[0116] Attachment information, which includes the specific attribute information of the attachment, is used to restore the display information of the attachment in the system; it also includes the physical file. After the receiving system restores the object, the attachment information can be fully displayed. Click to view the attachment content.
[0117] Model data transmission and model distribution process
[0118] At the initiating end, the business personnel select the model data that needs to be submitted for joint signing or data transmission and model distribution. After selecting the destination factory and personnel, the system will export the complete model information, relationship information, and attachment information based on the data, and organize and generate JSON messages. After the above information is organized, the data will be submitted to the exchange engine server, waiting for the data and message distribution operation.
[0119] After the data and messages arrive at the exchange engine server, the engine will parse the initiating factory and receiving factory in the message for query. If they exist, the message will be forwarded. If not, the exception information will be returned to the initiating end, which will capture the exception and display it to relevant business personnel.
[0120] After the forwarded message arrives at the receiving end, the background downloads the data packet file through the data packet link in the message, restores the model object and relationship object in turn, attaches the relationship, restores the attachment information, generates a receiving task for the receiving personnel, generates a receiving log, and attaches the model information to the existing BOM structure.
[0121] Overview of business scenarios for model data transmission and model distribution
[0122] Model data sharing data transmission and model distribution
[0123] The business process of model distribution data transmission and model distribution is shown in the following figure:
[0124] Initiate cross-domain sharing
[0125] The shared data and models are designed to a certain state, but have not been submitted for review. The purpose is mainly to collect design opinions, and process personnel and other relevant personnel will participate in the research process in advance to judge process feasibility, processing interference, etc., change the traditional serial working mode of design and manufacturing, and carry out design and manufacturing work in parallel to improve model development efficiency. What is shared is a small version of the design data or model. During the sharing period, the data or model can be edited and upgraded normally by the initiator, and the upgraded small version can be shared again.
[0126] If a designer needs to share his design files and models with users from other units, he should first select the objects to be shared, then create a corresponding sharing form, specify the specific people in the participating units or other units, and then initiate the cross-domain sharing process.
[0127] If the selected shared object does not have a physical file, a prompt will be given: "The selected shared object does not have a physical file, please reselect."
[0128] Receive and process cross-domain shared tasks
[0129] When initiating sharing, the initiator selects the receiving unit or a specific person in the receiving unit. If the receiving unit is selected, the person will be the sharing coordination administrator of the receiving unit. If there is no sharing coordinator, the cross-domain coordinator will receive the sharing task on the personal work surface, and the coordinator will forward the task to the relevant model researchers to carry out the sharing work. If the initiator selects a specific person in the receiving unit, the person will receive the sharing task on the personal work surface and then carry out the sharing work.
[0130] View shared data and models: During cross-domain sharing, users participating in sharing can view shared data and models through sharing tasks. Users need to download shared files or models to their local computers and use local tools to open the files for review.
[0131] After opening the file with a local tool, the user who participates in the sharing can use the local tool to annotate the file, and can upload the annotated file or model to the system as an attachment. The uploaded annotation attachment is named "original file name_annotation user name" by default. If the same user uploads annotations to the same model or file multiple times, the last upload will prevail.
[0132] Sharing feedback: The sharer adds sharing opinions, which are returned to the initiator along with the sharing task.
[0133] The initiator views cross-domain sharing opinions
[0134] The initiator can find the corresponding shared document in the collaborative document query, or directly view the corresponding shared document at the specific shared object such as the model to view the shared opinions. The initiator can also download the annotations attached to the shared model or file to the local computer for viewing.
[0135] Model data distributionData transmission and model distribution
[0136] Model distribution data transmission and model distribution and reception mainly involve the functions of the initiating unit initiating the distribution process, internal review, the receiving unit receiving the cross-domain distribution task, and processing the related links of the cross-domain distribution task.
[0137] After the initiator has selected the distribution data, model, and distribution unit, cross-domain distribution is initiated;
[0138] The data and models are packaged and processed as non-plaintext by the initiating unit and then distributed as message attachments;
[0139] After receiving the message, the receiving unit receives the data packet attachment and decompresses and decrypts it, and at the same time imports and creates the collaborative data and model in the data packet in the receiving unit system.
[0140] The technical effects of the cross-domain data transmission system, transmission method and distribution method provided by the present invention are as follows:
[0141] 1. Meet the enterprise's requirements for digital prototype delivery
[0142] At present, in the equipment delivery process, what is provided is a document-based equipment product data package. The data is implicit in the document, and the computer cannot automatically identify and analyze the association. The document and drawings are difficult to visualize and rely on people to read and analyze. The efficiency is low and the work intensity is high. It cannot meet the requirements of digital operation and support of weapons and equipment under modern conditions. It is urgent to transform from the current delivery mode based on document data packages to a model-based digital equipment delivery mode, deliver digital models and support the analysis and interface access application of digital prototype models. The digital prototype system improves the digital delivery capability of equipment through digital means to meet the application goals of digital models in training and combat scenarios.
[0143] 2. Meet the enterprise's requirements for unified management of digital prototypes
[0144] With the gradual deepening of enterprise informatization construction, the vast majority of product data has been generated and managed by various business systems, such as PDM, ERP, MES, quality management systems, test and inspection systems, etc. Various business systems have realized the management of various business data respectively, and the conditions for the informatization construction of product production process quality management have basically been formed.
[0145] However, there is a lack of a unified product data management platform. Usually, you need to log in to multiple systems to find some product data about the same product / batch. It is difficult to centrally view the data of the entire process of a certain product / batch, and the procedures are cumbersome and the integrity is poor. This brings many inconveniences to the query, sharing, analysis and use of product data.
[0146] At present, product data is managed in multiple systems in a decentralized manner, and product data is scattered in all corners of the enterprise. Various documents and receipts have not formed a complete product data organization link, making it difficult to support rapid query, positioning, tracking and tracing of data, and unable to quickly lock the scope of the problem and analyze the cause, which makes it difficult to return to zero. In this case, we can only rely on the experience of designers, process engineers, and quality management personnel to analyze the problem, lacking effective data support and data analysis methods. The digital prototype system adopts model data transmission and model distribution that supports multi-source heterogeneous cross-level and cross-unit, and uses unified data exchange data transmission and model distribution technology to establish digital prototype model data transmission and model distribution technology from single machine to subsystem, subsystem to overall, and define a digital prototype management plan that runs through the entire cycle from demand to design, process, production, assembly, testing, and on-orbit, and builds complete digital prototype model data to meet the final delivery requirements.
[0147] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.
[0148] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.
Claims
1. A cross-domain data transmission system, characterized in that: It includes a main switching engine server and multiple sub-servers. The multiple sub-servers exchange data with the parent switching engine server through transmission ports respectively, wherein the parent switching engine server belongs to a first entity, the multiple sub-servers belong to a second type of entity, and each entity in the second type of entity is subordinate to the first entity.
2. The cross-domain data transmission system according to claim 1, characterized in that: The IP network segments and port numbers of the multiple sub-servers are controlled by the first entity.
3. The cross-domain data transmission system according to claim 1, characterized in that: When the cross-domain data needs to be updated, the data of the parent exchange engine server is updated so that the corresponding data in the multiple child servers can be updated synchronously.
4. The cross-domain data transmission system according to claim 3, characterized in that: Identifying that the data has been updated comprises the following steps: Acquire real-time data A1 of target data at a first moment T1 and real-time data A2 of target data at a second moment T2, wherein the second moment T2 is later than the first moment T1; Comparing the real-time data A1 with the real-time data A2; If the real-time data A2 has changed relative to the real-time data A1, it is considered that the target data has changed between the first time T1 and the second time T2, and the target data is data to be updated.
5. A cross-domain data transmission method based on the cross-domain data transmission system according to any one of claims 1 to 4, characterized in that: The following steps are involved: Acquire data models of the multiple sub-servers and message contents of the multiple sub-servers; Packing the data models of the multiple sub-servers to obtain data compression packages corresponding to the data models of the multiple sub-servers; Encrypting data compression packages corresponding to the data models of the multiple sub-servers and message contents of the multiple sub-servers to obtain encrypted data; The encrypted data is transmitted through the network and reaches the pre-processing end of the parent switching engine server; At the pre-processing end of the mother switching engine server, the encrypted data is decrypted, and the data compression package is decompressed to obtain processed transmission data; After the processed transmission data is received by the mother switching engine server, it can be calculated, analyzed and processed.
6. The cross-domain data transmission method of the cross-domain data transmission system according to claim 5, characterized in that: The message content is in JSON format, including the initiator organization identification, initiator information, transmission data list, model file download address, receiving organization identification, recipient information, and operation rationale.
7. The cross-domain data transmission method of the cross-domain data transmission system according to claim 5, characterized in that: The data compression package corresponding to the data models of the multiple sub-servers includes: Detailed attribute information, including 3D models, documents and other related object information, through which the object can be fully restored; Detailed information about the relationship between models and between models and documents, which carries the complete relationship attributes between two objects. Through this attribute, after restoring the objects, the related objects can establish a complete relationship. Attachment information, which contains the specific attribute information of the attachment, is used to restore the display information of the attachment in the system; it also contains the physical file. After the receiving system restores the object, the attachment information can be fully displayed. Click to view the attachment content.
8. The cross-domain data transmission method of the cross-domain data transmission system according to claim 5, characterized in that: The data models of the multiple sub-servers and the message contents of the multiple sub-servers are audited security data.
9. A cross-domain data distribution method based on the cross-domain data transmission system according to any one of claims 1 to 4, characterized in that: The following steps are involved: The data sending sub-server determines the data to be distributed; The parent switching engine server obtains the IP network segment and port number of the child server receiving the data; The parent switching engine server sends the data to be distributed to the sub-server receiving the data according to the IP network segment and port number of the sub-server receiving the data.
10. The cross-domain data distribution method of the cross-domain data transmission system according to claim 9, characterized in that: The following steps are also included: The parent switching engine server feeds back the data receiving result of the data receiving sub-server to the data sending sub-server.
Citation Information
Cited By
Data management method and system based on cross-domain collaboration
CN121071011A
