SYSTEM AND METHOD FOR RENDERING SUPPLEMENTARY INFORMATION

FIELD OF THE INVENTION
[1] The present invention relates to the field of rendering supplementary information in an electronic device, and more specifically to the field of storing supplementary information in a phonebook contact.

BACKGROUND
[2] Phonebooks that come with present day phones have multiple fields to store information. Existing phonebooks store information in various fields, for example but not limited to, name field, field for mobile number, home phone number, and work phone number. Fields exist to set a specific ringtone or an alert tone to a contact in the phonebook.

[3] In an existing system, a phonebook includes information such as information of a contact, phone number of the contact, email address of the contact and profile picture of the contact. The information is either entered manually and if there are images associated with the contact, the images are retrieved from a local gallery and saved in the phonebook.

[4] Often, it is desired to add supplementary information from webpages. Existing systems do not provide means to add supplementary information such as billing rates, catalogues, menu cards, maps, photographs, video files and audio files to a contact in the phonebook from webpages.

[5] At times, a calling party requires supplementary information about the called party while placing a call. For example, if the called party is a commercial establishment and if the calling party is trying to place an order through call, it is convenient if supplementary information of the commercial establishment is provided to the user. Examples of commercial establishments include, but are not limited to restaurants, department stores, beauty parlours, medical stores, and medical clinics. Existing systems fail to provide supplementary information to the called party while on call.

[6] In light of the foregoing discussion, there is a need for a system to render supplementary information about a called party to a calling party before placing a call.
SUMMARY
[7] The above mentioned needs are met by employing a method and system to render supplementary information of a called party to a calling party. The present invention allows storage of supplementary information from webpages onto a phonebook contact. Further, the supplementary information is rendered to the calling party at the instance of the calling party establishing a call connection with a called party.

[8] An example of a method of identifying supplementary information includes parsing a webpage. The method includes generating at least one logical field marker (LFM) on the webpage. The method includes identifying supplementary information. Further, the method includes storing the supplementary information in a phonebook contact.

[9] An example of rendering supplementary information of a called party to a calling party includes parsing a webpage. The method includes generating at least one logical field marker (LFM) on the webpage. The method includes identifying supplementary information and storing the supplementary information in a phonebook contact. Further, the method includes rendering the supplementary information to the calling party at the instance of establishing a connection with the called party.

[10] An example of a system for rendering supplementary information of a called party to a calling party includes a webpage parser to parse a webpage. The system includes a logical field marker (LFM) generator to generate at least one logical field marker (LFM) on the webpage. The system includes an identification module to identify supplementary information. The system includes a phonebook to store the supplementary information and a phonebook contact controller for rendering the supplementary information to the calling party at the instance of establishing a connection with the called party.

[11] An example of an electronic device for rendering supplementary information of a called party to a calling party includes a memory for storing instructions. The electronic device includes a processor coupled to the memory and responsive to the instructions. The instructions enable the processor to parse a webpage, generate at least one logical field marker (LFM) on the webpage, identify supplementary information, store the supplementary information in a phonebook contact, and render the supplementary information to the calling party at the instance of establishing a connection with the called party.

[12] The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE FIGURES
[13] In the accompanying figures, similar reference numerals may refer to identical or functionally similar elements. These reference numerals are used in the detailed description to illustrate various embodiments and to explain various aspects and advantages of the present disclosure.

[14] FIG. 1 is a flowchart illustrating a method of rendering supplementary information about a called party to a calling party by use of a pointing device, in accordance with one embodiment of the present invention;

[15] FIG. 2 is an exemplary illustration of a user interface in an electronic device, in accordance with one embodiment of the present invention;

[16] FIG. 3 is an exemplary illustration of a user interface with a plurality of logical field markers in an electronic device, in accordance with another embodiment of the present invention;

[17] FIG. 4 is an exemplary illustration of a user interface with a plurality of logical field markers in an electronic device, in accordance with one embodiment of the present invention;

[18] FIG. 5 is an exemplary illustration of a user interface, in accordance with one embodiment of the present invention;

[19] FIG. 6 is an exemplary illustration of a user interface with a plurality of logical field markers in an electronic device, in accordance with one embodiment of the present invention;

[20] FIG. 7 is an exemplary illustration of a user interface in an electronic device, in accordance with another embodiment of the present invention;

[21] FIG. 8 is a flowchart illustrating a method of rendering supplementary information about a called party to a calling party by use of a touchscreen in an electronic device, in accordance with one embodiment of the present invention;

[22] FIG. 9 is an exemplary illustration of a user interface in an electronic device, in accordance with one embodiment of the present invention;

[23] FIG. 10 is an exemplary illustration of implementing the present invention in a smart phone, in accordance with one embodiment of the present invention;

[24] FIG. 11 is a flowchart illustrating a method of saving a supplementary attachment file (SAF) in a phonebook of an electronic device, in accordance with one embodiment of the present invention;

[25] FIG. 12 is an exemplary illustration of a calling screen, in accordance with another embodiment of the present invention;

[26] FIG. 13 is a flowchart illustrating a method of rendering supplementary information about a called party to a calling party in an electronic device, in accordance with another embodiment of the present invention;

[27] FIG. 14 is a block diagram of a system for rendering supplementary information of a called party to a calling party, in accordance with yet another embodiment of the present invention; and

[28] FIG. 15 is a block diagram of an electronic device, in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION
[29] Embodiments of the present disclosure described herein provide a method and system to render supplementary information of a called party to a calling party. The present invention enables a user to add contact information from webpages to a phonebook contact. The contact information includes primary information and supplementary information. Examples of the primary information includes name of the called party, phone number of a called party, email address of the called party and the profile picture of the called party. Examples of supplementary information includes billing rates, catalogues, menu cards, maps, photographs, video files and audio files. In the present invention, the supplementary information is automatically rendered to the calling party at the instance of the called party establishing a call connection with the calling party.

[30] The various methods, embodiments, and system level requirements to render supplementary information to a calling party is explained in conjunction with the description of FIGs 1-15.

[31] FIG. 1 is a flowchart illustrating a method of rendering supplementary information about a called party to a calling party by use of a pointing device of an electronic device, in accordance with one embodiment of the present invention. Examples of the electronic device include, but are not limited to smart phones, wearable computing devices, tablet computers, laptops and personal computers. Examples of the pointing device include, but are not limited to stylus, electronic mouse, trackballs, and touchscreens.

