WO2021258737A1 - 一种基于电子邮件的价值传输方法及价值传输集群系统 - Google Patents

一种基于电子邮件的价值传输方法及价值传输集群系统 Download PDF

Info

Publication number
WO2021258737A1
WO2021258737A1 PCT/CN2021/074894 CN2021074894W WO2021258737A1 WO 2021258737 A1 WO2021258737 A1 WO 2021258737A1 CN 2021074894 W CN2021074894 W CN 2021074894W WO 2021258737 A1 WO2021258737 A1 WO 2021258737A1
Authority
WO
WIPO (PCT)
Prior art keywords
remittance
mail
address
server
value transmission
Prior art date
Application number
PCT/CN2021/074894
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 US18/011,186 priority Critical patent/US20230246992A1/en
Publication of WO2021258737A1 publication Critical patent/WO2021258737A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/42—Mailbox-related aspects, e.g. synchronisation of mailboxes
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
    • 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
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • 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
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/386—Payment protocols; Details thereof using messaging services or messaging apps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/48—Message addressing, e.g. address format or anonymous messages, aliases
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • the invention relates to the technical field of value transmission, in particular to an email-based value transmission method and a value transmission cluster system.
  • Prior art 1 application number CN201910217445.8, and the title of the invention are "based on DNS domain name system value transmission system, method and DNS server", prior art 2, application number is CN201910092306.7, invention title is "an e-mail system, mail sending and receiving method integrating currency protocol", prior art
  • Both the prior art 1 and the prior art 2 have realized the synchronization of sending and receiving electronic money by e-mail, but neither the prior art 1 nor the prior art 2 has fully utilized the IP address and interaction capability of the e-mail server itself, which causes resources in some scenarios. waste.
  • this application provides an e-mail-based value transmission method and a value transmission cluster system.
  • the present invention provides an email-based value transmission method, which includes the steps:
  • the remittance operation is performed according to the receiving address.
  • the obtaining the payment address of the payee based on the interactive operation of the email interactive server specifically includes: querying the payee address corresponding to the payee's email address or querying the DNS based on the fund query function configured by the email interactive server The receiving address corresponding to the mail domain name of the payee configured in the server.
  • the obtaining the payment address of the payee based on the interactive operation of the e-mail interactive server specifically includes: querying the payment address based on the SMTP protocol supporting the remittance instruction configured by the e-mail interactive server.
  • the payment address is a unified interface address or a digital/electronic money address corresponding to the target mail address.
  • the remittance operation further includes sending remittance information to the beneficiary.
  • the present invention also provides an email-based value transmission cluster system, including: a mail client, several remittance mail management server clusters, and each remittance mail management server cluster is respectively configured with a corresponding email interaction server;
  • the remittance mail management server cluster is respectively interactively connected with the mail client and the corresponding email interaction server;
  • the remittance mail management server is used to receive mail sending request information sent by the mail client, and when the mail sending request information contains remittance information, the remittance mail management server is also used to send the remittance information to The email interactive server;
  • the email interaction server is used to send and receive emails, and is also used to obtain a remittance address according to the remittance information, and feed back the remittance address to the remittance mail management server cluster;
  • the remittance mail management server cluster is also used to perform remittance operations according to the remittance address.
  • the email interaction server is provided with a fund query module, and the fund query module is used to query the payee address corresponding to the payee's email address or query the payee corresponding to the payee's email domain name configured in the DNS server address.
  • the e-mail interaction server queries the remittance address based on the configured SMTP protocol supporting remittance instructions.
  • the payment address is a unified interface address or a digital/electronic money address corresponding to the target mail address.
  • each of the remittance mail management server clusters is respectively configured with a mail domain name, so that the remittance mail management server cluster performs a remittance operation according to the mail domain name.
  • value transmission can also be realized by simply extending the existing SMTP protocol without additional protocols.
  • Figure 1 is a flow chart of the value transmission method based on e-mail
  • Figure 2 is a flowchart of the client connecting to the remittance (mail) server;
  • Figure 3 is the connection flow chart of the IP address query of the email interactive server
  • Figure 4 is another connection flow chart of the email interactive server IP address query
  • Figure 5 is a flow chart of remittance based on SMTP protocol
  • Figure 6 is the basic flow chart of remittance
  • Figure 7 is a value transmission architecture diagram of the email interactive server with the function of querying the receiving address
  • Figure 8 is a structure diagram of value transmission based on the SMTP protocol to query the receiving address
  • Fig. 9 is a schematic diagram of the cluster system of Fig. 7;
  • Fig. 10 is a schematic diagram of the cluster system of Fig. 8.
  • Figure 11 is a schematic diagram of an independent remittance cluster system.
  • Digital/encrypted currency decentralized digital currency or tokens, generally produced through “mining” work, such as Bitcoin and Litecoin, etc., hereinafter referred to as “digital currency”, and its category also includes tokens that rely on its network circulation , Such as USDT stable currency, etc.
  • Electronic money electronic traditional/legal currency or tokens and related payment services, such as paypal and alipay and their virtualized electronic money.
  • Remittance email An email with a remittance logo in the body, such as "Pay-To” (ie, "Pay To”), and the remittance is synchronized when sent.
  • Fund management server The network protocol is used to transfer value, and the receiving and remitting parties can independently settle settlements based on the fund management server.
  • DNS server Domain Name System.
  • the application for the realization of an email interactive server is in addition to the traditional email receiving/sending function, but also Similar to the functions of the digital/electronic money service unified interface interactive server, the e-mail interactive server completes functions such as query and registration of the payment address.
  • This embodiment provides an email-based value transmission method.
  • the flowchart is shown in FIG. 1 and specifically includes the following steps.
  • S100 Establish a connection between the client and the remittance mail management server of the remittance party.
  • S200 Establish a connection with the IP address of the email interaction server between the sender and the receiver.
  • S300 Obtain the payment address of the payee based on the interactive operation of the email interactive server.
  • S400 Perform a remittance operation according to the receiving address.
  • step S100 is also included, that is, a connection between the client and the remittance party's remittance mail management server is first established.
  • the client can search for the corresponding remittance mail management server or remittance management server IP through the MX or other fields of the DNS according to the domain name of the user/remitter/sender email address. If there is a corresponding IP, you can try to connect to that IP. If the connection is successful, relevant operations will be performed through the e-mail interactive server. If the connection fails, the user will be prompted about the relevant situation and can try to connect to the default server. If there is no corresponding IP, you can also try to connect to the default server.
  • the default server accepts all domain addresses as a temporary supplement. If some domain names are directed to a specific remittance/remittance mail management server in the future, the relevant domain addresses in the default server can be transferred to the new remittance/remittance mail management server.
  • step S200 referring to the prior art 1, the IP address of the email interaction server corresponding to the domain name in the DNS is searched, and then the connection of the email interaction server IP address between the remittance party and the payee is established. It should be noted here that in step S200, it can be more general to refer to the establishment of a connection between the sender and the recipient of the email interaction server IP address, because as long as it is to send and receive emails, it is necessary to establish a connection between the two parties. The IP address of the email interaction server is connected.
  • step S300 the receiving address of the payee is obtained based on the interactive operation of the email interactive server.
  • the receiving address can be obtained in the following ways.
  • the first method of obtaining obtaining the payment address through the interactive server, as shown in Figure 3. Specifically, the remittance party queries the payment address corresponding to the recipient’s email address and possible internal unique transaction numbers to obtain the payment address.
  • a query module similar to the digital/electronic currency service unified interface interactive server is added to the email interactive server, so that the sender and receiver can obtain digital/electronic currency receipts through the interaction of the email interactive server running the module address. Since the IP address of the email interaction server can be obtained through the MX field of the DNS server, there is no need to query other fields such as CX.
  • the second method of obtaining Obtain the payment address through the DNS server, as shown in Figure 4. Specifically, the remittance party queries the DNS server for the payment address corresponding to the recipient's mail domain name to obtain the payment address returned by the DNS server. It should be further noted that when obtaining the remittance address through the DNS server, there is no need to establish a connection to the IP address of the e-mail interaction server between the remittance party and the remittance party, but the relevant fields in the DNS server are configured with corresponding Receiving address.
  • the receiving address is a unified digital/electronic currency receiving address
  • you can add a new record to the mail domain name in the DNS for example, add "under the domain name "mail.abcd.com” TXT" type record
  • its content can be the unified collection address of digital/electronic money, such as "1A2B3C”.
  • the remitter After the remitter obtains the address, it can first generate the possible transaction code for remittance to the address, and notify the remittance party of relevant information, such as the transaction number, by sending an email or server interaction. You can actually remit money to that address afterwards.
  • the third method of obtaining obtaining the receiving address through the SMTP protocol. Specifically, the sender sends a query command through the SMTP protocol, and the receiving party returns the receiving address and the internal unique transaction number through the SMTP protocol to obtain the receiving address.
  • the flow chart of value transmission based on SMTP protocol is shown in Figure 5.
  • the specific implementation of the third acquisition method is:
  • PAMT ADDR i.e. "Payment Address”
  • PAMT TO i.e. "Payment To”
  • PAMT ADDR ⁇ Payee Address> Unit Service Provider ID (optional)
  • PAMT TO ⁇ Payee Address> Amount Unit Transaction Number Service Provider ID (optional)
  • the interaction example is as follows:
  • the "PAMT TO" instruction can be submitted to the server before and after the transaction actually occurs. But preferably, it should be handed over to the server before the transaction number has been generated but the actual transaction has not been performed, especially for digital currency remittances, so as not to be reported by other users and cause the remittance to be mistakenly transferred to other email addresses. For example, for Bitcoin remittance, if the actual transaction is broadcasted and then submitted to the recipient’s email server, other users can obtain the public transaction number first, and register the payment to another email through a similar PAMT TO instruction. Address, causing losses.
  • the "PAMT TO" command can also be omitted, and the relevant information can be placed in the header of the email instead. Refer to Prior Art 2.
  • verification can also be completed by means of special character strings or public/private key signatures, for example:
  • PAMT ADDR ⁇ Payee Address> Unit Service Provider ID (optional);
  • the interaction example is as follows:
  • the aforementioned unique internal transaction identification string can be randomly generated and recorded during each query.
  • client instructions can be submitted to the server at any time, even if the actual transaction has been performed, without worrying about being received by other users Snatch the report.
  • step S400 the remittance operation is performed according to the receiving address.
  • the specific remittance operation is as follows, and the basic remittance process is shown in Figure 6:
  • the remittance party's fund interaction server queries the IP of the recipient's fund interaction server through DNS, and interacts with it to obtain the remittance address.
  • the receiving address can be either a unified interface address or a digital/electronic currency address corresponding to the target email address.
  • the remittance party needs to additionally inform the remittance party of the remittance information corresponding to the fund interaction server, so that the remittance party can correctly carry out internal distribution.
  • the sender can first generate the transaction instruction code and obtain the transaction number, and then inform the receiver of the corresponding information of the fund interaction server, such as the transaction number and the corresponding e-mail address of the receiver, and finally perform the actual broadcast money transfer. If the transaction number cannot be obtained in advance, it is better to perform the actual remittance after informing the recipient of the information.
  • the fund interactive server of the payee After receiving the transaction information provided by the remitter, the fund interactive server of the payee sends it to the fund management server, and the latter records it. After the recipient's fund interaction/management server obtains the actual payment and transaction number from the digital/electronic currency network, it can compare the relevant records and update the corresponding receiving account to complete the payment.
  • the receiving address is a digital/electronic currency address corresponding to the target mail address
  • the remitting party does not need to inform the beneficiary of the additional information of the fund interaction server, and only needs to realize the remittance.
  • the payee obtains the actual payment and transaction information from the digital/electronic money network, and retrieves the corresponding receiving account according to different addresses, and updates it to complete the payment.
  • the remitter can also provide additional information to the recipient's interactive server, such as the remitter's email address.
  • a different digital currency address can be used for the same destination email address each time the remittance is made.
  • the uniform interface address is used as the payment address.
  • Adopting this method has the following advantages: 1. Since all receiving accounts use the same receiving address, the information of the payee can be protected to prevent leakage. For example, for Bitcoin remittance, if the email address corresponds to the digital/electronic currency address, the user can get the corresponding digital/electronic currency address by sending money to a certain email address, and pass the block from the address The browser obtains other information of the payee, such as the accumulated payment amount and the number of remittances. If the address is not replaced in the future, all the collection records of the payee will be publicly available, which will cause the leakage of the payee’s economic information; 2.
  • Additional information can be used to ensure the reliability of the remittance process.
  • information such as the amount, the remitter’s email address, and the transaction number, the identity and transaction records of the remitter can be guaranteed to be authentic and reliable, and others can be prevented from impersonating.
  • the payee can record the relevant information in the database, such as the mail address and the corresponding transaction number and amount.
  • the payee obtains the actual remittance information from the digital/electronic currency network through regular scans or remote calls, it updates the relevant email address records based on the corresponding information previously registered, such as increasing or decreasing the corresponding amount. At this point, a remittance is completed.
  • the value transmission method provided in this embodiment supports obtaining, registering, and transmitting value through an email interactive server, without the need to use a digital/electronic money service unified interface server.
  • a digital/electronic money service unified interface server Using a unified interface address or a digital/electronic currency address corresponding to the receiving e-mail, the remittance/remittance mail server with the bound domain name can safely, efficiently and economically realize value transmission through the external mail address of the system.
  • this embodiment provides an email-based value transmission cluster system.
  • the value transmission cluster system provided in this embodiment can be an independent remittance cluster system or a cross-platform remittance mail cluster system.
  • This embodiment takes the cross-platform remittance mail cluster system as an example. Based on this, those skilled in the art can obtain an independent remittance cluster system through transformation.
  • cross-platform remittance mail cluster system clusters certain servers in the cross-platform remittance mail system, before introducing the cross-platform remittance mail cluster system, the cross-platform remittance mail system will be introduced first.
  • the improved cross-platform remittance mail system is shown in Figure 7, including mail client 1, remittance mail management server 2, email management server 3, user authentication server 4, fund management server 5, database server 6, email interaction server 7 , Digital currency interactive server 8 and third-party digital/electronic currency interactive server 9.
  • the email interaction server 7 is provided with a fund query module, which is used to query the payment address corresponding to the recipient’s mail address or query the payment address corresponding to the recipient’s mail domain name configured in the DNS server; the email
  • the interactive server 7 also assumes a function similar to an interactive server with a unified interface for digital/electronic money services.
  • FIG 8. Another improved cross-platform remittance mail system is shown in Figure 8.
  • the structure of the cross-platform remittance mail system is the same as that of the cross-platform remittance mail system in Figure 7. The difference is that the electronic The email interaction server 7 is configured with an SMTP protocol that supports remittance instructions, so that the email interaction server 7 in the cross-platform remittance mail system queries the receiving address based on the configured SMTP protocol that supports remittance instructions; the email server 7 is in addition to the traditional In addition to the e-mail receiving/sending function, an extended SMTP command that supports remittance is also used to complete functions such as inquiry and registration of the receiving address.
  • the price transmission cluster system (that is, a cross-platform remittance mail cluster system) provided in this embodiment includes a mail client 1, a database server 6, a digital currency interactive server 8, a third-party digital/electronic currency interactive server 9, and a number of remittance emails.
  • the management server cluster 10 and each remittance mail management server cluster are respectively configured with a corresponding email interaction server 7.
  • the remittance mail management server cluster 10 is interactively connected with the mail client 1 and the corresponding email interaction server 7; the remittance mail management server cluster 10 is used to receive the mail sending request information sent by the mail client, and the mail sending request information
  • the remittance mail management server cluster 10 is also used to send the remittance information to the email interactive server 7;
  • the email interactive server 7 is used to send and receive emails, and is also used to obtain the receiving address according to the remittance information, and to receive the payment.
  • the address is fed back to the remittance mail management server cluster 10; the remittance mail management server cluster 10 is also used to perform remittance operations according to the receiving address.
  • this embodiment provides corresponding two different cross-platform remittance mail cluster systems.
  • the cross-platform remittance mail cluster system provided in this embodiment is shown in FIG. 9, and corresponding to FIG. 8, another cross-platform remittance mail cluster system provided in this embodiment is shown in FIG. 10.
  • the remittance mail management server cluster 10 in FIG. 9 and FIG. 10 includes a remittance management server, a user authentication server, an email management server, and a fund management server.
  • three remittance mail management server clusters 10 can be set up, namely, remittance mail management server cluster A, remittance mail management server cluster B, and remittance mail management server cluster C, and configure corresponding mail domain names for each remittance mail management server cluster.
  • the mail domain name configured for remittance mail management server cluster A is @mail1.com
  • the mail domain name configured for remittance mail management server cluster B is @mail2.com
  • the mail domain name configured for remittance mail management server cluster C is @mail3.com.
  • each remittance mail management server cluster may be configured with a different number of domain names.
  • those skilled in the art can transform the above-mentioned cross-platform remittance mail cluster system to realize an independent remittance cluster system, for example, replace the email interaction server 7 in the above-mentioned cross-platform remittance mail cluster system
  • the digital/electronic money service unified interface interactive server 11, and the email management server 3 in the remittance mail management server cluster 10 in the cross-platform remittance mail cluster system are deleted to form the remittance management server cluster 12 to realize independent remittances
  • the cluster system as shown in FIG. 11, wherein the remittance management server cluster 12 only includes a remittance management server, a user authentication server, and a fund management server.
  • the value transmission cluster system can be implemented by one of the following architectures.
  • the current Bitcoin full node is about 300G
  • the synchronization requires 4 cores 8G and a large-capacity SSD server runs for about 5-10 days when the bandwidth is about 5M and the network is in good condition, whether it is computing, storage, bandwidth, traffic or Both are extremely time-consuming.
  • the release efficiency of the new system can be greatly improved and the cost can be significantly reduced.
  • the value transmission between different domain names and addresses can be done either through the digital/electronic currency network or through internal database updates. In different cluster systems, the value transmission between domain names and addresses needs to pass through the digital/electronic currency network.
  • the transfer of value between different domain names and addresses can be done either through the digital/electronic currency network or through internal database updates. If the domain name address does not belong to this system, the value transmission between them needs to pass through the digital/electronic money network.
  • Architecture 2 and Architecture 3 can also be in the same cluster system, that is, some remittance management servers correspond to their unique domain names, and some remittance management servers can correspond to multiple domain names.
  • fund management servers that belong to the same cluster system and share the same digital/electronic currency interactive server (that is, running digital currency wallet programs or digital/electronic currency external interactive programs) Use internal transfers, not externals.
  • the fund management server receives/remits money through the unified interface server, first confirm whether the servers of the sending and receiving parties are in the same cluster system. If so, the internal transfer is realized through database update, etc., if not, it is carried out through the digital currency or digital/electronic currency network External transfers.
  • the value transmission cluster system provided in this embodiment is flexible and diverse.
  • a cross-platform remittance mail cluster system can be used for value transmission, or an independent remittance cluster system can be used for value transmission.
  • No matter which type of cluster system can be used Any of the above-mentioned cluster architectures processes the unified payment address and multiple payment addresses, so that the increase or decrease of multiple domain name mail addresses is safe, flexible, and cost-effective.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Development Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Computer Hardware Design (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种基于电子邮件的价值传输方法及价值传输集群系统，价值传输方法包括步骤：建立汇款方与收款方之间的电子邮件交互服务器IP地址的连接；基于电子邮件交互服务器的交互操作获取收款方的收款地址；根据收款地址进行汇款操作。本发明提供的价值传输方法支持通过电子邮件交互服务器获得、注册并传输价值，无需再通过数字/电子货币服务统一接口服务器。采用统一接口地址或与收款电子邮件对应的数字/电子货币地址，使绑定域名的汇款/汇款邮件服务器能安全高效且经济地通过系统外部的邮件地址实现价值传输。通过结合集群系统架构，使用户能灵活地增减多域名及邮件地址，适合包括中小型公司，云服务商、企业与个人等在内的各类用户。

Description

一种基于电子邮件的价值传输方法及价值传输集群系统 技术领域
本发明涉及价值传输技术领域，具体涉及一种基于电子邮件的价值传输方法及价值传输集群系统。
背景技术
随着因特网的普及，电子邮件已成为广泛使用的交流工具，在商业沟通中尤为重要。作为一种文本文件信息，其内容也具有较高法律效用。然而因缺乏跨平台价值传输能力，传统电子邮件系统只能成为信息载体，无法承担金融职责，因此极大限制了其应用范围。与此同时，尽管银行或第三方支付承担了价值传输的主要职责，但其信息传递能力很弱，业务模式也与电子邮件系统差别较大，基本属完全不同的两种形态。
另一方面，目前区块链与数字货币(如比特币等)的发展方向主要参照银行或第三方支付，但难以获得类似的传输效率与法律保障，从而缺乏实际应用基础，无法真正体现区块链与数字货币的价值。同时匿名性也导致数字货币难以获得必要的法律支撑与监管。
与此同时，电子邮件与数字货币具有天然相似性(例如匿名、无障碍跨平台传输、传输成本低且不可回撤等)，在先技术1，申请号为CN201910217445.8，发明名称为“基于DNS域名系统的价值传输系统、方法及DNS服务器”，在先技术2，申请号为CN201910092306.7，发明名称为“一种融合货币协议的电子邮件系统、邮件发送、接收方法”，在先技术1和在先技术2均实现了电子邮件同步收发电子货币，但是，在先技术1和在先技术2均没有充分利用电子邮件服务器本身的IP地址与交互能力，从而在某些场景下造成资源浪费。
发明内容
针对电子邮件收发数字和/或电子货币存在的缺陷，本申请提供一种基于电子邮件的价值传输方法及价值传输集群系统。
本发明的技术方案如下：
本发明提供一种基于电子邮件的价值传输方法，包括步骤：
建立汇款方与收款方之间的电子邮件交互服务器IP地址的连接；
基于电子邮件交互服务器的交互操作获取收款方的收款地址；
根据所述收款地址进行汇款操作。
进一步优选的，所述基于电子邮件交互服务器的交互操作获取收款方的收款地址，具体包括：基于电子邮件交互服务器配置的资金查询功能查询收款方邮件地址对应的收款地址或者查询DNS服务器中配置的收款方邮件域名对应的收款地址。
进一步优选的，所述基于电子邮件交互服务器的交互操作获取收款方的收款地址，具体包括：基于电子邮件交互服务器配置的支持汇款指令的SMTP协议查询收款地址。
进一步优选的，所述收款地址为统一接口地址或为与目标邮件地址对应的数字/电子货币地址。
进一步优选的，若所述收款地址为统一接口地址时，所述汇款操作还包括向收款方发送汇款信息。
本发明还提供一种基于电子邮件的价值传输集群系统，包括：邮件客户端、若干个汇款邮件管理服务器集群、各个汇款邮件管理服务器集群分别配置有相应的电子邮件交互服务器；
所述汇款邮件管理服务器集群分别与所述邮件客户端和对应的电子邮件交互服务器交互连接；
所述汇款邮件管理服务器用于接收所述邮件客户端发送的邮件发送请求信息，且所述邮件发送请求信息中含有汇款信息时，所述汇款邮件管理服务器还用于将所述汇款信息发送至所述电子邮件交互服务器；
所述电子邮件交互服务器用于收发邮件，还用于根据所述汇款信息获取收款地址，并将所述收款地址反馈至所述汇款邮件管理服务器集群；
所述汇款邮件管理服务器集群还用于根据所述收款地址进行汇款操作。
进一步优选的，所述电子邮件交互服务器设置有资金查询模块，所述资金查询模块用于查询收款方邮件地址对应的收款地址或者查询DNS服务器中配置的收款方邮件域名对应的收款地址。
进一步优选的，所述电子邮件交互服务器基于配置的支持汇款指令的SMTP协议查询收款地址。
进一步优选的，所述收款地址为统一接口地址或为与目标邮件地址对应的数字/电子货币地址。
进一步优选的，各个所述汇款邮件管理服务器集群分别配置有邮件域名，以使所述汇款邮件管理服务器集群根据所述邮件域名进行汇款操作。
本发明提供的基于电子邮件的价值传输方法及价值传输集群系统，具有以下效果：
1、支持通过电子邮件交互服务器获得、注册并传输价值，无需再通过数字/电子货币服务统一接口服务器。
2、采用统一接口地址或与收款电子邮件对应的数字/电子货币地址，使绑定域名的汇款/汇款邮件服务器能安全高效且经济地通过系统外部的邮件地址实现价值传输。
3、除统一接口协议外，也可通过简单扩展现有SMTP协议来实现价值传输，无需额外协议。
4、通过结合集群系统架构，使用户能灵活地增减多域名及邮件地址，适合包括中小型公司，云服务商、企业与个人等在内的各类用户。
附图说明
图1为基于电子邮件的价值传输方法流程图；
图2为客户端连接汇款(邮件)服务器流程图；
图3为电子邮件交互服务器IP地址查询连接流程图；
图4为另一方式的电子邮件交互服务器IP地址查询连接流程图；
图5为基于SMTP协议汇款流程图；
图6为汇款基本流程图；
图7为电子邮件交互服务器具有查询收款地址功能的价值传输架构图；
图8为基于SMTP协议查询收款地址的价值传输架构图；
图9为图7的集群系统示意图；
图10为图8的集群系统示意图；
图11为独立的汇款集群系统示意图。
具体实施方式
下面通过具体实施方式结合附图对本发明作进一步详细说明。
本申请中用到的术语定义如下：
数字/加密货币：去中心化的数字货币或通证，一般通过“挖矿”工作产生，如比特币和莱特币等，下文简称“数字货币”，其范畴也包括依赖其网络流通的代币，如USDT稳定币等。
电子货币：电子化的传统/法定货币或代币及相关支付服务，如paypal和alipay及其虚拟化电子货币等。
普通邮件：普通的电子邮件。
汇款邮件：信体含汇款标识的电子邮件，例如”Pay-To”(即”Pay To”)， 并且发送时同步汇出款项。
资金管理服务器：采用网络协议以传输价值，收、汇款双方基于资金管理服务器能独立进行结算。
DNS服务器：Domain Name System。
基于电子邮件与数字货币具有天然相似性，如，匿名、无障碍跨平台传输、传输成本低且不可回撤等，因此申请实现电子邮件交互服务器除传统的电子邮件收/发功能外，还承担了类似数字/电子货币服务统一接口交互服务器的功能，基于电子邮件交互服务器完成收款地址的查询与注册等功能。
实施例一：
本实施例提供一种基于电子邮件的价值传输方法，其流程图如图1所示，具体包括以下步骤。
S100：建立客户端到汇款方的汇款邮件管理服务器的连接。
S200：建立汇款方与收款方之间的电子邮件交互服务器IP地址的连接。
S300：基于电子邮件交互服务器的交互操作获取收款方的收款地址。
S400：根据收款地址进行汇款操作。
下面对上述各步骤进行详细说明。
建立汇款方与收款方之间的电子邮件交互服务器IP地址连接之前，还包括步骤S100，即先建立客户端到汇款方的汇款邮件管理服务器的连接。在步骤S100中，如图2所示，客户端可根据用户/汇款人/发件人邮件地址域名通过DNS的MX或其它字段查找对应的汇款邮件管理服务器或汇款管理服务器IP。若存在对应IP，则可尝试连接该IP。如连接成功，则通过该电子邮件交互服务器进行相关操作。若连接失败，则提示用户相关情况，并可尝试连接默认服务器。若不存在对应IP，则亦可尝试连接默认服务器。
与域名相关的汇款/汇款邮件管理服务器不同，默认服务器可接受所有域名地址，以作为临时补充。若日后某些域名被指向特定的汇款/汇款邮件管理服务器，则默认服务器中相关的域名地址可转移至新的汇款/汇款邮件管理服务器。
在步骤S200中，参照在先技术1，通过查找DNS中域名所对应的电子邮件交互服务器IP地址，然后建立汇款方与收款方之间的电子邮件交互服务器IP地址的连接。在此需要说明的是，在步骤S200中可以更加泛指建立发件人与收件人之间的电子邮件交互服务器IP地址的连接，因为，只要是收发电子邮件，就需建立双方之间的电子邮件交互服务器IP地址连接。
在步骤S300中，基于电子邮件交互服务器的交互操作获取收款方的收款地址，具体可以通过以下几种方式获取收款地址。
第一种获取方式：通过交互服务器获得收款地址，如图3所示，具体的，汇款方查询收款方邮件地址对应的收款地址及可能的内部唯一交易号，以获取收款地址。
例如，对于汇款邮件系统，在电子邮件交互服务器中增加类似数字/电子货币服务统一接口交互服务器的查询模块，从而使收发双方通过运行该模块的电子邮件交互服务器交互来获得数字/电子货币收款地址。由于电子邮件交互服务器的IP地址可通过DNS服务器的MX字段获得，因此无需再查询CX等其他字段。
第二种获取方式：通过DNS服务器获得收款地址，如图4所示，具体的，汇款方查询DNS服务器收款方邮件域名对应的收款地址，以获取DNS服务器反馈的收款地址。进一步需要说明的是，通过DNS服务器获得收款地址时，可以不需要先建立汇款方与收款方之间的电子邮件交互服务器IP地址的连接，而是DNS服务器中的相关字段配置有相应的收款地址。
例如，对于汇款邮件或独立的汇款系统，若收款地址为数字/电子货币的统一收款地址，则可在DNS中对邮件域名增加新记录，例如”mail.abcd.com”域名下增加“TXT”类型记录，其内容可为数字/电子货币的统一收款地址，如“1A2B3C”。汇款方获得该地址后，可先行生成向该地址汇款的可能的交易编码，并通过发送电子邮件或服务器交互向收款方告知相关信息，如交易号等。之后可实际向该地址汇款。如不能事先获得交易号，则较优地，可在告知收款方信息后进行实际汇款。此方法需要确保与DNS服务器沟通的安全性，以免收款地址被篡改，为此可使用如DNSSEC等协议。
第三种获取方式：通过SMTP协议获得收款地址，具体的，汇款方通过SMTP协议发出查询指令，收款方通过SMTP协议返回收款地址及内部唯一交易号，以获取收款地址。基于SMTP协议实现价值传输的流程图如图5所示。
其中，第三种获取方式的具体实现方式是：
对于汇款邮件系统，参考RFC5321并扩展现有SMTP指令集，在其中增加新指令以获得收件人的数字/电子货币收款地址与其它信息。例如”PAMT ADDR”(即”Payment Address“)和/或”PAMT TO”(即“Payment To”)，其格式可为：
PAMT ADDR：<收款人地址>单位服务商标识(可选)
250 Ok：电子/数字货币收款地址
PAMT TO：<收款人地址>数额单位交易号服务商标识(可选)
250 Ok
交互样例如下：
客户端查询指令：PAMT ADDR：<abcd1234@abcd.com>BTC
服务器回应：250 Ok：1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa
客户端汇款指令：PAMT TO：<abcd1234@abcd.com>50 BTC 4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b
服务器回应：250 Ok
其中“PAMT TO”指令可以在交易实际发生前后提交给服务器。但较优地，应在交易号已生成，但尚未进行实际交易前提交给服务器，特别是对数字货币汇款，以免被其他用户抢报，导致汇款误转给其它电子邮件地址。例如，对于比特币汇款，若在实际交易广播发生后再提交给收款方电子邮件服务器，则其他用户可抢先获得公开的交易号，并抢先通过类似的PAMT TO指令将款项注册给另一邮件地址，从而造成损失。
另一方面，”PAMT TO”指令也可省略，转而将相关信息放在邮件头部，参照在先技术2。
进一步，对于扩展SMTP样例，也可采用特殊字符串或公/私钥签名等方式完成验证，例如：
PAMT ADDR：<收款人地址>单位服务商标识(可选)；
250 Ok：电子/数字货币收款地址新交易所对应的唯一内部交易标识字符串；
PAMT TO：<收款人地址>数额单位交易号唯一内部交易标识字符串服务商标识(可选)；
250 Ok；
交互样例如下：
客户端查询指令：PAMT ADDR：<abcd1234@abcd.com>BTC；
服务器回应：250 Ok：1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa23rj89wpgjas8e；
客户端汇款指令：PAMT TO：<abcd1234@abcd.com>50 BTC 4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b23rj89wpgjas8e；
服务器回应：250 Ok。
上述的唯一内部交易标识字符串可在每次查询时随机生成并记录。在此情况下，由于内部交易标识字符串存在唯一性，且仅为查询/回应方所知，因此客户端指令可在任意时间提交给服务器，即便已进行了实际交易，而无需担心被 其他用户抢报。
在步骤S400中，根据收款地址进行汇款操作，具体汇款操作如下，其汇款基本流程如图6所示：
1)汇款方资金交互服务器通过DNS查询到收款方资金交互服务器的IP，并与其交互来获得收款地址。收款地址既可为统一接口地址，也可为与目标邮件地址对应的数字/电子货币地址。
2)若收款地址为统一接口地址，则汇款方需额外告知收款方资金交互服务器对应的汇款信息，以使收款方能正确进行内部派发。例如，若为比特币汇款，则汇款方可先生成交易指令码并获得交易号，之后告知收款方资金交互服务器相应信息，如交易号与对应的收款电子邮件地址，最后通过广播进行实际汇款。如不能事先获得交易号，则较优地，可在告知收款方信息后进行实际汇款。收款方资金交互服务器在收到汇款方提供的交易信息后将其发给资金管理服务器，并由后者加以记录。当收款方资金交互/管理服务器从数字/电子货币网络得到实际款项与交易号后，可比照相关记录并更新对应的收款账户，从而完成收款。
3)若收款地址为与目标邮件地址对应的数字/电子货币地址，则通常汇款方无需告知收款方资金交互服务器额外信息，只需实现汇款即可。收款方从数字/电子货币网络得到实际款项与交易信息，并根据不同地址检索出对应的收款账户，从而进行更新以完成收款。某些情况下汇款方也可向收款方交互服务器提供额外信息，例如汇款人邮件地址等。对于数字货币汇款，为安全起见，可在每一次汇款时对同一目标邮件地址使用不同的数字货币地址。
优选的，采用统一接口地址作为收款地址。采用此方式具有以下优点：1.由于所有收款账户均采用同一收款地址，因此可保护收款人资料，防止外泄。例如，对于比特币汇款，若采用邮件地址与数字/电子货币地址对应的方式，则用户可通过向某一邮件地址汇款的方式得到其对应的数字/电子货币地址，并由该地址通过区块浏览器得到收款方的其它信息，例如累计收款额与汇款笔数等。若日后该地址未作替换，则该收款人所有收款记录均可公开获得，从而造成收款人经济信息的外泄；2.可通过额外信息确保汇款过程可靠。通过提供金额、汇款人邮件地址、交易号等信息，可确保汇款人身份与交易记录真实可靠，防止他人冒充。
进一步，收款方获得相关交易信息后，可将相关信息记录在数据库中，例如邮件地址与对应的交易号及金额。收款方通过定期扫描或远程调用等方式从数字/电子货币网络获得实际汇款信息后，根据之前注册的对应信息，更新相关 邮件地址记录，例如增减相应金额等。至此完成一笔汇款。
本实施例提供的价值传输方法，具有支持通过电子邮件交互服务器获得、注册并传输价值，无需再通过数字/电子货币服务统一接口服务器。采用统一接口地址或与收款电子邮件对应的数字/电子货币地址，使绑定域名的汇款/汇款邮件服务器能安全高效且经济地通过系统外部的邮件地址实现价值传输。
实施例二：
基于实施例一，本实施例提供一种基于电子邮件的价值传输集群系统。
本实施例提供的价值传输集群系统可以是独立的汇款集群系统，也可以是跨平台汇款邮件集群系统，本实施例以跨平台汇款邮件集群系统为例进行说明，在跨平台汇款邮件集群系统的基础上，本领域技术人员通过变换即可获得独立的汇款集群系统。
因跨平台汇款邮件集群系统是对跨平台汇款邮件系统中的某些服务器进行集群，因此，在介绍跨平台汇款邮件集群系统之前，先对跨平台汇款邮件系统进行介绍。
改进的跨平台汇款邮件系统如图7所示，包括邮件客户端1、汇款邮件管理服务器2、电子邮件管理服务器3、用户认证服务器4、资金管理服务器5、数据库服务器6、电子邮件交互服务器7、数字货币交互服务器8和第三方数字/电子货币交互服务器9。其中，电子邮件交互服务器7设置有资金查询模块，资金查询模块用于查询收款方邮件地址对应的收款地址或者查询DNS服务器中配置的收款方邮件域名对应的收款地址；该电子邮件交互服务器7除传统的电子邮件收/发功能外，还承担了类似数字/电子货币服务统一接口交互服务器的功能。
另一改进的跨平台汇款邮件系统如图8所示，该跨平台汇款邮件系统的结构与图7中的跨平台汇款邮件系统的结构相同，不同点在于，该跨平台汇款邮件系统中的电子邮件交互服务器7配置有支持汇款指令的SMTP协议，使得，该跨平台汇款邮件系统中的电子邮件交互服务器7基于配置的支持汇款指令的SMTP协议查询收款地址；该电子邮件服务器7除传统的电子邮件收/发功能外，还采用扩展的支持汇款的SMTP指令来完成收款地址的查询与注册等功能。
本实施例提供的价传输集群系统(也即是跨平台汇款邮件集群系统)包括邮件客户端1、数据库服务器6、数字货币交互服务器8、第三方数字/电子货币交互服务器9、若干个汇款邮件管理服务器集群10、各个汇款邮件管理服务器集群分别配置有相应的电子邮件交互服务器7。
其中，汇款邮件管理服务器集群10分别与邮件客户端1和对应的电子邮件 交互服务器7交互连接；汇款邮件管理服务器集群10用于接收邮件客户端发送的邮件发送请求信息，且邮件发送请求信息中含有汇款信息时，汇款邮件管理服务器集群10还用于将汇款信息发送至电子邮件交互服务器7；电子邮件交互服务器7用于收发邮件，还用于根据汇款信息获取收款地址，并将收款地址反馈至汇款邮件管理服务器集群10；汇款邮件管理服务器集群10还用于根据收款地址进行汇款操作。
对应上述提供的两种不同的跨平台汇款邮件系统，本实施例提供相对应的两种不同的跨平台汇款邮件集群系统。
与图7相对应，本实施例提供的跨平台汇款邮件集群系统如图9所示，与图8相对应，本实施例提供的另一跨平台汇款邮件集群系统如图10所示。其中，图9和图10中的汇款邮件管理服务器集群10包括汇款管理服务器、用户认证服务器、电子邮件管理服务器和资金管理服务器。例如，可以设置3个汇款邮件管理服务器集群10，即，汇款邮件管理服务器集群A、汇款邮件管理服务器集群B、汇款邮件管理服务器集群C，针对每一个汇款邮件管理服务器集群配置相应的邮件域名，例如，汇款邮件管理服务器集群A配置的邮件域名为@mail1.com，汇款邮件管理服务器集群B配置的邮件域名为@mail2.com，汇款邮件管理服务器集群C配置的邮件域名为@mail3.com。
上述各个汇款邮件管理服务器集群配置一个域名仅是一种实现方式，在其他实施例中，根据实际需要，各个汇款邮件管理服务器集群可以配置不同数量的域名。
在其他实施例中，本领域技术人员可以对上述提供的跨平台汇款邮件集群系统进行变换，以实现独立的汇款集群系统，例如，将上述跨平台汇款邮件集群系统中的电子邮件交互服务器7替换成数字/电子货币服务统一接口交互服务器11，及将跨平台汇款邮件集群系统中的汇款邮件管理服务器集群10中的电子邮件管理服务器3删减形成汇款管理服务器集群12，以此实现独立的汇款集群系统，如图11所示，其中，汇款管理服务器集群12仅包括汇款管理服务器、用户认证服务器和资金管理服务器。
本实施例提供的价值传输集群系统不论是采用跨平台汇款邮件集群系统实现，还是采用独立的汇款集群系统实现，其中的集群系统均可以采用以下架构之一实现。
1)使用完整的架构，该架构包括汇款管理服务器、用户认证服务器、资金管理服务器，数字/电子货币交互服务器、数字/电子货币服务统一接口交互服务器与数据库，并设置DNS服务器中对应的域名和IP。每套新系统中的资金管理 服务器均可通过DNS系统设置对应的域名和IP地址。此架构适合需自己构建系统，或将本系统融入自有系统的用户。由于服务器独立，不同域名地址间的价值传输需通过数字/电子货币网络。
2)在同一服务器端内复用现有的数字/电子货币服务器，但添加新的汇款管理服务器、用户认证服务器、资金管理服务器、数字/电子货币服务统一接口交互服务器与数据库等，并在DNS服务器中添加新域名和IP以指向新设的汇款管理服务器，从而构成集群系统。其中新添加的数据库可运行在同一数据库服务器内，也可运行在不同数据库服务器内。此架构无需新建完整的汇款管理系统，省去了因同步数字货币节点而产生的重复设备与资源浪费，极大降低成本，因此适合系统托管商或云服务商。例如，当前比特币全节点约300G左右，完成同步需4核8G且具有大容量SSD的服务器在约5M带宽且网络情况良好时运行约5-10天，无论是运算、存储、带宽、流量还是耗时均极大。通过省去此项消耗，可极大提高新系统的发布效率并显著降低成本，只需简单灵活地添减相应资金管理服务器与数据库即可。由于数字/电子货币服务器被多台资金管理服务器共享，因此其维护可由某台资金管理服务器单独进行。同一集群系统内，因域名分属不同集群，故不同域名地址间的价值传输既可通过数字/电子货币网络，也可通过内部数据库更新来完成。而不同集群系统内，域名地址间的价值传输需通过数字/电子货币网络。
3)不添加新服务器，仅通过数据库字段实现新域名和地址的查询与更新等操作。此架构无需增减服务器，因此具有较高的经济效益。但由于多域名的操作并非物理独立，而是共用同一数据库表并通过内部的虚拟化技术实现分隔，因此安全性较低，且易造成管理的混乱。此外，多域名记录的共表处理易造成数据库效率降低，增加出错可能性(如死锁等)。由于多域名共用同一汇款管理服务器的IP，因此若该汇款管理服务器因某一域名地址出现意外故障，则会波及到其它域名地址，产生较大负面影响。在此系统内，不同域名地址间的价值传输既可通过数字/电子货币网络，也通过内部数据库更新来完成。若域名地址不属于此系统，则其间的价值传输需通过数字/电子货币网络。
4)上述架构的混合。对于小型或可通过云服务商托管的域名及邮件地址，可通过架构2和/或架构3实现。对于中大型或需独立管理数字/电子货币服务器的域名及邮件地址，可通过架构1实现。架构2和架构3也可处于同一集群系统内，即某些汇款管理服务器对应其唯一的域名，而某些汇款管理服务器则可对应多个域名。
进一步，为提高资金传输效率，降低成本，可对属于同一集群系统且共用 相同数字/电子货币交互服务器(即运行数字货币钱包程序或数字/电子货币外部交互程序)的资金管理服务器间的资金传输使用内部转账，而非外部。资金管理服务器通过统一接口服务器作收/汇款时，先确认收发双方服务器是否在同一集群系统，若是，则通过数据库更新等方式实现内部转账，若否，则通过数字货币或数字/电子货币网络进行外部转账。
为验证不同资金管理服务器是否属于同一集群系统，可采用内部标识符、公/私钥签名验证或钱包地址签名验证等方式，例如：对属于同一集群系统的资金管理服务器可采用某一特定字符串作内部标识，如“abcd1234”。当收发双方确认该标识后，可认为对方属同一集群系统，进而作相应处理。或者，由于双方资金管理服务器均可访问同一数字/电子货币交互服务器，因此可通过地址签名等方式验证双方是否属于同一集群系统。或者，增加额外的管理服务器，并连接同一集群系统内所有的资金管理服务器。收发双方资金管理服务器通过访问该管理服务器来确认双方所属集群系统。
本实施例提供的价值传输集群系统，集群系统灵活多样，例如可以采用跨平台的汇款邮件集群系统进行价值传输，也可以采用独立的汇款集群系统进行价值传输，不论哪一种集群系统均可采用上述的任一种集群架构，进行统一收款地址与多收款地址的处理，使多域名邮件地址的增减安全灵活且经济高效。
以上应用了具体个例对本发明进行阐述，只是用于帮助理解本发明，并不用以限制本发明。对于本发明所属技术领域的技术人员，依据本发明的思想，还可以做出若干简单推演、变形或替换。

