Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
  • G06F3/0489—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using dedicated keyboard keys or combinations thereof
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M1/00—Substation equipment, e.g. for use by subscribers
  • H04M1/02—Constructional features of telephone sets
  • H04M1/22—Illumination; Arrangements for improving the visibility of characters on dials

Definitions

• the present invention relates to the field of data files, and more particularly, to image data files and related display methods.
• Multi-layer (or multi-page) images can be thought of as a set of images, all typically but not necessarily the same size, which are combined for the purpose of displaying on an output display device.
• multi-layer refers to multiple images in a single file.
• Each image in the file may be referred to as a layer.
• Multi-layer images may be used for image editing, graphic design, and/or animation (such as animation in web pages on the Internet).
• the Graphics Interchange Format (GIF) is widely used as a file format for animation.
• the Graphics Interchange Format is discussed, for example, in U.S. Patent No. 6,714,202.
• the GIF standard includes layers (or multiple images) which may be provided in sequence order.
• Each layer of a GIF file may be of different size and may be positioned using offset coordinates to improve storage efficiency in cases where only small areas contain changes from one layer to the next.
• the GIF standard defines a virtual screen upon which each layer is composed.
• the GIF standard generally uses a control block structure to indicate how the layers in the file are to be displayed.
• Each layer of the file format may be preceded by a control block, which may include: information about the location of the top left corner in the virtual screen, information on how long the layer should be displayed before proceeding to the next layer in the file; and whether the layer should be removed prior to display of a next layer in the file.
• This control block based structure may allow for relatively simple software implementation of the decoder. In fact little additional coding may be required to implement a GIF decoder capable of correctly displaying multi-layer animated GIF images.
• the GIF standard is further discussed in the GIF specification entitled
• methods may be provided for operating an electronic device including a screen and a plurality of lights.
• the method may include providing a plurality of image frames with each image frame defining an image for display on the screen, and providing illumination instructions for the plurality of lights wherein different illumination instructions are associated with different image frames and wherein each illumination instruction defines a respective illumination pattern for the plurality of lights.
• the images defined by the respective image frames may be displayed on the screen. While displaying a first image defined by a first image frame on the screen, a first illumination pattern for the plurality of lights may be provided with the first illumination pattern being defined by a first illumination instruction associated with the first image frame.
• a second illumination pattern for the plurality of lights may be provided with the second illumination pattern being defined by a second illumination instruction associated with the second image frame.
• the first and second illumination patterns may be different.
• Providing the plurality of image frames and providing the illumination instructions may include providing a graphic data file including the plurality of image frames and the associated illumination instructions.
• each image frame may be provided as a different image data block of the graphic data file, and each illumination instruction may be provided as an illumination data block of the graphic data file with each illumination data block being associated with a different image data block.
• Providing the graphic data file may also include providing a plurality of control data blocks with each of the control data blocks being associated with a respective one of the image data blocks and defining a duration for display of the image defined by the respective image data block.
• providing the graphic data file may include providing the graphic data file according to the Graphics Interchange Format (GIF) standard.
• GIF Graphics Interchange Format
• providing the plurality of image frames and providing the plurality of illumination instructions may include providing a first graphic data file including a first image frame and a first illumination instruction, and providing a second graphic data file including a second image frame and a second illumination instruction.
• the screen may include a liquid crystal display, and the plurality of lights may include a plurality of light emitting diodes.
• the plurality of lights may include at least one of a backlight for a keypad, a peripheral light outside a keypad, and/or a backlight for the liquid crystal display.
• the images may be displayed in sequence to provide animation.
• the first illumination pattern at least one of the lights may be on while displaying the first image
• the second illumination pattern the at least one light may be off while displaying the second image, for example, to provide different static illumination patterns associated with different images.
• with the first illumination pattern at least two of the lights may be turned on and/or off according to a first sequence while displaying the first image
• with the second illumination pattern at least two of the lights may be turned on and/or off according to a second sequence while displaying the second image, with the first and second sequences being different, for example, to provide different dynamic illumination patterns.
• providing the plurality of image frames may include receiving the plurality of image frames over a wireless interface
• providing the illumination instructions may include receiving the illumination instructions over the wireless interface.
• an electronic device may include a screen, a plurality of lights, a memory, and a processor coupled to the screen, the plurality of lights, and the memory.
• the memory may be configured to provide a plurality of image frames with each image frame defining an image for display on the screen.
• the memory may also be configured to provide illumination instructions for the plurality of lights wherein different illumination instructions are associated with different image frames and wherein each illumination instruction defines a respective illumination pattern for the plurality of lights.
• the processor may be configured to display the images defined by the respective image frames on the screen.
• the processor may be configured to provide a first illumination pattern for the plurality of lights with the first illumination pattern being defined by a first illumination instruction associated with the first image frame.
• the processor may be configured to provide a second illumination pattern for the plurality of lights with the second illumination pattern being defined by a second illumination instruction associated with the second image frame.
• the first and second illumination patterns may be different.
• the memory may be further configured to provide a graphic data file including the plurality of image frames and the associated illumination instructions.
• each image frame may be provided as a different image data block of the graphic data file
• each illumination instruction may be provided as an illumination data block of the graphic data file with each illumination data block being associated with a different image data block.
• the graphic data file may also include a plurality of control data blocks with each of the control data blocks being associated with a respective one of the image data blocks and defining a duration for display of the image defined by the respective image data block.
• the graphic data file may be provided according to the Graphics Interchange Format (GIF) standard.
• GIF Graphics Interchange Format
• the memory may be configured to provide a first graphic data file including a first image frame and a first illumination instruction, and to provide a second graphic data file including a second image frame and a second illumination instruction.
• the screen may be a liquid crystal display
• the plurality of lights may be a plurality of light emitting diodes. More particularly, the plurality of lights may include at least one of a backlight for a keypad, a peripheral light outside a keypad, and/or a backlight for the liquid crystal display
• the processor may be configured to display the images in sequence to provide animation.
• At least one of the lights may be on while displaying the first image, and with the second illumination pattern, the at least one light may be off while displaying the second image, for example, to provide different static illumination patterns associated with different images.
• at least two of the lights may be turned on and/or off according to a first sequence while displaying the first image
• at least two of the lights may be turned on and/or off according to a second sequence while displaying the second image with the first and second sequences being different, for example, to provide different dynamic illumination patterns associated with different images.
• a receiver may be coupled to the memory and/or the processor with the receiver being configured to receive the plurality of image frames and the illumination instructions over a wireless interface and to provide the plurality of image frames and the illumination instructions to the memory and/or the processor.
• computer program products may be provided for operating an electronic device including a screen and a plurality of lights.
• the computer program products may include a computer readable storage medium having computer readable program code embodied therein.
• the computer readable program code may include computer readable program code configured to provide a plurality of image frames with each image frame defining an image for display on the screen.
• Computer readable program code may also be configured to provide illumination instructions for the plurality of lights wherein different illumination instructions are associated with different image frames and wherein each illumination instruction defines a respective illumination pattern for the plurality of lights.
• computer readable program code may be configured to display the images defined by the respective image frames.
• computer readable program code may be configured to provide a first illumination pattern for the plurality of lights while displaying a first image defined by a first image frame on the screen with the first illumination pattern being defined by a first illumination instruction associated with the first image frame.
• computer readable program code may be configured to provide a second illumination pattern for the plurality of lights while displaying a second image defined by a second image frame on the screen with the second illumination pattern being defined by a second illumination instruction associated with the second image frame. More particularly, the first and second illumination patterns may be different.
• the computer readable program code configured to provide a plurality of image frames and the computer readable program code configured to provide illumination instructions together include computer readable program code configured to provide a graphic data file including the plurality of image frames and the associated illumination instructions. Each image frame may be provided as a different image data block of the graphic data file and each illumination instruction may be provided as an illumination data block of the graphic data file with each illumination data block being associated with a different image data block.
• the computer readable program code configured to provide the graphic data file may be further configured to provide a plurality of control data blocks with each of the control data blocks being associated with a respective one of the image data blocks and defining a duration for display of the image defined by the respective image data block.
• the computer readable program code configured to provide the graphic data file may be further configured to provide the graphic data file according to the Graphics Interchange Format (GIF) standard.
• GIF Graphics Interchange Format
• the screen may include a liquid crystal display, and the plurality of lights may include a plurality of light emitting diodes. Moreover, the plurality of lights may include at least one of a backlight for a keypad, a peripheral light outside a keypad, and/or a backlight for the liquid crystal display, and the images may be displayed in sequence to provide animation. More particularly, with the first illumination pattern, at least one of the lights may be on while displaying the first image, and with the second illumination pattern, the at least one light may be off while displaying the second image, for example, to provide different static illumination patterns associated with different images.
• At least two of the lights may be turned on and/or off according to a first sequence while displaying the first image
• at least two of the lights may be turned on and/or off according to a second sequence while displaying the second image with the first and second sequences may be different, for example, to provide different dynamic illumination patterns associated with different images.
• FIG. 1A is a block diagram illustrating an electronic device according to some embodiments of the present invention.
• Figures IB-C are front views of electronic devices according to some embodiments of the present invention.
• Figure 2 is a block diagram illustrating graphic data files according to some embodiments of the present invention.
• Figure 3 is a table illustrating structures of illumination data blocks according to some embodiments of the present invention.
• Figure 4 is a table illustrating static illumination commands according to some embodiments of the present invention.
• Figure 5A-B are tables illustrating static illumination identifiers according to some embodiments of the present invention.
• Figure 6 is a table illustrating dynamic illumination commands according to some embodiments of the present invention.
• Figure 7 is a table illustrating dynamic illumination identifiers according to some embodiments of the present invention.
• connection or “coupled” as used herein may include wirelessly connected or coupled.
• the term “and/or” includes any and all combinations of one or more of the associated listed items.
• the present invention may be embodied as systems, methods, and/or computer program products. Accordingly, the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). Furthermore, the present invention may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system.
• a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
• the computer-usable or computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a nonexhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CD-ROM).
• RAM random access memory
• ROM read-only memory
• EPROM or Flash memory erasable programmable read-only memory
• CD-ROM portable compact disc read-only memory
• the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
• the present invention is described herein with reference to flowchart and/or block diagram illustrations of methods, systems, and computer program products in accordance with various embodiments of the invention. It will be understood that each block of the flowchart and/or block diagram illustrations, and combinations of blocks in the flowchart and/or block diagram illustrations, may be implemented by computer program instructions and/or hardware operations.
• These computer program instructions may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart and/or block diagram block or blocks.
• These computer program instructions may also be stored in a computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instructions that implement the operation and/or function specified in the flowchart and/or block diagram block or blocks.
• FIG. 1A is a block diagram illustrating an electronic device according to some embodiments of the present invention.
• the electronic device 101 may include a controller 103, a screen 105, a keypad 107, a plurality of lights 109 such as light emitting diodes (LEDs), a transmitter 111, a receiver 115, a speaker 117, and a microphone 119.
• LEDs light emitting diodes
• the controller 103 may include one or more processors and memories.
• the electronic device 101 may be a wireless communications device and/or a mobile terminal such as radiotelephone.
• the term "wireless communication device” or “mobile terminal” includes: a cellular radiotelephone with or without a multi-line display; a Personal Communications System (PCS) terminal that combines a cellular radiotelephone with data processing, facsimile and data communications capabilities; a Personal Data Assistant (PDA) that includes a radiotelephone, pager,
• PCS Personal Communications System
• PDA Personal Data Assistant
• FIG. 1 Internet/intranet access, Web browser, organizer, calendar and/or a global positioning system (GPS) receiver; a gaming device, an audio video player, and a conventional laptop and/or palmtop portable computer that includes a radiotelephone transceiver.
• GPS global positioning system
• the speaker, microphone, transmitter, and/or receiver may not be required if the electronic device is a PDA and radiotelephone functionality is not provided.
• the screen 105 and the keypad 107 and/or portions thereof may be implemented together using a touch sensitive screen.
• elements of the electronic device 101 may be provided in a housing including a faceplate 121, with the screen 105 and the keypad 107 exposed and/or visible.
• the keypad 107 may include a plurality of keys 107 a- ⁇ to provide, for example, a numeric keypad for the numbers 0-9 and the symbols "*" and "#".
• the keypad may include additional keys such as a "send” key, an "end” key, one or more directional keys, etc.
• portions or all of the keypad may be eliminated, for example, using a touch sensitive screen, and fewer keys may be provided than shown in Figure IB.
• the electronic device 101 may include a plurality of light emitting diodes (LEDs) 109 1-29 (illustrated as block 109 labeled lights in
• LEDs 109 ⁇ 2 may be used to illuminate respective keys 107 a- ⁇ of keypad 107; LEDs 109i 3-28 may be provided as perimeter lights; and LED 109 29 may be provided as a backlight for the liquid crystal display (LCD) screen 105.
• the keys 107 a- ⁇ may be translucent so that the LEDs 109i.i 2 are not directly visible but backlight illumination from each of these LEDs is visible through the respective key when the LED is turned on.
• each of the perimeter LEDs may be provided behind a translucent portion of the faceplate 121. Accordingly, the perimeter LEDs may not be directly visible, but backlight illumination from each of these perimeter LEDs may be visible through the faceplate 121 when turned on.
• the LED 109 29 may be provided behind the LCD screen 105 to provide backlight illumination for the screen.
• the electronic device 101' may include LEDs 109i.n provided to illuminate respective keys 107 a- ⁇ of keypad 107; LEDs 109'i3-20 provided as perimeter lights; and LED 109 29 provided as a backlight for the liquid crystal display (LCD) screen 105.
• LEDs 109i.n provided to illuminate respective keys 107 a- ⁇ of keypad 107
• LEDs 109'i3-20 provided as perimeter lights
• LED 109 29 provided as a backlight for the liquid crystal display (LCD) screen 105.
• each of the perimeter LEDs 109O -2O may be provided behind a translucent portion of the faceplate 121. Accordingly, the perimeter LEDs may not be directly visible, but backlight illumination from each of these perimeter LEDs may be visible through the faceplate 121 when turned on.
• the LED 109 29 may be provided behind the LCD screen 105 to provide backlight illumination for the screen. While examples are illustrated with 8 and 16 perimeter lights, devices with any number of perimeter lights may be provided according to embodiments of the present invention.
• the LEDs 109 I-I ? may thus be used to illuminate respective keys 107 a- ⁇ of keypad 107 for ease of use in the dark, and the LED 109 29 may be used to provide a desired brightness for the screen 105.
• one or more of the LEDs 109i.?9 (or 109i-i 2 , lO9' 13-2 o, and 109'M) may be used to provide different illumination patterns associated with images displayed on the screen 105.
• a graphic data file may include one or more image frames with each image frame defining an image for display on the screen 105, and the graphic data file may also include illumination instructions for the LEDs 109i_ 29 (or 109 M2 , lO9'i3 -2 o, and 109' 2 9) with different illumination instructions associated with different frames. More particularly, the graphic data file may be provided according to the Graphics Interchange Format (GIF) standard.
• GIF Graphics Interchange Format
• the electronic device 101 may include a screen 105 and a plurality of lights 109i -29 .
• the controller 103 may provide a plurality of image frames with each image frame defining an image for display on the screen.
• the controller 103 may also provide illumination instructions for the plurality of LEDs 109i -29 with different illumination instructions being associated with different image frames, and each illumination instruction may define a respective illumination pattern for the plurality of lights. Images defined by the respective image frames may be displayed on the screen 105 responsive to the controller 103.
• the controller 103 may provide illumination patterns for the LEDs responsive to associated illumination instructions while displaying the images on the screen 105. More particularly, a first illumination pattern provided by the LEDs while displaying a first image on the screen 105 may be different than a second illumination pattern provided by the LEDs while displaying a second image on the screen 105.
• the plurality of image frames and the illumination instructions may be provided within a graphic data file, with each image frame being provided in a different image data block of the graphic data file and with each illumination instruction being provided in an illumination data block of the graphic data file.
• each illumination data block in the graphic data file may be associated with a different image data block.
• the graphic data file may also include a plurality of control data blocks with each of the control data blocks being associated with a respective one of the image data blocks. More particularly, each control data block may define a duration for display on the screen 105 of the image defined by the respective image data block.
• Each control data block may also include addition information such as a location of the image defined by the respective image data block on the screen 105.
• the graphic data file may be provided according to the Graphics Interchange Format (GIF) standard.
• the graphic data file may be received over a wireless interface at receiver 115 and provided to the controller 103 from the receiver 115.
• a graphic data file according to the GIF standard may be provided to the receiver 115 as an attachment to a Multimedia Messaging Service (MMS) message.
• MMS Multimedia Messaging Service
• a plurality of image data blocks, illumination data blocks, and control data blocks may thus be provided at the controller 103 in a graphic data file (such as a GIF file).
• the images defined by the image data blocks of the graphic data file may be displayed in sequence to provide animation, and one or more of the LEDs 109i -29 may be illuminated in different patterns while displaying different images during the animation.
• different static illumination patterns of the LED's may be provided while displaying different images of a graphic data file so that at least one of the LEDs is on while displaying a first image, and so that the at least one of the LEDs is off while displaying the second image.
• the LEDs 109i -28 may be turned on while displaying even images of a graphic data file and off while displaying odd images of the graphic data file, so that the LEDs 109i-2 8 alternate flashing on and off while displaying the images of the graphic data file.
• an illumination pattern of the LEDs provided with an image may be dynamic so that at least two of the lights are turned on and/or off according to a sequence.
• a dynamic illumination pattern may be desirable when an image of a graphic data file is displayed on the screen 105 for a perceptible duration of time, such as for a slide show, for a graphic data file including a single image, and/or for a last image of an animation. More particularly, a first illumination pattern may provide that at least two of the LEDs are turned on and/or off according to a first sequence while displaying a first image, and a second illumination pattern may provide that at least two of the LEDs are turned on and/or off according to a second sequence while displaying a second image.
• the first and second sequences may be different. Particular static and dynamic illumination instructions and patterns are discussed in greater detail below.
• a plurality of image data blocks of a graphic data file may define a plurality of images to be displayed relatively quickly to provide animation, and a plurality of illumination data blocks of the graphic data file may define a respective plurality of illumination instructions for the LEDs. Different illumination patterns of one or more of the LEDs 109i -29 may thus be synchronized with images of an animation displayed on the LCD screen 105.
• a plurality of images of a graphic data file may be displayed relatively slowly (either for durations defined in the graphic data file and/or until advanced by a user) to provide a slide show.
• a graphic data file may include a single image data block defining a single image.
• a graphic data file including a single image and an illumination instruction defining a dynamic illumination pattern for the LEDs may be used, for example, to provide a screen saver.
• a graphic data file may include a plurality of image data blocks defining a plurality of images to be displayed and one illumination data block defining one set of illumination instructions for the LEDs.
• the LEDs may thus be turned on and/or off according to the single set of illumination instructions of the single illumination data block may while displaying each of the images. Accordingly, a particular LED may be turned on and/or off according to a same static and/or dynamic illumination instruction while displaying a sequence of different images provided using a single graphic data file.
• a graphic data file may include a single image data block defining a single image to be displayed and a plurality of illumination data blocks defining a respective plurality of sets of illumination instructions for the LEDs.
• the LEDs may thus be turned on and/or off according to different sets of illumination instructions of the plurality of illumination data blocks while displaying the single image. Accordingly, a particular LED may be turned on and/or off according to different static and/or dynamic illumination instructions while displaying a same image.
• a plurality of graphic data files may each include a single image data block defining a respective image and a single illumination data block defining a respective set of illumination instructions for the LEDs.
• image frames and illumination instructions may be provided in a graphic data file according to the GIF standard.
• a GIF data file 200 may include a plurality of blocks 201a-n including a plurality of image data blocks 201g, 201j, and 201m defining respective images to be displayed on the screen 105 in a sequential order. While three image data blocks are shown in Figure 2, any number of image data blocks may be provided in a GIF data file.
• control data blocks may be provided prior to respective image data blocks, and each control data block may include information to control how an image defined by the respective image data block is displayed and to control how long the image defined by the respective image data block is displayed before displaying the image defined by the next image data block.
• a beginning and ending of the GIF data file 200 may be respectively defined by the GIF header block 201a and the GIF terminator block 201n.
• global data blocks such as Global Screen Descriptor data block 201b, Global Color Table data block 201c, and Netscape Extension data block 201d, may define aspects of an animation that apply to all of the image data blocks of the GIF data file.
• a GIF data file may also include plain text extension blocks, comment extension blocks, and application extension blocks.
• An application extension block may be used to provide customized application specific data to be included in a GIF data file.
• a Netscape extension block 201d may be used to define a loop count for an animation of the GIF data file.
• An application extension block may include an 8-byte application identification, a 3- byte application code and 0 or more bytes of application specific data.
• a device that does not recognize and/or support an application extension block may display the animation of the GIF data file while ignoring the data of the unrecognized/unsupported application extension block.
• GIF application extension blocks may be defined as illumination data blocks 301e, 301h, and 301k including illumination instructions for illumination patterns for the LEDs 109i. 28 to be provided while displaying images defined by the respective image data blocks 201g, 201j, and 201m.
• the timing information provided in the graphic control extension blocks 201f, 201i, and 2011 can thus be used to define how long an image is displayed and/or how long an LED illumination pattern is provided.
• a sequence of LED illumination patterns can thus be synchronized with a motion of a respective sequence of images in an animation.
• a pre- defined sequence of LED illumination patterns may be played that is not necessarily synchronized with a motion of a respective sequence of images in an animation.
• illumination data blocks may be added as application extension blocks without use of an LZW (Lemple-Ziv- WeIc) compression algorithm. Moreover, it may be useful to decompress the image data blocks to display the multiple frames and allow editing of the LED illumination patterns of a sequence while displaying individual images of a GIF data file.
• LZW Lane-Ziv- WeIc
• FIG 3 is a diagram illustrating a format that may be provided for the illumination data blocks 301e, 301h, and 301k of Figure 2 according to some embodiments of the present invention. More particularly, the illumination data block 301 of Figure 3 is provided in accordance with the GIF standard.
• An illumination data block may include: a one byte GIF block code; a one byte extension type code; a one byte block size; an eight byte application identification (ID); a three byte authentication code; a one byte extension block size; one or more one byte illumination commands and associated one byte illumination identifiers; and a one byte block terminator.
• the GIF block code may be 0x21 for a GIF extension block, the extension type code may be OxFF for an application extension block, and the block size may be OxOB for an eleven byte length according to the GIF standard.
• the application ID identifies the particular application extension, and the application ID for an illumination data block according to some embodiments of the present invention may be an alpha-numeric (e.g. ASCII) string such as "SEMC LED.”
• the authentication code may be an alpha-numeric string, such as "1.0", used to identify a version number of the application extension block.
• the extension block size may vary as a function of the number of illumination commands and associated illumination identifiers included in the illumination data block.
• the extension block size may identify a number of bytes in the illumination data block, and in the example of Figure 3, the extension block size may be an even number because the total size of all fields excluding the illumination command/identifier fields is even, and because the illumination command/identifier fields are provided as pairs.
• the 1 byte block terminator identifies the end of the illumination data block.
• an image frame defining an image may be provided in an image data block (such as 201g, 201j, or 201m), and an illumination instruction associated with the image data block may be provided as one or more illumination command/identifier pairs in a corresponding image data block 301.
• the illumination commands of Figure 4 define a state of an LED or group of LEDs identified using the illumination identifiers of Figure 5A-B. More particularly, one of the illumination commands of Figure 4 may be applied to one light or a group of lights identified using the illumination identifiers of Figure 5A-B while displaying an associated image on a screen of the device.
• Illumination command OxOO (hex) specifies that a light or lights identified by the corresponding illumination identifier are turned off while displaying an associated image
• illumination command 0x01 (hex) specifies that a light or lights identified by the corresponding illumination identifier are turned on while displaying an associated image.
• Illumination commands 0x02 and 0x03 respectively specify that an identified light or lights fade off or on while displaying an associated image.
• Illumination commands 0x04 and 0x05 respectively specify that an identified light or lights flash on and then fade off or blink off and then fade on.
• a time component may also be provided.
• intensity and/or color components may be provided for the light or lights being activated. Additional static illumination commands beyond those set forth in Figure 4 may be provided according to additional embodiments of the present invention.
• the static illumination identifiers of Figures 5A-B identify a particular light or particular lights to be activated in accordance with a corresponding static illumination command for some embodiments of the present invention.
• Illumination identifiers KEY_0 to KEY_9, KEY_STAR, and KEY_NUM, for example, may be used to identify respective ones of the LEDs 109i.i 2 associated with keys 107 a- ⁇ of keypad 107.
• illumination identifiers PERIPHERAL ⁇ to PERIPHERAL ⁇ 1 may be used to identify respective ones of the perimeter LEDs 109 13 . 28 located around a perimeter of the keypad and or around the perimeter of the device.
• Illumination identifiers PERIPHERAL_12 to PERIPHERAL_31 may not be supported by a device with only 12 (or fewer) perimeter LEDs so that the unsupported illumination identifiers PERIPHERALJ2 to PERIPHERAL ⁇ 1 are ignored.
• the illumination identifier DISPLAYO may be used to identify the LED 109 29 used as a backlight for the LCD screen 105.
• the illumination identifier DISPLAYl may be used to identify an LED used as a backlight for a secondary LCD screen, and the illumination identifier DISPLAYl may be unsupported if the device does not include a secondary display.
• Illumination identifiers KEYPAD_ROW_0 to KEYPAD_R0W_15 may be used to identify respective groups of LEDs in rows with KEYPAD_ROW_0 identifying LEDs 109 1-3 , with KEYPAD_ROW_1 identifying LEDs 109 4-6 , with
• the illumination identifiers KEYPAD_ROW_4 to KEYPAD_ROW_7 may be unsupported, and illumination instructions including the unsupported row identifiers may thus be ignored.
• Illumination identifiers PERTPH J J3CLOCK to PERIPHJ 2_OCLOCK may control one or more peripheral lights to represent a position of an hour hand on a 12 hour clock.
• PERIPHJ _OCLOCK may identify perimeter LEDs 109 24- 26
• PERIPH 2 OCLOCK may identify perimeter LEDs 109 23- 24
• PERIPH_3_OCLOCK may identify perimeter LEDs 109 22 - 23 .
• PERIPH_4_OCLOCK may identify perimeter LEDs 109 20 -2i
• PERIPH_5_OCLOCK may identify perimeter LEDs 109 19 .2
• PERIPH_6_OCLOCK may identify perimeter
• Additional illumination identifiers for additional keys and/or groups of keys may also be provided, and the illumination identifiers may be supported or ignored by a particular device depending on a configuration thereof. Additional static illumination identifiers may be provided as shown, for example, in Figures 5A-B, but further static illumination identifiers are not discussed herein for the sake of conciseness.
• a graphic data file 200 (such as a GIF file) as illustrated in Figure 2 may include three image data blocks 201g, 201j, and 201m; three illumination data blocks 301e, 301h, and 301k; and three graphic control extension blocks 201f, 201i, and 2011. Responsive to the graphic data file 200, the controller 103 of device 101 may display images and provide associated illumination patterns defined by the graphic data file.
• the device 101 may display a first image defined by image data block 20 Ig for a period of time defined by graphic control extension block 201f; the device 101 may then display a second image defined by image data block 201 j for a period of time defined by graphic control extension block 20 Ii; and the device 101 may then display a third image defined by image data block 201m for a period of time defined by graphic control extension block 2011.
• the first illumination data block 301e may include two illumination instructions with each illumination instruction including an illumination command and an illumination identifier. For example, the Turn On command (0x01) may be provided as the first illumination command, and FRONT_ROW_0 may be provided as the first illumination identifier.
• the Turn On command (0x01) may be provided as the second illumination command, and FRONT_ROW_2 may be provided as the second illumination identifier. Accordingly, the LEDs 109i- 3 and 109 7-9 are turned on while displaying the first image on the screen 105 for the period of time defined by the first graphic control extension block 201f.
• the second illumination data block 301h may include four illumination instructions with each illumination instruction including an illumination command and an illumination identifier.
• the Turn On command (0x01) may be provided as the first illumination command
• FRONT_ROW_1 may be provided as the first illumination identifier.
• the Turn On command (0x01) may be provided as the second illumination command
• FRONT_ROW_3 may be provided as the second illumination identifier.
• the Turn OFF command (0x00) may be provided as the third illumination command
• FRONT_ROW_0 may be provided as the third illumination identifier.
• the Turn OFF command (0x00) may be provided as the fourth illumination command
• FRONT_ROW_2 may be provided as the fourth illumination identifier.
• the LEDs 109 4 - 6 and lO9io-i 2 are turned on and the LEDs 109i- 3 and 109 7 - 9 are turned off while displaying the second image on the screen 105 for the period of time defined by the second graphic control extension block 201i.
• the third illumination data block 301k may include four illumination instructions, with each illumination instruction including an illumination command and an illumination identifier.
• the Turn On command (0x01) may be provided as the first illumination command
• FRONT_ROW_0 may be provided as the first illumination identifier.
• the Turn On command (0x01) may be provided as the second illumination command
• FRONT_ROW_2 may be provided as the second illumination identifier.
• the Turn OFF command (0x00) may be provided as the third illumination command
• FRONT_ROW_1 may be provided as the third illumination identifier.
• the Turn OFF command (OxOO) may be provided as the fourth illumination command
• FRONT_ROW_3 may be provided as the fourth illumination identifier.
• the LEDs 109i- 3 and 109 7-9 are turned on and the LEDs 109_i -7 and 109 I- -I 2 are turned off while displaying the third image on the screen 105 for the period of time defined by the second graphic control extension block 2011. Accordingly, the first and third rows of keypad LEDs may be lit while displaying the first and third images, and the second and fourth rows of LEDs may be lit while displaying the second image.
• a graphics data file 200 with three image data blocks is discussed by way of example herein, but graphics data files with any number of image data blocks may be provided according to embodiments of the present invention.
• each illumination identifier may map to one or a plurality of LEDs provided in the device.
• a single LED may map to a plurality of illumination identifiers.
• the illumination identifiers PERIPHERAL_3 and KEYJTALK may identify the same LED.
• a particular device may not include LEDs corresponding to all illumination identifiers provided in an illumination data block. Accordingly, such a device may execute any illumination instruction for an LED(s) included in the device, and the device may simply ignore illumination instructions for LED(s) not included in the device.
• a device may map an illumination identifier to a different LED if the intended LED is not included in the device.
• additional and/or fewer illumination identifiers may be provided according to some embodiments of the present invention.
• KEY_0 to KEY_9 and KEY_STAR and KEY_NUM illumination identifiers may be provided, but a particular device may include a single LED for each row of keys of keypad 107 or separate LEDs for a row of keys may not be separately controllable. Accordingly, the device may ignore illumination instructions directed to individual LEDs if the particular individual LEDs are not separately provided and/or controllable, and only illumination instructions including the row identifiers KEYPAD_ROW_0 to
• KEYPAD_ROW_3 may be recognized with respect to LEDs for the keypad.
• such a device may illuminate all LEDs of a row in response to an illumination instruction including an illumination identifier for that row or if an illumination instruction includes a illumination identifier for any LED of that row.
• illumination identifiers may be provided that do not map directly to particular LEDs, but instead map to a more general category of LEDs that may be interpreted differently by different devices.
• illumination identifiers may define general orientations of perimeter LEDs defined, for example, as clock orientations PERIPHERJ _OCLOCK to PERIPHJ 2_OCLOCK.
• PERIPHERJ 2 JDCLOCK may map to LEDs 109 26-2 7
• PERIPHERJ _OCLOCK may map to LEDs 109 24-26
• PERIPHER_2_OCLOCK may map to LEDs 109 23-25 ,
• PERIPHER_3_OCLOCK may map to LEDs 109 22-2 3
• PERIPHER_4_OCLOCK may map to LEDs lO9 2 o- 22
• PERIPHER_5_OCLOCK may map to LEDs 109 19-21
• PERIPHER_6_OCLOCK may map to LEDs 109i 8- i 9 , etc.
• a different device with a different number and/or placement of perimeter LEDs may map clock orientations PERIPHER J _OCLOCK to PERIPHERJ 2_OCLOCK differently.
• PERIPHERJ 2 JDCLOCK may map to LEDs 109 16 and 109 20
• PERIPHERJJDCLOCK may map to LED 109'i 6
• PERIPHER_2 JDCLOCK may map to LEDs 109' 15- i 6
• PERIPHER JJDCLOCK may map to LED 109' 15
• PERIPHER_4 JDCLOCK may map to LED 109' 14
• PERIPHER_5 JDCLOCK may map to LED 109 13
• PERIPHER_6 JDCLOCK may map to LEDs 109' 13 and 109' ⁇
• PERIPHER_7 JDCLOCK may map to LED 109' ⁇
• PERIPHERAL_8 JDCLOCK may map to LED 109'i 8
• PERIPHERAL_9 JDCLOCK may map to LED 109' 19
• PERIPHERALJOJDCLOCK may map to LED 109' 19
• PERIPHERALJOJDCLOCK may map to LED 109' 19
• illumination sequences may be displayed in a similar fashion on phones that have different numbers of perimeter LEDs.
• a phone with 24 perimeter LEDs may associate two LEDs with each hour; a phone with 12 perimeter LEDs may associate one LED with each hour; and a phone with 8 perimeter LEDs could associate 1 or 2 LEDs with each hour as discussed above with respect to Figure 1C.
• An illumination sequence that turns on and off the perimeter LEDs at successive "hour" positions and proceeds in a clockwise fashion, for example, may thus provide a similar appearance on different phones having different numbers of perimeter LEDs. Content can thus be developed and reused across different models of phones.
• each of the dynamic illumination commands of Figure 6 defines a sequence to be applied using a dynamic illumination pattern defined using dynamic illumination identifiers of Figure 7.
• the dynamic illumination commands of Figure 6 and the dynamic illumination identifiers of Figure 7 may be provided in an illumination data block 301 as discussed above with respect to Figures 2 and 3.
• a loop command OxOO may provide that a dynamic illumination pattern is repeated for a period of time defined by the corresponding graphic control extension block.
• a play command 0x11 to OxIN may provide that a dynamic illumination pattern is repeated a defined number of times from one time (0x11) to N times (OxIN).
• the play commands defined in Figure 6 may provide that an illumination pattern is repeated, for example, up to 15 times (OxIF).
• the dynamic illumination identifiers of Figure 7 define particular illumination patterns that may be provided while displaying a corresponding image and repeated while displaying the corresponding image according to a dynamic illumination command of Figure 6.
• the SEQ_RING_AROUND_ROSIE (0x00) illumination identifier may indicate that the perimeter LEDs 109 26 - 27 are sequentially turned on and then off to create the appearance of a single light moving around the keypad.
• the SEQ_NIGHT_RIDER (0x01) illumination identifier may indicate that LEDs of the vertical columns of perimeter LEDs (i.e.
• LEDs 109 17-13 and 109 2 g and LEDs 109 20 - 25 are sequentially turned on and off to create the appearance of a first light moving up and down one side of the keypad and a second light moving up and down a second side of the keypad.
• the SEQ_ALL_FLASH (0x02) illumination identifier may indicate that all perimeter LEDs 109 13 - 28 flash on and off at the same time.
• the SEQ_RANDOM (0x03) illumination identifier may indicate that the LEDs 109i_ 28 flash randomly.
• the SEQ_RANDOM_FADE (0x04) illumination identifier may indicate that the LEDs 109i -28 fade randomly.
• the SEQ_EQU ALIZER (0x05) illumination identifier may indicate that the LEDs 109i.i 2 are illuminated as columns of randomly increasing and decreasing height to create the appearance of an audio equalizer with bouncing columns of light.
• the SEQ_EVEN_ODD (0x06) illumination identifier may indicate that even and odd ones of the LEDs 109 1-28 alternately flash on and off.
• the SEQ_WINK_AROUND (0x07) illumination identifier may indicate that all but one of the perimeter LEDs 109i 3 -28 is turned on and that each of the perimeter LEDs is sequentially turned off then on to create the appearance of a dark spot moving around the perimeter of the keypad.
• the SEQJLANDING_STRIP (0x08) illumination identifier may create the appearance of a landing strip with an appearance of two lights moving down the edges of the device.
• the SEQJHEARTBEAT (0x09) illumination identifier may indicate that all LEDs are illuminated together two times quickly followed by a delay.
• the SEQ_SOS (OxOA) illumination identifier may indicate that all LEDs are turned on and off together in a pattern to mimic a pattern of SOS in Morse code.
• the SEQ_ALT_LEFT_RIGHT (OxOB) illumination identifier may indicate that LEDs on left and right sides of the device are alternatingly turned on and off.
• the SEQ_ALL_ON (OxOC) illumination identifier may indicate that all LEDs are turned on with no "motion”
• the SEQ_ALL_OFF (OxOD) illumination identifier may indicate that all LEDs are turned off with no "motion.”
• Additional dynamic illumination identifiers may be reserved for pre-defined standard sequences.
• dynamic illumination identifiers (such as 0x80 to OxFF) may be reserved for device specific sequences.
• the illumination commands and identifiers of Figures 4-7 are provided by way of example and additional and/or different commands and/or identifiers may be provided according to some embodiments of the present invention.
• a device according to some embodiments of the present invention may be configured to execute illumination commands and identifiers supported by the device and to translate or ignore illuminations commands and identifiers not supported by the device.
• the electronic device 101 may be a radiotelephone, and graphic data files including illumination instructions may be wirelessly downloaded from a network operator or other source to be used as an alert, notification, and/or entertainment.
• a particular graphic data file may be downloaded using a multimedia messaging service (MMS) message, and the graphic data file may be executed to notify a user of an incoming telephone call, of a missed call, of an e-mail or other message, etc.
• MMS multimedia messaging service
• a particular graphic data file including illumination instructions may be executed together with or instead of a ring or other incoming call notification.
• different graphic data files including different illumination instructions may be associated with different known telephone numbers so that a different graphic data files may be executed to provide unique incoming telephone call notifications for different callers using available caller identification information.
• a graphic data file including illumination instructions may be executed with only the LED illumination pattern (and not images) being visible.
• images may be provided on a secondary screen if a primary screen is turned off and/or closed.
• a graphic data file may include blank image data blocks and associated illumination instructions so that a blank screen is provided while providing an LED illumination pattern.

Landscapes

• Engineering & Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Signal Processing (AREA)
• Human Computer Interaction (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Control Of Indicators Other Than Cathode Ray Tubes (AREA)
• Telephone Set Structure (AREA)
• Telephone Function (AREA)
• Liquid Crystal Display Device Control (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (1)

Family

ID=34993324

Family Applications (1)

Country Status (5)

Cited By (1)

Families Citing this family (5)

Citations (7)

Family Cites Families (13)

• 2004
  • 2004-12-17 US US11/016,073 patent/US8035585B2/en not_active Expired - Fee Related
• 2005
  • 2005-06-15 WO PCT/US2005/021223 patent/WO2006065279A1/en not_active Ceased
  • 2005-06-15 JP JP2007546628A patent/JP4874263B2/ja not_active Expired - Fee Related
  • 2005-06-15 EP EP05760824A patent/EP1825351A1/en not_active Ceased
  • 2005-06-15 CN CN2005800434989A patent/CN101124531B/zh not_active Expired - Fee Related

Patent Citations (7)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events