Flow data processing method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to the technical field of big data processing, and particularly discloses a pipeline data processing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: receiving a first flow data acquisition request, acquiring a corresponding requested party identity identifier according to a first requester identity identifier after the first requester identity identifier passes verification, generating a second flow data acquisition request based on the requested party identity identifier under the condition that the current moment is matched with the target moment, and sending the second flow data acquisition request to a server; sending a second flow data acquisition request to a flow data storage device corresponding to the requested party identity identifier, and receiving flow data corresponding to the requested party identity identifier returned by the flow data storage device after the verification of the requested party identity identifier is passed; and classifying the flow data according to the purpose category of the flow data and the channel information corresponding to the identity identifier of the requested party. By adopting the method, the safety can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of big data processing, and in particular to a pipeline data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of computer technology, more and more companies use computer technology to process their business, including but not limited to obtaining business flow data.

[0003] In the related art, when implementing the process of acquiring business flow data, the flow data storage device acquires the flow data according to the received flow data acquisition request, and processes the flow data after acquiring the flow data.

[0004] However, in the process of obtaining the flow data in the related art, there are cases where illegal requests are made to obtain data. Therefore, there is a problem in the related art that the flow data is not secure enough. Summary of the invention

[0005] Based on this, it is necessary to provide a pipeline data processing method, device, computer equipment, computer-readable storage medium and computer program product that can improve security in response to the above-mentioned technical problems.

[0006] In a first aspect, the present application provides a pipeline data processing method, comprising:

[0007] Receive a first transaction data acquisition request, where the first transaction data acquisition request carries an identity identifier of a first requesting party;

[0008] After the first requesting party identity is verified, the corresponding requested party identity is obtained according to the first requesting party identity;

[0009] When the current time matches the target time, a second stream data acquisition request is generated based on the requested party identity, and the second stream data acquisition request is sent to the stream data storage device corresponding to the requested party identity, wherein the target time is the pre-generated stream data acquisition time corresponding to the requested party identity;

[0010] Receiving the flow data corresponding to the identity identifier of the requested party returned by the flow data storage device after the identity identifier of the requested party is verified;

[0011] The transaction data is classified and processed according to the usage category of the transaction data and the channel information corresponding to the identity identifier of the requested party.

[0012] In one embodiment, the second stream data request also carries the identity of the second requesting party; after the stream data storage device verifies the identity of the requested party and before returning the stream data corresponding to the identity of the requested party, the method also includes: receiving the public key returned by the stream data storage device, the public key is generated by the stream data storage device after determining that the identity of the second requesting party has been verified; receiving the stream data corresponding to the identity of the requested party, including: receiving the encrypted stream data sent by the stream data storage device, the stream data corresponds to the identity of the requested party, the encrypted stream data is obtained by encrypting the stream data with a private key, and the public key and the private key are set correspondingly; using the public key to parse and process the encrypted stream data to obtain decrypted stream data.

[0013] In one of the embodiments, the transaction data is classified according to the purpose category of the transaction data and the channel information corresponding to the identity identifier of the requested party, including: matching the purpose category with the account identifier of the pre-generated account; when the purpose category matches the account name of the pre-generated account, determining whether the pre-generated account includes a sub-account; when the pre-generated account includes a sub-account, obtaining the sub-account identifier corresponding to the sub-account; and classifying the transaction data according to the sub-account identifier and the channel information.

[0014] In one embodiment, transaction data is classified and processed according to subaccount identifiers and channel information, including: matching the subaccount identifier of the subaccount with the channel information of the transaction data; when the subaccount identifier of the subaccount matches the channel information of the transaction data, adding the transaction data to an array directory corresponding to the subaccount; when the subaccount identifier of the subaccount does not match the channel information of the transaction data, generating a new subaccount using the channel information of the transaction data as a subaccount identifier, and adding the transaction data to an array directory corresponding to the new subaccount.

[0015] In one of the embodiments, before matching the purpose category with the account name of the pre-generated account, the method further includes: receiving project data, the project data including the purpose of each project; and generating the pre-generated account using the purpose of each project as an account identifier.

[0016] In one embodiment, after matching the usage category with the account name of the pre-generated account, the method further includes: generating an alarm message when the usage category does not match the account identifier of the pre-generated account.

[0017] In a second aspect, the present application provides a pipeline data processing device, comprising:

[0018] A request receiving module, used for receiving a first pipeline data acquisition request, wherein the first pipeline data acquisition request carries an identity identifier of a first requesting party;

[0019] An identity acquisition module, used to acquire the corresponding requested party identity according to the first requesting party identity after verifying the first requesting party identity;

[0020] A request generation and sending module, used to generate a second stream data acquisition request based on the requested party identity identifier when the current time matches the target time, and send the second stream data acquisition request to the stream data storage device corresponding to the requested party identity identifier, wherein the target time is the pre-generated stream data acquisition time corresponding to the requested party identity identifier;

[0021] A flow data receiving module, used for receiving the flow data corresponding to the identity identifier of the requested party returned by the flow data storage device after the identity identifier of the requested party is verified;

[0022] The classification module is used to classify the transaction data according to the usage category of the transaction data and the channel information corresponding to the identity of the requested party.

[0023] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above-mentioned method embodiments when executing the computer program.

[0024] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the above-mentioned method embodiments when the computer program is executed by a processor.

[0025] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned method embodiments when executed by a processor.

[0026] The above-mentioned flow data processing method, device, computer equipment, computer-readable storage medium and computer program product, the server obtains the corresponding requested party identity according to the first requesting party identity carried in the first flow data acquisition request, and generates a second flow data acquisition request according to the requested party identity, sends the second flow data acquisition request to the flow data storage device, receives the flow data corresponding to the requested party identity returned by the flow data storage device, realizes the targeted acquisition of flow data, reduces the situation where the server obtains data from illegal devices, effectively reduces the redundancy of the server receiving data, reduces the possibility of server crashes, and improves security. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0028] Figure 1 An application environment diagram of a pipeline data processing method in one embodiment;

[0029] Figure 2 A schematic diagram of a flow chart of a pipeline data processing method in one embodiment;

[0030] Figure 3 A schematic diagram of a flow chart of a pipeline data processing method in another embodiment;

[0031] Figure 4 is a structural block diagram of a pipeline data processing device in one embodiment;

[0032] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. It should be noted that in the embodiments of the present application, certain software, groups, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0034] 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 this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations. The acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with relevant provisions of national laws and regulations.

[0035] The pipeline data processing method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The server 104 receives the first flow data acquisition request sent by the terminal 102, and the first flow data acquisition request carries the first requesting party identity; after verifying that the first requesting party identity is passed, the corresponding requested party identity is obtained according to the first requesting party identity; when the current moment matches the target moment, a second flow data acquisition request is generated based on the requested party identity, and the second flow data acquisition request is sent to the flow data storage device corresponding to the requested party identity, and the target moment is the pre-generated flow data acquisition moment corresponding to the requested party identity; after receiving the flow data storage device after verifying that the requested party identity is passed, the flow data corresponding to the requested party identity is returned; according to the use category of the flow data and the channel information corresponding to the requested party identity, the flow data is classified and processed. The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. The IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices may be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.

[0036] In an exemplary embodiment, Figure 2 As shown, a pipeline data method is provided, which is applied to Figure 1 The server in the example is used to illustrate, including the following steps 202 to 210. Among them:

[0037] Step 202: Receive a first pipeline data acquisition request.

[0038] Optionally, the first transaction data acquisition request carries an identity identifier of the first requesting party.

[0039] The first requester identity identifier is used to identify the identity information of the user who issues the first transaction data acquisition request.

[0040] Optionally, the first requesting party identity identifier may be account information. Exemplarily, a project platform may be provided, where users publish related projects, such as charity projects. In an optional embodiment, users may register on the project platform so that they may use the project platform to publish related projects. Optionally, when registering on the project platform, users may set account information and a corresponding password. Optionally, the project platform may be set on a server.

