CN117573762B - Data processing method and device of data connection platform, storage medium and server - Google Patents
Data processing method and device of data connection platform, storage medium and server Download PDFInfo
- Publication number
- CN117573762B CN117573762B CN202410053502.4A CN202410053502A CN117573762B CN 117573762 B CN117573762 B CN 117573762B CN 202410053502 A CN202410053502 A CN 202410053502A CN 117573762 B CN117573762 B CN 117573762B
- Authority
- CN
- China
- Prior art keywords
- data
- attribute
- request
- target
- request data
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 35
- 238000013507 mapping Methods 0.000 claims abstract description 58
- 238000006243 chemical reaction Methods 0.000 claims abstract description 51
- 230000004044 response Effects 0.000 claims description 101
- 238000012545 processing Methods 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 14
- 238000001914 filtration Methods 0.000 claims description 3
- 230000009466 transformation Effects 0.000 claims description 2
- 238000000034 method Methods 0.000 abstract description 10
- 238000013075 data extraction Methods 0.000 abstract description 7
- 230000008569 process Effects 0.000 abstract description 6
- 210000001072 colon Anatomy 0.000 description 13
- 230000000007 visual effect Effects 0.000 description 13
- 241000208340 Araliaceae Species 0.000 description 12
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 12
- 235000003140 Panax quinquefolius Nutrition 0.000 description 12
- 235000008434 ginseng Nutrition 0.000 description 12
- 239000000047 product Substances 0.000 description 10
- 239000010410 layer Substances 0.000 description 7
- 238000000926 separation method Methods 0.000 description 6
- 238000012800 visualization Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000002356 single layer Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Abstract
The data processing method of the data connection platform comprises the steps of receiving request data from the first interface, and converting the request data into converted request data described by Json Schema by adopting a request conversion rule; according to the request mapping rule, searching values of all attributes in the target Json Schema data structure in the converted request data to obtain target request data described by the Json Schema; and outputting the target request data through a second interface. The scheme can avoid data loss in the conversion process, and ensure the data extraction efficiency and the accurate and complete information of the target request data.
Description
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a data processing method and device of a data connection platform, a storage medium and a server.
Background
In service products related to customer service, since the customer groups facing each other have diversity, the application services that can be provided also have diversity. The protocols supported by clients accessing the service products are of various types, and the protocols supported by various application services are of various types. Because the data structures described by different protocols may be different, data required by an application service needs to be extracted from data of different data structures, and when the required data is extracted from data of different data structure types, problems of low data extraction efficiency, loss of key data and the like are easy to occur.
Disclosure of Invention
The technical problem solved by the embodiment of the invention is that when the required data is extracted from the data with different data structure types, the problems of low data extraction efficiency, lost key data and the like are easy to occur.
In order to solve the above technical problem, an embodiment of the present invention provides a data connection platform having a plurality of first interfaces and second interfaces, where data transmitted by the first interfaces conform to a definition of a data structure described by OAS, and data transmitted by the second interfaces conform to a definition of a target Json Schema data structure, and the data processing method includes: receiving request data from a first interface, and converting the request data into converted request data described by a Json Schema by adopting a request conversion rule corresponding to a protocol adopted by the request data; according to a request mapping rule, searching values of all attributes in the target Json Schema data structure in the converted request data to obtain target request data described by the Json Schema; and outputting the target request data through the second interface.
Optionally, the request data includes a plurality of entries, a protocol adopted by the request data defines a plurality of entry types, the request data is converted into converted request data described by Json Schema by adopting a request conversion rule corresponding to the protocol adopted by the request data, and the method includes: and taking the multiple entry types as attributes of the converted request data outermost layer object, and taking each entry as a next-level attribute of the corresponding attribute of the entry type to which the entry belongs.
Optionally, the parameter entering has a preset format, and the data processing method further includes: and filtering the request data according to the preset format to screen out the entry contained in the request data.
Optionally, according to a request mapping rule, searching values of each attribute in the target Json Schema data structure in the converted request data to obtain target request data described by the Json Schema, including: searching for an attribute matched with the attribute in the target Json Schema data structure in the converted request data according to the principle of the same path, and taking the value of the matched attribute as the value of the attribute in the target Json Schema data structure to obtain target request data described by the Json Schema; and/or acquiring a parameter entry mapping relation appointed by a user, and acquiring values of corresponding attributes from the converted request data according to the parameter entry mapping relation for each attribute in the target Json Schema data structure so as to acquire target request data described by the Json Schema.
Optionally, each attribute in the converted request data is configured with a priority, and searching the value of each attribute in the target Json Schema data structure in the converted request data includes: and searching the attributes matched with the attributes in the target Json Schema data structure in the converted request data according to the order of the priority from high to low and by adopting the principle of identical paths.
Optionally, the data processing method further includes: and if the matched attribute is not found in the converted request data for the attribute of the target Json Schema data structure, configuring the value of the matched attribute which is not found in the target Json Schema data structure as a default value.
Optionally, the data processing method further includes: and when receiving update information of the target Json Schema data structure, updating the target Json Schema data structure based on the update information.
Optionally, the request conversion rule corresponding to the protocol adopted by the input data is determined in the following manner: identifying an interface identifier of the first interface; searching request conversion rules corresponding to the first interfaces according to the interface identifiers of the first interfaces, wherein each request conversion rule corresponding to the first interfaces is preconfigured according to a protocol supported by the first interfaces.
Optionally, the data processing method further includes: response data corresponding to the request data are obtained, and the response data are converted into converted response data described by Json Schema in OAS by adopting a response conversion rule; according to a response mapping rule, searching values of all attributes in the data structure of the OAS description in the converted response data to obtain target response data of the OAS description; and outputting the target response data through the first interface.
Optionally, the target response data includes a plurality of parameters, a protocol adopted by the target response data defines a plurality of parameter types, and the adopting a response conversion rule converts the response data into converted response data described by Json Schema in OAS, including: and determining the parameter-out type corresponding to each parameter-out in the response data, taking the parameter-out types as the attribute of the outermost object of the converted response data, and taking each parameter-out as the next-stage attribute of the corresponding attribute of the parameter-out type to obtain the converted response data.
Optionally, according to a response mapping rule, searching values of each attribute in the data structure of the OAS description in the converted response data to obtain target response data of the OAS description, where the target response data includes: according to each attribute in the OAS description data structure and the principle of identical path, searching the value of the attribute in the OAS description data structure in the converted response data to obtain target response data of the OAS description; and/or acquiring a parameter-out mapping relation designated by a user, and acquiring values of corresponding attributes from the converted response data according to the parameter-out mapping relation for each attribute in the data structure of the OAS description so as to acquire target response data of the OAS description.
The embodiment of the invention also provides a data processing device of a data processing platform, the data connection platform is provided with a plurality of first interfaces and second interfaces, the data transmitted by the first interfaces accords with the definition of a data structure described by OAS, the data transmitted by the second interfaces accords with the definition of a target Json Schema data structure, and the data processing device comprises: the conversion unit is used for receiving request data from the first interface, and converting the request data into converted request data described by the Json Schema by adopting a request conversion rule corresponding to a protocol adopted by the request data; the processing unit is used for searching values of all the attributes in the target Json Schema data structure in the converted request data according to a request mapping rule so as to obtain target request data described by the Json Schema; and the output unit is used for outputting the target request data through the second interface.
The embodiments of the present invention also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of any of the data processing methods described above.
The embodiment of the invention also provides a server, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the steps of any one of the data processing methods when running the computer program.
Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:
and receiving the request data through a first interface of the data connection platform, and converting the request data into converted request data described by the Json Schema by adopting a request conversion rule corresponding to a protocol adopted by the request data. Because the data transmitted by the second interface of the data connection platform accords with the target Json Schema data structure, the structure consistency of the converted request data and the data transmitted by the second interface is realized by converting the request data into the converted request data described by the Json Schema. Because the data described by the Json Schema has the advantages of simplicity, easy understanding, better reading performance and the like, the Json Schema description is firstly converted on the request data, then under the same Json Schema description, the values of all the attributes in the target Json Schema data structure are searched from the converted request data consistent with the structure of the target Json Schema data structure, so that the data loss of the request data in the conversion process can be avoided, the values of all the attributes in the target Json Schema data structure can be quickly and accurately searched, and the data extraction efficiency and the obtained target request data can be more accurately and completely expressed.
Drawings
FIG. 1 is a flow chart of a data processing method of a data connection platform in an embodiment of the invention;
FIG. 2 is a schematic illustration of a visual interface;
fig. 3 is a schematic structural diagram of a data processing device of a data connection platform according to an embodiment of the present invention.
Detailed Description
As described above, protocols supported by clients accessing service products are of various types, and protocols supported by various application services are of various types. Since the data structures described by different protocols may be different, this results in problems such as inefficient extraction of data, loss of critical data, etc. when extracting the desired data from data of different data structure types. For example, taking request data as an example, parameters in the request data may be called as an entry, a data structure adopted by a previous service product is usually a request body (body), that is, the entry of a client and the entry of an application service are all from the body, and only required data need to be extracted from the body. However, with the rapid development of computers, a problem that occurs at present is that the participation mode of the protocol adopted by the client is not only from the body, but also from other participation types. And the manner of entry of the protocol employed by the application service may come from the body. For example, the data input by the client uses OAS description, where OAS is the OpenAPI Specification (Specification). OAS protocol is responsible for defining input interfaces (e.g., HTTP interfaces). Other types of entries may exist for the data described by the OAS, not only through the body, but also the Json Schema may only be the body, and when the body is converted and the entries are extracted from the body, the loss of other types of entries may be caused. And the data extraction efficiency is lower due to the different data structures.
In order to solve the above-mentioned problem, in the embodiment of the present invention, request data is received through a first interface of a data connection platform, and the request data is converted into converted request data described in Json Schema by adopting a request conversion rule corresponding to a protocol adopted by the request data. Because the data transmitted by the second interface of the data connection platform accords with the target Json Schema data structure, the structure consistency of the converted request data and the data transmitted by the second interface is realized by converting the request data into the converted request data described by the Json Schema. Because the data described by the Json Schema has the advantages of simplicity, easy understanding, better reading performance and the like, the Json Schema description is firstly converted on the request data, then under the same Json Schema description, the values of all the attributes in the target Json Schema data structure are searched from the converted request data consistent with the structure of the target Json Schema data structure, so that the data loss of the request data in the conversion process can be avoided, the values of all the attributes in the target Json Schema data structure can be quickly and accurately searched, and the data extraction efficiency and the obtained target request data can be more accurately and completely expressed.
In order to make the above objects, features and advantages of the embodiments of the present invention more comprehensible, the following detailed description of the embodiments of the present invention refers to the accompanying drawings.
The embodiment of the invention provides a data processing method of a data connection platform, which can be used for carrying out data processing on request data received by the data connection platform so as to obtain target request data described by Json Schema. The data processing method may be executed by the data connection platform, or may be executed by a connector, a Flow (Flow), or the like in the data connection platform, or may be executed by a terminal device, a server, or a cloud platform that carries the data connection platform, or the like.
In a specific implementation, the data connection platform has a plurality of first interfaces and second interfaces. The data transmitted by the first interface conforms to the definition of the data structure described by the OAS. The data transmitted by the second interface accords with the definition of the target Json Schema data structure. The second interface may be a connector, or may be a node in a Flow (Flow), or the like.
In some embodiments, the first interface may be used to connect to a client of a user to receive request data for the client. The protocols supported by each first interface may be different to suit the needs of different users.
The type of the first interface may be any of the following: hypertext transfer protocol (Hypertext Transfer Protocol, HTTP) interfaces, application programming (Application programming Interface) interfaces, web services (Webservice) interfaces, and the like.
The specific working principle and workflow of the data processing method will be described with reference to fig. 1. The data processing method may specifically include the following steps 11 to 13.
And step 11, receiving request data from a first interface, and converting the request data into converted request data described by Json Schema by adopting a request conversion rule corresponding to a protocol adopted by the request data.
And step 12, searching values of all the attributes in the target Json Schema data structure in the converted request data according to a request mapping rule to obtain target request data described by the Json Schema.
And step 13, outputting the target request data through the second interface.
From the above, the first interface of the data connection platform receives the request data, and uses the request conversion rule corresponding to the protocol adopted by the request data to convert the request data into the converted request data described by the Json Schema. Because the data output by the second interface of the data connection platform accords with the target Json Schema data structure, the structure consistency of the converted request data and the data output by the second interface is realized by converting the request data into the converted request data described by the Json Schema. Because the data described by the Json Schema has the advantages of simplicity, easy understanding, better reading performance and the like, the Json Schema description is firstly converted on the request data, then under the same Json Schema description, the values of all the attributes in the target Json Schema data structure are searched from the converted request data consistent with the structure of the target Json Schema data structure, so that the data loss of the request data in the conversion process can be avoided, the values of all the attributes in the target Json Schema data structure can be quickly and accurately searched, and the data extraction efficiency and the obtained target request data can be more accurately and completely expressed.
In addition, the data processing method can realize that the second interface described by the unified protocol is exposed to the application service, and the client side does not need to pay attention to the protocol adopted by the application service for the first interface, so that the protocol type of the application service is prevented from being exposed. Because the Json Schema has better universality, the compatibility and adaptability to different protocols can be improved.
In a specific implementation, each first interface is configured with a corresponding request conversion rule, and a corresponding relation between the first interface and the request conversion rule is established. For example, each first interface has a corresponding interface identifier, and the first interfaces are in one-to-one correspondence with the interface identifiers. And establishing a corresponding relation between the interface identifier of the first interface and the request conversion rule. The interface identifier may be an interface address, or may be identifier information of an interface. The protocol adapted by each first interface may be preconfigured, and the request conversion rule corresponding to each first interface is preconfigured according to the protocol supported by the first interface.
In one implementation of step 11, an interface identifier of the first interface may be identified, and a request conversion rule corresponding to the first interface is found according to the interface identifier of the first interface.
Because the data formats of different protocols are different, corresponding request conversion rules can be respectively configured for each different type of protocol, and the association relationship between the protocol and the corresponding request conversion rules is established. In another implementation of step 11, the data format of the request data may be identified to determine the protocol used by the request data, and further determine the request conversion rule corresponding to the protocol used by the request data.
The request data comprises a plurality of entry parameters, and a protocol adopted by the request data is defined with a plurality of entry parameter types. Each entry has a corresponding entry type.
For example, the request data includes HTTP request data. The entry type defined by the protocol employed by the HTTP request data includes at least one of: a request header parameter (header), a path parameter (path), a query parameter (query), and a request body parameter (body). I.e. may be entered by means of one or more of header, path, query or body types of entries. In other words, the entry may occur in the header, in the path, in the query, or in the body.
In one implementation of step 11, the request data may be converted into converted request data described by Json Schema by employing a request conversion rule corresponding to the protocol employed by the request data. Specifically, the plurality of entry types are used as attributes of the converted request data outermost layer object, and each entry is used as a next-level attribute of the corresponding attribute of the entry type.
In implementations, the data described by the Json Schema may have a hierarchy, i.e., be single-layered or multi-layered. And describing the data described by the Json Schema of the single layer by the attribute and the value corresponding to the attribute. For the data described by the Json Schema of multiple layers, for example, other objects can be nested in the object, other objects can be used as the attribute of the nested object, and multiple layers of nesting can be performed under the attribute by the mode of the next-level attribute. Each hierarchy is characterized by a set of brackets { }, which may also be referred to as curly brackets, etc. The hierarchy of the data described by the Json Schema, that is, the hierarchy of the attributes, is determined by determining the hierarchy between the multiple { }. Based on the characteristics that Json Schema describes data can be configured into a plurality of layers of data, the parameters and corresponding hierarchical relations in the request data can be reserved accurately and completely in the request data conversion process.
In some non-limiting embodiments, each attribute may also be an Object type, and thus each entry may be a next-level attribute of a corresponding attribute of the type of entry, and the value of the entry may be a value of the next-level attribute. Of course, the next-level attribute may also include its next-level attribute or the like, depending on the hierarchical relationship of the parameters included in the actual request data.
In some embodiments, the converted request data contains all the information in the request data to avoid information loss.
In some non-limiting embodiments, the OAS, when describing the requested data, includes not only the data related to the entry, but also other information defined by the first interface that is not related to the entry. In order to ensure that the obtained converted request data is not lost and is relatively concise, in some embodiments of the present invention, the request data may be filtered, and the entries included in the request data may be screened out.
For example, each entry has a preset format, and the request data is filtered according to the preset format to screen out entries contained in the request data.
For ease of understanding, the specific implementation of step 11 will be described using the HTTP request data described by the OAS protocol as an example.
The request data is as follows:
path: userName= zhangsan
header first name = Zhang Ying
query lastname=Zhang two
body：{
"email ":"xxx@qq.com",
"password":"123456",
"phone":"1311111111",
"userStatus":"OK"
}
The entry types in the request data are path, header, query and body, respectively. The colon of each entry type is followed by the entry and the value of the entry belonging to that entry type. The equal sign is preceded by an entry parameter and the equal sign is followed by the entry parameter. The bracket behind the colon of the body is the entered parameter and the entered parameter value in the body, the entered parameter and the entered parameter value are respectively added with double quotation marks and are separated by the colon, and a plurality of entered parameters are separated by commas.
The converted request data is as follows:
{
"path": {
"userName ": "zhangsan"
},
"header": {
"first name"
},
"query": {
"lastName": zhang Er "
},
"body": {
"email ": "xxx@qq.com",
"password": "123456",
"phone": "1311111111",
"userStatus": "OK"
}
}
In the converted request data, the attribute path, header, query and body of the outermost object are located in the outermost brackets, and double quotation marks are added respectively. The brackets behind the colon of the attribute of each outermost object are the next-level attribute and the value of the next-level attribute of the attribute, and the values of the next-level attribute and the next-level attribute are respectively added with double quotation marks and are separated by the colon. The body has a plurality of next-level attributes email, password, phone and userStatus, and the plurality of next-level attributes are separated by commas.
Specifically, path, header, query and body are attributes of the outermost object of the converted request data. userName is the next level attribute of the attribute path, and the value of the next level attribute userName is zhangsan. The first name is the next level attribute of the attribute header, and the value of the next level attribute first name is one. lastName is the next level attribute of attribute query, and the value of the next level attribute lastName is Zhang two. email, password, phone and userStatus are the next-level attributes of the attribute body, the value of the next-level attribute email is xxx@qq.com, the value of the next-level attribute password is 123456, the value of the next-level attribute phone is 1311111111, and the value of the next-level attribute userStatus is OK.
In one implementation of step 12, for each attribute in the target Json Schema data structure, according to the principle of the same path, searching for an attribute matched with the attribute in the target Json Schema data structure in the converted request data, and taking the value of the matched attribute as the value of the attribute in the target Json Schema data structure. Wherein, the same path may refer to the same Jsonpath. The paths are the same and used for representing the same hierarchy of the attributes, namely the attributes matched with the attributes in the target Json Schema data structure are searched in the attributes of the same hierarchy in the converted request data.
Each attribute in the target Json Schema data structure corresponds to one type of entry, and the value of each attribute in the target Json Schema data structure is searched from the converted request data, namely the value of the entry corresponding to the attribute is searched.
The number of attributes in the target Json Schema data structure may be preconfigured. The configuration of the attributes in the target Json Schema data structure may be implemented with a visualization interface. Specifically, an attribute configuration entry in the target Json Schema data structure can be presented to a user through a visual interface, and attributes in the target Json Schema data structure can be added, deleted or changed through the attribute configuration entry.
Further, each attribute in the converted request data is configured with a priority. The priority is used to define the order in which the various attributes in the converted request data are looked up.
In some embodiments, for each attribute in the target Json Schema data structure, the priority of each attribute in the converted request data may be configured separately. In other words, for different attributes in the Json Schema data structure, when matching attributes are found among the attributes in the converted request data, the order in which the attributes in the converted request data are found may be different. The priority of each attribute in the converted request data may be configured based on the probability that each attribute in the target Json Schema data structure appears in the converted request data.
According to the priority order of all the attributes in the converted request data from high to low, searching the attributes matched with the attributes in the target Json Schema data structure in the converted request data according to the principle of identical paths. In other words, for each attribute in the converted request data, the attribute having the same path is preferentially searched for among the attributes having higher priority.
And selecting the attribute of the target Json Schema data structure to be matched, starting matching from the attribute with the highest priority in the converted request data, and if the attribute with the highest priority is matched with the attribute of the target Json Schema data structure, not matching the rest attributes in the converted request data. If the attribute of the highest priority in the converted request data is not matched with the attribute of the target Json Schema data structure, continuing to match the attribute of the next priority in the converted request data until the attribute matched with the target Json Schema data structure is found or all the attributes in the converted request data are matched. When multiple entries are under the condition of renaming, the values of all the attributes of the target Json Schema data structure can be obtained efficiently and accurately by setting the priority.
For example, the target Json Schema data structure is { "id": "name": "," org ": { "name" }, the attributes in the target Json Schema data structure are "id", "name", and "org", respectively: { "name" }. Converting data into { "query": { "name" }, a "header": { "id" } "path": { "id" } "body": { "id", "name", "org": { "orgniame" } }, the attributes in the converted data are query, header, path and body, the next-level attribute of the attribute query is name, the next-level attribute of the attribute header is id, the next-level attribute of the attribute path is id, and the next-level attribute of the attribute body is id, name and org.
When searching the matching attribute of the attribute id in the target Json Schema data structure, the priority of the attribute in the converted request data is as follows in sequence from high to low: path, header, query and body. And for the attribute id in the target Json Schema data structure, according to the sequence of the attribute priority in the converted request data from high to low, adopting the principle of the same path, firstly matching from the attribute path in the converted request data, and at the moment, matching the attribute path in the converted request data with the attribute id in the target Json Schema data structure, so that the matching of the attribute header, query and body in the converted request data is not carried out. And taking the value of the attribute id of the next stage of the attribute path as the value of the attribute id in the target Json Schema data structure.
When searching the matching attribute of the attribute name in the target Json Schema data structure, the priority of the attribute in the converted request data is as follows in sequence from high to low: path, query, header and body. According to the same principle of the path, firstly, matching is carried out from the attribute path in the converted request data, and at the moment, the attribute path in the converted request data is not matched with the attribute name in the target Json Schema data structure. And matching the attribute query in the converted request data, wherein the attribute query in the converted request data is matched with the attribute name in the target Json Schema data structure, and the value of the next-stage attribute name of the attribute query in the converted request data is used as the value of the attribute name in the target Json Schema data structure.
In another implementation of step 12, a user-specified parameter entry mapping relationship is obtained, and for each attribute in the target Json Schema data structure, a value of the corresponding attribute is obtained from the converted request data according to the parameter entry mapping relationship. The mapping relation between each attribute in the converted request data and each attribute in the target Json Schema data structure is recorded in the parameter entering mapping relation.
The mapping relationship may include a mapping relationship on a path only, and the value of each attribute in the target Json Schema data structure is the value of the attribute in the converted request data with the mapping relationship. The mapping relation can also be adjusted by changing or modifying the value of the attribute in the converted request data through the expression, and the adjusted value is used as the value of the corresponding attribute in the target Json Schema data structure.
The configuration of the mapping relationship of the input parameters can be realized through a visual interface, specifically, the hierarchical relationship of each attribute of the converted request data and the hierarchical relationship of each attribute in the target Json Schema data structure can be presented to the user, and the mapping relationship between the two is specified by the user. The hierarchy of each attribute of the converted request data specified in the parameter-entering mapping relation and the hierarchy of the attribute in the target Json Schema data structure can be the same hierarchy or different hierarchies.
Continuing with the example above, the specified parameter-entry mapping relationship includes:
root.path.userName=root.userName；
root.header.firstName=root.firstName；
root.query.lastName=root.lastName；
root.body.email=root.email；
root.body.password=root.password；
root.body.phone=root.phone；
root.body.userStatus=root.userStatus。
the root is a root node and used for representing the outermost object in the path. The attributes of different levels are separated by symbol points, and the attribute after the points is the next-stage attribute of the attribute before the points. The path in the converted request data is in front of the equal sign, and the path in the target Json Schema data structure is in back of the equal sign. The equal sign characterizes that the paths at the two ends have a mapping relation. For example, the value of the attribute userName in the target Json Schema data structure is the value of the next-level attribute userName of the attribute path in the converted request data.
In a specific implementation, if the attribute of the target Json Schema data structure does not find a matched attribute in the converted request data, the value of the target Json Schema data structure, where the matched attribute is not found, is configured as a default value. Default values may be used to characterize that no corresponding entries exist in the request data. If the attributes in the target Json Schema data structure do not find the attributes which have the same path and are matched in the converted request data, the appointed parameter entering mapping relation does not appoint the attributes mapped by the attributes of the target Json Schema data structure in the converted request data, and the corresponding values of the attributes are configured as default values.
Parameters exposed through the second interface and compatibility of the parameter entry type of the parameters in the request data received by the first interface can be configured by configuring each attribute in the target Json Schema data structure. The extension of the supported application services can be achieved by configuring various attributes in the Json Schema data structure.
In practice, there may be situations where the user's needs change, such as the user increasing or decreasing some of the needs for application services. Such as increasing demand for credit variation, deleting demand for coupon issuance, etc. When the user demand changes, the target Json Schema data structure can be updated through the visual interface, for example, the attribute in the target Json Schema data structure is updated, so as to adjust the parameter input in the target request data output by the second interface.
In specific implementation, when update information of the target Json Schema data structure is received, updating the target Json Schema data structure based on the update information.
The method can compare each attribute in the updated target Json Schema data structure with each attribute in the target Json Schema data structure before updating, find out different attributes, present the different attributes to a user through a visual interface, and supplement and assign the different attributes to the parameter mapping relationship through the visual interface by the user.
In specific implementation, receiving first interface creation information, wherein the first interface creation information comprises an interface identifier of a created first interface and a request conversion rule of the created first interface; a corresponding first interface is created and an association between the created first interface and the request conversion rule is established.
In some embodiments, a new first interface may be created by a user through a visual interface.
In specific implementation, response data corresponding to the request data is obtained, and the response data is converted into converted response data described by Json Schema in OAS by adopting a response conversion rule. And searching values of all the attributes in the data structure of the OAS description in the converted response data according to the response mapping rule to obtain target response data of the OAS description. And outputting the target response data through the first interface.
For example, using a connector as an example, the connector executes the target request data and obtains corresponding response data. And obtaining response data of the request data.
In a specific implementation, the target response data includes a plurality of parameters, and a protocol adopted by the target response data defines a plurality of parameter types. Each of the parameter-out has a corresponding parameter-out type.
In a specific implementation, determining the parameter-out type corresponding to each parameter-out in the response data, taking the parameter-out types as the attribute of the outermost object of the converted response data, and taking each parameter-out as the next-stage attribute of the corresponding attribute of the parameter-out type to obtain the converted response data.
For example, the response data includes HTTP response data. The type of parameter-out defined by the protocol employed by the HTTP response data includes at least one of: a request header parameter (header), a request body parameter (body). I.e. may be made by means of one or more of the types of making a reference from the header or body. In other words, the out-references may appear in the header or in the body.
In some embodiments, the parameter-out type corresponding to each parameter-out in the response data is determined, the parameter-out types are used as the attribute of the outermost object of the converted response data, and each parameter-out is used as the next-stage attribute of the corresponding attribute of the parameter-out type to obtain the converted response data.
In other embodiments, a user-specified out-of-reference mapping relationship is obtained, and for each attribute in the OAS-described data structure, values of corresponding attributes are obtained from the converted response data according to the out-of-reference mapping relationship, so as to obtain target response data of the OAS description. The parameter-out mapping rule may include a parameter-out mapping relation.
The processing of response data is described below with reference to examples.
The response data are as follows:
{
"id":"1",
"userName ":"zhangsan",
"first name": one ",
"lastName": "Zhang Er",
"email ":"xxx@qq.com",
"password":"123456",
"phone":"1311111111",
"userStatus":"OK"
}
the attribute id, userName, firstName, lastName, email, password, phone of the outermost object in the response data and userStatus are located in the outermost bracket, and double quotation marks are added respectively. The value of the attribute of each outermost object is added with a double quote and separated by a colon and is located after the colon. Comma separation is adopted among a plurality of attributes.
The response data is converted into converted response data described by Json Schema in OAS by using a response conversion rule as follows:
{
"header": {
"id": 1
},
"body": {
"userName ": "zhangsan",
"first name": a first ",
"lastName": "Zhang Er",
"email ": "xxx@qq.com",
"password": "123456",
"phone": "1311111111",
"userStatus": "OK"
}
}
in the converted response data, the header and the body are the parameter-out type, and the parameter-out type is used as the attribute of the outermost object and is positioned in the outermost bracket, and double quotation marks are added. The contents in brackets after the colon after the ginseng type are the ginseng and the ginseng value under the ginseng type, and the ginseng value are respectively added with double quotation marks and separated by the colon. Comma separation is adopted among a plurality of ginseng under the same ginseng type.
According to a response mapping rule, searching values of all attributes in the data structure of the OAS description in the converted response data to obtain target response data of the OAS description, wherein the target response data comprises the following steps:
header:id = 1
body:
{
"userName ":"zhangsan",
"first name": a first ",
"lastName": "Zhang Er",
"email ":"xxx@qq.com",
"password":"123456",
"phone":"1311111111",
"userStatus":"OK"
}
the target response data comprises a parameter-outputting type header and a body, wherein the parameter-outputting type and the parameter-outputting belonging to the parameter-outputting type are separated by a colon, and the parameter-outputting values are equal. For the ginseng in body, the ginseng is placed in brackets, the value of each ginseng is added with double quotation marks, and the ginseng is separated by a colon, and a plurality of ginseng is separated by commas.
The response conversion rule adopted is as follows:
root.id = root.header.id；
root.userName= root.header.userName；
MatrixVariable("root.firstName", "String", "fqn")+".first" = root.body.firstName；
root.lastName= root.body.lastName；
root.email= root.body.email；
root.password= root.body.password；
root.phone= root.body.phone；
root.userStatus= root.body.userStatus。
the root is a root node and used for representing the outermost object in the path. The attributes of different levels are separated by symbol points, and the attribute after the points is the next-stage attribute of the attribute before the points. The equal sign is preceded by a path in the converted response data and followed by a path in the target response data. The equal sign characterizes that the paths at the two ends have a mapping relation. For example, the value of the attribute userName in the converted response data is the value of the attribute userName of the next stage of attribute header in the target response data.
In implementations, the data connection platform may provide a visualization interface where configuration entries for request transformation rules and request mapping rules may be provided. A user (e.g., project personnel, developer, maintenance personnel, etc.) may configure the request conversion rule through a configuration portal requesting the conversion rule, and may configure the request mapping rule through a configuration portal requesting the mapping rule.
The visual interface is provided with a first configuration item and a second configuration item. In the first configuration item, parameters and parameter entry types included in the request data may be selected. And in the second configuration item, a corresponding second interface can be selected, a target Json Schema data structure corresponding to the second interface is configured, and the attribute in the target Json Schema data structure is specified.
The information such as parameters and entry types included in the request data can be obtained according to metadata description of an original OAS description protocol, wherein the metadata description is used for describing a data structure of the request data and a structure of response data. The definitions of the entry type, entry, and entry value of the request data are described in the metadata, and the definitions of the exit type, exit, and exit value of the response data. Accordingly, the response data also has a corresponding metadata description. The following is an example.
For example, metadata of the original OAS description protocol is described as follows:
{"/user/{username}":{"get":{"tags":["user"],"summary":"create","description":"","operationId":"createUser","parameters":[{"name":"username","in":"path","required":true,"schema":{"type":"string"}},{"name":"firstName","in":"header","required":true,"schema":{"type":"string"}},{"name":"lastName","in":"query","required":true,"schema":{"type":"string"}}],"requestBody":{"content":{"application/json":{"schema":{"type":"object","properties":{"email":{"type":"string"},"password":{"type":"string"},"phone":{"type":"string"},"userStatus":{"type":"integer"}}}}}},"responses":{"200":{"description":"successful operation","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string"},"userName":{"type":"string"},"firstName":{"type":"string"},"lastName":{"type":"string"},"email":{"type":"string"},"password":{"type":"string"},"phone":{"type":"string"},"userStatus":{"type":"integer"}}}}}}}}}}。
according to the principle that the plurality of entry types are used as the attribute of the outermost object of the converted request data, each entry is used as the next attribute of the corresponding attribute of the entry type, and the metadata of the converted request data described by the Json Schema obtained by conversion is described as follows:
{"type":"object","properties":{"query":{"type":"object","roperties":{"username":{"type":"string"}}},"path":{"type":"object","roperties":{"username":{"type":"string"}}},"header":{"type":"object","roperties":{"id":{"type":"string"}}},"body":{"type":"object","properties":{"firstName":{"type":"string"},"lastName":{"type":"string"},"email":{"type":"string"},"password":{"type":"string"},"phone":{"type":"string"},"userStatus":{"type":"integer"}}}}}。
According to the principle that the parameter types corresponding to the parameter types in the response data are determined respectively, the parameter types are used as the attribute of the object at the outermost layer of the converted response data, the parameter types are used as the next-level attribute of the corresponding attribute of the parameter type, and the metadata of the response data described by the Json Schema obtained through conversion are described as follows:
{"type":"object","properties":{"path":{"type":"object","roperties":{"username":{"type":"string"}}},"header":{"type":"object","roperties":{"firstName":{"type":"string"}}},"query":{"type":"object","roperties":{"lastName":{"type":"string"}}},"body":{"type":"object","properties":{"email":{"type":"string"},"password":{"type":"string"},"phone":{"type":"string"},"userStatus":{"type":"integer"}}}}}。
metadata of the target request data described by Json Schema of the second interface is described as follows:
{"type":"object","properties":{"userName":{"type":"string"},"firstName":{"type":"string"},"lastName":{"type":"string"},"email":{"type":"string"},"password":{"type":"string"},"phone":{"type":"string"},"userStatus":{"type":"integer"}}}。
metadata of response data described by Json Schema of the second interface is described as follows:
{"type":"object","properties":{"id":{"type":"string"},"userName":{"type":"string"},"firstName":{"type":"string"},"lastName":{"type":"string"},"email":{"type":"string"},"password":{"type":"string"},"phone":{"type":"string"},"userStatus":{"type":"integer"}}}。
wherein, the format description of the metadata description is described, wherein, the content in the outermost bracket is the description of the outermost object, and the definitions of type and specific type are respectively added with double quotation marks and separated by colon marks. Comma separation is adopted between the type and the attribute properties of the object. The attributes properties and the specific defined attributes are separated by commas, a layer of brackets is added to the specific attributes, commas are used for separation between each attribute, specific definition description of the attribute is placed in the layer of brackets, a colon is used for separation between the next-level attribute of each attribute and the definition of the value of the next attribute in the brackets, double quotations are added to the next-level attribute, the definition of the value of the next-level attribute is placed in the layer of brackets, double quotations are added to the types of the values and the types of the specific definitions respectively, the commas are used for separation between the different attributes.
In a specific implementation, the converted request data format and the related attribute information can be obtained through the above metadata description of the converted request data, the data format of the target request data and the related attribute information can be obtained through the metadata description of the target request data, and the attribute information can be displayed through a visual interface.
Referring to fig. 2, the configuration of request mapping rules and the configuration of response mapping rules may be performed at a visualization interface. The following describes an example of the configuration of the request mapping rule.
In the first configuration item, the attribute of the converted request data described by the Json Schema can be selected, and related information of the attribute is displayed. In the second configuration item, an attribute of the target request data may be selected, and related information of the attribute may be displayed.
For example, referring to fig. 2, the attribute path of the converted request data and the next-level attribute fqn described by the Json Schema may be selected by the array filtering configuration item, where the root is used to characterize that the attribute path is an attribute of the outermost object. string refers to the next level of attribute fqn having a string of values. Attributes for the target request data in the second configuration item include a membership Id (membersid), a loyalty account Id (pointAccountId), and an expiration reminder Id (remindId). Wherein string refers to the value of attribute memberld as a character string, integer refers to the value of attribute poiintaccoutid and the value of attribute remindId as integer data.
The attributes having the request mapping relationship illustrated in fig. 2 may be arranged in the same row, and the request mapping relationship is path.fqn=memberid, fqn + "12345" =poiintaccoutid, path.fqn=remindid. Wherein fqn + "12345" refers to the value obtained by adding 12345 to fqn as the value of pointacoutid.
Pages may be saved and closed after configuration is complete. When the response mapping rule needs to be configured, switching to the response mapping configuration rule page for configuration.
Fig. 2 is a schematic view showing a visual interface, and the gray background color in fig. 2 does not have a specific meaning.
It should be noted that, the above description is given by taking the scenario of inquiring the expired point reminder as an example, and in practice, the configuration of the request mapping rule is slightly different according to the different application scenario requirements, which is not exemplified here.
Because the data structure described by the Json Schema has the advantages of simplicity, easy understanding, better readability and the like, a user can easily perform operations such as attribute matching in the request conversion rule, which also becomes possible for visualizing configuration request conversion rule, request mapping rule, response conversion rule and response mapping rule, and the user can adapt to the change of the user requirement by adjusting the attribute in the target Json Schema data structure without modifying the codes related to the first interface and the second interface.
In the visual interface, an automatic searching button can be configured, and the matching of the attributes in the converted request data and the attributes in the target Json Schema data structure can be automatically completed in response to the triggering of the automatic searching button by a user. The automatic searching key can be packaged with a corresponding attribute matching rule, and the attribute matching rule can be preconfigured, for example, the attribute matching rule is to match according to the principle of the same path, and for example, the matching rule is to adopt the principle of the same path according to the sequence of the priority of each attribute in the converted request data from high to low.
And displaying the matching result of the attribute of the converted request data and the attribute in the target Json Schema data structure through a visual interface. For example, the matching attributes may be displayed in the same row.
If the automatically found matching result is not the expected result, the matching result can be manually adjusted by a user through a visual interface, and the adjusted mapping relationship is saved as the mapping relationship of the input parameters.
The embodiment of the invention also provides a data processing device of the data processing platform, the data connection platform is provided with a plurality of first interfaces and second interfaces, the data transmitted by the first interfaces accords with the definition of the data structure described by the OAS, and the data transmitted by the second interfaces accords with the definition of the target Json Schema data structure. Referring to fig. 3, the data processing apparatus 30 includes: a conversion unit 31, configured to receive request data from a first interface, and convert the request data into converted request data described by Json Schema by using a request conversion rule corresponding to a protocol adopted by the request data; the processing unit 32 is configured to search values of each attribute in the target Json Schema data structure in the converted request data according to a request mapping rule, so as to obtain target request data described by the Json Schema; an output unit 33, configured to output the target request data through the second interface.
In a specific implementation, the data processing device 30 of the data processing platform may further include units corresponding to the steps for implementing the above data processing method, and for the specific working principle and specific working procedure of the data processing device 30 of the data processing platform, reference may be made to the description of the data processing method in the above embodiment, which is not repeated herein.
The embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor performs the steps of the data processing method of the data connection platform provided by any of the above embodiments of the present invention.
The computer readable storage medium may include non-volatile memory (non-volatile) or non-transitory memory, and may also include optical disks, mechanical hard disks, solid state disks, and the like.
The embodiment of the invention also provides a server, which comprises a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the steps of the data processing method of the data connection platform provided by any embodiment when running the computer program.
The memory is coupled to the processor, and the memory may be located inside the server or outside the server. The memory and the processor may be connected by a communication bus.
The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions described in accordance with the embodiments of the present application are all or partially produced.
In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus, and system may be implemented in other manners. For example, the device embodiments described above are merely illustrative; for example, the division of the units is only one logic function division, and other division modes can be adopted in actual implementation; for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may be physically included separately, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units. For example, for each device or product applied to or integrated on a chip, each module/unit included in the device or product may be implemented in hardware such as a circuit, or at least part of the modules/units may be implemented in software program, where the software program runs on a processor integrated inside the chip, and the rest (if any) of the modules/units may be implemented in hardware such as a circuit; for each device and product applied to or integrated in the chip module, each module/unit contained in the device and product can be realized in a hardware manner such as a circuit, different modules/units can be located in the same component (such as a chip, a circuit module and the like) or different components of the chip module, or at least part of the modules/units can be realized in a software program, the software program runs on a processor integrated in the chip module, and the rest (if any) of the modules/units can be realized in a hardware manner such as a circuit; for each device, product, or application to or integrated with the terminal, each module/unit included in the device, product, or application may be implemented by using hardware such as a circuit, different modules/units may be located in the same component (for example, a chip, a circuit module, or the like) or different components in the terminal, or at least part of the modules/units may be implemented by using a software program, where the software program runs on a processor integrated inside the terminal, and the remaining (if any) part of the modules/units may be implemented by using hardware such as a circuit.
It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In this context, the character "/" indicates that the front and rear associated objects are an "or" relationship.
The term "plurality" as used in the embodiments herein refers to two or more.
It should be noted that the serial numbers of the steps in the present embodiment do not represent a limitation on the execution sequence of the steps.
Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be made by one skilled in the art without departing from the spirit and scope of the invention, and the scope of the invention should be assessed accordingly to that of the appended claims.
Claims (13)
1. A data processing method of a data connection platform, wherein the data connection platform has a plurality of first interfaces and second interfaces, data transmitted by the first interfaces conform to a definition of a data structure described by OAS, and data transmitted by the second interfaces conform to a definition of a target Json Schema data structure, the data processing method comprising:
Receiving request data from a first interface, and converting the request data into converted request data described by a Json Schema by adopting a request conversion rule corresponding to a protocol adopted by the request data;
according to a request mapping rule, searching values of all attributes in the target Json Schema data structure in the converted request data to obtain target request data described by the Json Schema;
outputting the target request data through the second interface;
the request data includes a plurality of entries, a protocol adopted by the request data defines a plurality of entry types, and a request conversion rule corresponding to the protocol adopted by the request data is adopted to convert the request data into converted request data described by Json Schema, which includes:
and taking the multiple entry types as attributes of the converted request data outermost layer object, and taking each entry as a next-level attribute of the corresponding attribute of the entry type to which the entry belongs.
2. The data processing method of claim 1, wherein the enrollment has a preset format, the data processing method further comprising: and filtering the request data according to the preset format to screen out the entry contained in the request data.
3. The data processing method according to claim 1, wherein searching values of each attribute in the target Json Schema data structure in the converted request data according to a request mapping rule to obtain target request data described by Json Schema comprises:
searching for an attribute matched with the attribute in the target Json Schema data structure in the converted request data according to the principle of the same path, and taking the value of the matched attribute as the value of the attribute in the target Json Schema data structure to obtain target request data described by the Json Schema;
and/or acquiring a parameter entry mapping relation appointed by a user, and acquiring values of corresponding attributes from the converted request data according to the parameter entry mapping relation for each attribute in the target Json Schema data structure so as to acquire target request data described by the Json Schema.
4. The data processing method according to claim 3, wherein each attribute in the converted request data is configured with a priority, and the searching the converted request data for the value of each attribute in the target Json Schema data structure includes:
And searching the attributes matched with the attributes in the target Json Schema data structure in the converted request data according to the order of the priority from high to low and by adopting the principle of identical paths.
5. A data processing method according to claim 3, further comprising:
and if the matched attribute is not found in the converted request data for the attribute of the target Json Schema data structure, configuring the value of the matched attribute which is not found in the target Json Schema data structure as a default value.
6. The data processing method of claim 1, further comprising: and when receiving update information of the target Json Schema data structure, updating the target Json Schema data structure based on the update information.
7. The data processing method according to claim 1, wherein the request conversion rule corresponding to the protocol employed by the request data is determined by:
identifying an interface identifier of the first interface;
searching request conversion rules corresponding to the first interfaces according to the interface identifiers of the first interfaces, wherein each request conversion rule corresponding to the first interfaces is preconfigured according to a protocol supported by the first interfaces.
8. The data processing method of claim 1, further comprising:
response data corresponding to the request data are obtained, and the response data are converted into converted response data described by Json Schema in OAS by adopting a response conversion rule;
according to a response mapping rule, searching values of all attributes in the data structure of the OAS description in the converted response data to obtain target response data of the OAS description;
and outputting the target response data through the first interface.
9. The data processing method of claim 8 wherein the target response data includes a plurality of arguments, the protocol employed by the target response data defining a plurality of argument types, the employing response transformation rules to transform the response data into transformed response data described by Json Schema in OAS, comprising:
and determining the parameter-out type corresponding to each parameter-out in the response data, taking the parameter-out types as the attribute of the outermost object of the converted response data, and taking each parameter-out as the next-stage attribute of the corresponding attribute of the parameter-out type to obtain the converted response data.
10. The data processing method of claim 9, wherein said looking up values of each attribute in the data structure of the OAS description in the converted response data according to response mapping rules to obtain target response data of the OAS description, comprises:
According to each attribute in the OAS description data structure and the principle of identical path, searching the value of the attribute in the OAS description data structure in the converted response data to obtain target response data of the OAS description;
and/or acquiring a parameter-out mapping relation designated by a user, and acquiring values of corresponding attributes from the converted response data according to the parameter-out mapping relation for each attribute in the data structure of the OAS description so as to acquire target response data of the OAS description.
11. A data processing apparatus of a data processing platform, wherein the data connection platform has a plurality of first interfaces and second interfaces, data transmitted by the first interfaces conforms to a definition of a data structure described by OAS, and data transmitted by the second interfaces conforms to a definition of a target Json Schema data structure, the data processing apparatus comprising:
the conversion unit is used for receiving request data from the first interface, and converting the request data into converted request data described by the Json Schema by adopting a request conversion rule corresponding to a protocol adopted by the request data;
the processing unit is used for searching values of all the attributes in the target Json Schema data structure in the converted request data according to a request mapping rule so as to obtain target request data described by the Json Schema;
An output unit configured to output the target request data through the second interface;
the request data comprises a plurality of entries, a protocol adopted by the request data is defined with a plurality of entry types, and the conversion unit is used for taking the plurality of entry types as attributes of the outermost layer object of the converted request data and taking each entry as a next-level attribute of the corresponding attribute of the entry type.
12. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, performs the steps of the data processing method of any one of claims 1 to 10.
13. A server comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, characterized in that the processor executes the steps of the data processing method according to any of claims 1 to 10 when the computer program is executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410053502.4A CN117573762B (en) | 2024-01-15 | 2024-01-15 | Data processing method and device of data connection platform, storage medium and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410053502.4A CN117573762B (en) | 2024-01-15 | 2024-01-15 | Data processing method and device of data connection platform, storage medium and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117573762A CN117573762A (en) | 2024-02-20 |
| CN117573762B true CN117573762B (en) | 2024-04-16 |
Family
ID=89862727
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410053502.4A Active CN117573762B (en) | 2024-01-15 | 2024-01-15 | Data processing method and device of data connection platform, storage medium and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117573762B (en) |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908541A (en) * | 2017-07-26 | 2018-04-13 | 平安壹钱包电子商务有限公司 | Interface test method, device, computer equipment and storage medium |
| JP2018536935A (en) * | 2015-12-08 | 2018-12-13 | アリババ グループ ホウルディング リミテッド | Access request conversion method and apparatus |
| CN110275831A (en) * | 2019-06-18 | 2019-09-24 | 广州华多网络科技有限公司 | The mock data verification method and device of protocol interface |
| US10719503B1 (en) * | 2019-05-02 | 2020-07-21 | Servicenow, Inc. | Interface for supporting integration with cloud-based service providers |
| CN111475449A (en) * | 2020-03-05 | 2020-07-31 | 浪潮金融信息技术有限公司 | HIS system and external program interface adaptation method, system, interface adapter and comprehensive medical system |
| CN112379951A (en) * | 2020-11-19 | 2021-02-19 | 北京百度网讯科技有限公司 | Service interface access method, device, electronic equipment and medium |
| CN112650804A (en) * | 2020-12-30 | 2021-04-13 | 苏州科达科技股份有限公司 | Big data access method, device, system and storage medium |
| CN112883022A (en) * | 2021-03-18 | 2021-06-01 | 武汉众邦银行股份有限公司 | XML template-based object data cleaning and converting method |
| CN113079198A (en) * | 2021-03-18 | 2021-07-06 | 青岛海信智慧生活科技股份有限公司 | Method and device for converting cloud platform interface protocol |
| CN114116510A (en) * | 2021-12-03 | 2022-03-01 | 深圳前海微众银行股份有限公司 | Interface parameter checking method and device |
| CN114528044A (en) * | 2022-02-17 | 2022-05-24 | 深圳乐信软件技术有限公司 | Interface calling method, device, equipment and medium |
| US11347732B1 (en) * | 2019-10-01 | 2022-05-31 | Software Tree, LLC | JSON persistence service |
| CN115827084A (en) * | 2022-09-28 | 2023-03-21 | 中国建设银行股份有限公司 | Data processing method, device, equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9584632B2 (en) * | 2013-08-28 | 2017-02-28 | Wipro Limited | Systems and methods for multi-protocol translation |
-
2024
- 2024-01-15 CN CN202410053502.4A patent/CN117573762B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2018536935A (en) * | 2015-12-08 | 2018-12-13 | アリババ グループ ホウルディング リミテッド | Access request conversion method and apparatus |
| CN107908541A (en) * | 2017-07-26 | 2018-04-13 | 平安壹钱包电子商务有限公司 | Interface test method, device, computer equipment and storage medium |
| US10719503B1 (en) * | 2019-05-02 | 2020-07-21 | Servicenow, Inc. | Interface for supporting integration with cloud-based service providers |
| CN110275831A (en) * | 2019-06-18 | 2019-09-24 | 广州华多网络科技有限公司 | The mock data verification method and device of protocol interface |
| US11347732B1 (en) * | 2019-10-01 | 2022-05-31 | Software Tree, LLC | JSON persistence service |
| CN111475449A (en) * | 2020-03-05 | 2020-07-31 | 浪潮金融信息技术有限公司 | HIS system and external program interface adaptation method, system, interface adapter and comprehensive medical system |
| CN112379951A (en) * | 2020-11-19 | 2021-02-19 | 北京百度网讯科技有限公司 | Service interface access method, device, electronic equipment and medium |
| CN112650804A (en) * | 2020-12-30 | 2021-04-13 | 苏州科达科技股份有限公司 | Big data access method, device, system and storage medium |
| CN113079198A (en) * | 2021-03-18 | 2021-07-06 | 青岛海信智慧生活科技股份有限公司 | Method and device for converting cloud platform interface protocol |
| CN112883022A (en) * | 2021-03-18 | 2021-06-01 | 武汉众邦银行股份有限公司 | XML template-based object data cleaning and converting method |
| CN114116510A (en) * | 2021-12-03 | 2022-03-01 | 深圳前海微众银行股份有限公司 | Interface parameter checking method and device |
| CN114528044A (en) * | 2022-02-17 | 2022-05-24 | 深圳乐信软件技术有限公司 | Interface calling method, device, equipment and medium |
| CN115827084A (en) * | 2022-09-28 | 2023-03-21 | 中国建设银行股份有限公司 | Data processing method, device, equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| Internet of Things Multi-protocol Interoperability with Syntactic Translation Capability;Ahmed, N.H etc.;《INTERNATIONAL JOURNAL OF ADVANCED COMPUTER SCIENCE AND APPLICATIONS》;20221101;第610-620页 * |
| 基于Charles录制会话的HTTP接口自动化测试框架设计与实现;刘国庆 等;《计算机应用与软件》;20190630;第7-13页 * |
| 增值业务多外部接口协议转换器的设计与实现;周志鹏;《中国优秀硕士学位论文全文数据库（信息科技辑）》;20110315;第I136-312页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117573762A (en) | 2024-02-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10922341B2 (en) | Non-tabular datasource connector | |
| US11269872B1 (en) | Intent-based natural language processing system | |
| US10169434B1 (en) | Tokenized HTTP event collector | |
| US20130054707A1 (en) | Online monitoring for customer service | |
| WO2017156916A1 (en) | Data access method and device | |
| WO2017120814A1 (en) | Method and system for managing resource objects | |
| CN109683998A (en) | Internationalize implementation method, device and system | |
| US11841834B2 (en) | Method and apparatus for efficient synchronization of search heads in a cluster using digests | |
| CN112671950B (en) | Domain name processing method and device based on block chain, electronic equipment and storage medium | |
| CN112732572A (en) | Service testing method, device and system, storage medium and electronic device | |
| CN111651639B (en) | Address space management method, device, equipment and medium | |
| CN113626223A (en) | Interface calling method and device | |
| US20140237485A1 (en) | System and method for aggregate data from multiple sources to provide a single cim object | |
| CN113641700A (en) | Data processing method and device based on Spring boot frame | |
| CN101645935B (en) | Web service combined method based on QoS indexes and Web service output parameters and device thereof | |
| CN110334103A (en) | The update method of recommendation service provides device, access mechanism and recommender system | |
| CN117573762B (en) | Data processing method and device of data connection platform, storage medium and server | |
| CN116048517B (en) | API (application program interface) generating method, system and device based on B/S (browser/Server) architecture application system | |
| CN113157904A (en) | Sensitive word filtering method and system based on DFA algorithm | |
| US20220050851A1 (en) | Enabling dynamic data capture with database objects | |
| CN114996246A (en) | Data cleaning method for checking multiple fields of table based on NiFi assembly | |
| WO2022041280A1 (en) | Method and apparatus for generating file in internet of things, computer device, and storage medium | |
| US20130103724A1 (en) | Network and method for managing models | |
| CN112835573A (en) | Data query method and device, electronic equipment and storage medium | |
| CN117580074B (en) | Network management adaptation system and method of dual-mode base station |
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 | ||
| GR01 | Patent grant |