CN115022864B - Verification method and device for subscription service - Google Patents
Verification method and device for subscription service Download PDFInfo
- Publication number
- CN115022864B CN115022864B CN202210586804.9A CN202210586804A CN115022864B CN 115022864 B CN115022864 B CN 115022864B CN 202210586804 A CN202210586804 A CN 202210586804A CN 115022864 B CN115022864 B CN 115022864B
- Authority
- CN
- China
- Prior art keywords
- target
- service
- node
- subscription
- invalid
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/03—Protecting confidentiality, e.g. by encryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
Abstract
The application discloses a verification method and device for subscription service, belongs to the field of communication, and solves the problem that validity of a service subscription request in the related art needs to be judged. The method comprises the following steps: receiving a target ordering request submitted by a third party platform for ordering target business by a target user; in the event that the target subscription request is not the initial subscription request of the target user stored in a node of a blockchain, verifying whether the target subscription request is valid based on historical subscription requests of the target user stored in each node of the blockchain and the node.
Description
Technical Field
The application belongs to the field of communication, and particularly relates to a method and a device for verifying subscription service.
Background
In the related art, the service subscription flow is: (1) The user selects a subscription service and inputs a subscription mobile phone number on a subscription page of a third party platform, a communication service platform and the like so as to submit a subscription request to the subscription platform; (2) After receiving the order request, the order platform judges the attribution province of the mobile phone number, and then forwards the order request to an attribution province company platform; (3) And the third party platform, the communication service platform, the ordering platform, the provincial company platform and other multi-systems interact layer by layer through interfaces to complete the inquiry and ordering operations.
In the service subscription flow, the problems of service acceptance failure, system failure and the like occur in the third party platform, and the subscription interface between the third party platform and the communication service platform is easy to cause problems, so that the service subscription request is easy to be invalid.
Therefore, in the related art, in order to ensure the normal progress of the service subscription flow, it is necessary to determine the validity of the subscription request of the service.
Disclosure of Invention
The embodiment of the application provides a verification method and device for subscription service, which can solve the problem that the validity of a service subscription request in the related technology needs to be judged.
In a first aspect, an embodiment of the present application provides a method for verifying a subscription service, where the method includes: receiving a target ordering request submitted by a third party platform for ordering target business by a target user; in the event that the target subscription request is not the initial subscription request of the target user stored in a node of a blockchain, verifying whether the target subscription request is valid based on historical subscription requests of the target user stored in each node of the blockchain and the node.
In a second aspect, an embodiment of the present application provides an authentication apparatus for subscription services, where the apparatus includes: the receiving module is used for receiving a target ordering request submitted by a third party platform for ordering a target service by a target user; and the verification module is used for verifying whether the target subscription request is valid or not based on each node of the blockchain and the historical subscription requests of the target users stored in the nodes when the target subscription request is not the initial subscription request of the target users stored in the nodes of the blockchain.
In a third aspect, embodiments of the present application provide an electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction implementing the steps of the method according to the first aspect when executed by the processor.
In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps of the method according to the first aspect.
In a fifth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and where the processor is configured to execute a program or instructions to implement a method according to the first aspect.
In the embodiment of the application, a target user order target service target order request submitted by a third party platform is received; in the case that the target subscription request is not the initial subscription request of the target user stored in a node of a blockchain, verifying whether the target subscription request is valid or not based on each node of the blockchain and the historical subscription requests of the target user stored in the node, which solves the problem that the validity of the service subscription request needs to be judged in the related art.
Drawings
Fig. 1 is a flow chart of a method for verifying a subscription service according to an embodiment of the present application;
fig. 2 is a flow chart of another method for verifying a subscription service according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a verification apparatus for subscription service according to an embodiment of the present application;
fig. 4 is a schematic structural view of an electronic device according to another embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
The following describes in detail a method and an apparatus for verifying a subscription service provided in the embodiments of the present application through specific embodiments and application scenarios thereof with reference to the accompanying drawings.
Specifically, in the related art, the service subscription flow is: (1) The user selects a subscription service and inputs a subscription mobile phone number on a subscription page of a third party platform, a communication service platform and the like so as to submit a subscription request to the subscription platform; (2) After receiving the order request, the order platform judges the attribution province of the mobile phone number, and then forwards the order request to an attribution province company platform; (3) And the third party platform, the communication service platform, the ordering platform, the provincial company platform and other multi-systems interact layer by layer through interfaces to complete the inquiry and ordering operations.
In the service subscription flow, the problems of service acceptance failure, system failure and the like occur in the third party platform, and the subscription interface between the third party platform and the communication service platform is easy to cause problems, so that the service subscription request is easy to be invalid.
In view of the above, the method and the device receive the target subscription request of subscribing the target service of the target user submitted by the third party platform; in the case that the target subscription request is not the initial subscription request of the target user stored in a node of a blockchain, verifying whether the target subscription request is valid or not based on each node of the blockchain and the historical subscription requests of the target user stored in the node, which solves the problem that the validity of the service subscription request needs to be judged in the related art.
Fig. 1 illustrates a method for verifying a subscription service according to an embodiment of the present invention, which may be performed by an electronic device, which may include: a server and/or a terminal device, wherein the terminal device may be, for example, a mobile phone terminal or the like. In other words, the method may be performed by software or hardware installed in an electronic device, the method comprising the steps of:
step 101: and receiving a target subscription request submitted by the third-party platform for subscribing the target service by the target user.
Specifically, the third party platform may be any platform that may submit a target subscription request to the server, for example, a WeChat payment platform, a Payment device payment platform, a UnionPayment platform, and the like.
Alternatively, the target service may be a service to which the target user needs to subscribe, for example, the target service may be a pay phone fee service, a purchase flow service, or the like.
Step 102: in the event that the target subscription request is not the initial subscription request of the target user stored in a node of a blockchain, verifying whether the target subscription request is valid based on historical subscription requests of the target user stored in each node of the blockchain and the node.
Optionally, if the historical subscription request of the target user is not stored in the node of the blockchain, the target subscription request may be confirmed to be the initial subscription request of the target user.
Specifically, each node of the blockchain may include each federation party of the blockchain and a federation platform formed by each federation party.
It can be understood that, in the embodiments of the present application, both the third party platform and the service party for providing the target service may be considered as the federator of the blockchain.
In this way, the embodiment receives the target subscription request submitted by the third party platform for subscribing the target service by the target user; and under the condition that the target subscription request is not the initial subscription request of the target user stored in the nodes of the blockchain, verifying whether the target subscription request is valid or not based on each node of the blockchain and the historical subscription requests of the target user stored in the nodes, and solving the problem that the validity of the service subscription request needs to be judged in the related technology.
In an alternative implementation manner, after the receiving the target subscription request submitted by the third party platform for subscribing to the target service by the target user, the method further includes:
storing the target subscription request in a node of the blockchain if the target subscription request is a first subscription request of the target user stored in the node of the blockchain;
the target subscription request is stored in a node of a blockchain if the target subscription request is not the initial subscription request of the target user stored in the node of the blockchain and the target subscription request is valid.
It should be noted that the subscription requests stored in the nodes in the blockchain may be synchronized. For example, subscription requests for services submitted by two different third party platforms may be stored in different blockchain nodes, which may further synchronize the stored subscription requests.
Therefore, when the service ordering process fails, the service ordering request data of the service needs to be checked and checked, so that the service ordering data of multiple platforms needs to be checked, the service ordering data is difficult or cannot be traced, the tracing step of the service ordering data can be saved by storing the related data of the service ordering request in the blockchain, the service ordering data needing to be checked can be accurately found, the tracing time and tracing accuracy of the service ordering data can be greatly improved, and manpower and material resources are greatly saved.
In an alternative implementation manner, the target subscription request includes an identity of the target user and a target subscription time for the target user to subscribe to the target service;
before verifying whether the target subscription request is valid based on the historical subscription requests of the target user stored in each node of the blockchain and the node, the method further comprises: determining a historical ordering request corresponding to the target user based on the identity of the target user;
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises: if the target ordering time is not later than the ordering time corresponding to all the historical ordering requests corresponding to the target user stored in the node of the blockchain, determining that the target ordering time is invalid; and in the case that the target subscription time is determined to be invalid, determining that the target subscription request is invalid.
Alternatively, the identity of the target user may be the contact address of the target user.
Thus, the ordering time of the target service can be ensured to be free from problems by determining the validity of the ordering time of the target service, so that the problem of repeated ordering is avoided.
In an alternative implementation manner, the target subscription request includes an identifier of a service initiator of the target service, where the service initiator is the third party platform;
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the service initiator is not authenticated by each node of the blockchain and/or is not a service party disclosed by each node, determining that the identification of the service initiator is invalid;
and in the case that the identification of the service initiator is invalid, determining that the target subscription request is invalid.
It is understood that each node in the blockchain may include each federation party of the blockchain and a federation platform formed by the federation parties, and thus the service initiator may be a service party authenticated by each federation party and shown on the federation platform.
Alternatively, the identity of the service initiator may be unique.
Specifically, the identifier of the service initiator may be a number, a word, a letter, a character, etc., which is not limited herein.
Therefore, by verifying the identification of the service initiator, the platform which is not authenticated by each alliance party of the blockchain can be prevented from submitting the service subscription request, so that the security of the service subscription flow is ensured.
In an optional implementation manner, the target subscription request includes an identity of the target user and a target subscription serial number of the target service;
before verifying whether the target subscription request is valid based on the historical subscription requests of the target user stored in each node of the blockchain and the node, the method further comprises:
determining a historical ordering request corresponding to the target user based on the identity of the target user;
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the target order serial number is repeated with the order serial number corresponding to the historical order request corresponding to the target user stored in the node of the blockchain, determining that the target order serial number is invalid;
and determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid.
Optionally, the identity of the target user may be a contact way of the target user;
in this way, repeated subscriptions to services can be effectively prevented.
In an alternative implementation, the target subscription request includes a target subscription serial number of the target service;
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the target order serial number does not meet a preset secondary hash rule, determining that the target order serial number is invalid;
and determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid.
The target order serial number comprises an identification of a service initiator, a public key of the service initiator, an identification of the target user, a service identification of the target service and a target order time of the target service;
the service initiator is the third party platform, the service initiator is a service party approved by each node passing through the blockchain and disclosed at each node, and the public key of the service initiator is a public key disclosed at each node;
the secondary hash rule is that after a single hash is performed on the identity of the target user, the service identifier of the target service and the target ordering time of the target service, a secondary hash is performed on the target ordering serial number.
Therefore, compared with Shan Ciha, the method can effectively distinguish the orders of different services by performing secondary hash on the target order serial number, and can avoid the problem that the services are forged by adding the public key of the service initiator into the target order serial number.
Alternatively, the identity of the target user may be the contact address of the target user.
In an alternative implementation, the target subscription request includes a service identifier of the target service;
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the service identifier of the target service is not authenticated by each node of the blockchain and/or is not a service identifier disclosed in each node, determining that the service identifier of the target service is invalid;
and in the case that the service identification is determined to be invalid, determining that the target subscription request is invalid.
Alternatively, the service identifier of a service may be unique.
Optionally, each node of the blockchain may include each federation party of the blockchain and a federation platform formed by each federation party, and further, the service identifier of the target service may be a service identifier authenticated by each federation party of the blockchain and shown on the federation platform.
Alternatively, the service identifier of the target service may be a character string, a single character, or the like, which is not specifically limited herein.
Therefore, the service subscribed by the user can be ensured to be the service allowed by each alliance party through the blockchain, and the user can be prevented from subscribing the wrong service.
In an alternative implementation, the target subscription request further includes a target subscription time for a target service;
before verifying whether the target subscription request is valid based on the historical subscription requests of the target user stored in each node of the blockchain and the node, the method further comprises:
if the service identifier is not encrypted by the private key of the service party, determining that the service identifier is invalid;
if the target ordering time does not pass the encryption of the private key of the service party, determining that the target ordering time is invalid;
and determining that the target subscription request is invalid under the condition that the service identification and/or the target subscription time are invalid.
Optionally, the encryption mode of the private key of the service party on the service identifier and the target subscription time may be an RSA (RSA public key encryption algorithm) encryption mode.
It can be appreciated that the service identifier and the target subscription time may be decrypted by the public key of the service party, and if the service identifier and the target subscription time may be decrypted, it may be determined that the service identifier and the target subscription time are encrypted by the private key of the service party.
Thus, the service identifier is encrypted by the private key of the service party, so that the falsification of the service by other service parties can be prevented.
Alternatively, specific steps of an embodiment of the present application are described below in conjunction with fig. 2, where the blockchain in this embodiment is a federated chain.
Step 201: and receiving a subscription request of a user subscription service submitted by a third party platform.
Specifically, the user can input own contact information on the page of the third party platform and select the service to be subscribed, and the third party platform can submit the subscription request to the node of the blockchain connected with the third party platform.
Step 202: and storing the subscription request corresponding to the user into the node of the blockchain.
Specifically, if the subscription request is the first subscription request of the user stored in the node of the blockchain, the subscription request may be stored in the node of the blockchain, and the subscription request may be stored in other nodes of the blockchain;
if the subscription request is not the subscription request stored for the first time in the node of the blockchain, verifying the validity of the subscription request; if the subscription request is valid, the subscription request is stored in a node of the blockchain, and the subscription request is stored in other nodes of the blockchain.
Optionally, the subscription request may include a subscription time of the service, a subscription serial number of the service, a service initiator identifier of the service, and a service identifier of the service;
it can be understood that to determine the validity of the subscription request, it is natural to determine the subscription time of the service, the subscription serial number of the service, the service initiator identifier of the service, and the validity of the service identifier of the service.
Optionally, the subscription information of all the historic services corresponding to the contact information of the user stored in the blockchain can be queried, and if the subscription time of the current service is later than the subscription time of the historic services stored in the nodes of the blockchain, the subscription time of the current service can be considered to be valid;
optionally, each business side of the blockchain needs to be shown on a federation platform of the blockchain and obtain authentication of each federation side of the blockchain; optionally, the identifier of the service initiator may be a unique identifier authenticated by the federation party; on this basis, if the identifier of the service initiator meets the above requirement, the identifier of the service initiator can be considered valid.
Optionally, if the subscription serial number of the service is repeated with the subscription serial number corresponding to the historical subscription request corresponding to the user stored in the blockchain, it may be determined that the subscription serial number is invalid;
optionally, if the order serial number of the service does not conform to the secondary hash rule, it can be determined that the order serial number is invalid; optionally, the subscription serial number may include a service initiator identifier, a service initiator public key, a contact manner of a user, a service identifier of a service, and a subscription time of the service;
specifically, the secondary hash rule may be a single Ha Xihou of the contact manner of the user, the service identifier of the service, and the subscription time of the service, and a secondary hash of the subscription serial number;
optionally, if the service identifier of the service and the subscription time of the service cannot be decrypted by RSA through the public key of the service party, it may be determined that the service identifier of the service and the subscription time of the service are invalid; based on the above, it can be understood that the service identifier of the effective service and the subscription time of the service are RSA encrypted by the private key of the service party;
optionally, the service identifier of the service needs to be shown on the alliance platform and authenticated by each alliance party; alternatively, the service identity of the service may be unique.
Therefore, by verifying the validity of the service subscription request, the normal operation of the service subscription flow can be ensured, and the correctness and the safety of service subscription can be ensured; by storing the service subscription request into the blockchain, when the service subscription request is required to be traced and checked when the service subscription flow is in a problem, the service subscription request can be quickly and accurately found, so that tracing time and energy can be saved, and tracing accuracy can be improved.
It should be noted that, in the method for verifying a subscription service provided in the embodiment of the present application, the executing body may be a method for verifying a subscription service, or a control module in the device for verifying a subscription service, where the control module is used for executing a method for verifying a subscription service. In the embodiment of the present application, an example of a method for executing a verification method for a subscription service by a verification device for a subscription service is described.
Fig. 3 is a schematic structural view of a subscription service authentication apparatus according to an embodiment of the present invention. As shown in fig. 3, an authentication apparatus 300 for subscription service includes: a receiving module 310, a verifying module 320.
A receiving module 310, configured to receive a target subscription request submitted by a third party platform for subscribing to a target service by a target user;
a verification module 320, configured to, in a case where the target subscription request is not the initial subscription request of the target user stored in a node of a blockchain, verify whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node.
In one implementation, the verification module 320 is further configured to: storing the target subscription request in a node of the blockchain if the target subscription request is a first subscription request of the target user stored in the node of the blockchain;
the target subscription request is stored in a node of a blockchain if the target subscription request is not the initial subscription request of the target user stored in the node of the blockchain and the target subscription request is valid.
In one implementation, the target subscription request includes an identity of the target user and a target subscription time for the target user to subscribe to the target service;
the verification module 320 is further configured to: determining a historical ordering request corresponding to the target user based on the identity of the target user;
if the target ordering time is not later than the ordering time corresponding to all the historical ordering requests corresponding to the target user stored in the node of the blockchain, determining that the target ordering time is invalid;
and in the case that the target subscription time is determined to be invalid, determining that the target subscription request is invalid.
In one implementation, the verification module 320 is further configured to: the target subscription request comprises an identifier of a service initiator of the target service, wherein the service initiator is the third party platform;
if the service initiator is not authenticated by each node of the blockchain and/or is not a service party disclosed by each node, determining that the identification of the service initiator is invalid;
and in the case that the identification of the service initiator is invalid, determining that the target subscription request is invalid.
In one implementation, the verification module 320 is further configured to: the target order request comprises the identity of the target user and the target order serial number of the target service;
determining a historical ordering request corresponding to the target user based on the identity of the target user;
if the target order serial number is repeated with the order serial number corresponding to the historical order request corresponding to the target user stored in the node of the blockchain, determining that the target order serial number is invalid;
and determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid.
In one implementation, the verification module 320 is further configured to: the target order request comprises a target order serial number of the target service;
if the target order serial number does not meet a preset secondary hash rule, determining that the target order serial number is invalid;
and determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid.
The target order serial number comprises an identification of a service initiator, a public key of the service initiator, an identification of the target user, a service identification of the target service and a target order time of the target service;
the service initiator is the third party platform, the service initiator is a service party approved by each node passing through the blockchain and disclosed at each node, and the public key of the service initiator is a public key disclosed at each node;
the secondary hash rule is that after a single hash is performed on the identity of the target user, the service identifier of the target service and the target ordering time of the target service, a secondary hash is performed on the target ordering serial number.
In one implementation, the verification module 320 is further configured to: the target subscription request comprises a service identifier of the target service;
if the service identifier of the target service is not authenticated by each node of the blockchain and/or is not a service identifier disclosed in each node, determining that the service identifier of the target service is invalid;
and in the case that the service identification is determined to be invalid, determining that the target subscription request is invalid.
In one implementation, the verification module 320 is further configured to: the target subscription request further comprises a target subscription time of the target service;
if the service identifier is not encrypted by the private key of the service party, determining that the service identifier is invalid;
if the target ordering time does not pass the encryption of the private key of the service party, determining that the target ordering time is invalid;
and determining that the target subscription request is invalid under the condition that the service identification and/or the target subscription time are invalid.
The verification device for subscription service in the embodiment of the application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. By way of example, the mobile electronic device may be a cell phone, tablet computer, notebook computer, palm computer, vehicle-mounted electronic device, wearable device, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), netbook or personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device may be a server, network attached storage (Network Attached Storage, NAS), personal computer (personal computer, PC), television (TV), teller machine or self-service machine, etc., and the embodiments of the present application are not limited in particular.
The authentication device for subscription service in the embodiment of the present application may be a device with an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
The verification device for subscription service provided in the embodiment of the present application can implement each process implemented in the method embodiments of fig. 1 and fig. 2, and in order to avoid repetition, a description is omitted here.
Optionally, as shown in fig. 4, the embodiment of the present application further provides an electronic device 400, including a processor 401, a memory 402, and a program or an instruction stored in the memory 402 and capable of running on the processor 401, where the program or the instruction is executed by the processor 401 to implement each process of the embodiment of the method, and the process can achieve the same technical effect, so that repetition is avoided, and no further description is given here.
The electronic device in the embodiment of the application includes the mobile electronic device and the non-mobile electronic device described above.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above-mentioned verification method embodiment of the subscription service, and the same technical effects can be achieved, so that repetition is avoided, and no further description is provided herein.
Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run a program or an instruction, implement each process of the above-mentioned verification method embodiment of the subscription service, and achieve the same technical effect, so that repetition is avoided, and no further description is provided here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, chip systems, or system-on-chip chips, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.
Claims (3)
1. A method of verifying subscription service, comprising:
receiving a target ordering request submitted by a third party platform for ordering target business by a target user;
verifying whether the target subscription request is valid based on each node of the blockchain and a historical subscription request of the target user stored in the node, and storing the target subscription request in the node of the blockchain, if the target subscription request is not the initial subscription request of the target user stored in the node of the blockchain;
storing the target subscription request in a node of the blockchain if the target subscription request is a first subscription request of the target user stored in the node of the blockchain;
in case the target subscription request comprises an identity of the target user and a target subscription time for the target user to subscribe to the target service,
before verifying whether the target subscription request is valid based on the historical subscription requests of the target user stored in each node of the blockchain and the node, the method further comprises:
determining a historical ordering request corresponding to the target user based on the identity of the target user;
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the target ordering time is not later than the ordering time corresponding to all the historical ordering requests corresponding to the target user stored in the node of the blockchain, determining that the target ordering time is invalid;
determining that the target subscription request is invalid in the case that the target subscription time is determined to be invalid;
in case the target subscription request comprises an identification of a service initiator of the target service, wherein the service initiator is the third party platform,
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the service initiator is not authenticated by each node of the blockchain and/or is not a service party disclosed by each node, determining that the identification of the service initiator is invalid;
determining that the target subscription request is invalid under the condition that the identification of the service initiator is invalid;
in case the target subscription request comprises an identity of the target user and a target subscription flow number of the target service,
before verifying whether the target subscription request is valid based on the historical subscription requests of the target user stored in each node of the blockchain and the node, the method further comprises:
determining a historical ordering request corresponding to the target user based on the identity of the target user;
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the target order serial number is repeated with the order serial number corresponding to the historical order request corresponding to the target user stored in the node of the blockchain, determining that the target order serial number is invalid;
determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid;
in case the target subscription request comprises a target subscription flow number of the target service,
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the target order serial number does not meet a preset secondary hash rule, determining that the target order serial number is invalid;
determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid;
the target order serial number comprises an identification of a service initiator, a public key of the service initiator, an identification of the target user, a service identification of the target service and a target order time of the target service;
the service initiator is the third party platform, the service initiator is a service party approved by each node passing through the blockchain and disclosed at each node, and the public key of the service initiator is a public key disclosed at each node;
the secondary hash rule is that after the identity of the target user, the service identifier of the target service and the target ordering time of the target service are hashed once, the target ordering serial number is hashed twice;
in case the target subscription request comprises a service identity of the target service,
the verifying whether the target subscription request is valid based on each node of the blockchain and the historical subscription requests of the target user stored in the node comprises:
if the service identifier of the target service is not authenticated by each node of the blockchain and/or is not a service identifier disclosed in each node, determining that the service identifier of the target service is invalid;
and in the case that the service identification is determined to be invalid, determining that the target subscription request is invalid.
2. The method of claim 1, wherein the target subscription request further comprises a target subscription time for the target service;
before verifying whether the target subscription request is valid based on the historical subscription requests of the target user stored in each node of the blockchain and the node, the method further comprises:
if the service identifier is not encrypted by the private key of the service party, determining that the service identifier is invalid;
if the target ordering time does not pass the encryption of the private key of the service party, determining that the target ordering time is invalid;
and determining that the target subscription request is invalid under the condition that the service identification and/or the target subscription time are invalid.
3. A subscription service verification apparatus, comprising:
the receiving module is used for receiving a target ordering request submitted by a third party platform for ordering a target service by a target user;
a verification module, configured to, in a case where the target subscription request is not a primary subscription request of the target user stored in a node of a blockchain, verify whether the target subscription request is valid based on each node of the blockchain and a historical subscription request of the target user stored in the node, and store the target subscription request in the node of the blockchain;
storing the target subscription request in a node of the blockchain if the target subscription request is a first subscription request of the target user stored in the node of the blockchain;
the verification module is further configured to determine, based on the identity of the target user, a historical subscription request corresponding to the target user when the target subscription request includes the identity of the target user and a target subscription time for the target user to subscribe to the target service;
if the target ordering time is not later than the ordering time corresponding to all the historical ordering requests corresponding to the target user stored in the node of the blockchain, determining that the target ordering time is invalid;
determining that the target subscription request is invalid in the case that the target subscription time is determined to be invalid;
the verification module is further configured to, the target subscription request includes an identification of a service initiator of the target service, where the service initiator is the third party platform,
if the service initiator is not authenticated by each node of the blockchain and/or is not a service party disclosed by each node, determining that the identification of the service initiator is invalid;
determining that the target subscription request is invalid under the condition that the identification of the service initiator is invalid;
the verification module is also used for the target order request to comprise the identity of the target user and the target order serial number of the target service,
determining a historical ordering request corresponding to the target user based on the identity of the target user;
if the target order serial number is repeated with the order serial number corresponding to the historical order request corresponding to the target user stored in the node of the blockchain, determining that the target order serial number is invalid;
determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid;
the verification module is further configured to, the target subscription request includes a target subscription serial number of the target service,
if the target order serial number does not meet a preset secondary hash rule, determining that the target order serial number is invalid;
determining that the target order request is invalid under the condition that the target order serial number is determined to be invalid;
the target order serial number comprises an identification of a service initiator, a public key of the service initiator, an identification of the target user, a service identification of the target service and a target order time of the target service;
the service initiator is the third party platform, the service initiator is a service party approved by each node passing through the blockchain and disclosed at each node, and the public key of the service initiator is a public key disclosed at each node;
the secondary hash rule is that after the identity of the target user, the service identifier of the target service and the target ordering time of the target service are hashed once, the target ordering serial number is hashed twice;
the verification module is further configured to, the target subscription request including a service identification of the target service,
if the service identifier of the target service is not authenticated by each node of the blockchain and/or is not a service identifier disclosed in each node, determining that the service identifier of the target service is invalid;
and in the case that the service identification is determined to be invalid, determining that the target subscription request is invalid.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210586804.9A CN115022864B (en) | 2022-05-27 | 2022-05-27 | Verification method and device for subscription service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210586804.9A CN115022864B (en) | 2022-05-27 | 2022-05-27 | Verification method and device for subscription service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115022864A CN115022864A (en) | 2022-09-06 |
| CN115022864B true CN115022864B (en) | 2023-07-21 |
Family
ID=83070338
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210586804.9A Active CN115022864B (en) | 2022-05-27 | 2022-05-27 | Verification method and device for subscription service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115022864B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101536480A (en) * | 2006-11-03 | 2009-09-16 | 摩托罗拉公司 | Device and/or user authentication for network access |
| CN108924231A (en) * | 2018-07-10 | 2018-11-30 | 佛山伊苏巨森科技有限公司 | A method of for providing the subscription service based on block chain in customer network |
| CN108965991A (en) * | 2018-07-27 | 2018-12-07 | 深圳Tcl新技术有限公司 | Verification method and system, terminal device, the storage medium of program ordering state |
| KR102033042B1 (en) * | 2018-05-04 | 2019-10-16 | 주식회사 글로스퍼 | Login authentication system using block chain, login authentication method and login service application method |
| CN110717832A (en) * | 2019-10-21 | 2020-01-21 | 腾讯科技（深圳）有限公司 | Clean energy trading method, system, device and storage medium based on block chain |
| CN110995454A (en) * | 2019-11-08 | 2020-04-10 | 厦门网宿有限公司 | Service verification method and system |
| CN111163051A (en) * | 2019-11-29 | 2020-05-15 | 中国联合网络通信集团有限公司 | Service ordering method, device and terminal equipment |
| CN111356102A (en) * | 2018-12-21 | 2020-06-30 | 西安佰才邦网络技术有限公司 | Method and equipment for purchasing service based on block chain |
| CN113159896A (en) * | 2021-04-28 | 2021-07-23 | 中国工商银行股份有限公司 | Online marketing method, device and system for bank financing products |
| CN113422733A (en) * | 2021-08-25 | 2021-09-21 | 腾讯科技（深圳）有限公司 | Service processing method and device of block chain, computer equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190332691A1 (en) * | 2018-04-30 | 2019-10-31 | Robert Dale Beadles | Universal subscription and cryptocurrency payment management platforms and methods of use |
-
2022
- 2022-05-27 CN CN202210586804.9A patent/CN115022864B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101536480A (en) * | 2006-11-03 | 2009-09-16 | 摩托罗拉公司 | Device and/or user authentication for network access |
| KR102033042B1 (en) * | 2018-05-04 | 2019-10-16 | 주식회사 글로스퍼 | Login authentication system using block chain, login authentication method and login service application method |
| CN108924231A (en) * | 2018-07-10 | 2018-11-30 | 佛山伊苏巨森科技有限公司 | A method of for providing the subscription service based on block chain in customer network |
| CN108965991A (en) * | 2018-07-27 | 2018-12-07 | 深圳Tcl新技术有限公司 | Verification method and system, terminal device, the storage medium of program ordering state |
| CN111356102A (en) * | 2018-12-21 | 2020-06-30 | 西安佰才邦网络技术有限公司 | Method and equipment for purchasing service based on block chain |
| CN110717832A (en) * | 2019-10-21 | 2020-01-21 | 腾讯科技（深圳）有限公司 | Clean energy trading method, system, device and storage medium based on block chain |
| CN110995454A (en) * | 2019-11-08 | 2020-04-10 | 厦门网宿有限公司 | Service verification method and system |
| CN111163051A (en) * | 2019-11-29 | 2020-05-15 | 中国联合网络通信集团有限公司 | Service ordering method, device and terminal equipment |
| CN113159896A (en) * | 2021-04-28 | 2021-07-23 | 中国工商银行股份有限公司 | Online marketing method, device and system for bank financing products |
| CN113422733A (en) * | 2021-08-25 | 2021-09-21 | 腾讯科技（深圳）有限公司 | Service processing method and device of block chain, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于区块链的交易方案研究;杜逸聪;《中国优秀硕士学位论文辑》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115022864A (en) | 2022-09-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210152357A1 (en) | Method and device for identity verification | |
| US9560033B2 (en) | Method and system for authenticating user identity | |
| CN110768967B (en) | Service authorization method, device, equipment, system and storage medium | |
| CN102469091B (en) | Method for processing verification codes of pages, device and terminal | |
| CN104077689A (en) | Information verification method, relevant device and system | |
| CN107682336B (en) | Geographic position-based identity authentication method and device | |
| EP3206329B1 (en) | Security check method, device, terminal and server | |
| CN111641605B (en) | Electronic signature method and system based on dynamic password | |
| CN112950201B (en) | Node management method and related device applied to block chain system | |
| CN105991514A (en) | Service request authentication method and device | |
| CN111783049A (en) | User information processing method and system based on block chain | |
| CN110661779A (en) | Block chain network-based electronic certificate management method, system, device and medium | |
| CN111191212B (en) | Block chain-based digital certificate processing method, device, equipment and storage medium | |
| CN107679383B (en) | Identity verification method and device based on geographic position and touch area | |
| CN115022864B (en) | Verification method and device for subscription service | |
| CN105379176A (en) | System and method for validating SCEP certificate enrollment requests | |
| CN112732676B (en) | Block chain-based data migration method, device, equipment and storage medium | |
| CN106533685B (en) | Identity authentication method, device and system | |
| CN115664669A (en) | Financial equipment authentication method, cash dispenser, external equipment and storage medium | |
| CN112235247A (en) | Mobile terminal, terminal banking business security authentication method and system | |
| CN110766407A (en) | Transaction verification method, accounting node and medium based on block chain | |
| CN107491967B (en) | Method and system for inputting password through network payment | |
| CN115860745B (en) | Secret payment-free signing method, gateway equipment and storage medium | |
| CN115037549B (en) | Application protection method, device and storage medium | |
| CN116319070B (en) | Industrial Internet identification analysis system, method, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |