CN113114678A - Service execution method and device - Google Patents
Service execution method and device Download PDFInfo
- Publication number
- CN113114678A CN113114678A CN202110396572.6A CN202110396572A CN113114678A CN 113114678 A CN113114678 A CN 113114678A CN 202110396572 A CN202110396572 A CN 202110396572A CN 113114678 A CN113114678 A CN 113114678A
- Authority
- CN
- China
- Prior art keywords
- information
- acquirer
- server
- information acquirer
- payment
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 98
- 238000012790 confirmation Methods 0.000 claims abstract description 18
- 238000003860 storage Methods 0.000 claims description 22
- 238000013468 resource allocation Methods 0.000 claims description 19
- 230000004044 response Effects 0.000 claims description 10
- 238000004519 manufacturing process Methods 0.000 claims description 8
- 238000012795 verification Methods 0.000 claims description 6
- 238000009826 distribution Methods 0.000 claims description 2
- 230000008014 freezing Effects 0.000 claims description 2
- 238000007710 freezing Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 description 25
- 238000010586 diagram Methods 0.000 description 19
- 238000004590 computer program Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 9
- 230000006872 improvement Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- 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/3247—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 involving digital signatures
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a service execution method and a device, firstly, information issued by an information provider is stored in a server, when an acquisition request aiming at the information sent by an information acquirer is received, the information can be returned to the information acquirer firstly, then when a reply result returned by the information acquirer is received, if the reply result is a confirmation, resources of the information acquirer are allocated to the information provider, and if the reply result is a denial, the resources of the information acquirer are not allocated.
Description
Technical Field
The present application relates to the field of information technologies, and in particular, to a method and an apparatus for executing a service.
Background
In modern society, with the development of internet technology, information in networks is growing explosively. How to utilize massive information in the network becomes a problem of important attention of people.
The information is classified by the creator of the information, and the information can be roughly classified into two types: user Generated Content (UGC) and Occupational Generated Content (OGC). A server of a website (e.g., a video website, a web community, a blog, a microblog, etc.) that generally provides information can receive UGC issued by an information provider, and also can receive OGC through internal creation or external purchase as information provided to an information acquirer.
In the prior art, the website providing information generally needs richer information to attract users in order to improve the traffic of the website. In order to attract information providers to distribute more information, websites typically provide information to information acquirers for a fee and pay the information providers an amount of money paid by the information acquirers after receiving the amount of money. In the prior art, websites usually provide information for a fee by acquiring the information.
The process is shown in fig. 1, wherein the server stores information issued by the information provider, and the method specifically includes the following steps:
s102: the server receives an acquisition request aiming at the information sent by an information acquirer, wherein the acquisition request comprises an account identifier of the information acquirer;
s104: determining the payment amount of the acquired information according to a pre-stored amount payment mode corresponding to the information;
s106: initiating a payment service to the information acquirer according to the account identifier and the determined payment amount;
s108: and when the payment service is successfully executed, returning the information to the information acquirer and paying the payment amount to the information provider.
In addition, the website needs to ensure the quality of the published information to improve the customer retention rate. On the other hand, the UGC is not uniform in quality because it is self-issued by the information provider. On the other hand, due to problems such as network delay and network failure, the information acquirer may not receive the information or the received information is incomplete.
It can be seen that there are situations in the prior art where an information acquirer obtains low quality information after paying an amount. Therefore, a new service execution mode is needed to ensure the user experience of the information acquirer.
Disclosure of Invention
The embodiment of the application provides a service execution method, which is used for solving the problem that in the prior art, an information acquirer acquires low-quality information after paying for the information, so that the user experience of the information acquirer is poor.
The embodiment of the application provides a service execution device, which is used for solving the problem that in the prior art, an information acquisition party acquires low-quality information after paying for the information, so that the user experience of the information acquisition party is poor.
The embodiment of the application adopts the following technical scheme:
a service execution method, in which information issued by an information provider is stored in a server, the method comprising:
the server receives an acquisition request aiming at the information sent by an information acquirer;
returning the information to the information acquirer;
and receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
A method of service execution, comprising:
the information acquisition direction sends an acquisition request aiming at the information issued by the information provider to the server;
receiving the information returned by the server;
sending a reply result to the server to enable the server to determine whether to allocate the resource of the information acquirer to the information provider according to the reply result
A service execution apparatus comprising:
the storage module stores information issued by the information provider;
the receiving module is used for receiving an acquisition request aiming at the information sent by an information acquirer;
the sending module returns the information to the information acquisition party;
and the allocation module is used for receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
A service execution apparatus comprising:
the first sending module is used for sending an acquisition request aiming at the information issued by the information provider to the server;
the receiving module is used for receiving the information returned by the server;
and the second sending module is used for sending a reply result to the server so that the server determines whether to allocate the resource of the service execution device to the information provider according to the reply result.
A server in which information issued by an information provider is stored, comprising: one or more processors and memory, the memory storing a program and configured to perform, by the one or more processors:
the server receives an acquisition request aiming at the information sent by an information acquirer;
returning the information to the information acquirer;
and receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
A terminal, comprising: one or more processors and memory, the memory storing a program and configured to perform, by the one or more processors:
sending an acquisition request aiming at information issued by an information provider to a server;
receiving the information returned by the server;
and sending a reply result to the server so that the server determines whether to allocate the resource of the terminal to the information provider according to the reply result.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:
the server stores information issued by an information provider, and when receiving an acquisition request for the information sent by an information acquirer, the server can firstly return the information to the information acquirer, and then when receiving a reply result returned by the information acquirer, if the reply result is a confirmation, the server allocates the resource of the information acquirer to the information provider, and if the reply result is a denial, the server does not allocate the resource of the information acquirer. According to the method provided by the application, the information can be sent to the information acquirer firstly, and when the reply result sent by the subsequently received information acquirer is confirmed, the resource of the information acquirer is allocated to the information provider, so that the information acquirer can select whether to pay the acquired information, the defect that the information acquirer pays the acquired low-quality information is overcome, and the user experience is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a process for providing paid information;
fig. 2 is a service execution process provided in an embodiment of the present application;
fig. 3 is a schematic diagram illustrating a correspondence relationship between information and a resource allocation manner provided in an embodiment of the present application;
fig. 4 is a service execution process provided in an embodiment of the present application;
FIG. 5 is a schematic diagram of a reply page provided by an embodiment of the present application;
fig. 6 is a schematic structural diagram of a service execution device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a service execution device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 2 is a service execution process provided in the embodiment of the present application, which specifically includes the following steps:
s202: the server receives an acquisition request for the information sent by an information acquirer.
In an embodiment of the present application, the server is a server of a website that provides information (e.g., a server of a social networking site), and the information may be UGC or OGC, which is not specifically limited in this application. The website can be regarded as an intermediate platform, which provides a platform for issuing information for an information provider on one hand and provides a platform for acquiring information for an information acquirer on the other hand. Information issued by the information provider may be stored in the server of the website so as to be provided to the information acquirer when the information acquirer needs to acquire the information.
The information is provided for payment, that is, the information acquirer needs to use a certain resource as a reward (e.g., pay a corresponding resource or virtual currency, etc.) when acquiring the information. Therefore, when the server receives the information issued by the information provider, it may also receive the resource allocation method corresponding to the information sent by the information provider, and the server may also store the information and the resource allocation method corresponding to the information. Alternatively, when the information provider does not provide the resource allocation method, the resource allocation method of the information may be determined by the server and stored (for example, a default resource allocation method is stored as the resource allocation method of the information).
In addition, the information may be UGC and the types of the UGC are many, the resource allocation manners of different types of the UGC may not be completely the same, and when the information provider does not provide the resource allocation manner corresponding to the UGC, the server may determine the type of the UGC first when receiving the UGC, and then determine the resource allocation manner of the UGC according to the preset corresponding relationship between the type of the UGC and the resource allocation manner. Fig. 3 shows a schematic diagram of a correspondence relationship between a preset UGC type and a resource allocation manner.
As can be seen in fig. 3, the types of UGC in the present application may include: text, pictures, video, audio, and so forth. The resource allocation may include, for example: charging period, charging price, etc. Of course, since there is a mature method for determining how to determine the resource allocation manner of the information provided for compensation in the prior art, the resource allocation manner corresponding to the received information may be determined in the same manner as in the prior art, and the method is not particularly limited in this application.
Further, after receiving the information issued by the information provider, the server may store the information in a database corresponding to the server, and provide the information to the information acquirer through the server. Specifically, the information is stored in the server or a database corresponding to the server, and the application is not particularly limited.
In the embodiment of the application, the server may receive an acquisition request for information sent by an information acquirer. The information acquirer may be a user who requests to acquire information or a terminal used by the user.
For example, for any user, if the user provides UGC to a server, the user may be considered to be an information provider that issues information, and when the user sends an acquisition request for one or more pieces of information to the server, the user may be considered to be an information acquirer.
Further, to facilitate management of the information distributed by the information provider and the server (e.g., to recall the distributed information), the information provider may also send information to the server via an account registered with the server to cause the server to distribute the information on the website corresponding to the server. When the information acquirer requests to acquire information for paid provision, the information acquirer also needs to register an account in the server so as to provide certain resources for consideration through the account. Therefore, in the embodiment of the present application, the obtaining request may further include an account identifier of the information obtaining party.
It should be noted that the server may be a single device or a system composed of multiple devices, the information acquirer may send an acquisition request to the server through the terminal, the information provider may also send UGC to the server through the terminal, and the terminal may be a mobile phone, a tablet computer, a personal computer, or other devices, which is not limited in this application.
S204: and returning the information to the information acquirer.
In the embodiment of the application, after receiving the acquisition request of the information acquirer, the server may determine the information requested to be acquired according to the acquisition request, and even if the information is provided for payment, the server may return the information to the information acquirer. And in the subsequent step, whether the resource of the information acquirer is acquired or not is determined according to the reply information returned by the information acquirer, and the information is distributed to the information provider of the information.
S206: and receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
In the embodiment of the present application, since the server returns information to the information acquirer first, the server needs to wait for the information acquirer to return a reply result, so as to determine whether to allocate the resource of the information acquirer to the information provider according to the reply result.
The resource can be an amount, the resource allocation mode can be an amount payment mode, and the server can determine the payment amount according to the amount payment mode corresponding to the information. For convenience of description, the following description will be given by taking an amount and an amount payment method as examples, that is, the resource may be regarded as an amount, and the resource allocation method may be regarded as an amount payment method. In addition, the reply result can be sent to the server after being selected by the information acquirer. And, the reply result includes two kinds: acknowledgement and negative acknowledgement. I.e. confirmation of payment and refusal of payment.
Specifically, when the server receives that the reply result returned by the information acquirer is confirmation, the server may allocate the resource of the information acquirer to the information provider. Since the server can determine the amount payment method corresponding to the information when receiving the information issued by the information provider in step S202, the server can determine the payment amount (i.e., obtain the amount of money to be paid by the information) according to the amount payment method corresponding to the stored information, and send the payment information to the information acquirer according to the payment amount, so that the information acquirer pays the corresponding payment amount to the server after receiving the payment information, and the server can also obtain the payment amount provided by the information acquirer and pay the payment amount to the information provider.
The payment amount of the information acquirer to the server may be the same as the payment service in the prior art, and the application is not limited to this. For example, the payment information may be a cash register address link corresponding to the payment amount, and after receiving the cash register address link, the information acquirer may jump to a cash register page corresponding to the payment amount and perform a payment service.
When the server receives the negative acknowledgement of the reply result returned by the information acquirer, the server may not allocate the resource of the acquirer. That is, the server may not send payment information to the information acquirer and thus does not charge the amount of money of the information acquirer. Therefore, if the quality of the information acquired by the information acquirer does not meet the requirement, the information acquirer can refuse to pay the corresponding payment amount even if the information is provided for payment. Therefore, the condition that the information acquirer receives low-quality information after paying the payment amount in the prior art is avoided. Meanwhile, on the other hand, the information provider cannot cheat the payment amount of the information acquirer by providing a large amount of low-quality information. Therefore, the information provider can obtain the payment amount of the information acquirer only when needing to provide information with higher quality.
In addition, since there is a case where no reply information is returned to the server after the information acquirer acquires the information (e.g., due to a network failure, an equipment failure, or the information acquirer forgets to reply), when the server determines that the time period for waiting for receiving the reply result returned by the information acquirer exceeds a preset time after transmitting the information to the information acquirer, it is determined that the reply result of the confirmation returned by the information acquirer is received, or it is determined that the reply result of the denial returned by the information acquirer is received, and a subsequent operation is performed according to the reply result. That is, after the preset time is exceeded, if the reply result of the information acquirer is not received, the information acquirer is defaulted to return the confirmed or denied reply information.
Specifically, it is default that the information acquirer returns the confirmed reply information, or whether the denied reply information is set as required, which is not specifically limited in the present application.
For example, when the time length of waiting for receiving the reply result returned by the information acquirer exceeds a preset time after the information acquirer is sent, the server may determine the ratio of the number of payments of the information to the number of times of sending according to the number of times of sending of the information in the history and the number of times of payments (i.e., the number of times of receiving the confirmed reply result by the server for the information), determine the reply result as confirmation when the ratio exceeds a preset value (e.g., 80%), and otherwise. That is, when all the information acquirers that have acquired the information and exceed the preset ratio return the confirmed reply result, when the time length for sending the information to the information acquirer exceeds the preset time, the reply result that has received the confirmation returned by the information acquirer is determined. Of course, the preset value can be set as required.
Further, in this embodiment of the application, in order to avoid a situation that the information acquirer fails to complete the payment service after receiving the payment information, the server may determine the payment amount according to an amount payment manner corresponding to the stored information before sending the information to the information acquirer, freeze the payment amount of the information acquirer, and pay the frozen payment amount to the information provider when subsequently receiving the confirmed reply information returned by the information acquirer.
Specifically, the server may freeze the payment amount of the information acquirer by the same method as the fund freezing method in the prior art, which is not limited in this application. For example, the payment amount may be acquired by the server from the account of the information acquirer and temporarily stored in a preset account, and the information provider may be paid with the frozen payment amount from the preset account when the confirmed reply information is received. Alternatively, the server may send a freeze request to a third-party institution (e.g., a bank) corresponding to the account of the information acquirer, freeze the payment amount in the account of the information acquirer, and send transfer information to the third-party institution when receiving the confirmed reply information, so that the third-party institution pays the payment amount frozen in the account of the information acquirer to the information provider.
Through the service execution process shown in fig. 2, the server stores information issued by the information provider. When the server receives an acquisition request for the information sent by the information acquirer, the server may first determine the information according to the acquisition request and return the information to the information acquirer. And after receiving a reply result returned by the information acquirer, determining whether to allocate the resource of the information acquirer to the information provider according to the reply result. So that the information acquirer can return a confirmed reply result when determining that the acquired information meets the requirements of the information acquirer. Therefore, by the method provided by the embodiment of the application, the information acquirer can determine whether to pay the acquired information. The probability of payment for the acquired low-quality information by the information acquirer is reduced, and the user experience of the information acquirer is improved.
In addition, in the embodiment of the application, security in a service execution process and integrity in a data transmission process are ensured. The server may encrypt the network resource sent to the information acquirer. The information acquirer may encrypt the reply result when transmitting it to the server.
Specifically, when the information acquirer registers an account in the server, a key pair corresponding to the account may be created, and a public key in the key pair is sent to the server for storage. The server may store a correspondence of the account identification of the information acquirer and the public key. Then when the information acquirer sends the reply result to the server, the reply result may be signed by the private key of the key pair. And the server can check the signature according to the pre-stored public key of the information acquirer when receiving the reply result sent by the information acquirer. And after the check label passes, determining the reply result of the information acquirer. In addition, in the embodiment of the present application, when the information acquirer sends the acquisition request, the information acquirer can also sign the acquisition request through the private key of the key pair, and the server can also check the signature of the acquisition request when receiving the acquisition request sent by the information acquirer. That is to say, the information acquirer can carry out signature when communicating with the server, so that the server can carry out signature verification, and the application is not listed one by one.
In addition, in order to generally ensure the security of the key pair, and prevent potential security hazards due to the leakage of the key pair, the key pair is generally stored only in the terminal that created the key pair. Therefore, in the embodiment of the present application, the first terminal of the information acquirer may create and store the key pair corresponding to the identifier of the information acquirer, and the first terminal may send the public key to the server. The server may store therein a correspondence between the identifier of the information acquirer, the public key, and the device identifier of the first terminal.
Further, since the information acquirer may log in on multiple devices (that is, there may be multiple first terminals), and if the same key pair is shared among different devices, the key pair may be leaked, the information acquirer may create a corresponding key pair on each logged-in device, and send the public key to the server. That is, the identity of the information acquirer may correspond to multiple key pairs, and thus, multiple public keys corresponding to the information acquirer account identity may be stored in the server. Meanwhile, since the key pair is stored only in the device that created the key pair, the key pairs stored in different devices that correspond to the same identifier of the information acquirer are different. The server may then record the identity of the first terminal, i.e. the identity of the device, when it receives the public key sent by the first terminal. The server may store therein a correspondence between the identification of the information acquirer, the public key, and the identification of the device. As shown in table 1.
TABLE 1
Through the correspondence shown in table 1, it can be seen that account id a1 and account id B1 are stored in the server. The identifier of the same information acquirer may correspond to multiple public keys, and each public key corresponds to an identifier of one device. The server may first determine the identifier of the device that sent the request and the identifier of the information acquirer when receiving the acquisition request sent by the information acquirer. And then, the identifier of the equipment sending the request can be verified according to the corresponding relation between the stored identifier of the equipment and the identifier of the information acquirer. And when the verification is passed, the subsequent steps are executed.
In addition, when the verification fails, it may be determined that the information acquirer has not created the key pair on the device, and the server may further notify the information acquirer to create the key pair and return a corresponding public key.
Of course, the above authentication process may be regarded as an authentication process, and may be performed before the information is returned to the information acquirer in step S204. It should be noted that, in the verification process, only the correspondence between the account identifier of the information acquirer and the identifier of the device may be verified, and verification according to the public key is not required, that is, the acquisition request sent by the information acquirer may not carry a signature. When information is returned to the information acquirer in step S204, the information may be encrypted by using the public key corresponding to both the account identifier of the information acquirer and the identifier of the device, and then returned to the information acquirer.
In addition, in the embodiment of the application, in order to avoid malicious information providers from uploading low-quality UGC, the overall quality of network resources provided by the website is influenced. When receiving the information uploaded by the information provider, the server can also freeze the guaranteed amount corresponding to the information provided by the information provider. That is, the information provider may also pay a guarantee fee to guarantee the quality of the uploaded UGC.
Then, when the server receives a negative confirmation of the result of the reply sent by the information acquirer in step S206, the server may pay the frozen guaranteed amount to the information acquirer, or may pay the frozen guaranteed amount to a preset account. I.e. can be considered as deducting the guaranteed amount of money of the information provider.
Further, in order to avoid the malicious transmission of the denied reply result by the information obtaining party, the payment of the obtained information is maliciously refused. The server may periodically accumulate the number of times the information acquirer sends the negative reply result. And when receiving the response result denied by the information acquirer, firstly judging whether the number of times of the information acquirer for accumulatively sending the denied response result in the current period exceeds a preset threshold value, if so, judging that the information acquirer is a malicious user, paying the payment amount of the frozen information acquirer to the information provider, and if not, executing subsequent operation according to the response result. That is, any one of the information acquirers has an upper limit to send a negative reply result in each accumulation period. Thereby avoiding the malicious transmission of the repudiated reply result by the information acquisition party.
Further, when determining whether the information acquirer sends the denial response result maliciously, whether the ratio exceeds a preset ratio or not may be determined according to a ratio of the number of times of the received denial response result to the information to the number of times of sending the information, if so, it is determined that the quality of the information is too low, the information provider is not paid with the payment amount of the information acquirer, and if not, the information provider is paid with the payment amount of the information acquirer. Wherein, the preset proportion can be set according to the requirement.
Of course, a method similar to the user credit calculation method in the related art may be adopted, in which the credit score of each information acquirer is calculated, and only the acquisition request sent by the user whose credit score is higher than the preset threshold is responded, and so on. The method and the device do not limit which way is adopted to avoid the risk brought by the malicious sending of the rejected information by the information acquisition party.
It should be noted that all execution subjects of the steps of the method provided in the embodiments of the present application may be the same apparatus, or different apparatuses may also be used as execution subjects of the method. For example, the execution subject of step S202 and step S204 may be device 1, and the execution subject of step S206 may be device 2; for another example, the execution subject of step S202 may be device 1, and the execution subjects of step S204 and step S206 may be device 2; and so on. Thus, particular embodiments of the present subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may be advantageous.
Based on the service execution method shown in fig. 2, the embodiment of the present application further provides a service execution process of an information acquirer, as shown in fig. 4.
Fig. 4 is a service execution process provided in an embodiment of the present application, which specifically includes the following steps:
s302: the information acquisition direction sends an acquisition request aiming at the information issued by the information provider to the server;
s304: receiving the information returned by the server;
s306: and sending a reply result to the server so that the server determines whether to allocate the resource of the information acquirer to the information provider according to the reply result.
In this embodiment of the application, the service execution process is a service execution process executed by the information acquirer and corresponds to the service execution process shown in fig. 2, and a specific process may correspond to the process shown in fig. 2, which is not described herein again.
In step S306, the information obtaining party may send the reply result to the server after receiving the information returned by the server. Specifically, the information acquirer may acquire the reply page by accessing the server, and send the reply result to the server by selecting. Wherein the reply page may be as shown in figure 5. It can be seen that the reply page indicates that "whether to pay for information a" is the reply to information a, and includes keys for confirming payment and rejecting payment, and the information acquirer can return the reply result to the server by operating the keys.
Based on the service execution method shown in fig. 2, the embodiment of the present application further provides a schematic structural diagram of a service execution device, as shown in fig. 6.
Fig. 6 is a schematic structural diagram of a service execution device according to an embodiment of the present application, where the device includes:
a storage module 402, which stores information issued by an information provider;
a receiving module 404, configured to receive an acquisition request for the information sent by an information acquirer;
a sending module 406, configured to return the information to the information acquirer;
the allocating module 408 receives a reply result returned by the information acquirer, allocates the resource of the information acquirer to the information provider when the reply result is affirmative, and does not allocate the resource of the information acquirer when the reply result is negative.
The information is original content UGC of a user or occupational production content OGC, and the resource is money.
The storage module 402 receives and stores the information issued by the information provider and the amount payment method corresponding to the information, or the storage module 402 determines and stores the amount payment method corresponding to the received information.
The allocating module 408 determines a payment amount according to the amount payment method corresponding to the stored information, sends payment information to the information acquirer according to the payment amount, acquires the payment amount provided by the information acquirer according to the payment information, and pays the payment amount to the information provider.
The allocating module 408 determines a payment amount according to an amount payment method corresponding to the stored information before allocating the resource of the information acquirer, and freezes the payment amount of the information acquirer, and the allocating module 408 pays the frozen payment amount to the information provider when allocating the resource of the information acquirer.
The sending module 406 encrypts the information according to the pre-stored public key of the information acquirer and returns the encrypted information to the information acquirer.
The sending module 406 determines the device identifier and the account identifier of the information acquirer, performs identity authentication on the information acquirer according to the correspondence between the registered account identifier and the device identifier, and returns the information to the information acquirer when the identity authentication is passed.
The distribution module 408 receives the signed reply result returned by the information acquirer, and checks the signature according to the pre-stored public key of the information acquirer, so as to determine the reply result.
The allocating module 408 determines that the reply result returned by the information acquirer is received after the information acquirer is sent with the information, and the reply result returned by the information acquirer is not received within a preset time, or determines that the reply result returned by the information acquirer is received after the information acquirer is sent with the information, and the reply result returned by the information acquirer is not received within a preset time, and the reply result returned by the information acquirer is received.
The storage module 402 receives the information issued by the information provider and freezes the guarantee amount corresponding to the information provided by the information provider, and the allocation module 408 pays the frozen guarantee amount to the information acquirer or pays the frozen guarantee amount to a preset account when the answer result is negative.
Specifically, the service execution device may be located in a server of a website providing information, and the server may be a single device or a system composed of multiple devices, such as a distributed system.
Based on the service execution method shown in fig. 4, the embodiment of the present application further provides a schematic structural diagram of a service execution device of an information acquirer, as shown in fig. 7.
Fig. 7 is a schematic structural diagram of a service execution device according to an embodiment of the present application, where the device includes:
a first sending module 502, configured to send an acquisition request for information issued by an information provider to a server;
a receiving module 504, which receives the information returned by the server;
a second sending module 506, configured to send the reply result to the server, so that the server determines whether to allocate the resource of the service execution apparatus to the information provider according to the reply result.
The service execution device may be located in a terminal of the information obtaining party, where the terminal may be a mobile phone, a tablet computer, a personal computer, or the like.
Based on the service execution method shown in fig. 2, the embodiment of the present application further provides a server, as shown in fig. 8. The server stores information issued by an information provider, and comprises: one or more processors and memory, the memory storing a program and configured to perform, by the one or more processors:
the server receives an acquisition request aiming at the information sent by an information acquirer;
returning the information to the information acquirer;
and receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
Based on the service execution method shown in fig. 4, the embodiment of the present application further provides a terminal, as shown in fig. 9. The terminal includes: one or more processors and memory, the memory storing a program and configured to perform, by the one or more processors:
sending an acquisition request aiming at information issued by an information provider to a server;
receiving the information returned by the server;
and sending a reply result to the server so that the server determines whether to allocate the resource of the terminal to the information provider according to the reply result.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that 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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (26)
1. A service execution method, in which information issued by an information provider is stored in a server, the method comprising:
the server receives an acquisition request aiming at the information sent by an information acquirer;
returning the information to the information acquirer; the information is original user content UGC or occupational production content OGC;
and receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
2. The method of claim 1, the resource being an amount.
3. The method according to claim 2, wherein the server stores information issued by the information provider, and specifically comprises:
the server receives and stores the information issued by the information provider and the amount payment mode corresponding to the information; or
And the server determines and stores the payment mode of the amount corresponding to the received information.
4. The method of claim 3, wherein allocating the resource of the information acquirer specifically comprises:
determining the payment amount according to the amount payment mode corresponding to the stored information;
sending payment information to the information acquirer according to the payment amount;
and acquiring the payment amount provided by the information acquirer according to the payment information, and paying the payment amount to the information provider.
5. The method of claim 3, prior to allocating the information acquirer's resources, the method further comprising:
determining the payment amount according to the amount payment mode corresponding to the stored information;
freezing the payment amount of the information acquirer;
allocating the resource of the information acquirer specifically includes:
paying the frozen payment amount to the information provider.
6. The method according to claim 1, wherein returning the information to the information acquirer specifically comprises:
and according to the pre-stored public key of the information acquirer, encrypting the information and returning the information to the information acquirer.
7. The method according to claim 1, wherein returning the information to the information acquirer specifically comprises:
determining the equipment identification and the account identification of the information acquirer;
according to the corresponding relation between the registered account identification and the equipment identification, carrying out identity verification on the information acquirer;
and when the identity authentication is passed, returning the information to the information acquisition party.
8. The method as claimed in claim 1, wherein receiving the reply result returned by the information acquirer specifically includes:
receiving a signed reply result returned by the information acquirer;
and checking the signature according to a pre-stored public key of the information acquirer to determine the reply result.
9. The method as claimed in claim 1, wherein after sending the information to the information acquirer, the information acquirer is not configured to receive a reply result returned by the information acquirer within a preset time, and the information acquirer is configured to determine that the information acquirer returns a confirmed reply result; or
After the information is sent to the information acquirer, the reply result returned by the information acquirer is not received within the preset time, and the information acquirer is determined to return the denied reply result.
10. The method according to claim 2, wherein the server stores information issued by the information provider, and specifically comprises:
the server receives the information issued by the information provider and freezes the guaranteed amount corresponding to the information provided by the information provider;
when the answer result is negative, the method further comprises:
and paying the frozen guarantee amount to the information acquirer, or paying the frozen guarantee amount to a preset account.
11. The method according to claim 1, wherein the server further stores a resource allocation manner corresponding to the information, and the resource allocation manner includes: a billing period or a billing price.
12. The method according to claim 1, wherein when the time length for waiting for receiving the reply result returned by the information acquirer exceeds a preset time after the information acquirer is sent with the information, the server determines the ratio of the number of payments and the number of times of sending of the information according to the number of times of sending and the number of payments in the history record, and determines the reply result as confirmation when the ratio exceeds a preset value; the payment number represents the number of confirmed reply results received by the server for the information; the answer result is that the confirmation indicates that the payment is confirmed, and the answer result is that the denial indicates that the payment is refused.
13. A method of service execution, comprising:
the information acquisition direction sends an acquisition request aiming at the information issued by the information provider to the server; the server stores information issued by an information provider;
receiving the information returned by the server; the information is original user content UGC or occupational production content OGC;
and sending a reply result to the server so that the server determines whether to allocate the resource of the information acquirer to the information provider according to the reply result.
14. A service execution apparatus comprising:
the storage module stores information issued by the information provider; the information is original user content UGC or occupational production content OGC;
the receiving module is used for receiving an acquisition request aiming at the information sent by an information acquirer;
the sending module returns the information to the information acquisition party;
and the allocation module is used for receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
15. The apparatus of claim 14, the resource being an amount.
16. The apparatus of claim 15, wherein the storage module receives and stores the information issued by the information provider and the payment method corresponding to the information, or the storage module determines and stores the payment method corresponding to the received information.
17. The apparatus according to claim 16, wherein the allocation module determines a payment amount according to an amount payment method corresponding to the stored information, sends payment information to the information acquirer according to the payment amount, acquires the payment amount provided by the information acquirer according to the payment information, and pays the payment amount to the information provider.
18. The apparatus according to claim 16, wherein the allocating module determines a payment amount according to a payment method of an amount corresponding to the stored information before allocating the resource of the information acquirer, and freezes the payment amount of the information acquirer, and the allocating module pays the frozen payment amount to the information provider when allocating the resource of the information acquirer.
19. The apparatus according to claim 14, wherein the sending module encrypts the information according to a pre-stored public key of the information acquirer and returns the encrypted information to the information acquirer.
20. The apparatus according to claim 14, wherein the sending module determines a device identifier and an account identifier of the information acquirer, performs authentication on the information acquirer according to a correspondence between registered account identifiers and device identifiers, and returns the information to the information acquirer when the authentication is passed.
21. The apparatus according to claim 14, wherein the distribution module receives the signed reply result returned by the information acquirer, and verifies the signature according to a pre-stored public key of the information acquirer to determine the reply result.
22. The apparatus according to claim 14, wherein the allocating module determines that the response result returned by the information acquirer is received when the response result returned by the information acquirer is not received within a preset time after the information acquirer transmits the information, or determines that the response result returned by the information acquirer is received when the response result returned by the information acquirer is not received within a preset time after the information is transmitted to the information acquirer.
23. The apparatus according to claim 15, wherein the storage module receives information issued by the information provider and freezes a guarantee amount corresponding to the information provided by the information provider, and the allocation module pays the frozen guarantee amount to the information acquirer or pays the frozen guarantee amount to a preset account when a response result is negative.
24. A service execution apparatus comprising:
the first sending module is used for sending an acquisition request aiming at the information issued by the information provider to the server; the server stores information issued by an information provider; the information is original user content UGC or occupational production content OGC;
the receiving module is used for receiving the information returned by the server;
and the second sending module is used for sending a reply result to the server so that the server determines whether to allocate the resource of the service execution device to the information provider according to the reply result.
25. A server in which information issued by an information provider is stored, comprising: one or more processors and memory, the memory storing a program and configured to perform, by the one or more processors:
the server receives an acquisition request aiming at the information sent by an information acquirer;
returning the information to the information acquirer; the information is original user content UGC or occupational production content OGC;
and receiving a reply result returned by the information acquirer, allocating the resource of the information acquirer to the information provider when the reply result is a confirmation, and not allocating the resource of the information acquirer when the reply result is a denial.
26. A terminal, comprising: one or more processors and memory, the memory storing a program and configured to perform, by the one or more processors:
sending an acquisition request aiming at information issued by an information provider to a server; the server stores information issued by an information provider; the information is original user content UGC or occupational production content OGC;
receiving the information returned by the server;
and sending a reply result to the server so that the server determines whether to allocate the resource of the terminal to the information provider according to the reply result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110396572.6A CN113114678B (en) | 2017-07-03 | 2017-07-03 | Service execution method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710532385.XA CN107528822B (en) | 2017-07-03 | 2017-07-03 | Service execution method and device |
| CN202110396572.6A CN113114678B (en) | 2017-07-03 | 2017-07-03 | Service execution method and device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710532385.XA Division CN107528822B (en) | 2017-07-03 | 2017-07-03 | Service execution method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113114678A true CN113114678A (en) | 2021-07-13 |
| CN113114678B CN113114678B (en) | 2024-06-18 |
Family
ID=60748219
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110396572.6A Active CN113114678B (en) | 2017-07-03 | 2017-07-03 | Service execution method and device |
| CN201710532385.XA Active CN107528822B (en) | 2017-07-03 | 2017-07-03 | Service execution method and device |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710532385.XA Active CN107528822B (en) | 2017-07-03 | 2017-07-03 | Service execution method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN113114678B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110009320B (en) * | 2018-01-04 | 2024-04-16 | 财付通支付科技有限公司 | Resource conversion method, device, system, storage medium and computer equipment |
| CN110175915B (en) * | 2019-04-23 | 2021-04-06 | 创新先进技术有限公司 | Service execution result obtaining method and system based on block chain |
| US11062308B2 (en) | 2019-04-23 | 2021-07-13 | Advanced New Technologies Co., Ltd. | Service execution result obtaining method and system based on blockchain |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101246575A (en) * | 2008-01-31 | 2008-08-20 | 戚永德 | Credit buyer non-forced performance security post-paying transaction system and method |
| CN101369333A (en) * | 2007-08-17 | 2009-02-18 | 阿里巴巴集团控股有限公司 | Electronic commerce method, system and device suitable for traditional retail mode |
| CN101938364A (en) * | 2009-07-01 | 2011-01-05 | 华为技术有限公司 | Method, device and system for releasing original content of user to telecommunication system |
| CN104240102A (en) * | 2013-06-06 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Pushing method and system of virtual product |
| CN104574089A (en) * | 2015-01-13 | 2015-04-29 | 北京典精智慧科技有限公司 | Questioning and answering processing method and server |
| US20160140548A1 (en) * | 2014-11-13 | 2016-05-19 | Lg Cns Co., Ltd. | Method for performing non-repudiation, and payment managing server and user device therefor |
| CN105956904A (en) * | 2016-04-26 | 2016-09-21 | 武汉理工数字传播工程有限公司 | Digital reading appending package method, digital reading appending package system, and editing terminal |
| CN106790691A (en) * | 2017-02-20 | 2017-05-31 | 湖南云连天地网络科技有限公司 | A kind of information processing method and device |
| CN106776651A (en) * | 2015-11-24 | 2017-05-31 | 阿里巴巴集团控股有限公司 | The processing method and processing device of business dispute |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI266287B (en) * | 2000-08-18 | 2006-11-11 | Sony Corp | Communication system, communication apparatus, communication method, record medium, and program |
| US20080183551A1 (en) * | 2007-01-30 | 2008-07-31 | Microsoft Corporation | Transaction feedback mechanisms |
| CN101478568A (en) * | 2009-01-06 | 2009-07-08 | 杨洪 | Method for implementing mobile digital newspaper on handhold reading device |
| CN101697221A (en) * | 2009-09-18 | 2010-04-21 | 何国健 | Method for obtaining reading access to limited content of web site by purchasing web site products |
| US20120185355A1 (en) * | 2011-01-14 | 2012-07-19 | Suarez Corporation Industries | Social shopping apparatus, system and method |
| US20140164234A1 (en) * | 2012-12-12 | 2014-06-12 | Capital One Financial Corporation | Systems and methods for splitting a bill associated with a receipt |
| CN104463660A (en) * | 2014-12-31 | 2015-03-25 | 山东泰宝防伪技术产品有限公司 | Product personalized customization display system achieved through Internet and two-dimensional codes |
| CN106408278B (en) * | 2016-09-08 | 2021-09-24 | 北京星选科技有限公司 | Payment method and device |
| CN106447322A (en) * | 2016-09-30 | 2017-02-22 | 努比亚技术有限公司 | Mobile payment method and device |
| CN106446205A (en) * | 2016-10-01 | 2017-02-22 | 深圳市分享投融网络有限公司 | Internet-based method and device for forming paid knowledgea of expert into audio compilation album |
-
2017
- 2017-07-03 CN CN202110396572.6A patent/CN113114678B/en active Active
- 2017-07-03 CN CN201710532385.XA patent/CN107528822B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101369333A (en) * | 2007-08-17 | 2009-02-18 | 阿里巴巴集团控股有限公司 | Electronic commerce method, system and device suitable for traditional retail mode |
| CN101246575A (en) * | 2008-01-31 | 2008-08-20 | 戚永德 | Credit buyer non-forced performance security post-paying transaction system and method |
| CN101938364A (en) * | 2009-07-01 | 2011-01-05 | 华为技术有限公司 | Method, device and system for releasing original content of user to telecommunication system |
| CN104240102A (en) * | 2013-06-06 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Pushing method and system of virtual product |
| US20160140548A1 (en) * | 2014-11-13 | 2016-05-19 | Lg Cns Co., Ltd. | Method for performing non-repudiation, and payment managing server and user device therefor |
| CN104574089A (en) * | 2015-01-13 | 2015-04-29 | 北京典精智慧科技有限公司 | Questioning and answering processing method and server |
| CN106776651A (en) * | 2015-11-24 | 2017-05-31 | 阿里巴巴集团控股有限公司 | The processing method and processing device of business dispute |
| CN105956904A (en) * | 2016-04-26 | 2016-09-21 | 武汉理工数字传播工程有限公司 | Digital reading appending package method, digital reading appending package system, and editing terminal |
| CN106790691A (en) * | 2017-02-20 | 2017-05-31 | 湖南云连天地网络科技有限公司 | A kind of information processing method and device |
Non-Patent Citations (4)
| Title |
|---|
| 刘凯: ""内容付费平台的传播模式分析"", 《青年记者》 * |
| 刘凯: ""内容付费平台的传播模式分析"", 《青年记者》, 10 May 2017 (2017-05-10) * |
| 王传珍: ""知识付费奇点与未来"", 《互联网经济》 * |
| 王传珍: ""知识付费奇点与未来"", 《互联网经济》, 25 February 2017 (2017-02-25) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113114678B (en) | 2024-06-18 |
| CN107528822B (en) | 2021-03-05 |
| CN107528822A (en) | 2017-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107862215B (en) | Data storage method, data query method and device | |
| EP3968191B1 (en) | Trusted hardware-based identity management methods, apparatuses, and devices | |
| US20210312073A1 (en) | Data processing methods, apparatuses, and devices | |
| CN111899008B (en) | Resource transfer method, device, equipment and system | |
| CN108074024B (en) | Trusted data transmission method, device and system | |
| CN113837732A (en) | Internet resource transfer method, account transfer method and device | |
| CN107528822B (en) | Service execution method and device | |
| CN113821817B (en) | Data processing method, device, equipment and system based on block chain | |
| CN107070871B (en) | Identity verification method and device | |
| CN111784347B (en) | Resource transfer method and device | |
| CN112182506A (en) | Data compliance detection method, device and equipment | |
| US20200294124A1 (en) | Blockchain-based method, apparatus, and device | |
| CN114463110A (en) | Credit granting system and method based on block chain | |
| CN112100689B (en) | Trusted data processing method, device and equipment | |
| CN112990940B (en) | Enterprise authentication method and device | |
| CN110443291B (en) | Model training method, device and equipment | |
| CN111259430A (en) | Data processing method and device, electronic equipment and computer storage medium | |
| CN112434347B (en) | Rental business processing method, device, equipment and system | |
| CN114548965A (en) | Payment processing method and device | |
| CN113673844A (en) | Information feedback method, device and equipment | |
| CN107169761B (en) | Method and device for generating IC (integrated circuit) card security data | |
| CN111125211A (en) | Contract establishing method and device, computer readable medium and electronic equipment | |
| CN113327115B (en) | Rental business processing method, device, equipment and system | |
| CN112016915B (en) | Method and device for providing service for user | |
| US10742635B2 (en) | Multilevel sign-on |
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 |