Claims (10)

  1. 一种基于电子邮件的价值传输方法，其特征在于，包括步骤：
    建立汇款方与收款方之间的电子邮件交互服务器IP地址的连接；
    基于电子邮件交互服务器的交互操作获取收款方的收款地址；
    根据所述收款地址进行汇款操作。
  2. 如权利要求1所述的价值传输方法，其特征在于，所述基于电子邮件交互服务器的交互操作获取收款方的收款地址，具体包括：基于电子邮件交互服务器配置的资金查询功能查询收款方邮件地址对应的收款地址或者查询DNS服务器中配置的收款方邮件域名对应的收款地址。
  3. 如权利要求1所述的价值传输方法，其特征在于，所述基于电子邮件交互服务器的交互操作获取收款方的收款地址，具体包括：基于电子邮件交互服务器配置的支持汇款指令的SMTP协议查询收款地址。
  4. 如权利要求1所述的价值传输方法，其特征在于，所述收款地址为统一接口地址或为与目标邮件地址对应的数字/电子货币地址。
  5. 如权利要求4所述的价值传输方法，其特征在于，若所述收款地址为统一接口地址时，所述汇款操作还包括向收款方发送汇款信息。
  6. 一种基于电子邮件的价值传输集群系统，其特征在于，包括：邮件客户端、若干个汇款邮件管理服务器集群、各个汇款邮件管理服务器集群分别配置有相应的电子邮件交互服务器；
    所述汇款邮件管理服务器集群分别与所述邮件客户端和对应的电子邮件交互服务器交互连接；
    所述汇款邮件管理服务器用于接收所述邮件客户端发送的邮件发送请求信息，且所述邮件发送请求信息中含有汇款信息时，所述汇款邮件管理服务器还用于将所述汇款信息发送至所述电子邮件交互服务器；
    所述电子邮件交互服务器用于收发邮件，还用于根据所述汇款信息获取收款地址，并将所述收款地址反馈至所述汇款邮件管理服务器集群；
    所述汇款邮件管理服务器集群还用于根据所述收款地址进行汇款操作。
  7. 如权利要求6所述的价值传输集群系统，其特征在于，所述电子邮件交互服务器设置有资金查询模块，所述资金查询模块用于查询收款方邮件地址对应的收款地址或者查询DNS服务器中配置的收款方邮件域名对应的收款地址。
  8. 如权利要求6所述的价值传输集群系统，其特征在于，所述电子邮件交互服务器基于配置的支持汇款指令的SMTP协议查询收款地址。
  9. 如权利要求6所述的价值传输集群系统，其特征在于，所述收款地址 为统一接口地址或为与目标邮件地址对应的数字/电子货币地址。
  10. 如权利要求6所述的价值传输集群系统，其特征在于，各个所述汇款邮件管理服务器集群分别配置有邮件域名，以使所述汇款邮件管理服务器集群根据所述邮件域名进行汇款操作。
