WO2020155581A1 - 一种融合货币协议的电子邮件系统、邮件发送、接收方法 - Google Patents

一种融合货币协议的电子邮件系统、邮件发送、接收方法 Download PDF

Info

Publication number
WO2020155581A1
WO2020155581A1 PCT/CN2019/097045 CN2019097045W WO2020155581A1 WO 2020155581 A1 WO2020155581 A1 WO 2020155581A1 CN 2019097045 W CN2019097045 W CN 2019097045W WO 2020155581 A1 WO2020155581 A1 WO 2020155581A1
Authority
WO
WIPO (PCT)
Prior art keywords
remittance
mail
management server
email
server
Prior art date
Application number
PCT/CN2019/097045
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 JP2021540145A priority Critical patent/JP7308496B2/ja
Priority to CA3125771A priority patent/CA3125771A1/en
Priority to EP19912209.4A priority patent/EP3920472A4/en
Priority to US17/420,734 priority patent/US20220108307A1/en
Publication of WO2020155581A1 publication Critical patent/WO2020155581A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • 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/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/38—Payment protocols; Details thereof
    • G06Q20/386—Payment protocols; Details thereof using messaging services or messaging apps
    • 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/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • 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/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • 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/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/046—Interoperability with other network applications or services
    • 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/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/08—Annexed information, e.g. attachments
    • 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/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/18—Commands or executable codes

