Authorization verification management method and system based on customer privacy protection

Abstract

The present application provides an authorization verification management method and system based on customer privacy protection, the method comprising: the data query end obtains the business authorization code corresponding to the current data query request; the data query end sends the customer number, data query transaction code and business authorization code corresponding to the current data query request to the data management end; the data management end determines whether the current data query request meets the preset query conditions based on the customer number, data query transaction code and business authorization code; when the current data query request meets the preset query conditions, the data management end obtains the query result based on the data query transaction code, and returns the query result to the data query end. The above method only provides data query services for data query requests that meet the query conditions, thereby effectively controlling data access behavior, reducing the risk of abuse of external data, and effectively protecting customer privacy.

Description

Technical Field

[0001] The present application relates to the technical field of data security, and specifically, to an authorization verification management method and system based on customer privacy protection. Background Art

[0002] As citizens' awareness of privacy protection continues to grow, relevant national laws and regulations are gradually improved, and regulatory requirements are becoming increasingly stringent, the need to prevent data abuse risks is becoming increasingly urgent. Data, as an important strategic asset, drives the rapid development of online business. However, with the high concentration and widespread use of data, data risks are also increasing. It is urgent to regulate data use, protect customer privacy, and ensure legal acquisition and authorization of customer privacy data through the construction of relevant information systems. Summary of the invention

[0003] In view of the shortcomings of the existing methods, this application proposes an authorization verification management method and system based on customer privacy protection to solve at least one of the above technical problems.

[0004] In the first aspect, an embodiment of the present application provides an authorization verification management method based on customer privacy protection, including: a data query end obtains a business authorization code corresponding to a current data query request; the data query end sends a customer number, a data query transaction code and a business authorization code corresponding to the current data query request to a data management end; the data management end determines whether the current data query request meets a preset query condition based on the customer number, the data query transaction code and the business authorization code; when the current data query request meets the preset query condition, the data management end obtains a query result based on the data query transaction code, and returns the query result to the data query end.

[0005] In one embodiment of the present application, the data query end obtains the service authorization code corresponding to the current data query request, including: the data query end determines whether the current data query request is a new data query request; when the current data query request is not a new data query request, the data query end queries a pre-stored historical data query request that is the same as the current data query request, and uses the service authorization code corresponding to the historical data query request as the service authorization code corresponding to the current data query request;

[0006] When the current data query request is a new data query request, the data query end sends the personal privacy usage scenario number, the data query end number and the data query transaction code corresponding to the current data query request to the data management end; the data management end determines the business authorization code based on the personal privacy usage scenario number, the data query end number and the data query transaction code; the data management end returns the determined business authorization code to the data query end.

[0007] In one embodiment of the present application, the data query end determines whether the current data query request is a new data query request, including: the data query end locally queries whether there is a business authorization code that matches the personal privacy usage scenario number and the data query transaction code corresponding to the current data query request; when the query result is yes, it is determined that the current data query request is not a new data query request; when the query result is no, it is determined that the current data query request is a new data query request.

[0008] In one embodiment of the present application, the data management end determines whether the current data query request meets the preset query conditions based on the customer number, the data query transaction code and the business authorization code, including: when the current data query request has a business authorization code and it is determined based on the data query transaction code that the transaction involved in the current data query request is a non-customer privacy transaction, it is determined that the current data query request meets the preset query conditions.

[0009] In one embodiment of the present application, the authorization verification management method based on customer privacy protection further includes: when the current data query request does not have a service authorization code, rejecting the current data query request.

[0010] In one embodiment of the present application, the data management end determines whether the current data query request meets the preset query conditions based on the customer number, the data query transaction code and the business authorization code, including: the current data query request has a business authorization code, determining that the transaction involved in the current data query request is a customer privacy transaction based on the data query transaction code, and determining that the current data query request meets the preset query conditions when it is determined that the current data query request has customer authorization.

[0011] In one embodiment of the present application, determining that the current data query request has customer authorization includes: the data management end sends a customer authorization verification request to the authorization system server; the authorization system server associates the first business scenario number corresponding to the current data query request based on the business authorization code; the authorization system server queries the customer contract record based on the customer number; the authorization system server associates the customer-authorized scenario number, data query transaction code, data query terminal number and authorization validity period based on the agreement number associated with the customer contract record; the authorization system server determines that the first business scenario number, data query transaction code and data query terminal number corresponding to the current data query request match the customer-authorized scenario number, data query transaction code and data query terminal number respectively, and when the time of the current data query request does not exceed the authorization validity period, it is determined that the customer authorization verification is successful, and a notification of successful customer authorization verification is sent to the data management end; the data management determines that the current data query request has customer authorization based on the notification of successful customer authorization verification.