PCT/CN2021/074894 2020-06-24 2021-02-02 一种基于电子邮件的价值传输方法及价值传输集群系统 WO2021258737A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/011,186 US20230246992A1 (en) 2020-06-24 2021-02-02 Email-based value transfer method and value transfer cluster system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010595116.XA CN111756619B (zh) 2020-06-24 2020-06-24 一种基于电子邮件的价值传输方法及价值传输集群系统
CN202010595116.X 2020-06-24

Publications (1)

Publication Number Publication Date
WO2021258737A1 true WO2021258737A1 (zh) 2021-12-30

Family

ID=72677419

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/074894 WO2021258737A1 (zh) 2020-06-24 2021-02-02 一种基于电子邮件的价值传输方法及价值传输集群系统

Country Status (3)

Country Link
US (1) US20230246992A1 (zh)
CN (1) CN111756619B (zh)
WO (1) WO2021258737A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109981816B (zh) * 2019-03-21 2023-04-18 上海风汇网络科技有限公司 基于dns域名系统的价值传输系统、方法及dns服务器
CN111756619B (zh) * 2020-06-24 2022-12-27 上海风汇网络科技有限公司 一种基于电子邮件的价值传输方法及价值传输集群系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8443185B2 (en) * 2009-08-07 2013-05-14 Eco-Mail Development, Llc System for management and processing of electronic vendor mail
CN104702645A (zh) * 2013-12-10 2015-06-10 中国银联股份有限公司 一种基于Email的P2P数据处理系统以及数据处理方法
CN104956395A (zh) * 2012-12-27 2015-09-30 谷歌公司 对包含支付的电子邮件的管理
US20150310404A1 (en) * 2014-04-23 2015-10-29 Square, Inc. Transferring money using email
CN111756619A (zh) * 2020-06-24 2020-10-09 上海风汇网络科技有限公司 一种基于电子邮件的价值传输方法及价值传输集群系统

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010056395A1 (en) * 2000-06-09 2001-12-27 Khan Saadat H. Internet bargaining system
US8346659B1 (en) * 2001-07-06 2013-01-01 Hossein Mohsenzadeh Secure authentication and payment system
US10521776B2 (en) * 2002-10-01 2019-12-31 Andrew H B Zhou UN currency (virtual payment cards) issued by central bank or other issuer for mobile and wearable devices
RU2509360C1 (ru) * 2012-08-24 2014-03-10 Олег Александрович Серебренников Способ создания платежной системы
US10250535B2 (en) * 2014-01-08 2019-04-02 Swoop Ip Holdings Llc Email based e-commerce using embedded forms
US10015720B2 (en) * 2014-03-14 2018-07-03 GoTenna, Inc. System and method for digital communication between computing devices
CN109756418B (zh) * 2019-01-30 2021-11-16 上海风汇网络科技有限公司 一种融合货币协议的电子邮件系统、邮件发送、接收方法
CN109858902A (zh) * 2019-02-25 2019-06-07 上海风汇网络科技有限公司 一种基于http协议的服务器、用户终端收款系统及收款方法
CN109981816B (zh) * 2019-03-21 2023-04-18 上海风汇网络科技有限公司 基于dns域名系统的价值传输系统、方法及dns服务器
CN110351185A (zh) * 2019-06-28 2019-10-18 太原理工大学 一种基于区块链技术的分布式电子邮箱系统
GB201909960D0 (en) * 2019-07-11 2019-08-28 Nchain Holdings Ltd Computer-implemented system and method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8443185B2 (en) * 2009-08-07 2013-05-14 Eco-Mail Development, Llc System for management and processing of electronic vendor mail
CN104956395A (zh) * 2012-12-27 2015-09-30 谷歌公司 对包含支付的电子邮件的管理
CN104702645A (zh) * 2013-12-10 2015-06-10 中国银联股份有限公司 一种基于Email的P2P数据处理系统以及数据处理方法
US20150310404A1 (en) * 2014-04-23 2015-10-29 Square, Inc. Transferring money using email
CN111756619A (zh) * 2020-06-24 2020-10-09 上海风汇网络科技有限公司 一种基于电子邮件的价值传输方法及价值传输集群系统

