Data processing method and apparatus

Abstract

Embodiments of the present specification provide a data processing method and device, wherein the data processing method comprises: receiving a data processing request submitted by an initial service end through an interface configuration module, and parsing the data processing request to obtain service data; determining a field processing rule of service main data corresponding to the service data in a field mapping table, and converting the service main data based on the field processing rule to obtain target service data; determining a target service end identifier associated with the service data based on the interface configuration module, and sending the target service data to a target service end associated with the initial service end based on the target service end identifier, the initial service end and the target service end being heterogeneous service ends.

Description

Technical Field

[0001] The embodiments in this specification relate to the field of data processing technology, and in particular to data processing methods and apparatus. Background Technology

[0002] In the construction and operation of financial systems, various account-related data typically need to be kept consistent across multiple heterogeneous business systems. In current practice, this business data is often maintained independently by multiple business systems, lacking a unified input and distribution mechanism. This results in the same business data needing to be repeatedly entered into multiple systems, leading to a heavy operational burden and making it difficult to establish a unified data standard. Different business systems define the same business concept in significantly different ways, and cross-system data processing usually relies on manual comparison and processing, which is inefficient. Therefore, a more effective data processing method is urgently needed to solve these problems. Summary of the Invention

[0003] In view of the above, embodiments of this specification provide a data processing method. One or more embodiments of this specification also relate to a data processing apparatus, a computing device, a computer-readable storage medium, and a computer program product, to address the technical deficiencies existing in the prior art.

[0004] According to a first aspect of the embodiments of this specification, applied to a business server, a data processing method is provided, including: Receive the data processing request submitted by the initial business terminal through the interface configuration module, and parse the data processing request to obtain business data; Based on the business master data corresponding to the business data, the field processing rules are determined in the field mapping table, and the business master data is transformed based on the field processing rules to obtain the target business data; Based on the interface configuration module, the target business terminal identifier associated with the business data is determined, and the target business data is sent to the target business terminal associated with the initial business terminal based on the target business terminal identifier. The initial business terminal and the target business terminal are heterogeneous business terminals.

[0005] According to a second aspect of the embodiments of this specification, a data processing apparatus is provided, applied to a business server, comprising: The receiving module is configured to receive data processing requests submitted by the initial business terminal through the interface configuration module, and to parse the data processing requests to obtain business data. The conversion module is configured to determine field processing rules in a field mapping table based on the business master data corresponding to the business data, and to convert the business master data based on the field processing rules to obtain the target business data; The sending module is configured to determine the target service terminal identifier associated with the service data based on the interface configuration module, and send the target service data to the target service terminal associated with the initial service terminal based on the target service terminal identifier, wherein the initial service terminal and the target service terminal are heterogeneous service terminals.

[0006] According to a third aspect of the embodiments of this specification, a computing device is provided, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions, which, when executed by the processor, implement the steps of the above-described data processing method.

[0007] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores computer-executable instructions, which, when executed by a processor, implement the steps of the data processing method described above.

[0008] According to a fifth aspect of the embodiments of this specification, a computer program product is provided, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0009] This specification provides a data processing method in one embodiment, applied to a business server. It receives a data processing request submitted by an initial business client through an interface configuration module, parses the request, and obtains business data. Based on the corresponding business master data, it determines field processing rules in a field mapping table and transforms the business master data based on these rules to obtain target business data. For the business data provided by the initial business client, it uses a field mapping table containing rich field processing rules to match these rules and transforms the business master data, reducing manual intervention and business code modifications. The rich field processing rules can adapt to various business scenarios. Based on the interface configuration module, it determines the target business client identifier associated with the business data and sends the target business data to the target business client associated with the initial business client. Through the collaboration of the interface configuration module and the field mapping table, the data processing flow can adapt to various business scenarios, achieving efficient connection between heterogeneous initial and target business clients without code modifications. Attached Figure Description

[0010] Figure 1 This is a schematic diagram of a data processing method provided in one embodiment of this specification; Figure 2 This is a flowchart illustrating a data processing method provided in one embodiment of this specification; Figure 3This is a flowchart illustrating the processing procedure of a data processing method provided in one embodiment of this specification. Figure 4 This is a schematic diagram of the structure of a data processing apparatus provided in one embodiment of this specification; Figure 5 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0011] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0012] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0013] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0014] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0015] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0016] QMT System (Quick Model Trade / Xuntou Quantitative Trading Terminal): A professional quantitative trading platform primarily targeting quantitative private equity funds and high-net-worth individuals. It integrates market data display, strategy writing, backtesting, and live trading, supports the Python language, and covers trading instruments including stocks, futures, and options.

[0017] GMatrix System: A "Customized Strategy" service platform. This system provides clients with exclusive customized strategy services and is a digital investment research and trading platform integrating investment research, trade execution, and performance analysis.

[0018] JinGu Arbitrage (JinGu ETF Trading Platform / System): A professional platform focusing on ETF arbitrage trading, jointly launched by multiple securities firms. It provides streamlined arbitrage operations, supports Level-2 market data and various arbitrage modes (such as instantaneous and delayed arbitrage).

[0019] iTrade is a comprehensive real-time trading and information system designed for retail banks. It provides electronic order book entry management, portfolio display, and back-end connectivity, aiming to improve order execution speed and efficiency.