[0012] In one embodiment of the present application, determining that the transaction involved in the current data query request is a non-customer privacy transaction based on the data query transaction code includes: the data management end matches the data query transaction code with a built-in customer query privacy transaction code list; when the data query transaction code does not exist in the customer query privacy transaction code list, determining that the transaction involved in the current data query request is a non-customer privacy transaction.

[0013] In one embodiment of the present application, the authorization verification management method based on customer privacy protection also includes: if the current data query request does not have a business authorization code, the current data query request is rejected; and if the transaction involved in the current data query request is a customer privacy transaction, the current data query request is rejected if the current data query request does not have customer authorization.

[0014] In a second aspect, the embodiment of the present application provides an authorization verification management system based on customer privacy protection, including: a data query end and a data management end;

[0015] The data query end is used to: obtain the business authorization code corresponding to the current data query request;

[0016] The data query end is used to: send the customer number, data query transaction code and business authorization code corresponding to the current data query request to the data management end; based on the customer number, data query transaction code and business authorization code, determine whether the current data query request meets the preset query conditions; when the current data query request meets the preset query conditions, the data query transaction code is used to obtain the query results and return the query results to the data query end.

[0017] In a third aspect, an embodiment of the present application provides a data query end, the data query end includes a memory and a processor, and the processor is communicatively connected to the memory;

[0018] The memory stores a computer program, and when the computer program is executed by the processor, the steps performed by the data query end in the above-mentioned authorization verification management method based on customer privacy protection are implemented.

[0019] In a fourth aspect, an embodiment of the present application provides a data management terminal, the data management terminal includes a memory and a processor, and the processor is communicatively connected to the memory;

[0020] The memory stores a computer program, and when the computer program is executed by the processor, the steps performed by the data management end in the above-mentioned authorization verification management method based on customer privacy protection are implemented.

[0021] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps performed by the data query end in the above-mentioned authorization verification management method based on customer privacy protection are implemented.

[0022] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps performed by the data management end in the above-mentioned authorization verification management method based on customer privacy protection are implemented.

[0023] The technical solution provided in the embodiments of the present application has at least the following beneficial effects:

[0024] The authorization verification management method and system based on customer privacy protection provided in the present application can pre-determine data query requests that meet the query conditions based on the customer number, data query transaction code and the business authorization code, and only provide data query services for data query requests that meet the query conditions, thereby effectively managing data access behavior and reducing the risk of abuse of external data, thereby effectively protecting customer privacy.

[0025] Additional aspects and advantages of the present application will be partially given in the following description, which will become apparent from the following description, or will be understood through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0027] Figure 1 This is an architecture diagram of an authorization verification management system based on customer privacy protection provided by an embodiment of the present application;

[0028] Figure 2 A flowchart of an authorization verification management method based on customer privacy protection according to an embodiment of the present application;

[0029] Figure 3 A schematic diagram of a module of a data query terminal provided in an embodiment of the present application;

[0030] Figure 4 A schematic diagram of the modules of the data management terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] The present application is described in detail below, and examples of embodiments of the present application are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar components or components with the same or similar functions. In addition, if the detailed description of the known technology is unnecessary for the features of the present application shown, it will be omitted. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.

[0032] It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those generally understood by those skilled in the art to which this application belongs. It should also be understood that terms such as those defined in general dictionaries should be understood to have meanings consistent with those in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless specifically defined as here.

[0033] It will be understood by those skilled in the art that, unless expressly stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we refer to an element as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0034] First, the terms involved in this application are defined and explained.

[0035] Customer privacy information: Before using customer privacy data in various industries, a privacy agreement authorization contract document must be signed with the customer to clearly define the purpose of using the customer privacy data, business scenarios, usage content, how to collect and store, and other related content.

[0036] Customer authorization: When a customer signs a privacy agreement, he or she authorizes a product to use his or her personal privacy data in a certain scenario.

[0037] Business authorization: The data management department's approval of whether a system can use a certain data item.

