WO2007111596A1 - Système et méthode pour assurer la migration des données d'un compte utilisateur - Google Patents

Système et méthode pour assurer la migration des données d'un compte utilisateur Download PDF

Info

Publication number
WO2007111596A1
WO2007111596A1 PCT/US2006/011117 US2006011117W WO2007111596A1 WO 2007111596 A1 WO2007111596 A1 WO 2007111596A1 US 2006011117 W US2006011117 W US 2006011117W WO 2007111596 A1 WO2007111596 A1 WO 2007111596A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
new
mailbox
electronic mail
account data
Prior art date
Application number
PCT/US2006/011117
Other languages
English (en)
Inventor
Sarinder Virk
Ian Pedersen
Original Assignee
Teamon Systems, Inc.
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 Teamon Systems, Inc. filed Critical Teamon Systems, Inc.
Priority to EP06739735A priority Critical patent/EP1999914A1/fr
Priority to PCT/US2006/011117 priority patent/WO2007111596A1/fr
Priority to CA002638460A priority patent/CA2638460C/fr
Publication of WO2007111596A1 publication Critical patent/WO2007111596A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication

Definitions

  • the present invention relates to the field of communications systems, and, more particularly, to electronic mail (email) communications systems and related methods.
  • Electronic mail has become an integral part of business and personal communications. As such, many users have multiple email accounts for work and home use. Moreover, with the increased availability of mobile cellular and wireless local area network (LAN) devices that can send and receive emails, many users wirelessly access emails from mailboxes stored on different email storage servers (e.g., corporate email storage server, Yahoo, Hotmail, AOL, etc. ) .
  • email storage servers e.g., corporate email storage server, Yahoo, Hotmail, AOL, etc.
  • This system pushes user-selected data items from a host system to a user' s mobile wireless communications device upon detecting the occurrence of one or more user-defined event triggers.
  • the user may then move (or file) the data items to a particular folder within a folder hierarchy stored in the mobile wireless communications device, or may execute some other system operation on a data item.
  • Software operating at the device and the host system then synchronizes the folder hierarchy of the device with a folder hierarchy of the host system, and any actions executed on the data items at the device are then automatically replicated on the same data items stored at the host system, thus eliminating the need for the user to manually replicate actions at the host system that have been executed at the mobile wireless communications device.
  • the foregoing system advantageously provides great convenience to users of wireless email communication devices for organizing and managing their email messages. Yet, further convenience and efficiency features may be desired in email distribution and synchronization systems as email usage continues to grow in popularity.
  • An email push system often requires some mass migration from a web client system having an email service to a more sophisticated internet service, but it is not always desirable to allow a mass migration of data from one system to the new electronic mail system operative as an upgraded system because data often is not synchronized in a mass migration. Inconsistencies could remain between the new data and old data, in which a huge amount of data may be provided from different providers, creating inconsistencies.
  • the older email service as a web client could indicate that a Personal Identification Number (PIN) belongs to a portable wireless communications device in which the new email service does not have a record, even after migration.
  • PIN Personal Identification Number
  • FIG. 1 is schematic block diagram of a direct access electronic mail (email) distribution and synchronization system.
  • FIG. 2 is a schematic block diagram of an exemplary embodiment of user interface components of the direct access proxy of the system of FIG. 1.
  • FIG. 3 is a schematic block diagram of an exemplary embodiment of the Web client engine of the system of FIG. 1.
  • FIGS. 4 is a schematic block diagram of an exemplary embodiment of the mobile office platform engine machine for use in the system of FIG. 1.
  • FIG. 5 is a schematic block diagram of an exemplary embodiment of the database module of the system of FIG. 1.
  • FIG. 6 is a schematic block diagram of another embodiment of user interface components of the direct access proxy similar to that shown in FIG. 2.
  • FIG. 7 is a sequence diagram for the migration in accordance with one non-limiting embodiment .
  • FIG. 8 is a schematic block diagram illustrating an exemplary mobile wireless communications device that can be used with the Direct Access system shown in FIG. 1.
  • a system migrates user account data from an integrated electronic mailbox to a new electronic mail service.
  • An electronic mail (email) server is operative as a web client and has an integrated electronic mailbox of a user and user account data.
  • a mobile office platform is operative with the email server and has at least one stored procedure call for pulling user account data from the email server into a new electronic mail service at the mobile office platform.
  • the mobile office platform can be operative for querying a user of the integrated electronic mailbox whether the user desires to migrate the user account data into the new electronic mail service.
  • the mobile office platform is also operative for querying a user to accept new terms and conditions of the new electronic mail service in order to log-in to a user interface using HTTP or WAP.
  • This email server could include a simple object access protocol (SOAP) interface to pull the user account data from the integrated electronic mailbox.
  • SOAP simple object access protocol
  • the mobile office platform also includes a SOAP interface operative for creating a new, integrated electronic mailbox account of the new electronic mail service.
  • the system can include a mobile wireless communications device having a subscriber account associated therewith.
  • the electronic mail (email) server is operative as a web client and has an integrated electronic mailbox for the subscriber account of the user and contains user account data.
  • the mobile office platform is operative with the email server and has at least one stored procedure call for pulling the user account data from the email server into a new electronic mail service at the mobile office platform and is operative with the mobile wireless communications device as a new subscriber account.
  • a direct access (DA) email distribution and synchronization system 20 allows direct access to different mail sources, allowing messages to be transferred directly to a mobile wireless handheld device from a source mailbox.
  • DA direct access
  • synchronization system 20 allows direct access to different mail sources, allowing messages to be transferred directly to a mobile wireless handheld device from a source mailbox.
  • different mail stores need not be used for integrated external source mail accounts, and a permanent copy of an email in a local email store is not required.
  • this diagram depicts objects as functionally separate, such depiction is merely for illustrative purposes. It will be apparent to those skilled in the art that the objects portrayed in this figure can be arbitrarily combined or divided into separate software, firmware or hardware components. Furthermore, it will also be apparent to those skilled in the art that such objects, regardless of how they are combined or divided, can execute on the same computing device or can be arbitrarily distributed among different computing devices connected by one or more networks.
  • the direct access system 20 enables email users or subscribers to have email from third party email services pushed to various mobile wireless communications devices 25. Users need not create a handheld email account to gain direct access to an existing external email account.
  • the direct access system 20 may operate without performing aggregation as used in some prior- art systems, in which emails are aggregated from multiple different source mailboxes to a single target mailbox. In other words, email need not be stored in an intermediate target mailbox, but instead may advantageously be accessed directly from a source mail store.
  • the direct access system 20 illustratively includes a Web client (WC) engine 22 and a mobile office platform (MOP) 24. These Web client engine 22 and mobile office platform 24 operate together to provide users with direct access to their email from mobile wireless communications devices 25 via one or more wireless communications networks 27, for example. Both the Web client engine 22 and the mobile office platform 24 may be located at the same location or at separate locations, and implemented in one or more servers.
  • the web client engine 22 illustratively includes a port agent 30 for communicating with the wireless communications devices 25 via the wireless communications network (s) 27, a worker 32, a supervisor 34, and an attachment server 36, which will be discussed further below.
  • An alert server 38 is shown in dashed lines, and in one preferred embodiment, is not used, but could be part of the system in yet other embodiments .
  • the mobile office platform 24 illustratively includes a DA proxy 40, and a proxy application programming interface (API) 42 and a cache 44 cooperating with the DA proxy.
  • the mobile office platform 24 also illustratively includes a load balance and cache (LBAC) module 46, an event server 48, a universal proxy (UP) Servlet 54, an AggCron module 56, a mobile office platform (MOP) engine 58, and a database (DB) engine 60, which will be discussed in further detail below.
  • LBAC load balance and cache
  • UP universal proxy
  • MOP mobile office platform
  • DB database
  • Least Recently Used (LRU) cache 41 caches new messages, and can release messages and objects that were least recently used.
  • the supervisor 34 processes new mail notifications that it receives from the direct access proxy 40.
  • UDP User Datagram Protocol
  • heartbeat is a tool that monitors the state of the server.
  • the supervisor 34 will receive a new service book request from the direct access proxy 40 to send service books to the mobile wireless communication device for new or changed accounts.
  • a service book can be a class that could contain all service records currently defined. This class can be used to maintain a collection of information about the device, such as connection information or services, such as an email address of the account.
  • the worker 32 is an intermediary processing agent between the supervisor 34 and the port agent 30, and responsible for most processing in the Web client engine 22. It will retrieve e-mail from a universal proxy 54, via a direct access proxy, and format e-mail in Compressed Multipurpose Internet Mail Extension (CMIME) as a type of Multipurpose Internet Mail Extension, and send it to the port agent 30, for further processing. Its responsibilities include the following tasks: (1) messages sent to and received from the handheld; (2) message reply, forward and more requests; (3) Over The Air Folder Management operation (OTAFM); (4) attachment viewing; and (5) service book.
  • CMIME Compressed Multipurpose Internet Mail Extension
  • OTAFM Over The Air Folder Management operation
  • the port agent 30 acts as a transport layer between the infrastructure and the rest of the Web client engine 22. It is responsible for delivering packets to and from the mobile wireless communications device.
  • a port agent 30 can include one Server Relay Protocol (SRP) connection to a relay, but it can also handle multiple SRP connections, and each connection may have a unique Globally Unique Identifier (GUID) associated with a service book.
  • SRP Server Relay Protocol
  • GUID Globally Unique Identifier
  • the attachment server 36 provides service for document/attachment conversion requests from workers 32.
  • the direct access proxy 40 provides a Web- based Distributed Authoring and Versioning (WebDAV) interface that is used by the worker 32 to access account and mailbox information. This provides functionality to create, change and move documents on a remote server, e.g., a Web server.
  • WebDAV Distributed Authoring and Versioning
  • the direct access proxy 40 typically will present an asynchronous interface to its clients.
  • the LBAC module 46 is used by a notification server and the Web client engine 22 components to locate the proper DA proxy for the handling of a request.
  • the universal proxy Servlet 54 abstracts access to disparate mail stores into a common protocol.
  • the event server 48 responds to notifications of new messages from corporate servers 52 and/or mail service providers 50, which may be received via the Internet 40, for example.
  • the notifications are communicated to the direct access proxy 40 by the AggCron module 56 and the event server 48 so that it may initiate checking for new mail on source mailboxes 51, 53 of the mail service providers 50 and/or corporate servers 52.
  • the proxy API can be a Simple Object Access Protocol (SOAP) Daemon 42 and is the primary interface into a database 60, which is the primary data store for the mobile office platform 24.
  • SOAP Simple Object Access Protocol
  • the AggCron module 56 may also periodically initiate polling for new messages as well.
  • FIG. 2 is a high-level block diagram showing user interface components of the direct access proxy 40. More particularly, the direct access proxy 40 illustratively includes an identifier module 72 with various downstream proxy modules for different communication formats, such as a Wireless Application Protocol (WAP) proxy module 74 and a Hypertext Markup Language (HTML) proxy module 76.
  • WAP Wireless Application Protocol
  • HTTP Hypertext Markup Language
  • the identifier module 72 provides a centralized authentication service for the direct access system 20 and other services.
  • An authentication handshake may be provided between an ID service and direct access system 20 to ensure that users have the proper credentials before they are allowed access to the direct access system 20.
  • the ability to switch from managing a Web client to a direct access system, or vice versa, may occur without requiring the user to re-enter any login credentials. Any Web client and direct access may share session management information on behalf of a user.
  • the WAP proxy 74 provides a wireless markup language (WML) -based user interface for configuring source mailboxes with the mobile office platform 24.
  • the HTML proxy 76 provides an HTML-based user interface for configuring of source mailboxes in the MOP 24.
  • the proxy API 42 (SOAP Daemon) is the primary interface into the database 60.
  • the engine 58 is a protocol translator that connects to a source mailbox to validate configuration parameters.
  • the database 60 is the primary user data store for the mobile office platform 24.
  • FIGS. 3, 4 and 5 illustrate respective Web client engine machines 80 (FIG. 3), an engine machine 82 (FIG. 4), and database machine 84 (FIG. 5).
  • the Web client engine machine 80 illustratively includes the supervisors 34, workers 36, and port agents 38. Relays 86 cooperate with the port agents 38 using a GUID.
  • the engine machine 82 illustratively includes a direct access proxy 40, HTML proxy 76, WAP proxy 74, PDS module 88, UP Servlet 54, LBAC module 46, a sendmail module 90, an secure mail client (SMC) server 92, a secure sockets layer (SSL) proxy 94, an aggregation engine 96, and event server 48.
  • SMC secure mail client
  • SSL secure sockets layer
  • the SMC server 92 cooperates with corresponding SMC modules resident on certain corporate networks, for example, to convey email data between the mobile office platform 24 and source mailboxes.
  • the database machine 84 may include an aggregation application programming interface (API) 100 as a SOAP Daemon, an administration console 102, an aggregation database 104, the AggCron module 56, an SMC directory server 106, and a send mail module 90.
  • API application programming interface
  • the various components of the Web client engine 22 may be configured to run on different machines or servers.
  • the component binaries and configuration files may either be placed in a directory on the network or placed on a local disk that can be accessed to allow the appropriate components to run from each machine.
  • deployment may include one supervisor, two workers, and one port agent for supporting 30,000 external source mailboxes, although other configurations may also be used. Actual production deployment may depend on the results of load, performance and stress testing, as will be appreciated by those skilled in the art.
  • machines are typically installed in two configurations, namely engine machines (FIG. 4) and database machines (FIG. 5) . While these machines may have all of the above-described components installed on them, not all of these components need be active in all applications (e.g., aggregation may be used with systems that do not support push technology, etc.). Once again, actual production deployment may depend on the results of load, performance and stress testing.
  • the mobile office platform 24 architecture in one known technique advantageously uses a set of device/language-specific extensible Stylesheet Language (XSL) files, which transform application data into presentation information.
  • XSL device/language-specific extensible Stylesheet Language
  • a build process takes a non-localized XSL and generates a localized XSL for each supported language. When the XSL is used, it is "compiled" in memory and cached for repeated use. The purpose of pre-localizing and caching the templates is to reduce the CPU cycles required to generate a presentation page.
  • Branding may also be performed. Initially, a localized XSL may build a WAP application to access aggregated email accounts. A WAP proxy application may be localizable and support multiple WAP devices.
  • a device-specific XSL may be created, which may be localized for each language/country supported.
  • This rendering scheme may support not only WAP devices, but also SMTP, HTML and POP proxies, for example.
  • SMTP Simple Object Transfer Protocol
  • HTML HyperText Markup Language
  • POP proxies for example.
  • each page of a given application may be customized for each different brand.
  • the branding of a page may be accomplished through XSL imports, including the use of a Java application programming interface (API) for XML processing (JAXP) feature to resolve the imports dynamically.
  • API Java application programming interface
  • JavaXP XML processing
  • first and second pages for a single language/country may be combined with branded counterparts to generate a plurality of distinct template combinations. It is also possible to profile memory requirements of an application by loading templates for a single language, device/application and brand.
  • An HTML device may include a set of templates that are large compared to other devices.
  • the mobile office platform 24 advantageously builds processes and takes non-localized files and language-specific property files and combines them to make each non-localized XSL into an XSL for each supported language.
  • a separate XSL for each language need not be used, and the language factor may be removed from the memory usage equation.
  • a JAXP API may be used to extend XSL with Java classes. The extensions may take various forms, for example, including extension elements and extension functions.
  • a template may be transformed by creating and initializing an extension object with a locale and passing an object to a transformer. The system can remove multiple imports and use less memory. HTML templates can use template importing to enable template reuse, much like Java classes, and reuse other Java classes through a mechanism like derivation or importing.
  • users receive email on their mobile wireless communications devices 25 from multiple external accounts, and when replying to a received message, the reply-to and sent-from address integrity is preserved. For example, for a user that has an integrated Yahoo! account (user@yahoo.com) and a P0P3 account (user@pop3.com), if they receive an email at user@yahoo.com, their replies generated from the device 25 will appear to come from user@yahoo.com. Similarly, if a user receives an email at user@pop3.com, their replies will appear to come from user@pop3.com.
  • Selection of the "sent from” address is also available to a user that composes new messages.
  • the user will have the ability to select the "sent from” address when composing a new message.
  • the message may also be sent through the source mail service. This functionality can be supported by sending a configuration for each source mailbox, for example, as a non-limiting example, a service book for each source mailbox 51, 53 to the mobile wireless communications device 25.
  • a service book is a class that may include all service records currently defined. This class may be used to maintain a collection of information about the device, such as connection information.
  • the service book may be used to manage HTTP connections and mail (CMIME) information such as account and hierachy.
  • CMIME HTTP connections and mail
  • a delete service book request may be sent when a source mailbox 51, 53 is removed from the account.
  • the service book may also be resent to the device 25 with a viewable name that gives the user some indication that the selection is no longer valid.
  • a sent items folder may also be "synchronized.” Any device-originated sent messages may be propagated to a source account and stored in a sent mail folder, for example. Also, messages deleted on the device 25 may correspondingly be deleted from the source mailbox 51, 53. Another example is that device-originated marking of a message as read or unread on the device 25 may similarly be propagated to the source mailbox 51, 53. While the foregoing features are described as source-dependent and synchronizing one-way, in some embodiments certain synchronization features may in addition, or instead, propagate from the source mailbox/account to the handheld device, as will be appreciated by those skilled in the art.
  • the mail service provider or corporate mail server may be used for submission of outgoing messages. While this may not be possible for all mail service providers or servers, it is preferrably used when available as it may provide several advantages. For example, subscribers to AOL will get the benefit of AOL-specific features like parental controls. Furthermore, AOL and Yahoo users, as non-limiting examples, will see messages in their sent items folder, and messages routed in this manner may be more compliant with new spam policies such as Sender Policy Framework (SPF) and Sender Id. In addition, messages sent via corporate mail servers 52 will have proper name resolution both at the global address list level and the personal level. It should be understood, however, that the use of the mail service provider 50 to deliver mail may be dependant on partner agreements and/or protocol, depending upon the given implementation.
  • SPF Sender Policy Framework
  • Sender Id Sender Policy Framework
  • messages sent via corporate mail servers 52 will have proper name resolution both at the global address list level and the personal level. It should be understood, however, that the use of the mail service provider 50 to deliver mail may be dependant
  • the architecture described above also advantageously allows for features such as on-demand retrieval of message bodies and attachments and multiple folder support. Morever, a ⁇ N this-is-spam" button or indicator may be used allowing company labels and other service provider-specific features when supported by an underlying protocol, as will be appreciated by those skilled in the art.
  • One particular advantage of the direct access system 20 is that a user need not configure an account before integrating additional accounts. However, a standalone email address may be used, and this address advantageously need not be tied to a mailbox size which the subscriber is required to manage. For example, the email account may be managed by an administrator, and any mail could be purged from the system after a predetermined period of time (i.e., time-based auto-aging with no mailbox limit for all users) .
  • any integrated email account creation, settings and options may advantageously be available to the user from their mobile wireless communications device 25.
  • users need not visit an HTML site and change a setting, create a filter, or perform similar functions, for example.
  • an HTML site may optionally be used.
  • the Web client engine 22 may advantageously support different features including message to handheld (MTH) , message from handheld (MFH) , forward/reply a message, request to view more for a large message (e.g., larger than 2K) , request viewing message attachment, and over the air folder management (OTAFM) . These functions are explained below.
  • MTH message to handheld
  • MH message from handheld
  • OTAFM air folder management
  • each email account integrated for a user is linked with the user device through a Web client service book.
  • a notification that contains the new message information will typically be sent to a Web client engine supervisor component (FIG. 3), which in turn will assign the job to an available worker with the least load in the system.
  • the chosen worker 32 will validate the user information and retrieve the new message from the user source mailbox and deliver it to the user device.
  • MFH messages associated with a Web client service book are processed by the Web client engine 22 and delivered to the Internet 49 by the worker 32 via the simple mail transfer protocol (SMTP) or native outbox. If a user turns on the option to save the sent message to the sent items folder, the direct access proxy will save a copy of the sent message to this folder.
  • SMTP simple mail transfer protocol
  • the user can forward or reply an MTH or MFH message from the mobile wireless communications device 25 as long as the original message still existed in the direct access proxy cache or in user mailbox.
  • the worker 32 may send the first 2K, for example, or the whole message (whatever is less) to the user device. If the message is larger than 2K, the user can request MORE to view the next 2K of the message. In this case, the worker 32 will process the More request by retrieving the original message from the user source mailbox, and send back the 2K that the device requests. Of course, in some embodiments more than 2K of message text (or the entire message) may be sent.
  • a user can view a message attachment of a popular document format (e.g., MS Word, MS Power Point, MS Excel, Word Perfect, PDF, text, etc.) or image format (GIF, JPEG, etc).
  • a popular document format e.g., MS Word, MS Power Point, MS Excel, Word Perfect, PDF, text, etc.
  • image format GIF, JPEG, etc.
  • the worker 32 places a copy of each MFH message sent from the user device in the user sent items folder in the mailbox.
  • the Web client OTAFM service maintains any messages and folders in the user mailbox synchronized with the user device over the air.
  • the associated message on the device may also be Moved/Deleted accordingly, and vice-versa.
  • the associated message in the user Web client mailbox may also be Moved/Deleted accordingly.
  • the system 20 may advantageously support different subsets of various messaging features.
  • the mobile office platform 24 may be responsible for connecting to the various source mailboxes 51, 53 to detect new emails.
  • a notification is sent to the Web client engine 22 and, based on this notification, the supervisor 34 chooses one of the workers 32 to process that email. The chosen worker will fetch additional account information and the contents of the mail message from the direct access proxy 40 and deliver it to the user device 25.
  • the MFH could be given to the direct access proxy 40 from the Web client worker 32.
  • the mobile office platform 24 delivers a message to the Internet 49 by sending through a native outbox or sending it via SMTP. It should be understood, however, that the native outbox, whenever possible, may provide a better user experience, especially when taking into account current anti-spam initiatives such as SPF and sender Id.
  • the Web client engine 22 In a message deleted from handheld function, when a message is deleted from the device 25, the Web client engine 22 notifies the mobile office platform 24 via the direct access proxy 40. As such, the mobile office platform 24 can delete the same message on the source mailbox.
  • the Web client worker 32 may request an original mail from the direct access proxy 40. It will then process the request and send the results to the mobile wireless communications device 25.
  • the architecture may additionally support on-demand retrieval of message parts and other upgrades, for example.
  • each source mailbox 51, 53 may be associated with a unique service record. In this way, each MFH message is linked with a source mailbox 51, 53 based on the service record on the device.
  • the system 20 may also poll the integrated external mailboxes periodically to check for new mail and to access any messages.
  • the system 20 may further incorporate optimizations for polling bandwidth from an aggregation component allowing a quick poll.
  • the system 20 can also advantageously support a large active user base and incorporate a rapidly growing user base.
  • the topology of load balancing can be based on the size of a component's queue and its throughput. These load statistics can be monitored by a mechanism in one example called the UDP Heartbeat, as described before. If a component is overloaded or has a large queue size, the component will have less chance to get an assigned job from other components. In contrast, a component will get more assigned jobs if it completes more jobs in the last few hours than other components.
  • General load balancing for any mobile office platform components can be accomplished through the use of a load balancer module, for example, a BIG-IP module produced by F5 Networks of Seattle, Washington.
  • BIG-IP can provide load balancing and intelligent layer 7 switching, and can handle traffic routing from the Internet to any customer interfacing components such as the WAP and HTML proxies.
  • the use of a BIG-IP or similar module may provide the application with pooling capabilities, fault tolerance and session management, as will be appreciated by those skilled in the art.
  • LBAC 46 may support this function.
  • the LBAC 46 is a system-wide component that can perform two important functions. The first of these function is that it provides a mapping from the device PIN to a particular direct access proxy 40, while caching the information in memory for both fast access and to save load on the central database. Secondly, as the direct access proxy 40 will be run in clustered partitions, the LBAC 46 may distribute the load across all direct access proxies within any partition.
  • the LBAC 46 can be formed of different components.
  • the code which performs the load balancing can be an extended version of a secure mail connector.
  • the code can also perform lookups to the central database and cache the results (LBAC) .
  • LBAC results
  • a worker when a worker requires that a direct access proxy 40 perform work, it provides the LBAC 46 with a device PIN.
  • the LBAC 46 will discover which partition that PIN is associated with by looking in its cache, or retrieving the partition identifier from a central database (and caching the result) . Once the partition is known, the LBAC 46 then consults its cache to see which direct access proxy in that partition has been designated to handle requests for that PIN.
  • the secure mail connector 88 may run in failover pairs, where one is an active master and the other is a secondary standby. Internal data structures may be replicated in real-time from the master to the standby. Multiple LBACs 46 can be run for scalability and fault tolerance, but typically would require an external connection balancing component, such as the BIG-IP component as explained before.
  • a receiving component in the Web client engine 22 saves the job that has been assigned to it from other components to a job store on the disk before processing. It can update the status of the job and remove the job from the job store when the job processing is completed. In case of component failure or if the process is restarted, it can recover the jobs from the job store and, based on the current statuses of these jobs, continue processing these jobs to the next state, saving the time to reprocess them from the beginning.
  • Any recovery from the standpoint of MTH/MFH can be achieved through current polling behavior and on the Web client engine 22 recovery mechanisms. From within the mail office platform components, until a message has been successfully delivered to a Web client engine 22, that message is not recorded in the partition database 60. During the next polling interval, the system can again "discover" the message and attempt to notify the Web client engine 22. For new mail events, if an event is lost, the system can pick up that message upon receiving the next event or during the next polling interval. For sources supporting notifications, this interval could be set at six hours, as one non-limiting example. For messages sent from the Web client engine 22, and for messages that have been accepted by the Web client engine, recovery can be handled by different Web client engine components .
  • the Web client engine 22 may advantageously be horizontally and vertically scalable.
  • Multiple supervisors 34 can be registered/configured with direct access proxies 40 to provide the distribution of the notification load and the availability of engine service.
  • Multiple workers 32 and port agents 30 can run on the same machine or across multiple machines to distribute load and achieve redundancy. As the number of users grows, new components can be added to the system to achieve high horizontal scalability.
  • Each component within the mobile office platform 24 can be deployed multiple times to achieve horizontal scalability. To achieve vertical scalability, each mobile office platform 24 component can be a multithreaded process with a configurable number of threads to scale under heavy load. Pools of connections can be used to reduce the overhead of maintaining too many open connections.
  • FIG. 6 is another embodiment of the high level architectural diagram of the BDA user interface components similar to the functional components shown in the diagram of FIG. 2. There will now follow a brief description of these basic components and their function.
  • Provisioning (PRV) 110 provides a centralized database 111 or store to access user and device Identifier (ID) profile information.
  • ID user and device Identifier
  • the WAP and HTML Proxies 74, 76 retrieve the ID profile, which provides user and device information. Proxies update PRV 110 for certain user configuration actions, such as a changed PIN.
  • the web client database 112 (WC DB) contains account information for web client users. It is queried during login to determine if an unknown user is a web client user and whether they can be migrated.
  • the WAP Proxy 74 provides a Wireless Markup Language (WML) based user interface for configuration of source mailboxes in the Mobile Office Platform (MOP) .
  • WML Wireless Markup Language
  • the HTML Proxy 74 provides an HTML based user interface for configuration of source mailboxes in MOP.
  • the Soap Servlet 114 (SOAP Daemon) provides an interface into a database store.
  • the Agg Engine 116 acts as a protocol translator that connects to a source mailbox to validate configuration parameters.
  • the Mobile Office Platform Database (MOP DB) 118 is a primary user data store for the MOP.
  • the Web Admin 120 provides the MOP with notifications of account state changes. Provisioning 110 also provides notification of account state changes, such as inactive and active.
  • Provisioning can be used to notify and migrate a user from a Web Client (WC) service to an Internet Service (IS) , having more advance features that are accessible from a web browser with a user email account, allowing a user to add and edit email accounts.
  • the Web Client Aggregation Programming Interface (WC AggAPI) 122 includes a database 124 and provides integrated source data for WC accounts. It is queried to retrieve integrated source configuration data to be migrated to a new Internet Service (IS) account for the user.
  • the WC DB 112 provides web client account information. It is queried to retrieve web client account configuration data to be migrated to a Internet Service account for the user.
  • the system can make use of existing products such as the Provisioning 110 and WebAdmin 120. These products have scaling characteristics.
  • functionality has moved from Aggcron to the BDA proxy.
  • the system provides a direct connection to a partition database within the BDA proxy. Access to the database can be from a configurable connection pool that will grow and shrink as necessary, depending on the needs of the system. The pool can recover from network errors and database connectivity issues.
  • users in a new electronic mail service at the mobile office platform operative as an Internet Service have the ability to perform a migration of their existing Web Client/WebMail account data into the MOP Internet Service Email system if their carrier enables it. This feature is coined “self-migration” or "user- initiated migration”.
  • the first option is more typical because not all carriers would opt for simultaneously enabling the internet service at launch. Also, it is unlikely there would be a sufficiently complete dataset available in time. In fact, a complete dataset would be large and unwieldy.
  • the indicator for whether a site/brand has enabled user-initiated migration could come from a "user_migrated_enabled” column from a "Site” table in the WC/WebMail database.
  • a carrier will indicate they would like to enable user-initiated migration.
  • a "user_migrated_enabled” bit will be set for that site/brand in the WC.
  • Existing WC users will be prompted at login to migrate to the Internet Service. If they choose not to, then they will be routed to an old WC system and carry on as before. When this user returns later and attempts to login they will again be prompted to migrate to the Internet Service. If the user chooses to migrate then all required account information for this user from the old WC system will be passed to the new IS and a new IS account is created along with a hosted mailbox and any integrated source mailboxes . [0082] After a successful migration, the user would then be routed to the IS system from then on.
  • FIG. 7 shows basic components of the Internet Service Mobile Office Platform 200 and its HTML/WAP 202 and Proxy API 204. Also illustrated are the electronic mail server 205 operative as a mail server, and including a web client database 206, AggAPI 208. The PRV-IS API 208 is operative therewith and a flow sequence of operation is shown.
  • a LoginHandler 212 obtains a WCSubscriber object during user login.
  • the WCSubscriber object contains enough information to create an IS account if the user chooses to migrate.
  • a SelfMigrationHandler 214 makes a migrate wc ⁇ ser 216 soap call to the ProxyAPI 204. That soap call handles all of the steps involved in user-initiated migration. First, it looks at the IDProfile. loginld parameter. If it is null, then the user has no WC account. Otherwise, it fetches the WC Agg externalld by making a getExternalld soap call to the PRV-IS API and passing the IDProfile.
  • the createMigratedAcct call makes a migrateBwcUser soap call to PRV-IS in order to create a IDProfile for the migrated user. It then makes zero or more createMigratedMbox calls in order to migrate any integrated mailboxes the user may have. It calls deleteMboxAcct in order to delete the WC aggregation account.
  • the SelfMigrationHandler Upon successfully executing the migrateBwcUsersoap call, the SelfMigrationHandler makes a stored procedure (proc) call to the WC DB in order update the WC subscriber's status to MIGRATED.
  • Certain database changes are typically required before any user-initiated migration can begin.
  • MboxProvider/MboxAcctType One change is made in the central database for the MboxProvider/MboxAcctType.
  • a MboxProvider table In order to easily map between the MOP brand/MboxProviderName and the WC siteName, a MboxProvider table has a column "siteName". This allows some flexibility in coordinating the data between the Internet Service (IS) MOP and Web Client (WC) systems.
  • IS Internet Service
  • WC Web Client
  • a new MboxProvider entry could be made for all existing WC sites to be migrated.
  • New MboxAcctType entries can be made for each site added above.
  • This is a new mapping table required to map a site/plan from the old WC system to the new IS system. Locales may need to be changed and there may be a need to add locale data.
  • a partitioned database may be necessary, for example, MboxAcct, in which a new column is "migrated" to hold the date of the user-initiated migration.
  • a hostmailbox database may need to be changed.
  • a CarrierReservedLogin has each carrier providing a list of reserved logins to be added to the CarrierReservedLogin table, which will block all new users for this carrier from integrating these logins.
  • a GlobalReservedLogin could be changed.
  • a list of reserved logins could be added to the GlobalReservedLogin table, which will block all new users from integrating these logins.
  • a login handler for the Interet Service will obtain the following information from the WC database and pass it into the Internet Service migratewcUser SOAP ProxyAPI call: - Username Used for generating ID and hosted mailbox login.
  • the AcctMap. externallD could be the ID.
  • the ID could be the "sitename-username” .
  • the "Password” could be the user's WC Web login password from ⁇ subscriber_engine .user_password” . It is not determined from the MboxAcct .password in WC TeamOn Aggregation database, because that is not used for authentication and therefore is always empty.
  • An example of the logic used to determine the SrcMbox. address (the BIS-X reply to address) is:
  • the WC alert rules are stored in a WC database and have a different format . Translating them would not be easy, and would most likely end up with incorrect rules . Filters can be easily re-created by the user . Some data is required from PRV .
  • the MOP ProxyAPI migrateBwcUser SOAP method will request the following information from PRV/BIS-API in separate requests :
  • ProxyAPI migrateBwcUser SOAP method will request the following information for each integrated external mailbox from the old WC Aggregation API .
  • a new method “migrateBwcUser” could perform the actual user migration. This new SOAP method would be called from the new IS migration login handler when a users indicates that they wish to be migrated. It will accept most of the WC data as input and use the following methods to complete the migration process.
  • a new method “getBrandPlanMapping” can retrieve the new mboxProviderName and mboxAcctTypeName for IS by referring to the new MboxAcctTypeMap table using the old site name and plan from WC. The new method will require the following information as arguments :
  • a new method "createMigratedAccount” is required for migrated user account creation in order to incorporate the created date, migrated date, UTF-8 supported flag, and the users current status.
  • This new method may use the following information as arguments:
  • String login ⁇ hosted mailbox address for example, usernameSsitename . blackberry. net
  • the output is: o long srcMboxID for newly created SrcMbox row
  • a new method "createMigratedMailbox" would allow for migrated user'-s source mailbox creation in order to incorporate specific settings bits, autoCC, signature, and to not perform source validation.
  • the source mailbox data is coming from a trusted source, therefore the source valid bit, along with all required source configuration values, will be preserved as it was in the old WC database.
  • This new method typically requires the following information as arguments:
  • the output is: long srcMboxID for newly created SrcMbox row.
  • ID user names could contain a-z, A-Z, 0-9 plus ".”, " ⁇ ", and "_" . Also it is a requirement that at least one character must not be a digit (this requirement comes from quickmail) .
  • the maximum length is 32.
  • SMC Mailbox Migration There is a SMC Mailbox Migration. Some users have WC integrated mailboxes- which use the SMC. Currently this would be an older version of the SMC which does not inherently support migration. A newer version of the SMC has been developed which accepts a PROPPATCH command to switch the PWP server that it points to. This makes migration easier, in the sense that the user is not required to intervene (i.e. the user is not required to download or install an SMC) during the migration process.
  • UID Migration There could be UID Migration.
  • the system has altered the format used to store UIDs (or message IDs) in the database (in the SrcMboxMsg table) .
  • the migration scripts it is not possible for the migration scripts to derive automatically the new values, so a 100% seamless migration experience is not possible for such sources.
  • the IS system requires that IMAP sources store a SrcMboxMsg row for each message in the source mailbox (regardless of whether the message was forwarded to the Supervisor) , which was not the case in the WC, so there is no choice but to perform a catch-up PignoreOld") poll against the source, in order to build and store the SrcMboxMsg rows.
  • the rules (by protocol) are as follows:
  • IMAP and variants CS2000, AOL
  • Domino must use catch-up (“ignoreOld”) poll to build and store the SrcMboxMsg rows. This is accomplished by ensuring that "ignoreOld” setting bit is set to TRUE for the source, and that no SrcMboxMsg rows are created for source in BIS-T during migration.
  • TeamOnHash (Vinbox/ ⁇ msgType># ⁇ objId>”) .
  • the SrcMboxMsg. davHref field could be null, since it is only relevant in cases where a notification was sent to a IS Supervisor, which is never the case at the point of migration.
  • the SrcMboxMsg.msgNumber could be set to some arbitrary (but monotonically increasing) value since it is a mandatory field and must to be unique across all rows having the same srcMboxID.
  • the value for SrcMbox.lastMsgNumber MUST match the MAX (msgNumber) in SrcMboxMsg for the corresponding srcMboxID.
  • the user-initiated migration happens without downtime, and within seconds. Retrieving the UIDs would require another call to the System Aggregation database to retrieve the UIDs, which is not part of the existing AggAPI. Therefore, the system could add a new API call to the WC code line, or query the database directly. This could add complexity and risk to the migration process.
  • An alternative is to just do an IgnoreOld poll for all users. An IgnoreOld poll will happen immediately after the SrcMbox row is created resulting in a very small (seconds) window for message loss.
  • XML of course, as an extensive mark-up language, is a subset of the standard generalized markup language (SGML) and would allow data to be stored and published on websites and be richer in presentation.
  • Custom tags could be created to define the content of documents.
  • Common information formats could be created and the format and data shared on the internet, corporate internets and/or other networks.
  • the mark-up symbols in XML could be unlimited and self- defining.
  • the channel definition format (CDF) could describe any channel and a specific CDF file can contain data that specifies an initial web page and how it can be updated.
  • SOAP allows one program running in one kind of operating system to communicate with the program in the same or another type of operating system by using HTTP and XML for information exchange.
  • SOAP could specify how to encode an HTTP header in an XML file, thus, allowing one computer to call a program in another computer and pass data, while also dictating how it can return a response.
  • SOAP is advantageous to allow data to pass through firewall servers that screen-out requests other than those for known applications to a designated port.
  • SOAP is an XML- based protocol that has at least three parts, including: (a) an envelope to define a framework for describing what is in a message; (b) a set of encoding rules for expressing application-defined data types; and (c) a convention for representing remote procedure calls and responses.
  • the mobile office platform 16 could include software that is implemented as an ActiveX control as a component object model (COM) and provide a framework for building software components that communicate with each other.
  • ActiveX controls could be automatically downloaded and executed by a web browser.
  • Distributed object applications could be built in active web pages and ActiveX controls could be downloaded to different browsers and clients.
  • ActiveX controls could be held in a web browser as a container and distributed over an internet or corporate intranet. ActiveX controls could also manage and update web content and client systems and work closely with a user interface of a targeted operating system. Java applets or similar component objects could also be used instead of ActiveX controls.
  • an object model control could also be any type of dynamic link library (DLL) module that runs in a container as an application program using a component object model program interface.
  • DLL dynamic link library
  • FIG. 8 An example of a handheld mobile wireless communications device 1000 that may be used is further described in the example below with reference to FIG. 8.
  • the device 1000 illustratively includes a housing 1200, a keypad 1400 and an output device 1600.
  • the output device shown is a display 1600, which is preferably a full graphic LCD. Other types of output devices may alternatively be utilized.
  • a processing device 1800 is contained within the housing 1200 and is coupled between the keypad 1400 and the display 1600. The processing device 1800 controls the operation of the display 1600, as well as the overall operation of the mobile device 1000, in response to actuation of keys on the keypad 1400 by the user.
  • the housing 1200 may be elongated vertically, or may take on other sizes and shapes (including clamshell housing structures) .
  • the keypad may include a mode selection key, or other hardware or software for switching between text entry and telephony entry.
  • FIG. 8 In addition to the processing device 1800, other parts of the mobile device 1000 are shown schematically in FIG. 8. These include a communications subsystem 1001; a short-range communications subsystem 1020; the keypad 1400 and the display 1600, along with other input/output devices 1060, 1080, 1100 and 1120; as well as memory devices 1160, 1180 and various other device subsystems 1201.
  • the mobile device 1000 is preferably a two-way RF communications device having voice and data Communications capabilities. In addition, the mobile device 1000 preferably has the capability to communicate with other computer systems via the Internet.
  • Operating system software executed by the processing device 1800 is preferably stored in a persistent store, such as the flash memory 1160, but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element.
  • system software, specific device applications, or parts thereof may be temporarily loaded into a volatile store, such as the random access memory (RAM) 1180.
  • Communications signals received by the mobile device may also be stored in the RAM 1180.
  • the processing device 1800 in addition to its operating system functions, enables execution of software applications 1300A-1300N on the device 1000.
  • a predetermined set of applications that control basic device operations, such as data and voice communications 1300A and 1300B, may be installed on the device 1000 during manufacture.
  • a personal information manager (PIM) application may be installed during manufacture.
  • the PIM is preferably capable of organizing and managing data items, such as e-mail, calendar events, voice mails, appointments, and task items.
  • the PIM application is also preferably capable of sending and receiving data items via a wireless network 1401.
  • the PIM data items are seamlessly integrated, synchronized and updated via the wireless network 1401 with the device user's corresponding data items stored or associated with a host computer system.
  • the communications subsystem 1001 includes a receiver 1500, a transmitter 1520, and one or more antennas 1540 and 1560.
  • the communications subsystem 1001 also includes a processing module, such as a digital signal processor (DSP) 1580, and local oscillators (LOs) 1601.
  • DSP digital signal processor
  • LOs local oscillators
  • a mobile device 1000 may include a communications subsystem 1001 designed to operate with the MobitexTM, Data TACTM or General Packet Radio Service (GPRS) mobile data communications networks, and also designed to operate with any of a variety of voice communications networks, such as AMPS, TDMA, CDMA, PCS, GSM, etc. Other types of data and voice networks, both separate and integrated, may also be utilized with the mobile device 1000.
  • GPRS General Packet Radio Service
  • Network access requirements vary depending upon the type of communication system. For example, in the Mobitex and DataTAC networks, mobile devices are registered on the network using a unique personal identification number or PIN associated with each device. In GPRS networks, however, network access is associated with a subscriber or user of a device. A GPRS device therefore requires a subscriber identity module, commonly referred to as a SIM card, in order to operate on a GPRS network.
  • SIM card subscriber identity module
  • the mobile device 1000 may send and receive communications signals over the communication network 1401.
  • Signals received from the communications network 1401 by the antenna 1540 are routed to the receiver 1500, which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog-to- digital conversion of the received signal allows the DSP 1580 to perform more complex communications functions, such as demodulation and decoding.
  • signals to be transmitted to the network 1401 are processed (e.g. modulated and encoded) by the DSP 1580 and are then provided to the transmitter 1520 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network 1401 (or networks) via the antenna 1560.
  • the DSP 1580 provides for control of the receiver 1500 and the transmitter 1520. For example, gains applied to communications signals in the receiver 1500 and transmitter 1520 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 1580.
  • a received signal such as a text message or web page download
  • the received signal is then further processed by the processing device 1800 for an output to the display 1600, or alternatively to some other auxiliary I/O device 1060.
  • a device user may also compose data items, such as e- mail messages, using the keypad 1400 and/or some other auxiliary 1/0 device 1060, such as a touchpad, a rocker switch, a thumb-wheel, or some other type of input device.
  • the composed data items may then be transmitted over the communications network 1401 via the communications subsystem 1001.
  • a voice communications mode In a voice communications mode, overall operation of the device is substantially similar to the data communications mode, except that received signals are output to a speaker 1100, and signals for transmission are generated by a microphone 1120.
  • Alternative voice or audio I/O subsystems such as a voice message recording subsystem, may also be implemented on the device 1000.
  • the display 1600 may also ' be utilized in voice communications mode, for example to display the identity of a calling party, the duration of a voice call, or other voice call related information.
  • the short-range communications subsystem enables communication between the mobile device 1000 and other proximate systems or devices, which need not necessarily be similar devices.
  • the short-range communications subsystem may include an infrared device and associated circuits and components, or a BluetoothTM communications module to provide for communication with similarly-enabled systems and devices .

Abstract

Ce système permet d'assurer la migration des données de compte utilisateur depuis une boîte à lettres électronique intégrée vers un nouveau service de messagerie électronique. Un serveur de messagerie électronique (e-mail) opère en tant que client Web et possède pour chaque utilisateur une boîte à lettres électronique intégrée ainsi que des données de compte utilisateur. Une plate-forme de bureau mobile interagit avec le serveur de messagerie électronique et possède au minimum une procédure cataloguée permettant d'extraire du serveur de messagerie électronique les données du compte utilisateur pour les placer dans un nouveau service de messagerie électronique de la plate-forme de bureau mobile.
PCT/US2006/011117 2006-03-27 2006-03-27 Système et méthode pour assurer la migration des données d'un compte utilisateur WO2007111596A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP06739735A EP1999914A1 (fr) 2006-03-27 2006-03-27 Système et méthode pour assurer la migration des données d'un compte utilisateur
PCT/US2006/011117 WO2007111596A1 (fr) 2006-03-27 2006-03-27 Système et méthode pour assurer la migration des données d'un compte utilisateur
CA002638460A CA2638460C (fr) 2006-03-27 2006-03-27 Systeme et methode pour assurer la migration des donnees d'un compte utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2006/011117 WO2007111596A1 (fr) 2006-03-27 2006-03-27 Système et méthode pour assurer la migration des données d'un compte utilisateur

Publications (1)

Publication Number Publication Date
WO2007111596A1 true WO2007111596A1 (fr) 2007-10-04

Family

ID=36636430

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/011117 WO2007111596A1 (fr) 2006-03-27 2006-03-27 Système et méthode pour assurer la migration des données d'un compte utilisateur

Country Status (3)

Country Link
EP (1) EP1999914A1 (fr)
CA (1) CA2638460C (fr)
WO (1) WO2007111596A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110295925A1 (en) * 2010-03-30 2011-12-01 Jason Lieblich Systems and methods for selecting an alternative computing infrastructure
US11405345B2 (en) 2016-11-01 2022-08-02 Microsoft Technology Licensing, Llc E-mail with smart reply and roaming drafts
US10516630B2 (en) 2016-11-01 2019-12-24 Microsoft Technology Licensing, Llc Switching synchronization systems for synchronizing server/client data

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003058483A1 (fr) * 2002-01-08 2003-07-17 Seven Networks, Inc. Architecture de connexion pour un reseau mobile
US6779019B1 (en) 1998-05-29 2004-08-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US20040254976A1 (en) * 2003-06-16 2004-12-16 Malik Dale W. Migrating from an old instant messaging (IM) platform to a new IM platform
US20050038857A1 (en) * 2003-08-11 2005-02-17 Teamon Systems, Inc. System and method for gererating configurations used for accessing electronic mailboxes
EP1569396A1 (fr) * 2004-02-27 2005-08-31 Research In Motion Limited Configuration à distance d'un système de redirection de courrier électronique par un dispositif mobile

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6779019B1 (en) 1998-05-29 2004-08-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
WO2003058483A1 (fr) * 2002-01-08 2003-07-17 Seven Networks, Inc. Architecture de connexion pour un reseau mobile
US20040254976A1 (en) * 2003-06-16 2004-12-16 Malik Dale W. Migrating from an old instant messaging (IM) platform to a new IM platform
US20050038857A1 (en) * 2003-08-11 2005-02-17 Teamon Systems, Inc. System and method for gererating configurations used for accessing electronic mailboxes
EP1569396A1 (fr) * 2004-02-27 2005-08-31 Research In Motion Limited Configuration à distance d'un système de redirection de courrier électronique par un dispositif mobile

Also Published As

Publication number Publication date
EP1999914A1 (fr) 2008-12-10
CA2638460A1 (fr) 2007-10-04
CA2638460C (fr) 2010-01-12

Similar Documents

Publication Publication Date Title
US20070226304A1 (en) System and method for migrating user account data
US8301711B2 (en) Electronic mail communications system with client email internet service provider (ISP) polling application and related methods
US8626857B2 (en) System and method for provisioning an email account using mail exchange records
US8315603B2 (en) System and method for provisioning a mobile wireless communications device, including indicators representative of image and sound data
US20070073817A1 (en) System and method for authenticating a user for accessing an email account using authentication token
US8117267B2 (en) System and method for provisioning an email account using mail exchange and address records
EP1929401B1 (fr) Serveur de courrier electronique destine a traiter un nombre seuil de taches de courriers electroniques pour un utilisateur donne et procedes associes
US20070072588A1 (en) System and method for reconciling email messages between a mobile wireless communications device and electronic mailbox
US20080256197A1 (en) Email system including email aggregation server providing security parameter determination features and related methods
US7987235B2 (en) System and method for delayed acknowledgment of client requests in electronic mail system
EP1929721B1 (fr) Procede et systeme permettant des communications asynchrones sur internet
CA2647019C (fr) Systeme de communication de courriers electroniques avec une application d'interrogation du fournisseur de services internet (fsi) de courriers electroniques client et procedes connexes
US20070078934A1 (en) System and method for provisioning an email account hosted on an assured email service provider
CA2638460C (fr) Systeme et methode pour assurer la migration des donnees d'un compte utilisateur
EP1929723B1 (fr) Systeme et procede de reconciliation des messages entre un terminal de radiocommunications mobiles et une boite de courrier electronique
EP1929726A1 (fr) Systeme et procede d'approvisionnement d'un compte de courrier electronique au moyen d'enregistrement d'echange de courrier records
EP2175595B1 (fr) Système et procédé pour la fourniture d'un compte de courrier électronique
EP1929740A1 (fr) Systeme et procede permettant d'authentifier un utilisateur pour acces a un compte de courriers electroniques au moyen d'un jeton d'authentification
CA2634792C (fr) Systeme et methode d'approvisionnement d'un dispositif de communication mobile sans fil, comportant des indicateurs representant les donnees image et son
EP1929722A1 (fr) Systeme et procede d'approvisionnement d'un compte de courrier electronique au moyen d'enregistrements d'echange de courrier et d'adresses

Legal Events

Date Code Title Description
DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06739735

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2006739735

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2638460

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE