CN113626223A

CN113626223A - Interface calling method and device

Info

Publication number: CN113626223A
Application number: CN202110924106.0A
Authority: CN
Inventors: 刘春和
Original assignee: Beijing Jingdong Zhenshi Information Technology Co Ltd
Current assignee: Beijing Jingdong Zhenshi Information Technology Co Ltd
Priority date: 2021-08-12
Filing date: 2021-08-12
Publication date: 2021-11-09

Abstract

The invention discloses an interface calling method and device, and relates to the technical field of computers. One embodiment of the method comprises: receiving a mapping request sent by a first application interface, calling a mapping model corresponding to a service code specified in the mapping request according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises a parameter field of the first application interface, the target object comprises a parameter field of a second application interface, inputting the parameter field of the first application interface into the mapping model, outputting the parameter field value of the second application interface, and returning the parameter field value of the second application interface to the first application interface so that the first application interface calls the second application interface. The implementation mode can overcome the defect that the efficiency of a hard coding mode is extremely low, reduce the development cost, realize the mapping of dynamic parameters to downstream and solve the problems of high construction cost, high requirement on technical personnel and inconsistent service execution of the current automatic service.

Description

Interface calling method and device

Technical Field

The invention relates to the technical field of computers, in particular to an interface calling method and device.

Background

Currently, a B2C (business to consumer) service is ordering through a specific interface or ordering through a merchant end, the architecture is from application a to downstream application B, parameter mapping is required before application a calls an interface of application B, for example, after application a receives an order, ordering to application B may need to be converted into a field of application B, assuming that the field format of application a is cardType: 1; deliveryType 2; if the field format corresponding to the application B is of a map type, the value of cardType in the field of the application A needs to be assigned to a certain key in the corresponding field of the application B; it may also be necessary to perform a field-pass-through, e.g. to pass through the value of a field of application a into the same name field of downstream application B, or the value of a field of application a is 1, 2, 3, 4, 5 and the value of another field corresponding to downstream application B is T0001, T0002, T0003. For the above situation, the code is developed each time, the code is written from top to bottom, and finally assigned to the downstream import parameter DTO (data transfer object).

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:

the hard coding mode has extremely low efficiency and high requirement on technical personnel.

Disclosure of Invention

In view of this, embodiments of the present invention provide an interface calling method and apparatus, which can overcome the defect of extremely low efficiency of a hard coding method, shorten a development period, reduce development cost, implement mapping of dynamic parameters to downstream, and solve the problems of high construction cost, high requirement on technicians, and inconsistent service execution of the current automated service.

To achieve the above object, according to an aspect of an embodiment of the present invention, an interface calling method is provided.

An interface calling method, comprising: receiving a mapping request sent by a first application interface, wherein the mapping request comprises a specified service code; calling a mapping model corresponding to the specified service code according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises an entry field of the first application interface, and the target object comprises an entry field of the second application interface; inputting the parameter input field of the first application interface into the mapping model, outputting the parameter input field value of the second application interface, and returning the parameter input field value of the second application interface to the first application interface, so that the first application interface calls the second application interface.

Optionally, before the invoking of the mapping model corresponding to the specified service code according to the mapping request, the method further includes: acquiring a corresponding service code according to an input service type, and configuring the mapping rule corresponding to the service code to obtain the mapping model; wherein the mapping rule includes a mapping type and an expression.

Optionally, the inputting the parameter field of the first application interface into the mapping model and outputting the parameter field value of the second application interface includes: under the condition that the mapping type is common mapping and the expression has a value, outputting the value of the parameter field of the second application interface according to the expression; under the condition that the mapping type is common mapping and the expression has no value, mapping the input parameter field value of the first application interface into the corresponding field of the second application interface in a one-to-one manner according to the corresponding relation between the source object and the target object in the mapping model; and under the condition that the mapping type is enumeration mapping, acquiring the corresponding relation between the field value of the source object and the field value of the target object according to the corresponding relation between the source object and the target object in the mapping model, and mapping the input parameter field value of the first application interface to the corresponding field value of the second application interface according to the corresponding relation between the field value of the source object and the field value of the target object.

Optionally, the expression is a jeel expression; outputting the value of the parameter field of the second application interface according to the expression, including: parsing the JUEL expression through an expression parser to process the value of the ingress field of the first application interface, the processing including mapping a plurality of values of the ingress field of the first application interface into different fields of the second application interface.

Optionally, the expression is a custom function, and the custom function is dynamically registered to the field mapping analysis processor; outputting the value of the parameter field of the second application interface according to the expression, including: and calling the self-defined function through the field mapping analysis processor, and converting the value of the parameter entering field of the first application interface into the parameter entering key value pair of the second application interface.

Optionally, the mapping request further includes a function type; before the parameter field of the first application interface is input into the mapping model, the method further comprises the following steps: and acquiring a configuration template associated with the source object according to the function type, and checking the parameter field of the first application interface according to a checking rule configured in the configuration template associated with the source object.

Optionally, after inputting the parameter field of the first application interface into the mapping model and outputting the parameter field value of the second application interface, the method further includes: and acquiring a configuration template associated with the target object according to the function type, and checking the access field of the second application interface according to a checking rule configured in the configuration template associated with the target object.

Optionally, the mapping request further includes a service party code, and when a configuration template associated with the source object is acquired or a configuration template associated with the target object is acquired, the configuration template corresponding to the service party code is preferentially acquired.

Optionally, the configuration template associated with the source object or the configuration template associated with the target object is created by selecting corresponding metadata, wherein the parameter entry field in the configuration template is obtained by selecting the corresponding metadata, and the check rule corresponding to the parameter entry field in the configuration template is configured.

Optionally, after the configuration template is established, storing configuration information indicating whether the check of the parameter field is started for each parameter field in the configuration template; before checking the parameter entering field of the first application interface or checking the parameter entering field of the second application interface, the method includes: and determining that the configuration information configured corresponding to the parameter field in the configuration template used for verification indicates that the parameter field starts verification.

Optionally, the mapping request further includes a service party code; the calling the mapping model corresponding to the specified service code according to the mapping request comprises: and preferentially calling the mapping model corresponding to the appointed service code and the service party code.

According to another aspect of the embodiments of the present invention, an interface calling apparatus is provided.

An interface invocation apparatus, comprising: a request receiving module, configured to receive a mapping request sent by a first application interface, where the mapping request includes a specified service code; the model calling module is used for calling a mapping model corresponding to the specified service code according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises a parameter field of the first application interface, and the target object comprises a parameter field of the second application interface; and the parameter mapping module is used for inputting the parameter input field of the first application interface into the mapping model, outputting the parameter input field value of the second application interface, and returning the parameter input field value of the second application interface to the first application interface so that the first application interface calls the second application interface.

Optionally, the system further comprises a model configuration module, which acquires a corresponding service code according to the input service type; configuring the mapping rule corresponding to the service code to obtain the mapping model; wherein the mapping rule includes a mapping type and an expression.

Optionally, the parameter mapping module is further configured to: under the condition that the mapping type is common mapping and the expression has a value, outputting the value of the parameter field of the second application interface according to the expression; under the condition that the mapping type is common mapping and the expression has no value, mapping the input parameter field value of the first application interface into the corresponding field of the second application interface in a one-to-one manner according to the corresponding relation between the source object and the target object in the mapping model; and under the condition that the mapping type is enumeration mapping, acquiring the corresponding relation between the field value of the source object and the field value of the target object according to the corresponding relation between the source object and the target object in the mapping model, and mapping the input parameter field value of the first application interface to the corresponding field value of the second application interface according to the corresponding relation between the field value of the source object and the field value of the target object.

Optionally, the expression is a jeel expression; the parameter mapping module is further configured to: parsing the JUEL expression through an expression parser to process the value of the ingress field of the first application interface, the processing including mapping a plurality of values of the ingress field of the first application interface into different fields of the second application interface.

Optionally, the expression is a custom function, and the custom function is dynamically registered to the field mapping analysis processor; the parameter mapping module is further configured to: and calling the self-defined function through the field mapping analysis processor, and converting the value of the parameter entering field of the first application interface into the parameter entering key value pair of the second application interface.

Optionally, the mapping request further includes a function type; the system further comprises a parameter checking module used for: and acquiring a configuration template associated with the source object according to the function type, and checking the parameter field of the first application interface according to a checking rule configured in the configuration template associated with the source object.

Optionally, the parameter checking module is further configured to: and acquiring a configuration template associated with the target object according to the function type, and checking the access field of the second application interface according to a checking rule configured in the configuration template associated with the target object.

Optionally, the mapping request further includes a service side code, and the parameter checking module is further configured to: and when the configuration template associated with the source object is acquired or the configuration template associated with the target object is acquired, preferentially acquiring the configuration template corresponding to the service party code.

Optionally, the system further includes a template establishing module, configured to establish a configuration template associated with the source object or a configuration template associated with the target object by selecting corresponding metadata, where when the configuration template is established, the parameter entry field in the configuration template is obtained by selecting corresponding metadata, and the check rule corresponding to the parameter entry field in the configuration template is configured.

Optionally, the template establishing module is further configured to store, for each entry field in the configuration template, configuration information indicating whether the entry field is checked; the parameter checking module is further configured to determine that the configuration information configured corresponding to the parameter entry field in the configuration template used for checking indicates that the parameter entry field starts checking before checking the parameter entry field of the first application interface or checking the parameter entry field of the second application interface.

Optionally, the mapping request further includes a service party code; the model calling module is further configured to: and preferentially calling the mapping model corresponding to the appointed service code and the service party code.

According to yet another aspect of an embodiment of the present invention, an electronic device is provided.

An electronic device, comprising: one or more processors; a memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the interface call method provided by embodiments of the present invention.

According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.

A computer-readable medium, on which a computer program is stored, which, when executed by a processor, implements an interface calling method provided by an embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits: receiving a mapping request sent by a first application interface, calling a mapping model corresponding to a service code specified in the mapping request according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises a parameter field of the first application interface, the target object comprises a parameter field of a second application interface, inputting the parameter field of the first application interface into the mapping model, outputting the parameter field value of the second application interface, and returning the parameter field value of the second application interface to the first application interface so that the first application interface calls the second application interface. The method can overcome the defect of extremely low efficiency of a hard coding mode, shorten the development period, reduce the development cost, realize the mapping of dynamic parameters to downstream, and solve the problems of high construction cost, high requirement on technical personnel and inconsistent service execution of the current automatic service.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a diagram illustrating the main steps of an interface call method according to one embodiment of the present invention;

FIG. 2 is a schematic diagram of a source object and a target object according to one embodiment of the invention;

FIG. 3 is a diagram of a mapping model configuration interface, according to one embodiment of the invention;

FIG. 4 is a diagram of a dictionary table interface according to one embodiment of the present invention;

FIG. 5 is a sub-interface diagram of a metadata object management interface, according to one embodiment of the invention;

FIG. 6 is a schematic view of a configuration interface for a configuration template according to one embodiment of the invention;

FIG. 7 is a schematic diagram of an interface call flow according to one embodiment of the invention;

FIG. 8 is a schematic diagram of the main blocks of an interface invocation means according to an embodiment of the present invention;

FIG. 9 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

FIG. 10 is a schematic block diagram of a computer system suitable for use with a server implementing an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Fig. 1 is a schematic diagram of main steps of an interface calling method according to an embodiment of the present invention.

As shown in fig. 1, the interface calling method according to an embodiment of the present invention mainly includes the following steps S101 to S103.

Step S101: receiving a mapping request sent by a first application interface, wherein the mapping request comprises a specified service code;

step S102: calling a mapping model corresponding to the specified service code according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises a parameter field of a first application interface, and the target object comprises a parameter field of a second application interface;

step S103: and inputting the parameter input field of the first application interface into the mapping model, outputting the parameter input field value of the second application interface, and returning the parameter input field value of the second application interface to the first application interface so that the first application interface calls the second application interface.

The mapping of the argument field of the first application interface to the argument field of the second application interface may be performed by a mapping model.

According to the mapping request, before calling the mapping model corresponding to the specified service code, the mapping model can be configured in advance, specifically, the corresponding service code is obtained according to the input service type, and the mapping rule corresponding to the service code is configured to obtain the mapping model, wherein the mapping rule comprises the mapping type and the expression.

Inputting the parameter field of the first application interface into the mapping model, and outputting the parameter field value of the second application interface, which specifically comprises: judging whether an expression in the mapping rule has a value or not under the condition that the mapping type is common mapping, and executing mapping according to the expression to output a parameter field value of a second application interface under the condition that the mapping type is common mapping and the expression has the value; under the condition that the mapping type is common mapping and the expression has no value, mapping the input parameter field value of the first application interface into the corresponding field of the second application interface one to one according to the corresponding relation between the source object and the target object in the mapping model; and under the condition that the mapping type is enumeration mapping, acquiring the corresponding relation between the field value of the source object and the field value of the target object according to the corresponding relation between the source object and the target object in the mapping model, and mapping the input parameter field value of the first application interface into the corresponding field value of the second application interface according to the corresponding relation between the field value of the source object and the field value of the target object.

The Expression in the mapping rule may be a JUEL Expression, which is an implementation of a Unified Expression Language (EL). Outputting the value of the parameter field of the second application interface according to the expression, which may specifically include: parsing the JUEL expression by an expression parser to process an entry field value of the first application interface, the processing including mapping a plurality of entry field values of the first application interface into different fields of the second application interface. The expression parser can be any parser capable of parsing JUEL expressions.

The expression in the mapping rule may be a custom function, which is dynamically registered with the field mapping parsing processor. Outputting the value of the parameter field of the second application interface according to the expression, which may specifically include: and calling a custom function through a field mapping analysis processor to convert the value of the parameter input field of the first application interface into the parameter key value pair of the second application interface. The field mapping analysis processor is used for calling the custom function and mapping by using the custom function.

The mapping request may further include function types, the function types being set according to the service functions, one function type indicating one service function. Before the parameter field of the first application interface is input into the mapping model, the configuration template associated with the source object can be obtained according to the function type, and the parameter field of the first application interface is verified according to the verification rule configured in the configuration template associated with the source object.

Inputting the parameter field of the first application interface into the mapping model, outputting the parameter field value of the second application interface, acquiring a configuration template associated with the target object according to the function type, and verifying the parameter field of the second application interface according to a verification rule configured in the configuration template associated with the target object.

The mapping request may further include a service party code, and when the configuration template associated with the source object is acquired or the configuration template associated with the target object is acquired, the configuration template corresponding to the service party code is preferentially acquired.

The configuration template associated with the source object or the configuration template associated with the target object may be established by selecting corresponding metadata, wherein the parameter fields in the configuration template are obtained by selecting the corresponding metadata, and the verification rules corresponding to the parameter fields in the configuration template are configured.

After the configuration template is established, configuration information indicating whether check is opened for the entry field may be stored for each entry field in the configuration template. Before checking the parameter entry field of the first application interface or checking the parameter entry field of the second application interface, it may be determined that the configuration information configured corresponding to the parameter entry field in the configuration template used for checking indicates that the parameter entry field starts checking.

And calling a mapping model corresponding to the specified service code according to the mapping request, and particularly preferably calling the mapping model corresponding to both the specified service code and the service party code.

The following scenario is taken as an example, and the interface calling method according to the embodiment of the present invention is described in detail below.

The B2C service places a bill through JOS (aeus, an open service) or the merchant, calls the ldop-center-provider application (an example of the second application) through the ldop-pipe-web (an example of the first application), whose jsf (jeff) interface (an example of the first application interface) is entered into the orderindto, which is entered into the ldop-center-provider interface (an example of the second application interface): the WayBillDTO can solve the problem of value mapping between two DTO (Data Transfer Object) fields, does not need to write codes, and can realize one-to-one mapping, many-to-one mapping, enumeration mapping and user-defined function processing through interface configuration. Wherein:

one-to-one mapping, which is to one-to-one map the value of the ingress field of the first application interface into the corresponding field of the second application interface, for example: the cardId value in the first application interface import parameter OrderInfoDTO is mapped to the cardId field of the second application interface import parameter WayBillDTO, namely the field is transmitted through.

Many-to-one mapping maps multiple values of the entry parameters of a first application interface into different fields of a second application interface, for example: multiple fields in the first application interface in-parameter OrderInfoDTO map to different attributes in the second application interface in-parameter WayBillDTO.

Enumerating and mapping, namely mapping the value of an input parameter field of a first application interface to the corresponding value of a second application interface, wherein the value of the field is an enumerated value, for example: the promisetimtype enumerated value in the first application interface in-parameter OrderInfoDTO maps to the productType enumerated value in the second application interface in-parameter WayBillDTO.

And (3) performing self-defined function processing, namely calling a self-defined function to convert the value of the parameter of the first application interface into the value pair of the parameter of the second application interface, for example, converting the addService value of the parameter of the first application interface into the value pair of the extendedmessag (map type) of the parameter of the second application interface, wherein the map is used for storing the value pair of the key.

The embodiment of the invention configures the storage of the source object and the target object and the related attributes into the database, manages the check rule of each field into the database, and manages the mapping relation between the source object and the target object, including but not limited to one-to-one mapping, many-to-one mapping, enumeration mapping and mapping by calling a custom function. The mapping is carried out by calling a custom function, the custom function can be specifically configured and built in, then the resolver is used for resolving, and the value of the object to be entered is mapped to the attribute of the target object, and the resolver is a field mapping resolving processor.

Fig. 2 is a schematic diagram of a source object and a target object according to an embodiment of the present invention, as shown in fig. 2, a name, a gender, an address, an identification number, a remark, a certificate type, and the like of the source object are mapped to an order number, a recipient name, a recipient address, an identification number, an extension type, a certificate type, and the like of the target object, and the actual application object in fig. 2 may be a set of entries of a downstream application (i.e., a second application), that is, an entry required for invoking a second application interface, and in a case where all entries are obtained by this mapping, the target object is the same as the actual application object. In the case that only part of the entries of the second application interface are obtained by the mapping this time (for example, some entries of the second application interface are obtained by mapping the parameter field before, and then the entries do not need to be obtained by remapping this time), the actual application object is the result of merging the target object with the existing mapping result (i.e., those entries obtained by mapping before).

The mapping model of the embodiment of the invention can be configured according to needs, the mapping model has the model code of the mapping model, a general mapping model (namely a general mapping model) can be configured, and personalized configuration can also be carried out aiming at a certain merchant (namely a business party), namely the personalized mapping model is configured, each merchant has the merchant code of the merchant, and the merchant code is the business party code. A mapping model parsing interface may be invoked at a placing interface of a first application (e.g., ldop-pipe-web), where the mapping model parsing interface is an interface provided by the mapping model according to an embodiment of the present invention, and a call request of the first application to the interface of the mapping model, that is, a mapping request sent by the first application interface, includes a specified service code, and the mapping request may also include a merchant code, and a personalized mapping model of a merchant may be obtained according to the merchant code. If the personalized mapping model of the merchant is configured, the personalized mapping model of the merchant is preferably called, and if the personalized mapping model of the merchant does not exist, the universal mapping model is called. The personalized mapping model of the merchant is the mapping model corresponding to the specified business code and business party code (i.e. merchant code) in the mapping request. The mapping model resolves the entry value corresponding to the jsf interface of the second application (e.g., the ldop-center-provider application) for different field configuration rules (i.e., mapping rules).

A mapping model can be configured through a model configuration interface, as shown in fig. 3, which is a schematic diagram of a mapping model configuration interface according to an embodiment of the present invention, a service type needs to be selected first, a service code is read according to the service type, the service code is a model code, the model code is uniformly managed in a dictionary table function, each dictionary table function corresponds to one model code, the model type can select a custom model (i.e., a personalized mapping model) or a general model (i.e., a general mapping model), a source object and a target object are selected, after the target object is selected, all field information configured in the target object in a list can be obtained, including a name, an attribute and a type, and for each row, a corresponding attribute of the source object can be selected.

A configuration template associated with the target object may be pre-established, all field information configured in the target object may be obtained from the configuration template associated with the target object, and a configuration template associated with the source object may also be established, which will be described in detail below.

When the mapping model is configured, the mapping type and the expression may also be configured, that is, the mapping rule may include the mapping type and the expression, and the mapping type is, for example: ordinary mapping, enumeration mapping, for ordinary mapping, if an expression is not set, it is a one-to-one mapping, for example, a value of a certain argument field a of the first application interface: 1, mapping to the value of the corresponding parameter field b of the second application interface: 1, if the expression has a value, the value can fill in a JUEL expression and a self-defined function, and then the value is analyzed through an expression analyzer. For enumeration mapping, all values of the field of the target object are pulled out, and a source field value may be selected, i.e., field enumeration mapping may be implemented, for example, by pulling a source field value (i.e., a parameter field value of a first application interface): 1, mapped as a target field value (i.e. the corresponding field value of the second application interface): t-m-001.

The method can be dynamically registered to a field mapping analysis processor, and if the mapping model configures the method, the field mapping analysis processor can call the method to analyze and process the attribute value.

The dictionary table is mainly used for dynamically configuring function types and mapping model types. When the template is configured, the function type needs to be selected, and when the mapping model is configured, a mapping model type also needs to be selected. A diagram of a dictionary table interface in accordance with one embodiment of the present invention is shown in fig. 4.

The embodiment of the invention can check different fields, including checking the parameter-entering field of the first application interface before parameter mapping and checking the parameter-entering field of the second application interface after parameter mapping. The mapping request can also comprise a function type, and parameter fields are checked through a checking rule configured by the configuration template.

The method comprises the steps of establishing associated configuration templates aiming at a source object and a target object in advance, wherein each configuration template corresponds to a function type, only one default template can exist in the same function type, a plurality of personalized templates can exist, and each merchant can correspond to a plurality of function types. The personalized configuration template of the merchant can be obtained according to the function type and the business party code (namely, the merchant code), and when the personalized configuration template of the merchant is obtained, the personalized configuration template is preferentially used, namely: when the configuration template associated with the source object is obtained or the configuration template associated with the target object is obtained, the configuration template corresponding to the business party code (namely, the personalized configuration template of the merchant) is preferentially obtained. And checking the parameter entering field of the first application interface according to a checking rule configured in the configuration template associated with the source object, and checking the parameter entering field of the second application interface according to a checking rule configured in the configuration template associated with the target object.

The configuration template associated with the source object or the configuration template associated with the target object is created by selecting the corresponding metadata. The source object comprises a parameter field of the first application interface, and can be selected from metadata of the first application interface according to the requirement of current call. The target object comprises a parameter field of the second application interface, and can be selected from metadata of the second application interface according to the requirement of current call. The data of the source object and the target object are the reference fields of the configuration template configuration. The metadata for an application interface includes all the fields that can be referenced as an application interface under various service types.

One embodiment of the present invention can manage metadata objects through a metadata object management interface, which mainly aims at performing unified management on parameter objects of the interface. For example, the metadata names may be queried or added in the metadata object management interface by using class full path names, and each metadata name corresponds to information such as class full path name, metadata encoding, function type, creation time, update time, creator, modifier, operation type (editing, deleting, etc.).

Each metadata object is provided with a plurality of fields, namely metadata fields, each field is provided with attributes such as name, field type and the like, and the metadata field can be a metadata object, namely, the metadata is equivalent to the metadata embedded in the metadata field to form metadata of a tree structure. Metadata fields under a certain metadata object can be newly added (newly created) in the metadata object management interface, field names under the metadata object can be inquired by using metadata object names (namely metadata names), and each field name corresponds to information such as field description (used for describing the corresponding metadata field), field type, field classification, industry type (defined according to business requirements), sequencing (sequence number of the field), creation time, updating time, creator, modifier, operation type (editing, deleting and the like).

Fig. 5 is a schematic sub-interface diagram of a metadata object management interface according to an embodiment of the present invention, which is used for adding a metadata field newly, when a metadata field is newly created, if a field type is selected as Java.

The metadata field can have a known fixed value, can be uniformly managed through a metadata object management interface, and can be added with a plurality of values.

When the configuration template is established, the configuration template is mainly established aiming at the metadata field, and the configuration template is divided into a default configuration template and a personalized configuration template.

