System And Method Of Operating An Email Service For Mobile Telephones

Abstract

For email communication, an APP downloaded onto a smartphone and email accounts are automatically provided through an associated server system. Each email account is uniquely related the APP and includes a key associated with the telephone number.

Claims

1. A system for activating an email account and sending and receiving emails on a mobile telephone, the system comprising a first mobile telephone comprising a SIM card with a registered first telephone number, TelNo1, and with Internet access capabilities; a first email software application, APP1, installed on the first mobile telephone, wherein APP1 is non-transferable to other mobile telephones after installation, wherein APP1 is configured for automatically providing a first software key and second software key, and sending a key-combination of the first and the second software key to an application server system associated with APP1; an application server system associated with APP1 and configured for receiving the key-combination from APP1 as an authorization code for email transactions of a first email account, wherein the first email account is uniquely associated to the key-combination; wherein the application server system is configured for email transactions for receiving emails by the application server system from APP1 and sending the received email to a recipient address and receiving emails addressed to the first email account from other email addresses and sending those emails to APP1; characterized in that the first software key, TelNo1Key, is uniquely linked to the first telephone number and the second software key, APP1Key is uniquely linked to APP1; wherein the application server system is configured for email transactions for the first email account only upon receipt of the key-combination, Comb(TelNo1Key, APP1Key), as authorization code from the APP1, wherein the application server system is configured for automatic creation of the first email account as a consequence of a first-time receipt of the key-combination COMB(TelNo1Key, APP1Key) by the application server system, wherein an email address identifier of the first email account is an alphanumeric sequence containing TelNo1.

2. A system according to claim 1, wherein the application server system is configured for email transactions for the first email account only if the first SIM card has not been installed in another mobile telephone with a different email software application.

3. A system according to claim 1 or 2, wherein the application server system is configured for automatically creating a second email account as a consequence of either A or B, wherein A) is receipt from APP1 a key-combination, Comb(TelNo2Key, APP1Key), wherein TelNo2Key is a software key uniquely associated with a different telephone number TelNo2 of a different SIM card in the first telephone; wherein the email address identifier of the second email account is an alphanumeric sequence containing TelNo2. B) is receipt from a different email software application, APP2, a key-combination Comb(TelNo1Key, APP2Key), wherein APP2Key is a software key uniquely associated with APP2 on the first telephone or on a different telephone containing the first SIM card with the first telephone number TelNo1, wherein email address identifier of the second email account is identical of the email address identifier of the first email account containing TelNo1, and wherein the first email account discontinues working.

4. A system according to claim 3, wherein the application server system in event A) and B) is further configured for automatically A) providing access by APP1 on the first telephone to previous emails from the first email account, if the received key-combination Comb(TelNo2Key, APP1Key), wherein TelNo2Key is a software key uniquely associated with a different telephone number TelNo2 of a different SIM card in the first telephone, is followed by receipt from APP1 of an authorised number-change-code that was previously sent from the application server system to APP1 upon request by a user command, or if there is at least 80% identity between the contact lists in the first telephone before and after change of telephone number from TelNo1 to TelNo2; B) providing access by APP2 to previous emails from the first email account, if the received key-combination Comb(TelNo1Key, APP2Key) is followed by receipt from APP2 of an authorised APP-change-code that was previously sent from the application server system to APP1 upon request by a user command, or if there is at least 80% identity between the contact list in first telephone with APP1 and the contact list in the telephone with APP2.

5. A system according to any preceding claim, wherein the application server system is configured for email transactions for the first email account only if the first telephone comprises the SIM card with the registered first telephone number.

