DESC:FORM 2

THE PATENTS ACT, 1970
[39 of 1970]
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(Section 10; Rule 13)

SYSTEM AND METHOD FOR ENABLING ONE TOUCH AUTOMATIC APPLICATION DOWNLOAD USING A NEAR FIELD COMMUNICATION (NFC) ENABLED LINK

SAMSUNG R&D INSTITUTE INDIA – BANGALORE PRIVATE LIMITED
# 2870, ORION Building,
Bagmane Constellation Business Park,
Outer Ring Road, Doddanakundi Circle,
Marathahalli Post, Bangalore-560 037
A wholly owned subsidiary
of Samsung Electronics Co. Ltd., Korea,
an Indian Company

The following Specification describes the invention and the method it is being performed

RELATED APPLICATION
The present invention claims the benefit of the Indian Provisional Application No. 227/CHE/2014 titled "SYSTEM AND METHOD FOR ENABLING ONE TOUCH AUTOMATIC APPLICATION DOWNLOAD FROM STATIONARY APPLICATION” by Samsung R&D Institute India – Bangalore Private Limited, filed on 20th January 2014, which is herein incorporated in its entirety by reference for all purposes.

FIELD OF THE INVENTION
The present invention generally relates to handheld mobile devices and more particularly relates to a system and method for enabling automatic application download from stationary application storage device to handheld mobile device using a near field communication (NFC) enabled link.

BACKGROUND OF THE INVENTION
Near-field (or near field) communication (NFC) allows smartphones and other mobile devices to establish radio communication with each other by touching them together or bringing them into close proximity, usually no more than a few centimetres. Currently, NFC can be used in contactless transactions, image/data exchange, and simplified setup of more complex communications such as Wi-Fi. Further, using one touch NFC technology, images/data can be transferred to a stationary NFC enabled device such as, but not limited to, a printer, television and the like from the handheld mobile device.

Currently, when a user wants to remotely control, configure and check status of a stationary near field communication (NFC) enabled device, he needs to connect to the internet and download the stationary NFC enabled device application from an online mobile operating system (OS) App store or two communicating devices to directly share/download applications based on a manual process, where the mobile user selects the Apps and other options before sharing the application.

In view of the foregoing, there is a need for a system and method to enable a user to automatically download applications from a stationary NFC enabled device to a NFC enabled handheld mobile device.

The above mentioned shortcomings, disadvantages and problems are addressed herein and which will be understood by reading and studying the following specification.

SUMMARY OF THE INVENTION
The various embodiments of the present invention disclose a method and system for automatic application download from a stationary near filed communication (NFC) enabled application storage device to a handheld mobile device using NFC enabled link. The handheld mobile device can control/configure/check the status of the stationary NFC enabled application storage device remotely using the downloaded application.

According to an embodiment of the present invention, the method of enabling automatic application download to a Near Field Communication (NFC) enabled mobile device comprises of transmitting by a first device, an initial NFC handshake signal to a second device, activating an Near Field Communication – Logical Link Control Protocol (NFC-LLCP) link between the first device and the second device, transmitting, by the first device, a set of device information to the second device, verifying, by the second device, availability of a compatible application corresponding to a received set of device information, providing a set of application information, if the compatible application is available in an application repository associated with the second device; and enabling the first device to automatically download the compatible application to the first device.

According to an embodiment of the present invention, the first device is an NFC enabled handheld mobile communication device and the second device is an NFC enabled stationary device comprising one of a printer, television, a Multi-Function Peripheral (MFP) or any other NFC enabled stationary device.

According to an embodiment of the present invention, the device information associated with the first device comprises at least one of device model, operating system version and Operating System name.

According to an embodiment of the present invention, the application information transmitted from the second device comprises at least one of application ID and application version

According to an embodiment of the present invention, verifying if the application is already installed in the first device or not; establishing, by the first device a Bluetooth/Wi-Fi Direct connection with the second device if the application is not installed in the first device and downloading the application over the Bluetooth/Wi-Fi Direct connection.

According to an embodiment of the present invention, the method further comprises of obtaining, one or more compatible application from an internet application store, if the compatible application is not available in the application repository associated with the second device and updating the application repository associated with the second device on receiving the one or more compatible applications from the internet application store.

According to an embodiment of the present invention, the process of obtaining one or more compatible applications from the application store comprises of sending, by the second device, an application request message over Bluetooth/Wi-Fi Direct to NFC enabled stationary device to get the required application.

According to an embodiment of the present invention, the application request message comprises of a field for request type application id and application version.

Embodiments herein further disclose a method and system for enabling automatic application download to a Near Field Communication (NFC) enabled mobile device. The method comprises of establishing an NFC-LLCP link between the first device and the second device, transmitting, by the second device, an application information to the first device, verifying, by the first device, if a compatible application is already installed in the first device, transmitting, by the first device, a NULL auxiliary record along with a selected carrier capabilities to the second device, if the compatible application is already installed in the first device and initiating a connection handover by the second device.

According to an embodiment of the present invention, the method further comprises of sending, by the first device, an application request message in the auxiliary record along with a selected carrier capabilities, if the compatible application is not installed in the first device and initiating, by the second device a Bluetooth/Wi-Fi Direct connection establishment with the first device by parsing the auxiliary record if the application is not installed in the second device.

According to an embodiment of the present invention, the method further comprises of checking if a the connection handover is success or not; sending, by the second device, the compatible application to the first device over the Bluetooth/Wi-Fi Direct connection, if the connection handover is success; sending, by the second device, the requested application over an NFC-LLCP link if the connection handover is failed.

Embodiments herein further disclose a system comprising at least one NFC enabled handheld mobile communication device and an NFC enabled stationary device having at least one means adapted for performing the method steps as discussed above.

According to an embodiment herein, the device application provided in the first and second enabled device comprises some or all features to control the stationary device’s operation, which is supported directly on the stationary device user interface. The following lists the device application features:
a. The stationary device application on the first NFC enabled device could communicate with the second NFC enabled device from a remote location through wired or/and wireless network.
b. The device application detects the current operational state of the second NFC enabled device hardware/software and unicast/broadcast this information to other sources.
c. The device application detects issues on the stationary device and notifies the user through the application.
d. The device application is adapted to configure the settings exposed by the second NFC enabled device.
e. The device application is adapted to configure the second NFC enabled device hardware software settings of the second NFC enabled device.

According to an embodiment herein, the device application storage device could also be used alternatively as a mobile or wearable device.

According to an embodiment herein, the device application can be automatically downloaded and installed on the first NFC enabled device on a one touch contact between the NFC ports of the first NFC enabled device and the second NFC enabled device.

According to an embodiment herein, the first NFC enabled device automatically opens the application for the user in a single touch if the application is already installed.

According to an embodiment herein, if the required application is not available on the stationary second NFC enabled device and is downloaded from an online repository, after which it is downloaded automatically to the first NFC enabled mobile device without further intervention from the user.

These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

The other objects, features and advantages will occur to those skilled in the art from the following description of the preferred embodiment and the accompanying drawings in which:

Figure 1 is a flow diagram representing a signal flow for enabling application download to a user device, according to an embodiment of the present invention.

Figure 2 is a signal flow diagram representing a signal flow for enabling application download when the stationary device plays a requestor role, according to an embodiment of the present invention.

Figure 3 is a schematic representation of auxiliary records for handheld device information, according to an embodiment of the present invention.

Figure 4 is a schematic representation of auxiliary record for stationary NFC enabled device’s application information, according to an embodiment of the present invention.

Figure 5 is a flow chart illustrating a process of transferring the application when the handheld mobile device plays a requestor role, according to an embodiment of the present invention.

Figure 6 is a flow chart illustrating a process of transferring the application when the stationary device plays a requestor role, according to an embodiment of the present invention.

Figure 7 is a schematic representation for inserting a get APP request message as part of data field of TCP packet, according to an embodiment of the present invention.

Figure 8 is a schematic representation of sending a Get APP request message over SPP session, according to an embodiment of the present invention.

Figure 9 is a schematic representation of updating database of the stationary NFC enabled device on periodic basis by the OS App store, according to an embodiment of the present invention.

