Configuration-based interface response information conversion method, device and equipment

Abstract

The invention provides a configuration-based interface response information conversion method, device and equipment. The method comprises the following steps: configuring a strategy table, a conversion rule table and a strategy and conversion rule association table; initializing all configuration items to a strategy pool and a conversion rule pool; intercepting and identifying an interface number, a response result code and response result description information; matching a corresponding strategy table and a conversion rule table in the strategy pool; calling a parser to parse and map the association rules in sequence to obtain internal and external result information; and transmitting the mapped internal and external information to subsequent processing logic, recording a log, and returning the log to the client. According to the method, a standardized and configurable conversion mechanism is provided, original error codes and error descriptions which are different in source and high in technicality are intelligently converted into detailed error information needed for internal troubleshooting and guide information friendly to external users, and therefore unified management and flexible expansion of interface error processing are achieved.

Description

Technical Field

[0001] This application relates to the fields of computer technology and information technology, and more specifically to a method, apparatus, and device for configuration-based interface response information conversion. Background Technology

[0002] Currently, the functionality of enterprise-level software systems increasingly relies on the collaborative work of multi-source heterogeneous systems, and third-party interface integration has become a core aspect of system development. Due to significant differences in development standards, technical architectures, and business scenarios among various third-party interfaces, the error messages they return exhibit strong heterogeneity. This is mainly reflected in the following three aspects: first, inconsistent error code rules; second, an imbalance in the level of detail in error descriptions; and third, significant differences in description styles. Ordinary users cannot understand these messages, while the descriptions of some interfaces are too vague (e.g., "operation failed"), failing to meet internal debugging needs or guide user operations.

[0003] This method, based on configuration interface response information transformation, includes strategies, matching rules, and configurations for associating strategies and rules. All interface-level configurations are integrated into a strategy pool, and rules for transforming interface response encoding and description information are integrated into a rule pool. This unified, configurable, and easily maintainable interface response information transformation scheme manages all third-party interfaces requiring transformation, standardizes the processing of heterogeneous error information, and outputs differentiated format information adapted to internal debugging and external users. This is crucial for ensuring system operation and maintenance efficiency and user experience. Summary of the Invention

[0004] This application addresses the technical problems existing in the prior art by providing a configuration-based interface response information conversion method, apparatus, and device. The method provided in this application can convert error descriptions of interfaces connected to third parties, outputting differentiated format information adapted for internal debugging and external user-friendly prompts.

[0005] Firstly, this application provides a configuration-based method for converting interface response information, applied to a current system that interfaces with an upstream system. The method includes: Configure the policy table, conversion rule table, and policy-conversion rule association table; When the application service is enabled, all configuration items are initialized to the policy pool and transformation rule pool; Receive responses from upstream systems to requests for interfaces, and intercept and identify the interface number (InterfaceID), response result encoding, and response result description information; Based on the identified InterfaceID, match the corresponding policy table and transformation rule table in the policy pool; The parser is invoked to sequentially parse and map the association rules into internal and external result information. The mapped internal and external information is passed to subsequent processing logic, and logs are recorded and returned to the client.

[0006] In one possible implementation, the parameters of the strategy table are as follows: Trac_ID: Strategy number; Trac_Desc: Policy description; Enabled: Whether it is available, Y - enabled, N - disabled; InterfaceID: Third-party interface number; IsInConver: Whether internal conversion is enabled, Y - Enabled, N - Disabled; IsOutConver: Whether external conversion is enabled, Y - Enabled, N - Disabled.

[0007] In one possible implementation, the parameters of the transformation rule table are as follows: ConvRule_ID: Rule number; Trac_Desc: Rule description; Enabled: Whether it is available, Y - enabled, N - disabled; AccordType: Matches the object type; Code: Response code; Message: Response message. AnalyType: Matching method type, Equ: equal to, Include: includes, Begin: start of matching, End: end of matching; AnalyContent: Matching content; InConverResult: Internal conversion result; OutConverResult: External conversion result.

