Method, device and equipment for querying cross-system data and storage medium

Abstract

The application relates to the fields of data processing and financial technology, and discloses a cross-system data query method and device, equipment and a storage medium. The method comprises the following steps: receiving a data query request for target data of at least one target data providing system in multiple data providing systems, which is sent by a target data consumption terminal, wherein the data query request comprises an ID parameter of the target data; querying a URL of the target data associated with the ID parameter of the target data according to the ID parameter of the target data; and outputting the URL of the target data to the target data consumption terminal. According to the technical scheme, it is not necessary to manually copy and query data in each data providing system, so that the query process of the user is simplified, efficient data query is realized, and the data details are not involved in the data query process, so that the safety of the data in the data providing system is ensured.

Description

[Technical Field]

[0001] This application relates to the fields of data processing and financial technology, and in particular to a method, apparatus, device and storage medium for querying cross-system data. [Background Technology]

[0002] When conducting data query operations within an enterprise, data queries often involve cross-system queries, such as... Figure 1 As shown, what business personnel often need to do is to first find the required data A in the first system based on the data ID, and then copy the data B ID into the second system to find data B. If data B contains the data C ID and data C needs to be found in the third system, the data C ID needs to be copied again to the third system to find data C. If there is more data to be searched, multiple copy and paste operations and multiple cross-system login queries are required.

[0003] The above operation will have the following problems:

[0004] Firstly, copying and pasting data is often done manually, which easily leads to copying or pasting errors.

[0005] Secondly, the copied data cannot be queried directly; you must log in to another system before you can query it. Cross-system queries may require additional login operations, and the manual copying operations generated by cross-system queries are also quite time-consuming.

[0006] For example, in a full-chain financial transaction, the process of a user purchasing goods, placing an order, making a payment, and accounting statistics involves user information, product information, order information, payment information (such as internal and external payment channels), transaction information, and accounting information. In enterprise applications, this information is often stored independently and has certain data control permissions. If you want to access this data, you need to log in across systems. It is often troublesome to switch platforms to query data every time. Fully developing the code details is also quite complicated, and permissions are not easy to manage.

[0007] Overall, cross-system business data queries often face the following problems:

[0008] 1) Copying business IDs across systems is prone to errors.

[0009] 2) Cross-system data querying involves many steps and is time-consuming and labor-intensive.

[0010] 3) Querying data from other systems within a single system involves security access control, making it difficult to query all data. [Summary of the Invention]

[0011] This application provides a method, apparatus, device, and storage medium for querying cross-system data, aiming to solve the problems of inefficient and time-consuming manual copying and querying in the financial field, and the difficulty in querying all data due to security permission control in related technologies.

[0012] In a first aspect, embodiments of this application provide a method for querying cross-system data, including:

[0013] The system receives a data query request sent by a target data consumption terminal for target data in at least one target data providing system among multiple data providing systems, wherein the data query request includes: the ID parameter of the target data;

[0014] Based on the ID parameter of the target data, query the URL of the target data associated with the ID parameter of the target data;

[0015] The URL of the target data is output to the target data consumption terminal.

[0016] Secondly, embodiments of this application provide a cross-system data query device, including:

[0017] The receiving module is configured to receive a data query request sent by the target data consumption terminal for target data of at least one target data providing system among multiple data providing systems, wherein the data query request includes: the ID parameter of the target data;

[0018] The query module is used to query the URL of the target data associated with the ID parameter of the target data based on the ID parameter of the target data;

[0019] The output module is used to output the URL of the target data to the target data consumption terminal.

[0020] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described cross-system data query method.

[0021] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the aforementioned cross-system data query method.

[0022] In the above-described cross-system data query method, apparatus, device, and storage medium, a data query request for target data from at least one target data provider among multiple data provider systems is received from a target data consuming terminal. The data query request includes: an ID parameter of the target data; a URL of the target data associated with the ID parameter of the target data is queried based on the ID parameter; and the URL of the target data is output to the target data consuming terminal. In this invention, the proposed cross-system data query method can receive a data query request from a target data consuming terminal for target data from at least one target data provider among multiple data provider systems, and then query the URL of the associated target data based on the ID parameter in the data query request. This allows the target data consuming terminal to directly query data from different data provider systems, achieving cross-system data querying without manually copying and querying data in each data provider system, thus simplifying the user's query process and achieving efficient data querying. Furthermore, the data query process does not involve detailed data information, thereby ensuring the security of the data in the data provider systems. [Attached Image Description]

