General dynamic adaptation method and system for interface docking with filing management bureau

Abstract

The invention discloses a general dynamic adaptation method and system for interface docking with a filing management bureau, and belongs to the technical field of communication network and government affair interface data processing, the system uniformly packages HTTP, HTTPS, SOAP, REST and XML, JSON and Form differences based on protocol, data format and semantic three-level abstraction; field automatic matching is realized through combination of rule mapping and semantic recognition, and manual feedback updating is supported; the authentication plug-in is automatically switched according to a response state; adjusting timeout, retry, current limiting and fusing of the calling strategy according to historical data; the security gateway adds a timestamp and an HMAC signature, encrypts sensitive data, and records a full-link log; through combination of the distributed gateway and the configuration center, access can be realized without code change of a newly-added management bureau.

Description

Technical Field

[0001] This invention belongs to the field of communication network and government interface data processing technology, and in particular relates to a general dynamic adaptation method and system for interface docking with the filing authority. Background Technology

[0002] With the implementation of my country's Internet information service filing system, various online platforms are required to submit filing information to the local communications administration bureau before going online and complete data interaction through its e-government interface. Because the systems of the provincial and municipal administration bureaus are independently built by different vendors, the technical standards are not uniform, and the interfaces differ in communication protocols, data formats, field naming, authentication mechanisms, and error code systems, making the integration process difficult to reuse and resulting in high maintenance costs.

[0003] Currently, common integration methods mainly include custom development for each regulatory authority, static configuration for field mapping, or using an intermediate proxy layer to forward requests. These methods generally suffer from high code duplication, difficulty in adapting to interface changes, and a lack of semantic understanding of fields.

[0004] Furthermore, existing technologies also have the following shortcomings: it is difficult to establish a unified abstract model to shield protocol and format differences; field mapping relies on manual fixed configuration; it is impossible to dynamically adjust authentication methods and calling strategies based on interface response behavior; and it lacks capabilities in request signing, anti-replay, encrypted transmission, extended access, and fault location. Summary of the Invention

[0005] In view of this, the present invention aims to propose a general dynamic adaptation method and system for interface docking with the filing authority, so as to at least solve one of the problems in the background art.

[0006] To achieve the above objectives, the technical solution of the present invention is implemented as follows: A general dynamic adaptation method for interface integration with the filing authority includes: Obtain the target regulatory authority's identifier; Read the interface metadata corresponding to the target authority from the configuration center. The interface metadata includes at least the protocol type, data format, field dictionary, authentication configuration, error code mapping rules, and call constraints. The interface metadata is processed based on a multi-level interface abstraction layer, which includes at least protocol abstraction, data format abstraction and semantic abstraction, so as to convert the unified semantic model on the business side into the target interface request and the target interface response into the unified semantic model. The dynamic field mapping engine is invoked to map the fields of the unified semantic model to the target fields in the field dictionary. Rule mapping is preferred, and when rules are missing or fields do not match, semantic recognition is used to generate candidate mappings and form executable mappings. The authentication strategy adaptive module is invoked to assemble authentication information according to the authentication configuration, and the authentication method is switched when an authentication failure response is detected. The API call strategy engine adjusts timeouts, retry rates, and frequencies based on historical call data and executes rate limiting or circuit breaking strategies. The request is sent to the target regulatory authority's interface after being timestamped and HMAC-signed by the security audit gateway and sensitive data is encrypted. Upon receiving the response, output the general processing result according to the error code mapping rules and record the full-link log.

[0007] Furthermore, the dynamic field mapping engine supports manual feedback calibration and writes the manually confirmed mapping relationship back to the configuration center to form mapping rules; when a change in the target regulatory authority interface version is detected, the mapping rules associated with that interface version are loaded first.

[0008] Furthermore, the interface call strategy engine dynamically adjusts at least one call parameter based on historical call data. The call parameters include call frequency, timeout, number of retries, and concurrency limit. When the failure rate or timeout rate threshold is met, rate limiting, circuit breaking, or degradation strategies are executed. The degradation strategy includes writing the request to a queue for subsequent submission.

[0009] Furthermore, this solution discloses a general dynamic adaptation system for interface communication with the filing authority, including: Multi-level interface abstraction layer, dynamic field mapping engine, authentication policy adaptive module, interface call strategy engine, security audit gateway, distributed interface gateway cluster, and configuration center; The configuration center is used to store and distribute interface metadata corresponding to the target authority. The multi-level interface abstraction layer is used to perform protocol abstraction, data format abstraction, and semantic abstraction. The dynamic field mapping engine is used to switch between rule mapping and semantic recognition to generate executable mappings; The authentication strategy adaptive module is used to assemble authentication information and switch authentication methods when authentication fails. The interface call strategy engine is used to dynamically adjust call parameters and execute rate limiting or circuit breaking strategies. The security audit gateway is used to sign and encrypt outgoing requests and record full-link logs. The distributed interface gateway cluster is used to provide external connection services and supports horizontal scaling and load balancing.