FIG. 6 is a schematic configuration interface diagram of a configuration template for editing a template configuration, according to an embodiment of the invention. When the configuration template is established, the metadata is selected first, all fields under the metadata are pulled out after the metadata is selected, and each field can be selectively started and stopped, namely, the configuration information indicating whether the input parameter field is started for verification is stored, if the configuration information is configured to be stopped, the field is ignored, and if the configuration information is configured to be started, the field is valid, and the verification is started. Fields of the configuration template support a tree structure, and each field may have sub-attributes. The configuration template is configured with a check rule, for example, whether the check is necessary to be performed or not, a value range check, a regular check, and the like can be configured.

When the parameters are checked (namely, the parameter entry fields are checked), if the personalized configuration template is configured for the corresponding merchant, the personalized configuration template is preferentially obtained, if the personalized configuration template of the merchant is not configured, the default configuration template is obtained, each configuration template has a function type, only one default configuration template can be used for the same function type, but a plurality of personalized configuration templates can be used. The personalized configuration template of the merchant can be obtained through merchant code and function type inquiry.

The embodiment can perform unified arrangement on the ordering process, manage the whole interface process in a unified way, perform parameter verification, perform product verification according to needs, group parameters and adjust the external interface ordering, can define a global parameter manager, manage the output parameters of each step in the whole process, and transmit the output parameters to the downstream interface, thereby realizing the automation of the whole process. The dynamic expansion of the interface can be carried out, a map is defined for the interface, when a new service scene comes, a field is needed to identify the service meaning, the field is not needed to be added at the moment, only a key is needed to be added in the map, the key can be defined by a merchant, the key needs to be uniformly configured and managed through a background, if the parameter is not configured, if the parameter is transmitted when the merchant places an order, the parameter is directly returned to be invalid.

FIG. 7 is a schematic diagram of an interface call flow according to one embodiment of the invention.

As shown in fig. 7, the interface call flow of an embodiment of the present invention includes: managing and controlling metadata and fields uniformly, configuring fields and verification rules for the metadata through configuration templates, associating a source object with a target object and attributes through a mapping model, and configuring the mapping rules (S701), wherein the source object and the target object are both associated with the configuration templates, and each configuration template configures the verification rules such as mandatory padding, value range configuration, regular configuration, other verification configurations and the like for the fields; after receiving a mapping request sent by a first application interface, searching a corresponding configuration template through a function type and a merchant code (S702); if the merchant configures the personalized configuration template, reading out the personalized configuration template, and if the personalized configuration template is not configured, reading out the general configuration template (S703); searching a corresponding mapping model through the model code and the merchant code (S704); if the merchant configures the personalized mapping model, the personalized mapping model is called, if the personalized mapping model is not configured, the general mapping model is called (S705), wherein each model associates the attributes of the source object and the target object, performs configuration enumeration mapping or common mapping on the attributes, and can also configure an expression and a self-defining method, the source object belongs to the input parameter of the first application interface, the target object is an object needing mapping processing, namely the input parameter of the second application interface to be called by the first application interface, and the first application interface needs to be provided with the input parameter of the second application interface when calling the second application interface; before mapping, parameter verification is carried out on a source object field (namely a parameter input field of a first application interface) through a configuration template, after the verification is passed, mapping of the parameter input field is carried out by using a mapping model according to a source object value, and all parameter input values of a target object are obtained (S706); parameter verification is carried out on the field of the target object (all the entries of the target object, namely the entry field of the second application interface) through the configuration template (S707); after the verification is passed, the value of the target object field (all the entry parameters of the target object, i.e., the entry parameters of the second application interface) is returned to the first application interface for the first application interface to call the target interface (i.e., the second application interface) (S708).

The embodiment of the invention aims at solving the problem that the efficiency of the demand of a docking merchant is low because different processes are required to be carried out on field mapping and value transfer verification in the prior interface calling technology every time and development is required every time, can enable non-research and development personnel to realize dynamic parameter mapping to the downstream through an interface or file configuration mode, and solves the problems of high construction cost, high requirement on technical personnel and discontinuous service execution of the current automatic service.

Fig. 8 is a schematic diagram of main blocks of an interface calling apparatus according to an embodiment of the present invention.

As shown in fig. 8, an interface calling apparatus 800 according to an embodiment of the present invention mainly includes: a request receiving module 801, a model calling module 802, and a parameter mapping module 803.

A request receiving module 801, configured to receive a mapping request sent by a first application interface, where the mapping request includes a specified service code;

a model calling module 802, configured to call a mapping model corresponding to a specified service code according to a mapping request, where the mapping model includes a mapping rule between a source object and a target object, the source object includes a parameter field of a first application interface, and the target object includes a parameter field of a second application interface;

the parameter mapping module 803 is configured to input the parameter entry field of the first application interface into the mapping model, output the parameter entry field value of the second application interface, and return the parameter entry field value of the second application interface to the first application interface, so that the first application interface calls the second application interface.

The interface calling device 800 may further include a model configuration module, configured to obtain a corresponding service code according to the input service type, and configure a mapping rule corresponding to the service code to obtain a mapping model; the mapping rule comprises a mapping type and an expression.

