CN111275461A

CN111275461A - Data processing method and device and computer readable storage medium

Info

Publication number: CN111275461A
Application number: CN202010074798.XA
Authority: CN
Inventors: 郑罗海
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-01-22
Filing date: 2020-01-22
Publication date: 2020-06-12

Abstract

The embodiment of the application discloses a data processing method, a data processing device and a computer readable storage medium. The method comprises the following steps: the method comprises the steps that a bill management node in a block chain network receives a first request from an enterprise node, distributes first certification information to the enterprise node according to attribute information of the enterprise node in the first request, sends the first certification information to the enterprise node, receives a second request from the enterprise node, and generates a first bill voucher according to the first bill information in the second request if the first certification information in the second request passes identity authentication. Therefore, the enterprise node requests the bill management node to generate the bill voucher through the certification information and the bill information, so that the process of generating the bill voucher is simplified, and the utilization rate of network resources is improved.

Description

Data processing method and device and computer readable storage medium

Technical Field

The present application relates to the field of computer networks, and in particular, to a data processing method and apparatus, and a computer-readable storage medium.

Background

Data processing is often involved in many application scenarios, such as: in the scenario of generating the bill voucher, an enterprise needs to log in a bill management system and submit bill information to generate the bill voucher. In practice, however, the time and place at which the business generates the ticket vouchers may vary. For example, the bill management system needs the fingerprint of the principal of enterprise a to log in, the departments of enterprise a in areas B and C need to generate bill vouchers for customers, the staff of the two departments need to send bill information to the principal of enterprise a, the principal of enterprise a logs in the bill management system again to generate bill vouchers through the bill information, and the bill management system needs to log in again at intervals. There is a disadvantage that the process of generating the ticket voucher is complicated.

Disclosure of Invention

The embodiment of the application discloses a data processing method, a data processing device and a computer readable storage medium, which can simplify the process of generating a bill voucher.

In a first aspect, the present application provides a data processing method, including:

receiving a first request from an enterprise node, the first request including attribute information of the enterprise node;

distributing first certification information to the enterprise nodes according to the attribute information of the enterprise nodes;

sending the first attestation information to the enterprise node;

receiving a second request from the enterprise node, the second request including the first attestation information and first ticket information;

and if the first certification information passes the identity authentication, generating a first bill voucher according to the first bill information.

In a second aspect, the present application provides a data processing apparatus comprising:

a transceiving unit, configured to receive a first request from an enterprise node, where the first request includes attribute information of the enterprise node;

the processing unit is used for distributing first certification information to the enterprise nodes according to the attribute information of the enterprise nodes;

the transceiving unit is further configured to send the first attestation information to the enterprise node, and receive a second request from the enterprise node, where the second request includes the first attestation information and first ticket information;

the processing unit is further configured to generate a first ticket voucher according to the first ticket information if the first certification information passes identity authentication.

In a third aspect, the present application provides a data processing apparatus comprising a processor, a memory and a communication interface, wherein the processor, the memory and the communication interface are connected to each other, wherein the memory is used for storing a computer program, and the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the method according to the first aspect.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon one or more instructions adapted to be loaded by a processor and to perform the method of the first aspect described above.

In the embodiment of the application, a bill management node in a block chain network receives a first request from an enterprise node, distributes first certification information to the enterprise node according to attribute information of the enterprise node in the first request, sends the first certification information to the enterprise node, receives a second request from the enterprise node, and generates a first bill voucher according to the first bill information in the second request if the first certification information in the second request passes identity verification. Therefore, the enterprise node requests the bill management node to generate the bill voucher through the certification information and the bill information, so that the process of generating the bill voucher is simplified, and the utilization rate of network resources is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a scene architecture diagram of a blockchain network according to an embodiment of the present invention;

fig. 2 is a flowchart of a data processing method according to an embodiment of the present application;

fig. 3 is a flowchart of another data processing method provided in the embodiment of the present application;

fig. 4 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of another data processing apparatus according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The embodiment of the application relates to a Block Chain and a Block Chain network, wherein the Block Chain (Block Chain) is a Chain data structure formed by combining data blocks in a sequential connection mode according to a time sequence, and a distributed account book which can ensure data to be untrustable and unforgeable in a cryptographic mode is provided. The blockchain is essentially a decentralized database, which is a string of data blocks associated by using cryptography, each data block contains information of a batch of network transactions, and the information is used for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.

