DSL-based interface communication method and device, and storage medium

Abstract

The invention provides a DSL-based interface communication method and device, and a storage medium. The method comprises the following steps: receiving a first request sent by a first system; calling a configuration resource corresponding to the first request to process the first request to obtain a second request, and sending the second request to a second system; receiving a first processing result sent by the second system in response to the second request; in response to the first request, sending a second processing result to the first system; the second processing result is generated based on the first processing result and the configuration resource. In the embodiment of the invention, the interface communication device based on the DSL technology realizes interface collaboration among multiple systems, and completes unified and effective centralized support through unified access and return of the interface information, thereby eliminating interface heterogeneity, forming unified and effective centralized support, improving the development efficiency and reusability of interface communication among the multiple systems, and improving the user experience. And the development cost is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a DSL-based interface communication method, device and storage medium. Background Art

[0002] It should be noted that each independent system has multiple interfaces for communicating with the outside world. In order to complete data interaction, information sharing and collaborative work among multiple independent systems, it is necessary to call the interfaces between the systems in a point-to-point manner.

[0003] However, as the application systems support more businesses, the systems continue to iterate and evolve, and the technology evolves, the interface relationships between application systems have also become complex, resulting in low efficiency in the development of communication systems between interfaces among multiple systems, and the inability to form a unified and effective centralized support, which will lead to duplicate construction between different systems, poor reusability, and high development costs. Summary of the invention

[0004] The main purpose of this application is to provide a DSL-based interface communication method, device and storage medium, aiming to solve the technical problems of low development efficiency of communication systems between interfaces among multiple systems, inability to form a unified and effective centralized support, resulting in repeated construction between different systems, poor reusability and high development costs.

[0005] To achieve the above object, the present application provides a DSL-based interface communication method, the method comprising: receiving a first request sent by a first system; Calling the configuration resource corresponding to the first request to process the first request to obtain a second request, and sending the second request to the second system; receiving a first processing result sent by the second system in response to the second request; In response to the first request, a second processing result is sent to the first system; the second processing result is generated based on the first processing result and the configuration resource.

[0006] Optionally, before calling the configuration resource corresponding to the first request to process the first request to obtain the second request, the method further includes: Obtaining a request type of the first request; Parsing the first request based on the request type of the first request to obtain configuration information corresponding to the first request; Determining whether the configuration resource represented by the configuration information can be called; In the case where the configuration resource can be called, the step of calling the configuration resource corresponding to the first request to process the first request to obtain a second request is executed.

[0007] Optionally, the calling a configuration resource corresponding to the first request to process the first request to obtain a second request includes: Calling the configuration resource to authenticate the first request; If the authentication is successful, determining whether the network protocol of the first request is a supported network protocol; In a case where the network protocol corresponding to the first request is a supported network protocol, determining whether a format of the first request is a supported request format; In a case where the format of the first request is a supported request format, determining the first request as a second request; When the format of the first request is not a supported request format, the format of the first request is adjusted to a supported request format to obtain a second request.

[0008] Optionally, after determining whether the configuration resource represented by the configuration information can be called, the method further includes: In a case where the configuration resource cannot be called, generating first monitoring information according to a transmission path of the first request, and generating a first log according to the first request and the configuration resource; The first monitoring information and the first log are stored.

[0009] Optionally, before sending the second request to the second system, the method further includes: generating second monitoring information according to a generation path of the second request, and generating a second log according to the second request and the configuration resource; The second monitoring information and the second log are stored.

[0010] Optionally, before sending the second processing result to the first system in response to the first request, the method further includes: generating third monitoring information according to the transmission path of the second processing result, and generating a third log according to the second processing result and the configuration resource; The third monitoring information and the third log are stored.

[0011] In addition, to achieve the above-mentioned purpose, the present application also provides an interface communication device, the interface communication device comprising: A request processing module, configured to receive a first request sent by a first system; Calling the configuration resource corresponding to the first request to process the first request to obtain a second request, and sending the second request to the second system; receiving a first processing result sent by the second system in response to the second request; In response to the first request, a second processing result is sent to the first system; the second processing result is generated based on the first processing result and the configuration resource.

[0012] Optionally, the request processing module is further used to: Obtaining a request type of the first request; The device further includes a basic module, and the basic module is used to parse the first request based on the request type of the first request to obtain configuration information corresponding to the first request; The request processing module is further used to determine whether the configuration resource represented by the configuration information can be called; In the case where the configuration resource can be called, the step of calling the configuration resource corresponding to the first request to process the first request to obtain a second request is executed.

[0013] Optionally, the device further includes an information management module, and the information management module is used to call the configuration resource; The request processing module is further used to authenticate the first request; If the authentication is successful, determining whether the network protocol of the first request is a supported network protocol; In a case where the network protocol corresponding to the first request is a supported network protocol, determining whether a format of the first request is a supported request format; In a case where the format of the first request is a supported request format, determining the first request as a second request; When the format of the first request is not a supported request format, the format of the first request is adjusted to a supported request format to obtain a second request.

[0014] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution: The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of any one of the DSL-based interface communication methods proposed in the embodiments of the present application are implemented.

[0015] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution: The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the steps of any one of the DSL-based interface communication methods proposed in the embodiments of the present application are implemented.

[0016] Compared with the prior art, the embodiments of the present application have the following beneficial effects: The present application provides a DSL-based interface communication method, device and storage medium, the method comprising: receiving a first request sent by a first system; calling the configuration resource corresponding to the first request to process the first request to obtain a second request, and sending the second request to the second system; receiving a first processing result sent by the second system in response to the second request; sending the second processing result to the first system in response to the first request; the second processing result is generated based on the first processing result and the configuration resource. In an embodiment of the present application, a first request sent by a first system is received, a second request is generated after processing the first request, and the second request is sent to the second system to obtain a first processing result fed back by the second system, and then the second processing result generated based on the first processing result is sent to the first system; in this way, the interface communication device based on DSL technology realizes the interface collaboration between multiple systems, completes unified and effective centralized support by unified access and return of interface information, thereby eliminating interface heterogeneity, forming a unified and effective centralized support, improving the development efficiency and reusability of each interface communication between multiple systems, and reducing development costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 is an exemplary system architecture diagram to which the present application may be applied; Figure 2 It is a schematic diagram of multi-system interface communication in the prior art; Figure 3 is a flow chart of a DSL-based interface communication method provided in an embodiment of the present application; Figure 4 It is a schematic diagram of multi-system interface communication in the DSL-based interface communication method provided in an embodiment of the present application; Figure 5 is an application flow chart of a DSL-based interface communication method provided in an embodiment of the present application; Figure 6 It is a structural diagram of an embodiment of an interface communication device provided in an embodiment of the present application; Figure 7 It is a basic structural block diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0019] The DSL-based interface communication method provided in the embodiment of the present application is applied to the interface communication device. Unless otherwise defined, all technical and scientific terms used in this document have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" in the specification and claims of the present application and the above-mentioned drawings and any variations thereof are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0020] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0021] 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 accompanying drawings.

[0022] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0023] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social online platform software, etc.

[0024] Terminal devices 101, 102, 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 (Moving Picture Experts Group Audio Layer IV), laptop computers, desktop computers, etc.

[0025] The server 105 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal devices 101 , 102 , and 103 .

[0026] It should be noted that the DSL-based interface communication method provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the interface communication device is generally arranged in the server / terminal device.

[0027] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0028] See also Figure 2 , Figure 2 It is a schematic diagram of multi-system interface communication in the prior art, such as Figure 2 As shown in the figure, the interface communication of each system adopts a point-to-point mode, which has the following problems: 1. As the application system supports more businesses, the calling relationships between systems become complex, the interfaces are heterogeneous, and data processing is hard-coded, which leads to longer development, testing, and joint debugging time and high maintenance costs.

[0029] 2. The application systems are connected and coordinated in a point-to-point manner, which cannot form a unified and effective centralized support, and cannot uniformly implement interface restriction strategies to ensure system security. It has poor scalability, will lead to duplicate construction between different systems, poor reusability, and high costs.

[0030] 3. The application system interfaces are coordinated, but lack the ability to trace complete interface execution information. Problems cannot be discovered proactively, and the propagation of faults cannot be effectively controlled. Potential performance bottlenecks of interfaces cannot be proactively analyzed.