The parameter mapping module 803 may be specifically configured to: under the condition that the mapping type is common mapping and the expression has a value, outputting the value of the parameter field of the second application interface according to the expression; under the condition that the mapping type is common mapping and the expression has no value, mapping the input parameter field value of the first application interface into the corresponding field of the second application interface one to one according to the corresponding relation between the source object and the target object in the mapping model; and under the condition that the mapping type is enumeration mapping, acquiring the corresponding relation between the field value of the source object and the field value of the target object according to the corresponding relation between the source object and the target object in the mapping model, and mapping the input parameter field value of the first application interface into the corresponding field value of the second application interface according to the corresponding relation between the field value of the source object and the field value of the target object.

The expression in the mapping rule may be a jeel expression. The parameter mapping module 803 is further specifically configured to: parsing the JUEL expression by an expression parser to process an entry field value of the first application interface, the processing including mapping a plurality of entry field values of the first application interface into different fields of the second application interface.

The expression in the mapping rule may be a custom function, which is dynamically registered with the field mapping parsing processor. The parameter mapping module 803 is further specifically configured to: and calling a custom function through a field mapping analysis processor to convert the value of the parameter input field of the first application interface into the parameter key value pair of the second application interface.

The mapping request may also include a function type. The interface invocation device 800 may also include a parameter checking module for: and according to the function type, acquiring a configuration template associated with the source object, and according to a verification rule configured in the configuration template associated with the source object, verifying the parameter entering field of the first application interface.

The parameter checking module is used for: and according to the function type, acquiring a configuration template associated with the target object, and according to a verification rule configured in the configuration template associated with the target object, verifying the parameter entering field of the second application interface.

The mapping request may also include a service side code. The parameter verification module is specifically further configured to: and when the configuration template associated with the source object is acquired or the configuration template associated with the target object is acquired, preferentially acquiring the configuration template corresponding to the business side code.

The interface invoking device 800 may further include a template establishing module, configured to establish a configuration template associated with the source object or a configuration template associated with the target object by selecting the corresponding metadata, wherein when the configuration template is established, the parameter field in the configuration template is obtained by selecting the corresponding metadata, and the check rule corresponding to the parameter field in the configuration template is configured.

The template establishing module is further specifically configured to store, for each entry field in the configuration template, configuration information indicating whether the entry field is checked.

The parameter checking module is further specifically configured to determine that configuration information configured in a configuration template used for checking indicates that the parameter entering field starts checking before checking the parameter entering field of the first application interface or before checking the parameter entering field of the second application interface.

The mapping request may also include a service side code. The model calling module 802 is further specifically configured to: and calling the mapping model corresponding to the appointed service code and the service party code preferentially.

In addition, the specific implementation content of the interface calling device in the embodiment of the present invention has been described in detail in the above interface calling method, so that repeated content herein is not described again.

Fig. 9 illustrates an exemplary system architecture 900 to which an interface calling method or interface calling apparatus of an embodiment of the present invention may be applied.

As shown in fig. 9, the system architecture 900 may include

end devices

901, 902, 903, a network 904, and a server 905. Network 904 is the medium used to provide communication links between

terminal devices

901, 902, 903 and server 905. Network 904 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

901, 902, 903 to interact with a server 905 over a network 904 to receive or send messages and the like. The

terminal devices

901, 902, 903 may have installed thereon various messenger client applications such as, for example only, a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, social platform software, etc.

The

terminal devices

901, 902, 903 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 905 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the

terminal devices

901, 902, 903. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.

It should be noted that the interface calling method provided by the embodiment of the present invention is generally executed by the server 905, and accordingly, the interface calling apparatus is generally disposed in the server 905.

It should be understood that the number of terminal devices, networks, and servers in fig. 9 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 10, a block diagram of a computer system 1000 suitable for use in implementing a server according to embodiments of the present application is shown. The server shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 10, the computer system 1000 includes a Central Processing Unit (CPU)1001 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. In the RAM 1003, various programs and data necessary for the operation of the system 1000 are also stored. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.

The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The driver 1010 is also connected to the I/O interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. The computer program executes the above-described functions defined in the system of the present application when executed by the Central Processing Unit (CPU) 1001.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises a request receiving module, a model calling module and a parameter mapping module. The names of these modules do not constitute a limitation to the module itself in some cases, for example, the request receiving module may also be described as a "module for receiving a mapping request sent by the first application interface".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: receiving a mapping request sent by a first application interface, wherein the mapping request comprises a specified service code; calling a mapping model corresponding to the specified service code according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises an entry field of the first application interface, and the target object comprises an entry field of the second application interface; inputting the parameter input field of the first application interface into the mapping model, outputting the parameter input field value of the second application interface, and returning the parameter input field value of the second application interface to the first application interface, so that the first application interface calls the second application interface.

