Data query method and device

Abstract

The invention discloses a data query method and device, and relates to the technical field of computers. The method comprises the following steps: receiving a data query request sent by an upstream system, wherein the data query request indicates a service code corresponding to the upstream system; querying a target conversion message corresponding to the service code from the conversion message according to the service code; the conversion message is obtained by performing field conversion on a historical message sent by an upstream system according to a preset association relationship; the preset association relationship indicates a corresponding relationship between a first field in the historical message and a second field in the conversion message; according to a target second field in the target conversion message, determining a target associated field corresponding to the target second field from first fields corresponding to the upstream system; and generating a data query result corresponding to the service code according to the target associated field and the target second field. According to the embodiment, the upstream system can conveniently obtain the data processing result and the data processing process of the downstream system.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for data querying. Background Technology

[0002] In existing upstream and downstream systems, the downstream system typically transforms messages sent by the upstream system based on the correspondence between fields in the upstream and downstream systems, and finally performs statistics and displays them according to the fields required by the downstream system. For example, the upstream system includes two fields: shipping weight and sampling weight, while the downstream billing system only considers the shipping weight and does not care about the sampling process. The field name for statistics in the downstream system is "weight". Therefore, during message transformation, the upstream "shipping weight" field is converted to the downstream "weight" field, and billing is performed based on the "weight" field to obtain the billing result. When the upstream system wants to query the processing result of the downstream system, it can only obtain the "weight" field used by the downstream system in billing and the billing result, but cannot know whether it was calculated from the "shipping weight" field or the "sampling weight". Therefore, to facilitate the upstream system to clearly obtain the data processing result and the data processing process during the query process, this embodiment of the invention provides a data query method applied to the downstream system. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a data processing method and apparatus. First, based on the service code, the target conversion message corresponding to the service code is found from the conversion message of the downstream system. Then, based on the target second field in the target conversion message, the target associated field is determined from the first field. This allows it to know which specific fields are processed according to the upstream system during the downstream system's processing. The results are then fed back to the upstream system in the form of data query results, so that the upstream system can clearly obtain the data processing results and the data processing process.

[0004] To achieve the above objectives, according to one aspect of the present invention, a method for data querying is provided.

[0005] An embodiment of the present invention provides a data query method comprising: receiving a data query request sent by an upstream system, the data query request indicating a service code corresponding to the upstream system; querying a target conversion message corresponding to the service code from a conversion message according to the service code; wherein the conversion message is obtained by performing field conversion on historical messages sent by the upstream system according to a preset association relationship; the preset association relationship indicates the correspondence between a first field in the historical message and a second field in the conversion message; determining a target association field corresponding to the target second field from the first field corresponding to the upstream system according to the target second field in the target conversion message; generating a data query result corresponding to the service code according to the target association field and the target second field, and feeding the data query result back to the upstream system.

[0006] Optionally, before receiving the data query request sent by the upstream system, the method further includes: parsing a first set of fields from the historical messages sent by the upstream system; matching the associated fields corresponding to each second field from the first set of fields; and for each second field, associating the second field with the associated field corresponding to the second field to generate the preset association relationship.

[0007] Optionally, after generating the preset association relationship and before receiving the data query request sent by the upstream system, the method further includes: setting the field value of the association field to the corresponding field value of the second field according to the preset association relationship, so as to generate the conversion message.

[0008] Optionally, the step of matching the associated field corresponding to each of the second fields from the first field set includes: traversing each of the first fields in the first field set, performing fuzzy matching with each of the second fields respectively, and generating a matching result; and determining the associated field when the matching result indicates that the matching degree is greater than a preset threshold.

[0009] Optionally, when there are multiple upstream systems, the step of associating the second field with the corresponding associated field for each second field to generate the preset association relationship includes: determining the business code corresponding to each of the upstream systems; and for each second field: associating the business code, the second field, and the associated field corresponding to the second field to obtain the preset association relationship.

[0010] Optionally, the upstream system is a business system, and the downstream system is a billing system.

[0011] Optionally, generating a data query result corresponding to the business code based on the target associated field and the target second field includes: determining a billing result based on the field value corresponding to the target second field; dynamically generating a display page based on the target associated field and the billing result, and using the display page as the data query result.

