NON-LINEAR DISPLAY OF MOBILE APPLICATION DATA
BACKGROUND
Technical Field
[0001] The embodiments herein generally relate to relates to the phonebook, messaging, call records user interface in mobile communication devices.
Description of the Related Art
[0002] In a mobile communication device, phonebook application acts as a storage media for contact data unit such as name, phone numbers, email ID, postal address etc. Pictures and custom tones can be associated with each of the contacts. Once a contact is stored into the phonebook more details can be added or the current details can be also edited. The contacts in a phonebook application are presented as a list of names through which user can browse. User of a mobile communication device can search a particular contact from the device by typing a first few letters of the contact name.
[0003] The details for the currently highlighted contact can be viewed; a call can be made to the contact by press of call key of the mobile communication device. The picture associated with a contact is displayed and the associated custom tone is played when an incoming call is received from one of the phone numbers stored with the contact.

[0004] As described previously user can view or change the picture associated with a contact. It may not be possible to view the call records and the messages by the pictures assigned to contacts in the phonebook. Accordingly, there remains a need for a user to view the call records and the messages by the pictures assigned to contacts in the phonebook.
SUMMARY
[0005] In view of the foregoing, an embodiment herein provides a method of displaying locally stored graphics in a mobile device that includes processing a request on at least one of a phonebook, a messaging, and a call records contact data units, each of the contact data units associated with a graphic, and displaying the graphics associated with the contact data units along based on the request in a nonlinear representation of the contact data units.
[0006] The method may include organizing the display of the contact data units based on a priority information. The priority information may be an alphabetical sequence, a frequency of calling, a proximity within a social network, a geo-graphical location, a group, a time of dialing, a time of missed call, a time of received call, and a time of receiving a message. The non-linear representation may be a grid, a tree and a graph. The mobile device may be is at least one of a GSM phone, a UMTS phone, a CDMA phone, a CDMA 2000 phone, a PDC, a TDMA

phone, a PDA (Pocket Digital Assistant), a touch sensitive device, a computer, a handheld device, and wireless device. The image may include a JPEG, a BMP, a TIFF, a PNG, a GIF, and a RAW. The text may be displayed in at least one of hovering over the image, elsewhere when the graphic is highlighted, adjacent to the image, and superimposing the image The text may be a name, a phone number of a contact, a fax number, an SMS message character string, an EMS message character string, and an MMS message character string and the call record is at least one of a missed call information, a received call information and a dialed call information.
[0007] In another aspect, a mobile device includes a memory, a display and a processor to execute instructions. The processor may include processing a request on at least one of a phonebook, a messaging, and a call records contact data units, each of the contact data units associated with a graphic, displaying the graphics associated with the contact data units based on the request in a non-linear representation of the contact data units, and organizing the display of the contact data unit based on a priority information.
[0008] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein

without departing from the spirit thereof, and the embodiments herein include all such modifications.
BRIEF DESCRIPTION OF THE DRAWINGS
[0009] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
[0010] FIG. 1 illustrates an exemplary view of a mobile device in idling mode according to an embodiment herein;
[0011] FIG. 2 illustrates a user interface view of the mobile device with menu items displayed on a screen according to an embodiment herein;
[0012] FIG. 3A and FIG. 3B illustrate a user interface view of the mobile device displaying phonebook contacts in a grid of n x m elements to the user based on user preferences according to an embodiment herein;
[0013] FIG. 4 illustrates a user interface view of the mobile device displaying availability of various options for the user to opt for a highlighted contact according to an embodiment herein;
[0014] FIG. 5A, FIG. 5B, FIG. 5C and FIG, 5D illustrate a user interface view of the mobile device displaying a search methodology to find a particular contact data unit from the phonebook according to an embodiment herein;
[0015] FIG. 6 illustrates an exploded view of the mobile device according to

an embodiment herein;
[0016] FIG, 7 illustrates exploded view of a typical mobile device of FIG. 1 having an a memory having a computer set of instructions, a bus, a display, a speaker, and a processor capable of processing a set of instructions to perform any one or more of the methodologies herein, according to an embodiment herein; and
[0017] FIG. 8 is a process flow illustrating a method of displaying locally stored contact data units in a mobile device according to an embodiment herein.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
[0018] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0019] As mentioned, there remains a need for a user to view the call records and the messages by the pictures assigned to contacts in the phonebook. The

embodiments herein achieve this by providing a method of displaying locally stored contact data units in a mobile device that includes processing a request on at least one of a phonebook, a messaging, and a call records contact data units, each of the contact data units associated with a graphic, and displaying the graphics associated with the contact data units based on the request in a non-linear representation of the contact data units. Referring now to the drawings, and more particularly to FIGS. 1 through FIG. 8, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
[0020] FIG. 1 illustrates an exemplary view of a mobile device 100 in an idling mode according to an embodiment herein. The mobile device 100 includes a display 110, a keypad 120, a microphone 130, and a speaker 140 according to the embodiment herein. The mobile device 100 may a GSM phone, a UMTS phone, a CDMA phone, a CDMA 2000 phone, a PDC, a TDMA phone, a PDA (Pocket Digital Assistant), a touch sensitive device, a computer, a handheld device, and/or wireless device. The mobile device 100 may display day, date and/time on the screen based on user settings in the idling mode. The display 110 may enable the user to view content associated with contact data unit's in a phonebook on the screen. The content may be a graphic, a call record information and/or ring tones, etc. The graphic may include a text and/or an image. The keypad 120 may enable the user to type a text message, perform some fiinctions and/or search for a particular contact data unit. The keypad 120 may include a navigation panel 150, two soft keys

160 and 170, a call key 180 and an end power key 190. The microphone 130 may enable the user to speak to other users when he/she initiates a call.
[0021] The speaker 140 may enable the user to listen/hear to the other users when he/she makes a call. The navigation panel 150 may enable a user to view further content associated with the contact data unit and/or messages in the phonebook by making use of up, down, right, left and centre functionalities. The sofl keys 160 and 170 may enable the user to view phonebook options that may contain various other options (e.g., file manager, messaging, contacts, organizer and/or settings) of the mobile device 100. The call key 180 may enable the user to make a new call and/or initiate a call to the default number for highlighted contact data unit. The call key 180 may also enable the user to receive an incoming call by pressing it. The end power key 190 may enable the user to end up a call and/or also switch off his/her mobile device 100 by pressing the button (e.g., the end power key 190) for a period of seconds (e.g., by holding it for 2 seconds).
[0022] FIG. 2 illustrates a user interface view 200 of the mobile device 100 with menu items 200 displayed on a screen according to an embodiment herein. The mobile device 100 may enable the user to view the menu items 200 by pressing at least one of the soft keys 160 and 170. The menu items 200 may include contacts, messaging, call record information's, organizer, settings, radio, internet services and/or entertainments, etc. The soft keys 160 and 170 may enable the user to select a particular action item and/or return back to the idling mode.

[0023] FIG. 3 A and FIG. 3B illustrate a user interface view 300 of the mobile device 100 displaying phonebook contacts 300 in a grid of n x m elements to the user based on user preferences according to an embodiment herein. The mobile device 100 may include a view all option 310 which enables the user to view contact data unit's one at a time and/or all at a time. The mobile device 100 may also enable the user to add a new contact, delete a contact, and/or create groups. In an example embodiment, the user may create groups (e.g., family, friends and/or colleagues) and initiate a call to a particular contact data unit. The user may also create a group for frequently dialed contact data units. The mobile device 100 may also enable the user to speed dial a contact by assigning a number to a particular contact associated with the phonebook. In an example embodiment, the user may select a contact data unit (e.g., Alex as shown in figure) with a graphic which includes a text and an image (e.g., JPEG, BMP, TIFF, PNG, GIF, RAW format, etc.) from the contact menu and assign a number (e.g., 2) to the contact data unit associated with the phonebook and he/she may initiate a call by pressing the assigned number (e.g., 2) followed by pressing the soft key 160. The text may be displayed in at least one of hovering over the image, elsewhere when the graphic is highlighted, adjacent to the image, and superimposing the image. The text may include at least one of a name, a phone number of a contact, a fax number, an SMS message character string, an EMS message character string, and an MMS message character string and the call record is at least one of a missed call information, a received call information and a dialed

call information. In an example embodiment, the n x m elements may consist of one or more resources. The resources may include a text only, an image only, a text and an image both.
[0024] The mobile device 100 may also provide additional information (e.g., email ID, birthday, etc.) of the contact data unit associated with the phonebook. If there is no graphic associated with the contact data unit in the phonebook, a default placeholder image (e.g., "?" as shovm in figure) may be displayed for the contact. The mobile device 100 may include a scroll option 320 which may enable the user to view one or more contacts and/or information with the help of the navigation panel 150 (e.g., by pressing up, down, right and/or left key).
[0025] FIG. 4 illustrates a user interface view 400 of the mobile device 100 displaying availability of various options 400 for the user to opt for a highlighted contact according to an embodiment herein. The mobile device 100 may provide various options 400 for the user to opt for a highlighted contact. The various options 400 may include view details, call, send message, send MMS, send email, delete and/or speed dial. The mobile device 100 may enable the user to view details of contact data unit and initiate a call through a speed dial option. In addition, the mobile device 100 may also enable the user to send message, MMS (multimedia message service), and/or email. The mobile device 100 may further enable the user to delete particular contact data unit from the phonebook.
[0026] FIG. 5A, FIG. 5B and FIG. 5C and FIG. 5D illustrate a user interface

view 500 of the mobile device 100 displaying a search methodology to find a particular contact data unit from the phonebook using a search tool 510 according to an embodiment herein. The mobile device 100 may enable the user to search contact data unit based on a search criteria. In an example embodiment, the user may search for a contact data unit in the search tool 510 by typing a character string (e.g., "j" as shown in FIG. 5A). The mobile device 100 may display the contact data imit associated with a graphical image and/or a defauU place holder image ("?") which begin with the character string "j" and also other contact data unit "j" onwards.
[0027] The mobile device 100 may enable the user to narrow down the search contact data unit (e.g., as shown in FIG. 5B and FIG. 5C) by typing more character strings (e.g., "je" and "jen") and obtain more specific result. While or after searching if the user hits/presses any one of the soft keys 160 and 170, the soft keys 160 and 170 enables the user to select particular contact data unit and/or end up the search and return to the contact menu of the last search (e.g., as shown in FIG. 5D). In an example embodiment, the mobile device 100 may enable the user to search for messages associated with a resource received by other users.
[0028] FIG. 6 illustrates an exploded view 600 of the mobile device 100 according to an embodiment herein. The module device 100 includes a database 600, a non-linear display module 602, a search module 606, and a organize module 608 according to the embodiment herein. The database 600 may contain information associated with the contacts, messages, call records, graphics and/or ring tones, etc.

The non-linear display module 602 may generate a display view of content associated with the contact data unit in the phonebook. The non-linear display module 602 may include a representation of a grid display, a tree display and/or a graph display. The organizing module 604 may organize the display of the contact data units based on priority information. In an example embodiment, organizing the display of the contact data units is done be based on an alphabetical sequence, a frequency of calling, a proximity within a social network, a geo-graphical location, a group, a time of dialing, a time of missed call, a time of received call, and a time of receiving a message. The search module 606 may generate a search criteria based on at least one of a text search and a voice recognition search. In an example embodiment, the user may search for particular contact data unit with a graphical image by typing a character string. In another example embodiment, the user may perform a search to go to particular menu item by a voice record through the microphone 130.
[0029] FIG. 7 illustrates exploded view 700 of a typical mobile device 100 of FIG. 1 having an a memory 702 having a computer set of instructions, a bus 704, a display 706, a speaker 708, and a processor 710 capable of processing a set of instructions to perform any one or more of the methodologies herein, according to an embodiment herein. The processor 710 may also enable digital content to be consumed in the form of video for output via one or more displays 706 or audio for output via speaker and/or earphones 708. The processor 710 may also carry out the

