Apparatuses, methods and systems for ad-hoc applications based on advertisement

Abstract

The disclosure details the implementation of apparatuses, methods and systems for a Framework for Ad-hoc Applications Based on Advertising (FAABA). The FAABA may employ short-range radio-frequency communications. The disclosure teaches mechanisms for providing targeted advertising in connection with ad-hoc applications/point-to-point (P2P) communications between user terminals. In a manner, the invention teaches general collection components for user terminals, which is responsible for collecting and maintaining a dynamic set of advertisements as a background operation. This allows the user terminals to initiate applications that are based on P2P communication, and furthermore, allows collections of pre-loaded advertisements to be provided to the user terminals along and/or during the P2P communications. Also, the FAABA teaches that after advertisements are stored in the receiving device, the advertisements can be tailored more closely to the interests of the user of the device and the advertisements can be filtered based on current context of the user.

What is claimed is: 
     
         1 . A method, comprising:
 determining proximity of a first mobile client device and a second mobile client device,   wherein the first mobile client device is associated with a first user and the second mobile client device is associated with a second user;   establishing a communication connection between the first mobile client device and the second mobile client device;   receiving data on the first mobile client device from the second mobile client device through the communication connection; and   causing, at least in part, a displaying of the data on the first mobile client device.   
     
     
         2 . The method of  claim 1 , wherein the communication connection is a handshake protocol. 
     
     
         3 . The method of  claim 1 , further comprising:
 determining stored data on the first mobile client device associated with the first user is not the same as the data; and   requesting additional data from the second mobile client device, wherein the additional data is the data received from the second mobile client device that is not stored in the first mobile client device.   
     
     
         4 . The method of  claim 1 , further comprising:
 determining stored data on the first mobile client is not the same as the data;   presenting updating data from the first mobile client device, wherein the updating data is data stored on the first mobile client device that was not received from the second mobile client device; and   receiving acceptance of the updating data by the second mobile client device.   
     
     
         5 . The method of  claim 3 , wherein stored data includes currently stored data, logged data representing previously stored and/or viewed data, or a combination thereof. 
     
     
         6 . The method of  claim 1 , further comprising:
 causing, at least in part, storage of the data in a buffer on the first mobile client device; and   deleting previously stored buffer data based on a determination of whether space is needed to store the data in the buffer.   
     
     
         7 . The method of  claim 1 , wherein the data is is provided in one or more of an audio, graphical, multimedia, program, textual, and video format. 
     
     
         8 . An apparatus, comprising:
 at least one processor; and   at least one memory including computer program code, for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following:   determine proximity of a first mobile client device and a second mobile client device,   wherein the first mobile client device is associated with a first user and the second mobile client device is associated with a second user;   establish a communication connection between the first mobile client device and the second mobile client device;   receive data on the first mobile client device from the second mobile client device through the communication connection; and   cause, at least in part, a displaying of the data on the first mobile client device.   
     
     
         9 . The apparatus of  claim 8 , wherein the communication connection is a handshake protocol. 
     
     
         10 . The apparatus of  claim 8 , further comprising:
 determine stored data on the first mobile client device associated with the first user is not the same as the data; and   request additional data from the second mobile client device, wherein the additional data is the data received from the second mobile client device that is not stored in the first mobile client device.   
     
     
         11 . The apparatus of  claim 8 , further comprising:
 determine stored data on the first mobile client is not the same as the data;   present updating data from the first mobile client device, wherein the updating data is data stored on the first mobile client device that was not received from the second mobile client device; and   receive acceptance of the updating data by the second mobile client device.   
     
     
         12 . The apparatus of  claim 11 , wherein stored data includes currently stored data, logged data representing previously stored and/or viewed data, or a combination thereof. 
     
     
         13 . The apparatus of  claim 8 , further comprising:
 cause, at least in part, storage of the data in a buffer on the first mobile client device; and   delete previously stored buffer data based on a determination of whether space is needed to store the data in the buffer.   
     
     
         14 . The apparatus of  claim 8 , wherein the data is is provided in one or more of an audio, graphical, multimedia, program, textual, and video format. 
     
     
         15 . A non-transitory computer-readable storage medium caning one or more sequences of one or more instructions which, when executed by one or more processors, cause an apparatus to at least perform the following steps:
 determine proximity of a first mobile client device and a second mobile client device,   wherein the first mobile client device is associated with a first user and the second mobile client device is associated with a second user;   establish a communication connection between the first mobile client device and the second mobile client device;   receive data on the first mobile client device from the second mobile client device through the communication connection; and   cause, at least in part, a displaying of the data on the first mobile client device.   
     
     
         16 . The non-transitory computer-readable storage medium of  claim 15 , wherein the communication connection is a handshake protocol. 
     
     
         17 . The non-transitory computer-readable storage medium of  claim 15 , further comprising:
 determining stored data on the first mobile client device associated with the first user is not the same as the data; and   requesting additional data from the second mobile client device, wherein the additional data is the data received from the second mobile client device that is not stored in the first mobile client device.   
     
     
         18 . The non-transitory computer-readable storage medium of  claim 15 , further comprising:
 determining stored data on the first mobile client is not the same as the data;   presenting updating data from the first mobile client device, wherein the updating data is data stored on the first mobile client device that was not received from the second mobile client device; and   receiving acceptance of the updating data by the second mobile client device.   
     
     
         19 . The non-transitory computer-readable storage medium of  claim 18 , wherein stored data includes currently stored data, logged data representing previously stored and/or viewed data, or a combination thereof. 
     
     
         20 . The non-transitory computer-readable storage medium of  claim 15 , further comprising:
 causing, at least in part, storage of the data in a buffer on the first mobile client device; and   deleting previously stored buffer data based on a determination of whether space is needed to store the data in the buffer.