CN113377369A - Universal method and device for interfacing third-party service system and terminal equipment - Google Patents
Universal method and device for interfacing third-party service system and terminal equipment Download PDFInfo
- Publication number
- CN113377369A CN113377369A CN202110537093.1A CN202110537093A CN113377369A CN 113377369 A CN113377369 A CN 113377369A CN 202110537093 A CN202110537093 A CN 202110537093A CN 113377369 A CN113377369 A CN 113377369A
- Authority
- CN
- China
- Prior art keywords
- parameter
- parameters
- standardized
- docking
- personalized
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Abstract
The invention discloses a universal method and a universal device for docking a third-party service system and terminal equipment. The method comprises the following steps: acquiring a target docking interface of a third-party service system and personalized parameters for docking the target docking interface; according to the parameter matching template corresponding to the target docking interface, determining a standardized parameter for docking the target docking interface, and converting the personalized parameter into the standardized parameter; and generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to the third-party service system, and receiving a docking response returned by the target docking interface. According to the invention, the configured personalized parameters can be automatically converted into the standardized parameters according to the parameter matching templates corresponding to different third-party service system interfaces, technical personnel do not need to repeatedly encode and joint-tune butt joint details such as parameters and authentication modes, the development workload is effectively reduced, and the development, operation and maintenance difficulty of application software is reduced.
Description
Technical Field
The invention relates to the technical field of software development, in particular to a universal method and a universal device for interfacing a third-party service system interface and terminal equipment.
Background
Developing application software in a specific field often requires interfacing with a third-party service system, and taking e-commerce ToB SaaS field as an example, a SaaS service provider provides e-commerce services for an enterprise, and may require interfacing with an existing internal ERP system, an external purchase, sale, inventory system, a logistics system, and the like of the enterprise. The third-party service systems belong to the same field, the provided interfaces are different in size, and although the interface functions of different third-party service systems are approximately the same, the parameters and the authentication modes are different greatly. In the prior art, the overall process of the method for interfacing different third-party service system interfaces is similar, but in terms of specific interfacing details, technical personnel still need to repeatedly perform coding and joint debugging, the development workload is large, and later operation and maintenance are inconvenient, so that a general method for interfacing the third-party service system interfaces is urgently needed.
Disclosure of Invention
The invention provides a universal method, a universal device and terminal equipment for interfacing with a third-party service system interface, which can automatically convert configured personalized parameters into standardized parameters according to parameter matching templates corresponding to different third-party service system interfaces, and do not need technicians to repeatedly encode and jointly adjust parameters, authentication modes and other interfacing details, thereby effectively reducing the development workload and reducing the development, operation and maintenance difficulty of application software.
In order to solve the foregoing technical problem, in a first aspect, an embodiment of the present invention provides a general method for interfacing a third party service system interface, including:
acquiring a target docking interface of a third-party service system and personalized parameters for docking the target docking interface;
according to the parameter matching template corresponding to the target docking interface, determining a standardized parameter for docking the target docking interface, and converting the personalized parameter into the standardized parameter;
and generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to the third-party service system, and receiving a docking response returned by the target docking interface.
Further, the determining a standardized parameter for docking the target docking interface according to the parameter matching template corresponding to the target docking interface specifically includes:
acquiring a parameter matching template corresponding to the target docking interface from a configuration database, and extracting the standardized parameters from the parameter matching template; wherein the standardized parameter is obtained by encapsulating the underlying code of the target docking interface.
Further, the converting the personalized parameters into the standardized parameters specifically includes:
loading a parameter mapping file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter mapping file; wherein, the parameter mapping file comprises the parameter name corresponding relation of the personalized parameter and the standardized parameter.
Further, the converting the personalized parameters into the standardized parameters includes:
loading a parameter configuration file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter configuration file; wherein the parameter configuration file comprises an expression corresponding relation between the personalized parameter and the standardized parameter.
In a second aspect, an embodiment of the present invention provides a general apparatus for interfacing with a third-party service system, including:
the data acquisition module is used for acquiring a target docking interface of a third-party service system and personalized parameters for docking the target docking interface;
the parameter conversion module is used for determining a standardized parameter for butting the target butting interface according to the parameter matching template corresponding to the target butting interface and converting the personalized parameter into the standardized parameter;
and the docking processing module is used for generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to the third-party service system and receiving a docking response returned by the target docking interface.
Further, the determining a standardized parameter for docking the target docking interface according to the parameter matching template corresponding to the target docking interface specifically includes:
acquiring a parameter matching template corresponding to the target docking interface from a configuration database, and extracting the standardized parameters from the parameter matching template; wherein the standardized parameter is obtained by encapsulating the underlying code of the target docking interface.
Further, the converting the personalized parameters into the standardized parameters specifically includes:
loading a parameter mapping file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter mapping file; wherein, the parameter mapping file comprises the parameter name corresponding relation of the personalized parameter and the standardized parameter.
Further, the converting the personalized parameters into the standardized parameters includes:
loading a parameter configuration file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter configuration file; wherein the parameter configuration file comprises an expression corresponding relation between the personalized parameter and the standardized parameter.
In a third aspect, an embodiment of the present invention provides a universal terminal device interfacing with a third party service system, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, where the memory is coupled to the processor, and the processor implements the above-mentioned universal method of interfacing with a third party service system when executing the computer program.
The embodiment of the invention has the following beneficial effects:
the method comprises the steps of obtaining a target docking interface of a third-party service system and personalized parameters of the docking target docking interface, determining standardized parameters of the docking target docking interface according to a parameter matching template corresponding to the target docking interface, converting the personalized parameters into standardized parameters, generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to the third-party service system, receiving a docking response returned by the target docking interface, and completing docking of the third-party service system interface. Compared with the prior art, the embodiment of the invention designs the corresponding parameter matching template aiming at each docking interface of the third-party service system in advance so as to call the parameter matching template corresponding to the target docking interface of the third-party service system when developing the application software, and automatically converts the configured personalized parameters for docking the target docking interface into the standardized parameters in the parameter matching template corresponding to the target docking interface.
Drawings
Fig. 1 is a flowchart illustrating a general method for interfacing a third party service system according to a first embodiment of the present invention;
fig. 2 is a flowchart illustrating a general method for interfacing with a third party service system according to a first embodiment of the present invention;
FIG. 3 is a diagram illustrating a structure of a general device interfacing with a third-party service system according to a second embodiment of the present invention;
fig. 4 is a schematic structural diagram of a universal terminal device interfacing with a third-party service system according to a third embodiment of the present invention.
Detailed Description
The technical solutions in the present invention will be described clearly and completely with reference to the accompanying drawings, and it is obvious that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, the first embodiment provides a general method for interfacing a third party service system, which includes steps S1 to S3:
s1, acquiring a target docking interface of a third-party service system and personalized parameters of the docking target docking interface;
s2, determining the standardized parameters of the target docking interface according to the parameter matching template corresponding to the target docking interface, and converting the personalized parameters into the standardized parameters;
and S3, generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to a third-party service system, and receiving a docking response returned by the target docking interface.
Illustratively, in step S1, when the application software is developed, docking information of the internal system is obtained, where the docking information includes at least a target docking interface of the third-party service system and personalized parameters of the docking target docking interface. And determining a target docking interface of a third-party service system to be docked by the internal system and personalized parameters which are pre-configured in the internal system and are used for docking the target docking interface by acquiring the docking information of the internal system.
In step S2, according to the target docking interface in the docking information, a parameter matching template corresponding to the target docking interface is obtained, a standardized parameter for docking the target docking interface is extracted from the parameter matching template, and the personalized parameter is converted into a standardized parameter. Wherein the parameter matching template is designed for the target docking interface in advance.
In step S3, after the target docking interface and the converted standardized parameters are obtained, based on the interface specification defined by the third-party service system, the target docking interface and the standardized parameters are spliced to generate a docking request, and the docking request is sent to the third-party service system, so that a docking response returned by the target docking interface can be obtained, and the target docking interface of the third-party service system is completed.
In the embodiment, the corresponding parameter matching template is designed aiming at each docking interface of the third-party service system in advance, so that the parameter matching template corresponding to the target docking interface of the third-party service system can be called when application software is developed, the configured personalized parameters for docking the target docking interface are automatically converted into the standardized parameters in the parameter matching template corresponding to the target docking interface, and since the interface functions of different third-party service systems in the same field are basically the same, docking can be realized only by configuring the personalized parameters when the interfaces of other third-party service systems in the same field are docked, technical personnel do not need to repeatedly encode and coordinate docking details such as parameters and authentication modes, the development workload is effectively reduced, and the development, operation and maintenance difficulty of the application software is reduced.
In a preferred embodiment, the determining a standardized parameter of the target docking interface according to the parameter matching template corresponding to the target docking interface specifically includes: acquiring a parameter matching template corresponding to the target docking interface from a configuration database, and extracting standardized parameters from the parameter matching template; wherein the standardized parameters are obtained by encapsulating the underlying code of the target docking interface.
Illustratively, the underlying code of the target docking interface is encapsulated into various standardized parameters through the SaaS platform, and the parameter matching templates are stored in the configuration database after the various standardized parameters are written into the parameter matching templates.
According to the embodiment, the underlying code of the target docking interface is encapsulated into various standardized parameters, the underlying code of the target docking interface can be prevented from being exposed, and the standardized parameters are written into the parameter matching template, so that the parameter matching template can be adapted only by inputting specific parameter values, such as page parameters, report parameters, functional parameters and the like, during subsequent development of application software, and the target docking interface of the third-party service system is completed.
In a preferred embodiment, the converting the personalized parameters into standardized parameters specifically includes: loading a parameter mapping file through a template engine, and converting personalized parameters into standardized parameters according to the parameter mapping file; the parameter mapping file comprises a parameter name corresponding relation between personalized parameters and standardized parameters.
Considering that the parameter names of the personalized parameters pre-configured in the internal system and the standardized parameters of the target docking interface are possibly inconsistent, loading a parameter mapping file through a template engine, and replacing the parameter names of the personalized parameters with the parameter names of the corresponding standardized parameters according to the corresponding relation between the personalized parameters and the parameter names of the standardized parameters in the parameter mapping file, thereby converting the personalized parameters into the standardized parameters. For example, if the parameter name of the personalized parameter is orderId and the parameter name of the corresponding standardized parameter is tid, the content of the parameter mapping file is similar to orderId- > tid.
In the embodiment, the parameter mapping file is loaded through the template engine, and the personalized parameters are directly mapped into the standardized parameters by using the parameter name corresponding relation between the personalized parameters and the standardized parameters in the parameter mapping file, so that the parameter conversion efficiency is improved.
In a preferred embodiment, the converting the personalized parameters into the standardized parameters includes: loading a parameter configuration file through a template engine, and converting personalized parameters into standardized parameters according to the parameter configuration file; the parameter configuration file comprises expression corresponding relations of personalized parameters and standardized parameters.
Considering that part of fields of the standardized parameters of the target docking interface are in an expression form and may not be directly mapped, for the complex and special fields, an interface-level parameter configuration file supporting the expression is additionally set, the parameter configuration file is loaded through a template engine, and the personalized parameters are configured into the standardized parameters containing the complex and special fields according to the expression corresponding relation of the personalized parameters and the standardized parameters in the parameter configuration file, so that the personalized parameters are converted into the standardized parameters.
In the embodiment, the parameter configuration file is loaded through the template engine, and the personalized parameters are configured into the standardized parameters containing complex and special fields by using the expression corresponding relation between the personalized parameters and the standardized parameters in the parameter mapping file, so that the parameter conversion efficiency is improved.
As shown in fig. 2, as an example, in a specific implementation of this embodiment, a specific flow of interfacing the third-party service system is as follows:
1. when application software is developed, an internal system self-defines a JAVA DTO object, wherein the value of the DTO object comprises a target docking interface of a third-party service system to be requested, a configured personalized parameter for docking the target docking interface and an external interface identifier to be accessed;
2. the universal gateway converts the customized JAVA DTO object into a universal Json format, and data in the internal system are in the Json format, so that the internal system does not depend on development languages, and any development language is suitable;
3. extracting a Url and a dynamic parameter list of a target docking interface of a third-party service system to be accessed from a configuration database according to an external interface identifier to be accessed, and converting the Url and the dynamic parameter list into a Json form, wherein the dynamic parameter list is in an expression form, and an expression is required to be converted into a value through a template engine, for example, token parameters of some third-party service system interfaces need to be operated in real time, and the dynamic parameter list is stored in the configuration database in the expression form;
4. transmitting the Json file and the parameter mapping file generated in the step 2 to a template engine, and performing parameter filling by the template engine, wherein the parameter filling is to read the value corresponding to the parameter in the Json file, convert the value and fill the value into a parameter matching template;
5. transmitting the Json file and the parameter mapping file generated in the step 3 to a template engine for parameter filling, wherein the parameter filling is to read out values corresponding to parameters in the Json file, convert the values and fill the values into a parameter matching template;
6. the template engine obtains the Json string filled with the dynamic parameters, wherein the Json string contains all parameters of the internal universal interface and the external interface;
7. reading a parameter mapping file corresponding to a target docking interface of the third-party service system from a configuration database;
8. calculating a parameter list required by a target docking interface of the third-party service system according to the Json file in the step 6 and the parameter mapping file in the step 7, and completing parameter adaptation from an internal interface to an external interface in the step;
9. and splicing the target docking interface and the standardized parameters to generate a docking request, and sending the docking request to the third-party service system to obtain a docking response returned by the target docking interface so as to complete docking of the target docking interface of the third-party service system.
As shown in fig. 3, a second embodiment provides a generic apparatus for interfacing with a third-party service system, including: the data acquisition module 21 is configured to acquire a target docking interface of the third-party service system and personalized parameters of the docking target docking interface; the parameter conversion module 22 is used for determining the standardized parameters of the target docking interface according to the parameter matching template corresponding to the target docking interface and converting the personalized parameters into the standardized parameters; and the docking processing module 23 is configured to generate a docking request according to the target docking interface and the standardized parameter, send the docking request to the third-party service system, and receive a docking response returned by the target docking interface.
Illustratively, by the data obtaining module 21, when the application software is developed, the docking information of the internal system is obtained, and the docking information at least includes the target docking interface of the third-party service system and the personalized parameters of the docking target docking interface. The data obtaining module 21 obtains the docking information of the internal system, and determines a target docking interface of the third-party service system to which the internal system needs to be docked, and personalized parameters pre-configured in the internal system for docking the target docking interface.
Through the parameter conversion module 22, according to the target docking interface in the docking information, a parameter matching template corresponding to the target docking interface is obtained, a standardized parameter for docking the target docking interface is extracted from the parameter matching template, and the personalized parameter is converted into the standardized parameter. Wherein the parameter matching template is designed for the target docking interface in advance.
Through the docking processing module 23, after the target docking interface and the converted standardized parameters are obtained, based on the interface specification defined by the third-party service system, the target docking interface and the standardized parameters are spliced to generate a docking request, and the docking request is sent to the third-party service system, so that a docking response returned by the target docking interface can be obtained, and the target docking interface of the third-party service system is docked.
In the embodiment, the corresponding parameter matching template is designed aiming at each docking interface of the third-party service system in advance, so that the parameter matching template corresponding to the target docking interface of the third-party service system can be called when application software is developed, the configured personalized parameters for docking the target docking interface are automatically converted into the standardized parameters in the parameter matching template corresponding to the target docking interface, and since the interface functions of different third-party service systems in the same field are basically the same, docking can be realized only by configuring the personalized parameters when the interfaces of other third-party service systems in the same field are docked, technical personnel do not need to repeatedly encode and coordinate docking details such as parameters and authentication modes, the development workload is effectively reduced, and the development, operation and maintenance difficulty of the application software is reduced.
In a preferred embodiment, the determining a standardized parameter of the target docking interface according to the parameter matching template corresponding to the target docking interface specifically includes: acquiring a parameter matching template corresponding to the target docking interface from a configuration database, and extracting standardized parameters from the parameter matching template; wherein the standardized parameters are obtained by encapsulating the underlying code of the target docking interface.
Illustratively, the underlying code of the target docking interface is encapsulated into various standardized parameters through the SaaS platform, and the parameter matching templates are stored in the configuration database after the various standardized parameters are written into the parameter matching templates.
According to the embodiment, the underlying code of the target docking interface is encapsulated into various standardized parameters, the underlying code of the target docking interface can be prevented from being exposed, and the standardized parameters are written into the parameter matching template, so that the parameter matching template can be adapted only by inputting specific parameter values, such as page parameters, report parameters, functional parameters and the like, during subsequent development of application software, and the target docking interface of the third-party service system is completed.
In a preferred embodiment, the converting the personalized parameters into standardized parameters specifically includes: loading a parameter mapping file through a template engine, and converting personalized parameters into standardized parameters according to the parameter mapping file; the parameter mapping file comprises a parameter name corresponding relation between personalized parameters and standardized parameters.
Considering that the parameter names of the personalized parameters pre-configured in the internal system and the standardized parameters of the target docking interface may not be consistent, the parameter conversion module 22 loads the parameter mapping file by using the template engine, and according to the corresponding relationship between the parameter names of the personalized parameters and the standardized parameters in the parameter mapping file, the parameter names of the personalized parameters are replaced by the parameter names of the corresponding standardized parameters, so that the personalized parameters are converted into the standardized parameters. For example, if the parameter name of the personalized parameter is orderId and the parameter name of the corresponding standardized parameter is tid, the content of the parameter mapping file is similar to orderId- > tid.
In this embodiment, the parameter conversion module 22 loads the parameter mapping file by using the template engine, and directly maps the personalized parameter into the standardized parameter by using the parameter name corresponding relationship between the personalized parameter and the standardized parameter in the parameter mapping file, which is beneficial to improving the parameter conversion efficiency.
In a preferred embodiment, the converting the personalized parameters into the standardized parameters includes: loading a parameter configuration file through a template engine, and converting personalized parameters into standardized parameters according to the parameter configuration file; the parameter configuration file comprises expression corresponding relations of personalized parameters and standardized parameters.
Considering that some fields of the standardized parameters of the target docking interface are in an expression form and may not be directly mapped, for these complex and special fields, an interface-level parameter configuration file supporting an expression is additionally set, the parameter configuration file is loaded by using the template engine through the parameter conversion module 22, and the personalized parameters are configured into the standardized parameters containing the complex and special fields according to the expression corresponding relation between the personalized parameters and the standardized parameters in the parameter configuration file, so that the personalized parameters are converted into the standardized parameters.
In this embodiment, the parameter conversion module 22 loads the parameter configuration file by using the template engine, and configures the personalized parameters into the standardized parameters containing complex and special fields by using the expression corresponding relationship between the personalized parameters and the standardized parameters in the parameter mapping file, which is beneficial to improving the parameter conversion efficiency.
As shown in fig. 4, the third embodiment provides a universal terminal device interfacing with a third party service system, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, where the memory is coupled to the processor, and the processor executes the computer program to implement the universal method interfacing with the third party service system according to the first embodiment, which achieves the same advantages.
In summary, the embodiments of the present invention have the following beneficial effects:
the method comprises the steps of obtaining a target docking interface of a third-party service system and personalized parameters of the docking target docking interface, determining standardized parameters of the docking target docking interface according to a parameter matching template corresponding to the target docking interface, converting the personalized parameters into standardized parameters, generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to the third-party service system, receiving a docking response returned by the target docking interface, and completing docking of the third-party service system interface. According to the embodiment of the invention, the corresponding parameter matching template is designed aiming at each docking interface of the third-party service system in advance, so that the parameter matching template corresponding to the target docking interface of the third-party service system can be called when application software is developed, the configured personalized parameters for docking the target docking interface are automatically converted into the standardized parameters in the parameter matching template corresponding to the target docking interface, and since the interface functions of different third-party service systems in the same field are basically the same, docking can be realized only by configuring the personalized parameters when the interfaces of other third-party service systems in the same field are docked, technical personnel do not need to repeatedly encode and coordinate docking details such as parameters and authentication modes, the development workload is effectively reduced, and the development, operation and maintenance difficulty of the application software is reduced.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
It will be understood by those skilled in the art that all or part of the processes of the above embodiments may be implemented by hardware related to instructions of a computer program, and the computer program may be stored in a computer readable storage medium, and when executed, may include the processes of the above embodiments. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
Claims (9)
1. A universal method for interfacing to a third party services system, comprising:
acquiring a target docking interface of a third-party service system and personalized parameters for docking the target docking interface;
according to the parameter matching template corresponding to the target docking interface, determining a standardized parameter for docking the target docking interface, and converting the personalized parameter into the standardized parameter;
and generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to the third-party service system, and receiving a docking response returned by the target docking interface.
2. The universal method for interfacing a third-party service system interface according to claim 1, wherein the determining standardized parameters for interfacing the target docking interface according to the parameter matching template corresponding to the target docking interface specifically comprises:
acquiring a parameter matching template corresponding to the target docking interface from a configuration database, and extracting the standardized parameters from the parameter matching template; wherein the standardized parameter is obtained by encapsulating the underlying code of the target docking interface.
3. The universal method for interfacing a third party service system according to claim 1, wherein said converting said personalized parameters into said standardized parameters comprises:
loading a parameter mapping file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter mapping file; wherein, the parameter mapping file comprises the parameter name corresponding relation of the personalized parameter and the standardized parameter.
4. The universal method for interfacing a third party services system according to claim 1 or 3, wherein said translating said personalized parameters into said standardized parameters comprises:
loading a parameter configuration file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter configuration file; wherein the parameter configuration file comprises an expression corresponding relation between the personalized parameter and the standardized parameter.
5. A generic device for interfacing with a third party services system, comprising:
the data acquisition module is used for acquiring a target docking interface of a third-party service system and personalized parameters for docking the target docking interface;
the parameter conversion module is used for determining a standardized parameter for butting the target butting interface according to the parameter matching template corresponding to the target butting interface and converting the personalized parameter into the standardized parameter;
and the docking processing module is used for generating a docking request according to the target docking interface and the standardized parameters, sending the docking request to the third-party service system and receiving a docking response returned by the target docking interface.
6. The universal device for interfacing a third-party service system interface according to claim 5, wherein the determining standardized parameters for interfacing the target docking interface according to the parameter matching template corresponding to the target docking interface specifically comprises:
acquiring a parameter matching template corresponding to the target docking interface from a configuration database, and extracting the standardized parameters from the parameter matching template; wherein the standardized parameter is obtained by encapsulating the underlying code of the target docking interface.
7. The generic device of claim 5, wherein the conversion of the personalized parameters into the standardized parameters is specifically:
loading a parameter mapping file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter mapping file; wherein, the parameter mapping file comprises the parameter name corresponding relation of the personalized parameter and the standardized parameter.
8. The universal method for interfacing a third party services system according to claim 5 or 7, wherein said translating said personalized parameters into said standardized parameters comprises:
loading a parameter configuration file through a template engine, and converting the personalized parameters into the standardized parameters according to the parameter configuration file; wherein the parameter configuration file comprises an expression corresponding relation between the personalized parameter and the standardized parameter.
9. A universal terminal device interfacing with a third party services system, comprising a processor, a memory and a computer program stored in the memory and configured to be executed by the processor, the memory being coupled to the processor and the processor implementing the universal method interfacing with a third party services system as claimed in any one of claims 1 to 4 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110537093.1A CN113377369A (en) | 2021-05-17 | 2021-05-17 | Universal method and device for interfacing third-party service system and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110537093.1A CN113377369A (en) | 2021-05-17 | 2021-05-17 | Universal method and device for interfacing third-party service system and terminal equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113377369A true CN113377369A (en) | 2021-09-10 |
Family
ID=77571201
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110537093.1A Pending CN113377369A (en) | 2021-05-17 | 2021-05-17 | Universal method and device for interfacing third-party service system and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113377369A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115174650A (en) * | 2022-09-06 | 2022-10-11 | 深圳领筑科技有限公司 | Open service platform, service response method, device, equipment and storage medium |
| CN115242872A (en) * | 2022-06-24 | 2022-10-25 | 平安银行股份有限公司 | Data processing method and device, computer equipment and readable storage medium |
| CN115934177A (en) * | 2022-05-24 | 2023-04-07 | 北京有限元科技有限公司 | Dynamic docking method and device for storage service, electronic equipment and medium |
| CN117033032A (en) * | 2023-09-28 | 2023-11-10 | 北京谷器数据科技有限公司 | Platform for automatically analyzing and calling third-party service interface |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111064708A (en) * | 2019-11-25 | 2020-04-24 | 精硕科技（北京）股份有限公司 | Authorization authentication configuration method, authorization authentication device and electronic equipment |
| CN112153152A (en) * | 2020-09-28 | 2020-12-29 | 深圳壹账通智能科技有限公司 | Management method and system of algorithm service interface |
| CN112199079A (en) * | 2020-12-07 | 2021-01-08 | 震坤行网络技术(南京)有限公司 | System docking method, computing device and storage medium |
| CN112287009A (en) * | 2020-11-03 | 2021-01-29 | 平安普惠企业管理有限公司 | Interface calling and interface data warehousing method, device, equipment and storage medium |
-
2021
- 2021-05-17 CN CN202110537093.1A patent/CN113377369A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111064708A (en) * | 2019-11-25 | 2020-04-24 | 精硕科技（北京）股份有限公司 | Authorization authentication configuration method, authorization authentication device and electronic equipment |
| CN112153152A (en) * | 2020-09-28 | 2020-12-29 | 深圳壹账通智能科技有限公司 | Management method and system of algorithm service interface |
| CN112287009A (en) * | 2020-11-03 | 2021-01-29 | 平安普惠企业管理有限公司 | Interface calling and interface data warehousing method, device, equipment and storage medium |
| CN112199079A (en) * | 2020-12-07 | 2021-01-08 | 震坤行网络技术(南京)有限公司 | System docking method, computing device and storage medium |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115934177A (en) * | 2022-05-24 | 2023-04-07 | 北京有限元科技有限公司 | Dynamic docking method and device for storage service, electronic equipment and medium |
| CN115934177B (en) * | 2022-05-24 | 2023-08-18 | 北京有限元科技有限公司 | Dynamic docking method and device for storage service, electronic equipment and medium |
| CN115242872A (en) * | 2022-06-24 | 2022-10-25 | 平安银行股份有限公司 | Data processing method and device, computer equipment and readable storage medium |
| CN115242872B (en) * | 2022-06-24 | 2024-02-02 | 平安银行股份有限公司 | Data processing method, device, computer equipment and readable storage medium |
| CN115174650A (en) * | 2022-09-06 | 2022-10-11 | 深圳领筑科技有限公司 | Open service platform, service response method, device, equipment and storage medium |
| CN115174650B (en) * | 2022-09-06 | 2022-12-06 | 深圳领筑科技有限公司 | Open service platform, service response method, device, equipment and storage medium |
| CN117033032A (en) * | 2023-09-28 | 2023-11-10 | 北京谷器数据科技有限公司 | Platform for automatically analyzing and calling third-party service interface |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113377369A (en) | Universal method and device for interfacing third-party service system and terminal equipment | |
| US7734583B2 (en) | Transparent virtual machine for mobile applications | |
| CN112835782B (en) | Interface access test method and system | |
| CN110806945A (en) | Interface docking method, device and computer readable medium | |
| CN113225379A (en) | Method and device for sending HTTP request message | |
| CN109491802A (en) | A kind of method and adapter of the RESTFul network request based on Unity | |
| US20090319985A1 (en) | Method, system and apparatus for acquiring interface | |
| CN107357792B (en) | Data analysis method and device | |
| CN114745449B (en) | Message processing method and device, storage medium and electronic equipment | |
| US10289462B1 (en) | Systems and methods for integration of websphere optimized local adapters with the spring framework | |
| CN109816462A (en) | A kind of recognition methods of invoice information and device | |
| CN114281341A (en) | Compiling method and device of data structure definition file, computer equipment and medium | |
| CN114925120A (en) | Insurance business information query method and related equipment | |
| CN111158661A (en) | System interface docking method, device, medium and electronic equipment | |
| CN109376023B (en) | Method and equipment for generating calling information and issuing return code group | |
| CN115618396B (en) | Data encryption method and device | |
| CN114116067B (en) | Information configuration method and device for internal and external systems, electronic equipment and readable storage medium | |
| CN113364636B (en) | Visual configuration docking method for data of Internet of things | |
| CN115373655B (en) | Information protocol code automatic generation method based on standardized template | |
| CN114116520B (en) | Algorithm evaluation method, device, gateway and storage medium | |
| CN112764763B (en) | Code conversion method, system, equipment and computer readable storage medium | |
| CN117492744A (en) | Automatic docking and analyzing method and system for SOAP interface | |
| CN109857404B (en) | SDK interface packaging method and device, storage medium and electronic equipment | |
| CN112379926A (en) | Business system diagnosis method, system and related product | |
| CN111857792A (en) | Method and equipment for configuring system docking instance |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210910 |
|
| RJ01 | Rejection of invention patent application after publication |