Data source access method and system and storage medium

Abstract

The invention provides a data source access method and system and a storage medium. And the service system initiates an access instruction to the target data source by calling the universal access interface provided by the intermediate system. The intermediate system determines a target protocol adapter from a plurality of pre-configured protocol adapters based on the type of the target data source, and different protocol adapters are configured to process communication protocols of different types of data sources. And the intermediate system controls the target protocol adapter to execute a data source access operation and sends an execution result of the access instruction to the service system. Wherein the data source access operation comprises the steps of converting an access instruction into a request message conforming to a communication protocol of a target data source, sending the request message to the target data source through a communication link with the target data source, and receiving a response message returned by the target data source, and analyzing the response message according to the communication protocol of the target data source to obtain an execution result of the access instruction.

Description

Technical Field

[0001] This specification relates to the field of Internet technology, and in particular to a data source access method, system, and storage medium. Background Technology

[0002] In modern information system architectures, data sources are diverse, encompassing various databases, file systems, message brokers, and real-time data streams. These data sources differ fundamentally in communication protocols, data formats, and read / write methods, making accessing these data sources a significant challenge.

[0003] For example, when a business system needs to access multiple data sources, the developers of the business system need to manually write code for each data source to implement the corresponding access logic. Furthermore, when a new or replaced data source needs to be added, the developers need to add or modify the code. This code development process leads to low data source access efficiency and high development costs. Therefore, a technical solution is needed that enables efficient and low-cost access to data sources.

[0004] The information in the background section is merely information known only to the inventor and does not imply that such information had entered the public domain before the date of this application, nor does it imply that it can be considered prior art in this disclosure. Summary of the Invention

[0005] This specification provides a data source access method, system, and storage medium. Business systems can access the data source by calling a general access interface, which improves the efficiency of data source access and reduces code development and maintenance costs.

[0006] Firstly, this specification provides a data source access method applied to an intermediate system communicating with multiple data sources, comprising: receiving an access instruction initiated by a business system for a target data source, the access instruction being initiated by the business system by calling a general access interface provided by the intermediate system; determining a target protocol adapter from a plurality of pre-configured protocol adapters based on the type of the target data source, wherein different protocol adapters are configured to handle communication protocols for different types of data sources; controlling the target protocol adapter to perform the following data source access operations: converting the access instruction into a request message conforming to the communication protocol of the target data source, sending the request message to the target data source through a communication link with the target data source, receiving a response message returned by the target data source, parsing the response message according to the communication protocol of the target data source to obtain the execution result of the access instruction; and sending the execution result of the access instruction to the business system.

[0007] In some embodiments, the intermediate system includes a management subsystem and an execution subsystem; receiving an access instruction initiated by a business system for a target data source includes: receiving the access instruction initiated by the business system for the target data source through the execution subsystem; before receiving the access instruction through the execution subsystem, the method further includes: receiving a pre-access request initiated by the business system for the target data source through the management subsystem and sending access guidance information to the business system, wherein the access guidance information is used to guide the business system to generate and send the access instruction to the execution subsystem.

[0008] In some embodiments, after receiving a pre-access request initiated by the business system for the target data source through the management subsystem, the method further includes: sending a guidance request to the execution subsystem through the management subsystem; and generating the access guidance information through the execution subsystem and returning the access guidance information to the management subsystem.

[0009] In some embodiments, the execution subsystem includes at least one execution device, each execution device being connected to at least a portion of the plurality of data sources, and the access guidance information including at least the identification information of a target execution device, wherein the target execution device is an execution device in the execution subsystem connected to the target data source; receiving access instructions initiated by the business system for the target data source through the execution subsystem includes: receiving access instructions initiated by the business system for the target data source through the target execution device.

[0010] In some embodiments, the access guidance information includes an access token; the access instruction includes the access token; invoking the target protocol adapter includes: authenticating the business system based on the access token, and invoking the target protocol adapter if the authentication is successful.

[0011] In some embodiments, the target data source includes at least one dataset; the pre-access request includes at least one of the following: identification information of the target data source, or identification information of at least a portion of the datasets in the target data source, wherein the identification information of the target data source and the identification information of the target datasets are pre-assigned to the business system by the management subsystem.

[0012] In some embodiments, the method further includes: receiving a registration request from the business system through the management subsystem, the registration request including at least one of the metadata of the target data source or the metadata of at least a portion of the datasets in the target data source; performing an identifier allocation operation through the management subsystem, the identifier allocation operation including at least one of the following: generating identifier information of the target data source based on the metadata of the target data source and storing the correspondence between the metadata of the target data source and its identifier information, or generating identifier information of the at least a portion of the datasets based on the metadata of the at least a portion of the datasets and storing the correspondence between the metadata of the at least a portion of the datasets and its identifier information; and sending a registration response to the business system through the management subsystem, the registration response including at least one of the identifier information of the target data source or the identifier information of the at least a portion of the datasets.

[0013] In some embodiments, the target data source includes at least one dataset; the pre-access request includes at least one of the following: metadata of the target data source, metadata of at least a portion of the datasets in the target data source.

[0014] In some embodiments, the pre-access request includes personalized access parameters of the business system to the target data source; controlling the target protocol adapter to perform data source access operations includes: controlling the target protocol adapter to perform data source access operations based on the personalized access parameters.

[0015] In some embodiments, the personalized access parameters include at least one of the following: a range parameter, used to characterize the location of the data to be read in the target data source; a format parameter, used to characterize the return format of the data to be read; and an encryption parameter, used to characterize the encryption method of the data to be read when it is returned.

[0016] In some embodiments, the access instruction represents a read access type to the target data source, the response message contains the target data requested to be read by the business system, and the step of parsing the response message according to the communication protocol of the target data source to obtain the execution result of the access instruction includes: parsing the response message according to the communication protocol of the target data source to obtain the target data represented in a first format, wherein the first format is the data format adopted by the target data source; and converting the target data from the first format to a second format, and obtaining the execution result of the access instruction based on the converted data, wherein the second format is a general data format preset by the intermediate system.

[0017] In some embodiments, converting the target data from the first format to the second format and obtaining the execution result of the access instruction based on the converted data includes: converting the target data from the first format to the second format, then converting the target data from the second format to the data format required to be returned by the business system, and obtaining the execution result of the access instruction based on the converted data.

[0018] In some embodiments, the access instruction includes the data format that the business system requires to be returned; or before receiving the access instruction, the method further includes: receiving a pre-access request initiated by the business system for the target data source, the pre-access request including the data format that the business system requires to be returned.