[32] Typically, the pointing device has a menu invoking button. A user presses the menu invoking button to cause the electronic device to display a menu of commands capable of being performed by the electronic device. The menu of commands is hereafter referred to as a pop-up menu. The pointing device has a select button. The user points the pointing device on a command in the pop-up menu and presses the select button to select the command. Pressing the select button on the command is hereafter referred to as clicking the command. The electronic device follows the command clicked by the user. The flowchart illustrating the various steps performed by the user begins at step 105.

[33] At step 110, a user opens a webpage in a web browser installed in the electronic device. Examples of webpages include but are not limited to static webpages and dynamic webpages. In one embodiment of the present invention, the user opens an app in the electronic device. The app retrieves information from the webpage and displays the information to the user in the form of the webpage.

[34] Prior to opening the webpage, the electronic device parses the webpage. Further, the electronic device identifies contact information relating to an entity in the webpage. Examples of entities include but is not limited to individual people, commercial establishments, and organizations. The contact information includes data elements associated with the entity. Examples of the data elements include, but are not limited to a name, an address, a phone number, and supplementary attachment files associated with the entity. The name, the address, and the phone number of the entity form the primary information associated with the entity. The supplementary attachment files contain the supplementary information associated with the entity. Examples of the supplementary information include billing rates, catalogues, menu cards, map coordinates, and maps relevant to the entity.

[35] At step 115, the user clicks on the webpage with the pointing device. To click on the webpage, the user points the pointing device on the webpage and presses the select button. As a result, the user selects the webpage.

[36] At step 120, the user invokes the pointing device pop-up menu by pressing the menu invoking button on the pointing device. The pop-up menu lists out a plurality of commands capable of being performed by the electronic device. Examples of commands include, but are not limited to “save page”, “copy text”, “phonebook option”, “close page”, and “save images”. In one embodiment of the present invention, the pointing device is the stylus pen. The user invokes the pop-up menu on the webpage using the stylus pen. The user selects a phonebook option in the pop-up menu to automatically generate a plurality of logical field markers.

[37] At step 125, the user clicks the command to extract contact information rendered in the webpage. In one embodiment of the present invention, the command to extract the contact information is “phonebook option”. Furthermore, the electronic device generates the plurality of logical field markers. The plurality of logical field markers marks the data elements in the contact information.

[38] At step 130, the electronic device displays the plurality of logical field markers (LFM) on the webpage. The plurality of logical field markers (LFM) are displayed as labels in the webpage. Examples of logical field markers (LFM) include Title markers (T), Number markers (N), and Attachment markers (A). Title Markers (T) mark the data elements containing name of the entity in the contact information. In one embodiment of the present invention, the electronic device identifies the data elements to be marked by the Title Markers (T) by recognizing keywords in the webpage. Examples of keywords used to identify the data elements include, but is not limited to “name”, and “brand name”. In another embodiment of the present invention, the electronic device identifies name of the entity from Universal Resource Locator (URL) of the webpage and places the title marker (T) on the URL. In yet another embodiment of the present invention, the electronic device reads metadata of the webpage to identify data elements to be marked by the Title Markers (T). In yet another embodiment of the present invention, the electronic device identifies the name of the entity from a heading frame of data content in the webpage. The number Markers (N) mark the data elements containing phone number of the entity in the contact information. The electronic device identifies number markers (N) by recognizing keywords in the webpage. Examples of keywords used to identify number markers (N) include, but is not limited to “phone number”, “tel no.”, “ph. No.” and “contact number”. In one embodiment of the present invention, the electronic device identifies the number markers (N) by recognizing numeric characters in the webpage. In another embodiment of the present invention, the electronic device identifies the number markers (N) by recognizing patterns of numerical characters and special characters in the webpage. In one exemplary illustration of the present invention, the electronic device identifies the number marker (N) by recognizing a pattern of numerical characters starting with a "+" special character as a phone number. In yet another embodiment of the present invention, the electronic device identifies multiple phone numbers from the web page.

[39] The attachment Markers (N) mark the data elements containing supplementary information in the contact information. The electronic device identifies attachment markers (A) by recognizing keywords in the webpage. Examples of keywords used to identify attachment markers (A) include, but is not limited to “menu”, “maps”, “catalogue” and “billing rates”. In another embodiment of the present invention, the electronic device opens a hyperlink in the webpage to extract a file and save as attachment. In yet another embodiment of the present invention, the electronic device identifies multiple attachments in the webpage. In yet another embodiment of the present invention, the electronic device identifies attachment markers (A) by recognizing hyperlinked redirections to a specific file extension. Examples of the special file extension include, but is not limited to “.tiff”, “.pwg”, “.mp3”, “.mp4”, “.wmv”, “.wma”, “.png”, “.gif”, “.docx”, “.xls”, “.xps”, ".jpg" files, and ".pdf" files. In yet another embodiment of the present invention, the electronic device opens a hyperlink in the webpage to extract a file and save as attachment.

[40] At step 135, the user edits the displayed Logical field markers (LFM) with the pointing device. In one embodiment of the present invention, the user edits the logical field markers (LFM) markers by performing a drag and drop function with the pointing device. To perform the drag and drop function, the user follows three steps. In first step, the user points the logical field marker (LFM) with the pointing device. In the second step, the user presses and holds the select button and moves the pointing device to a preferred destination. In the third step, the user releases the select button. In one exemplary illustration of the present invention, the user drags and drops the Title marker (T) on a word in the webpage to identify the word as a name of the entity. In another exemplary illustration of the present invention, the user drags and drops a number marker on a number in the webpage. The number is identified as a phone number of the entity.

[41] At step 140, the user clicks on the save command in the pop-up menu to save the contact information. As a result, the electronic device creates a new contact in the phonebook.

[42] At step 145, the electronic device fills name, number and attachment in the new contact in accordance with the data elements marked by the logical field markers. The electronic device automatically maps data elements to the new contact. The data elements marked by the title marker (T) and the number marker (N) are saved as primary information in the new contact. Data elements marked by the attachment marker (A) are mapped as supplementary information in the new contact.

[43] At step 150, the electronic device renders the supplementary information about the called party to the calling party at the instance of the called party establishing a call connection with the calling party.