[0038] Figure 1 This is an architecture diagram of an authorization verification management system based on customer privacy protection provided by an embodiment of the present application. The system includes the following devices:

[0039] Product signing client, used to collect basic customer information.

[0040] The product signing service is used to review and approve customer signing qualifications and transmit customer signing records to the authorization management service.

[0041] The data query end is used to query different personal privacy transactions of different customers based on different usage scenarios.

[0042] The data management end is used to publish data query transactions, provide data query services to the privacy query end, and address and query data according to the corresponding data provider API interface of the transaction background. According to regulatory requirements, personal privacy data keywords are extracted, the data query transaction data dictionary is traversed, and a list of personal privacy transaction codes is generated.

[0043] The authorization management client is used to collect customer privacy agreement information, product and system information corresponding to the agreement, customer information, customer privacy data item information, and business authorization information.

[0044] The authorization management server is used to manage customer privacy agreement information, product and system information corresponding to the agreement, customer information, customer privacy data item information, business authorization information, and customer authorization records. The authorization management server can also provide customer authorization verification services to the data management side and provide contract record addition services to the product contract service side.

[0045] The following describes the relevant process of maintaining basic information for authorization management using the authorization verification management system based on customer privacy protection:

[0046] Product and system information maintenance: The authorization management client collects system information (system number, system name, system maintenance department, etc.) and product information (product number, product name, product corresponding business department information), and transmits it to the authorization management server. The authorization management server maintains product and system information based on the content collected by the client, and associates the product number and its underlying system number based on the dependency relationship between product application and system environment.

[0047] Maintenance of personal privacy data item information: The authorization management client collects privacy data number, data item name (such as provident fund, social security, individual tax data), and online transaction identification. When the online mark is "yes", the data item is judged to be an online query transaction, and the online transaction code (such as A0123BM01), online service name (such as provident fund pre-loan details acquisition transaction, provident fund post-loan data push transaction), and external data identification (when the external data identification is "yes", it is an external network data real-time query transaction; when it is "no", it is an intranet data real-time query transaction); when the online mark is "no", the data item is judged to be a batch query transaction, and the intranet data source number, data resource Chinese name, and data resource English name are collected. The authorization management server maintains the data item information based on the content collected by the client, and its association with online query transactions and batch transactions.

[0048] Maintenance of personal privacy data usage scenarios: The authorization management client collects the name of the personal privacy data usage scenario (such as new card application, installment repayment, card upgrade) and sends it to the authorization management server. The authorization management server maintains the personal privacy data usage scenario information and generates a scenario number.

[0049] Product License Agreement: Create a new agreement or register an agreement.

[0050] The following describes the relevant process of implementing a new agreement in the authorization verification management system based on customer privacy protection. This process generates authorization terms and a unified agreement number for scenarios where there is no agreement, and includes:

[0051] Select an agreement template and generate product terms: The authorization management client collects the preset template number and product number; the authorization management server adds the corresponding product terms to the agreement framework pre-stored in the agreement template according to the preset rules.

[0052] Generate authorization terms: The authorization management client collects the personal privacy data item number, product number, and usage scenario number; the authorization management server converts the structured authorization information into authorization terms based on the preset corpus, and adds the authorization terms to the agreement generated in step 1. Combine the new product authorization agreement.

[0053] The following describes the relevant process of implementing protocol registration in the authorization verification management system based on customer privacy protection. This process splits the authorization terms for the existing protocol scenario and generates a unified protocol number. The process specifically includes:

[0054] The authorization management client uploads the unstructured / semi-structured attachments of the agreement text, the product number, the legal review document number, and the structured information of the effective time of the agreement to the authorization management server.

[0055] The server uses OCR recognition / text recognition algorithm to parse unstructured / semi-structured text information based on the uploaded agreement text, extracts the authorization terms, and identifies the personal privacy data item number, product number, and scenario number to generate structured authorization information (the source of the number can be found in the above information maintenance unit).

[0056] The following introduces the relevant process of implementing agreement approval in the authorization verification management system based on customer privacy protection, including: after adding / registering the agreement, the authorization management server approves the agreement according to expert rules, generates a unified agreement number, and returns it to the authorization management client.

[0057] The following describes the relevant process of implementing protocol maintenance in the authorization verification management system based on customer privacy protection, including: the authorization management server regularly maintains the protocol number, protocol version information, structured authorization terms associated with the protocol, protocol-related products, and product-related component information;