[0023] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 A schematic flowchart illustrating a cross-system data query method in related technologies is shown.

[0025] Figure 2 A schematic flowchart of a cross-system data query method according to an embodiment of this application is shown.

[0026] Figure 3 A detailed schematic diagram of a cross-system data query method according to an embodiment of this application is shown.

[0027] Figure 4 A block diagram of a transaction risk identification model training apparatus according to an embodiment of this application is shown.

[0028] Figure 5 A schematic diagram of the structure of a computer device according to an embodiment of this application is shown.

[0029] Figure 6 Another structural schematic diagram of a computer device according to an embodiment of this application is shown.

Detailed Implementation Methods

[0030] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0031] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0032] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0033] To address the inefficiency and time-consuming nature of manual copying and querying in the financial field, as well as the difficulty in querying all data due to security access control, this application proposes a method, apparatus, device, and storage medium for querying cross-system data.

[0034] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0035] It should be noted that the embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0036] Foundational technologies for artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interactive systems, and mechatronics. AI software technologies mainly encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0037] Please see Figure 2 , Figure 2 A schematic flowchart of a cross-system data query method according to an embodiment of this application is shown. This cross-system data query method is used to solve technical problems in the financial field, such as the inefficiency and time-consuming manual copying queries, and the difficulty in querying all data due to security access control.

[0038] like Figure 2As shown, a cross-system data query method according to an embodiment of this application can be used in a data transfer station system. The method flow includes:

[0039] Step S201: Receive a data query request sent by the target data consumption terminal for target data of at least one target data providing system among multiple data providing systems, wherein the data query request includes: the ID (Identity Document) parameter of the target data;

[0040] Data consumption terminals include consumer terminals in financial transactions and terminals that require data querying.

[0041] Multiple data providing systems can be different systems in the financial field, such as those for user purchases, order placement, payments, and financial statistics. This includes user information systems, product information systems, payment systems, and transaction systems. In related technologies, these systems store their own information independently. Accessing data from these systems requires cross-system logins and switching platforms to query data each time. In this invention, after a user issues a data query request, the system can directly query the URL (Uniform Resource Locator) of the corresponding system, which is then returned for the data consumption terminal to access, eliminating the need for the user to switch between different systems.

[0042] Data query requests can be made using network communication methods such as HTTP and TCP, depending on the service methods provided by the data providing system.

[0043] Step S202: Based on the ID parameter of the target data, query the URL of the target data associated with the ID parameter of the target data;

[0044] In one embodiment, preferably, step S202 includes:

[0045] Based on the ID parameter of the target data, determine the target data providing system to which the target data belongs and its corresponding URL;

[0046] The URL corresponding to the target data providing system is determined as the URL of the target data.

[0047] The target data can be data from a single data source belonging to a certain data provider system, or data from multiple data sources from multiple data provider systems that needs to be queried across systems.

[0048] When it is determined that the target data belongs to a target data providing system, the target data providing system to which the target data belongs and its corresponding URL can be determined directly based on the ID parameter of the target data, and then the data is sent to the target data consuming terminal via that URL.

[0049] For example, when a target data consumer terminal needs to query data in data provider system A, the data transfer station system can directly query the URL of data provider system A based on the ID parameter of the target data.

[0050] When it is determined that the target data belongs to multiple target data providing systems, the URL of each target data providing system is determined sequentially according to the data query order;

[0051] According to the data query order, output the URL of each target data providing system to the target data consumption terminal.

[0052] For example, when a target data consumer terminal needs to query data C through data providing systems A, B, and C, such as Figure 3 As shown, the data transfer station system first generates the URL for querying the data details of system A based on the data ID, then generates the URL for querying the data details of system B based on the ID of data B, and finally generates the URL for querying the data details of system C based on the ID of data C.