Also Published As

Publication number Publication date
US20230246992A1 (en) 2023-08-03
CN111756619A (zh) 2020-10-09
CN111756619B (zh) 2022-12-27

Similar Documents

Publication Publication Date Title
AU2006206255B2 (en) Data exchanges related to financial transactions over a public network
WO2021258737A1 (zh) 一种基于电子邮件的价值传输方法及价值传输集群系统
US8813208B2 (en) System and method for the management of secure electronic correspondence sessions
WO2020155581A1 (zh) 一种融合货币协议的电子邮件系统、邮件发送、接收方法
US9020850B1 (en) Method and system for implementing effective governance of transactions between trading partners
US20170091733A1 (en) Sending bills
CN110377635B (zh) 基于区块链架构的人民币跨境支付查询查复方法及装置
CN110458539B (zh) 一种加密货币自动提取方法及系统
CN101115062B (zh) 分布式智能代理系统、注册中心及注册、消息路由方法
CN113255014B (zh) 一种基于区块链的数据处理方法以及相关设备
US20120109825A1 (en) Check Clearing Systems
CN111507747A (zh) 一种区块链积分兑换里程系统
JP2022528710A (ja) 分散台帳のためのエイリアスに基づくアドレッシングを実施する、コンピュータにより実施されるシステム及び方法
US20220188809A1 (en) Value transfer system based on the domain name system (dns), method thereof and dns server
CN110808841B (zh) 基于区块链网络的通信系统及其通信方法
CN112163870A (zh) 基于区块链的信息管理方法、解析节点及复工平台
CN112132581A (zh) 基于iota的pki身份认证系统及方法
CN112150157B (zh) 通过区块链发行应收凭证的方法及装置
CN114641967A (zh) 区块链交易的回调机制
WO2020042930A1 (zh) 基于平行链的交易方法及区块链系统
US20050251679A1 (en) Original Transcript System: Method and System to issue, submit and view original electronic transcripts.
JP2022549624A (ja) ブロックチェーントランザクションのコールバックメカニズム
US20230334175A1 (en) Distributed Ledger Network for Data Portability
Jevans et al. Travel Rule Information Sharing Architecture for Virtual Asset Service Providers (TRISA) Version 7 June 23, 2020
CN115880088A (zh) 账务处理方法、接入服务器、节点服务器及账务处理系统

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: 21829255

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21829255

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21829255

Country of ref document: EP

Kind code of ref document: A1