[0019] In some embodiments, the access instruction represents the access type of the target data source as a write type, the access instruction includes the target data that the business system requests to be written, and the step of converting the access instruction into a request message conforming to the communication protocol of the target data source includes: parsing the target data from the access instruction, converting the data format of the target data into the data format required by the target data source, and generating the request message based on the converted data according to the communication protocol of the target data source.

[0020] Secondly, this specification also provides a data source access method applied to a business system, comprising: sending an access instruction for a target data source to the intermediate system by calling a general access interface provided by the intermediate system, wherein the intermediate system is connected to multiple data sources and pre-configured with multiple protocol adapters, the multiple protocol adapters being used to handle communication protocols of different types of data sources; and receiving the execution result of the access instruction from the intermediate system, wherein the execution result is obtained by the intermediate system controlling the target protocol adapter to perform a data source access operation, the target protocol adapter corresponding to the type of the target data source, the data source access operation comprising: converting the access instruction into a request message conforming to the communication protocol of the target data source, sending the request message to the target data source through a communication link with the target data source, receiving a response message returned by the target data source, parsing the response message according to the communication protocol of the target data source, and obtaining the execution result of the access instruction.

[0021] Thirdly, this specification also provides an intermediate system comprising: at least one storage medium storing at least one instruction set; and at least one processor communicatively connected to the at least one storage medium, wherein the at least one processor reads the at least one instruction set during operation and executes the data source access method as described in any one of the first aspects above according to the instructions of the at least one instruction set.

[0022] Fourthly, this specification also provides a business system, comprising: at least one storage medium storing at least one instruction set; and at least one processor communicatively connected to the at least one storage medium, wherein the at least one processor reads the at least one instruction set during operation and executes the data source access method as described in the second aspect above according to the instructions of the at least one instruction set.

[0023] Fifthly, this specification also provides a computer-readable non-transitory storage medium, wherein the computer-readable non-transitory storage medium stores at least one instruction set, which, when executed by at least one processor, implements the data source access method as described in any one of the first aspects above, or the data source access method as described in the second aspect above.

[0024] Other functionalities of the data source access methods, systems, and storage media provided in this specification will be partially listed in the following description. The inventive aspects of the data source access methods, systems, and storage media provided in this specification can be fully understood through practice or use of the methods, apparatus, and combinations described in the detailed examples below. Attached Figure Description

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

[0026] Figure 1 A schematic diagram of a data source access scenario provided according to an embodiment of this specification is shown; Figure 2 A hardware structure diagram of a computing system provided according to an embodiment of this specification is shown; Figure 3 A flowchart of a data source access method provided according to an embodiment of this specification is shown; Figure 4 A flowchart illustrating another data source access method provided according to an embodiment of this specification is shown. Detailed Implementation

[0027] The following description provides specific application scenarios and requirements for this specification, intended to enable those skilled in the art to make and use the contents of this specification. Various partial modifications to the disclosed embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments and applications without departing from the spirit and scope of this specification. Therefore, this specification is not limited to the embodiments shown, but rather to the widest scope consistent with the claims.

[0028] The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not restrictive. For example, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein may also include the plural forms. When used in this specification, the terms “comprising,” “including,” and / or “containing” mean that the associated integers, steps, operations, elements, and / or components are present, but do not exclude the presence of one or more other features, integers, steps, operations, elements, components, and / or groups, or that other features, integers, steps, operations, elements, components, and / or groups may be added to the system / method.

[0029] Considering the following description, these and other features of this specification, as well as the operation and function of the related components of the structure, and the economy of assembly and manufacture of the parts, can be significantly improved. All of these form part of this specification with reference to the accompanying drawings. However, it should be clearly understood that the drawings are for illustrative and descriptive purposes only and are not intended to limit the scope of this specification. It should also be understood that the drawings are not drawn to scale.

[0030] The flowcharts used in this specification illustrate operations implemented according to some embodiments of this specification. It should be clearly understood that the operations in the flowcharts may not be implemented in a sequential order. Instead, the operations may be implemented in reverse order or simultaneously. Furthermore, one or more additional operations may be added to the flowcharts. One or more operations may be removed from the flowcharts.

[0031] The embodiments described in this specification can be applied to data source access scenarios, especially those involving access to different types of data sources. Data source access refers to the process by which a business system interacts with a data source to read or write data. A data source can refer to any entity, system, or service that can provide data to a system or application. Simply put, a data source is the origin or source of data.

[0032] In some embodiments, data access logic is encoded within the business system, which communicates directly with the data source. Specifically, when the business system needs to access a target data source, it directly executes the access logic code corresponding to the target data source and returns the access result to the operator. It is understood that different data source types require different access logic codes. For example, when accessing a first data source, the business system executes the first access logic code; when accessing a second data source, it executes the second access logic code; and when accessing a third data source, it executes the third access logic code.

[0033] Because the access logic code is encoded in the business system, and different data sources correspond to different access logic codes, whenever a new or replaced data source is added, the corresponding data access logic code needs to be added or modified in the business system, resulting in low access efficiency of the data source and high development costs.

[0034] Therefore, this specification provides a data source access method, system, and storage medium. When a business system accesses a data source, it can invoke a general access interface provided by an intermediate system to initiate access to the target data source. Based on the type of the target data source, the intermediate system determines the target protocol adapter from a set of pre-configured protocol adapters and controls the target protocol adapter to perform the data source access operation. In this scheme, the intermediate system is responsible for communicating with the data source, thus eliminating the need for the business system to communicate directly with the data source; instead, it can access the data source by invoking the general access interface. Developers of the business system do not need to write or modify the access logic code for each data source, improving the efficiency of data source access and reducing code development and maintenance costs.

[0035] Figure 1 A schematic diagram of a data source access scenario 100 provided according to an embodiment of this specification is shown. Figure 1 As shown, scenario 100 may include business system 110, intermediate system 120, and data source 130. Among them, intermediate system 120 is used to provide intermediate services between business system 110 and data source 130.

[0036] Data source 130 refers to a system that stores or provides data. Figure 1 The scenario 100 shown may include multiple data sources 130. These multiple data sources 130 may be of different types. For example, each data source 130 may be of one of the following types: database, file system, message queue, etc.

[0037] Databases are data sources used for the systematic storage, management, and retrieval of data; examples include MySQL, Oracle, and Redis. Different types of databases can use different communication protocols. For instance, MySQL uses the proprietary TCP / IP protocol, while Redis uses RESP (Redis Serialization Protocol). Different types of databases also employ different data formats. For example, relational databases like MySQL and Oracle store data in tables, while Redis stores data in key-value pairs.

[0038] A file system is a mechanism within an operating system used to organize, store, and manage files and directories. For example, the file format used may be CSV (Comma-Separated Values) or JSON (JavaScript Object Notation). File systems logically manage data on storage devices through a unified hierarchical directory structure (such as a tree structure). The data format of a file system is usually determined by its type; for example, ext4, NTFS, and APFS each define their own file metadata (permissions, timestamps, size) and data block storage layout. File system read and write operations are primarily performed through system calls provided by the operating system (such as open, read, write, and close). The accessing party needs to directly manipulate byte streams and file pointers and parse the file content itself.

[0039] A message queue is an asynchronous communication mechanism used to reliably deliver data between components in a distributed system. It employs asynchronous publish-subscribe or point-to-point communication patterns. Data is organized into structured message units (containing message headers and bodies), facilitating serialization and cross-platform parsing. The read / write operation follows a producer-consumer model. Producers send messages to the queue (writing), and consumers subscribe to or retrieve messages from the queue (reading). It supports various modes such as point-to-point and publish / subscribe, and ensures message integrity through persistence, acknowledgment mechanisms, and retry strategies, achieving system decoupling, traffic shaping, and asynchronous processing.

[0040] Each data source 130 may include one or more datasets. A dataset refers to a complete collection of data organized according to certain structures and rules within the data source 130 to represent a specific type of business or theme. A dataset can be defined as a group of data records with the same data schema. Data sets can exist in the form of tables, files, document collections, or streaming data. A dataset contains multiple fields or attributes to describe the characteristics of an entity. A dataset is the basic unit for data analysis, processing, and modeling. For example, a user behavior data source may contain multiple datasets, such as "user login logs" and "order transaction records," each corresponding to different business scenarios and data formats.

[0041] Business system 110 refers to a system with data source access requirements. In this specification, business system 110 can be any type of system designed to support business operations, such as Enterprise Resource Planning (ERP) systems, Customer Relationship Management (CRM) systems, Supply Chain Management (SCM) systems, Warehouse Management System (WMS) systems, financial management systems, human resource management systems, Office Automation (OA) systems, Manufacturing Execution System (MES) systems, Point of Sale (POS) systems, Hospital Information System (HIS) systems, bank transaction systems, risk control systems, etc.

[0042] Business system 110 is a system with data processing and computing capabilities. In some embodiments, business system 110 may include hardware devices with data processing functions and the necessary programs to drive the hardware devices. Business system 110 can access data sources by driving the hardware devices to execute the aforementioned programs. In some embodiments, business system 110 may have a display screen, or business system 110 may have an external display screen. Business system 110 can provide an interactive page through the display screen. For example, business system 110 displays function buttons on the display screen. Users can issue data source access commands by clicking function buttons on the interactive page.

[0043] The intermediate system 120 can be a computing system with a certain computing capability. For example... Figure 1 As shown, the intermediate system 120 is communicatively connected to the business system 110 and multiple data sources 130.

[0044] The intermediate system 120 provides a general access interface to the business system 110. When the business system 110 needs to access any data source 130, it can call this general access interface to access the data source.

[0045] The intermediate system 120 includes multiple pre-configured protocol adapters, each specifically encapsulating and processing the communication protocol for a particular type of data source. For example, a first protocol adapter encapsulates and processes a first data source. A second protocol adapter encapsulates and processes a second data source. A third protocol adapter encapsulates and processes a third data source. In some embodiments, the multiple protocol adapters exist in the intermediate system 120 in a plug-in manner. In some embodiments, the multiple protocol adapters exist in the intermediate system 120 in a modular manner.

[0046] Protocol adapters can be core functional modules within an intermediate system, essentially serving as protocol conversion and communication proxy units. Each protocol adapter is specifically configured to understand and handle a particular type of data source communication protocol. Its core function is to shield the communication details of heterogeneous lower-layer data sources and provide a unified calling interface to the upper layer, thereby decoupling the business system from the data source. By introducing protocol adapters, the compatibility logic for different protocols, which would originally be handled by the business system, is decentralized and solidified within the intermediate system. The business system does not need to concern itself with the protocol used by the target data source; it only needs to issue standardized requests, and the intermediate system automatically selects and invokes the corresponding protocol adapter to complete the interaction with the target data source.

[0047] The intermediate system 120 is communicatively connected to multiple data sources 130. Specifically, the multiple data sources 130 can communicate with multiple protocol adapters in the intermediate system 120. For example, a first protocol adapter is communicatively connected to a first data source; a second protocol adapter is communicatively connected to a second data source; and a third protocol adapter is communicatively connected to a third data source.

[0048] Both the business system 110 and the intermediate system 120 may include one or more computing devices. For example, when the intermediate system 120 or the business system 110 includes multiple computing devices, these multiple computing devices may be deployed using server cluster architecture, distributed architecture, cloud service architecture, or other similar methods.

[0049] The following is combined with Figure 1The data source access process is illustrated with an example. For instance, intermediate system 120 is pre-configured with a first protocol adapter, a second protocol adapter, and a third protocol adapter. A target user triggers a service request with the intent to query a first data source within business system 110. Business system 110 detects this service request and initiates an access command for the first data source to intermediate system 120. Upon receiving the access command from business system 110, intermediate system 120 determines the first protocol adapter from the pre-configured protocol adapters to handle the first data source based on its type. Subsequently, intermediate system 120 invokes the first protocol adapter to trigger it to perform the following operations: The first protocol adapter converts the access command into a request message conforming to the communication protocol of the first data source. The first protocol adapter sends the request message to the first data source through the communication link and receives the response message returned by the first data source. The first protocol adapter parses the response message according to the communication protocol of the first data source to obtain the execution result of the access command. Intermediate system 120 sends the execution result of the access command to business system 110. After receiving the execution result, business system 110 displays it to the target user on the interactive interface.

[0050] The data source access method provided in this specification can be executed in cooperation between the business system 110 and the intermediate system 120. The business system 110 and the intermediate system 120 may store data or instructions for executing the data source access method described in this specification, and may execute or be used to execute said data or instructions. In some embodiments, the business system 110 and the intermediate system 120 may include hardware devices with data processing capabilities and the necessary programs required to drive the hardware devices.

[0051] In some embodiments, the intermediate system 120 and the business system 110 can be independent of each other. In this case, the intermediate system 120 and the business system 110 can correspond to different hardware devices. In some embodiments, the intermediate system 120 can be integrated into the business system 110. For example, the intermediate system 120 can be integrated into the business system 110 in the form of an SDK (Software Development Kit). Alternatively, the intermediate system 120 can be integrated into the business system 110 in the form of a module / unit.

[0052] The communication medium between the business system 110 and the intermediate system 120, and between the intermediate system 120 and the data source 130, can be a network. A network can facilitate the exchange of information or data.

[0053] In some embodiments, the network can be any type of wired or wireless network, or a combination thereof. For example, the network may include a cable network, a wired network, a fiber optic network, a telecommunications network, an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network (MAN), a public switched telephone network (PSTN), a Bluetooth network™, a ZigBee™ short-range wireless network, a near field communication (NFC) network, or a similar network.

[0054] In some embodiments, the network may include one or more network access points. For example, the network may include wired or wireless network access points, such as base stations or internet switching points, through which the business system 110 can connect to the network with one or more components of the intermediate system 120 and the data source 130 to exchange data or information.

[0055] It should be understood that Figure 1 The number of business systems 110 and data sources 130 shown is merely illustrative. Depending on implementation needs, there can be any number of business systems 110 and data sources 130.

[0056] Figure 2 A schematic diagram of the hardware structure of a computing system 200 according to an embodiment of this specification is shown. The computing system 200 can be used as... Figure 1 The business system 110 in the system executes the data source access method described in this specification. The computing system 200 can also serve as... Figure 1 The intermediate system 120 executes the data source access method described in this specification.

[0057] like Figure 2 As shown, the computing system 200 may include at least one storage medium 230 and at least one processor 220. In some embodiments, the computing system 200 may also include a communication port 250 and an internal communication bus 210. The computing system 200 may also include I / O components 240.

[0058] The internal communication bus 210 can connect to different system components. For example, the internal communication bus 210 can connect to storage medium 230, processor 220, communication port 250, and I / O component 240, etc.

[0059] I / O component 240 supports input / output between computing system 200 and other components.

[0060] Communication port 250 is used for data communication between computing system 200 and the outside world. For example, communication port 250 can be used for data communication between computing system 200 and wireless network. Communication port 250 can be a wired communication port or a wireless communication port.

[0061] Storage medium 230 may include a data storage device. The data storage device may be a computer-readable non-transitory storage medium or a computer-readable temporary storage medium. For example, the data storage device may include one or more of a disk 232, a read-only storage medium (ROM) 234, or a random access storage medium (RAM) 236. Storage medium 230 also includes at least one instruction set stored in the data storage device. The instruction set may include computer program code, which may include programs, routines, objects, components, data structures, procedures, modules, etc. Storage medium 230 stores at least one set of instructions, which are computer program code. When these instructions are retrieved and executed by a processor, they can instruct the processor to perform specific functions or steps, such as the various methods and steps described later in this application.

[0062] At least one processor 220 may be communicatively connected to at least one storage medium 230. When the computing system 200 is running, at least one processor 220 reads the at least one set of instructions and executes the methods and steps provided in this specification according to the instructions of the at least one set of instructions. Processor 220 may be in the form of one or more processors. In some embodiments, processor 220 may include one or more hardware processors, such as microcontrollers, microprocessors, reduced instruction set computers (RISC), application-specific integrated circuits (ASICs), application-specific instruction set processors (ASIPs), central processing units (CPUs), graphics processing units (GPUs), physical processing units (PPUs), microcontroller units, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), advanced RISC machines (ARMs), programmable logic devices (PLDs), any circuit or processor capable of performing one or more functions, or any combination thereof.

[0063] For illustrative purposes only, the accompanying drawings show only one processor 220 for the computing system 200. However, it should be noted that the computing system 200 may also include multiple processors; therefore, the operations and / or method steps disclosed herein may be executed by one processor or by multiple processors in combination. For example, if the processor 220 of the computing system 200 described in this specification executes steps A and B, it should be understood that steps A and B may also be executed jointly or separately by two different processors 220 (e.g., a first processor executes step A, a second processor executes step B, or the first and second processors jointly execute steps A and B).

[0064] Figure 3 A flowchart of a data source access method P300 according to an embodiment of this specification is shown. As described above, the business system and the intermediate system can execute the data source access method P300. Figure 3 As shown, the data source access method P300 may include S310-S340.

[0065] S310: The business system sends an access command for the target data source to the intermediate system by calling the general access interface provided by the intermediate system.

[0066] Correspondingly, the intermediate system receives access commands from the business system for the target data source.

[0067] The general access interface is a unified call entry point provided by the intermediate system to the business system. The business system can initiate access commands to different data sources by calling this general access interface.

[0068] The target data source is any one of multiple data sources that the business system requests to access.

[0069] An access command is a message sent by a business system to an intermediate system to request access to a target data source. The access command includes the information required to complete the access to the target data source.

[0070] For example, a target user triggers a service request within the business system with the intent to query a target data source. The business system detects this service request and sends an access instruction for the target data source to the intermediate system by calling a general access interface provided by the intermediate system.

[0071] By calling the general access interface provided by the intermediate system, business systems do not need to develop and maintain separate access logic code for each data source. On the one hand, this calling method simplifies the complexity of business system integration, improves development efficiency and system maintainability. On the other hand, when the data source changes or a new data source is added, only the intermediate system needs to be adapted; the business system does not need to be modified, thereby enhancing the flexibility and scalability of the business system and reducing operation and maintenance costs and error risks.

[0072] S320: The intermediate system determines the target protocol adapter from a plurality of pre-configured protocol adapters based on the type of the target data source, wherein different protocol adapters are used to handle the communication protocols of different types of data sources.

[0073] Multiple protocol adapters are pre-configured by the intermediate system. Different protocol adapters are used to handle communication protocols for different types of data sources. For example, the intermediate system pre-configures a first protocol adapter for MySQL databases; a second protocol adapter for CSV file systems; and a third protocol adapter for Kafka message queues.

[0074] Upon receiving an access command for a target data source, the intermediate system determines the type of the target data source and then, based on that type, selects the appropriate protocol adapter from a pool of pre-configured protocol adapters. In this specification, the protocol adapter corresponding to the target data source is referred to as the target protocol adapter. For example, if the target data source is a MySQL database, the intermediate system selects the first protocol adapter as the target protocol adapter; if the target data source is a CSV file system, the intermediate system selects the second protocol adapter; and if the target data source is a Kafka message queue, the intermediate system selects the third protocol adapter.