[0008] In one possible implementation, the parameters of the strategy and transformation rule association table are as follows: Rela_ID: Associated serial number; Trac_ID: Strategy number; ConvRule_ID: Rule number, the rule number of the rule ConvRule; AnalyOrder: The parsing order, the sorting number of the parsing rules.

[0009] In one possible implementation, initializing all configuration items to the policy pool and transformation rule pool when enabling the application service includes: Iterate through the full configuration policy table and filter out the effective policies with an enabled status of Y; The effective policies are then placed into the policy pool in sequence. Iterate through the entire configuration's conversion rule table and filter out the effective rules whose enabled status is Y; The effective rules are then placed into the conversion rule pool in sequence.

[0010] In one possible implementation, the step of matching the corresponding policy table and transformation rule table in the policy pool based on the identified interface ID (InterfaceID) includes: The policy pool is traversed sequentially; if the identified interface number is equal to the interface number InterfaceID configured in the policy table, the match is successful and information conversion processing is performed; otherwise, information conversion processing is not performed. Based on the successfully matched strategy ID Trac_ID, traverse the strategy and transformation rule association table to match the associated rule ID ConvRule_ID; then use the rule ID to traverse the rule table in the transformation rule pool that matches it.

[0011] In one possible implementation, the call parser sequentially parses the association rules to map out internal and external result information, including: The parser is invoked to receive the interface response result encoding and result description information. The configuration items for loading the matching strategy table include whether internal conversion is enabled (IsInConver) and whether external conversion is enabled (IsOutConver). After parsing the rules, these two parameters are used to determine whether internal and external conversion information needs to be processed. Sort all matching rule tables in ascending order according to the parsing order of the strategy and transformation rule association tables; Parse the first rule after sorting and load the matching configuration parameters: matching object type AccordType, matching method type AnalyType, and matching content AnalyContent; If the matched object type AccordType is Code, the rule takes the encoding of the interface response result as the subsequent matching data source MatDataSource; if the matched object type AccordType is Message, the rule takes the description information of the interface response result as the subsequent matching data source MatDataSource. Split the matched content, dividing the matched content AnalyContente into multiple matched sub-items using delimiters; The split matching sub-items are matched with the data source MatDataSource according to the configured matching method AnalyType; if the match is successful, the corresponding internal transformation result InConverResult and external transformation result OutConverResult are extracted; if the match is unsuccessful, the next rule is parsed and matched. Determine whether to return the matched internal / external transformation result value based on the enabled status of loading internal / external transformations.

[0012] Secondly, this application provides a configuration-based interface response information conversion device, applied to a current system that interfaces with an upstream system, the device comprising: The configuration module is used to configure the strategy table, the transformation rule table, and the strategy-transformation rule association table. The initialization module is used to initialize all configuration items to the policy pool and transformation rule pool when the application service is enabled. The response identification module is used to receive responses from upstream systems to interface requests, and to intercept and identify the interface number (InterfaceID), response result encoding, and response result description information. The matching module is used to match the corresponding policy table and transformation rule table in the policy pool based on the identified interface number InterfaceID; The parsing module is used to call the parser to sequentially parse and map the association rules into internal and external result information; The transmission module is used to pass the mapped internal and external information to the subsequent processing logic, and to log and return the information to the client.

[0013] Thirdly, this application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements a configuration-based interface response information conversion method as described in the first aspect.

[0014] Fourthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a configuration-based interface response information conversion method as described in the first aspect.

[0015] The technical effects of this application are as follows: The method described in this application provides a standardized and configurable conversion mechanism to intelligently convert original error codes and error descriptions from various sources and with high technical complexity into detailed error information needed for internal troubleshooting and user-friendly guidance information for external users. This efficiently solves the problem of handling error information from multiple interfaces and enables unified management and flexible expansion of interface error handling. The method provided in this application standardizes heterogeneous information, is compatible with various coding rules, unifies the output format, eliminates the need for manual matching and interpretation, and reduces operation and maintenance costs. The method provided in this application outputs in a dual format: internally, it provides debugging information including source code and technical details to shorten troubleshooting time; externally, it outputs easy-to-understand instructions to users, which can reduce the number of customer service inquiries. The method provided in this application can significantly improve maintainability, requiring only additional configuration for new interfaces, thus shortening the access cycle; at the same time, it has built-in sensitive information filtering to prevent technology leakage and ensure security. Attached Figure Description

[0016] Figure 1 A flowchart illustrating a configuration-based method for converting interface response information provided in an embodiment of this application; Figure 2 A schematic diagram of the three configuration tables provided in the embodiments of this application; Figure 3 A schematic diagram illustrating the configuration strategies and conversion rules provided in the embodiments of this application; Figure 4 A schematic diagram illustrating the process of receiving and converting information returned from the upstream system according to configuration, provided for an embodiment of this application; Figure 5 A schematic diagram of a configuration-based interface response information conversion device provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0017] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0018] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0019] In the description of this application, the term "for example" is used to mean "used as an example, illustration, or description." Any embodiment described as "for example" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid unnecessarily obscuring the description of this application. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0020] Based on the deficiencies in the background technology, especially the technical problems of converting incorrect descriptions when connecting to third-party interfaces in existing methods, this application provides a configuration-based interface response information conversion method, apparatus, and device.

[0021] See Figure 1 This application provides a method for converting configuration interface response information, used in a current system that interfaces with an upstream system. The method includes the following steps: S101, Configuration strategy table, conversion rule table, and strategy-conversion rule association table.

[0022] In one possible implementation, the parameters of the strategy table are as follows: Trac_ID: Strategy number; Trac_Desc: Policy description; Enabled: Whether it is available, Y - enabled, N - disabled; InterfaceID: Third-party interface number; IsInConver: Whether internal conversion is enabled, Y - Enabled, N - Disabled; IsOutConver: Whether external conversion is enabled, Y - Enabled, N - Disabled.

[0023] For example, the tactics table is as follows:

[0024] In one possible implementation, the parameters of the transformation rule table (ConvRule) are as follows: ConvRule_ID: Rule number; Trac_Desc: Rule description; Enabled: Whether it is available, Y - enabled, N - disabled; AccordType: Matches the object type; Code: Response code; Message: Response message. AnalyType: Matching method type, Equ: equal to, Include: includes, Begin: start of matching, End: end of matching; AnalyContent: Matching content; InConverResult: Internal conversion result; OutConverResult: External conversion result.

[0025] It should be noted that the matching content refers to a set of data, rules, identifiers, or conditions used to establish correspondences, identify rules, or determine transformation logic during a transformation, mapping, or response process. It serves as a bridge and basis connecting the "internal result" (raw / standard data) and the "external result" (target / presentation data).

[0026] The internal conversion result refers to the data format, unit, or encoding used when processing or storing data within the system (current system). It typically employs standardized and unified formats (such as UTC time, International System of Units, or specific character encoding). For example, time is stored as a UTC timestamp (e.g., 1625097600), and currency is stored in "cents" or "basic units" (e.g., RMB is stored in "cents," with 100 representing 1 yuan).

[0027] The external conversion result refers to the data format, unit, or encoding converted according to the user or client (upstream system) requirements for use in external interface responses. For example, time: converted to the user's local time (e.g., 2021-07-01 08:00:00 CST), currency: converted to a local format with currency symbols (e.g., ¥1.00 or $1.00). For example, the conversion rule table is as follows:

[0028] In one possible implementation, the strategy and conversion rule association table (Tactics_ConvRule_Rela) parameters are as follows: Rela_ID: Associated serial number, the numbering rule is to start with R followed by an auto-incrementing sequence of numbers; Trac_ID: Strategy ID, the strategy ID of the strategy Tactics. ConvRule_ID: Rule number, the rule number of the rule ConvRule. AnalyOrder: Parsing order, the sorting number of the parsing rules. For example, the association table between the strategy and the conversion rules is as follows:

[0029] Figure 2 Three configuration tables for embodiments of this application are shown.

[0030] S102. When enabling the application service, initialize all configuration items to the policy pool and transformation rule pool.

