System interface protocol updating method and device, storage medium and electronic equipment

Abstract

The invention discloses a system interface protocol updating method and device, a storage medium and electronic equipment. The method comprises the following steps: acquiring a configured interface protocol of at least one target interface in a to-be-configured system and a to-be-configured interface protocol; determining difference information between the to-be-configured interface protocol and the configured interface protocol; based on the configuration attribute of the target interface, converting the difference information to obtain configuration data of the target interface; and updating the interface protocol of the target interface from the configured interface protocol to the to-be-configured interface protocol by using the configuration data. Through the method and the device, the problem of low updating efficiency of the interface protocol is solved.

Description

Technical Field

[0001] The present application relates to a field, and in particular to a method, device, storage medium and electronic device for updating an interface protocol of a system. Background Art

[0002] Currently, when the system interface is upgraded or a new seller is introduced, a new set of interface protocols needs to be added. This process covers all files involved in the import and export of the entire system. Therefore, the above process requires a comparison and analysis of the new and old interface protocols.

[0003] In the related art, manual comparative analysis can be performed to determine the differences between the new and old interface protocols, and then the system can be rectified and upgraded based on the differences. However, this method not only involves a large amount of inefficient repetitive work, but also results in inaccurate interface upgrades, and even system operation errors. Therefore, this method has the technical problem of low interface protocol update efficiency.

[0004] Currently, no effective solution has been proposed to the problem of low updating efficiency of interface protocols. Summary of the invention

[0005] The main purpose of the present application is to provide a method, device, storage medium and electronic device for updating a system interface protocol, so as to solve the problem of low updating efficiency of the interface protocol.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for updating the interface protocol of a system is provided. The method may include: obtaining the configured interface protocol of at least one target interface in the system to be configured, and the interface protocol to be configured; determining the difference information between the interface protocol to be configured and the configured interface protocol; based on the configuration attributes of the target interface, converting the difference information to obtain the configuration data of the target interface; using the configuration data, updating the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured.

[0007] Optionally, based on the configuration attributes of the target interface, the difference information is converted to obtain the configuration data, including: converting the difference information to obtain a difference document; based on the configuration attributes, converting the difference document to obtain the configuration data.

[0008] Optionally, based on the configuration attribute, the difference document is converted to obtain the configuration data, including: determining a target configuration attribute matching the difference information among multiple configuration attributes; based on the target configuration attribute, the difference document is converted to obtain the configuration data.

[0009] Optionally, based on the target configuration attribute, the difference document is converted to obtain the configuration data, including: mapping the difference document according to the target configuration attribute to obtain a mapping result; and generating the configuration data according to the mapping result.

[0010] Optionally, determining the difference information between the interface protocol to be configured and the configured interface protocol includes: cutting the interface protocol to be configured to obtain at least one first sub-data, and cutting the configured interface protocol to obtain at least one second sub-data; determining the difference information between the first sub-data and the second sub-data according to preset characteristics.

[0011] Optionally, using the configuration data, updating the interface protocol of the target interface from a configured interface protocol to an interface protocol to be configured, including: inputting the configuration data into a database; and updating the configured interface protocol in the database to the interface protocol to be configured according to the configuration data.

[0012] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a system interface protocol updating device is provided. The device may include: an acquisition unit, used to acquire the configured interface protocol of the target interface in the system to be configured, and the interface protocol to be configured; a determination unit, used to determine the difference information between the interface protocol to be configured and the configured interface protocol; a conversion unit, used to convert the difference information based on the configuration attributes of the target interface to obtain configuration data; and an update unit, used to update the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured using the configuration data.

[0013] Optionally, the conversion unit may further include: a first conversion module, used to convert the difference information to obtain a difference document; and a second conversion module, used to convert the difference document based on the configuration attribute to obtain the configuration data.

[0014] Optionally, the second conversion module may further include: a determination submodule, used to determine a target configuration attribute matching the difference information among multiple configuration attributes; and a conversion submodule, used to convert the difference document based on the target configuration attribute to obtain configuration data.

[0015] Optionally, the conversion submodule may also be used to map the difference documents according to the target configuration attributes to obtain a mapping result; and generate configuration data according to the mapping result.

[0016] Optionally, the determination unit may also include: a cutting module, used to cut the interface protocol to be configured to obtain at least one first sub-data, and to cut the configured interface protocol to obtain at least one second sub-data; a determination module, used to determine the difference information between the first sub-data and the second sub-data according to preset characteristics.

[0017] Optionally, the updating unit may further include: an input module for inputting configuration data into a database; and an updating module for updating the configured interface protocol in the database to the interface protocol to be configured according to the configuration data.

[0018] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer-readable storage medium is further provided, which may include a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located can be controlled to execute the above-mentioned method.

[0019] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an electronic device is further provided, which may include: a memory storing an executable program; and a processor for running the program, wherein the above-mentioned method is executed when the program is running.

[0020] In order to achieve the above objective, according to another aspect of the present application, a computer program product is provided. The computer program product may include computer instructions. When the computer instructions are executed by a processor, the steps of the above method are implemented.

[0021] In an embodiment of the present application, the configured interface protocol of at least one target interface in the system to be configured and the interface protocol to be configured are obtained; the difference information between the interface protocol to be configured and the configured interface protocol is determined; based on the configuration attributes of the target interface, the difference information is converted to obtain the configuration data of the target interface; using the configuration data, the interface protocol of the target interface is updated from the configured interface protocol to the interface protocol to be configured. That is, in this embodiment, the configured interface protocol and the interface protocol to be configured are obtained, the difference information between the two is determined, and the configuration data of the target interface is used to convert the difference information to obtain the configuration data, and the configured interface protocol can be updated according to the configuration data to obtain the interface protocol to be configured, thereby achieving the technical effect of improving the updating efficiency of the interface protocol and solving the technical problem of low updating efficiency of the interface protocol. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing a system interface protocol update method is shown;

[0024] Figure 2 is a flowchart of a method for updating an interface protocol of a system according to an embodiment of the present application;

[0025] Figure 3 is a schematic diagram of intelligent comparative analysis of new and old protocols according to an embodiment of the present application;

[0026] Figure 4 is a schematic diagram of the interaction between the system and the vendor file according to an embodiment of the present application;

[0027] Figure 5 is a schematic diagram of an interface field maintenance table according to an embodiment of the present application;

[0028] Figure 6 is a schematic diagram of configuring TA system interface protocol interaction according to an embodiment of the present application;

[0029] Figure 7 is a flow chart of fund interface protocol conversion according to an embodiment of the present application;

[0030] Figure 8 is a schematic diagram of an interface protocol updating device of a system according to an embodiment of the present application;

[0031] Fig. 9 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following explanations:

[0035] Intelligent comparative analysis can refer to the use of computer systems and algorithms to compare and analyze different data or information to extract useful information and insights. This analysis can cover different fields, including text, images, sounds, etc.

[0036] Interface protocol conversion can refer to the conversion of communication interfaces and protocols between different systems or devices so that they can communicate with each other and exchange data. This conversion can involve different communication protocols so that different systems can communicate effectively.

[0037] It should be noted that the collected information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with relevant laws, regulations and standards, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0038] Example 1

[0039] According to an embodiment of the present application, a method embodiment of updating the interface protocol of a system is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings 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 can be executed in an order different from that shown here.

[0040] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or mobile device) for implementing the system interface protocol update method is shown. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0041] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0042] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the interface protocol update method of the system in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the interface protocol update method of the above-mentioned system is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0043] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0044] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0045] Under the above operating environment, this application provides Figure 2 The interface protocol updating method of the system shown. Figure 2 is a flowchart of a method for updating an interface protocol of a system according to an embodiment of the present application. Figure 2 As shown, the method may include the following steps:

[0046] Step S201, obtaining a configured interface protocol of at least one target interface in a system to be configured and an interface protocol to be configured.

[0047] In this embodiment, the system to be configured may be a system that needs to upgrade or modify the interface protocol, for example, it may be a fund registration system (also referred to as a TA system), or a system that needs to upgrade or change the data interaction protocol with the seller or custodian bank. The target interface may be an interface or interface type that specifically needs to be updated in the system to be configured, for example, in the fund TA system, the target interface may be an account application interface, a transaction application interface, etc. The configured interface protocol may refer to the interface protocol currently being used in the system to be configured, which is the benchmark for system data exchange, for example, it may be the fund interface protocol version 1.0, which may include detailed field configurations of files such as account application (01 file) and account confirmation (02 file). The interface protocol to be configured may be a new protocol that is about to be introduced or upgraded to the system to be configured, which is different from the configured protocol, for example, it may be the fund interface protocol version 2.0. It should be noted that this is only an example, and the type of the system to be configured, the configured interface protocol, and the type of the interface protocol to be configured are not specifically limited.

[0048] Optionally, the existing interface protocol files (i.e., configured interface protocols) and new interface protocol files to be configured (i.e., protocol interfaces to be configured) in the current TA system are collected. For example, the configured interface protocols can be obtained by reading the existing configurations in the database tables (e.g., TFIELDDICT, TTAFIELDDICT, and TFILEFIELD, etc.), and the new version of the protocol files can be obtained from the vendor or custodian bank to obtain the interface protocols to be configured.

[0049] For example, the TA system needs to be upgraded to adapt to the new interface protocol requirements of the seller. The target interface that needs to be upgraded according to the seller's new protocol, as well as the configured interface protocol and configured interface protocol of the target interface can be determined. For example, the configured interface protocol can include detailed field configurations of files such as account application (01 file) and account confirmation (02 file). The interface protocol to be configured can include newly added fields or modify the length of existing fields, such as increasing the length of the customer ID field from 10 bits to 15 bits.

[0050] Step S202: Determine the difference information between the interface protocol to be configured and the configured interface protocol.

[0051] In this embodiment, the difference information may be the difference between the configured interface protocol and the interface protocol to be configured, which is determined by comparing and analyzing the two protocols, and may be identified by artificial intelligence (AI), a neural network model, etc. It should be noted that this is only an example, and there is no specific limitation on the method of obtaining the difference information.

[0052] Optionally, after obtaining the configured interface protocol and the interface protocol to be configured, an AI algorithm can be used to perform intelligent comparative analysis on the new and old protocols, identify all differences in field names, field types, field lengths, etc., and reassemble them into difference information. Through the difference information, the differences between the interface protocol to be configured and the configured interface protocol can be identified and recorded.

[0053] For example, after intelligent comparative analysis, it was found that the redemption option was added to the transaction type field in the Fund Interface Protocol Version 2.0, and the customer identity (Identification, referred to as ID) field length was increased from 10 digits to 15 digits. The above contents can all be difference information.

[0054] Step S203: based on the configuration attributes of the target interface, convert the difference information to obtain the configuration data of the target interface.

[0055] In this embodiment, the above configuration attributes may be parameters describing how the interface is defined and used in the system, may include the relevant configuration table corresponding to the target interface, may include field name, field type, field length, whether it is required, etc. For example, in the TA system, the configuration attributes of the customer ID field may include field name, field type, field length of 15, whether it is required, etc. The above configuration data may be based on the configuration attributes of the system to be configured, converting the difference information into specific and executable update data, and may exist in the form of structured query language (SQL) or configuration script. For example, for the update of the length of the customer ID field, the configuration data may be an SQL statement, such as: sql: UPDATE TTAFIELDDICT SET L_TAFIELDLEN=15WHERE C_TAFIELD='customer ID'. It should be noted that this is only an example, and there is no specific limitation on the type of configuration attributes, the content or type of configuration data.

[0056] Optionally, after the difference information is acquired, the difference information may be converted based on the configuration data of the target interface to obtain the configuration data of the target interface.

[0057] Step S204: using the configuration data, updating the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured.

[0058] In this embodiment, after obtaining the configuration data, the interface protocol of the target interface can be updated based on the configuration data and the configured interface protocol to obtain the interface protocol to be configured. For example, the configured interface protocol can be modified using the configuration data to obtain the interface protocol to be configured.

[0059] Optionally, after obtaining the configuration data, the configuration data may be a configuration update command, and thus the generated configuration update command may be executed. The above process may involve running an SQL script in the database of the TA system to update the configurations such as field length and field type. After the update, the TA system will be able to recognize and process the data in the new version of the interface protocol, ensuring smooth data exchange with the seller or custodian bank.

[0060] In this embodiment, the interface protocol of the target interface can be updated from the configured interface protocol to the interface protocol to be configured through intelligent comparison and automated configuration update of the AI ​​algorithm, thereby significantly improving the efficiency and accuracy of the interface protocol conversion, reducing manual intervention, and reducing operational risks.

[0061] In the above steps S201 to S204, the configured interface protocol of at least one target interface in the system to be configured and the interface protocol to be configured are obtained; the difference information between the interface protocol to be configured and the configured interface protocol is determined; based on the configuration attributes of the target interface, the difference information is converted to obtain the configuration data of the target interface; using the configuration data, the interface protocol of the target interface is updated from the configured interface protocol to the interface protocol to be configured. That is, in this embodiment, the configured interface protocol and the interface protocol to be configured are obtained, the difference information between the two is determined, and the difference information is converted using the configuration data of the target interface to obtain the configuration data. The configured interface protocol can be updated according to the configuration data to obtain the interface protocol to be configured, thereby achieving the technical effect of improving the updating efficiency of the interface protocol and solving the technical problem of low updating efficiency of the interface protocol.

[0062] The embodiments of the present application are described in detail below in combination with the above steps.

[0063] As an optional implementation, step S203, based on the configuration attributes of the target interface, converting the difference information to obtain configuration data, includes: converting the difference information to obtain a difference document; based on the configuration attributes, converting the difference document to obtain configuration data.

[0064] In this embodiment, the difference information may be converted to obtain a difference document, and further, the difference document may be converted based on the configuration data to obtain the configuration data. The difference document may have different characteristic items, and may be a document that only includes the difference information.

[0065] Optionally, the difference information is converted into a difference document by aggregation, conversion, etc., and the difference document can be converted according to the characteristics of the system interface configuration to be configured (i.e., configuration attributes) to convert the information in the difference document into configuration data that can be understood by the database. For example, if the difference document indicates that the length of the customer ID field in the account application file needs to be increased from 10 to 15, then a corresponding SQL statement needs to be generated to update the L_TAFIELDLEN field in the TTAFIELDDICT table. Through the above steps, the abstract difference information can be converted into a specific and executable configuration update command.

[0066] Optionally, after obtaining the difference information, the difference information can be reassembled in a module, sub-module, and matching feature index manner to complete the assembly of feature items with differences, thereby obtaining two protocol version difference documents containing only the differences for output.

[0067] Optionally, the interface protocol to be configured and the configured interface protocol can be read through the intelligent comparison and analysis module to identify the difference information therein. These difference information may include the addition of fields, deletion of fields, changes in field types or lengths, etc. The identified difference information can be organized and converted into a format that is easier to understand and process, namely a difference document. The difference document can be a structured report that lists all the differences in detail for processing in subsequent steps. Furthermore, after obtaining the difference document, the information in the difference document can be converted into specific configuration data based on the configuration attributes of the target interface (such as the transaction confirmation interface in the TA system). The above configuration attributes may include the corresponding tables and fields of the fields in the database, the database type and length of the fields, etc., as well as the position and order of the fields in the file. Configuration data is an instruction that can be directly executed by the system, usually expressed as an SQL update statement or a configuration script, which is used to automatically adjust the system configuration to adapt to the new interface protocol.

[0068] Optionally, in addition to generating SQL statements, this process may also involve updating other configuration tables of the TA system, such as TFIELDDICT and TFILEFIELD, to ensure that the configuration of external fields and file fields is consistent with the internal field configuration. In addition, the TA system may also need to update its import and export configuration to reflect changes in field order and file naming rules. All of these configuration updates will be automated by analyzing difference documents and applying corresponding conversion rules. This not only saves manpower, but also ensures the accuracy and consistency of configuration, reducing problems caused by human errors.

[0069] In this step, the AI ​​algorithm automatically compares the old and new protocols and generates a difference document, which is then automatically converted into configuration data based on the configuration attributes, greatly reducing the workload of manual comparison and configuration updates, and improving the efficiency of the entire fund interface protocol conversion process. The above automation process can reduce errors caused by human factors and ensure that each difference point is accurately identified and processed. Conversion based on the configuration attributes of the target interface can ensure the accuracy and consistency of the configuration data, thereby improving the stability and reliability of the system after the upgrade. At the same time, the application of automation tools reduces dependence on professionals, reduces the labor costs caused by manual comparison and configuration updates, and avoids the potential costs of system downtime or data loss caused by manual operations.

[0070] In this embodiment, intelligent comparative analysis and automated configuration conversion reduce the operational risks during the interface protocol update process, reduce the possibility of data transmission failure or system abnormality due to configuration errors, and ensure smooth and error-free data exchange between the system and the external interface. When the seller or custodian bank requires the TA system to change the interface protocol, this automated process can quickly respond and adapt to the new protocol requirements, improving the system's flexibility and adaptability to external changes.

[0071] As an optional implementation, based on the configuration attribute, the difference document is converted to obtain configuration data, including: determining a target configuration attribute matching the difference information among multiple configuration attributes; based on the target configuration attribute, the difference document is converted to obtain configuration data.

[0072] In this embodiment, among multiple configuration attributes, a target configuration attribute matching the difference information can be determined, and based on the target configuration data, the difference document is converted to obtain configuration data. The target configuration data may refer to configuration information related to fields that need to be modified or added according to the new protocol, and may be a key component used to define the interface file structure, field mapping, and data processing rules within the system, such as a configuration file interface field. It should be noted that this is only an example, and there is no specific restriction on the type of target configuration data.

[0073] Optionally, in the system to be configured, there are multiple configuration attributes, which may include field name, field type, field length, field description, whether the field is required, etc. When the intelligent comparison and analysis module identifies the difference information between the new and old protocols, it can filter out the attributes directly related to the difference information from these configuration attributes, that is, the target configuration attributes. For example, if the difference information indicates that the transaction ID field type in the transaction confirmation file needs to be changed, then the target configuration attributes include the field type and field length of the transaction ID. Once the target configuration attributes are determined, the information in the difference document can be converted based on these attributes to generate specific configuration data. This usually involves writing SQL statements or scripts to update or insert the target configuration attributes. In this way, it can be ensured that the update to the system configuration only involves the parts that really need to be changed, avoiding unnecessary modifications and improving the accuracy and efficiency of the configuration update.

[0074] For example, suppose that the intelligent comparison analysis finds that the transaction ID field type of the transaction confirmation file in the Fund Interface Protocol Version 2.0 has changed from VARCHAR to NUMERIC, and the field length has changed from 10 to 15. In the database configuration of the TA system, the transaction ID field may have two configuration attributes in the TTAFIELDDICT table: C_DATATYPE and L_TAFIELDLEN, corresponding to the field type and field length respectively. Therefore, C_DATATYPE and L_TAFIELDLEN can be regarded as target configuration attributes that match the difference information. Further, based on the target configuration attributes, the difference document can be converted, and the generated configuration data may be the following SQL statement: sql--update field type UPDATE TTAFIELDDICT SET C_DATATYPE='NUMERIC'WHERE C_TAFIELD='Transaction ID';--update field length UPDATE TTAFIELDDICT SET L_TAFIELDLEN=15WHERE C_TAFIELD='Transaction ID'.

[0075] Optionally, in actual operation, it may also involve updating the position and order of fields in the file, as well as the associated external field dictionary table TFIELDDICT and interface file field table TFILEFIELD. All these updates should be made based on the target configuration properties identified in the difference document to ensure that each change accurately reflects the differences in the protocol.

[0076] Optionally, for the interface protocol file configuration of the system to be configured, the import and export of the interface protocol file of the system to be configured can read the corresponding relevant configuration table to complete the import and export of the file to the database table. The interface protocol file configuration of the system to be configured can be completed by configuring the file interface field format and configuring the TA system interface protocol interaction process.

[0077] Optionally, the file interface fields of the system to be configured can be configured in advance. The system to be configured can maintain three tables for the file interface fields, such as an external field dictionary table (TFIELDDICT), a system internal field dictionary (TTAFIELDDICT) and an interface file field table (TFILEFIELD). Among them, the above-mentioned external field dictionary table can correspond to each field name of the import and export file, and the interface field number (L_IDNO) is uniquely identified, and is used to correspond to the internal field number (L_TAIDNO) of the system internal field dictionary table. The above-mentioned system internal field dictionary table corresponds to the table structure field corresponding to the export file in the database. The above-mentioned interface file field table can be used to associate the internal and external field table numbers, and determine the order of the import and export file fields through the field sequence number (L_ORDER).

[0078] Optionally, configuring the TA system interface protocol interaction process may include: defining the import and export files in all daily operation processes through the interface process configuration table (TINTERFACESET), the C_IOFLOW field indicates the import and export file type, the C_IOFLAG field indicates the processing flag, and the C_PATHDIR indicates the import and export folder path. After selecting the file type to be exported, the interface process configuration table C_IOFLOW field is associated with the interface process classification table (TINTERFACECLASS) to obtain the export file interface process code (C_FLOWCODE) and interface version (C_IVERSIONSQL) list; C_FLOWCODE is the minimum batch unit for file export (optional support), and its batch name can be found by associating the query field code name escape table (TQUERYFIELDVALUE). The interface process code list and interface version list obtained by traversing the above steps are associated with the SQL statement configuration table (TSQL) to first obtain the interface version, where: accounting export returns the interface version list of all custodian banks; salesperson market, confirm data export, and return the interface version list of all salespeople. Furthermore, according to the interface version list and the interface flow code, the interface version information table (TINTERFACEVERINFO) and the interface file definition table (TINTERFACEFILEDEFINE) can be associated to obtain the file type list under the specific interface flow code (C_FLOWCODE). The file type list obtained by traversing the above steps is combined with the specific interface flow code to generate an export database table of a specific file type.

[0079] In this step, the above steps enable the difference document to be converted accurately and specifically during the automation interface protocol conversion process, thereby improving the efficiency of difference document conversion and ensuring that the obtained configuration data can accurately reflect the protocol differences.

[0080] As an optional implementation, based on the target configuration attribute, the difference document is converted to obtain configuration data, including: mapping the difference document according to the target configuration attribute to obtain a mapping result; and generating configuration data according to the mapping result.

[0081] In this embodiment, the difference document may be mapped according to the target configuration data to obtain a mapping result, and further, the configuration data may be generated according to the mapping result.

[0082] For example, the above target configuration attributes can be used to determine the corresponding configuration table. Therefore, after obtaining the difference document, the difference document can be parsed in detail to identify which parts of the file naming format, data file content format and business data exchange items are different from the old version of the protocol. Each different feature is mapped to the relevant configuration table in the system to be configured. For example, the difference in field name corresponds to the update of the `TFIELDDICT` table, and the change in field length requires the modification of the field length configuration in the `TTAFIELDDICT` table. It can be determined which configuration table in the system to be configured is associated with each difference listed in the difference document. For example, if the document indicates that the description or required attribute of a field has changed, it is necessary to locate the relevant row in the `TTAFIELDDICT` table for updating. The mapping result can be obtained through the above steps, and the mapping result can be a corresponding table. Further, based on the mapping result, configuration data can be generated, that is, a specific SQL update statement can be generated for each configuration table that needs to be modified. For example, the `UPDATE` command can be used to modify the field length, field type, field description, etc. For newly added fields or protocol features, you may need to use the `INSERT` command to add these new information to the corresponding configuration table. If some old fields or features are no longer needed, you can use the `DELETE` command to remove them from the configuration table.

[0083] Optionally, according to the file types and processes involved in the difference document, the information in the `TINTERFACESET` table, such as the path, file type, and processing flag, can be updated to ensure the correctness of the process code and version information in the `TINTERFACECLASS` table so that the system to be configured can adapt to the data exchange process under the new protocol.

[0084] Optionally, after obtaining the configuration data, all SQL update statements can be integrated into a configuration script to ensure that the logical order of the script is correct and to avoid update conflicts. Before officially running the system, the configuration script can be tested, using simulated data or a test environment to verify whether the update works as expected and to avoid incorrect operations in the production environment.

[0085] Optionally, all executed update statements and configuration scripts can also be logged to maintain version control and audit trails. Save diff documents and change logs for future reference and possible audit needs.

[0086] In this step, through the above steps, the system to be configured can automatically generate update statements or configuration scripts based on the difference documents, thereby automatically completing the upgrade of the interface protocol. This method not only improves efficiency and reduces manual configuration errors, but also ensures the traceability and security of the upgrade process.

[0087] As an optional implementation, step S202, determining the difference information between the interface protocol to be configured and the configured interface protocol, includes: cutting the interface protocol to be configured to obtain at least one first sub-data, and cutting the configured interface protocol to obtain at least one second sub-data; according to preset characteristics, determining the difference information between the first sub-data and the second sub-data.

[0088] In this embodiment, the interface protocol to be configured can also be cut to obtain at least one first sub-data, and the configured interface protocol can be cut to obtain at least one second sub-data, and the first sub-data and the second sub-data can be compared according to the preset characteristics to determine the difference information. Among them, the above-mentioned first sub-data and the second sub-data can be data corresponding to the information exchange format module, and data corresponding to the business exchange data item module, respectively. The above-mentioned preset characteristics can be information such as file naming format, data file content format, account application, account confirmation, etc. It should be noted that this is only an example, and there is no specific limitation on the type of the first sub-data, the type of the second sub-data, and the type of the preset characteristics.

[0089] Optionally, after obtaining the interface protocol to be configured and the configured interface protocol, the above interface protocol can be preprocessed, and the interface protocol to be configured and the configured interface protocol can be divided into two modules: information exchange format and business exchange data item according to the characteristics of the fund interface protocol.

[0090] Optionally, the input needs to be compared with the output difference column features. Taking the fund business data exchange protocol as an example, Table 1 is the feature table of the fund business data exchange protocol. As shown in Table 1, the information exchange format may include two sub-modules: data file naming format and data file content format; the business exchange data items may include fund business-related file data formats, for example, account application (01 file), account confirmation (02 file), transaction application (03 file), transaction confirmation (04 file), etc. The protocol is divided into sub-modules and re-arranged and assembled. According to the above preset features, the first sub-data and the second sub-data are compared to obtain difference information.

[0091] Table 1 Characteristics of fund business data exchange protocol

[0092]

[0093]

[0094] In this step, the interface protocol to be configured and the configured interface protocol are segmented, and the first sub-data and the second sub-data after segmentation are compared to determine difference information. Through the above method, the efficiency of determining the difference information is improved.

[0095] As an optional implementation, step S204, using configuration data, updates the interface protocol of the target interface from a configured interface protocol to an interface protocol to be configured, including: inputting the configuration data into a database; and updating the configured interface protocol in the database to an interface protocol to be configured according to the configuration data.

[0096] In this embodiment, after obtaining the configuration data, the configuration data can be input into the database, and according to the configuration data, the configured interface protocol in the database can be updated to the interface protocol to be configured. That is, the configuration data can be written into the database to realize the interface protocol conversion.

[0097] In an embodiment of the present application, a configured interface protocol and an interface protocol to be configured are obtained, difference information between the two is determined, and the difference information is converted using the configuration data of the target interface to obtain the configuration data. The configured interface protocol can be updated according to the configuration data to obtain the interface protocol to be configured, thereby achieving the technical effect of improving the updating efficiency of the interface protocol and solving the technical problem of low updating efficiency of the interface protocol.

[0098] Another optional specific implementation is described in detail below.

[0099] At present, each time the fund registration and filing system (hereinafter referred to as the TA system) interface is upgraded or a new seller is introduced, a new set of interface protocols needs to be added. This process covers all files involved in the import and export of the entire TA system. Therefore, the above process requires a comparative analysis of the new and old interface protocols, which can include analysis of the information exchange format, field name, field length, field type, dictionary items, etc. in the interface protocol.

[0100] In the related technology, manual comparative analysis can be performed to determine the differences between the new and old protocols, and then the system can be rectified and upgraded based on the differences. However, this method not only involves a large amount of inefficient and repetitive work, but also leads to inaccurate interface upgrades and even system operation errors.

[0101] Since the existing TA fund interface protocol upgrade relies on manpower to compare the new and old interface protocols, a large amount of manpower is required and may also cause errors in the interface upgrade. There is a technical problem of low update efficiency of the interface protocol. In order to solve the above problem, in this embodiment, a method for fund interface protocol conversion based on artificial intelligence is provided. The method generates a difference document based on the comparison of the new and old fund interface protocols based on the artificial intelligence algorithm; then, according to the generated difference document and system characteristics (which can be the configuration properties of the target interface), configuration data is generated, and configuration scripts are imported and exported to realize one-click financial management interface protocol conversion, thereby achieving the technical effect of improving the update efficiency of the interface protocol and solving the technical problem of low update efficiency of the interface protocol.

[0102] Next, the database switching verification method of the accounting system in this application is further introduced.

[0103] Figure 3 is a schematic diagram of intelligent comparative analysis of new and old protocols according to an embodiment of the present application, such as Figure 3 As shown, the fund interface protocol version 1.0 (configured interface protocol) and the fund interface protocol version 2.0 (to be configured interface protocol) are obtained. According to the characteristics of the fund interface protocol, the configured interface protocol and the interface protocol to be configured can be preprocessed to divide the configured interface protocol and the interface protocol to be configured into two modules: information exchange format and business exchange data item. Among them, the above-mentioned information exchange format includes two sub-modules: data file naming format and data file content format; the business exchange data item includes fund business-related file data format, such as account application (01 file), account confirmation (02 file), transaction application (03 file), transaction confirmation (04 file), etc. The protocol can be divided by sub-module and re-ordered and assembled. Further, based on the AI ​​algorithm, the two versions of the interface protocol can be processed and compared according to the above features to identify the differences between the two documents. According to the module and sub-module, the feature index can be matched, and the feature items with differences can be reassembled to form two protocol version difference documents containing only the differences for output.

[0104] In this embodiment, since the import and export of the system interface protocol file is to read the corresponding configuration table to complete the import and export of the file to the database table, the interface protocol file configuration may include: configuring the file interface field format and configuring the TA system interface protocol interaction process.

[0105] Figure 4 is a schematic diagram of the interaction between the system and the vendor file according to an embodiment of the present application, such as Figure 4 As shown, the core processing of the system may include: fund account management and fund transaction management. The system communicates with the seller through an interface protocol. The above interface protocol conversion may be performed for the dealer interface and the accounting interface. The interface protocol file may include information such as account application 01, account confirmation 02, account application 03, etc.

[0106] Optionally, the TA core processing content may include fund account management and fund transaction management, which requires file interaction with the seller. The specific interaction process is as follows: Figure 4 As shown; the interactive files need to comply with the vendor interface protocol. To ensure accurate and smooth interaction, the TA system interface needs to be configured according to the interface protocol. Then, based on the TA system interface protocol configuration features and combined with the difference documents, an executable upgrade interface protocol configuration statement is generated to achieve one-click fund TA interface protocol conversion.

[0107] In this embodiment, Figure 5 is a schematic diagram of an interface field maintenance table according to an embodiment of the present application, such as Figure 5 As shown, TA maintains three tables for file interface fields, which may include: external field dictionary table, TA internal field dictionary and interface file field table. Among them, the external field dictionary table corresponds to the various field names of the imported and exported files (for example, C_CLASS, C_IVERSION, C_FILETYPE), the interface field number is uniquely identified, and is used to correspond to the internal field number of the TA internal field dictionary table. The TA internal field dictionary table can correspond to the table structure field corresponding to the exported file in the database. The interface file field table can associate the internal and external field table numbers, and determine the order of the imported and exported file fields by the field sequence number.

[0108] In this embodiment, Figure 6 is a schematic diagram of configuring the TA system interface protocol interaction according to an embodiment of the present application, such as Figure 6As shown, the first step is the interface process configuration table: define the import and export files in all daily operation processes, the C_IOFLOW field indicates the import and export file type, the C_IOFLAG field indicates the processing flag, and the C_PATHDIR indicates the import and export folder path. The second step is to select the file type to be exported, and the interface process configuration table C_IOFLOW field is associated with the interface process classification table to obtain the export file interface process code (C_FLOWCODE) and interface version (C_IVERSIONSQL) list; C_FLOWCODE is the minimum batch unit for file export (optional support), and its batch name can be found by associating the query field code name escape table (TQUERYFIELDVALUE). The third step is to traverse the interface process code list and interface version list obtained in the second step and associate them with the SQL statement configuration table to obtain the interface version, among which: accounting export, return the interface version list of all custodian banks; salesperson market, confirm data export, return the interface version list of all salespersons. Step 4: According to the interface version list and interface flow code, associate the interface version information table and the interface file definition table to obtain the file type list under the specific interface flow code (C_FLOWCODE). Step 5: traverse the file type list obtained in step 4 and generate an export database table of specific file types in combination with the specific interface flow code.

[0109] Figure 7 is a flow chart of the fund interface protocol conversion according to an embodiment of the present application, such as Figure 7 As shown, the method may include the following steps:

[0110] Step S701, obtaining a difference document.

[0111] Step S702, configure the system to the database.

[0112] Step S703, reading the difference file field format.

[0113] Step S704, read the database file interface field maintenance table.

[0114] Step S705: Generate executable configuration statements.

[0115] Step S706, writing into the database to implement interface protocol conversion.

[0116] In this embodiment, an executable upgrade interface protocol configuration statement can be generated according to the TA system interface protocol configuration characteristics combined with the difference document output in the first part to achieve one-click fund TA interface protocol conversion.

[0117] In this embodiment, an artificial intelligence algorithm is used to analyze the differences between the new and old interface protocols, and according to the characteristics of the TA system, configuration import and export configuration scripts are generated to achieve one-click financial management interface protocol conversion, which greatly saves labor costs, improves the accuracy of fund interface upgrades, and reduces operational risks.

[0118] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0119] Example 2

[0120] The embodiment of the present application also provides an interface protocol update device for a system. It should be noted that the interface protocol update device for a system in the embodiment of the present application can be used to execute the interface protocol update method for a system provided in the embodiment of the present application. The interface protocol update device for a system provided in the embodiment of the present application is introduced below.

[0121] According to an embodiment of the present application, a device for implementing the interface protocol updating method of the above system is also provided. Figure 8 is a schematic diagram of an interface protocol updating device of a system according to an embodiment of the present application, such as Figure 8 As shown, the interface protocol updating device 800 includes: an acquiring unit 801 , a determining unit 802 , a converting unit 803 and an updating unit 804 .

[0122] The acquisition unit 801 is used to acquire the configured interface protocol of the target interface in the system to be configured and the interface protocol to be configured.

[0123] The determining unit 802 is configured to determine difference information between the interface protocol to be configured and the configured interface protocol.

[0124] The conversion unit 803 is used to convert the difference information based on the configuration attributes of the target interface to obtain configuration data.

[0125] The updating unit 804 is used to update the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured by using the configuration data.

[0126] The interface protocol updating device of the system provided in the embodiment of the present application obtains the configured interface protocol of the target interface in the system to be configured and the interface protocol to be configured through an acquisition unit; determines the difference information between the interface protocol to be configured and the configured interface protocol through a determination unit; converts the difference information based on the configuration attributes of the target interface through a conversion unit to obtain configuration data; and updates the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured through an update unit using the configuration data, thereby achieving the technical effect of improving the updating efficiency of the interface protocol and solving the technical problem of low updating efficiency of the interface protocol.

[0127] It should be noted that the acquisition unit 801, the determination unit 802, the conversion unit 803 and the update unit 804 correspond to steps S201 to S204 in Example 1, and the four modules and the corresponding steps implement the same examples and application scenarios, but are not limited to the contents disclosed in the above-mentioned Example 1. It should be noted that the above-mentioned modules or units may be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n), and the above-mentioned modules may also be part of the device and may be run in the computer terminal 10 provided in Example 1.

[0128] Example 3

[0129] An embodiment of the present application may provide an electronic device, Fig. 9 is a structural block diagram of an electronic device according to an embodiment of the present application. Fig. 9 As shown, the electronic device may include: one or more ( Fig. 9 (only one is shown) processor 902, memory 904, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0130] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0131] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: obtain the configured interface protocol of at least one target interface in the system to be configured, and the interface protocol to be configured; determine the difference information between the interface protocol to be configured and the configured interface protocol; based on the configuration attributes of the target interface, convert the difference information to obtain the configuration data of the target interface; and use the configuration data to update the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured.

[0132] The processor may also call the information and application programs stored in the memory through the transmission device to perform the following steps: converting the difference information to obtain a difference document; and converting the difference document based on the configuration attributes to obtain configuration data.

[0133] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: determine the target configuration attribute that matches the difference information among multiple configuration attributes; based on the target configuration attribute, convert the difference document to obtain configuration data.

[0134] The processor may also call the information and application program stored in the memory through the transmission device to perform the following steps: mapping the difference document according to the target configuration attribute to obtain a mapping result; and generating configuration data according to the mapping result.

[0135] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: cutting the interface protocol to be configured to obtain at least one first sub-data, and cutting the configured interface protocol to obtain at least one second sub-data; according to the preset characteristics, determine the difference information between the first sub-data and the second sub-data.

[0136] By adopting the embodiment of the present application, a system interface protocol update method is provided, which obtains the configured interface protocol and the interface protocol to be configured, determines the difference information between the two, and converts the difference information using the configuration data of the target interface to obtain the configuration data. The configured interface protocol can be updated according to the configuration data to obtain the interface protocol to be configured, thereby achieving the technical effect of improving the update efficiency of the interface protocol and solving the technical problem of low update efficiency of the interface protocol.

[0137] It can be understood by those skilled in the art that Fig. 9The structure shown is for illustration only, and the electronic device may also be a terminal device such as a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, abbreviated as MID), a personal access device (Personal Access Device, abbreviated as PAD), etc. Fig. 9 The structure of the electronic device is not limited. Fig. 9 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Fig. 9 Different configurations are shown.

[0138] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0139] Example 4

[0140] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the system interface protocol update method provided in the first embodiment.

[0141] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0142] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing the program steps of the system interface protocol updating method.

[0143] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0144] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0145] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0146] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0147] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0148] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), mobile hard disk, disk or optical disk and other media that can store program codes.

[0149] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for updating a system interface protocol, characterized in that: include: Obtaining a configured interface protocol of at least one target interface in the system to be configured and an interface protocol to be configured; Determine difference information between the interface protocol to be configured and the configured interface protocol; Based on the configuration attributes of the target interface, convert the difference information to obtain configuration data of the target interface; The configuration data is used to update the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured.

2. The method according to claim 1, characterized in that The converting the difference information based on the configuration attribute of the target interface to obtain the configuration data includes: Converting the difference information to obtain a difference document; Based on the configuration attributes, the difference document is converted to obtain the configuration data.

3. The method according to claim 2, characterized in that The converting the difference document based on the configuration attribute to obtain the configuration data includes: Determine, among the plurality of configuration attributes, a target configuration attribute that matches the difference information; Based on the target configuration attribute, the difference document is converted to obtain the configuration data.

4. The method according to claim 3, characterized in that The converting the difference document based on the target configuration attribute to obtain the configuration data includes: According to the target configuration attribute, mapping the difference document to obtain a mapping result; The configuration data is generated according to the mapping result.

5. The method according to claim 1, characterized in that: The determining of difference information between the interface protocol to be configured and the configured interface protocol includes: Cut the interface protocol to be configured to obtain at least one first sub-data, and cut the configured interface protocol to obtain at least one second sub-data; According to a preset feature, the difference information between the first sub-data and the second sub-data is determined.

6. The method according to claim 1, characterized in that The step of using the configuration data to update the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured includes: inputting the configuration data into a database; According to the configuration data, the configured interface protocol in the database is updated to the interface protocol to be configured.

7. A system interface protocol updating device, characterized in that: include: An acquisition unit, used for acquiring the configured interface protocol of the target interface in the system to be configured and the interface protocol to be configured; A determination unit, configured to determine difference information between the interface protocol to be configured and the configured interface protocol; A conversion unit, configured to convert the difference information based on the configuration attributes of the target interface to obtain configuration data; An updating unit is used to update the interface protocol of the target interface from the configured interface protocol to the interface protocol to be configured using the configuration data.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 6 when running.

10. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images