[0020] In the fintech sector, during the construction and operation of institutional investment management systems, account master data such as institutional account opening, products, fund accounts, and operators typically need to be consistent across multiple heterogeneous business systems (e.g., itrade, QMT, JinGu Arbitrage, GMatrix). In current practice, this master data is often maintained separately by each external system, resulting in a large amount of repetitive data entry work and making it difficult to establish a unified master data standard and consistent authorization view. Significant differences exist in field naming and coding values ​​across systems, making cross-system account opening reliant on manual verification inefficient and error-prone, and increasing the cost of cross-system verification. Figure 1 A schematic diagram of a data processing method according to an embodiment of this specification is shown, such as... Figure 1As shown in the figure, the data processing method provided in one embodiment of this specification is applied to a business server. It receives a data processing request submitted by the initial business client through an interface configuration module, parses the request, and obtains business data. Based on the business master data corresponding to the business data, it determines field processing rules in a field mapping table and transforms the business master data based on these rules to obtain the target business data. For the business data provided by the initial business client, a field mapping table containing rich field processing rules is used to match these rules, and the business master data is transformed using these rules, reducing manual intervention and business code modifications. The rich field processing rules can adapt to various business scenarios. Based on the interface configuration module, the target business client identifier associated with the business data is determined, and the target business data is sent to the target business client associated with the initial business client based on this identifier. With the collaboration of the interface configuration module and the field mapping table, the data processing flow can adapt to various business scenarios, enabling the connection between heterogeneous initial and target business clients without code modifications.

[0021] This specification provides a data processing method, and also relates to a data processing apparatus, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0022] See Figure 2 , Figure 2 A flowchart of a data processing method according to an embodiment of this specification is shown, which specifically includes the following steps.

[0023] Step 202: Receive the data processing request submitted by the initial business terminal through the interface configuration module, and parse the data processing request to obtain business data.

[0024] Specifically, the data processing method is applied to the business server, which can be a unified account management server. This server provides a unified account master data model for managing at least two heterogeneous business terminals. These heterogeneous business terminals are business systems; correspondingly, the initial business terminal is the initial business system, which can be an upstream business system. Data processing requests can be data operation requests in the financial field, such as account opening requests or account change requests. The unified account master data model uses "fund account + institution + product + operator" as its core data domain, with the business terminal identifier as its identity identifier. The unified account master data model converges the semantics of multiple business terminal fields to a unified field definition through field mapping configuration and enables configurable addressing of each external business terminal through interface address configuration. The interface configuration module is the interface address configuration service in the unified account master data model. Business data refers to the business request message obtained by parsing the data processing request.

[0025] Based on this, the business server receives a data processing request submitted by the initial business end through invoking the interface configuration module, and parses the data processing request to obtain business data. As the receiver of the data processing request, the business server provides an interface address configuration service for the initial business end. The initial business end can invoke the interface address configuration service to implement addressing, and submit the data processing request to the business server through the interface configuration module. Parsing the data processing request refers to invoking the unified account service to parse the data processing request, so as to obtain the business data of the financial service to be processed, where the financial service may be account opening or account modification.

[0026] In practical applications, the interface address configuration service may store interface access information of each third-party business end, such as a URL or a service endpoint, according to the business end identifier, business function classification and business operation type. When the unified account performs operations such as account opening delivery, the target address is dynamically parsed accordingly, so that the addressing is fully configurable, and the core invocation chain does not need to be modified when the vendor system is replaced.

[0027] In the financial field, the business server provides a unified account service through a unified account master data model. As an upstream business system, the initial business end may submit a data processing request to the business server through HTTP POST, and the data processing request is used to implement account opening or account modification. In the case that the data processing request corresponds to an account opening request, the business data can be obtained by parsing the data processing request, that is, the account opening request message "{\"fund_acc\":\"F001\",\"cust_name\":\"Zhang San\",\"open_date\":\"20250601\",\"broker\":\"Broker A\"}".

[0028] Step 204: Determine a field processing rule in a field mapping table according to the business master data corresponding to the business data, and convert the business master data based on the field processing rule to obtain target business data.

[0029] Specifically, after receiving the initial business client's data processing request submitted through the interface configuration module and parsing the request to obtain the business data, the field processing rules are determined in the field mapping table based on the corresponding business master data. The business master data is then transformed based on these rules to obtain the target business data. The business master data is generated from the business data and contains business data with a composite primary key of business function category and business client identifier. The field mapping table corresponds to the field mapping configuration and records at least one configuration item included in the configuration. Each configuration item includes at least one of the following: third-party message field name, unified account target field name, unified account field name, third-party message processing rule, unified account processing rule, format validation regular expression, and default parameter value. The field processing rule is the field parsing rule included in the configuration item, used to parse and transform the business master data. The target business data is the data obtained after parsing and transforming the data according to the field processing rule. The purpose of transforming the business master data according to the field processing rule is to make the target business data compatible with the business concepts of the target business client, such as field naming conventions and value encoding methods. The field processing rules in the field mapping table are used to unify the data standards between the initial business end and the target business end.

[0030] Based on this, after receiving the data processing request submitted by the initial business end through the interface configuration module and parsing the request to obtain the business data, the field processing rules are determined in the field mapping table according to the corresponding business master data. The field mapping table contains at least one configuration item, and each configuration item corresponds to at least one field processing rule. Rule matching is performed in the field mapping table based on the data type of the business master data to determine the field processing rule that matches the business master data. Based on the field processing rules, the business master data is transformed to obtain target business data with a data scope adapted to the target business end.

[0031] Furthermore, considering that business data is obtained by parsing the data processing requests submitted by the initial business end, in order to record and manage business data, we can determine the primary key identifier of the business data and record the business status of the data processing requests. The specific implementation is as follows: The system identifies account data and account business data from the business data and generates a primary key identifier based on the account data; it also determines the business status of the data processing request and generates the business master data based on the business status, the primary key identifier, and the account business data.