[0031] In one possible implementation, S102 includes: S102a. Traverse the full configuration policy table and filter out the effective policies with the enabled status set to Y. S102b: Place the effective policies into the policy pool in sequence; S102c: Traverse the full configuration conversion rule table and filter out the effective rules with the enabled status set to Y; S102d. Place the effective rules described in S102c into the ConvRulePool in sequence.

[0032] S103. Receive the response from the upstream system to the interface request, and intercept and identify the interface number InterfaceID, response result encoding, and response result description information.

[0033] It should be noted that the response result encoding is a predefined, standardized numeric or alphanumeric code used to quickly and accurately represent the execution status and result category of an API call. It is language-independent and is a machine-readable identifier for the operation result.

[0034] The response description is human-readable natural language text that details the result of the API call, the cause of any errors, or suggestions for the user. It is a user-friendly prompt for both developers and end users.

[0035] S104. Based on the identified interface ID (InterfaceID), match the corresponding policy table and conversion rule table (ConvRule) in the policy pool.

[0036] In one possible implementation, S104 includes: S104a. Iterate through the TacticsPool sequentially. If the identified interface number is equal to the InterfaceID configured in the Tactics table, the match is successful, and information conversion processing is performed; otherwise, information conversion processing is not performed. S104b. Based on the successfully matched strategy number Trac_ID, traverse the strategy and transformation rule association table Tactics_ConvRule_Rela to match the associated rule number ConvRule_ID; use the rule number to traverse the matching rule table ConvRule in the transformation rule pool ConvRulePool.

[0037] S105. Call the parser to sequentially parse and map the association rules to the internal and external result information.

[0038] See Figure 3 , Figure 3 The configuration strategies and conversion rules provided in the embodiments of this application are illustrated.

[0039] In one possible implementation, see [link to relevant documentation] Figure 4 S105 includes: S105a, Call the parser to receive the interface response result encoding and result description information; S105b: Load the configuration items of the matching strategy table Tactics to determine whether internal conversion is enabled (IsInConver) and external conversion is enabled (IsOutConver). After parsing the rules, these two parameters will be used to determine whether internal and external conversion information needs to be processed. S105c. Sort all matched rule tables ConvRule in ascending order according to the parsing order of the strategy and transformation rule association table Tactics_ConvRule_Rela, AnalyOrder. S105d, Parse the first rule after sorting, and load the matching configuration parameters: matching object type AccordType, matching method type AnalyType, and matching content AnalyContent; S105e. If the matched object type AccordType is Code, then this rule takes the interface response result encoding as the subsequent matched data source MatDataSource; if the matched object type AccordType is Message, then this rule takes the interface response result description information as the subsequent matched data source MatDataSource. S105f, Split the matched content, split the matched content AnalyContente into multiple matched sub-items using the delimiter |&|; S105g: Match the split matching sub-items with the data source MatDataSource according to the configured matching method AnalyType; if the match is successful, extract the corresponding internal transformation result InConverResult and external transformation result OutConverResult; if the match is unsuccessful, continue to parse the next rule for matching. S105h: Based on the enabled status of loading internal / external conversion in S105b, determine whether to return the matched internal / external conversion result value.

[0040] S106. Pass the mapped internal and external information to the subsequent processing logic, record the log, and return it to the client.

[0041] In one possible implementation, the subsequent processing logic in S106 includes: communication layer processing logic, business layer processing logic, and user interaction layer processing logic.

[0042] Specifically, the communication layer processing logic includes: displaying a system maintenance prompt if a network / HTTP error occurs; and proceeding to the business layer for processing if a response body is successfully received.

[0043] Specifically, the business layer processing logic includes: processing according to business codes, updating local data upon successful processing; displaying registration guidance if the user does not exist; and displaying a verification code input box if a verification code is required.

[0044] Specifically, the user interaction layer processing logic includes: order payment, displaying a successful result; price change, displaying a price update confirmation.

