Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20090063647 A1
Publication typeApplication
Application numberUS 12/228,325
Publication dateMar 5, 2009
Filing dateAug 11, 2008
Priority dateNov 22, 2004
Also published asUS7643818, US7769400, US20060240805, US20090075683, US20150149575
Publication number12228325, 228325, US 2009/0063647 A1, US 2009/063647 A1, US 20090063647 A1, US 20090063647A1, US 2009063647 A1, US 2009063647A1, US-A1-20090063647, US-A1-2009063647, US2009/0063647A1, US2009/063647A1, US20090063647 A1, US20090063647A1, US2009063647 A1, US2009063647A1
InventorsAri Backholm, Seppo Salorinne, Antti Saarilahti, Marko Ketonen, Lauri Vuornos, Petri Salmi
Original AssigneeSeven Networks International Oy
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Messaging centre for forwarding e-mail
US 20090063647 A1
Abstract
Methods and systems for forwarding an e-mail message from an e-mail server to a mobile terminal are provided. A messaging centre may store a permanent terminal identifier of the mobile terminal and an associated temporary identifier of the mobile terminal. The messaging center, upon receiving an e-mail message, may identify the mobile terminal based on an indication of the permanent terminal identifier included in the message and the stored association information. The e-mail message may then be transmitted to the mobile terminal using the temporary identifier associated with the permanent identifier of the mobile terminal.
Images(5)
Previous page
Next page
Claims(20)
1. A method for forwarding an e-mail message from an e-mail server to a mobile terminal, the method comprising:
storing a permanent terminal identifier of the mobile terminal and an associated temporary identifier of the mobile terminal;
receiving the e-mail message, wherein the e-mail message includes an indication of the permanent terminal identifier;
transmitting the e-mail address to the mobile terminal using the temporary identifier associated with the permanent identifier of the mobile terminal.
2. The method of claim 1, further comprising storing an e-mail address of the mobile terminal in association with the permanent identifier and the temporary identifier of the mobile terminal.
3. The method of claim 1, wherein the permanent identifier of the mobile terminal is an e-mail address of the mobile terminal.
4. The method of claim 1, further comprising installing a messaging centre in a host system.
5. The method of claim 4, wherein the messaging centre serves a plurality of data networks.
6. The method of claim 1, wherein the e-mail message is encrypted.
7. The method of claim 6, wherein the e-mail message is further packed.
8. The method of claim 6, further comprising receiving the encrypted e-mail message from a connectivity application.
9. The method of claim 6, wherein mobile terminal receives and decrypts the e-mail message.
10. The method of claim 7, wherein the mobile terminal unpacks the e-mail message.
11. A system for forwarding an e-mail message from an e-mail server to a mobile terminal, the system comprising:
a memory for storing a permanent identifier of the mobile terminal and an associated temporary identifier of the mobile terminal;
a processor configured to execute software stored in memory, the execution of the software resulting in the identification of the mobile terminal based on a received e-mail message including an indication of the permanent identifier of the mobile terminal and the stored association between the permanent identifier and the temporary identifier of the mobile terminal; and
a communications interface configured to transmit the e-mail message to the identified mobile terminal.
12. The system of claim 11, wherein the communications interface is further configured to receive the e-mail message from a connectivity application.
13. The system of claim 11, wherein the permanent identifier of the mobile terminal is an e-mail address of the mobile terminal.
14. The system of claim 11, wherein the e-mail message is encrypted.
15. The system of claim 14, wherein the e-mail message is further packed.
16. The system of claim 14, wherein mobile terminal receives and decrypts the e-mail message.
17. The system of claim 15, wherein the mobile terminal unpacks the e-mail message.
18. A computer-readable storage medium having embodied thereon a program, the program being executable by a processing device to perform a method for forwarding an e-mail message from an e-mail server to a mobile terminal, the method comprising:
storing a permanent terminal identifier of the mobile terminal and an associated temporary identifier of the mobile terminal;
receiving the e-mail message, wherein the e-mail message includes an indication of the permanent terminal identifier;
transmitting the e-mail address to the mobile terminal using the temporary identifier associated with the permanent identifier of the mobile terminal.
19. The computer-readable storage medium of claim 18, further comprising instructions for storing an e-mail address of the mobile terminal in association with the permanent identifier and the temporary identifier of the mobile terminal.
20. The computer-readable storage medium of claim 18, further comprising instructions for receiving the encrypted e-mail message from a connectivity application.
Description
    CROSS-REFERENCE TO RELATED APPLICATIONS
  • [0001]
    This application is a divisional and claims the priority benefit of U.S. patent application Ser. No. 11/282,950 filed Nov. 21, 2005, which claims the priority benefit of U.S. provisional patent application No. 60/650,975 filed Feb. 9, 2005 and the priority benefit of Finnish patent application number 20045451 filed Nov. 22, 2004, the disclosures of the aforementioned applications being incorporated herein by reference.
  • BACKGROUND OF THE INVENTION
  • [0002]
    1. Field of the Invention
  • [0003]
    The invention relates to methods and equipment for transmitting electronic mail (e-mail) messages to or from a mobile terminal. More specifically, the present invention relates to a messaging centre for transmitting e-mail messages to and from a mobile terminal.
  • [0004]
    2. Description of the Related Art
  • [0005]
    U.S. Pat. No. 6,701,378 to Barry Gilhuly et al. discloses a system and method for pushing information, such as e-mail messages, from a host system to a mobile data communication device (mobile terminal). The technique permits e-mail processing at a mobile terminal in addition to a more stationary computer, referred to as a host system in the Gilhuly patent. Specifically, a redirector program operating at the host system enables a user to continuously redirect certain user-selected data items from the host system to the user's mobile data communication device upon detecting that one or more user-defined triggering events has occurred. The redirector program operates in connection with event-generating applications and repackaging systems at the host system to configure and detect a particular user-defined event, and then to repackage the user-selected data items in an electronic wrapper prior to pushing the data items to the mobile device. The mobile data communication device may originate new messages or reply messages to previously received information, such messages being transmitted to a wireless redirector host system, which then transmits a copy of the messages to both the intended recipient and a first electronic mail account associated with the mobile data communication device.
  • [0006]
    The above-described prior art technique suffers from certain limitations. For example, the host system, such as an office computer, and the mobile terminal require separate e-mail accounts. Some e-mail systems support a forward-type file for forwarding e-mail messages from a first e-mail account to a second e-mail account, but some systems do not support it. It is difficult to set up e-mail systems that do not support such forwarding techniques.
  • [0007]
    Furthermore, the Gilhuly patent does not address issues that relate to manipulating e-mail messages at the second e-mail account (at the mobile terminal). For instance, it is difficult or impossible to use the terminal to arrange incoming e-mail messages into different folders at the host system. Also, if the terminal user deletes an incoming e-mail message at the terminal, a copy of the deleted message is not present in a “deleted items” folder at the host system, which typically is the case in e-mail systems. Likewise, when the terminal sends an e-mail message, a copy of the message is not added to the host system's “sent items” folder. A further related problem is that e-mail messages that the user has read at the terminal may appear as unread messages at the host system.
  • [0008]
    Yet another problem is that configuring an e-mail client software at the mobile terminal is difficult because of user interface restrictions in typical mobile terminals.
  • SUMMARY OF THE INVENTION
  • [0009]
    Embodiments of the present invention provide for methods and systems for messaging centres for forwarding an e-mail message from an e-mail server. A permanent terminal identifier of the mobile-terminal and an associated temporary identifier of the mobile terminal may be stored. An e-mail message including an indication of a permanent identifier of the mobile terminal may be received. The e-mail message may then be transmitted to the mobile terminal using the temporary identifier associated with the permanent identifier of the mobile terminal.
  • [0010]
    Various embodiments of the present invention include methods for forwarding an e-mail message from an e-mail server to a mobile terminal. Such methods may include storing a permanent terminal identifier of the mobile terminal and an associated temporary identifier of the mobile terminal, receiving the e-mail message, wherein the e-mail message includes an indication of the permanent terminal identifier, and transmitting the e-mail address to the mobile terminal using the temporary identifier associated with the permanent identifier of the mobile terminal. Some embodiments may further include storing the e-mail address of the e-mail message in association with the stored permanent and temporary identifier of the mobile terminal. The message may have been encrypted, packed, and received from a connectivity application in some embodiments of the present invention. The mobile terminal receiving the e-mail message may decrypt and unpack the message.
  • [0011]
    Some embodiments of the present invention further include a system of a memory for storing a permanent identifier of the mobile terminal and an associated temporary identifier of the mobile terminal, a processor configured to execute software stored in memory, the execution of the software resulting in the identification of the mobile terminal based on a received e-mail message including an indication of the permanent identifier of the mobile terminal and the stored association between the permanent identifier and the temporary identifier of the mobile terminal, and a communications interface configured to transmit the e-mail message to the identified mobile terminal.
  • [0012]
    Some embodiments may further include a computer-readable storage media upon which is embodied programs including instructions for performing methods for forwarding an e-mail message from an e-mail server.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0013]
    In the following the invention will be described in greater detail by means of preferred embodiments with reference to the attached drawings, in which
  • [0014]
    FIG. 1 shows an exemplary system architecture in which the invention can be used;
  • [0015]
    FIG. 2 shows provisioning of an e-mail system;
  • [0016]
    FIG. 3 shows a hypothetical scenario in which the e-mail system is used;
  • [0017]
    FIG. 4 shows information flows in mobile-terminated e-mail transmission;
  • [0018]
    FIG. 5 shows information flows in mobile-originated e-mail transmission;
  • [0019]
    FIG. 6 shows an enhanced embodiment in which some of the functions of the messaging centre are performed by a separate connectivity function;
  • [0020]
    FIG. 7 shows traffic flow in the embodiment shown in FIG. 6.
  • DETAILED DESCRIPTION
  • [0021]
    FIG. 1 shows an exemplary system architecture in which the invention can be used. 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.
  • [0022]
    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. 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.
  • [0023]
    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 comprises a connectivity function, whose task is to push e-mail messages to the mobile terminal. In the embodiment shown in FIG. 1, the connectivity function is considered a physically integral but logically distinct element of the messaging centre 110. Later, in connection with FIGS. 6 and 7, an enhanced embodiment will be described that explicitly assigns the security-related functions to the connectivity function and traffic-related functions to the messaging centre 110.
  • [0024]
    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 implementations 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.
  • [0025]
    We assume here that the access network 114 is able to establish and maintain a tunnel 120 between the messaging centre 110 and the mobile terminal 102. For instance, the tunnel may be set up using GPRS Tunneling Protocol (GTP) or its later derivatives, or any other suitable tunneling protocol.
  • [0026]
    In a real system, there are naturally a large number of mobile terminals 102 and tunnels 120. In order to keep track of which e-mail account and which tunnel belongs to which mobile terminal, the messaging centre 110 maintains an association 122 for each mobile terminal supported by it. Each association 122 joins three fields, namely an e-mail address 122A assigned to the mobile terminal or its user, encryption information 122C and a temporary wireless identity 122D of the mobile terminal in the access network. The embodiment shown in FIG. 1 also employs a terminal identifier 122B which may be the same as the e-mail address 122A of the mobile terminal 102, in which case the association 122 actually associates three information items. Alternatively, the terminal identifier 122B may be an identifier arbitrarily assigned to the mobile terminal. In a preferred implementation the terminal identifier 122B is the mobile terminal's equipment identifier or its derivative. The encryption information 122C will be generated by the mobile terminal, as described later in connection with FIG. 2. The temporary wireless identity 122D may be the identifier of the tunnel to the mobile station. Of course, the tunnel identifier is not permanent and is only known when a tunnel exists. The creation and use of the association 122 will be further described in connection with FIGS. 2, 3 and 6.
  • [0027]
    FIG. 2 shows provisioning of an e-mail system in a system as shown in FIG. 1. The e-mail provisioning phase comprises the following steps. In a preparatory step (not shown), appropriate e-mail software is installed in the host system 100 (if present) and mobile terminal 102, as well as in the e-mail server 108. For instance, the host system 100, the mobile terminal 102 and the e-mail server 108 may comprise and execute conventional e-mail software, such as Microsoft® Outlook, which may be augmented by inventive client software that will be described in more detail whenever necessary.
  • [0028]
    After the software installation, the next task is to create a secure binding between the connectivity function and the mobile terminal 102. The idea is to ensure that, in addition to the host system 100, only the mobile terminal 102 used in the binding process can be used to access and manipulate e-mail addressed to the mobile terminal's e-mail address. The binding operation faces two types of security risks. First, the communication used during binding must be secured against eavesdropping or other types of hacking. Second, the only the user of the bound terminal 102 may access e-mail addressed to the e-mail address. The eavesdropping problem is not trivial in a phase in which no trust exists between the mobile terminal 102 and the rest of the system. Yet another problem is that the e-mail server 108 and the messaging centre 110 typically have user interfaces that are only accessible to dedicated support persons.
  • [0029]
    FIG. 2 shows a secure e-mail provisioning technique in which the host system 100 authenticates the user of the mobile terminal 102. In step 2-1 the client software in the mobile terminal 102 generates and displays a service activation code. In step 2-2 the host system 100 authenticates the person who enters the service activation code. Instead of a dedicated authentication step, the technique may rely on the authentication of the underlying e-mail system, such as user name and password combination. After all, the e-mail provisioning need not be more secure than the underlying e-mail system. In step 2-3 the service activation code is then conveyed off-line to the host system 100. The idea of the off-line communication is to eliminate any chance of eavesdropping before secure a communication channel can be established. For instance, the service activation code may be entered manually or via a local connection, such as a wired or optical interface or a short-range wireless interface, such as Bluetooth™. Finally, in step 2-4, the mobile terminal's service activation code is registered with the connectivity function in the messaging centre 110.
  • [0030]
    The service activation code is closely related to an encryption key to be used in future communications between the connectivity function in the messaging centre 110 and the mobile terminal 102. The service activation code and the encryption key may be identical, or one may be a subset of the other, or the encryption key may be derived from the service activation code by means of some, preferably unpublished, algorithm. The fact that the service activation code and the encryption key are closely related to each other ensures that the terminal used in the authentication process is the terminal used to access the e-mail service afterwards.
  • [0031]
    Thus the idea of conveying the service activation code to the messaging centre 110 via the host system 100 solves both the security-related and user interface-related problems mentioned above. If there is no host system 100 that can authenticate the mobile terminal and its user. Instead, the user may enter the provisioning data to the connectivity function via some suitable connection. The provisioning data entered by the user may be checked by sending a trial e-mail message and attempting to read it. If the check succeeds, it is regarded as the authentication. Yet another way is to convey the service activation code to a dedicated support person who performs the authentication (eg by recognizing the person's face or voice) and enters the service activation code into the connectivity function in the messaging centre 110. The messaging centre/connectivity function 110 now stores an association (item 122 in FIG. 1) between the e-mail address 122A and encryption information 122C.
  • [0032]
    FIG. 3 shows a hypothetical scenario in which the e-mail system is used. This scenario comprises four events, which are delineated by thick dashed lines. The first event, steps 3-10 through 3-16, relate to incoming e-mail. In step 3-10 the external e-mail terminal 104 sends an e-mail message to the e-mail server 108. The e-mail message is addressed to the user of the host system 100. Accordingly, a notification of the incoming e-mail is sent to the host system 100, but that step is omitted from FIG. 3 as purely conventional. In step 3-11 the mobile terminal 102 requests the access network to establish a tunnel between itself and the messaging centre 110. Step 3-11 may take place before or after step 3-10. After the tunnel establishment, the messaging centre 110 now stores a complete association triplet (item 122 in FIG. 1) that joins the e-mail address 122A of the host system 100, the service activation code 122C of the mobile terminal 102 and the tunnel identifier 122D of the tunnel to the mobile terminal 102.
  • [0033]
    In step 3-12 the messaging centre 110 detects and retrieves the incoming e-mail from the e-mail server 108. For instance, the messaging centre 110 may regularly poll the e-mail server 108 or it may register itself as a listener to the e-mail server. In step 3-13 the messaging centre 110 encrypts, and optionally packs, the e-mail message or parts of it. For instance, the messaging centre 110 may omit the destination address of the e-mail message because it is self-evident that the e-mail message is addressed to the user of the host system 100, who is also the user of the mobile terminal 102. The messaging centre 110 may also omit all attachments or large attachments, up to some threshold size, from the e-mail message to be conveyed to the mobile terminal. The encryption process uses the mobile terminal's service activation code 122C, or its derivative, as the encryption key. In step 3-14 the messaging centre 110 transmits the encrypted and packed e-mail to the mobile terminal that decrypts and unpacks it in step 3-15. The messaging centre 110 knows the correct encryption key (service activation code) 122C and the tunnel identifier 122D on the basis of the association triplet 122.
  • [0034]
    In step 3-16 the mobile terminal 102 sends the messaging centre 110 an automatic control message indicating that the user has read the e-mail message. In response to the control message, the messaging centre 110 signals the e-mail server 108 to mark the e-mail message as read in step 3-17, which act the e-mail server performs in step 3-18. The control message comprises some identification of the e-mail message but not its contents, whereby it loads the radio interface only lightly. A benefit of the control message is that the user, when beginning to user the host system 100, immediately sees which messages he/she has already read and does not have to read them twice.
  • [0035]
    Next in this scenario, the user decides that the e-mail message needs further attention when he/she is at the host system 100. The user may initiate another control message 3-22 that causes the previously read message to be marked as unread at the e-mail server in step 3-22.
  • [0036]
    The next phase, steps 3-30 through 3-34, relates to e-mail message generation at the mobile terminal 102. We assume here, that the e-mail message to be generated is a reply message to the incoming message described above (steps 3-10 to 3-17), but the operation is very similar if the message to be generated is an original (non-reply) message. In step 3-30 the mobile terminal user generates a reply message. Since it is a reply message, its recipient is automatically the sender of the incoming message, and the subject field comprises the original subject with a prefix of “RE:” or something similar. If the message is not a reply message, the user will have to fill in the recipient and subject fields. In step 3-31 the client software at the mobile terminal 102 encrypts, and optionally packs, the outgoing e-mail message and transmits it via the tunnel to the messaging centre 110. The messaging centre 110 does not immediately know the sender of the e-mail message or the required decryption key. But the messaging centre 110 does know the identifier of the tunnel 120, and it employs the association triplet 122 to retrieve the decryption key 122C and the mobile terminal user's e-mail address 122A. The latter is not included in the e-mail message transmitted over the wireless interface 118 in order to load the wireless interface as little as possible. In step 3-32, the messaging centre 110 employs the decryption key 122C to decrypt the e-mail message. It also inserts the mobile terminal user's e-mail address 122A, which is the same as the host system's e-mail address because they share the same e-mail account. In step 3-33 the messaging centre 110 signals the e-mail server 108 to send a conventional reply message. In step 3-34 the e-mail server 108 stores a copy of the message in its “sent items” folder. Because the messaging centre 110 signals the e-mail server 108 to send a conventional reply message, the recipient of the message has no way of knowing that the user actually used the mobile terminal to initiate the message, and the desired transparency is achieved. A benefit of the transparency is that when the external terminal 104 sends a further reply, its user does not need to decide whether to send the reply to the host system or to the mobile terminal.
  • [0037]
    The final phase, steps 3-41 to 3-43, relate to deletion of an e-mail message. In response to the mobile terminal user's deletion command, the mobile terminal 102 sends a control message in step 3-41 to the messaging centre 110. In step 3-42 it signals the e-mail server 108 to delete the message, and in step 3-43 the message is moved to the “deleted items” folder, again achieving complete transparency between the host system and the mobile terminal.
  • [0038]
    As a further example of control messages, the user of the mobile terminal 102 may wish to explicitly move an e-mail message to a particular folder. In this case the signalling is analogous to steps 3-41 to 3-43, except that the message is not deleted but moved to a different folder. Only the control message has to be sent via the wireless interface, not the actual e-mail message.
  • [0039]
    FIG. 4 shows information flows in mobile-terminated e-mail transmission. Reference numeral 400 denotes an e-mail message as it appears on the fixed network side of the wireless interface 118. The e-mail message 400 is sent by an external e-mail terminal 104 and processed by the host system 100, the e-mail server 108 and/or the messaging centre 110. For the purposes of this description it comprises a source address field 401, a destination address field 402, a subject field 403, a message body field 404 and, optionally, one or more attachments 405. There may be other fields, such as cc (carbon copy) or bcc (blind carbon copy) but they can be ignored in this discussion.
  • [0040]
    The messaging centre 110 comprises an encryption and packing logic 422 that encrypts, and optionally packs (compresses), most of the fields of the e-mail message 400. However, the destination address field 402 is not processed because the mobile terminal will generate it internally. The mobile terminal comprises a decryption and unpacking logic 424 whose operation is inverse to the encryption and packing logic 422.
  • [0041]
    It is also advantageous to implement a filtering logic 430 that filters out attachments that exceed a threshold size, which is preferably user-settable. This means that the user is able to set an upper limit for attachments that will be sent to the mobile terminal. Omitting attachments saves resources in the wireless interface and the mobile terminal. Instead of filtering long attachments, or in addition to it, the filtering logic 430 may be configured to cut out portions of an e-mail message body that exceeds a threshold size. Reference numeral 410 denotes the e-mail message as received and processed by the mobile terminal. Instead of size-based filtering, or in addition to it, the filtering logic may employ type-based filtering that filters out attachment types that the mobile terminal is not able to process. For instance, if the mobile terminal does not have a suitable codec for certain types of video clips, it is pointless to send such video clips to the mobile terminal.
  • [0042]
    FIG. 5 shows information flows in mobile-originated e-mail transmission. Reference numeral 500 denotes an e-mail message generated at the mobile terminal in response to a user input received via the terminal's user interface. The e-mail message 500 is encrypted, and optionally packed, by an encryption and packing logic 522 that operates similarly to the logic 422 in the messaging centre. Reference numeral 510 denotes the same e-mail message after processing by a decryption and unpacking logic 524 that reverses the encryption and packing by the logic 522.
  • [0043]
    The information flows in FIG. 5 are largely analogous to those in FIG. 4, and a detailed description is omitted. However, in this direction the source address, instead of the destination address, is omitted from the packet sent over the wireless interface. In either direction, the e-mail address shared between the host system 100 and the mobile terminal 102 is not transmitted over the wireless interface. Another difference to FIG. 4 is absence of the size/type-based filtering logic 430, because in mobile-originated messages the user can each time make the decision whether or not to include attachments.
  • [0044]
    FIG. 6 shows an enhanced embodiment in which some of the functions of the messaging centre are performed by a separate connectivity function. In the embodiments described so far the messaging centre 110 was responsible for data security issues and traffic coordination to/from the access network. In the embodiment shown in FIG. 6 a dedicated connectivity function 600 is responsible for the data security issues. FIG. 6 shows an arrangement in which the connectivity function 600 is 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 600 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 600 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 network operators, or they 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 600 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 600 in their host systems 100, such connectivity functions bypass the connectivity function in the messaging centre 110 and address the messaging centre 110 directly.
  • [0045]
    In the embodiment shown in FIGS. 1 to 3, the messaging centre maintained an association 122 that joined the e-mail address 122A, terminal identifier 122B (which may or may not be the same as the e-mail address), encryption information 122C and the temporary wireless identity 122D of the mobile terminal. In the embodiment shown in FIGS. 6 and 7, the association is split into two, such that the connectivity function 600 maintains a first association 610 between the e-mail address 122A, terminal identifier 122B and the encryption information 122C, while the messaging centre 110 maintains a second association 612 between the terminal identifier 122B (or e-mail address 122A) and the temporary wireless identity 122D of the mobile terminal. Thus in this embodiment the messaging centre 110 does not know or need to know the encryption information 122C, which means that it only forwards traffic without being able to interpret it.
  • [0046]
    A further change caused by the separation (at least logical and, optionally, physical separation) of the connectivity function 600 from the messaging centre 110 is the fact that in step 2-4 of FIG. 2, the mobile terminal's activation code (or any encryption information based on it) is not delivered to the messaging centre 110 but to the connectivity function 600.
  • [0047]
    FIG. 7 shows traffic flow in the embodiment shown in FIG. 6. An extensive messaging scenario was described in connection with FIG. 3, and the description of FIG. 7 is restricted to the differences caused by the separate connectivity function. In step 7-10, the e-mail server 108 sends an incoming e-mail message to the connectivity function 600 (cf. steps 3-10 and 3-12 in FIG. 3). In step 7-11, the connectivity function 600 encrypts, and optionally packs, the e-mail message. The packing comprises one or more of the following: data compression, omission of redundant fields, omission of long attachments and shortening message bodies (cf. step 3-13 in FIG. 3 and items 422 and 430 in FIG. 4). In step 7-12, the connectivity function 600 sends the encrypted and packed e-mail message to the messaging centre 110. Up to this point, the recipient of the e-mail message has been identified based on the e-mail address 122A. In step 7-13, the messaging centre 110 forwards the encrypted and packed e-mail message via the access network to the mobile terminal, but in this step the recipient of the e-mail message is identified based on the temporary wireless identity 122D of the mobile terminal. In step 7-14 the mobile terminal decrypts and unpacks the e-mail message. The unpacking comprises data decompression and/or regeneration of redundant fields (cf. step 3-15 in FIG. 3 and item 424 in FIG. 4). Steps 7-20 through 7-25 relate to mobile-originated e-mail transmission, and the steps performed are self-explanatory based on the above descriptions.
  • [0048]
    As shown on the bottom row of FIG. 7, between the e-mail server 108 and the connectivity function 600, traffic is identified based on the e-mail address 122A. Between the connectivity function 600 and the messaging centre 110 traffic is identified based on the terminal identifier 122B. Finally, between the messaging centre 110 and the mobile terminal 102, traffic is identified based on the temporary wireless identity 122D, such as the tunnel identifier, TLLI or TMSI.
  • [0049]
    It is readily apparent to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The invention and its embodiments are not limited to the examples described above but may vary within the scope of the claims.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4807182 *Mar 12, 1986Feb 21, 1989Advanced Software, Inc.Apparatus and method for comparing data groups
US4897781 *Feb 13, 1987Jan 30, 1990International Business Machines CorporationSystem and method for using cached data at a local node after re-opening a file at a remote node in a distributed networking environment
US5283856 *Oct 4, 1991Feb 1, 1994Beyond, Inc.Event-driven rule-based messaging system
US5384892 *Dec 31, 1992Jan 24, 1995Apple Computer, Inc.Dynamic language model for speech recognition
US5386564 *Feb 24, 1993Jan 31, 1995Hewlett-Packard CompanyConversion of data and objects across classes in an object management system
US5392390 *Apr 10, 1992Feb 21, 1995Intellilink Corp.Method for mapping, translating, and dynamically reconciling data between disparate computer platforms
US5487100 *May 17, 1994Jan 23, 1996Motorola, Inc.Electronic mail message delivery system
US5491703 *Jun 29, 1993Feb 13, 1996Sgs-Thomson Microelectronics Ltd.Cam with additional row cells connected to match line
US5493692 *Dec 3, 1993Feb 20, 1996Xerox CorporationSelective delivery of electronic messages in a multiple computer system based on context and environment of a user
US5600834 *Apr 5, 1995Feb 4, 1997Mitsubishi Electric Information Technology Center America, Inc.Method and apparatus for reconciling different versions of a file
US5603054 *Jun 7, 1995Feb 11, 1997Xerox CorporationMethod for triggering selected machine event when the triggering properties of the system are met and the triggering conditions of an identified user are perceived
US5604788 *Mar 16, 1995Feb 18, 1997Motorola, Inc.Wireless messaging system with electronic mail replication
US5706502 *Mar 25, 1996Jan 6, 1998Sun Microsystems, Inc.Internet-enabled portfolio manager system and method
US5706507 *Jul 5, 1995Jan 6, 1998International Business Machines CorporationSystem and method for controlling access to data located on a content server
US5710918 *Jun 7, 1995Jan 20, 1998International Business Machines CorporationMethod for distributed task fulfillment of web browser requests
US5713019 *Oct 26, 1995Jan 27, 1998Keaten; Timothy M.Iconic access to remote electronic monochrome raster data format document repository
US5715403 *Nov 23, 1994Feb 3, 1998Xerox CorporationSystem for controlling the distribution and use of digital works having attached usage rights where the usage rights are defined by a usage rights grammar
US5717925 *Jun 5, 1996Feb 10, 1998International Business Machines CorporationInformation catalog system with object-dependent functionality
US5721908 *Jun 7, 1995Feb 24, 1998International Business Machines CorporationComputer network for WWW server data access over internet
US5721914 *Sep 14, 1995Feb 24, 1998Mci CorporationSystem and method for hierarchical data distribution
US5857201 *Jun 18, 1996Jan 5, 1999Wright Strategies, Inc.Enterprise connectivity to handheld devices
US5862223 *Jul 24, 1996Jan 19, 1999Walker Asset Management Limited PartnershipMethod and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce
US5867665 *Mar 24, 1997Feb 2, 1999Pfn, IncDomain communications server
US6016478 *Aug 13, 1996Jan 18, 2000Starfish Software, Inc.Scheduling system with methods for peer-to-peer scheduling of remote users
US6016520 *Jul 14, 1995Jan 18, 2000Microsoft CorporationMethod of viewing at a client viewing station a multiple media title stored at a server and containing a plurality of topics utilizing anticipatory caching
US6018762 *Mar 31, 1998Jan 25, 2000Lucent Technologies Inc.Rules-based synchronization of mailboxes in a data network
US6170014 *Mar 18, 1999Jan 2, 2001Community Learning And Information NetworkComputer architecture for managing courseware in a shared use operating environment
US6173312 *Jul 9, 1997Jan 9, 2001Hitachi, Ltd.System for reliably connecting a client computer to a server computer
US6173446 *Feb 2, 1999Jan 9, 2001Ultimus, Inc.Apparatus for licensing software applications
US6175831 *Jan 17, 1997Jan 16, 2001Six Degrees, Inc.Method and apparatus for constructing a networking database and system
US6178419 *Jul 18, 1997Jan 23, 2001British Telecommunications PlcData access system
US6181935 *May 8, 1997Jan 30, 2001Software.Com, Inc.Mobility extended telephone application programming interface and method of use
US6336117 *Apr 30, 1999Jan 1, 2002International Business Machines CorporationContent-indexing search system and method providing search results consistent with content filtering and blocking policies implemented in a blocking engine
US6336138 *Aug 25, 1998Jan 1, 2002Hewlett-Packard CompanyTemplate-driven approach for generating models on network services
US6505214 *Sep 28, 1999Jan 7, 2003Microsoft CorporationSelective information synchronization based on implicit user designation
US6847974 *Jul 25, 2001Jan 25, 2005Us Search.Com IncMethod and apparatus for intelligent data assimilation
US6985933 *May 30, 2000Jan 10, 2006International Business Machines CorporationMethod and system for increasing ease-of-use and bandwidth utilization in wireless devices
US6985983 *Mar 1, 2001Jan 10, 2006Hewlett-Packard Development Company, L.P.Translating device adapter having a common command set for interfacing multiple types of redundant storage devices to a host processor
US6986061 *Nov 20, 2000Jan 10, 2006International Business Machines CorporationIntegrated system for network layer security and fine-grained identity-based access control
US6987734 *Apr 20, 2001Jan 17, 2006Clear Channel Wireless, Inc.Provision of digital data via multiple broadcasts
US6990472 *Oct 23, 2001Jan 24, 2006Starpound CorporationTelecommunications initiated data fulfillment system
US6993326 *Apr 2, 2001Jan 31, 2006Bellsouth Intellectual Property CorporationSystem and method for providing short message targeted advertisements over a wireless communications network
US6993327 *Oct 29, 2001Jan 31, 2006Motorola, Inc.Multicast distribution of presence information for an instant messaging system
US7162241 *May 16, 2003Jan 9, 2007Lg Electronics Inc.Method for managing multicast group in mobile communication system
US7165727 *Feb 24, 2004Jan 23, 2007Sun Microsystems, Inc.Method and apparatus for installing an application onto a smart card
US7289792 *May 25, 1999Oct 30, 2007Nokia CorporationMethod for transmitting multimedia messages and a multimedia message communication system
US7324473 *Oct 7, 2003Jan 29, 2008Accenture Global Services GmbhConnector gateway
US7483036 *Jul 15, 2005Jan 27, 2009Canon Kabushiki KaishaReducing the number of compositing operations performed in a pixel sequential rendering system
US7643818 *Nov 21, 2005Jan 5, 2010Seven Networks, Inc.E-mail messaging to/from a mobile terminal
US7644166 *Dec 30, 2003Jan 5, 2010Aol LlcSource audio identifiers for digital communications
US7650416 *Aug 12, 2003Jan 19, 2010Riverbed TechnologyContent delivery for client-server protocols with user affinities using connection end-point proxies
US7877703 *Sep 14, 2005Jan 25, 2011Seven Networks, Inc.Intelligent rendering of information in a limited display environment
US8107921 *Jan 11, 2008Jan 31, 2012Seven Networks, Inc.Mobile virtual network operator
US20020002478 *Dec 14, 2000Jan 3, 2002Garret SwartMethods for managing yields of engaged services created from reservable services available in a database-driven transaction system
US20020002591 *Jul 2, 2001Jan 3, 2002Pekka KetolaMethod, terminal and system for controlling several remote mailboxes
US20020007303 *Apr 30, 2001Jan 17, 2002Brookler Brent D.System for conducting electronic surveys
US20020013727 *Feb 8, 2001Jan 31, 2002Lee Seong RyulSystem for advertising on a network by displaying guide codes
US20030005151 *Aug 12, 2002Jan 2, 2003Ullman Craig D.Enhanced video programming system and method for providing a distributed community network
US20030014491 *Jun 28, 2001Jan 16, 2003Horvitz Eric J.Methods for and applications of learning and inferring the periods of time until people are available or unavailable for different forms of communication, collaboration, and information access
US20030023692 *Nov 16, 2001Jan 30, 2003Fujitsu LimitedElectronic message delivery system, electronic message delivery managment server, and recording medium in which electronic message delivery management program is recorded
US20040002324 *Sep 13, 2002Jan 1, 2004Sonera OyjTransaction-based service billing in a telecommunication system
US20040006630 *Mar 27, 2003Jan 8, 2004John FriendSystem and method for providing provisioning and upgrade services for a wireless device
US20040015504 *Jul 17, 2002Jan 22, 2004Rafiul AhadSystem and method for caching data for a mobile application
US20050002501 *Jul 21, 2004Jan 6, 2005Metro One Telecommunications, Inc.Technique for providing personalized information and communications services
US20050002508 *Jul 21, 2004Jan 6, 2005Metro One Telecommunications, Inc.Technique for providing personalized information and communications services
US20050002509 *Jul 21, 2004Jan 6, 2005Metro One Telecommunications, Inc.Technique for providing personalized information and communications services
US20050002510 *Jul 21, 2004Jan 6, 2005Metro One Telecommunications, Inc.Technique for providing personalized information and communications services
US20050010694 *Aug 2, 2004Jan 13, 2005Clarinet Systems, Inc.Method and interface for facilitating communication between a cellular telephone or similar wireless device and other devices or systems via an interface
US20050015432 *May 13, 2004Jan 20, 2005Cohen Hunter C.Deriving contact information from emails
US20050021750 *Jun 16, 2003Jan 27, 2005Friendster Inc., A California CorporationSystem, method and apparatus for connecting users in an online computer system based on their relationships within social networks
US20050022000 *Apr 7, 2004Jan 27, 2005Fuji Xerox Co., Ltd.Illegal communication detector, illegal communication detector control method, and storage medium storing program for illegal communication detector control
US20050022182 *Jul 23, 2003Jan 27, 2005Nokia CorporationSystem, and associated method, for downloading an application
US20060012672 *Jun 30, 2005Jan 19, 2006Thies SchraderMonitoring and control of administration systems
US20060020525 *Nov 19, 2001Jan 26, 2006Csg Systems, Inc.System and method for providing access to network services
US20060020580 *Jul 22, 2004Jan 26, 2006International Business Machines CorporationMethod and system for providing aggregate data access
US20060020804 *Apr 25, 2005Jan 26, 2006Microsoft CorporationCross-pollination synchronization of data
US20060020947 *Oct 15, 2004Jan 26, 2006Mika HallamaaArranging management operations in management system
US20060031300 *Aug 29, 2003Feb 9, 2006Kock Martijn W MMethod and system for the phased retrieval of data
US20060085503 *May 20, 2003Apr 20, 2006William StoyeData communications system using e-mail tunnelling
US20070005738 *Jun 29, 2005Jan 4, 2007Microsoft CorporationAutomated remote scanning of a network for managed and unmanaged devices
US20070006317 *Jun 27, 2006Jan 4, 2007Sony Ericsson Mobile Communications Japan, Inc.Mobile terminal, contents delivery system, and contents reproduction program
US20070011367 *Jun 23, 2005Jan 11, 2007Research In Motion LimitedSystem and method for automatically responding to a received communication
US20070019610 *Jun 21, 2006Jan 25, 2007Seven Networks International OyMaintaining an IP connection in a mobile network
US20070022118 *Jul 7, 2006Jan 25, 2007Layne Kevin ACollection agency data access method
US20080001717 *Mar 27, 2007Jan 3, 2008Trevor FiatalSystem and method for group management
US20080008095 *Jul 10, 2006Jan 10, 2008International Business Machines CorporationMethod for Distributed Traffic Shaping across a Cluster
US20080009344 *Jul 9, 2007Jan 10, 2008IgtIntegrating remotely-hosted and locally rendered content on a gaming device
US20080016236 *Jul 16, 2007Jan 17, 2008Bigfoot Networks, Inc.Data buffering and notification system and methods thereof
US20090010204 *Apr 10, 2008Jan 8, 2009Hart Communication FoundationSupport for Network Management and Device Communications in a Wireless Network
US20090010259 *Jul 8, 2007Jan 8, 2009Alexander SirotkinDevice, system, and method of classification of communication traffic
US20090012841 *Feb 27, 2008Jan 8, 2009Yahoo! Inc.Event communication platform for mobile device users
US20090016526 *Sep 16, 2008Jan 15, 2009Seven Networks, Inc.Method and apparatus for intercepting events in a communication system
US20090019485 *Sep 18, 2008Jan 15, 2009United Video Properties, Inc.Interactive television program guide system and method with niche hubs
US20090019532 *Dec 17, 2004Jan 15, 2009Nokia CorporationCommunication system
US20090024794 *Sep 3, 2007Jan 22, 2009Oracle International CorporationEnhanced Access To Data Available In A Cache
US20090031006 *Jul 10, 2007Jan 29, 2009Johnson William JSystem and method for alerting a first mobile data processing system nearby a second mobile data processing system
US20120005276 *Jan 5, 2012Guo Katherine HMethod and apparatus for reducing application update traffic in cellular networks
US20120008536 *Jan 12, 2012Seven Networks International OyDynamic adjustment of keep-alive message intervals in a mobile network
US20120022980 *Jul 20, 2010Jan 26, 2012Neopost TechnologiesSystem and Method for Managing Postal Accounting Data Using Transient Data Collectors
US20120023190 *Jan 26, 2012Ari BackholmMobile network traffic coordination across multiple applications
US20120023226 *Jan 26, 2012Steve PetersenPrediction of activity session for mobile network use optimization and user experience enhancement
US20120023236 *Jan 26, 2012Ari BackholmDistributed implementation of dynamic wireless traffic policy
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US8010082Oct 19, 2005Aug 30, 2011Seven Networks, Inc.Flexible billing architecture
US8064583Sep 21, 2006Nov 22, 2011Seven Networks, Inc.Multiple data store authentication
US8069166Feb 27, 2006Nov 29, 2011Seven Networks, Inc.Managing user-to-user contact with inferred presence information
US8078158Jun 26, 2008Dec 13, 2011Seven Networks, Inc.Provisioning applications for a mobile device
US8107921Jan 11, 2008Jan 31, 2012Seven Networks, Inc.Mobile virtual network operator
US8116214Nov 30, 2005Feb 14, 2012Seven Networks, Inc.Provisioning of e-mail settings for a mobile terminal
US8127342Sep 23, 2010Feb 28, 2012Seven Networks, Inc.Secure end-to-end transport through intermediary nodes
US8166164Oct 14, 2011Apr 24, 2012Seven Networks, Inc.Application and network-based long poll request detection and cacheability assessment therefor
US8190701Nov 1, 2011May 29, 2012Seven Networks, Inc.Cache defeat detection and caching of content addressed by identifiers intended to defeat cache
US8204953Nov 1, 2011Jun 19, 2012Seven Networks, Inc.Distributed system for cache defeat detection and caching of content addressed by identifiers intended to defeat cache
US8209709Jul 5, 2010Jun 26, 2012Seven Networks, Inc.Cross-platform event engine
US8291076Mar 5, 2012Oct 16, 2012Seven Networks, Inc.Application and network-based long poll request detection and cacheability assessment therefor
US8316098Nov 20, 2012Seven Networks Inc.Social caching for device resource sharing and management
US8326985Nov 1, 2011Dec 4, 2012Seven Networks, Inc.Distributed management of keep-alive message signaling for mobile network resource conservation and optimization
US8356080Jan 15, 2013Seven Networks, Inc.System and method for a mobile device to use physical storage of another device for caching
US8364181Dec 10, 2007Jan 29, 2013Seven Networks, Inc.Electronic-mail filtering for mobile devices
US8412675Feb 24, 2006Apr 2, 2013Seven Networks, Inc.Context aware data presentation
US8417823Nov 18, 2011Apr 9, 2013Seven Network, Inc.Aligning data transfer to optimize connections established for transmission over a wireless network
US8438633Dec 18, 2006May 7, 2013Seven Networks, Inc.Flexible real-time inbox access
US8468126Dec 14, 2005Jun 18, 2013Seven Networks, Inc.Publishing data in an information community
US8484314Oct 14, 2011Jul 9, 2013Seven Networks, Inc.Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US8494510Dec 6, 2011Jul 23, 2013Seven Networks, Inc.Provisioning applications for a mobile device
US8539040Feb 28, 2012Sep 17, 2013Seven Networks, Inc.Mobile network background traffic data management with optimized polling intervals
US8549587Feb 14, 2012Oct 1, 2013Seven Networks, Inc.Secure end-to-end transport through intermediary nodes
US8561086May 17, 2012Oct 15, 2013Seven Networks, Inc.System and method for executing commands that are non-native to the native environment of a mobile device
US8621075Apr 27, 2012Dec 31, 2013Seven Metworks, Inc.Detecting and preserving state for satisfying application requests in a distributed proxy and cache system
US8635339Aug 22, 2012Jan 21, 2014Seven Networks, Inc.Cache state management on a mobile device to preserve user experience
US8693494Mar 31, 2008Apr 8, 2014Seven Networks, Inc.Polling
US8700728May 17, 2012Apr 15, 2014Seven Networks, Inc.Cache defeat detection and caching of content addressed by identifiers intended to defeat cache
US8738050Jan 7, 2013May 27, 2014Seven Networks, Inc.Electronic-mail filtering for mobile devices
US8738909 *Oct 26, 2011May 27, 2014Blackberry LimitedForwarding E-mail from a wireless device
US8750123Jul 31, 2013Jun 10, 2014Seven Networks, Inc.Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network
US8761756Sep 13, 2012Jun 24, 2014Seven Networks International OyMaintaining an IP connection in a mobile network
US8774844Apr 8, 2011Jul 8, 2014Seven Networks, Inc.Integrated messaging
US8775631Feb 25, 2013Jul 8, 2014Seven 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
US8782222Sep 5, 2012Jul 15, 2014Seven NetworksTiming of keep-alive messages used in a system for mobile network resource conservation and optimization
US8787947Jun 18, 2008Jul 22, 2014Seven Networks, Inc.Application discovery on mobile devices
US8793305Dec 13, 2007Jul 29, 2014Seven Networks, Inc.Content delivery to a mobile device from a content service
US8799410Apr 13, 2011Aug 5, 2014Seven Networks, Inc.System and method of a relay server for managing communications and notification between a mobile device and a web access server
US8805334Sep 5, 2008Aug 12, 2014Seven Networks, Inc.Maintaining mobile terminal information for secure communications
US8805425Jan 28, 2009Aug 12, 2014Seven Networks, Inc.Integrated messaging
US8811952May 5, 2011Aug 19, 2014Seven Networks, Inc.Mobile device power management in data synchronization over a mobile network with or without a trigger notification
US8812695Apr 3, 2013Aug 19, 2014Seven Networks, Inc.Method and system for management of a virtual network connection without heartbeat messages
US8831561Apr 28, 2011Sep 9, 2014Seven Networks, IncSystem and method for tracking billing events in a mobile wireless network for a network operator
US8832228Apr 26, 2012Sep 9, 2014Seven Networks, Inc.System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief
US8838744Jan 28, 2009Sep 16, 2014Seven Networks, Inc.Web-based access to data objects
US8838783Jul 5, 2011Sep 16, 2014Seven Networks, Inc.Distributed caching for resource and mobile network traffic management
US8839412Sep 13, 2012Sep 16, 2014Seven Networks, Inc.Flexible real-time inbox access
US8843153Nov 1, 2011Sep 23, 2014Seven Networks, Inc.Mobile traffic categorization and policy for network use optimization while preserving user experience
US8849902Jun 24, 2011Sep 30, 2014Seven Networks, Inc.System for providing policy based content service in a mobile network
US8861354Dec 14, 2012Oct 14, 2014Seven Networks, Inc.Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization
US8862657Jan 25, 2008Oct 14, 2014Seven Networks, Inc.Policy based content service
US8868753Dec 6, 2012Oct 21, 2014Seven Networks, Inc.System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation
US8873411Jan 12, 2012Oct 28, 2014Seven Networks, Inc.Provisioning of e-mail settings for a mobile terminal
US8874761Mar 15, 2013Oct 28, 2014Seven Networks, Inc.Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US8886176Jul 22, 2011Nov 11, 2014Seven Networks, Inc.Mobile application traffic optimization
US8903954Nov 22, 2011Dec 2, 2014Seven Networks, Inc.Optimization of resource polling intervals to satisfy mobile device requests
US8909192Aug 11, 2011Dec 9, 2014Seven Networks, Inc.Mobile virtual network operator
US8909202Jan 7, 2013Dec 9, 2014Seven Networks, Inc.Detection and management of user interactions with foreground applications on a mobile device in distributed caching
US8909759Oct 12, 2009Dec 9, 2014Seven Networks, Inc.Bandwidth measurement
US8914002Aug 11, 2011Dec 16, 2014Seven Networks, Inc.System and method for providing a network service in a distributed fashion to a mobile device
US8918503Aug 28, 2012Dec 23, 2014Seven Networks, Inc.Optimization of mobile traffic directed to private networks and operator configurability thereof
US8930689Sep 28, 2011Jan 6, 2015Mcafee, Inc.Securing email conversations
US8966066Oct 12, 2012Feb 24, 2015Seven Networks, Inc.Application and network-based long poll request detection and cacheability assessment therefor
US8977755Dec 6, 2012Mar 10, 2015Seven Networks, Inc.Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation
US8984581Jul 11, 2012Mar 17, 2015Seven Networks, Inc.Monitoring mobile application activities for malicious traffic on a mobile device
US8989728Sep 7, 2006Mar 24, 2015Seven Networks, Inc.Connection architecture for a mobile network
US9002828Jan 2, 2009Apr 7, 2015Seven Networks, Inc.Predictive content delivery
US9009250Dec 7, 2012Apr 14, 2015Seven Networks, Inc.Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation
US9021021Dec 10, 2012Apr 28, 2015Seven Networks, Inc.Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system
US9043433May 25, 2011May 26, 2015Seven Networks, Inc.Mobile network traffic coordination across multiple applications
US9043731Mar 30, 2011May 26, 2015Seven Networks, Inc.3D mobile user interface with configurable workspace management
US9047142Dec 16, 2010Jun 2, 2015Seven Networks, Inc.Intelligent rendering of information in a limited display environment
US9049179Jan 20, 2012Jun 2, 2015Seven Networks, Inc.Mobile network traffic coordination across multiple applications
US9055102Aug 2, 2010Jun 9, 2015Seven Networks, Inc.Location-based operations and messaging
US9060032May 9, 2012Jun 16, 2015Seven Networks, Inc.Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic
US9065765Oct 8, 2013Jun 23, 2015Seven Networks, Inc.Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
US9077630Jul 8, 2011Jul 7, 2015Seven Networks, Inc.Distributed implementation of dynamic wireless traffic policy
US9084105Apr 19, 2012Jul 14, 2015Seven Networks, Inc.Device resources sharing for network resource conservation
US9100873Sep 14, 2012Aug 4, 2015Seven Networks, Inc.Mobile network background traffic data management
US9131397Jun 6, 2013Sep 8, 2015Seven Networks, Inc.Managing cache to prevent overloading of a wireless network due to user activity
US9161258Mar 15, 2013Oct 13, 2015Seven Networks, LlcOptimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion
US9172684 *Sep 6, 2013Oct 27, 2015Mitsubishi Electric CorporationInformation gathering system
US9173128Mar 6, 2013Oct 27, 2015Seven Networks, LlcRadio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
US9203864Feb 4, 2013Dec 1, 2015Seven Networks, LlcDynamic categorization of applications for network access in a mobile network
US9208123Dec 7, 2012Dec 8, 2015Seven Networks, LlcMobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor
US9225524 *May 26, 2014Dec 29, 2015Blackberry LimitedForwarding e-mail from a wireless device
US9239800Jul 11, 2012Jan 19, 2016Seven Networks, LlcAutomatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network
US9241314Mar 15, 2013Jan 19, 2016Seven Networks, LlcMobile device with application or context aware fast dormancy
US9251193Oct 28, 2007Feb 2, 2016Seven Networks, LlcExtending user relationships
US20120278620 *Nov 1, 2012Research In Motion LimitedForwarding E-Mail From A Wireless Device
US20140006774 *Sep 6, 2013Jan 2, 2014Mitsubishi Electric CorporationInformation gathering system, terminal unit, program for information gathering, and program for a terminal
US20140258722 *May 26, 2014Sep 11, 2014Blackberry LimitedForwarding E-Mail From A Wireless Device
USRE45348Mar 16, 2012Jan 20, 2015Seven Networks, Inc.Method and apparatus for intercepting events in a communication system
WO2013049078A1 *Sep 25, 2012Apr 4, 2013Mcafee, Inc.Securing email conversations
Classifications
U.S. Classification709/206, 713/150
International ClassificationG06F15/16, H04W4/12, H04L9/00, H04W8/26
Cooperative ClassificationH04L12/5895, H04L51/38, H04L63/18, H04L63/0428, H04L63/08, H04W8/26, H04W4/12, H04W12/06, H04W12/02
European ClassificationH04L63/08, H04L63/04B, H04L63/18, H04L12/58W, H04W12/02, H04W12/06
Legal Events
DateCodeEventDescription
Aug 11, 2008ASAssignment
Owner name: SEVEN NETWORKS INTERNATIONAL OY, FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BACKHOLM, ARI;SALORINNE, SEPPO;SAARILAHTI, ANTTI;AND OTHERS;REEL/FRAME:021460/0624;SIGNING DATES FROM 20060606 TO 20060613
Oct 6, 2014ASAssignment
Owner name: SEVEN NETWORKS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SEVEN NETWORKS INTERNATIONAL OY;REEL/FRAME:033894/0475
Effective date: 20141006
Aug 27, 2015ASAssignment
Owner name: SEVEN NETWORKS, LLC, CALIFORNIA
Free format text: ENTITY CONVERSION;ASSIGNOR:SEVEN NETWORKS, INC.;REEL/FRAME:036485/0059
Effective date: 20150714