The blockchain underlying platform may include processing modules for user management, basic services, and intelligent contracts. The user management module is responsible for identity information management of all blockchain participants, and comprises public and private key generation maintenance (account management), key management, user real identity and blockchain address corresponding relation maintenance (authority management) and the like, and under the authorization condition, the user management module supervises and audits the transaction condition of certain real identities and provides rule configuration (wind control audit) of risk control; the basic service module is deployed on all block chain node equipment and used for verifying the validity of the service request, recording the service request to storage after consensus on the valid request is completed, for a new service request, the basic service firstly performs interface adaptation analysis and authentication processing (interface adaptation), then encrypts service information (consensus management) through a consensus algorithm, transmits the service information to a shared account (network communication) completely and consistently after encryption, and performs recording and storage; the intelligent contract module is responsible for registering and issuing contracts, contract triggering and contract execution, developers can define contract logic through a certain programming language, issue the contract logic onto a block chain (contract registration), and call keys or other event triggering execution according to the logic of contract terms to complete the contract logic.

The blockchain network is a distributed application architecture for distributing tasks and workloads among peers, and is a networking or network form formed by peer-to-peer computing models in an application layer. Generally, a blockchain network includes a plurality of computers connected to each other, and these computers are also called node devices of the blockchain network. In a blockchain network environment, a plurality of computers connected with each other are in an equivalent position, each computer has the same function and is not divided into a master computer and a slave computer, and one computer can be used as a server to set shared resources for other computers in the network to use; the network as a whole generally does not rely on a dedicated centralized server, and there are no dedicated workstations. Each computer in the network can both act as a requester of network services and provide resources, services and content in response to requests from other computers.

Fig. 1 is a scene architecture diagram of a blockchain network according to an embodiment of the present disclosure. As shown in FIG. 1, the blockchain network includes an enterprise node 101, a ticket management node 102, a first proxy node 103, and a second proxy node 104. The form and number of each node in the blockchain network shown in fig. 1 are only examples, for example: the enterprise nodes 101 and the bill management nodes 102 may be multiple, and a third agent node, a fourth agent node, etc. may also exist in the blockchain network, and the number of each node is not limited in the present application.

The enterprise node 101 is a device used by an enterprise requesting to generate a ticket voucher, and may specifically be a client or a server, which is not limited in the embodiment of the present application. Wherein, the client can be any one of the following: a terminal, a separate Application, an API (Application Programming Interface), or an SDK (software development Kit). Among others, the terminal may include but is not limited to: smart phones (such as Android phones, iOS phones, etc.), tablet computers, portable personal computers, mobile internet devices (MID for short), and the like, which are not limited in the embodiments of the present application. The type of node device may include, but is not limited to, a full node, a Simple Payment Verification (SPV) node, or other node types in a blockchain network.

Ticket management node 102 is an organization or department that generates ticket vouchers for an enterprise, for example, a ticket management node is a device used by a tax bureau or business administration. The application may specifically be a client or a server, and the embodiment of the application is not limited. Wherein, the client can be any one of the following: a terminal, a separate Application, an API (Application programming interface), or an SDK (Software Development Kit). The type of node device may be a full node, i.e., the ticket management node 102 has all ticket vouchers stored therein.

The agent node is a device used by a third party instrument agent that provides services for the enterprise, such as WeChat or Payment treasures, and the like. The first agent node 103 and the second agent node 104 correspond to different third party instrument agents, for example, the first agent node 103 corresponds to WeChat and the second agent node 104 corresponds to Payment treasurer. The proxy node may specifically be a client or a server, and the embodiment of the present application is not limited. Wherein, the client can be any one of the following: a terminal, a separate Application, an API (Application Programming Interface), or an SDK (software development Kit). Among others, the terminal may include but is not limited to: smart phones (such as Android phones, iOS phones, etc.), tablet computers, portable personal computers, mobile internet devices (MID for short), and the like, which are not limited in the embodiments of the present application. The type of node device may include, but is not limited to, a full node, a Simple Payment Verification (SPV) node, or other node types in a blockchain network.

In one embodiment, the facilities of an organization or department that generate ticket vouchers for an enterprise may be deployed in a blockchain network as a whole with the ticket management node 102. In another embodiment, the ticket management node 102 is deployed as a core node in a blockchain network, and a device of an organization or department that generates a ticket voucher for an enterprise may be deployed as an SPV node in the blockchain network; alternatively, the facilities of an organization or department that generate ticket vouchers for an enterprise may be deployed outside of the blockchain network for data communications by connecting to nodes in the blockchain network. Similarly, the devices used by the enterprise may be deployed in the blockchain network as enterprise nodes; alternatively, devices used by an enterprise may be deployed outside of the blockchain network, which may be in data communication with node devices in the blockchain network.

In the block chain network shown in fig. 1, the data processing flow mainly includes that ① the enterprise principal logs in the ticket management system through the attribute information of the enterprise, in this embodiment, the attribute information of the enterprise includes an account password of the enterprise, biometric information of a corporate legal person (e.g., face information, fingerprint information, iris information, etc.), or other information for uniquely identifying the identity of the enterprise, and sends a first request to the ticket management node 102 in the block chain network through the enterprise node 101, the first request is used for obtaining first certification information (e.g., an electronic certificate containing a public key and a private key) that the enterprise node 101 can certify the identity of the enterprise when requesting to generate a ticket, the enterprise node 101 can digitally sign the sent information through the private key to certify the identity of the enterprise) after receiving the first request, the ticket management node 102 in the block chain network verifies the attribute information of the enterprise (e.g., confirms whether the enterprise node 101 has the generated ticket, etc.), if the first certification information is distributed to the enterprise node 101, and if the first certification information does not include the first certification information after receiving the first request, the first certificate information is distributed to the enterprise node 101 and the first certificate information does not include the first certification information (e.g., the first certificate is a bill management node 6335 after receiving the first certificate and the first certificate information is received by the first certificate after the first certificate and the second certificate request, the first certificate is a second certificate.

Therefore, after the enterprise node acquires the first certification information by the data processing method, when a bill voucher is generated by subsequent application, the first certification information and the first bill information are provided, so that the process of generating the bill voucher is simplified, and the utilization rate of network resources is improved.

A data processing method provided by the present application is described in detail below.

Referring to fig. 2, fig. 2 is a flowchart of a data processing method according to an embodiment of the present disclosure. The data processing method can be realized by the enterprise node 101 and the bill management node 102 shown in fig. 1 in an interactive way; as shown in fig. 2, the data processing method includes, but is not limited to, the following steps 201 to 205:

201. the ticket management node receives a first request from an enterprise node.

The first request is sent to the bill management node after a responsible person of the enterprise corresponding to the enterprise node logs in the bill management system through attribute information of the enterprise. The attribute information of the enterprise comprises account number and password of the enterprise, fingerprint information or iris information of an enterprise legal person and the like used for uniquely identifying the identity of the enterprise. The first request is for requesting allocation of first certification information capable of certifying an identity of itself. For example, the first certification information is an electronic certificate, which includes a public key, a private key and information related to the enterprise corresponding to the enterprise (e.g., an enterprise license number). The enterprise node can verify the identity of the self message sender by digitally signing the message sending information through a private key in the electronic certificate.

In one embodiment, the enterprise node has registered related information of the enterprise corresponding to the enterprise node in the bill management system, and the first request includes attribute information of the enterprise. In another embodiment, the enterprise node does not register the related information of the enterprise corresponding to the enterprise node in the bill management system, and the first request includes the attribute information of the enterprise and the registration information of the enterprise (such as a license number of the enterprise).

202. And the bill management node distributes first certification information for the enterprise nodes according to the attribute information of the enterprise nodes.

In one embodiment, the enterprise node has registered related information of a corresponding enterprise in the bill management system, and the bill management node determines related information of the corresponding enterprise (such as a license number of the enterprise, a certificate of the enterprise, etc.) according to the attribute information of the enterprise node, and confirms whether the enterprise is qualified for generating the bill voucher according to the related information of the enterprise. And if the enterprise is qualified for generating the bill voucher, distributing first certification information to the enterprise corresponding to the enterprise node. The first certification information includes an identifier of a business corresponding to the business node (e.g., a license number of the business), and symmetric key information allocated to the business. Specifically, the symmetric key information may be generated by a Data Encryption Standard (DES), an International Data Encryption Algorithm (IDEA), an RC5 block cipher algorithm, or the like. And if the enterprise does not have the qualification of generating the bill voucher, sending first prompt information to the enterprise node, wherein the first prompt information is used for indicating that the enterprise corresponding to the enterprise node does not have the qualification of generating the bill voucher.

In another embodiment, the enterprise node does not register the related information of the enterprise corresponding to the enterprise node in the bill management system, and the bill management node establishes the association relationship between the attribute information of the enterprise and the registration information of the enterprise. And the registration information of the enterprise is checked (for example, the business administration department inquires whether the enterprise is qualified to generate the bill voucher or not, or the certificate authority checks the registration information of the enterprise). And if the verification is passed (namely the enterprise is qualified to generate the bill voucher), allocating first certification information to the enterprise corresponding to the enterprise node. For the specific implementation, reference may be made to the implementation in the previous embodiment, which is not described herein again. And if the audit is not passed (namely the enterprise does not have the qualification of generating the bill voucher), sending second prompt information to the enterprise node, wherein the second prompt information is used for indicating that the enterprise corresponding to the enterprise node does not have the qualification of generating the bill voucher.

203. The ticket management node sends first attestation information to the enterprise node.

In one embodiment, the ticket management node sends the first attestation information assigned to the enterprise node. After the enterprise node receives the first certification information, when a bill voucher needs to be generated, a first message digest is generated from the first bill information by adopting a hash function, and then the first message digest is encrypted by adopting a private key in the first certification information to obtain a digital signature. And packaging the digital signature and the first bill information into a second request, and sending the second request to a bill management node. The first bill information includes information for generating bill vouchers, such as tax payment numbers of customers, bill amounts and the like.

204. The ticket management node receives a second request from the enterprise node.

In one embodiment, the ticket management node receives the second request from the enterprise node. And generating a second message digest from the first bill information by adopting a hash function, and then decrypting the digital signature by adopting a public key in the first certification information to obtain the first message digest. And determining whether the first message digest is consistent with the second message digest. If the first message digest is identical to the second message, it indicates that the enterprise node passes the authentication (i.e., the first certification information passes the authentication), and step 205 is executed. And if the first message abstract is inconsistent with the second message, the enterprise node fails to pass the identity authentication, and the bill management node sends third prompt information to the enterprise node, wherein the third prompt information is used for indicating that the identity authentication of the enterprise node fails.

205. And if the first certification information passes the identity authentication, the bill management node generates a bill voucher according to the first bill information.

Specifically, the bill management node generates a bill voucher according to the information such as the customer tax payment number and the bill amount in the first bill information. And packaging the bill voucher into a transaction to be stored in the block chain.

Optionally, the ticket management node sends the generated ticket voucher to the enterprise node.

For example, the person in charge of company a logs in the ticket management system (i.e. establishes a communication connection with the ticket management node) through a fingerprint at the computer of company a (i.e. the enterprise node). Then, the application 1 is sent to the ticket management node for applying for the certification information 1. After receiving the application certification information 1, the ticket management system confirms the identity of company a (i.e., verifies the attribute information of company a) and the related information, and then confirms whether company a is qualified to generate a ticket voucher through the related information of company a. After confirming that the company a is error-free and qualified to generate the ticket, the company a is assigned certification information 1 and the certification information 1 is transmitted to the company a. After receiving the certification information 1, the person in charge of company a notifies the certification information 1 to the workers in company a branches in areas B and C. When workers of company A in area B and area C need to generate bill vouchers, digital signature is carried out on bill information through the certification information 1, and the digital signature and the bill information are packaged into an application 2 to be sent to a bill management node. And after receiving the application 2, the bill management node verifies the digital signature through the certification information 1, and if the verification is passed, namely the application 2 is sent by company A, the bill management node generates a bill voucher according to the bill information. And storing the ticket voucher as a transaction in the blockchain.

In one embodiment, the first ticket information in the second request further includes address information of the customer node. The bill management node sends the bill voucher to the client node through the address information (such as the mailbox or the company address of the client) of the client node in the first bill information. The bill management node directly sends the bill voucher to the client node, and the enterprise node is not required to transfer, so that the client can obtain the bill voucher more conveniently.

In another embodiment, if the address information of the client node is not included in the first ticket information in the second request, the ticket management node sends the generated ticket voucher to the enterprise node, and the enterprise node sends the ticket voucher to the client node so that the client can obtain the ticket voucher.

Therefore, after the enterprise node acquires the first certification information, when a bill certificate is generated in a subsequent application, the enterprise node signs the first bill information through the first certification information, and the identity of the enterprise node is certified through the signature. The identity does not need to be verified by logging in to the ticket management system each time through the attribute information. The process of generating the bill voucher is simplified, and therefore the utilization rate of network resources is improved.

Referring to fig. 3, fig. 3 is a flowchart of another data processing method according to an embodiment of the present disclosure. The data processing method can be interactively realized by the enterprise node 101, the bill management node 102, the first proxy node 103 and the second proxy node 104 shown in fig. 1. Optionally, the application scenario further includes a client node; as shown in fig. 3, the data processing method includes, but is not limited to, the following steps 301 to 311:

301. the ticket management node receives a first request from an enterprise node.

The specific implementation manner of step 301 may refer to the specific implementation manner of step 201, and is not described herein again.

In one embodiment, the first request further includes attribute information of a first agent node associated with the enterprise node (i.e., enterprise-selected billing agent 1). The attribute information of the first proxy node is used to certify the first proxy node, e.g., a license number of the proxy node, etc. In another embodiment, the first request further includes attribute information of a first proxy node (i.e., enterprise-selected billing agent 1) and attribute information of a second proxy node (i.e., enterprise-selected billing agent 2) associated with the enterprise node. For example, agent 1 is a wechat platform and agent 2 is a payroll platform. It will be appreciated that the enterprise may select one or more proxy nodes, for example, a third Ticket proxy node, a fourth Ticket proxy node, etc. may also be included in the first request. In the embodiment of the present application, the number of proxy nodes is not limited.

In one embodiment, an enterprise corresponding to an enterprise node selects a proxy node when registering for the first time. In another embodiment, the enterprise corresponding to the enterprise node is not selected as the proxy node when registering for the first time, and when the proxy node is needed to provide service, the enterprise logs in the bill management system and selects the proxy node by submitting the first request. If an enterprise corresponding to an enterprise node selects a plurality of proxy nodes, the plurality of proxy nodes may be selected by one application or may be selected by several applications. For example, company a has selected proxy node 1 and proxy node 2 through application 1; company B selects proxy node 1 by application 1 and proxy node 2 by application 2.

302. The bill management node distributes first certification information to the enterprise nodes according to the attribute information of the enterprise nodes; and distributing second certification information for the first proxy node according to the attribute information of the first proxy node.

In one embodiment, the first request sent by the enterprise node further includes attribute information of the second proxy node, and the ticket management node assigns the third certification information to the second proxy node according to the attribute information of the second proxy node.

It will be appreciated that the distributed attestation information of the ticket management node for the different proxy nodes is different. Therefore, when the enterprise node cancels the certification information corresponding to a certain agent node, the enterprise node and other agent nodes are not affected.

303. The ticket management node sends the first attestation information and the second attestation information to the enterprise node.

The specific implementation manners of step 302 and step 303 may refer to the specific implementation manners of step 202 and step 203, and are not described herein again.

In one embodiment, if an enterprise corresponding to the enterprise node selects the first proxy node and the second proxy node in the same application, the ticket management node may package and send the first certification information, the second certification information, and the third certification information to the enterprise node. In another embodiment, if an enterprise corresponding to the enterprise node selects different agent nodes in different applications, the bill management node sends the certification information corresponding to the agent nodes to the enterprise node in a time division manner.

304. The enterprise node sends the second attestation information to the first proxy node.

In one embodiment, the enterprise node sends the second certification information to the first proxy node so that the first proxy node can provide the billing agency service for the enterprise node through the second certification information. Similarly, if the enterprise node further needs the second proxy node to provide service, the enterprise node sends third certification information to the second proxy node, so that the second proxy node can provide the ticket agency service for the enterprise node through the third certification information.

305. The ticket management node receives a third request from the first proxy node.

In one embodiment, the first proxy node receives the second attestation information sent from the enterprise node. If the first proxy node needs to provide the bill proxy service for the enterprise corresponding to the enterprise node, the first proxy node sends a third request to the bill management node, where the third request includes second certification information and second bill information, and the second bill information includes address information of the customer (e.g., an address of the customer node or a mailbox of the customer). For example, assuming that the certification information of the wechat platform is certification information 1, customer a purchases a product that company B is at the wechat platform, and submits ticket information 1 to ask the wechat platform for a ticket voucher. The ticket information 1 includes information such as a tax payment number and a ticket collecting address of the customer a. The WeChat platform packages the bill information 1 and the certification information 1 into a request 1 and sends the request 1 to a bill management node.

306. And the bill management node performs identity verification on the second certification information.

The specific implementation manners in step 305 and step 306 may refer to the specific implementation manners in step 203 and step 204, and are not described herein again.

It should be noted that, if the second certification information passes the identity authentication, the ticket management node may also directly perform the step of generating the second ticket credential according to the second ticket information in step 309.

307. And the bill management node sends prompt information to the enterprise node.

In one embodiment, after the bill management node verifies the second certification information (i.e., determines that the identity of the first proxy node is correct), a prompt message is sent to the enterprise node, where the prompt message is used to instruct the first proxy node to apply for generating the second bill credential on the name of the enterprise corresponding to the enterprise node. The prompt message includes second ticket information. And after receiving the prompt message, the enterprise node determines whether to allow the first proxy node to apply for generating a second bill voucher on the name of the enterprise corresponding to the enterprise node or not through the second bill information. And sending response information to the bill management node, wherein the response information is used for indicating whether the enterprise corresponding to the enterprise node allows the first proxy node to apply for generating the second bill voucher on the name of the enterprise corresponding to the enterprise node.

For example, the ticket management node sends a prompt message 1 to enterprise a, the prompt message 1 instructing the wechat platform to apply for generating the ticket voucher 1 on behalf of enterprise a. The prompt information 1 includes bill information 1, the bill information 1 includes commodity information, and the enterprise a checks whether the commodity information in the bill information 1 is produced by the enterprise a. And after checking, sending response information to the bill management node.

308. The ticket management node receives the response message from the enterprise node.

309. And if the response information indicates that the first proxy node is allowed to generate the bill voucher, the bill management node generates a second bill voucher according to the second bill information.

In one embodiment, if the response information allows the first proxy node to generate the ticket voucher, the ticket managing node generates a second ticket voucher according to the second ticket information. And packaging the second ticket voucher into a transaction for storage in the blockchain and continuing to step 310. Correspondingly, if the response information does not allow the first proxy node to generate the second bill voucher, the bill management node sends fourth prompt information to the first proxy node, and the fourth prompt information is used for prompting the enterprise node not to allow the first proxy node to generate the second bill voucher.

310. And the bill management node sends the second bill voucher to the client node according to the address information of the client node.

The specific implementation manner of step 310 may refer to the specific implementation manner of step 205, and is not described herein again.

311. The ticket management node sends fourth attestation information to the enterprise node.

In one embodiment, the second certification information assigned by the ticket management node to the first proxy node includes a timer (i.e., a validity time range). If the timer is overtime (namely the second certification information is not in the valid time range), the bill management node updates the second certification information to obtain fourth certification information. And send the fourth attestation information to the enterprise node. And if the enterprise node needs the first proxy node to continue providing the proxy service, sending the fourth certification information to the first proxy node. By updating the certification information of the agent node at regular time, the security can be realized, and the risk that the agent node maliciously generates the bill voucher under the name of the enterprise corresponding to the enterprise node can be reduced.

Optionally, if the enterprise corresponding to the enterprise node needs to cancel the first certification information of the enterprise or the certification information corresponding to the proxy node. And after logging in the bill management system through the attribute information of the enterprise, the responsible person of the enterprise sends a revocation request to the bill management node, wherein the revocation request comprises the attribute information of the enterprise or the agent node. After receiving the revocation request, the bill management node verifies the identity of the enterprise node, and the specific verification mode is not limited herein. After the identity authentication is passed, the corresponding certification information is cancelled (the certification information is invalidated) according to the revocation request.

It should be noted that step 311 may be executed in parallel in the process from step 304 to step 310.

Therefore, after the first agent node acquires the second certification information, when a bill certificate is generated in a subsequent application, the second certification information is used for signing the second bill information, and the identity of the agent is certified through the signature. The ticket voucher need not be generated by the enterprise node authorization each time. The process of generating the bill voucher is further simplified, and therefore the utilization rate of network resources is improved.

While the method of the embodiments of the present application has been described in detail above, to facilitate better implementation of the above-described aspects of the embodiments of the present application, the apparatus of the embodiments of the present application is provided below accordingly.

Referring to fig. 4, fig. 4 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application, where the data processing apparatus may be mounted on a bill management node in the foregoing method embodiment. The data processing apparatus shown in fig. 4 may be used to perform some or all of the functions in the method embodiments described above with respect to fig. 2 and 3. Wherein, the detailed description of each unit is as follows:

a transceiving unit 401, configured to receive a first request from an enterprise node, where the first request includes attribute information of the enterprise node;

a processing unit 402, configured to allocate first certification information to the enterprise node according to the attribute information of the enterprise node;

the transceiver 401 is further configured to send the first attestation information to the enterprise node, and receive a second request from the enterprise node, where the second request includes the first attestation information and the first ticket information;

the processing unit 402 is further configured to generate a first ticket voucher according to the first ticket information if the first certification information passes the identity authentication.

In one embodiment, the first request further includes attribute information of a first proxy node associated with the enterprise node;

the processing unit 402 is further configured to:

distributing second certification information to the enterprise nodes according to the attribute information of the enterprise nodes and the attribute information of the first proxy nodes;

sending the second attestation information to the enterprise node.

In an embodiment, the processing unit 402 is further configured to:

receiving a third request from the first proxy node, the third request including the second attestation information and second ticket information;

and if the second certification information passes the identity authentication, generating a second bill voucher according to the second bill information.

In an embodiment, the processing unit 402 is further configured to, if the second certification information passes the identity authentication, generate a second ticket credential according to the second ticket information, and specifically configured to:

if the second certification information passes the identity authentication, sending prompt information to the enterprise node, wherein the prompt information is used for prompting the first proxy node to request to generate a bill voucher;

receiving response information from the enterprise node;

and if the response information indicates that the first proxy node is allowed to generate the bill voucher, generating a second bill voucher according to the second bill information.

In one embodiment, the first request further includes attribute information of a second proxy node associated with the enterprise node;

the processing unit 402 is further configured to:

distributing third certification information to the enterprise node according to the attribute information of the enterprise node and the attribute information of the second proxy node;

sending the third attestation information to the enterprise node.

In an embodiment, the processing unit 402 is further configured to:

if the timer of the second certification information is overtime, updating the second certification information to obtain fourth certification information;

sending the fourth attestation information to the enterprise node.

In one embodiment, the first ticket information further includes address information of the customer node;

the processing unit 402 is further configured to:

and sending the first bill voucher to the client node according to the address information of the client node.

According to an embodiment of the present application, some steps involved in the data processing methods shown in fig. 2 and 3 may be performed by respective units in the data processing apparatus shown in fig. 4. For example, step 201, step 203 and step 204 shown in fig. 2 may be performed by the transceiving unit 401 shown in fig. 4, and step 202 and step 205 may be performed by the processing unit 402 shown in fig. 4. Steps 301, 303, 305, 307, 308, 310 and 311 shown in fig. 3 may be performed by the transceiving unit 401 shown in fig. 4, and steps 302, 306 and 309 may be performed by the processing unit 402 shown in fig. 4. The units in the data processing apparatus shown in fig. 4 may be respectively or entirely combined into one or several other units to form one or several other units, or some unit(s) may be further split into multiple functionally smaller units to form one or several other units, which may achieve the same operation without affecting the achievement of the technical effect of the embodiments of the present application. The units are divided based on logic functions, and in practical application, the functions of one unit can be realized by a plurality of units, or the functions of a plurality of units can be realized by one unit. In other embodiments of the present application, the data processing apparatus may also include other units, and in practical applications, the functions may also be implemented by being assisted by other units, and may be implemented by cooperation of a plurality of units.

According to another embodiment of the present application, the data processing apparatus as shown in fig. 4 may be constructed by running a computer program (including program codes) capable of executing the steps involved in the respective methods as shown in fig. 2 and 3 on a general-purpose computing apparatus such as a computer including a processing element such as a Central Processing Unit (CPU), a random access storage medium (RAM), a read-only storage medium (ROM), and a storage element, and implementing the data processing method of the embodiment of the present application. The computer program may be recorded on a computer-readable recording medium, for example, and loaded and executed in the above-described computing apparatus via the computer-readable recording medium.

Based on the same inventive concept, the principle and the advantageous effect of the data processing apparatus provided in the embodiment of the present application for solving the problem are similar to the principle and the advantageous effect of the data processing apparatus in the embodiment of the method of the present application for solving the problem, and for brevity, the principle and the advantageous effect of the implementation of the method may be referred to, and are not described herein again.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a data processing apparatus according to an exemplary embodiment of the present application, where the data processing apparatus includes at least a processor 501, a communication interface 502, and a memory 503. The processor 501, the communication interface 502, and the memory 503 may be connected by a bus or other means, and the embodiment of the present application is exemplified by being connected by a bus. The processor 501 (or Central Processing Unit (CPU)) is a computing core and a control core of the terminal, and can analyze various instructions in the terminal and process various data of the terminal, for example: the CPU can be used for analyzing a power-on and power-off instruction sent to the terminal by a user and controlling the terminal to carry out power-on and power-off operation; the following steps are repeated: the CPU may transmit various types of interactive data between the internal structures of the terminal, and so on. The communication interface 502 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI, mobile communication interface, etc.), and may be controlled by the processor 501 for transceiving data; the communication interface 502 can also be used for transmission and interaction of data inside the terminal. A Memory 503(Memory) is a Memory device in the terminal for storing programs and data. It is understood that the memory 503 herein may include both the built-in memory of the terminal and, of course, the expansion memory supported by the terminal. The memory 503 provides storage space that stores the operating system of the terminal, which may include, but is not limited to: android system, iOS system, Windows Phone system, etc., which are not limited in this application.

