CN117395314A

CN117395314A - Request processing method, request processing device, electronic equipment and storage medium

Info

Publication number: CN117395314A
Application number: CN202311337618.2A
Authority: CN
Inventors: 李浩然; 冯伟伦; 麦倩; 吴尚艳
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-10-16
Filing date: 2023-10-16
Publication date: 2024-01-12

Abstract

The disclosure provides a request processing method, a request processing device, electronic equipment and a storage medium, which can be applied to the distributed technical field and the financial technical field. The method comprises the following steps: in response to receiving a request to be processed of a first external system, determining target entity classes corresponding to M fields to be requested included in the request to be processed, wherein M is an integer greater than or equal to 1; invoking at least one target method corresponding to each of the M target entity classes; and processing the request to be processed by using at least one target method to obtain processing information.

Description

Request processing method, request processing device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of distributed technology and the field of financial technology, and in particular, to a request processing method, apparatus, electronic device, medium, and program product.

Background

Because the business objectives of the organizations are different, the respective systems of the organizations may coexist in multiple system architectures. In this case, a communication area is defined in each system of each institution for data interaction with other external systems.

In the process of implementing the inventive concept of the present disclosure, the inventors found that accuracy of processing information and efficiency of request processing are low.

Disclosure of Invention

In view of the foregoing, the present disclosure provides a request processing method, apparatus, electronic device, medium, and program product.

According to a first aspect of the present disclosure, there is provided a request processing method, including: in response to receiving a request to be processed of a first external system, determining target entity classes corresponding to M fields to be requested included in the request to be processed, wherein M is an integer greater than or equal to 1; invoking at least one target method corresponding to each of the M target entity classes; and processing the request to be processed by using at least one target method to obtain processing information.

According to an embodiment of the present disclosure, determining a target entity class corresponding to each of M fields to be requested included in a request to be processed includes: calling a mapping routine; and obtaining target entity classes corresponding to the M fields to be requested respectively according to the M fields to be requested included in the request to be processed based on the mapping routine.

According to an embodiment of the present disclosure, based on a mapping routine, obtaining, from M fields to be requested included in a request to be processed, target entity classes corresponding to the M fields to be requested, respectively, includes: for each of the M fields to be requested, determining a field matching the field to be requested from a predetermined set of associations using a mapping routine; based on the mapping routine, determining a preset association relation corresponding to the field to be requested according to the field matched with the field to be requested; obtaining a target entity class corresponding to the field to be requested according to a preset association relation corresponding to the field to be requested; the predetermined association relation set comprises N predetermined association relations, wherein the predetermined association relations represent association relations between fields and entity classes, and N is an integer greater than or equal to 1.

According to an embodiment of the present disclosure, the request response method further includes: responding to a field adding request received by a second external system, and analyzing the field adding request to obtain a field to be added; and updating the predetermined association relation set by using the field to be added.

According to an embodiment of the present disclosure, updating a predetermined association relationship set with a field to be added includes: determining an entity class corresponding to the field to be added; and creating an association relation between the field to be added and the entity class corresponding to the field to be added to obtain a newly added preset association relation so as to update the preset association relation set.

According to an embodiment of the present disclosure, based on a mapping routine, obtaining, from M fields to be requested included in a request to be processed, target entity classes corresponding to the M fields to be requested, respectively, includes: for each field to be requested in the M fields to be requested, extracting features of the fields to be requested by using a mapping routine to obtain field feature information; and processing the field characteristic information by using a mapping routine to obtain a target entity class corresponding to the field to be requested.

According to an embodiment of the present disclosure, processing a request to be processed using at least one target method to obtain processing information includes: under the condition that the at least one third external system is required to be called according to the current method corresponding to the current field to be requested, converting the current field to be requested into a matching request field matched with each of the at least one third external system by utilizing the current method corresponding to the current field to be requested; converting the feedback fields corresponding to the at least one third external system into target fields corresponding to target entity classes corresponding to the fields to be requested currently by using the current method corresponding to the fields to be requested currently in response to receiving the feedback fields corresponding to the at least one third external system respectively, wherein the feedback fields are obtained by the third external system according to the matching request fields; obtaining processing information corresponding to a current method corresponding to the current field to be requested according to a target field corresponding to a target entity class corresponding to the current field to be requested; the current fields to be requested are determined from M fields to be requested according to the association relation among the M fields to be requested; the current method is determined from at least one target method corresponding to the current field to be requested according to the calling relation between at least one target method corresponding to the current field to be requested.

According to an embodiment of the present disclosure, the request response method further includes: and under the condition that the fact that at least one third external system is not required to be called is determined according to the current method corresponding to the current field to be requested, the current field to be requested is processed by the current method corresponding to the current field to be requested, and processing information corresponding to the current method corresponding to the current field to be requested is obtained.

According to an embodiment of the present disclosure, the request response method further includes: and associating the feedback field corresponding to each of the at least one third external system with the target entity class corresponding to the current field to be requested so that other methods can obtain a preset feedback field under the condition of calling the target entity class corresponding to the current field to be requested, wherein the preset feedback field is a feedback field in the feedback field corresponding to each of the at least one third external system.

A second aspect of the present disclosure provides a request processing apparatus, including: the determining module is used for determining target entity classes corresponding to M fields to be requested respectively, wherein the M is an integer greater than or equal to 1, included in a request to be processed in response to receiving the request to be processed of the first external system; the calling module is used for calling at least one target method corresponding to each of the M target entity classes; and the processing module is used for processing the request to be processed by utilizing at least one target method to obtain processing information.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method described above.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described method.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above method.

According to the request processing method, the device, the electronic equipment, the medium and the program product provided by the disclosure, under the condition that the request to be processed of the first external system is received, the target entity class corresponding to each of M fields to be requested included in the request to be processed is determined, and the conversion of the fields to be requested into the target entity class is realized, so that the number of fields with different business meanings generated due to interaction with the communication area of the first external system can be reduced, and the accuracy of acquiring the fields is improved. On the basis, the processing information is obtained by processing the request to be processed by utilizing at least one target method corresponding to each of M target entity classes, and the accuracy of the processing information and the request processing efficiency are improved.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of a request processing method according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow chart of a request processing method according to an embodiment of the disclosure;

FIG. 3 schematically illustrates a schematic diagram of processing fields according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates a schematic diagram of processing fields according to another embodiment of the present disclosure;

FIG. 5 schematically illustrates a block diagram of a request processing apparatus according to an embodiment of the present disclosure; and

fig. 6 schematically illustrates a block diagram of an electronic device adapted to implement a request processing method according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the technical scheme of the disclosure, the related data (such as including but not limited to personal information of a user) are collected, stored, used, processed, transmitted, provided, disclosed, applied and the like, all conform to the regulations of related laws and regulations, necessary security measures are adopted, and the public welcome is not violated.

Because the core system has more interaction with other external core systems, the core system has the problem that various communication area fields point to the same business meaning. For example: the communication area field of the mechanism system, the communication area field of the application in the mechanism, the communication area field of the platform, the communication area field of the host computer and the like. Wherein the core system and the external core system may both be distributed systems. Based on the above, after the core system performs data interaction with the external communication area, fields with different names, fields with different storage structures and the like can be generated, the fields can reduce the code cleanliness, and the problems of field error taking and error using caused by non-uniform fields exist. Based on this, there is a problem that accuracy of processing information and request processing efficiency are low.

In view of this, an embodiment of the present disclosure provides a request processing method, including: and in response to receiving a to-be-processed request of a first external system, determining target entity classes corresponding to M to-be-requested fields included in the to-be-processed request, wherein M is an integer greater than or equal to 1. And calling at least one target method corresponding to each of the M target entity classes. And processing the request to be processed by using the at least one target method to obtain processing information.

Fig. 1 schematically illustrates an application scenario diagram of a request processing method according to an embodiment of the present disclosure.

As shown in fig. 1, an application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is a medium used to provide a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may interact with the server 105 through the network 104 using at least one of the first terminal device 101, the second terminal device 102, the third terminal device 103, to receive or send messages, etc. Various communication client applications, such as a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only) may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103.

The first terminal device 101, the second terminal device 102, the third terminal device 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by the user using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that, the method for processing a request provided by the embodiment of the present disclosure may be generally performed by the server 105. Accordingly, the request processing apparatus provided by the embodiments of the present disclosure may be generally disposed in the server 105. The request processing method provided by the embodiment of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105. Accordingly, the request processing apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and/or the server 105.

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

The request processing method of the disclosed embodiment will be described in detail below with reference to fig. 2 to 6 based on the scenario described in fig. 1.

Fig. 2 schematically illustrates a flow chart of a request processing method according to an embodiment of the disclosure.

As shown in fig. 2, the request processing method of this embodiment includes operations S210 to S230.

In operation S210, in response to receiving the pending request of the first external system, a target entity class corresponding to each of M pending request fields included in the pending request is determined, where M is an integer greater than or equal to 1.

At least one target method corresponding to each of the M target entity classes is invoked in operation S220.

