System for handling file attachments

• US 7,317,697 B2
• Filed: 11/18/2002
• Issued: 01/08/2008
• Est. Priority Date: 11/16/2001
• Status: Expired due to Fees

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Lewis, John Ervin, Schlieber, Karl J., Lai, Danh Tan, McNamara, Justin
• Primary Examiner(s): Levitan, Dmitry
• Application Number:
  US10/299,409
• Publication Number:
  US 20030095550A1
• Time in Patent Office: 1,877 Days
• Field of Search: 370/310, 370/312, 370/313, 370/432, 370/400, 370/402, 709/206, 709/207, 709/217, 709/229, 709/203
• US Class Current: 370/312
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/308 Route determination based on user's profile, e.g. premium users
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 40/246 Connectivity information discovery
• CPC Class Codes: H04W 40/248 : Connectivity information update
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 88/184 : Messaging devices, e.g. message centre
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: H04W 92/06 : between gateways and public network devices

Abstract

A method and system for forwarding an attachment sent to a wireless device includes receiving a message with an attachment within a wireless network, detecting the attachment, accessing a forwarding address associated with the message, and sending the attachment to the forwarding address.

Claims

1. A method for handling a message including an attachment sent to a wireless device within a wireless network, wherein the wireless device is not capable of displaying the attachment, the method comprising:

receiving via a first network transport bus a message with an attachment within the wireless network, wherein the first network transport bus communicatively connects a plurality of network elements and utilizes a common messaging format for communication among and between the network elements, wherein the network elements comprise a plurality of adaptive routing concentrators, a plurality of routing and validation entities, and a plurality of network databases all communicatively connected to the first network transport bus, and wherein at least one routing and validation entity is communicatively connected to a user alias database and a routing and validation database via a second network transport bus;

detecting the attachment;

translating with at least one adaptive routing concentrator the received message and the received attachment into the common messaging format for storage in at least one network database, wherein the network database is communicatively connected to the first network transport bus;

retrieving the message from the first network transport bus in the common messaging format with at least one routing and validation entity and validating the retrieved message by comparing at least one of an originating address or a destination address to a list of approved addresses, wherein the list of approved addresses is stored in the user alias database that is communicatively connected to the first network transport bus;

accessing with at least one routing and validation entity the routing and validation database to locate a forwarding address associated with the wireless device, wherein a user of the wireless device had selected and stored information relating to a preferred destination device in the routing and validation database; and

sending the attachment to the preferred forwarding address.

2. The method of claim 1, further comprising:

sending an acknowledgement message to the wireless device indicating that the attachment has been forwarded to the preferred destination device.

3. The method of claim 1, wherein detecting the attachment further comprises:

reading a header of the message to determine if an attachment is attached to the message.

4. The method of claim 1, wherein detecting the attachment further comprises:

reading a header of the message to determine a type of attachment.

5. The method of claim 1, wherein detecting the attachment further comprises:

determining a size of the message and ascertaining that an attachment is present when the size of the message is larger than a predetermined threshold size.

6. The method of claim 1, wherein detecting the attachment further comprises:

reading the attachment to determine a type of the attachment based on information included in a header of the attachment.

7. The method of claim 1, wherein prior to sending the attachment to the forwarding address, the method further comprises:

translating the attachment into a format associated with the receiving device; and

appending the forwarding address to the attachment.

8. The method of claim 1, wherein the detecting step further comprises detecting the attachment with an adaptive routing concentrator (ARC), a routing and validation entity (RAVE), a data storage and routing terminal (DART), a Mail Transfer Agent (MTA) or a Mail Transfer Gateway (MTG).

9. The method of claim 1, further comprising:

retrieving the attachment from the at least one network database communicatively connected to the first network transport bus; and

publishing the attachment on the first network transport bus within the wireless network.

10. The method of claim 1, further comprising:

determining a type of attachment included with the message and forwarding the attachment to a preferred destination device based on the type of attachment.

11. A method for forwarding an attachment sent to a wireless device within a wireless network, the method comprising:

receiving a message with an attachment within the wireless network via a first network transport bus, wherein the message is formatted in a first messaging format, wherein the first network transport bus communicatively connects a plurality of network elements and utilizes a common messaging format for communication among and between the network elements, wherein the network elements comprise a plurality of adaptive routing concentrators, a plurality of routing and validation entities, a plurality of data storage and routing terminals, and a plurality of network databases all communicatively connected to the first network transport bus, and wherein at least one routing and validation entity is communicatively connected to a user alias database and a routing and validation database via a second network transport bus;

translating the first formatted message and attachment with at least one adaptive routing concentrator into the common messaging format that can be retrieved by any network device communicatively coupled to the first network transport bus;

retrieving the message from the first network transport bus in the common messaging format with at least one routing and validation entity and validating the retrieved message by comparing at least one of an originating address or a destination address to a list of approved addresses, wherein the list of approved addresses is stored in the user alias database;

accessing the routing and validation database with at least one routing and validation entity to determine a forwarding address associated with the wireless device, to which the attachment is to be sent, wherein the routing and validation database includes subscriber'"'"'s information stored therein;

storing with at least one data storage and routing terminal the message and attachment in the common messaging format in at least one network database communicatively connected to the at least one data storage and routing terminal via a third network transport bus within the wireless network;

translating with at least one adaptive routing concentrator the attachment from the common messaging format to a format suitable for the forwarding device; and

sending the attachment to the forwarding device associated with the forwarding address.

12. The method of claim 11, further comprising:

determining a type of attachment included with the message and forwarding the attachment to a preferred forwarding device based on the type of attachment.

13. A system for handling a message and an attachment sent to a wireless device within a wireless network, the system comprising:

a component for receiving a message with an attachment within the wireless network via a first network transport bus, wherein the first network transport bus communicatively connects a plurality of network elements and utilizes a common messaging format for communication among and between the network elements, wherein the network elements comprise a plurality of adaptive routing concentrators, a plurality of routing and validation entities, a plurality of data storage and routing terminals, and a plurality of network databases all communicatively connected to the first network transport bus, and wherein at least one routing and validation entity is communicatively connected to a user alias database and a routing and validation database via a second network transport bus;

a component for detecting the attachment;

an adaptive routing concentrator for translating the received message and attachment into the common messaging format;

a routing and validation entity

for retrieving the published message from the first network transport bus in the common messaging format and validating the received message by comparing at least one of an originating address or a destination address to a list of approved addresses, wherein a user alias database and a routing and validation database are communicatively connected to at least one routing and validation entity via a second network transport bus and wherein the list of approved addresses is stored in the user alias database, and

for accessing at least one routing and validation database to locate a forwarding address associated with the wireless device, wherein a user of the wireless device had previously selected and stored information relating to a preferred destination device in the routing and validation database; and

a component for sending the attachment to the forwarding address.

14. The system of claim 13, further comprising:

a component for sending an acknowledgement message to the wireless device indicating that the attachment has been forwarded to the destination device.

15. The system of claim 13, wherein the component for detecting the attachment is further configured to:

read a header of the message to determine if an attachment is present based on information contained in the header.

16. The system of claim 13, wherein the component for detecting the attachment is further configured to:

read a header of the message to determine a type of attachment based on information contained in the header.

17. The system of claim 13, wherein the component for detecting the attachment is further configured to:

determine a size of the message; and

determine an attachment when the size of the message is greater than a predetermined threshold size.

18. The system of claim 13, wherein the component for detecting the attachment is further configured to:

determine a type of attachment from information included in a header of the attachment.

19. The system of claim 13, wherein the component for accessing the forwarding address is further configured to:

determine if the forwarding address is included in the message.

20. The system of claim 13 further comprising a component for:

storing the attachment in the common messaging format in at least one network database communicatively connected to at least one data storage and routing terminal.

21. The system of claim 20, further comprising a component for:

retrieving the attachment from the at least one network database communicatively connected to the at least one data storage and routing terminal; and

publishing the attachment on the first network transport bus within the wireless network.

22. The system of claim 13, wherein the component for detecting the attachment further comprises an adaptive routing concentrator (ARC), a routing and validation entity (RAVE), a data storage and routing terminal (DART), a Mail Transfer Agent (MTA) or a Mail Transfer Gateway (MTG).

23. The system of claim 13, wherein the component for detecting the attachment further detects a type of attachment and wherein the routing and validation entity locates a preferred destination device based on the type of message detected.