Definitions

  • the present invention relates to the technical field of electronic mail, in particular to an electronic mail system and a mail sending and receiving method incorporating currency protocols.
  • This application provides an e-mail system, e-mail sending and receiving methods that integrate currency protocols. Combining e-mail, digital currency and electronic money can solve the problem of separate transmission of existing information and value, and improve the financial function of the e-mail system .
  • an embodiment provides an email system that integrates currency protocols, including: a remittance plug-in, a mail client, a remittance mail management server, an email management server, and a fund management server;
  • the mail client is loaded with the remittance plug-in to provide users with an e-mail interface with a remittance identifier, the remittance identifier carrying currency recipient information, amount and currency, and the currency is digital currency or /And electronic money;
  • the remittance mail management server interacts with the mail client, the email management server and the fund management server respectively;
  • the remittance mail management server works cooperatively with the email management server and the fund management server. After receiving the mail message sent by the mail client, the remittance mail management server determines whether the mail message contains a remittance identifier, if Contains a remittance identifier, the remittance mail management server dispatches the email management server to send the mail message and dispatches the fund management server to perform the remittance operation according to the remittance identifier, if not, the remittance mail management server only dispatches The email management server sends the email message.
  • an embodiment provides an email sending method of an email system that incorporates a currency protocol.
  • the email system includes a remittance plug-in, a mail client, a remittance mail management server, an email management server, and fund management.
  • Server, the mail sending method includes the steps:
  • the mail client Determine whether the remittance plug-in is triggered, if not, the mail client generates a normal mail and sends it to the remittance mail management server, and the remittance mail management server schedules the email management server to send the normal mail;
  • the mail client runs the remittance plug-in to provide users with an email interface with a remittance identifier, the remittance identifier carrying information of the recipient of the currency, amount and currency, and the currency is digital currency or/ And electronic money;
  • the remittance mail management server works in cooperation with the email management server and the fund management server, and dispatches the email management server to send the mail messages in the remittance email and dispatches the fund management server to perform all operations according to the remittance identification. Describe the remittance operation in the remittance email.
  • an embodiment provides an email receiving method for an email system that incorporates a currency protocol.
  • the email system includes a remittance plug-in, a mail client, a remittance mail management server, an email management server, and fund management.
  • Server, the mail receiving method includes the steps:
  • the remittance mail management server judges whether the received e-mail contains a remittance identifier, and if not, the e-mail is processed as a normal e-mail, and the remittance identifier carries the currency beneficiary information, possible transaction number, Amount and currency, said currency being digital currency or/and electronic currency;
  • the received email is a remittance mail, and the relevant information of the remittance mail is transmitted to the fund management server;
  • the fund management server queries the remittance status, and feeds back the query result to the remittance mail management server;
  • the remittance mail management server sends the remittance mail and related information to the mail client of the recipient according to the feedback query result.
  • the sender and receiver of digital currency/electronic currency can also obtain real-name authentication through the email system, thereby obtaining higher security, reliability and legal protection;
  • Figure 1 is a schematic diagram of a traditional email message
  • Figure 2 is a schematic diagram of an email message after merging the currency agreement
  • Fig. 3 is a block diagram of the principle of the email system in the first embodiment
  • Figure 4 is a schematic diagram of an email message with a remittance transaction number
  • Figure 5 is a block diagram of the principle of the email system of the second embodiment
  • Fig. 6 is a block diagram of the principle of the email system of the third embodiment.
  • FIG. 7 is a schematic diagram of mail sending by the email system of the fourth embodiment.
  • Fig. 8 is a schematic diagram of mail sending of automatic remittance of reply mail
  • Fig. 9 is a schematic diagram of mail receiving in the email system of the fifth embodiment.
  • Digital/encrypted currency Decentralized digital currency, generally produced through “mining” work, such as Bitcoin and Litecoin, etc., 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.
  • Remittance email An email with a remittance identification in the body, such as "Pay-To” (ie "Pay To”), and the remittance is synchronized when sent.
  • the application for the integration of digital currency protocol into the traditional email system in order to not lose generality
  • both the digital currency protocol and the electronic currency protocol are integrated into the email system, so that the traditional email system can realize the synchronous transmission of information and value through the blockchain and the digital/electronic currency protocol.
  • FIG. 1 A schematic diagram of the complete content of a mail message in a traditional e-mail system is shown in Figure 1.
  • Figure 2 a schematic diagram of the complete content of a mail message in an e-mail system incorporating currency protocols is shown in Figure 2, which can be seen from the comparison of Figure 1 and Figure 2.
  • Pay-To field in 2 is a newly added field after the email system merges with the currency protocol. It is used for remittance to realize the synchronization of information transmission and value transmission.
  • the fields in the same part of FIG. 1 and FIG. 2 are the format of a traditional email, which is well known to those skilled in the art, and will not be repeated in this example.
  • the e-mail system of the convergent currency protocol provided in this example is shown in Figure 3, including a remittance plug-in (not identified in the figure), a mail client 1, a remittance mail management server 2, an email management server 3, and a fund management server 4.
  • the sender and receiver server of the mail and remittance corresponding to the e-mail system in the example are all on the network where the server of the system is located, generally located in the internal LAN or cloud network.
  • the mail client 1 is loaded with a remittance plug-in, which can be a piece of code in the running program of the mail client 1, or a control independent of the mail client 1.
  • the mail client 1 is connected to the control through an interface.
  • the code corresponding to the remittance plug-in can be directly run to provide the user with an email interface with a remittance logo.
  • the remittance logo can be displayed anywhere in the browsing page of the email interface; if the email is only If you send a multimedia email, you cannot add a remittance logo in the body. Therefore, it is preferable that the remittance logo is located in the mail header of the email interface. In this way, regardless of the content of the email, you can add the remittance logo to the mail header, as shown in the figure 2 shown.
  • the remittance logo can be any one or a combination of remittance fields (Pay-To), remittance windows, views, and visual identification elements.
  • the remittance logo is displayed on the email interface for the user to identify. When the user needs a remittance operation , Just trigger the remittance logo.
  • the remittance logo carries the currency of the recipient information, amount, currency and other information for users to choose.
  • the currency can be digital currency or electronic currency. It can be a combination of digital currency and electronic currency.
  • the remittance identification can include one or more payee information, and each payee information must provide at least the following information:
  • the digital currency address of the payee such as Bitcoin, Litecoin, etc.;
  • the account number and service provider bound to the beneficiary's digital currency or electronic currency.
  • the account number can be an email account or mobile phone number, etc.;
  • an address book name can only correspond to a digital currency address, or an account and service provider bound to a digital/electronic currency; and the account bound to the payee must be able to receive the sender's remittance, for example , Both accounts are located in this system. If the payee address is an account outside the system, the user needs to designate the corresponding service provider.
  • the remittance logo can also provide users with the following optional information, which can be set in advance through user account preferences, so that it does not need to be displayed on the email interface, specifically:
  • the sender's digital currency private key must be obtained from a third party or a local file, it must provide a method of obtaining it, such as uploading a local private key file or sharing third-party information.
  • the email system in this example must also store basic user account information.
  • the basic user account information includes: user mailbox (ie, user name), digital currency address and balance, electronic currency address and balance, user security settings, user preferences Settings and user authentication information.
  • the user can recharge the digital currency balance of the account through digital currency transfer, such as bitcoin transfer, or the user can use banks and other institutions under the framework of laws and related certification Recharge the electronic currency balance of the account, such as bank transfer.
  • digital currency transfer such as bitcoin transfer
  • banks and other institutions under the framework of laws and related certification Recharge the electronic currency balance of the account, such as bank transfer.
  • the user does not need to operate the remittance identification. If the user needs to send the remittance email, the user will operate according to the ordinary e-mail and provide the recipient and other information. Then, the user provides all the receipts through the remittance identification.
  • the payee address, amount, and unit of the payee If the payee address is a digital currency address, different payees can specify different types of digital currencies. If the payee address is an account number, different payees can specify different The service provider’s account number must be able to receive the sender’s remittance.
  • the email client 1 edits the email and loads the email header.
  • the system will add a payment header to the header of the ordinary email.
  • the format of the Pay-To field is:
  • the "//” is used to distinguish the complete “Pay-To” header, and the "//" character itself does not belong to the "Pay-To” header.
  • the remittance mail management server 2 in this example interacts with the mail client 1, the email management server 3 and the fund management server 4 respectively; the remittance mail management server 2 works with the email management server 3 and the fund management server 4, and the remittance mail management server 2
  • the remittance mail management server 2 After receiving the mail message sent by the mail client 1, judge whether the mail message contains a remittance logo, if it contains a remittance logo, the remittance mail management server 2 dispatches the email management server 3 sends the mail message and dispatches the fund management server 4 to execute according to the remittance identity
  • the remittance mail management server 2 only schedules the email management server 3 to send mail messages.
  • the remittance mail management server 2 works with the email management server 3 and the fund management server 4 to realize the synchronization of mail information transmission and value transmission, and improve the financial function of the traditional email system.
  • the remittance mail management server 2 before the remittance mail management server 2 dispatches the fund management server 4, the remittance mail management server 2 first dispatches the email management server 3 to send mail messages, and the remittance mail management server 2 After receiving the instruction of successful sending of the mail message feedback from the email management server 3, the remittance mail management server 2 then dispatches the fund management server 4; specifically, the remittance mail management server 2 will first try to send the email to all recipients. At least one of the recipients can successfully receive the sent mail, the remittance mail management server 2 then dispatches the fund management server 4 to perform the remittance operation, otherwise the remittance is cancelled.
  • this example also includes a database server 5, which is used to store the remitter’s and beneficiary’s fund information.
  • the fund information includes at least user account numbers, transaction information, The number of funds, the database server 5 interacts with the remittance mail management server 2 and the funds management server 4 respectively.
  • the funds management server 4 sends a remittance request to the database server 5 according to the dispatching instructions of the remittance mail management server 2, and the database server 5 updates the remitter according to the remittance request The fund information related to this remittance of the beneficiary to realize internal remittance.
  • the remittance mail management server 2 also sends emails containing the status and results of the remittance to the recipient and the sender according to the email address based on the updated fund information in the database server 5. That is, the recipient and the sender can be the recipient and the sender during the remittance.
  • the recipient provides dynamic information in the form of e-mail. If supported by the systems of both parties, the dynamic information can be an interactive progress bar.
  • this example also includes an authentication server 6, which interacts with the database server 5 and the remittance mail management server 2.
  • the authentication server 6 is used to authenticate the user's identity, such as an authentication server 6 Verify the identity of the sender and provide the details of the remittance for the sender to reconfirm the authenticated information.
  • the remittance mail management server 2 passes the authentication server 6 to obtain the user authentication status and confirms the validity, the remittance mail management server 2 and The email management server 3 and the fund management server 4 work together.
  • the email system in this example is the internal remittance of the system, so that the remittance transaction number can be obtained in advance before the actual remittance. Therefore, in this example, the mail client 1 edits the mail And when loading the mail header, the system will add a payment header to the header of ordinary mail.
  • the payment header also carries the remittance transaction number, that is, the mail message also carries the remittance transaction number, so that all parties can pass the remittance transaction number
  • the remittance progress can be tracked correctly, and the e-mail content information diagram with the remittance transaction number is shown in Figure 4.
  • the format of the Pay-To field is:
  • the e-mail system provided in this example can realize the synchronous transmission of digital/electronic money and e-mail by adding remittance identification, that is, realize the synchronous transmission of information and value, and the sender and receiver of digital/electronic money can also obtain real-name authentication through the e-mail system , So as to obtain higher security, reliability and legal protection, and further improve the financial functions of the email system, such as sending and receiving bills through email, automatic deduction and payment, identity authentication and address authentication, etc., thereby greatly improving Reliability and efficiency of business communication and life applications, and reduction of related costs, combined with electronic currency agreements, the email system of this example can also achieve some of the aforementioned financial functions through electronic currency, and add digital currency and electronic currency under the legal framework Interchangeable characteristics.
  • the email system in this example also uses certain security and authentication mechanisms to ensure the reliability and identity of the communication and remittance process.
  • the authenticity of the source for example, PGP and other encryption methods such as mail encryption or digital signature are needed to ensure that the mail is not tampered with or stolen during the transmission process, and encryption and digital certificates are used to ensure the security of remittance transmission and the authenticity of the source.
  • this example provides another email system that integrates currency protocols.
  • the difference from the first embodiment is that the mail recipient of the email system in this example is located outside the system, and the beneficiary's digital/electronic money account number is located inside the system. Therefore, the mail in this example, that is, the transmission of information, needs to be cross-system; while the remittance, that is, the transmission of value, needs to be carried out internally.
  • the schematic diagram of the e-mail system in this example is shown in Figure 5.
  • the recipient’s email system architecture is similar to the sender’s email system architecture.
  • This example takes the sender’s email system architecture as an example for detailed description, including the remittance plug-in (not shown in the figure), mail client 1, Remittance mail management server 2, email management server 3, fund management server 4, database server 5, authentication server 6, email interactive server 7, and third-party digital/electronic money interactive server 8.
  • the remittance plug-in mail client 1, remittance mail management server 2, email management server 3, fund management server 4, database server 5, and authentication server 6, please refer to the first embodiment. This example will not be repeated.
  • the interactive server 7 is the internal and external network interface of the e-mail system.
  • the internal and external network interfaces can send mail between different platforms.
  • the third-party digital/electronic currency interactive server 8 is also the internal and external network interfaces of the e-mail system.
  • the internal and external network interfaces can achieve different Remittance and inquiry between platforms.
  • the e-mail interaction server 7 interacts with the e-mail management server 3 through the network, and is used to convert the internal request from the e-mail management server 3 and the external e-mail information from the network according to related protocols to perform information sending and receiving operations;
  • the e-mail interactive server 7 is a server running an e-mail service program (such as Postfix), and sends e-mails to the outside through a public e-mail network.
  • the third-party digital/electronic currency interaction server 8 interacts with the fund management server 4, and is used to convert the internal request from the fund management server 4 and the external request from the network according to relevant protocols to perform query and remittance operations; for example, third-party digital /Electronic currency interaction server 8 is a server supporting local or third-party interfaces (such as node.js or nginx, etc.). In this example, the third-party digital/electronic currency interaction server 8 is only used to perform query operations.
  • the sender operates through a mail client 1 such as a PC, a web page, etc., and the mail client 1 sends related requests of the sender to the remittance mail management server 2.
  • the remittance mail management server 2 obtains the user authentication status through the user authentication server 6.
  • the remittance mail management server 2 works with the email management server 3 and the fund management server 4 to send ordinary mail or remittance mail through the email network Send to the recipient, and conduct internal remittance through the fund management server 4; specifically, the e-mail interactive server 7 converts the internal request from the e-mail management server 3 into external e-mail information according to related protocols to perform information transmission; The server 4 sends a remittance request to the database server 5 according to the scheduling instructions of the remittance mail management server 2, and the database server 5 updates the remittance and beneficiary's fund information related to this remittance according to the remittance request to realize internal remittance.
  • the remittance mail management server 2, the email management server 3, the fund management server 4, and the authentication server 6 are all connected to the database server 5 for data query and update.
  • the e-mail system of this example is applied to the receiver to receive the remittance mail, and its specific working method is: the e-mail management server 3 receives the remittance mail from the e-mail network through the e-mail interactive server 7, and transmits the mail information of the remittance mail to The remittance mail management server 2, after identifying the remittance information, the remittance mail management server transmits the relevant information to the fund management server 4.
  • the fund management server 4 inquires the sender about the remittance status through the third-party digital/electronic money interactive server 8 The result is fed back to the remittance mail management server 2.
  • the remittance mail management server 2 obtains the authentication status through the user authentication server 6, and after confirming the validity, it transmits the remittance mail and related information to the recipient's mail client 1, and the recipient sends the mail via PC, webpage, etc.
  • the client 1 obtains mail and remittance information.
  • the remittance mail management server 2, the email management server 3, the fund management server 4 and the authentication server 6 are all connected to the database server 5 for data query and update.
  • the e-mail system in this example is the internal remittance of the system, so that the remittance transaction number can be obtained in advance before the actual remittance.
  • this example will not repeat it
  • the e-mail system provided in this example can realize partial cross-platform synchronous transmission of digital/electronic money and e-mail by adding a remittance identification, that is, realize partial cross-platform synchronous transmission of information and value, and the sender and receiver of digital/electronic money can also Obtain real-name authentication through the email system, thereby obtaining higher security, reliability and legal protection, and further improving the financial functions of the email system, such as sending and receiving bills through email, automatic deduction and payment, identity authentication and address Authentication, etc., thereby greatly improving the reliability and efficiency of business communication and life applications, and reducing related costs.
  • the e-mail system in this example can also achieve some of the aforementioned financial functions through electronic currency, and is in the legal framework Add the swap feature between digital currency and electronic currency.
  • this example provides another email system that integrates currency protocols.
  • the difference between the first and second embodiments is that the email system of this example can realize the difference between the sender and the receiver.
  • the schematic diagram of the email system in this example is shown in Figure 6.
  • the recipient’s email system architecture is similar to the sender’s email system architecture.
  • This example takes the sender’s email system architecture as an example for detailed description, including the remittance plug-in (not shown in the figure), mail client 1, Remittance mail management server 2, email management server 3, fund management server 4, database server 5, authentication server 6, email interaction server 7, third-party digital/electronic currency interaction server 8, and digital currency interaction server 9, among which, remittance Specific description of plug-in, mail client 1, remittance mail management server 2, email management server 3, fund management server 4, database server 5, authentication server 6, email interaction server 7, and third-party digital/electronic currency interaction server 8 Please refer to the second embodiment, which will not be repeated in this example.
  • the digital currency interactive server 9 is an internal and external network interface of the email system, and the internal and external network interface can realize remittance and inquiry between different platforms.
  • the digital currency interaction server 9 interacts with the fund management server 4, and is used to convert internal requests from the fund management server 4 and external requests from the network according to related protocols to perform query and remittance operations; for example, the digital currency interactive server 9 It is a server running digital currency service programs (such as Bitcoin Core daemon).
  • the sender operates through a mail client 1 such as a PC, a web page, etc., and the mail client 1 sends related requests of the sender to the remittance mail management server 2.
  • the remittance mail management server 2 obtains the user authentication status through the user authentication server 6.
  • the remittance mail management server 2 works with the email management server 3 and the fund management server 4 to send ordinary mail or remittance mail through the email network
  • the email interaction server 7 converts the internal request from the email management server 3 into external email information according to the relevant protocol to perform the information transmission
  • the digital currency interactive server 9 converts the internal request from the fund management server 4 into an external request according to the relevant protocol to perform the remittance operation
  • the remittance mail management server 2, the email management server 3, the fund management server 4 and the authentication server 6 are all connected with
  • the database server 5 is connected to perform data query and update.
  • the e-mail system of this example is applied to the receiver to receive the remittance mail, and its specific working method is: the e-mail management server 3 receives the remittance mail from the e-mail network through the e-mail interactive server 7, and transmits the mail information of the remittance mail to The remittance mail management server 2, after identifying the remittance information, the remittance mail management server 2 transmits the relevant information to the fund management server 4, and the fund management server 4 queries the third-party digital/electronic currency interactive server 8 or/and the digital currency interactive server 9 The remittance status, and the query result is fed back to the remittance mail management server 2.
  • the remittance mail management server 2 obtains the authentication status through the user authentication server 6, and transmits the remittance mail and related information to the recipient’s mail client 1 after confirmation. Obtain mail and remittance information through mail clients 1 such as PCs and web pages. At the same time, the remittance mail management server 2, email management server 3, fund management server 4 and authentication server 6 are all connected to the database server 5 for data query and update Wait.
  • the remittance transaction number can generally only be obtained after the actual remittance. Therefore, the first The three-party digital/electronic currency interaction server 8 converts the internal request from the fund management server 4 into an external request according to the relevant protocol to perform the remittance operation, and then feeds back the remittance result to the fund management server 4.
  • the remittance result includes the remittance transaction number and the fund
  • the management server 4 feeds back the remittance transaction number to the remittance mail management server 2, and the remittance mail management server 2 dispatches the email management server 3 to send auxiliary mails to the recipient and the sender, and displays the auxiliary mail to the sender through the mail client 1 ,
  • the auxiliary email contains the remittance transaction number, so that all parties can correctly track the remittance progress through the remittance transaction number.
  • the system will add a payment header to the header of ordinary mail.
  • the payment header also carries the remittance transaction number, that is, the mail message also carries the remittance transaction number, so that all parties can correctly track the progress of the remittance through the remittance transaction number.
  • a schematic diagram of the content information of an email with a remittance transaction number is shown in Figure 4. For a specific description, please refer to Embodiment 1, and this example will not be repeated.
  • This example also applies to the situation where the beneficiary and the remitter are in the same system, and the payment information contains a digital currency address.
  • the payment information contains a digital currency address.
  • the cross-system remittance method in this example can be used to obtain the actual digital currency transaction number, thereby avoiding the above problems.
  • the e-mail system provided in this example can realize the cross-platform synchronous transmission of digital/electronic money and e-mail by adding remittance identification, that is, realize the cross-platform synchronous transmission of information and value, and the sender and receiver of digital/electronic money can also use electronic
  • the mail system has obtained real-name authentication, thereby obtaining higher security, reliability and legal protection, and further improving the financial functions of the email system, such as sending and receiving bills through email, automatic deduction and payment, identity authentication and address authentication, etc.
  • the e-mail system in this example can also achieve some of the aforementioned financial functions through electronic currency, and increase under the legal framework The swap characteristics between digital currency and electronic currency.
  • this example provides an email sending method of an email system that integrates currency protocols.
  • the email system includes a remittance plug-in, a mail client, a remittance mail management server, and an email
  • Embodiment 1 for the detailed description of the email system. This example will not go into details.
  • the email sending method is applied to the email system of Embodiment 1 to realize the synchronous transmission of information and value within the system. Including the following steps, the flowchart is shown in Figure 7.
  • S101 Determine whether the remittance plug-in is triggered, if not, the mail client generates a normal mail and sends it to the remittance mail management server, and the remittance mail management server schedules the email management server to send the normal mail.
  • the mail client runs the remittance plug-in to provide the user with an email interface with a remittance identification.
  • the remittance identification carries the recipient information, amount and currency of currency, and the currency is digital currency or/and electronic currency.
  • the remittance identifier is located in the mail header of the email interface, and the remittance identifier is any one or a combination of a remittance field, a remittance window, a view, and a visual identification element.
  • the payee information includes at least one of the following:
  • the account number and service provider bound to the recipient's digital currency or electronic currency
  • S103 Obtain the beneficiary information, amount, and currency through the remittance identifier, and generate a remittance email to send to the remittance email management server.
  • the remittance mail management server works in coordination with the email management server and the fund management server to dispatch the email management server to send mail messages in the remittance email and dispatch the fund management server to execute the remittance operation in the remittance email according to the remittance identifier.
  • this example also includes the step of automatically replying to the email. If the automatic reply email includes recognizable remittance request information, the process of automatically replying to the email also includes the remittance through the reply email.
  • the flow chart of the steps is shown in Figure 8, which specifically includes the following steps.
  • the remittance mail management server dispatches the email management server to send mail messages in the remittance mail automatically responded and dispatches the capital management server to execute the remittance operation in the remittance mail automatically responded according to the remittance identifier.
  • the email system also includes an external network interface, which includes an email interaction server, a digital currency interaction server and Third-party digital/electronic currency interactive server; based on the above email sending steps, if the email sent is an external email, this example also provides steps for sending remittance emails across systems.
  • the specific steps for sending remittance emails across systems are as follows:
  • S301 Convert the internal request from the email management server into external email information according to the relevant protocol through the email interactive server to perform information transmission;
  • S302 Perform an internal remittance operation through the fund management server, or convert the internal request from the fund management server into an external request according to the relevant protocol through the digital currency interactive server or/and the third-party digital/electronic currency interactive server to perform the remittance operation.
  • the remittance mail management server before the remittance mail management server dispatches the fund management server, the remittance mail management server first dispatches the email management server to send mail messages, and the remittance mail management server receives the email management server feedback The remittance mail management server then dispatches the fund management server after sending the successful instruction of the mail message.
  • the remittance transaction number can be provided in the following two ways:
  • the remittance transaction number is obtained after the actual remittance.
  • an auxiliary email can be sent to the sender and recipient.
  • the auxiliary email contains the remittance transaction number so that all parties can The remittance progress can be accurately tracked through the remittance transaction number.
  • the third-party payment can only obtain the remittance transaction number after the actual remittance. Therefore, the third-party digital/electronic currency interactive server converts the internal request from the fund management server to the external according to the relevant agreement After requesting to perform the remittance operation, it also includes the steps of sending an auxiliary email to the recipient and the sender:
  • the remittance result includes the remittance transaction number
  • the fund management server feeds back the remittance transaction number to the remittance mail management server;
  • the remittance mail management server dispatches the email management server to send auxiliary mails to the recipient and the sender, and displays the auxiliary mail to the sender through the mail client.
  • the auxiliary mail contains the remittance transaction number.
  • the remittance transaction number can be obtained before the actual remittance, such as digital currency such as Bitcoin or local remittance. Therefore, if the remittance is identified as internal remittance or through the digital currency interactive server, the internal request from the fund management server will be sent Converting to an external request according to the relevant agreement to perform the remittance operation, the process of sending the remittance mail also includes the step of loading the remittance transaction number, so that the mail message in the remittance mail also carries the remittance transaction number.
  • the email sending method provided in this example can realize the same platform or cross-platform synchronous transmission of digital/electronic currency and email by adding remittance identification, that is, realize the same platform or cross-platform synchronous transmission of information and value, and digital/electronic currency
  • Sending and receiving parties can also obtain real-name authentication through the email system, thereby obtaining higher security, reliability and legal protection, and further improving the financial functions of the email system, for example, sending and receiving bills through email, automatic deduction and payment , Identity authentication and address authentication, etc., so as to greatly improve the reliability and efficiency of business communication and life applications, and reduce related costs.
  • the e-mail system in this example can also achieve some of the aforementioned financial functions through electronic currency , And increase the swap feature between digital currency and electronic currency under the legal framework.
  • this example provides an email receiving method of an email system that incorporates currency protocols.
  • the email system includes a remittance plug-in, a mail client, a remittance mail management server, and an email
  • Embodiment 1 for the detailed description of the email system. This example will not go into details.
  • the email receiving method is applied to the email system of Embodiment 1 to realize the synchronous reception of information and value within the system. Including the following steps, the flowchart is shown in Figure 9.
  • S401 Receive emails through the email management server, and transmit the email information to the remittance email management server.
  • the remittance mail management server judges whether the received e-mail contains a remittance logo, and if not, the e-mail is processed as an ordinary e-mail, and the remittance logo carries the currency of the recipient information, possible transaction number, amount and currency ,
  • the currency is digital currency or/and electronic currency.
  • the remittance identification is located in the header part of the email or the auxiliary email.
  • the remittance identifier is any one or several combinations of payment header, remittance field, remittance window, view, and visual identification elements.
  • the payee information includes at least one of the following:
  • the received email is a remittance mail, and the relevant information of the remittance mail is transmitted to the fund management server.
  • the fund management server queries the remittance status and feeds back the query result to the remittance mail management server.
  • the remittance mail management server sends the remittance mail and related information to the mail client of the recipient according to the feedback query result.
  • the email system also includes an external network interface, which includes an email interaction server, a digital currency interaction server and Third-party digital/electronic currency interactive server; based on the above mail receiving steps, if the received mail is an external mail, this example also provides steps for receiving remittance mail across systems.
  • the specific steps for receiving remittance mail across systems are as follows.
  • the email management server obtains externally sent emails through the email interactive server, and sends the email information of the emails to the remittance email management server.
  • the remittance mail management server judges whether the received mail information contains a remittance identifier, and if not, the e-mail is processed as a normal e-mail.
  • the fund management server queries the remittance status through the fund management server of the sender, or through the digital currency interactive server or/and the third-party digital/electronic currency interactive server, and feeds back the query result to the remittance mail management server.
  • the remittance mail management server sends the remittance mail and related information to the mail client of the recipient according to the feedback query result.

Abstract

一种融合货币协议的电子邮件系统，包括：邮件客户端加载有汇款插件，以向用户提供具有汇款标识的电子邮件界面；汇款邮件管理服务器分别与邮件客户端、电子邮件管理服务器和资金管理服务器交互；汇款邮件管理服务器与电子邮件管理服务器和资金管理服务器协同工作，汇款邮件管理服务器接收到邮件客户端发送的邮件消息后，判断邮件消息是否含有汇款标识，若有，汇款邮件管理服务器调度电子邮件管理服务器发送邮件消息及调度资金管理服务器根据汇款标识执行汇款操作，若否，汇款邮件管理服务器仅调度电子邮件管理服务器发送邮件消息。实现信息与价值的同一平台和跨平台同步传输。

Description

一种融合货币协议的电子邮件系统、邮件发送、接收方法 技术领域
本发明涉及电子邮件技术领域，具体涉及一种融合货币协议的电子邮件系统、邮件发送、接收方法。
背景技术
随着因特网的普及，电子邮件已成为广泛使用的交流工具，在商业沟通中尤为重要。作为一种文本文件信息，其内容也具有较高法律效用。然而因缺乏价值传输能力，传统电子邮件系统只能成为信息载体，无法承担金融职责，因此极大限制了其应用范围。与此同时，尽管银行或第三方支付承担了价值传输的主要职责，但其信息传递能力很弱，业务模式也与电子邮件系统差别较大，基本属完全不同的两种形态。
另一方面，目前区块链与数字货币(如比特币等)的发展方向主要参照银行或第三方支付，但难以获得类似的传输效率与法律保障，从而缺乏实际应用基础，无法真正体现区块链与数字货币的价值。同时匿名性也导致数字货币难以获得必要的法律支撑与监管。
与此同时，尽管电子邮件与数字货币具有天然相似性(例如匿名、无障碍跨平台传输、传输成本低且不可回撤等)，但目前并没有将两者结合的发明与应用。对于电子货币而言，尽管目前已被广泛应用于第三方支付等领域，但仍缺乏可与电子邮件同步收发电子货币的发明与应用。多数第三方支付系统仅限使用电子邮件地址作为用户名，而非与电子邮件同步收发，因此本质上仍属银行模式。
因此，在现有条件下，信息与价值传输需要分开进行，从而在时间与成本上造成极大浪费，同时也容易因传输不同步而造成困扰与误解，进而产生商业与社会纠纷。
发明内容
本申请提供一种融合货币协议的电子邮件系统、邮件发送、接收方法，将电子邮件、数字货币与电子货币相结合，可以解决现有信息与价值分开传输的问题，提升电子邮件系统的金融功能。
根据第一方面，一种实施例中提供一种融合货币协议的电子邮件系统，包括：汇款插件、邮件客户端、汇款邮件管理服务器、电子邮件管理服务器和资 金管理服务器；
所述邮件客户端加载有所述汇款插件，以向用户提供具有汇款标识的电子邮件界面，所述汇款标识携带有货币的收款人信息、金额与币种，所述币种为数字货币或/和电子货币；
所述汇款邮件管理服务器分别与所述邮件客户端、电子邮件管理服务器和资金管理服务器交互；
所述汇款邮件管理服务器与所述电子邮件管理服务器和资金管理服务器协同工作，所述汇款邮件管理服务器接收到所述邮件客户端发送的邮件消息后，判断所述邮件消息是否含有汇款标识，若含有汇款标识，所述汇款邮件管理服务器调度所述电子邮件管理服务器发送所述邮件消息及调度所述资金管理服务器根据所述汇款标识执行汇款操作，若否，所述汇款邮件管理服务器仅调度所述电子邮件管理服务器发送所述邮件消息。
根据第二方面，一种实施例中提供一种融合货币协议的电子邮件系统的邮件发送方法，所述电子邮件系统包括汇款插件、邮件客户端、汇款邮件管理服务器、电子邮件管理服务器和资金管理服务器，所述邮件发送方法包括步骤：
判断所述汇款插件是否被触发，若否，所述邮件客户端生成普通邮件并发送至所述汇款邮件管理服务器，所述汇款邮件管理服务器调度所述电子邮件管理服务器发送所述普通邮件；
若所述汇款插件被触发：
所述邮件客户端运行所述汇款插件，以向用户提供具有汇款标识的电子邮件界面，所述汇款标识携带有货币的收款人信息、金额与币种，所述币种为数字货币或/和电子货币；
通过所述汇款标识获取收款人信息、金额与币种，并生成汇款邮件发送至汇款邮件管理服务器；
所述汇款邮件管理服务器与所述电子邮件管理服务器和资金管理服务器协同工作，调度所述电子邮件管理服务器发送所述汇款邮件中的邮件消息及调度所述资金管理服务器根据所述汇款标识执行所述汇款邮件中的汇款操作。
根据第三方面，一种实施例中提供一种融合货币协议的电子邮件系统的邮件接收方法，所述电子邮件系统包括汇款插件、邮件客户端、汇款邮件管理服务器、电子邮件管理服务器和资金管理服务器，所述邮件接收方法包括步骤：
通过所述电子邮件管理服务器接收电子邮件，并将邮件信息传输给汇款邮件管理服务器；
所述汇款邮件管理服务器判断收到的电子邮件是否包含有汇款标识，若无， 将所述电子邮件按普通电子邮件处理，所述汇款标识携带有货币的收款人信息、可能的交易号、金额与币种，所述币种为数字货币或/和电子货币；
若含有汇款标识，则接收到的电子邮件为汇款邮件，将汇款邮件的相关信息传输给所述资金管理服务器；
所述资金管理服务器查询汇款状态，并将查询结果反馈给所述汇款邮件管理服务器；
所述汇款邮件管理服务器根据反馈的查询结果将汇款邮件及相关信息发送给收件人的邮件客户端。
依据上述实施例的电子邮件系统，具有以下有益效果：
1)立足于电子邮件系统，即通过在传统电子邮件系统中融合货币协议，实现信息传输与价值传输同步；
2)数字货币/电子货币的收发方也可通过电子邮件系统得到实名认证，从而获得较高的安全性、可靠性与法律保障；
3)提升电子邮件系统的金融功能；
4)通过电子邮件与数字货币的的跨系统特性实现信息与价值的跨平台同步传输。
附图说明
图1为传统电子邮件消息示意图；
图2为融合货币协议后的电子邮件消息示意图；
图3为实施例一的电子邮件系统原理框图；
图4为具有汇款交易号的电子邮件消息示意图；
图5为实施例二的电子邮件系统原理框图；
图6为实施例三的电子邮件系统原理框图；
图7为实施例四的电子邮件系统邮件发送示意图；
图8为回复邮件自动汇款的邮件发送示意图；
图9为实施例五的电子邮件系统邮件接收示意图。
具体实施方式
下面通过具体实施方式结合附图对本发明作进一步详细说明。
数字/加密货币：去中心化的数字货币，一般通过“挖矿”工作产生，如比特币和莱特币等，下文简称“数字货币”。
电子货币：电子化的传统/法定货币或代币及相关支付服务，如paypal和alipay及其虚拟化电子货币等。
普通邮件：普通的电子邮件。
汇款邮件：信体含汇款标识的电子邮件，例如”Pay-To”(即”Pay To”)，并且发送时同步汇出款项。
基于电子邮件与数字货币具有天然相似性，如，匿名、无障碍跨平台传输、传输成本低且不可回撤等，因此申请将数字货币协议融合到传统的电子邮件系统中，为了不失一般性，本申请将数字货币协议和电子货币协议均融合到电子邮件系统中，从而使传统电子邮件系统能通过区块链与数字/电子货币协议实现信息与价值的同步传输。
实施例一：
传统的电子邮件系统中邮件消息完整内容示意图如图1所示，而本例中融合货币协议的电子邮件系统中邮件消息完整内容示意图如图2所示，由图1和图2对比可知，图2中多了Pay-To字段，该字段是电子邮件系统融合货币协议后新增的字段，用来汇款，以实现信息传输和价值传输同步。图1和图2相同部分的字段是传统电子邮件的格式，是本领域技术人员所熟知的，本例不作赘述。
本例提供的融合货币协议的电子邮件系统如图3所示，包括汇款插件(图中未标识)、邮件客户端1、汇款邮件管理服务器2、电子邮件管理服务器3和资金管理服务器4，本例的电子邮件系统所对应的邮件及汇款的发送方与接收方服务端均为本系统服务器所在的网络，一般位于内部局域网或云端网络等。
其中，邮件客户端1加载有汇款插件，该汇款插件可以是邮件客户端1运行程序中的一段代码，也可以是独立于邮件客户端1的控件，邮件客户端1与该控件通过接口连接，当邮件客户端1运行程序时可以直接运行汇款插件对应的代码，以向用户提供具有汇款标识的电子邮件界面，该汇款标识可以显示于电子邮件界面的浏览页面内任一位置；若电子邮件仅发送多媒体邮件，则无法在正文中添加汇款标识，因此，优选的，汇款标识位于电子邮件界面的邮件标头，这样，不论电子邮件发送何种内容均可在邮件标头添加汇款标识，如图2所示。
汇款标识可以为汇款字段(Pay-To)、汇款窗口、视图、可视化的标识元素中的任一种或几种组合，汇款标识显示于电子邮件界面上，供用户识别，待用户 需要汇款操作时，触发汇款标识即可。
为了方便用户使用电子邮件系统汇款，进一步，汇款标识携带有货币的收款人信息、金额、币种等信息，以供用户选择，其中，币种可以是数字货币，也可以是电子货币，还可以是数字货币和电子货币的组合。
汇款标识中可以包括一个或多个收款人信息，每一个收款人信息至少需提供如下信息：
收款人的数字货币地址，如，比特币、莱特币等；
收款人的数字货币地址所对应的名称，该名称可存储于电子邮件系统的通信录中；
收款人的数字货币或电子货币所绑定的账号及服务商，该账号可以为邮箱账号或手机号码等；
收款人的数字货币或电子货币所绑定的账号及服务商所共同对应的名称，该名称可存储于电子邮件系统的通信录中。
需要说明的是，一个通信录名称只能对应一个数字货币地址，或一个数字/电子货币所绑定的账号及服务商；及收款人绑定的账号须能接收发件人的汇款，例如，双方账号均位于本系统中。如果收款人地址为本系统外账号，则用户需指定相应服务商。
汇款标识除了为用户提供上述信息外，还可以为用户提供以下可选信息，该可选信息可通过用户账户偏好事先进行设置，从而不必显示在电子邮件界面上，具体的：
1)若存在接收数字货币的收款人，则可为每一种数字货币指定转账优先级、转账速度或转账费率等；
2)若发件人的数字货币私钥必须通过第三方或本地文件获得，则须提供获得方式，如上传本地私钥文件或共享第三方信息等。
同样的，本例的电子邮件系统也必然存储有用户账户基本信息，用户账户基本信息包括：用户邮箱(即用户名)、数字货币地址及余额、电子货币地址及余额、用户安全设置、用户偏好设置和用户身份认证信息。
待用户通过用户名登录本例的电子邮件系统时，用户可通过数字货币转账方式对账户数字货币余额进行充值，如比特币转账，或者，用户在法律及相关认证框架下，可通过银行等机构对账户电子货币余额进行充值，如银行转账等。
若用户只需发送普通电子邮件，则用户不需要操作汇款标识即可，若用户 需要发送汇款邮件，则用户按普通电子邮件操作，提供收件人等信息，然后，用户通过汇款标识提供所有收款人的收款人地址、金额、单位，若收款人地址为数字货币地址，不同收款人可指定不同种类的数字货币，若收款人地址为账号，则不同收款人可指定不同服务商的账号，但均需能接收发件人的汇款。
待用户通过汇款标识填写完成后，邮件客户端1编辑邮件并加载邮件标头，系统将在普通邮件的标头部分增加付款头部，例如Pay-To字段的格式为：
Pay-To:[收款人名称]<收款人地址><金额><单位>[服务商标识]；
例如：/Pay-To:<1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa>50BTC/；
/Pay-To:”Payee1”<1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa>50BTC/；
/Pay-To:<abcd1234@abcd.com>100 CNY payserv1/；
/Pay-To:”Payee2”<abcd1234@abcd.com>100 CNY payserv1/。
其中“//”用来区分完整的”Pay-To”头部，而“//”字符本身不属于”Pay-To”头部。
本例的汇款邮件管理服务器2分别与邮件客户端1、电子邮件管理服务器3和资金管理服务器4交互；汇款邮件管理服务器2与电子邮件管理服务器3和资金管理服务器4协同工作，汇款邮件管理服务器2接收到邮件客户端1发送的邮件消息后，判断邮件消息是否含有汇款标识，若含有汇款标识，汇款邮件管理服务器2调度电子邮件管理服务器3发送邮件消息及调度资金管理服务器4根据汇款标识执行汇款操作，若否，汇款邮件管理服务器2仅调度电子邮件管理服务器3发送邮件消息。
本例通过汇款邮件管理服务器2与电子邮件管理服务器3和资金管理服务器4协同工作，实现邮件信息传输和价值传输同步，提升传统电子邮件系统的金融功能。
进一步，为了提高电子邮件汇款的可靠性，本例中，汇款邮件管理服务器2调度资金管理服务器4之前，汇款邮件管理服务器2先调度电子邮件管理服务器3发送邮件消息，且待汇款邮件管理服务器2接收到电子邮件管理服务器3反馈的邮件消息发送成功的指令后，汇款邮件管理服务器2再调度资金管理服务器4；具体的，汇款邮件管理服务器2将首先尝试发送该邮件给所有收件人，若其中至少一位收件人能成功收到所发的邮件，则汇款邮件管理服务器2再调度资金管理服务器4执行汇款操作，否则取消汇款。
进一步，因本例的电子邮件系统实现的是系统内部汇款，本例还包括数据 库服务器5，数据库服务器5用于存储汇款人和收款人的资金信息，资金信息至少包括用户账号、交易信息、资金数目，数据库服务器5分别与汇款邮件管理服务器2和资金管理服务器4交互，资金管理服务器4根据汇款邮件管理服务器2的调度指令向数据库服务器5发送汇款请求，数据库服务器5根据汇款请求更新汇款人和收款人本次汇款相关的资金信息以实现内部汇款。
相应的，汇款邮件管理服务器2还根据数据库服务器5内更新的资金信息，按邮箱地址向收件人与发件人发送含有汇款状态与结果的邮件，即，汇款期间可以为收件人与发件人以邮件形式提供动态信息，若在双方系统支持的情况下，该动态信息可为交互式的进度条。
进一步，为确保电子邮件系统传输的安全可靠性，本例还包括认证服务器6，认证服务器6与数据库服务器5和汇款邮件管理服务器2交互，认证服务器6用于对用户身份进行认证，如认证服务器6验证发件人身份，并提供汇款详情，以供发件人再次确认所认证的信息，待汇款邮件管理服务器2通过认证服务器6获得用户认证状态并确认有效后，汇款邮件管理服务器2再与电子邮件管理服务器3和资金管理服务器4协同工作。
进一步，为了使各方都能正确跟踪汇款进度，因本例的电子邮件系统为系统内部汇款，使得，在实际汇款前可以提前得到汇款交易号，因此，本例中，邮件客户端1编辑邮件并加载邮件标头时，系统将在普通邮件的标头部分增加付款头部，付款头部中还携带有汇款交易号，即邮件消息还携带有汇款交易号，使各方通过该汇款交易号能正确跟踪汇款进度，携带有汇款交易号的电子邮件内容信息示意图如图4所示。
例如Pay-To字段的格式为：
Pay-To:[收款人名称]<收款人地址><金额><单位><是否有交易号>[交易号][服务商标识]；
例如/Pay-To:<1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa>50 BTC true4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b/；
/Pay-To:”Payee1”<1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa>50 BTC true 4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b/；
/Pay-To:<abcd1234@abcd.com>100 CNY false payserv1/；
/Pay-To:”Payee2”<abcd1234@abcd.com>100 CNY false payserv1/。
本例提供的电子邮件系统能通过增加汇款标识来实现数字/电子货币与电子 邮件同步传输，即实现信息与价值的同步传输，而数字/电子货币的收发方也可通过电子邮件系统得到实名认证，从而获得较高的安全性、可靠性与法律保障，进一步提升电子邮件系统的金融功能，例如，通过电子邮件来收发账单、自动扣款与支付、身份认证与地址认证等，从而极大提高商业交流与生活应用的可靠性与效率，并降低相关成本，结合电子货币协议，本例的电子邮件系统也可通过电子货币实现前述的部分金融功能，并在法律框架下增加数字货币与电子货币间的互换特性。
需要说明的是，为了防止邮件传输过程中，及汇款过程中发生他人窃取，或他人篡改，本例的电子邮件系统还通过一定的安全和认证机制来确保通信和汇款过程的可靠性与身份/来源的真实性，如，传输过程中需要PGP等邮件加密或数字签名等加密方式来确保邮件不被篡改和窃取，通过加密和数字证书等用来确保汇款传输安全，以及来源真实可靠。
实施例二：
基于实施例一，本例提供另外一种融合货币协议的电子邮件系统。与实施例一不同的是，本例的电子邮件系统的邮件收件人位于本系统外，而收款人数字/电子货币账号位于本系统内。因此本例的邮件，即信息传输，需跨系统；而汇款，即价值传输，需内部进行。
本例的电子邮件系统示意图如图5所示。其中，接收方的电子邮件系统架构与发送方的电子邮件系统架构相似，本例以发送方的电子邮件系统架构为例进行详细说明，包括汇款插件(图中未显示)、邮件客户端1、汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4、数据库服务器5、认证服务器6、电子邮件交互服务器7和第三方数字/电子货币交互服务器8。其中，汇款插件、邮件客户端1、汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4、数据库服务器5和认证服务器6的具体描述请参考实施例一，本例不作赘述，电子邮件交互服务器7是电子邮件系统的内外网络接口，该内外网络接口可实现不同平台间发送邮件，第三方数字/电子货币交互服务器8同样是电子邮件系统的内外网络接口，该内外网络接口可实现不同平台间汇款与查询。
其中，电子邮件交互服务器7与电子邮件管理服务器3网络交互，用于将来自电子邮件管理服务器3的内部请求与来自网络的外部电子邮件信息根据相关协议进行转换以执行信息发送与接收操作；如，电子邮件交互服务器7为运行电子邮件服务程序(如Postfix)的服务器，通过公共的电子邮件网络实现向外部 发送电子邮件。第三方数字/电子货币交互服务器8与资金管理服务器4交互，用于将来自资金管理服务器4的内部请求与来自网络的外部请求根据相关协议进行转换以执行查询与汇款操作；如，第三方数字/电子货币交互服务器8为支持本地或第三方接口的服务器(如node.js或nginx等)。本例中第三方数字/电子货币交互服务器8仅用于执行查询操作。
本例的电子邮件系统应用于发送方时，其具体的工作方式是：发送方通过PC、网页等邮件客户端1进行操作，该邮件客户端1将发送方的相关请求发送至汇款邮件管理服务器2，汇款邮件管理服务器2通过用户认证服务器6获得用户认证状态，确认有效后，汇款邮件管理服务器2与电子邮件管理服务器3和资金管理服务器4协同工作，将普通邮件或汇款邮件通过电子邮件网络发送给收件人，并通过资金管理服务器4进行内部汇款；具体的，电子邮件交互服务器7将来自电子邮件管理服务器3的内部请求根据相关协议转换为外部电子邮件信息以执行信息发送；资金管理服务器4根据汇款邮件管理服务器2的调度指令向数据库服务器5发送汇款请求，数据库服务器5根据汇款请求更新汇款人和收款人本次汇款相关的资金信息以实现内部汇款。同时，汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4和认证服务器6均与数据库服务器5连接，以进行数据查询与更新等。
本例的电子邮件系统应用于接收方接收汇款邮件时，其具体的工作方式是：电子邮件管理服务器3通过电子邮件交互服务器7从电子邮件网络得到汇款邮件后，将汇款邮件的邮件信息传输给汇款邮件管理服务器2，汇款邮件管理服务器识别出汇款信息后，将相关信息传输给资金管理服务器4，资金管理服务器4通过第三方数字/电子货币交互服务器8向发送方查询汇款状态，并将查询结果反馈给汇款邮件管理服务器2，汇款邮件管理服务器2通过用户认证服务器6获得认证状态，确认有效后将汇款邮件与相关信息传输给接收方的邮件客户端1，接收方通过PC、网页等邮件客户端1获得邮件与汇款信息，同时，汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4和认证服务器6均与数据库服务器5连接，以进行数据查询与更新等。
进一步，为了使各方都能正确跟踪汇款进度，因本例的电子邮件系统为系统内部汇款，使得，在实际汇款前可以提前得到汇款交易号。具体描述请参考实施例一，本例不作赘述
本例提供的电子邮件系统能通过增加汇款标识来实现数字/电子货币与电子 邮件的部分跨平台同步传输，即实现信息与价值的部分跨平台同步传输，而数字/电子货币的收发方也可通过电子邮件系统得到实名认证，从而获得较高的安全性、可靠性与法律保障，进一步提升电子邮件系统的金融功能，例如，通过电子邮件来收发账单、自动扣款与支付、身份认证与地址认证等，从而极大提高商业交流与生活应用的可靠性与效率，并降低相关成本，结合电子货币协议，本例的电子邮件系统也可通过电子货币实现前述的部分金融功能，并在法律框架下增加数字货币与电子货币间的互换特性。
实施例三：
基于实施例一和实施例二，本例提供另外一种融合货币协议的电子邮件系统，与实施例一和实施例二均不同的是，本例的电子邮件系统能实现发送方和接收方之间跨系统传输信息和价值，本例的电子邮件系统示意图如图6所示。其中，接收方的电子邮件系统架构与发送方的电子邮件系统架构相似，本例以发送方的电子邮件系统架构为例进行详细说明，包括汇款插件(图中未显示)、邮件客户端1、汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4、数据库服务器5、认证服务器6、电子邮件交互服务器7、第三方数字/电子货币交互服务器8和数字货币交互服务器9，其中，汇款插件、邮件客户端1、汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4、数据库服务器5、认证服务器6、电子邮件交互服务器7和第三方数字/电子货币交互服务器8的具体描述请参考实施例二，本例不作赘述，数字货币交互服务器9是电子邮件系统的内外网络接口，该内外网络接口可实现不同平台间汇款与查询。
其中，数字货币交互服务器9与资金管理服务器4交互，用于将来自资金管理服务器4的内部请求与来自网络的外部请求根据相关协议进行转换以执行查询与汇款操作；如，数字货币交互服务器9为运行数字货币服务程序(如Bitcoin Core daemon)的服务器。
本例的电子邮件系统应用于发送方时，其具体的工作方式是：发送方通过PC、网页等邮件客户端1进行操作，该邮件客户端1将发送方的相关请求发送至汇款邮件管理服务器2，汇款邮件管理服务器2通过用户认证服务器6获得用户认证状态，确认有效后，汇款邮件管理服务器2与电子邮件管理服务器3和资金管理服务器4协同工作，将普通邮件或汇款邮件通过电子邮件网络发送给收件人，具体的，电子邮件交互服务器7将来自电子邮件管理服务器3的内部请求根据相关协议转换为外部电子邮件信息以执行信息发送；第三方数字/电子 货币交互服务器8或/和数字货币交互服务器9将来自资金管理服务器4的内部请求根据相关协议转换为外部请求以执行汇款操作；同时，汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4和认证服务器6均与数据库服务器5连接，以进行数据查询与更新等。
本例的电子邮件系统应用于接收方接收汇款邮件时，其具体的工作方式是：电子邮件管理服务器3通过电子邮件交互服务器7从电子邮件网络得到汇款邮件后，将汇款邮件的邮件信息传输给汇款邮件管理服务器2，汇款邮件管理服务器2识别出汇款信息后，将相关信息传输给资金管理服务器4，资金管理服务器4通过第三方数字/电子货币交互服务器8或/和数字货币交互服务器9查询汇款状态，并将查询结果反馈给汇款邮件管理服务器2，汇款邮件管理服务器2通过用户认证服务器6获得认证状态，确认有效后将汇款邮件与相关信息传输给接收方的邮件客户端1，接收方通过PC、网页等邮件客户端1获得邮件与汇款信息，同时，汇款邮件管理服务器2、电子邮件管理服务器3、资金管理服务器4和认证服务器6均与数据库服务器5连接，以进行数据查询与更新等。
在上述信息与价值传输的过程中，若是通过第三方数字/电子货币交互服务器8执行的汇款操作，由于第三方支付的方式，其汇款交易号一般只能在实际汇款后才能得到，因此，第三方数字/电子货币交互服务器8将来自所述资金管理服务器4的内部请求根据相关协议转换为外部请求以执行汇款操作后，将汇款结果反馈给资金管理服务器4，汇款结果包含汇款交易号，资金管理服务器4向汇款邮件管理服务器2反馈汇款交易号，汇款邮件管理服务器2调度电子邮件管理服务器3向收件人和发件人发送辅助邮件，并通过邮件客户端1向发件人显示辅助邮件，辅助邮件包含汇款交易号，这样，各方均能通过汇款交易号正确跟踪汇款进度。
同样的，若是通过数字货币交互服务器9执行的汇款操作，使得，在实际汇款前可以提前得到汇款交易号，因此，本例中，发送方的邮件客户端1编辑邮件并加载邮件标头时，系统将在普通邮件的标头部分增加付款头部，付款头部中还携带有汇款交易号，即邮件消息还携带有汇款交易号，使各方通过该汇款交易号能正确跟踪汇款进度，携带有汇款交易号的电子邮件内容信息示意图如图4所示，具体描述请参考实施例一，本例不作赘述。
本例也适用于收款人与汇款人位于同一系统，且收款信息含数字货币地址的情形。当用户汇款至本系统内某一用户数字货币地址时，若采用通过资金管 理服务器4进行内部汇款，则易造成数字货币协议与内部汇款交易号的不匹配与混淆。因此采用本例的跨系统汇款方式可以获得实际的数字货币交易号，进而避免上述问题。
本例提供的电子邮件系统能通过增加汇款标识来实现数字/电子货币与电子邮件的跨平台同步传输，即实现信息与价值的跨平台同步传输，而数字/电子货币的收发方也可通过电子邮件系统得到实名认证，从而获得较高的安全性、可靠性与法律保障，进一步提升电子邮件系统的金融功能，例如，通过电子邮件来收发账单、自动扣款与支付、身份认证与地址认证等，从而极大提高商业交流与生活应用的可靠性与效率，并降低相关成本，结合电子货币协议，本例的电子邮件系统也可通过电子货币实现前述的部分金融功能，并在法律框架下增加数字货币与电子货币间的互换特性。
实施例四：
基于实施例一、实施例二和实施例三，本例提供一种融合货币协议的电子邮件系统的邮件发送方法，其中，电子邮件系统包括汇款插件、邮件客户端、汇款邮件管理服务器、电子邮件管理服务器和资金管理服务器，电子邮件系统的具体描述请参考实施例一，本例不作赘述，该邮件发送方法应用于实施例一的电子邮件系统中，实现系统内部的信息和价值同步传输，具体包括如下步骤，其流程图如图7所示。
S101：判断汇款插件是否被触发，若否，邮件客户端生成普通邮件并发送至汇款邮件管理服务器，汇款邮件管理服务器调度电子邮件管理服务器发送普通邮件。
若汇款插件被触发：
S102：邮件客户端运行汇款插件，以向用户提供具有汇款标识的电子邮件界面，汇款标识携带有货币的收款人信息、金额与币种，币种为数字货币或/和电子货币。
优选的，汇款标识位于电子邮件界面的邮件标头，汇款标识为汇款字段、汇款窗口、视图、可视化的标识元素中的任一种或几种组合。
其中，收款人信息至少包括以下之一：
收款人的数字货币地址；
收款人的数字货币地址所对应的名称；
收款人的数字货币或电子货币所绑定的账号及服务商；
收款人的数字货币或电子货币所绑定的账号及服务商共同所对应的名称。
S103：通过汇款标识获取收款人信息、金额与币种，并生成汇款邮件发送至汇款邮件管理服务器。
S104：汇款邮件管理服务器与电子邮件管理服务器和资金管理服务器协同工作，调度电子邮件管理服务器发送汇款邮件中的邮件消息及调度资金管理服务器根据汇款标识执行汇款邮件中的汇款操作。
进一步，为了实现电子邮件自动回复邮件时能自动付款，本例还包括自动回复邮件的步骤，若自动回复邮件包括可识别的汇款请求信息，则自动回复邮件的过程还包括通过回复邮件进行汇款的步骤，其流程图如图8所示，具体包括如下步骤。
S201：若自动回复邮件包含可识别的汇款请求信息，则提示用户是否按照汇款请求信息汇款。
S202：若是，生成回复邮件，以使回复邮件的电子邮件界面自动加载有汇款标识，并将汇款请求信息中的收款人信息、金额与币种自动录入汇款标识，以生成能自动回复的汇款邮件，并发送至汇款邮件管理服务器。
S203：汇款邮件管理服务器调度电子邮件管理服务器发送自动回复的汇款邮件中的邮件消息及调度资金管理服务器根据所述汇款标识执行自动回复的汇款邮件中的汇款操作。
上述仅涉及了同一平台内的信息和价值同步传输，进一步，为了实现跨平台的信息和价值同步传输，电子邮件系统还包括外部网络接口，外部网络接口包括电子邮件交互服务器、数字货币交互服务器和第三方数字/电子货币交互服务器；在上述邮件发送步骤的基础上，若所发送的邮件为外部邮件，本例还提供跨系统发送汇款邮件的步骤，跨系统发送汇款邮件的具体步骤如下：
S301：通过电子邮件交互服务器将来自电子邮件管理服务器的内部请求根据相关协议转换为外部电子邮件信息以执行信息发送；
S302：通过资金管理服务器执行内部汇款操作，或通过数字货币交互服务器或/和第三方数字/电子货币交互服务器将来自资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作。
进一步，为了保证信息和价值传输的安全可靠性，汇款邮件管理服务器调度资金管理服务器之前，汇款邮件管理服务器先调度电子邮件管理服务器发送邮件消息，且待汇款邮件管理服务器接收到电子邮件管理服务器反馈的邮件消息发送成功的指令后，汇款邮件管理服务器再调度资金管理服务器。
进一步，为了使各方能正确跟踪汇款进度，还包括提供汇款交易号的步骤， 根据货币的类型不同或内外汇款方式的不同，汇款交易号的提供由以下两种方式：
一种方式是：汇款交易号在实际汇款后获得，则可在发送汇款邮件并实际汇款后，向发件人及收件人发送辅助邮件，辅助邮件中包含汇款交易号，从而使各方都能通过汇款交易号正确跟踪汇款进度，一般，第三方支付是在实际汇款后才能获得汇款交易号，因此，第三方数字/电子货币交互服务器将来自资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作后，还包括向收件人和发件人发送辅助邮件的步骤：
将汇款结果反馈给资金管理服务器，汇款结果包含汇款交易号；
资金管理服务器向汇款邮件管理服务器反馈汇款交易号；
汇款邮件管理服务器调度电子邮件管理服务器向收件人及发件人发送辅助邮件，并通过邮件客户端向发件人显示辅助邮件，辅助邮件包含汇款交易号。
另一种方式是：汇款交易号在实际汇款前就能得到，如，比特币等数字货币或本地汇款，因此，若汇款标识为内部汇款或通过数字货币交互服务器将来自资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作，则发送汇款邮件的过程中还包括加载汇款交易号的步骤，以使汇款邮件中的邮件消息还携带有汇款交易号。
本例提供的邮件发送方法，能通过增加汇款标识来实现数字/电子货币与电子邮件的同一平台或跨平台同步传输，即实现信息与价值的同一平台或跨平台同步传输，而数字/电子货币的收发方也可通过电子邮件系统得到实名认证，从而获得较高的安全性、可靠性与法律保障，进一步提升电子邮件系统的金融功能，例如，通过电子邮件来收发账单、自动扣款与支付、身份认证与地址认证等，从而极大提高商业交流与生活应用的可靠性与效率，并降低相关成本，结合电子货币协议，本例的电子邮件系统也可通过电子货币实现前述的部分金融功能，并在法律框架下增加数字货币与电子货币间的互换特性。
实施例五：
基于实施例一、实施例二和实施例三，本例提供一种融合货币协议的电子邮件系统的邮件接收方法，其中，电子邮件系统包括汇款插件、邮件客户端、汇款邮件管理服务器、电子邮件管理服务器和资金管理服务器，电子邮件系统的具体描述请参考实施例一，本例不作赘述，该邮件接收方法应用于实施例一的电子邮件系统中，实现系统内部的信息和价值同步接收，具体包括如下步骤，其流程图如图9所示。
S401：通过电子邮件管理服务器接收电子邮件，并将邮件信息传输给汇款邮件管理服务器。
S402：汇款邮件管理服务器判断收到的电子邮件是否包含有汇款标识，若无，将电子邮件按普通电子邮件处理，汇款标识携带有货币的收款人信息、可能的交易号、金额与币种，币种为数字货币或/和电子货币。
其中，汇款标识位于所述电子邮件的标头部分或所述辅助邮件。汇款标识为付款头部、汇款字段、汇款窗口、视图、可视化的标识元素中的任一种或几种组合。
收款人信息至少包括以下之一：
收款人的数字货币地址，或/和所对应的名称；
收款人的数字货币或电子货币所绑定的账号及服务商，或/和共同所对应的
名称。
S403：若含有汇款标识，则接收到的电子邮件为汇款邮件，将汇款邮件的相关信息传输给资金管理服务器，资金管理服务器查询汇款状态，并将查询结果反馈给汇款邮件管理服务器。
S404：汇款邮件管理服务器根据反馈的查询结果将汇款邮件及相关信息发送给收件人的邮件客户端。
上述仅涉及了同一平台内的信息和价值同步接收，进一步，为了实现跨平台的信息和价值同步接收，电子邮件系统还包括外部网络接口，外部网络接口包括电子邮件交互服务器、数字货币交互服务器和第三方数字/电子货币交互服务器；在上述邮件接收步骤的基础上，若所接收的邮件为外部邮件，本例还提供跨系统接收汇款邮件的步骤，跨系统接收汇款邮件的具体步骤如下。
S501：电子邮件管理服务器通过电子邮件交互服务器获取外部发送的电子邮件，并将电子邮件的邮件信息发送给汇款邮件管理服务器。
S502：汇款邮件管理服务器判断收到的邮件信息是否包含有汇款标识，若无，将电子邮件按普通电子邮件处理。
S503：若含有汇款标识，则接收到的电子邮件为汇款邮件，将汇款邮件的相关信息传输给资金管理服务器。
S504：资金管理服务器通过发送方的资金管理服务器，或者通过数字货币交互服务器或/和第三方数字/电子货币交互服务器查询汇款状态，并将查询结果反馈给汇款邮件管理服务器。
S505：汇款邮件管理服务器根据反馈的查询结果将汇款邮件及相关信息发送给收件人的邮件客户端。
以上应用了具体个例对本发明进行阐述，只是用于帮助理解本发明，并不用以限制本发明。对于本发明所属技术领域的技术人员，依据本发明的思想，还可以做出若干简单推演、变形或替换。