In operation S230, the pending request is processed using at least one target method, resulting in processed information.

According to an embodiment of the present disclosure, a first external system may be used to send a request to be processed, the first external system may be a distributed system or the like. The pending request may include a plurality of pending request fields. The field to be requested may be a service field related to an actual service, and the field to be requested may include an accno field in HashMap (hash map) format, an accno field in List (List) format, and the like, where the accno field may be a field for characterizing an account number.

According to the embodiment of the disclosure, the entity class may be a class which is obtained by uniformly managing and storing the service fields with the same service meaning but different names according to actual service modeling, for example, the entity class may be a class related to financial services. For example, the entity class may include a transaction class or the like, which may include an order class, a settlement account class, or the like. The settlement account class may include, among other things, a payment account class, a collection account class, and the like. The target entity class may be an entity class having an association relationship with the field to be requested, that is, may be an entity class having the same business meaning as the field to be requested.

According to embodiments of the present disclosure, a target method may be used to process a pending request. For example: in the case where the request to be processed is a settlement request, a method for processing the settlement request may be determined.

According to an embodiment of the present disclosure, the processing information may be information obtained by processing a request to be processed. For example: in the case where the request to be processed is a settlement request, the settlement request may be processed by using the target method to obtain processing information corresponding to the settlement request, and the processing information may be a settlement result or the like.

According to the embodiment of the disclosure, under the condition that a request to be processed of a first external system is received, the request to be processed is analyzed to obtain M fields to be requested included in the request to be processed; and processing the field to be requested by using the trained model to determine a target entity class corresponding to the field to be requested, wherein the trained model can store the association relation between the field to be requested and the target entity class.

According to the embodiment of the disclosure, at least one target method corresponding to each of M target entity classes may be determined according to the M target entity classes, and then the at least one target method corresponding to each of the M target entity classes may be invoked. For example: the method for processing the settlement account class can be determined according to the settlement account class, and then the method for processing the settlement account class is called.

According to an embodiment of the present disclosure, the at least one target method described above may be performed to process a request to be processed, resulting in processing information.

According to the embodiment of the disclosure, under the condition that the pending request of the first external system is received, the target entity class corresponding to each of M pending request fields included in the pending request is determined, so that the conversion of the pending request fields into the target entity class is realized, thereby reducing the number of fields with different fields having the same business meaning due to interaction with the communication area of the first external system, and improving the accuracy of field acquisition. On the basis, the processing information is obtained by processing the request to be processed by utilizing at least one target method corresponding to each of M target entity classes, and the accuracy of the processing information and the request processing efficiency are improved.

According to an embodiment of the present disclosure, determining a target entity class corresponding to each of M fields to be requested included in a request to be processed includes: a mapping routine is called. And obtaining target entity classes corresponding to the M fields to be requested respectively according to the M fields to be requested included in the request to be processed based on the mapping routine.

According to the embodiment of the disclosure, the mapping routine may be constructed based on the association relationship between the field to be requested and the entity class, and thus, the mutual conversion may be performed according to the association relationship between the field to be requested and the entity class through the mapping routine. The mapping routine may be a tangential program that exists in layers that interact with the external system, which may include a combination layer and an access layer, etc. A mapping rule of the corresponding relation between HashMap and the entity class of the system can be set through an XML (eXtensible Markup Language) format, the content of the XML is read by a mapping routine, and then conversion between the field to be requested and the entity class is carried out according to the set corresponding relation.

According to the embodiment of the disclosure, the target entity class corresponding to each of the M fields to be requested is obtained by calling the mapping routine, so that accuracy and efficiency of obtaining the target entity class are improved.

According to an embodiment of the present disclosure, based on a mapping routine, obtaining, from M fields to be requested included in a request to be processed, target entity classes corresponding to the M fields to be requested, respectively, includes: for each of the M fields to be requested, determining a field matching the field to be requested from a predetermined set of associations using a mapping routine. Based on the mapping routine, a predetermined association relationship corresponding to the field to be requested is determined according to the field matched with the field to be requested. And obtaining the target entity class corresponding to the field to be requested according to the preset association relation corresponding to the field to be requested. The predetermined association relation set comprises N predetermined association relations, wherein the predetermined association relations represent association relations between fields and entity classes, and N is an integer greater than or equal to 1.

According to an embodiment of the present disclosure, the field that matches the field to be requested may be a field whose similarity with the field to be requested satisfies a predetermined similarity threshold. For example: the similarity between the field to be requested and each field in the predetermined association set may be determined, and thus, the field in the predetermined association set, for which the similarity with the field to be requested satisfies the predetermined similarity threshold, may be determined as the above-mentioned field matching the field to be requested. Wherein the predetermined similarity may include 70%, 80%, 90%, or the like.