[0058] The following describes the relevant process of adding / canceling contract records in the authorization verification management system based on customer privacy protection. The process includes:

[0059] The contract signing client uploads the contract: the contract signing client sends the basic information of the customer handling the product (customer number, customer name, customer ID type, customer ID number, customer mobile phone number), the product agreement number signed by the customer, the contract signing time and the agreement period to the contract signing server, and the operation type is (contract signing / cancellation).

[0060] Approval and signing of the contract by the contract signing service: The contract signing service system scores the customer's qualification information according to the preset approval conditions (such as customer reputation, customer portrait, etc.). If the customer meets the product handling conditions, the contract signing information will be sent to the authorization verification management system server. The authorization server queries the product number associated with the agreement number. Based on the product number, the associated system number is queried. If the system number associated with the product is consistent with the contract signing service number, the contract signing record is judged to be credible and the contract signing information is stored in the database.

[0061] The above authorization verification management system based on customer privacy protection can centrally manage the privacy agreements signed with customers, as well as the corresponding privacy data items, products, business scenarios, etc. It provides online interfaces for contract upload, contract cancellation, and contract verification, cooperates with regulators to issue relevant risk review information, assists businesses in discovering and rectifying customer authorization gaps, and ensures the compliance and legality of the use of customer privacy data.

[0062] Figure 2 : is a flowchart of an authorization verification management method based on customer privacy protection provided by an embodiment of the present application, the method comprising the following steps:

[0063] S110: The data query end obtains the service authorization code corresponding to the current data query request.

[0064] In one embodiment of the present application, the data query end obtains the business authorization code corresponding to the current data query request, including: the data query end determines whether the current data query request is a new data query request; when the current data query request is not a new data query request, the data query end queries the pre-stored historical data query request that is the same as the current data query request, and uses the business authorization code corresponding to the historical data query request as the business authorization code corresponding to the current data query request.

[0065] When the current data query request is a new data query request, the data query end sends the personal privacy usage scenario number, the data query end number and the data query transaction code corresponding to the current data query request to the data management end; the data management end determines the business authorization code based on the personal privacy usage scenario number, the data query end number and the data query transaction code; the data management end returns the determined business authorization code to the data query end.

[0066] In one embodiment of the present application, the data query end determines whether the current data query request is a new data query request, including: the data query end locally queries whether there is a business authorization code that matches the personal privacy usage scenario number and the data query transaction code corresponding to the current data query request; when the query result is yes, it is determined that the current data query request is not a new data query request; when the query result is no, it is determined that the current data query request is a new data query request.

[0067] S120: The data query end sends the customer number, data query transaction code and business authorization code corresponding to the current data query request to the data management end.

[0068] S130: The data management terminal determines whether the current data query request meets the preset query conditions based on the customer number, the data query transaction code and the business authorization code.

[0069] In one embodiment of the present application, the data management end determines whether the current data query request meets the preset query conditions based on the customer number, the data query transaction code and the business authorization code, including: when the current data query request has a business authorization code and it is determined based on the data query transaction code that the transaction involved in the current data query request is a non-customer privacy transaction, it is determined that the current data query request meets the preset query conditions.

[0070] In one embodiment of the present application, the authorization verification management method based on customer privacy protection further includes: when the current data query request does not have a service authorization code, rejecting the current data query request.

[0071] In one embodiment of the present application, the data management end determines whether the current data query request meets the preset query conditions based on the customer number, the data query transaction code and the business authorization code, including: the current data query request has a business authorization code, determining that the transaction involved in the current data query request is a customer privacy transaction based on the data query transaction code, and determining that the current data query request meets the preset query conditions when it is determined that the current data query request has customer authorization.

[0072] In one embodiment of the present application, the authorization verification management method based on customer privacy protection also includes: if the current data query request does not have a business authorization code, the current data query request is rejected; and if the transaction involved in the current data query request is a customer privacy transaction, the current data query request is rejected if the current data query request does not have customer authorization.

[0073] S140: When the current data query request meets the preset query conditions, the data management end obtains the query result based on the data query transaction code and returns the query result to the data query end.

[0074] In one embodiment of the present application, when the data management end determines that the current data query request meets the preset query conditions, the data management end can call a third-party data query interface and send a data query transaction code, perform data query based on the data query transaction code, and then obtain the data query result. For example, the data management end can call a third-party API interface to address and query data.

