Abstract: The embodiments herein provide a method and system for automatically displaying an item for communication with a contact stored in an electronic device. The method includes storing a frequency of usage of the item for the contact in a Frequently Opted Communication Application (FOCA) database. Further, the method includes receiving an interaction event performed on the contact in the electronic device. Furthermore, the method includes identifying the item for communication with the contact from the FOCA database and displaying the identified item on the electronic device as a response to the interaction event performed on the contact. FIG. 1
CLIAMS:We claim:
1. A method for automatically displaying at least one item for communication with at least one contact stored in an electronic device, the method comprising:
storing a frequency of usage of at least one item for each said contact in a database;
receiving at least one interaction event performed on at least one said contact in said electronic device;
identifying at least one said item for communication with at least one said contact from said database; and
displaying said at least one identified item on said electronic device as a response to said interaction event performed on at least one said contact.
2. The method of claim 1, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and a long range communication application.
3. The method of claim 1, wherein storing said frequency of usage of at least one item for each said contact in said database further comprises:
tracking at least said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
4. The method of claim 1, wherein said method further comprises displaying said at least one item along with each said contact in at least one said contact list of said electronic device, wherein said at least one item is selected for display from said database.
5. A method for automatically displaying at least one contact associated with at least one item in an electronic device, the method comprising:
storing a frequency of communication with at least one said contact using each said item in a database;
receiving at least one interaction event performed on at least one said item in said electronic device;
identifying at least one said contact associated with at least one said item from said database; and
displaying said at least one identified contact on said electronic device as a response to said event performed on at least one said item.
6. The method of claim 5, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
7. The method of claim 5, wherein storing said frequency of usage with at least one contact using each said item in said database further comprises:
tracking at least said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
8. An electronic device for automatically displaying at least one item for communication with at least one contact, the electronic device comprising a controller configured to:
store a frequency of usage of at least one item for at least one said contact in a database;
receive at least one interaction event performed on at least one said contact in said electronic device;
identify at least one said item for communication with at least one said contact from said database; and
display said at least one identified item on said electronic device as a response to said interaction event performed on at least one said contact.
9. The electronic device of claim 8, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
10. The electronic device of claim 8, wherein store said frequency of usage of at least one item for at least one said contact in said database further comprises:
track at least said item used to communicate with at least one said contact in said electronic device;
count said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
store said at least one said frequency of usage of at least one item for at least one said contact in said database.
11. The electronic device of claim 8, wherein said controller is further configured to display said at least one said item along with at least one said contact in at least one contact list of said electronic device, wherein said at least one said item is selected for display from said database.
12. An electronic device for automatically displaying at least one contact associated with at least one item in an electronic device, the electronic device comprising a controller configured to:
store a frequency of communication with at least one said contact using each said item in a database;
receive at least one event performed on at least one said item in said electronic device;
identifying at least one said contact associated with at least one said item from said database; and
display said at least one identified contact on said electronic device as a response to said event performed on at least one said item.
13. The electronic device of claim 12, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
14. The electronic device of claim 12, wherein store said frequency of usage with at least one said contact using each said item in said database further comprises:
track at least one said item used to communicate with each contact in said electronic device;
count said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
store said at least one said frequency of usage of at least one said item for at least one said contact in said database.
15. A computer program product comprising a computer executable program code recorded on a computer readable non-transitory storage medium, wherein said computer executable program code when executed causing the actions including:
storing a frequency of usage of at least one item for at least one said contact in a database;
receiving at least one interaction event performed on at least one said contact in said electronic device;
identifying at least one said item for communication with at least one said contact from said database; and
displaying said at least one identified item on said electronic device as a response to said interaction event performed on at least one said contact.
16. The computer program product of claim 15, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
17. The computer program product of claim 15, wherein storing frequency of usage of at least one said item for at least one said contact in said database further comprising:
tracking at least said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one said item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
18. The computer program product of claim 15, wherein said computer executable program code when executed causing the actions including displaying said at least one item along with at least one said contact in at least one contact list of said electronic device, wherein said at least one said item is selected for display from said database.
19. A computer program product comprising a computer executable program code recorded on a computer readable non-transitory storage medium, wherein said computer executable program code when executed causing the actions including:
storing a frequency of communication with at least one contact using at least one said item in a database;
receiving at least one interaction event performed on at least one said item in said electronic device;
identifying at least one said contact associated with at least one said item from said database; and
displaying said at least one identified contact on said electronic device as a response to said event performed on at least one said item.
20. The computer program product of claim 19, wherein said item comprises a short message service, application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
21. The computer program product of claim 19, wherein storing said frequency of usage with at least one said contact using at least one said item in said database further comprises:
tracking at least one said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one said item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
Dated: 30th Day of April, 2014 Signature
Arun Kishore Narasani Patent Agent ,TagSPECI:FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005
COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)
TITLE OF THE INVENTION
“Method for communication with a contact”
APPLICANTS:
Name : Samsung India Electronics Pvt Ltd.
Nationality : Indian.
Address : Logix Cyber Park Tower C 8th to 10th floor, Tower D, Ground to 10th floor, Plot No.C - 28-29, Sector -62, Noida-201301 (U.P), India
The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-
FIELD OF INVENTION
[001] The embodiments herein generally relate to selecting communication modes. More particularly to a mechanism for selecting a Frequently Opted Communication Application (FOCA) for communication with a contact stored in an electronic device in response to receiving a gesture event performed on the contact.
BACKGROUND OF THE INVENTION
[002] Increasingly there are communication devices available which can allow a user to communicate in several different modes. The different modes of communication include, for example, but not limited to, Short Message Service (SMS), Multimedia Message Service (MMS), electronic mail, Instant Messaging (IM), social network service (SNS), and the like. Generally whenever a user wants to access one of the communication modes in a conventional mobile device, the user has to often pass through various options available in the mobile device.
[003] Different systems and methods are proposed to automatically select a communication mode suitable for a user. The conventional mechanism allows the user to swipe on a contact name to either message or call a person. Further, there are mechanisms to suggest a list of communication modes available on swipe performed on a contact name. Furthermore, there are mechanisms that automatically select the communication mode for communicating between two user devices based on the abilities of the user devices and/or the preferences of the users. However, all these mechanisms are hard coded into the system and are not intuitive to the user, especially when the user actually wants to establish the communication through IM, SMS, MMS, SNS, email, or other mode.
[004] Thus, there is a need in the art for a robust and simple system and method for effectively selecting a communication mode for a user, more particularly when the user desires to establish the communication with the contacts stored in the electronic device through IM, SMS, MMS, SNS, email, or other modes.
[005] The above information is presented as background information only to help the reader to understand the present invention. Applicants have made no determination and make no assertion as to whether any of the above might be applicable as Prior Art with regard to the present application.
OBJECT OF INVENTION
[006] The principal object of the embodiments herein is to provide a method for automatically displaying a Frequently Opted Communication Application (FOCA) for communication with a contact stored in an electronic device in response to receiving a gesture event performed on the contact.
[007] Another object of the embodiments herein is to provide a mechanism for automatically invoking a Frequently Opted Communication Application (FOCA) for communication with a contact stored in an electronic device in response to receiving a gesture event performed on the contact.
SUMMARY
[008] Accordingly the embodiments herein provide a method for automatically displaying an item for communication with a contact stored in an electronic device. The method includes storing a frequency of usage of the item for the contact in a Frequently Opted Communication Application (FOCA) database. Further, the method includes receiving an interaction event performed on the contact in the electronic device. Furthermore, the method includes identifying the item for communication with the contact from the FOCA database and displaying the identified item on the electronic device as a response to the interaction event performed on the contact.
[009] Accordingly the embodiments herein provide a method for automatically displaying a contact associated with an item in an electronic device. The method includes storing a frequency of communication with the contact using the item in a Frequently Opted Communication Application (FOCA) database. Further, the method includes receiving an interaction event performed on the item in the electronic device. Furthermore, the method includes identifying the contact associated with the item from the FOCA database and displaying the identified contact on the electronic device as a response to the interaction event performed on the item.
[0010] Accordingly the embodiments herein provide an electronic device for automatically displaying an item for communication with a contact. The electronic device includes a Frequently Opted Communication Application (FOCA) controller configured to store a frequency of usage of an item for the contact in a FOCA database. Further, the FOCA controller is configured to receive an interaction event performed on the contact in the electronic device. Furthermore, the FOCA controller is configured to identify the item for communication with the contact from the FOCA database. Furthermore, the FOCA controller is configured to display the identified item on the electronic device as a response to the interaction event performed on the contact.
[0011] Accordingly the embodiments herein provide an electronic device for automatically displaying a contact associated with an item in an electronic device. The electronic device includes a Frequently Opted Communication Application (FOCA) controller configured to store a frequency of communication with the contact using the item in a FOCA database. Further, the FOCA controller is configured to receive an interaction event performed on the item in the electronic device. Furthermore, the FOCA controller is configured to identify the contact associated with the item from the FOCA database. Furthermore, the FOCA controller is configured to display the identified contact on the electronic device as a response to the interaction event performed on the item.
[0012] Accordingly the embodiments herein provide a computer program product including a computer executable program code recorded on a computer readable non-transitory storage medium, the computer executable program code when executed causing the actions including automatically displaying an item for communication with a contact stored in an electronic device. Further the computer executable program code when executed causing the actions including storing a frequency of usage of an item for a contact in a frequently opted communication application (FOCA) database. Furthermore, the computer executable program code when executed causing the actions including receiving an interaction event performed on the contact in the electronic device. The computer executable program code when executed causing the actions including identifying the item for communication with the contact from the FOCA database. Furthermore, the computer executable program code when executed causing the actions including displaying the identified item on the electronic device as a response to the interaction event performed on the contact.
[0013] Accordingly the embodiments herein provide a computer program product including a computer executable program code recorded on a computer readable non-transitory storage medium, the computer executable program code when executed causing the actions including automatically displaying an item for communication with a contact stored in an electronic device. Further, the computer executable program code when executed causing the actions including storing a frequency of communication with a contact using the item in a frequently opted communication application (FOCA) database. Furthermore, the computer executable program code when executed causing the actions including receiving an interaction event performed on the item in the electronic device. Furthermore, the computer executable program code when executed causing the actions including identifying the contact associated with the item from the FOCA database. Furthermore, the computer executable program code when executed causing the actions including displaying the contact on the electronic device as a response to the interaction event performed on the item.
[0014] 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 FIGURES
[0015] This invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0016] FIG. 1 illustrates a high level overview of a system for invoking Frequently Opted Communication Application (FOCA), according to embodiments as disclosed herein;
[0017] FIG. 2 example illustration showing a detailed overview of a FOCA controller and a FOCA database, according to embodiments as disclosed herein;
[0018] FIG. 3 illustrates various operations performed by the system, according to embodiments as disclosed herein;
[0019] FIG. 4 illustrates an example system block diagram in an example mobile operating system environment, according to embodiments as disclosed herein;
[0020] FIG. 5 is a flow diagram illustrating a method for automatically displaying an item for communicating with a contact stored in an electronic device, according to embodiments as disclosed herein;
[0021] FIG. 6 is a flow diagram illustrating a method for automatically displaying a contact associated with an item in an electronic device, according to embodiments as disclosed herein;
[0022] FIGS. 7a – 7e illustrates an example scenario of frequent mode communication associated with a contact, according to embodiments as disclosed herein;
[0023] FIGS. 8a – 8d illustrates an example scenario of making a user interested application as a default application for a contact, according to embodiments as disclosed herein;
[0024] FIGS. 9a and 9b illustrates an example scenario of a frequent short range communication invoked for communication with a contact, according to embodiments as disclosed herein; and
[0025] FIG. 10 illustrates a computing environment implementing the method and system for automatically displaying an item for communicating with a contact stored in an electronic device, according to embodiments as disclosed herein.
DETAILED DESCRIPTION OF INVENTION
[0026] 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. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0027] The embodiments herein disclose a system and method for automatically displaying an item for communication with a contact stored in an electronic device. The method includes storing a frequency of usage of the item for the contact in a Frequently Opted Communication Application (FOCA) database. Further, the method includes receiving a gesture event performed on the contact in the electronic device. Further, the method comprises identifying the item for communication with the contact from the FOCA database. Furthermore, the method includes displaying the identified item on the electronic device as a response to the gesture event performed on the contact. In conventional systems, where the user needs to follow multiple steps to open other mode of communication with the same contact. Unlike conventional systems, the user can save time to launch the frequent mode of communication item associated with the contact thereby increasing the overall user experience of the system.
[0028] Further, the embodiments herein disclose a system and method for automatically displaying a contact associated with an item in an electronic device. The method includes storing a frequency of communication with the contact using the item in the FOCA database. Further, the method includes receiving a gesture event performed on the item in the electronic device. Furthermore, the method includes identifying the contact associated with the item in the electronic device. Furthermore, the method includes displaying the identified contact on the electronic device as a response to the event performed on the item. Unlike conventional systems, fast access to perform direct action for the contact name in phone book, call log, chat-on or other applications can be achieved based on the frequency of particular communication modes with the contact.
[0029] Throughout the description the term contact and contact name are used interchangeably.
[0030] Throughout the description the term gesture event and interaction event are used interchangeably.
[0031] Referring now to the drawings, and more particularly to FIGS. 1 through 10, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
[0032] FIG. 1 illustrates a high level overview of a system for invoking a Frequently Opted Communication Application (FOCA), according to embodiments as disclosed herein. In an embodiment, the electronic device 100 can be, for example and not limited to laptop, desktop computer, mobile phone, smart phone, Personal Digital Assistants (PDAs), tablet, phablet, consumer electronic device, server, or any other electronic device. The electronic device 100 can be configured to include a FOCA controller 102, a contacts database 104, an application manager 106, a gesture recognition module 108, a display module 110, a communication module 112, and a FOCA database 114.
[0033] In an embodiment, the FOCA controller 102 can be configured to receive an item for communication with a contact stored in the electronic device 100. The contact described herein can be a VCF or CSV file stored in the electronic device 100 having details of a person such as name, mobile number, email, and the like. Each contact can be associated with, for example, but not limited to, a phonebook application, a call log application, a chat-on application, a Social Networking Service (SNS) application, and so on. In an embodiment, the item described herein can be, for example, but not limited to, a Short Message Service (SMS) application, a Multimedia Messaging Service (MMS) application, an Electronic Mail (Email) application, an Instant Message (IM) application, a SNS application, a call application, a short range communication application, a long range communication application, and the like.
[0034] Further, the FOCA controller 102 can be configured to track the item used to communicate with the contact in the electronic device 100. Based on the tracked information, the FOCA controller 102 further configured to count the frequency of usage of the item associated with the contact. The FOCA controller 102 can be configured to store the frequency of usage of the item for the contact in the FOCA database 114.
[0035] In an embodiment, the FOCA database 114 described herein can be stored locally in the electronic device or remotely in the cloud. The FOCA database 114 on the cloud can be used, for example, to synchronize the FOCA information associated with one electronic device of the user with other electronic devices of the user.
[0036] Further, the FOCA controller 102 can be configured to add a contact ID and the requested item as package name into the FOCA database 114. For example, the contact name can be associated with the contact ID in the electronic device 100. The contact ID can be associated with multiple applications such as Chat-on ID, Video Call, SNS1, SNS2, or the like. Each of the fields can be linked by a common ID in the electronic device 100, called the contact ID. In the event of the gesture performed on the contact ID, such as sending an email then a contact name, a package name and a contact ID are linked by the electronic device 100.
[0037] Further, the FOCA controller 102 can be configured to receive the frequency of usage of various items associated with different contacts from the FOCA database 114 after performing the gesture event on the item in the electronic device 100. The FOCA controller 102 can be further configured to identify the contact associated with the item from the frequency of usage of various items associated with different contacts IDs obtained from the FOCA database 114. Further, the FOCA controller 102 can be configured to display the contact on the electronic device 100 as a response to the event performed on the item. Unlike conventional systems, fast access to perform direct actions for a contact name in the Phonebook application, Call log application, Chat-on application, or other applications is achieved based on frequency of particular communication with the contact using the item.
[0038] In an embodiment, the FOCA database 114 can be configured to store the frequency of usage of an item for the contact in the electronic device 100. Further, the FOCA database 114 can be configured to provide the frequency of usage of various items for different contacts to the FOCA controller 102.
[0039] In an embodiment, the FOCA database 114 can be configured to store the frequency of usage of a contact associated with an item in the electronic device 100. Further, the FOCA database 114 can be configured to provide the frequency of usage of various contacts associated with the different items to the FOCA controller 102.
[0040] In an embodiment, the contacts database 104 can be configured to store various contacts of the user of the electronic device 100. The contacts database 104 can be configured to provide various contacts associated with different users to the FOCA controller 110. In an embodiment, the application manager 106 can be configured to receive the frequent mode of communication item associated with the contact from the FOCA controller 102. The application manager 106 can be configured to launch the frequent mode of communication item associated with the contact in the electronic device 100.
[0041] In an embodiment, the gesture recognition module 108 can be configured to receive and identify the gesture event performed on the contact in the electronic device 100. The gesture recognition module 108 can be configured to provide the gesture event information performed on the contact to the FOCA controller 102.
[0042] In an embodiment, the display module 110 can be configured to display the frequent mode of communication item associated with the contact on the electronic device 100.
[0043] The FIG. 1 shows a limited overview of the system but, it is to be understood that another embodiment is not limited thereto. Further, the system can include different modules communicating among each other along with other hardware or software components. For example, the component can be, but not limited to, a process running in the electronic device, an executable process, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on an electronic device and the electronic device can be the component.
[0044] FIG. 2 example illustration showing a detailed overview 200 of the FOCA controller 102 and FOCA database 114, according to embodiments as disclosed herein. In an embodiment, the application name (i.e. package name) and the contact ID are given as input to the FOCA controller 102 as shown in the FIG. 2. The FOCA controller 102 can be configured to add this information into the FOCA database 114 as the source contact ID and requested intent as package name and increases the counter of the application occurrences from 0 to n. If already same application has some count then the FOCA controller 102 will increase the counter. The FOCA database 114 can store the unique contact ID with frequent communication application (package name of the application) like Chat-on, SNS, Email, etc. For example, the contact name can be associated with the contact ID in the electronic device 100. The contact ID can be associated with multiple applications such as Chat-on ID, email ID, SNS ID, Video Call or the like. Each of the fields can be linked by a common ID on the electronic device, called the contact ID. In the event of the gesture performed on the contact ID, such as sending an email then a contact name a package name and a contact ID are linked by the electronic device 100.The FOCA database 114 maintains the application priority list for the particular contact ID as high, medium, and low frequency (counter of the application). For example, the contact IDs such as 123_xyz, 673_xyz, and 990_xyz along with frequent communication application (i.e. packages names of the application) such as Chat-on, SNS, email, etc. are shown below in Table 1. The frequency of usage of different applications (application intent counter) for each and every contact ID as shown below in the Table 1 can be stored in the FOCA database 114. The count of occurrence of the item (example shown in the Table 1) can be increased from 0 to n and if already same item has some count then the FOCA controller 102 may increase the count of occurrence of the item.
Contact ID : 123_xyz Contact ID : 673_xyz Contact ID : 990_xyz
App Name Occurrence count App Name Occurrence count App Name Occurrence count
Chat-On 5 Chat-On 2 Chat-On 15
SNS1 8 SNS1 12 SNS1 9
email 2 email 5 email 2
SNS2 20 SNS2 4 SNS2 8
Table 1
[0045] For example, the application priority list for the particular contact IDs such as 123_xyz, 673_xyz, and 990_xyz as High, Medium, and Low frequency are stored in the FOCA list as shown in the FIG. 2.
[0046] In another embodiment, the application name (i.e. package name) and the contact ID are provided as an input to the FOCA controller 102 as shown in the FIG. 2. When an intent call from the item enables the contact to communicate through the item, the FOCA controller 102 can add this information into the FOCA database 114 as the item and requested contact and increases the counter of the contact occurrences from 0 to n. If already same contact has some count then the FOCA controller 102 will increase the counter. The FOCA database 114 can store the item with frequently communicated contact. The FOCA database 114 maintains the contact priority list for the particular item as high, medium, and low frequency. For example, the applications such as Chat-on, SNS1, and email along with contact IDs such as 456_xyz, 324_xyz, and 879_xyz are shown below in Table 2.
App name : Chat-on App name : SNS1 App name : email
Contact ID Occurrence count Contact ID Occurrence count Contact ID Occurrence count
456_xyz 5 456_xyz 2 456_xyz 15
324_xyz 8 324_xyz 12 324_xyz 9
879_xyz 2 879_xyz 5 879_xyz 2
Table 2
[0047] For example, the contact priority list for the particular application as High, Medium, and Low frequency are stored in the FOCA list as shown in Table 3. Further, in an embodiment, the FOCA controller 102 can the user to manually prioritize the list pursuant to the requirement.
Table 3
[0048] FIG. 3 illustrates various operations performed by the system, according to embodiments as disclosed herein. In an embodiment, at 302, the gesture recognition module 112 can receive the input from the user. The input can be a gesture event such as a swipe or slide gesture performed on the contact in the electronic device 100. A slide listener can receive the input from the gesture recognition module 112. At 304, the gesture recognition module 112 can be configured to send the request to the FOCA controller 102 to receive the list of frequent communication mode applications and then decide which application can be opened as a response to the gesture performed on the contact in the electronic device 100. In an embodiment, a user interface (UI) icon represent the frequent communication mode for the contact which may provide an hint to the user that the frequent communication mode for the particular contact is a Chat-on, email, or the like. The user can be able to manage the frequent communication mode associated with the contact list by selecting and reshuffling the list content (Refer to the FIGS. 7a – 7e, and FIGS. 8a – 8d).
[0049] Further, at 306, the FOCA controller 102 can be configured to receive the frequency of usage of various applications associated with different contacts from the FOCA database 114. Further, the FOCA controller 102 can be configured to identify the application for communication with the contact from the frequency of usage of various applications associated with different contacts obtained from the FOCA database 114. At 308, the application manager 106 can be configured to receive the frequent mode of communication application associated with the contact from the FOCA controller 102 and automatically launch the application associated with the contact in the electronic device 100. At 310, the display module108 can be configured to display the application associated with the contact on the electronic device 100 as part of the output.
[0050] FIG. 4 illustrates an example system block diagram in an example mobile operating system environment, according to embodiments as disclosed herein. In an embodiment, the FOCA database 114 and the FOCA controller 102 can be a part of the system for managing frequent applications and storing in the FOCA database 114. Upon performing a gesture event on the contact, the FOCA database 114 and the FOCA controller 102 can be configured to determine an appropriate application for sending the request to the application manager 106 to open/manage other applications with the contact. The gesture recognition module 108 can be configured to track the gesture event performed on the contact in the contact application or the call log application. The telephony manager interface 402 can be configured to allow access to the telephony manager to perform other telephony related functions like MMS. The FOCA database 114 can be configured to store the application name (i.e. package name) occurrence counter with associated contact ID as shown in the Table 1. Further, the FOCA controller 102 can be enabled to add the source contact ID and requested intent as package name and increase occurrences of the counter from 0 to n. Further, the application manager 106 can be enabled to call the associated application such as to launch the application with related contact.
[0051] FIG. 5 is a flow diagram illustrating a method 500 for automatically displaying an item for communicating with a contact stored in an electronic device 100, according to embodiments as disclosed herein. In an embodiment, at step 502, the method 500 includes receiving the item associated with the contact in the electronic device 100. The method 500 allows the FOCA controller 102 to receive the item associated with the contact in the electronic device 100. The item for communication with the contact is provided after performing a gesture event on the contact in the electronic device 100. In an embodiment, the gesture event described herein can be, for example, but not limited to, a swipe gesture, a slide gesture, a tap gesture, a voice gesture, a hover gesture, and the like. At step 504, the method 500 includes counting the frequency of usage of the item associated with the contact. The method 500 allows the FOCA controller 102 to track the item used to communicate with the contact in the electronic device 100. Further, the method 500 allows the FOCA controller 102 to count the frequency of usage of the item associated with the contact in the electronic device 100.
[0052] At step 506, the method 500 includes storing the frequency of usage of the item for the contact in the FOCA database 114. At step 508, the method 500 includes receiving the gesture event performed on the contact in the electronic device 100. The method 500 allows the gesture recognition module 108 to receive and identify the gesture event performed on the contact in the electronic device 100. Further, the method 500 allows the gesture recognition module 108 to provide the gesture event to the FOCA controller 102.
[0053] At step 510, the method 500 includes identifying the item for communication associated with the contact from the FOCA database 114. The method 500 allows the FOCA controller 102 to identify the item for communication with the contact from the FOCA database 114. At step 512, the method 500 includes displaying the identified item on the electronic device 100 in response to the gesture event performed on the contact. The method 500 allows the display module 110 to display the identified item on the electronic device 100 for the gesture event on the contact.
[0054] At step 514, the method 500 includes frequently monitoring communication activities associated with the contact in the electronic device 100. The method 500 allows the FOCA controller 102 to frequently monitor the communication activities associated with the contact. At step 516, the method 500 includes determining whether any changes are detected in the communication activities associated with the contact. Further, the method includes repeating the steps 506 to 516 in response to detecting any change in the communication activities associated with the contact.
[0055] The various actions, acts, blocks, steps, and the like in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions, acts, blocks, steps, and the like may be omitted, added, modified, skipped, and the like without departing from the scope of the invention.
[0056] FIG. 6 is a flow diagram illustrating a method 600 for automatically displaying a contact associated with an item in an electronic device 100, according to embodiments as disclosed herein. In an embodiment, at step 602, the method 600 includes receiving the contact associated with the item in the electronic device 100. The method 600 allows the FOCA controller 102 to receive the contact associated with the item in the electronic device 100. The method 600 provides the contact for communicating through the item after performing a gesture event on the item in the electronic device 100. In an embodiment, the gesture event described herein can be, for example, but not limited to, a swipe gesture, a tap gesture, a slide gesture, a voice gesture, a hover gesture, and the like. At step 604, the method 600 allows counting the frequency of usage of the item associated with the contact. The method 600 allows the FOCA controller 102 to track the communication to the contact associated with the item in the electronic device 100. Further, the method 600 allows the FOCA controller 102 to count the frequency of usage of the item associated with the contact in the electronic device 100.
[0057] At step 606, the method 600 includes storing the frequency of communication with the contact using the item in the FOCA database 114. The method 600 allows the FOCA controller 102 to track the item used to communicate with the contact in the electronic device 100. Based on the tracked information, the method 600 allows the FOCA controller 102 to count the frequency of usage of the item associated with the contact in the electronic device 100. Further, the method 600 allows the FOCA controller 102 to store the frequency of usage of the item for the contact in the FOCA database 114.
[0058] At step 608, the method 600 includes receiving the gesture event performed on the item in the electronic device 100. The method 600 allows the gesture recognition module 108 to receive and identify the gesture event on the item in the electronic device 100. Further, the method 600 allows the gesture recognition module 108 to the identified gesture event to the FOCA controller 102.
[0059] At step 610, the method 600 includes identifying the contact associated with the item from the FOCA database 114. The method 600 allows the FOCA controller 102 to identify the contact to communicate using the item from the FOCA database 114. At step 612, the method 600 includes displaying the identified contact on the electronic device 100 as a response to the gesture event performed on the item. The method 600 allows the display module 110 to display the identified contact on the electronic device 100 for the gesture event performed on the item. Unlike conventional systems, the frequent mode of communication with the contact using the item can be displayed on the electronic device 100.
[0060] At step 614, the method 600 includes frequently monitoring communication activities associated with the item in the electronic device 100. The method 600 allows the FOCA controller 102 to frequently monitor the communication activities associated with the item. At step 616, the method 600 includes determining whether any changes are detected in the communication activities associated with the item. Further, the method 600 includes repeating the steps 606 to 616 in response to determining any changes in the communication activities associated with the item.
[0061] The various actions, acts, blocks, steps, and the like in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions, acts, blocks, steps, and the like may be omitted, added, modified, skipped, and the like without departing from the scope of the invention.
[0062] FIGS. 7a – 7e illustrates an example scenario of a frequent mode communication item associated with a contact in the electronic device 100, according to embodiments as disclosed herein. In an embodiment, the items along with various contacts in the call log list of the electronic device 100 are displayed on the electronic device 100 as shown in the FIG. 7a. For example, the item “email application” is displayed as a frequent mode of communication for the contact “Dan Banderet”, and “Mark Xerri”. The item “Chat-on application” is displayed as a frequent mode of communication for the contact “Darren Allen”. The item “SNS1 application” is displyed as a frequent mode of communication for the contact “Matt Smith”. The item “SNS2 application” is displayed as a frequent mode of communication for the contact “Dan Wright”. In an embodiment, if the gesture event is performed on the contact “Dan Banderet” as shown in the FIG. 7b for communication, then the item “email application” can be automatically launched as a suitable communication mode to send a message to the contact “Dan Banderet” as shown in the FIG. 7c.
[0063] In another embodiment, if the gesture event is performed on the contact “Matt smith” as shown in the FIG. 7d for communication, then the item “Messaging application” can be automatically launched as a suitable communication mode to send a message to the contact “Matt smith” as shown in the FIG. 7e.
[0064] FIGS. 8a – 8d illustrates an example scenario of making a user interested application as a default application for a contact, according to embodiments as disclosed herein. In case of more than one mode of communication is associated with the contact “Dan Banderet” with same frequency, a list of actions can be shown to the user to choose upon on performing the gesture event In an example, as shown in the FIG. 8a, if the gesture event is performed on the contact “Dan Banderet” then a list of frequent communication mode indicator like email, chat-on, SNS, and the like can be displayed as shown in the FIG. 8b. The FOCA controller 102 can allow the user to configure the priority for the desired communication modes. As shown in the FIG. 8c, the frequent mode list can include a high, medium, and low frequency modes of communication, such as to allow the user to change the priority of frequent communication mode. As shown in the FIGS. 8c and 8d, the preferred communication mode associated with the contact “Dan Banderet” can be changed to the application “Chat-on” by performing gesture event on the application. In an embodiment, where the IM is selected as the preferred communication for the contact, the FOCA controller 102 can be configured to check the availability of the user. If the contact is available online then the IM is selected as the preferred mode of communication with the other contact else other communication mode is selected from the list. Further, in an embodiment, the FOCA controller 102 can allow the user to manually priorities the list pursuant to the user requirement.
[0065] FIGS. 9a and 9b illustrates an example scenario of a frequent short range communication invoked for communication with a contact, according to embodiments as disclosed herein. In an embodiment, the various short range communication applications can also be launched for the paired device of the contacts with the electronic device 100. As shown in the FIG. 9a, the various short range communication application associated with one or more paired devices is displayed on the electronic device 100. For example, the “a paired device of contact 2” is displayed along with the short range communication “Bluetooth” indicating that the most frequent communication mode for the contact 2 is Bluetooth. The “a paired device of contact 4” is displayed along with the short range communication “Near Field Communication (NFC)” indicating that the most frequent communication mode for the contact 4 is NFC. The “a paired device of contact 1” is displayed along with the short range communication “Infrared” indicating that the most frequent communication mode for the contact 1 is Infrared. The “a paired device of contact 3” is displayed along with the short range communication “Wi-Fi direct” indicating that the most frequent communication mode for the contact 3 is Wi-Fi direct.
[0066] In an embodiment, the FOCA controller 102 can allow the user to select or prioritize the paired devices for communication with the contacts using a short range communication. As shown in the FIG. 9b and the FIG 9c, Bluetooth can be associated with the device of contact 2, device of contact 3, and device of contact 4. The user can prioritize the devices for communication. For example as shown in the FIG. 9d, the user select the device of contact 3 as a preferred mode of communication, such that the FOCA controller 102 can automatically invoke the Bluetooth application for communication as a response to gesture operation performed on the contact 3.
[0067] FIG. 10 illustrates a computing environment implementing the method and system for automatically displaying an item for communicating with a contact stored in an electronic device, according to embodiments as disclosed herein. As depicted in the figure, the computing environment 1001 comprises at least one processing unit 1004 that is equipped with a control unit 1002 and an Arithmetic Logic Unit (ALU) 1003, a memory 1005, a storage unit 1006, plurality of networking devices 1008 and a plurality Input output (I/O) devices 1007. The processing unit 1004 is responsible for processing the instructions of the algorithm. The processing unit 1004 receives commands from the control unit in order to perform its processing. Further, any logical and arithmetic operations involved in the execution of the instructions are computed with the help of the ALU 1003.
[0068] The overall computing environment 1001 can be composed of multiple homogeneous and/or heterogeneous cores, multiple CPUs of different kinds, special media and other accelerators. The processing unit 1004 is responsible for processing the instructions of the algorithm. Further, the plurality of processing units 1004 may be located on a single chip or over multiple chips.
[0069] The algorithm comprising of instructions and codes required for the implementation are stored in either the memory unit 1005 or the storage 1006 or both. At the time of execution, the instructions may be fetched from the corresponding memory 1005 and/or storage 1006, and executed by the processing unit 1004.
[0070] In case of any hardware implementations various networking devices 1008 or external I/O devices 1007 may be connected to the computing environment to support the implementation through the networking unit and the I/O device unit.
[0071] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in Figs. 1, 2 and 10 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0072] 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 from 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 embodiments as described herein.
STATEMENT OF CLAIMS
We claim:
1. A method for automatically displaying at least one item for communication with at least one contact stored in an electronic device, the method comprising:
storing a frequency of usage of at least one item for each said contact in a database;
receiving at least one interaction event performed on at least one said contact in said electronic device;
identifying at least one said item for communication with at least one said contact from said database; and
displaying said at least one identified item on said electronic device as a response to said interaction event performed on at least one said contact.
2. The method of claim 1, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and a long range communication application.
3. The method of claim 1, wherein storing said frequency of usage of at least one item for each said contact in said database further comprises:
tracking at least said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
4. The method of claim 1, wherein said method further comprises displaying said at least one item along with each said contact in at least one said contact list of said electronic device, wherein said at least one item is selected for display from said database.
5. A method for automatically displaying at least one contact associated with at least one item in an electronic device, the method comprising:
storing a frequency of communication with at least one said contact using each said item in a database;
receiving at least one interaction event performed on at least one said item in said electronic device;
identifying at least one said contact associated with at least one said item from said database; and
displaying said at least one identified contact on said electronic device as a response to said event performed on at least one said item.
6. The method of claim 5, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
7. The method of claim 5, wherein storing said frequency of usage with at least one contact using each said item in said database further comprises:
tracking at least said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
8. An electronic device for automatically displaying at least one item for communication with at least one contact, the electronic device comprising a controller configured to:
store a frequency of usage of at least one item for at least one said contact in a database;
receive at least one interaction event performed on at least one said contact in said electronic device;
identify at least one said item for communication with at least one said contact from said database; and
display said at least one identified item on said electronic device as a response to said interaction event performed on at least one said contact.
9. The electronic device of claim 8, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
10. The electronic device of claim 8, wherein store said frequency of usage of at least one item for at least one said contact in said database further comprises:
track at least said item used to communicate with at least one said contact in said electronic device;
count said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
store said at least one said frequency of usage of at least one item for at least one said contact in said database.
11. The electronic device of claim 8, wherein said controller is further configured to display said at least one said item along with at least one said contact in at least one contact list of said electronic device, wherein said at least one said item is selected for display from said database.
12. An electronic device for automatically displaying at least one contact associated with at least one item in an electronic device, the electronic device comprising a controller configured to:
store a frequency of communication with at least one said contact using each said item in a database;
receive at least one event performed on at least one said item in said electronic device;
identifying at least one said contact associated with at least one said item from said database; and
display said at least one identified contact on said electronic device as a response to said event performed on at least one said item.
13. The electronic device of claim 12, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
14. The electronic device of claim 12, wherein store said frequency of usage with at least one said contact using each said item in said database further comprises:
track at least one said item used to communicate with each contact in said electronic device;
count said frequency of usage of said at least one item associated with at least one said contact based on said tracking; and
store said at least one said frequency of usage of at least one said item for at least one said contact in said database.
15. A computer program product comprising a computer executable program code recorded on a computer readable non-transitory storage medium, wherein said computer executable program code when executed causing the actions including:
storing a frequency of usage of at least one item for at least one said contact in a database;
receiving at least one interaction event performed on at least one said contact in said electronic device;
identifying at least one said item for communication with at least one said contact from said database; and
displaying said at least one identified item on said electronic device as a response to said interaction event performed on at least one said contact.
16. The computer program product of claim 15, wherein said item comprises a short message service application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
17. The computer program product of claim 15, wherein storing frequency of usage of at least one said item for at least one said contact in said database further comprising:
tracking at least said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one said item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
18. The computer program product of claim 15, wherein said computer executable program code when executed causing the actions including displaying said at least one item along with at least one said contact in at least one contact list of said electronic device, wherein said at least one said item is selected for display from said database.
19. A computer program product comprising a computer executable program code recorded on a computer readable non-transitory storage medium, wherein said computer executable program code when executed causing the actions including:
storing a frequency of communication with at least one contact using at least one said item in a database;
receiving at least one interaction event performed on at least one said item in said electronic device;
identifying at least one said contact associated with at least one said item from said database; and
displaying said at least one identified contact on said electronic device as a response to said event performed on at least one said item.
20. The computer program product of claim 19, wherein said item comprises a short message service, application, a multimedia service application, an electronic mail application, an instant message application, a social network service application, a call application, a short range communication application, and long range communication application.
21. The computer program product of claim 19, wherein storing said frequency of usage with at least one said contact using at least one said item in said database further comprises:
tracking at least one said item used to communicate with at least one said contact in said electronic device;
counting said frequency of usage of said at least one said item associated with at least one said contact based on said tracking; and
storing said at least one said frequency of usage of at least one item for at least one said contact in said database.
Dated: 30th Day of April, 2014 Signature
Arun Kishore Narasani Patent Agent
ABSTRACT
The embodiments herein provide a method and system for automatically displaying an item for communication with a contact stored in an electronic device. The method includes storing a frequency of usage of the item for the contact in a Frequently Opted Communication Application (FOCA) database. Further, the method includes receiving an interaction event performed on the contact in the electronic device. Furthermore, the method includes identifying the item for communication with the contact from the FOCA database and displaying the identified item on the electronic device as a response to the interaction event performed on the contact.
FIG. 1
| Section | Controller | Decision Date |
|---|---|---|
| 15 | HITENDRA SHARMA | 2023-04-11 |
| 15 | HITENDRA SHARMA | 2023-04-11 |
| 15 | HITENDRA SHARMA | 2023-04-11 |
| # | Name | Date |
|---|---|---|
| 1 | 1170-DEL-2014-PROOF OF ALTERATION [16-01-2024(online)].pdf | 2024-01-16 |
| 1 | Form 5.pdf | 2014-05-02 |
| 2 | 1170-DEL-2014-IntimationOfGrant11-04-2023.pdf | 2023-04-11 |
| 2 | Form 3.pdf | 2014-05-02 |
| 3 | Drawings.pdf | 2014-05-02 |
| 3 | 1170-DEL-2014-PatentCertificate11-04-2023.pdf | 2023-04-11 |
| 4 | Disclosure 38_SEL_13_2037_Complete App_Form 2_Finalized.pdf | 2014-05-02 |
| 4 | 1170-DEL-2014-Annexure [27-02-2023(online)].pdf | 2023-02-27 |
| 5 | 1170-DEL-2014-Response to office action [27-02-2023(online)].pdf | 2023-02-27 |
| 5 | 1170-del-2014-GPA-(12-05-2014).pdf | 2014-05-12 |
| 6 | 1170-DEL-2014-Written submissions and relevant documents [27-02-2023(online)].pdf | 2023-02-27 |
| 6 | 1170-del-2014-Correspondence-Others-(12-05-2014).pdf | 2014-05-12 |
| 7 | 1170-DEL-2014-Request For Certified Copy-Online(10-02-2015).pdf | 2015-02-10 |
| 7 | 1170-DEL-2014-Correspondence to notify the Controller [09-02-2023(online)].pdf | 2023-02-09 |
| 8 | Letter for Issue of Priority Document-CS.pdf | 2015-03-12 |
| 8 | 1170-DEL-2014-FORM-26 [09-02-2023(online)].pdf | 2023-02-09 |
| 9 | 1170-DEL-2014-US(14)-HearingNotice-(HearingDate-13-02-2023).pdf | 2023-01-23 |
| 9 | SEL_New POA_ipmetrix.pdf | 2015-04-16 |
| 10 | 1170-DEL-2014-FER_SER_REPLY [12-02-2020(online)].pdf | 2020-02-12 |
| 10 | FORM 13-change of POA - Attroney.pdf | 2015-04-16 |
| 11 | 1170-DEL-2014-FER.pdf | 2019-08-13 |
| 11 | 1170-DEL-2014-PETITION UNDER RULE 137 [11-02-2020(online)]-1.pdf | 2020-02-11 |
| 12 | 1170-DEL-2014-ASSIGNMENT DOCUMENTS [10-10-2019(online)].pdf | 2019-10-10 |
| 12 | 1170-DEL-2014-PETITION UNDER RULE 137 [11-02-2020(online)].pdf | 2020-02-11 |
| 13 | 1170-DEL-2014-8(i)-Substitution-Change Of Applicant - Form 6 [10-10-2019(online)].pdf | 2019-10-10 |
| 13 | 1170-DEL-2014-Proof of Right (MANDATORY) [25-11-2019(online)].pdf | 2019-11-25 |
| 14 | 1170-DEL-2014-FORM-26 [11-10-2019(online)].pdf | 2019-10-11 |
| 15 | 1170-DEL-2014-8(i)-Substitution-Change Of Applicant - Form 6 [10-10-2019(online)].pdf | 2019-10-10 |
| 15 | 1170-DEL-2014-Proof of Right (MANDATORY) [25-11-2019(online)].pdf | 2019-11-25 |
| 16 | 1170-DEL-2014-ASSIGNMENT DOCUMENTS [10-10-2019(online)].pdf | 2019-10-10 |
| 16 | 1170-DEL-2014-PETITION UNDER RULE 137 [11-02-2020(online)].pdf | 2020-02-11 |
| 17 | 1170-DEL-2014-PETITION UNDER RULE 137 [11-02-2020(online)]-1.pdf | 2020-02-11 |
| 17 | 1170-DEL-2014-FER.pdf | 2019-08-13 |
| 18 | FORM 13-change of POA - Attroney.pdf | 2015-04-16 |
| 18 | 1170-DEL-2014-FER_SER_REPLY [12-02-2020(online)].pdf | 2020-02-12 |
| 19 | 1170-DEL-2014-US(14)-HearingNotice-(HearingDate-13-02-2023).pdf | 2023-01-23 |
| 19 | SEL_New POA_ipmetrix.pdf | 2015-04-16 |
| 20 | 1170-DEL-2014-FORM-26 [09-02-2023(online)].pdf | 2023-02-09 |
| 20 | Letter for Issue of Priority Document-CS.pdf | 2015-03-12 |
| 21 | 1170-DEL-2014-Correspondence to notify the Controller [09-02-2023(online)].pdf | 2023-02-09 |
| 21 | 1170-DEL-2014-Request For Certified Copy-Online(10-02-2015).pdf | 2015-02-10 |
| 22 | 1170-del-2014-Correspondence-Others-(12-05-2014).pdf | 2014-05-12 |
| 22 | 1170-DEL-2014-Written submissions and relevant documents [27-02-2023(online)].pdf | 2023-02-27 |
| 23 | 1170-del-2014-GPA-(12-05-2014).pdf | 2014-05-12 |
| 23 | 1170-DEL-2014-Response to office action [27-02-2023(online)].pdf | 2023-02-27 |
| 24 | 1170-DEL-2014-Annexure [27-02-2023(online)].pdf | 2023-02-27 |
| 24 | Disclosure 38_SEL_13_2037_Complete App_Form 2_Finalized.pdf | 2014-05-02 |
| 25 | Drawings.pdf | 2014-05-02 |
| 25 | 1170-DEL-2014-PatentCertificate11-04-2023.pdf | 2023-04-11 |
| 26 | Form 3.pdf | 2014-05-02 |
| 26 | 1170-DEL-2014-IntimationOfGrant11-04-2023.pdf | 2023-04-11 |
| 27 | Form 5.pdf | 2014-05-02 |
| 27 | 1170-DEL-2014-PROOF OF ALTERATION [16-01-2024(online)].pdf | 2024-01-16 |
| 1 | 2019-08-0717-56-23_07-08-2019.pdf |