[0075] S330: The intermediate system controls the target protocol adapter to perform data source access operations.

[0076] The data source access operation can include S331-S333.

[0077] S331: Convert the access instruction into a request message that conforms to the communication protocol of the target data source.

[0078] This step is responsible for translating the access commands issued by the business system into a specific communication protocol format that the target data source can recognize. Since different types of data sources use their own unique communication rules and message structures, the target protocol adapter acts as a protocol translator in this stage, re-encapsulating and encoding standardized access commands into request messages that conform to the target data source's communication specifications, ensuring that the request messages can be correctly received and understood by the target data source.

[0079] S332: Send the request message to the target data source through the communication link with the target data source, and receive the response message returned by the target data source.

[0080] This step establishes network communication between the intermediate system and the target data source through an established physical or logical communication link. The target protocol adapter sends the converted request message to the target data source and simultaneously waits for and receives the response message returned by the data source. This process requires handling communication details such as network transmission, timeout control, and retry mechanisms to ensure that the request message is reliably delivered and the response message is completely received.

[0081] S333: Parse the response message according to the communication protocol of the target data source to obtain the execution result of the access instruction.

[0082] Upon receiving the response message from the target data source, the target protocol adapter needs to parse the original response according to the specifications of the corresponding communication protocol. This process includes parsing the message structure, decoding the data content, and extracting valid information, ultimately converting the original response returned by the target data source into a standardized execution result that the business system can recognize. This step completes the reverse conversion from the target data source's specific protocol format to a general data format, allowing the business system to use the returned data without needing to be concerned with the underlying protocol differences.

[0083] S340: The intermediate system sends the execution result of the access instruction to the business system.

[0084] In the above solution, the business system can access the data source by calling the general access interface provided by the intermediate system, without needing to worry about the communication protocols, connection methods, or authentication mechanisms of different data sources, thus reducing the development complexity of the business system. Furthermore, when the data source type changes, the intermediate system adjusts or extends the corresponding protocol adapter, while the business system does not need to modify its code. This reduces the development cost of the business system and improves its scalability and adaptability to different data sources, thereby enhancing the overall efficiency of data source access.

[0085] In some embodiments, the intermediate system may include a management subsystem and an execution subsystem. The management subsystem manages information related to the data source. The execution subsystem receives access instructions and, based on information provided by the management subsystem, invokes the appropriate protocol adapter to complete the actual data request forwarding, protocol conversion, and result return. In other words, in S310, the intermediate system can receive access instructions initiated by the business system for the target data source through the execution subsystem.

[0086] In some embodiments, prior to S310, the business system can obtain access guidance information through interaction with the intermediate system. This access guidance information is used to guide the business system in generating and sending access instructions to the execution subsystem. In this case, during S310, the business system can generate access instructions under the guidance of the access guidance information and send the access instructions to the execution subsystem of the intermediate system.

[0087] The following is combined with Figure 4 Explain the process by which the business system obtains access guidance information.

[0088] Figure 4 A flowchart illustrating another data source access method P400 provided according to an embodiment of this specification is shown. Figure 4 As shown, S410: The business system sends a pre-access request for the target data source to the management subsystem.

[0089] Correspondingly, the management subsystem receives pre-access requests from the business system for the target data source.

[0090] The pre-access request includes configuration information related to the target data source, used to establish a connection with the target data source, verify permissions, parse the data structure, and confirm the query path.

[0091] In some embodiments, the target data source includes at least one dataset. The pre-access request may include at least one of the following: metadata of the target data source, metadata of at least a portion of the datasets in the target data source. For example, a business system may maintain metadata of each data source and its datasets. When access to a specific dataset within a data source is required, the metadata of that data source and dataset can be included in the pre-access request.

[0092] In this specification, the metadata of a data source can refer to information used to describe the technical and administrative attributes of the data source. For example, the metadata of a data source may include at least one of the following: the name of the data source, the type of the data source, the access address, the authentication method, the network protocol, the security level, the organization to which it belongs, and a descriptive description of the data source. As an example, the metadata of a data source may be shown in Table 1.

[0093] Table 1

[0094] Meta-information of a dataset refers to information used to describe the content characteristics and usage of the dataset. For example, dataset meta-information may include at least one of the following: the dataset's name, field structure, data volume, update frequency, creation time, data source, and associated data model. As an example, dataset meta-information may be shown in Table 2.

[0095] Table 2

[0096] In some embodiments, the intermediate system can also provide metadata management services to the business system. That is, the intermediate system, as a unified metadata management center, can receive metadata from the data source / dataset in advance from the business system and help the business system manage the metadata of the data source / dataset.

[0097] like Figure 4 As shown, in some embodiments, before S410, the business system and the management subsystem may also execute S401-S403.

[0098] S401: The business system sends a registration request to the management subsystem.

[0099] Accordingly, the management subsystem receives registration requests from the business system. These registration requests may include at least one of the following: metadata of the target data source, or metadata of at least a portion of the dataset within the target data source.

[0100] S402: The management subsystem performs the identifier allocation operation.

[0101] After receiving a registration request, the management subsystem can assign an identifier to the target data source or at least a portion of the dataset within the target data source according to a preset naming rule.

[0102] In some embodiments, when the registration request includes metadata about the target data source, the identifier allocation operation may include: generating identifier information for the target data source based on the metadata of the target data source, and storing the correspondence between the metadata of the target data source and its identifier information. The identifier information of a data source is used to uniquely represent that data source.

[0103] In some embodiments, when the registration request includes metadata of at least a portion of the datasets in the target data source, the identifier allocation operation may include: generating identifier information for at least a portion of the datasets based on the metadata of the at least a portion of the datasets, and storing the correspondence between the metadata of the at least a portion of the datasets and their identifier information. The identifier information of a dataset is used to uniquely represent that dataset.

[0104] As an example, the target system can store the correspondences shown in Table 3 or Table 4.

[0105] Table 3

[0106] Table 4

[0107] S403: The management subsystem sends a registration response to the business system.

[0108] Wherein, when the registration request includes metadata about the target data source, the registration response includes the identification information of the target data source. Where the registration request includes metadata about at least a portion of the dataset in the target data source, the registration response includes the identification information of the at least a portion of the dataset.

[0109] Through the registration process described in S401-S403, the intermediate system can establish a correspondence between the metadata of the data source / dataset and its identification information, thereby abstracting complex and lengthy metadata into a concise and unique identification information. After obtaining the identification information of the data source / dataset, the business system does not need to carry the metadata of the data source / dataset in subsequent interactions with the intermediate system (management subsystem, execution subsystem), but only needs to carry the identification information. This approach simplifies the complexity of information interaction between the business system and the intermediate system and improves the efficiency of inter-system collaboration. Furthermore, the business system does not need to maintain the metadata of the data source / dataset itself, which reduces the maintenance cost of metadata for the business system.

[0110] In some embodiments where the intermediate system is responsible for assisting the business system in managing metadata, in step S410, the pre-access request sent by the business system to the management subsystem may include at least one of the following: the identification information of the target data source, or the identification information of at least a portion of the datasets in the target data source. That is, the business system does not need to carry the metadata of the data source / dataset in the pre-access request. After receiving the pre-access request, the management subsystem can obtain the metadata of the corresponding data source by querying the correspondence shown in Table 3 based on the identification information of the data source carried in the pre-access request; and can obtain the metadata of the corresponding dataset by querying the correspondence shown in Table 4 based on the identification information of the dataset carried in the pre-access request.

[0111] In some embodiments, access to a target data source by a business system may have specific personalized requirements. In this case, the pre-access request sent by the business system may also include its personalized access parameters to the target data source. Personalized access parameters refer to non-generic configuration parameters specified by the business system according to its own business scenario, performance requirements, or data usage habits, used to customize the connection behavior or data acquisition method with the target data source. In some embodiments, personalized access parameters may include at least one of the following: range parameters, format parameters, and encryption parameters.

[0112] The range parameter is used to characterize the location of the data to be read within the target data source. For example, the range parameter can specify conditions such as a time interval, ID range, or file path. This allows the intermediate system to selectively read the required data based on the range parameter, avoiding full data reads and improving read efficiency and performance.

[0113] Format parameters characterize the returned format of the data to be read. For example, format parameters can specify formats such as JSON, XML, CSV, Excel, or binary. Format parameters determine the data's organization and encoding. After reading data from the target data source, the intermediate system can convert the data according to the format parameters. This ensures that the data returned by the intermediate system meets the business system's data format requirements, allowing the business system to directly use the returned data without further format conversion, reducing subsequent conversion costs and improving data utilization efficiency.

[0114] Encryption parameters characterize the encryption method used when the data to be read is returned. For example, encryption parameters can specify HTTPS (HyperText Transfer Protocol Secure), AES (Advanced Encryption Standard), or RSA (Rivest–Shamir–Adleman) encryption. After reading data from the target data source, the intermediate system can encrypt the read data according to the encryption parameters and return the encrypted data to the business system, thereby improving data security during transmission. The business system can specify appropriate encryption parameters based on its data security requirements, requesting the intermediate system to use an appropriate encryption method to encrypt the data.

[0115] S420: The management subsystem sends a boot request to the execution subsystem.

[0116] After the management subsystem receives a pre-access request from the business system for the target data source, it can send a bootstrapping request to the execution subsystem. The bootstrapping request is used to request the execution subsystem to generate access bootstrapping information for the target data source.

[0117] In some embodiments, the bootstrapping request may include all or part of the parameters carried in the pre-access request, enabling the execution subsystem to understand the data source access requirements of the business system and generate accurate access bootstrapping information. For example, when the pre-access request includes metadata about the target data source, the management subsystem can include this metadata in the bootstrapping request and send it to the execution subsystem. When the pre-access request includes metadata about a portion of the datasets in the target data source, the management subsystem can include this metadata in the bootstrapping request and send it to the execution subsystem. When the pre-access request includes identification information about the target data source, the management subsystem can query the metadata about the target data source based on its identification information and then include this metadata in the bootstrapping request and send it to the execution subsystem. When the pre-access request includes identification information about a portion of the datasets in the target data source, the management subsystem can query the metadata about these datasets based on their identification information and then include this metadata in the bootstrapping request and send it to the execution subsystem.

[0118] S430: The execution subsystem generates the access boot information.

[0119] After receiving the bootstrap request, the execution subsystem generates access bootstrap information based on the request. This access bootstrap information guides the business system in generating and sending access commands to the execution subsystem. In other words, the access bootstrap information contains the information needed by the business system when sending access commands.

[0120] In some embodiments, the execution subsystem includes at least one execution device, each execution device being connected to at least a portion of multiple data sources. Assume the execution device connected to the target data source is the target execution device. In this case, the access boot information may include identification information of the target execution device. The identification information of the target execution device is used to uniquely indicate the target execution device. This identification information may be the target execution device's network address (such as an IP address), hostname, device serial number, or a unique ID assigned by the system, etc. By carrying the identification information of the target execution device in the access boot information, the business system can determine which execution device to send boot instructions to.

[0121] In some embodiments, the access guidance information may further include an access token corresponding to the target data source. An access token is a digital credential with an expiration date and scope of permissions, used for authentication and permission verification when accessing the target data source, ensuring that the requester has legitimate data access rights and preventing unauthorized access. By including the access token corresponding to the target data source in the access guidance information, the business system can know the token information required when sending the guidance instruction.

[0122] It should be noted that the access guidance information may include other information besides the identification information of the target execution device and the access token, and this manual does not limit this.

[0123] S440: The execution subsystem returns the access guidance information to the management subsystem.

[0124] S450: The management subsystem sends the access guidance information to the business system.

[0125] After passing through S410-S450, the business system obtains the access guidance information and sends it back to the client system. Thus, the business system can learn from the access guidance information how to generate and send the corresponding access commands when it needs to access the target data source.

[0126] By receiving pre-access requests and returning access guidance information to the business systems through the management subsystem, access control is centralized and proactive. The management subsystem can perform unified authentication and scheduling based on permission policies, data source status, and security rules, dynamically generating secure and compliant access guidance information. The business systems generate access instructions based on the access guidance information without needing to be aware of the details of the target data source, thus reducing coupling with the target data source.

[0127] S460: The business system sends an access instruction for the target data source to the execution subsystem based on the access guidance information.

[0128] The business system generates an access instruction for the target data source based on the access guidance information and sends the access instruction to the execution subsystem. Specifically, by parsing the access guidance information, the business system can obtain the identification information of the target execution device and the access token, etc. Then, the business system assembles the parsed information to generate a structured access instruction based on its common access interface with the intermediate system. According to the access instruction, the execution subsystem can access the specific target data source.

[0129] In some embodiments, when the access guidance information includes the identification information of the target execution device, the business system directly sends the access instruction to the target execution device based on the identification information of the target execution device.

[0130] In some embodiments, when the access boot information contains an access token, the access instruction sent by the business system to the execution subsystem in S460 includes the access token.

[0131] In some embodiments, the access instruction sent by the business system to the execution subsystem may further include information indicating the target data source to be accessed. For example, when the intermediate system provides metadata management services for data sources / datasets, the access instruction may also include at least one of the identification information of the target data source or the identification information of at least a portion of the dataset. As another example, when the intermediate system does not provide metadata management services for data sources / datasets, the access instruction may also include metadata of the target data source or at least one of the metadata of at least a portion of the dataset in the target data source.

[0132] S470: The execution subsystem determines the target protocol adapter from a plurality of pre-configured protocol adapters based on the type of the target data source.

[0133] The execution subsystem can determine the target data source to be accessed based on the access command, and then determine the protocol adapter corresponding to the type of the target data source from a number of pre-configured protocol adapters based on the type of the target data source, and use it as the target protocol adapter.

[0134] S480: The execution subsystem controls the target protocol adapter to perform data source access operations and obtain the execution results of the access instructions.

[0135] S490: The execution result of the access command sent by the execution subsystem to the business system.

[0136] The specific implementation of the data source access operation is similar to that described above, and will not be repeated here.

[0137] In S410, if the pre-access request received by the management subsystem includes personalized access parameters of the business system to the target data source, the management subsystem can pass the personalized access parameters to the execution subsystem so that the execution subsystem can control the target protocol adapter to perform data source access operations based on the personalized access parameters in S480; or, the management subsystem can store the personalized access parameters in the target storage space so that the execution subsystem can obtain the personalized access parameters from the target storage space in S480 and then control the target protocol adapter to perform data source access operations based on the personalized access parameters.

[0138] In some embodiments, when the access instruction includes an access token, the execution subsystem authenticates the business system based on the access token and invokes the target protocol adapter if authentication is successful. Specifically, the execution subsystem extracts the access token from the received access instruction and compares it with a list of valid tokens pre-stored in the execution subsystem. If the extracted access token matches a stored valid token, authentication is successful. In this case, the execution subsystem invokes the target protocol adapter. If the extracted access token does not match a stored valid token or the extracted access token is invalid, authentication fails. In this case, the execution subsystem will refuse to execute the access instruction.

[0139] By verifying the legitimacy of access tokens, the intermediate system can confirm the identity of business systems, prevent unauthorized systems from accessing sensitive data or performing critical operations, thereby reducing the risk of data leakage, tampering, or abuse, and improving the compliance, stability, and credibility of the intermediate system.

[0140] In some embodiments, the access instruction can also characterize the access type to the target data source. The access type can be either a read type or a write type.

[0141] When the access command represents a read type, in S480, the execution subsystem converts the access command into a request message conforming to the communication protocol of the target data source, sends the request message to the target data source through the communication link, and receives a response message returned by the target data source. Then, the execution subsystem parses the response message according to the communication protocol of the target data source to obtain the target data represented in a first format. Here, the first format is the data format adopted by the target data source. Further, the execution subsystem converts the target data from the first format to a second format, and obtains the execution result of the access command based on the converted data. Here, the second format is a general data format preset by the intermediate system.

[0142] By converting target data in the first format to the second format, data from different data sources is transformed into a common data format preset by the intermediate system, facilitating subsequent transmission and processing by the intermediate system. Furthermore, different business systems can obtain data with a common data format, making it easier for them to process and use the returned data.

[0143] In some embodiments, the business system has specific requirements for the data format of the returned data. For example, the business system may include format parameters in the pre-access request sent in S410. In this case, the intermediate system converts the target data from the first format to the second format, and then converts the target data from the second format to the data format required by the business system according to the aforementioned format parameters, thereby obtaining the execution result of the access instruction based on the converted data.

[0144] By converting the target data format from the second format to the data format required by the business system, the target data format is made to match the data format required by the business system. This simplifies the processing steps of the business system for the target data, improves the efficiency of the business system in using data, and reduces the processing cost of data.

[0145] In some embodiments, in conjunction with the foregoing description, the execution subsystem may receive in advance a pre-access request initiated by the business system for the target data source, the pre-access request including the data format requested by the business system. Thus, the execution subsystem can determine the data format requested by the business system based on the pre-access request.

[0146] In some embodiments, when the access type represented by the access instruction is write, the execution subsystem parses the target data from the access instruction, converts the data format of the target data into the data format required by the target data source, and generates the request message based on the converted data according to the communication protocol of the target data source. Then, the execution subsystem sends the request message to the target data source through the communication link and receives a response message returned by the target data source. The response message represents the writing result of the target data, such as successful or failed writing. The execution subsystem parses the response message according to the communication protocol of the target data source to obtain the execution result of the access instruction. The execution result can be successful or failed writing.

[0147] By converting the target data format to the format required by the target data source, business systems can submit data using a common or their own proprietary format without needing to understand the specific writing formats of each data source. This approach improves the data writing efficiency of business systems and reduces the cost of data format conversion.

[0148] In summary, this specification provides a data source access method, system, and storage medium. When a business system accesses a data source, it can initiate access to the target data source by calling a general access interface provided by an intermediate system. The intermediate system can determine the target protocol adapter from a set of pre-configured protocol adapters based on the type of the target data source and control the target protocol adapter to perform the data source access operation. This scheme handles communication between the intermediate system and the data source, eliminating the need for the business system to communicate directly with the data source; instead, it allows access through the general access interface. Developers of the business system do not need to write or modify the access logic code for each data source, improving access efficiency and reducing code development and maintenance costs.

[0149] This specification, in another aspect, provides a non-transitory storage medium storing at least one set of executable instructions for performing a data source access method. When the executable instructions are executed by a processor, they instruct the processor to implement the steps of the data source access method P300 described in this specification. In some possible embodiments, various aspects of this specification can also be implemented as a program product comprising program code. When the program product is run on a computing system 200, the program code causes the computing system 200 to perform the steps of the data source access method P300 described in this specification. The program product for implementing the above method may employ a portable compact disk read-only memory (CD-ROM) containing program code and may run on the computing system 200. However, the program product of this specification is not limited thereto. In this specification, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system. The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may 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 readable storage media include: electrical connections having one or more wires, portable disks, hard disks, 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 devices, magnetic storage devices, or any suitable combination thereof. The computer-readable storage medium may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable storage medium may also be any readable medium other than a readable storage medium that can send, propagate, or transmit programs for use by or in connection with an instruction execution system, apparatus, or device. Program code contained on a readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof. Program code for performing the operations described herein can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on computing system 200, partially on computing system 200, as a standalone software package, partially on computing system 200 and partially on a remote computing device, or entirely on a remote computing device.

