WO2020173041A1 - 一种基于http协议的服务器、用户终端收款***及收款方法 - Google Patents

一种基于http协议的服务器、用户终端收款***及收款方法 Download PDF

Info

Publication number
WO2020173041A1
WO2020173041A1 PCT/CN2019/097047 CN2019097047W WO2020173041A1 WO 2020173041 A1 WO2020173041 A1 WO 2020173041A1 CN 2019097047 W CN2019097047 W CN 2019097047W WO 2020173041 A1 WO2020173041 A1 WO 2020173041A1
Authority
WO
WIPO (PCT)
Prior art keywords
collection
information
http
server
payment
Prior art date
Application number
PCT/CN2019/097047
Other languages
English (en)
French (fr)
Inventor
张海旻
Original Assignee
上海风汇网络科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 上海风汇网络科技有限公司 filed Critical 上海风汇网络科技有限公司
Priority to US17/432,106 priority Critical patent/US20220188783A1/en
Priority to EP19917056.4A priority patent/EP3933733A4/en
Publication of WO2020173041A1 publication Critical patent/WO2020173041A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • 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/04—Payment circuits
    • G06Q20/047—Payment circuits using payment protocols involving electronic receipts
    • 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/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • 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/12—Payment architectures specially adapted for electronic shopping systems
    • G06Q20/123—Shopping for digital content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers

Definitions

  • the present invention belongs to the technical field of electronic payment, and in particular relates to a server, user terminal payment system and payment method based on HTTP protocol
  • the current development direction of blockchain and digital currency (such as Bitcoin, etc.) mainly refers to bank or third-party payment, but it is difficult to obtain similar transmission efficiency and legal protection, which lacks practical application foundation and cannot truly reflect the block.
  • the value of chain and digital currency At the same time, anonymity also makes it difficult for digital currencies to obtain necessary legal support and supervision.
  • most third-party payment systems cannot transmit information such as websites and videos while transmitting value, which is basically an extension of the banking model.
  • online media and other services which currently use fixed-time or packaged content account package systems, and lack a payment method that can be accurate to a specific page or content, so that users spend a lot of money on meaningless content.
  • the need to register an account in order to browse a small amount of paid media content will waste a lot of time and expense, and will easily reduce consumption willingness.
  • the account package system will lead to the loss of a large number of fast-consuming user groups, and it is difficult to reflect the value of online media.
  • the technical purpose of the present invention is to provide a server, a user terminal collection system and a collection method based on the HTTP protocol, which can solve the problem of separate transmission of existing information and value and improve the financial function application of the HTTP protocol.
  • the technical solution of the present invention is:
  • an embodiment provides a server collection system based on the HTTP protocol, a collection message management server, a page management server, and a fund management server;
  • the collection message management server interacts and cooperates with the page management server and the fund management server;
  • the collection message management server is configured to receive an HTTP collection request message sent by a user, and identify collection information of the HTTP collection request message;
  • the collection message management server is further configured to schedule the page management server to obtain page content, and perform charging according to a charging method corresponding to the page content;
  • the collection message management server is further configured to generate an HTTP collection confirmation response message according to the page content, and feed back the HTTP collection confirmation response message to the user, so as to provide the user with the page content;
  • the collection message management server is also used to schedule the fund management server to perform a remittance operation to the user according to the charged amount and the collection information;
  • the collection information includes a collection object and a collection method
  • the collection information is set in the header field of the HTTP collection request message.
  • an embodiment provides a user terminal collection system based on HTTP protocol, including: a collection message management module, a page management module, and a fund management module;
  • the collection message management module interacts and cooperates with the page management module and the fund management module;
  • the collection message management module is configured to send an HTTP ordinary request message to the page server to obtain an HTTP collection response message, and to identify the collection information of the HTTP collection response message;
  • the receipt message management module is further configured to dispatch the fund management module to perform a remittance operation to the page server according to the receipt information, and generate an HTTP receipt confirmation request message according to the information of the remittance operation and send the HTTP Receipt confirmation request message to obtain HTTP normal response message with charged page content;
  • the collection message management module is further configured to schedule the page management module to display the charged page content according to the HTTP normal response message; wherein,
  • the collection information includes a collection object and a collection method
  • the payment information is set in the header field of the HTTP payment response message.
  • an embodiment provides a method for collecting money in a server collection system based on the HTTP protocol.
  • the server collection system includes a collection message management server, a page management server, and a fund management server. The method includes the following steps:
  • the collection message management server receives the HTTP collection request message sent by the user, and identifies the collection information of the HTTP collection request message;
  • A2 The collection message management server schedules the page management server to obtain page content, and the collection message management server performs charging according to the charging method corresponding to the page content;
  • the collection message management server generates the HTTP collection confirmation response message according to the page content, and feeds back the HTTP collection confirmation response message to the user, so as to provide the user with the page content;
  • step A4 is executed:
  • the collection message management server schedules the fund management server to perform a remittance operation to the user according to the charged amount and the collection information;
  • the collection information includes a collection object and a collection method; the collection information is set in the header field of the HTTP collection request message.
  • an embodiment provides a payment method for a payment collection message management server based on an HTTP protocol, which includes the following steps:
  • the collection message management server receives the HTTP collection request message sent by the user, and identifies the collection information of the HTTP collection request message;
  • the collection message management server sends a page scheduling instruction according to the HTTP collection request message to obtain page content
  • the collection message management server generates an HTTP collection confirmation response message according to the page content, and feeds back the HTTP collection confirmation response message to the user, so as to provide the user with the page content;
  • step B4 is executed:
  • the collection message management server performs charging according to the charging method corresponding to the page content
  • step B5 is executed:
  • the collection message management server sends a remittance scheduling instruction according to the charged amount and the collection information to realize the remittance operation to the user;
  • the collection information includes a collection object and a collection method; the collection information is set in the header field of the HTTP request message.
  • an embodiment provides a payment method for a user terminal payment system based on the HTTP protocol.
  • the user terminal payment system includes a payment message management module, a page management module, and a fund management module.
  • the collection method includes the following steps:
  • the collection message management module sends an HTTP ordinary request message to the page server to obtain an HTTP collection response message, and identify the collection information of the HTTP collection response message;
  • the receipt message management module dispatches the fund management module to perform a remittance operation to the page server according to the receipt information, and generates an HTTP receipt confirmation request message based on the remittance operation information and sends the HTTP receipt Payment confirmation request message to obtain HTTP normal response message with charged page content;
  • the collection message management module dispatches the page management module to display the charged page content according to the HTTP normal response message; wherein,
  • the collection information includes a collection object and a collection method; the collection information is set in the header field of the HTTP collection response message.
  • the present invention has the following advantages and positive effects due to the above technical scheme:
  • the present invention sets the collection information in the HTTP collection request message or the HTTP collection response message, and the HTTP protocol is combined with digital currency/electronic currency, so that the traditional HTTP protocol has financial functions such as collection.
  • the information is coordinated by the collection message management server, the page management server, and the fund management server. While the HTTP protocol transmits information, it also realizes the collection between the user and the page content provider, thus realizing the transfer of value and improving Financial function application of HTTP protocol;
  • the payment information of the present invention is set in the header field of the HTTP payment request message or the HTTP payment response message, and its location is identifiable, and it does not affect the normal information transmission and reading of the HTTP protocol. Will not cause any impact on the page content; at the same time, the information transfer process of the page content through the request message and the value transfer process of the page server or the user through the payment information in the request message are generally not involved in the information transfer process Value transfer process, so the information transfer process generally does not cause any delay due to value transfer; in some cases, even if the value transfer process is involved in the information transfer process, because the efficiency can be improved through technological improvements, such as the use of specific numbers Currency remittance, or digital/electronic currency third-party payment for instant remittance, so the information transmission process will not be significantly delayed due to the transmission of value, achieving the technical effect that the transmission of HTTP protocol information and value does not affect each other;
  • the payment information is directly provided by the user or the page server, and the user can directly realize the payment and payment without a special account.
  • the recipient of the HTTP payment request message or the HTTP payment response message can send any The visitor or the server makes barrier-free remittance, achieving the convenient and humanized technical effect of information and value transmission;
  • the present invention verifies the receipt information through the fund management server or the fund management module, ensuring the legitimacy and safety of the receipt information.
  • the database server or database module optimizes the receipt information that has passed the verification. Choose to enable users and/or servers to provide multiple collection information, increase the compatibility between the payer and the payee, and achieve the technical effects of optimized, humanized, and diversified collection methods;
  • the present invention puts the optimal collection information into the HTTP collection confirmation response message or the HTTP collection confirmation request message through the collection message management server to feed back the collection information to the user or the page server.
  • Users can also query related content in the database server or database module by sending query requests, achieving the humanized and diversified technical effects of information feedback;
  • the server collection system of the present invention converts the internal request from the fund management server with the external request from the network through the digital currency interactive server and the third-party digital/electronic currency interactive server to perform actual remittance or information verification, and can support multiple The remittance of two currencies achieves the technical effect of diversified remittance methods.
  • the conversion of internal and external requests achieves the cross-platform synchronous transmission of information and value; similarly, the user terminal collection system interacts through digital currency
  • the module, third-party digital/electronic currency interaction module converts internal requests from the fund management module to external requests from the network to perform actual remittance or information verification. It can support remittances in multiple currencies and achieve a diversified remittance technology. Effect, at the same time, the conversion of internal requests and external requests achieves the cross-platform synchronous transmission of information and value;
  • the present invention uses the payment switch and the payment switch to control the on and off of the generation and identification functions of the payment information, so as to control the switch control of the value transmission in the HTTP payment request message or the HTTP payment response message. Achieved a humanized technical effect.
  • FIG. 1 is a schematic diagram of the architecture of a collection system for a server and a user terminal based on the HTTP protocol of the present invention
  • FIG. 2 is a schematic diagram of an HTTP payment request message of a server payment collection system based on the HTTP protocol of the present invention
  • FIG. 3 is a schematic diagram of an HTTP payment confirmation response message of a server payment collection system based on the HTTP protocol of the present invention
  • FIG. 4 is a schematic diagram of an HTTP payment response message of the user terminal payment system based on the HTTP protocol of the present invention
  • FIG. 5 is a schematic diagram of an HTTP payment confirmation request message of a user terminal payment system based on the HTTP protocol of the present invention
  • FIG. 6 is a schematic flowchart of an embodiment of a collection method of a server collection system based on HTTP protocol according to the present invention
  • FIG. 7 is a schematic flowchart of another embodiment of a collection method of a server collection system based on HTTP protocol according to the present invention.
  • FIG. 8 is a schematic flowchart of an embodiment of a payment method of a user terminal payment system based on HTTP protocol according to the present invention.
  • FIG. 9 is a schematic flowchart of another embodiment of a collection method of a user terminal collection system based on the HTTP protocol of the present invention.
  • Digital/encrypted currency Decentralized digital currency or pass, generally produced through “mining” work, such as Bitcoin and Litecoin. Hereinafter referred to as "digital currency”.
  • Electronic money electronic traditional/legal currency or tokens and related payment services, such as paypal and alipay and their virtualized electronic money.
  • HTTP payment request message HTTP request message, whose header contains payment information for the server to confirm.
  • HTTP Receipt Confirmation Response Message HTTP response message, whose header contains the receipt information of the remittance operation receipt confirmation, to be fed back to the user.
  • HTTP payment response message HTTP response message, whose header contains payment information for user terminal confirmation.
  • HTTP Receipt Confirmation Request Message HTTP request message, whose header contains the receipt information of the remittance operation receipt confirmation, to be fed back to the page server.
  • HTTP ordinary request message ordinary HTTP request message whose header does not contain payment information.
  • HTTP ordinary response message ordinary HTTP response message, without the information of the payment method confirmed by the server.
  • the HTTP request message is generally sent by the user terminal to the server
  • the HTTP response message is generally returned by the server to the user terminal.
  • the user terminal sends a collection request: the user terminal sends an "HTTP collection request message" to the server, and the server responds with an "HTTP collection confirmation response message" to the user terminal;
  • the server sends a collection request: the user terminal sends an "HTTP request message" to the server, which is generally a normal request.
  • the server sends an "HTTP collection response message” to the user terminal, and the user terminal sends an "HTTP collection confirmation request message” to the server.
  • HTTP protocol refers to: Hypertext Transfer Protocol (HTTP) and related extended protocols, such as Hypertext Transfer Security Protocol (HTTPS).
  • HTTP Hypertext Transfer Protocol
  • HTTPS Hypertext Transfer Security Protocol
  • this embodiment provides a server collection system based on HTTP protocol, including: collection message management server, page management server, and fund management server;
  • the collection message management server interacts and works with the page management server and the fund management server;
  • the collection message management server is used to receive the HTTP collection request message sent by the user, and identify the collection information of the HTTP collection request message;
  • the collection message management server is also used to schedule the page management server to obtain the page content, and perform charging according to the charging method corresponding to the page content;
  • the collection message management server is also used to generate an HTTP collection confirmation response message according to the page content, and feed back the HTTP collection confirmation response message to the user to provide the user with the page content;
  • the receipt message management server is also used to dispatch the fund management server to perform remittance operations to users according to the billed amount and receipt information; among them,
  • the collection information includes the recipient and the method of collection
  • the collection information is set in the header field of the HTTP collection request message.
  • the traditional HTTP request message and HTTP response message do not have the Pay-To field circled in Figures 2 and 3, but in this embodiment, the traditional HTTP request message and HTTP response
  • the message sets the Pay-To field circled in Figure 2 and Figure 3. This field is a newly added field after the HTTP protocol is integrated with the currency protocol.
  • the Pay-To field in Figure 2 is used to collect payments, and the Pay-To field in Figure 3
  • the -To field is used to feed back information to realize the synchronization of information transmission and value transmission.
  • the circled Pay-To field is set in the header field of the HTTP request message or HTTP response message.
  • "//” is used to distinguish the complete “Pay-To” header field, so that multiple "Pay-To” header fields provide different payment methods for the server to choose, and the "//" character itself does not belong to "Pay-To” header field.
  • "Confirmed” indicates that the payment information has been confirmed, and is generally located in the HTTP payment confirmation request message or the HTTP payment confirmation response message.
  • the collection information of this embodiment is set in the header field of the HTTP collection request message or the HTTP collection confirmation response message, and its position is identifiable, and it does not affect the normal information transmission and reading of the HTTP protocol. It will have any impact on the content of the page; at the same time, the information transmission process of the page content is carried out through the request message and the value transmission process of the payment collection from the page server or the user through the payment information in the request message.
  • the information transmission process generally does not involve value Because of the transfer process, the information transfer process generally does not cause any delay due to the transfer of value; in some cases, even if the value transfer process is involved in the information transfer process, because the efficiency can be improved through technical improvements, such as the use of specific digital currencies Remittance, or digital/electronic currency third-party payment of instant remittance, so the information transmission process will not be significantly delayed due to the transmission of value, achieving the technical effect that the transmission of HTTP protocol information and value does not affect each other.
  • the content of the page can be text, picture, audio, video, file, web page, etc., content that can be delivered through the HTTP protocol.
  • the payment information is provided by the user and can be input by the user terminal.
  • the user terminal can be a browser, media player, reader, and other information delivery terminals.
  • the user terminal can also be a mobile phone, tablet, or PC with HTTP protocol function. And other equipment.
  • the collection information includes the recipient of the payment and the method of payment.
  • the recipient of the payment is the payment address or the payment account.
  • the payment address can be Bitcoin, Litecoin, etc.
  • the payment account can be paypal and alipay. Wait for the account number, and the payment information carries the service provider information of the account, such as paypal, alipay, or bitpay.
  • the collection information also includes the collection unit, such as Renminbi (CNY), U.S. dollar (USD), Bitcoin (BTC) or Litecoin (LTC).
  • the collection information is directly provided by the user, and the user can directly realize collection and payment without a special account.
  • the recipient of the HTTP collection request message can make a barrier-free remittance to any visitor, achieving information and value Deliver convenient and user-friendly technical effects.
  • the collection message management server is also used to dispatch the fund management server to verify the availability of the collection information.
  • the fund management server verifies the payment information, which ensures the legality and security of the payment information.
  • this implementation also includes a database server, which is used to store or update collection information, billing methods, and collection priority; the database server interacts with the collection message management server and the fund management server respectively,
  • the collection message management server is also used to schedule the database server to select the collection information according to the priority of collection, and determine an optimal collection information as the remittance method for the remittance operation; among them, the optimal collection information is the available collection information Among them, the collection information with the highest priority of the collection object and the highest priority of the collection method.
  • the collection information contains multiple collection objects, multiple collection methods, and multiple collection units.
  • the best collection information can be selected through usability verification and collection priority.
  • the collection priority includes the priority of the recipient, the priority of the collection method, and further, the priority of the collection unit, which can be determined in the optimal collection information according to the priority of the collection unit The best collection unit.
  • the payment priority can be set by the user through the user terminal.
  • the billing method can be in various forms, such as the number of clicks, behavior, stay time, access time, page type, and reward method, etc.
  • the billing method is set by the provider of the page content.
  • the remittance operation can be performed automatically through scripts, digital currency agreements, or interaction with third-party institutions.
  • the method can be a unified remittance at a fixed time, such as once a day or once a week.
  • the remittance is specifically based on a specific billing method.
  • the server can set the minimum remittance amount, etc.
  • remittances can be made using mixed currency or strong anonymous currency, thereby reducing the risk of leakage of the amount of the HTTP server and the recipient's digital currency address.
  • This embodiment uses the fund management server to verify the legality and security of the payment information.
  • the database server or database module is used to make the best selection of the verified payment information so that the user and/or server can provide
  • a variety of payment information increases the compatibility between the payer and the receiver, and achieves the technical effects of optimization, humanization, and diversification of payment methods.
  • the collection message management server is also used to put the optimal collection information into the header of the page content to provide feedback to the user.
  • the database server is also used to store billing and remittance detailed records; the collection message management server is also used to receive query requests sent by users, and dispatch the fund management server to effectively verify the information requested by the query.
  • the collection message management server dispatches the page management server to obtain the page content and dispatches the database server to obtain the query content, and generates the query result based on the page content and the query content to feed back to the user.
  • the collection message management server puts the optimal collection information into the header of the page content to feedback the collection related information to the user.
  • the user can also send a query request through the user terminal to query the database server.
  • the relevant content has achieved the humanized and diversified technical effects of information feedback.
  • this embodiment also includes an internal and external network interface.
  • the internal and external network interfaces include a digital currency interactive server and a third-party digital/electronic currency interactive server; the digital currency interactive server and the third-party digital/electronic currency interactive server respectively and
  • the fund management server interacts to convert internal requests from the fund management server to external requests from the network to perform actual remittance or information verification.
  • the digital currency interactive server is a server that runs a digital currency service program
  • the third-party digital/electronic currency interactive server is a server that supports local or third-party interfaces.
  • the server collection system of this embodiment converts the internal request from the fund management server with the external request from the network through the digital currency interactive server and the third-party digital/electronic currency interactive server to perform actual remittance or information verification, and can support a variety of Currency remittance has achieved the technical effect of diversified remittance methods.
  • the conversion of internal and external requests has achieved the cross-platform synchronous transmission of information and value.
  • this embodiment also includes a payment switch and/or a payment switch.
  • the payment switch is used to control the opening and closing of the recognition function of the payment information to realize the control of the remittance operation, and the payment switch is used to control the sending to the user. Whether to generate payment information in the HTTP response message to achieve the control of the payment to the user.
  • the server when the payment switch is turned on, the server can identify the payment information of the HTTP payment request message, so that the server can provide page content, charge, and remit money to the user according to the situation.
  • the server When the payment switch is turned off, the server shields the payment information in the HTTP payment request message, so that the server can handle it as usual.
  • the HTTP response message sent by the server collection system will contain the collection information, that is, the HTTP collection response message, so that the user terminal can identify the collection information of the HTTP collection response message and enable The user terminal can remit money according to the situation.
  • the HTTP response message sent by the server will not contain the payment information, that is, the HTTP general response message, so that the user terminal can handle it as usual.
  • the payment switch and/or the payment switch are used to control the switch control of the value transmission in the HTTP request message, which achieves the humanized technical effect.
  • this embodiment further includes an HTTP server extension module, and the collection message management module loads the HTTP server extension module to identify the HTTP request message with collection information.
  • the HTTP server extension module is loaded by the collection message management module to identify the HTTP request message with collection information, which realizes the expansion of the general server and achieves the technical effect of wide application range and low cost.
  • HTTP communications containing payment information between the user terminal and the server must be encrypted and transmitted, for example, via HTTPS.
  • this embodiment enables a cross-platform model of “revenue from watching ads, no ads without paying”, which can solve the problem of low advertising fund utilization and low advertising benefits.
  • the user can choose to obtain digital/electronic currency revenue by watching advertisements, so that they can truly find products of interest; or choose a mode with no advertisements and no revenue, so that they can use the website without interference.
  • Due to the cross-platform nature of digital currency users do not need to register for an account, and only need a suitable browser to obtain revenue through browsing on compatible websites. Therefore, users have a high degree of freedom and choice. For companies, using this model can directly invest advertising funds to the market and end users, thereby reducing intermediate costs and obtaining higher publicity effects and user enthusiasm.
  • HTTP can not only transmit HTML and other website content, but also directly transmit images or files and other data
  • the billing scope of the server is not limited to HTML and other web pages, and it is also applicable to all interactions via HTTP protocol.
  • the content of the file can achieve a good file sharing effect and publicity effect.
  • this example provides another user terminal collection system based on the HTTP protocol.
  • the difference from Embodiment 1 is that the payment information in this example is sent by the server, and the payment confirmation information is sent by the user terminal and the money is sent.
  • the system structure of this embodiment is similar to that of Embodiment 1, including: a collection message management module, a page management module, and a fund management module;
  • the collection message management module interacts and works with the page management module and the fund management module;
  • the collection message management module is used to send an HTTP ordinary request message to the page server to obtain the HTTP collection response message and identify the collection information of the HTTP collection response message;
  • the receipt message management module is also used to dispatch the fund management module to perform a remittance operation to the page server according to the receipt information, and generate an HTTP receipt confirmation request message and send an HTTP receipt confirmation request message according to the information of the remittance operation, so as to obtain charges HTTP general response message of the page content;
  • the collection message management module is also used to schedule the page management module to display the charged page content according to the HTTP normal response message; among them,
  • the collection information includes the recipient and the method of collection
  • the payment information is set in the header field of the HTTP payment response message.
  • the Pay-To field in this embodiment is based on Embodiment 1.
  • the difference from Embodiment 1 is that the Pay-To field in this embodiment is newly added with "amount" and "transaction number" information.
  • the Pay-To field circled in Figure 4 and Figure 5, the Pay-To field in Figure 4 is used to collect payments, and the Pay-To field in Figure 5 is used to feed back information to achieve synchronization of information transmission and value transmission.
  • the circled Pay-To field is set in the header field of the HTTP response message or HTTP request message.
  • the payment information format in the HTTP response message and the HTTP request message may be:
  • the collection information of this embodiment is set in the header field of the HTTP response message, and its position is identifiable, and it does not affect the normal information transmission and reading of the HTTP protocol, and will not cause any impact on the page content.
  • the efficiency can be improved through technical improvements, such as Special digital currency remittances, or digital/electronic currency third-party payments for instant remittances are used, so the information transmission process will not be significantly delayed due to the transmission of value, and the technical effect that the transmission of information and value in the HTTP protocol does not affect each other is achieved.
  • the content of the page can be text, picture, audio, video, file, web page, etc., content that can be delivered through the HTTP protocol.
  • the collection information is provided by the server and can be set by the server operator.
  • the user terminal can be a browser, media player, reader, and other information delivery terminals.
  • the user terminal can also be a mobile phone, tablet, or tablet with HTTP protocol function. PC and other equipment.
  • the receiving information includes the receiving object and the receiving method.
  • the receiving object is the receiving address or the receiving account.
  • the receiving address can be Bitcoin, Litecoin, etc.
  • the receiving account can be paypal and alipay. Waiting for an account, the receiving account carries the service provider information of the account, such as paypal, alipay, or bitpay.
  • the collection information also includes the collection unit, such as Renminbi (CNY), U.S. dollar (USD), Bitcoin (BTC) or Litecoin (LTC).
  • the payment information is directly provided by the server, and the user can directly realize payment to the content provider without a special account.
  • the recipient user of the HTTP response message can make a barrier-free remittance to any content provider. Convenience of value transmission and humanized technical effect.
  • the user terminal collection message management module is also used to dispatch the fund management module to verify the availability of the collection information.
  • the payment information is verified through the fund management module, which ensures the legality and safety of the payment information.
  • this implementation also includes a user terminal database module, which is used to store or update remittance records and remittance priority; the database module interacts with the collection message management module and the fund management module respectively, and the collection message management The module is also used to schedule the database module to select the remittance information according to the remittance priority, and determine an optimal remittance information as the remittance method of the remittance operation; among them, the optimal remittance information is the remittance object of the available remittance information The payment information with the highest priority and the highest priority of the payment method.
  • a user terminal database module which is used to store or update remittance records and remittance priority
  • the database module interacts with the collection message management module and the fund management module respectively, and the collection message management
  • the module is also used to schedule the database module to select the remittance information according to the remittance priority, and determine an optimal remittance information as the remit
  • the collection information contains multiple collection objects, multiple collection methods, and multiple collection units.
  • the best collection information can be selected through usability verification and collection priority.
  • the collection priority includes the priority of the recipient, the priority of the collection method, and further, the priority of the collection unit, which can be determined in the optimal collection information according to the priority of the collection unit The best collection unit.
  • the payment priority can be set by the service provider.
  • the remittance operation can be automatically executed through scripts, digital currency protocols, or interaction with third-party institutions, and the method can be to remit according to the requested amount after receiving the HTTP collection response message and before generating the HTTP collection confirmation request message , In order to prevent a large number of small remittances, users can set a minimum remittance amount, etc.
  • remittances can be made using mixed currency or strong anonymity, thereby reducing the risk of leakage of the digital currency address of the user and the payee.
  • the server can provide a variety of payment information, which increases the compatibility between the payer and the payee, and achieves the optimization and optimization of the payment collection.
  • the database module is also used for querying remittance records
  • the collection message management module is used for receiving query requests sent by users
  • the funds management module is dispatched to effectively verify the information requested by the query based on the effective query request.
  • the collection message management module dispatches the database module to obtain the query content, and generates the query result according to the query content and feeds it back to the user.
  • the collection message management module puts the optimal collection information into the header of the HTTP collection confirmation request message.
  • the collection message management module puts the optimal collection information into the header of the HTTP request message to feed back the collection related information to the server.
  • the user can also query the database server in the database module. Inquiry about relevant content has achieved the humanized and diversified technical effect of information feedback.
  • this embodiment also includes an internal and external network interface.
  • the internal and external network interface includes a digital currency interaction module and a third-party digital/electronic currency interaction module; the digital currency interaction module and the third-party digital/electronic currency interaction module respectively and
  • the fund management module interacts to convert the internal request from the fund management module to the external request from the network to perform actual remittance or information verification.
  • the digital currency interaction module is a module that supports digital currency protocols
  • the third-party digital/electronic currency interaction server is a module that supports third-party interfaces.
  • This embodiment uses the digital currency interaction module and the third-party digital/electronic currency interaction module to convert the internal request from the fund management module and the external request from the network to perform actual remittance or information verification, which can support multiple currency remittances.
  • the technical effects of diversified remittance methods are achieved.
  • the conversion of internal requests and external requests has achieved cross-platform synchronous transmission of information and value.
  • this embodiment also includes the internal and external network interfaces on the server side.
  • the internal and external network interfaces include a digital currency interactive server and a third-party digital/electronic currency interactive device; its functions and interaction methods are the same as those in the first embodiment or this example.
  • the user terminal is similar.
  • the user terminal payment system also includes a payment switch and/or a payment switch.
  • the payment switch is used to control the opening and closing of the recognition function of the payment information to control the remittance operation.
  • the payment switch is used to control the direction Whether to place payment information in the HTTP request message sent by the page server to achieve control of the payment to the page server.
  • the user terminal when the payment switch is turned on, after receiving the HTTP payment response message sent by the server, the user terminal will send the payment and send the HTTP payment confirmation request message to the server, so that the server can provide page content according to the situation.
  • the payment switch is turned off, after receiving the HTTP payment response message sent by the server, the user terminal will ignore the payment information in it, and send the HTTP general request message to the server as appropriate, so that the server can handle it as usual.
  • the HTTP request message sent by the user terminal will contain payment information, that is, the HTTP payment request message, so that the server can identify the payment information of the HTTP payment request message and enable the server to press
  • the situation provides page content, billing and remittance to users.
  • the HTTP request message sent by the user terminal will not contain the payment information, that is, the HTTP ordinary request message, so that the server can handle it in a normal situation.
  • the payment switch and/or the payment switch are used to control the switch control of the value transmission in the HTTP response message, which achieves the humanized technical effect.
  • this embodiment further includes an HTTP server extension module, and the server receipt message management module loads the HTTP server extension module to identify the HTTP request message with receipt confirmation information.
  • the HTTP server extension module is loaded by the server payment message management module to identify the HTTP request message with payment confirmation information, which realizes the expansion of general equipment terminals and achieves the technical effect of wide application range and low cost.
  • the collection message management module of the user terminal is also used to process the HTTP response message, such as prompting the user through a message window or status icon to feed back abnormal information or payment information.
  • the user terminal performs corresponding processing according to the received HTTP response message, such as displaying a web page, prompting the user, or performing abnormal handling, etc.
  • Some possible abnormal situations such as: no response for a long time after sending an HTTP payment confirmation request message to the server , Or return an HTTP exception message (such as 404 Page not found).
  • HTTP can not only transmit HTML and other website content, but also directly transmit images or files and other data
  • the prepayment range of the server is not limited to HTML and other web pages, and it is also applicable to all interactions via HTTP protocol.
  • the content of the file can achieve a good file sharing effect and publicity effect.
  • this embodiment provides a collection method of a server collection system based on HTTP protocol.
  • the server collection system includes a collection message management server, a page management server, a fund management server, and a collection method It includes the following steps:
  • the collection message management server receives the HTTP collection request message sent by the user, and identifies the collection information of the HTTP collection request message;
  • A2 The collection message management server dispatches the page management server to obtain the page content, and the collection message management server performs charging according to the charging method corresponding to the page content;
  • the collection message management server generates an HTTP collection confirmation response message according to the page content, and feeds back the HTTP collection confirmation response message to the user to provide the user with the page content;
  • step A4 executes:
  • the receipt message management server dispatches the fund management server to perform remittance operations to the user according to the billed amount and receipt information; among them,
  • the collection information includes the recipient and the collection method; the collection information is set in the header field of the HTTP collection request message.
  • step A2 while the collection message management server schedules the page management server to obtain page content, the collection message management server also schedules the fund management server to verify the availability of the collection information and obtain available collections. information.
  • the server collection system also includes a database server; in step A2 of the collection method, after obtaining available collection information, the collection message management server schedules the database server according to the collection priority in the database server Select the payment information, and determine an optimal payment information as the remittance method for the remittance operation; among them, the optimal payment information is the available payment information that has the highest priority of the recipient and the highest priority of the payment method Payment information.
  • the receipt information is verified by the fund management server to ensure the legitimacy and safety of the receipt information.
  • the database server is used to make the best choice for the receipt information that has passed the verification, so that the user can provide multiple receipts
  • the payment information increases the compatibility between the payer and the payee, and achieves the technical effects of optimization, humanization, and diversification of payment methods.
  • the collection message management server After determining an optimal collection information, the collection message management server puts the optimal collection information in the header of the page content.
  • the collection message management server puts the optimal collection information into the header of the page content to feedback the collection related information to the user.
  • the user can also send a query request through the user terminal to query the database server.
  • the relevant content has achieved the humanized and diversified technical effects of information feedback.
  • step A5 is further included after step A4: the fund management server receives the result of the remittance operation, and sends the result to the database server for storage.
  • the server payment collection system also includes an internal and external network interface, which includes a digital currency interactive server and a third-party digital/electronic currency interactive server; step A4 of the payment method specifically includes the following steps:
  • the fund management server receives the remittance scheduling instruction from the collection message management server;
  • A42 The fund management server dispatches the database server to obtain the billed amount and optimal collection information
  • the fund management server sends an internal request to the digital currency interactive server or the third-party digital/electronic currency interactive server;
  • A44 The digital currency interactive server or the third-party digital/electronic currency interactive server converts internal requests into external requests to perform remittance operations.
  • This embodiment uses a digital currency interactive server and a third-party digital/electronic currency interactive server to convert internal requests from the fund management server into external requests to perform actual remittances, which can support multi-currency remittances and achieve a technology of diversified remittance methods The effect, at the same time, the conversion of internal requests and external requests has achieved the cross-platform synchronous transmission of information and value.
  • the server collection system further includes a payment switch; in step A1 of the collection method, the process of identifying the collection information of the HTTP collection request message specifically includes the following steps:
  • the payment switch is used to control the switch control of the value transmission in the HTTP request message, which achieves the humanized technical effect.
  • this embodiment provides a collection method of a collection message management server based on HTTP protocol, which includes the following steps:
  • the collection message management server receives the HTTP collection request message sent by the user, and identifies the collection information of the HTTP collection request message;
  • the collection message management server sends a page scheduling instruction according to the HTTP collection request message to obtain the page content
  • the collection message management server generates an HTTP collection confirmation response message according to the page content, and feeds back the HTTP collection confirmation response message to the user to provide the user with the page content;
  • step B4 is executed:
  • the collection message management server performs charging according to the charging method corresponding to the page content
  • step B5 is executed:
  • the receipt message management server sends remittance scheduling instructions according to the billed amount and receipt information to realize the remittance operation to the user; among them,
  • the payment information includes the payment object and the payment method; the payment information is set in the header field of the HTTP request message.
  • the collection information is set in the HTTP request message, and the HTTP protocol is combined with digital currency/electronic currency, so that the traditional HTTP protocol has financial functions such as collection, and the HTTP protocol transmits information while also realizing the user to the page content
  • the provider collects money, thereby realizing the transfer of value and improving the financial function application of the HTTP protocol;
  • the collection information of this embodiment is set in the header field of the HTTP request message, and its location is identifiable, and it does not affect the normal information transmission and reading of the HTTP protocol, and will not cause any impact on the page content.
  • the value transfer process is not involved in the information transfer process, so the information transfer process will not be affected by the value transfer. Any delay occurs, and the technical effect that the transmission of HTTP protocol information and value does not affect each other is achieved;
  • the collection information is directly provided by the user, and the user can directly realize the collection without a special account.
  • the requester of the HTTP request message can make a barrier-free remittance to any visitor, achieving the convenience of information and value transfer. Humanized technical effect.
  • this embodiment provides a method for collecting money in a client-side money-collection system based on the HTTP protocol.
  • the client-side money-collection system includes a collection message management module, a page management module, and a fund management module.
  • the method includes the following steps:
  • the collection message management module sends an HTTP ordinary request message to the page server to obtain the HTTP collection response message and identify the collection information of the HTTP collection response message;
  • the receipt message management module dispatches the fund management module to execute the remittance operation to the page server according to the receipt information, and generates the HTTP receipt confirmation request message and sends the HTTP receipt confirmation request message according to the receipt information to obtain the fee HTTP normal response message for page content;
  • the collection message management module dispatches the page management module to display the charged page content according to the HTTP normal response message; among them,
  • the payment information includes the recipient and the payment method; the payment information is set in the header field of the HTTP payment response message.
  • the collection message management module before the remittance operation is performed, the collection message management module also dispatches the fund management module to verify the availability of the collection information and obtain available collection information.
  • the client payment collection system also includes a database module; in step C2 of the payment method, after obtaining the available payment information and before the remittance operation is performed, the payment message management module dispatches the database module according to the database module Select the remittance information in the remittance priority level, and determine an optimal remittance information as the remittance method for the remittance operation; among them, the optimal remittance information is the available remittance information that has the highest priority and the recipient of the payment. The payment information with the highest priority of the method.
  • the payment information is verified by the fund management module, which guarantees the legality and security of the payment information.
  • the database module is used to make the best selection of the verified payment information, so that the user can provide a variety of receipts.
  • the payment information increases the compatibility between the payer and the payee, and achieves the technical effects of optimization, humanization, and diversification of payment methods.
  • the client-side payment collection system also includes an internal and external network interface, which includes a digital currency interaction module and a third-party digital/electronic currency interaction module;
  • the fund management module of the collection method specifically includes the following steps:
  • the fund management module receives the remittance scheduling instruction of the collection message management module
  • the fund management module dispatches the database module to obtain the remittance amount of the payment information and the optimal payment information;
  • the fund management module sends an internal request to the digital currency interaction module or the third-party digital/electronic currency interaction module;
  • D4 The digital currency interaction module or third-party digital/electronic currency interaction module converts internal requests into external requests to perform remittance operations.
  • This embodiment uses a digital currency interaction module and a third-party digital/electronic currency interaction module to convert internal requests from the fund management module into external requests to perform actual remittances, which can support multi-currency remittances, and achieves the technology of diversified remittance methods The effect, at the same time, the conversion of internal requests and external requests has achieved the cross-platform synchronous transmission of information and value.
  • the client payment collection system further includes a payment switch; in step B1 of the payment method, the process of identifying payment information in the HTTP payment response message specifically includes the following steps:
  • the payment switch is used to control the switch control of the value transmission in the HTTP response message, which achieves the humanized technical effect.
  • this embodiment uses a browser as the user terminal payment system, combined with the server payment system, to explain the execution process of the system and method of the foregoing embodiment:
  • the user terminal collects money from the server:
  • the user sets the payment information in the browser
  • the browser verifies the correctness of related settings, such as the validity of digital currency addresses (for example, through Bitcoin-cli commands such as validateaddress);
  • the page will be updated according to the status of the "Receive" button on the main interface of the browser:
  • the page refresh process is executed to handle the situation of changing the state of the payment button when browsing the web;
  • the browser When the user opens the web page, the browser will send an HTTP payment request message to the server at this time, and the payment method contained in it has priority, for example, it gradually decreases from top to bottom;
  • the server will return an HTTP normal response message; if the server supports the collection request, it will obtain all the collection method information through the HTTP collection request message header;
  • the server If the server accepts one or more requested payment methods, it generates an HTTP payment confirmation response message, which contains an acceptable payment method, which has the highest priority in the HTTP payment request message; if If the server does not accept any payment method, it will generate a normal HTTP response message;
  • the server is billed according to the situation, such as the number of clicks, behaviors, stay time, access time, page type and reward method, etc., and associates the relevant information with the payment method (address/account + unit, etc.) in the HTTP payment confirmation response message ;
  • the server provides the required content according to the situation, such as web page HTML code or binary file, etc., and puts it into the aforementioned generated HTTP response message.
  • the server returns the generated HTTP response message to the browser. Since the process of generating the response message does not involve remittance, the server's response will not have any delay.
  • the user's browser performs corresponding processing according to the received HTTP response message, such as displaying a web page, prompting the user, or performing exception handling.
  • Some possible abnormal situations are as follows: the received is an HTTP payment confirmation response message, but the payment method in the response message is not one of the payment methods in the request message; there is no response for a long time after sending the HTTP payment request message to the server , Or return an HTTP exception message (such as 404 Page not found).
  • the browser When the user opens the webpage, the browser will send a normal HTTP request message to the server;
  • the server generates an HTTP general response message
  • the server provides the required content according to the situation, such as web page HTML code or binary file, etc., and puts it into the generated HTTP ordinary response message;
  • the server returns the generated HTTP response message to the browser
  • the user's browser performs corresponding processing according to the received HTTP response message, such as prompting the user or performing exception handling.
  • Some possible abnormal situations are as follows: the received is an HTTP payment confirmation response message; there is no response for a long time after an HTTP ordinary request message is sent to the server, or an HTTP abnormal message (such as 404 Page not found) is returned.
  • the user browser determines whether it needs to prompt the user to refresh the page. If the user is performing an operation that cannot be refreshed, such as filling in a form, the browser should give a corresponding prompt;
  • the browser will send a new HTTP payment request message to the server; if the new status is closed, then browse The server will send a new HTTP general request message to the server;
  • the server replies to the corresponding page according to the new request, and then the user's browser performs corresponding processing, such as refreshing the corresponding page, etc. If the browser cannot directly refresh the page, and the user does not agree to send a new HTTP request, the browser does not perform further processing.
  • the server remits the money to the user through the digital currency protocol or JSON/API for third-party payment.
  • the remittance can be automatically executed through scripts, digital currency protocols, or interaction with third-party institutions, and the method can be unified remittance at a fixed time, for example Once a day or once a week, in order to prevent a large amount of small remittances, the server can set a minimum remittance amount, etc.;
  • the server updates the corresponding billing and remittance information.
  • the user can enter the payment address (such as Bitcoin), a custom verification message, and the generated signature (for example, generated through the signmessage command of Bitcoin-cli or a graphical interface) on this page.
  • the payment address such as Bitcoin
  • a custom verification message for example, generated through the signmessage command of Bitcoin-cli or a graphical interface
  • the generated signature for example, generated through the signmessage command of Bitcoin-cli or a graphical interface
  • the relevant verification information can also be directly submitted to the server by the browser through HTTP and other protocols;
  • the user can enter the corresponding verification or login information (such as user name/password or identity certificate, etc.) for third-party payment on this page.
  • the relevant verification information can be Directly submitted to the server by the browser through HTTP and other protocols;
  • the server verifies whether the user is the actual owner of the payment address (for example, through Bitcoin-cli's verifymessage command or graphical interface, etc.) or account (for example, through JSON or API interaction with a third-party payment). If the verification is successful, it will provide the corresponding Billing and remittance details, or send it to the mailbox provided by the user, etc., if the verification fails, abnormal processing will be performed.
  • the actual owner of the payment address for example, through Bitcoin-cli's verifymessage command or graphical interface, etc.
  • account for example, through JSON or API interaction with a third-party payment.
  • the server collects money from the user terminal:
  • the user sets the payment information in the browser
  • the browser verifies the correctness of related settings, such as the validity of digital currency addresses and private keys (for example, through Bitcoin-cli commands such as validateaddress);
  • the browser will process the payment information in the received HTTP payment response message, and perform a page refresh process if necessary to handle the situation where the payment button state is changed when browsing the web;
  • the browser will ignore the payment information in the received HTTP payment response message.
  • the browser When the user opens the webpage, the browser will send an HTTP request message to the server and receive the HTTP payment response message sent back by the server.
  • the payment method contained in it has priority, such as gradually decreasing from top to bottom;
  • the browser will send an HTTP normal request message; if the browser supports the payment request, it will obtain all payment method information through the HTTP payment response message header;
  • an HTTP payment confirmation request message is generated, which contains an acceptable payment method, which has the highest priority in the HTTP payment response message; If the browser does not accept any payment method, it will generate an HTTP ordinary request message;
  • the browser will send the payment according to the requested amount and associate the relevant information with the payment method (address/account + unit, etc.) in the HTTP payment confirmation request message;
  • the browser displays relevant content, such as web pages, according to the situation.
  • the user terminal returns the generated HTTP request message to the browser.
  • the value transmission process may be involved in the information transmission process, as the efficiency can be improved through technical improvements, such as the use of specific digital currency remittances, or the digital/electronic currency third-party payment of instant remittances, the information transmission process will not be valued. There is a significant delay in delivery.
  • the server performs corresponding processing according to the received HTTP request message, such as returning an HTTP response message containing the corresponding web page or performing exception handling.
  • Some possible abnormal situations are as follows: the received is an HTTP payment confirmation request message, but the payment method in the request message is not one of the payment methods in the HTTP payment response message.
  • the user's browser performs corresponding processing according to the received HTTP response message, such as displaying a web page or performing exception handling.
  • the browser When the user opens the webpage, the browser will send a normal HTTP request message to the server;
  • the server generates an HTTP collection response message
  • the server returns the generated HTTP response message to the browser
  • the user's browser ignores the payment information in the received HTTP response message, and performs corresponding processing, such as displaying a page.
  • the user's browser receives an HTTP payment response message, and the new state of the payment button is on, the user is prompted to remit the payment according to the payment information in the response message. If the user agrees to the remittance, the remittance is performed and an HTTP receipt confirmation request message is sent; if the new status is closed, the remittance via the receipt information in the response message is stopped, and a new HTTP ordinary request message is sent to the server as appropriate.
  • the browser can prompt the user to refresh the page.
  • the user’s browser remits the money to the server through the digital currency protocol or JSON/API for third-party payment.
  • the remittance can be automatically executed through scripts, digital currency protocols, or interaction with third-party institutions.
  • the method can be after receiving HTTP After receiving the payment response message and before generating the HTTP payment confirmation request message, remit according to the requested amount.
  • the server can set a minimum remittance amount, etc.;
  • the browser and server update the corresponding fees and remittance information.
  • the user browser obtains the corresponding remittance information through the database module, and displays it in a page or graph.
  • the collection information is set in the HTTP request message or response, and the HTTP protocol is combined with digital currency/electronic currency, so that the traditional HTTP protocol has financial functions such as collection.
  • the collection information is used by the collection message
  • the collaborative work of management server, page management server, and fund management server realizes mutual remittance between user terminals and servers while transmitting information through HTTP protocol, thus realizing value transfer and improving the financial function application of HTTP protocol;
  • the payment information of this embodiment is set in the header field of the HTTP request message or HTTP response message, and its location is identifiable, and it does not affect the normal information transmission and reading of the HTTP protocol, and will not affect the page The content causes any impact.
  • the information transmission process of obtaining the page content and the collection information realize the value transmission process of the collection.
  • the value transmission process is not involved in the information transmission process, so the information transmission process will not cause any delay due to the value transmission. Achieved the technical effect that the transmission of HTTP protocol information and value does not affect each other;
  • the collection information is directly provided by the user or the page server, and the user can directly realize the collection and payment without a special account.
  • the recipient of the HTTP collection request message or the HTTP collection response message can send Accessible remittance by any visitor or server achieves the convenient and humanized technical effect of information and value transmission.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本发明公开了基于HTTP协议的服务器、用户终端收款***及收款方法，在传统HTTP协议上增加具有收款信息的头部字段，通过HTTP协议与数字货币/电子货币结合，使传统的HTTP协议具有收款和汇款等金融功能，在HTTP协议传输信息的同时也实现了用户与页面内容提供方之间进行收款，从而传输价值，收款***和收款方法可以广泛应用于服务器和如浏览器、媒体播放器、阅读器等用户终端，以实现HTTP协议的信息和价值同步传输。本发明具有价值与信息同步传递、互不影响、价值传递无需注册账号、便捷高效、节省时间和成本的技术特点。

Description

一种基于HTTP协议的服务器、用户终端收款***及收款方法 技术领域
本发明属于电子收款技术领域，尤其涉及一种基于HTTP协议的服务器、用户终端收款***及收款方法
背景技术
随着因特网的普及，基于HTTP协议的互联网资源已成为广泛使用的信息获取方式，在商业运营与公共事务中尤为重要。然而HTTP协议本身仅支持信息传输，无法承担金融职责，因此极大限制了其应用范围及由此产生的商业模式。
另一方面，目前区块链与数字货币(如比特币等)的发展方向主要参照银行或第三方支付，但难以获得类似的传输效率与法律保障，从而缺乏实际应用基础，无法真正体现区块链与数字货币的价值。同时匿名性也导致数字货币难以获得必要的法律支撑与监管。与此同时，多数第三方支付***不能在传输价值的同时传输如网站、视频等信息，基本属银行模式的延伸。
如线上广告，目前相关营销模式多为普通公司向互联网广告商购买相关服务，之后互联网广告商将广告发布在大流量页面上。从用户角度来讲，随机且强制性的网页广告将极大干扰其正常使用网站，例如撰写邮件或观看在线视频等，并由此对广告内容产生负面印象，易造成事与愿违的结果。从公司角度而言，由于受广告商的覆盖范围与营销模式等限制，大量的广告投入仅能有限增加其知名度，难以使***真正获益并进而产生兴趣，资金利用率较低。为缓解该问题，部分网站已实施“会员制”，即用户付费成为会员从而不受广告干扰。但该方式具有捆绑性与强迫性，同样不能对公司与用户起真正促进作用。
再如在线媒体等业务，目前多采用固定时长或打包内容的账户套餐制，缺乏可精确到某一具体页面或内容的支付方式，从而使用户将大量资金花费在无意义的内容上。从用户角度来讲，为了浏览少量付费媒体内容而需注册账户将浪费大量时间与费用，容易降低消费意愿。从公司角度而言，账户套餐制将导致大量快速消费式用户群体的流失，难以体现在线媒体的价值。
因此，在现有条件下，信息与价值传输需要分开进行，从而在时间与成本上造成极大浪费，同时也容易因传输不同步而造成困扰与误解，进而产生商业与社会纠纷。
发明内容
本发明的技术目的是提供一种基于HTTP协议的服务器、用户终端收款***及收款方法，可以解决现有信息与价值分开传输的问题，提升HTTP协议的金融功能应用。
为解决上述问题，本发明的技术方案为：
根据第一方面，一种实施例中提供一种基于HTTP协议的服务器收款***，收款消息管理服务器、页面管理服务器、资金管理服务器；
所述收款消息管理服务器与所述页面管理服务器和所述资金管理服务器交互协同工作；
所述收款消息管理服务器用于接收用户发送的HTTP收款请求消息，并识别所述HTTP收款请求消息的收款信息；
所述收款消息管理服务器还用于调度所述页面管理服务器获取页面内容，并根据所述页面内容对应的计费方式执行计费；
所述收款消息管理服务器还用于根据所述页面内容生成HTTP收款确认回应消息，并将所述HTTP收款确认回应消息反馈给用户，以向用户提供所述页面内容；
所述收款消息管理服务器还用于调度所述资金管理服务器根据所述计费 的金额和所述收款信息向用户执行汇款操作；其中，
所述收款信息包括收款对象、收款方式；
所述收款信息设于所述HTTP收款请求消息的头部字段。
根据第二方面，一种实施例中提供一种基于HTTP协议的用户终端收款***包括：收款消息管理模块、页面管理模块、资金管理模块；
所述收款消息管理模块与所述页面管理模块和所述资金管理模块交互协同工作；
所述收款消息管理模块用于向页面服务端发送HTTP普通请求消息，以获取HTTP收款回应消息，并识别所述HTTP收款回应消息的收款信息；
所述收款消息管理模块还用于调度所述资金管理模块根据所述收款信息向页面服务端执行汇款操作，并根据所述汇款操作的信息生成HTTP收款确认请求消息及发送所述HTTP收款确认请求消息，以获取具有收费的页面内容的HTTP普通回应消息；
所述收款消息管理模块还用于调度所述页面管理模块根据所述HTTP普通回应消息显示收费的所述页面内容；其中，
所述收款信息包括收款对象、收款方式；
所述收款信息设于所述HTTP收款回应消息的头部字段。
根据第三方面，一种实施例中提供一种基于HTTP协议的服务器收款***的收款方法，所述服务器收款***包括收款消息管理服务器、页面管理服务器、资金管理服务器，所述收款方法包括以下步骤：
A1：所述收款消息管理服务器接收用户发送的HTTP收款请求消息，并识别所述HTTP收款请求消息的收款信息；
A2：所述收款消息管理服务器调度所述页面管理服务器获取页面内容，所述收款消息管理服务器并根据所述页面内容对应的计费方式执行计费；
A3：所述收款消息管理服务器根据所述页面内容生成所述HTTP收款确认回应消息，并将所述HTTP收款确认回应消息反馈给用户，以向用户提供所述 页面内容；
在所述步骤A3执行过程中或所述步骤A3之后，执行步骤A4：
所述收款消息管理服务器调度所述资金管理服务器根据所述计费的金额和所述收款信息向用户执行汇款操作；其中，
所述收款信息包括收款对象、收款方式；所述收款信息设于所述HTTP收款请求消息的头部字段。
根据第四方面，一种实施例中提供一种基于HTTP协议的收款消息管理服务器的收款方法，包括以下步骤：
B1：所述收款消息管理服务器接收用户发送的HTTP收款请求消息，并识别所述HTTP收款请求消息的收款信息；
B2：所述收款消息管理服务器根据所述HTTP收款请求消息，发送页面调度指令，以获取页面内容；
B3：所述收款消息管理服务器根据所述页面内容生成HTTP收款确认回应消息，并将所述HTTP收款确认回应消息反馈给用户，以向用户提供所述页面内容；
在所述步骤B3执行的同时，执行步骤B4：
所述收款消息管理服务器根据所述页面内容对应的计费方式执行计费；
在所述步骤B3和所述步骤B4执行过程中或执行之后，执行步骤B5：
所述收款消息管理服务器根据所述计费的金额和所述收款信息发送汇款调度指令，以实现向用户汇款的汇款操作；其中，
所述收款信息包括收款对象、收款方式；所述收款信息设于所述HTTP请求消息的头部字段。
根据第五方面，一种实施例中提供一种基于HTTP协议的用户终端收款***的收款方法，所述用户终端收款***包括收款消息管理模块、页面管理模块、资金管理模块，所述收款方法包括以下步骤：
C1：所述收款消息管理模块向页面服务端发送HTTP普通请求消息，以获 取HTTP收款回应消息，并识别所述HTTP收款回应消息的收款信息；
C2：所述收款消息管理模块调度所述资金管理模块根据所述收款信息向页面服务端执行汇款操作，并根据所述汇款操作的信息生成HTTP收款确认请求消息及发送所述HTTP收款确认请求消息，以获取具有收费的页面内容的HTTP普通回应消息；
C3：所述收款消息管理模块调度所述页面管理模块根据所述HTTP普通回应消息显示收费的所述页面内容；其中，
所述收款信息包括收款对象、收款方式；所述收款信息设于所述HTTP收款回应消息的头部字段。
本发明由于采用以上技术方案，使其与现有技术相比具有以下的优点和积极效果：
(1)本发明通过在HTTP收款请求消息或HTTP收款回应消息中设置收款信息，HTTP协议与数字货币/电子货币结合，使传统的HTTP协议具有收款等金融功能，通过该收款信息由收款消息管理服务器、页面管理服务器、资金管理服务器的协同工作，在HTTP协议传输信息的同时也实现了用户与页面内容提供方之间进行收款，从而实现了价值的传递，提升了HTTP协议的金融功能应用；
(2)本发明的收款信息设于在HTTP收款请求消息或HTTP收款回应消息的头部字段，其位置具有可识别性，且其本身并不影响HTTP协议的正常信息传递和阅读，不会对页面内容造成任何影响；同时通过请求消息进行页面内容的信息传递过程与通过请求消息中的收款信息从页面服务端或用户实现收款的价值传递过程，信息传递过程中一般不涉及价值传递过程，故信息传递过程一般不会因为价值的传递而产生任何延迟；在某些情况下，即使信息传递过程中涉及价值传递过程，由于可通过技术改进来提高效率，例如采用特定的数字货币汇款，或者即时汇款的数字/电子货币第三方支付，因此信息传递过程也不会因为价值的传递而产生明显延迟，达到了HTTP协议信息与价值 的传输互不影响的技术效果；
(3)本发明通过收款信息由用户或页面服务端直接提供，用户不必专门的账户即可直接实现收款与付款，同时HTTP收款请求消息或HTTP收款回应消息的接收方可向任意访问者或服务器进行无障碍汇款，达到了信息与价值传递便捷性、人性化的技术效果；
(4)本发明通过资金管理服务器或资金管理模块对收款信息进行验证，保障了收款信息的合法性且安全性，同时，通过数据库服务器或数据库模块对通过验证的收款信息的最优选择，使用户和/或服务器可提供多种收款信息，增加了付款方与收款方的兼容性，达到了收款最佳化、人性化、收款方式多样化的技术效果；
(5)本发明通过收款消息管理服务器将最优收款信息放入HTTP收款确认回应消息或HTTP收款确认请求消息中，以向用户或页面服务端反馈收款的相关信息，同时，用户也可以通过发送查询请求在数据库服务器或数据库模块中查询相关内容，达到了信息反馈人性化、多样化的技术效果；
(6)本发明服务器收款***通过数字货币交互服务器、第三方数字/电子货币交互服务器将来自资金管理服务器的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证，可支持多种货币的汇款，达到了汇款方式多样化的技术效果，同时，内部请求和外部请求的转换，达到了信息与价值的跨平台同步传输；与之类似地，用户终端收款***通过数字货币交互模块、第三方数字/电子货币交互模块将来自资金管理模块的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证，可支持多种货币的汇款，达到了汇款方式多样化的技术效果，同时，内部请求和外部请求的转换，达到了信息与价值的跨平台同步传输；
(7)本发明通过收款开关和付款开关，以控制所述收款信息的生成与识别功能的开启和关闭，以控制HTTP收款请求消息或HTTP收款回应消息中价值传输的开关控制，达到了人性化的技术效果。
附图说明
图1为本发明的一种基于HTTP协议的服务器、用户终端收款***的架构示意图；
图2为本发明的一种基于HTTP协议的服务器收款***的HTTP收款请求消息示意图；
图3为本发明的一种基于HTTP协议的服务器收款***的HTTP收款确认回应消息示意图；
图4为本发明的一种基于HTTP协议的用户终端收款***的HTTP收款回应消息示意图；
图5为本发明的一种基于HTTP协议的用户终端收款***的HTTP收款确认请求消息示意图；
图6为本发明的一种基于HTTP协议的服务器收款***的收款方法的一实施例的流程示意图；
图7为本发明的一种基于HTTP协议的服务器收款***的收款方法的另一实施例的流程示意图；
图8为本发明的一种基于HTTP协议的用户终端收款***的收款方法的一实施例的流程示意图；
图9为本发明的一种基于HTTP协议的用户终端收款***的收款方法的另一实施例的流程示意图。
具体实施方式
以下结合附图和具体实施例对本发明提出的一种基于HTTP协议的服务器、用户终端收款***及收款方法作进一步详细说明。根据下面说明和权利要求书，本发明的优点和特征将更清楚。
数字/加密货币：去中心化的数字货币或通证，一般通过“挖矿”工作产 生，如比特币和莱特币等。下文简称“数字货币”。
电子货币：电子化的传统/法定货币或代币及相关支付服务，如paypal和alipay及其虚拟化电子货币等。
HTTP收款请求消息：HTTP请求消息，其头部含有收款信息以供服务器确认。
HTTP收款确认回应消息：HTTP回应消息，其头部含有汇款操作接收确认的收款信息，以反馈给用户。
HTTP收款回应消息：HTTP回应消息，其头部含有收款信息以供用户终端确认。
HTTP收款确认请求消息：HTTP请求消息，其头部含有汇款操作接收确认的收款信息，以反馈给页面服务端。
HTTP普通请求消息：普通的HTTP请求消息，其头部不含有收款信息。
HTTP普通回应消息：普通的HTTP回应消息，不含服务器确认接受的收款方式信息。
本实施例中，HTTP请求消息一般由用户终端发送给服务器，HTTP回应消息一般由服务器回应给用户终端。其对应关系与顺序如下：
普通请求过程：用户终端向服务器发出“HTTP普通请求消息”，服务器向用户终端回应“HTTP普通回应消息”；
用户终端发出收款请求：用户终端向服务器发出“HTTP收款请求消息”，服务器向用户终端回应“HTTP收款确认回应消息”；
服务器发出收款请求：用户终端向服务器发出“HTTP请求消息”，一般为普通请求，服务器向用户终端发出“HTTP收款回应消息”，用户终端向服务器发出“HTTP收款确认请求消息”。
HTTP协议指：超文本传输协议(HTTP)与相关的扩展协议，如超文本传输安全协议(HTTPS)。
实施例1
参看图1，本实施例提供一种基于HTTP协议的服务器收款***，包括：收款消息管理服务器、页面管理服务器、资金管理服务器；
收款消息管理服务器与页面管理服务器和资金管理服务器交互协同工作；
收款消息管理服务器用于接收用户发送的HTTP收款请求消息，并识别HTTP收款请求消息的收款信息；
收款消息管理服务器还用于调度页面管理服务器获取页面内容，并根据页面内容对应的计费方式执行计费；
收款消息管理服务器还用于根据页面内容生成HTTP收款确认回应消息，并将HTTP收款确认回应消息反馈给用户，以向用户提供页面内容；
收款消息管理服务器还用于调度资金管理服务器根据计费的金额和收款信息向用户执行汇款操作；其中，
收款信息包括收款对象、收款方式；
收款信息设于HTTP收款请求消息的头部字段。
现结合图1至图3对本实施例进行详细说明：
具体地，参看图2和图3，传统的HTTP请求消息和HTTP回应消息并没有如图2和图3中圈出的Pay-To字段，而本实施例中在传统的HTTP请求消息和HTTP回应消息设置了如图2和图3中圈出的Pay-To字段，该字段是HTTP协议融合货币协议后新增的字段，图2中的Pay-To字段用来收款，图3中的Pay-To字段用来反馈信息，以实现信息传输和价值传输同步，其中，圈出的Pay-To字段设于HTTP请求消息或HTTP回应消息的头部字段。
具体地，HTTP收款请求消息与HTTP收款确认回应消息中的收款信息格式可以为：/Pay-To:<"收款地址">；unit＝<单位(含类型)>；provider＝[服务商标识][；confirmed]/，例如：
/Pay-To:"1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"；unit＝BTC/；
/Pay-To:"[email protected]"；unit＝CNY；provider＝payserv1/；
/Pay-To:"1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"；unit＝BTC；confirmed/。
其中“//”用来区分完整的“Pay-To”头部字段，以实现多个“Pay-To”头部字段提供不同的收款方式供服务器选择，而“//”字符本身不属于“Pay-To”头部字段。“confirmed”标识该收款信息已确认，一般位于HTTP收款确认请求消息或HTTP收款确认回应消息。
本实施例的收款信息设于在HTTP收款请求消息或HTTP收款确认回应消息的头部字段，其位置具有可识别性，且其本身并不影响HTTP协议的正常信息传递和阅读，不会对页面内容造成任何影响；同时通过请求消息进行页面内容的信息传递过程与通过请求消息中的收款信息从页面服务端或用户实现收款的价值传递过程，信息传递过程中一般不涉及价值传递过程，故信息传递过程一般不会因为价值的传递而产生任何延迟；在某些情况下，即使信息传递过程中涉及价值传递过程，由于可通过技术改进来提高效率，例如采用特定的数字货币汇款，或者即时汇款的数字/电子货币第三方支付，因此信息传递过程也不会因为价值的传递而产生明显延迟，达到了HTTP协议信息与价值的传输互不影响的技术效果。
具体地，页面内容可以为文字、图片、音频、视频、文件、网页等等HTTP协议可传递内容。
具体地，收款信息由用户提供，可由用户终端输入，用户终端可以为浏览器、媒体播放器、阅读器等信息传递终端，用户终端亦可为具有HTTP协议功能的手机、平板电脑、PC机等设备。
具体地，收款信息包括收款对象、收款方式，收款对象为收款地址或收款账号，其中，收款地址可以为比特币、莱特币地址等，收款账号可以为paypal和alipay等账号，所述收款信息携带有账号的服务商信息，如paypal、alipay或bitpay等。进一步地，收款信息还包括收款单位，如人民币(CNY)、美元(USD)、比特币(BTC)或莱特币(LTC)等。
本实施例通过收款信息由用户直接提供，用户不必专门的账户即可直接实现收款与付款，同时HTTP收款请求消息的接收方可向任意访问者进行无障 碍汇款，达到了信息与价值传递便捷性、人性化的技术效果。
较优地，参看图1，收款消息管理服务器还用于调度资金管理服务器对收款信息进行验证可用性。
本实施例通过资金管理服务器对收款信息进行验证，保障了收款信息的合法性与安全性。
较优地，参看图1，本实施还包括数据库服务器，数据库服务器用于存储或更新收款信息、计费方式、收款优先级；数据库服务器分别和收款消息管理服务器、资金管理服务器交互，收款消息管理服务器还用于调度数据库服务器根据收款优先级对收款信息进行选择，确定一最优收款信息作为汇款操作的汇款方式；其中，最优收款信息为可用的收款信息中收款对象的优先级最高且收款方式的优先级最高的收款信息。
较优地，收款信息内包含多种收款对象、多种收款方式、多种收款单位，可通过可用性验证和收款优先级进行选择一最优收款信息。
具体地，收款优先级包括收款对象的优先级、收款方式的优先级，进一步地，还包括收款单位的优先级，根据收款单位的优先级可在最优收款信息中确定最优收款单位。较优地，收款优先级可由用户通过用户终端进行设定。
具体地，计费方式可以为多种形式，如点击数、行为、停留时间、访问时间、页面类型和奖励方式等，该计费方式由页面内容的提供者进行设定。
具体地，汇款操作可通过脚本、数字货币协议或与第三方机构交互等自动执行，方式可为固定时间统一汇款，例如每天或每周一次，具体根据特定的计费方式进行汇款，为防止大量小额汇款，服务器可设置最低汇款额等。
较优地，为防止通过数字货币地址与交易编号进行跟踪，可采用混币或强匿名币等方式汇款，从而降低HTTP服务器与收款人数字货币地址金额泄漏的风险。
本实施例通过资金管理服务器进行验证，保障了收款信息的合法性且安全性，同时，通过数据库服务器或数据库模块对通过验证的收款信息的最优 选择，使用户和/或服务器可提供多种收款信息，增加了付款方与收款方的兼容性，达到了收款最佳化、人性化、收款方式多样化的技术效果。
较优地，参看图1，收款消息管理服务器还用于将最优收款信息放入页面内容的表头，以向用户反馈。
较优地，参看图1，数据库服务器还用于存储计费与汇款明细记录；收款消息管理服务器还用于接收用户发送的查询请求，调度资金管理服务器对查询请求的信息进行有效验证，根据有效的查询请求，收款消息管理服务器调度页面管理服务器获取页面内容及调度数据库服务器获取查询内容，并根据页面内容和查询内容生成查询结果反馈至用户。
本实施例通过收款消息管理服务器将最优收款信息放入页面内容的表头，以向用户反馈收款的相关信息，同时，用户也可以通过用户终端发送查询请求以在数据库服务器中查询相关内容，达到了信息反馈人性化、多样化的技术效果。
较优地，参看图1，本实施例还包括内外网接口，内外网接口包括数字货币交互服务器、第三方数字/电子货币交互服务器；数字货币交互服务器和第三方数字/电子货币交互服务器分别和资金管理服务器交互，用于将来自资金管理服务器的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证。
具体地，参看图1，数字货币交互服务器为运行数字货币服务程序的服务器，第三方数字/电子货币交互服务器为支持本地或第三方接口的服务器。
本实施例的服务器收款***通过数字货币交互服务器、第三方数字/电子货币交互服务器将来自资金管理服务器的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证，可支持多种货币的汇款，达到了汇款方式多样化的技术效果，同时，内部请求和外部请求的转换，达到了信息与价值的跨平台同步传输。
较优地，本实施例还包括付款开关和/或收款开关，付款开关用于控制收 款信息的识别功能的开启和关闭，以实现汇款操作的控制，收款开关用于控制向用户发送的HTTP回应消息中是否生成收款信息，以实现向用户收款的控制。
具体地，当付款开关打开后，服务器可识别HTTP收款请求消息的收款信息，从而使服务器能按情况提供页面内容、计费并向用户汇款。当付款开关关闭后，服务器屏蔽HTTP收款请求消息的收款信息，从而使服务器能按普通情况处理。
具体地，当收款开关打开后，服务器收款***发送的HTTP回应消息将含有收款信息，即HTTP收款回应消息，从而使用户终端能识别HTTP收款回应消息的收款信息，并使用户终端能按情况进行汇款。当收款开关关闭后，服务器发送的HTTP回应消息将不含收款信息，即HTTP普通回应消息，从而使用户终端能按普通情况处理。
本实施例通过付款开关和/或收款开关，以控制HTTP请求消息中价值传输的开关控制，达到了人性化的技术效果。
较优地，本实施例还包括HTTP服务器扩展模块，收款消息管理模块加载HTTP服务器扩展模块，以识别具有收款信息的HTTP请求消息。
本实施例通过收款消息管理模块加载HTTP服务器扩展模块，以识别具有收款信息的HTTP请求消息，实现了一般服务器的扩展，达到了适用范围广、成本低的技术效果。
为确保安全与防止篡改，用户终端与服务器之间所有含收款信息的HTTP通讯均需被加密传输，例如通过HTTPS。
现举例对本实施的收款***技术效果进行说明：
以线上广告为例，通过HTTP与货币协议的结合，本实施例使跨平台的“看广告有收入，无广告不付费”模式成为可能，进而可解决广告资金利用率低、广告效益低等技术问题。本实施例中，用户可选择通过观看广告来获得数字/电子货币收益，从而能真正找到感兴趣的产品；或者选择无广告也无收益的 模式，从而能不受干扰地使用网站。由于数字货币的跨平台性，用户不必专门注册账号，只需有合适的浏览器即可在兼容网站上通过浏览获得收益，因此用户拥有高度自由与选择权。对公司而言，采用该模式可直接将广告资金投放给市场与最终用户，进而降低中间成本并获得较高的宣传效果与用户积极性。
以网站激励为例，对于某天前100名访问者进行奖励，或者对网页互动内容(如游戏)进行奖励。由于不需注册账户，因此用户可直接访问网站并获得奖励，从而降低双方的资金与时间成本，并为网站获得较好的推广效果。
以下载文件为例，由于HTTP不仅能传递HTML等网站内容，也能直接传递图像或文件等数据，因此服务器的计费范围并不局限在HTML等网页，同样也适用于所有通过HTTP协议进行交互的内容，达到很好的文件共享效果及宣传效果。
实施例2
基于实施例1，本例提供另外一种基于HTTP协议的用户终端收款***。与实施例1不同的是，本例的收款信息由服务器发出，而收款确认信息由用户终端发出并进行汇款。
参看图1，本实施例的***结构与实施例1近似，包括：收款消息管理模块、页面管理模块、资金管理模块；
收款消息管理模块与页面管理模块和资金管理模块交互协同工作；
收款消息管理模块用于向页面服务端发送HTTP普通请求消息，以获取HTTP收款回应消息，并识别HTTP收款回应消息的收款信息；
收款消息管理模块还用于调度资金管理模块根据收款信息向页面服务端执行汇款操作，并根据汇款操作的信息生成HTTP收款确认请求消息及发送HTTP收款确认请求消息，以获取具有收费的页面内容的HTTP普通回应消息；
收款消息管理模块还用于调度页面管理模块根据HTTP普通回应消息显示收费的页面内容；其中，
收款信息包括收款对象、收款方式；
收款信息设于HTTP收款回应消息的头部字段。
现结合图1、图4、图5对本实施例进行详细说明：
具体地，参看图4和图5，本实施例中的Pay-To字段基于实施例1。与实施例1不同的是，本实施例中的Pay-To字段新增加“金额”与“交易号”信息。如图4和图5中圈出的Pay-To字段，图4中的Pay-To字段用来收款，图5中的Pay-To字段用来反馈信息，以实现信息传输和价值传输同步，其中，圈出的Pay-To字段设于HTTP回应消息或HTTP请求消息的头部字段。
具体地，HTTP回应消息与HTTP请求消息中的收款信息格式可以为：
/Pay-To:<"收款地址">；amount＝<金额>；unit＝<单位(含类型)>；
provider＝[服务商标识][；txid＝<交易号>；confirmed]/，例如：
/Pay-To:"1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"；amount＝1；unit＝BTC/；
/Pay-To:"[email protected]"；amount＝100；unit＝CNY；provider＝payserv1/；
/Pay-To:"1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"；amount＝1；unit＝BTC；
txid＝txid1；confirmed/。
其中“//”用来区分完整的“Pay-To”头部字段，以实现多个“Pay-To”头部字段提供不同的收款方式供服务器选择，而“//”字符本身不属于“Pay-To”头部字段。
本实施例的收款信息设于在HTTP回应消息的头部字段，其位置具有可识别性，且其本身并不影响HTTP协议的正常信息传递和阅读，不会对页面内容造成任何影响，同时通过HTTP请求消息获取页面内容的信息传递过程与通过HTTP回应消息中的收款信息实现收款的价值传递过程，尽管信息传递过程中涉及价值传递过程，但由于可通过技术改进来提高效率，例如采用特定的数字货币汇款，或者即时汇款的数字/电子货币第三方支付，故信息传递过程不会因为价值的传递而产生明显延迟，达到了HTTP协议信息与价值的传输互不影响的技术效果。
具体地，页面内容可以为文字、图片、音频、视频、文件、网页等等HTTP协议可传递内容。
具体地，收款信息由服务器提供，可由服务器运营方设定，用户终端可以为浏览器、媒体播放器、阅读器等信息传递终端，用户终端亦可为具有HTTP协议功能的手机、平板电脑、PC机等设备。
具体地，收款信息包括收款对象、收款方式，收款对象为收款地址或收款账号，其中，收款地址可以为比特币、莱特币地址等，收款账号可以为paypal和alipay等账号，所述收款账号携带有账号的服务商信息，如paypal、alipay或bitpay等。进一步地，收款信息还包括收款单位，如人民币(CNY)、美元(USD)、比特币(BTC)或莱特币(LTC)等。
本实施例通过收款信息由服务器直接提供，用户不必专门的账户即可直接实现向内容提供商付款，同时HTTP回应消息的接受方用户可向任意内容提供商进行无障碍汇款，达到了信息与价值传递便捷性、人性化的技术效果。
较优地，参看图1，用户终端收款消息管理模块还用于调度资金管理模块对收款信息进行验证可用性。
本实施例通过资金管理模块对收款信息进行验证，保障了收款信息的合法性与安全性。
较优地，参看图1，本实施还包括用户终端数据库模块，数据库模块用于存储或更新汇款记录、汇款优先级；数据库模块分别和收款消息管理模块、资金管理模块交互，收款消息管理模块还用于调度数据库模块根据汇款优先级对收款信息进行选择，确定一最优收款信息作为汇款操作的汇款方式；其中，最优收款信息为可用的收款信息中收款对象的优先级最高且收款方式的优先级最高的收款信息。
较优地，收款信息内包含多种收款对象、多种收款方式、多种收款单位，可通过可用性验证和收款优先级进行选择一最优收款信息。
具体地，收款优先级包括收款对象的优先级、收款方式的优先级，进一 步地，还包括收款单位的优先级，根据收款单位的优先级可在最优收款信息中确定最优收款单位。较优地，收款优先级可由服务商进行设定。
具体地，汇款操作可通过脚本、数字货币协议或与第三方机构交互等自动执行，方式可为在收到HTTP收款回应消息后及在生成HTTP收款确认请求消息前根据请款金额进行汇款，为防止大量小额汇款，用户可设置最低汇款额等。
较优地，为防止通过数字货币地址与交易编号进行跟踪，可采用混币或强匿名币等方式汇款，从而降低用户与收款人数字货币地址金额泄漏的风险。
本实施例通过数据库模块对通过验证的收款信息的最优选择，使服务器可提供多种收款信息，增加了付款方与收款方之间的兼容性，达到了收款最佳化、人性化、收款方式多样化的技术效果。
较优地，参看图1，数据库模块还用于汇款记录的查询，收款消息管理模块用于接收用户发送的查询请求，调度资金管理模块对查询请求的信息进行有效验证，根据有效的查询请求，收款消息管理模块调度数据库模块获取查询内容，并根据查询内容生成查询结果反馈给用户。
较优地，收款消息管理模块将最优收款信息放入HTTP收款确认请求消息的表头。
本实施例通过收款消息管理模块将最优收款信息放入HTTP请求消息的表头，以向服务器反馈收款的相关信息，同时，用户也可以通过查询请求以在数据库模块的数据库服务器中查询相关内容，达到了信息反馈人性化、多样化的技术效果。
较优地，参看图1，本实施例还包括内外网接口，内外网接口包括数字货币交互模块、第三方数字/电子货币交互模块；数字货币交互模块和第三方数字/电子货币交互模块分别和资金管理模块交互，用于将来自资金管理模块的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证。
具体地，参看图1，数字货币交互模块为支持数字货币协议的模块，第 三方数字/电子货币交互服务器为支持第三方接口的模块。
本实施例通过数字货币交互模块、第三方数字/电子货币交互模块将来自资金管理模块的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证，可支持多种货币的汇款，达到了汇款方式多样化的技术效果，同时，内部请求和外部请求的转换，达到了信息与价值的跨平台同步传输。
较优地，参看图1，本实施例还包括服务器端的内外网接口，内外网接口包括数字货币交互服务器、第三方数字/电子货币交互器；其功能与交互方式与实施例1或本例中的用户终端相似。
较优地，用户终端收款***还包括付款开关和/或收款开关，付款开关用于控制收款信息的识别功能的开启和关闭，以实现汇款操作的控制，收款开关用于控制向页面服务端发送的HTTP请求消息中是否放置收款信息，以实现向页面服务端收款的控制。
具体地，当付款开关打开后，用户终端在收到服务器发出的HTTP收款回应消息后，将进行汇款并发送HTTP收款确认请求消息给服务器，从而使服务器能按情况提供页面内容。当付款开关关闭后，用户终端在收到服务器发出的HTTP收款回应消息后，将忽略其中的收款信息，并按情况发送HTTP普通请求消息给服务器，从而使服务器能按普通情况处理。
具体地，当收款开关打开后，用户终端发送的HTTP请求消息将含有收款信息，即HTTP收款请求消息，从而使服务器能识别HTTP收款请求消息的收款信息，并使服务器能按情况提供页面内容、计费并向用户汇款。当收款开关关闭后，用户终端发送的HTTP请求消息将不含收款信息，即HTTP普通请求消息，从而使服务器能按普通情况处理。
本实施例通过付款开关和/或收款开关，以控制HTTP回应消息中价值传输的开关控制，达到了人性化的技术效果。
较优地，本实施例还包括HTTP服务器扩展模块，服务器收款消息管理模块加载HTTP服务器扩展模块，以识别具有收款确认信息的HTTP请求消息。
本实施例通过服务器收款消息管理模块加载HTTP服务器扩展模块，以识别具有收款确认信息的HTTP请求消息，实现了一般设备终端的扩展，达到了适用范围广、成本低的技术效果。
较优地，用户终端的收款消息管理模块还用于根据HTTP回应消息进行处理，如通过消息窗口或状态图标等方式来提示用户，以反馈异常信息或者付款信息。具体地，用户终端根据所收到的HTTP回应消息作相应处理，例如显示网页、提示用户或进行异常处理等，部分可能的异常情况如：向服务器发出HTTP收款确认请求消息后长时间无回应，或返回HTTP异常消息(如404 Page not found)。
现举例对本实施的收款***技术效果进行说明：
以在线内容订阅为例。通过HTTP与货币协议的结合，用户可为浏览的每一页内容付费，而无需支付完整的套餐费。由于数字货币的跨平台性，用户不必专门注册账号，只需有合适的浏览器即可在兼容网站上通过浏览进行支付，因此用户拥有高度自由与选择权。对公司而言，采用该模式可直接将在线内容有针对性地投放给最终用户，进而降低中间成本并获得较高的市场效果与用户积极性。
以下载文件为例，由于HTTP不仅能传递HTML等网站内容，也能直接传递图像或文件等数据，因此服务器的预付费范围并不局限在HTML等网页，同样也适用于所有通过HTTP协议进行交互的内容，达到很好的文件共享效果及宣传效果。
实施例3
基于实施例1，参看图6，本实施例提供一种基于HTTP协议的服务器收款***的收款方法，服务器收款***包括收款消息管理服务器、页面管理服务器、资金管理服务器，收款方法包括以下步骤：
A1：收款消息管理服务器接收用户发送的HTTP收款请求消息，并识别HTTP收款请求消息的收款信息；
A2：收款消息管理服务器调度页面管理服务器获取页面内容，收款消息管理服务器并根据页面内容对应的计费方式执行计费；
A3：收款消息管理服务器根据页面内容生成HTTP收款确认回应消息，并将HTTP收款确认回应消息反馈给用户，以向用户提供页面内容；
在步骤A3执行过程中或步骤A3之后，执行步骤A4：
收款消息管理服务器调度资金管理服务器根据计费的金额和收款信息向用户执行汇款操作；其中，
收款信息包括收款对象、收款方式；收款信息设于HTTP收款请求消息的头部字段。
现对本实施例进行详细地说明：
较优地，参看图7，步骤A2中，收款消息管理服务器调度页面管理服务器获取页面内容的同时，收款消息管理服务器还调度资金管理服务器对收款信息进行验证可用性，获取可用的收款信息。
较优地，参看图7，服务器收款***还包括数据库服务器；收款方法的步骤A2中，获取可用的收款信息之后，收款消息管理服务器调度数据库服务器根据数据库服务器中的收款优先级对收款信息进行选择，确定一最优收款信息作为汇款操作的汇款方式；其中，最优收款信息为可用的收款信息中收款对象的优先级最高且收款方式的优先级最高的收款信息。
本实施例通过资金管理服务器对收款信息进行验证，保障了收款信息的合法性与安全性，同时，通过数据库服务器对通过验证的收款信息的最优选择，使用户可提供多种收款信息，增加了付款方与收款方之间的兼容性，达到了收款最佳化、人性化、收款方式多样化的技术效果。
较优地，步骤A2中，确定一最优收款信息之后，收款消息管理服务器将最优收款信息放入页面内容的表头。
本实施例通过收款消息管理服务器将最优收款信息放入页面内容的表头，以向用户反馈收款的相关信息，同时，用户也可以通过用户终端发送查询请 求以在数据库服务器中查询相关内容，达到了信息反馈人性化、多样化的技术效果。
较优地，步骤A4之后还包括步骤A5：资金管理服务器接收汇款操作的结果，并将结果发送至数据库服务器进行存储。
较优地，服务器收款***还包括内外网接口，内外网接口包括数字货币交互服务器、第三方数字/电子货币交互服务器；收款方法的步骤A4具体包括以下步骤：
A41：资金管理服务器接收收款消息管理服务器的汇款调度指令；
A42：资金管理服务器调度数据库服务器获取计费的金额和最优收款信息；
A43：根据计费的金额和最优收款信息，资金管理服务器向数字货币交互服务器或者第三方数字/电子货币交互服务器发送内部请求；
A44：数字货币交互服务器或者第三方数字/电子货币交互服务器将内部请求转换为外部请求以执行汇款操作。
本实施例通过数字货币交互服务器、第三方数字/电子货币交互服务器将来自资金管理服务器的内部请求转换为外部请求以执行实际汇款，可支持多种货币的汇款，达到了汇款方式多样化的技术效果，同时，内部请求和外部请求的转换，达到了信息与价值的跨平台同步传输。
较优地，服务器收款***还包括付款开关；收款方法的步骤A1中，识别HTTP收款请求消息的收款信息的过程具体包括以下步骤：
判断付款开关是否已打开：若付款开关已打开，收款消息管理服务器识别HTTP收款请求消息的收款信息；若付款开关未打开，收款消息管理服务器不识别HTTP收款请求消息的收款信息。
本实施例通过付款开关，以控制HTTP请求消息中价值传输的开关控制，达到了人性化的技术效果。
实施例4
基于实施例2，本实施例提供一种基于HTTP协议的收款消息管理服务器 的收款方法，包括以下步骤：
B1：收款消息管理服务器接收用户发送的HTTP收款请求消息，并识别HTTP收款请求消息的收款信息；
B2：收款消息管理服务器根据HTTP收款请求消息，发送页面调度指令，以获取页面内容；
B3：收款消息管理服务器根据页面内容生成HTTP收款确认回应消息，并将HTTP收款确认回应消息反馈给用户，以向用户提供页面内容；
在步骤B3执行的同时，执行步骤B4：
收款消息管理服务器根据页面内容对应的计费方式执行计费；
在步骤B3和步骤B4执行过程中或执行之后，执行步骤B5：
收款消息管理服务器根据计费的金额和收款信息发送汇款调度指令，以实现向用户汇款的汇款操作；其中，
收款信息包括收款对象、收款方式；收款信息设于HTTP请求消息的头部字段。
本实施例具有以下技术效果：
本实施例通过在HTTP请求消息中设置收款信息，HTTP协议与数字货币/电子货币结合，使传统的HTTP协议具有收款等金融功能，在HTTP协议传输信息的同时也实现了用户向页面内容提供方进行收款，从而实现了价值的传递，提升了HTTP协议的金融功能应用；
本实施例的收款信息设于在HTTP请求消息的头部字段，其位置具有可识别性，且其本身并不影响HTTP协议的正常信息传递和阅读，不会对页面内容造成任何影响，同时通过HTTP请求消息获取页面内容的信息传递过程与通过HTTP请求消息中的收款信息实现收款的价值传递过程，信息传递过程中不涉及价值传递过程，故信息传递过程不会因为价值的传递而产生任何延迟，达到了HTTP协议信息与价值的传输互不影响的技术效果；
本实施例通过收款信息由用户直接提供，用户不必专门的账户即可直接 实现收款，同时HTTP请求消息的请求方可向任意访问者进行无障碍汇款，达到了信息与价值传递便捷性、人性化的技术效果。
实施例5
基于实施例2，参看图8，本实施例提供一种基于HTTP协议的客户端收款***的收款方法，客户端收款***包括收款消息管理模块、页面管理模块、资金管理模块，收款方法包括以下步骤：
C1：收款消息管理模块向页面服务端发送HTTP普通请求消息，以获取HTTP收款回应消息，并识别HTTP收款回应消息的收款信息；
C2：收款消息管理模块调度资金管理模块根据收款信息向页面服务端执行汇款操作，并根据汇款操作的信息生成HTTP收款确认请求消息及发送HTTP收款确认请求消息，以获取具有收费的页面内容的HTTP普通回应消息；
C3：收款消息管理模块调度页面管理模块根据HTTP普通回应消息显示收费的页面内容；其中，
收款信息包括收款对象、收款方式；收款信息设于HTTP收款回应消息的头部字段。
现对本实施例进行详细地说明：
较优地，参看图9，步骤C2中，汇款操作执行之前，收款消息管理模块还调度资金管理模块对收款信息进行验证可用性，获取可用的收款信息。
较优地，参看图9，客户端收款***还包括数据库模块；收款方法的步骤C2中，获取可用的收款信息之后且汇款操作执行之前，收款消息管理模块调度数据库模块根据数据库模块中的汇款优先级对收款信息进行选择，确定一最优收款信息作为汇款操作的汇款方式；其中，最优收款信息为可用的收款信息中收款对象的优先级最高且收款方式的优先级最高的收款信息。
本实施例通过资金管理模块对收款信息进行验证，保障了收款信息的合法性与安全性，同时，通过数据库模块对通过验证的收款信息的最优选择，使用户可提供多种收款信息，增加了付款方与收款方之间的兼容性，达到了 收款最佳化、人性化、收款方式多样化的技术效果。
较优地，客户端收款***还包括内外网接口，内外网接口包括数字货币交互模块、第三方数字/电子货币交互模块；收款方法的资金管理模块执行汇款操作具体包括以下步骤：
D1：资金管理模块接收收款消息管理模块的汇款调度指令；
D2：资金管理模块调度数据库模块获取收款信息的汇款金额和最优收款信息；
D3：根据汇款金额和最优收款信息，资金管理模块向数字货币交互模块或者第三方数字/电子货币交互模块发送内部请求；
D4：数字货币交互模块或者第三方数字/电子货币交互模块将内部请求转换为外部请求以执行汇款操作。
本实施例通过数字货币交互模块、第三方数字/电子货币交互模块将来自资金管理模块的内部请求转换为外部请求以执行实际汇款，可支持多种货币的汇款，达到了汇款方式多样化的技术效果，同时，内部请求和外部请求的转换，达到了信息与价值的跨平台同步传输。
较优地，客户端收款***还包括付款开关；收款方法的步骤B1中，识别HTTP收款回应消息的收款信息的过程具体包括以下步骤：
判断付款开关是否已打开：若付款开关已打开，收款消息管理模块识别HTTP收款回应消息的收款信息；若付款开关未打开，收款消息管理模块不识别HTTP收款回应消息的收款信息。
本实施例通过付款开关，以控制HTTP回应消息中价值传输的开关控制，达到了人性化的技术效果。
实施例6
基于实施例1至实施例5，本实施例以浏览器为用户终端收款***，并结合服务器收款***，对上述实施例的***与方法执行过程进行说明：
A.用户终端向服务器进行收款：
1)浏览器用户设置过程：
用户设置浏览器中的收款信息；
浏览器验证相关设置的正确性，比如数字货币地址的有效性(例如通过Bitcoin-cli的validateaddress等命令)等；
若验证通过，则根据浏览器主界面的“收款”按钮状态更新页面：
若收款按钮已打开，则执行页面刷新流程，以处理浏览网页时改变收款按钮状态的情况；
若收款按钮已关闭，则不作页面刷新。
2)浏览网页时收款按钮已打开的执行过程：
用户打开网页，此时浏览器将向服务器发出HTTP收款请求消息，其所含的收款方式存在优先级，例如自上而下逐渐降低；
若服务器不支持收款请求，服务器将返回HTTP普通回应消息；若服务器支持收款请求，则通过HTTP收款请求消息头部获得所有收款方式信息；
若服务器接受一种或多种所请求的收款方式，则生成HTTP收款确认回应消息，其中含有一种可接受的收款方式，该方式在HTTP收款请求消息内具有最高优先级；若服务器不接受任何一种收款方式，则生成HTTP普通回应消息；
服务器按情况计费,例如点击数、行为、停留时间、访问时间、页面类型和奖励方式等，并将相关信息关联到HTTP收款确认回应消息里的收款方式(地址/账号+单位等)；
服务器按情况提供所需内容，例如网页HTML代码或二进制文件等，并将其放入前述生成的HTTP回应消息中。
服务器将生成的HTTP回应消息返回给浏览器，由于回应消息的生成过程不涉及汇款，服务器的回应不会有任何延迟。
用户浏览器根据所收到的HTTP回应消息作相应处理，例如显示网页、提示用户或进行异常处理等。部分可能的异常情况如下：所收到的是HTTP收款确认回应消息，但回应消息内的收款方式并非请求消息内收款方式之一；向 服务器发出HTTP收款请求消息后长时间无回应，或返回HTTP异常消息(如404 Page not found)。
3)浏览网页时收款按钮已关闭的执行过程：
用户打开网页，此时浏览器将向服务器发出HTTP普通请求消息；
服务器生成HTTP普通回应消息；
服务器按情况提供所需内容，例如网页HTML代码或二进制文件等，并将其放入生成的HTTP普通回应消息中；
服务器将生成的HTTP回应消息返回给浏览器；
用户浏览器根据所收到的HTTP回应消息作相应处理，例如提示用户或进行异常处理等。部分可能的异常情况如下：所收到的是HTTP收款确认回应消息；向服务器发出HTTP普通请求消息后长时间无回应，或返回HTTP异常消息(如404 Page not found)。
4)浏览网页时改变收款按钮状态的过程：
用户浏览器判断是否需要提示用户刷新页面。若用户在执行不可刷新的操作，例如填写表单，则浏览器应给出相应提示；
若浏览器可直接刷新页面，或用户同意发送新的HTTP请求消息，且新收款按钮状态为打开，则浏览器将向服务器发送新的HTTP收款请求消息；若新状态为关闭，则浏览器将向服务器发送新的HTTP普通请求消息；
服务器根据新请求回复相应页面，之后用户浏览器作相应处理，例如刷新相应页面等，若浏览器不可直接刷新页面，且用户不同意发送新的HTTP请求，则浏览器不作进一步处理。
5)服务器向用户汇款的过程：
服务器将款项通过数字货币协议或与第三方支付的JSON/API等交互来汇给用户，汇款可通过脚本、数字货币协议或与第三方机构交互等自动执行，方式可为固定时间统一汇款，例如每天或每周一次，为防止大量小额汇款，服务器可设置最低汇款额等；
服务器更新相应的计费与汇款等信息。
6)用户查询计费明细的过程：
用户访问服务器提供的查询页面：
若为数字货币，则用户可在该页面上输入收款地址(如比特币)、自定义验证消息及所生成的签名(例如通过Bitcoin-cli的signmessage命令或图形界面生成)，如果浏览器本身支持数字货币协议，则相关验证信息亦可直接由浏览器通过HTTP等协议提交给服务器；
若为数字/电子货币账户，则用户可在该页面上输入第三方支付相应的验证或登陆信息(如用户名/密码或身份证书等)，如果浏览器本身支持相应账户，则相关验证信息可直接由浏览器通过HTTP等协议提交给服务器；
服务器验证用户是否为收款地址(例如通过Bitcoin-cli的verifymessage命令或图形界面等)或账号(例如通过与第三方支付的JSON或API交互)的实际拥有人，若验证成功，则提供对应的计费与汇款明细，或将其发至用户提供的邮箱等，若验证失败则进行异常处理。
B.服务器向用户终端进行收款：
1)浏览器用户设置过程：
用户设置浏览器中的付款信息；
浏览器验证相关设置的正确性，比如数字货币地址和私钥的有效性(例如通过Bitcoin-cli的validateaddress等命令)等；
若验证通过，则根据浏览器主界面的“付款”按钮状态更新页面：
若付款按钮已打开，则浏览器将处理收到的HTTP收款回应消息中的收款信息，并在必要时执行页面刷新流程，以处理浏览网页时改变收款按钮状态的情况；
若付款按钮已关闭，则浏览器将忽略收到的HTTP收款回应消息中的收款信息。
2)浏览网页时付款按钮已打开的执行过程：
用户打开网页，此时浏览器将向服务器发出HTTP请求消息，并收到由服务器发回的HTTP收款回应消息，其所含的收款方式存在优先级，例如自上而下逐渐降低；
若浏览器不支持收款请求，浏览器将发送HTTP普通请求消息；若浏览器支持收款请求，则通过HTTP收款回应消息头部获得所有收款方式信息；
若浏览器接受一种或多种所请求的收款方式，则生成HTTP收款确认请求消息，其中含有一种可接受的收款方式，该方式在HTTP收款回应消息内具有最高优先级；若浏览器不接受任何一种收款方式，则生成HTTP普通请求消息；
若生成HTTP收款确认请求消息，则浏览器按请款金额汇款,并将相关信息关联到HTTP收款确认请求消息里的收款方式(地址/账号+单位等)；
浏览器按情况显示相关内容，例如网页等。
用户终端将生成的HTTP请求消息返回给浏览器。尽管信息传递过程中可能涉及价值传递过程，但由于可通过技术改进来提高效率，例如采用特定的数字货币汇款，或者即时汇款的数字/电子货币第三方支付，故信息传递过程不会因为价值的传递而产生明显延迟。
服务器根据所收到的HTTP请求消息作相应处理，例如返回含有相应网页的HTTP回应消息或进行异常处理等。部分可能的异常情况如下：所收到的是HTTP收款确认请求消息，但请求消息内的收款方式并非HTTP收款回应消息内收款方式之一。
用户浏览器根据所收到的HTTP回应消息作相应处理，例如显示网页或进行异常处理等。
3)浏览网页时付款按钮已关闭的执行过程：
用户打开网页，此时浏览器将向服务器发出HTTP普通请求消息；
服务器生成HTTP收款回应消息；
服务器将生成的HTTP回应消息返回给浏览器；
用户浏览器忽略所收到的HTTP回应消息里的收款信息，并作相应处理， 例如显示页面等。
4)浏览网页时改变付款按钮状态的过程：
若用户浏览器所收到的为HTTP收款回应消息，且付款按钮新状态为打开，则根据回应消息中的收款信息提示用户汇款。若用户同意汇款，则进行汇款并发送HTTP收款确认请求消息；若新状态为关闭，则停止通过回应消息中的收款信息汇款，并按情况向服务器发送新的HTTP普通请求消息。
若有必要，浏览器可提示用户刷新页面。
5)用户向服务器汇款的过程：
用户浏览器将款项通过数字货币协议或与第三方支付的JSON/API等交互来汇给服务器，汇款可通过脚本、数字货币协议或与第三方机构交互等自动执行，方式可为在收到HTTP收款回应消息后及在生成HTTP收款确认请求消息前根据请款金额进行汇款，为防止大量小额汇款，服务器可设置最低汇款额等；
浏览器和服务器更新相应的费用与汇款等信息。
6)用户查询汇款明细的过程：
用户浏览器通过数据库模块获得相应汇款信息，并以页面或图形等方式显示。
本实施例的收款方法具有以下技术效果：
(1)本实施例通过在HTTP请求消息或回应中设置收款信息，HTTP协议与数字货币/电子货币结合，使传统的HTTP协议具有收款等金融功能，通过该收款信息由收款消息管理服务器、页面管理服务器、资金管理服务器的协同工作，在HTTP协议传输信息的同时也实现了用户终端与服务器之间的互相汇款，从而实现了价值的传递，提升了HTTP协议的金融功能应用；
(2)本实施例的收款信息设于HTTP请求消息或HTTP回应消息的头部字段，其位置具有可识别性，且其本身并不影响HTTP协议的正常信息传递和阅读，不会对页面内容造成任何影响，同时获取页面内容的信息传递过程与收 款信息实现收款的价值传递过程，信息传递过程中不涉及价值传递过程，故信息传递过程不会因为价值的传递而产生任何延迟，达到了HTTP协议信息与价值的传输互不影响的技术效果；
(3)本实施例通过收款信息由用户或页面服务端直接提供，用户不必专门的账户即可直接实现收款与付款，同时HTTP收款请求消息或HTTP收款回应消息的接收方可向任意访问者或服务器进行无障碍汇款，达到了信息与价值传递便捷性、人性化的技术效果。
上面结合附图对本发明的实施方式作了详细说明，但是本发明并不限于上述实施方式。即使对本发明作出各种变化，倘若这些变化属于本发明权利要求及其等同技术的范围之内，则仍落入在本发明的保护范围之中。