[0045] Understandably, the subsequent processing logic refers to the program flow control and business processing performed by the client after receiving the interface response, based on the response result (especially the response encoding and description). It defines "what should be done next after receiving the response".

[0046] The method provided in this application first configures Tactics, ConvRule, and Tactics_ConvRule_Rela to configure the conversion mechanism; then, it initializes the configuration items into the policy pool; next, it receives the response from the upstream system to the interface request, intercepts and identifies the interface number InterfaceID, the response result encoding, and the response result description information; next, based on the identified interface number InterfaceID, it matches the corresponding policy table and conversion rule table in the policy pool; then, it calls the parser to sequentially parse and map the associated rules to the internal and external result information. Through the relevant rules, the conversion rules can be parsed in sequence and error information can be excluded, effectively solving the problem of handling error information from multiple interfaces, and enabling dual-format output. Internally, it provides debugging information containing source code and technical details, shortening the troubleshooting time; externally, it outputs easy-to-understand guidance to users, reducing the volume of customer service inquiries; finally, it passes the mapped internal and external information to the subsequent processing logic, records logs, and returns it to the client.

[0047] The method provided in this application can standardize heterogeneous information, be compatible with various encoding rules, and unify the output format. It eliminates the need for manual matching and interpretation, reducing operation and maintenance costs. It can also significantly improve maintainability, requiring only additional configuration for new interfaces, thus shortening the access cycle. At the same time, it has built-in sensitive information filtering to prevent technology leakage and ensure security.

[0048] The following describes the configuration-based interface response information conversion apparatus provided in this application. The configuration-based interface response information conversion apparatus described below and the configuration-based interface response information conversion method described above can be referred to in correspondence.

[0049] Figure 5 This is a schematic diagram of the structure of an interface response information conversion device based on configuration provided in an embodiment of this application, as shown below. Figure 5 As shown, it includes: a configuration module 51, an initialization module 52, a response recognition module 53, a matching module 54, a parsing module 55, and a transmission module 56, wherein: Configuration module 51 is used to configure the strategy table, the conversion rule table, and the strategy-conversion rule association table; Initialization module 52 is used to initialize all configuration items to the policy pool and transformation rule pool when the application service is enabled; The response identification module 53 is used to receive the response to the interface request from the upstream system, and to intercept and identify the interface number InterfaceID, response result code, and response result description information. The matching module 54 is used to match the corresponding policy table and conversion rule table in the policy pool based on the identified interface number InterfaceID; Parsing module 55 is used to call the parser to sequentially parse and map the association rules into internal and external result information; The transmission module 56 is used to transmit the mapped internal and external information to the subsequent processing logic, and to record logs and return them to the client.

[0050] Figure 6 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 6 As shown, the electronic device may include a processor 810, a communications interface 620, a memory 630, and a communications bus 640. The processor 610, communications interface 620, and memory 630 communicate with each other via the communications bus 640. The processor 610 can invoke logical instructions from the memory 630 to execute a configuration-based interface response information conversion method.

[0051] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0052] On the other hand, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is implemented to perform a configuration-based interface response information conversion method provided by the above methods.

[0053] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0054] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0055] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for converting interface response information based on configuration, characterized in that, Applied to the current system, which interfaces with the upstream system, the method includes: Configure the policy table, conversion rule table, and policy-conversion rule association table; When the application service is enabled, all configuration items are initialized to the policy pool and transformation rule pool; Receive responses from upstream systems to requests for interfaces, and intercept and identify the interface number (InterfaceID), response result encoding, and response result description information; Based on the identified InterfaceID, match the corresponding policy table and transformation rule table in the policy pool; The parser is invoked to sequentially parse and map the association rules into internal and external result information. The mapped internal and external information is passed to subsequent processing logic, and logs are recorded and returned to the client.

2. The method according to claim 1, characterized in that, The parameters of the strategy table are as follows: Trac_ID: Strategy number; Trac_Desc: Policy description; Enabled: Whether it is available, Y - enabled, N - disabled; InterfaceID: Third-party interface number; IsInConver: Whether internal conversion is enabled, Y - Enabled, N - Disabled; IsOutConver: Whether external conversion is enabled, Y - Enabled, N - Disabled.

3. The method according to claim 1, characterized in that, The parameters of the conversion rule table are as follows: ConvRule_ID: Rule number; Trac_Desc: Rule description; Enabled: Whether it is available, Y - enabled, N - disabled; AccordType: Matches the object type; Code: Response code; Message: Response message. AnalyType: Matching method type, Equ: equal to, Include: includes, Begin: start of matching, End: end of matching; AnalyContent: Matching content; InConverResult: Internal conversion result; OutConverResult: External conversion result.

4. The method according to claim 1, characterized in that, The parameters of the strategy and conversion rule association table are as follows: Rela_ID: Associated serial number; Trac_ID: Strategy number; ConvRule_ID: Rule number, the rule number of the rule ConvRule; AnalyOrder: The parsing order, the sorting number of the parsing rules.

5. The method according to claim 1, characterized in that, When enabling the application service, all configuration items are initialized to the policy pool and transformation rule pool, including: Iterate through the full configuration policy table and filter out the effective policies with an enabled status of Y; The effective policies are then placed into the policy pool in sequence. Iterate through the entire configuration's conversion rule table and filter out the effective rules whose enabled status is Y; The effective rules are then placed into the conversion rule pool in sequence.

6. The method according to claim 1, characterized in that, The step of matching the corresponding policy table and transformation rule table in the policy pool based on the identified interface ID (InterfaceID) includes: The policy pool is traversed sequentially; if the identified interface number is equal to the interface number InterfaceID configured in the policy table, the match is successful and information conversion processing is performed; otherwise, information conversion processing is not performed. Based on the successfully matched strategy ID Trac_ID, traverse the strategy and transformation rule association table to match the associated rule ID ConvRule_ID; then use the rule ID to traverse the rule table in the transformation rule pool that matches it.

7. The method according to claim 1, characterized in that, The call parser sequentially parses and maps the association rules to internal and external result information, including: The parser is invoked to receive the interface response result encoding and result description information. The configuration items for loading the matching strategy table include whether internal conversion is enabled (IsInConver) and whether external conversion is enabled (IsOutConver). After parsing the rules, these two parameters are used to determine whether internal and external conversion information needs to be processed. Sort all matching rule tables in ascending order according to the parsing order of the strategy and transformation rule association tables; Parse the first rule after sorting and load the matching configuration parameters: matching object type AccordType, matching method type AnalyType, and matching content AnalyContent; If the matched object type AccordType is Code, the rule takes the interface response result encoding as the subsequent matched data source MatDataSource; if the matched object type AccordType is Message, the rule takes the interface response result description information as the subsequent matched data source MatDataSource. Split the matched content, dividing the matched content AnalyContente into multiple matched sub-items using delimiters; The split matching sub-items are matched with the data source MatDataSource according to the configured matching method AnalyType; if the match is successful, the corresponding internal transformation result InConverResult and external transformation result OutConverResult are extracted; if the match is unsuccessful, the next rule is parsed and matched. Determine whether to return the matched internal / external transformation result value based on the enabled status of loading internal / external transformations.

8. A device for converting interface response information based on configuration, characterized in that, Applied to the current system, which interfaces with the upstream system, the device includes: The configuration module is used to configure the strategy table, the transformation rule table, and the strategy-transformation rule association table. The initialization module is used to initialize all configuration items to the policy pool and transformation rule pool when the application service is enabled. The response identification module is used to receive responses from upstream systems to interface requests, intercept and identify the interface number (InterfaceID), response result encoding, and response result description information. The matching module is used to match the corresponding policy table and transformation rule table in the policy pool based on the identified interface number InterfaceID; The parsing module is used to call the parser to sequentially parse and map the association rules into internal and external result information; The transmission module is used to pass the mapped internal and external information to the subsequent processing logic, and to log and return the information to the client.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements a configuration-based interface response information conversion method as described in any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements a configuration-based interface response information conversion method as described in any one of claims 1 to 7.

Images