[0150] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0151] In summary, after reading this detailed disclosure, those skilled in the art will understand that the foregoing detailed disclosure is presented by way of example only and is not restrictive. Although not explicitly stated herein, those skilled in the art will understand that this specification requires various reasonable changes, improvements, and modifications to the embodiments. These changes, improvements, and modifications are intended to be made by this specification and are within the spirit and scope of the exemplary embodiments described herein.

[0152] Furthermore, certain terms in this specification have been used to describe embodiments of this specification. For example, "an embodiment," "an embodiment," and / or "some embodiments" mean that a particular feature, structure, or characteristic described in connection with that embodiment may be included in at least one embodiment of this specification. Therefore, it is to be emphasized and understood that two or more references to "an embodiment" or "an embodiment" or "alternative embodiment" in various parts of this specification do not necessarily refer to the same embodiment. Moreover, specific features, structures, or characteristics may be suitably combined in one or more embodiments of this specification.

[0153] It should be understood that in the foregoing description of the embodiments in this specification, various features are combined in a single embodiment, drawing, or description for the purpose of simplifying the description and to aid in understanding a feature. However, this does not mean that the combination of these features is necessary, and those skilled in the art, upon reading this specification, may readily identify some of the devices as separate embodiments. That is, the embodiments in this specification can also be understood as an integration of multiple secondary embodiments. And the content of each secondary embodiment is valid even if it contains fewer than all the features of a single foregoing disclosed embodiment.

[0154] Every patent, patent application, publication of a patent application, and other material, such as articles, books, specifications, publications, documents, and literature (excluding any related historical examination documents), cited in this disclosure is incorporated herein for all purposes, including, for example, in the specification and claims of this disclosure. However, in the event of any inconsistency or conflict between the descriptions, definitions, and / or terms used in the foregoing and those used in this disclosure, the descriptions, definitions, and / or terms used in this disclosure shall prevail.

[0155] Other modified embodiments are also within the scope of this specification. Therefore, the embodiments disclosed in this specification are merely examples and not limitations. Those skilled in the art can implement the applications in this specification using alternative configurations based on the embodiments in this specification. Therefore, the embodiments in this specification are not limited to the embodiments precisely described in the applications.

Claims

1. A data source access method, characterized by, The method is applied to an intermediate system connected with a plurality of data sources, and comprises: receiving an access instruction initiated by a business system for a target data source, the access instruction being initiated by the business system by calling a general access interface provided by the intermediate system; determining a target protocol adapter from a plurality of protocol adapters pre-configured based on a type of the target data source, wherein different protocol adapters are configured to process communication protocols of different types of data sources; controlling the target protocol adapter to perform a data source access operation as follows: converting the access instruction into a request message conforming to a communication protocol of the target data source, sending the request message to the target data source through a communication link between the target data source and the intermediate system, and receiving a response message returned by the target data source, and parsing the response message according to the communication protocol of the target data source to obtain an execution result of the access instruction; and sending the execution result of the access instruction to the business system.

2. The data source access method of claim 1, wherein, The intermediate system comprises a management subsystem and an execution subsystem; receiving the access instruction initiated by the business system for the target data source comprises receiving the access instruction initiated by the business system for the target data source through the execution subsystem; before receiving the access instruction through the execution subsystem, the method further comprises receiving a pre-access request initiated by the business system for the target data source through the management subsystem, and sending access guide information to the business system, wherein the access guide information is used to guide the business system to generate and send the access instruction to the execution subsystem.

3. The data source access method of claim 2, wherein, after receiving the pre-access request initiated by the business system for the target data source through the management subsystem, the method further comprises: sending a guide request to the execution subsystem through the management subsystem; and generating the access guide information through the execution subsystem, and returning the access guide information to the management subsystem.

4. The data source access method of claim 3, wherein, The execution subsystem comprises at least one execution device, each execution device being connected with at least part of the plurality of data sources, the access guide information at least comprising identification information of a target execution device, the target execution device being an execution device of the execution subsystem connected with the target data source; receiving the access instruction initiated by the business system for the target data source through the execution subsystem comprises receiving the access instruction initiated by the business system for the target data source through the target execution device.

5. The data source access method of claim 3, wherein, The access guide information comprises an access token; The access instruction comprises the access token; calling the target protocol adapter comprises authenticating the business system based on the access token, and calling the target protocol adapter if the authentication is passed.

6. The data source access method of claim 2, wherein, The target data source comprises at least one data set; The pre-access request comprises at least one of the following: identification information of the target data source, or identification information of at least part of data sets in the target data source, the method further comprises: receiving, by the management subsystem, a registration request from the business system, the registration request comprising at least one of meta-information of the target data source or meta-information of at least part of data sets in the target data source; performing, by the management subsystem, an identity allocation operation, the identity allocation operation comprising at least one of: generating identity information of the target data source based on the meta-information of the target data source, and storing a correspondence between the meta-information of the target data source and the identity information thereof, or generating identity information of the at least part of data sets based on the meta-information of the at least part of data sets, and storing a correspondence between the meta-information of the at least part of data sets and the identity information thereof; and sending, by the management subsystem, a registration response to the business system, the registration response comprising at least one of the identity information of the target data source or the identity information of the at least part of data sets.

7. The data source access method of claim 2, wherein, the pre-access request comprises a personalized access parameter of the business system to the target data source; controlling the target protocol adapter to perform a data source access operation comprises controlling the target protocol adapter to perform a data source access operation based on the personalized access parameter.

8. The data source access method of claim 7, wherein, the personalized access parameter comprises at least one of: a range parameter for representing a position of data to be read in the target data source; a format parameter for representing a return format of data to be read; an encryption parameter for representing an encryption manner of data to be read when returned.

9. An intermediate system, characterized by comprise: at least one storage medium storing at least one instruction set; and at least one processor communicatively connected with the at least one storage medium, wherein the at least one processor reads the at least one instruction set when running, and performs the data source access method according to the instruction of the at least one instruction set. the computer readable non-transitory storage medium stores at least one instruction set, and the at least one instruction set is executed by at least one processor to implement the data source access method according to any one of claims 1-8.

10. A computer-readable non-transitory storage medium, characterized in that, ​

Images