In the embodiment of the present application, the processor 501 executes the executable program code in the memory 503 to perform the following operations:

receiving a first request from an enterprise node over a communication interface 502, the first request including attribute information for the enterprise node;

sending the first attestation information to the enterprise node over a communication interface 502; receiving a second request from the enterprise node, the second request including the first attestation information and first ticket information;

As an optional implementation, the first request further includes attribute information of a first proxy node associated with the enterprise node;

the processor 501, by executing the executable program code in the memory 503, also performs the following operations:

sending the second attestation information to the enterprise node.

As an alternative embodiment, the processor 501, by executing the executable program code in the memory 503, further performs the following operations:

receiving a third request from the first proxy node over a communication interface 502, the third request including the second attestation information and second ticket information;

As an optional implementation manner, if the second certification information passes the identity verification, the specific implementation manner of the processor 501 generating the second ticket credential according to the second ticket information is as follows:

if the second certification information passes the identity authentication, sending prompt information to the enterprise node through a communication interface 502, wherein the prompt information is used for prompting the first proxy node to request to generate a bill voucher; receiving response information from the enterprise node;

As an optional implementation, the first request further includes attribute information of a second proxy node associated with the enterprise node;

the third attestation information is sent to the enterprise node via the communication interface 502.

the fourth attestation information is sent to the enterprise node over a communication interface 502.