6. A method of operating a system with an email service on a mobile telephone, the method comprising providing a first mobile telephone comprising a SIM card with a registered first telephone number, TelNo1, and with Internet access capabilities; providing a first email software application, APP1, on the first mobile telephone, wherein APP1 is non-transferable to other mobile telephones after installation, by the APP1 automatically providing a first software key and second software key, and sending a key-combination of the first and the second software key to an application server system associated with APP1; by the application server system receiving the key-combination from APP1 as an authorization code for email transactions of a first email account, wherein the first email account is uniquely associated to the key-combination; further by email transactions receiving emails by the application server system from APP1 and sending the received email to a recipient address and receiving emails addressed to the first email account from other email addresses and sending those emails to APP1, characterized in that the first software key, TelNo1Key, is uniquely linked to the first telephone number and the second software key, APP1Key is uniquely linked to APP1; wherein the application server system is configured for email transactions for the first email account only upon receipt of the key-combination, Comb(TelNo1Key, APP1Key), as authorization code from the APP1, and wherein the method comprises performing email transactions with APP1, wherein the method comprises first-time receiving the key-combination, Comb(TelNo1Key, APP1Key), by the application server system and, as a consequence thereof, automatically creating the first email account by the application server system wherein the method comprises providing the email address identifier of the first email account as an alphanumeric sequence containing TelNo1.

7. A method according to claim 6, wherein the method comprises removing the SIM card with TelNo1 from the first mobile telephone and installing a different SIM card with a different telephone number, TelNo2, in the first mobile telephone; by APP1 automatically providing a different first software key, TelNo2Key, and sending the resulting software key-combination, Comb(TelNo2Key, APP1Key), to the application server system, and as a consequence of receiving the software key-combination Comb(TelNo2Key, APP1Key), automatically creating a second email account by the application server system, wherein the second email account is uniquely associated to the key-combination Comb(TelNo2Key, APP1Key), wherein the email address identifier of the second email account is an alphanumeric sequence containing TelNo2.

8. A method according to claim 6 or 7, wherein the method comprises, by a user's input on a user interface of APP1 on the first mobile telephone by user command requesting a number-change-code from the application server system for change of telephone number from the first telephone number TelNo1 to a different telephone number; by APP1 receiving the number-change-code and displaying it to the user; then, removing the SIM card from the first mobile telephone and installing a different SIM card with a different telephone number, TelNo2, in the first mobile telephone; by APP1 automatically providing a different first software key, TelNo2Key, and sending the resulting software key-combination, Comb(TelNo2Key, APP1Key), to the application server system; inserting the number-change-code on a user interface of APP1 on the first mobile telephone and sending the number-change-code by APP1 to the application server system; as a consequence of receiving the number-change-code from APP1 by the application server system, providing access to emails in the first email account despite the change of software key-combination from Comb(TelNo1Key, APP1Key) to Comb(TelNo2Key, APP1Key).

9. A method according to claim 8, wherein the method comprises, as a consequence of the receipt of Comb(TelNo2Key, APP1Key), by the application server system automatically creating a second email account uniquely related to Comb(TelNo2Key, APP1Key); as a consequence of the receiving of the number-change-code from APP1 by the application server system, linking the first email account associated to TelNo1 to the second email account associated with TelNo2 and providing access to previous emails in the first email account through operation of the second email account.

10. A method according to anyone of the claims 6-9, wherein the method comprises, removing the SIM card from the first mobile telephone and installing the SIM card in a second mobile telephone; providing the second mobile telephone with a second email software application, APP2, similar to APP1 but with a different software key, APP2Key; by APP2 sending a software key-combination Comb(TelNo1Key, APP2Key) to the application server system, and as a consequence of the receipt of Comb(TelNo1Key, APP2Key), by the application server system automatically creating a further email account uniquely related to Comb(TelNo1Key, APP2Key), wherein email address identifier of the second email account is identical of the email address identifier of the first email account containing TelNo1, and wherein the first email account is discontinued working.

11. A method according to anyone of the claims 6-10, wherein the method comprises, by a user's input on a user interface of APP1 on the first mobile telephone by user command requesting an APP-change-code from the application server system for change of the APP; by APP1 receiving the APP-change-code and displaying it to the user; removing the SIM card from the first mobile telephone and installing the SIM card in a second mobile telephone; providing the second mobile telephone with a second email software application, APP2, similar to APP1 but with a different software key, APP2Key; by APP2 sending a software key-combination Comb(TelNo1Key, APP2Key) to the application server system; inserting the APP-change-code on a user interface of APP2 on the second mobile telephone and sending the APP-change-code by APP2 to the application server system; as a consequence of receiving APP-change-code from APP2 by the application server system, providing access to emails in the first email account despite the changed software key-combination from Comb(TelNo1Key, APP1Key) to Comb(TelNo1Key, APP2Key).

12. A method according to claim 11, wherein the method comprises, as a consequence of the receipt of the key-combination Comb(TelNo1Key, APP2Key) by the application server system, creating a second email account uniquely related to Comb(TelNo1Key, APP2Key); as a consequence of receiving of the APP-change-code from APP2 by the application server system, linking the first email account associated to APP1 to the second email account associated with APP2, and providing access to previous emails in the first email account through operation of the second email account.

Description

SHORT DESCRIPTION OF THE DRAWINGS

[0113] The invention will be explained in more detail with reference to the drawing, where

[0114] FIG. 1 is a flow chart illustrating the stages to activate a proprietary email account for the smartphone for sending and receiving emails;

[0115] FIG. 2 is a flow chart illustrating the stages for sending and receiving emails between two proprietary email accounts;

[0116] FIG. 3 is a flow chart illustrating the stages for sending an email from the first proprietary email account to a conventional email address;

[0117] FIG. 4 is a flow chart illustrating the stages for receiving an email from a conventional email address to proprietary email address and forwarding it to a smartphone.

[0118] FIG. 5 is a flow chart illustrating the stages for changing the TelNo and transferring the previous proprietary email account to the new proprietary email account

[0119] FIG. 6 is a flow chart illustrating the stages for changing the APP and transferring the previous proprietary email account to new proprietary email account

DETAILED DESCRIPTION/PREFERRED EMBODIMENT

[0120] The system is explained in more detail in the following by referring to various examples. The examples are given with respect to a proprietary email account that has the telephone number as part of the proprietary email address.

[0121] With reference to FIG. 1, the following stages are performed to prepare a mobile telephone for sending and receiving emails.

[0122] Stage 101: A first mobile telephone of a first user is provided with a SIM card inside having a first registered telephone number TelNo1. A first App APP1 is downloaded, with an appropriate APP distribution service for example PlayStore for Android and AppStore for iOS, through the Internet onto the first mobile telephone and installed thereon.

[0123] Stage 102: As part of the installation procedure, APP1 receives TelNo1 from the SIM card, either automatically or by user input, and submits the key-combination, Comb(TelNo1Key, APP1Key) automatically to the application server system.

[0124] In the event the TelNo1 is by user input, the application server system sends a SMS with an authentication code to the telephone number to verify the correctness of telephone number. On receiving the authentication code by user input, the APP submits it automatically to the application server system.

[0125] Stage 103: Upon receipt of the key-combination, Comb(TelNo1Key, APP1Key), the application server system automatically activates a first proprietary email account with the first email address TelNo1@domainname.TLD. Thus, the email address contains the mobile number, which for international use also contains the country code. It also contains a domain name, domainname, as part of the email address, for example with the format @domainname.com, where com, is a specific examples of top-level domain (TLD).

[0126] Stage 104: The application server system confirms to APP1 that a proprietary email account has been activated.

[0127] Stage 105: Upon activation of first proprietary email account, either automatically or by user confirmation, APP1 sends a copy of the contact list on the first mobile phone to the application server system to be stored in the first proprietary email account or be stored in association with the first proprietary email account. The APP continually updates the stored contact list on the application server system.

[0128] Optional stage 106: Optionally, APP1 prompts the user to indicate whether the established first proprietary email account should be linked to a conventional email address to which all received emails are forwarded. This option gives the user the possibility to use an existing conventional email account, which will also receive all emails that are received by proprietary email account. For others, this implies the advantage that they do not need to remember or store the email address of the conventional email account but only the first telephone number. This is an advantage because contact lists in telephones typically only contain the telephone numbers of contacts, which are stored upon receipt of a call and typically not even inspected and remembered by the user. If the first user indicates that a link to a conventional email account should be established, APP1 submits the information to the application server system which registers such forwarding link in connection with the first proprietary email account.

[0129] After these few stages, the user is ready to send and receive emails. It is universal for any telephone number in any country and independent of the specific telephone service provider, for example Orange, Vodafone, or AT&T.

[0130] With reference to FIG. 2, an example is given for sending and receiving email between two mobile telephones.

[0131] Stage 201: Upon activating the first proprietary email account for the first telephone number, APP1 on the first mobile telephone presents an email client to the first user as a prompt to compose an email by inserting a telephone number TelNo2 to which an email should be sent. The first user either enters a telephone number on the keypad or selects a certain contact number TelNo2 from the list of contacts stored in the first mobile telephone. A proprietary email address is automatically created by APP1 of the format TelNo2@domainname.TLD

[0132] Stage 202: The user finalises the email by inserting text in a subject field and/or the email body, optionally with attachments, such as documents, images, or videos.

[0133] Stage 203: Upon user command and request, APP1 sends the email to the application server system, optionally by using a proprietary communication protocol different from SMTP.

[0134] Stage 204: The application server system receives the email and checks whether a proprietary email account with TelNo2 in the address is already activated.

[0135] Stage 205: In the affirmative, the application server system stores the email onto that account and establishes a connection to the second APP, APP2, on the second mobile telephone with TelNo2 and forwards the email to APP2 on the second mobile telephone, optionally by using a proprietary communication protocol.

[0136] Optional stage 206: If such proprietary email account does not yet activated, the application server system sends a message, typically via SMS, to the second mobile telephone that an email is pending for receipt and prompts the second user of such second mobile telephone to install the APP on the second mobile telephone. For example, the installation of the APP is done automatically upon confirmation by the recipient, which becomes a second user, optionally by pressing on a link in the SMS message. Optionally, a message is sent to the first user that the recipient does not yet have the APP, which motivates the first user to contact the recipient and ask him/her to install the APP. Once the APP is installed to the second mobile telephone, the email is sent to the second APP on the second mobile telephone. The received email is pushed to the second APP on the second mobile telephone automatically, optionally by the proprietary communication protocol. Alternatively, the forwarding is done by a pull-action, in which the forwarding is paused until ordered by the second APP of the second mobile telephone, for example upon activation of the second APP by the second user.

[0137] Optional stage 207: Optionally, the application server system confirms to the first user the proper delivery of the email to the second mobile telephone.

[0138] For example, the proprietary communication protocol contains certain proprietary functions. One of the optional functions is a prompt for confirmation whether an email sender address is accepted for the current and/or future emails. Such function largely eliminates receipt of spam mails. The prompt for allowing email delivery from specific senders is optionally a selected function; for example, the first user may select receiving all emails from contact persons according to the contact list but request a prompt for other senders. Alternatively, the user may request a prompt for each email sender from which an email has not been accepted for delivery before. Blocking senders is also an option to avoid spam.

[0139] In order to facilitate message transfer, the APP is optionally configured to allow sending the same email to numerous recipients selected among contacts in the contact list or even to all contacts in the contact list and, potentially to further added contacts which are not in the list. Those contacts that already have such APP installed will receive the email and those contacts that have not yet installed the APP will receive a message, typically SMS message, motivating the recipient to install the APP. This is also a way to distribute the APP quickly to a large number of users.

[0140] The APP is optionally configured for storing email history per sender/recipient, similarly to what users today are used to in messaging application and services, such as WhatsApp, WeChat, Viber, or Instagram. This makes it easy for the user to trace email conversations.

