A data transmission method and system based on associated references
By obtaining the associated references of components and populating them into the context library for data processing, the problem of low data transmission efficiency in the business model is solved, and the associated references between components are realized, thereby improving the data transmission efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- HANGZHOU FRAUDMETRIX TECH CO LTD
- Filing Date
- 2022-06-29
- Publication Date
- 2026-07-10
Smart Images
Figure CN115292252B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a data transmission method and system based on associated references. Background Technology
[0002] Business platforms based on big data and other technologies can provide users with various business services, generating a large amount of business data in the process. Based on user needs or the needs of the business platform, this business data needs to be transmitted according to certain data processing methods. The main methods for transmitting data from business models include the following two:
[0003] Technical Solution 1: Importing and exporting business model data based on a relational database. In this solution, the configuration of the business model is stored in a relational database. When executing a data export task, it is necessary to query the business model configuration from the relational database based on the business model identifier, and then perform operations such as serialization and encryption on the configuration information. During the data import process, the imported encrypted files also need to be decrypted and deserialized, modifying the data in the relational database. Multiple import and export operations are required for each business, making cascading import and export impossible, as well as one-click import and export operations.
[0004] Technical Solution 2: Import and export business model data based on configuration parsing. This solution enables one-click import and export of business models and related business models. However, parsing the business model configuration consumes a significant amount of time. If the business model configuration is complex and the dependencies between business models are deep, it is necessary to parse the configuration of each business model and then query its dependent business models, traversing layer by layer to export the business models, resulting in low efficiency in data transfer of business models.
[0005] Currently, no effective solutions have been proposed for the problems in the relevant technologies. Summary of the Invention
[0006] This application provides a data transmission method and system based on association references, which at least solves the problem of improving the data transmission efficiency of business models while realizing one-click import and export of business model data in related technologies.
[0007] In a first aspect, embodiments of this application provide a data transfer method based on associated references, the method including data export and data import, wherein, during the data export process:
[0008] Obtain an export request, wherein the export request contains the type and identifier of the component to be exported, and obtain the current component based on the type and identifier of the component to be exported;
[0009] Query the associated references of the current component to obtain the type and identifier of the dependent component, and then obtain the dependent components of the current component, wherein the dependent components include direct dependent components and indirect dependent components;
[0010] The file data of the current component and its dependent components is populated into the context component library and processed. The resulting file stream is then exported.
[0011] In some embodiments, during the data import process:
[0012] Obtain an import request, wherein the import request contains the file data and type of the component to be imported;
[0013] Obtain the import mode, and import the file data according to the import mode, wherein the import mode includes add, overwrite, version creation and skip.
[0014] In some embodiments, the method further includes, prior to data import / export:
[0015] Based on the complexity of the dependencies between business models, the business models are categorized into underlying components, basic components, and business components.
[0016] Based on the dependencies, construct the associated references between the underlying components, basic components, and business components.
[0017] In some embodiments, an import request is obtained, wherein the import request contains files containing the components to be imported, including:
[0018] The file data of the component to be imported is decrypted. After successful decryption, the file data is deserialized and parsed. The deserialized and parsed data is converted into a standard component model and populated into the context component library.
[0019] Determine whether authentication is required. If so, verify the file data in the context component library. If the verification passes, obtain the import mode. If not, directly obtain the import mode.
[0020] In some embodiments, importing data into the file includes:
[0021] Depending on the type of component to be imported, the data is imported first from the underlying components, then from the basic components, and finally from the business components.
[0022] In some embodiments, the business models are categorized based on the complexity of the dependencies between them, resulting in underlying components, basic components, and business components, including:
[0023] Based on the complexity of the dependencies between business models, the business models are classified into different types.
[0024] If the complexity of the dependencies of the current business model is less than the first threshold, then the current business model is a bottom-level component;
[0025] If the complexity of the dependency relationship of the current business model is greater than the first threshold but less than the second threshold, then the current business model is a basic component.
[0026] If the complexity of the dependencies in the current business model is greater than the second threshold, then the current business model is a business pricing model.
[0027] In some embodiments, populating the context component library with file data of the current component and dependent components and performing data processing includes:
[0028] Based on the association references between the current component and its dependent components, the file data of the current component and its dependent components are populated into the context component library in a hierarchical manner;
[0029] Based on the file type exported by the current component, the file data is serialized and encrypted.
[0030] In some embodiments, exporting the file stream obtained after data processing includes:
[0031] Based on the hierarchical structure of component population in the context component library, the file data of the current component is exported first, and then the file data of dependent components is exported.
[0032] In some embodiments, the context component library is a collection of key-value pairs, where the key is the type of the business component and the value is the business model of the business component.
[0033] Secondly, embodiments of this application provide a data transmission system based on association references, characterized in that the system includes an application adaptation layer module, an import / export module, a component management module, and an association reference module, wherein during the data export process:
[0034] The application adaptation layer module is used as the interface entry point for external systems to obtain import / export requests, wherein the export request includes the type and identifier of the component to be exported.
[0035] The component management module is used to obtain the current component and its configuration details based on the type and identifier of the component to be exported.
[0036] The associated reference module is used to query the associated references of the current component to obtain the type and identifier of the dependent component;
[0037] The component management module is also used to obtain the dependent components of the current component according to the type and identifier of the dependent components;
[0038] The import / export module is used to populate the file data of the current component and dependent components into the context component library and perform data processing, and then export the resulting file stream.
[0039] Compared to related technologies, this application provides a data transmission method and system based on associated references. The method includes data export and data import. During data export: an export request is obtained, containing the type and identifier of the component to be exported; the current component is obtained based on the type and identifier of the component to be exported; the associated references of the current component are queried to obtain the types and identifiers of dependent components, thereby obtaining the dependent components of the current component, including direct and indirect dependent components; the file data of the current component and dependent components are populated into a context component library and processed; the resulting file stream is exported. This solves the problem of low efficiency in data transmission of business models, realizes the construction of associated references between components, and enables one-click, cascading export of components based on these associated references, while improving the data transmission efficiency of business models. Attached Figure Description
[0040] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:
[0041] Figure 1 This is a flowchart illustrating the steps of a data export method based on associated references according to an embodiment of this application;
[0042] Figure 2 This is a schematic diagram illustrating the data export interface implemented according to an embodiment of this application;
[0043] Figure 3 This is a flowchart of the steps of a data import method based on associated references according to an embodiment of this application;
[0044] Figure 4 This is a schematic diagram illustrating the data import interface implemented according to an embodiment of this application;
[0045] Figure 5 This is a schematic diagram illustrating the component type classification according to embodiments of this application;
[0046] Figure 6 This is a schematic diagram of the inter-component association reference fields according to an embodiment of this application;
[0047] Figure 7This is a structural block diagram of a data transmission system based on associated references according to an embodiment of this application;
[0048] Figure 8 This is a schematic diagram of the internal structure of an electronic device according to an embodiment of this application.
[0049] Figure descriptions: 71. Application Adaptation Layer Module; 72. Import / Export Module; 73. Component Management Module; 74. Association Reference Module. Detailed Implementation
[0050] To make the objectives, technical solutions, and advantages of this application clearer, the application is described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application.
[0051] Obviously, the accompanying drawings described below are merely some examples or embodiments of this application. Those skilled in the art can apply this application to other similar scenarios based on these drawings without any inventive effort. Furthermore, it is understood that although the efforts made in this development process may be complex and lengthy, for those skilled in the art related to the content disclosed in this application, any changes to design, manufacturing, or production based on the technical content disclosed in this application are merely conventional technical means and should not be construed as insufficient disclosure of the content of this application.
[0052] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment that is mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.
[0053] Unless otherwise defined, the technical or scientific terms used in this application shall have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms “a,” “an,” “an,” “the,” and similar words used in this application do not indicate quantity limitation and may indicate singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units not listed, or may include other steps or units inherent to these processes, methods, products, or devices. The terms “connected,” “linked,” “coupled,” and similar words used in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. “Multiple” used in this application refers to two or more. “And / or” describes the relationship between related objects, indicating that three relationships may exist; for example, “A and / or B” can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following objects are in an "or" relationship. The terms "first," "second," and "third" used in this application are merely to distinguish similar objects and do not represent a specific ordering of the objects.
[0054] This application provides a data transfer method based on associated references, which includes data export and data import. Figure 1 This is a flowchart illustrating the steps of a data export method based on associated references according to an embodiment of this application, as follows: Figure 1 As shown, the data export process includes the following steps:
[0055] Step S102: Obtain the export request, wherein the export request contains the type and identifier of the component to be exported, and obtain the current component according to the type and identifier of the component to be exported;
[0056] Specifically, when a user passes on an export request, the current component is retrieved from the component management domain based on the component type and identifier passed by the user. It should be noted that in this embodiment, the data transmission of components is uniformly maintained in the component management domain. If the export or import requires the use of a specific type of component, it can be directly retrieved from the global component management domain. Furthermore, the component management domain also maintains the dependency relationships of each component.
[0057] It should be noted that the components in this application refer to the business model, that is, the data model used for business processing.
[0058] Step S104: Query the associated references of the current component to obtain the type and identifier of the dependent component, and then obtain the dependent components of the current component. The dependent components include direct dependent components and indirect dependent components.
[0059] Specifically, the acquisition of the type, identifier, and the component itself as a dependency is obtained recursively during the component drill-down process. For example, current component A directly depends on components B, C, and D (A->B, A->C, and A->D), and indirectly depends on components E, F, M, and N (B->E, B->F, C->M, and C->N). That is, current component A belongs to the first level, directly dependent components B, C, and D belong to the second level, and indirectly dependent components E, F, M, and N belong to the third level. During the component export process, dependent components B, C, and D are found through current component A; when exporting component A, B, C, and D are then exported; when drilling down to component B, components E and F are found through component B and exported. Similarly, based on the dependency relationship of component C, components M and N are found and exported. Through this top-to-bottom hierarchical recursion, the file data of all dependent components is obtained and populated into the context's component library.
[0060] Step S106: Populate the file data of the current component and dependent components into the context component library and process the data; then export the file stream obtained after data processing.
[0061] Specifically, based on the association references between the current component and its dependent components, the file data of the current component and its dependent components are hierarchically populated into the context component library; the file data is serialized and encrypted according to the exported file type of the current component; and based on the hierarchical structure of component population in the context component library, the file data of the current component is exported first, followed by the file data of the dependent components. Furthermore, this context component library is a collection of key-value pairs, where the key is the type of the business component, and the value is the business model of the business component.
[0062] Preferably, the components are exported according to the hierarchical structure of the component population in the context component library. For example, the current component A → B, A → C, A → D, while B → E, B → F, C → M, C → N. That is, the current component A belongs to the first level in the context component library, the dependent components B, C, and D belong to the second level, and the dependent components E, F, M, and N belong to the third level. During the component export process, the current component A is exported first, followed by the directly dependent components B, C, and D, and finally the indirectly dependent components E, F, M, and N.
[0063] More preferably, the data export method of steps S102 to S106 can be implemented by defining an interface. Figure 2This is a schematic diagram illustrating the data export interface implemented according to an embodiment of this application, as shown below. Figure 2 As shown, three interfaces are defined: ExportProcess, IExport, and IComponent. The ExportProcess interface defines the three stages: before export, the export action, and after export. The IComponent interface defines an abstraction of the export method, and the IComponent interface inherits from the IComponent interface. These interfaces satisfy the single responsibility principle; the implementation of file data export for specific components only requires constructing these interfaces.
[0064] Through steps S102 to S106 in the embodiments of this application, while ensuring one-click import and export of business model data, the problem of low efficiency in data transmission of business models is solved, the construction of inter-component references is realized, and one-click and cascading export of components is realized based on the references, thereby improving the data transmission efficiency of business models.
[0065] This application provides a data transfer method based on associated references. The method includes data export and data import. It should be noted that the import process requires two interactions with the front end. The first interaction mainly involves the validation of various components. Based on the validation results, the import modes of each component are integrated and returned to the front end for the user to select. Furthermore, during this process, the front end will also present the validation results of each component to the user in a table format for the user to selectively download. The second interaction involves the user confirming the import mode and actually executing the import details. In the previous step, no substantial changes have been made to the component configuration. After the second interaction (user confirmation), the import operation is submitted and the import operation is executed specifically according to the import mode selected by the user for each component. The import operation of each component is different, so the implementation details of the import lie within the component itself.
[0066] Figure 3 This is a flowchart of the steps of the data import method based on associated references according to an embodiment of this application, as follows: Figure 3 As shown, the data export process includes the following steps:
[0067] Step S302: Obtain an import request, wherein the import request contains the file data and type of the component to be imported;
[0068] Specifically, the user selects the file of the component to be imported and sends the specific core parameters to the backend. The file data of the component to be imported is decrypted. After successful decryption, the file data is deserialized and parsed, and the deserialized data is converted into a standard component model and populated into the context component library. It is then determined whether authentication is required. If so, the file data in the context component library is verified. If the verification passes, the import mode is obtained, and the file data verified according to the import mode is imported. If not, the import mode is directly obtained, and the file data is imported according to the import mode.
[0069] Preferably, the user selects the file of the component to be imported and sends the specific request core parameters to the backend. Based on these parameters, the backend determines the number of interactions with the frontend. If it's the first time, the file is parsed, and the parsed detailed component configuration information is populated into the context component library. Then, a validation operation is performed, including missing item validation, component configuration validation, import environment validation, and user permission validation. For example, missing item validation verifies the component's configuration information, deleting missing items or filling in special or equal values. Import environment validation verifies whether the system environment executing the current import operation meets the requirements, or whether the hardware conditions of the processing device meet the requirements. There is no specific order among these validations. After all validations are completed, the component import mode is assembled based on the validation results, and the status, files, and validation information of the current batch of export tasks are written to a relational database. Each batch of import tasks has a unique task identifier. The validation details and missing items for each component are provided to the user in a table for download and data comparison.
[0070] Step S304: Obtain the import mode and import the file data according to the import mode. The import modes include add, overwrite, version creation and skip.
[0071] Specifically, depending on the type of component to be imported, the file data of the underlying component is imported first, then the file data of the basic component is imported, and finally the file data of the business component is imported.
[0072] Preferably, after the verification and other operations in step S302 are completed, the page obtains the import mode. The user determines the import mode of the component based on the component's positioning and the actual business scenario configuration. During the second interaction with the front end, the request parameters will carry the import mode of each component and the task identifier returned during the first interaction to send a request to the back end. The back end imports each component according to the import mode passed by the user. Processing starts from the bottom-level components. After all the bottom-level components are successfully imported, the basic components are processed. At this time, all the bottom-level components that the basic components depend on have been imported. Finally, the most complex business components are configured. After all components are imported, the import tasks of the current batch are archived in the form of tasks and recorded in the relational database.
[0073] More preferably, the data import method in steps S302 to S304 can be implemented by defining an interface. Figure 4 This is a schematic diagram illustrating the data import interface implemented according to an embodiment of this application, as shown below. Figure 4 As shown, three interfaces are defined: ImportProcess, ImportImport, and Component. The ImportProcess interface defines the two-way interaction with the frontend. The ComponentImport interface abstracts the import method, encapsulating the core import process. It eliminates the need to worry about details like decryption and validation during the import process; simply calling the interface implements the entire import process. The ComponentImport interface inherits from the ComponentImport interface. These interfaces adhere to the Single Responsibility Principle, the Open / Closed Principle (OCP), and the Interface Segregation Principle. Implementing file data export for specific components only requires building these interfaces. By abstracting the core import process and delegating all validation and import details to the interfaces, developers and subsequent component extensions only need to focus on the component itself, without needing to worry about the overall process.
[0074] Through steps S302 to S304 in the embodiments of this application, while ensuring one-click import and export of business model data, the problem of low efficiency in data transmission of business models is solved, the construction of inter-component references is realized, and one-click and cascading import of components is realized based on the references, thereby improving the data transmission efficiency of business models.
[0075] In some embodiments, the components need to be categorized by type before data import and export.
[0076] Specifically, Figure 5 This is a schematic diagram illustrating the component type classification according to embodiments of this application, such as... Figure 5As shown, before importing and exporting data, business models are categorized based on the complexity of their dependencies. If the complexity of the dependencies of the current business model is less than the first threshold, then the current business model is a bottom-level component; if the complexity of the dependencies of the current business model is greater than the first threshold but less than the second threshold, then the current business model is a basic component; if the complexity of the dependencies of the current business model is greater than the second threshold, then the current business model is a business component. It should be noted that the first threshold is less than the second threshold, and the values of the first and second thresholds can be set according to actual needs.
[0077] Preferably, for low-level components (low-level components do not depend on other components, i.e., the complexity of the dependency relationship is zero), they are classified as low-level components; for components that only depend on low-level components, have few dependencies, and do not contain business configuration, they are classified as basic components (only depend on low-level components, and the complexity of the dependency relationship is low); for components that contain upper-level business configuration and have more complex dependencies, they are classified as business components (can depend on any type of component, and the complexity of the dependency relationship is higher).
[0078] Specifically, Figure 6 This is a schematic diagram of the inter-component reference domain according to an embodiment of this application. Based on dependencies, it constructs inter-component references between underlying components, basic components, and business components. It should be noted that constructing inter-component references is one of the core aspects of this invention, enabling one-click import and export. In addition to the function of constructing inter-component references (relationship building), the inter-component reference domain also has functions such as relationship updating, relationship querying, and relationship dissolution. By using inter-component reference domains, the component configuration parsing process is reduced, and components at each layer do not need to care about which components they depend on, but only need to care about the import and export implementation details of the current layer.
[0079] It should be noted that the steps shown in the above process or in the flowchart of the accompanying figures can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.
[0080] This application provides a data transmission system based on associated references. Figure 7 This is a structural block diagram of a data transmission system based on associated references according to an embodiment of this application, such as... Figure 7 As shown, the system includes an application adaptation layer module 71, an import / export module 72, a component management module 73, and an association reference module 74. During the data export process:
[0081] Application adaptation layer module 71 is used as the interface entry point for external systems to obtain import and export requests, wherein the export request includes the type and identifier of the component to be exported; component management module 73 is used to obtain the current component and the configuration details of the component based on the type and identifier of the component to be exported.
[0082] The associated reference module 74 is used to query the associated references of the current component to obtain the type and identifier of the dependent components;
[0083] The component management module 73 is also used to obtain the dependent components of the current component based on the type and identifier of the dependent components;
[0084] The import / export module 72 is used to populate the file data of the current component and its dependent components into the context component library and process the data, then export the resulting file stream.
[0085] The application adaptation layer module 71, import / export module 72, component management module 73, and association reference module 74 in this embodiment solve the problem of low efficiency in data transmission of business models, realize the construction of association references between components, and realize one-click and cascading export of components based on the association references, thereby improving the data transmission efficiency of business models.
[0086] It should be noted that the above modules can be functional modules or program modules, and can be implemented through software or hardware. For modules implemented through hardware, the above modules can reside in the same processor; or the above modules can be located in different processors in any combination.
[0087] This embodiment also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0088] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.
[0089] It should be noted that the specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.
[0090] Furthermore, in conjunction with the data transfer method based on association references in the above embodiments, this application embodiment can provide a storage medium for implementation. This storage medium stores a computer program; when executed by a processor, the computer program implements any of the data transfer methods based on association references in the above embodiments.
[0091] In one embodiment, a computer device is provided, which may be a terminal. The computer device includes a processor, memory, a network interface, a display screen, and an input device connected via a system bus. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, it implements a data transfer method based on associative references. The display screen of the computer device may be a liquid crystal display (LCD) or an electronic ink display. The input device of the computer device may be a touch layer covering the display screen, or buttons, a trackball, or a touchpad located on the casing of the computer device, or an external keyboard, touchpad, or mouse, etc.
[0092] In one embodiment, Figure 8 This is a schematic diagram of the internal structure of an electronic device according to an embodiment of this application, such as... Figure 8 As shown, an electronic device is provided, which can be a server, and its internal structure diagram can be as follows. Figure 8 As shown, the electronic device includes a processor, a network interface, internal memory, and non-volatile memory connected via an internal bus. The non-volatile memory stores the operating system, computer programs, and a database. The processor provides computing and control capabilities, the network interface communicates with external terminals via a network connection, the internal memory provides an environment for the operation of the operating system and computer programs, the computer programs are executed by the processor to implement a data transfer method based on associative references, and the database stores data.
[0093] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.
[0094] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.
[0095] Those skilled in the art should understand that the technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments have been described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0096] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.
Claims
1. A data transfer method based on association references, characterized in that, The method includes data export and data import; Based on the complexity of the dependencies between business models, the business models are categorized into underlying components, basic components, and business components. Specifically, if the complexity of the dependencies of the current business model is less than a first threshold, then the current business model is an underlying component; if the complexity of the dependencies of the current business model is greater than the first threshold but less than a second threshold, then the current business model is a basic component; and if the complexity of the dependencies of the current business model is greater than the second threshold, then the current business model is a business component. The association reference field constructs association references between the underlying components, basic components, and business components based on the dependency relationships. The association reference field also has the functions of updating association reference relationships, querying relationships, and breaking relationships. During the data export process: Obtain an export request, wherein the export request contains the type and identifier of the component to be exported, and obtain the current component based on the type and identifier of the component to be exported; Query the associated references of the current component to obtain the type and identifier of the dependent components, and then obtain the dependent components of the current component; The file data of the current component and its dependent components is populated into the context component library and processed. The resulting file stream is then exported.
2. The method according to claim 1, characterized in that, During the data import process: Obtain an import request, wherein the import request contains the file data and type of the component to be imported; Obtain the import mode, and import the file data according to the import mode, wherein the import mode includes add, overwrite, version creation and skip.
3. The method according to claim 2, characterized in that, Obtain an import request, wherein the import request contains files containing the components to be imported, including: The file data of the component to be imported is decrypted. After successful decryption, the file data is deserialized and parsed. The deserialized and parsed data is converted into a standard component model and populated into the context component library. Determine whether authentication is required. If so, verify the file data in the context component library. If the verification passes, obtain the import mode. If not, directly obtain the import mode.
4. The method according to claim 2 or 3, characterized in that, Importing data into the file includes: Depending on the type of component to be imported, the data is imported first from the underlying components, then from the basic components, and finally from the business components.
5. The method according to claim 1, characterized in that, Populating the file data of the current component and its dependent components into the context component library and performing data processing includes: Based on the association references between the current component and its dependent components, the file data of the current component and its dependent components are populated into the context component library in a hierarchical manner; Based on the file type exported by the current component, the file data is serialized and encrypted.
6. The method according to claim 5, characterized in that, Exporting the file stream obtained after data processing includes: Based on the hierarchical structure of component population in the context component library, the file data of the current component is exported first, and then the file data of dependent components is exported.
7. The method according to claim 1, characterized in that, The context component library is a collection of key-value pairs, where the key is the type of the business component and the value is the business model of the business component.
8. A data transmission system based on association references, characterized in that, The system includes an application adaptation layer module, an import / export module, a component management module, and an association / reference module. Based on the complexity of the dependencies between business models, the business models are categorized into underlying components, basic components, and business components. Specifically, if the complexity of the dependencies of the current business model is less than a first threshold, then the current business model is an underlying component; if the complexity of the dependencies of the current business model is greater than the first threshold but less than a second threshold, then the current business model is a basic component; and if the complexity of the dependencies of the current business model is greater than the second threshold, then the current business model is a business component. The association reference field constructs association references between the underlying components, basic components, and business components based on the dependency relationships. The association reference field also has the functions of updating association reference relationships, querying relationships, and breaking relationships. During the data export process: The application adaptation layer module is used as the interface entry point for external systems to obtain import / export requests, wherein the export request includes the type and identifier of the component to be exported. The component management module is used to obtain the current component and its configuration details based on the type and identifier of the component to be exported. The associated reference module is used to query the associated references of the current component to obtain the type and identifier of the dependent component; The component management module is also used to obtain the dependent components of the current component according to the type and identifier of the dependent components; The import / export module is used to populate the file data of the current component and dependent components into the context component library and perform data processing, and then export the resulting file stream.