[0041] Optionally, the user logs in using account information and a corresponding password, and after logging in, the project platform sends a display interface to the user's corresponding terminal, and the user operates the project through the display interface, for example, publishing the project, managing the published projects, etc.

[0042] In one embodiment, when a user uses the project platform to publish a related project, he or she may set a corresponding requested party. Optionally, the requesting party may correspond to at least one requested party.

[0043] The requested party is used to represent the account corresponding to the requesting party and used to perform resource transfer. Optionally, the requested party can be a WeChat account or an Alipay account opened by the requesting party. For example, if a user publishes a project on a project platform and also publishes the same project on other payment platforms, the account set when publishing the same project on other payment platforms can be considered as the requested party.

[0044] Optionally, a requested party identity may be set to distinguish different requesting parties.

[0045] Optionally, the requested party may generate a requesting party identity using the channel information and the usage category.

[0046] The channel information is used to indicate which payment platform the requested party belongs to, for example, WeChat Pay or Alipay.

[0047] The purpose category is used to characterize the items for which the payment account can be used to pay for, for example, a payment account can be used to pay for a certain item.

[0048] In one embodiment, the requesting party identity and the requested party identity can be set correspondingly, so that when it is necessary to process the flow data, the corresponding requested party identity can be obtained according to the requesting party identity, and the corresponding flow data can be obtained based on the requested party identity. In this way, the server can actively obtain the required flow data, reduce the situation where the server passively receives data from illegal devices, and improve security.

[0049] In one embodiment, the generation of the first transaction data acquisition request can be generated by the user through the terminal. For example, the user logs in to the project platform through the account information used during registration, and after the login is completed, the project platform provides a display interface to the user's corresponding terminal. The display interface may include a transaction data acquisition request control. The user uses the terminal to trigger the transaction data acquisition request control to achieve the generation of the first transaction data acquisition request; or, the display interface includes a transaction data processing control. The user uses the terminal to trigger the transaction data processing control to achieve the generation of the first transaction data acquisition request.

[0050] Optionally, a first flow data acquisition request can be generated based on the first requesting party identity identifier, so that after the server obtains the first flow data acquisition request, it can obtain the first requesting party identity identifier from the first flow data acquisition request. The server can further process based on the first requesting party identity identifier, for example, confirm whether the first requesting party identity identifier is legal based on the first requesting party identity identifier, and further obtain the requested party identity identifier if it is legal.

[0051] Optionally, the first requesting party identity identifier can be the user's account information. For example, when the user uses the terminal to operate the display interface to generate a first transaction data acquisition request, the terminal obtains the account information as the first requesting party identity identifier, generates a first transaction data acquisition request based on the obtained account information, and the terminal sends the generated first transaction data acquisition request to the server.

[0052] In an optional embodiment, the first pipeline data acquisition request may also be generated by the server itself.

[0053] Optionally, different transaction data acquisition times can be set and stored for different users. The server obtains the current time and matches the current time with the transaction data acquisition time corresponding to the user. When a match occurs, the first requesting party identity corresponding to the user at this time is obtained, and a first requesting party acquisition request is generated based on the first requesting party identity.

[0054] Step 204: after the first requesting party identity is verified, the corresponding requested party identity is obtained according to the first requesting party identity.

[0055] In one embodiment, after obtaining the first flow data acquisition request, the server can extract the first requester identity from the first flow data acquisition request and process the first requester identity, for example, verify whether the first requester identity is legal.

[0056] In one embodiment, after obtaining the first requester identity, the server can send a verification code to the terminal corresponding to the first requester identity, receive the input verification code returned by the terminal, and match the input verification code with the sent verification code. If they match, the first requester identity is considered to have been verified, and the first requester identity can be considered to be legal. Optionally, after verifying the legality of the first requester identity, the server obtains the corresponding requested party identity based on the first requester identity, and obtains the corresponding flow data based on the requested party identity. The above method can improve the security of obtaining flow data.

[0057] Step 206: When the current time matches the target time, a second pipeline data acquisition request is generated based on the requested party identity, and the second pipeline data acquisition request is sent to the pipeline data storage device corresponding to the requested party identity.