Although specific features of the present invention are shown in some drawings and not in others. This is done for convenience only as each feature may be combined with any or all of the other features in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION
The embodiments of the present invention will now be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiments. The present invention can be modified in various forms. Thus, the embodiments of the present invention are only provided to explain more clearly the present invention to the ordinarily skilled in the art of the present invention. In the accompanying drawings, like reference numerals are used to indicate like components.
The specification may refer to “an”, “one” or “some” embodiment(s) in several locations. This does not necessarily imply that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.
As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes”, “comprises”, “including” and/or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements and/or components, but do not preclude the presence or addition of one or more other features integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations and arrangements of one or more of the associated listed items.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The present invention relates to handheld mobile devices and more particularly, the present invention relates to a system and method for automatic application download from a stationary near filed communication (NFC) enabled application storage device to a handheld mobile device using NFC enabled link. The handheld mobile device can control/configure/check the status of the stationary NFC enabled application storage device remotely using the downloaded application.

According to an embodiment of the present invention, the stationary NFC enabled device acts as an application store for all the latest applications needed for any handheld mobile device. The method herein is a one-touch application download solution when the required application is not already installed on the handheld mobile device.

According to an embodiment herein, the NFC facilitates the downloading of the handheld mobile device application using a peer-to-peer communication mode. Here two NFC enabled devices detects each other when devices come into close proximity. Further an NFC-LLCP connection will be established as per NFC standard protocol defined by ISO/IEC 18092. For ease of use, on the basis of the exchanged device information, the stationary NFC enabled device can send the compatible application to the NFC enabled handheld device. To transfer large amount of data between two NFC enabled devices, the devices have to be kept in close proximity for long time which is very inconvenient.

According to an embodiment herein, Ad Hoc Wi-Fi is used as an alternate carrier technology which has a faster data rate than NFC technology. The data can then be transferred using either of the two mentioned technologies. If alternative carrier is not available, then the NFC link is used to transfer the data between devices.

The information on the handheld mobile device such as OS name, OS version and model number, is shared over NFC–LLCP link, are carried in auxiliary data part as NFC Data Exchange Format (NDEF) record messages. The handheld mobile device sends the auxiliary record as part of Handover Request message. The stationary NFC enabled device sends the application ID and application version as part of Handover Select message. The stationary NFC enabled device application id and application version are carried in auxiliary data as NDEF record.

Figure 1 is a schematic flow diagram 100 representing a signal flow for enabling application download to a user device when the user device plays the role of a requestor, according to an embodiment of the present invention. As illustrated in Figure.1, an initial handshake process is initiated between a first device 102 and a second device 104. The first device 102 herein is a NFC enabled mobile device and the second device 104 is an NFC enabled stationary device such as, but not limited to, television, printer, MFP or the like.

According to Figure 1, an NFC-LLCP link connection is established between the NFC enabled mobile device 102 and the NFC enabled device 104. Once the connection is established, the NFC enabled handheld mobile device 102 sends the auxiliary record data for the device information such as, but not limited to, operating system (OS) name, OS version, model number, alternative carrier capabilities, and the like on the LLCP link to the NFC enabled device 104. The NFC enabled device 104 receives the device information provided by the NFC enabled handheld mobile device 102. Based on the received device information, the NFC enabled device 104 searches the plurality of pre-stored applications for providing the application specific to the NFC enabled mobile device 102. On identifying the application, the NFC enabled device 104 transmits auxiliary record data for application information to the NFC enabled handheld mobile device 102. Here the application information comprises of, but not limited to, application ID and application version along with alternative carrier capabilities on the LLCP link. Once the first device 102 receives the auxiliary record data for application information, a WFD/ BT connection is established between the first device 102 and the second device 104. The NFC enabled handheld mobile device 102 receives the application information from the NFC enabled device and the checks if the application is already installed or not. If the application is not installed with specific version, the NFC enabled handheld mobile device 102 sends a request to the NFC enabled device 104 to get the required application over a WFD/BT connection. Upon receiving the request, the NFC enabled device 104 searches for the required application.

Once the NFC enabled device 104 obtains the APP as per the NFC enabled mobile device 102, the NFC enabled device 104 sends the application required by the NFC enabled mobile device 102 over the WFD/ BT connection. The NFC enabled handheld mobile device 102 receives the application and installs the received application in the device. If the WFD/ BT connection is not supported due to some reasons, then the NFC enabled device 104 sends the required application to the NFC enabled handheld mobile device 102 as per the NFC enabled device 104 device information on the NFC-LLCP link, and the NFC enabled handheld mobile device 102 receives the application and installs the received application in the device.