According to the technical scheme of the embodiment of the invention, a mapping model corresponding to a specified service code in the mapping request is called according to the mapping request sent by a first application interface, the mapping model comprises a mapping rule of a source object and a target object, the source object comprises a parameter field of the first application interface, the target object comprises a parameter field of a second application interface, the parameter field of the first application interface is input into the mapping model, the parameter field value of the second application interface is output, and the parameter field value of the second application interface is returned to the first application interface, so that the first application interface calls the second application interface. The method can overcome the defect of extremely low efficiency of a hard coding mode, shorten the development period, reduce the development cost, realize the mapping of dynamic parameters to downstream, and solve the problems of high construction cost, high requirement on technical personnel and inconsistent service execution of the current automatic service.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. An interface calling method, comprising:

receiving a mapping request sent by a first application interface, wherein the mapping request comprises a specified service code;

calling a mapping model corresponding to the specified service code according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises an entry field of the first application interface, and the target object comprises an entry field of the second application interface;

inputting the parameter input field of the first application interface into the mapping model, outputting the parameter input field value of the second application interface, and returning the parameter input field value of the second application interface to the first application interface, so that the first application interface calls the second application interface.

2. The method according to claim 1, wherein before the invoking of the mapping model corresponding to the specified service code according to the mapping request, the method further comprises:

acquiring a corresponding service code according to the input service type;

configuring the mapping rule corresponding to the service code to obtain the mapping model; wherein the mapping rule includes a mapping type and an expression.

3. The method of claim 2, wherein inputting the value of the parameter field of the first application interface into the mapping model and outputting the value of the parameter field of the second application interface comprises:

under the condition that the mapping type is common mapping and the expression has a value, outputting the value of the parameter field of the second application interface according to the expression;

under the condition that the mapping type is common mapping and the expression has no value, mapping the input parameter field value of the first application interface into the corresponding field of the second application interface in a one-to-one manner according to the corresponding relation between the source object and the target object in the mapping model;

and under the condition that the mapping type is enumeration mapping, acquiring the corresponding relation between the field value of the source object and the field value of the target object according to the corresponding relation between the source object and the target object in the mapping model, and mapping the input parameter field value of the first application interface to the corresponding field value of the second application interface according to the corresponding relation between the field value of the source object and the field value of the target object.

4. The method of claim 3, wherein the expression is a JUEL expression;

outputting the value of the parameter field of the second application interface according to the expression, including:

parsing the JUEL expression through an expression parser to process the value of the ingress field of the first application interface, the processing including mapping a plurality of values of the ingress field of the first application interface into different fields of the second application interface.

5. The method of claim 3, wherein the expression is a custom function that is dynamically registered with a field mapping parser processor;

and calling the self-defined function through the field mapping analysis processor, and converting the value of the parameter entering field of the first application interface into the parameter entering key value pair of the second application interface.

6. The method of claim 1, wherein the mapping request further includes a function type;

before the parameter field of the first application interface is input into the mapping model, the method further comprises the following steps:

and acquiring a configuration template associated with the source object according to the function type, and checking the parameter field of the first application interface according to a checking rule configured in the configuration template associated with the source object.

7. The method of claim 6, wherein after inputting the value of the parameter field of the first application interface into the mapping model and outputting the value of the parameter field of the second application interface, further comprising:

and acquiring a configuration template associated with the target object according to the function type, and checking the access field of the second application interface according to a checking rule configured in the configuration template associated with the target object.

8. The method according to claim 7, wherein the mapping request further includes a service code, and when the configuration template associated with the source object is obtained or the configuration template associated with the target object is obtained, the configuration template corresponding to the service code is preferentially obtained.

9. The method according to claim 7, wherein the configuration template associated with the source object or the configuration template associated with the target object is created by selecting corresponding metadata, wherein the parameter fields in the configuration template are obtained by selecting corresponding metadata, and the check rules corresponding to the parameter fields in the configuration template are configured.

10. The method according to claim 9, further comprising storing configuration information indicating whether the access field is checked for opening for each access field in the configuration template after the configuration template is established;

before checking the parameter entering field of the first application interface or checking the parameter entering field of the second application interface, the method includes:

and determining that the configuration information configured corresponding to the parameter field in the configuration template used for verification indicates that the parameter field starts verification.

11. The method of claim 1, wherein the mapping request further includes a service side code;

the calling the mapping model corresponding to the specified service code according to the mapping request comprises: and preferentially calling the mapping model corresponding to the appointed service code and the service party code.

12. An interface invocation apparatus, comprising:

a request receiving module, configured to receive a mapping request sent by a first application interface, where the mapping request includes a specified service code;

the model calling module is used for calling a mapping model corresponding to the specified service code according to the mapping request, wherein the mapping model comprises a mapping rule of a source object and a target object, the source object comprises a parameter field of the first application interface, and the target object comprises a parameter field of the second application interface;

and the parameter mapping module is used for inputting the parameter input field of the first application interface into the mapping model, outputting the parameter input field value of the second application interface, and returning the parameter input field value of the second application interface to the first application interface so that the first application interface calls the second application interface.

13. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-11.

14. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-11.