[0053] For example, if a user needs to query detailed order data, they send an order data query request to the data transfer station system. The request includes ID parameters such as order ID and order type. The system retrieves basic order information using the order ID and order type. During the query, the data transfer station system finds the cached order data provider based on the order type. Orders often contain product IDs. The user then selects the product ID and product type. Similarly, the system finds the service providing product data based on the product type and queries the product information using the product ID. For more detailed product information, the user simply uses the provided product service query URL. Clicking this URL directly redirects the user to the product management system, simplifying the query process and enabling efficient data retrieval. Furthermore, the data query process does not involve detailed data information, thus ensuring data security within the data provider system.

[0054] Step S203: Output the URL of the target data to the target data consumption terminal.

[0055] In this embodiment, a data query request sent by a target data consumer terminal for target data in at least one of multiple data providing systems can be received. Then, based on the ID parameter in the data query request, the URL of the associated target data can be queried. This allows the target data consumer terminal to directly query data from different data providing systems, enabling cross-system data queries without manually copying and querying data from each system. This simplifies the user's query process and achieves efficient data retrieval. Furthermore, the data query process does not involve detailed data information, thus ensuring the security of the data in the data providing systems.

[0056] Of course, before performing data queries, the method also includes:

[0057] Receive a service registration request from each data providing system, wherein the service registration request includes service information between the data providing system and each corresponding data consuming terminal, and the service information includes a data ID parameter and the URL address of the data providing system;

[0058] Based on the service registration request, the service information between each data providing system and the corresponding data consuming terminal is associated and stored.

[0059] In this embodiment, such as Figure 3 As shown, a registration center service needs to be started first. That is, each data provider system sends a service registration request to the service registration center of the data transfer station system. The service registration request includes service information between the data provider system and each corresponding data consumer terminal. The service information includes data ID parameters and the URL address of the data provider system. The data transfer station system can associate and store the data ID parameters and the URL address of the data provider system according to the service information.

[0060] For example, if data provider system A wants to register a service, it can send a service registration request to the data transfer station system. The service registration request includes service information between data provider system A and each of its corresponding data consumption terminals. In this way, the data transfer station system will store the service information in its cache so that it can be retrieved when it receives a data query request.

[0061] To facilitate querying, the service information of all data provider systems can be stored in a mapping table. One column of the table contains the data ID parameter, and the other column contains the URL address of the data provider system; these two are stored in a corresponding manner. The data ID parameter can include both the data ID and the data type, with the data type indicating which data provider system the data belongs to.

[0062] In other words, in this invention, the data transfer station system does not directly query data. However, in order to allow navigation within the data ID, it needs to query data indirectly. This indirect query method involves the data transfer station system internally building a service consumption terminal, externally providing a data provider system library, and in between, building a registry center for service discovery between the data consumption terminal and the data provider system. The data provider system integrates the logic that needs to query business data IDs externally. Here, it doesn't need to query data details, but when it involves navigation within a data link, it needs to retrieve the link data ID. When the data consumption terminal calls this function, the data URL can be returned to the data consumption terminal.

[0063] Because the query process only involves the data ID and does not query detailed data within the system, sensitive information within the system will not be leaked, thus ensuring the security of the data provided in the system.

[0064] In one embodiment, preferably, the method further includes:

[0065] After the data providing system service is successfully registered, the data providing system service will be pushed to each data consuming terminal;

[0066] In this embodiment, the data providing system registers its services with the registration center, and the registration center pushes the data providing system's services to the data consuming terminal. Once the data consuming terminal senses the service interface of the data providing system, it can initiate a remote data query request as needed. The specific data to be queried is also based on actual needs, querying detailed data from the data providing system.

[0067] In one embodiment, preferably, the method further includes:

[0068] Receive service information update requests sent by the data provider system;

[0069] Update the associated stored service information according to the service information update request.

[0070] In this embodiment, when the service information in any data providing system is updated, a service information update request can be sent to the data transfer station system, thereby updating the associated service information stored in the cache of the data transfer station system.