[0031] In order to solve the above-mentioned technical problems, an embodiment of the present application provides an interface communication method, which is based on a custom domain specific language (Domain Specific Language, DSL) technology. Specifically, an interface processing device is generated based on the custom DSL technology, and unified and effective centralized support is completed for interface collaboration between multiple systems through unified access and return of interface information, and the interface integrated media processing device's own specifications are formed, thereby eliminating interface heterogeneity.

[0032] Please refer to Figure 3 , shows a flow chart of an embodiment of a DSL-based interface communication method proposed in the present application. The embodiment of the present application can acquire and process relevant data based on artificial intelligence technology.

[0033] The DSL-based interface communication method provided in the embodiment of the present application includes the following steps: S310: Receive a first request sent by a first system.

[0034] The DSL-based interface communication method proposed in this application can be applied to an interface communication device, such as Figure 4 As shown, the interface communication device communicates with the first system and the second system respectively.

[0035] In an optional application scenario, the first system is an external system.

[0036] In this step, a first request sent by the first system is received.

[0037] S320: Call the configuration resource corresponding to the first request to process the first request to obtain a second request, and send the second request to the second system.

[0038] After receiving the first request, the configuration resource corresponding to the first request is called to process the first request to obtain a second request, and the second request is sent to the second system.

[0039] In an optional application scenario, the second system is an internal system, that is, it belongs to the same system as the interface communication device.

[0040] It should be understood that the above configuration resources involve an access controller, a signature verification controller, a message processor and a protocol controller. Please refer to the subsequent embodiments for specific processing methods.

[0041] S330: Receive a first processing result sent by the second system in response to the second request.

[0042] After receiving the second request, the second system responds to the second request, generates a first processing result, and sends the first processing result to the interface communication device.

[0043] S340: In response to the first request, send a second processing result to the first system; the second processing result is generated based on the first processing result and the configuration resources.

[0044] After receiving the first processing result, the interface communication system generates a second processing result according to the first processing result and the called configuration resources, optionally integrates the first processing result and the configuration resources to obtain the second processing result, and sends the second processing result to the first system.

[0045] In an embodiment of the present application, a first request sent by a first system is received, a second request is generated after processing the first request, and the second request is sent to the second system to obtain a first processing result fed back by the second system, and then a second processing result generated based on the first processing result is sent to the first system; in this way, an interface communication device based on DSL technology realizes interface collaboration between multiple systems, and completes unified and effective centralized support through unified access and return of interface information, thereby eliminating interface heterogeneity, forming a unified and effective centralized support, improving the development efficiency and reusability of interface communications between multiple systems, and reducing development costs.

[0046] Optionally, before calling the configuration resource corresponding to the first request to process the first request to obtain the second request, the method further includes: Obtaining a request type of the first request; Parsing the first request based on the request type of the first request to obtain configuration information corresponding to the first request; Determining whether the configuration resource represented by the configuration information can be called; In the case where the configuration resource can be called, the step of calling the configuration resource corresponding to the first request to process the first request to obtain a second request is executed.

[0047] In this embodiment, after receiving the first request, the request type of the first request is obtained, and according to the request type of the first request, the first request is parsed to obtain configuration information corresponding to the first request.

[0048] It should be understood that for different request types, different tools can be used to parse the requests to obtain corresponding configuration information.

[0049] After obtaining the configuration information, it is determined whether the configuration resource represented by the configuration information can be called. Specifically, it can be checked whether the configuration resource is in a callable state, and it can be checked whether the system in which the interface communication device is embedded has the configuration resource.

[0050] In the case where the configuration resource can be called, the configuration resource is called to process the first request to obtain the second request.

[0051] In this embodiment, when a first request is received, a corresponding configuration resource is called to process the first request, thereby improving the response speed of the request.

[0052] The following specifically describes the process of processing the first request: Optionally, the calling a configuration resource corresponding to the first request to process the first request to obtain a second request includes: Calling the configuration resource to authenticate the first request; If the authentication is successful, determining whether the network protocol of the first request is a supported network protocol; In a case where the network protocol corresponding to the first request is a supported network protocol, determining whether a format of the first request is a supported request format; In a case where the format of the first request is a supported request format, determining the first request as a second request; When the format of the first request is not a supported request format, the format of the first request is adjusted to a supported request format to obtain a second request.

[0053] Calling a configuration resource to authenticate the first request; An optional implementation is to authenticate the first request.

[0054] Another optional implementation is to obtain a signature carried in the first request and authenticate the signature.

[0055] If the authentication is successful, the network protocol of the first request is obtained, and it is determined whether the format of the first request is a supported request format. If the format of the first request is a supported request format, the first request is determined as the second request; if the format of the first request is not a supported request format, the format of the first request is adjusted to a supported request format to obtain a second request.

[0056] Optionally, the above network protocol is HTTP protocol, HTTPS protocol and WS protocol.

[0057] Optionally, the request format is JSON format and XML format.

[0058] In this embodiment, by authenticating the first request and setting the network protocol and request format supported by the second request, a unified and effective centralized support is formed, so that the interface docking has flexible scalability and scalability, supports heterogeneous differences, improves development efficiency, solves the problem of long docking cycle, and improves quality.

[0059] Optionally, after determining whether the configuration resource represented by the configuration information can be called, the method further includes: In a case where the configuration resource cannot be called, generating first monitoring information according to a transmission path of the first request, and generating a first log according to the first request and the configuration resource; The first monitoring information and the first log are stored.

[0060] In this embodiment, when the configuration resource cannot be called, first monitoring information is generated according to the transmission path of the first request, and a first log is generated according to the first request and the configuration resource; and the first monitoring information and the first log are stored.

[0061] In this embodiment, the transmission path of the first request is stored to provide a traceable basis for the transmission path of the first request during the interface communication process, and to provide an optimization basis for analyzing possible performance bottlenecks of the interfaces of multiple systems.

[0062] Optionally, before sending the second request to the second system, the method further includes: generating second monitoring information according to a generation path of the second request, and generating a second log according to the second request and the configuration resource; The second monitoring information and the second log are stored.

[0063] In this embodiment, after the second request is generated, second monitoring information is generated according to the generation path of the second request, a second log is generated according to the second request and the configuration resources, and the second monitoring information and the second log are stored.

[0064] In this embodiment, the generation path of the second request is stored to provide a traceable basis for the generation path of the second request during the interface communication process, and to provide an optimization basis for analyzing possible performance bottlenecks of the interfaces of multiple systems.

[0065] Optionally, before sending the second processing result to the first system in response to the first request, the method further includes: generating third monitoring information according to the transmission path of the second processing result, and generating a third log according to the second processing result and the configuration resource; The third monitoring information and the third log are stored.

[0066] In this embodiment, during the calling process of the second processing result, third monitoring information is generated according to the transmission path of the second processing result, and a third log is generated according to the second processing result and the configuration resources, and the third monitoring information and the third log are stored.

[0067] In this embodiment, the transmission path of the second processing result is stored to provide a traceable basis for the transmission path of the second processing result during the interface communication process, and to provide an optimization basis for analyzing possible performance bottlenecks of the interfaces of multiple systems.

[0068] To understand the overall technical solution provided by the above embodiment, please refer to Figure 5 , Figure 5 The “external system” in the embodiment is the first system in the present application. Figure 5 The "internal application system" in the embodiment of the present application is the second system. Figure 5 The “HTTP processing engine” in the embodiment of the present application is the request processing module. Figure 5 The "interface information management" in the embodiment of the present application is the information management module, and the module Figure 5 The “operation and maintenance management” in the embodiment of the present application refers to the operation and maintenance module. Figure 5 The “basic module” in the embodiment of the present application is the basic module. Figure 5 The “component storage” in the embodiment of the present application refers to the storage module. pass Figure 5 The application flow chart shown forms a complete request processing flow of the interface communication device.

[0069] See also Figure 6 , an interface communication device 600 provided in an embodiment of the present application, the interface communication device 600 includes: The request processing module 610 is used to receive a first request sent by a first system; Calling the configuration resource corresponding to the first request to process the first request to obtain a second request, and sending the second request to the second system; receiving a first processing result sent by the second system in response to the second request; In response to the first request, a second processing result is sent to the first system; the second processing result is generated based on the first processing result and the configuration resource.

[0070] The interface communication device 600 provided in the embodiment of the present application is independently deployed between the first system and the second system, and data exchange between the first system and the second system is all through the interface communication device 600.