[0032] Specifically, the account data may be an account identifier, such as an account ID. The account service data refers to data related to account services, including but not limited to data such as account name, account opening time, and account type. The primary key identifier represents the primary key ID of the service master data. In the stage of generating service master data, the service status of the data processing request is in a to-be-processed state; after the generation of the service master data is completed, the service status of the data processing request is represented as a completed state. The service status may also indicate whether the data processing request is processed normally; after the service master data is generated, it indicates that no abnormality occurs in the data processing request, and the data processing request is in a normal state.

[0033] On this basis, account data representing the account identifier and account service data representing data such as account name and account type are determined from the service data. A primary key identifier is generated based on the account data, the service status of the data processing request is determined, and service master data is generated based on the service status, the primary key identifier and the account service data. The primary key identifier, the account service data and the service status are integrated to obtain the service master data.

[0034] For example, in the case where the initial service end is an upstream financial system, the data processing request may be an account opening request, and the account opening request is parsed to obtain an account opening request message, that is, the service data is "{\"fund_acc\":\"F001\",\"cust_name\":\"Zhang San\",\"open_date\":\"20250601\",\"broker\":\"Broker A\"}". It is determined that "fund_acc":"F001" in the service data is the account data, and "cust_name":"Zhang San", "open_date":"20250601" are the account service data. The primary key identifier "primary key ID":"M001" can be generated according to the account data. At this time, the data processing request is in the to-be-processed state, and after the service master data is generated, the service status in the service master data is the normal state. The primary key identifier, the account service data and the service status are integrated to obtain the service master data {"primary key ID":"M001","fund_acc":"F001","cust_name":"Zhang San","open_date":"20250601","status":"normal"}. The service master data can be written into the master data table, and the status is updated to account opened at the same time.

[0035] In summary, the primary key identifier, the account service data and the service status are integrated to obtain the service master data of the data processing request, and the service master data can be sent to the target service end after the data standard of the service master data is unified subsequently.

[0036] Furthermore, considering that the field mapping table corresponds to the field mapping configuration, and the field mapping table records at least one configuration item contained in the field mapping configuration, with each configuration item containing at least one field parsing rule, after determining the business master data, the field processing rule matching the business master data can be selected in the field mapping table. The specific implementation is as follows: In the business master data corresponding to the business data, at least one field to be processed is determined; in the field mapping table, field parsing rules corresponding to the at least one field to be processed are determined respectively, and the field parsing rules corresponding to the at least one field to be processed are used as the field processing rules; the field parsing rules include at least one of the following: format verification rules, value conversion rules, field concatenation rules, code table mapping rules, and format conversion rules.

[0037] Specifically, fields to be processed refer to business information fields contained in the business master data, including but not limited to the account name field and the account opening date field. Each field to be processed can correspond to at least one field parsing rule. For example, the account name field corresponds to a field parsing rule for regular expression validation, and the account opening date corresponds to a field parsing rule for format conversion. The format validation rules correspond to mandatory field validation, regular expression format validation, and length range validation, used to validate the field format of third-party messages, such as mobile phone number (regular expression ^1[3-9]\d{9}$), identity ID, account length, etc.; the value conversion rules correspond to direct assignment, default value filling, conditional value retrieval, and expression calculation, used to convert third-party enumeration values ​​into a unified standard, such as mapping "1=spot" in the QMT system to "TYPE_SPOT" in the unified account; the field concatenation rules correspond to multi-field concatenation, field splitting, and substring extraction, used to combine multiple scattered fields into complete semantics, such as assembling "province code + city code" into a complete region code; the code table mapping rules correspond to enumeration value mapping, code table conversion, and classification normalization, used to normalize code table values ​​of different business terminals, such as different fund account prefixes for different business terminals but all corresponding to the same unified account; the format conversion rules correspond to date format conversion, encoding conversion, and desensitization / encryption processing, used for date format unification (such as YYYYMMDD→standard timestamp), character encoding conversion, desensitization and encryption, etc.

[0038] Based on this, at least one field to be processed is identified in the business master data corresponding to the business data; at least one field parsing rule corresponding to each field to be processed is identified in the field mapping table, and the field parsing rule corresponding to each field to be processed is used as the field processing rule. Each field to be processed can correspond to at least one field parsing rule. The field parsing rule includes at least one of the following: format validation rule, value conversion rule, field concatenation rule, code table mapping rule, and format conversion rule. The format validation rule corresponds to mandatory field validation, regular expression format validation, and length range validation; the value conversion rule corresponds to direct assignment, default value filling, conditional value retrieval, and expression calculation; the field concatenation rule corresponds to multi-field concatenation, field splitting, and substring extraction; the code table mapping rule corresponds to enumeration value mapping, code table conversion, and classification normalization; the format conversion rule corresponds to date format conversion, encoding conversion, and desensitization / encryption processing.

[0039] Following the previous example, determine the fields to be processed in the business master data {"Primary Key ID":"M001","fund_acc":"F001","cust_name":"Zhang San","open_date":"20250601","status":"Normal"}. "fund_acc":"F001","cust_name":"Zhang San","open_date":"20250601"]. Based on the initial business terminal identifier system_tag=QMT and the business type oper_func_class=open_account, read the corresponding row set of field mapping configurations. Determine the third-party message field name and third-party message processing rules (value conversion rules, field concatenation rules) corresponding to "fund_acc":"F001". The field parsing rule for "cust_name":"Zhang San" corresponds to regular expression validation, and the field parsing rule for "open_date":"20250601" corresponds to format conversion.

[0040] In summary, the field parsing rules corresponding to at least one field to be processed in the field mapping table and the business master data are used as field processing rules. This enables the matching of field processing rules based on the business master data in the field mapping table, and the combination of the field parsing rules corresponding to at least one field to be processed to achieve automatic parsing of the business master data.