As an optional implementation, the first ticket information further includes address information of the customer node;

processor 501 also performs the following operations:

the first ticket voucher is sent to the customer node via the communication interface 502 based on the address information of the customer node.

The embodiment of the present application further provides a computer-readable storage medium, where one or more instructions are stored in the computer-readable storage medium, and the one or more instructions are adapted to be loaded by a processor and to execute the data processing method described in the foregoing method embodiment.

Embodiments of the present application further provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the data processing method described in the above method embodiments.

It should be noted that, for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the order of acts described, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.

The modules in the device can be merged, divided and deleted according to actual needs.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, which may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method of data processing, the method comprising:

sending the first attestation information to the enterprise node;

2. The method of claim 1, wherein the first request further includes attribute information of a first proxy node associated with the enterprise node;

the method further comprises the following steps:

sending the second attestation information to the enterprise node.

3. The method of claim 2, further comprising:

4. The method of claim 3, wherein generating a second ticket voucher based on the second ticket information if the second attestation information passes authentication comprises:

receiving response information from the enterprise node;

5. The method of claim 2, wherein the first request further includes attribute information of a second proxy node associated with the enterprise node;

the method further comprises the following steps:

sending the third attestation information to the enterprise node.

6. The method of claim 2, further comprising:

sending the fourth attestation information to the enterprise node.

7. The method of claim 1, wherein the first ticket information further includes address information of a customer node;

the method further comprises the following steps:

8. A data processing apparatus, comprising

9. A data processing apparatus comprising a processor, a memory and a communication interface, the processor, the memory and the communication interface being interconnected, wherein the memory is for storing a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any of claims 1 to 7.

10. A computer-readable storage medium having stored thereon one or more instructions adapted to be loaded by a processor and to perform the method of any of claims 1 to 7.