As the use of mobile devices such as cellular phones, personal digital assistants (PDAs), portable computing devices, and mobile e-mail devices has expanded, the desire of users to utilize the devices to access e-mail systems has also increased. Unfortunately, connecting any mobile device to an e-mail system is not an easy task that may be completed without specialized knowledge. In particular, connecting to an enterprise e-mail system may require the assistance and support of members of an information technology (IT) department to either offer technical assistance or to implement the requested change. For the average non-technical user, finding the appropriate person to contact in the IT department, asking the right questions about the desired service that the user would like implemented, and providing the right information to the IT staff can be a very daunting task that is fraught with the possibility of error. Even if the correct person is identified in the IT department, one or more conversations may be required before the desired functionality is implemented. Moreover, because of the level of interaction that may be required, it is often beneficial to only request such a change when at the enterprise office. Implementing such a change remotely, such as when using the mobile device, only adds to the complexity of the operation. From an end-user perspective, it would therefore be beneficial for a simpler method and system to be developed to enable a user to add e-mail connectivity to a mobile device with a minimum amount of effort.
A software and/or hardware facility is described that allows users to enable e-mail on a mobile device in an automated fashion and with a minimal amount of technical support interaction. Using a mobile device, a user is allowed to select an e-mail service that they desire to access from the mobile device. An e-mail system administrator (“sysadmin”) may be associated with the desired e-mail service. An access request is made from the mobile device to a configuration management server. The configuration management server sends an e-mail, SMS message, or other message to the user or the system administrator with the access request. The user or system administrator is presented with a form that allows the user or sysadmin to quickly provide sufficient information to enable e-mail service for the mobile device. The received information is used to automatically configure the e-mail of the mobile device, and the user is alerted when the service is ready for use. The configuration management server may store the information received from the user or sysadmin in a database so that the information can be re-used by other mobile device users with the same e-mail domain. Storing the information minimizes the amount of input needed from other users requesting access to or system administrators managing access to the e-mail domain in the future.
Various embodiments of the facility will now be described. The following description provides specific details for a thorough understanding and enabling description of these embodiments. One skilled in the art will understand, however, that the facility may be practiced without many of these details. Additionally, some well-known structures or functions may not be shown or described in detail so as to avoid unnecessarily obscuring the relevant description of the various embodiments. The terminology used in the description presented below is intended to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific embodiments of the invention. While certain terms may be emphasized below, any terminology intended to be interpreted in a restricted manner will be overtly and specifically defined as such in this Detailed Description section.
Referring back to
Referring back to
A representative form 525 is depicted in
Returning to
Returning to
If the user requests access to an e-mail system other than an enterprise system at decision block 215, the processing continues to a block 270. At block 270 the facility prompts the user to enter the user's e-mail account information, such as an e-mail address, password, e-mail server information, and other characteristics necessary to access the requested e-mail service. At block 280, the user may optionally be prompted to enter any account settings for the requested service, such as “remember password,” “leave on server” (for POP3), etc. Processing then continues to block 250.
It will be appreciated that in certain circumstances, multiple sets of configuration information may be stored in the database in association with a single domain. For example, large enterprises or corporations may have multiple email servers, each with different configuration information for the domain used by the enterprise or corporation. If multiple sets of configuration information are stored in the database in association with a single domain, the facility may sequentially try each set of configuration information until a set is found that enables e-mail on the requesting mobile device. Alternatively, the facility may send a message to a user or a system administrator that provides the different sets of configuration information and requests the user or the system administrator to select which set of configuration information to use when enabling e-mail for the mobile device.
In general, the detailed description of embodiments of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific embodiments of, and examples for, the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention. For example, while processes are presented in a given order, alternative embodiments may perform routines having steps in a different order, and some steps may be deleted, moved, added, subdivided, combined, and/or modified. Each of these processes may be implemented in a variety of different ways. Also, while processes are at times shown as being performed in series, these processes may instead be performed in parallel, or may be performed at different times.
Aspects of the invention may be stored or distributed on computer-readable media, including magnetically or optically readable computer discs, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, biological memory, or other data storage media. Indeed, computer implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Internet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or they may be provided on any analog or digital network (packet switched, circuit switched, or other scheme). Those skilled in the relevant art will recognize that portions of the invention reside on a server computer, while corresponding portions reside on a client computer such as a mobile or portable device, and thus, while certain hardware platforms are described herein, aspects of the invention are equally applicable to nodes on a network.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain embodiments of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated.
From the foregoing, it will be appreciated that specific embodiments of the invention have been described herein for purposes of illustration, but that various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims.
This application is a U.S. National Phase Application of International Application Serial No. PCT/US08/50814, filed Jan. 10, 2008, which claims priority to, and incorporates by reference in its entirety, U.S. Provisional. Application No. 60/884,395, filed on Jan. 10, 2007.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2008/050814 | 1/10/2008 | WO | 00 | 2/19/2010 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2008/086504 | 7/17/2008 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
7113803 | Dehlin | Sep 2006 | B2 |
7317699 | Godfrey et al. | Jan 2008 | B2 |
7353016 | Roundtree et al. | Apr 2008 | B2 |
7475115 | Gardner et al. | Jan 2009 | B2 |
7580367 | Bleckert et al. | Aug 2009 | B2 |
20020078185 | Swerup et al. | Jun 2002 | A1 |
20040002943 | Merrill et al. | Jan 2004 | A1 |
20040137919 | Biundo | Jul 2004 | A1 |
20050141438 | Quetglas et al. | Jun 2005 | A1 |
20050260996 | Groenendaal | Nov 2005 | A1 |
20060036494 | Aufricht et al. | Feb 2006 | A1 |
20060190530 | Gruneberg et al. | Aug 2006 | A1 |
20060195557 | Dew et al. | Aug 2006 | A1 |
20060230433 | Chang | Oct 2006 | A1 |
20080016187 | Neil et al. | Jan 2008 | A1 |
20080119136 | Khazi | May 2008 | A1 |
Number | Date | Country |
---|---|---|
WO-2005081852 | Sep 2005 | WO |
WO-2005083996 | Sep 2005 | WO |
WO-2006034399 | Mar 2006 | WO |
WO-2007002499 | Jan 2007 | WO |
WO-2008022291 | Feb 2008 | WO |
WO-2008086504 | Jul 2008 | WO |
Entry |
---|
U.S. Appl. No. 12/446,221, filed Jan. 6, 2010, Roundtree. |
International Search Report and Written Opinion for International Application No. PCT/US08/50814, Mail Date Jul. 11, 2008, 10 pages. |
Lin, et al., “An introduction to OMA Device Management,” <http://www.ibm.com/developerworks/library/wi-oma/index.html>, internet accessed on Feb. 10, 2010, 11 pages. |
MSDN, “OMA DM version 1.1.2 Architecture,” <http://msdn.microsoft.com/en-us/library/bb737307(printer).aspx>, internet accessed on Feb. 10, 2010, 3 pages. |
MSDN, “OMA DM Standards and Extensions,” <http://msdn.microsoft.com/en-us/library/bb737228(printer).aspx>, internet accessed on Feb. 10, 2010, 7 pages. |
Open Mobile Alliance Ltd., “OMA Device Management Notification Initiated Session, OMA-TS-DM—Notification-V1—2—1-20080617-A,” Jun. 17, 2008, 16 pages. |
Number | Date | Country | |
---|---|---|---|
20100169443 A1 | Jul 2010 | US |
Number | Date | Country | |
---|---|---|---|
60884395 | Jan 2007 | US |