[0058] The target time is the time for obtaining the pre-generated flow data corresponding to the identity identifier of the requested party.

[0059] Optionally, when setting the requesting party identifier and the requested party identifier, the user may set different target times for different requested party identifiers. Optionally, the server may pre-store the target times corresponding to the requested party identifiers.

[0060] Optionally, the setting of the target time can be related to the service system corresponding to the requested party identifier. When the service system is set with a time when the running data is allowed to be obtained, the target time is after the time when the running data is allowed to be obtained. For example, if the service system sets the time when the running data is allowed to be obtained after 10 o'clock every night, the target time can be set to any time after 10 o'clock every night. When the server system does not have a time when the running data is allowed to be obtained, the target time can be set by the user as needed, and there is no limitation on this.

[0061] In one embodiment, the server obtains the current time and matches the current time with the stored target time. When the current time matches the target time, the requested party identity corresponding to the target time is obtained, and a second stream data acquisition request is generated based on the obtained requested party identity. The second stream data acquisition request can be sent to the stream data storage device corresponding to the requested party identity.

[0062] Optionally, when there are multiple requested party identities, a corresponding second stream data acquisition request may be generated for each requested party identity, and the second stream data acquisition request may be sent to the stream data storage device corresponding to the requested party identity.

[0063] In one embodiment, if the current time does not match the target time, a second stream data acquisition request can be generated based on the requested party identifier, and when the target time is reached, the second stream data acquisition request is sent to the stream data storage device corresponding to the requested party identifier.

[0064] Step 208: receiving the flow data corresponding to the identity identifier of the requested party returned by the flow data storage device after the identity identifier of the requested party is successfully verified.

[0065] The flow data storage device is used to store the flow data corresponding to the requested party identifier.

[0066] Optionally, there may be multiple running data storage devices, and different requested party identifiers correspond to different running data storage devices. When the server sends a second running data acquisition request to the running data storage device, it sends the second running data acquisition request corresponding to the requested party identifier to the running data storage devices corresponding to different requesting party identifiers.

[0067] Optionally, the flow data storage device may also be one, and the flow data corresponding to different requested party identifiers are stored in the same flow data storage device. The server then sends a second flow data acquisition request to the same flow data storage device. After receiving the second flow data acquisition request, the flow data storage device extracts the requested party identity identifier from the second flow data acquisition request, and acquires the corresponding flow data based on the requested party identity identifier.

[0068] In one embodiment, in order to ensure the security of the flow data, the flow data storage device verifies whether the requested party identifier is legal after obtaining the second flow data acquisition request and obtaining the requested party identifier from the second flow data acquisition request. Only after verifying that the requested party identifier is legal does it execute the step of obtaining the corresponding flow data according to the requested party identifier.

[0069] Optionally, after obtaining the identity identifier of the requested party, the flow data storage device can generate a verification code for the requested party identifier, send the verification code to the terminal corresponding to the requested party identifier, receive the input verification information returned by the terminal corresponding to the requested party identifier, and match the sent verification code with the verification information. If they match, the identity authentication corresponding to the requested party identifier is passed.

[0070] In one embodiment, to further ensure data security, the second requester identity may be encapsulated in the second pipeline data request, wherein the second requester identity may be an identity of a server, used to verify whether communication between the server and the pipeline data storage device is allowed.

[0071] In one embodiment, after the receiving running data storage device verifies the identity of the requested party and before returning the running data corresponding to the identity of the requested party, the running data processing method also includes: receiving the public key returned by the running data storage device; receiving the encrypted running data sent by the running data storage device, the running data corresponding to the identity of the requested party, and using the public key to parse and process the encrypted running data to obtain decrypted running data.

[0072] The public key and the private key are generated by the running data storage device after the second requester's identity verification is confirmed, and the public key and the private key are set in pairs. The private key is used to encrypt the running data, and the public key is used to decrypt the running data encrypted by the private key.