[0010] Furthermore, the multi-level interface abstraction layer includes a protocol adaptation unit, a format conversion unit, and a semantic conversion unit; the semantic conversion unit is used to perform bidirectional conversion between the unified semantic model and the target regulatory field set.

[0011] Furthermore, the dynamic field mapping engine includes a rule mapping unit and a semantic recognition unit; the semantic recognition unit is used to generate a candidate mapping list based on the field name or field description text when a rule is missing or a field does not match, and supports updating the rule base of the rule mapping unit after manual confirmation.

[0012] Furthermore, the interface call strategy engine includes a statistical analysis unit and a strategy execution unit; the statistical analysis unit is used to statistically analyze the call success rate and latency distribution of the target administration; the strategy execution unit is used to adjust timeouts and retries accordingly, and to perform rate limiting, circuit breaking, or degradation when thresholds are met.

[0013] Furthermore, the system supports adding new regulatory agencies to the system by adding the agency's interface metadata, field dictionary, and authentication configuration in the configuration center, without changing the already deployed docking service program.

[0014] Furthermore, this solution discloses an electronic device, including a processor and a memory, wherein the memory stores a computer program, and the computer program, when executed by the processor, implements the method described.

[0015] Furthermore, this solution discloses a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the method described thereon.

[0016] Compared with existing technologies, the universal dynamic adaptation method and system for interface docking with the filing authority described in this invention has the following advantages: (1) This invention encapsulates the differences in protocols such as HTTP, HTTPS, SOAP, and REST, as well as the differences in data formats such as XML, JSON, and Form, adopted by different regulatory authorities through three-level abstraction of protocol, data, and semantics. It also unifies the fields into semantic models such as subject information, website information, and access information, so that the upper-layer business can be connected according to a unified model, which significantly reduces the amount of repetitive development work. (2) This invention uses a dynamic field mapping mechanism, combined with rule mapping and semantic recognition, to perform field semantic matching when the interface is first accessed or when the field changes, and supports continuous updating of mapping rules after manual feedback calibration, thereby reducing the maintenance cost and failure risk caused by interface changes; (3) The authentication strategy adaptive module of the present invention supports multiple authentication method plugins and can automatically switch authentication strategies according to the interface response status, such as 401 error type; the interface call strategy engine can dynamically adjust the call frequency, timeout and retry based on historical call data, and supports circuit breaking, degradation and rate limiting strategies, thereby improving availability under the conditions of fluctuations on the government side and network instability. (4) The security audit gateway of the present invention can automatically add timestamps and HMAC digital signatures to requests to reduce the risk of replay attacks, perform AES encryption transmission of sensitive data, and record full-link call logs to meet the needs of security audit and traceability. (5) The present invention adopts a microservice architecture of distributed interface gateway cluster, which supports horizontal expansion, cross-regional deployment and load balancing; combined with a centralized configuration center, it supports real-time parameter push, version management and rollback, so that new access of the management bureau or configuration adjustment does not require code modification and service restart. Attached Figure Description

[0017] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings: Figure 1 This is a schematic diagram of the method described in an embodiment of the present invention; Figure 2 This is a schematic diagram of the overall system architecture as described in an embodiment of the present invention; Figure 3 This is a schematic diagram of the distributed gateway deployment topology according to an embodiment of the present invention. Detailed Implementation

[0018] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0019] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first," "second," etc., 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 with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0020] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art will understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0021] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0022] Example 1: System Composition and Deployment The general dynamic adaptation system in this embodiment is deployed on the network platform side, providing unified filing and docking services to multiple target regulatory authorities. The system includes at least a multi-level interface abstraction layer MIAL, a dynamic field mapping engine DFME, an authentication policy adaptive module ASAM, an interface call policy engine ICSE, a security audit gateway SAG, a distributed interface gateway cluster DIGC, and a configuration center and hot update mechanism.

[0023] 1. Multi-level Interface Abstraction Layer (MIAL) MIAL includes a protocol abstraction layer, a data format abstraction layer, and a semantic abstraction layer. It is used to shield the differences between underlying protocols such as HTTP, HTTPS, SOAP, and REST, uniformly handle the parsing and generation of data formats such as XML, JSON, and Form, and map the regulatory field to a unified semantic model for upper-layer business calls.