According to the embodiment of the disclosure, the predetermined association corresponding to the field matched with the field to be requested may be determined as the predetermined association corresponding to the field to be requested. Thus, the target entity class with the association relation with the field to be requested can be determined according to the preset association relation. For example, the predetermined association relation set may include a predetermined association relation between the field A1 and the entity B1. The request to be processed may include a field A2 to be requested, a similarity between the field A2 to be requested and the field A1 may be determined, and in a case where the similarity satisfies a predetermined similarity threshold, a predetermined association relationship corresponding to the field A2 to be requested may be determined as a predetermined association relationship between the field A1 and the entity B1, thereby, based on the predetermined association relationship, it may be determined that the entity class B1 is a target entity class of the field A2 to be requested.

According to the embodiment of the disclosure, since the predetermined association relation set is constructed based on the determined association relation, the mapping relation between the fields of the predetermined association relation set and the entity class is more accurate, and based on the mapping relation, the more accurate fields matched with the fields to be requested can be determined from the predetermined association relation set, and further the target entity class corresponding to the fields to be requested can be more accurately determined, so that the accuracy of determining the target entity class is improved.

According to an embodiment of the present disclosure, the request response method further includes: and responding to the received field adding request of the second external system, and analyzing the field adding request to obtain the field to be added. And updating the preset association relation set by using the field to be added.

According to an embodiment of the present disclosure, the second external system may be a distributed system, which may be used to send the field addition request. And under the condition that a field adding request of the second external system is received, the field adding request can be parsed to obtain a field to be added, which is included in the field adding request, wherein the field to be added can be a field to be added into a preset association relation set.

According to the embodiment of the disclosure, the predetermined association relationship corresponding to the field in the predetermined association relationship set with the similarity of the field to be added meeting the preset threshold can be used as the predetermined association relationship corresponding to the field to be added, so that the predetermined association relationship set can be updated. Wherein the predetermined similarity may include 70%, 80%, 90%, or the like. Based on the above, a predetermined association relationship corresponding to the added field may be determined according to the field to be added, and then an entity class corresponding to the field to be added may be determined based on the predetermined association relationship.

According to the embodiments of the present disclosure, based on the above, in the case of receiving a new field from another system, an entity class corresponding to the new field may be determined according to the new field.

According to the embodiment of the disclosure, the expansion of the predetermined association relation set is realized by updating the predetermined association relation set by the field to be added from the second external system, so that the flexibility of determining entity class through the predetermined association relation set is improved.

According to an embodiment of the present disclosure, updating a predetermined association relationship set with a field to be added includes: and determining the entity class corresponding to the field to be added. And creating an association relation between the field to be added and the entity class corresponding to the field to be added to obtain a newly added preset association relation so as to update the preset association relation set.

According to the embodiment of the disclosure, the predetermined association relationship corresponding to the field in the predetermined association relationship set, in which the similarity satisfies the predetermined similarity threshold, may be used as the predetermined association relationship corresponding to the field to be added, by determining the similarity between the field to be added and each field in the predetermined association relationship set. Therefore, the predetermined association relation corresponding to the added field can be determined according to the field to be added, and the entity class corresponding to the field to be added can be determined based on the predetermined association relation.

According to the embodiment of the disclosure, the association relation between the field to be added and the entity class corresponding to the field to be added can be created to obtain the newly added preset association relation, and then the newly added preset association relation is added into the preset association relation set to update the preset association relation set.

According to the embodiment of the disclosure, the association relationship between the field to be added and the entity class corresponding to the field to be added is created through determining the entity class corresponding to the field to be added, so that the newly added predetermined association relationship is obtained, and further the newly added predetermined association relationship can be added into the predetermined association relationship set to update the predetermined association relationship set, thereby realizing the expansion of the predetermined association relationship set and improving the flexibility of determining the entity class through the predetermined association relationship set.

According to an embodiment of the present disclosure, based on a mapping routine, obtaining, from M fields to be requested included in a request to be processed, target entity classes corresponding to the M fields to be requested, respectively, includes: and extracting the characteristics of the fields to be requested by using a mapping routine according to each field to be requested in the M fields to be requested, so as to obtain field characteristic information. And processing the field characteristic information by using a mapping routine to obtain a target entity class corresponding to the field to be requested.

According to the embodiment of the disclosure, the field characteristic information is processed by using a mapping routine to obtain a target entity class corresponding to the field to be requested. The similarity between the field characteristic information and the field characteristic information of each field in the predetermined association set may be determined.