[0141] With reference to FIG. 3, the following stages are performed in order to send an email from the first application, APP1, on the first mobile telephone to a conventional email address.

[0142] Stage 301: The user composes an email by inserting a conventional email address as an alternative to a telephone number to which an email should be sent. The first user either types in a conventional email address or selects a certain email address from a stored list in the first mobile telephone.

[0143] Stage 302: An email is generated by the user by inserting text in a subject field and/or the email body, optionally with attachments, such as documents, images, or videos.

[0144] Stage 303: Upon user command and request, APP1 sends the email to the application server system, optionally according to the proprietary communication protocol.

[0145] Stage 304: From APP1, the application server system receives the proprietary email, optionally according to the proprietary communication protocol, where the email contains a conventional email address to which the email should be sent.

[0146] Stage 305: For the case that the proprietary email is provided in a proprietary format, the application server system converts the proprietary email from a proprietary communication format to a conventional email in SMTP format and sends the email according to the SMTP via the Internet to the conventional email server system that is associated with this conventional email address. For example, the conventional email server system is an MTA (mail transport agent) server system, optionally using Microsoft Exchange, qmail, Exim or sendmail as an email routing program.

[0147] Stage 306: The corresponding conventional email server system receives the email from the Internet.

[0148] With reference to FIG. 4, the following stages are performed in order to receive an email from conventional email address and forward it to APP1 on the first telephone in a proprietary format.

[0149] Stage 401: The application server system receives a conventional email for the address TelNo1@domainname.TLD through the Internet from a conventional email server system, according to SMTP.

[0150] Stage 402: The application server system converts the conventional email from SMT format to a proprietary email in a proprietary communication format and stores the email in the corresponding proprietary email account of TelNo1.

[0151] Stage 403: The application server system sends the email to APP1 on the first mobile telephone by proprietary communication protocol.

[0152] With reference to FIG. 5, the following stages are performed in order to change the TelNo and linking the first proprietary email account to the new proprietary email account.

[0153] Stage 501: Upon user command and request, APP1 sends a number-change-code for first proprietary email account to the application server system.

[0154] Stage 502: The application server system receives the request and sends an alphanumeric number-change-code for first proprietary email account to APP1. The user notes this code down or memorizes it.

[0155] Stage 503: The first user removes the SIM card from the first mobile phone and installs a different SIM card with a different telephone number, TelNo2, in the first mobile phone.

[0156] Stage 504: APP1 receives TelNo2 from the SIM card, either automatically or by user input, and submits the key-combination, Comb(TelNo2Key, APP1Key) automatically to the application server system.

[0157] Stage 505: Upon receipt of key-combination, Comb(TelNo2Key, APP1Key) the application server system automatically activates a second proprietary email account with the second email address TelNo2@domainname.TLD.

[0158] Stage 506: The application server system confirms to APP1 that a second proprietary email account has been activated.

[0159] Stage 507: Upon activation of second proprietary email account, either automatically or by user confirmation, the APP1 sends the contact list on the first mobile phone to the application server system to store it in or in association with the second proprietary email account.

[0160] Stage 508: The first user enters the number-change-code on APP1 to link the first proprietary email account to the second proprietary email account for accessing the first email account through the second email account address and submits it to the application server system.

[0161] Stage 509: Upon receipt of number-change-code, the application server system correspondingly links the first proprietary email account to the second proprietary email account, providing access to emails in the first proprietary email account through the second proprietary email account.

[0162] Stage 510: In the event, the first user does not remember the number-change-code, upon user command, APP1 sends a verification request to application server system to verify that the first proprietary email account belongs to the first user.

[0163] Stage 511: Upon receipt of the verification request, the application server systems compares the contact list stored for the first proprietary email account with the contact list on the first mobile phone. If the contact list on the first mobile phone matches a predetermined fraction, for example at least 80% or even 90%, of contacts stored for first proprietary account, the application server system links the first proprietary email account to the second proprietary email account, providing access to emails in the first proprietary email account through the second proprietary email account.