According to an embodiment herein, consider an example, where a handheld smartphone is available in the same location as the stationary NFC enabled printer. The user of the smartphone could automatically download the printer’s application directly from the printer instead of the user spending time connecting to the Online App store to download the application. The printer acts as an App store for all available handheld mobile devices. The mobile phone establishes NFC-LLCP link with the printer for communication and downloading the application. Upon establishing connection and providing the necessary information such as, OS name, OS version, model number, and alternative carrier capabilities, the printer identifies the application suitable for the smartphone, sends the application to the smartphone. The smartphone receives the application and installs the application from the printer itself. The application once downloaded could support some or all features that are available to the user on the printer’s user interface. The features supported on the application for the printer could include functionality to remotely control/configure/monitor the printer using the smartphone.

Figure 2 is a schematic flow diagram 200 representing a signal flow for enabling application download to a user device when a stationary device plays the role of a requestor, according to an embodiment of the present invention. As illustrated in Figure.2, an initial handshake process is initiated between a first device 202 and a second device 204. The first device 202 herein is a NFC enabled mobile device and the second device 204 is an NFC enabled stationary device such as, but not limited to, television, printer, MFP or the like.

According to Figure 2, an NFC-LLCP link connection is established between the NFC enabled mobile device 202 and the NFC enabled device 204. Once the connection is established, the NFC enabled device 204 sends a list of applications along with alternative carrier capabilities over the NFC-LLCP link. The NFC enabled mobile device202 receives the list of applications that are being supported by the NFC enabled mobile device 204 along with alternative carrier capabilities. The NFC enabled mobile device 202 parses the list to check whether the required APP is already installed or not. If the APP is already installed then, the NFC enabled mobile device 202 launches the APP and sends selected carrier capabilities to the NFC enabled device 204 with NULL auxiliary record values. If the APP is not installed, then the NFC enabled mobile device 202 sends GET APP request message to the NFC enabled device 204 as part of auxiliary record along with selected carrier capabilities. The NFC enabled device 204 receives the GET APP request message from the NFC enabled mobile device 202 along with selected carrier capabilities and auxiliary record. Upon receiving the request message and auxiliary record, the NFC enabled device 204 initiates connection handover process, and WFD/ BT connection is established between the NFC enabled mobile device 202 and the NFC enable device 204.

The NFC enabled device 204 checks the requested auxiliary record whether the value is NULL or has some request data. If the in the requested auxiliary record is not NULL, then the NFC enabled device 204 sends the requested APP to the NFC enabled mobile device 202 over the WFD/ BT connection. Upon receiving the requested APP, the NFC enabled mobile device 202 installs and launches the received APP. If the WFD/ BT connection is not supported due to some reasons, then the NFC enabled device 204 sends the required application or APP to the NFC enabled mobile device 202 as per the NFC enabled device 204 device information on the NFC-LLCP link, and the NFC enabled mobile device 202 receives the application and installs the received application in the device.

Figure 3 is a schematic representation of auxiliary records 300 for handheld device information, according to an embodiment of the present invention. The auxiliary record is a well-known type of NFC data exchange format (NDEF) record. The NFC enabled handheld mobile device uses the auxiliary record to transfer information to the NFC enabled device. The different fields of the auxiliary record data comprises, but not limited to, MB(0), ME(0), CF(0), SR(0), IL(1), TNF(001), type length, payload length, ID length, type value, ID value, and payload data, wherein the handheld device transmits the OS name, OS version and model number as part of the payload data. The auxiliary record is stored in the alternative carrier record, wherein the alternative carrier record is present in the handover request record. When the handheld device sends the handover request to the NFC enabled device, then along with the handover request, the auxiliary device information is also sent to the NFC enabled device.

Figure 4 is a schematic representation of auxiliary record 400 for stationary NFC enabled device’s application information, according to an embodiment of the present invention. The NFC enabled device also uses the auxiliary reference data to transfer information such as, but not limited to, application ID and application version to the handheld mobile device. The NFC enabled device uses the auxiliary record to transfer information to the NFC enabled device. The different fields of the auxiliary record data comprises, but not limited to, MB(0), ME(0), CF(0), SR(0), IL(1), TNF(001), type length, payload length, ID length, type value, ID value, and payload data. The NFC enabled device transmits the application ID and application version, as a part of the payload data. The auxiliary reference data can be stored in the alternative carrier record, wherein the alternative carrier record can further be stored in the handover select record. When the NFC enabled device responds to the handover request of the handheld device, then along with the handover select, the auxiliary device information is also sent to the handheld device. The handheld device receives the auxiliary reference data and identifies the payload data, which comprises of application information, and based on the application information initiates downloading of the application from the NFC enabled device.

Figure 5 is flow diagram 500 illustrating an exemplary decision process made on the handheld mobile device for selecting data transfer mode to download application from a stationary NFC enabled device when the handheld mobile device plays the role of a requestor, according to an embodiment of the present invention. At step 502, NFC-LLCP link connection is established between the NFC enabled handheld mobile device and the NFC enabled device. At step 504, the NFC enabled handheld mobile device sends the auxiliary record data for the device information such as, but not limited to, operating system (OS) name, OS version, model number, alternative carrier capabilities, and the like on the LLCP link to the NFC enabled device, once the connection is established. At step 506, the NFC enabled device on receiving the device information, checks if any application compatible with the NFC enabled handheld mobile device is available in the application database of the NFC enabled device. If the application is compatible with NFC enabled handheld mobile device, then method goes to step 508, otherwise the method goes to step 510.

At step 508, the NFC enabled device identifies that the application that is compatible with the NFC enabled handheld mobile device is available, therefore the NFC enabled device sends the application information such as the application ID and application version along with the supported carrier capabilities to the NFC enabled handheld mobile device. At step 510, the NFC enabled device identifies that the application that can be compatible with the NFC enabled handheld mobile device is not available, and therefore the NFC enabled device sends a request message to a server to update the database with required compatible application.

At step 512, the NFC enabled device checks whether the application that can be compatible with the NFC enabled handheld mobile device or not. If the application that can be compatible with the NFC enabled handheld mobile device is available with the server, then at step 514, the NFC enable device updates the device database with the newly obtained application from the server and sends the same to the step 508, wherein the NFC enabled device sends the application to the NFC enabled handheld mobile device along with application information such as the application ID and application version along with supported carrier capabilities.

If the application that can be compatible with the NFC enabled handheld mobile device is not available with the server, then the method goes to step 516, wherein NFC enabled device identifies that the required application is not available on the server store. At step 518, the NFC enabled device displays a message to user of the NFC enabled handheld mobile device that the application compatible with the NFC enabled handled mobile device is not available.

At step 520, the NFC enabled handheld mobile device checks if the application is installed on the NFC enabled handheld mobile device or not, upon receiving the application information. If the application is already installed in the NFC enabled handheld mobile device, then the process moves to step 522, where the NFC enabled handheld mobile device understands that the required application is already installed and thereby ends the process. If application is not already installed, then the process moves to step 524.

At step 524, the NFC enabled handheld mobile device checks whether connection handover process is successful or not. If the connection handover process is successful, then at step 526 the NFC enabled handheld mobile device identifies that connection is being handed over to WFD/ BT connection and thereby sends the request message to the NFC enabled device to get the required application over the same WFD/ BT connection. At step 530, the NFC enabled device sends the requested application to the NFC enabled handheld mobile device, upon receiving the request message for getting the application. At step 534, the NFC enabled handheld mobile device receives the application from the NFC enabled device and installs the application, and thereby ending the process.

If the connection handover process is not successful, then at step 528 the NFC enabled handheld mobile device sends the request message to the NFC enabled device to get the required application over the LLCP-NFC link connection. At step 532, the NFC enabled device sends the requested application to the NFC enabled handheld mobile device, upon receiving the request message for getting the application. Once the NFC enabled device sends the requested application to the NFC enabled handheld mobile device, the method goes to step 534, wherein the NFC enabled handheld mobile device receives the application from the NFC enabled device and installs the application, and thereby ending the process.

Figure 6 is flow diagram 600 illustrating an exemplary decision process made on the handheld mobile device for selecting data transfer mode to download application from a stationary NFC enabled device when the stationary NFC enabled device plays the role of a requestor, according to an embodiment of the present invention. At step 602, NFC-LLCP link connection is established between the NFC enabled handheld mobile device and the NFC enabled device. At step 604, the NFC enabled device sends list of supported applications to the NFC enabled handheld mobile device along with alternative carrier capabilities. At step 606, the NFC enabled handheld mobile device checks whether the compatible application is already installed on the NFC enabled handheld mobile device. If the compatible application is already installed on the NFC enabled handheld mobile device, then method goes to step 608, otherwise the method goes to step 612.

At step 608, the NFC enabled handheld mobile device launches the application and sends auxiliary records to the NFC enabled device with NULL values along with selected carrier capabilities. At step 610, the NFC enabled handheld mobile device initiates the connection handover procedure and thereby ending the process.

At step 612, the NFC enabled handheld mobile device sends the GET APP request message to the NFC enabled device as part of the auxiliary record along with selected carrier capabilities. At the step 614, the NFC enabled device parses the received auxiliary records, and initiates the connection handover procedure with the NFC enabled handheld mobile device. At step 616, the NFC enabled device checks whether the connection handover procedure with the NFC enabled handheld mobile device is successful or not. If the handover connection procedure is successful, then the method moves to step 618, otherwise to the step 620.

At step 618, the NFC enabled device sends the requested application to the NFC enabled handheld mobile device over the WFD/ BT connection. At step 622, the NFC enabled handheld mobile device receives the application sent by the NFC enabled device and installs the application, and thereby ending the process. At step 620, the NFC enabled device sends the requested application to the NFC enabled handheld mobile device over the NFC-LLCP link connection. At step 622, the NFC enabled handheld mobile device receives the application sent by the NFC enabled device and installs the application, and thereby ending the process.

Figure 7 is a schematic packet diagram 700 that illustrates data fields of a TCP packet along with GET APP request message inserted into the data fields, according to an embodiment of the present invention. According to the present invention, the TCP packet 700 can be of 7 layers with each layer of 32 bits length. First layer comprises of source and destination port addresses, second layer comprises of sequence number, third layer comprises of acknowledgement number, fourth layer comprises of fields such as, data offset, reserved bits, flags, and window, fifth layer comprises of values such as checksum and urgent pointer, six layer comprises of options and padding values, and the seventh layer comprises of GET APP request message present in the form of data.

The GET APP request message in the TCP packet 700 comprises of a request type of 8 bits length, version length of 8 bits indicating version of the application that is being asked for, application version, id length of 8 bits indicating the NFC handheld mobile device id length, and the application id. The NFC enabled handheld mobile device sends the request message over Wi-Fi Direct/ Bluetooth (WFD/ BT) when the required application is not installed on the NFC enabled handheld mobile device. The application request message is sent to the NFC enabled device as part of TCP packet, which is transferred over Wi-Fi Direct interface.
Figure 8 is schematic message flow diagram 800 illustrating sending GET APP request message from a NFC enabled handheld mobile device 802 to a NFC enabled stationary device 804 over SPP session, according an embodiment of the present invention. The GET APP request message is sent from the NFC enabled handheld mobile device 802 to the NFC enabled stationary device 804 when required application is not installed on the NFC enabled handheld mobile device 802. Initially, connection between the NFC enabled handheld mobile device 802 to the NFC enabled stationary device 804 is handed over to Bluetooth connection. In another embodiment, the connection handover can be done to WFD connection. The NFC enabled handheld mobile device 802 creates SPP session with the NFC enabled stationary device 804 over the Bluetooth connection. Upon establishing SPP session, the NFC enabled handheld mobile device 802 sends the GET APP request message to the NFC enabled stationary device 804, wherein the GET APP request message can comprise of fields such as request type of 8 bits length, version length of 8 bits length, application version, id length of 8 bits length, and application id, as described herein above in Figure 7.
Figure 9 illustrates a schematic representation 900 of updating an application database of an NFC enabled stationary device 902, according to an embodiment of the present invention. The NFC enabled stationary device 902 stores and references all applications based on lookup information such as the handheld mobile device OS name, OS version and model number on which the application is to be installed. The NFC enabled stationary device 902 periodically connects to one or more application stores 904 where the latest version of applications for newly supported or existing devices are stored. The NFC enabled stationary device 902 synchronizes with the application stores 904 and downloads the latest version of the application and stores it in an internal storage 906. The NFC enabled stationary device 902 stores the applications based on handheld mobile device OS name, OS version and model number. When a handheld mobile device (not shown in the Figure) establishes a NFC link with the NFC enabled stationary device 902, the NFC enabled stationary device 902 receives the mobile OS name, OS version and model number stored in the handover request, as described in Figure 3, using which the NFC enabled stationary device 902 retrieves the required application from the internal storage 906 and provides the application for download through the accepted transfer mode. If the application is not already available with the NFC enabled device, then the stationary NFC enabled stationary device 902 sends a query to OS APP store 904 to check availability and then download the application. If the application is not available, the application download process displays a message to the user that the application could not be found for the handheld mobile device.
Although the embodiments herein are described with various specific embodiments, it will be obvious for a person skilled in the art to practice the invention with modifications. However, all such modifications are deemed to be within the scope of the claims. It is also to be understood that the following claims are intended to cover all of the generic and specific features of the embodiments described herein and all the statements of the scope of the embodiments which as a matter of language might be said to fall there between.