[44] In an exemplary embodiment of the present invention, an electronic device retrieves the contact information associated with a restaurant from a webpage. Further, the electronic device retrieves a supplementary attachment file associated with the restaurant from the webpage. The supplementary attachment file is at least one of a menu card and a catalogue. The electronic device creates a new contact in a phonebook with the number of the restaurant number and the restaurant’s menu card. The electronic device attaches the supplementary attachment file to the new contact and saves the new contact information.

[45] Further, whenever a calling party establishes a call with the restaurant to place an order, the electronic device renders supplementary information, for example, a menu card on the electronic device. Thus, the calling party scrolls through the menu card while on call with the restaurant and place the order. Likewise, the user scrolls through the catalogue while on call with a commercial establishment and place the order.

[46] The flowchart ends at step 155.

[47] FIG. 2 is an exemplary illustration of a user interface 200 in an electronic device. A user browses through a webpage 205. Prior to opening the webpage 205, the electronic device parses the webpage 205. The user invokes a pop-up menu 210 using a pointing device. Examples of the pointing device include, but are not limited to stylus pens, electronic mouse, trackballs, and touchscreens. Typically, the pointing device has a menu invoking button. The user presses the menu invoking button to cause the electronic device to display the pop-up menu 210. The pop-up menu 210 lists out a “TAKE SCREENSHOT” command, an “EXTRACT CONTACT” command, a “SAVE IN CONTACTS” command, and an “EXIT” command. The pointing device has a select button. The user points the pointing device on a command in the pop-up menu 210 and presses the select button to select the command. The electronic device follows the command selected by the user.

[48] The “TAKE SCREENSHOT” command allows the user to take screenshot of the webpage 205. The “EXTRACT CONTACT” command allows the user to extract contact information from the webpage 205. The contact information includes data elements associated with an entity. Examples of entity include but are not limited to individual people, restaurants, commercial establishments, and organizations. Examples of the data elements include, but are not limited to a name, an address, a phone number, and supplementary attachment files associated with the entity. Examples of supplementary attachment files include images, documents, video files, audio files and maps. The data elements including the name, the address and the phone number of the entity are primary information associated with the entity. Information in the supplementary attachment files are the supplementary information associated with the entity. Examples of the supplementary information include billing rates, catalogues, menu cards, map coordinates, and maps relevant to the entity. The webpage 205 includes contact information of an entity named “HOTEL XYZ”. Further, the contact information rendered in the webpage 205 includes phone number and address of the entity. The webpage 205 includes links to supplementary attachment files in the webpage 205. The links are “INFO”, “MENU” and “PHOTOS”. The “SAVE IN CONTACTS” command allows the user to save the contact information into a phonebook contact. The “EXIT” command allows the user to exit the pop-up menu 210.

[49] FIG. 3 is an exemplary illustration of a user interface 300 with a plurality of logical field markers in an electronic device, in accordance with one embodiment of the present invention. Upon selection of “EXTRACT CONTACT” command (not shown in figure) the user interface 300 generates a plurality of logical field markers (LFM) on the webpage. The plurality of logical field markers is depicted as 310, 315, and 320. A user is enabled to edit the LFM. The editing includes duplicating the LFM on the webpage, resizing the LFM, dragging the LFM to other positions on the webpage, adding one or more phone numbers, and attaching a file from one of a local storage drive, a phone gallery, a camera, and an external storage source.

[50] The plurality of LFM 310, 315, and 320 are displayed as labels in the webpage 305. The plurality of logical field markers 310, 315, 320 include a title marker (T) 310, a number markers (N) 315, and an attachment marker (A) 320. The title Marker (T) 310 marks the data elements containing name of the entity in the contact information. Examples of keywords used to identify the title marker (T) 310 include, but is not limited to “name”, and “brand name”. In one embodiment of the present invention, the electronic device identifies name of the entity from Universal Resource Locator (URL) of the webpage and places the title marker (T) 310 on the URL. The number markers (N) 315 mark the data elements containing phone number of the entity in the contact information. The electronic device identifies the number marker (N) 315 by recognizing keywords in the webpage 305. Examples of keywords used to identify number markers (N) 315 include, but is not limited to “PHONE”, “phone number”, “telephone no.”, “landline no.”, “ph. No.” and “contact number”. The attachment marker (A) 320 marks the data elements containing supplementary information in the contact information. The electronic device identifies the attachment markers (A) 320 by recognizing keywords in the webpage. Examples of keywords used to identify the attachment marker (A) 320 include, but is not limited to “menu”, “maps”, “catalogue”, “INFO”, “Photos”, and “billing rates”. In yet another embodiment of the present invention, the electronic device reads metadata of the webpage to identify data elements to be marked by the Title Markers (T). In yet another embodiment of the present invention, the electronic device identifies the name of the entity from a heading frame of data content in the webpage. In one embodiment of the present invention, the electronic device identifies the number markers (N) by recognizing numeric characters in the webpage. In another embodiment of the present invention, the electronic device identifies the number markers (N) by recognizing patterns of numerical characters and special characters in the webpage. In one exemplary illustration of the present invention, the electronic device identifies the number marker (N) by recognizing a pattern of numerical characters starting with a "+" special character as a phone number. In yet another embodiment of the present invention, the electronic device identifies multiple phone numbers from the web page. In another embodiment of the present invention, the electronic device identifies attachment markers (A) by recognizing hyperlinked redirections to a specific file extension. Examples of the special file extension include, but is not limited to “.tiff”, “.pwg”, “.mp3”, “.mp4”, “.wmv”, “.wma”, “.png”, “.gif”, “.docx”, “.xls”, “.xps”, ".jpg" files, and ".pdf" files. In yet another embodiment of the present invention, the electronic device opens a hyperlink in the webpage to extract a file and save as attachment. In yet another embodiment of the present invention, the electronic device identifies multiple attachments in the webpage.

[51] FIG. 4 is an exemplary illustration of a user interface 400 with a plurality of logical field markers in an electronic device, in accordance with one embodiment of the present invention. FIG. 4 includes two views of the user interface 400, a first view 405a and a second view 405b. A user is enabled to edit the LFM. The editing includes duplicating the LFM on the webpage, resizing the LFM, dragging the LFM to other positions on the webpage, adding one or more phone numbers, and attaching a file from one of a local storage drive, a phone gallery, a camera, and an external storage source.

[52] In the first view 405a, a webpage includes a plurality of logical field markers such as a title marker (T) 410a, a number marker (N) 415a, and an attachment marker (A) 425a. The webpage includes an auxiliary phone number 420a. However, a number “N” marker is not assigned initially to the auxiliary phone number 420a.

[53] A user edits the number marker (N) 415a to include the auxiliary phone number 420a by performing a drag and drop function with a pointing device, thereby duplicating the number marker. To perform the drag and drop function, the user follows three steps. In first step. The user points the number marker (N) 415a with the pointing device. In the second step, the user presses and holds a select button of the pointing device and moves the pointing device to a preferred destination. In the third step, the user releases the select button. In one exemplary illustration of the present invention, the user drags and drops the number marker (N) 415a on the auxiliary phone number 420a in the webpage. Thus, number marker (N) 415a marks two phone numbers after the user performs the drag and drop function. As a result, the user duplicates the number marker (N) 415a with the drag and drop function.

[54] The attachment marker (A) 425a marks the “INFO” as a link to a supplementary attachment file. The user changes the link to “MENU” by performing the drag and drop function on the attachment marker (A) 425a and moving the attachment marker (A) 425a to the “MENU” link. The user interface 400 changes from the first view 405a to the second view 405b after the user performs the drag and drop functions on the number marker (N) 415a and the attachment marker (A) 425a.

[55] The second view 405b depicts the webpage after the user has dragged and dropped the logical field markers. The webpage now includes a title marker (T) 410b, a number marker (N) 415b, a duplicate number marker 415c and a new attachment marker (A) 425b marking the “MENU” as a link to the supplementary attachment file. In some embodiments, a user drags and drop the LFM to multiple attachments. For example, the user includes “MENU”, “INFO”, and “PHOTOS” as attachments.

[56] FIG. 5 is an exemplary illustration of a user interface 500, in accordance with one embodiment of the present invention. The user interface 500 includes a first view 505a and a second view 505b. In the first view 505a a webpage includes a plurality of logical field markers including a title marker (T) 510a, Number marker (N) 515a, and an attachment marker (A) 520a. The title marker (T) 510a marks data elements containing name of the entity in the contact information. The number marker (N) 515a marks the phone number of the entity. The attachment marker (A) 520a marks the supplementary attachment file. The second view 505b depicts a screen for entering contact information in a phonebook of an electronic device. The various contact information are mapped automatically to a phonebook contact. In one embodiment of the present invention, data elements marked by the plurality of logical field markers are entered into default fields in a phonebook contact. In another embodiment of the present invention, the data elements marked by the logical field markers are stored in a new phonebook contact. The information associated with the title and the phone number are mapped as primary information and the attachment is mapped as supplementary information in the phonebook contact. The second view 505b includes a name field 510b, a phone number field 515b and an attachment field 520b. The electronic device automatically enters the data element marked by the title marker (T) 510a into name field 510b. Further, the electronic device automatically enters the data element marked by the number marker (N) 515a into phone number field 515b. The electronic device automatically enters the data element marked by the attachment marker (A) 520a into attachment field 520b.

[57] FIG. 6 is an exemplary illustration of a user interface 600 with a plurality of logical field markers in an electronic device, in accordance with one embodiment of the present invention. FIG. 6 includes two views of the user interface 600, a first view 605a and a second view 605b of a webpage. A user is enabled to edit the LFM. The editing includes dragging a logical field marker LFM to other positions on the webpage and to resize the LFM.

[58] The first view 605a includes a plurality of logical field markers 610a, 615a, and 625a. The plurality of logical field markers (LFM) 610a, 615a, and 625a are displayed as labels in the first view 605a. The plurality of logical field markers 610a, 615a, and 625a includes a title marker (T) 610a, a number marker (N) 615a, and an attachment marker (A) 625a. Further, the first view 605a includes a webpage. The webpage includes contact information of an entity named “Hotel ABC”. Further, the contact information rendered in the webpage includes phone number and address of the entity. The webpage includes links to supplementary attachment files in the webpage. The links are “INFO”, and “MENU”. Further, the webpage includes an auxiliary phone number 620b. The number marker (N) 615a marks one phone number 620a of the entity. However, the number marker (N) 615a fails to mark the auxiliary phone number 620b.

[59] A user edits the number marker (N) 615a to include the auxiliary phone number 620b by performing a drag and drop function with a pointing device. Examples of a pointing device include stylus pen, electronic mouse, touchscreen and trackball. To perform the drag and drop function, the user follows three steps. In a first step, the user points the number marker (N) 615a with the pointing device. In the second step, the user presses and holds a select button of the pointing device and moves the pointing device to a preferred destination. In the third step, the user releases the select button. In one exemplary illustration of the present invention, the user drags and drops the number marker (N) 615a on the auxiliary phone number 620b in the webpage. Thus, number marker (N) 615a is shifted to the auxiliary phone number after the user performs the drag and drop function. As a result, the user resizes the number marker (N) 615a with the drag and drop function.

[60] The second view 605b depicts the logical field markers after the user edits the markers by dragging the logical field marker LFM to other positions on the webpage and to resize the LFM.

[61] The webpage now includes a title marker (T) 610b, a number marker (N) 615b, and an attachment marker (A) 625b. The shifted or resized number marker (N) 615b marks the auxiliary phone number 620c. Further, the attachment marker (A) 625b marks the “MENU” as a link to the supplementary attachment file.

[62] FIG. 7 is an exemplary illustration of a user interface 700 in an electronic device, in accordance with one embodiment of the present invention. The user interface 700 includes a first view 705a and a second view 705b.

[63] The first view 705a includes a webpage. The webpage includes links to supplementary attachment files in the webpage 305. The links are “INFO”, and “MENU”. Further, the first view 705a includes the plurality of logical field markers 710a, 715a, and 720a. The plurality of logical field markers (LFM) 710a, 715a, and 720a are displayed as labels in the webpage. The plurality of logical field markers 710a, 715a, 720a include a title marker (T) 710a, a number marker (N) 715a, and an attachment marker (A) 720a. The title marker (T) 710a marks the data elements containing name of the entity in the contact information. The number marker (N) 715a marks the phone numbers of the entity. The attachment marker (A) 720a marks the supplementary attachment file.

