Source: http://www.google.co.uk/patents/US20060277265
Timestamp: 2017-12-17 16:05:39
Document Index: 636547928

Matched Legal Cases: ['Application No. 20045466', 'art 212', 'art 216', 'art 216', 'art 216', 'art 310', 'art 212', 'art 212']

Patent US20060277265 - Provisioning of e-mail settings for a mobile terminal - Google Patents
Method and apparatus for provisioning an e-mail service to a mobile terminal in an e-mail system that uses e-mail addresses comprising a domain part. The apparatus maintains a list of good setting parameter sets versus e-mail domain parts. It receives an e-mail address and user authentication information...http://www.google.co.uk/patents/US20060277265?utm_source=gb-gplus-sharePatent US20060277265 - Provisioning of e-mail settings for a mobile terminal
Publication number US20060277265 A1
Application number US 11/289,308
Filing date 30 Nov 2005
Priority date 3 Dec 2004
Also published as US8116214, US8873411, US20120185918
Publication number 11289308, 289308, US 2006/0277265 A1, US 2006/277265 A1, US 20060277265 A1, US 20060277265A1, US 2006277265 A1, US 2006277265A1, US-A1-20060277265, US-A1-2006277265, US2006/0277265A1, US2006/277265A1, US20060277265 A1, US20060277265A1, US2006277265 A1, US2006277265A1
Inventors Ari Backholm, Seppo Salorinne, Jussi Heinonen, Marko Ketonen, Lauri Vuornos
Original Assignee Seven Networks International Oy
Patent Citations (99), Referenced by (100), Classifications (5), Legal Events (7)
US 20060277265 A1
Method and apparatus for provisioning an e-mail service to a mobile terminal in an e-mail system that uses e-mail addresses comprising a domain part. The apparatus maintains a list of good setting parameter sets versus e-mail domain parts. It receives an e-mail address and user authentication information from a user and compares the domain part of the received address with domain parts in the list of good parameter sets. If a match is found, e-mail service is provisioned with the matching parameter set. If no match is found, the apparatus requests and receives further parameters from the user, including an e-mail server address, and provisions the e-mail service with the further parameters. If the provisioning with the further parameters is successful, the domain part and the further parameters are used to generate a new setting parameter set in the list of good setting parameter sets.
1. A method for provisioning an e-mail service to a mobile terminal in an e-mail system that uses e-mail addresses, wherein each e-mail address comprises a domain part, the method comprising:
a) maintaining a list of good setting parameter sets, wherein each good setting parameter set relates to a domain part of an e-mail address;
b) requesting and receiving an e-mail address and a user authentication information from a user of the mobile terminal, wherein the e-mail address comprises a domain part;
c) comparing the domain part of the e-mail address received from the user with domain parts in the list of good setting parameter sets;
d) if a match is found in step c), provisioning the e-mail service to the mobile terminal with the setting parameter set that produced the match;
e) if no match is found in step c), requesting and receiving further parameters from the user, the further parameters including at least an address of an e-mail server, and provisioning the e-mail service to the mobile terminal with the further parameters;
f) if the provisioning in step e) is successful, using the domain part and the further parameters to generate a new setting parameter set in the list of good setting parameter sets.
keeping track of a failure measure of the provisioning in step e); and
if the failure measure exceeds a predetermined threshold, marking the corresponding domain part as bad; and wherein
the provisioning in step c) is only performed if the domain part received from the user is not is not marked as bad.
3. A method according to claim 1, further comprising maintaining a list of alternative setting parameter sets for one or more domain parts.
4. A method according to claim 1, further comprising automatically determining at least part of the authentication information from the e-mail address.
5. A method according to claim 1, further comprising maintaining a set of domain-specific instructions to be displayed to the user.
6. A method according to claim 1, further comprising testing the provisioning in step d) and/or e), wherein the testing comprises sending a test message using the provisioned e-mail service and attempting to read the test message.
7. An apparatus for provisioning an e-mail service to a mobile terminal in an e-mail system that uses e-mail addresses, wherein each e-mail address comprises a domain part;
a list of good setting parameter sets, wherein each good setting parameter set relates to a domain part of an e-mail address;
user interface means for requesting and receiving an e-mail address and a user authentication information from a user of the mobile terminal, wherein the e-mail address comprises a domain part;
comparison means for comparing the domain part of the e-mail address received from the user with domain parts in the list of good setting parameter sets and for finding matching setting parameter set;
user interface means for requesting and receiving further parameters from the user if no matching setting parameter set exists, the further parameters including at least an address of an e-mail server,
provisioning means coupled to the comparison means for provisioning the e-mail service to the mobile terminal with said matching setting parameter set and for provisioning the e-mail service to the mobile terminal with the further parameters if no matching setting parameter set exists;
setting generation means for generating a new setting parameter set in the list of good setting parameter sets based on the domain part and the further parameters, if said provisioning with the further parameters is successful.
8. Software for a data processor embodied in a carrier, the software comprising program instructions for carrying out the steps of claim 1 when the software is executed in the data processor.
This non-provisional application relies upon Finnish Application No. 20045466, filed on Dec. 3, 2004, for priority and also relies upon U.S. Provisional Application 60/651,081, filed Feb. 9, 2005, the contents of both of which are incorporated herein by reference in their entireties.
The invention relates to methods, equipment and software for provisioning of e-mail service.
Before using an e-mail service with a mobile terminal, the e-mail service must be provisioned, which involves entering a set of settings, such as the address of an e-mail server. Some systems require the server addresses for incoming e-mail and outgoing e-mail separately. Prior e-mail service provisioning techniques suffer from certain problems. For instance, users are not normally aware of the required settings, and when they are, entry of parameters is difficult given the small user interfaces of mobile terminals.
An object of the present invention is to provide a method and an apparatus for implementing the method so as to alleviate the above problems. The object of the invention is achieved by the methods and equipment which are characterized by what is stated in the independent claims. Preferred embodiments of the invention are disclosed in the dependent claims.
An aspect of the invention is a method that comprises the steps of:
Another aspect of the invention is an apparatus for carrying out the steps of the method. The apparatus may be a dedicated provisioning server, or it may be integrated in or co-located with some other network element or function.
As used herein, ‘good’ and ‘bad’ in the context of domains and setting parameters are not relative terms but precise shorthand notations to indicate domains under which e-mail service respectively can and cannot be validly provisioned with this technique.
The success or failure of e-mail service provisioning can be tested by sending a test message using the provisioned e-mail service and attempting to read, and optionally delete, the test message.
An advantage of the invention is that in many cases e-mail service can be successfully provisioned to users unaware of the required setting parameters. A further benefit is that the amount of data to be entered is reduced. In other words, the invention save time and reduces errors.
In terms of hardware, the apparatus can be a conventional Internet server comprising appropriate input and output interfaces, processor and memory, wherein the memory comprises routines and data structures for carrying out the steps of the above method.
FIG. 2 shows a user interface screen for requesting setting parameters from a user;
FIG. 3 shows a table of good and bad setting parameters;
FIG. 4A shows a table of bad setting parameters;
FIG. 4B shows a table of alternative setting parameters; and
FIG. 5 shows a flow chart for processing user-supplied setting parameters.
The invention is applicable to virtually any mobile e-mail system architecture. FIG. 1 shows an exemplary system architecture which is supported by the owner of the present application. Reference numeral 100 denotes a host system that is able to send an receive e-mail messages. Reference numeral 102 denotes a mobile terminal, also able to send an receive e-mail messages. The e-mail messages may originate or terminate at external e-mail terminals, one of which is denoted by reference numeral 104. The invention aims at improving cooperation between the host system 100 and mobile terminal 102 such that they can use a single e-mail account as transparently as possible. This means, for example, that the users of the external e-mail terminals 104, when sending or receiving e-mail, do not need to know if the user of the host system 100 actually uses the host system 100 or the mobile terminal 102 to communicate via e-mail. The transparency also means that e-mail manipulation at the mobile terminal 102 has, as far as possible, the same effect as the corresponding e-mail manipulation at the host system 100. For example, e-mail messages read at the mobile terminal 102 should preferably be marked as read at the host system.
We assume here that the access network 114 is able to establish and maintain a tunnel 122 between the messaging centre 110 and the mobile terminal 102. For instance, the tunnel may be set up using GPRS Tunnelling Protocol (GTP) or its later derivatives, or any other suitable tunnelling protocol.
A real e-mail system supports a large number of mobile terminals 102 and tunnels 122. In order to keep track of which e-mail account and which tunnel belongs to which mobile terminal, the messaging centre 110 and the connectivity function collectively maintain an association 124, 124′ for each supported mobile terminal. Basically, each association 124, 124′ joins three fields, namely an e-mail address 124A assigned to the mobile terminal or its user, encryption information 124C and a temporary wireless identity 124D of the mobile terminal in the access network. The embodiment shown in FIG. 1 also employs a terminal identifier 124B which may be the same as the e-mail address 124A of the mobile terminal 102, in which case the association 124 actually associates three information items. Alternatively, the terminal identifier 124B may be an identifier arbitrarily assigned to the mobile terminal. In a preferred implementation the terminal identifier 124B is the mobile terminal's equipment identifier or its derivative. The encryption information 124C is preferably related to the mobile terminal's equipment identity and is preferably generated by the mobile terminal itself, so as to ensure that no other terminal besides the one used for creating the encryption information 124C will be able to decrypt incoming encrypted e-mail messages. The temporary wireless identity 124D may be the identifier of the tunnel 122 to the mobile station. Of course, the tunnel identifier is not permanent and is only known when a tunnel exists.
In the embodiment shown in FIG. 1, the inventive method can be executed in the connectivity function 120, but if one is not present, a separate provisioning server 126 can be used.
FIG. 2 shows a user interface screen 200 for requesting setting parameters from a user. The user may enter the setting parameters by means of the mobile terminal 102 or a conventional computer, such as the host system 100. Reference numeral 202 generally denotes a set of prompts displayed to the user. Reference numerals on the right-hand side of FIG. 2 denote the setting parameters entered by the user. Parameter 210 is the user's e-mail address. The e-mail address 210 contains a user-specific part 212 and a domain part 216 which are separated by a separator character @ 214. As used herein, the domain part of an e-mail address is the part of the e-mail address that follows the separator character @. Parameters 220 and 222 constitute user-specific authentication information, which in this example consists of a user name 220 and a password 222.
The above-described parameters will be requested from every user, and for many users they suffice. Users who cannot be provisioned by the e-mail address 210 and authentication information 220, 222, will be requested to enter further parameters, such as server addresses for incoming and outgoing e-mail, denoted by reference numerals 240 and 242 respectively.
FIG. 3 shows a table 300 of setting parameters. FIG. 3 shows an embodiment in which good and bad setting parameter sets are stored in a single table. Reference numerals 300A and 300B denote good and bad setting parameter sets respectively. FIG. 3 shows three versions of the table 300 that are present at different times. Reference numeral 300 shows the table in a some phase of operation, while reference numerals 300′ and 300″ denote versions of the table at two different phases of development. In the two first versions 300 and 300′, all setting parameter sets are assumed good, as indicated by the reference numeral 300A.
In this illustrative example, the table 300 comprises a row or record for three domains. For each domain, the table 300 comprises a column or field for a domain name 310, incoming server address 320 and outgoing server address 330. Preferably, there is also a failure measure column 340, the use of which will be described later.
The first version of table 300 comprises entries for two domains, denoted by subscripts after the columns. For example, reference numeral 310 1 denotes a domain 310 for a first operator.
Embodiments of the invention are best described by describing the user interface of FIG. 2, the data structures of FIGS. 3 and 4, and a method shown in FIG. 5 simultaneously. FIG. 5 shows a flow chart for processing user-supplied setting parameters. In step 500 a user logs in with a provisioning server that, by way of non-limiting example, can be the connectivity function 120 shown in FIG. 1. Alternatively, a dedicated provisioning server (not shown separately) can be provided. In step 502 the user is requested to enter the e-mail address 210 and authentication information 220, 222, shown in FIG. 2. At this step, the remaining parameters 240, 242 shown in FIG. 2 need not be requested or entered. In step 504, the provisioning server parses the domain part 216 from the user-supplied e-mail address 210 and compares, in step 506, the domain part 216 with the domains in the domain column 310 of the table 300. In the example shown in FIGS. 2 and 3, the domain is operator.fi, which matches the domain part 310 1 in the first displayed record in the table 300. The table 300 comprises sets of known good setting parameters, and in step 508, the provisioning of the e-mail service for the user is completed with the parameters 320 1 and 330 1 (server addresses for incoming and outgoing e-mail) found in this record.
Steps 510 to 518 are performed if a match is not found in step 506. In step 510 the user is requested to enter further parameters, such as the server addresses for incoming and outgoing e-mail, items 240 and 242 in FIG. 2. In step 512 the user's e-mail service provisioning is performed with these parameters. In step 514, the validity of the user's newly-supplied parameters 240 and 242 is tested. For example, the provisioning server may send a test e-mail message to the user-supplied address 210 and attempt to read, and optionally, delete it with the user-supplied authentication information 220, 222. If this test, or some other suitable test, is successful, the provisioning server creates, in step 518, a new record in the table 300. The complemented table is denoted by reference numeral 300′. It comprises the domain name 310 3 and the user's newly-supplied parameters 320 3 and 330 3.
If the test 514 initially fails, it may be repeated some time afterwards to take care of situations in which the e-mail server(s) supporting the user is/are temporarily out of action.
Step 520 relates to an optional but beneficial act of keeping track of a failure measure of e-mail service provisioning. The failure measure may, by way of example, indicate a count, rate or ratio of provisioning failures. Keeping track of the failure measure is beneficial because the user-supplied parameters 320 3 and 330 3 may not be valid to all users within the same domain 310 3. In other words, even if the test in step 514 is successful for one user, the parameters may still be invalid for other users because the relation of domain name versus server addresses may be ambiguous. This is why it is beneficial to keep track of a failure measure per domain, shown as column 340 in FIG. 300. The failure measure for the domain operator—3.fi is denoted by reference numeral 340 3. Let us assume that after some monitoring period, that measure exceeds some predetermined threshold. As a result, the data for the domain operator—3.fi is marked as bad (not configurable). In the example of FIG. 3, the server addresses for incoming and outgoing e-mail for operator 3, denoted by reference numerals 320 3 and 330 3, are replaced by zeros. The zeros acts as signs for invalid data, which means that the e-mail addresses in the domain operator—3.fi are ambiguous and cannot be adequately provisioned by this technique. Reference numeral 300B denotes a section of the table 300 that comprises bad setting parameter sets.
The predetermined threshold for the failure measure cannot be zero or very close to zero because even validly provisioned e-mail servers can be out of service for some time, and some failures must be tolerated even with good setting parameters.
FIG. 4A shows an alternative embodiment that employs an explicit list 400 of bad domains. In this embodiment the list 300 of good settings parameters is naturally devoid of bad domains.
FIG. 4B shows a further alternative embodiment that employs a list 420 of alternative setting parameters. This embodiment makes use of the fact that even if the e-mail server address(es) for a domain may not be unambiguously derivable from the domain name, a setting selected from a finite set of alternative settings usually applies. FIG. 4B shows a list 420 of alternative setting parameters for two operators. Reference numeral 422 denotes three alternative setting sets for operator—3.fi and reference numeral 424 denotes two alternative setting sets for operator—5.fi. If the user-indicated e-mail address 210 (FIG. 2) is under a domain 216 that is listed in the list 420, the alternative setting sets can be tried automatically one by one, or they can be shown to the user for selection. If the user does not find a suitable setting parameter set among the alternative settings, he/she may enter a new setting parameter set, which can be tested and added to the list 420 if the test succeeds. The list of alternative setting sets for each operator can be maintained in the order of decreasing success rate of provisioning, whereby the most likely correct setting set will be tried first.
FIG. 2 showed an embodiment in which the user name 220 was requested from the user separately from the e-mail address 210. In some e-mail systems it is possible to deduce the user name 220 from the e-mail address 210 automatically. For instance, some e-mail systems may use the user-specific part 212 of the e-mail address 210 as the user name 220, possibly after stripping of non-alphabetic characters. Accordingly, it is beneficial to maintain in the connectivity function 120 or provisioning server 126 a set of domain-specific rules for determining the user name 220 from the e-mail address 210 automatically. Such rules can be domain-specific. In other words, under a certain e-mail domain 216, the user name 220 may be deduced from the e-mail address 210 by some specific rule. In case the connectivity function 120 or provisioning server 126 does not have a specific rule for a certain domain, it may try all or some of the most generally applicable rules, such as using the user specific part 212 as the user name 220.
The set of domain-specific rules may also comprise instructions to be displayed in case of provisioning problems. For instance, the connectivity function 120 or provisioning server 126 may test e-mail provisioning with the user-supplied parameters 210, 220, 222. If the test fails, the user may be instructed to activate a premium service.
It is readily apparent to a person skilled in the art that the inventive concept can be implemented in various ways, and the above embodiments are meant to illustrate rather than restrict the invention. For example, there may be one combined server address or separate e-mail server addresses for incoming and outgoing e-mail. The server addresses are shown in DNS (domain name server) format, but they can be maintained in any applicable format, such as IP addresses. Those skilled in the art will recognize that many other modifications are possible without departing from the scope of the invention as defined in the attached claims.
US5559800 * 19 Jan 1994 24 Sep 1996 Research In Motion Limited Remote control of gateway functions in a wireless data communication network
US5785355 * 19 Nov 1996 28 Jul 1998 Kobel, Inc. Single unit phone card assembly and method of producing same
US5802312 * 27 Sep 1994 1 Sep 1998 Research In Motion Limited System for transmitting data files between computers in a wireless environment utilizing a file transfer agent executing on host system
US5898780 * 9 Oct 1996 27 Apr 1999 Gric Communications, Inc. Method and apparatus for authorizing remote internet access
US6119171 * 29 Jan 1998 12 Sep 2000 Ip Dynamics, Inc. Domain name routing
US6170014 * 18 Mar 1999 2 Jan 2001 Community Learning And Information Network Computer architecture for managing courseware in a shared use operating environment
US6535892 * 13 May 2002 18 Mar 2003 Starfish Software, Inc. System and methods for exchanging messages between a client and a server for synchronizing datasets
US6615253 * 31 Aug 1999 2 Sep 2003 Accenture Llp Efficient server side data retrieval for execution of client side applications
US6625621 * 14 Dec 2000 23 Sep 2003 Starfish Software, Inc. System and methods for a fast and scalable synchronization server
US6886030 * 17 Dec 1998 26 Apr 2005 United Video Properties, Inc. Electronic mail system employing a low bandwidth link for e-mail notifications
US6938079 * 19 Sep 2000 30 Aug 2005 3Com Corporation System and method for automatically configuring a client device
US7100821 * 13 May 2004 5 Sep 2006 Mehran Randall Rasti Charge card and debit transactions using a variable charge number
US7240095 * 22 Feb 2002 3 Jul 2007 Bellsouth Intellectual Property Corporation Electronic mail notification
US7373386 * 13 Feb 2004 13 May 2008 Research In Motion Limited System and method for configuring access to electronic mailboxes
US20010034225 * 12 Feb 2001 25 Oct 2001 Ash Gupte One-touch method and system for providing email to a wireless communication device
US20020099809 * 16 May 2001 25 Jul 2002 Lycos Korea, Inc. Method for providing integrated user management environment to multi-internet service and system for the same
US20030084165 * 10 Oct 2002 1 May 2003 Openwave Systems Inc. User-centric session management for client-server interaction using multiple applications and devices
US20040073476 * 24 Mar 2003 15 Apr 2004 Prolink Services Llc Method and system for identifying key opinion leaders
US20040073651 * 7 Oct 2003 15 Apr 2004 International Business Machines Corporation Secure system and method for providing a robust radius accounting server
US20040082346 * 29 May 2003 29 Apr 2004 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced-service provision
US20040128375 * 16 Oct 2003 1 Jul 2004 Xerox Corporation. Integrated server platform for the autonomous provisioning of device services
US20040133626 * 17 Dec 2003 8 Jul 2004 International Business Machines Corporation Selecting a preferred server from groups of servers based on geographical information obtained from the requesting client
US20040167966 * 18 Feb 2004 26 Aug 2004 Simon Lee Method and system for directing communications in a communications network
US20050055578 * 21 Jul 2004 10 Mar 2005 Michael Wright Administration of protection of data accessible by a mobile device
US20050073982 * 7 Oct 2003 7 Apr 2005 Accenture Global Services Gmbh. Connector gateway
US20050094625 * 29 Jul 2004 5 May 2005 Hewlett-Packard Development Company, L.P. Communications
US20060165226 * 19 Dec 2003 27 Jul 2006 Matthias Ernst Automatic, connection-based terminal or user authentication in communication networks
US20060168043 * 10 Jan 2005 27 Jul 2006 George Eisenberger Systems with message integration for data exchange, collection, monitoring and/or alerting and related methods and computer program products
US20060190984 * 23 Sep 2002 24 Aug 2006 Credant Technologies, Inc. Gatekeeper architecture/features to support security policy maintenance and distribution
US20060242320 * 21 Apr 2005 26 Oct 2006 Paul Nettle Method and apparatus for polling
US20070118620 * 18 Jan 2007 24 May 2007 Brian Cartmell Registering and using multilingual domain names
US20110138402 * 5 Jul 2010 9 Jun 2011 Michael Fleming Cross-Platform Event Engine
US7756937 * 14 Aug 2007 13 Jul 2010 Brother Kogyo Kabushiki Kaisha Network device
US8386570 17 Aug 2007 26 Feb 2013 Brother Kogyo Kabushiki Kaisha Electronic mail communication device
US20080046521 * 14 Aug 2007 21 Feb 2008 Brother Kogyo Kabushiki Kaisha Network device
US20080046523 * 17 Aug 2007 21 Feb 2008 Brother Kogyo Kabushiki Kaisha Electronic mail communication device
International Classification H04L, G06F15/16
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BACKHOLM, ARI;SALORINNE, SEPPO;HEINONEN, JUSSI;AND OTHERS;REEL/FRAME:017869/0426;SIGNING DATES FROM 20060606 TO 20060612
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BACKHOLM, ARI;SALORINNE, SEPPO;HEINONEN, JUSSI;AND OTHERS;SIGNING DATES FROM 20060606 TO 20060612;REEL/FRAME:017869/0426
5 Aug 2009 AS Assignment
27 Jun 2015 AS Assignment
14 Aug 2015 FPAY Fee payment
22 Mar 2016 SULP Surcharge for late payment