When the similarity satisfies the predetermined similarity threshold, the predetermined association relationship corresponding to the field in the predetermined association relationship set, for which the similarity satisfies the predetermined similarity threshold, may be used as the predetermined association relationship corresponding to the field feature information, that is, the predetermined association relationship corresponding to the field to be requested. Therefore, the predetermined association relation corresponding to the field to be requested can be determined according to the field to be requested, and the entity class corresponding to the field to be requested can be determined based on the predetermined association relation.

According to the embodiment of the disclosure, the field characteristic information is obtained by extracting the characteristics of the field to be requested by using the mapping routine, and the target entity class corresponding to the field to be requested is obtained by processing the field characteristic information by using the mapping routine, so that the efficiency and accuracy of obtaining the target entity class are improved.

According to an embodiment of the present disclosure, processing a request to be processed using at least one target method to obtain processing information includes: and under the condition that the at least one third external system is required to be called according to the current method corresponding to the current field to be requested, converting the current field to be requested into a matching request field matched with each of the at least one third external system by utilizing the current method corresponding to the current field to be requested. And converting the feedback field corresponding to each of the at least one third external system into a target field corresponding to a target entity class corresponding to the current field to be requested by using the current method corresponding to the current field to be requested in response to receiving the feedback field corresponding to each of the at least one third external system, wherein the feedback field is obtained by the third external system according to the matching request field. And obtaining processing information corresponding to the current method corresponding to the current field to be requested according to the target field corresponding to the target entity class corresponding to the current field to be requested. The current fields to be requested are determined from the M fields to be requested according to the association relation among the M fields to be requested. The current method is determined from at least one target method corresponding to the current field to be requested according to the calling relation between at least one target method corresponding to the current field to be requested.

According to an embodiment of the present disclosure, the third external system may be a distributed system. The third external system may be configured to process the matching request field and to send a feedback field resulting from processing the matching request field.

According to an embodiment of the present disclosure, the matching request field may be a field whose field format matches a field format of a field processed by the third external system. The field format of the current field to be requested can be converted into the matching request field by using the current method corresponding to the current field to be requested, so that the matching request field can be processed by the third external system, and the processing of the field to be requested by the third external system can be realized.

According to the embodiment of the disclosure, when a feedback field is received, the feedback field can be converted into a target field corresponding to a target entity class corresponding to a field to be requested by using a current method corresponding to a current field to be requested. The converting the feedback field into the target field corresponding to the target entity class corresponding to the field to be requested may be converting the feedback field into the target field consistent with the field format of the target entity class according to the field format without changing the meaning of the feedback field representation.

According to the embodiment of the disclosure, the field to be requested can be processed in combination with the target field, so that the processing information corresponding to the current method corresponding to the current field to be requested can be obtained. For example, in the case that the processing information of the third external system is required for processing the field to be requested, the third external system processes the matching request field by processing the field to be requested into the matching request field, obtains the feedback field, and then converts the feedback field into the target field. Based on the above, the target field can be read to obtain the processing information of the third party external system included in the target field, and then the field to be requested can be processed in combination with the processing information of the third party external system, so as to obtain the processing information corresponding to the current method corresponding to the current field to be requested.

According to the embodiment of the disclosure, the current field to be requested is converted into the matching request field matched with each of the at least one third external system by using the current method corresponding to the current field to be requested, and then the third external system processes the matching request field to obtain the feedback field, so that the problem that the third external system is difficult to process the field to be requested due to field mismatching is solved, and further the feedback field is converted into the target field corresponding to the target entity class corresponding to the current field to be requested under the condition that the feedback field is received, and the efficiency of calling the third external system to process the field to be requested to obtain the target field is improved, and further the information processing efficiency is improved.

Fig. 3 schematically shows a schematic diagram of processing fields according to an embodiment of the present disclosure.

As shown in fig. 3, in case the first external system receives an operation from the client, a pending request may be sent to the core system, and the pending request may include field 1 in HashMap format. The field 1 in HashMap format may be converted into field 1 of entity class through the first adaptation layer. Wherein the first adaptation layer is deployed with a mapping routine.

In the event that the core system within the organization receives field 1 of the entity class, method a may be utilized to process field 1 of the entity class. In the case where field 1 of the entity class is processed using sub-method A1 of method a, field 1 of the entity class may be transmitted to the third external system. The field 1 of the entity class may be converted into a field 1 of List format through the second adaptation layer, where the field 1 of List format may correspond to the matching request field.

Thus, the third external system may process field 1 of the List format, obtain field 2 of the List format, and send field 2 of the List format to the core system, where field 2 of the List format may correspond to the feedback field described above. Wherein the second adaptation layer is deployed with a mapping routine.

The field 2 in List format can be converted into the field 2 of entity class through the second adaptation layer. Based on this, field 1 of the entity class and field 2 of the entity class can be processed using sub-method A2 of method a. In the case where field 1 of the entity class and field 2 of the entity class are processed using the sub-method a, field 1 of the entity class and field 2 of the entity class may be transmitted by the core system to the fourth external system. The field 1 of the entity class and the field 2 of the entity class may be converted into the field 1 of the List format and the field 2 of the HashMap format through the third adaptive layer, so that the fourth external system may process the field 1 of the List format and the field 2 of the HashMap format, where the field 1 of the List format and the field 2 of the HashMap format may correspond to the target fields. Wherein the third adaptation layer is deployed with a mapping routine.

Based on the above, a fourth external system is called to process the field 1 in the List format and the field 2 in the HashMap format, so as to obtain processing information corresponding to the request to be processed.

Fig. 4 schematically illustrates a schematic diagram of processing fields according to another embodiment of the present disclosure.

As shown in fig. 4, in case the first external system receives an operation from the client, a pending request may be sent to the core system, and the pending request may include field 1 in HashMap format. The field 1 in HashMap format may be converted into field 1 of entity class through the first adaptation layer.

Thus, the third external system may process field 1 of the List format, obtain field 2 of the List format, and send field 2 of the List format to the core system, where field 2 of the List format may correspond to the feedback field described above.

Based on this, field 1 of the entity class and field 2 of the List format can be processed using sub-method A2 of method a. In the case where field 1 of the entity class and field 2 of the List format are processed using sub-method A2, field 1 of the entity class and field 2 of the List format may be transmitted by the core system to the fourth external system. The field 1 of the entity class and the field 2 of the List format may be converted into the field 1 of the List format and the field 2 of the HashMap format by the third adaptation layer, and thus, the fourth external system may process the field 1 of the List format and the field 2 of the HashMap format, where the field 1 of the List format and the field 2 of the HashMap format may correspond to the target fields described above.

Based on the processing information, a fourth external system processing target field is called, and processing information corresponding to the request to be processed is obtained.

According to the embodiment of the disclosure, based on the data processing method disclosed by the disclosure, the problem of field mismatch caused by data exchange between the data of the external communication area and the core system can be avoided. In addition, the problems of different coding habits and different personnel capacities caused by different developers can be avoided, and the human resources can be saved.

According to the embodiment of the disclosure, the current field to be requested is processed by the current method corresponding to the current field to be requested, so that the processing information corresponding to the current method corresponding to the current field to be requested is obtained, and the accuracy of the processing information and the request processing efficiency are improved.

According to the embodiment of the disclosure, in the case that other methods need to call the third external system, the predetermined feedback field associated with the target entity class can be acquired according to the target entity class called by the other methods, and the third external system is not required to process the matching field information to obtain the feedback field. Wherein the predetermined feedback field may be a field in XML format.

According to the embodiment of the disclosure, the feedback fields corresponding to the at least one third external system and the target entity class corresponding to the current field to be requested are associated, so that other methods can obtain the preset feedback field under the condition that the target entity class corresponding to the current field to be requested is called, and therefore under the condition that the feedback field is obtained by calling the third external system to process the current field to be requested, the preset feedback field associated with the target entity class can be directly obtained, the efficiency of obtaining the feedback field is improved, and the efficiency of processing the request to be processed can be improved.

Based on the request processing method, the disclosure further provides a request processing device. The device will be described in detail below in connection with fig. 5.

Fig. 5 schematically shows a block diagram of a request processing apparatus according to an embodiment of the present disclosure.

As shown in fig. 5, the request processing apparatus 500 of this embodiment includes a determination module 510, a calling module 520, and a processing module 530.

The determining module 510 is configured to determine, in response to receiving a request to be processed of the first external system, a target entity class corresponding to each of M fields to be requested included in the request to be processed, where M is an integer greater than or equal to 1. In an embodiment, the determining module 510 may be configured to perform the operation S210 described above, which is not described herein.

The calling module 520 is configured to call at least one target method corresponding to each of the M target entity classes. In an embodiment, the calling module 520 may be configured to perform the operation S220 described above, which is not described herein.

The processing module 530 is configured to process the request to be processed by using at least one target method, to obtain processing information. In an embodiment, the processing module 530 may be configured to perform the operation S230 described above, which is not described herein.

According to an embodiment of the present disclosure, the determination module 510 includes a call sub-module and an get sub-module. The calling sub-module is used for calling the mapping routine; the obtaining submodule is used for obtaining target entity classes corresponding to the M fields to be requested respectively according to the M fields to be requested included in the request to be processed based on the mapping routine.

According to an embodiment of the present disclosure, the first obtaining submodule includes a first determining unit, a second determining unit, and a first obtaining unit. The first determining unit is used for determining a field matched with the fields to be requested from a preset association relation set by using a mapping routine for each field to be requested in the M fields to be requested; the second determining unit is used for determining a preset association relation corresponding to the field to be requested according to the field matched with the field to be requested based on the mapping routine; the first obtaining unit is used for obtaining a target entity class corresponding to the field to be requested according to a preset association relation corresponding to the field to be requested.

According to an embodiment of the present disclosure, the first obtaining sub-module further includes an parsing unit and an updating unit. The analysis unit is used for responding to the received field adding request of the second external system, analyzing the field adding request and obtaining a field to be added; the updating unit is used for updating the preset association relation set by utilizing the field to be added.

According to an embodiment of the present disclosure, the update unit includes a determination subunit and a creation subunit. The determining subunit is used for determining entity classes corresponding to the fields to be added; the creation subunit is used for creating the association relation between the field to be added and the entity class corresponding to the field to be added, and obtaining a newly added preset association relation so as to update the preset association relation set.

According to an embodiment of the present disclosure, the obtaining sub-module includes a second obtaining unit and a third obtaining unit. The second obtaining unit is used for extracting characteristics of the fields to be requested by using a mapping routine for each field to be requested in the M fields to be requested to obtain field characteristic information; and the third obtaining unit is used for processing the field characteristic information by using the mapping routine to obtain the target entity class corresponding to the field to be requested.

According to an embodiment of the present disclosure, the processing module 530 includes a first conversion sub-module, a second conversion sub-module, and a second acquisition sub-module. Wherein the first conversion sub-module is used for determining that at least one third external system needs to be called according to the current method corresponding to the current field to be requested,

converting the current field to be requested into a matching request field respectively matched with at least one third external system by using a current method corresponding to the current field to be requested; the second conversion sub-module is used for converting the feedback fields corresponding to the at least one third external system into target fields corresponding to target entity classes corresponding to the current field to be requested by utilizing the current method corresponding to the current field to be requested in response to receiving the feedback fields corresponding to the at least one third external system, wherein the feedback fields are obtained by the third external system according to the matching request fields; the second obtaining sub-module is used for obtaining processing information corresponding to the current method corresponding to the current field to be requested according to the target field corresponding to the target entity class corresponding to the current field to be requested; the current fields to be requested are determined from M fields to be requested according to the association relation among the M fields to be requested; the current method is determined from at least one target method corresponding to the current field to be requested according to the calling relation between at least one target method corresponding to the current field to be requested.

According to an embodiment of the present disclosure, the processing module 530 further includes a processing sub-module. The processing sub-module is used for processing the current field to be requested by using the current method corresponding to the current field to be requested under the condition that at least one third external system is not required to be called according to the current method corresponding to the current field to be requested, so as to obtain processing information corresponding to the current method corresponding to the current field to be requested.

According to an embodiment of the present disclosure, the processing module 530 further includes an association sub-module. The association sub-module is used for associating the feedback field corresponding to each of the at least one third external system with the target entity class corresponding to the current field to be requested, so that other methods can obtain a preset feedback field under the condition of calling the target entity class corresponding to the current field to be requested, wherein the preset feedback field is a feedback field in the feedback field corresponding to each of the at least one third external system.

Any of the determination module 510, the invocation module 520, and the processing module 530 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules, according to embodiments of the present disclosure. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the determination module 510, the invocation module 520, and the processing module 530 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or by hardware or firmware, such as any other reasonable way of integrating or packaging the circuitry, or in any one of or a suitable combination of any of three implementations of software, hardware, and firmware. Alternatively, at least one of the determination module 510, the invocation module 520, and the processing module 530 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.

As shown in fig. 6, an electronic device 600 according to an embodiment of the present disclosure includes a processor 601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. The processor 601 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 601 may also include on-board memory for caching purposes. The processor 601 may comprise a single processing unit or a plurality of processing units for performing different actions of the method flows according to embodiments of the disclosure.