[64] The second view 705b depicts a screen for entering contact information in a phonebook in the electronic device. The second view 705b includes a name field 710b, a first phone number field 715b, a second phone number field 720b and an attachment field 725b. The electronic device automatically enters the data element marked by the title marker (T) 710a into name field 710b. Further, the electronic device automatically enters the data element marked by the number marker (N) 715a into the first phone number field 715b and the second phone number field 720b. The electronic device automatically enters the data element marked by the attachment marker (A) 720a into attachment field 725b.

[65] FIG. 8 is a flowchart illustrating a method of rendering supplementary information about a called party to a calling party by use of a touchscreen in an electronic device, in accordance with another embodiment of the present invention. Examples of the electronic devices include, but are not limited to smart phones, wearable computing devices, tablet computers, laptops and personal computers. Examples of the touchscreen include, but are not limited to resistive touch, and capacitive touch. A process illustrated by the flowchart begins at step 805.

[66] At step 810, a user opens a webpage in a web browser installed in the electronic device.

[67] At step 815, the user performs a long press on the touchscreen. To perform the long press, the user presses the touchscreen for an extended time period. As a result, the user selects the webpage.

[68] At step 820, the user invokes the quick launch side menu by performing the long press on the touchscreen. The quick launch side menu lists out a plurality of applications in the electronic device. Applications in the quick launch side menu include, but are not limited to phonebook, camera, and messaging application. Further, the electronic device displays the plurality of Logical Field Markers (LFM) on the webpage. The plurality of logical field markers (LFM) is displayed as labels in the webpage. Examples of logical field markers include Title markers (T), Number markers (N), and Attachment markers (A). Title Markers (T) mark the data elements containing name of the entity in the contact information. The electronic device identifies title markers (T) by recognizing keywords in the webpage. Examples of keywords used to identify title markers (T) include, but is not limited to “name”, and “brand name”. In one embodiment of the present invention, the electronic device identifies name of the entity from Universal Resource Locator (URL) of the webpage and places the title marker (T) on the URL. The electronic device identifies number markers (N) by recognizing keywords in the webpage. Examples of keywords used to identify number markers (N) include, but is not limited to “phone number”, “tel no.”, “ph. No.” and “contact number”. In one embodiment of the present invention, the electronic device identifies multiple phone numbers from the web page. The electronic device identifies attachment markers (A) by recognizing keywords in the webpage. Examples of keywords used to identify attachment markers (A) include, but is not limited to “menu”, “maps”, “catalogue” and “billing rates”. In one embodiment of the present invention, the electronic device identifies multiple attachments in the webpage. In another embodiment of the present invention, the electronic device identifies attachment markers (A) by recognizing hyperlinked redirections to a specific file extension. Examples of the special file extension include, but is not limited to “.tiff”, “.pwg”, “.mp3”, “.mp4”, “.wmv”, “.wma”, “.png”, “.gif”, “.docx”, “.xls”, “.xps”, ".jpg" files, and ".pdf" files.

[69] At step 825, the user performs drag and drop function on the webpage to drop the webpage to the phonebook in the quick launch side menu. To perform the drag and drop function, the user follows three steps. In first step. The user presses and holds on the webpage via the touchscreen. In the second step, the user moves a finger to the phonebook application in the quick launch side menu. In the third step, the user releases the touchscreen. Further, the electronic device creates a new contact in the phonebook.

[70] At step 830, the electronic device fills name, number and attachment in the new contact in accordance with the data elements marked by the logical field markers. The electronic device automatically maps data elements to the new contact. The data elements marked by the title marker (T) and the number marker (N) are saved as primary information in the new contact. Data elements marked by the attachment marker (A) are mapped as supplementary information in the new contact. Further, the electronic device saves the new contact.

[71] At step 835, the electronic device takes a screen shot of the webpage and stores the screenshot as the supplementary attachment file in the new contact.

[72] At step 840, the electronic device renders the supplementary information about the called party to the calling party at the instance of the called party establishing a call connection with the calling party.

[73] The flowchart ends at step 845.

[74] FIG. 9 is an exemplary illustration of a user interface 900 in an electronic device, in accordance with one embodiment of the present invention. The user interface 900 includes a webpage 905. Examples of electronic devices include, but are not limited to smart phones, tablet computers and personal computers. Examples of webpage 905 include but are not limited to static webpages and dynamic webpages. The webpage 905 includes contact information of an entity named “HOTEL XYZ”. Further, the contact information rendered in the webpage 905 includes phone number and address of the entity. The webpage 905 includes links to supplementary attachment files in the webpage 905. The links are “INFO”, “MENU” and “PHOTOS”.