[0164] With reference to FIG. 6, the following stages are performed in order to change the APP from APP1 to APP2 and transferring the first proprietary email account to the new proprietary email account.

[0165] Stage 601: Upon user command and request, APP1 sends a request for an APPchange-code for the first proprietary email account to the application server system.

[0166] Stage 602: The application server system receives the request and sends an alphanumeral APP-change-code for first proprietary email account to APP1. The user notes this code down or memorizes it.

[0167] Stage 603: The first user removes the SIM card from the first mobile phone and installs the SIM card in a second mobile phone with APP2.

[0168] Stage 604: APP2 receives TelNo1 from the SIM card, either automatically or by user input, and submits the key-combination, Comb(TelNo1Key, APP2Key) automatically to the application server system.

[0169] Stage 605: Upon receipt of key-combination, Comb(TelNo1Key, APP2Key) the application server system automatically activates a second proprietary email account with the email address TelNo1@domainname.TLD.

[0170] It must be noted that the email addresses TelNo1@domainname.TLD of the first and second proprietary email account are identical but the accounts different in the sense that the second account cannot be opened with the first key combination Comb(TelNo1Key, APP1Key) but only with the second key combination Comb(TelNo1Key, APP2Key) and vice versa. Only once, the APP-change-code has been entered, as explained in the following, or the contact list had been compared, the two accounts are linked. This is done to safeguard the interest of the users in case that the telephone number was acquired by a second user.

[0171] Stage 606: The application server system confirms to APP2 that a second proprietary email account has been activated.

[0172] Stage 607: Upon activation of second proprietary email account, either automatically or by user confirmation, APP2 sends the contact list on the second mobile phone to the application server system to store in the second proprietary email account.

[0173] Stage 608: The first user enters the APP-change-code on APP2 to link the first proprietary email account with the second proprietary email account and submits it to the application server system.

[0174] Stage 609: Upon receipt of APP-change-code, the application server system links the first proprietary email account to the second proprietary email account, providing access to emails in the first proprietary email account through the second proprietary email account.

[0175] Stage 610: In the event, the first user does not remember the APP-change-code, upon user command, APP1 sends a request to the application server system to verify that the first proprietary email account belongs to the first user.

[0176] Stage 611: Upon receipt of the request, the application server systems compares the contact list stored for the first proprietary email account and the contact list on the second mobile phone. If the contact list on the second mobile phone matches a predetermined fraction, for example at least 80 or even at least 90%, of contacts stored on first proprietary account, the application server system links the first proprietary email account to the second proprietary email account, providing access to emails in the first proprietary email account through the second proprietary email account.

[0177] Optionally, the first proprietary email account is also accessible from a laptop or desktop computer via a desktop application, which is associated with APP1 on the first mobile telephone and in function similar to APP1 on the first mobile telephone. For example, the desktop application mirrors APP1 and is synchronized with APP1. In such case, the application server system is linking APP1 and the desktop application upon submission of a desktop-access-code on the desktop application, which is sent by the application server system to APP1 upon user command and request.

[0178] If more than one proprietary email account is linked to APP1, in such a case all the proprietary email accounts linked to APP1 are also accessible from the desktop application.

[0179] In order to give further access possibilities, APP1 may also be accessible from any arbitrary Internet terminal via web applications, upon submission of the web-access-code on the web, which is sent by the application server system to APP1 upon user command and request.

[0180] When an email is received by the APP, the corresponding sender phone number is shown, or optionally the corresponding name from the contact list stored in the mobile telephone.

[0181] Further, as already indicated above, the proprietary email account can be linked to conventional email accounts such that emails received to TelNo@domainame.TLD are forwarded to the conventional email account. If the system uses a proprietary email format, the format is changed thereto, for example to SMTP format.