[0024] 2. Dynamic Field Mapping Engine DFME DFME supports rule mapping and introduces a semantic recognition module to perform field semantic matching through text similarity algorithms such as Levenshtein, Jaro-Winkler, or lightweight natural language models; it also supports manual feedback calibration to update mapping rules.

[0025] To facilitate project implementation and reduce the risk of mismapping, this embodiment further discloses the following mechanism: a) Confidence score of candidate mapping: Calculate the confidence score for each candidate mapping and set a first threshold and a second threshold; candidate mappings that are higher than the first threshold can be automatically activated, candidate mappings that are between the two thresholds enter the manual confirmation queue, and candidate mappings that are lower than the second threshold are marked as requiring additional field definitions.

[0026] b) Mapping version management: Each time the mapping rule is changed, a mapping version number is generated and associated with the target regulatory authority interface version. When the call failure rate exceeds the preset threshold within the statistics window, it will automatically fall back to the previous mapping version to reduce the spread of anomalies.

[0027] 3. Authentication Policy Adaptive Module ASAM ASAM adopts a plug-in architecture and supports multiple authentication methods such as API Key, OAuth2.0, digital certificate, and dynamic token. It can automatically switch authentication strategies based on the interface response status, such as 401 error type, and perform token refresh or certificate update when necessary.

[0028] This embodiment is further extended: to avoid additional failures caused by frequent switching, an authentication switching cooldown time and a maximum number of switching times can be set. When the continuous switching reaches the upper limit, a manual investigation or delayed retry process is initiated.

[0029] 4. Interface Call Strategy Engine ICSE ICSE dynamically adjusts call frequency, timeout, and retry count based on historical call data, and supports strategies such as circuit breaking, degradation, and rate limiting. It can also configure different call constraint rules for different regulatory authorities.

[0030] This embodiment is further extended as follows: a) The timeout parameter can be automatically adjusted according to the response time distribution over a recent period. For example, the timeout can be set to the larger of the high quantile value of historical timeout and the minimum upper limit. b) Retry uses a backoff interval strategy to avoid concentrated requests during transient failures; c) When the circuit breaker is triggered and the business allows for a delayed submission, the filing request will be written into the queue and the status of "accepted and pending submission" will be returned. The filing will be automatically submitted after the detection is restored.

[0031] 5. Security Audit Gateway (SAG) SAG is used to automatically add timestamps and HMAC digital signatures to outgoing requests to reduce the risk of replay attacks, encrypt sensitive data for transmission with AES, and record end-to-end call logs for auditing and tracing.

[0032] This embodiment extends the log field set to include at least the target authority identifier, interface version, mapping version, authentication method identifier, request time, response code, and general error classification, and de-identifies and stores sensitive fields in the logs.

[0033] 6. Distributed Interface Gateway Cluster (DIGC) and Configuration Center DIGC adopts a microservice architecture, supports horizontal scaling, cross-regional deployment and local access, and achieves load balancing through service registration and discovery mechanisms.

[0034] The configuration center centrally manages the interface parameters of each regulatory authority, supports real-time push of configuration changes without requiring service restarts, and has configuration version management and rollback capabilities.

[0035] Example 2: Method Flow Example (Taking Jiangsu Administration Bureau) This embodiment provides an end-to-end processing procedure for a single filing request: S1. Users submit a filing application on the online platform and select the Jiangsu Administration Bureau as the target authority.

[0036] S2: The system retrieves the interface metadata of Jiangsu Administration from the configuration center, including protocol type, data format, field dictionary, authentication configuration, error code mapping rules and call constraints, and loads the corresponding version.

[0037] S3, the dynamic field mapping engine loads mapping rules; if it is the first access or a field change is detected, the semantic recognition module is started to perform field matching, generate candidate mappings and form an executable mapping table.

[0038] S4, the authentication policy adaptive module selects the digital certificate method for identity authentication according to the configuration; if an authentication failure response is received, it switches the authentication plugin or triggers a refresh process based on the response type.

[0039] S5, the API call strategy engine sets timeout and retry parameters for this request based on historical call behavior, and executes rate limiting or circuit breaking strategies when necessary.

[0040] S6 requests that a timestamp and HMAC signature be added via the security audit gateway, and that sensitive fields be encrypted before being sent to the Jiangsu Administration's interface.

[0041] S7: After receiving the response, the system translates the regulatory error code into a platform-side general description and returns it to the user. At the same time, it writes the full-link log to the audit system for subsequent analysis.