In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. The processor 601 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 602 and/or the RAM 603. Note that the program may be stored in one or more memories other than the ROM 602 and the RAM 603. The processor 601 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 600 may also include an input/output (I/O) interface 605, the input/output (I/O) interface 605 also being connected to the bus 604. The electronic device 600 may also include one or more of the following components connected to an input/output (I/O) interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to an input/output (I/O) interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: 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), 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 context of this disclosure, 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. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 602 and/or RAM 603 and/or one or more memories other than ROM 602 and RAM 603 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to perform the methods provided by embodiments of the present disclosure.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 601. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and/or installed from the removable medium 611. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 601. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts 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 disclosure. 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.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. A request processing method, comprising:

in response to receiving a request to be processed of a first external system, determining target entity classes corresponding to M fields to be requested included in the request to be processed, wherein M is an integer greater than or equal to 1;

Invoking at least one target method corresponding to each of M target entity classes; and

and processing the request to be processed by using the at least one target method to obtain processing information.

2. The method of claim 1, wherein the determining the target entity class corresponding to each of M pending request fields included in the pending request comprises:

calling a mapping routine; and

and obtaining target entity classes corresponding to the M fields to be requested respectively according to the M fields to be requested included in the request to be processed based on the mapping routine.

3. The method of claim 2, wherein the obtaining, based on the mapping routine, a target entity class corresponding to each of M fields to be requested included in the request to be processed according to the M fields to be requested, includes:

for each of the M fields to be requested,

determining a field matched with the field to be requested from a preset association relation set by utilizing the mapping routine;

based on the mapping routine, determining a preset association relation corresponding to the field to be requested according to the field matched with the field to be requested; and

Obtaining a target entity class corresponding to the field to be requested according to a preset association relation corresponding to the field to be requested;

the predetermined association relation set comprises N predetermined association relations, wherein the predetermined association relations represent association relations between fields and entity classes, and N is an integer greater than or equal to 1.

4. A method according to claim 3, further comprising:

responding to a field adding request received by a second external system, and analyzing the field adding request to obtain a field to be added; and

and updating the preset association relation set by utilizing the field to be added.

5. The method of claim 4, wherein the updating the predetermined set of association relationships with the field to be added comprises:

determining entity class corresponding to the field to be added; and

and creating an association relation between the field to be added and the entity class corresponding to the field to be added to obtain a newly added preset association relation so as to update the preset association relation set.

6. The method of claim 2, wherein the obtaining, based on the mapping routine, a target entity class corresponding to each of M fields to be requested included in the request to be processed according to the M fields to be requested, includes:

For each of the M fields to be requested,

extracting features of the fields to be requested by using the mapping routine to obtain field feature information; and

and processing the field characteristic information by using the mapping routine to obtain a target entity class corresponding to the field to be requested.

7. The method according to any one of claims 1-6, wherein said processing said request to be processed with said at least one target method to obtain processed information comprises:

in case it is determined that at least one third external system needs to be called according to the current method corresponding to the current field to be requested,

converting the current field to be requested into a matching request field respectively matched with the at least one third external system by using a current method corresponding to the current field to be requested;

converting, by the current method corresponding to the current field to be requested, a feedback field corresponding to each of the at least one third external system into a target field corresponding to a target entity class corresponding to the current field to be requested in response to receiving the feedback field corresponding to each of the at least one third external system, where the feedback field is obtained by the third external system according to the matching request field; and

Obtaining processing information corresponding to a current method corresponding to the current field to be requested according to a target field corresponding to a target entity class corresponding to the current field to be requested;

the current fields to be requested are determined from the M fields to be requested according to the association relation among the M fields to be requested;

the current method is determined from at least one target method corresponding to the current field to be requested according to a calling relation between at least one target method corresponding to the current field to be requested.

8. The method of claim 7, further comprising:

in case it is determined that the at least one third external system does not need to be called according to the current method corresponding to the current field to be requested,

and processing the current field to be requested by using a current method corresponding to the current field to be requested to obtain processing information corresponding to the current method corresponding to the current field to be requested.

9. The method of claim 7, further comprising:

and associating the feedback field corresponding to each of the at least one third external system with the target entity class corresponding to the current field to be requested so that other methods can obtain a preset feedback field under the condition of calling the target entity class corresponding to the current field to be requested, wherein the preset feedback field is a feedback field in the feedback field corresponding to each of the at least one third external system.

10. A request processing apparatus comprising:

the determining module is used for determining target entity classes corresponding to M fields to be requested respectively, wherein the M is an integer greater than or equal to 1, in response to receiving a request to be processed of a first external system;

the calling module is used for calling at least one target method corresponding to each of the M target entity classes; and

and the processing module is used for processing the request to be processed by utilizing the at least one target method to obtain processing information.

11. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.

12. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1 to 9.

13. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 9.