,CLAIMS:
CLAIMS
We Claim:

1. A method of enabling automatic application download to a Near Field Communication (NFC) enabled mobile device, the method comprises of:
transmitting by a first device, an initial NFC handshake signal to a second device;
activating an Near Field Communication – Logical Link Control Protocol (NFC-LLCP) link between the first device and the second device;
transmitting, by the first device, a set of device information to the second device;
verifying, by the second device, availability of a compatible application corresponding to a received set of device information;
providing a set of application information, if the compatible application is available in an application repository associated with the second device; and
enabling the first device to automatically download the compatible application to the first device.

2. The method of claim 1, wherein the first device is an NFC enabled handheld mobile communication device.

3. The method of claim 1, wherein the second device is a NFC enabled stationary device comprising one of a printer, television, a Multi-Function Peripheral (MFP) or any other NFC enabled stationary device.

4. The method of claim 1, wherein the device information associated with the first device comprises at least one of device model, operating system version and Operating System name.

5. The method of claim 1, wherein the application information transmitted from the second device comprises at least one of application ID and application version.

6. The method of claim 1, further comprising:
verifying if the application is already installed in the first device or not;
establishing, by the first device a Bluetooth/Wi-Fi Direct connection with the second device if the application is not installed in the first device; and
downloading the application over the Bluetooth/Wi-Fi Direct connection.

7. The method of claim 1, further comprising:
obtaining, one or more compatible application from an internet application store, if the compatible application is not available in the application repository associated with the second device; and
updating the application repository associated with the second device on receiving the one or more compatible applications from the internet application store.

8. The method of claim 7, wherein the process of obtaining one or more compatible applications from the application store comprises of:
sending, by the second device, an application request message over Bluetooth/Wi-Fi Direct to NFC enabled stationary device to get the required application.

9. The method of claim 7, wherein the application request message comprises of a field for request type application id and application version.

10. A method of enabling automatic application download to a Near Field Communication (NFC) enabled mobile device, the method comprises of:
establishing an Near Field Communication – Logical Link Control Protocol (NFC-LLCP) link between the first device and the second device;
transmitting, by the second device, an application information to the first device;
verifying, by the first device, if a compatible application is already installed in the first device;
transmitting, by the first device, a NULL auxiliary record along with a selected carrier capabilities to the second device, if the compatible application is already installed in the first device; and
initiating a connection handover by the second device.

11. The method of claim 10, further comprising:
sending, by the first device, an application request message in the auxiliary record along with a selected carrier capabilities, if the compatible application is not installed in the first device; and
initiating, by the second device a Bluetooth/Wi-Fi Direct connection establishment with the first device by parsing the auxiliary record if the application is not installed in the second device.

12. The method of claim 10, further comprising:
checking if a the connection handover is success or not;
sending, by the second device, the compatible application to the first device over the Bluetooth/Wi-Fi Direct connection, if the connection handover is success.

13. The method of claim 10, further comprising:
sending, by the second device, the requested application over an NFC-LLCP link if the connection handover is failed.

14. The method of claim 10, wherein the first device is an NFC enabled handheld mobile communication device.

15. The method of claim 10, wherein the second device is a NFC enabled stationary device comprising one of a printer, television, a Multi-Function Peripheral (MFP) or any other NFC enabled stationary device.