Claims (27)

  1. 一种基于HTTP协议的服务器收款***，其特征在于，包括：收款消息管理服务器、页面管理服务器、资金管理服务器；
    所述收款消息管理服务器与所述页面管理服务器和所述资金管理服务器交互协同工作；
    所述收款消息管理服务器用于接收用户发送的HTTP收款请求消息，并识别所述HTTP收款请求消息的收款信息；
    所述收款消息管理服务器还用于调度所述页面管理服务器获取页面内容，并根据所述页面内容对应的计费方式执行计费；
    所述收款消息管理服务器还用于根据所述页面内容生成HTTP收款确认回应消息，并将所述HTTP收款确认回应消息反馈给用户，以向用户提供所述页面内容；
    所述收款消息管理服务器还用于调度所述资金管理服务器根据所述计费的金额和所述收款信息向用户执行汇款操作；其中，
    所述收款信息包括收款对象、收款方式；
    所述收款信息设于所述HTTP收款请求消息的头部字段。
  2. 根据权利要求1所述的基于HTTP协议的服务器收款***，其特征在于，所述收款消息管理服务器还用于调度所述资金管理服务器对所述收款信息进行验证可用性。
  3. 根据权利要求2所述的基于HTTP协议的服务器收款***，其特征在于，还包括数据库服务器，所述数据库服务器用于存储或更新所述收款信息、所述计费方式、收款优先级；
    所述数据库服务器分别和所述收款消息管理服务器、所述资金管理服务器交互，所述收款消息管理服务器还用于调度所述数据库服务器根据所述收款优先级对所述收款信息进行选择，确定一最优收款信息作为所述汇款操作的汇款方式；
    其中，所述最优收款信息为可用的所述收款信息中所述收款对象的优先级最高且所述收款方式的优先级最高的收款信息。
  4. 根据权利要求3所述的基于HTTP协议的服务器收款***，其特征在于，所述收款消息管理服务器还用于将所述最优收款信息放入所述页面内容的表头，以向用户反馈。
  5. 根据权利要求3所述的基于HTTP协议的服务器收款***，其特征在于，所述数据库服务器还用于存储计费与汇款明细记录；
    所述收款消息管理服务器还用于接收用户发送的查询请求，调度所述资金管理服务器对所述查询请求的信息进行有效验证，根据有效的所述查询请求，所述收款消息管理服务器调度所述页面管理服务器获取所述页面内容及调度所述数据库服务器获取查询内容，并根据所述页面内容和所述查询内容生成查询结果反馈至用户。
  6. 根据权利要求1-5任意一项所述的基于HTTP协议的服务器收款***，其特征在于，还包括内外网接口，所述内外网接口包括数字货币交互服务器、第三方数字/电子货币交互服务器；
    所述数字货币交互服务器和第三方数字/电子货币交互服务器分别和所述资金管理服务器交互，用于将所述来自资金管理服务器的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证。
  7. 根据权利要求6所述的基于HTTP协议的服务器收款***，其特征在于，所述数字货币交互服务器为运行数字货币服务程序的服务器，所述第三方数字/电子货币交互服务器为支持本地或第三方接口的服务器。
  8. 根据权利要求1-5任意一项所述的基于HTTP协议的服务器收款***，其特征在于，还包括付款开关和/或收款开关，所述付款开关用于控制所述收款信息的识别功能的开启和关闭，以实现所述汇款操作的控制，所述收款开关用于控制向用户发送的HTTP回应消息中是否生成所述收款信息，以实现向用户收款的控制。
  9. 一种基于HTTP协议的用户终端收款***，其特征在于，包括：收款消息管理模块、页面管理模块、资金管理模块；
    所述收款消息管理模块与所述页面管理模块和所述资金管理模块交互协同工作；
    所述收款消息管理模块用于向页面服务端发送HTTP普通请求消息，以获取HTTP收款回应消息，并识别所述HTTP收款回应消息的收款信息；
    所述收款消息管理模块还用于调度所述资金管理模块根据所述收款信息向页面服务端执行汇款操作，并根据所述汇款操作的信息生成HTTP收款确认请求消息及发送所述HTTP收款确认请求消息，以获取具有收费的页面内容的HTTP普通回应消息；
    所述收款消息管理模块还用于调度所述页面管理模块根据所述HTTP普通回应消息显示收费的所述页面内容；其中，
    所述收款信息包括收款对象、收款方式；
    所述收款信息设于所述HTTP收款回应消息的头部字段。
  10. 根据权利要求9所述的基于HTTP协议的用户终端收款***，其特征在于，所述收款消息管理模块还用于调度所述资金管理模块对所述收款信息进行验证可用性。
  11. 根据权利要求10所述的基于HTTP协议的用户终端收款***，其特征在于，还包括数据库模块，所述数据库模块用于存储或更新汇款记录、汇款优先级；
    所述数据库模块分别和所述收款消息管理模块、所述资金管理模块交互，所述收款消息管理模块还用于调度所述数据库模块根据所述汇款优先级对所述收款信息进行选择，确定一最优收款信息作为所述汇款操作的汇款方式；
    其中，所述最优收款信息为可用的所述收款信息中所述收款对象的优先级最高且所述收款方式的优先级最高的收款信息。
  12. 根据权利要求9-11任意一项所述的基于HTTP协议的用户终端收款 ***，其特征在于，还包括内外网接口，所述内外网接口包括数字货币交互模块、第三方数字/电子货币交互模块；
    所述数字货币交互模块和第三方数字/电子货币交互模块分别和所述资金管理模块交互，用于将所述来自资金管理模块的内部请求与来自网络的外部请求进行转换以执行实际汇款或信息验证。
  13. 根据权利要求12所述的基于HTTP协议的用户终端收款***，其特征在于，所述数字货币交互模块为运行数字货币服务程序的模块，所述第三方数字/电子货币交互模块为支持本地或第三方接口的模块。
  14. 根据权利要求9-13任意一项所述的基于HTTP协议的用户终端收款***，其特征在于，还包括付款开关和/或收款开关，所述付款开关用于控制所述收款信息的识别功能的开启和关闭，以实现所述汇款操作的控制，所述收款开关用于控制向页面服务端发送的HTTP请求消息中是否生成所述收款信息，以实现向页面服务端收款的控制。
  15. 一种如权利要求1-8任意一项所述的基于HTTP协议的服务器收款***的收款方法，其特征在于，所述服务器收款***包括收款消息管理服务器、页面管理服务器、资金管理服务器，所述收款方法包括以下步骤：
    A1：所述收款消息管理服务器接收用户发送的HTTP收款请求消息，并识别所述HTTP收款请求消息的收款信息；
    A2：所述收款消息管理服务器调度所述页面管理服务器获取页面内容，所述收款消息管理服务器并根据所述页面内容对应的计费方式执行计费；
    A3：所述收款消息管理服务器根据所述页面内容生成所述HTTP收款确认回应消息，并将所述HTTP收款确认回应消息反馈给用户，以向用户提供所述页面内容；
    在所述步骤A3执行过程中或所述步骤A3之后，执行步骤A4：
    所述收款消息管理服务器调度所述资金管理服务器根据所述计费的金额和所述收款信息向用户执行汇款操作；其中，
    所述收款信息包括收款对象、收款方式；所述收款信息设于所述HTTP收款请求消息的头部字段。
  16. 根据权利要求15所述的收款方法，其特征在于，所述步骤A2中，所述收款消息管理服务器调度所述页面管理服务器获取所述页面内容的同时，所述收款消息管理服务器还调度所述资金管理服务器对所述收款信息进行验证可用性，获取可用的所述收款信息。
  17. 根据权利要求16所述的收款方法，其特征在于，所述服务器收款***还包括数据库服务器；所述收款方法的所述步骤A2中，获取可用的所述收款信息之后，所述收款消息管理服务器调度所述数据库服务器根据所述数据库服务器中的收款优先级对所述收款信息进行选择，确定一最优收款信息作为所述汇款操作的汇款方式；
    其中，所述最优收款信息为可用的所述收款信息中所述收款对象的优先级最高且所述收款方式的优先级最高的收款信息。
  18. 根据权利要求17所述的收款方法，其特征在于，所述步骤A2中，所述确定一最优收款信息之后，所述收款消息管理服务器将所述最优收款信息放入所述页面内容的表头。
  19. 根据权利要求17所述的收款方法，其特征在于，所述步骤A4之后还包括步骤A5：
    所述资金管理服务器接收所述汇款操作的结果，并将所述结果发送至所述数据库服务器进行存储。
  20. 根据权利要求17-19任意一项所述的收款方法，其特征在于，所述服务器收款***还包括内外网接口，所述内外网接口包括数字货币交互服务器、第三方数字/电子货币交互服务器；所述收款方法的所述步骤A4具体包括以下步骤：
    A41：所述资金管理服务器接收所述收款消息管理服务器的汇款调度指令；
    A42：所述资金管理服务器调度所述数据库服务器获取所述计费的金额和 所述最优收款信息；
    A43：根据所述计费的金额和所述最优收款信息，所述资金管理服务器向所述数字货币交互服务器或者所述第三方数字/电子货币交互服务器发送内部请求；
    A44：所述数字货币交互服务器或者所述第三方数字/电子货币交互服务器将所述内部请求转换为外部请求以执行所述汇款操作。
  21. 根据权利要求15-19任意一项所述的收款方法，其特征在于，所述服务器收款***还包括所述付款开关；所述收款方法的所述步骤A1中，所述识别所述HTTP收款请求消息的收款信息的过程具体包括以下步骤：
    判断所述付款开关是否已打开：
    若所述付款开关已打开，所述收款消息管理服务器识别所述HTTP收款请求消息的所述收款信息；
    若所述付款开关未打开，所述收款消息管理服务器不识别所述HTTP收款请求消息的所述收款信息。
  22. 一种基于HTTP协议的收款消息管理服务器的收款方法，其特征在于，包括以下步骤：
    B1：所述收款消息管理服务器接收用户发送的HTTP收款请求消息，并识别所述HTTP收款请求消息的收款信息；
    B2：所述收款消息管理服务器根据所述HTTP收款请求消息，发送页面调度指令，以获取页面内容；
    B3：所述收款消息管理服务器根据所述页面内容生成HTTP收款确认回应消息，并将所述HTTP收款确认回应消息反馈给用户，以向用户提供所述页面内容；
    在所述步骤B3执行的同时，执行步骤B4：
    所述收款消息管理服务器根据所述页面内容对应的计费方式执行计费；
    在所述步骤B3和所述步骤B4执行过程中或执行之后，执行步骤B5：
    所述收款消息管理服务器根据所述计费的金额和所述收款信息发送汇款调度指令，以实现向用户汇款的汇款操作；其中，
    所述收款信息包括收款对象、收款方式；所述收款信息设于所述HTTP请求消息的头部字段。
  23. 一种如权利要求9-15任意一项所述的基于HTTP协议的用户终端收款***的收款方法，其特征在于，所述用户终端收款***包括收款消息管理模块、页面管理模块、资金管理模块，所述收款方法包括以下步骤：
    C1：所述收款消息管理模块向页面服务端发送HTTP普通请求消息，以获取HTTP收款回应消息，并识别所述HTTP收款回应消息的收款信息；
    C2：所述收款消息管理模块调度所述资金管理模块根据所述收款信息向页面服务端执行汇款操作，并根据所述汇款操作的信息生成HTTP收款确认请求消息及发送所述HTTP收款确认请求消息，以获取具有收费的页面内容的HTTP普通回应消息；
    C3：所述收款消息管理模块调度所述页面管理模块根据所述HTTP普通回应消息显示收费的所述页面内容；其中，
    所述收款信息包括收款对象、收款方式；所述收款信息设于所述HTTP收款回应消息的头部字段。
  24. 根据权利要求23所述的收款方法，其特征在于，所述步骤C2中，所述汇款操作执行之前，所述收款消息管理模块还调度所述资金管理模块对所述收款信息进行验证可用性，获取可用的所述收款信息。
  25. 根据权利要求24所述的收款方法，其特征在于，所述用户终端收款***还包括数据库模块；所述收款方法的所述步骤C2中，获取可用的所述收款信息之后且所述汇款操作执行之前，所述收款消息管理模块调度所述数据库模块根据所述数据库模块中的汇款优先级对所述收款信息进行选择，确定一最优收款信息作为所述汇款操作的汇款方式；
    其中，所述最优收款信息为可用的所述收款信息中所述收款对象的优先 级最高且所述收款方式的优先级最高的收款信息。
  26. 根据权利要求25所述的收款方法，其特征在于，所述用户终端收款***还包括内外网接口，所述内外网接口包括数字货币交互模块、第三方数字/电子货币交互模块；所述收款方法的所述资金管理模块执行所述汇款操作具体包括以下步骤：
    D1：所述资金管理模块接收所述收款消息管理模块的汇款调度指令；
    D2：所述资金管理模块调度所述数据库模块获取所述收款信息的汇款金额和所述最优收款信息；
    D3：根据所述汇款金额和所述最优收款信息，所述资金管理模块向所述数字货币交互模块或者所述第三方数字/电子货币交互模块发送内部请求；
    D4：所述数字货币交互模块或者所述第三方数字/电子货币交互模块将所述内部请求转换为外部请求以执行所述汇款操作。
  27. 根据权利要求23-26任意一项所述的收款方法，其特征在于，所述用户终端收款***还包括所述付款开关；所述收款方法的所述步骤B1中，所述识别所述HTTP收款回应消息的收款信息的过程具体包括以下步骤：
    判断所述付款开关是否已打开：
    若所述付款开关已打开，所述收款消息管理模块识别所述HTTP收款回应消息的所述收款信息；
    若所述付款开关未打开，所述收款消息管理模块不识别所述HTTP收款回应消息的所述收款信息。
PCT/CN2019/097047 2019-02-25 2019-07-22 一种基于http协议的服务器、用户终端收款***及收款方法 WO2020173041A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/432,106 US20220188783A1 (en) 2019-02-25 2019-07-22 Http-based server payment collection system, http-based user terminal payment collection system, and http-based payment collection method
EP19917056.4A EP3933733A4 (en) 2019-02-25 2019-07-22 HTTP PROTOCOL-BASED SERVER, USER TERMINAL CHARGE COLLECTION SYSTEM, AND CHARGE COLLECTION METHOD

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910137752.5 2019-02-25
CN201910137752.5A CN109858902A (zh) 2019-02-25 2019-02-25 一种基于http协议的服务器、用户终端收款***及收款方法

Publications (1)

Publication Number Publication Date
WO2020173041A1 true WO2020173041A1 (zh) 2020-09-03

Family

ID=66898823

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/097047 WO2020173041A1 (zh) 2019-02-25 2019-07-22 一种基于http协议的服务器、用户终端收款***及收款方法

Country Status (4)

Country Link
US (1) US20220188783A1 (zh)
EP (1) EP3933733A4 (zh)
CN (1) CN109858902A (zh)
WO (1) WO2020173041A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115037500A (zh) * 2022-04-07 2022-09-09 水利部信息中心 一种基于配置文件检测挖矿失陷主机的方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109858902A (zh) * 2019-02-25 2019-06-07 上海风汇网络科技有限公司 一种基于http协议的服务器、用户终端收款***及收款方法
CN109981816B (zh) * 2019-03-21 2023-04-18 上海风汇网络科技有限公司 基于dns域名***的价值传输***、方法及dns服务器
CN111756619B (zh) * 2020-06-24 2022-12-27 上海风汇网络科技有限公司 一种基于电子邮件的价值传输方法及价值传输集群***
CN114004554A (zh) * 2020-07-27 2022-02-01 四川物软网联科技有限公司 运输订单管理***及方法
CN113159780A (zh) * 2021-02-03 2021-07-23 中国工商银行股份有限公司 信息校验方法、装置、设备、介质和程序产品

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101055638A (zh) * 2007-03-13 2007-10-17 中兴通讯股份有限公司 一种在网络电视中实现电子商务的***和方法
US20090006243A1 (en) * 2004-04-26 2009-01-01 Michael Davis Networked Electronic Trading System
CN102737341A (zh) * 2011-03-31 2012-10-17 中兴通讯股份有限公司 应用商店***及实现应用内购买功能的方法
CN103854191A (zh) * 2012-12-06 2014-06-11 腾讯科技（深圳）有限公司 线上应用虚拟资源自动交易方法及装置
CN109858902A (zh) * 2019-02-25 2019-06-07 上海风汇网络科技有限公司 一种基于http协议的服务器、用户终端收款***及收款方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0848361B1 (en) * 1996-12-13 1999-08-25 Telefonaktiebolaget L M Ericsson (Publ) Method and system for performing money transactions
GB2400962B (en) * 2001-05-02 2004-12-29 Virtual Access Ltd Secure payment method and system
FI20012044A (fi) * 2001-10-22 2003-04-23 Portalify Oy Menetelmä ja tietoliikenneverkko palvelujen tarjoamiseksi ja laskuttamiseksi
US8346660B2 (en) * 2004-02-26 2013-01-01 David C. Reardon System and method for two-way transfer of funds and electronic content between summa account users with gathering of behavioral metrics and management of multiple currencies and escrow accounts
CN103186852A (zh) * 2011-12-31 2013-07-03 乐活在线（北京）网络技术有限公司 网络交易的支付方法、装置及***
CN106557962A (zh) * 2015-09-24 2017-04-05 腾讯科技（深圳）有限公司 支付方法、装置及***

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090006243A1 (en) * 2004-04-26 2009-01-01 Michael Davis Networked Electronic Trading System
CN101055638A (zh) * 2007-03-13 2007-10-17 中兴通讯股份有限公司 一种在网络电视中实现电子商务的***和方法
CN102737341A (zh) * 2011-03-31 2012-10-17 中兴通讯股份有限公司 应用商店***及实现应用内购买功能的方法
CN103854191A (zh) * 2012-12-06 2014-06-11 腾讯科技（深圳）有限公司 线上应用虚拟资源自动交易方法及装置
CN109858902A (zh) * 2019-02-25 2019-06-07 上海风汇网络科技有限公司 一种基于http协议的服务器、用户终端收款***及收款方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115037500A (zh) * 2022-04-07 2022-09-09 水利部信息中心 一种基于配置文件检测挖矿失陷主机的方法
CN115037500B (zh) * 2022-04-07 2024-02-13 水利部信息中心 一种基于配置文件检测挖矿失陷主机的方法

