|Publication number||WO2006058967 A1|
|Publication date||8 Jun 2006|
|Filing date||1 Dec 2005|
|Priority date||3 Dec 2004|
|Also published as||EP1817883A1, EP1817883A4|
|Publication number||PCT/2005/50441, PCT/FI/2005/050441, PCT/FI/2005/50441, PCT/FI/5/050441, PCT/FI/5/50441, PCT/FI2005/050441, PCT/FI2005/50441, PCT/FI2005050441, PCT/FI200550441, PCT/FI5/050441, PCT/FI5/50441, PCT/FI5050441, PCT/FI550441, WO 2006/058967 A1, WO 2006058967 A1, WO 2006058967A1, WO-A1-2006058967, WO2006/058967A1, WO2006058967 A1, WO2006058967A1|
|Inventors||Ari Backholm, Seppo Salorinne, Marko Ketonen, Lauri Vuornos, Jussi Heinonen|
|Applicant||Seven Networks International Oy|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (8), Non-Patent Citations (1), Referenced by (105), Classifications (6), Legal Events (6)|
|External Links: Patentscope, Espacenet|
PROVISIONING OF E-MAIL SETTINGS FORA MOBILE TERMINAL
BACKGROUND OF THE INVENTION
The invention relates to methods and equipment 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.
BRIEF DESCRIPTION OF THE INVENTION
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: 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. 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 val- idly 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 saves 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.
BRIEF DESCRIPTION OF THE DRAWINGS
In the following the invention will be described in greater detail by means of preferred embodiments with reference to the attached drawings, in which
Figure 1 shows an exemplary system architecture in which the in- vention can be used;
Figure 2 shows a user interface screen for requesting setting parameters from a user;
Figure 3 shows a table of good and bad setting parameters;
Figure 4A shows a table of bad setting parameters; Figure 4B shows a table of alternative setting parameters; and
Figure 5 shows a flow chart for processing user-supplied setting parameters.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
The invention is applicable to virtually any mobile e-mail system ar- chitecture. Figure 1 shows an exemplary system architecture which is sup- ported 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.
Reference numeral 106 denotes a data network, such as an IP (Internet Protocol) network, which may be the common Internet or its closed subnetworks, commonly called intranets or extranets. Reference numeral 108 denotes an e-mail server and its associated database. There may be separate e-mail servers and/or server addresses for incoming and outgoing e-mail. The database stores an e-mail account, addressable by means of an e-mail address, that appears as a mailbox to the owner of the e-mail account. In order to communicate with mobile terminals 102, the data network 106 is connected, via a gateway 112 to an access network 114. The access network comprises a set of base stations 116 to provide wireless coverage over a wireless interface 118 to the mobile terminals 102.
Reference numeral 110 denotes a messaging centre that is largely responsible for providing the above-mentioned transparency between the host system 100 and the mobile terminal 102. The system architecture also com- prises a connectivity function 120, whose task is to push e-mail messages to the mobile terminal. In the embodiment shown in Figure 1 , the connectivity function 120 is considered a physically integral but logically distinct element of the messaging centre 110.
The mobile terminal 102 may be a pocket or laptop computer with a radio interface, a smart cellular telephone, or the like. Depending on implementation, the host system 100, if present, may have different roles. In some im- plementations the host system 100 is optional and may be a conventional office computer that merely acts as the mobile terminal user's principal computer and e-mail terminal. In other implementations the host system may act as a platform for a single user's connectivity function, in addition to being an office computer. In yet other implementations the host system 100 may comprise the connectivity function for several users. Thus it is a server instead of a normal office computer.
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.
Figure 1 shows an embodiment in which the messaging centre 110 is largely responsible for e-mail transport to/from the mobile terminal 102 via the access network 114, while a separate connectivity function 120 is respon- sible for data security issues. The connectivity function 120 may be physically attached to or co-located with the messaging centre 110, but they are logically separate elements. Indeed, a definite advantage of the separate connectivity function 120 is that it can be detached from the messaging centre, for instance, within the company that owns the host system 100 or the e-mail server 108. For a small number of users, the connectivity function 120 can be installed in each host system 100, or the host system 100 can be interpreted as a separate server configured to support multiple users. It is even possible to implement some or all the above-mentioned options. This means, for example, that there is one or more messaging centres 110 that offer services to several net- work operators, or there may be a dedicated messaging centre for each network operator (somewhat analogous to short messaging centres). Each messaging centre 110 may have an integral connectivity function 120 to support users who don't wish to install a separate connectivity function in a host system 100. For users who do install a separate connectivity function 120 in their host systems 100, such connectivity functions bypass the connectivity function in the messaging centre 110 and address the messaging centre 110 directly.
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 Figure 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 pref- erably 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 Figure 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. Figure 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 Figure 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. Figure 3 shows a table 300 of setting parameters. Figure 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. Figure 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 31 Oi denotes a domain 310 for a first operator.
Embodiments of the invention are best described by describing the user interface of Figure 2, the data structures of Figures 3 and 4, and a method shown in Figure 5 simultaneously. Figure 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 Figure 1. Alternatively, a dedicated provisioning server 126 can be provided. In step 502 the user is requested to enter the e-mail address 210 and authentication information 220, 222, shown in Figure 2. At this step, the remaining parameters 240, 242 shown in Figure 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 Figures 2 and 3, the domain is operator.fi, which matches the domain part 31 Oi 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 320i and 330i (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 Figure 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 31 O3 and the user's newly-supplied parameters 32O3 and 33O3.
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 32O3 and 33O3 may not be valid to all users within the same domain 31 O3. 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 Figure 3. The failure measure for the domain operator_3.fi is denoted by reference numeral 34O3. Let us assume that after some monitoring period, that measure exceeds some predetermined threshold. As a result, the data for the domain opera- tor_3.fi is marked as bad (not configurable). In the example of Figure 3, the server addresses for incoming and outgoing e-mail for operator_3, denoted by reference numerals 32O3 and 33O3, 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.
Figure 4A shows an alternative embodiment that employs an explicit list 400 of bad domains. In this embodiment the list 300 of good settings pa- rameters is naturally devoid of bad domains.
Figure 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. Figure 4B shows a list 420 of alternative setting parameters for two operators. Reference numeral 422 denotes three alternative setting parameter 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 (Figure 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.
Further preferred embodiments
Figure 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 do- main, it may try all or some of the most generally applicable rules, such as us- ing 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.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|WO2001030130A2 *||20 Oct 2000||3 May 2001||Nomadix, Inc.||System and method for network access without reconfiguration|
|WO2004017591A2||18 Aug 2003||26 Feb 2004||Research In Motion Limited||System and method for triggering a provisioning event|
|WO2005015925A2 *||26 Jul 2004||17 Feb 2005||Koninklijke Kpn N.V.||A method and system to enable email services for mobile devices|
|WO2005020108A1 *||26 Feb 2004||3 Mar 2005||Teamon Systems, Inc.||System and method for configuring access to electronic mailboxes|
|EP1422899A1 *||25 Nov 2002||26 May 2004||T-Mobile Deutschland GmbH||Method and system for providing easy access to an e-mail account via a mobile communication network|
|EP1482702A1||30 May 2003||1 Dec 2004||Research In Motion Limited||System and methods for provisioning a service for a communication device|
|US6119171 *||29 Jan 1998||12 Sep 2000||Ip Dynamics, Inc.||Domain name routing|
|US20040128375 *||16 Oct 2003||1 Jul 2004||Xerox Corporation.||Integrated server platform for the autonomous provisioning of device services|
|1||*||See also references of EP1817883A1|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|EP1890449A1||17 Aug 2007||20 Feb 2008||Brother Kogyo Kabushiki Kaisha||Network device|
|EP2073502A1||21 Dec 2007||24 Jun 2009||Vodafone Holding GmbH||Providing communication services at a mobile terminal in dependence of a foreign recipient's contact data|
|US7756937||14 Aug 2007||13 Jul 2010||Brother Kogyo Kabushiki Kaisha||Network device|
|US8001177||28 Feb 2007||16 Aug 2011||Hewlett-Packard Development Company, L.P.||Method and apparatus for automated personal information management data transfer for a wireless enabled handheld|
|US8015163||29 Jun 2009||6 Sep 2011||Hewlett-Packard Development Company, L.P.||Detecting duplicative user data on computing device|
|US8064583||21 Sep 2006||22 Nov 2011||Seven Networks, Inc.||Multiple data store authentication|
|US8069166||27 Feb 2006||29 Nov 2011||Seven Networks, Inc.||Managing user-to-user contact with inferred presence information|
|US8078158||26 Jun 2008||13 Dec 2011||Seven Networks, Inc.||Provisioning applications for a mobile device|
|US8107921||11 Jan 2008||31 Jan 2012||Seven Networks, Inc.||Mobile virtual network operator|
|US8116214||30 Nov 2005||14 Feb 2012||Seven Networks, Inc.||Provisioning of e-mail settings for a mobile terminal|
|US8127342||23 Sep 2010||28 Feb 2012||Seven Networks, Inc.||Secure end-to-end transport through intermediary nodes|
|US8135798||15 Nov 2006||13 Mar 2012||Hewlett-Packard Development Company, L.P.||Over-the-air device services and management|
|US8166164||14 Oct 2011||24 Apr 2012||Seven Networks, Inc.||Application and network-based long poll request detection and cacheability assessment therefor|
|US8190701||1 Nov 2011||29 May 2012||Seven Networks, Inc.||Cache defeat detection and caching of content addressed by identifiers intended to defeat cache|
|US8204953||1 Nov 2011||19 Jun 2012||Seven Networks, Inc.||Distributed system for cache defeat detection and caching of content addressed by identifiers intended to defeat cache|
|US8209709||5 Jul 2010||26 Jun 2012||Seven Networks, Inc.||Cross-platform event engine|
|US8291076||5 Mar 2012||16 Oct 2012||Seven Networks, Inc.||Application and network-based long poll request detection and cacheability assessment therefor|
|US8316098||19 Apr 2012||20 Nov 2012||Seven Networks Inc.||Social caching for device resource sharing and management|
|US8326985||1 Nov 2011||4 Dec 2012||Seven Networks, Inc.||Distributed management of keep-alive message signaling for mobile network resource conservation and optimization|
|US8356080||20 Jul 2012||15 Jan 2013||Seven Networks, Inc.||System and method for a mobile device to use physical storage of another device for caching|
|US8364181||10 Dec 2007||29 Jan 2013||Seven Networks, Inc.||Electronic-mail filtering for mobile devices|
|US8386570||17 Aug 2007||26 Feb 2013||Brother Kogyo Kabushiki Kaisha||Electronic mail communication device|
|US8412675||24 Feb 2006||2 Apr 2013||Seven Networks, Inc.||Context aware data presentation|
|US8417823||18 Nov 2011||9 Apr 2013||Seven Network, Inc.||Aligning data transfer to optimize connections established for transmission over a wireless network|
|US8438633||18 Dec 2006||7 May 2013||Seven Networks, Inc.||Flexible real-time inbox access|
|US8468126||14 Dec 2005||18 Jun 2013||Seven Networks, Inc.||Publishing data in an information community|
|US8484314||14 Oct 2011||9 Jul 2013||Seven Networks, Inc.||Distributed caching in a wireless network of content delivered for a mobile application over a long-held request|
|US8494510||6 Dec 2011||23 Jul 2013||Seven Networks, Inc.||Provisioning applications for a mobile device|
|US8539040||28 Feb 2012||17 Sep 2013||Seven Networks, Inc.||Mobile network background traffic data management with optimized polling intervals|
|US8549587||14 Feb 2012||1 Oct 2013||Seven Networks, Inc.||Secure end-to-end transport through intermediary nodes|
|US8561086||17 May 2012||15 Oct 2013||Seven Networks, Inc.||System and method for executing commands that are non-native to the native environment of a mobile device|
|US8621075||27 Apr 2012||31 Dec 2013||Seven Metworks, Inc.||Detecting and preserving state for satisfying application requests in a distributed proxy and cache system|
|US8635339||22 Aug 2012||21 Jan 2014||Seven Networks, Inc.||Cache state management on a mobile device to preserve user experience|
|US8693494||31 Mar 2008||8 Apr 2014||Seven Networks, Inc.||Polling|
|US8700728||17 May 2012||15 Apr 2014||Seven Networks, Inc.||Cache defeat detection and caching of content addressed by identifiers intended to defeat cache|
|US8738050||7 Jan 2013||27 May 2014||Seven Networks, Inc.||Electronic-mail filtering for mobile devices|
|US8750123||31 Jul 2013||10 Jun 2014||Seven Networks, Inc.||Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network|
|US8761756||13 Sep 2012||24 Jun 2014||Seven Networks International Oy||Maintaining an IP connection in a mobile network|
|US8774844||8 Apr 2011||8 Jul 2014||Seven Networks, Inc.||Integrated messaging|
|US8775631||25 Feb 2013||8 Jul 2014||Seven Networks, Inc.||Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications|
|US8782222||5 Sep 2012||15 Jul 2014||Seven Networks||Timing of keep-alive messages used in a system for mobile network resource conservation and optimization|
|US8787947||18 Jun 2008||22 Jul 2014||Seven Networks, Inc.||Application discovery on mobile devices|
|US8793305||13 Dec 2007||29 Jul 2014||Seven Networks, Inc.||Content delivery to a mobile device from a content service|
|US8799410||13 Apr 2011||5 Aug 2014||Seven Networks, Inc.||System and method of a relay server for managing communications and notification between a mobile device and a web access server|
|US8805334||5 Sep 2008||12 Aug 2014||Seven Networks, Inc.||Maintaining mobile terminal information for secure communications|
|US8805425||28 Jan 2009||12 Aug 2014||Seven Networks, Inc.||Integrated messaging|
|US8811952||5 May 2011||19 Aug 2014||Seven Networks, Inc.||Mobile device power management in data synchronization over a mobile network with or without a trigger notification|
|US8812695||3 Apr 2013||19 Aug 2014||Seven Networks, Inc.||Method and system for management of a virtual network connection without heartbeat messages|
|US8831561||28 Apr 2011||9 Sep 2014||Seven Networks, Inc||System and method for tracking billing events in a mobile wireless network for a network operator|
|US8832228||26 Apr 2012||9 Sep 2014||Seven Networks, Inc.||System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief|
|US8838744||28 Jan 2009||16 Sep 2014||Seven Networks, Inc.||Web-based access to data objects|
|US8838783||5 Jul 2011||16 Sep 2014||Seven Networks, Inc.||Distributed caching for resource and mobile network traffic management|
|US8839412||13 Sep 2012||16 Sep 2014||Seven Networks, Inc.||Flexible real-time inbox access|
|US8843153||1 Nov 2011||23 Sep 2014||Seven Networks, Inc.||Mobile traffic categorization and policy for network use optimization while preserving user experience|
|US8849902||24 Jun 2011||30 Sep 2014||Seven Networks, Inc.||System for providing policy based content service in a mobile network|
|US8861354||14 Dec 2012||14 Oct 2014||Seven Networks, Inc.||Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization|
|US8862657||25 Jan 2008||14 Oct 2014||Seven Networks, Inc.||Policy based content service|
|US8868753||6 Dec 2012||21 Oct 2014||Seven Networks, Inc.||System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation|
|US8873411||12 Jan 2012||28 Oct 2014||Seven Networks, Inc.||Provisioning of e-mail settings for a mobile terminal|
|US8874761||15 Mar 2013||28 Oct 2014||Seven Networks, Inc.||Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols|
|US8886176||22 Jul 2011||11 Nov 2014||Seven Networks, Inc.||Mobile application traffic optimization|
|US8903945||12 Dec 2011||2 Dec 2014||Qualcomm Incorporated||Over the air services for mobile devices|
|US8903954||22 Nov 2011||2 Dec 2014||Seven Networks, Inc.||Optimization of resource polling intervals to satisfy mobile device requests|
|US8909192||11 Aug 2011||9 Dec 2014||Seven Networks, Inc.||Mobile virtual network operator|
|US8909202||7 Jan 2013||9 Dec 2014||Seven Networks, Inc.||Detection and management of user interactions with foreground applications on a mobile device in distributed caching|
|US8909759||12 Oct 2009||9 Dec 2014||Seven Networks, Inc.||Bandwidth measurement|
|US8914002||11 Aug 2011||16 Dec 2014||Seven Networks, Inc.||System and method for providing a network service in a distributed fashion to a mobile device|
|US8918503||28 Aug 2012||23 Dec 2014||Seven Networks, Inc.||Optimization of mobile traffic directed to private networks and operator configurability thereof|
|US8966066||12 Oct 2012||24 Feb 2015||Seven Networks, Inc.||Application and network-based long poll request detection and cacheability assessment therefor|
|US8977755||6 Dec 2012||10 Mar 2015||Seven Networks, Inc.||Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation|
|US8984581||11 Jul 2012||17 Mar 2015||Seven Networks, Inc.||Monitoring mobile application activities for malicious traffic on a mobile device|
|US8989728||7 Sep 2006||24 Mar 2015||Seven Networks, Inc.||Connection architecture for a mobile network|
|US9002828||2 Jan 2009||7 Apr 2015||Seven Networks, Inc.||Predictive content delivery|
|US9009250||7 Dec 2012||14 Apr 2015||Seven Networks, Inc.||Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation|
|US9021021||10 Dec 2012||28 Apr 2015||Seven Networks, Inc.||Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system|
|US9037685||2 Mar 2007||19 May 2015||Qualcomm Incorporated||Intelligent migration between devices having different hardware or software configuration|
|US9043433||25 May 2011||26 May 2015||Seven Networks, Inc.||Mobile network traffic coordination across multiple applications|
|US9043731||30 Mar 2011||26 May 2015||Seven Networks, Inc.||3D mobile user interface with configurable workspace management|
|US9047142||16 Dec 2010||2 Jun 2015||Seven Networks, Inc.||Intelligent rendering of information in a limited display environment|
|US9049179||20 Jan 2012||2 Jun 2015||Seven Networks, Inc.||Mobile network traffic coordination across multiple applications|
|US9055102||2 Aug 2010||9 Jun 2015||Seven Networks, Inc.||Location-based operations and messaging|
|US9060032||9 May 2012||16 Jun 2015||Seven Networks, Inc.||Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic|
|US9065765||8 Oct 2013||23 Jun 2015||Seven Networks, Inc.||Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network|
|US9077630||8 Jul 2011||7 Jul 2015||Seven Networks, Inc.||Distributed implementation of dynamic wireless traffic policy|
|US9084105||19 Apr 2012||14 Jul 2015||Seven Networks, Inc.||Device resources sharing for network resource conservation|
|US9100873||14 Sep 2012||4 Aug 2015||Seven Networks, Inc.||Mobile network background traffic data management|
|US9131397||6 Jun 2013||8 Sep 2015||Seven Networks, Inc.||Managing cache to prevent overloading of a wireless network due to user activity|
|US9161258||15 Mar 2013||13 Oct 2015||Seven Networks, Llc||Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion|
|US9173128||6 Mar 2013||27 Oct 2015||Seven Networks, Llc||Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol|
|US9203864||4 Feb 2013||1 Dec 2015||Seven Networks, Llc||Dynamic categorization of applications for network access in a mobile network|
|US9208123||7 Dec 2012||8 Dec 2015||Seven Networks, Llc||Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor|
|US9239800||11 Jul 2012||19 Jan 2016||Seven Networks, Llc||Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network|
|US9241314||15 Mar 2013||19 Jan 2016||Seven Networks, Llc||Mobile device with application or context aware fast dormancy|
|US9251193||28 Oct 2007||2 Feb 2016||Seven Networks, Llc||Extending user relationships|
|US9271238||15 Mar 2013||23 Feb 2016||Seven Networks, Llc||Application or context aware fast dormancy|
|US9275163||17 Oct 2011||1 Mar 2016||Seven Networks, Llc||Request and response characteristics based adaptation of distributed caching in a mobile network|
|US9277443||7 Dec 2012||1 Mar 2016||Seven Networks, Llc||Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol|
|US9300719||14 Jan 2013||29 Mar 2016||Seven Networks, Inc.||System and method for a mobile device to use physical storage of another device for caching|
|US9307493||15 Mar 2013||5 Apr 2016||Seven Networks, Llc||Systems and methods for application management of mobile device radio state promotion and demotion|
|US9325662||9 Jan 2012||26 Apr 2016||Seven Networks, Llc||System and method for reduction of mobile network traffic used for domain name system (DNS) queries|
|US9326189||4 Feb 2013||26 Apr 2016||Seven Networks, Llc||User as an end point for profiling and optimizing the delivery of content and data in a wireless network|
|US9330196||14 Jun 2012||3 May 2016||Seven Networks, Llc||Wireless traffic management system cache optimization using http headers|
|US9407713||16 Jan 2012||2 Aug 2016||Seven Networks, Llc||Mobile application traffic optimization|
|US9712986||22 Mar 2012||18 Jul 2017||Seven Networks, Llc||Mobile device configured for communicating with another mobile device associated with an associated user|
|USRE45348||16 Mar 2012||20 Jan 2015||Seven Networks, Inc.||Method and apparatus for intercepting events in a communication system|
|Cooperative Classification||H04L51/38, H04M1/72552, H04L51/28, H04L51/30|
|8 Jun 2006||AK||Designated states|
Kind code of ref document: A1
Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KN KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW
|8 Jun 2006||AL||Designated countries for regional patents|
Kind code of ref document: A1
Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG
|19 Jul 2006||121||Ep: the epo has been informed by wipo that ep was designated in this application|
|5 Jun 2007||NENP||Non-entry into the national phase in:|
Ref country code: DE
|8 Jun 2007||WWE||Wipo information: entry into national phase|
Ref document number: 2005815115
Country of ref document: EP
|15 Aug 2007||WWP||Wipo information: published in national office|
Ref document number: 2005815115
Country of ref document: EP