System interfacing method, computer device, storage medium and product

Abstract

The application relates to a system docking method, a computer device, a storage medium and a product. The method comprises the following steps: acquiring a first interface for docking with a second system in a first system, and acquiring a second interface for docking with the first system in the second system; creating a first field group corresponding to the first interface and a second field group corresponding to the second interface according to field information corresponding to the first interface and the second interface; determining a mapping relationship between the first field group and the second field group according to a system docking agreement; and mapping fields in the first field group to corresponding second field groups respectively according to the mapping relationship. The method can solve the problem of low system docking stability.

Description

Technical Field

[0001] This application relates to the field of information system integration, and in particular to system interface methods, computer equipment, storage media and products. Background Technology

[0002] In the field of information system integration, the integration of multiple systems is often involved. Traditional integration methods have many drawbacks. Typically, the two parties involved first agree on the interface fields, detailed field descriptions, message formats, and request methods, or directly select an existing interface from one party. Then, they proceed to the substantive code writing phase, followed by interface testing and integration. However, this integration model involves multiple complex and time-consuming steps, as well as a large amount of manual coding, which can easily lead to deviations in the entire integration process and result in low system integration stability.

[0003] There is currently no effective solution to the problem of low system integration stability in related technologies. Summary of the Invention

[0004] Therefore, it is necessary to provide a system docking method, computer equipment, storage medium, and product that can solve the problem of low system docking stability, in response to the above-mentioned technical problems.

[0005] Firstly, this embodiment provides a system docking method, the method comprising:

[0006] In the first system, obtain the first interface for interfacing with the second system; in the second system, obtain the second interface for interfacing with the first system.

[0007] Based on the field information corresponding to the first interface and the second interface, create a first field group corresponding to the first interface and a second field group corresponding to the second interface;

[0008] According to the system interface agreement, the mapping relationship between the first field group and the second field group is determined;

[0009] Based on the mapping relationship, the fields in the first field group are mapped to the corresponding second field groups.

[0010] In some embodiments, before mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship, the method includes:

[0011] Determine whether the message structure of the first field group conforms to the preset message structure;

[0012] If the message structure does not conform to the preset message structure, then a message template is constructed according to the preset message structure;

[0013] The values ​​in the first field group are filled into the message template to obtain the first field group that conforms to the preset structure.

[0014] In some embodiments, determining whether the message structure of the first field group conforms to the preset message structure corresponding to the second interface includes:

[0015] The preset message structure is obtained based on the markup language and / or hierarchical features corresponding to the second interface;

[0016] Determine whether the message structure in the first field group conforms to the preset message structure.

[0017] In some embodiments, before mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship, the method further includes:

[0018] Test cases are constructed based on the field validation rules of the first field group and the first interface;

[0019] If the test cases confirm successful integration between the first system and the second system, the fields in the first field group are mapped to the corresponding second field group based on the mapping relationship.

[0020] In some embodiments, constructing test cases based on the fields and field validation rules entered in the first interface includes:

[0021] Combine the fields in the first field group;

[0022] Based on the combined fields, generate test data that conforms to the field validation rules;

[0023] The test cases are constructed by combining the combined fields and the test data.

[0024] In some embodiments, creating a first field group corresponding to the first interface and a second field group corresponding to the second interface based on field information corresponding to the first interface and the second interface includes:

[0025] The fields of the first interface are divided according to the message structure and field name corresponding to the fields of the first interface as required, to obtain the first field group;

[0026] As needed, the message structure and field names of the fields of the second interface are entered, and the fields of the second interface are divided to obtain the second field group.

[0027] In some embodiments, after mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship, the method further includes:

[0028] Based on the field mapping results between the first field group and the second field group within a preset time period, adjust the number of users using the first interface and the second interface to connect to the first system and the second system.

[0029] Thirdly, this embodiment provides a computer device including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the system docking method described in the first aspect above.

[0030] Fourthly, this embodiment provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the system docking method described in the first aspect above.

[0031] Fifthly, this embodiment provides a computer program product, including a computer program that, when executed by a processor, implements the system interfacing method described in the first aspect above.

[0032] The aforementioned system docking method, computer equipment, storage medium, and products improve system docking stability by grouping the fields of the first and second interfaces during system docking, thereby distinguishing the interface field flow between systems through field groups. Attached Figure Description

[0033] Figure 1 This is an application environment diagram of the system docking method in one embodiment;

[0034] Figure 2 This is a flowchart illustrating a system docking method in one embodiment;

[0035] Figure 3 This is a flowchart illustrating the rule engine execution system integration method in one embodiment;

[0036] Figure 4 This is a structural block diagram of the system docking device in one embodiment;

[0037] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with 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.

[0039] The system docking method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown. It can be applied to, for example... Figure 1 The application environment shown. For example... Figure 1 As shown, terminal 102 communicates with N systems 104 via a network, and connects to multiple systems to achieve interoperability between them. Here, N is a positive integer, N≥2. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, and tablets. Furthermore, terminal 102 can also communicate with a server via the network, where a data storage system stores the data that server 104 needs to process. This data storage system can also be located in the cloud or on other network servers. Furthermore, system 104 can include servers, routers, gateways, and multiple devices.

[0040] In one embodiment, such as Figure 2 As shown, a system docking method is provided, which can be applied to Figure 1 Taking the terminal in the example, the explanation includes the following steps:

[0041] Step 202: Obtain the first interface for interfacing with the second system in the first system, and obtain the second interface for interfacing with the first system in the second system.

[0042] The first system and the second system can be any type of computer system; the system types of the first system and the second system can be the same or different, and there is no limitation here. The first interface and the second interface can be existing interfaces in the first system and the second system, or they can be created according to the docking requirements of the first system and the second system. The first interface is used for data exchange with the second system, and the second interface is used for data exchange with the first system.

[0043] Optionally, based on system integration requirements, one or more first interfaces are created in the first system for integration with the second system, and one or more second interfaces are created in the second system for integration with the first system.

[0044] Step S204: Based on the field information corresponding to the first interface and the second interface, create a first field group corresponding to the first interface and a second field group corresponding to the second interface.

[0045] The field information includes, but is not limited to, the content, format, and type of the fields that need to be input into the first interface, and the content, format, and type of the fields that need to be input into the second interface. Furthermore, the field information can also be field mapping conditions manually set according to business requirements.

[0046] Optionally, based on the field information corresponding to the first interface, one or more first field groups are created under the first interface, with different field contents in different first field groups. Synchronously or asynchronously, based on the field information corresponding to the second interface, one or more second field groups are created under the second interface, with different field contents in different second field groups.

[0047] Step S206: Determine the mapping relationship between the first field group and the second field group according to the system interface agreement.

[0048] The system integration agreements include, but are not limited to, the defined first interface agreement, second interface agreement, message definitions, field validation rules, and request / response formats transmitted in the first and second systems. Optionally, the upstream and downstream of the data mapping are determined based on the first and second interface agreements to obtain the data flow direction, and then the mapping relationship between each field group is established based on the data flow direction.

[0049] Step S208: Map the fields in the first field group to the corresponding second field group according to the mapping relationship.

[0050] Optionally, the field data to be transmitted is entered into the first interface, the first field group corresponding to the field data is determined, and the first field group is mapped to the corresponding second field group in the second interface according to the mapping relationship, so as to realize the upstream and downstream mapping.

[0051] Furthermore, the terminal includes a visual rule engine, which enables the implementation of steps S202 to S208 above, making the connection between the first system and the second system easier to maintain, and making the data flow between the first system and the second system clearer and more transparent.

[0052] In the above system integration method, the fields of upstream and downstream are grouped by combining the field information of the first and second interfaces during system integration, resulting in the first field group and the second field group, as well as the mapping relationship between the first field group and the second field group. By distinguishing the direction of interface fields between systems through the mapping relationship, the error rate of system integration can be reduced, thereby improving stability.

[0053] In one embodiment, before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship, the method includes: determining whether the message structure of the first field group conforms to the preset message structure corresponding to the second interface; if the message structure does not conform to the preset message structure, constructing a message template according to the preset message structure; mapping the values ​​in the first field group to the message template to obtain a field group that conforms to the preset structure.

[0054] The message structure includes, but is not limited to, the message hierarchy; the data in the message header, message trailer, and message body adopts a protocol and format. Optionally, the hierarchical structure of the message composed of each field in the first field group and the hierarchical structure of the message to be received by the second interface are obtained, and it is determined whether the hierarchical structure of the message corresponding to the first field group is the same as the hierarchical structure of the message corresponding to the second interface. If they are the same, the message structure conforms to the preset message structure. If they are not the same, the following steps are executed: construct a message template according to the preset message structure; fill the values ​​in the first field group into the message template to obtain a field group that conforms to the preset structure.

[0055] The message template includes a pre-defined message structure framework. Optionally, the message template includes one or more expressions, which indicate information about the values ​​of variables, access indexes, and access objects corresponding to key names. Values ​​corresponding to the key names specified by the expressions are selected from the first field group and populated into the expressions to obtain the first field group conforming to the pre-defined structure. Optionally, the message template includes one or more expressions that dynamically reference the attribute values ​​of variables or objects in the first field group. The attribute values ​​of each variable or object in the first field group are extracted by a script, and the values ​​of the attributes of each variable or object in the first field group are mapped to the message template according to the expressions to obtain the first field group conforming to the pre-defined structure.

[0056] Furthermore, before mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship, data filtering and cleaning can be performed on the field data.

[0057] In this embodiment, by performing intermediate conversion on the structure of the message composed of fields, the problems of configuration difficulties and code redundancy caused by language differences between interfacing systems can be reduced. This reduces the instability of system interfacing caused by complex configuration and redundant code, and at the same time, it is convenient to modify the system interfacing method according to business requirements, which is beneficial to the operation and maintenance of the system.

[0058] Further, in one embodiment, determining whether the message structure of the first field group conforms to the preset message structure includes: obtaining the preset message structure based on the markup language and / or hierarchical features corresponding to the second interface; and determining whether the message structure in the first field group conforms to the preset message structure.

[0059] In this context, the markup language of the second interface refers to the language or format used to describe and define the interface structure, behavior, and interaction methods; the hierarchical features refer to the organization of each level of the messages that the second interface needs to receive. Optionally, after determining the preset message structure based on the markup language and hierarchical features, a message template conforming to the corresponding hierarchical features of the second structure is constructed based on the markup language. In this embodiment, obtaining the preset message structure based on the markup language allows for intermediate message conversion when the upstream and downstream systems use different markup languages; obtaining the preset message structure through hierarchical features allows for adjustment of the upstream data hierarchy complexity, ensuring that the adjusted field data corresponds to the downstream data hierarchy complexity; thereby reducing the error rate during system integration.

[0060] In one embodiment, before mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship, the method further includes: constructing test cases according to the field validation rules of the first field group and the first interface; and if the test cases verify that the first system and the second system have successfully connected, mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship.

[0061] The field validation rules for the first interface are derived from the system integration agreement, including but not limited to validating the format and content of the input fields. Optionally, parameters for constructing test cases are built based on the field validation rules of the first field group and the first interface. Multiple test cases are generated by adjusting the parameters to simulate whether the integration of the first and second systems meets the integration requirements under the currently configured parameters. The rationality and completeness of the data content transmitted between the first and second systems, the data format, and one or more other aspects can be verified based on the integration requirements. If the simulation results of the test cases do not meet the integration requirements, it is determined that the first and second systems cannot successfully integrate, and the configuration parameters of the first and second interfaces are incorrect. The configuration parameters can be adjusted until the first and second systems successfully integrate. Optionally, test case construction and verification can be achieved through visual configuration, thereby achieving effective system configuration evaluation with a small amount of code. Furthermore, after automatically constructing test cases and completing the test case simulation request, the test structure can be recorded, and statistical reports of the system response can be generated.

[0062] In this embodiment, by constructing and verifying test cases, the amount of code development is reduced and configuration logic problems are reduced, thereby improving the stability of system integration.

[0063] Furthermore, in one embodiment, constructing test cases based on the fields and field validation rules entered in the first interface includes: combining the fields in the first field group; generating test data that conforms to the field validation rules based on the combined fields; and constructing test cases by combining the combined fields and the test data.

[0064] This involves combining fields from one or more of the first field groups. Optionally, the following characteristics of the fields are determined: the field is empty, the field is not empty, the field is a number, the field is a character, the field length is greater than a certain length, and the field length is less than a certain length. Fields are then randomly combined based on these characteristics. Furthermore, the number of input parameters provided by the first interface can be used to combine fields, resulting in different combinations of fields with varying numbers of input parameters. The combined fields are then used as sample input data. Optionally, the required fields in the combined fields are retrieved, and one or more test data sets conforming to the field validation rules are randomly generated based on these required fields. In this embodiment, the automated construction of test cases is achieved by combining upstream fields.

[0065] In one embodiment, creating a first field group corresponding to the first interface and a second field group corresponding to the second interface based on the field information corresponding to the first interface and the second interface includes: dividing the fields of the first interface into a first field group according to the message structure and field name corresponding to the fields of the first interface as needed; and dividing the fields of the second interface into a second field group according to the message structure and field name of the fields of the second interface as needed.

[0066] The message structure includes the message hierarchy and message composition. Optionally, one or more first field groups are obtained based on the message hierarchy formed by the fields of the first interface and the field division of each field. One or more second field groups are obtained based on the message hierarchy formed by the fields of the second interface and the field division of each field.

[0067] For example, if the message structure consisting of the fields entered in the first interface is as follows:

[0068]

[0069] Based on the above fields, two first field groups are constructed, one of which is:

[0070]

[0071] Another first field group is:

[0072]

[0073]

[0074] The message structure received by the second interface is as follows:

[0075] {

[0076] "ad":"Zhejiang",

[0077] "moeny":12.23,

[0078] "t_d":"test"

[0079] }

[0080] The messages received in the second structure are treated as the second field group. The two first field groups in the first interface are jointly mapped to the second field group. It is understood that the division rules between the first and second field groups can be adjusted according to business requirements; for example, the fields in the first interface can be directly treated as the first field group, and the first field group can be mapped to the third field group.

[0081] In this embodiment, field grouping is implemented based on message structure and field name to meet the data flow requirements in different scenarios.

[0082] In one embodiment, after mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship, the method further includes: adjusting the number of users using the first interface and the second interface to connect to the first system and the second system according to the field mapping results between the first field group and the second field group within a preset time period.

[0083] The field mapping results include, but are not limited to, the call status of the first and second interfaces, data flow, and data request data. Optionally, the configured first and second interfaces are published to the production environment, and the field mapping results within this period are obtained based on a preset time period. If the field mapping results meet business expectations, the number of users using the first and second interfaces to connect to the first and second systems is increased; otherwise, the number of users using the first and second interfaces to connect to the first and second systems is maintained or decreased.

[0084] In this embodiment, by adjusting the number of users, it is beneficial to reduce the connection risk between the first system and the second system before fully using the first interface and the second interface to connect to the first system and the second system.

[0085] In one embodiment, a visual rules engine is provided to enable cross-system integration. By deploying the visual rules engine service in a specified environment, and ensuring stable and uninterrupted network connections between this service and existing services as well as the services being integrated, a sound network environment is provided to facilitate smooth subsequent integration work. Figure 3A schematic diagram of a method for integrating a rule engine execution system is provided, such as... Figure 3 As shown, it includes:

[0086] Step S301: Agree on interface information. This agreement includes obtaining system interface agreements from the rules engine. Optionally, based on the actual business needs of the first and second systems, and the characteristics of the first and second systems, interface agreements, message definitions, field validation rules, and request / response formats are established for the first and second interfaces to cover various normal and abnormal situations during system interface integration. Agreeing on interface information establishes the framework for the interface work, clarifying the interaction specifications and standards between the first and second systems.

[0087] Step S302: Create upstream and downstream groups, and enter fields, field types, and field validation rules. Optionally, based on system integration agreements, create corresponding upstream and downstream groups in the message mapping component of the rule engine. Enter the required fields, field types, and field validation rules on the upstream interface according to business requirements. Optionally, enter the field validation rules using validation regular expressions. Enter the required fields, field types, and field validation rules on the downstream interface. Wherein, if the first interface corresponds to the upstream, the upstream group is the first field group; if the second interface corresponds to the downstream, the downstream group is the second field group.

[0088] By creating upstream and downstream groups, the flow of interface data between systems can be clearly reflected; the number of interface interactions between the same systems can be indirectly reflected; the logical relationship between pushed and received data can be determined; and the effect of facilitating daily operation and maintenance and modification, and reducing the error rate of system integration can be achieved.

[0089] Step S303: Establish upstream and downstream correspondence. By establishing a mapping relationship between upstream and downstream groups, the fields belonging to each group are automatically mapped and matched. After user confirmation, the upstream and downstream data transfer is completed. For example, as follows... Figure 3 As shown, after creating upstream and downstream field groups, the fields in the upstream groups are cleaned and mapped, and then forwarded. During the forwarding process, mappings are automatically created based on field names and hierarchical upstream groups, or the corresponding downstream groups are selected according to pre-set conditions such as "$variable[data]->variable", mapping the fields in the upstream groups to the corresponding downstream groups.

[0090] Optionally, the rules engine also includes script components, judgment and control components, and data filtering and cleaning components. These components can perform intermediate transformations on upstream data. Data cleaning is used to intercept data that does not conform to system integration agreements. The script component is used to fulfill system integration requirements that cannot be achieved with the current configuration using a small number of script language fragments, or to implement business integration requirements in scenarios with cumbersome configurations. The judgment and control component determines whether intermediate transformations of upstream fields by the script component and the data filtering and cleaning component are necessary.

[0091] If the control component determines that the complexity of upstream and downstream data is mismatched based on their respective hierarchical complexity levels, and therefore requires transformation of the upstream data, it will determine that the intermediate data transformation be performed by a script component. For example, if the upstream data structure is JSON, the specific details are as follows:

[0092]

[0093] The downstream data structure is as follows:

[0094] {

[0095] "pdCode":"12",

[0096] "pdTime":"2024-12-12:12:12:12",

[0097] "t_d":"test"

[0098] }

[0099] Configure the following template using the script component to perform intermediate transformation of upstream data:

[0100] {

[0101] "pdCode":$test.$adf[0].$pdCode,

[0102] "pdTime":$test.$adf[0].$pdCode,

[0103] "t_d":$td.$t_d

[0104] }

[0105] Alternatively, the values ​​of the script components `adf` and `td` can be mapped, with `adf` value A and `td` value B, to the code provided by the following script component:

[0106] {

[0107] "pdCode":$A.$pdCode,

[0108] "pdTime":$A.$pdCode,

[0109] "t_d":$B.$t_d

[0110] }

[0111] By using intermediate conversion methods, the configuration difficulty in complex scenarios can be simplified, especially when different markup languages ​​are used upstream and downstream. For example, if the upstream uses XML markup language and the downstream only accepts JSON markup language, this intermediate conversion can significantly reduce the configuration difficulty, facilitate real-time modification according to business requirements, reduce redundant code, and facilitate operation and maintenance.

[0112] Step S304: Configure automated test case verification. Optionally, obtain the upstream creation fields and field verification rules, and combine the fields according to their required and non-required features. Randomly generate data that satisfies the field verification rules based on the combined required fields. Obtain a test case set based on this data and the combined fields, automatically execute the test cases, and provide statistical feedback on the execution results. Optionally, when combining fields, multiple combinations can be obtained based on the arrangement of interface input parameters, including: combining input parameter sample data based on the number of input parameters and the following field characteristics: empty, not empty, number, character, greater than a specified length, less than a specified length. Simulate requests automatically based on the input parameter sample data, record the results, and generate corresponding statistical reports. The configuration will only officially take effect after the automated test case verification is successful based on the recorded results.

[0113] Step S305: Configure and implement traffic canary deployment. Publish the above system integration configuration to the production environment according to the confirmed window in the system integration agreement. Adjust the open ratio of the system integration configuration in the production environment based on the daily system integration results. Furthermore, operations and maintenance personnel can use a visual interface to obtain detailed status of interface calls in both systems in real time, including real-time dynamics of data flow, raw data of data requests, intermediate data during the conversion process, and other key information. In subsequent operation, if there are changes in requirements, simply dynamically adjust the system configuration to easily meet them, truly achieving time-saving, labor-saving, efficient, and flexible cross-system integration.

[0114] In this embodiment, by using automatic message packet mapping and automated case generation and detection methods before configuration takes effect, the probability of errors is reduced, ensuring that the effective configuration is a production-ready configuration. This significantly reduces the need for repeated debugging and confirmation, and minimizes human error. By introducing a visual rule engine, online configuration can be achieved, and the location and status of data flow nodes can be monitored in real time. This significantly reduces the time cost required for integration and can also greatly reduce or even achieve zero-code development, making the entire system easier to maintain. This solves the problems of long system integration cycles, high error rates, and resource waste caused by reliance on code writing.

[0115] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0116] Based on the same inventive concept, this application also provides a system docking apparatus for implementing the system docking method described above. The solution provided by this apparatus is similar to the solution described in the above method; therefore, the specific limitations in one or more system docking apparatus embodiments provided below can be found in the limitations of the system docking method described above, and will not be repeated here.

[0117] In one embodiment, such as Figure 4 As shown, a system docking device is provided, comprising:

[0118] The interface acquisition module acquires the first interface for interfacing with the second system in the first system, and acquires the second interface for interfacing with the first system in the second system.

[0119] The grouping module creates a first field group corresponding to the first interface and a second field group corresponding to the second interface based on the field information corresponding to the first interface and the second interface.

[0120] The connection module determines the mapping relationship between the first field group and the second field group according to the system interface agreement;

[0121] The mapping module maps the fields in the first field group to their corresponding second field groups according to the mapping relationship.