16. The method of claim 10, wherein the application information comprises of an application ID of a list of supported applications along with alternative carrier capabilities.

17. A system for enabling automatic application download to a Near Field Communication (NFC) enabled mobile device, the system comprising:
a first NFC enabled device; and
a second NFC enabled device;
wherein the first NFC enabled device comprises at least one means adapted for:
transmitting an initial NFC handshake signal to the second NFC enabled device;
activating an Near Field Communication – Logical Link Control Protocol (NFC-LLCP) link between the first NFC enabled device and the second NFC enabled device; and
transmitting a set of device information to the second NFC enabled device;
wherein the second NFC enabled device comprises at least one means adapted for:
verifying availability of a compatible application corresponding to set of device information received from the first NFC enabled device;
providing a set of application information, if the compatible application is available in an application repository associated with the second NFC enabled device; and
enabling the first NFC enabled device to automatically download the compatible application to the first NFC enabled device.

18. The system of claim 17, wherein the first NFC enabled device is an NFC enabled handheld mobile communication device.

19. The system of claim 17, wherein the second NFC enabled device is a NFC enabled stationary device comprising one of a printer, television, a Multi-Function Peripheral (MFP) or any other NFC enabled stationary device.

20. The system of claim 17, wherein the device information associated with the first NFC enabled device comprises at least one of device model, operating system version and Operating System name.

21. The system of claim 17, wherein the application information transmitted from the second NFC enabled device comprises at least one of application ID and application version.

22. The system of claim 17, wherein the first NFC enabled device comprises at least one means adapted for:
verifying if the application is already installed in the device or not;
establishing, a Bluetooth/Wi-Fi Direct connection with the second NFC enabled device if the application is not installed in the first NFC enabled device; and
downloading the application over the Bluetooth/Wi-Fi Direct connection.

23. The system of claim 17, wherein the first NFC enabled device is further adapted for:
obtaining, one or more compatible application from an internet application store, if the compatible application is not available in the application repository associated with the second NFC enabled device; and
updating the application repository associated with the second NFC enabled device on receiving the one or more compatible applications from the internet application store.

24. The system of claim 17, wherein the second NFC enabled device obtains one or more compatible applications from the application store by sending, an application request message over Bluetooth/Wi-Fi Direct to the second NFC enabled device to get the required application.

25. The system of claim 24, wherein the application request message comprises of a field for request type application id and application version.

26. A system enabling automatic application download to a Near Field Communication (NFC) enabled mobile device, the system comprises of:
a first NFC enabled device; and
a second NFC enabled device;
wherein the first NFC enabled device and the second NFC enabled device comprises at least one means adapted for:
establishing an Near Field Communication – Logical Link Control Protocol (NFC-LLCP) link between the first NFC enabled device and the second NFC enabled device;
transmitting an application information to the first NFC enabled device;
verifying if a compatible application is already installed in the first enabled NFC device;
transmitting a NULL auxiliary record along with a selected carrier capabilities to the second NFC enabled device, if the compatible application is already installed in the first NFC enabled device; and
initiating a connection handover by the second NFC enabled device.

27. The system of claim 26, wherein the first NFC enabled device further comprises at least one means adapted for sending an application request message in the auxiliary record along with a selected carrier capabilities to the second NFC enabled device, if the compatible application is not installed in the first NFC enabled device.

28. The system of claim 26, wherein the second NFC enabled device further comprises at least one means adapted for:
initiating, by the second device a Bluetooth/Wi-Fi Direct connection establishment with the first device by parsing the auxiliary record if the application is not installed in the second device;
checking if a the connection handover is success or not;
sending the compatible application to the first NFC enabled device over the Bluetooth/Wi-Fi Direct connection, if the connection handover is success; and
sending the requested application over an NFC-LLCP link if the connection handover is failed.

29. The system of claim 26, wherein the first NFC enabled device is an NFC enabled handheld mobile communication device.

30. The system of claim 26, wherein the second NFC enabled device is a NFC enabled stationary device comprising one of a printer, television, a Multi-Function Peripheral (MFP) or any other NFC enabled stationary device.

31. The system of claim 30, wherein the application information comprises of an application ID of a list of supported applications along with alternative carrier capabilities.

Dated this the 2nd day of December 2014

Signature

KEERTHI J S
Patent agent
Agent for the applicant