[0071] The interface format of the second system is supported to be converted into the interface format of the first system. The format agreed upon between the second system is the JSON format that complies with RESTful. The interface format of the first system is based on the agreement between the two parties, and optionally supports the JSON format or the XML format.

[0072] When sending interface data to the first system, there is usually a requirement for authentication and authorization, and the authentication and authorization method may be OAUTH2.0, or an authentication method customized by the first system.

[0073] When sending interface data to the first system, according to the requirements of the first system, the interface data needs to be encrypted, and the encryption algorithm is agreed upon by both parties.

[0074] In order to prevent data transmission from being tampered with, the interface data content must be signed.

[0075] Expose a unified entrance to the outside world for the first system to call.

[0076] Externally exposed entrances require necessary authentication to prevent illegal requests.

[0077] Provide a unified data encryption and signature verification method to the first system. When the first system calls the interface, it needs to follow the encryption protocol and signature method.

[0078] When receiving the interface access from the first system, it is converted into a recognizable format according to the interface format agreed upon by both parties.

[0079] The presentation layer of the interface communication device 600 provides a user interface in a page manner, with VUE used on the front end and Spring Boot framework used on the back end.

[0080] The business logic layer of the interface communication device 600 adopts Spring declarative transaction management.

[0081] The data persistence layer of the interface communication device 600 adopts the MyBatis object / relational mapping framework.

[0082] The interface communication device 600 uses the MySQL database for data storage.

[0083] The cache of the interface communication device 600 uses the distributed cache system Redis.

[0084] The interface communication device 600 uses the distributed messaging system Kafka to meet the high-throughput processing of logs.

[0085] Optionally, the request processing module 610 is further configured to: Obtaining a request type of the first request; See also Figure 6 , the interface communication device 600 further includes a basic module 620, and the basic module 620 is used to parse the first request based on the request type of the first request to obtain configuration information corresponding to the first request; The request processing module 610 is further used to determine whether the configuration resource represented by the configuration information can be called; In the case where the configuration resource can be called, the step of calling the configuration resource corresponding to the first request to process the first request to obtain a second request is executed.

[0086] See also Figure 6 Optionally, the interface communication device 600 further includes an information management module 630, and the information management module 630 is used to call the configuration resource; The request processing module 610 is further configured to authenticate the first request; If the authentication is successful, determining whether the network protocol of the first request is a supported network protocol; In a case where the network protocol corresponding to the first request is a supported network protocol, determining whether a format of the first request is a supported request format; In a case where the format of the first request is a supported request format, determining the first request as a second request; When the format of the first request is not a supported request format, the format of the first request is adjusted to a supported request format to obtain a second request.

[0087] See also Figure 6 Optionally, the interface communication device 600 further includes an operation and maintenance module 640, wherein the operation and maintenance module 640 is configured to generate first monitoring information according to the transmission path of the first request and generate a first log according to the first request and the configuration resource when the configuration resource cannot be called; See also Figure 6 Optionally, the interface communication device 600 further includes a storage module 650, and the storage module 650 is used to store the first monitoring information and the first log.

[0088] Optionally, the operation and maintenance module 640 is specifically configured to generate second monitoring information according to a generation path of the second request, and generate a second log according to the second request and the configuration resource; Optionally, the storage module 650 is specifically used to store the second monitoring information and the second log.

[0089] Optionally, the operation and maintenance module 640 is further specifically configured to generate third monitoring information according to a transmission path of the second processing result, and generate a third log according to the second processing result and the configuration resource; Optionally, the storage module 650 is further specifically used to store the third monitoring information and the third log.

[0090] To solve the above technical problems, the present application also provides a computer device. Figure 7 , Figure 7 This is a basic structural block diagram of the computer device in this embodiment. The computer device 7 includes a memory 71, a processor 72, and a network interface 73 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 7 with components 71-73, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0091] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0092] The memory 71 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 71 can be an internal storage unit of the computer device 7, such as a hard disk or memory of the computer device 7. In other embodiments, the memory 71 can also be an external storage device of the computer device 7, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), etc. equipped on the computer device 7. Of course, the memory 71 can also include both the internal storage unit of the computer device 7 and its external storage device. In this embodiment, the memory 71 is generally used to store the operating system and various application software installed on the computer device 7, such as the program code of the interface communication method based on DSL, etc. In addition, the memory 71 can also be used to temporarily store various types of data that have been output or are to be output.

[0093] The processor 72 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 72 is generally used to control the overall operation of the computer device 7. In this embodiment, the processor 72 is used to run the program code stored in the memory 71 or process data, such as running the program code of the DSL-based interface communication method.

[0094] The network interface 73 may include a wireless network interface or a wired network interface. The network interface 73 is generally used to establish a communication connection between the computer device 7 and other electronic devices.

[0095] The present application also provides another implementation, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores the interface communication program, and the interface communication program can be executed by at least one processor to enable the at least one processor to perform the steps of the DSL-based interface communication method as described above.

[0096] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware online platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0097] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0098] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A DSL-based interface communication method, characterized in that: include: receiving a first request sent by a first system; Calling the configuration resource corresponding to the first request to process the first request to obtain a second request, and sending the second request to the second system; receiving a first processing result sent by the second system in response to the second request; In response to the first request, sending a second processing result to the first system; The second processing result is generated based on the first processing result and the configuration resource.

2. The method according to claim 1, characterized in that Before calling the configuration resource corresponding to the first request to process the first request to obtain the second request, the method further includes: Obtaining a request type of the first request; Parsing the first request based on the request type of the first request to obtain configuration information corresponding to the first request; Determining whether the configuration resource represented by the configuration information can be called; In the case where the configuration resource can be called, the step of calling the configuration resource corresponding to the first request to process the first request to obtain a second request is executed.

3. The method according to claim 1, characterized in that The calling of the configuration resource corresponding to the first request to process the first request to obtain the second request includes: Calling the configuration resource to authenticate the first request; If the authentication is successful, determining whether the network protocol of the first request is a supported network protocol; In a case where the network protocol corresponding to the first request is a supported network protocol, determining whether a format of the first request is a supported request format; In a case where the format of the first request is a supported request format, determining the first request as a second request; When the format of the first request is not a supported request format, the format of the first request is adjusted to a supported request format to obtain a second request.

4. The method according to claim 2, characterized in that: After determining whether the configuration resource represented by the configuration information can be called, the method further includes: In a case where the configuration resource cannot be called, generating first monitoring information according to a transmission path of the first request, and generating a first log according to the first request and the configuration resource; The first monitoring information and the first log are stored.

5. The method according to claim 1, characterized in that Before sending the second request to the second system, the method further includes: generating second monitoring information according to a generation path of the second request, and generating a second log according to the second request and the configuration resource; The second monitoring information and the second log are stored.

6. The method according to claim 1, characterized in that Before sending the second processing result to the first system in response to the first request, the method further includes: generating third monitoring information according to the transmission path of the second processing result, and generating a third log according to the second processing result and the configuration resource; The third monitoring information and the third log are stored.

7. An interface communication device, characterized in that: include: A request processing module, configured to receive a first request sent by a first system; Calling the configuration resource corresponding to the first request to process the first request to obtain a second request, and sending the second request to the second system; receiving a first processing result sent by the second system in response to the second request; In response to the first request, sending a second processing result to the first system; The second processing result is generated based on the first processing result and the configuration resource.

8. The device according to claim 7, characterized in that The request processing module is further used for: Obtaining a request type of the first request; The device further includes a basic module, and the basic module is used to parse the first request based on the request type of the first request to obtain configuration information corresponding to the first request; The request processing module is further used to determine whether the configuration resource represented by the configuration information can be called; In the case where the configuration resource can be called, the step of calling the configuration resource corresponding to the first request to process the first request to obtain a second request is executed.

9. The device according to claim 7, characterized in that The device also includes an information management module, and the information management module is used to call the configuration resource; The request processing module is further used to authenticate the first request; If the authentication is successful, determining whether the network protocol of the first request is a supported network protocol; In a case where the network protocol corresponding to the first request is a supported network protocol, determining whether a format of the first request is a supported request format; In a case where the format of the first request is a supported request format, determining the first request as a second request; When the format of the first request is not a supported request format, the format of the first request is adjusted to a supported request format to obtain a second request.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the interface communication method according to any one of claims 1 to 6 are implemented.

Images