[0122] In some embodiments, the system interface device further includes an intermediate conversion module. This intermediate conversion module is used to perform the following method before mapping the fields in the first field group to their corresponding second field groups based on the mapping relationship: determining whether the message structure of the first field group conforms to a preset message structure; if the message structure does not conform to the preset message structure, constructing a message template based on the preset message structure; and filling the message template with the values ​​from the first field group to obtain a first field group that conforms to the preset structure. Optionally, determining whether the message structure of the first field group conforms to the preset message structure corresponding to the second interface includes: obtaining the preset message structure based on the markup language and / or hierarchical features corresponding to the second interface; and determining whether the message structure in the first field group conforms to the preset message structure.

[0123] In some embodiments, the system docking device further includes a testing module, which is used to construct test cases according to the field verification rules of the first field group and the first interface before mapping the fields in the first field group to the corresponding second field group based on the mapping relationship; and if the first system and the second system are successfully docked based on the test cases, the fields in the first field group are grouped and mapped to the corresponding second field group based on the mapping relationship.

[0124] In some embodiments, test cases are constructed based on the fields and field validation rules entered in the first interface, including: combining the fields in the first field group; generating test data that conforms to the field validation rules based on the combined fields; and constructing test cases by combining the combined fields and the test data.

[0125] In some embodiments, based on the field information corresponding to the first interface and the second interface, a first field group corresponding to the first interface and a second field group corresponding to the second interface are created, including: dividing the fields of the first interface into a first field group according to the message structure and field name corresponding to the fields of the first interface as needed; and dividing the fields of the second interface into a second field group according to the message structure and field name of the fields of the second interface as needed.

[0126] In some embodiments, the system docking device further includes a publishing module, which is used to adjust the number of users using the first interface and the second interface to dock with the first system and the second system according to the field mapping results between the first field group and the second field group within a preset time period after mapping the fields in the first field group to the corresponding second field group based on the mapping relationship.

[0127] Each module in the aforementioned system docking device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0128] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 5 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface and display unit are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a system docking method. The display unit is used to form a visually visible image and can be a display screen or a projection device. The display screen can be a liquid crystal display (LCD) or an e-ink display.

[0129] Those skilled in the art will understand that Figure 5 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 computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0130] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0131] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0132] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0133] 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. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0134] 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 are 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.

[0135] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. 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 application should be determined by the appended claims.

Claims

1. A system docking method, characterized in that, The method includes: In the first system, obtain the first interface for interfacing with the second system; in the second system, obtain the second interface for interfacing with the first system. Based on the field information corresponding to the first interface and the second interface, create a first field group corresponding to the first interface and a second field group corresponding to the second interface; According to the system interface agreement, the mapping relationship between the first field group and the second field group is determined; Based on the mapping relationship, the fields in the first field group are mapped to the corresponding second field groups; Based on the field mapping results between the first field group and the second field group within a preset time period, adjust the number of users using the first interface and the second interface to connect to the first system and the second system.

2. The method according to claim 1, characterized in that, Before mapping the fields in the first field group to their corresponding second field groups according to the mapping relationship, the method includes: Determine whether the message structure of the first field group conforms to the preset message structure; If the message structure does not conform to the preset message structure, then a message template is constructed according to the preset message structure; The values ​​in the first field group are filled into the message template to obtain the first field group that conforms to the preset message structure.

3. The method according to claim 2, characterized in that, The step of determining whether the message structure of the first field group conforms to the preset message structure corresponding to the second interface includes: The preset message structure is obtained based on the markup language and / or hierarchical features corresponding to the second interface; Determine whether the message structure in the first field group conforms to the preset message structure.

4. The method according to claim 1, characterized in that, Before mapping the fields in the first field group to their corresponding second field groups according to the mapping relationship, the method further includes: Test cases are constructed based on the field validation rules of the first field group and the first interface; If the test cases confirm successful integration between the first system and the second system, the fields in the first field group are mapped to the corresponding second field group based on the mapping relationship.

5. The method according to claim 4, characterized in that, The step of constructing test cases based on the fields and field validation rules entered in the first interface includes: Combine the fields in the first field group; Based on the combined fields, generate test data that conforms to the field validation rules; The test cases are constructed by combining the combined fields and the test data.

6. The method according to claim 1, characterized in that, The step of creating a first field group corresponding to the first interface and a second field group corresponding to the second interface based on the field information corresponding to the first interface and the second interface includes: The fields of the first interface are divided according to the message structure and field name corresponding to the fields of the first interface as required, to obtain the first field group; As needed, the message structure and field names of the fields of the second interface are entered, and the fields of the second interface are divided to obtain the second field group.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images