[0075] The authorization verification management method based on customer privacy protection provided in the present application can pre-judge data query requests that meet the query conditions based on the customer number, data query transaction code and the business authorization code, and only provide data query services for data query requests that meet the query conditions, thereby effectively managing data access behavior and reducing the risk of abuse of external data, thereby effectively protecting customer privacy.

[0076] The following describes the specific steps of step S130 in which the data management end determines whether the current data query request meets the preset query condition.

[0077] Step a: The data management terminal determines whether the current data query request has a service authorization code. If the service authorization code is available, continue to step b; if the service authorization code is not available, reject the current data query request.

[0078] Step b: The data management terminal determines the type of transaction involved in the current data query request based on the data query transaction code. When the transaction involved in the current data query request is a non-customer privacy transaction, it is determined that the current data query request meets the preset query conditions; when the transaction involved in the current data query request is a customer privacy transaction, continue to step c.

[0079] Step c: The data management end determines whether the current data query request has customer authorization. If the current data query request has customer authorization, it determines that the current data query request meets the preset query conditions; if the current data query request does not have customer authorization, it rejects the current data query request.

[0080] In one embodiment of the present application, determining that the current data query request has customer authorization includes: the data management end sends a customer authorization verification request to the authorization system server; the authorization system server associates the first business scenario number corresponding to the current data query request based on the business authorization code; the authorization system server queries the customer contract record based on the customer number; the authorization system server associates the customer-authorized scenario number, data query transaction code, data query terminal number and authorization validity period based on the agreement number associated with the customer contract record; the authorization system server determines that the first business scenario number, data query transaction code and data query terminal number corresponding to the current data query request match the customer-authorized scenario number, data query transaction code and data query terminal number respectively, and when the time of the current data query request does not exceed the authorization validity period, it is determined that the customer authorization verification is successful, and a notification of successful customer authorization verification is sent to the data management end; the data management determines that the current data query request has customer authorization based on the notification of successful customer authorization verification.

[0081] It can be understood that when the authorization system server determines that the first business scenario number, data query transaction code and data query terminal number corresponding to the current data query request do not match the scenario number, data query transaction code and data query terminal number authorized by the customer, or the time of the current data query request exceeds the authorization validity period, it determines that the customer authorization verification has failed, and sends a notification of the customer authorization verification failure to the data management end. Based on the notification of the customer authorization verification failure, the data management determines that the current data query request does not have the customer authorization.

[0082] In one embodiment of the present application, determining that the transaction involved in the current data query request is a non-customer privacy transaction based on the data query transaction code includes: the data management end matches the data query transaction code with a built-in customer query privacy transaction code list; when the data query transaction code does not exist in the customer query privacy transaction code list, determining that the transaction involved in the current data query request is a non-customer privacy transaction.

[0083] It can be understood that the data management end can match the data query transaction code with the built-in customer query privacy transaction code list. When the data query transaction code exists in the customer query privacy transaction code list, it is determined that the transaction involved in the current data query request is a customer privacy transaction.

[0084] Based on the same inventive concept, an embodiment of the present application provides an authorization verification management system based on customer privacy protection, which includes a data query end and a data management end.

[0085] The data query end is used to obtain the business authorization code corresponding to the current data query request.

[0086] The data query end is used to: send the customer number, data query transaction code and business authorization code corresponding to the current data query request to the data management end; based on the customer number, data query transaction code and business authorization code, determine whether the current data query request meets the preset query conditions; when the current data query request meets the preset query conditions, the data query transaction code is used to obtain the query results and return the query results to the data query end.

[0087] In one embodiment of the present application, the data query end determines whether the current data query request is a new data query request; when the current data query request is not a new data query request, the data query end queries a pre-stored historical data query request that is the same as the current data query request, and uses the service authorization code corresponding to the historical data query request as the service authorization code corresponding to the current data query request;

[0088] When the current data query request is a new data query request, the data query end sends the personal privacy usage scenario number, the data query end number and the data query transaction code corresponding to the current data query request to the data management end; the data management end determines the business authorization code based on the personal privacy usage scenario number, the data query end number and the data query transaction code; the data management end returns the determined business authorization code to the data query end.

[0089] In one embodiment of the present application, the data query end locally queries whether there is a business authorization code that matches the personal privacy usage scenario number and the data query transaction code corresponding to the current data query request; when the query result is yes, it is determined that the current data query request is not a new data query request; when the query result is no, it is determined that the current data query request is a new data query request.

[0090] In one embodiment of the present application, when the current data query request has a business authorization code and the transaction involved in the current data query request is determined to be a non-customer privacy transaction based on the data query transaction code, the data management end determines that the current data query request meets the preset query conditions.

[0091] In one embodiment of the present application, when the current data query request does not have a service authorization code, the data management end rejects the current data query request.

[0092] In one embodiment of the present application, the data management end determines whether the current data query request meets the preset query conditions based on the customer number, the data query transaction code and the business authorization code, including: the current data query request has a business authorization code, determining that the transaction involved in the current data query request is a customer privacy transaction based on the data query transaction code, and determining that the current data query request meets the preset query conditions when it is determined that the current data query request has customer authorization.

[0093] In one embodiment of the present application, the data management end sends a customer authorization verification request to the authorization system server; the authorization system server associates the first business scenario number corresponding to the current data query request based on the business authorization code; the authorization system server queries the customer contract record based on the customer number; the authorization system server associates the customer-authorized scenario number, data query transaction code, data query terminal number and authorization validity period based on the agreement number in the customer contract record; the authorization system server determines that the first business scenario number, data query transaction code and data query terminal number corresponding to the current data query request match the customer-authorized scenario number, data query transaction code and data query terminal number respectively, and when the time of the current data query request does not exceed the authorization validity period, it is determined that the customer authorization verification is successful, and a notification of successful customer authorization verification is sent to the data management end; the data management determines that the current data query request has customer authorization based on the notification of successful customer authorization verification.

[0094] In one embodiment of the present application, the data management end matches the data query transaction code with the built-in customer query privacy transaction code list. When the data query transaction code does not exist in the customer query privacy transaction code list, it is determined that the transaction involved in the current data query request is a non-customer privacy transaction.

[0095] In one embodiment of the present application, the current data query request does not have a business authorization code, and the data management end rejects the current data query request; and when the transaction involved in the current data query request is a customer privacy transaction, the current data query request does not have customer authorization, and the current data query request is rejected.

[0096] Compared with the prior art, the authorization verification management system based on customer privacy protection provided by the present application can pre-judge data query requests that meet the query conditions based on the customer number, data query transaction code and the business authorization code, and only provide data query services for data query requests that meet the query conditions, thereby effectively controlling data access behavior and reducing the risk of abuse of external data, thereby effectively protecting customer privacy.

[0097] The authorization verification management system based on customer privacy protection provided in the embodiment of the present application has the same inventive concept as the embodiments described above. The contents not shown in detail in the authorization verification management system based on customer privacy protection can be referred to the embodiments described above and will not be repeated here.

[0098] Based on the same inventive concept, the embodiment of the present application also provides a data query terminal, such as Figure 3 As shown, the data query end includes a memory 103 and a processor 101 , and the processor 101 is communicatively connected with the memory 103 .

[0099] The memory 103 stores a computer program, and when the computer program is executed by the processor 101, the authorization verification management method based on customer privacy protection provided in the above embodiment of the present application is implemented.

[0100] Optionally, the processor 101 and the memory 103 may be connected via a bus 102. Optionally, the speech synthesis server 100 may further include a transceiver 104. It should be noted that in actual applications, the transceiver 104 is not limited to one, and the structure of the speech synthesis server 100 does not constitute a limitation on the embodiments of the present application.

[0101] The processor 101 is applied in the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 104 may include a receiver and a transmitter. The transceiver 104 is applied in the embodiment of the present application to implement the function of the speech synthesis server 100 in the embodiment of the present application communicating with other devices when executed.

[0102] Processor 101 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 101 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0103] The bus 102 may include a path to transmit information between the above components. The bus 102 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 102 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0104] The memory 103 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store a desired computer program in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0105] The data query end provided in the embodiment of the present application has the same inventive concept as the embodiments described above. The contents not shown in detail in the data query end can be referred to the embodiments described above and will not be repeated here.

[0106] Based on the same inventive concept, the embodiment of the present application also provides a data management terminal, such as Figure 4 As shown, the data management end includes a memory 203 and a processor 201 , and the processor 201 is in communication connection with the memory 203 .

[0107] The memory 203 stores a computer program, and when the computer program is executed by the processor 201, the authorization verification management method based on customer privacy protection provided in the above embodiment of the present application is implemented.

[0108] Optionally, the processor 201 and the memory 203 may be connected via a bus 202. Optionally, the speech synthesis server 200 may further include a transceiver 204. It should be noted that in actual applications, the transceiver 204 is not limited to one, and the structure of the speech synthesis server 200 does not constitute a limitation on the embodiments of the present application.

[0109] The processor 201 is applied in the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 204 may include a receiver and a transmitter. The transceiver 204 is applied in the embodiment of the present application to implement the function of the speech synthesis server 200 in the embodiment of the present application communicating with other devices when executed.

[0110] The processor 201 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor 201 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0111] The bus 202 may include a path to transmit information between the above components. The bus 202 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 202 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0112] The memory 203 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store a desired computer program in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0113] The data management terminal provided in the embodiment of the present application has the same inventive concept as the embodiments described above. The contents not shown in detail in the data management terminal can be referred to the embodiments described above and will not be repeated here.

[0114] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps performed by the data query end in the above-mentioned authorization verification management method based on customer privacy protection are implemented.

[0115] Based on the same inventive concept, an embodiment of the present application provides another computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps performed by the data management end in the above-mentioned authorization verification management method based on customer privacy protection are implemented.

[0116] The computer-readable storage media provided herein include, but are not limited to, any type of disk (including floppy disk, hard disk, optical disk, CD-ROM, and magneto-optical disk), ROM, RAM, EPROM (Erasable Programmable Read-Only Memory), EEPROM, flash memory, magnetic card or optical card. In other words, the readable medium includes any medium that can store or transmit information in a readable form by a device (e.g., a computer).

[0117] The computer-readable storage medium provided in the embodiment of the present application has the same inventive concept as the embodiments described above. The contents not shown in detail in the computer-readable storage medium can be referred to the embodiments described above and will not be repeated here.

[0118] Those skilled in the art will appreciate that the various operations, methods, steps, measures, and schemes in the processes discussed in this application may be alternated, altered, combined, or deleted. Further, other steps, measures, and schemes in the various operations, methods, and processes discussed in this application may also be alternated, altered, rearranged, decomposed, combined, or deleted. Further, the steps, measures, and schemes in the prior art that are similar to those disclosed in this application may also be alternated, altered, rearranged, decomposed, combined, or deleted.

[0119] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the feature. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0120] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence based on the indications of the arrows, these steps are not necessarily executed in sequence based on the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0121] The above description is only a partial implementation method of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. An authorization verification management method based on customer privacy protection, characterized in that: include: The data query end obtains the business authorization code corresponding to the current data query request, including: The data query end determines whether the current data query request is a new data query request; When the current data query request is not a new data query request, the data query end queries a pre-stored historical data query request that is the same as the current data query request, and uses the service authorization code corresponding to the historical data query request as the service authorization code corresponding to the current data query request; When the current data query request is a new data query request, the data query end sends the personal privacy usage scenario number corresponding to the current data query request, the number of the data query end and the data query transaction code to the data management end; the data management end determines the service authorization code according to the personal privacy usage scenario number, the number of the data query end and the data query transaction code; the data management end returns the determined service authorization code to the data query end; The data query end sends the customer number, data query transaction code and business authorization code corresponding to the current data query request to the data management end; The data management terminal determines whether the current data query request meets the preset query condition based on the customer number, the data query transaction code and the service authorization code; When the current data query request meets the preset query condition, the data management end obtains the query result based on the data query transaction code, and returns the query result to the data query end.

2. The authorization verification management method based on customer privacy protection according to claim 1 is characterized in that: The data query end determines whether the current data query request is a new data query request, including: The data query end locally queries whether there is a business authorization code that matches the personal privacy usage scenario number corresponding to the current data query request and the data query transaction code; When the query result is yes, determining that the current data query request is not a new data query request; When the query result is no, it is determined that the current data query request is a new data query request.

3. The authorization verification management method based on customer privacy protection according to claim 1 is characterized in that: The data management end determines whether the current data query request meets a preset query condition based on the customer number, the data query transaction code, and the service authorization code, including: When the current data query request has the service authorization code and it is determined according to the data query transaction code that the transaction involved in the current data query request is a non-customer privacy transaction, it is determined that the current data query request meets the preset query condition.