[0041] Furthermore, after determining the field processing rules that match the business master data, the business master data can be transformed based on these rules, as specifically implemented below: The account business data is determined in the business master data, and the mapping rule matching the account business data is determined in the field processing rules; the account business data is converted into the target business data according to the conversion rule corresponding to the mapping rule.

[0042] Specifically, the mapping rule matched by the account service data is the field parsing rule, such as a format verification rule, a value conversion rule, a field splicing rule, a code table mapping rule, and a format conversion rule.

[0043] On this basis, the account service data is determined from the main service data, and the mapping rule matched by the account service data is determined from the field processing rules; the account service data is converted into target service data according to the conversion rule corresponding to the mapping rule.

[0044] Continuing with the above example, the account service data "fund_acc":"F001", "cust_name":"Zhang San", "open_date":"20250601" is determined in the main service data. It is determined that "fund_acc":"F001" corresponds to a third-party message field name and a third-party message processing rule (value conversion rule, field splicing rule), "cust_name":"Zhang San" corresponds to the field parsing rule of regular verification, and "open_date":"20250601" corresponds to the field parsing rule of format conversion. source_field (third-party message field name) = "fund_acc" → target_field (unified account target field name) = "fund_account", conversion_rule (third-party message processing rule) = "direct", validation_regex = "^F\d{3}$"; regular verification (2-20 Chinese characters) is performed on cust_name, format conversion (YYYYMMDD → standard date format) is performed on open_date, and a target message {"fund_account":"F001", "cust_name":"Zhang San", "open_dt":"2025-06-01"} is generated, where the target message is the target service data.

[0045] In conclusion, the account service data is converted into the target service data according to the conversion rule corresponding to the mapping rule, so as to realize field parsing of the account service data and ensure that the target service data is accurately adapted to the target service end.

[0046] Step 206: Determine a target service end identifier associated with the service data based on the interface configuration module, and send the target service data to a target service end associated with the initial service end based on the target service end identifier, where the initial service end and the target service end are heterogeneous service ends.

[0047] Specifically, after determining the field processing rules in the field mapping table based on the business master data corresponding to the business data, and transforming the business master data based on the field processing rules to obtain the target business data, the target business terminal identifier associated with the business data can be determined based on the interface configuration module. Then, the target business data is sent to the target business terminal associated with the initial business terminal based on the target business terminal identifier. The target business terminal identifier associated with the business data can be the access address of the target business terminal. The initial business terminal and the target business terminal are heterogeneous business terminals, indicating that the initial business terminal and the target business terminal have different data interfaces and authorization views.

[0048] Based on this, after determining the field processing rules in the field mapping table according to the business master data corresponding to the business data, and transforming the business master data based on the field processing rules to obtain the target business data, the target business terminal identifier associated with the business data is determined based on the interface configuration module. Then, the target business data is sent to the target business terminal associated with the initial business terminal based on the target business terminal identifier, thus realizing the landing of the target business data to the target business terminal. The initial business terminal and the target business terminal are heterogeneous business terminals with different data definitions and authorization views.

[0049] Furthermore, after sending the target business data to the target business terminal, business feedback data can be received from the target business terminal. The business feedback data is used to compare with the business master data to achieve consistency verification, as specifically implemented as follows: Receive business feedback data associated with the target business data sent by the target business terminal; compare the business feedback data with the business master data to obtain comparison data; if the business feedback data and the business master data are consistent according to the comparison data, generate a data processing log; if the business feedback data and the business master data are inconsistent according to the comparison data, generate a data difference log and alarm information.

[0050] Specifically, business feedback data can be a data reception receipt returned by the target business end after receiving the target business data, used for data consistency verification. Comparison data represents the consistency comparison result between the business feedback data and the business master data. If the business feedback data and the business master data are consistent, the comparison data represents the conclusion of consistency. The data processing log is used to record successful business data synchronization. If the business feedback data and the business master data are inconsistent, the comparison data includes the conclusion of inconsistency, as well as information on the differences between the business feedback data and the business master data. The data difference log is used to record the differences between the business feedback data and the business master data, and the alarm information is used to indicate inconsistencies between the business feedback data and the business master data.

[0051] Based on this, the system receives business feedback data related to target business data sent by the target business end. A consistency comparison is performed between the business feedback data and the business master data to obtain comparison data representing the comparison result. If the comparison data determines that the business feedback data and the business master data are consistent, it indicates that the data between the initial business end and the target business end is consistent, and a data processing log can be generated to record successful data synchronization. If the comparison data determines that the business feedback data and the business master data are inconsistent, it indicates that the data between the initial business end and the target business end is inconsistent, and a data difference log and alarm information are generated, triggering an alarm. When comparing the business feedback data and the business master data, semantic inconsistencies in field values ​​can also be identified, such as inconsistent holdings of the same fund account on both ends, which can trigger an alarm and support automatic retries or manual intervention.

[0052] Continuing with the previous example, the target message is sent to the target system - the target business end (GMatrix, address resolved by pub_tsystemurl), and a receipt is received: {"code":"0000","msg":"success","fund_account":"F001"}, which is the business feedback data. A consistency check is performed by comparing the fund_account in the GMatrix receipt with the unified account master data. If they match, a synchronization success log is recorded; otherwise, an alarm is triggered and a difference log is recorded.

[0053] In summary, when the business feedback data and the business master data are found to be inconsistent based on the comparison data, data difference logs and alarm information are generated to ensure timely alarms when the business feedback data and the business master data are inconsistent, thus ensuring data consistency between the initial business end and the target business end.