Claims (26)

  1. 一种融合货币协议的电子邮件系统，其特征在于，包括：汇款插件、邮件客户端、汇款邮件管理服务器、电子邮件管理服务器和资金管理服务器；
    所述邮件客户端加载有所述汇款插件，以向用户提供具有汇款标识的电子邮件界面，所述汇款标识携带有货币的收款人信息、金额与币种，所述币种为数字货币或/和电子货币；
    所述汇款邮件管理服务器分别与所述邮件客户端、电子邮件管理服务器和资金管理服务器交互；
    所述汇款邮件管理服务器与所述电子邮件管理服务器和资金管理服务器协同工作，所述汇款邮件管理服务器接收到所述邮件客户端发送的邮件消息后，判断所述邮件消息是否含有汇款标识，若含有汇款标识，所述汇款邮件管理服务器调度所述电子邮件管理服务器发送所述邮件消息及调度所述资金管理服务器根据所述汇款标识执行汇款操作，若否，所述汇款邮件管理服务器仅调度所述电子邮件管理服务器发送所述邮件消息。
  2. 如权利要求1所述的电子邮件系统，其特征在于，所述汇款邮件管理服务器调度所述资金管理服务器之前，所述汇款邮件管理服务器先调度所述电子邮件管理服务器发送所述邮件消息，且待所述汇款邮件管理服务器接收到所述电子邮件管理服务器反馈的邮件消息发送成功的指令后，所述汇款邮件管理服务器再调度所述资金管理服务器。
  3. 如权利要求1所述的电子邮件系统，其特征在于，所述还包括数据库服务器，所述数据库服务器用于存储汇款人和收款人的资金信息及可能的账户信息，所述数据库服务器分别与所述汇款邮件管理服务器和资金管理服务器交互，所述资金管理服务器根据所述汇款邮件管理服务器的调度指令向所述数据库服务器发送汇款请求，所述数据库服务器根据所述汇款请求更新汇款人和收款人本次汇款相关的资金信息以实现内部汇款。
  4. 如权利要求3所述的电子邮件系统，其特征在于，还包括认证服务器，所述认证服务器与所述数据库服务器和汇款邮件管理服务器交互，所述认证服务器用于对用户身份进行认证，待所述汇款邮件管理服务器通过所述认证服务器获得用户认证状态并确认有效后，所述汇款邮件管理服务器再与所述电子邮件管理服务器和资金管理服务器协同工作。
  5. 如权利要求1所述的电子邮件系统，其特征在于，还包括内外网络接口，所述内外网络接口包括电子邮件交互服务器、数字货币交互服务器和第三方数字/电子货币交互服务器；
    所述电子邮件交互服务器与所述电子邮件管理服务器交互，用于将来自所述电子邮件管理服务器的内部请求与来自网络的外部电子邮件信息根据相关协议进行转换以执行信息发送与接收操作；
    所述数字货币交互服务器和第三方数字/电子货币交互服务器分别与所述资金管理服务器交互，用于将来自所述资金管理服务器的内部请求与来自网络的外部请求根据相关协议进行转换以执行查询与汇款操作。
  6. 如权利要求5所述的电子邮件系统，其特征在于，所述电子邮件交互服务器为运行电子邮件服务程序的服务器，所述数字货币交互服务器为运行数字货币服务程序的服务器，所述第三方数字/电子货币交互服务器为支持本地或第三方接口的服务器。
  7. 如权利要求5所述的电子邮件系统，其特征在于，所述第三方数字/电子货币交互服务器将来自所述资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作后，将汇款结果反馈给所述资金管理服务器，所述汇款结果包含汇款交易号，所述资金管理服务器向所述汇款邮件管理服务器反馈所述汇款交易号，所述汇款邮件管理服务器调度所述电子邮件管理服务器向收件人及发件人发送辅助邮件，并通过所述邮件客户端向发件人显示辅助邮件，所述辅助邮件包含所述汇款交易号。
  8. 如权利要求5所述的电子邮件系统，其特征在于，若所述汇款标识为内部汇款或通过所述数字货币交互服务器将来自所述资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作，则所述邮件消息还携带有汇款交易号。
  9. 如权利要求1-8所述的电子邮件系统，其特征在于，所述汇款标识位于所述电子邮件界面的浏览页面内任一位置。
  10. 如权利要求9所述的电子邮件系统，其特征在于，所述汇款标识位于所述电子邮件界面的邮件标头。
  11. 如权利要求9所述的电子邮件系统，其特征在于，所述汇款标识为汇款字段、汇款窗口、视图、可视化的标识元素中的任一种或组合。
  12. 如权利要求9所述的电子邮件系统，其特征在于，所述收款人信息至少包括以下之一：
    收款人的数字货币地址；
    收款人的数字货币地址所对应的名称；
    收款人的数字货币或电子货币所绑定的账号及服务商；
    收款人的数字货币或电子货币所绑定的账号及服务商共同所对应的名称。
  13. 一种如权利要求1-12任一项所述的融合货币协议的电子邮件系统的邮件发送方法，其特征在于，所述电子邮件系统包括汇款插件、邮件客户端、汇款邮件管理服务器、电子邮件管理服务器和资金管理服务器，所述邮件发送方法包括步骤：
    判断所述汇款插件是否被触发，若否，所述邮件客户端生成普通邮件并发送至所述汇款邮件管理服务器，所述汇款邮件管理服务器调度所述电子邮件管理服务器发送所述普通邮件；
    若所述汇款插件被触发：
    所述邮件客户端运行所述汇款插件，以向用户提供具有汇款标识的电子邮件界面，所述汇款标识携带有货币的收款人信息、金额与币种，所述币种为数字货币或/和电子货币；
    通过所述汇款标识获取收款人信息、金额与币种，并生成汇款邮件发送至汇款邮件管理服务器；
    所述汇款邮件管理服务器与所述电子邮件管理服务器和资金管理服务器协同工作，调度所述电子邮件管理服务器发送所述汇款邮件中的邮件消息及调度所述资金管理服务器根据所述汇款标识执行所述汇款邮件中的汇款操作。
  14. 如权利要求13所述的邮件发送方法，其特征在于，还包括自动回复邮件的步骤，若自动回复邮件包含可识别的汇款请求信息，则自动回复邮件的过程中还包括通过回复邮件进行汇款的步骤：
    若自动回复邮件包含可识别的汇款请求信息，则提示用户是否按照所述汇款请求信息汇款；
    若是，生成回复邮件，以使所述回复邮件的电子邮件界面自动加载有所述汇款标识，并将所述汇款请求信息中的收款人信息、金额与币种自动录入所述汇款标识，以生成能自动回复的汇款邮件，并发送至汇款邮件管理服务器；
    所述汇款邮件管理服务器调度所述电子邮件管理服务器发送所述自动回复的汇款邮件中的邮件消息及调度所述资金管理服务器根据所述汇款标识执行所述自动回复的汇款邮件中的汇款操作。
  15. 如权利要求13或14所述的邮件发送方法，其特征在于，所述电子邮件系统还包括外部网络接口，所述外部网络接口包括电子邮件交互服务器、数字货币交互服务器和第三方数字/电子货币交互服务器；所述邮件发送方法还包括跨系统发送汇款邮件的步骤：
    通过所述电子邮件交互服务器将来自所述电子邮件管理服务器的内部请求根据相关协议转换为外部电子邮件信息以执行信息发送；
    通过所述数字货币交互服务器或/和第三方数字/电子货币交互服务器将来自所述资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作。
  16. 如权利要求15任一项所述的邮件发送方法，其特征在于，所述汇款邮件管理服务器调度所述资金管理服务器之前，所述汇款邮件管理服务器先调度所述电子邮件管理服务器发送所述邮件消息，且待所述汇款邮件管理服务器接收到所述电子邮件管理服务器反馈的邮件消息发送成功的指令后，所述汇款邮件管理服务器再调度所述资金管理服务器。
  17. 如权利要求15所述的邮件发送方法，其特征在于，所述第三方数字/电子货币交互服务器将来自所述资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作后，还包括向收件人和发件人发送辅助邮件的步骤：
    将汇款结果反馈给所述资金管理服务器，所述汇款结果包含汇款交易号；
    所述资金管理服务器向所述汇款邮件管理服务器反馈所述汇款交易号；
    所述汇款邮件管理服务器调度所述电子邮件管理服务器向收件人及发件人发送辅助邮件，并通过所述邮件客户端向发件人显示辅助邮件，所述辅助邮件包含所述汇款交易号。
  18. 如权利要求15所述的邮件发送方法，其特征在于，若所述汇款标识为内部汇款或通过所述数字货币交互服务器将来自所述资金管理服务器的内部请求根据相关协议转换为外部请求以执行汇款操作，则发送汇款邮件的过程中还包括加载汇款交易号的步骤，以使所述汇款邮件中的邮件消息还携带有汇款交易号。
  19. 如权利要求15所述的邮件发送方法，其特征在于，所述汇款标识位于所述电子邮件界面的邮件标头。
  20. 如权利要求15所述的邮件发送方法，其特征在于，所述汇款标识为汇款字段、汇款窗口、视图、可视化的标识元素中的任一种或组合。
  21. 如权利要求15所述的邮件发送方法，其特征在于，所述收款人信息至少包括以下之一：
    收款人的数字货币地址；
    收款人的数字货币地址所对应的名称；
    收款人的数字货币或电子货币所绑定的账号及服务商；
    收款人的数字货币或电子货币所绑定的账号及服务商共同所对应的名称。
  22. 一种如权利要求1-12任一项所述的融合货币协议的电子邮件系统的邮件接收方法，其特征在于，所述电子邮件系统包括汇款插件、邮件客户端、 汇款邮件管理服务器、电子邮件管理服务器和资金管理服务器，所述收款方法包括步骤：
    通过所述电子邮件管理服务器接收电子邮件，并将邮件信息传输给汇款邮件管理服务器；
    所述汇款邮件管理服务器判断收到的电子邮件是否包含有汇款标识，若无，将所述电子邮件按普通电子邮件处理，所述汇款标识携带有货币的收款人信息、可能的交易号、金额与币种，所述币种为数字货币或/和电子货币；
    若含有汇款标识，则接收到的电子邮件为汇款邮件，将汇款邮件的相关信息传输给所述资金管理服务器；
    所述资金管理服务器查询汇款状态，并将查询结果反馈给所述汇款邮件管理服务器；
    所述汇款邮件管理服务器根据反馈的查询结果将汇款邮件及相关信息发送给收件人的邮件客户端。
  23. 如权利要求22所述的邮件接收方法，其特征在于，所述电子邮件系统还包括外部网络接口，所述外部网络接口包括电子邮件交互服务器、数字货币交互服务器和第三方数字/电子货币交互服务器；所述邮件接收方法还包括跨系统接收邮件的步骤：
    所述电子邮件管理服务器通过所述电子邮件交互服务器获取外部发送的电子邮件，并将所述电子邮件的邮件信息发送给所述汇款邮件管理服务器；
    所述汇款邮件管理服务器判断收到的邮件信息是否包含有汇款标识，若无，将所述电子邮件按普通电子邮件处理，
    若含有汇款标识，则接收到的电子邮件为汇款邮件，将汇款邮件的相关信息传输给所述资金管理服务器；
    所述资金管理服务器通过所述数字货币交互服务器或/和第三方数字/电子货币交互服务器查询汇款状态，并将查询结果反馈给所述汇款邮件管理服务器；
    所述汇款邮件管理服务器根据反馈的查询结果将汇款邮件及相关信息发送给收件人的邮件客户端。
  24. 如权利要求22所述的邮件接收方法，其特征在于，所述汇款标识位于所述电子邮件界面的邮件标头。
  25. 如权利要求22所述的邮件接收方法，其特征在于，所述汇款标识为汇款字段、汇款窗口、视图、可视化的标识元素中的任一种或组合。
  26. 如权利要求22所述的邮件接收方法，其特征在于，所述收款人信息至少包括以下之一：
    收款人的数字货币地址，或/和所对应的名称；
    收款人的数字货币或电子货币所绑定的账号及服务商，或/和共同所对应的名称。
PCT/CN2019/097045 2019-01-30 2019-07-22 一种融合货币协议的电子邮件系统、邮件发送、接收方法 WO2020155581A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2021540145A JP7308496B2 (ja) 2019-01-30 2019-07-22 通貨プロトコルを融合する電子メールシステム、メール送信方法、メール受信方法
CA3125771A CA3125771A1 (en) 2019-01-30 2019-07-22 Currency-protocol converged e-mail system, and e-mail sending and receiving methods therefor
EP19912209.4A EP3920472A4 (en) 2019-01-30 2019-07-22 E-MAIL SYSTEM MERGED WITH CURRENCY PROTOCOLS, METHOD FOR SENDING MAIL, AND METHOD FOR RECEIVING MAIL
US17/420,734 US20220108307A1 (en) 2019-01-30 2019-07-22 Currency-protocol converged e-mail system, and e-mail sending and receiving methods therefor

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910092306.7A CN109756418B (zh) 2019-01-30 2019-01-30 一种融合货币协议的电子邮件系统、邮件发送、接收方法
CN201910092306.7 2019-01-30

Publications (1)

Publication Number Publication Date
WO2020155581A1 true WO2020155581A1 (zh) 2020-08-06

Family

ID=66407140

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/097045 WO2020155581A1 (zh) 2019-01-30 2019-07-22 一种融合货币协议的电子邮件系统、邮件发送、接收方法