[0071] In one embodiment, preferably, the method further includes:

[0072] The service availability status between each data providing system and its corresponding data consuming terminal is monitored through heartbeat requests.

[0073] When the service liveness status between any data providing system and its corresponding data consuming terminal is detected as not alive, the stored service information between the data providing system and its corresponding data consuming terminal will be deleted.

[0074] In this embodiment, a heartbeat request can be used to monitor the service liveness status between each data providing system and each corresponding data consuming terminal. If the service liveness status is detected as live, the corresponding service information can continue to be stored in the cache for use when querying data. If the service liveness status is detected as not live, the corresponding service information can be directly deleted from the cache to save cache space.

[0075] In one embodiment, preferably, the method further includes:

[0076] Receive the selection operation of the target data URL by the target data consuming terminal;

[0077] Based on the selected operation, the service interface will be redirected to the URL address corresponding to the target data providing system.

[0078] In this embodiment, after determining the URL of the target data, when business personnel need to query detailed data information, they can click the URL link to directly jump to the data provider system to which the data belongs to query the data. At this time, the data query behavior is performed in the data provider system to which the data belongs, and the specific permission control is also guaranteed by the data provider system. This not only satisfies the purpose of data query but also effectively satisfies the purpose of data permission security control.

[0079] Figure 4 A block diagram of a transaction risk identification model training apparatus according to an embodiment of this application is shown.

[0080] like Figure 4 As shown, in a second aspect, embodiments of this application provide a cross-system data query device 40, comprising:

[0081] Receiving module 41 is used to receive a data query request sent by a target data consumption terminal for target data of at least one target data providing system in multiple data providing systems, wherein the data query request includes: the ID parameter of the target data;

[0082] Query module 42 is used to query the URL of the target data associated with the ID parameter of the target data based on the ID parameter of the target data;

[0083] Output module 43 is used to output the URL of the target data to the target data consumption terminal.

[0084] In one embodiment, preferably, the device further includes:

[0085] The request receiving module is used to receive service registration requests from each data providing system, wherein the service registration request includes service information between the data providing system and each corresponding data consuming terminal, and the service information includes a data ID parameter and the URL address of the data providing system;

[0086] The storage module is used to associate and store the service information between each data providing system and the corresponding data consuming terminal according to the service registration request.

[0087] In one embodiment, preferably, the query module 42 includes:

[0088] The first determining unit is used to determine the target data providing system to which the target data belongs and its corresponding URL based on the ID parameter of the target data;

[0089] The second determining unit is used to determine the URL corresponding to the target data providing system as the URL of the target data.

[0090] In one embodiment, preferably, the device further includes:

[0091] The determination module is used to determine the URL of each target data providing system in sequence according to the data query order when it is determined that the target data belongs to multiple target data providing systems;

[0092] The output module is also used for:

[0093] According to the data query order, output the URL of each target data providing system to the target data consumption terminal.

[0094] In one embodiment, preferably, the device further includes:

[0095] The push module is used to push the services of the data providing system to each data consumption terminal after the data providing system service is successfully registered.

[0096] The receiving module is also used for:

[0097] Receive service information update requests sent by the data provider system;

[0098] The update module is used to update the associated stored service information according to the service information update request.

[0099] In one embodiment, preferably, the device further includes:

[0100] The monitoring module is used to monitor the service liveness status between each data providing system and each corresponding data consuming terminal through heartbeat requests;

[0101] The processing module is used to delete the stored service information between any data providing system and the corresponding data consuming terminal when the service liveness status between any data providing system and the corresponding data consuming terminal is detected to be not alive.

[0102] In one embodiment, preferably, the device further includes:

[0103] The receiving module is also used for:

[0104] Receive the selection operation of the target data URL by the target data consuming terminal;

[0105] The jump module is used to jump the service interface to the URL address corresponding to the target data providing system based on the selected operation.