methods described herein and in accordance with the embodiments herein. Digital content may also be stored in the memory 702 for future processing or consumption. The memory 702 may also store program specific information and/or service information (PSI/SI), including information about digital content available in the future or stored from the past.
[0030] A user of mobile device 100 may view this stored information on display 706 and select an item of for viewing, listening, or other uses via input 700, which may take the form of keypad, scroll, or other input device(s) or combinations thereof. When digital content is selected, the processor 710 may pass information. The content and PSI/SI may be passed among functions within mobile device 100 using bus 704.
[0031] FIG. 8 is a process flow illustrating a method of displaying locally stored contact data imits in a mobile device 100 according to an embodiment herein, wherein the method comprises processing (802) a request on at least one of a phonebook, a messaging, and a call records contact data units, each of the contact data units associated with a graphic; displaying (804) the contact data units along with the graphics based on the request in a non-linear representation (e.g., using the non-display module 602 of FIG. 6) of the contact data units, and organizing (806) the display of the contact data units based on a priority information.
[0032] In step 802, a request is processed on at least one of a phonebook, a messaging, and a call records contact data units, each of the contact data units

associated with a graphic. In step 804, the contact data units along with the graphics is displayed based on the request in a non-linear representation (e.g., using the non-display module 602 of FIG. 6) of the contact data units. In step 806, the display of the contact data units may be organized based on a priority information.
[0033] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing fi*om the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the appended claims.

CLAIMS
What is claimed is:
1, A method of displaying locally stored contact data units in a mobile device comprising:
processing a request on at least one of a phonebook, a messaging, and a call records contact data units, each of said contact data units associated with a graphic; and
displaying said graphics associated with said contact data units based on said request in a non-linear representation of said graphics.
2. The method of claim 1, further comprising organizing said display of said contact data units based on a priority information.
3. The method of claim 2, wherein said priority information is at least one of an alphabetical sequence, a frequency of calling, a proximity within a social network, a geo-graphical location, a group, a time of dialing, a time of missed call, a time of received call, and a time of receiving a message.
4. The method of claim 1, wherein said non-linear representation is at least one of a grid, a tree and a graph.

5. The method of claim 1, wherein said mobile device is at least one of a GSM phone, a UMTS phone, a CDMA phone, a CDMA 2000 phone, a PDC, a TDMA phone, a PDA (Pocket Digital Assistant), a touch sensitive device, a computer, a handheld device, and wireless device.
6. The method of claim 1, wherein said graphic includes at least one of an image and a text, said image at least one of a JPEG, a BMP, a TIFF, a PNG, a GIF, and a RAW and said text is displayed in at least one of hovering over said image, elsewhere when said graphic is highlighted, adjacent to said image, and superimposing said image.
7. The method of claim 6, wherein said text is at least one of a name, a phone number of a contact, a fax number, an SMS message character string, an EMS message character string, and an MMS message character string and said call record is at least one of a missed call information, a received call information and a dialed call information.
8. A mobile device comprising:
a memory;
a display; and
a processor to execute instructions, said processor comprising:

processing a request on at least one of a phonebook, a messaging, and
a call records contact data units, each of said contact data units
associated with a graphic;
displaying said graphics associated with said contact data based on
said request in a non-linear representation of said graphics; and
organizing said display of said contact data unit based on a priority
information.