4. The authorization verification management method based on customer privacy protection according to claim 3 is characterized in that: Determining, according to the data query transaction code, that the transaction involved in the current data query request is a non-client privacy transaction includes: The data management end matches the data query transaction code with a built-in customer query privacy transaction code list, and when the customer query privacy transaction code list does not contain the data query transaction code, determines that the transaction involved in the current data query request is a non-customer privacy transaction.

5. The authorization verification management method based on customer privacy protection according to claim 3 is characterized in that: Also includes: When the current data query request does not have the service authorization code, the current data query request is rejected.

6. The authorization verification management method based on customer privacy protection according to claim 1 is characterized in that: The data management end determines whether the current data query request meets a preset query condition based on the customer number, the data query transaction code, and the service authorization code, including: When the current data query request has the business authorization code, it is determined that the transaction involved in the current data query request is a customer privacy transaction according to the data query transaction code, and it is determined that the current data query request has customer authorization, it is determined that the current data query request meets the preset query condition.

7. The authorization verification management method based on customer privacy protection according to claim 6 is characterized in that: The determining that the current data query request has the client authorization includes: The data management end sends a client authorization verification request to the authorization system server; The authorization system server associates the first business scenario number corresponding to the current data query request according to the business authorization code; The authorization system server queries the customer contract record according to the customer number; The authorization system server associates the customer's authorized scenario number, data query transaction code, data query terminal number and authorization validity period according to the agreement number associated with the customer contract record; The authorization system service end determines that the first business scenario number, the data query transaction code and the data query terminal number corresponding to the current data query request match the scenario number, the data query transaction code and the data query terminal number authorized by the customer, respectively, and when the time of the current data query request does not exceed the authorization validity period, it determines that the customer authorization verification is successful, and sends a notification of the success of the customer authorization verification to the data management end; The data management determines that the current data query request has the customer authorization based on the notification of successful customer authorization verification.

8. The authorization verification management method based on customer privacy protection according to claim 6 is characterized in that: Determining, according to the data query transaction code, that the transaction involved in the current data query request is a customer privacy transaction includes: The data management end matches the data query transaction code with a built-in customer query privacy transaction code list, and when the customer query privacy transaction code list contains the data query transaction code, determines that the transaction involved in the current data query request is a customer privacy transaction.

9. The authorization verification management method based on customer privacy protection according to claim 6 is characterized in that: Also includes: When the current data query request does not have the service authorization code, reject the current data query request; as well as In the case that the transaction involved in the current data query request is a customer privacy transaction, when the current data query request does not have customer authorization, the current data query request is rejected.

10. An authorization verification management system based on customer privacy protection, characterized in that: include: Data query end and data management end; The data query end is used to obtain the service authorization code corresponding to the current data query request, including: The data query end determines whether the current data query request is a new data query request; When the current data query request is not a new data query request, the data query end queries a pre-stored historical data query request that is the same as the current data query request, and uses the service authorization code corresponding to the historical data query request as the service authorization code corresponding to the current data query request; When the current data query request is a new data query request, the data query end sends the personal privacy usage scenario number corresponding to the current data query request, the number of the data query end and the data query transaction code to the data management end; the data management end determines the service authorization code according to the personal privacy usage scenario number, the number of the data query end and the data query transaction code; the data management end returns the determined service authorization code to the data query end; The data query end is used to: send the customer number, data query transaction code and business authorization code corresponding to the current data query request to the data management end; based on the customer number, data query transaction code and business authorization code, determine whether the current data query request meets the preset query conditions; when the current data query request meets the preset query conditions, the data query transaction code obtains the query result and returns the query result to the data query end.

11. A data query terminal, characterized in that: comprising a memory and a processor, wherein the processor is communicatively connected to the memory; The memory stores a computer program, and when the computer program is executed by the processor, the steps performed by the data query end in the authorization verification management method based on customer privacy protection as described in any one of claims 1 to 9 are implemented.

12. A data management terminal, characterized in that: comprising a memory and a processor, wherein the processor is communicatively connected to the memory; The memory stores a computer program, and when the computer program is executed by the processor, the steps performed by the data management end in the authorization verification management method based on customer privacy protection as described in any one of claims 1 to 9 are implemented.

13. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by the processor, the steps performed by the data query end in the authorization verification management method based on customer privacy protection as described in any one of claims 1 to 9 are implemented.

14. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by the processor, the steps performed by the data management end in the authorization verification management method based on customer privacy protection as described in any one of claims 1 to 9 are implemented.

Images