[0073] Optionally, the flow data storage device obtains the second requester identity from the second flow data request, and verifies whether the second requester identity is legal. If it is legal, a public key can be generated, and the generated public key can be returned to the device corresponding to the second requester identity, so that the second requester identity can decrypt the data encrypted by the private key according to the public key to obtain the required data. The specific public key and private key are not limited here, as long as encryption and decryption can be achieved.

[0074] Step 210: classify the transaction data according to the usage category of the transaction data and the channel information corresponding to the identity identifier of the requested party.

[0075] In one embodiment, account-related information for classification may be generated in advance, so that after the transaction data is acquired, the usage category and channel information of the transaction data may be classified.

[0076] Optionally, project data may be accepted, the project data including the purpose of each project, and each project purpose may be used as an account identifier to generate a pre-generated account. Exemplarily, when a user publishes a project on the project platform, he or she may fill in the purpose category of the project together. After obtaining the purpose category, the project platform may generate a pre-generated account based on the purpose category, for example, using the purpose category as the account name to generate a pre-generated account.

[0077] In an optional embodiment, the generation of sub-accounts can also be achieved based on channel information. Exemplarily, when a user publishes a project on a project platform, the user can also input channel information in advance, so that the project platform generates sub-accounts under the pre-generated account based on the channel information. Exemplarily, when a project is published on a project platform, it can be pre-determined on which other payment platforms the corresponding project is also published. The determined other payment platforms are the channel information, so that the project platform can generate sub-accounts based on the channel information, for example, using the channel information as the name of the sub-account. Optionally, a user can publish a project on the project platform, and the project platform monitors whether the same user publishes the same project on other payment platforms. If it is monitored that the user publishes the same project on other payment platforms, the corresponding channel information determined by the payment platform is obtained, and a sub-account is generated based on the obtained channel information.

[0078] In an optional embodiment, after obtaining the transaction data, the channel information corresponding to the transaction data and the purpose category of the transaction data can be obtained, and the transaction data can be classified using the purpose category of the transaction data and the channel information of the transaction data. Optionally, the purpose category is matched with the account identifier of the pre-generated account; if the purpose category matches the account name of the pre-generated account, it is determined whether the pre-generated account includes a sub-account; if the pre-generated account includes a sub-account, the sub-account identifier corresponding to the sub-account is obtained; and the transaction data is classified according to the sub-account identifier and the channel information.

[0079] In an optional embodiment, when the usage category does not match the account identifier of the pre-generated account, a warning message is generated so that the user can make manual adjustments.

[0080] In one embodiment, the account identifier may be generated using the usage category when the usage category does not match the account identifier of the pre-generated account.

[0081] Optionally, classifying the transaction data according to the subaccount identifier and channel information may include: matching the subaccount identifier of the subaccount with the channel information of the transaction data; when the subaccount identifier of the subaccount matches the channel information of the transaction data, adding the transaction data to the array directory corresponding to the subaccount; when the subaccount identifier of the subaccount does not match the channel information of the transaction data, generating a new subaccount using the channel information of the transaction data as the subaccount identifier, and adding the transaction data to the array directory corresponding to the new subaccount.

[0082] In the above-mentioned flow data processing method, the server obtains the corresponding requested party identity according to the first requesting party identity carried in the first flow data acquisition request, generates a second flow data acquisition request according to the requested party identity, sends the second flow data acquisition request to the flow data storage device, receives the flow data corresponding to the requested party identity returned by the flow data storage device, realizes the directional acquisition of flow data, reduces the situation that the server obtains data from illegal devices, effectively reduces the redundancy of the server receiving data, reduces the possibility of server crash, and improves security. Moreover, in the process of realizing the acquisition of flow data, it also involves the verification of the requesting party identity. After the verification is passed, the requested party identity is obtained, which can ensure the security of the obtained requested party identity, thereby ensuring the security of the acquired data. Furthermore, it also includes the verification of the requested party identity. After the verification is passed, the step of obtaining flow data according to the requested party identity is performed, which can further improve the security of the data.

[0083] In an exemplary embodiment, Figure 3 As shown, a pipeline data processing method is provided, and the method is applied to Figure 1 Taking the server as an example, step A includes steps 302 to 326. Among them:

[0084] Step 302: Receive a first pipeline data acquisition request.

[0085] Optionally, the first transaction data acquisition request carries an identity identifier of the first requesting party.

[0086] Step 304: after the first requesting party identity is verified, the corresponding requested party identity is obtained according to the first requesting party identity.

[0087] Step 306: When the current time matches the target time, a second pipeline data acquisition request is generated based on the requested party identity, and the second pipeline data acquisition request is sent to the pipeline data storage device corresponding to the requested party identity.

[0088] The target time is the time for obtaining the pre-generated flow data corresponding to the identity identifier of the requested party.

[0089] Optionally, the second transaction data request carries an identity identifier of a second requesting party.

[0090] Step 308: Receive the public key returned by the running data storage device. The public key is generated by the running data storage device after determining that the identity of the second requesting party has been authenticated.

[0091] Step 310: receiving the encrypted flow data corresponding to the identity identifier of the requested party returned by the flow data storage device after verifying the identity identifier of the requested party.

[0092] Optionally, the encrypted flow data is obtained by encrypting the flow data with a private key, and the public key and the private key are set correspondingly.

[0093] Step 312, using the public key to parse the encrypted flow data to obtain decrypted flow data.

[0094] Step 314 , determining whether the usage category matches the account identifier of the pre-generated account, if so, executing step 316 , if not, executing step 326 .

[0095] Step 316 , determining whether the pre-generated account includes a sub-account, if so, executing step 318 , if not, executing step 324 .

[0096] Step 318, obtaining the sub-account identifier corresponding to the sub-account.

[0097] Step 320, determine whether the sub-account identifier of the sub-account matches the channel information of the transaction data, if so, execute step 322, if not, execute step 324.

[0098] Step 322, add the transaction data to the array directory corresponding to the sub-account.

[0099] Step 324, using the channel information of the transaction data as the sub-account identifier to generate a new sub-account, and adding the transaction data to the array directory corresponding to the new sub-account.

[0100] Step 326, generate warning information.

[0101] In this embodiment, the server obtains the corresponding requested party identity according to the first requesting party identity carried in the first flow data acquisition request, generates a second flow data acquisition request according to the requested party identity, sends the second flow data acquisition request to the flow data storage device, receives the flow data corresponding to the requested party identity returned by the flow data storage device, realizes the acquisition of directional flow data, reduces the situation that the server obtains data from illegal devices, effectively reduces the redundancy of the server receiving data, reduces the possibility of server crash, and improves security. In addition, in the process of realizing the acquisition of flow data, it also involves the verification of the requesting party identity. After the verification is passed, the requested party identity is obtained, which can ensure the security of the obtained requested party identity, thereby ensuring the security of the acquired data. Further, it also includes the verification of the requested party identity. After the verification is passed, the step of obtaining flow data according to the requested party identity is performed, which can further improve the security of the data. In addition, in the above embodiment, the automatic classification of data can be realized through the use category and channel information to improve the data processing efficiency.

[0102] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0103] Based on the same inventive concept, the embodiment of the present application also provides a pipeline data processing device for implementing the pipeline data processing method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more pipeline data processing device embodiments provided below can refer to the limitations of the pipeline data processing method above, and will not be repeated here.

[0104] In an exemplary embodiment, Figure 4 As shown, a pipeline data processing device 400 is provided, comprising: a request receiving module 402, an identity obtaining module 404, a request generating and sending module 406, a pipeline data receiving module 408 and a classification module 410, wherein:

[0105] The request receiving module 402 is used to receive a first pipeline data acquisition request, where the first pipeline data acquisition request carries an identity identifier of a first requesting party;

[0106] The identity obtaining module 404 is used to obtain the corresponding requested party identity according to the first requesting party identity after verifying the first requesting party identity;

[0107] A request generation and sending module 406 is used to generate a second stream data acquisition request based on the requested party identity identifier when the current time matches the target time, and send the second stream data acquisition request to the stream data storage device corresponding to the requested party identity identifier, wherein the target time is the pre-generated stream data acquisition time corresponding to the requested party identity identifier;

[0108] The flow data receiving module 408 is used to receive the flow data corresponding to the identity identifier of the requested party returned by the flow data storage device after the identity identifier of the requested party is verified;

[0109] The classification module 410 is used to classify the transaction data according to the usage category of the transaction data and the channel information corresponding to the identity of the requested party.

[0110] In one embodiment, the second pipeline data request also carries the identity of the second requester; the pipeline data processing device also includes a public key receiving module for receiving the public key returned by the pipeline data storage device, and the public key is generated by the pipeline data storage device after determining that the identity of the second requester has been verified.

[0111] The flow data receiving module is also used to receive the encrypted flow data sent by the flow data storage device. The flow data corresponds to the identity of the requested party. The encrypted flow data is obtained by encrypting the flow data with a private key. The public key and the private key are set correspondingly. The encrypted flow data is parsed and processed using the public key to obtain the decrypted flow data.

[0112] In one embodiment, the classification module is also used to match the purpose category with the account identifier of the pre-generated account; when the purpose category matches the account name of the pre-generated account, determine whether the pre-generated account includes a sub-account; when the pre-generated account includes a sub-account, obtain the sub-account identifier corresponding to the sub-account; and classify the transaction data according to the sub-account identifier and channel information.

[0113] In one of the embodiments, the classification module is also used to match the subaccount identifier of the subaccount with the channel information of the transaction data; when the subaccount identifier of the subaccount matches the channel information of the transaction data, the transaction data is added to the array directory corresponding to the subaccount; when the subaccount identifier of the subaccount does not match the channel information of the transaction data, a new subaccount is generated using the channel information of the transaction data as the subaccount identifier, and the transaction data is added to the array directory corresponding to the new subaccount.

[0114] In one embodiment, the pipeline data processing device further includes an account pre-generation module for receiving project data, the project data including the purpose of each project; and generating a pre-generated account using the purpose of each project as an account identifier.

[0115] In one embodiment, the pipeline data processing device further includes an alarm generating module, which is used to generate an alarm message when the usage category does not match the account identifier of the pre-generated account.

[0116] Each module in the above-mentioned pipeline data processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0117] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 5 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a pipeline data processing method is implemented.

[0118] Those skilled in the art will understand that Figure 5The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0119] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps of the above-mentioned method embodiments when executing the computer program.

[0120] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned method embodiments are implemented.

[0121] In one embodiment, a computer program product is provided, including a computer program, which implements the steps of the above method embodiments when executed by a processor.

[0122] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0123] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0124] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A pipeline data processing method, characterized in that: The method comprises: Receive a first pipeline data acquisition request, where the first pipeline data acquisition request carries an identity identifier of a first requesting party; After verifying the identity of the first requesting party, obtaining the corresponding identity of the requested party according to the identity of the first requesting party; In the case where the current time matches the target time, generating a second stream data acquisition request based on the requested party identity, and sending the second stream data acquisition request to the stream data storage device corresponding to the requested party identity, wherein the target time is the pre-generated stream data acquisition time corresponding to the requested party identity; Receiving the flow data corresponding to the identity identifier of the requested party returned by the flow data storage device after the identity identifier of the requested party is verified; The transaction data is classified according to the usage category of the transaction data and the channel information corresponding to the identity identifier of the requested party.

2. The method according to claim 1, characterized in that The second stream data request also carries a second requesting party identity; after the receiving stream data storage device verifies the requested party identity and before returning the stream data corresponding to the requested party identity, the method further includes: Receiving a public key returned by the running data storage device, where the public key is generated by the running data storage device after determining that the identity of the second requesting party has been authenticated; Receiving flow data corresponding to the requested party identity identifier, including: Receiving the encrypted running data sent by the running data storage device, the running data corresponding to the identity identifier of the requested party, the encrypted running data being obtained by encrypting the running data with a private key, and the public key and the private key being set correspondingly; The encrypted flow data is parsed using the public key to obtain decrypted flow data.