[75] Further, the user interface 900 includes a quick launch side menu 910. A user invokes the quick launch side menu 910 by performing a long press on a touchscreen of the electronic device. The quick launch side menu 910 lists out a plurality of applications in the electronic device. Applications in the quick launch side menu 910 include, but are not limited to a phonebook application 915, a first application (APP #1), a second application (APP #2), a third application (APP #3), a fourth application (APP #4), and a fifth application (APP #5). The user performs drag and drop function on the webpage 905 to drop the webpage to the phonebook in the quick launch side menu 915. To perform the drag and drop function, the user follows three steps. In first step, the user presses and holds the user's finger on the webpage via the touchscreen. In the second step, the user moves the finger to the phonebook application 915 in the quick launch side menu 910. In the third step, the user releases the touchscreen. If the user performs the drag and drop function, the electronic device extracts the contact information from the webpage 905. Further, the electronic device creates a new contact in the phonebook and stores the contact information in the new contact. In one embodiment of the present invention, the user performs a swipe function on the touchscreen to add the webpage to the quick launch side menu 915. In another embodiment of the present invention, the user performs a long press on the webpage to add the webpage to the quick launch side menu 915. The electronic device enters the primary information associated with the entity in the new contact. The electronic device attaches the supplementary information associated with the entity to the new contact.

[76] FIG. 10 is an exemplary illustration of implementation of the present invention in a smart phone, in accordance with one embodiment of the present invention. The smart phone 1005 includes at least a touchscreen, and a menu button 1010. The touch screen displays a webpage containing contact information of an entity. A user presses the menu button 1010 to invoke an options menu 1015. The options menu 1015 lists out a “TAKE SCREENSHOT” command, a “SAVE IN CONTACTS” command, and an “EXIT” command. The user selects the “SAVE IN CONTACTS” to save contact information of the entity into the smart phone. The smartphone 1005 extracts the contact information from the webpage and stores the contact information as a contact in a phonebook application. Further, the smartphone 1005 automatically takes a screenshot and saves the screenshot in a contact of the phonebook as a supplementary attachment file. The “TAKE SCREENSHOT” command allows the user to take screenshot of the webpage. The “EXIT” command allows the user to exit the options menu 1015.

[77] FIG. 11 is a flowchart illustrating a method of saving a supplementary attachment file (SAF) in a phonebook of an electronic device, in accordance with another embodiment of the present invention. Examples of the supplementary attachment file include images and documents. A process illustrated by the flowchart begins at step 1105.

[78] At step 1110, the process checks if a user prefers to use an image in an image gallery as the supplementary attachment file. The process proceeds to step 1120 if the user prefers an image from the image gallery. The process proceeds to step 1115 if the user prefers to use an image from a camera.

[79] At step 1120, the user selects an image from at least one of the image gallery, phone gallery, and an external storage source. In one embodiment of the present invention, the supplementary attachment file is a document.

[80] At step 1115, the user opens a camera application in the electronic device. The camera applications enable the user to take photographs in the electronic device.

[81] At step 1125, the user opens the phonebook application in the electronic device. Further, the user links the camera application with the phonebook.

[82] At step 1130, the user clicks an image in the camera application. The electronic device saves the image in an internal memory of the electronic device.

[83] At step 1135, the electronic device attaches the image as the supplementary attachment file.

[84] The flowchart ends at step 1140.

[85] FIG. 12 is an exemplary illustration of a calling screen 1200, in accordance with one embodiment of the present invention. The calling screen 1200 is presented to a calling party when a call connection is established with a called party. The calling screen 1200 includes a supplementary information display area 1205. In one embodiment of the present invention, the supplementary information display area 1205 includes a menu card of a restaurant. The calling party views the supplementary information in the supplementary information display area 1205 when a call connection is established with a called party. The calling party scrolls down the menu while the calling party establishes a call with the called party.

[86] FIG. 13 is a flowchart illustrating a method of rendering supplementary information about a called party to a calling party in an electronic device, in accordance with another embodiment of the present invention. A process illustrated by the flowchart begins at step 1305.

[87] At step 1310, a user opens a webpage in a web browser installed in the electronic device. Examples of webpages include but are not limited to static webpages and dynamic webpages.

[88] At step 1315, the electronic device parses the webpage. Further, the electronic device identifies contact information relating to an entity in the webpage. Examples of entities include but are not limited to individual people, commercial establishments, restaurants and organizations. The contact information includes data elements associated with the entity. The data elements are also referred to as information. Examples of the data elements include, but are not limited to a name, an address, a phone number, and supplementary attachment files associated with the entity. Examples of supplementary attachment files include images, documents, audio files, video files and maps. The supplementary attachment files contain the supplementary information associated with the entity. Examples of the supplementary information include billing rates, catalogues, menu cards, map coordinates, and maps relevant to the entity. In one embodiment of the present invention, the called party is one of a restaurant and a commercial establishment. Further, the calling party establishes a call connection with the caller party to place an order with the called party. The supplementary attachment file is at least one of a menu card and a catalogue. Further, the calling party scrolls through at least one of the menu cards and the catalogue while on call with the called party.

[89] At step 1320, the electronic device generates a plurality of logical field markers. The plurality of logical field markers marks the data elements in the contact information. Examples of logical field markers include Title markers (T), Number markers (N), and Attachment markers (A). Title Markers (T) mark the data elements containing name of the entity in the contact information. The electronic device identifies title markers (T) by recognizing keywords in the webpage. Examples of keywords used to identify title markers (T) include, but is not limited to “name”, and “brand name”. In one embodiment of the present invention, the electronic device identifies name of the entity from Universal Resource Locator (URL) of the webpage and places the title marker (T) on the URL. The electronic device identifies number markers (N) by recognizing keywords in the webpage. Examples of keywords used to identify number markers (N) include, but is not limited to “phone number”, “tel no.”, “ph. No.” and “contact number”. In one embodiment of the present invention, the electronic device identifies multiple phone numbers from the web page. The electronic device identifies attachment markers (A) by recognizing keywords in the webpage. Examples of keywords used to identify attachment markers (A) include, but is not limited to “menu”, “maps”, “catalogue” and “billing rates”. In one embodiment of the present invention, the electronic device identifies multiple attachments in the webpage. In another embodiment of the present invention, the electronic device identifies attachment markers (A) by recognizing hyperlinked redirections to a specific file extension. Examples of the special file extension include, but is not limited to “.tiff”, “.pwg”, “.mp3”, “.mp4”, “.wmv”, “.wma”, “.png”, “.gif”, “.docx”, “.xls”, “.xps”, ".jpg" files, and ".pdf" files.

[90] At step 1325, the electronic device automatically maps information associated with the plurality of logical field markers (LFM) to a phonebook contact. The electronic device maps information associated with the plurality of logical field markers (LFM) based on a look-up table. The look-up table defines rules for associating information of the plurality of logical field markers (LFM) with relevant fields in the phonebook.

[91] In one embodiment, a user saves the primary information and the supplementary information in the phonebook contact and a user dial screen is invoked automatically upon saving.

[92] At step 1330, the electronic device renders the supplementary information about the called party to the calling party at the instance of the called party establishing a call connection with the calling party.

[93] The flowchart ends at step 1335.

[94] FIG. 14 is a block diagram of a system 1400 for rendering supplementary information of a called party to a calling party, in accordance with one embodiment of the present invention. The system 1400 is implemented in an electronic device 1465. Examples of electronic devices include, but are not limited to smart phones, personal computers and tablet computers. The electronic device 1465 includes a random number generator 1405, a rendering module 1410, a phonebook storage 1415, a controller module 1420, a configuration module 1425, and a gesture recognition module 1430.

[95] The random number generator 1405 generates random numbers for encryption of phonebook contacts in the phonebook storage 1415. The random number generator 1405 is at least one of a pseudo random number generator and a true random number generator. The random number generator 1405 transmits the random number to the controller module 1420 for processing.

[96] The controller module 1420 includes a webpage parser 1440, a logical field marker (LFM) generator 1445, a logical field marker parser 1450, and a phonebook contact controller 1455. The webpage parser 1440 enables parsing of a webpage in the electronic device 1465. The LFM generator 1445 generates the plurality of logical field markers on the webpage. Examples of logical field markers include title markers (T), number markers (N), and attachment markers (A). The Title Markers (T) marks the data elements containing name of the entity in the contact information. The electronic device 1465 identifies title markers (T) by recognizing keywords in the webpage. Examples of keywords used to identify title markers (T) include, but is not limited to “name”, and “brand name”. In one embodiment of the present invention, the electronic device 1465 identifies name of the entity from Universal Resource Locator (URL) of the webpage and places the title marker (T) on the URL. The number markers (N) mark the data elements containing the phone number of the entity in the contact information. The electronic device 1465 identifies number markers (N) by recognizing keywords in the webpage. Examples of keywords used to identify number markers (N) include, but is not limited to “phone number”, “tel no”, “ph. No” and “contact number”. In one embodiment of the present invention, the electronic device 1465 identifies multiple phone numbers from the web page. The attachment markers (A) marks the data elements containing the supplementary attachment file of the entity. The electronic device 1465 identifies attachment markers (A) by recognizing keywords in the webpage. Examples of keywords used to identify attachment markers (A) include, but is not limited to “menu”, “maps”, “catalogue” and “billing rates”. In one embodiment of the present invention, the electronic device 1465 identifies multiple attachments in the webpage.

[97] The LFM parser 1450 automatically maps information associated with the plurality of LFM to a phonebook contact. Information associated with name of the entity and the phone number of the entity is mapped as primary information and the supplementary attachment file is mapped as supplementary information in the phonebook. The primary information and the supplementary information are stored in the phonebook storage 1415. The phonebook contact controller 1455 renders the supplementary information about the called party via the rendering module 1410.

[98] The rendering module 1410 includes a phonebook display 1435 and a dialer 1470 to render the supplementary information about the called party to the calling party when a call is established between the called party and the calling party. The dialer 1470 presents the supplementary information to the user via the phonebook display 1435. Examples of the phonebook display 1435 include but not limited to LCD screen, touchscreen, LED screen. The user communicates with the electronic device via the gesture recognition module 1430. The dialer 1470 includes a supplementary information display area. In one embodiment of the present invention, the supplementary information display area includes a menu card of a restaurant. The calling party views the supplementary information in the supplementary information display area when a call connection is established with a called party. The calling party scrolls down the menu while the calling party establishes a call with the called party.

[99] In one embodiment, the supplementary information includes map directions of a contact in a phonebook. A caller navigates the map for getting directions from the called party while on call. In another embodiment, every contact in the phonebook is associated with a map, thereby enabling the calling party to find directions of the calling party while on call.

[100] The gesture recognition module 1430 recognises gestures input by the user on a user input 1460. The gestures input by the user is at least one of a click, touch, swipe, pinch, visual and auditory gestures. The user input 1460 is at least one of a keypad, touchscreen, and stylus. In one embodiment, the electronic device 1465 includes an identification module (not shown in figure) to identify supplementary information. Supplementary attachments are in one or more formats. The supplementary information are, but not limited to a .jpg, .png, .bmp, .mpg, .gif, .docs, .pdf, .mp3, .mp4, .avi, .wmv, .wma, .ppt, .xls format. The identification module in conjunction with LFM parser 1450, parses the webpage, performs semantic filtering using standard algorithms, and identifies file extensions to identify the supplementary information.

[101] FIG. 15 is a block diagram of an electronic device 1500 in accordance with one embodiment of the present invention. The electronic device 1500 includes a processor 1505 coupled with a networking device 1510. The networking device 1510 enables communication of information internal and external to the device. The networking device 1510 includes a bus, a wifi router, a Bluetooth transceiver, a RFID sensor, and a co-axial cable port. The processor 1505 includes at least an integrated electronic circuit for processing and controlling functionalities of the electronic device 1500. Further, the processor 1505 includes a control unit 1535 and an Arithmetic and Logical Unit (ALU) 1540. The ALU 1540 make mathematical and logical decisions for the processor 1505. The control unit 1535 controls the ALU 1540 and the networking device 1510. The electronic device 1500 includes a networking device 1510 for communicating information. Moreover, the electronic device 1500 includes a memory 1525. Examples of the memory 1525 includes a random access memory (RAM) and a dynamic random access memory. The memory 1525 stores temporary information. The electronic device 1500 further includes a storage unit 1520. Examples of the storage unit 1520 includes at least a magnetic disk and an optical disk.

[102] Various embodiments are related to the use of the electronic device 1500 for implementing the techniques described herein. In one embodiment, the techniques are performed by the processor 1505 with information included in the memory 1525. The information is read into the memory 1525 from another machine-readable medium, such as the storage unit 1520. The instructions are stored in the memory 1525. The instructions enable the processor 1505 to parse a webpage, generate at least one logical field marker (LFM) on the webpage, identify supplementary information, store the supplementary information in a phonebook contact, and render the supplementary information to the calling party at the instance of establishing a connection with the called party.

[103] The term “machine-readable medium” as used herein refers to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the electronic device 1500, various machine-readable medium are involved, for example, in providing information to the processor 1505. The machine-readable medium is a storage media. Storage media includes both non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as the storage unit 1520. Volatile media includes dynamic memory, such as the memory 1525. All such media must be tangible to enable the information carried by the media to be detected by a physical mechanism that reads the information into a machine.

[104] Common forms of machine-readable medium include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge. In another embodiment, the machine-readable medium is a transmission media including coaxial cables, copper wire and fibre optics, including the wires. Transmission media is in the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications. The electronic device 1500 also includes a clock 1530 generate clock signals and time the processing cycles of the processor 1505. Examples of the clock 1530 include synchronous clocks and asynchronous clocks.

[105] The electronic device 1500 includes an I/O device 1515. The I/O device 1515 includes user input devices and display devices. Examples of display devices include but is not limited to a cathode ray tube (CRT), a liquid crystal display (LCD) or a light emitting diode (LED) display. Examples of the input device includes a Touchpad, alpha numeric keyboard, touchscreen, stylus, microphone and camera.

[106] Advantageously, the embodiments specified in the present disclosure provide a method and system to render supplementary information of a called party to a calling party. The supplementary information is rendered to the calling party at the instance of the calling party establishing a call connection with a called party. The supplementary information is a menu card if the called party is a restaurant. The present invention enables the calling party to scrolls through the menu card while on call with the called party. As a result, the calling party is enabled to place an order with the called party with ease. Moreover, the present invention provides a method of extracting and parsing contact information from webpages by making use of the plurality of logical field markers. The present invention stores the contact information in a phonebook automatically. This makes adding contacts from webpages easier and time efficient.

[107] In the preceding specification, the present disclosure and its advantages have been described with reference to specific embodiments. However, it will be apparent to a person of ordinary skill in the art that various modifications and changes can be made, without departing from the scope of the present disclosure, as set forth in the claims below.

[108] Accordingly, the specification and figures are to be regarded as illustrative examples of the present disclosure, rather than in restrictive sense. All such possible modifications are intended to be included within the scope of present disclosure.

CLAIMS:1. A method of identifying supplementary information, the method comprising:
parsing a webpage;
generating at least one logical field marker (LFM) on the webpage;
identifying supplementary information; and
storing the supplementary information in a phonebook contact.

2. The method as claimed in claim 1, wherein the supplementary information is
retrieved at the instance of establishing a call connection.

3. The method as claimed in claim 1, wherein a user scrolls through the
supplementary information to place an order.

4. The method as claimed in claim 1, wherein the supplementary information
comprises map directions of a contact in a phonebook.

5. The method as claimed in claim 4, wherein a user navigates the map
directions while making a call with the contact in the phonebook.

6. A method of rendering supplementary information of a called party to a calling
party, the method comprising:
parsing a webpage;
generating at least one logical field marker (LFM) on the webpage;
identifying supplementary information;
storing the supplementary information in a phonebook contact; and
rendering the supplementary information to the calling party at the instance of
establishing a connection with the called party.

7. The method as claimed in claim 6, wherein the at least one LFM is one of a
title marker, a phone number marker, and an attachment marker.

8. The method as claimed in claim 7, wherein supplementary information is
information associated with the attachment marker.

9. The method as claimed in claim 6, wherein a calling party scrolls through
the supplementary information while on call with the called party.

10. The method as claimed in claim 6, wherein the supplementary information
comprises map directions of a contact in a phonebook.

11. The method as claimed in claim 10, wherein the calling party navigates
the map directions while making a call with the contact in the phonebook.

12. The method as claimed in claim 6, wherein parsing the webpage comprises:
invoking a menu on the webpage using a stylus; and
selecting a phonebook option to automatically generate the at least one
logical field marker.

13. The method as claimed in claim 6, wherein parsing the webpage comprises:
invoking a phonebook option by dragging and dropping the webpage in a
contact icon.

14. The method as claimed in claim 6, wherein parsing the webpage comprises:
invoking a phonebook option by selecting a menu button.

15. The method as claimed in claim 6, wherein generating the at least one LFM
comprises
editing the LFM.

16. The method as claimed in claim 15, wherein editing the LFM comprises:
duplicating the LFM;
dragging a duplicate LFM to an additional information; and
identifying additional information to store in the phonebook.

17. The method as claimed in claim 15, wherein editing the LFM comprises:
dragging the LFM to a desired position on the webpage if position of
generated LFM requires change.

18. The method as claimed in claim 15, wherein editing the LFM comprises:
attaching a file from one of a local storage drive, a phone gallery, a camera,
and an external storage source.

19. The method as claimed in claim 6, further comprising
automatically mapping information associated with the at least one LFM
to the phonebook contact.

20. The method as claimed in claim 19, wherein the mapping comprises
mapping information associated with the at least one LFM based on a look-up
table, wherein the look-up table defines rules for associating the LFM with relevant fields in the phonebook contact.

21. A system for rendering supplementary information of a called party to a calling
party, the system comprising:
a webpage parser to parse a webpage;
a logical field marker (LFM) generator to generate at least one logical field
marker (LFM) on the webpage;
an identification module to identify supplementary information;
a phonebook to store the supplementary information; and
a phonebook contact controller for rendering the supplementary information to
the calling party at the instance of establishing a connection with the called party.

22. The system as claimed in claim 21, further comprising an LFM parser to
automatically map information associated with the at least one LFM to a phonebook contact.

23. The system as claimed in claim 21, wherein the at least one LFM is one of a
title marker, a phone number marker, and an attachment marker.

24. The system as claimed in claim 23, wherein supplementary information is
information associated with the attachment marker.

25. The system as claimed in claim 21, wherein the calling party scrolls through
the supplementary information while on call with the called party.

26. The system as claimed in claim 21, wherein the supplementary information
comprises map directions of a contact in the phonebook.

27. The system as claimed in claim 26, wherein the calling party navigates
the map directions while making a call with the contact in the phonebook.

28. The system as claimed in claim 21, wherein parsing the webpage comprises:
invoking a menu on the webpage using a stylus; and
selecting a phonebook option to automatically generate the at least one
logical field marker.

29. The system as claimed in claim 21, wherein parsing the webpage comprises:
invoking a phonebook option by dragging and dropping the webpage in a
contact icon.

30. The system as claimed in claim 21, wherein parsing the webpage comprises:
invoking a phonebook option by selecting a menu button.

31. The system as claimed in claim 21, wherein generating the at least one LFM
comprises
editing the LFM.

32. The system as claimed in claim 31, wherein editing the LFM comprises:
duplicating the LFM;
dragging a duplicate LFM to an additional information; and
identifying additional information to store in the phonebook.

33. The system as claimed in claim 31, wherein editing the LFM comprises:
dragging the LFM to a desired position on the webpage if position of
generated LFM requires change.

34. The system as claimed in claim 31, wherein editing the LFM comprises:
attaching a file from one of a local storage drive, a phone gallery, a camera,
and an external storage source.

35. An electronic device for rendering supplementary information of a called party
to a calling party, the electronic device comprising:
a memory for storing instructions;
a processor coupled to the memory and responsive to the instructions;
wherein the instructions enable the processor to:
parse a webpage;
generate at least one logical field marker (LFM) on the webpage;
identify supplementary information;
store the supplementary information in a phonebook contact; and
render the supplementary information to the calling party at the
instance of establishing a connection with the called party.