The present embodiment relates to displaying attachments on a portable electronic device, in particular, a method for requesting and viewing an attachment image on a portable electronic device.
Wireless technology has made it possible for email messages to be received and displayed by various portable electronic devices including Personal Digital Assistants (PDAs), for example. Sending email messages including attachments, such as photographs or scanned documents, is becoming increasingly popular, however, most attachments are formatted for a rich desktop or printer experience and generally require a desktop PC with a large screen display for proper viewing. As such, viewing these attachments on the small screens of most portable electronic devices presents a challenge.
When a user makes a request to view an attachment, the request is received at a server where the attachment is scaled down to fit on the portable electronic device screen and then returned to the portable electronic device. When viewing high resolution attachments such as scanned documents, for example, details of the scaled down image are often difficult to distinguish. In order to view text or other details of the scaled down image, the user may enlarge a desired portion by selecting an appropriate menu option. Each time the user requests enlargement of an area of the scaled down image, the request is sent to the server and a higher resolution image of the selected area is returned to the portable electronic device. Often, the enlargement process must be performed multiple times before the user is able to view the details of the entire scanned document.
The embodiment will be better understood with reference to the following Figures in which like numerals denote like parts and in which:
Referring to
It will be appreciated that the portable electronic device 12 is movable within the coverage area and can be moved to coverage areas defined by other base stations. Further, as will be understood by one of ordinary skill in the art, wireless networks include GSM/GPRS, CDPD, TDMA, iDEN Mobitex, DataTAC networks, EDGE or UMTS and broadband networks such as Bluetooth and variants of 802.11.
A server 18 handles wireless client requests from the portable electronic device 12. A firewall, or proxy server, 16, is provided between the server 18 and the Internet 14. The server 18 further operates as an attachment server, which communicates with an email client and an attachment viewer of the portable electronic device 12 to allow a user to view attachments that are received in email messages. While only one server 18 is shown for illustration purposes, a person skilled in the art will understand that the attachment server may alternatively be a separate server.
Referring now to
The portable electronic device 12 is based on a microcomputer including a processor 20 connected to a read-only-memory (ROM) 22 that contains a plurality of applications executable by the processor 20 that enables each portable electronic device 12 to perform certain functions including, for example, PIN message functions, SMS message functions and cellular telephone functions. The processor 20 is also connected to a random access memory unit (RAM) 24 and a persistent storage device 26 which are responsible for various non-volatile storage functions of the portable electronic device 12. The processor 20 receives input from various input devices including a keypad 28. The processor 20 outputs to various output devices including an LCD display 30. A microphone 32 and phone speaker 34 are connected to the processor 20 for cellular telephone functions. The processor 20 is also connected to a modem and radio device 36. The modem and radio device 36 is used to connect to wireless networks and transmit and receive voice and data communications through an antenna 38. A content store 40, which is generally a file storage system for the portable electronic device 12, is also provided.
Referring to
Prior to step 42, the attachment server performs the resize operation on the original image and downloads the resized image to the device 12. In order to perform the resize operation, the attachment server first builds a Document Object Model (DOM) by parsing the attachment document. In this manner, a graph structure is built within the server representing a map of the original image. The original image is then resized based on the requesting device image size limit, or device screen size width and height (in pixels). The DOM structure is disclosed in U.S. Pat. No. 7,451,405, which is herein incorporated by reference.
At step 44, the attachment viewer determines if the original image width is greater than the device display width and/or if the original image height is greater than the device display height. If one or both of the original image width and original image height are greater than the display width and display height, respectively, then the attachment viewer moves to step 46 and displays a “full image” option in an attachment viewer menu 62, which is shown in
As indicated at step 50, if the user invokes the “full image” option from the menu 62 (step 48), the attachment viewer first determines if a full image for the particular attachment was previously requested from the attachment server. Previously requested full images are stored locally on the portable electronic device 12 in the content store 40. Therefore, the attachment viewer searches the content store 40 and if corresponding full image data is available for the requested image, the attachment viewer displays the full image, as indicated at step 56. If no corresponding full image data is found, the attachment viewer requests the “full image” from the attachment server. The request that is sent to the attachment server includes the device screen size as well as calculated width and height parameters, as indicated at step 52. Alternatively, if the user does not invoke the “full image” option, the attachment viewer returns to step 42 and simply continues to display the resized image.
The calculated width and height parameters for the full image are determined as follows. The full image width is equal to 8/3 multiplied by the smaller one of the original image width and the device screen width. The full image height is equal to 8/3 multiplied by the smaller one of the original image height and the device screen height. The aspect ratio of the original image is maintained during the “full image” operation.
If the attachment server successfully resizes the attachment image, the full image is shown on the display 30 of the portable electronic device 12 and saved in the content store 40, as indicated at steps 56 and 57, and the execution logic of
Successful execution of the “full image” option results in an image being returned from the attachment server that is larger and has a higher resolution than the image that is displayed at step 42. An example of a larger, higher resolution full image 64 is shown in
The relationship between the original image, the resized image and the full image is generally shown in
Referring now to
If the separate image component does not exist, the attachment server collects the image binary data from the original image component in memory, as indicated at step 76, and constructs a new image component from the binary data, as indicated at step 78. At step 80, the attachment server caches the DSS image component as an attribute of the original image component in the DOM structure. The DSS binary image data is collected at step 82 and then tailored to create new binary image data based on the calculated width and height parameters and the new binary image data is returned to the attachment viewer of the portable electronic device 12, as indicated at step 84.
In operation, the user of the portable electronic device 12 receives an email message having an attachment and opens the attachment in the attachment viewer. The attachment appears as shown in
A specific embodiment of the present embodiment has been shown and described herein. However, modifications and variations may occur to those skilled in the art. For example, although the portable electronic device 12 has been described having cellular telephone capabilities, the described embodiment is not limited to portable electronic devices having both cellular telephone and email capabilities. A portable electronic device having email capabilities but not cellular telephone capabilities may also be used. All such modifications and variations are believed to be within the sphere and scope of the present embodiment.
The present application is a continuation of U.S. patent application Ser. No. 12/371,136, filed Feb. 13, 2009 now U.S. Pat. No. 7,733,356, entitled “Method for Requesting and Viewing an Attachment Image on a Portable Electronic Device”, which is a continuation of U.S. patent application Ser. No. 11/395,107, filed Mar. 31, 2006, now issued U.S. Pat. No. 7,511,723, also entitled “Method for Requesting and Viewing an Attachment Image on a Portable Electronic Device”. The contents of U.S. patent application Ser. Nos. 12/371,136 and 11/395,107 are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5701500 | Ikeo et al. | Dec 1997 | A |
6141270 | Casper | Oct 2000 | A |
6449639 | Blumberg | Sep 2002 | B1 |
6556217 | Makipaa et al. | Apr 2003 | B1 |
6915333 | Delia et al. | Jul 2005 | B2 |
7038701 | Niemi | May 2006 | B2 |
7072984 | Polonsky et al. | Jul 2006 | B1 |
7209149 | Jogo | Apr 2007 | B2 |
7242493 | Hall et al. | Jul 2007 | B2 |
7536440 | Budd et al. | May 2009 | B2 |
20010051007 | Teshima | Dec 2001 | A1 |
20020016818 | Kirani et al. | Feb 2002 | A1 |
20020062396 | Kakei et al. | May 2002 | A1 |
20020161796 | Sylthe | Oct 2002 | A1 |
20040003117 | McCoy et al. | Jan 2004 | A1 |
20040073873 | Croney et al. | Apr 2004 | A1 |
20040172453 | De Mendonca et al. | Sep 2004 | A1 |
20040183817 | Kaasila | Sep 2004 | A1 |
20050128366 | Cha | Jun 2005 | A1 |
20050193074 | Garland | Sep 2005 | A1 |
20050200610 | Skantze et al. | Sep 2005 | A1 |
20050232581 | Karasawa | Oct 2005 | A1 |
20060031336 | Friedman et al. | Feb 2006 | A1 |
20060055693 | Sylthe et al. | Mar 2006 | A1 |
20060056334 | Yuan et al. | Mar 2006 | A1 |
20060056604 | Sylthe et al. | Mar 2006 | A1 |
20060061550 | Fateh | Mar 2006 | A1 |
20060062362 | Davis | Mar 2006 | A1 |
20060225001 | Sylthe et al. | Oct 2006 | A1 |
20070283247 | Brenneman et al. | Dec 2007 | A1 |
20080028335 | Rohrabaugh et al. | Jan 2008 | A1 |
20080102887 | Sylthe et al. | May 2008 | A1 |
20080188304 | Escalera et al. | Aug 2008 | A1 |
20080214204 | Ramer et al. | Sep 2008 | A1 |
20080316225 | Sylthe et al. | Dec 2008 | A1 |
Number | Date | Country | |
---|---|---|---|
20100235753 A1 | Sep 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12371136 | Feb 2009 | US |
Child | 12767352 | US | |
Parent | 11395107 | Mar 2006 | US |
Child | 12371136 | US |