3. The method according to claim 1 or 2, characterized in that: The classifying the transaction data according to the usage category of the transaction data and the channel information corresponding to the identity identifier of the requested party includes: Using the usage category and the account identifier of the pre-generated account for matching; In a case where the usage category matches the account name of the pre-generated account, determining whether the pre-generated account includes a sub-account; In the case where the pre-generated account includes a sub-account, obtaining a sub-account identifier corresponding to the sub-account; The transaction data is classified and processed according to the sub-account identifier and the channel information.

4. The method according to claim 3, characterized in that The classifying and processing the transaction data according to the sub-account identifier and the channel information includes: Matching the sub-account identifier of the sub-account with the channel information of the transaction data; When the sub-account identifier of the sub-account matches the channel information of the transaction data, the transaction data is added to the array directory corresponding to the sub-account; In the case that the subaccount identifier of the subaccount does not match the channel information of the transaction data, a new subaccount is generated using the channel information of the transaction data as the subaccount identifier, and the transaction data is added to the array directory corresponding to the new subaccount.

5. The method according to claim 3, characterized in that: Before matching the usage category with the account name of the pre-generated account, the method further includes: Receiving project data, the project data including the purpose of each project; The pre-generated account is generated by using the purpose of each project as an account identifier.

6. The method according to claim 3, characterized in that After matching the usage category with the account name of the pre-generated account, the method further includes: In the event that the usage category does not match the account identifier of the pre-generated account, an alarm message is generated.

7. A pipeline data processing device, characterized in that: The device comprises: A request receiving module, configured to receive a first pipeline data acquisition request, wherein the first pipeline data acquisition request carries an identity identifier of a first requesting party; An identity acquisition module, configured to acquire a corresponding requested party identity according to the first requesting party identity after verifying the first requesting party identity; A request generation and sending module, used for generating a second stream data acquisition request based on the requested party identity identifier when the current time matches the target time, and sending the second stream data acquisition request to the stream data storage device corresponding to the requested party identity identifier, wherein the target time is the pre-generated stream data acquisition time corresponding to the requested party identity identifier; A flow data receiving module, used for receiving the flow data corresponding to the identity identifier of the requested party returned by the flow data storage device after the identity identifier of the requested party is verified; The classification module is used to classify the transaction data according to the usage category of the transaction data and the channel information corresponding to the identity identifier of the requested party.

8. The device according to claim 7, characterized in that The second pipeline data request also carries a second requester identity; the pipeline data processing device further comprises a public key receiving module for receiving a public key returned by the pipeline data storage device, wherein the public key is generated by the pipeline data storage device after determining that the second requester identity has been verified; The flow data receiving module is also used to receive the encrypted flow data sent by the flow data storage device, the flow data corresponds to the identity of the requested party, the encrypted flow data is obtained by encrypting the flow data with a private key, and the public key and the private key are set correspondingly; the encrypted flow data is parsed and processed using the public key to obtain the decrypted flow data.

9. The device according to claim 7 or 8, characterized in that The classification module is specifically used for: Perform matching processing using the purpose category and the account identifier of the pre-generated account; if the purpose category matches the account name of the pre-generated account, determine whether the pre-generated account includes a sub-account; if the pre-generated account includes a sub-account, obtain the sub-account identifier corresponding to the sub-account; The transaction data is classified and processed according to the sub-account identifier and the channel information.

10. The device according to claim 9, characterized in that The classification module is further used to match the sub-account identifier of the sub-account with the channel information of the transaction data; if the sub-account identifier of the sub-account matches the channel information of the transaction data, the transaction data is added to the array directory corresponding to the sub-account; In the case that the subaccount identifier of the subaccount does not match the channel information of the transaction data, a new subaccount is generated using the channel information of the transaction data as the subaccount identifier, and the transaction data is added to the array directory corresponding to the new subaccount.

11. The device according to claim 9, characterized in that The pipeline data processing device also includes an account pre-generation module, which is used to receive project data, wherein the project data includes the purpose of each project; and generate the pre-generated account by using the purpose of each project as an account identifier.

12. The device according to claim 9, characterized in that The device further comprises an alarm generating module, which is used to generate an alarm message when the usage category does not match the account identifier of the pre-generated account.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images