[0012] To achieve the above objectives, according to another aspect of the present invention, a data query apparatus is provided.

[0013] An embodiment of the present invention provides a data query apparatus comprising:

[0014] The receiving module is used to receive data query requests sent by the upstream system, wherein the data query request indicates the business code corresponding to the upstream system;

[0015] The query module is used to retrieve the target converted message corresponding to the service code from the converted message according to the service code; wherein, the converted message is obtained by converting the fields of historical messages sent by the upstream system according to a preset association relationship; the preset association relationship indicates the correspondence between the first field in the historical message and the second field in the converted message;

[0016] The determination module is used to determine the target association field corresponding to the target second field from the first field corresponding to the upstream system based on the target second field in the target conversion message;

[0017] The generation module is used to generate data query results corresponding to the business code based on the target association field and the target second field, and to feed the data query results back to the upstream system.

[0018] To achieve the above objectives, according to another aspect of the present invention, an electronic device for data querying is provided.

[0019] An electronic device for data querying according to an embodiment of the present invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement a data querying method according to an embodiment of the present invention.

[0020] To achieve the above objectives, according to another aspect of the present invention, a computer-readable storage medium is provided.

[0021] An embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements a data query method according to an embodiment of the present invention.

[0022] To achieve the above objectives, according to another aspect of the present invention, a computer product is provided.

[0023] A computer product according to an embodiment of the present invention includes a computer program, which, when executed by a processor, implements a data query method according to an embodiment of the present invention.

[0024] One embodiment of the above invention has the following advantages or beneficial effects: First, the target conversion message corresponding to the business code is found from the conversion message of the downstream system according to the business code. Then, the target associated field is determined from the first field according to the second target field in the target conversion message. It can be known which specific fields are processed according to the upstream system during the processing of the downstream system. The results are fed back to the upstream system in the form of data query results, so that the upstream system can clearly obtain the data processing results and data processing process.

[0025] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0026] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0027] Figure 1 This is a schematic diagram of the main flow of a data query method according to an embodiment of the present invention;

[0028] Figure 2 This is a schematic diagram of the main process for generating a preset association relationship according to an embodiment of the present invention;

[0029] Figure 3 This is a schematic diagram illustrating the main process of determining associated fields according to an embodiment of the present invention;

[0030] Figure 4 This is a schematic diagram of another main process for generating a preset association relationship according to an embodiment of the present invention;

[0031] Figure 5 This is a schematic diagram of the main process for generating data query results according to an embodiment of the present invention;

[0032] Figure 6 This is a schematic diagram illustrating the detailed process of a data query method according to an embodiment of the present invention;

[0033] Figure 7 This is a schematic diagram of the main modules of a data query device according to an embodiment of the present invention;

[0034] Figure 8 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0035] Figure 9 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0036] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0037] It should be noted that, unless otherwise specified, the embodiments of the present invention and the technical features thereof can be combined with each other.

[0038] It should be noted that the collection, gathering, updating, analysis, processing, use, transmission, and storage of user personal information involved in this disclosed technical solution all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0039] Figure 1 This is a schematic diagram illustrating the main steps of a data query method according to an embodiment of the present invention.

[0040] like Figure 1 As shown, the data query method of this invention mainly includes the following steps:

[0041] Step S101: Receive a data query request sent by the upstream system. The data query request indicates the corresponding business code of the upstream system.

[0042] Step S102: Query the target conversion message corresponding to the service code from the conversion message according to the service code; wherein, the conversion message is obtained by converting the fields of the historical messages sent by the upstream system according to the preset association relationship; the preset association relationship indicates the correspondence between the first field in the historical message and the second field in the conversion message;

[0043] Step S103: Based on the second target field in the target conversion message, determine the target association field corresponding to the second target field from the first field corresponding to the upstream system;

[0044] Step S104: Generate the data query results corresponding to the business code based on the target associated field and the target second field, and feed the data query results back to the upstream system.

[0045] In this system, upstream and downstream systems typically transmit data via messages. The downstream system needs to filter and process the data sent by the upstream system to generate a processing result. However, the upstream system is completely unaware of the downstream system's data processing process. Furthermore, in existing technologies, the upstream system can only obtain the final processing result from the downstream system and cannot determine which specific fields from the sent data were used during processing, nor can it optimize the system based on the processing result. Therefore, the purpose of this invention is to respond to a data query request sent by the upstream system by feeding back the target related fields actually used by the downstream system during data processing, so that the upstream system can understand the downstream system's data processing process.

[0046] For the query process, through the above steps, the transformation message stored in the downstream system can be directly queried based on the business code in the data query request to obtain the target transformation message. Then, the target associated field corresponding to the target second field is parsed from the target transformation message, realizing the process of the upstream system quickly obtaining the target associated field. However, before step S101, a preset association relationship needs to be pre-built, and historical messages need to be transformed according to the preset association relationship to obtain the transformation message before the query of the target associated field can be completed. Therefore, the following describes in detail the process of generating the preset association relationship and the transformation message when the upstream system is a business system and the downstream system is a billing system, based on an embodiment provided by the present invention.

[0047] Understandably, each business system typically handles only one type of business, and the first field it contains corresponds to that business. For example, when the business system is a waybill system, the first field could be package information, waybill code, package weight, etc. In the downstream system, the second field (the field used for billing) is usually fixed, and different calculation methods and rules are pre-set for different business systems. This allows the downstream system to convert the first field in the historical messages sent by the business system into the second field for billing calculation. However, during the billing process in the downstream system, not all the first fields sent by the upstream system are useful; the downstream system only selects the fields needed for billing from the first fields sent by the upstream system. Therefore, it is necessary to pre-establish the correspondence between the first field in the historical messages sent by the business system and the second field required by the downstream system based on the billing method and rules corresponding to each business. This is the process of generating a preset association. Only then can the billing system convert the historical messages received by the business system according to the preset association to obtain the converted message.

[0048] In one optional embodiment, before step S101, the process of generating the preset relationship is as follows: Figure 2 As shown, it also includes:

[0049] Step S201: Parse the first set of fields from the historical messages sent by the upstream system;

[0050] Step S202: Match the associated fields corresponding to each second field from the first field set;

[0051] Step S203: For each second field, associate the second field with the corresponding associated field to generate a preset association relationship.

[0052] The second field can be pre-set according to the billing methods and rules of different businesses, meaning the second field is relatively fixed. The first field set can include one or more first fields, and the parsed first field set is usually different for different business systems. For example, when the business system is a waybill system, the first field can be package information, waybill code, package weight, etc.; when the business system is a warehousing system, the first field can be product information, product weight, product volume, warehouse location, etc. Through the above steps S201 to S203, the first field set can be parsed from the historical messages corresponding to the business system, and the associated fields that can be associated with the second field can be further determined to obtain the preset association relationship.

[0053] For the matching process in step S202, in one optional embodiment, such as Figure 3 As shown, it includes:

[0054] Step S301: Iterate through each first field in the first field set, and perform fuzzy matching with each second field to generate matching results;

[0055] Step S302: If the matching result indicates that the matching degree is greater than the preset threshold, determine the associated field.

[0056] Specifically, for multiple first fields in the first field set, batch fuzzy matching can be used to match them with a set of second fields composed of multiple second fields. Preliminary filtering is performed based on the matching results. When multiple first fields have a match degree greater than a preset threshold with the same second field, manual review is required to determine and adjust the match, ensuring that each second field corresponds to only one associated field. For example, the first field may include multiple weight fields such as "product weight," "inspection weight," and "transportation weight." However, in the billing system, billing is only based on product weight, and the second field only contains the "weight" field. Therefore, it is necessary to match "product weight," "inspection weight," and "transportation weight" in the first field with the "weight" field in the second field. If the match degrees are the same, it is impossible to determine which is the associated field. Therefore, manual review is required to determine "product weight" as the associated field from "product weight," "inspection weight," and "transportation weight," and associate it with "weight" in the second field to generate a preset association relationship of "product weight" - "weight."

[0057] In practical applications, multiple upstream systems may contain the same first field. That is, the "goods weight" field may be present in the waybill system, warehousing system, and express delivery system, and all may be associated with the "weight" field in the billing system. To differentiate between different upstream systems, in an optional embodiment, when there are multiple upstream systems, the process of generating a preset association in step S203 can be as follows: Figure 4 As shown, it includes:

[0058] Step S401: Determine the business code corresponding to each upstream system;

[0059] Step S402: For each second field: associate the business code, the second field, and the associated fields corresponding to the second field to obtain the preset association relationship.

[0060] Understandably, after the above process, the preset association relationship stored is "System A" - "Product Weight" - "Weight" and "System B" - "Product Weight" - "Weight". This is to distinguish between different upstream systems and avoid confusion.

[0061] After the above Figures 2 to 4The process shown, after receiving historical messages sent by the upstream system, completes the process of constructing the preset association relationship between the first field in the historical message and the second field required by the downstream system, but the converted message has not yet been obtained. Therefore, after step S203 and before step S101, it further includes: setting the field values ​​of the associated fields to the corresponding field values ​​of the second field according to the preset association relationship, in order to generate the converted message. That is to say, after determining which associated fields in the first field have an association relationship with the second field, it is also necessary to set the field values ​​of the determined associated fields to the corresponding values ​​of the second field to obtain the converted message.

[0062] In an optional embodiment, the process of generating the data query result corresponding to the business code in step S104 can be as follows: Figure 5 As shown, it includes:

[0063] Step S501: Determine the billing result based on the field value corresponding to the second field of the target;

[0064] Step S501: Dynamically generate a display page based on the target associated fields and the billing results, and use the display page as the data query result.

[0065] To intuitively display the data query results, this embodiment of the invention renders the target associated field and the billing result, and generates a display page that is then fed back to the upstream system for easy data viewing. In an optional embodiment, fields other than the target associated field and the target second field can also be displayed according to actual needs; this invention does not impose specific limitations on this.

[0066] The following is based on Figure 6 Taking an example, the specific process of the data query method provided by this invention will be described in detail:

[0067] Step S601: Receive historical messages sent by the upstream system;

[0068] Step S602: Parse the first set of fields from historical messages;

[0069] Step S603: Perform fuzzy matching between the first field in the first field set and the preset second field to determine the associated field corresponding to each second field;

[0070] Step S604: Associate the business code, associated field, and second field corresponding to the upstream system to generate a preset association relationship of "business code" - "associated field" - "second field";

[0071] Step S605: Transform historical messages according to preset association relationships to generate transformed messages; wherein, the transformed messages include business codes and a second field;

[0072] Step S606: Receive a data query request sent by the upstream system. The data query request indicates the target service code corresponding to the upstream system.

[0073] Step S607: Based on the target service code, retrieve the target conversion message corresponding to the target service code from the conversion messages;

[0074] Step S608: Determine the second target field and the target-related field corresponding to the second target field from the target conversion message;

[0075] Step S609: Determine the billing result based on the field value corresponding to the second field of the target;

[0076] Step S610: Dynamically generate a display page from the target associated field, the target second field, and the billing result, and use the display page as the data query result to feed back to the upstream system.

[0077] As can be seen, the above process realizes the entire process from building a preset association relationship, generating a conversion message, and determining the target conversion message corresponding to the data query request from the conversion message after receiving the data query request, and obtaining the corresponding target association field from the target conversion message. This solves the technical problem in the prior art that the upstream system cannot obtain the data processing process of the downstream system.

[0078] It is understood that the business system and billing system in the embodiments of the present invention are only one example, and can also be applied to other upstream and downstream systems that have data processing relationships.

[0079] According to the data query method of the present invention, the target conversion message corresponding to the business code is first found from the conversion message of the downstream system based on the business code. Then, the target associated field is determined from the first field based on the target second field in the target conversion message. This allows it to know which specific fields are processed according to the upstream system during the downstream system's processing. The data query results are then fed back to the upstream system, making it easy for the upstream system to clearly obtain the data processing results and the data processing process.

[0080] Figure 7 This is a schematic diagram of the main modules of a data query device according to an embodiment of the present invention.

[0081] like Figure 7 As shown, the data query device 700 of this embodiment includes:

[0082] The receiving module 701 is used to receive a data query request sent by the upstream system, wherein the data query request indicates the business code corresponding to the upstream system;

[0083] The query module 702 is used to query the target conversion message corresponding to the service code from the conversion message according to the service code; wherein, the conversion message is obtained by converting the fields of the historical messages sent by the upstream system according to a preset association relationship; the preset association relationship indicates the correspondence between the first field in the historical message and the second field in the conversion message;

[0084] The determination module 703 is used to determine the target association field corresponding to the target second field from the first field corresponding to the upstream system based on the target second field in the target conversion message;

[0085] The generation module 704 is used to generate a data query result corresponding to the business code based on the target association field and the target second field, and to feed the data query result back to the upstream system.

[0086] In an optional embodiment of the present invention, the apparatus further includes a construction module, configured to parse a first set of fields from historical messages sent by the upstream system before receiving a data query request from the upstream system; match the associated fields corresponding to each second field from the first set of fields; and for each second field, associate the second field with the associated field corresponding to the second field to generate the preset association relationship.

[0087] In an optional embodiment of the present invention, the construction module is further configured to, after generating the preset association relationship and before receiving the data query request sent by the upstream system, set the field value of the association field to the corresponding field value of the second field according to the preset association relationship, so as to generate the conversion message.

[0088] In an optional embodiment of the present invention, the construction module is further configured to traverse each of the first fields in the first field set, perform fuzzy matching with each of the second fields respectively, and generate matching results; and determine the associated field when the matching results indicate that the matching degree is greater than a preset threshold.

[0089] In an optional embodiment of the present invention, when there are multiple upstream systems, the construction module is further configured to: determine the business code corresponding to each of the upstream systems; and for each of the second fields: associate the business code, the second field, and the associated field corresponding to the second field to obtain the preset association relationship.

[0090] In one optional embodiment of the present invention, the upstream system is a business system and the downstream system is a billing system.

[0091] In an optional embodiment of the present invention, the generation module 704 is further configured to: determine the billing result based on the field value corresponding to the target second field; dynamically generate a display page based on the target associated field and the billing result; and use the display page as the data query result.

[0092] According to the data query apparatus of the present invention, the target conversion message corresponding to the service code is first found from the conversion message of the downstream system based on the service code, and then the target associated field is determined from the first field based on the target second field in the target conversion message. This allows the apparatus to know which specific fields are processed according to the upstream system during the downstream system's processing. The data query results are then fed back to the upstream system, making it easy for the upstream system to clearly obtain the data processing results and the data processing process.

[0093] Figure 8 An exemplary system architecture 800 is shown, in which the data query method or data query apparatus of embodiments of the present invention can be applied.

[0094] like Figure 8 As shown, system architecture 800 may include terminal devices 801, 802, and 803, a network 804, and a server 805. Network 804 serves as the medium for providing communication links between terminal devices 801, 802, and 803 and server 805. Network 804 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0095] Users can use terminal devices 801, 802, and 803 to interact with server 805 via network 804 to receive or send data. Various communication client applications can be installed on terminal devices 801, 802, and 803, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, and social media platforms.

[0096] Terminal devices 801, 802, and 803 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0097] Server 805 can be a server that provides various services, such as a backend management server that supports data query requests sent by users using terminal devices 801, 802, and 803. The backend management server can analyze and process the received data query requests and other data, and feed back the processing results (such as data query results) to the terminal devices.

[0098] It should be noted that the data query method provided in the embodiments of the present invention is generally executed by the server 805, and correspondingly, the data query device is generally set in the server 805.

[0099] It should be understood that Figure 8 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0100] The following is for reference. Figure 9 It shows a schematic diagram of the structure of a computer system 900 suitable for implementing a terminal device of the present invention. Figure 9 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0101] like Figure 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 902 or programs loaded from storage section 908 into random access memory (RAM) 903. The RAM 903 also stores various programs and data required for the operation of the system 900. The CPU 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) first interface 905 is also connected to the bus 904.

[0102] The following components are connected to the I / O first interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network first interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O first interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0103] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by central processing unit (CPU) 901, it performs the functions defined above in the system of this invention.

[0104] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0105] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0106] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a receiving module, a querying module, a determining module, and a generating module. The names of these modules do not necessarily limit the module itself; for example, the receiving module can also be described as "a module that receives data query requests sent by an upstream system."

[0107] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to include: receiving a data query request sent by an upstream system, the data query request indicating a service code corresponding to the upstream system; querying a target conversion message corresponding to the service code from a conversion message according to the service code; wherein the conversion message is obtained by converting fields of historical messages sent by the upstream system according to a preset association relationship; the preset association relationship indicates the correspondence between a first field in the historical message and a second field in the conversion message; determining a target association field corresponding to the target second field from the first field corresponding to the upstream system according to the target second field in the target conversion message; generating a data query result corresponding to the service code based on the target association field and the target second field, and feeding the data query result back to the upstream system.

[0108] According to the technical solution of the present invention, the target conversion message corresponding to the service code is first found from the conversion message of the downstream system based on the service code. Then, the target associated field is determined from the first field based on the target second field in the target conversion message. This allows it to know which specific fields are processed according to the upstream system during the downstream system's processing. The results are then fed back to the upstream system in the form of data query results, so that the upstream system can clearly obtain the data processing results and the data processing process.

[0109] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method of data querying, characterized by, The application is applied to a downstream system, comprising: receiving a data query request sent by an upstream system, the data query request indicating a service code corresponding to the upstream system; querying a target conversion message corresponding to the service code from a conversion message according to the service code; wherein the conversion message is obtained by field conversion on historical messages sent by the upstream system according to a preset association relationship; the preset association relationship indicates a corresponding relationship between a first field in the historical message and a second field in the conversion message; determining a target association field corresponding to the target second field from a first field corresponding to the upstream system according to a target second field in the target conversion message; generating a data query result corresponding to the service code according to the target association field and the target second field, and feeding back the data query result to the upstream system.

2. The method of claim 1, wherein, Before the receiving a data query request sent by an upstream system, further comprising: parsing a first field set from historical messages sent by the upstream system; matching an association field corresponding to each second field from the first field set respectively; for each second field, associating the second field with the association field corresponding to the second field to generate the preset association relationship.

3. The method of claim 2, wherein, After the generating the preset association relationship, before the receiving a data query request sent by an upstream system, further comprising: according to the preset association relationship, setting a field value of the association field as a field value of the second field to generate the conversion message.

4. The method of claim 2, wherein, The matching an association field corresponding to each second field from the first field set respectively, comprising: traversing each first field in the first field set, respectively performing fuzzy matching with each second field to generate a matching result; in a case where the matching result indicates that a matching degree is greater than a preset threshold, determining the association field.

5. The method of claim 2, wherein, In a case where the upstream system is multiple, the for each second field, associating the second field with the association field corresponding to the second field to generate the preset association relationship, comprising: determining service codes corresponding to each upstream system respectively; for each second field: associating the service code, the second field, and the association field corresponding to the second field to obtain the preset association relationship.

6. The method of claim 1, wherein: the upstream system is a service system, and the downstream system is a billing system.

7. The method of claim 6, wherein, The generating a data query result corresponding to the service code according to the target association field and the target second field, comprising: determining a billing result according to a field value corresponding to the target second field; dynamically generating a display page according to the target association field and the billing result, and taking the display page as the data query result.

8. An apparatus for data query, characterized by comprising: a receiving module, configured to receive a data query request sent by an upstream system, the data query request indicating a service code corresponding to the upstream system; The query module is configured to query a target conversion message corresponding to the service code from a conversion message according to the service code, wherein the conversion message is obtained by performing field conversion on a historical message sent by the upstream system according to a preset association relationship, and the preset association relationship indicates a corresponding relationship between a first field in the historical message and a second field in the conversion message. The determination module is configured to determine a target association field corresponding to the target second field from a first field corresponding to the upstream system according to the target second field in the target conversion message. The generation module is configured to generate a data query result corresponding to the service code according to the target association field and the target second field, and feed back the data query result to the upstream system.

9. An electronic device for data processing, characterized by The computer program product includes: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the method of any one of claims 1-7.

10. A computer readable medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the method of any one of claims 1-7.

11. A computer product comprising a computer program which, when executed by a processor, implements the method of any one of claims 1-7.

Images