WO2015110837A2

WO2015110837A2 - Short-range communications control

Info

Publication number: WO2015110837A2
Application number: PCT/GB2015/050169
Authority: WO
Inventors: Ralph Mahmoud Omar
Original assignee: Omarco Network Solutions Limited
Priority date: 2014-01-27
Filing date: 2015-01-26
Publication date: 2015-07-30
Also published as: AR099193A1; GB201401338D0; WO2015110837A3

Abstract

A method of downloading a selected application program (app) to a mobile device via a wireless communications channel is described. The app comprises a plurality of components including an app mask and at least one content component and the app mask comprises instructions for controlling the download of the at least one content component. The method comprises :establishing a wireless communications channel between the mobile device and a terminal;receiving the app mask at the mobile device via the wireless channel;using the app mask to control downloading of the at least one content component until the entire app has been downloaded; and making the app available on the mobile device for use.

Description

Short-Range Communications Control

Field of Invention

The present invention relates to a method and system for short-range communications control, and more specifically relates to a system for improved Near Field

Communications and data transfer related to mobile device applications.

Background Conventionally smart mobile devices have the ability to be configured by application software (known as 'apps' or 'mobile apps') which are downloaded onto the device and installed. An app is a software program which has a specific purpose and so is a convenient way of making the relevant functionality available to the user on their mobile device when run.

Currently apps are available to be downloaded from the website of a provider of a service (such as a bank) or typically from an on-line store such as the Apple App Store^® which allows users to browse and download apps from the iTunes Store^® that was developed for Apple iOS devices such as the Apple iPhone^®.

In order to download an app, the mobile device user needs to be connected to the internet via a mobile telecommunications network such as 3G or 4G, or via a WiFi route connection or be connected to a desktop or laptop computer which has a connection to the internet. Also the user needs to be familiar with the manner in which an app is selected and installed on their device. Whilst this is not onerous for the younger generation, the elderly or less technically able, for example, often find difficulties with this process.

A further problem with conventional downloading via a website, is the length of time it takes to have the app installed. Not only is the connection to the internet required for the entire time period or the download may well fail, the time it takes can be considerable. The time taken does depend on the power of the device, the strength of signal and the number of other programs already installed on the smart device. This can result in apps sometimes taking 5 to 10 minutes to download. This leads to the problem that when using a wired connection, the user has to stay in one location for a considerable period of time. Also when using a wireless connection, the longer the app takes to download the greater the chance that the strength of the connection will vary, which in the worst case (particularly if the downloading device is mobile) may cut the link with the internet altogether, thereby necessitating a reinstall of the app.

In a related topic, when considering the different means of data transfer and interaction available, one of the preferred means is via a Near Field Communications (NFC) link, which allows the data to be sent and received quickly and with minimal user interaction. Some other local communications technologies such as Blutooth require a device pairing procedure which in some cases can be onerous on the inexperienced user. Typically, NFC devices can be active (requiring a power supply) or passive (not requiring a power supply). Passive devices can be read by an active device but do not provide the ability to change their interaction and hence have limited functionality. Active devices enable the interaction and data being communicated to be varied and so are more useful as devices in many circumstances. At present, many mobile devices have an active NFC capability which enables different types of interaction with fixed NFC devices acting as readers. These devices can be provided in many different locations, for example at a point of sale terminal (such as a supermarket checkout or a lottery machine) or at a vending machine, on a train, at a station, etc.

As the number of such locations and places grows, a problem which arises is to do with the inadvertent communication with a fixed NFC terminal when such communication is not desired. One way of addressing this problem which has been used in enhanced security applications is to provide a layer of security on each use of the NFC device, for example by the requirement to input a Personal Identification Number (PIN) before each use of the NFC communication. However, whilst this does solve the problem of inadvertent use, the use of a PIN complicates the process of completing the transaction, and the additional steps required can frustrate the user. An additional problem that may also arise as a result of this method is that the user will have to deal with problems caused when they forget their PIN.

One further related issue arises in situations where some mobile devices have an NFC antenna provided, but are not provided with specific software to drive the antenna in a particular manner. Normally, such software is available to be downloaded and the user would have to configure the mobile device on their own so as to operate the NFC antenna in a specific manner. However, such configuration varies from mobile device to mobile device and requires a fair amount of technological know-how. One of the main difficulties is that the user has to provide details of their mobile device (e.g. the unique address of the device, as well as various other identifying features of their mobile device) to enable the correct software to be downloaded to the device. The average (and generally inexperienced) user may not know what these details are, or even how to obtain them.

Therefore, carrying out NFC interactions using a mobile device, while beneficial in many ways, is complicated and not necessarily accessible to the average user.

The present invention seeks to overcome or at least substantially reduce at least some of the above described problems. Summary of Invention

According to one aspect of the present invention there is provided a method of downloading a selected application program (app) to a mobile device via a wireless communications channel, the app comprising a plurality of components including an app mask and at least one content component, wherein the app mask comprises instructions for controlling the download of the at least one content component, the method comprising: establishing a wireless communications channel between the mobile device and a terminal; receiving the app mask at the mobile device via the wireless channel; using the app mask to control downloading of the at least one content component until the entire app has been downloaded; and making the app available on the mobile device for use.

The establishing step may advantageously comprise establishing a Near Field

Communications (NFC) channel between the mobile device and the terminal. This type of communications channel leads to minimal required user interaction and speeds up the process of completing a user interaction.

The establishing step may comprise transmitting a mobile device identifier to a central server via an alternative wireless communications channel, the device identifier enabling the central server to determine the required configuration data for the mobile device and receiving the configuration data from the central server and configuring an NFC aerial in the mobile device for use with the terminal.

In one embodiment, the configuration data is arranged to control the timing and duration of the operation of the NFC antenna. The establishing step may comprise comparing a currently available type of terminal with a set of user-selected terminals and enabling the establishing step to be carried out if the currently available terminal matches a pre-selected type of terminal. This provides the ability to have secondary user control of user interaction with terminals as has been explained later.

The establishing step in one embodiment comprises selecting the terminal on the basis of a type of service that the terminal provides. In another embodiment the method further comprises determining a current geographic location of the mobile device and the establishing step further comprises selecting the terminal on the basis of a geographic location of the terminal.

The using step may comprise monitoring the established wireless communications channel and if the strength of the wireless communications channel is below a predetermined threshold, carrying out a search of other wireless channels available to the mobile device for the download of the at least one content component.

The using step may comprise monitoring the strength of any wireless channels available to the mobile device for the download of the at least one content component and choosing the wireless channel with the strongest signal. The choosing step may comprise checking that the connection with the strongest wireless channel has been maintained for a predetermined time before choosing the wireless channel for use.

The receiving step may further comprise receiving a unique transaction identifier from the terminal for use in validating the app mask.

The method may further comprise discarding a current content component if the current content component has not completely been downloaded via a wireless channel and a new content component is being received via a different wireless communications channel.

The receiving step in one embodiment comprises incrementing a marker of the number of content components which have been successfully downloaded after completion of download of a current content component.

According to another aspect of the present invention there is provided a mobile device arranged to download a selected application program (app) via a wireless

communications channel, the app comprising a plurality of components including an app mask and at least one content component, wherein the app mask comprises instructions for controlling the download of the at least one content component, the mobile device comprising: a wireless communications module for establishing a wireless

communications channel between the mobile device and a terminal; the app mask received at the mobile device via the wireless channel; a controller arranged to use the app mask to control downloading of the at least one content component until the entire app has been downloaded; and a display for making the app available on the mobile device for use. According to another aspect of the present invention there is provided a method of transmitting a selected application program (app) to a mobile device via a wireless communications channel, the app comprising a plurality of components including an app mask and at least one content component, the method comprising: establishing a wireless communications channel between a terminal and the mobile device; providing the app mask from the terminal to the mobile device via the wireless channel; the app mask comprising executable instructions for controlling the downloading of the at least one content component until the entire app has been downloaded; receiving control instructions from the app mask operating on the mobile device; transmitting the at least one content component to the mobile device via a currently available wireless communications channel, wherein the currently available wireless communications channel comprises the established wireless communication channel or a different available wireless communications channel to the mobile device; and continuing the transmitting step until the entire app has been downloaded. The establishing step may advantageously comprise establishing a Near Field

Communications (NFC) channel between the terminal and the mobile device.

The transmitting step may further comprise transmitting a unique transaction identifier from the terminal for use in validating the app mask. The unique identifier can advantageous validate ownership of a validly downloaded app.

In an embodiment the transmitting step comprises providing a marker of the number of content components which have been successfully downloaded and incrementing the marker after completion of download of a current content component. The method may further comprise retransmitting the current content component indicated by the marker if the current content component is unable to be completely downloaded by the mobile device. The method may further comprise providing at least one further wireless communications channel to the mobile device and using the at least one further wireless communications channel for the transmission of the at least one content components if requested by the mobile device.

The app mask is preferably relatively small in size compared to the at least one content component. This enables the all-important app mask to be transmitted as a placeholder and to then control the remaining download. The app mask may in some embodiments be less than 20% of the total app size even for fairly small apps.

In an embodiment, the at least one content component comprises a plurality of content components. The greater the number of content components that are provided the greater the segmentation. This in turn increases the robustness of the process to disruption of wireless communications channels.

According to another aspect of the present invention there is provided a terminal for transmitting a selected application program (app) to a mobile device via a wireless communications channel, the app comprising a plurality of components including an app mask and at least one content component, the terminal comprising: a communications module for establishing a wireless communications channel between a terminal and the mobile device; an app mask module for providing the app mask from the terminal to the mobile device via the wireless channel; the app mask comprising executable instructions for controlling the downloading of the at least one content component until the entire app has been downloaded; a receiver for receiving control instructions from the app mask operating on the mobile device; and a content module arranged to transmit the at least one content component to the mobile device via a currently available wireless communications channel, wherein the currently available wireless communications channel comprises the established wireless communication channel or a different available wireless communications channel to the mobile device; wherein the content module is arranged to continue to transmit the at least one content component until the entire app has been downloaded.

The present invention also extends to a combination of a server and a terminal as described above, wherein the server is operatively connected to the terminal via a communications network and is configured to provide additional storage for the at least one content component of the app.

According to another aspect of the present invention a method of controlling a Near Field Communications (NFC) interaction between a mobile device and a fixed NFC device, the method comprising: storing, in a user profile file, a user selection of a type of NFC fixed device with which communication will be permitted; and conducting a potential interaction event; wherein the conducting step comprises: establishing a current geographical location of the mobile device; transmitting the current geographical location and a unique identifier of the mobile device to a central server; determining the types of fixed NFC devices present in the current location; comparing the types for the fixed NFC devices at the current location with those specified by the user profile; and if any of the fixed NFC devices at the current location match those specified in the user profile, activating an NFC antenna in the mobile device to facilitate an NFC interaction with the fixed NFC device.

Advantageously this maintains a simplified NFC interaction protocol that is easy for the average user to carry out, but does not compromise the security of the interactions. The transmitting step may be carried out via a non-NFC communications channel. The use of alternative communications channels means that this initial process can be carried out remotely to the fixed device, as the mobile device is not required to be in such close proximity as if the communications were carried out using NFC channel. Therefore the process may be begun before the user reaches the fixed device and will save time (e.g. at a POS terminal where the process may be initiated while the user is queuing to use the terminal).

The non-NFC communication channel may comprises a SMS messaging channel, a WiFi communications channel, 3/4 G telecommunications channel. All of these channels are readily available on many commercial mobile devices such as smart phones and provide a set of different channels available to be used.

The determining and comparing steps may be carried out at the central server and the method may further comprise sending back to the mobile device a trigger message for triggering execution of the activating step. This advantageously decreases the mobile device resources that need to be used to carry out this process, as the mobile device does not have to store or process the details and locations of all the available fixed NFC devices. This also typically speeds up the process. It also means that only one centrally updated record is maintained at the central server which is simpler, and may allow more details to be stored and updated (e.g. if a fixed device is suddenly out of order, this can be more easily updated on a centralised record, rather than on every single individual's mobile device).

Alternatively the determining and comparing steps may be carried out at the mobile device. The advantage of this is that the process is self-contained, and easy to carry out without having to worry about the availability of any other communications networks to carry out the process

The determining step may comprise using the current geographical location to look up in a map database of fixed NFC devices, the NFC devices and their respective types. It is simply easier to contain all the details in one single database (location, type, availability), so that their details may be quickly and easily obtained and updated.

The method may further comprise updating the map database of fixed NFC devices. The activating step is in one embodiment carried out for a predetermined time period after which the NFC antenna is deactivated. The advantage of this is that the connection is only maintained for as long as possible as is required, which conserves the mobile device's resources. The alternative of keeping the antenna energised constantly can drain the mobile device's power substantially.

Brief Description of Drawings

Preferred embodiments of the present invention are described below with reference to the appended figures, in which:

Figure 1 is a schematic block diagram of an environment of a communications system carrying out interactions and data transfer in accordance with a first embodiment of the present invention;

Figure 2 is a schematic block diagram showing details of the components of the mobile device of Figure 1 ;

Figure 3 is a schematic block diagram showing details of the components of the remote terminal of Figure 1 ;

Figure 4 is a schematic block diagram showing details of the components of the central communications server of Figure 1 ; Figure 5 is a flow diagram of a high level process of user interaction with the system of Figure 1 , in the embodiment where the user is downloading an app;

Figures 6a and 6b are flow diagrams of a process carried out by the mobile device of Figure 2 when purchasing and downloading an app;

Figure 7 is a flow diagram of a process of providing an app using the remote terminal and central server of Figures 3 and 4;

Figure 8 is a flow diagram of a process of creating and/or updating a user profile for use in an improved NFC interaction in accordance with an embodiment of the present invention;

Figure 9 is a schematic block diagram of a user profile database of Figure 4, showing an embodiment where multiple user profiles, created by the process of Figure 8, are collated into a database;

Figure 10 is a flow diagram of a process carried out during an NFC interaction using the system of Figure 1 ; and Figure 1 1 is a flow diagram of a process carried out using the terminal and server of Figures 3 and 4, in preparation for an NFC interaction using the system of Figure 1. The figures laid out herein illustrate embodiments of the present invention but should not be construed as limiting to the scope of the invention. Where appropriate, like reference numerals will be used in different figures to relate to the same structural features of the illustrated embodiments.

Detailed Description of Exemplary Embodiments

The present embodiment, which is described herein, relates to a communications system which may be used to carry out interactions and transfer data between a remote fixed terminal and a mobile telecommunications device.

Figure 1 shows a communications system 10 used to implement a data transfer in accordance with a first embodiment of the present invention. The communications system 10 comprises at least one remote terminal 12, 12a for provision of services and data to the user of a mobile device 14 (for example, a mobile phone, tablet, laptop or other form of smart device with wireless communication capabilities). The remote terminal 12 is provided in this embodiment at a retail outlet at the Point of Sale (POS) terminal. Both the remote terminal 12 and the mobile device 14 comprise NFC capabilities (e.g. an NFC antenna) such that the data transfer and interaction between the two may be carried out via an NFC channel 16.

The communications system 10 of Figure 1 also comprises a communications network 18, and the mobile device 14 may be operatively connected to the remote terminal 12 via the communications network 18, so that communication channels 20 supporting modes of communication other than NFC channels (e.g. Bluetooth, WiFi internet connection, GPRS, 3G or 4G) may be utilised for interaction between the two devices. For example, the user may use the communications network 18 to transmit data from the mobile device 14 to a remote terminal 12 (and vice versa), in order to initiate the establishment of an NFC channel 16 between the terminal 12 and the mobile device 14.

The communications system 10 of Figure 1 also comprises a central communications server 22 which is operatively connected to the remote terminal 12 and to the mobile device 14 via the communications network 18. The central server 22 functions as a storage repository, which the remote terminal 12 and the mobile device 14 are able to reference to obtain additional data to carry out interactions and data transfer, and which aids in configuring the system 10 of Figure 1.

In certain embodiments, a server 24 of the mobile device operator may also be operatively connected to the central server 22 via the communications network 18. This server 24 provides a storage facility which the central server 22 (and the other components of the system 10) is able to reference for additional information when carrying out data transfers. In such embodiments, the mobile device operator's server 24 further comprises or is connected to a database 26 of mobile device user records, which can be used to match a unique identifier (for example, Mobile Identification Number MIN) of an individual mobile device to the type (i.e. make and model) of the mobile device. One example of a data transfer that may be carried out using the system 10 of Figure 1 is the download of software applications (apps) from the remote terminal 12 to the mobile device 14. These apps may be initially divided into a plurality of individually- downloadable portions, with a master portion (the 'app mask') that is relatively small and may be downloaded very quickly over a local wireless communication network. This app mask is typically downloaded first and contains executable instructions on how to subsequently control the download process for the remaining portions. Furthermore, to speed up the download process, the 'app mask' may be downloaded via a Near Field Communications (NFC) channel between the remote terminal 12 and the mobile device 14, after which the user may move away from the terminal and the remaining portions of the app may be downloaded at a later time using any means of local wireless

communication available. This process is described in greater detail later with reference to Figures 4 and 5. This is especially useful in cases where the throughput of users at a remote terminal is high and interaction with each customer must be processed quickly (e.g. in supermarkets or at unmanned vending machines for relatively fast purchase of apps). The division of apps into smaller individually downloadable portions is also especially useful in poor connectivity conditions, where a subsequent loss or reduction in quality of internet connection can cause the entire app download to fail if the app only comprises one portion. In the case of a segmented app download, any complete portions which had been successfully received prior to the connection failure would not need to be downloaded again, thereby reducing the overall time to download an app. In the above example of app download, the user may use a remote terminal to select, purchase and download an app to the mobile device via the NFC link 16 (as will be described in detail later with the aid of Figures 4 and 5). It is, however, also possible for the user to utilise the remote terminal to carry out other transactions or data transfers, and, upon provision of a unique identifier of their mobile device, receive (be 'pushed') an app that is associated with the purchase or retailer.

In one possible scenario, in response to the user making a purchase at a retail outlet's POS terminal, an app may be pushed to their mobile device providing discount coupons or vouchers for further shopping at that outlet. In an alternative scenario, the user's mobile device may additionally have a functionality enabled to store credit (e.g. an electronic wallet), enabling them to carry out transactions at a POS terminal for payment of goods/services. The mobile device may then automatically provide the POS terminal with a unique identifier of itself, and receive an app via an NFC transfer (as above). Figure 2 illustrates the components of the mobile device 14 used as part of the communications system 10 of Figure 1. Although all the main components required to carry out all embodiments of the present invention are shown in the figure, it will be appreciated by the skilled person that not all components are necessary to carry out every embodiment, and the configuration shown herein should not be regarded as limiting. The mobile device comprises a display screen 30, on which graphical representations 32 of the apps and app masks may be displayed to the user, to confirm their successful download and readiness for use. As previously described, the mobile device also comprises an active NFC antenna 34 which allows an NFC link 16 to be established with a separate fixed-location NFC capability at a remote terminal 12. The benefit of the mobile device having an active NFC capability (i.e. an active device requires a power supply whereas a passive device would not) is that an active NFC capability enables the communication and data being communicated to be varied, rendering the device more useful.

The NFC antenna 34 is arranged to be configured by an NFC antenna app 36, which is located in a data store 38 of the mobile device 14. The NFC antenna 34 is also arranged to be controlled by an NFC control app 40 which facilitates a selection procedure for an NFC transaction protocol and determines when and for how long the NFC antenna 34 is to be activated. This NFC control app 40 therefore regulates NFC interactions with one of a plurality of fixed-location NFC capable terminals 12, 12a, ensuring that the resultant interaction is both secure and simple.

The mobile device 14 also comprises a wireless communication module 42 which controls all standard means of local wireless communications so that the mobile device 14 may communicate with the separate remote terminals 12, 12a via these alternative channels 20. As previously described, one use of this is to transmit an initialisation request to the remote terminal 12 in order to gain approval for, and hence establish, an NFC link 16 between the mobile device 14 and the remote terminal 12.

The mobile device 14 comprises a central processor 44 which is operatively connected to the display screen 30, and the data store 38, as well as the NFC antenna 34 and the wireless communications module 42, and controls the interactions between all these various components.

The data store 38 stores a plurality of downloaded apps 46 which have corresponding representations 32 on the display screen. The data store 38 of the mobile device 14 further comprises a record 48 of identifying information of the mobile device 14, containing details of the device (e.g. the IMSI and the MIN) which may be used to identify to the remote terminal 12 in order to establish the NFC link 16. This record 48 may include a unique identifier 50 which is used to facilitate the download of an app from a remote terminal 12. This identifier 50 does not need to be highly unique as its main purpose is merely to distinguish the device from other local devices in the vicinity of the remote terminal 12 at that time - there may be a few tens of these around a POS terminal at a supermarket for example, but not hundreds or thousands. Thus only part of the unique identifier needs to be provided to permit distinction between different local devices in the same general region. This unique identifier may (in the case of a mobile phone) comprise some part of the mobile phone number (IMSI - for example the last 3 digits).

The data store 38 of the mobile device 14 also contains a user profile record 52, which is accessed by the NFC control app 40, and allows the user to select particular fixed NFC terminals 12, 12a which their mobile device 14 may communicate with using the NFC link 16. This increases the security with which NFC interactions may be carried out, as there is a greatly reduced risk of inadvertent communication with devices for which

communication is undesirable. As described earlier, this problem has been overcome in previous systems by requiring the user to input a Personal Identification Number (PIN) every time an NFC link is requested. The present embodiments obviate this need, and the user is able to control the level of interaction with a myriad of fixed NFC terminals without having to key in a passcode on each use, thereby greatly increasing the speed and simplicity with which an NFC link may be established while maintaining a minimal number of steps.

Furthermore, this functionality may be used to enable a more experienced first user to be in control of the settings of the mobile device, allowing a second user (who may be much less experienced in how to operate a mobile device) to utilise the device to carry out transactions. This is especially useful in the case of a parent (who owns the mobile device) being able to control how their child (to whom the mobile device is given) uses that device for making payments of purchasing goods. The parent may set up the user profile, and the child would only be able to use the mobile device to communicate with approved NFC terminals. For example, the parent could only allow the device to be used on transportation ticketing fixed NFC terminals, thereby enabling the child to always have the ability to purchase a transportation ticket home, whilst preventing the child from using the credit on their mobile device to purchase goods at a retail outlet POS terminal instead. The mobile device 14 further comprises a GPS location tracker 54 to determine its current position; the GPS location tracker 54 is operatively connected to the central processor 44 so that the location information may be utilised in processes involving other components. The mobile device 14 also comprises a map 56 which is periodically updated, and which contains details of the location and categorisation of all fixed NFC terminals 12, 12a that the mobile device 14 may potentially interact with at any given time. These may be used in combination with the user profile 52 in the mobile device 14 to locate potential nearby fixed NFC terminals with which an NFC link may be

established, and to subsequently carry out transactions and data transfers. In this regard, the data store of this embodiment also comprises a mobile wallet 58 which can be used in such transactions.

Figure 3 illustrates the components of the remote terminal 12 used as part of the communications system 10 of Figure 1. Although all the main components required to carry out all embodiments of the present invention are shown in the figure, it will be appreciated by the skilled person that only a subset of components are necessary to carry out particular embodiments, and the configuration shown herein should not be regarded as limiting.

The terminal 12 comprises a display screen (for example a touch screen) 70 whereby an exchange of information may take place between the terminal 12 and the user. For example, the display screen may provide graphical representations 72 of available apps 46, allowing the user to browse the range of possible apps 46 for download, and to input their selection.

The terminal 12 also comprises a data store 74 which contains an app database 76, providing a record of all possible apps 46 that are available for selection by a user. In addition, the data store 74 of the terminal 12 further comprises an app log database 78 containing a record of the details of each mobile device 14 (and user) with which the terminal 12 has interacted, as well as a log of all the apps 46 associated with each mobile device 14 that have been pushed to each mobile device by the terminal 12. This app log database 78 may be accessed at any time to provide a method of auditing the app provision process.

The remote terminal 12 also comprises a wireless communication module 80 (which provides at least one channel 20 of local wireless communication), as well as providing an NFC capability (i.e. having an NFC antenna 82). The remote terminal 12 may thereby exchange information with the mobile device 14, as well as with the central server 22, by multiple different communication channels 16, 20.

For example, in certain embodiments, the details of the downloaded app, together with the associated mobile device 14 and user to which the app is provided, may be transmitted from the remote terminal 12 to a centralised website or server 22 using the communications network 18. This website or server may then provide, via other terminals or other communication channels, additional portions of the app to the user's mobile device 14 in response to receiving this transmission from the remote terminal 12.

The terminal 12 also comprises a system controller (processor) 84 which is operatively connected to the display screen 70, the data store 74, and both the NFC antenna 82 and the wireless communications module 80, controlling the interaction and data transfer between the different components.

Figure 4 illustrates the components of the central communications server 22 used as part of the system 10 of Figure 1. Although all the main components required to carry out all embodiments of the present invention are shown in the figure, it will be

appreciated by the skilled person that only a subset of components are necessary to carry out particular embodiments, and the configuration shown herein should not be regarded as limiting.

The central server 22 comprises a wireless communication module 90 enabling the exchange of data with the remote terminal 12 and mobile device 14 via the

communications network 18, as shown in Figure 1.

In certain embodiments, the central server may additionally comprise an app database 92, similar to the app database 76 comprised in the remote terminal 12 of Figure 3. Depending on the storage capacity of the terminal and the number of apps available at the terminal for download, the terminal 12 may not have sufficient capacity to

accommodate all possible apps 46. Instead, the bulk of each app (or even the entire app) may be stored at the central server 22 and only a small portion of the apps (e.g. the app masks) or a simple graphical representation 72 of the app may be displayed on the terminal display screen 70. Once the user has selected a particular app, the terminal 12 may then communicate with the central server 22 and retrieve the rest of the app for provision to the user.

Similarly, the central server 22 may also comprise a database (not shown) containing the details of every mobile device that has interacted with the connected terminal, as well as a log of all the apps that have ever been pushed to each device. This can aid in the secondary download process when the remainder of the app is downloaded not from the terminal itself, but from the centralised website or server 22 via a different

communications channel which is suitable for the download.

In one embodiment of the present invention, the map 56 of NFC terminal types together with their associated GPS locations (shown in Figure 2 to be stored in the mobile device 14) may instead be stored at the central server 22. In a further embodiment of the present invention, the user profile records of every single registered mobile device user (previously shown to be stored in the mobile device) may be collated and stored at the central server in a large user profiles database 94. In such embodiments, the server 22 (rather than the mobile device 14) may carry out the determination of allowable fixed NFC terminals, and send back a trigger message to the mobile device 14, using the wireless communications module 90, to trigger activation of the mobile device's NFC antenna 34. The configuration of this embodiment uses less mobile phone resources, and only requires a single centrally-updated map of the fixed devices and their categorisation to be stored on the central server 22, which is easier to update than individual maps on millions of user's mobile devices.

Finally, the central server 22 may also comprise a software updates database 96, which contains a record of all possible mobile device types as well as the corresponding software updates available for each device type. Specifically, this database may contain details of the software updates required to configure the NFC antenna 34 of each individual type of mobile device 14. These updates may be provided to the user's mobile device 14 in an automated process (described later in Figure 11) which configures the device's NFC antenna 34 quickly and easily, with very little user interaction or know-how required.

The central server 22 comprises a system central processor 98 to which all other components are operatively connected, to enable interactions and for data to be transferred between these components.

One of the ways by which the improved NFC interaction may be utilised is in the download of apps, implemented on the system 10 as described earlier, and further illustrated in the flow diagrams of Figures 5, 6a, 6b and 7. These figures contrast the user interaction and input required to carry out the download (Figure 5) with the steps carried out by the mobile device (Figures 6a and 6b), as well as the terminal and central server (Figure 7), to effect the download. Figure 5 illustrates an embodiment of the present invention in which the user is involved in the selection of the app for download at the remote terminal.

The process 100 begins when the user at a remote terminal 12 selects an app 46 for download at Step 102. This may involve browsing through a selection of apps 72 on a display screen 70 of the terminal; alternatively, Step 102 may involve the user having browsed through a catalogue of available apps in-store and entering at Step 102 the name or selection of the app at the terminal 12. The terminal 12 then determines at Step 104 whether payment for the app 46 is required. If the app requires payment, the user is notified of this and pays at Step 106 for the app at the terminal using any conventional mode of payment.

After an app has been selected, the user provides at Step 102 the unique identifier 50 of the mobile device 14 to the terminal 12, so that the terminal may identify the mobile device and enable transmission of the app 46 to the mobile device 14. The process 100 then enables at Step 109 the NFC communications channel 16 for transmission of the app. The terminal retrieves the app details from its associated app database 76 and creates a unique transaction identifier (which may comprise a representation of the transaction details, mobile device details, or a combination of the two). The app mask, together with the unique transaction identifier, is then transferred to the mobile device 14.

It will be appreciated that in those embodiments where the app database is located at the central server 22 instead of the terminal 12, there is an additional step (not shown) in process 100 where the terminal 12 requests the transfer of the app from the central server 22, and then provides the app 46 to the user's mobile device 14.

In the present embodiments, the transfer of the app mask and transaction identifier takes place using the NFC channel 16. One method by which this may be carried out is shown in Figure 10, and is described in greater detail later in this document.

Once the app mask has been received at Step 110 by the mobile device 14, a graphical representation 32 of the app is displayed on the screen 30 of the mobile device 14, and the user is provided at Stage 108 with the unique transaction identifier, to confirm that the app has been paid for and the first stage of download has been successful.

The app mask then automatically initiates at Step 112 the second stage of download, whereby the remaining portions (content components) of the app are individually downloaded onto the mobile device 14. The process then checks at Step 1 14 whether Know-Your-Client (KYC) checks are required, as certain apps will require KYC checks to be carried out before they may be used (e.g. those which will involve financial transactions). In those cases, the unique transaction identifier (which earlier functioned as a confirmation of successful initial app download) may be provided at Step 116 by the user as a proof of purchase and of the identity of their mobile device, together with some basic personal details of the user. In some embodiments, the app mask may have some limited user interface functionality, allowing the app mask to prompt a user for input of their personal details. These details are then stored and may be provided by the app when registration or KYC checks are carried out. One example of how this could be used is described in our International patent applications WO 2009/019602A and WO 2010/086827A, where the information stored on the smart phone would be used as virtual multifunction tickets.

Once the user has provided this data at Step 116, the co-pending app download continues at Step 1 18. Once all the remaining portions of the app have been successfully downloaded, the second stage of download is complete and the app mask confirms to the user at Step 120 that the app is ready for use. This confirmation may comprise any one of a number of conventional notification means, such as an on-screen pop-up notification, or a change in the graphical representation 32 of the app mask on the device screen.

It will be appreciated by the skilled person that in those embodiments where an app is automatically pushed to the user's mobile device (e.g. upon the carrying out of a separate transaction), the user will not have to go through any of the app selection Steps 102 to 106 at the terminal. In addition, in some cases, the user may not need to provide the unique identifier of their mobile device. For example, if the user has just carried out a transaction (using credit from their mobile device), the mobile device 14 will already have been identified by the terminal 12, to establish communication between the two and the identity of the mobile device will already be known. The terminal may then easily push an app straight to the mobile device, and the download process will begin at Step 110 with the receipt of the app mask by the user. By contrast, the flow diagrams of Figures 6a and 6b illustrate the underlying processes that are carried out by the mobile device 14, in combination with the remote terminal 12.

The process 130 begins when the mobile device 14 receives at Step 132 a request from the terminal 12 that the terminal would like to push an app to the mobile device, (for example, in response to actions of the user carried out at the terminal). The mobile device 14 then establishes at Step 134 an NFC communications link 16 with the terminal 12, preferably by the method illustrated in Figure 10 (although other means of wireless communication would also be acceptable), and the app mask and unique transaction identifier are transmitted at Step 136 to the mobile device from the terminal. The mobile device displays at Step 138 the app mask on its screen as proof that the purchase and initial download have been successful. The app mask, which contains instructions for how the remainder of the app is to be downloaded, then carries out the following steps in the background of normal operation of the mobile device (hidden from the user's view and without requiring any further user intervention).

In certain embodiments, the remainder of the app has already been divided into predetermined individual portions (content components), and the app mask may contain a log of all these portions. Alternatively, the app mask may contain instructions to carry out the segmentation of the app (not shown) to be downloaded into small easily- downloadable portions. In either situation, the app mask creates at Step 140 a record of all the remaining portions to download, as well as a placeholder marker, which is placed at the beginning of the first of the remaining portions. Thereafter, as the secondary download progresses, once each portion has been successfully downloaded, the marker will be moved to the beginning of the next portion to be downloaded.

The app mask then checks in Step 142 whether the NFC channel link 16 is maintained between the mobile device 14 and the terminal 12. If the NFC link is maintained, the app mask skips Steps 144 to 148 of process 130, and proceeds to access at Step 150 the location where the remaining app portions are stored for download.

In cases where the mobile device 14 no longer has an open NFC communication channel 16 with the terminal 12, the secondary download process begins with the app instructing at Step 144 the wireless communications module 42 of the mobile device 14 to search for all available wireless communications networks. The network with the strongest signal is selected at Step 146, and the mobile device attempts to connect to it. In certain embodiments, once a connection has been initiated a timer may be started (not shown). The length of time that an uninterrupted communication is maintained between the terminal and mobile device is thereby monitored and the app mask determines at Step 148 if the connection has been maintained for a predetermined length of time (for example, longer than 30 seconds to ensure that the connection is not transient). If the time period criterion is met, the app mask provides at Step 150 the mobile device 14 with the requisite information to allow the mobile device to access the location where the remaining portions of the app are stored. If the time period criterion is not met, the app mask instructs at Step 148 the mobile device 14 to repeat Steps 144 to 148 until a wireless communication has been established for the required length of time.

Once a communication channel has been reliably established, the process 130 proceeds at Step 152 to download the first of the remaining app portions, beginning from the position of the placeholder marker. After a period of time has elapsed, the app mask checks at Step 154 if the selected portion has been completely downloaded. If this is not the case, the app mask then checks at Step 156 if the communication channel is still open. In the case where the communications link has been prematurely terminated (for example, if the user has moved out of the range of the network), the app mask will proceed at Step 158 to maintain the marker at its current position and repeat the remainder of the process 130, from the searching at Step 144 for a wireless

communication network onwards. However, if the app mask determines at Step 156 that the download of the selected portion has not been completed but the communication channel is still open, the app mask will maintain at Step 160 the marker position and continue with the download, repeating the check at Step 154 at a later time. Once the app mask has determined at Step 154 that the selected portion of the app has been successfully downloaded, a check is then performed at Step 162 to determine if the marker position in the log indicates that all portions of the app have been successfully downloaded. If this is the case, the app mask proceeds to combine (not shown) all portions of the app so that the app can function as intended. The app mask then notifies at Step 164 the user that the app download has been successfully completed and that the app is now ready for use. The process 130 terminates at this step. Alternatively, if it is determined at Step 162 that the entire app has not been downloaded, the app mask then checks at Step 166 if the communication channel is still open. As in the earlier scenario where the communication link has been prematurely terminated, the app mask will proceed at Step 158 to maintain the marker at its current position and repeat the remainder of the process 130, from the searching at Step 144 for a wireless communication network onwards. However, if it is determined at Step 166 that the communication link has been maintained, the app mask will proceed at Step 168 to move the marker to the beginning of the next section and repeat (beginning from Step 152) the download of the next portion of the app.

From the above described steps, it may be seen that the download process is constantly monitored by the app mask, and if the network connection is lost at any time before the download of a selected portion has been completed (or before the entire app has been successfully downloaded), the marker position in the log is maintained and the app mask instructs the mobile device to repeat the steps of the download process beginning from the stage where a search for available network connections is carried out.

Using this method, the app download is carried out in a manner that requires minimal input from the user, and thereby makes apps more accessible to the technologically- savvy users. Although the segmentation of the app may add slightly to the overall time required for the download (assuming an uninterrupted and constant quality

communications link to the mobile device), the main advantage lies in the reduced overall download times in less optimal conditions where the connections are of poor quality.

The flow diagram of Figure 7 also shows the process of app download by a mobile device 14 from a remote terminal 12, but focuses on the steps carried out by the terminal 12, including its interaction with the central server 22. The process 170 begins with the terminal receiving at Step 172 details of the user's mobile device 14, including the unique identifier of the device. The terminal 12 then establishes at Step 174 an NFC communications channel 16 with the mobile device, using both the NFC antenna 82 of the terminal 12 and the NFC antenna 34 of the mobile device 14. In the present embodiment, the NFC communications channel 16 is established in the manner illustrated in Figure 10.

Once a stable NFC communication channel has been established between the terminal 12 and the mobile device 14, the terminal then retrieves at Step 176 the app mask from an app database for transmission to the mobile device. In preferred embodiments, the app database 76 may be located within the terminal itself (as shown in Figure 3), or in operative connection to it. Alternatively, the app database 92 may be located at the central server 22 (as shown in Figure 4). In the case of the latter, the terminal 12 must also send a message to the central server 22 (not shown) to request the desired app. Upon receipt of this message, the central server will then transmit (not shown) the app mask to the terminal for provision to the user. A unique transaction identifier is then created at Step 178 at the terminal, and may be based on and/or represent one or more of the details of the transaction, the app details and the mobile device identifying details. The unique transaction identifier is then transmitted at Step 180 to the mobile device, together with the app mask, via the NFC channel 16 that was established at Step 174.

Once this initial transmission has been successfully completed, the terminal accesses at Step 182 the app log database 78 (described earlier with reference to Figure 3), and updates the records contained therein with the details of the user's mobile device, the app mask (and details of the associated app) that was transmitted to the mobile device, and the unique transaction identifier that was generated at Step 178. As previously discussed, the database 78 may be comprised within the terminal 12, or alternatively comprised within the central server 22.

In order to begin the transfer of the remaining portion of the app, the terminal 12 must first ascertain at Step 184 if the terminal has direct access to the remainder of the app, or if the app is stored in the app database 92 at the central server 22.

If the terminal does have direct access to the remainder of the app, the terminal will then attempt to provide the remainder of the app to the mobile device. This process begins with a check at Step 186 to determine a communication channel exists or may be established between the mobile device and the terminal. In this case, the communication channel may comprise the NFC communication link 16 which was established at Step 174 and remains open, or the communication channel may comprise a different communication channel 20 established (not shown) via the communications network 18. Once a stable communications link has been established between the mobile device and the terminal, the terminal begins at Step 188 to retrieve and carry out the download of the first of the remaining portions of the app.

Subsequently, the terminal determines at Step 190 whether the download of the portion in the previous step has resulted in the successful download of the entire app. Once the download has been completed, the terminal terminates at Step 192 the communications link between itself and the mobile device, and the process 170 finishes. If the app download is determined at Step 190 to be incomplete, Steps 186 to 190 are repeated until such as a time as the app is completely downloaded, or the terminal cannot establish a stable communications channel with the mobile device. A placeholder marker and log of all portions of the app may be utilised in this step to keep track of the completeness of the app download (using a similar method to that used by the app mask in process 130).

If it is determined at Step 184 that the remainder of the app is not available for download directly from the remote terminal, or if it is determined at Step 186 that the terminal cannot establish a stable communications link with the mobile device, then a message is transmitted at Step 194 to the central server 22 (via the communications network 18). This message contains any details of the user's mobile device 12 and the app 46 that is to be downloaded, that the central server may require to establish (not shown) a communication channel with the mobile device to carry out the secondary download of the remaining portions of the app. Once the terminal has completed Step 194, the terminal proceeds to terminate at Stage 192 any communications link between the terminal and the mobile device, and the process 170 is deemed to have been completed. Subsequently (not shown), the app mask on the mobile device 14 must access the central server 22 or a centralised website to download the remaining portions of an app (in which case the information required to enable this will be contained within the app mask).

The present embodiment as shown in Figures 8-10 relates to a method of improved NFC interaction between a user's mobile device 14 and one of a plurality of fixed NFC terminals 12, 12a with which the mobile device has the potential to connect. This method is controlled by the NFC control app 40 which is downloaded to the user's mobile device 14, either through the processes 130, 170 described above with reference to Figures 5, 6 and 6a, or in a pre-installation process (not shown) that takes place before the user acquires the mobile device 14. The first stage in this method involves an initialisation process 200 which is shown in the flow diagram of Figure 8. The NFC control app 40 begins process 200 by providing at Step 202 a list of all possible types or categories of fixed-location NFC terminals 12, 12a that the user's mobile device 14 may connect to at a later time. For example, the terminals may be categorised based on their usages, such as Retail POS terminals, Transport Ticketing terminals. The NFC control app then receives at Step 204 the user's selection of those types of fixed terminals with which the mobile device 14 is allowed to carry out NFC interactions. Step 204 may involve the user selecting only those terminal types that they wish to allow NFC interactions with, while the others are automatically rejected; alternatively, Step 204 may involve the user actively either accepting or rejecting the terminal types on a case by case basis.

Once the user's selection has been received, the NFC control app 40 checks at Step 206 if a user profile record 52 containing the relevant information has previously been created and stored in the data store 38 of the mobile device 14. If no such record is located (for example, if this is the first time the user has used the NFC capabilities of their mobile device), the NFC control app creates at Step 208 the user profile record 52 comprising a log of all the fixed-location terminal types that have been approved for future NFC communication. If a user profile record 52 is located at Step 206, the NFC control app 40 updates at Step 210 the record with the newly-input information. The process 200 is then complete.

It should be noted that the user profile record 52 may be updated, and categories of NFC terminals may be added to or removed from the user profile record 52 at any time.

Furthermore, in some embodiments, it may be also possible to introduce the feature of password-protection, such that the ability to update the user profile record is only available to the user with the correct password. This would be advantageous in the earlier example of the parent and child, whereby the parent would set up the user profile with a password protection so that the user profile cannot be altered by the child at a later date.

It will be appreciated that it is not necessary for the user profile record 52 to be kept solely in the mobile device 14. Instead, this record may be contained in a large user profile database 94 at the central server 22, along with the details of multiple other mobile device users, and their NFC interaction preferences. The user may potentially need to register for this service, but this may be carried out (not shown) via the NFC control app, or may be simply carried out at a centralised website.

One embodiment of a user profile database 94 located at the central server 22 can be seen in Figure 9, in which the details associated with each user occupy a horizontal row 212 in the table. These details comprise (but are not limited to) a User ID 214

representing the user's identity and details, and/or a Device ID 216 which provides the identifying details of the user's mobile device 14 that are required to enable an NFC connection with said device to be established. Each user's profile will also contain a record 218 of all the fixed-location terminals 12, 12a that are approved for NFC interaction with the user's mobile device 14. In certain embodiments, the user profile may comprise a log of all possible fixed NFC terminals with a marker for each one denoting approval or rejection by the user. For example, in the user profile database 94 of Figure 9, User A001 has approved their mobile device for connection with retail POS and ticketing type fixed NFC terminals, but not with NFC terminals used for advertising purposes. The flow diagram of Figure 10 illustrates the steps of process 220 that are required to carry out the method of improved NFC interactions (after a user profile has been established), for certain embodiments of the present invention whereby the mobile device 14 comprises the user profile record 52. When the user wishes to carry out an NFC interaction with a particular fixed NFC terminal using their mobile device, the NFC control app 40 is automatically activated at Step 222 and controls the following steps in process 220.

First, the current GPS location of the mobile device 14 is retrieved at Step 224 from the GPS location tracker 54. The NFC control app 40 then accesses at Step 226 the map 56, which is periodically updated and contains details of all the NFC terminals 12, 12a that are associated with a particular GPS location. The app 40 also retrieves at Step 226 the details of all the terminals 12, 12a which have a GPS location corresponding to that of the mobile device 14. The NFC control app 40 then selects at Step 228 a terminal from those retrieved in the previous step and determines its type or category. The terminal type is then compared at Step 230 with the list of pre-selected approved device categories contained in the user profile record 52. If it is subsequently determined at Step 232 that the terminal type currently selected is not a match for any of the approved types in the user profile record, the selecting and comparing at Steps 228 and 230 is repeated until a match is found.

Once the NFC control app 40 has determined that a particular fixed NFC terminal 12 present at the current location is of a pre-approved type, the app transmits at Step 234 the GPS location data of the mobile device 14, together with certain unique identifying details of the mobile device, to the fixed NFC terminal 12 via the communications network 18. This transmission may be carried out using, for example, standard messaging service SMS, or another free communications channel such as BlackBerry Messenger. The purpose of this transmission is to inform the chosen terminal 12 that the mobile device 14 intends to establish an NFC link 16 with it.

Once the fixed terminal 12 has received the transmitted message, and if the terminal is able to establish an NFC link 16 with the mobile device 14, the terminal transmits (not shown) a communication to the mobile device 14 which indicates approval and contains identifying details of the fixed terminal. Upon receipt at Step 236 of this communication, the NFC control app 40 energises and activates at Step 238 the NFC antenna 34 on the mobile device 14 (or instruct the NFC antenna app 36 to do so) to establish an NFC link 16 with the fixed terminal 12.

In the present embodiment, the NFC control app 40 comprises a timer which is activated at Step 240 once an NFC link has been established. The timer is set to record a predetermined period of time (e.g. five minutes, which should be sufficient time for the user to take their mobile device to the fixed device and carry out the transaction or data transfer). The NFC interaction and data transfer is then begun at Step 242.

The NFC control app 40 is programmed with instructions so that at certain time intervals (for example, every minute) the NFC control app checks at Step 244 to determine if the predetermined time period allocated for the NFC interaction has expired, and if the data transfer has been successfully completed. If the transfer is incomplete (but the predetermined time limit has not yet been reached), Steps 242 to 246 are repeated until the download has been completed. In the scenario at Step 246 where the data transfer is incomplete but the predetermined time limit has been reached, the timer is reset or paused at Step 248 and the NFC interaction is maintained at Step 242 so that the data transfer remains uninterrupted. The progress check at Step 244 is performed periodically until it is determined at Step 250 that the data transfer has been successfully completed. At this stage, regardless of whether the time limit has been reached, the NFC control app 40 proceeds at Step 252 to issue instructions to the NFC antenna app 36 to deactivate or de-energise the NFC antenna 34. The process 220 of establishing an NFC interaction, and maintaining the NFC interaction until a successful data transfer has occurred, is then deemed complete.

In certain embodiments, the NFC control app 40 may additionally comprise a marker of some sort which indicates when the data transfer is completed. Other embodiments might involve the fixed NFC terminal 12 sending a communication to the mobile device 14 to notify the mobile device that the data transfer has been completed and the NFC antenna 34 may be deactivated. This method of NFC interaction represents an improvement over previous methods as it is easy for the NFC antenna to be automatically activated and deactivated for only as long as is required for a data transfer to occur. This decreases the power output required for the mobile device and helps to conserve its battery life. In addition, the automated procedure involving only pre-selected approved devices simplifies the user experience when carrying out NFC interactions and data transfers, whilst maintaining the security of the interactions. It will be appreciated that in some instances, it may be possible for there to be more than one fixed terminal at the current location of the mobile device which is of a user- approved type. Therefore, certain embodiments may include functionalities allowing the NFC control app 40 to display these as options for the user to select the desired one. Alternatively, the app 40 could automatically rank the fixed terminals based on other factors (for example, if the mobile device has previously successfully communicated with a particular terminal, that terminal could be ranked first), and prioritise communication with the highest ranked terminal, if no specific instructions are provided by the user. In alternative embodiments, the user profile record 52 may be comprised in the user profile database 94 at the central server 22. In addition, the map 56 containing the locations and types of all available fixed NFC terminals, may also be located at the central server 22. In such embodiments, the process of establishing NFC

communications is still controlled by the NFC control app 40 on the mobile device 14 and is similar to that described with reference to Figure 10, with a few minor differences.

At the beginning of process 220, prior to the accessing of the map at Step 226, the GPS location and unique identifier of the mobile device 14 must be transmitted (not shown) to the central server 22 so that the correct user profile 212 there may be retrieved, and the details 218 of approved fixed NFC terminals comprised therein may be compared with the map 56 to determine which of the nearby fixed NFC terminals 12, 12a the mobile device 14 may communicate with. The comparing and determining Steps 228 to 232 are then carried out as before and a fixed device is selected, although these steps are carried out at the central server 22 instead of at the mobile device 14. A message is transmitted (not shown) from the central server 22 to the mobile device 14, and contains details of the fixed terminal required for an NFC communications link 16 to be established. Thereafter, all the remaining steps (from Step 234 onwards) are

substantially the same, as the NFC control app 40 on the mobile device 14 handles the initialisation and termination of the NFC interaction 16.

One advantage of locating the map 56 of fixed NFC terminals at the central server 22 is that there only needs to be one centrally updated map, as opposed to millions of maps (one on each individual user's mobile device). The single central map may therefore be more comprehensive and contain a greater amount of information, as the storage capacity and processing ability of the server will be much greater than that of any individual mobile device. This configuration will also reduce the proportion of the mobile device's resources that need to be allocated to this particular process.

A method of configuring and controlling the mobile device's NFC antenna 34 for a specific use (in an automated and simple way), according to one embodiment of the present invention, is described below with reference the flow diagram of Figure 11.

The process 260 begins with the user at a remote terminal 12, where the option to carry out the configuration of a mobile device's NFC antenna 34 is provided. The terminal display screen 70 provides at Step 262 a means of transmitting information relating to the user's mobile device which will be used to facilitate the configuration process. The information transmitted using this method is received at the terminal at Step 264, providing the terminal with identifying details of the user's mobile device. These details are then displayed at Step 266 on the terminal's screen 70, to allow the user to confirm that the details are correct. The terminal checks to see if a confirmation has been received from the user: if a confirmation has not been received from the user, the entire process 260 begins again from Step 262.

One simplifying example of this process is the case of a mobile phone, where the terminal display screen displays a phone number for the user to dial. This number is configured not to require an answer. When the user dials the number, their mobile phone number (unique identifier) is automatically recorded (for example by a server 22 or database in operative connection with the terminal 12), and transmitted to the terminal for display to the user. The user must subsequently provide confirmation that this number is the correct one before the configuration can take place (for example, by indicating on the terminal display screen that the displayed number corresponds to his mobile device).

Once this initial stage has been successfully completed, the terminal 12 transmits at Step 270 the unique identifier of the mobile device to the central server 22, which is also operatively connected to the server 24 of the mobile device's service provider via the communications network 18. The service provider's server 24 comprises a database 26 of mobile device user records, which contains a log of each mobile device user, their mobile device identifier, and the type (i.e. make and model) of mobile device associated with that identifier. The central server 22 retrieves at Step 272 the records from the data base 26, and compares at Step 274 these records to the unique mobile device identifier (provided at Step 270). The central server thereby is able to determine the device type that is associated with that particular mobile device identifier.

The central server 22 then accesses (not shown) the software updates database 96, which contains a record of all types of mobile devices, and the corresponding software updates that are required to correctly configure and control the NFC antenna for each one. The central server then compares this information at Step 276 to the mobile device type (obtained in the previous step), in order to identify the correct software update that is required to configure the NFC antenna corresponding to the mobile device type.

Once the comparison has been carried out and the correct software update has been successfully identified, the central server 22 transmits at Step 278 this software (using any means of wireless network connection 16, 20) to the mobile device 14. The central server then creates or updates at Step 280 a user profile with details of the mobile device, as well as the software updates provided to it, so that when any new software updates are subsequently released, the mobile device 14 may be notified and the new updates may be transmitted to the mobile device 14.

The central server 22 then determines at Step 282 whether any further software updates are required. If so, the central server repeats Steps 276 to 282, providing the correct software updates and updating the internal records to reflect this.

Once the mobile device 14 has been provided with all the correct software containing instructions for configuring the NFC antenna, the NFC antenna app 36 may then automatically configure at Step 284 the NFC antenna 34 according to the provided instructions so as to allow the NFC antenna to establish an NFC channel 16.

In certain embodiments, where a unique identifier of the mobile device is required to carry out an interaction of data transfer, the user may not be required to actively provide the unique identifier of their mobile device to the terminal. Instead, the mobile device may be configured to automatically transmit the unique identifier to the terminal or directly to the central server, depending on the process that is being carried out. All herein described embodiments are for illustrative purposes only and are not to be deemed limiting to the present invention. Minor amendments of the herein described embodiments may be made without departing from the spirit and scope of the present invention.

Claims

1. A method of downloading a selected application program (app) to a mobile device via a wireless communications channel, the app comprising a plurality of components including an app mask and at least one content component, wherein the app mask comprises instructions for controlling the download of the at least one content component, the method comprising:

Establishing a wireless communications channel between the mobile device and a terminal;

Receiving the app mask at the mobile device via the wireless channel;

Using the app mask to control downloading of the at least one content component until the entire app has been downloaded; and

Making the app available on the mobile device for use.

2. The method of Claim 1 , wherein the establishing step comprises establishing a Near Field Communications (NFC) channel between the mobile device and the terminal.

3. The method of Claim 2, wherein the establishing step comprises transmitting a mobile device identifier to a central server via an alternative wireless communications channel, the device identifier enabling the central server to determine the required configuration data for the mobile device and receiving the configuration data from the central server and configuring an NFC aerial in the mobile device for use with the terminal.

4. The method of Claim 3, wherein the configuration data is arranged to control the timing and duration of the operation of the NFC antenna.

5. The method of any of Claims 1 to 4, wherein the establishing step comprises comparing a currently available type of terminal with a set of user-selected terminals and enabling the establishing step to be carried out if the currently available terminal matches a pre-selected type of terminal.

6. The method of Claim 5, wherein the establishing step comprises selecting the terminal on the basis of a type of service that the terminal provides.

7. The method of Claim 5 or 6, further comprising determining a current geographic location of the mobile device and wherein the establishing step comprises selecting the terminal on the basis of a geographic location of the terminal.

8. The method of any of Claims 1 to 7, wherein the using step comprises monitoring the established wireless communications channel and if the strength of the wireless communications channel is below a predetermined threshold, carrying out a search of other wireless channels available to the mobile device for the download of the at least one content component.

9. The method of Claim 8, wherein the using step comprises monitoring the strength of any wireless channels available to the mobile device for the download of the at least one content component and choosing the wireless channel with the strongest signal.

10. The method of Claim 9, wherein the choosing step comprises checking that the connection with the strongest wireless channel has been maintained for a predetermined time before choosing the wireless channel for use.

1 1. The method of any of Claims 1 to 10, wherein the receiving step further comprises receiving a unique transaction identifier from the terminal for use in validating the app mask.

12. The method of any of Claims 1 to 11 , further comprising discarding a current content component if the current content component has not completely been downloaded via a wireless channel and a new content component is being received via a different wireless communications channel.

13. The method of any of Claims 1 to 12, wherein the receiving step comprises incrementing a marker of the number of content components which have been successfully downloaded after completion of download of a current content component.

14. A mobile device arranged to download a selected application program (app) via a wireless communications channel, the app comprising a plurality of components including an app mask and at least one content component, wherein the app mask comprises instructions for controlling the download of the at least one content component, the mobile device comprising:

A wireless communications module for establishing a wireless communications channel between the mobile device and a terminal;

The app mask received at the mobile device via the wireless channel;

A controller arranged to use the app mask to control downloading of the at least one content component until the entire app has been downloaded; and

A display for making the app available on the mobile device for use.

15. A method of transmitting a selected application program (app) to a mobile device via a wireless communications channel, the app comprising a plurality of components including an app mask and at least one content component, the method comprising:

Establishing a wireless communications channel between a terminal and the mobile device;

Providing the app mask from the terminal to the mobile device via the wireless channel; the app mask comprising executable instructions for controlling the

downloading of the at least one content component until the entire app has been downloaded;

Receiving control instructions from the app mask operating on the mobile device; Transmitting the at least one content component to the mobile device via a currently available wireless communications channel, wherein the currently available wireless communications channel comprises the established wireless communication channel or a different available wireless communications channel to the mobile device; and

Continuing the transmitting step until the entire app has been downloaded.

16. The method of Claim 15, wherein the establishing step comprises establishing a Near Field Communications (NFC) channel between the terminal and the mobile device.

17. The method of Claim 15 or 16, wherein the transmitting step further comprises transmitting a unique transaction identifier from the terminal for use in validating the app mask.

18. The method of any of Claims 15 to17, wherein the transmitting step comprises providing a marker of the number of content components which have been successfully downloaded and incrementing the marker after completion of download of a current content component.

19. The method of Claim 18, further comprising retransmitting the current content component indicated by the marker if the current content component is unable to be completely downloaded by the mobile device.

20. The method of any of Claims 15 to19, further comprising providing at least one further wireless communications channel to the mobile device and using the at least one further wireless communications channel for the transmission of the at least one content components if requested by the mobile device.

21. The method of any of Claims 1 to 20, wherein the app mask is relatively small in size compared to the at least one content component.

22. The method of any of Claims 1 to 21 , wherein the at least one content component comprises a plurality of content components.

23. A terminal for transmitting a selected application program (app) to a mobile device via a wireless communications channel, the app comprising a plurality of components including an app mask and at least one content component, the terminal comprising:

A communications module for establishing a wireless communications channel between a terminal and the mobile device;

an app mask module for providing the app mask from the terminal to the mobile device via the wireless channel; the app mask comprising executable instructions for controlling the downloading of the at least one content component until the entire app has been downloaded;

A receiver for receiving control instructions from the app mask operating on the mobile device; and

A content module arranged to transmit the at least one content component to the mobile device via a currently available wireless communications channel, wherein the currently available wireless communications channel comprises the established wireless communication channel or a different available wireless communications channel to the mobile device;

Wherein the content module is arranged to continue to transmit the at least one content component until the entire app has been downloaded.

24. A combination of a server and a terminal of Claim 23, wherein the server is operatively connected to the terminal via a communications network and is configured to provide additional storage for the at least one content component of the app.

25. A method of controlling a Near Field Communications (NFC) interaction between a mobile device and a fixed NFC device, the method comprising:

Storing, in a user profile file, a user selection of a type of NFC fixed device with which communication will be permitted; and

Conducting a potential interaction event;

wherein the conducting step comprises:

a) Establishing a current geographical location of the mobile device;

b) Transmitting the current geographical location and a unique identifier of the mobile device to a central server;

c) Determining the types of fixed NFC devices present in the current location; d) Comparing the types for the fixed NFC devices at the current location with those specified by the user profile; and

e) If any of the fixed NFC devices at the current location match those specified in the user profile, activating an NFC antenna in the mobile device to facilitate an NFC interaction with the fixed NFC device.

26. A method according to Claim 25, wherein the transmitting step is carried out via a non-NFC communications channel.

27. A method according to Claim 26, wherein the non-NFC communication channel comprises a SMS messaging channel, a WiFi communications channel, 3/4 G

telecommunications channel.

28. A method according to any of Claims 25 to 27, wherein the determining and comparing steps are carried out at the central server and the method further comprises sending back to the mobile device a trigger message for triggering execution of the activating step.

29. A method according to any of Claims 25 to 28, wherein the determining and comparing steps are carried out at the mobile device.

30. A method according to any of Claims 25 to 29, wherein the determining step comprises using the current geographical location to look up in a map database of fixed NFC devices, the NFC devices and their respective types.

31. A method according to Claim 30, further comprising updating the map database of fixed NFC devices.

32. A method according to any of Claims 25 to 31 , wherein the activating step is carried out for a predetermined time period after which the NFC antenna is deactivated.