Also Published As

Publication number Publication date
EP3933733A1 (en) 2022-01-05
EP3933733A4 (en) 2022-11-30
US20220188783A1 (en) 2022-06-16
CN109858902A (zh) 2019-06-07

Similar Documents

Publication Publication Date Title
WO2020173041A1 (zh) 一种基于http协议的服务器、用户终端收款***及收款方法
US7302411B2 (en) Electronic Billing with required viewing of supplemental information
US8606247B2 (en) Systems and methods for billing for a network enabled application through a network platform regardless of whether the network enabled application is hosted by the platform
US20080288582A1 (en) Systems and methods for passing application pods between multiple social network service environments
US20120296823A1 (en) Content owner verification and digital rights management for automated distribution and billing platforms
US20020026423A1 (en) Automated usage-independent and location-independent agent-based incentive method and system for customer retention
US20030208406A1 (en) Method and apparatus for processing one or more value bearing instruments
US8635156B2 (en) Converting paper invoice to electronic form for processing of electronic payment thereof
US20040128257A1 (en) Method and apparatus for administering one or more value bearing instruments
JP2008504612A (ja) ペイメント処理方法システム
US20040128516A1 (en) Method and apparatus for verifying bearing instruments
WO2019218757A1 (zh) 基于会员特征码的支付方法以及装置
JP2006518515A (ja) オンライン商取引のシステムおよび方法
CA2675486A1 (en) System and method for verification of identity for transactions
EP1902414A2 (en) Billing system and method for micro-transactions
CN108960941A (zh) 电子支付开票方法
US20060195397A1 (en) Centralized electronic bill presentment
JP7428424B2 (ja) 個人情報提供システムおよび個人情報提供方法並びに個人情報提供プログラム
US20060195396A1 (en) Centralized customer care for electronic payments and other transactions via a wide area communications network
JP4129291B1 (ja) 決済システムとの連携機能を有するアフィリエイトシステム
US20160180299A1 (en) Payment unification service
CN111192041B (zh) 资源转移方法和资源转移设备
KR100364013B1 (ko) 인터넷 상에서 온라인으로 통합요금 청구 및 납부를 대행하는 방법
US20150170193A1 (en) System and method for distributing and processing coupons
US10068236B2 (en) Methods and arrangements for third party charging authorization for mobile service providers

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19917056

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019917056

Country of ref document: EP

Effective date: 20210927