Data processing method, system and device, storage medium and program product

By pre-configuring resource location identifiers and docking rules, the central platform decouples docking rules from business logic rules, solves the problem of low flexibility and efficiency of functional service interfaces in multi-system docking, and improves the flexibility and efficiency of data processing.

CN120897003APending Publication Date: 2025-11-04BOE TECHNOLOGY GROUP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511218481.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-08-28
Publication Date
2025-11-04

AI Technical Summary

Technical Problem

In existing technologies, the functional service interfaces in a project system need to be encapsulated and parsed multiple times when connecting to multiple business systems, resulting in poor flexibility and low data processing efficiency.

Method used

By pre-configuring different resource location identifiers and corresponding docking rules, the central platform receives data access requests and performs security verification and parameter parsing based on the pre-configured docking rules, avoiding multiple encapsulation of target interfaces and achieving decoupling between docking rules and business logic rules.

Benefits of technology

It improves the flexibility and efficiency of data processing, reduces repetitive encapsulation steps in the docking process, and enhances the overall performance of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120897003A_ABST
    Figure CN120897003A_ABST
Patent Text Reader

Abstract

The invention discloses a data processing method, system and device, a storage medium and a program product. The method comprises the steps that a central platform receives a data access request from a first service node through a target interface; obtaining a target docking rule corresponding to the target resource positioning identifier from docking rule configuration information based on the target resource positioning identifier; performing security verification on the request data of the first service node based on the target docking rule, analyzing the request data of the first service node based on a parameter analysis rule after a security verification result is successful, and obtaining response data based on an analysis result of the request data of the first service node; and sending the response data to the first service node through the target interface. According to the embodiment of the invention, the data processing efficiency is improved by utilizing the pre-configured docking rule, and meanwhile, the problem of relatively poor data processing flexibility caused by coupling of the docking rule and the business logic rule in the prior art is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a data processing method, system, device, storage medium, and program product. Background Technology

[0002] With the extensive research and development of Java programs, existing technologies can encapsulate the existing functional service interfaces in the project system based on the parsing rules of various business systems, so as to realize the interface between the functional service interfaces and different business systems.

[0003] However, when existing functional service interfaces in a project system connect to multiple business systems, the functional service interfaces need to be encapsulated multiple times according to the parsing rules of different business systems. This means that every time a functional service interface connects to a new business system, it needs to be encapsulated with the parsing rules corresponding to that business system, resulting in poor flexibility for the functional service interface to connect to different business systems. Secondly, the multiple encapsulation of parsing rules also leads to low data processing efficiency. Summary of the Invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a data processing method, system, device, storage medium and program product. The method pre-configures different resource location identifiers and corresponding docking rules. When a data access request is received from different business nodes, the response data of the data access request is obtained based on the pre-configured docking rules corresponding to the target resource location identifier, so as to improve data processing efficiency and flexibility while avoiding multiple encapsulation of target interfaces.

[0005] In a first aspect, the present invention provides a data processing method applied to a data processing system, the data processing system including a central platform and multiple business nodes that interact with the central platform through a target interface configured on the central platform. The method includes: The central platform receives data access requests from the first business node through the target interface. The data access request includes the target resource location identifier and the request data from the first business node. Based on the target resource location identifier, the target docking rule corresponding to the target resource location identifier is obtained from the docking rule configuration information; the docking rule configuration information includes multiple pre-configured different resource location identifiers and docking rules corresponding to each resource location identifier, and the docking rules include security verification rules and parameter parsing rules; The request data of the first business node is security verified based on the target docking rules. After the security verification result is passed, the request data of the first business node is parsed based on the parameter parsing rules, and the response data is obtained based on the parsing result of the request data of the first business node. Send response data to the first business node through the target interface.

[0006] Secondly, the present invention provides a data processing system, which includes a central platform and multiple business nodes that interact with the central platform through target interfaces configured on the central platform. The target interface is used to receive data access requests from the first business node. The data access request includes the target resource location identifier and the request data from the first business node. The central platform is used to obtain the target docking rule corresponding to the target resource location identifier from the docking rule configuration information based on the target resource location identifier. The docking rule configuration information includes multiple pre-configured different resource location identifiers and docking rules corresponding to each resource location identifier. The docking rules include security verification rules and parameter parsing rules. The central platform is also used to perform security verification on the request data of the first business node based on the target docking rules, and after the security verification result is passed, to parse the request data of the first business node based on the parameter parsing rules, and to obtain the response data based on the parsing result of the request data of the first business node. The target interface is also used to send response data to the first business node.

[0007] 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 when the processor executes the program, it implements the method as described in the first aspect.

[0008] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, characterized in that the program, when executed by a processor, implements the method described in the first aspect.

[0009] Fifthly, a computer program product is provided, which includes instructions that, when executed, perform the method described in any one of the first aspects.

[0010] The data processing method, system, device, storage medium, and program product provided in this application, by pre-configuring different resource location identifiers and corresponding docking rules, when receiving data access requests sent by different business nodes, obtains the response data of the data access request based on the pre-configured docking rules corresponding to the target resource location identifier, so as to decouple the docking rules from the business logic rules without repeatedly encapsulating the target interface, thereby improving the efficiency and flexibility of data processing. Attached Figure Description

[0011] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a schematic diagram of the implementation environment architecture to which the embodiments of this application apply; Figure 2 A flowchart illustrating a data processing method provided in an embodiment of this application; Figure 3 A flowchart illustrating another data processing method provided in an embodiment of this application; Figure 4 A schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0012] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0013] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. The present application will now be described in detail with reference to the accompanying drawings and embodiments. Furthermore, the term "and / or" in this document 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, or B existing alone. The terms "first" and "second," etc., in the specification and claims of the embodiments of this application are used to distinguish different objects, not to describe a specific order of objects.

[0014] The following explains the terms used in this application: (1) Spring Framework: It is an open-source Java platform that provides a programming and configuration model for building enterprise applications. The automatic dependency management and extensibility of the Spring Framework can quickly develop Java language applications. (2) Spring MVC framework: A module in the Spring framework used to build web applications, specifically the Model-View-Controller (MVC) design pattern; (3) Hypertext Transfer Protocol (HTTP): is a protocol used to transfer data between a client and a server. Specifically, a client can request a specific resource from a server and receive a response from the server. The specific resource can be a webpage, an image, or a video. The client can be a web browser, and the server can be a web server. (4) Uniform Resource Locator (URL): is an address used to identify resources on the Internet. Nodes in the network can encapsulate the URL in a request to access the resource indicated by the URL, such as web pages, pictures, videos, files, etc. For example, nodes in the network can initiate an HTTP request based on the HTTP protocol. The HTTP request includes the URL and is used to access the resource indicated by the URL. In this embodiment of the application, the Uniform Resource Locator corresponds to the resource location identifier.

[0015] In existing technologies, when existing functional service interfaces in a project system connect to multiple business systems, the functional service interfaces need to be encapsulated multiple times according to the parsing rules of different business systems. This results in the functional service interface needing to be encapsulated with the parsing rules corresponding to the new business system every time it connects to a new business system, thus leading to poor flexibility in connecting the functional service interface to different business systems. Secondly, the multiple encapsulation of parsing rules also leads to low data processing efficiency.

[0016] In response, this application proposes a data processing method. This method pre-configures different resource location identifiers and corresponding docking rules. When a data access request is received from a different business node, the response data of the data access request is obtained based on the pre-configured docking rules corresponding to the target resource location identifier. This improves data processing efficiency and flexibility by avoiding multiple encapsulations of the target interface.

[0017] Figure 1 This is a schematic diagram of the implementation environment architecture to which the embodiments of this application apply. For example... Figure 1 As shown, the implementation environment architecture can be a data processing system 10. The basic architecture of the data processing system 10 is the Spring MVC framework, which specifically includes a central platform 101 and multiple business nodes 102 that interact with the central platform 101 through the target interface 1011 configured on the central platform 101.

[0018] For example, the central platform 101 can be a data processing platform of a preset project system; the target interface 1011 can be a functional service interface of the central platform 101; and the multiple business nodes 102 can be multiple other business systems that interact with the central platform 101.

[0019] For example, the central platform 101 is pre-configured with docking rule configuration information, which includes multiple different resource location identifiers and docking rules corresponding to each resource location identifier; correspondingly, each business node 102 corresponds to a resource location identifier.

[0020] In specific implementation, when a business node 1021 interacts with the central platform 101, the central platform 101 receives a data access request from the business node 1021 through the target interface 1011. First, it matches the target resource location identifier in the data access request with the pre-configured docking rule information of the central platform 101 to obtain the target docking rule corresponding to the target resource location identifier. Then, based on the target docking rule, it first performs security verification on the request data in the data access request of the business node 1021. If the security verification of the request data passes, it obtains the response data of the data access request according to the target docking rule. Finally, it returns the response data of the data access request through the target interface 1011.

[0021] It should be noted that although the operation of the method of the present invention is described in a specific order in the accompanying drawings, this does not require or imply that the operations must be performed in that specific order, or that all the operations shown must be performed in order to achieve the desired result.

[0022] This application provides a data processing method, which can be applied to, for example... Figure 1 The data processing system 10 shown is... Figure 2 This is a flowchart illustrating a data processing method provided in an embodiment of this application, as shown below. Figure 2 As shown, the method specifically includes the following steps: In step S201, the central platform 101 receives a data access request from the first business node through the target interface 1011. The data access request includes the target resource location identifier and the request data from the first business node.

[0023] For example, a data access request can be a Hypertext Transfer Protocol request (corresponding to the HTTP communication protocol's request message), which consists of a request line, request headers, a blank line, and request data.

[0024] Specifically, when the central platform 101 receives an HTTP request, it can determine the target URL and query parameters based on the parsing result of the HTTP request line; and determine the location of the request data according to the specific type of the HTTP request, so as to obtain the request data by parsing based on the corresponding location.

[0025] For example, when the HTTP request type is GET, the request data can be obtained by querying the URL parameters; when the HTTP request type is POST, the request data can be obtained by querying the URL parameters or the request body. The request body is located after the HTTP request header, separated by a blank line.

[0026] Step S202: Obtain the target docking rule corresponding to the target resource location identifier from the docking rule configuration information based on the target resource location identifier; the docking rule configuration information includes multiple pre-configured different resource location identifiers and docking rules corresponding to each resource location identifier, and the docking rules include security verification rules and parameter parsing rules.

[0027] In this embodiment, multiple resource location identifiers and corresponding docking rules can be pre-configured in the central platform 101 according to current business needs to form docking rule configuration information. Based on this docking rule configuration information, docking with multiple business nodes can be achieved through one-time development of the target interface 1011 in the central platform 101.

[0028] For example, the configuration rule for the resource location identifier is an absolute URL path, without adding parameters or domain name path information. That is, the file location can be determined based on the resource location identifier without relying on other information, such as the physical path starting from the drive letter or the path with the URL.

[0029] In one possible implementation, after obtaining the target resource location identifier in the data access request of the first business node based on step S201, the resource location identifier that matches the target resource location identifier is obtained by matching the target resource location identifier with multiple resource location identifiers in the docking rule configuration information, and the docking rule corresponding to the resource location identifier is determined as the target docking rule corresponding to the target resource location identifier.

[0030] Step S203: Perform security verification on the request data of the first business node based on the target docking rules, and after the security verification result is passed, parse the request data of the first business node based on the parameter parsing rules, and obtain the response data based on the parsing result of the request data of the first business node.

[0031] In one possible implementation, different security verification rules are used to perform security verification on the request data of the business nodes based on different configuration methods of security verification rules in the rule configuration information.

[0032] For example, the security verification rules in the connection rules corresponding to each resource location identifier in the connection rule configuration information are different. Based on this, for each data access request, the request data of the data access request is security verified based on the security verification rule corresponding to the resource location identifier in the data access request.

[0033] Optionally, the security verification rules in the connection rules corresponding to multiple resource location identifiers in the connection rule configuration information are the same. Based on this, for each data access request, the request data of the data access request is security verified based on the same security verification rule (that is, the data processing system 10 performs system-level security verification).

[0034] In one possible implementation, the request data of the first business node is encrypted data generated based on the first communication key. Based on this, the security verification is determined according to the decryption result of the request data.

[0035] For example, if the decryption result of the requested data is successfully obtained, the security verification of the requested data is considered to have passed; otherwise, the security verification of the requested data is considered to have failed. It should be noted that when the security verification of the requested data fails, the central platform 101 sends the security verification failure result to the business node corresponding to the requested data.

[0036] For example, when the security verification of the requested data passes, the requested data is parsed to determine the response data for the data access request based on the parsing result of the requested data.

[0037] In one possible implementation, after the security verification of the request data passes, the processing method corresponding to the parsing result can be obtained from the preset mapping relationship based on the parsing result of the request data, thereby obtaining the response data of the request data.

[0038] For example, the preset mapping relationship can be represented as a key-value mapping table, which can be configured to correspond to different parsing results and different processing methods.

[0039] Step S204: Send response data to the first service node through the target interface 1011.

[0040] For example, the central platform 101 can send the response data determined in step S203 to the first service node through its own target interface 1011 based on the transmission control connection established with the first service node.

[0041] The data processing method provided in this application embodiment, by pre-configuring different resource location identifiers and corresponding docking rules, when receiving data access requests sent by different business nodes 102, obtains the response data of the data access request based on the pre-configured docking rules corresponding to the target resource location identifier, so as to decouple the docking rules and business logic rules without encapsulating the target interface multiple times, thereby improving the efficiency and flexibility of data processing.

[0042] In another embodiment of this application, a specific verification method for the request data of the first service node is also provided. For example, the aforementioned "performing security verification on the request data of the first service node based on the target interface rules, and parsing the request data of the first service node based on parameter parsing rules after the security verification result is passed" specifically includes: determining a second communication key based on the target interface rules, the second communication key being an associated key of the first communication key; and parsing the request data of the first service node based on the parameter parsing rules when the request data is successfully decrypted using the second communication key.

[0043] In one possible implementation, the second communication key serves as the associated key of the first communication key. The association method between the first and second communication keys can be determined based on the encryption algorithm used by the business node 102 when encrypting the request data, and the second communication key can be determined based on this association method.

[0044] For example, when the business node 102 uses a symmetric encryption algorithm to encrypt the request data, the first communication key and the second communication key are shared keys. That is, the first communication key used by the business node 102 to encrypt the request data and the second communication key used by the platform center 101 to decrypt the request data are the same key.

[0045] For example, when the business node 102 encrypts the request data using an asymmetric encryption algorithm, the first communication key and the second communication key are a public-private key pair. For instance, the first communication key and the second communication key are the public key and private key of the central platform 101, respectively. Based on this, the business node 102 encrypts and generates the request data using the public key of the central platform 101. Then, when the central platform 101 receives the request data sent by the business node 102, it decrypts the request data using its own private key.

[0046] For example, when the request data is successfully decrypted using the second communication key, it is determined that the request data has passed the security verification of the central platform 101.

[0047] It should be noted that after successfully decrypting the request data, the parsed plaintext parameters can be stored in the request context (e.g., attribute) to provide parameter information for the response data that is subsequently obtained from the request data.

[0048] In another embodiment of this application, additional functions of the data processing system 10 are also provided. For example, see reference... Figure 1The data processing system 10 also includes a monitoring module 103. Based on this, the method further includes: for each first business node, obtaining the case where the security verification result is passed during the security verification process of the request data for the first business node, and sending the request data corresponding to the case where the security verification result is passed to the monitoring module 103.

[0049] In this embodiment of the application, a monitoring module 103 is set in the data processing system 10 to monitor the data access status of each business node, thereby realizing functions such as data statistics, security reminders, and real-time data updates based on the data access status of each business node.

[0050] In one possible implementation, after the request data of the business node whose verification result is passed is sent to the monitoring module 103, the monitoring module 103 can filter the request data corresponding to the target resource location identifier corresponding to the current business requirement from the received request data according to the current business requirements, thereby realizing the monitoring function of preset business parameters.

[0051] For example, the monitoring module 103 can realize asynchronous identification between terminal devices and business statistics of preset services based on the request data corresponding to the target resource location identifier corresponding to the current business needs.

[0052] In another embodiment of this application, a specific method for updating the target docking rules is also provided. For example, the method further includes: obtaining the proxy status of the second business node indicated by the target resource location identifier; when the proxy status of the second business node is "proxied," obtaining the proxy resource location identifier of the proxy second business node; determining the configuration type of the proxy resource location identifier; and updating the target docking rules corresponding to the target resource location identifier based on the configuration type.

[0053] In this embodiment of the application, when the target resource location identifier remains unchanged (i.e., the front-end path address for the interaction between business node 102 and central platform 101 has not changed), the target docking rules are updated by determining the proxy resource location identifier, thereby jumping to other path addresses to achieve interaction with other business nodes.

[0054] In one possible implementation, the central platform 101 configures the proxy resource location identifier within the business node indicated by a target resource location identifier, thereby changing the proxy state of the business node to the proxied state.

[0055] Based on this, for example, the proxy status of a business node can be determined according to the configuration of the proxy resource location identifier within the business node.

[0056] Specifically, when a pre-configured proxy resource location identifier exists within a business node, the proxy status of the business node is determined to be proxied; otherwise, when the proxy resource location identifier field within a business node is empty, the business node is determined not to be proxied.

[0057] It should be noted that when the business node indicated by the target resource location identifier is not proxied and the current business node cannot provide services, the data access request of the first business node will be marked as failed, and an HTTP response will be returned to the first business node to indicate that the signature verification failed.

[0058] In one possible implementation, when the proxy status of the business node indicated by the target resource location identifier is "proxied", the target docking rule corresponding to the target resource location identifier is updated according to the configuration type of the proxy resource location identifier.

[0059] For example, when the configuration type of the proxy resource location identifier is complete configuration information (i.e., full URL path configuration), a communication connection is established with the business node corresponding to the proxy resource location identifier. Based on the communication connection, the docking rules corresponding to the proxy resource location identifier are obtained, and the target docking rules are updated to the docking rules corresponding to the proxy resource location identifier.

[0060] For example, the business node indicated by the target resource location identifier can send a GET request or a POST request to the business node corresponding to the proxy resource location identifier in order to establish a communication connection between the business node sending the data access request and the business node corresponding to the proxy resource location identifier.

[0061] Optionally, when the configuration type of the proxy resource location identifier is partial configuration information (i.e., internal path configuration), the business node corresponding to the target resource location identifier forwards the request data to the business node corresponding to the proxy resource location identifier, receives the docking rules formed by the business node corresponding to the proxy resource location identifier based on the request data, and updates the target docking rules to the docking rules sent by the business node corresponding to the proxy resource location identifier.

[0062] For example, the business node corresponding to the target resource location identifier can redirect the request path to the business node corresponding to the proxy resource location identifier based on classes such as jakarta.servlet.RequestDispatcher.

[0063] In another embodiment of this application, another data processing method is also provided, which can also be applied to the above-described data processing system 10. For example, Figure 3 This is a flowchart illustrating another data processing method provided in an embodiment of this application, such as... Figure 3 As shown, the method specifically includes the following steps: Step S301: The first business node sends a data access request to the central platform 101.

[0064] For example, a data access request includes a target resource location identifier and request data from a first business node.

[0065] In step S3021, the central platform 101 receives a data access request through the target interface 1011 and obtains the matching status of the target resource location identifier and the docking rule configuration information in the data access request.

[0066] For example, if the target resource location identifier exists in the docking rule configuration information (i.e., the data access request and the docking rule configuration information are successfully matched), then the target docking rule corresponding to the target resource location identifier is obtained and step S3031 is executed; otherwise, step S3032 is executed.

[0067] It should be noted that the function of the central platform 101 is to intercept and match. The central platform 101 can be an interceptor based on the Spring framework. Correspondingly, the data processing system 10 is a network routing and forwarding system based on the Spring interceptor.

[0068] Step S3031: Based on the setting of the target docking rules corresponding to the target resource location identifier, perform security verification on the request data in the data access request.

[0069] For example, if the connection rule configuration information sets a target connection rule, the request data is security verified based on the target connection rule; otherwise, step S304 is executed.

[0070] Step S3032: Process the data access request based on the target resource location identifier in the data access request.

[0071] Step S304: Obtain and execute the monitoring rules preset by the monitoring module 103 based on the current business requirements.

[0072] For example, if the monitoring rule is used to characterize the response event of the target resource location identifier as a monitoring event, then the monitoring module 103 receives all parameters corresponding to the target resource location identifier.

[0073] Step S305: Obtain the proxy status of the second service node indicated by the target resource location identifier.

[0074] For example, when the proxy status of the second business node is "proxied", step S302 is executed to obtain the matching status of the proxy resource location identifier and the docking rule configuration information; otherwise, step S3032 is executed.

[0075] In this embodiment, the interception and matching function of the central platform 101 and the pre-configuration of the docking rule configuration information achieve the decoupling of the docking rules corresponding to the target resource location identifier and the business logic rules. This allows for flexible configuration of the docking rules for the existing target interface 1011 according to preset requirements, and enables monitoring settings for the existing target interface 1011. Secondly, during system integration, historically retained interfaces can be flexibly configured, allowing for the calling of other system interfaces without changing the front-end address, thus transferring interface functions to other systems. Based on this, the data processing system 10 can implement routing proxy settings, security verification and parameter parsing, and monitoring notifications for specified HTTP requests.

[0076] The following is for reference. Figure 4 , Figure 4 A schematic diagram of a computer device suitable for implementing embodiments of this application is shown, such as... Figure 4 As shown, the computer device 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 402 or programs loaded from storage section 408 into random access memory (RAM) 403. The RAM 403 also stores various programs and data required for the system's operating instructions. The CPU 401, ROM 402, and RAM 403 are interconnected via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

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

[0078] Specifically, according to embodiments of this application, the flowchart above refers to... Figure 2 , 3Any of the described processes can be implemented as a computer software program. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program contains program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by central processing unit (CPU) 401, it performs the functions defined in the system of this application.

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

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

[0081] The units or modules described in the embodiments of this application can be implemented in software or hardware. The described units or modules can also be housed in a processor; for example, a processor may be described as including a semantic extraction unit, a weight allocation unit, and a determination unit. The names of these units or modules do not necessarily constitute a limitation on the unit or module itself.

[0082] On the other hand, this application also provides a computer-readable storage medium, which may be included in the computer device described in the above embodiments, or may exist independently and not assembled into the computer device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the methods described in this application. For example, it may execute... Figure 2 , 3 Each step of any of the methods shown.

[0083] This application provides a computer program product including instructions that, when executed, cause the method described in this application to be performed. For example, it can execute... Figure 2 , 3 Each step of any of the methods shown.

[0084] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the foregoing disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A data processing method, characterized in that, The method is applied to a data processing system, which includes a central platform and multiple business nodes that interact with the central platform through a target interface configured on the central platform. The central platform receives a data access request from the first business node through the target interface. The data access request includes a target resource location identifier and the request data from the first business node. Based on the target resource location identifier, the target docking rule corresponding to the target resource location identifier is obtained from the docking rule configuration information; the docking rule configuration information includes multiple pre-configured different resource location identifiers and docking rules corresponding to each resource location identifier, and the docking rule includes security verification rules and parameter parsing rules; The request data of the first business node is security verified based on the target docking rules. After the security verification result is passed, the request data of the first business node is parsed based on the parameter parsing rules, and the response data is obtained based on the parsing result of the request data of the first business node. The response data is sent to the first service node through the target interface.

2. The data processing method according to claim 1, characterized in that, The request data of the first service node is encrypted data generated based on the first communication key. The step of performing security verification on the request data of the first service node based on the target connection rule, and parsing the request data of the first service node based on the parameter parsing rule after the security verification result is passed, includes: Based on the target docking rules, a second communication key is determined, which is an associated key of the first communication key; When the request data is successfully decrypted using the second communication key, the request data of the first service node is parsed based on the parameter parsing rules.

3. The data processing method according to claim 1, characterized in that, The process of obtaining response data based on the parsing result of the request data from the first business node includes: Based on the parsing result of the request data, the processing method corresponding to the parsing result is obtained from the preset mapping relationship, and the processing method is executed to obtain the response data; wherein, the preset mapping relationship includes the correspondence between different parsing results and different processing methods.

4. The data processing method according to claim 1, characterized in that, The data processing system further includes a monitoring module, and the method further includes: For each of the first business nodes, the system obtains the case where the security verification result of the security verification process for the request data of the first business node is passed, and sends the request data corresponding to the case where the security verification result is passed to the monitoring module.

5. The data processing method according to claim 1, characterized in that, The method further includes: Obtain the proxy status of the second service node indicated by the target resource location identifier. When the proxy status of the second service node is being proxied, obtain the proxy resource location identifier that proxied the second service node. Determine the configuration type of the proxy resource location identifier, and update the target docking rule corresponding to the target resource location identifier based on the configuration type.

6. The data processing method according to claim 5, characterized in that, The step of updating the target docking rule corresponding to the target resource location identifier based on the configuration type includes: When the configuration type is complete configuration information, a communication connection is established with the business node corresponding to the proxy resource location identifier. Based on the communication connection, the docking rule corresponding to the proxy resource location identifier is obtained, and the target docking rule is updated to the docking rule corresponding to the proxy resource location identifier; or When the configuration type is partial configuration information, the business node corresponding to the target resource location identifier forwards the request data to the business node corresponding to the proxy resource location identifier, receives the docking rules formed by the business node corresponding to the proxy resource location identifier based on the request data, and updates the target docking rules to the docking rules sent by the business node corresponding to the proxy resource location identifier.

7. A data processing system, characterized in that, The data processing system includes a central platform and multiple business nodes that interact with the central platform through target interfaces configured on the central platform. The target interface is used to receive a data access request from the first service node, the data access request including a target resource location identifier and request data from the first service node; The central platform is used to obtain the target docking rule corresponding to the target resource location identifier from the docking rule configuration information based on the target resource location identifier; the docking rule configuration information includes multiple pre-configured different resource location identifiers and docking rules corresponding to each resource location identifier, and the docking rule includes security verification rules and parameter parsing rules; The central platform is also used to perform security verification on the request data of the first business node based on the target docking rules, and after the security verification result is passed, parse the request data of the first business node based on the parameter parsing rules, and obtain response data based on the parsing result of the request data of the first business node. The target interface is also used to send the response data to the first service node.

8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes instructions that, when executed, cause the method as described in any one of claims 1 to 6 to be performed.