Country Status (6)

Country Link
US (1) US20220108307A1 (zh)
EP (1) EP3920472A4 (zh)
JP (1) JP7308496B2 (zh)
CN (1) CN109756418B (zh)
CA (1) CA3125771A1 (zh)
WO (1) WO2020155581A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11625719B2 (en) * 2020-06-24 2023-04-11 Synchrony Bank Framework free integration

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109756418B (zh) * 2019-01-30 2021-11-16 上海风汇网络科技有限公司 一种融合货币协议的电子邮件系统、邮件发送、接收方法
CN109981816B (zh) * 2019-03-21 2023-04-18 上海风汇网络科技有限公司 基于dns域名系统的价值传输系统、方法及dns服务器
CN110717746A (zh) * 2019-10-14 2020-01-21 杭州复杂美科技有限公司 一种转账、地址命名方法和系统、设备及存储介质
CN111756619B (zh) * 2020-06-24 2022-12-27 上海风汇网络科技有限公司 一种基于电子邮件的价值传输方法及价值传输集群系统
CN114971602A (zh) * 2021-02-19 2022-08-30 银联国际有限公司 支持数字货币的电子支付方法及交易系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104063784A (zh) * 2013-03-22 2014-09-24 中国银联股份有限公司 基于电子邮件的电子支付方法及系统
CN104702645A (zh) * 2013-12-10 2015-06-10 中国银联股份有限公司 一种基于Email的P2P数据处理系统以及数据处理方法
CN104956395A (zh) * 2012-12-27 2015-09-30 谷歌公司 对包含支付的电子邮件的管理
US9904924B1 (en) * 2013-03-15 2018-02-27 Square, Inc. Transferring money using electronic messages
CN109756418A (zh) * 2019-01-30 2019-05-14 张海旻 一种融合货币协议的电子邮件系统、邮件发送、接收方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997002539A1 (fr) * 1995-07-06 1997-01-23 Hitachi, Ltd. Systeme d'envoi de monnaie electronique
US20080249937A1 (en) * 2007-04-06 2008-10-09 Walls Robert K Payment card based remittance system with delivery of anti-money laundering information to receiving financial institution
JP5491357B2 (ja) 2010-11-04 2014-05-14 ヤフー株式会社 送金システム連携装置及びその方法
CN102360480B (zh) * 2011-10-06 2017-06-16 浙江易网科技股份有限公司 一种链接网上支付及记录链接的方法和系统
US10497037B2 (en) * 2014-03-31 2019-12-03 Monticello Enterprises LLC System and method for managing cryptocurrency payments via the payment request API
CN107230299B (zh) * 2016-03-25 2021-07-16 中国人民银行数字货币研究所 数字货币的银行存储的方法及系统
WO2018201237A1 (en) * 2017-05-01 2018-11-08 Blockchain Technology Group Inc. Dba Blockchain Intelligence Group System, devices and method for approximating a geographic origin of a cryptocurrency transaction
WO2018236765A1 (en) * 2017-06-18 2018-12-27 Hieu Trung Tran METHOD AND SYSTEM FOR REWARDING PARTICIPANTS FOR DIRECT ENGAGEMENT IN AN ENHANCED COMMUNICATION AND PAYMENT NETWORK

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104956395A (zh) * 2012-12-27 2015-09-30 谷歌公司 对包含支付的电子邮件的管理
US9904924B1 (en) * 2013-03-15 2018-02-27 Square, Inc. Transferring money using electronic messages
CN104063784A (zh) * 2013-03-22 2014-09-24 中国银联股份有限公司 基于电子邮件的电子支付方法及系统
CN104702645A (zh) * 2013-12-10 2015-06-10 中国银联股份有限公司 一种基于Email的P2P数据处理系统以及数据处理方法
CN109756418A (zh) * 2019-01-30 2019-05-14 张海旻 一种融合货币协议的电子邮件系统、邮件发送、接收方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3920472A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11625719B2 (en) * 2020-06-24 2023-04-11 Synchrony Bank Framework free integration
US20230281624A1 (en) * 2020-06-24 2023-09-07 Synchrony Bank Framework free integration

Also Published As

Publication number Publication date
CN109756418A (zh) 2019-05-14
CA3125771A1 (en) 2020-08-06
EP3920472A4 (en) 2023-01-11
EP3920472A1 (en) 2021-12-08
US20220108307A1 (en) 2022-04-07
JP2022522606A (ja) 2022-04-20
JP7308496B2 (ja) 2023-07-14
CN109756418B (zh) 2021-11-16

Similar Documents

Publication Publication Date Title
WO2020155581A1 (zh) 一种融合货币协议的电子邮件系统、邮件发送、接收方法
US20210042714A1 (en) System and method for compositing items and authorizing transactions
US20170140346A1 (en) Systems and methods providing payment transactions
US20130013516A1 (en) Social network financial portal
US20120284175A1 (en) Method and system for facilitating person-to-person payments
US10735356B1 (en) Intelligent messaging system based multiple account selection for electronic message communications
US8401938B1 (en) Transferring funds between parties&#39; financial accounts
US20160127234A1 (en) Service Router
US20230129136A1 (en) Communication exchanges and methods of use thereof
WO2015085852A1 (zh) 一种基于Email的P2P数据处理系统以及数据处理方法
US11935028B1 (en) Real-time account-to-account payment
WO2021258737A1 (zh) 一种基于电子邮件的价值传输方法及价值传输集群系统
KR102240540B1 (ko) 고신뢰 문서 유통을 위한 블록체인 기술 기반 이메일 송수신 시스템
US20220188809A1 (en) Value transfer system based on the domain name system (dns), method thereof and dns server
US10158614B2 (en) Database processing system for multiple destination payloads
US20220405748A1 (en) Call-back mechanisms for blockchain transactions
US20210319415A1 (en) Two-in-one process for payments and electronic data
US20220172209A1 (en) Direct extended reach system and method
EP4038829A1 (en) Call-back mechanisms for blockchain transactions
KR100785531B1 (ko) 전자문서 처리방법 및 시스템과 이를 위한 프로그램기록매체
TWI494882B (zh) 電子帳單處理自動化
JP5629350B1 (ja) 総合振込データ作成支援システム
JP2020003907A (ja) 情報通信装置、情報通信方法及び情報通信プログラム

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3125771

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2021540145

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019912209

Country of ref document: EP

Effective date: 20210830