An XML-based gearbox data exchange method

Abstract

This invention discloses an XML-based method for exchanging transmission data, proposing a standardized document, GBDB document specification, which includes descriptions of transmission component data, relationships between transmission components, and different operating condition information. It also explains the document specifications, usage methods, data exchange, and application scenarios. This invention can be applied to the development specifications of transmission-related industrial internet applications and can also solve the problem of collaborative development and manufacturing by transmission OEMs, enabling data sharing among various components.

Description

Technical Field

[0001] This invention relates to the field of gearbox data exchange, and in particular to an XML-based gearbox data exchange method. Background Technology

[0002] Currently, my country lags significantly behind foreign countries in industrial internet software standards research and software development technologies, particularly in some specialized areas. Secondly, the scale of new energy vehicles is expanding, leading to increasing technological demands in related industries and presenting new challenges in the production, manufacturing, and testing of key components for new energy vehicles. In particular, the design and development of electric vehicle transmissions in my country requires substantial technical expertise in data exchange and model building. Furthermore, each component in a transmission has unique attributes, numerous parameter types, and complex relationships, necessitating standardized documentation. Additionally, data exchange and collaborative development among different component OEMs present numerous challenges. For instance, different manufacturers use varying R&D standards, making it difficult to obtain accurate data and macro-level data architectures from various manufacturers quickly, resulting in prolonged development times and significant difficulties in collaborative development.

[0003] Therefore, this invention proposes a solution for data storage technology and collaborative development methods among manufacturers of transmissions, thereby meeting the needs of industrial internet software development and collaborative development and manufacturing among component manufacturers in the field of transmissions. Summary of the Invention

[0004] To overcome the shortcomings of existing technologies, this invention provides an XML-based method for exchanging transmission data, which improves the efficiency and reliability of transmission software (APP) development, as well as data sharing and collaborative development among manufacturers.

[0005] To achieve the aforementioned objectives of the invention, the technical solution adopted to solve its technical problems is as follows:

[0006] An XML-based method for exchanging transmission data describes the transmission data, which is divided into three main categories: part relationship description specification, part unit description specification, and operating condition information description specification. This is described in detail through the following steps:

[0007] Step S1: Use XML as the primary form of data carrier;

[0008] Step S2: Use XML to describe the data of each component in the gearbox;

[0009] Step S3: Use XML to describe the relationships between the various components in the gearbox;

[0010] Step S4: Use XML to describe data under different operating conditions;

[0011] Step S5: Use XML to implement the component data description format under specific working conditions;

[0012] Step S6: Use XML to realize the data exchange and storage of results obtained from different working conditions, calculation methods, safety factors, industry standards, and empirical formulas;

[0013] Step S7: Use XML to implement a data flattening development model.

[0014] Furthermore, in step S1, XML is used as the data carrier language, and Schema and DTD are used to constrain the permissions and data validity of the document.

[0015] Furthermore, in step S2, XML is used to describe the data of each component in the gearbox. The description of each component is divided into parent nodes and child nodes, and each parent node has a unique ID, which is used to bind with other gearbox data information; the child nodes contain component attribute information.

[0016] Furthermore, in step S3, XML is used to describe the relationships between the various components in the gearbox. The relational data in the gearbox includes four types of relationships: component-to-component, component-to-non-component, component-to-result, and operating condition-to-result. Similarly, the component relational data has parent nodes and child nodes, and both parent and child nodes must contain the attribute form of id, and id is unique.

[0017] Furthermore, in step S4, XML is used to describe different working condition data. The working condition information and result information both belong to the loadcases working condition type data. Each independent parent node of the working condition information contains a unique id, which facilitates retrieval through relational data. Its child nodes contain the corresponding specific data, and the child node attributes contain information such as name, unit, and value.

[0018] Furthermore, in step S5, XML is used to implement the part data description form under specific working conditions. The part data under specific working conditions is the result information. The result information describes the data information of a part under a certain working condition, including speed, torque, force, temperature, and time. The child nodes also contain the corresponding part ID. The result node has a unique ID, and in the relational data, the working condition ID and the result ID are bound together.

[0019] Furthermore, in step S6, XML is used to expand data exchange and storage. Under the working condition information description specification, new node types can be added, including data describing calculation methods, safety factors, industry standards, and empirical formulas. Relational data under the corresponding component relationship description specification node and result information under the working condition information description specification can also be added to realize the expanded function.

[0020] Furthermore, in step S7, XML is used to implement a data flattening development model. This mainly involves retrieving the ID of related information from the bound relational data through the ID of the component, and then using this ID to retrieve the desired gearbox data information from the components, loadcases, and results of the independent unit. This achieves flattened data storage and retrieval.

[0021] By employing the above technical solutions, this invention has the following advantages and positive effects compared with the prior art:

[0022] 1. The present invention provides an XML-based gearbox data exchange method, which proposes a scientific digital modeling method for gearboxes. Its flat data structure facilitates the addition, deletion, modification, and querying of data, as well as data management, and makes it easy to use programming languages ​​to achieve batch processing of data.

[0023] 2. The XML-based gearbox data exchange method described in this invention has a unique data description and storage format, which is conducive to data exchange between different CAE and OEM manufacturers. It also has compatibility with different types of data according to the above description format, making it convenient for each CAE and OEM manufacturer to expand the data content and format. Attached Figure Description

[0024] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0025] Figure 1 This invention uses XML to describe an assembly relationship diagram;

[0026] Figure 2 This is a diagram illustrating the description of a component in this invention;

[0027] Figure 3 This is a structural diagram showing the relationship between the results and the operating load in this invention;

[0028] Figure 4 This is an overall structural diagram of the gearbox data in this invention;

[0029] Figure 5 This is a diagram showing the relationship between the results, working conditions, and components in this invention.

[0030] Figure 6 This is a diagram illustrating the description method of a loadcase message in this invention;

[0031] Figure 7 This is a diagram illustrating the format of a result message in this invention;

[0032] Figure 8 This is a diagram illustrating the data application methods of different CAE software in this invention;

[0033] Figure 9 This is the EER diagram of the gearbox data document in this invention. Detailed Implementation

[0034] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. 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.

[0035] like Figures 1 to 9 As shown, this embodiment discloses an XML-based method for exchanging gearbox data. The method describes gearbox data, which is divided into three main categories: parts relationship description specifications (relations), parts unit description specifications (components), and load case description specifications (loadcases). This technical document is named GDBD (gearbox database) and implements the following functions:

[0036] Step S1: Use XML (Extensible Markup Language) as the primary form of data transmission;

[0037] Step S2: Use XML to describe the data of each component in the gearbox;

[0038] Step S3: Use XML to describe the relationships between the various components in the gearbox;

[0039] Step S4: Use XML to describe data under different operating conditions;

[0040] Step S5: Use XML to implement the component data description format under specific working conditions;

[0041] Step S6: Use XML to realize the data exchange and storage of results obtained from different working conditions, calculation methods, safety factors, industry standards, empirical formulas, etc.

[0042] Step S7: Use XML to implement a data flattening development model.

[0043] Furthermore, in step S1, XML is used as the data carrier language, and Schema and DTD are used to constrain document permissions and data validity. DTD is a syntax rule for XML used to validate XML files. Different users can share data by defining DTD elements. DTD has many element qualifiers, such as "()", "|", "`", "*", "?", and "+", each with a different meaning. For example, to ensure the uniqueness of the id attribute of each XML node, the syntax <!ELEMENTid#REQUIRED> can be used. Schema defines the attributes and elements of the XML document, ensuring that different users can obtain the same content and expanding the custom data types of XML. For example, the definition of time.<model date="2000-10-01T10:41:01+01:00"> This ensures that all users of the article receive the same amount of time.

[0044] Furthermore, in step S2, XML is used to describe the data of each component in the gearbox. The description of the component is divided into parent nodes and child nodes, and each parent node has a unique ID, which is used to bind with other gearbox data information; the child nodes contain information such as component attributes.

[0045] Furthermore, in step S3, XML is used to describe the relationships between the various components in the gearbox. The relational data in the gearbox includes four types of relationships: component-to-component, component-to-non-component, component-to-result, and operating condition-to-result. Similarly, component relational data has parent and child nodes, and both parent and child nodes must contain an 'id' attribute, which must be unique. The attribute information of other parent and child nodes can be added or deleted as needed.

[0046] Furthermore, in step S4, XML is used to describe different working condition data. The working condition information and result information both belong to the loadcases working condition type data. Each independent parent node of the working condition information contains a unique id, which facilitates retrieval through relational data. Its child nodes contain the corresponding specific data, and the child node attributes contain information such as name, unit, and value, but are not limited to the above information.

[0047] Furthermore, in step S5, XML is used to implement the data description format of parts under specific working conditions. The data of parts under specific working conditions is the result information, namely the result node. The result information describes the data information of a part under a certain working condition, including speed, torque, force, temperature, time, etc. The child nodes also contain the corresponding part ID. The result node has a unique ID, and in the relational data, the working condition ID and the result ID are bound together.

[0048] Furthermore, in step S6, XML is used to expand data exchange and storage. Under the working condition information description specification, new node types can be added, including data describing calculation methods, safety factors, industry standards, empirical formulas, etc. Relational data under the corresponding component relationship description specification node and result information under the working condition information description specification can be added to realize the extended function.

[0049] Furthermore, in step S7, XML is used to implement a data flattening development model. This mainly involves retrieving the ID of related information from the bound relational data through the ID of the component, and then using this ID to retrieve the desired gearbox data information from the components, loadcases, and results of the independent unit. This method achieves flattened data storage and retrieval, which is particularly convenient for the development of gearbox-related industrial internet apps.

[0050] Furthermore, by using EER diagrams and GBDB together, data flow between component manufacturers can be facilitated, accelerating development and manufacturing efficiency and improving collaborative development capabilities. The EER diagram primarily contains the overall structure of the transmission database, allowing for direct access to hierarchical relationships, understanding of the transmission data structure, and easy information extraction.

[0051] Specific examples:

[0052] This invention provides an XML-based method for exchanging transmission data, including the XML format, information description methods for transmission components, description methods for relationships between transmission components, description methods for different operating condition information, collaborative development and application methods using different CAE software, and data sharing methods among component manufacturers, wherein:

[0053] The XML format is the document format for gearbox data exchange standards. Data interface documents built using XML are structured and easy to operate. Furthermore, when describing gearbox data, XML's schema and DTD (Document Type Definition) technologies can be used to constrain the files, making information exchange standardized and consistent across various situations. Figure 1In this format, the parent node describes the type of information to be displayed, generally without containing specific values. The child nodes expand upon the parent node's information, which also also lacks specific values. Different attribute information can be added to each node, and is not limited to... Figure 1 The information shown includes the ID, data type, component name, etc., with parent and child nodes together forming a single gearbox data entry. The entire document comprises three parts: relations, components, and loadcases. For example... Figure 4 The three specification structures shown also include, among other things, the following: Figure 4 The diagram illustrates various subclass specifications. These subclasses may have relationships, using `id` as the parameter for specific relationships to achieve data flattening. This facilitates data extraction, storage, and categorization operations using program code.

[0054] The information description method of the transmission components, such as Figure 2 The image shows the data format for a bearing component. This component type data includes the parent node's ID, name, and type. The ID must be unique throughout the XML data document specification to distinguish different data entries. Furthermore, attribute information can be added, deleted, or modified appropriately to achieve flexibility and scalability in this technical document. If child nodes cover other information, they can be expanded until complete data information is covered. The child nodes mainly contain the component's name, data, and unit, but are not limited to specific types of the above. Gearboxes have a wide variety of components, including gears, shafts, bearings, abstract external load components, gear shifts, housings, and lubricating oil. This information can cover all independent component units and some abstract component units within the gearbox.

[0055] The method for describing the relationship information between the transmission components is as follows: Figure 3 As shown, this mainly illustrates the structure of the parent and child nodes for this data type, specifically as follows: Figure 1As shown, this is a similar XML document format. The `relations` feature includes relationships between components, relationships between components and non-components, relationships between components and results, and relationships between operating conditions and results. Relationships between components are varied, such as assembly relationships, side association relationships, and meshing relationships. These can be customized based on different components; for example, a bearing can be divided into information combinations of inner ring, outer ring, and rolling elements, and a gear shaft can be divided into information combinations of different shaft segments. Information between components and non-components is also varied, such as the matching relationship between a component and materials, the matching relationship between a component and lubrication, and the relationship between a component and non-components such as temperature. When using this information, the component's ID can be used to retrieve the child node IDs of related data with the same ID in the relational database. This allows for the search of the associated component or non-component IDs, and the assignment or extraction of values. The operating condition information and result relationship information, as well as the component information and result relationship information, adopt a flat data storage format, such as... Figure 3 The structure shown contains two child nodes under the parent node of the relation. These child nodes can be combinations of result and component, or result and operating condition. Here, only the relationship between the two child nodes is bound; both the child and parent nodes have unique IDs. The node data type is indicated, but the actual data value is not shown. The specific data value is as follows: Figure 4 The load case description is shown in the specification. The relationship between the load case, component, and result is as follows: Figure 5 As shown. The most important feature is that it has a unique ID, which is used to link various types of data. This flat data format can facilitate the development of gearbox software, as well as data sharing and collaborative development among different manufacturers.

[0056] The description methods of the different operating condition information, such as Figure 6-7 As shown, it means as Figure 4 The load information shown here is only a partial display. If more features are needed, such as calculation methods, safety factors, industry standards, and empirical formulas, simply add them as required. For example... Figure 6 As shown, this represents operating condition information, indicating the operating conditions under which the transmission system is running. Typical operating condition information includes initial torque, initial temperature, initial gear, running time, and external load. This information is contained under a loadcase node and records the actual data values. Multiple loadcases form various operating conditions. By finding the corresponding operating condition ID associated with the component through the child node information of the relationship data, the operating condition information of that component can be determined. For example... Figure 7As shown, this XML structure can represent the operational data or other data of a specific component. For example... Figure 7 The image shows the force, speed, and torque information of a gear under a specific operating condition. Information can be added or deleted as needed, thus enabling data scalability.

[0057] The collaborative development and application methods of different CAE software, such as Figure 8 As shown, by applying the above description specifications, a GBDB document database is formed, which can then be used to extract and store information in different CAE analysis software. Figure 8 The diagram illustrates how CAE software A performs initial data processing to create a basic GBDB document. This document is then sent to CAE software B for specialized development. The resulting data is then stored in a GBDB document according to the aforementioned document specifications. This new GBDB document is then sent to CAE software C, and this cycle repeats to achieve data exchange. Due to the classification and description format and structure of GBDB within XML, data can be easily transferred within a centralized database, enabling both relay-style development and independent specialized development. By using the ID of a specific component, one can find the IDs of related components, operating conditions, results, etc., in the relational database. Information can then be retrieved from the corresponding components, results, and loadcases using this ID.

[0058] The data sharing method of the component manufacturers, such as Figure 9 The diagram shown represents the EER diagram in MySQL. This database structure depicts the entire gearbox description document's structure and subcategories. Different companies can easily and quickly obtain key information by understanding and mastering the overall data structure using this method. Furthermore, by performing CRUD operations on the GBDB database and correspondingly modifying parts of the EER diagram, a manufacturer obtaining the GBDB database and EER diagram can quickly grasp the entire database structure and begin developing and producing their own corresponding data.

[0059] As described above, this invention achieves digital modeling of the transmission by establishing descriptive methods for each component of the gearbox, as well as relational and operational condition data description methods. This facilitates data sharing, is easy to operate, requires simple logical thinking, and is convenient for programming implementation. It also facilitates the development of industrial internet software and data sharing and collaborative development among manufacturers.

[0060] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for exchanging gearbox data based on XML, characterized in that, The data for the transmission is described, and the data types are divided into three main categories: part relationship description specifications, part unit description specifications, and operating condition information description specifications. These are described in detail through the following steps: Step S1: Use XML as the primary form of data carrier; Step S2: Use XML to describe the data of each component in the gearbox; In step S2, XML is used to describe the data of each component in the gearbox. The description of each component is divided into parent nodes and child nodes. Each parent node has a unique ID, which is used to bind with other gearbox data information. The child nodes contain component attribute information. Step S3: Use XML to describe the relationships between the various components in the gearbox; In step S3, XML is used to describe the relationships between the various components in the gearbox. The relational data in the gearbox includes four types of relationships: component-component, component-non-component, component-result, and operating condition-result. Similarly, the component relational data has parent nodes and child nodes, and both parent and child nodes must contain the attribute form of id, and the id must be unique. Step S4: Use XML to describe data under different operating conditions; In step S4, XML is used to describe different working condition data. The working condition information and result information both belong to the loadcases working condition type data. Each independent parent node of the working condition information contains a unique id, which facilitates retrieval through relational data. Its child nodes contain the corresponding specific data, and the child node attributes contain information such as name, unit, and value. Step S5: Use XML to implement the component data description format under specific working conditions; Step S6: Use XML to realize the data exchange and storage of results obtained from different working conditions, calculation methods, safety factors, industry standards, and empirical formulas; In step S6, XML is used to expand data exchange and storage. Under the working condition information description specification, new node types can be added, including data describing calculation methods, safety factors, industry standards, and empirical formulas. Relational data under the corresponding component relationship description specification node and result information under the working condition information description specification are also added to realize the expanded function. Step S7: Use XML to implement a data flattening development model; In step S7, XML is used to implement a flattened data development model. This mainly involves retrieving the ID of related information from the bound relational data using the ID of the component, and then using this ID to retrieve the desired gearbox data information from the components, loadcases, and results of the independent unit. This achieves flattened data storage and retrieval.

2. The method for exchanging gearbox data based on XML according to claim 1, characterized in that, In step S1, XML is used as the data carrier language, and Schema and DTD are used to constrain the permissions and data validity of the document.

3. The method for exchanging gearbox data based on XML according to claim 1, characterized in that, In step S5, XML is used to implement the data description format of parts under specific working conditions. The data of parts under specific working conditions is the result information. The result information describes the data information of a part under a certain working condition, including speed, torque, force, temperature and time. The child nodes also contain the ID of the corresponding part. The result node has a unique ID, and in relational data, the condition ID and the result ID are bound together.

Images