[0054] Furthermore, during the execution of data processing requests, the entire execution process can be logged to generate request processing logs for subsequent tracing of the data processing request execution process. The specific implementation is as follows: A request processing log is constructed based on the business data, the field processing rules, and the target business terminal identifier. The request processing log is used to execute exception handling tasks.

[0055] Based on this, a request processing log is constructed using business data, field processing rules, and target business terminal identifiers. This log is used to execute exception handling tasks. As a full-link log of the data processing request execution process, the request processing log can accurately trace back to the specific business terminal identifiers, business functions, and mapping lines involved in the data processing request execution process.

[0056] Using the previous example, during the data synchronization phase of the target business end, each synchronization request is associated with its mapping rules and addressing configuration through the business function classification (oper_func_class) dimension, and the entire link log is recorded so that anomalies can be accurately traced back to the specific business end identifier, business function and mapping line.

[0057] In summary, request processing logs are constructed based on business data, field processing rules, and target business terminal identifiers to trace the execution process of data processing requests, ensuring that the specific business terminal identifier, business function, and mapping line can be accurately traced.

[0058] Furthermore, after parsing the data processing request and obtaining the business data, an internal data processing identifier can be generated, as specifically implemented below: Generate a data processing identifier corresponding to the business data, and update the processing status of the data processing request to the pending status.

[0059] Based on this, after parsing the data processing request and obtaining the business data, a data processing identifier corresponding to the business data is generated, and the processing status of the data processing request is updated to "pending processing". The data processing identifier can be maintained internally on the business server side, and the processing status of the data processing request is updated in real time as the processing progress of the data processing request, ensuring data consistency between heterogeneous business terminals.

[0060] Continuing with the previous example, the unified account service parses the data processing request, generating an internal application number REQ20250601001, which is the data processing identifier, and sets the processing status to "pending." Generating REQ20250601001 transforms the "raw HTTP message" into an "internal manageable, traceable, and retryable business task instance." This step converts external input into an internal state to ensure the stability and maintainability of the financial system. The "pending" status enables asynchronous decoupling between heterogeneous business terminals and controllable data processing request flow, ensuring eventual consistency of transaction data.

[0061] In summary, after parsing the data processing request and obtaining the business data, a data processing identifier corresponding to the business data is generated, transforming the external input into an internal state to ensure the stability and maintainability of the financial system.

[0062] Furthermore, after determining the field processing rules in the field mapping table based on the business master data corresponding to the business data, field format validation can be performed on the fields in the business master data to achieve pre-interception of invalid data. The specific implementation is as follows: The business master data is validated according to the field processing rules. If the data validation passes, the step of transforming the business master data based on the field processing rules to obtain the target business data is executed.

[0063] Based on this, the business master data is validated according to the field processing rules. If the data validation passes, it means that the fields in the business master data have passed the field format validation, and the business master data can continue to be transformed according to the field processing rules to obtain the target business data. Performing field format validation on the fields in the business master data before transforming it according to the field processing rules can achieve pre-interception of invalid data; that is, if the data validation fails, the processing of the business master data is terminated.

[0064] Following the previous example, after determining the field processing rules in the field mapping table based on the business master data corresponding to the business data, the format of the fields in the business master data is validated using regular expressions to block invalid data from entering the core domain. Invalid data includes, but is not limited to: data that fails format validation, such as letters in the mobile phone number field (not matching the range of regular expression ^1[3-9]\d{9}$); missing required fields, such as an empty fund_acc (fund account); exceeding the length limit, such as cust_name exceeding 20 characters; out-of-range values, such as fund account values ​​exceeding the preset range; and enumerated values ​​not within the code table range (such as broker="unknown broker" returned by a third-party system not being in the configured code table list). The above invalid data is intercepted at the pre-interception layer during the adaptation phase and does not enter the core domain.

[0065] In summary, if data validation passes, it means that the fields in the business master data have passed field format validation, and the business master data can continue to be transformed based on the field processing rules. Performing field format validation on the fields in the business master data allows for the pre-emptive interception of invalid data.

[0066] This specification provides a data processing method in one embodiment, applied to a business server. It receives a data processing request submitted by an initial business client through an interface configuration module, parses the request, and obtains business data. Based on the corresponding business master data, it determines field processing rules in a field mapping table and transforms the business master data based on these rules to obtain target business data. For the business data provided by the initial business client, it uses a field mapping table containing rich field processing rules to match these rules and transforms the business master data, reducing manual intervention and business code modifications. The rich field processing rules can adapt to various business scenarios. Based on the interface configuration module, it determines the target business client identifier associated with the business data and sends the target business data to the target business client associated with the initial business client. Through the collaboration of the interface configuration module and the field mapping table, the data processing flow can adapt to various business scenarios, enabling the connection between heterogeneous initial and target business clients without code modifications.

[0067] The following is in conjunction with the appendix Figure 3 Taking the application of the data processing method provided in this specification in multi-service terminal data synchronization as an example, the data processing method will be further explained. Among them, Figure 3 A flowchart illustrating the processing procedure of a data processing method according to an embodiment of this specification is shown, specifically including the following steps.

[0068] Step 302: Receive the data processing request submitted by the initial business terminal through the interface configuration module, parse the data processing request, and obtain the business data.

[0069] In the fintech field, during the construction and operation of institutional investment management systems, account master data such as institutional account opening, products, fund accounts, and operators typically need to be consistent across multiple heterogeneous business systems (e.g., itrade, QMT, JinGu Arbitrage, GMatrix). In current practice, this master data is often maintained separately by each external system, resulting in a large amount of repetitive data entry work and making it difficult to establish a unified master data standard and consistent authorization view. The naming and coding values ​​of fields differ significantly between systems, making cross-system account opening reliant on manual verification, inefficient, error-prone, and costly. This specification provides a data processing method, applied to the business server, to address these issues.

[0070] The data processing method is applied to the business server, which can be a unified account management server. This business server provides a unified account master data model for managing at least two heterogeneous business terminals. These heterogeneous business terminals are business systems; correspondingly, the initial business terminal is the initial business system, which can be an upstream business system. Data processing requests can be financial data operation requests such as account opening requests or account change requests. The unified account master data model uses "fund account + institution + product + operator" as its core data domain, with the business terminal identifier as its identity identifier. The unified account master data model converges the semantics of multiple business terminal fields to a unified field definition through field mapping configuration and enables configurable addressing of each external business terminal through interface address configuration. The interface configuration module is the interface address configuration service in the unified account master data model. Business data refers to the business request message obtained by parsing the data processing request.

[0071] In practical applications, field mapping configuration maintains the mapping rules between source fields and target fields under the same business-side identifier and business function classification dimension. Specifically, it includes: source_field: third-party message field name; target_field: unified account target field name; union_field: unified account field name; conversion_rule: third-party message processing rules (value conversion rules, union field assembly rules, etc.); union_conversion_rule: unified account processing rules (value conversion rules, union field assembly rules, etc.); validation_regex: format validation regular expression; param_value_default: default parameter value.

[0072] When the adaptation module performs data import or distribution, it reads the corresponding mapping row set according to the business function category (oper_func_class) and business terminal identifier (system_tag). First, it uses validation_regex for format verification, and then executes conversion logic such as conversion_rule sequentially. With this configuration method, adding any third-party system or adjusting field semantics only requires modifying the mapping data, resulting in zero code intrusion. Field parsing rules cover five categories: ① Format verification (3 types): required field verification, regular expression format verification, length range verification; ② Value conversion (4 types): direct assignment, default value filling, conditional value retrieval, expression calculation; ③ Union assembly (3 types): multi-field concatenation (union_conversion_rule), field splitting, substring extraction; ④ Code table mapping (3 types): enumerated value mapping (ValueMap), code table conversion, category normalization; ⑤ Special processing (3 types): date format conversion, encoding conversion, desensitization / encryption processing. The above rules can be freely combined according to business scenarios to form "single-field rule chains" or "multi-field joint rules", breaking through the limitation of traditional solutions that only support simple one-to-one mapping.

[0073] Step 304: Validate the business master data. If the data validation passes, determine the field processing rules in the field mapping table based on the business master data corresponding to the business data.

[0074] Regular expressions are used to validate the field formats of the business master data, blocking invalid data from entering the core domain. Invalid data includes, but is not limited to: data that fails format validation, such as letters in the mobile phone number field (not matching the range of regular expression ^1[3-9]\d{9}$); missing required fields, such as an empty fund_acc (fund account); exceeding the length limit, such as cust_name exceeding 20 characters; out-of-range values, such as fund account values ​​exceeding the preset range; and enumerated values ​​not within the code table range (such as broker="unknown broker" returned by a third-party system not being in the configured code table list). The above invalid data is blocked at the pre-interception layer during the adaptation phase and does not enter the core domain.

[0075] Step 306: Transform the business master data based on field processing rules to obtain the target business data.

[0076] Determine the field to be processed in the business master data {"primary key ID": "M001", "fund_acc": "F001", "cust_name": "Zhang San", "open_date": "20250601", "status": "Normal"}, where the fields are "fund_acc": "F001", "cust_name": "Zhang San", "open_date": "20250601". Read the corresponding row set of the field mapping configuration according to the initial service end identifier system_tag=QMT and the service type oper_func_class=account opening. Determine the third-party message field name and third-party message processing rules (value conversion rule, field concatenation rule) corresponding to "fund_acc": "F001". "cust_name": "Zhang San" corresponds to the field parsing rule of regular verification, and "open_date": "20250601" corresponds to the field parsing rule of format conversion.

[0077] The adaptation module reads the corresponding row set of pub_tfieldmapping (field mapping configuration) according to system_tag=QMT and oper_func_class=account opening, where source_field (third-party message field name) = "fund_acc" → target_field (unified account target field name) = "fund_account", conversion_rule (third-party message processing rule) = "direct", validation_regex="^F\d{3}$"; perform regular verification (2-20 Chinese characters) on cust_name, perform format conversion (YYYYMMDD → standard date format) on open_date, and generate the target message {"fund_account": "F001", "cust_name": "Zhang San", "open_dt": "2025-06-01"}, where the target message is the target business data.

[0078] Step 308: Determine the target service end identifier associated with the business data based on the interface configuration module, and send the target business data to the target service end associated with the initial service end based on the target service end identifier.

[0079] The target service end identifier associated with the business data may be the access address of the target service end. The initial service end and the target service end are heterogeneous service ends, which means that there are different data calibers and authorization views between the initial service end and the target service end.

[0080] Step 310: Receive the service feedback data associated with the target business data sent by the target service end, and compare the service feedback data with the business master data.

[0081] The adaptation module sends the target message to the target system (GMatrix, address resolved by pub_tsystemurl) and receives an acknowledgment {"code":"0000","msg":"success","fund_account":"F001"}, which is the business feedback data.

[0082] Step 312: If the comparison results determine that the business feedback data and the business master data are consistent, generate a data processing log. If the comparison results determine that the business feedback data and the business master data are inconsistent, generate a data difference log and alarm information.

[0083] The fund_account in the GMatrix receipt is compared with the unified account master data. If they match, a synchronization success log is recorded; otherwise, an alarm is triggered and a difference log is recorded.

[0084] Step 314: Construct a request processing log based on business data, field processing rules, and target business terminal identifier. The request processing log is used to execute exception handling tasks.

[0085] During the data synchronization phase on the target business side, each synchronization request is associated with its mapping rules and addressing configuration through the business function classification (oper_func_class) dimension, and the entire link log is recorded so that anomalies can be accurately traced back to the specific business side identifier, business function and mapping line.

[0086] In summary, the data processing method provided in one embodiment of this specification allows interface address configuration and field mapping configuration to work collaboratively under the same business dimension. New business units only need to configure data, without modifying program code, significantly reducing integration costs and risks. Interface addresses and field mappings can achieve equivalent functionality through configuration centers, parameter libraries, views, or scripted strategies. From format validation, value conversion, and joint assembly to code table mapping, a complete field semantic conversion capability is formed, breaking through the limitations of traditional solutions that only support simple one-to-one mapping. Pre-interception, process tracing, and receipt comparison form a complete consistency verification system, supporting bidirectional synchronization and data comparison to ensure eventual data consistency across multiple systems.

[0087] This embodiment constructs an account management system centered on a unified account master data model. Through a layered architecture and configurable field mapping and interface addressing mechanisms, it converges the differences between multiple systems into maintainable rules and data configurations, forming a standardized internal framework and enabling rapid system integration externally. The core of the solution is "unified account opening management." During the process of accepting institutional account opening applications, generating master data, and synchronizing with multiple external systems, it automatically completes semantic conversion and verification with the help of a rich mapping rule base, significantly reducing manual intervention and code modifications. Between the unified account master data model and the external system (business side), a "dual-table driven" mapping engine is introduced, which uses business function classification (oper_func_class) and system identifier (system_tag) as the joint primary key. This engine coordinates the interface addressing and field semantic transformation under the same business dimension, allowing the same set of adaptation processes to be repeatedly used for different systems and business scenarios. At the same time, the code table and enumeration value domain are extended and transformed through the ValueMap auxiliary mapping interface, so that the mapping capability not only covers the one-to-one correspondence of field names, but also covers the semantic normalization and joint assembly of value space, thereby achieving zero-code intrusion interface expansion under the condition of heterogeneous business sides.

[0088] Corresponding to the above method embodiments, this specification also provides data processing apparatus embodiments. Figure 4 A schematic diagram of the structure of a data processing apparatus according to one embodiment of this specification is shown. Figure 4 As shown, the data processing device is used on the business server side, and the device includes: The receiving module 402 is configured to receive a data processing request submitted by the initial business terminal through the interface configuration module, and to parse the data processing request to obtain business data; The conversion module 404 is configured to determine field processing rules in the field mapping table based on the business master data corresponding to the business data, and to convert the business master data based on the field processing rules to obtain the target business data; The sending module 406 is configured to determine the target service terminal identifier associated with the service data based on the interface configuration module, and send the target service data to the target service terminal associated with the initial service terminal based on the target service terminal identifier, wherein the initial service terminal and the target service terminal are heterogeneous service terminals.

[0089] In an optional embodiment, the determination of the business master data includes: Identify account data and account business data from the business data, and generate a primary key identifier based on the account data; Determine the business status of the data processing request, and generate the business master data based on the business status, the primary key identifier, and the account business data.

[0090] In an optional embodiment, determining the field processing rules in the field mapping table based on the business master data corresponding to the business data includes: At least one field to be processed is identified in the business master data corresponding to the business data; Determine the field parsing rules corresponding to the at least one field to be processed in the field mapping table, and use the field parsing rules corresponding to the at least one field to be processed as the field processing rules. The field parsing rules include at least one of the following: format verification rules, value conversion rules, field concatenation rules, code table mapping rules, and format conversion rules.

[0091] In an optional embodiment, the transformation of the business master data based on the field processing rules to obtain target business data includes: The account business data is determined in the business master data, and the mapping rule matching the account business data is determined in the field processing rules; The account business data is converted into the target business data according to the conversion rules corresponding to the mapping rules.

[0092] In an optional embodiment, after sending the target service data to the target service terminal associated with the initial service terminal based on the target service terminal identifier, the method further includes: Receive business feedback data associated with the target business data sent by the target business terminal; The business feedback data and the business master data are compared to obtain comparison data. If the business feedback data and the business master data are determined to be consistent based on the comparison data, a data processing log is generated; If, based on the comparison data, it is determined that the business feedback data and the business master data are inconsistent, a data difference log and alarm information are generated.

[0093] In an optional embodiment, the method further includes: A request processing log is constructed based on the business data, the field processing rules, and the target business terminal identifier. The request processing log is used to execute exception handling tasks.

[0094] In an optional embodiment, after parsing the data processing request to obtain business data, the process further includes: Generate a data processing identifier corresponding to the business data, and update the processing status of the data processing request to the pending status.

[0095] In an optional embodiment, after determining the field processing rules in the field mapping table based on the business master data corresponding to the business data, the method further includes: The business master data is validated according to the field processing rules. If the data validation passes, the step of transforming the business master data based on the field processing rules to obtain the target business data is executed.

[0096] This specification provides a data processing apparatus in one embodiment, applied to a business server. It receives data processing requests submitted by an initial business client through an interface configuration module, parses the requests, and obtains business data. Based on the corresponding business master data, it determines field processing rules in a field mapping table and transforms the business master data based on these rules to obtain target business data. For the business data provided by the initial business client, it uses a field mapping table containing rich field processing rules to match these rules and transforms the business master data, reducing manual intervention and business code modifications. The rich field processing rules can adapt to various business scenarios. Based on the interface configuration module, it determines the target business client identifier associated with the business data and sends the target business data to the target business client associated with the initial business client. Through the collaboration of the interface configuration module and the field mapping table, the data processing flow can adapt to various business scenarios, enabling the connection between heterogeneous initial and target business clients without code modifications.