[0042] Example 3: New Authority Access and Rapid Adaptation When it is necessary to add other provincial bureaus, this embodiment can complete the access by adding the interface description and parameter configuration of the bureau in the configuration center, without modifying the deployed docking program; if the fields are significantly different, candidate mappings are given through semantic recognition and the rules are settled through manual confirmation for subsequent reuse.

[0043] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A general dynamic adaptation method for interface interfacing with a filing authority, characterized in that, include: Obtain the target regulatory authority's identifier; Read the interface metadata corresponding to the target authority from the configuration center. The interface metadata includes at least the protocol type, data format, field dictionary, authentication configuration, error code mapping rules, and call constraints. The interface metadata is processed based on a multi-level interface abstraction layer, which includes at least protocol abstraction, data format abstraction and semantic abstraction, so as to convert the unified semantic model on the business side into the target interface request and the target interface response into the unified semantic model. The dynamic field mapping engine is invoked to map the fields of the unified semantic model to the target fields in the field dictionary. Rule mapping is preferred, and when rules are missing or fields do not match, semantic recognition is used to generate candidate mappings and form executable mappings. The authentication strategy adaptive module is invoked to assemble authentication information according to the authentication configuration, and the authentication method is switched when an authentication failure response is detected. The API call strategy engine adjusts timeouts, retry rates, and frequencies based on historical call data and executes rate limiting or circuit breaking strategies. The request is sent to the target regulatory authority's interface after being timestamped and HMAC-signed by the security audit gateway and sensitive data is encrypted. Upon receiving the response, output the general processing result according to the error code mapping rules and record the full-link log.

2. The method according to claim 1, characterized in that, The dynamic field mapping engine supports manual feedback calibration and writes the manually confirmed mapping relationship back to the configuration center to form mapping rules; when a change in the target regulatory authority interface version is detected, the mapping rules associated with that interface version are loaded first.

3. The method according to claim 1, characterized in that, The interface call strategy engine dynamically adjusts at least one call parameter based on historical call data. The call parameters include call frequency, timeout, number of retries, and concurrency limit. When the failure rate or timeout rate threshold is met, rate limiting, circuit breaking, or degradation strategies are executed. The degradation strategy includes writing the request to a queue for subsequent submission.

4. A universal dynamic adaptation system for interface interfacing with the filing and registration authority, characterized in that, include: Multi-level interface abstraction layer, dynamic field mapping engine, authentication policy adaptive module, interface call strategy engine, security audit gateway, distributed interface gateway cluster, and configuration center; The configuration center is used to store and distribute interface metadata corresponding to the target authority. The multi-level interface abstraction layer is used to perform protocol abstraction, data format abstraction, and semantic abstraction. The dynamic field mapping engine is used to switch between rule mapping and semantic recognition to generate executable mappings; The authentication strategy adaptive module is used to assemble authentication information and switch authentication methods when authentication fails. The interface call strategy engine is used to dynamically adjust call parameters and execute rate limiting or circuit breaking strategies. The security audit gateway is used to sign and encrypt outgoing requests and record full-link logs. The distributed interface gateway cluster is used to provide external connection services and supports horizontal scaling and load balancing.

5. The system according to claim 4, characterized in that, The multi-level interface abstraction layer includes a protocol adaptation unit, a format conversion unit, and a semantic conversion unit; the semantic conversion unit is used to perform bidirectional conversion between the unified semantic model and the target regulatory field set.

6. The system according to claim 4, characterized in that, The dynamic field mapping engine includes a rule mapping unit and a semantic recognition unit; the semantic recognition unit is used to generate a candidate mapping list based on the field name or field description text when a rule is missing or a field does not match, and supports updating the rule base of the rule mapping unit after manual confirmation.

7. The system according to claim 4, characterized in that, The interface call strategy engine includes a statistical analysis unit and a strategy execution unit; the statistical analysis unit is used to statistically analyze the call success rate and latency distribution of the target administration bureau; the strategy execution unit is used to adjust timeouts and retries accordingly, and to perform rate limiting, circuit breaking or degradation when thresholds are met.

8. The system according to claim 4, characterized in that, The system supports adding new regulatory agencies by adding their interface metadata, field dictionary, and authentication configuration in the configuration center, thus enabling the system to complete the connection without changing the already deployed docking service program.

9. An electronic device comprising a processor and a memory, wherein the memory stores a computer program, which, when executed by the processor, implements the method of any one of claims 1 to 3.

10. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method of any one of claims 1 to 3.

Images