[0106] In the above-described cross-system data query method, apparatus, device, and storage medium, a data query request for target data from at least one target data provider among multiple data provider systems is received from a target data consuming terminal. The data query request includes: an ID parameter of the target data; a URL of the target data associated with the ID parameter of the target data is queried based on the ID parameter; and the URL of the target data is output to the target data consuming terminal. In this invention, the proposed cross-system data query method can receive a data query request from a target data consuming terminal for target data from at least one target data provider among multiple data provider systems, and then query the URL of the associated target data based on the ID parameter in the data query request. This allows the target data consuming terminal to directly query data from different data provider systems, achieving cross-system data querying without manually copying and querying data in each data provider system, thus simplifying the user's query process and achieving efficient data querying. Furthermore, the data query process does not involve detailed data information, thereby ensuring the security of the data in the data provider systems.

[0107] For specific limitations regarding the cross-system data query device, please refer to the limitations of the cross-system data query method described above, which will not be repeated here. Each module in the aforementioned cross-system data query device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0108] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used to communicate with external clients via a network connection. When the computer program is executed by the processor, it implements a cross-system data query method, server-side functionality, or steps.

[0109] In one embodiment, a computer device is provided, which may be a client, and its internal structure diagram may be as follows: Figure 6 As shown, the computer device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements a cross-system data query method, client-side functions or steps.

[0110] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0111] The computer device in this application embodiment exists in various forms, including but not limited to:

[0112] (1) Mobile communication devices: These devices are characterized by their mobile communication capabilities and primarily aim to provide voice and data communication. These terminals include: smartphones (e.g., iPhones), multimedia phones, feature phones, and low-end phones, etc.

[0113] (2) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, possessing computing and processing capabilities, and generally also have mobile internet access features. These terminals include PDAs, MIDs, and UMPCs, such as the iPad.

[0114] (3) Portable entertainment devices: These devices can display and play multimedia content. This category includes audio and video players (such as iPods), handheld game consoles, e-book readers, as well as smart toys and portable car navigation devices.

[0115] (4) Server: A device that provides computing services. The components of a server include a processor, hard disk, memory, system bus, etc. Servers are similar to general computer architectures, but because they need to provide highly reliable services, they have higher requirements in terms of processing power, stability, reliability, security, scalability, and manageability.

[0116] (5) Other electronic devices with data interaction functions.

[0117] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:

[0118] The system receives a data query request sent by a target data consumption terminal for target data in at least one target data providing system among multiple data providing systems, wherein the data query request includes: the ID parameter of the target data;

[0119] Based on the ID parameter of the target data, query the URL of the target data associated with the ID parameter of the target data;

[0120] The URL of the target data is output to the target data consumption terminal.

[0121] In one embodiment, preferably, the step further includes:

[0122] Receive a service registration request from each data providing system, wherein the service registration request includes service information between the data providing system and each corresponding data consuming terminal, and the service information includes a data ID parameter and the URL address of the data providing system;

[0123] Based on the service registration request, the service information between each data providing system and the corresponding data consuming terminal is associated and stored.

[0124] In one embodiment, preferably, querying the URL of the target data associated with the ID parameter of the target data according to the ID parameter of the target data includes:

[0125] Based on the ID parameter of the target data, determine the target data providing system to which the target data belongs and its corresponding URL;

[0126] The URL corresponding to the target data providing system is determined as the URL of the target data.

[0127] In one embodiment, preferably, the step further includes:

[0128] When it is determined that the target data belongs to multiple target data providing systems, the URL of each target data providing system is determined sequentially according to the data query order;

[0129] According to the data query order, output the URL of each target data providing system to the target data consumption terminal.

[0130] In one embodiment, preferably, the step further includes:

[0131] After the data providing system service is successfully registered, the data providing system service will be pushed to each data consuming terminal;

[0132] Receive service information update requests sent by the data provider system;

[0133] Update the associated stored service information according to the service information update request.

[0134] In one embodiment, preferably, the step further includes:

[0135] The service availability status between each data providing system and its corresponding data consuming terminal is monitored through heartbeat requests.

[0136] When the service liveness status between any data providing system and its corresponding data consuming terminal is detected as not alive, the stored service information between the data providing system and its corresponding data consuming terminal will be deleted.

[0137] In one embodiment, preferably, the step further includes:

[0138] Receive the selection operation of the target data URL by the target data consuming terminal;

[0139] Based on the selected operation, the service interface will be redirected to the URL address corresponding to the target data providing system.

[0140] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or computer device described above can be referred to the relevant descriptions on the server side and client side in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0141] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0142] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0143] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0144] It should be understood that although the terms "first," "second," etc., may be used to describe the setting units in the embodiments of this application, these setting units should not be limited to these terms. These terms are only used to distinguish the setting units from each other. For example, without departing from the scope of the embodiments of this application, the first setting unit may also be referred to as the second setting unit, and similarly, the second setting unit may also be referred to as the first setting unit.

[0145] Depending on the context, the word "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrase "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination," "in response to determination," "when detection (of the stated condition or event)," or "in response to detection (of the stated condition or event)."

[0146] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0147] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0148] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method for querying cross-system data, characterized in that, The method includes: The system receives a data query request sent by a target data consumption terminal for target data in at least one target data providing system among multiple data providing systems. The data query request includes an ID parameter for the target data, and the target data includes business link data in the financial field. Based on the ID parameter of the target data, query the URL of the target data associated with the ID parameter of the target data, which is used to directly jump to the target data providing system details page where the target data is located. The query process does not obtain the detailed information of the target data, but only queries the mapping relationship between the ID parameter and the URL. The URL of the target data is output to the target data consumer terminal, and the corresponding target data providing system performs permission control when redirected for access. When it is determined that the target data belongs to multiple target data providing systems, the URL of each target data providing system is determined sequentially according to the data query order; According to the data query order, output the URL of each target data providing system to the target data consumption terminal.

2. The cross-system data query method according to claim 1, characterized in that, The method further includes: Receive a service registration request from each data providing system, wherein the service registration request includes service information between the data providing system and each corresponding data consuming terminal, and the service information includes a data ID parameter and the URL address of the data providing system; Based on the service registration request, the service information between each data providing system and the corresponding data consuming terminal is associated and stored.

3. The cross-system data query method according to claim 2, characterized in that, Based on the ID parameter of the target data, query the URL of the target data associated with the ID parameter of the target data, including: Based on the ID parameter of the target data, determine the target data providing system to which the target data belongs and its corresponding URL; The URL corresponding to the target data providing system is determined as the URL of the target data.

4. The cross-system data query method according to claim 2, characterized in that, The method further includes: After the data providing system service is successfully registered, the data providing system service will be pushed to each data consuming terminal; Receive service information update requests sent by the data provider system; Update the associated stored service information according to the service information update request.

5. The cross-system data query method according to claim 2, characterized in that, The method further includes: The service availability status between each data providing system and its corresponding data consuming terminal is monitored through heartbeat requests. When the service liveness status between any data providing system and its corresponding data consuming terminal is detected as not alive, the stored service information between the data providing system and its corresponding data consuming terminal will be deleted.

6. The method for querying cross-system data according to any one of claims 1 to 5, characterized in that, The method further includes: Receive the selection operation of the target data URL by the target data consuming terminal; Based on the selected operation, the service interface will be redirected to the URL address corresponding to the target data providing system.

7. A cross-system data query device, characterized in that, include: The receiving module is used to receive a data query request sent by the target data consumption terminal for target data of at least one target data providing system in multiple data providing systems, wherein the data query request includes: the ID parameter of the target data, and the target data includes business link data in the financial field; The query module is used to query the URL of the target data associated with the ID parameter of the target data, which is used to directly jump to the target data providing system details page where the target data is located. The query process does not obtain the detailed information of the target data, but only queries the mapping relationship between the ID parameter and the URL. The output module is used to output the URL of the target data to the target data consumption terminal, and the corresponding target data providing system completes the permission control when redirecting to access it; The determination module is used to determine the URL of each target data providing system in sequence according to the data query order when it is determined that the target data belongs to multiple target data providing systems; The output module is also used for: According to the data query order, output the URL of each target data providing system to the target data consumption terminal.

8. A computer device, characterized in that, include: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, the instructions being configured to perform the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The device stores computer-executable instructions for performing the method as described in any one of claims 1 to 6.

Images