[0097] The above is an illustrative scheme of a data processing apparatus according to this embodiment. It should be noted that the technical solution of this data processing apparatus and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the data processing apparatus, please refer to the description of the technical solution of the data processing method described above.

[0098] Figure 5 A structural block diagram of a computing device 500 according to one embodiment of this specification is shown. The components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and a database 550 is used to store data.

[0099] The computing device 500 also includes an access device 540, which enables the computing device 500 to communicate via one or more networks 560. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 540 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.

[0100] In one embodiment of this specification, the above-described components of the computing device 500 and Figure 5 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 5 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0101] The computing device 500 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 500 can also be a mobile or stationary server.

[0102] The processor 520 is configured to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the above-described data processing method.

[0103] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the data processing method described above.

[0104] An embodiment of this specification also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0105] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the data processing method described above.

[0106] An embodiment of this specification also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0107] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the data processing method described above.

[0108] 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 the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0109] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0110] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0111] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0112] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described in this specification. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification.

Claims

1. A data processing method, applied to a business server, characterized in that, include: The system receives data processing requests submitted by the initial business end through the interface configuration module, parses the data processing requests, and obtains business data. The unified account master data model provided by the business server uses the business end identifier as the identity identifier. Through field mapping configuration, the semantics of multiple business end fields are converged to a unified field definition. The unified account master data model and the business end are connected by a dual-table driven mapping engine with business function classification and business end identifier as joint primary keys, which is used to coordinate the configuration of interface addressing and field semantic conversion under the same business dimension. Based on the business master data corresponding to the business data, the field processing rules are determined in the field mapping table, and the business master data is transformed based on the field processing rules to obtain the target business data; Based on the interface configuration module, the target business terminal identifier associated with the business data is determined, and the target business data is sent to the target business terminal associated with the initial business terminal based on the target business terminal identifier. The initial business terminal and the target business terminal are heterogeneous business terminals.

2. The data processing method according to claim 1, characterized in that, The determination of the business master data includes: Identify account data and account business data from the business data, and generate a primary key identifier based on the account data; Determine the business status of the data processing request, and generate the business master data based on the business status, the primary key identifier, and the account business data.

3. The data processing method according to claim 1, characterized in that, The step of determining field processing rules in the field mapping table based on the business master data corresponding to the business data includes: At least one field to be processed is identified in the business master data corresponding to the business data; Determine the field parsing rules corresponding to the at least one field to be processed in the field mapping table, and use the field parsing rules corresponding to the at least one field to be processed as the field processing rules. The field parsing rules include at least one of the following: format verification rules, value conversion rules, field concatenation rules, code table mapping rules, and format conversion rules.

4. The data processing method according to claim 2, characterized in that, The process of transforming the business master data based on the field processing rules to obtain the target business data includes: The account business data is determined in the business master data, and the mapping rule matching the account business data is determined in the field processing rules; The account business data is converted into the target business data according to the conversion rules corresponding to the mapping rules.

5. The data processing method according to claim 1, characterized in that, After sending the target service data to the target service terminal associated with the initial service terminal based on the target service terminal identifier, the method further includes: Receive business feedback data associated with the target business data sent by the target business terminal; The business feedback data and the business master data are compared to obtain comparison data. If the business feedback data and the business master data are determined to be consistent based on the comparison data, a data processing log is generated; If, based on the comparison data, it is determined that the business feedback data and the business master data are inconsistent, a data difference log and alarm information are generated.

6. The data processing method according to any one of claims 1-5, characterized in that, The method further includes: A request processing log is constructed based on the business data, the field processing rules, and the target business terminal identifier. The request processing log is used to execute exception handling tasks.

7. The data processing method according to claim 1, characterized in that, After parsing the data processing request to obtain the business data, the process also includes: Generate a data processing identifier corresponding to the business data, and update the processing status of the data processing request to the pending status.

8. The data processing method according to claim 1, characterized in that, After determining the field processing rules in the field mapping table based on the business master data corresponding to the business data, the process further includes: The business master data is validated according to the field processing rules. If the data validation passes, the step of transforming the business master data based on the field processing rules to obtain the target business data is executed.

9. A data processing apparatus, applied to a business server, characterized in that, include: The receiving module is configured to receive data processing requests submitted by the initial business end through the interface configuration module, and parse the data processing requests to obtain business data. The unified account master data model provided by the business server uses the business end identifier as the identity identifier and converges the semantics of multiple business end fields to a unified field definition through field mapping configuration. The unified account master data model and the business end are provided with a dual-table driven mapping engine with business function classification and business end identifier as joint primary keys, which is used to coordinate the configuration of interface addressing and field semantic conversion under the same business dimension. The conversion module is configured to determine field processing rules in a field mapping table based on the business master data corresponding to the business data, and to convert the business master data based on the field processing rules to obtain the target business data; The sending module is configured to determine the target service terminal identifier associated with the service data based on the interface configuration module, and send the target service data to the target service terminal associated with the initial service terminal based on the target service terminal identifier, wherein the initial service terminal and the target service terminal are heterogeneous service terminals.

10. A computing device, characterized in that, include: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions, which, when executed by the processor, implement the steps of the data processing method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, It stores computer-executable instructions that, when executed by a processor, implement the steps of the data processing method according to any one of claims 1 to 8.

12. A computer program product, characterized in that, It includes a computer program or instructions that, when executed by a processor, implement the steps of the data processing method according to any one of claims 1 to 8.

Images