System for the secure distributed firmware and configuration update of unnetworked physical devices

Systems and methods are disclosed for the secure distribution of firmware and configuration updates to un-networked physical devices. A client component is provided for installation on a client device, which is configured to receive, via the client component, a status data packet including a status indication from a beacon, when the client is proximate to the beacon. A server receives the status data packet via the client component, determines whether an update is available for the beacon based at least in part on the status indication, and transmits, to the client device, an encrypted update data message relating to the update for installation at the beacon to complete the update of the beacon.

BACKGROUND OF THE DISCLOSURE

The merchandise offered by local and national retailers is always changing. The retailers may wish to display content to customers when the customers arrive to the store or are near specific merchandise. Presently it is difficult to detect where a customer is within a retail location. Additionally, when the retailer has a diverse number of products for sell and wishes to provide content to customers responsive to a number of different conditions, it is difficult for a retailer to easily and repeatedly associate specific content with specific merchandise.

Retailers may address this problem using beacons broadcasting a signal to support micro location detection. Large organizations may have thousands of locations with each location containing 100s of beacon devices. These devices are often not connected to any network and operate independently. The typical installation and maintenance process requires the direct one-to-one connection between the beacon device and a networked configuration device like a smartphone. This process requires a trust relationship between the phone and the device to safely configure or reconfigure the installed device(s). The process of visiting these 10s or 100s of thousands of devices becomes a major effort in time and money. The systems and methods of the present disclosure simplify and facilitate the process of updating beacons while also allowing a user to eliminate the trust relationship between the beacon and the networked configuration device.

BRIEF SUMMARY OF THE DISCLOSURE

Systems and methods are described herein for secure distributed update of un-networked physical devices. A client component for installation on a client device is provided wherein the client device is configured to receive, via the client component, a status data packet including a status indication from a beacon when the client is proximate to the beacon. The status data packet is received via the client component and at a server. It is determined by the server that an update is available for the beacon based at least in part on the status indication. An encrypted update data message relating to the update is transmitted by the server to the client device for installation at the beacon to complete the update of the beacon.

In one implementation, the encrypted update data message is transmitted by the client device to the beacon.

In one implementation, the encrypted update data packet is decrypted by the beacon to extract the update, validate the encrypted update data packet, and perform the update.

In one implementation, the status data packet is received by the client device from the beacon via a first wireless communication protocol. The status data packet is received by the server from the client device via a second wireless communication protocol without a direct network connection between the beacon and the server.

In one implementation, a nonce is included by the server in the encrypted update data packet.

In one implementation, the encrypted update data packet is validated by the beacon, and the validating comprises extracting the nonce and comparing the nonce to a previously received nonces.

In one implementation, an encrypted status message is transmitted by the beacon back to the server upon completed delivery.

In one implementation, a shared secret key that is known to the beacon and the server is used to perform the encryption.

In one implementation, determining, by the server, that an update is available for the beacon based at least in part on the status indication further comprises (1) retrieving, from a database, a desired status and (2) comparing the status indication to the desired status.

In one implementation, the client device includes any of a computer, a handheld device, and a point of sale (POS) register, and relays to the beacon the encrypted update data message without decrypting the encrypted update data message.

In one implementation, the encrypted update data message is transmitted to the client device without authenticating the client device.

In one implementation, the encrypted update data message is atomically packaged for transmission.

According to another aspect, the disclosure relates to a method for secure distributed updates of un-networked physical devices. A status data packet including a status indication from a beacon is received, via a client component installed at a client device, when the client is proximate to the beacon. The status data packet is transmitted via the client component to a server. An update indication that an update is available is obtained for the beacon based at least in part on the status indication. An encrypted update data message relating to the update for installation at the beacon to complete the update of the beacon is received from the server. The encrypted update data message is transmitted to the beacon.

In one implementation, obtaining the update indication includes searching a local database at the client device for previously downloaded update data.

In one implementation, obtaining the update indication includes receiving the update indication from the server, wherein the server determines that the update is available for the beacon based at least in part on the status indication.

In one implementation, the encrypted update data message is atomically packaged, and transmitted to the beacon from the client device without being decrypted at the client device.

In one implementation, the status data packet is received from the beacon via a first wireless communication protocol, and the status data packet is transmitted to the server from the client device via a second wireless communication protocol without a direct network connection between the beacon and the server.

In one implementation, the encrypted update data message is decrypted and installed at the beacon.

According to another aspect, the disclosure relates to a system for secure distributed update of un-networked physical devices, the system comprises a memory, a communication interface, and a processor. The memory stores a client component for installation on a client device and an encrypted update data message relating to an update for installation at a beacon. The communication interface is coupled to the memory and configured to: (1) provide the client component for installation on the client device, wherein the client device is configured to receive, via the client component, a status data packet including a status indication from a beacon when the client is proximate to the beacon, and (2) receive, from the client component, the status data packet, and (3) transmit the encrypted update data message relating to the update for installation at the beacon to complete the update of the beacon. The processor is coupled to the memory and configured to: (1) determine that the update is available for the beacon based at least in part on the status indication and (2) prepare the encrypted update data message.

According to another aspect, the disclosure relates to a processor-readable non-transitory storage medium storing processor-executable instructions for secure distributed update of un-networked physical devices, the processor-executable instructions being executed by a processor to (1) receive, via a client component installed at a client device, a status data packet including a status indication from a beacon when the client is proximate to the beacon, (2) transmit, via the client component and to a server, the status data packet, (3) obtain an update indication that an update is available for the beacon based at least in part on the status indication, (4) receive, from the server, an encrypted update data message relating to the update for installation at the beacon to complete the update of the beacon, and (5) transmit, to the beacon, the encrypted update data message.

DETAILED DESCRIPTION

A. Computing and Network Environment

Prior to discussing specific embodiments of the present solution, it may be helpful to describe aspects of the operating environment as well as associated system components (e.g., hardware elements) in connection with the methods and systems described herein. Referring toFIG. 1A, an embodiment of a network environment is depicted. In brief overview, the network environment includes one or more client devices102a-102n(also generally referred to as local machine(s)102, client(s)102, client node(s)102, client machine(s)102, client computer(s)102, client device(s)102, endpoint(s)102, or endpoint node(s)102) in communication with one or more servers106a-106n(also generally referred to as server(s)106, node106, or remote machine(s)106) via one or more networks104. In some embodiments, a client device102has the capacity to function as both a client node seeking access to resources provided by a server and as a server providing access to hosted resources for other client devices102a-102n.

AlthoughFIG. 1Ashows a network104between the client devices102and the servers106, the client devices102and the servers106may be on the same network104. In some embodiments, there are multiple networks104between the client devices102and the servers106. In one of these embodiments, a network104′ (not shown) may be a private network and a network104may be a public network. In another of these embodiments, a network104may be a private network and a network104′ a public network. In still another of these embodiments, networks104and104′ may both be private networks.

The network104may be connected via wired or wireless links. Wired links may include Digital Subscriber Line (DSL), coaxial cable lines, or optical fiber lines. The wireless links may include BLUETOOTH, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), an infrared channel or satellite band. The wireless links may also include any cellular network standards used to communicate among mobile devices, including standards that qualify as 1G, 2G, 3G, or 4G. The network standards may qualify as one or more generation of mobile telecommunication standards by fulfilling a specification or standards such as the specifications maintained by International Telecommunication Union. The 3G standards, for example, may correspond to the International Mobile Telecommunications-2000 (IMT-2000) specification, and the 4G standards may correspond to the International Mobile Telecommunications Advanced (IMT-Advanced) specification. Examples of cellular network standards include AMPS, GSM, GPRS, UMTS, LTE, LTE Advanced, Mobile WiMAX, and WiMAX-Advanced. Cellular network standards may use various channel access methods e.g. FDMA, TDMA, CDMA, or SDMA. In some embodiments, different types of data may be transmitted via different links and standards. In other embodiments, the same types of data may be transmitted via different links and standards.

The network104may be any type and/or form of network. The geographical scope of the network104may vary widely and the network104can be a body area network (BAN), a personal area network (PAN), a local-area network (LAN), e.g. Intranet, a metropolitan area network (MAN), a wide area network (WAN), or the Internet. The topology of the network104may be of any form and may include, e.g., any of the following: point-to-point, bus, star, ring, mesh, or tree. The network104may be an overlay network which is virtual and sits on top of one or more layers of other networks104′. The network104may be of any such network topology as known to those ordinarily skilled in the art capable of supporting the operations described herein. The network104may utilize different techniques and layers or stacks of protocols, including, e.g., the Ethernet protocol, the internet protocol suite (TCP/IP), the ATM (Asynchronous Transfer Mode) technique, the SONET (Synchronous Optical Networking) protocol, or the SDH (Synchronous Digital Hierarchy) protocol. The TCP/IP internet protocol suite may include application layer, transport layer, internet layer (including, e.g., IPv6), or the link layer. The network104may be a type of a broadcast network, a telecommunications network, a data communication network, or a computer network.

In some embodiments, the system may include multiple, logically-grouped servers106. In one of these embodiments, the logical group of servers may be referred to as a server farm38or a machine farm38. In another of these embodiments, the servers106may be geographically dispersed. In other embodiments, a machine farm38may be administered as a single entity. In still other embodiments, the machine farm38includes a plurality of machine farms38. The servers106within each machine farm38can be heterogeneous—one or more of the servers106or machines106can operate according to one type of operating system platform (e.g., WINDOWS NT, manufactured by Microsoft Corp. of Redmond, Wash.), while one or more of the other servers106can operate on according to another type of operating system platform (e.g., Unix, Linux, or Mac OS X).

In one embodiment, servers106in the machine farm38may be stored in high-density rack systems, along with associated storage systems, and located in an enterprise data center. In this embodiment, consolidating the servers106in this way may improve system manageability, data security, the physical security of the system, and system performance by locating servers106and high performance storage systems on localized high performance networks. Centralizing the servers106and storage systems and coupling them with advanced system management tools allows more efficient use of server resources.

The servers106of each machine farm38do not need to be physically proximate to another server106in the same machine farm38. Thus, the group of servers106logically grouped as a machine farm38may be interconnected using a wide-area network (WAN) connection or a metropolitan-area network (MAN) connection. For example, a machine farm38may include servers106physically located in different continents or different regions of a continent, country, state, city, campus, or room. Data transmission speeds between servers106in the machine farm38can be increased if the servers106are connected using a local-area network (LAN) connection or some form of direct connection. Additionally, a heterogeneous machine farm38may include one or more servers106operating according to a type of operating system, while one or more other servers106execute one or more types of hypervisors rather than operating systems. In these embodiments, hypervisors may be used to emulate virtual hardware, partition physical hardware, virtualize physical hardware, and execute virtual machines that provide access to computing environments, allowing multiple operating systems to run concurrently on a host computer. Native hypervisors may run directly on the host computer. Hypervisors may include VMware ESX/ESXi, manufactured by VMWare, Inc., of Palo Alto, Calif.; the Xen hypervisor, an open source product whose development is overseen by Citrix Systems, Inc.; the HYPER-V hypervisors provided by Microsoft or others. Hosted hypervisors may run within an operating system on a second software level. Examples of hosted hypervisors may include VMware Workstation and VIRTUALBOX.

Management of the machine farm38may be de-centralized. For example, one or more servers106may comprise components, subsystems and modules to support one or more management services for the machine farm38. In one of these embodiments, one or more servers106provide functionality for management of dynamic data, including techniques for handling failover, data replication, and increasing the robustness of the machine farm38. Each server106may communicate with a persistent store and, in some embodiments, with a dynamic store.

Server106may be a file server, application server, web server, proxy server, appliance, network appliance, gateway, gateway server, virtualization server, deployment server, SSL VPN server, or firewall. In one embodiment, the server106may be referred to as a remote machine or a node. In another embodiment, a plurality of nodes290may be in the path between any two communicating servers.

Referring toFIG. 1B, a cloud computing environment is depicted. A cloud computing environment may provide client device102with one or more resources provided by a network environment. The cloud computing environment may include one or more client devices102a-102n, in communication with the cloud108over one or more networks104. Client devices102may include, e.g., thick clients, thin clients, and zero clients. A thick client may provide at least some functionality even when disconnected from the cloud108or servers106. A thin client or a zero client may depend on the connection to the cloud108or server106to provide functionality. A zero client may depend on the cloud108or other networks104or servers106to retrieve operating system data for the client device. The cloud108may include back end platforms, e.g., servers106, storage, server farms or data centers.

The cloud108may be public, private, or hybrid. Public clouds may include public servers106that are maintained by third parties to the client devices102or the owners of the clients. The servers106may be located off-site in remote geographical locations as disclosed above or otherwise. Public clouds may be connected to the servers106over a public network. Private clouds may include private servers106that are physically maintained by client devices102or owners of clients. Private clouds may be connected to the servers106over a private network104. Hybrid clouds108may include both the private and public networks104and servers106.

Client devices102may access IaaS resources with one or more IaaS standards, including, e.g., Amazon Elastic Compute Cloud (EC2), Open Cloud Computing Interface (OCCI), Cloud Infrastructure Management Interface (CIMI), or OpenStack standards. Some IaaS standards may allow clients access to resources over HTTP, and may use Representational State Transfer (REST) protocol or Simple Object Access Protocol (SOAP). Client devices102may access PaaS resources with different PaaS interfaces. Some PaaS interfaces use HTTP packages, standard Java APIs, JavaMail API, Java Data Objects (JDO), Java Persistence API (JPA), Python APIs, web integration APIs for different programming languages including, e.g., Rack for Ruby, WSGI for Python, or PSGI for Perl, or other APIs that may be built on REST, HTTP, XML, or other protocols. Client devices102may access SaaS resources through the use of web-based user interfaces, provided by a web browser (e.g. GOOGLE CHROME, Microsoft INTERNET EXPLORER, or Mozilla Firefox provided by Mozilla Foundation of Mountain View, Calif.). Client devices102may also access SaaS resources through smartphone or tablet applications, including, e.g., Salesforce Sales Cloud, or Google Drive app. Client devices102may also access SaaS resources through the client operating system, including, e.g., Windows file system for DROPBOX.

The client device102and server106may be deployed as and/or executed on any type and form of computing device, e.g. a computer, network device or appliance capable of communicating on any type and form of network and performing the operations described herein.FIGS. 1C and 1Ddepict block diagrams of a computing device100useful for practicing an embodiment of the client device102or a server106. As shown inFIGS. 1C and 1D, each computing device100includes a central processing unit121, and a main memory unit122. As shown inFIG. 1C, a computing device100may include a storage device128, an installation device116, a network interface118, an I/O controller123, display devices124a-124n, a keyboard126and a pointing device127, e.g. a mouse. The storage device128may include, without limitation, an operating system, software, and a software of a Pinpoint System Server120. As shown inFIG. 1D, each computing device100may also include additional optional elements, e.g. a memory port103, a bridge170, one or more input/output devices130a-130n(generally referred to using reference numeral130), and a cache memory140in communication with the central processing unit121.

The central processing unit121is any logic circuitry that responds to and processes instructions fetched from the main memory unit122. In many embodiments, the central processing unit121is provided by a microprocessor unit, e.g.: those manufactured by Intel Corporation of Mountain View, Calif.; those manufactured by Motorola Corporation of Schaumburg, Ill.; the ARM processor and TEGRA system on a chip (SoC) manufactured by Nvidia of Santa Clara, Calif.; the POWER7 processor, those manufactured by International Business Machines of White Plains, N.Y.; or those manufactured by Advanced Micro Devices of Sunnyvale, Calif. The computing device100may be based on any of these processors, or any other processor capable of operating as described herein. The central processing unit121may utilize instruction level parallelism, thread level parallelism, different levels of cache, and multi-core processors. A multi-core processor may include two or more processing units on a single computing component. Examples of a multi-core processors include the AMD PHENOM IIX2, INTEL CORE i5 and INTEL CORE i7.

Main memory unit122may include one or more memory chips capable of storing data and allowing any storage location to be directly accessed by the microprocessor121. Main memory unit122may be volatile and faster than storage128memory. Main memory units122may be Dynamic random access memory (DRAM) or any variants, including static random access memory (SRAM), Burst SRAM or SynchBurst SRAM (BSRAM), Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended Data Output DRAM (BEDO DRAM), Single Data Rate Synchronous DRAM (SDR SDRAM), Double Data Rate SDRAM (DDR SDRAM), Direct Rambus DRAM (DRDRAM), or Extreme Data Rate DRAM (XDR DRAM). In some embodiments, the main memory122or the storage128may be non-volatile; e.g., non-volatile read access memory (NVRAM), flash memory non-volatile static RAM (nvSRAM), Ferroelectric RAM (FeRAM), Magnetoresistive RAM (MRAM), Phase-change memory (PRAM), conductive-bridging RAM (CBRAIVI), Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), Resistive RAM (RRAM), Racetrack, Nano-RAM (NRAM), or Millipede memory. The main memory122may be based on any of the above described memory chips, or any other available memory chips capable of operating as described herein. In the embodiment shown inFIG. 1C, the processor121communicates with main memory122via a system bus150(described in more detail below).FIG. 1Ddepicts an embodiment of a computing device100in which the processor communicates directly with main memory122via a memory port103. For example, inFIG. 1Dthe main memory122may be DRDRAM.

Devices130a-130nmay include a combination of multiple input or output devices, including, e.g., Microsoft KINECT, Nintendo Wiimote for the WII, Nintendo WII U GAMEPAD, or Apple IPHONE. Some devices130a-130nallow gesture recognition inputs through combining some of the inputs and outputs. Some devices130a-130nprovides for facial recognition which may be utilized as an input for different purposes including authentication and other commands. Some devices130a-130nprovides for voice recognition and inputs, including, e.g., Microsoft KINECT, SIRI for IPHONE by Apple, Google Now or Google Voice Search.

Additional devices130a-130nhave both input and output capabilities, including, e.g., haptic feedback devices, touchscreen displays, or multi-touch displays. Touchscreen, multi-touch displays, touchpads, touch mice, or other touch sensing devices may use different technologies to sense touch, including, e.g., capacitive, surface capacitive, projected capacitive touch (PCT), in-cell capacitive, resistive, infrared, waveguide, dispersive signal touch (DST), in-cell optical, surface acoustic wave (SAW), bending wave touch (BWT), or force-based sensing technologies. Some multi-touch devices may allow two or more contact points with the surface, allowing advanced functionality including, e.g., pinch, spread, rotate, scroll, or other gestures. Some touchscreen devices, including, e.g., Microsoft PIXELSENSE or Multi-Touch Collaboration Wall, may have larger surfaces, such as on a table-top or on a wall, and may also interact with other electronic devices. Some I/O devices130a-130n, display devices124a-124nor group of devices may be augment reality devices. The I/O devices may be controlled by an I/O controller123as shown inFIG. 1C. The I/O controller may control one or more I/O devices, such as, e.g., a keyboard126and a pointing device127, e.g., a mouse or optical pen. Furthermore, an I/O device may also provide storage and/or an installation medium116for the computing device100. In still other embodiments, the computing device100may provide USB connections (not shown) to receive handheld USB storage devices. In further embodiments, an I/O device130may be a bridge between the system bus150and an external communication bus, e.g. a USB bus, a SCSI bus, a FireWire bus, an Ethernet bus, a Gigabit Ethernet bus, a Fibre Channel bus, or a Thunderbolt bus.

In some embodiments, display devices124a-124nmay be connected to I/O controller123. Display devices may include, e.g., liquid crystal displays (LCD), thin film transistor LCD (TFT-LCD), blue phase LCD, electronic papers (e-ink) displays, flexile displays, light emitting diode displays (LED), digital light processing (DLP) displays, liquid crystal on silicon (LCOS) displays, organic light-emitting diode (OLED) displays, active-matrix organic light-emitting diode (AMOLED) displays, liquid crystal laser displays, time-multiplexed optical shutter (TMOS) displays, or 3D displays. Examples of 3D displays may use, e.g. stereoscopy, polarization filters, active shutters, or autostereoscopy. Display devices124a-124nmay also be a head-mounted display (HMD). In some embodiments, display devices124a-124nor the corresponding I/O controllers123may be controlled through or have hardware support for OPENGL or DIRECTX API or other graphics libraries.

In some embodiments, the computing device100may include or connect to multiple display devices124a-124n, which each may be of the same or different type and/or form. As such, any of the I/O devices130a-130nand/or the I/O controller123may include any type and/or form of suitable hardware, software, or combination of hardware and software to support, enable or provide for the connection and use of multiple display devices124a-124nby the computing device100. For example, the computing device100may include any type and/or form of video adapter, video card, driver, and/or library to interface, communicate, connect or otherwise use the display devices124a-124n. In one embodiment, a video adapter may include multiple connectors to interface to multiple display devices124a-124n. In other embodiments, the computing device100may include multiple video adapters, with each video adapter connected to one or more of the display devices124a-124n. In some embodiments, any portion of the operating system of the computing device100may be configured for using multiple displays124a-124n. In other embodiments, one or more of the display devices124a-124nmay be provided by one or more other computing devices100aor100bconnected to the computing device100, via the network104. In some embodiments software may be designed and constructed to use another computer's display device as a second display device124afor the computing device100. For example, in one embodiment, an Apple iPad may connect to a computing device100and use the display of the device100as an additional display screen that may be used as an extended desktop. One ordinarily skilled in the art will recognize and appreciate the various ways and embodiments that a computing device100may be configured to have multiple display devices124a-124n.

Referring again toFIG. 1C, the computing device100may comprise a storage device128(e.g. one or more hard disk drives or redundant arrays of independent disks) for storing an operating system or other related software, and for storing application software programs such as any program related to the Pinpoint System Server120. Examples of storage device128include, e.g., hard disk drive (HDD); optical drive including CD drive, DVD drive, or BLU-RAY drive; solid-state drive (SSD); USB flash drive; or any other device suitable for storing data. Some storage devices may include multiple volatile and non-volatile memories, including, e.g., solid state hybrid drives that combine hard disks with solid state cache. Some storage device128may be non-volatile, mutable, or read-only. Some storage device128may be internal and connect to the computing device100via a bus150. Some storage device128may be external and connect to the computing device100via a I/O device130that provides an external bus. Some storage device128may connect to the computing device100via the network interface118over a network104, including, e.g., the Remote Disk for MACBOOK AIR by Apple. Some client devices100may not require a non-volatile storage device128and may be thin clients or zero client devices102. Some storage device128may also be used as an installation device116, and may be suitable for installing software and programs. Additionally, the operating system and the software can be run from a bootable medium, for example, a bootable CD, e.g. KNOPPIX, a bootable CD for GNU/Linux that is available as a GNU/Linux distribution from knoppix.net.

Client device100may also install software or application from an application distribution platform. Examples of application distribution platforms include the App Store for iOS provided by Apple, Inc., the Mac App Store provided by Apple, Inc., GOOGLE PLAY for Android OS provided by Google Inc., Chrome Webstore for CHROME OS provided by Google Inc., and Amazon Appstore for Android OS and KINDLE FIRE provided by Amazon.com, Inc. An application distribution platform may facilitate installation of software on a client device102. An application distribution platform may include a repository of applications on a server106or a cloud108, which the client devices102a-102nmay access over a network104. An application distribution platform may include application developed and provided by various developers. A user of a client device102may select, purchase and/or download an application via the application distribution platform.

The computer system100can be any workstation, telephone, desktop computer, laptop or notebook computer, netbook, ULTRABOOK, tablet, server, handheld computer, mobile telephone, smartphone or other portable telecommunications device, media playing device, a gaming system, mobile computing device, or any other type and/or form of computing, telecommunications or media device that is capable of communication. The computer system100has sufficient processor power and memory capacity to perform the operations described herein. In some embodiments, the computing device100may have different processors, operating systems, and input devices consistent with the device. The Samsung GALAXY smartphones, e.g., operate under the control of Android operating system developed by Google, Inc. GALAXY smartphones receive input via a touch interface.

In some embodiments, the computing device100is a gaming system. For example, the computer system100may comprise a PLAYSTATION 3, or PERSONAL PLAYSTATION PORTABLE (PSP), or a PLAYSTATION VITA device manufactured by the Sony Corporation of Tokyo, Japan, a NINTENDO DS, NINTENDO 3DS, NINTENDO WII, or a NINTENDO WII U device manufactured by Nintendo Co., Ltd., of Kyoto, Japan, an XBOX 360 device manufactured by the Microsoft Corporation of Redmond, Wash.

In some embodiments, the computing device100is a tablet e.g. the IPAD line of devices by Apple; GALAXY TAB family of devices by Samsung; or KINDLE FIRE, by Amazon.com, Inc. of Seattle, Wash. In other embodiments, the computing device100is a eBook reader, e.g. the KINDLE family of devices by Amazon.com, or NOOK family of devices by Barnes & Noble, Inc. of New York City, N.Y.

In some embodiments, the communications device102includes a combination of devices, e.g. a smartphone combined with a digital audio player or portable media player. For example, one of these embodiments is a smartphone, e.g. the IPHONE family of smartphones manufactured by Apple, Inc.; a Samsung GALAXY family of smartphones manufactured by Samsung, Inc; or a Motorola DROID family of smartphones. In yet another embodiment, the communications device102is a laptop or desktop computer equipped with a web browser and a microphone and speaker system, e.g. a telephony headset. In these embodiments, the communications devices102are web-enabled and can receive and initiate phone calls. In some embodiments, a laptop or desktop computer is also equipped with a webcam or other video capture device that enables video chat and video call.

B. System for Determining Location and Delivering Content

The present disclosure is directed towards systems and methods for providing supplemental content to a user based on the user's location and preferences. In some implementations, the system and methods described herein are implemented with the computer and network environment ofFIGS. 1A-1D. As described herein, a user's location can include the user's micro-location within the premises of a store, building, or outdoor location. For example, the system may narrow the location of a client device to a specific section within a store.

While the system and methods have been particularly shown and described with reference to specific implementations, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the system and methods described in this disclosure.

FIG. 2Ais a schematic representation of a Pinpoint Network (PN)200for delivering content responsive to a client's location. As a brief overview, the PN200includes a Pinpoint System Server (PSS)120. The PSS120may include a plurality of components and modules. These modules may include an anti-spoofing module261, a logistics module262, user interface module263, and an analysis module264. Additionally, the PSS120includes at least one database. The databases may include a beacon location database265, a content database266, a user preference database267, and a content provider database268.

The PN200can also include a plurality of client devices102each in use by a user230. The client devices102may include a camera221, a GPS module222, and a wireless module223. The PN200also includes at least one beacon240. The beacon240includes a wireless module241for communicating with the client device102(or PSS120), an anti-spoofing module242, and a battery243. Additionally, the PN200includes at least one content provider250that provides supplemental content251to the PSS120. The PSS120delivers supplemental content251to the plurality of client devices102. The above described components of the PN200are connected by a network104.

In some implementations, the content provider250a merchant that sells merchandise (or more generically referred to as content) to customers or users. In some implementations, the supplemental content251is associated with the content for sell by the content provider250. For example, the content provider250may be a clothing store selling content such as women's and men's fashions. In this example, the supplemental content251may include information or other digital content related to the fashions for sell by the clothing store. The content provider250may place a beacon240near specific content in the content provider's store. For example, the content provider250may place a first beacon240near a display of sweaters and a second beacon240near a rack of women's jeans. In other implementations, the beacon240may be also placed near a non-content item, such as a door, cash register, or be positioned such that the beacon240is near a plurality of content items. The PSS120may deliver supplemental content251to a client device102when the PSS120determines the client device102is within a predetermined proximity of a beacon240.

The beacon240includes a wireless module241, an anti-spoofing module242, and a battery243. The wireless module241may be a WIFI radio, a Bluetooth radio, RFID tag and/or similar wireless transmitter or receiver. In some implementations, the wireless module241is only a wireless transmitter. For example, the beacon240may broadcast a signal that is detected by the client device102, but may not receive a signal from the client device102. The wireless module241may be a low power wireless module such as a Bluetooth 4.0 (i.e., low energy) radio. Additionally, or alternatively, the wireless module241may cycle on and off to conserve energy. In some implementations, the cycling may occur based on time of day or the detection of a nearby user. The beacon240may be configured to only broadcast a wireless signal during business hours. In some implementations, the wireless module241emits a wireless signal that covers a predetermined proximity zone. As described in greater detail below, the beacon240may broadcast a unique beacon identification number over the wireless signal, which is detected by the client device102. In some implementations, the size and shape of the proximity zone may be adjusted. For example, the size of the proximity zone may be adjusted by altering the power level of the wireless signal. For example, the power level of the wireless signal may be set to one of 4 dB, 0 dB, −6 dB, or −23 dB.

In some implementations, the beacon identification number is a unique identifier number that may not be detected if one is outside the defined proximity zone. In some implementations, a plurality of beacons240may be daisy chained together such that they create a unified proximity zone. For example, a content provider250may wish to have a single proximity zone cover an entire store rather than having micro proximity zones distributed throughout the store. In this example, each of the daisy changed Beacons240broadcast the same Beacon identification number.

Only able to detect the beacon identification number within the proximity zone allows the PSS120to determine a location of the client device102. For example, and as described in greater detail below, if the client is detecting the beacon identification number39475423, then the client must be within the proximity zone of the beacon240having the identification number of 39475423. Accordingly, the PSS120may associate the location of the beacon240with the client device102.

In some implementations, the wireless module241allows the beacon240to communicate directly with the PSS120via the network104. In other implementations, as in the implementation ofFIG. 2A, the beacon240does not communicate directly with the PSS120, but rather passes data to the client device102, which then forwards the data to the PSS120. The method of forwarding data from the Beacon240to the PSS120, via a client device102, is discussed in greater detail in relation toFIGS. 2B-3B.

In some implementations, the data transmitted from a beacon240to the client device102or PSS120is encrypted, for example, with 16 byte AES encryption. The data may include an AES key identifier, a beacon ID, a MAC address, the current battery level, beacon uptime, data, random data, or any combination thereof. The beacon ID may be randomly generated, and in some implementations, updated at specific intervals. For example, the beacon ID may be generated using a function (e.g., a hash function), which generates a new beacon ID at periodic intervals. The PSS120may have the same hash function and may update its record of the beacon IDs as the beacons240updates their beacon IDs. In some implementations, updating the beacon ID is done to prevent spoofing of the beacon240and its data. An example method of encrypting the communication within the PN200is described in greater detail in relation toFIG. 3C.

As described above, the beacon240can include an anti-spoofing module242. The anti-spoofing module242may ensure the data transmitted from the beacon240to the PSS120is authentic. As discussed below, in some implementations, the PSS120may provide a user230with supplemental content when the user's client device102is within a predetermined proximity zone of a beacon240. The supplemental content may be a coupon, loyalty points, or other benefit. Accordingly, a content provider250may desire to ensure the client device102is actually located in the expected location before providing supplemental content to the client device102. The anti-spoofing module242may use the AES key identifier, location ID, battery level, beacon up time, or a combination thereof to ensure the authenticity of transmitted data. For example, the data packets transmitted to the PSS120may be encrypted and include the current battery level and up time of the beacon240generating the data packets.

The anti-spoofing module242may check that the battery level and up time indicated in the data packets correspond to expected values. For example, if the anti-spoofing module242receives a data packet that indicates the up time of a Beacon240should be 1 day, 3 hours and 15 minutes, but receives a data packet that indicates the up time is four days, the anti-spoofing module may determine that someone copied the data packets and is attempting to rebroadcast them without revisiting the store. In some implementations, the anti-spoofing module242may use a GPS radio or other location service to determine if the data packets are arriving from a location generally associated with the beacon240. In yet other implementations, the anti-spoofing module242may provide the client device102with a password or other unique identification number such that the client device102may verify to the PSS120that the client device102is near the beacon240. The password may be a rolling password. In some implementations, if spoofing is detected the content provider250housing the beacon and/or the PSS120may be notified. A beacon240that is the tampered with or spoofed may be remotely disabled.

InFIG. 2A, the user230interacts with a client device102. As described above in greater detail in relation toFIG. 1, the client may be, but is not limited to, a smart phone, a tablet computer, a laptop and/or a desktop computer. In some implementations, the client device102includes a GPS module222. The GPS module222detects the current location of the client device102and may transmit the detected location to the PSS120via the network104. The anti-spoofing module in the beacon and/or in the PSS120, modules242and261respectively, may receive the detected location and verify the client device102is near the reported location of the beacon. For example, the client device102may transmit the current location of the client device102to the anti-spoofing module261of the PSS120. The PSS120may receive a unique beacon identification number. Referencing the beacon location database265, the unique beacon identification number transmitted to the PSS120may indicate the beacon should be located in a particular store of a shopping mall. The current location determined by the GPS module222may indicate that the client device102is in the corresponding shopping mall, and accordingly the client device102may be authenticated as being near the beacon240.

The client device102may include a camera221. The user230may use the camera to capture images of merchandise or other content the user prefers. For example, if a user230finds a jacket that the user230may want to purchase at a later date, the user230may use the camera221to capture an image of the jacket. In some implementations, the captured image may remain on the client device102, and in other implementations they are transmitted to the PSS120to be stored in the user preference database267.

User preferences may include, but are not limited to, preferred content providers, preferred content, preferred colors, preferred price points, locations, preferred looks, preferred fashion styles, preferred users, or any combination thereof. For example, using the user interface discussed below, the user230may select a jacket the user likes. The jacket may then be saved to the user's preferences. In some implementations, the user230may view or change the stored user preferences via the PSS120. Responsive to those preferences, the PSS120may deliver supplemental content to the user. For example, after a user has stored a number of preferences the PSS120may send the user230a recommendation for pants that match the jacket the user230is viewing. The pants may be in a color and a price point the user230indicated that she liked in her saved preferences.

The client device102may also include a wireless module223. In some implementations, the wireless module223may detect the broadcast from the Beacon240. As described above, the broadcast may include the unique beacon identification number and other data. The other data may include a password, location data, system status data, system statistics, or any combination thereof. For example, the beacon240may include current battery levels in the data broadcast. In some implementations, the data packet in the broadcast may be only a few bits in size. Using the wireless module223the client device102may transmit the data packet to the PSS120on behalf of the beacon240. In some implementations, the client device102forwards the data to the PSS120without reading (or decrypting) the data within the data packets.

Still referring toFIG. 2A, and in more detail, the PSS120includes a plurality of modules and databases. In some implementations, the PSS120is a computer program running on a central server. In other implementations, the PSS120is a distributed system running on a plurality of computer servers. For example, the PSS120may be replicated across a plurality of servers or specific functions of the PSS120may be executed on specific computer servers.

The PSS120may include an anti-spoofing module261. Discussed in greater detail with the anti-spoofing module242of the beacon240, the anti-spoofing module261ensures the authenticity of the data received from the client device102and/or Beacons240. For example, the PSS120may receive data from the client device that includes the up time of a beacon240. The anti-spoofing module261may compare the up time with an expected up time to ensure the data is authentic. For example, if the up time is only 470 hours when it should be 1,213 hours, the anti-spoofing module may determine that the data was recorded and a third party is attempting to spoof the data to receive supplemental content such as reward points from the PSS120.

The logistics module262of the PSS120may provide the content provider250with logistical data. For example, the logistics module262may monitor the number of client devices102that detect a specific beacon identification number over a given period of time and determine the content (or merchandise) near those beacons is more popular than the content near beacons240whose beacon identification numbers are not detected as often over the same given time period. The logistics module262may also monitor customer flow patterns through the content providers. The content providers250may make decisions on where to place content based on the data returned from the logistics module262. For example, a content provider250may place popular content near the back of the store such that a user will have to pass less popular content to get to the more popular content.

The PSS120also includes an interface263. The interface263is discussed in greater detail in relation to the exemplary embodiments described in Section C. Briefly, the interface263provides a means for a user230and/or content provider250to interact with the PSS120. In some implementations, the interface263is a plurality of web pages. In other implementations, the interface263is a computer program running on the PSS120and/or on a client device102. There may be multiple versions of the user interface263. For example, there may be one user interface for content providers250and another user interface for users230. In certain implementations, the user interface263that is displayed to the user230may be responsive to the type of client device102used to view the user interface263. For example, the user interface may appear different when a user views the interface263on a smart phone as compared to if the user views the interface263on a personal computer.

The first type of interface263, a content provider interface, (also referred to as a console) may be the interface presented to a content provider250upon logging into the PSS120. The content provider interface may allow a content provider250to upload, to the content database266, descriptions and details of supplemental content251, images of content215, availability of content215, or any combination thereof. Additionally, the content provider250may upload coupons and/or benefits to the content database266via the content provider interface. For example, the content provider250may upload a benefit to the content database266that indicates the content provider will be having a sale on Memorial Day. Accordingly, users viewing the user interface may be presented with the details of the Memorial Day sale. The console for a content provider250is described below in relation to Section G.

In other implementations, the PSS120may provide, through the user interface263, a platform for the user230to barter or haggle over the price of a piece of supplemental content251with the content provider. In these implementations, the content provider250may use the content provider interface to define minimum acceptable prices for supplemental content251in the content database266or to define other rules that may govern the bartering and haggling process.

In another implementation, the content provider interfaces may allow for the control, configuration, and management of beacons240. Beacon management functions of the content provider interface may include such functions as updating firmware; configuring the hours of operation for the beacon; setting a logical radius; updating the PSS120as to the physical location of the beacon; and checking beacon settings, statistics, and current status (e.g., battery life). The console for PSS120administration is described further in relation to Section G.

In some implementations, the content provider interface is displayed via a computer program or webpage that interacts directly with the PSS120, which in turn transmits the above described configurations and settings to the beacon240. In other implementations, the content provider interface is displayed by a program or webpage executing on a mobile device. The mobile device may then allow for the direct configuration of the beacon240. For example, the mobile device may connect directly to the beacon240by Bluetooth to deliver new configuration files, firmware updates, and/or settings to the beacon240.

The second type of interface263, the user interface, may be provided to the user230when interacting with the PSS120. The exemplary embodiments discussed in Section F provide a detailed description of the user interface. Briefly, the user interface, may allow the user to view the supplemental content251available by the plurality of content providers250. For example, the user interface may allow the user230to view or search for black high-heels available for sale by one or more stores using the PSS120. Other searches performed by the use230aim include searching for content within a specific location, distance from a specific location, price range, color, size, or any combination thereof.

In some implementations, the user230may input preferences to the PSS120via the user interface. These preferences may be saved into the user preference database267. The preferences may be directly input into PSS120(e.g., the user may indicate they prefer Nike tennis shoes) or the PSS120may infer the user's preferences. In inferring the user's preferences, the user may “like” (or select) a plurality of content items. The PSS120may then determine similarities between the selected content to determine the user's preferences. In some implementations, selecting a preferred content item may include selecting the image of the content item as it is displayed to the user230via the user interface263. In yet other implementations, the user230may upload images captured with the camera221to user preference database267. In yet other implementations, a first user230may use selected content of a second user230to augment the preferences of the first user230.

The PSS120also includes an analysis module264. In some implementations, responsive to the preferences of the user230stored in the user preference database267, the analysis module264provides the user230with supplemental content251the user230may like. The supplemental content251provided to the user230may include coupons, benefits, links to other content or any combination thereof. In some implementations, the selection of the supplemental content251is responsive to the location of the client device102. For example, when a user230enters the proximity zone of a beacon240and the PSS120determines the client device102is at a specific location, the analysis module264may then analyze the user preferences stored in the user preference database267and provide supplemental content251for the user230responsive to the user's preferences and the current location of the user. For example, the analysis module264may determine a user is viewing sweaters within a specific store. Analyzing that a high percentage of the captures images of clothes the user uploaded to the PSS120include green articles of clothing, the analysis module264may suggest to the user230to view the content provider's selection of green sweaters, located at the front of the store. In another example, the supplemental content selected by the analysis module264may be responsive to only the user's current location. In some implementations, selected supplemental content251is associated with a competitor of content item near the user. For example, when viewing a pair of pants in a first store, the analysis module264may send the user a coupon for a pair of similar pants at a second store.

As described herein, the supplemental content251selected by the analysis module264can include coupons, ads, product information or any combination thereof. In certain implementations, the supplemental content251is time sensitive. For example, a coupon may be issued by the analysis module264and only be valid for the next 10 minutes. In some implementations, the analysis module264issues a time sensitive coupons when it has determined the user230may be uncertain if they wish to purchase the content item near the user. For example, the analysis module264may determine that the user230has lingered in the vicinity of the content item for a set period of time (e.g. five minutes), and determined the user230is unsure of the purchase. The analysis module264may provide the user230with a coupon in order to persuade the user230to purchase the content item.

In yet other implementations, the analysis module264may incorporate the data of the content database266and the content provider database268to provide the client device102with supplemental content that is information about content provided by a competing content provider250. For example, the analysis module264may determine that a client device102is in a store viewing shirts. Incorporating the data of the content provider database268and the content database the analysis module264may provide the user with supplemental content251that provides the user with additional information about the shirt near the user. The information may include availability, sizing information, information about similar content items, or general information about the product.

In some implementations, the analysis module264provides the user230with information when the client device102is not in the proximity zone of a beacon240. For example, the analysis module264may determine that the user230has uploaded a number of jackets and determines the user may be actively looking for a new winter coat. The analysis module may search the content database266and the content provider database268to determine if any content providers250in the general area currently have sales on jackets. In yet other implementations, the content providers may place bids on the opportunity to provide the user230with a coupon or supplemental content. Ad auctions are described further in relation to Section H.

C. Communication with the Beacon and Determining Micro Location

In some implementations, the beacons240can be placed in a location without providing the beacons240with a power connector or a connection to the network104. For example, and as described above, the beacons240can include a battery243that is configured to power the beacons240for a least 1 month, 3 months, 6 months, or a year without needing to be replaced or recharged. In some implementations, the beacons240do not have a direct connection to the network104. As described further below, in these implementations, the beacons240can communicate with the PSS120through the data connection of a client device102. This can allow a content provider store owner to place a beacon240without first setting up a network104within the store or running power to the location where the store owner wishes to place the beacon240.

FIG. 2Bis an illustration that provides further detail about the interconnectivity between some of the components of the PN200. In brief,FIG. 2Billustrates a plurality of client devices102, each at different distances from a beacons240. As described above the client devices102are connected to the PSS120via a network104. A logical radius271extends a first distance from the beacons240and a physical radius272extends a second distance from the beacons240.

As described above, the beacons240transmits a wireless signal, such as a Bluetooth signal. The greatest distance the wireless signal may be received by a client device102is the physical radius272of the beacon240. In some implementations, a logical radius271may also be set for the beacon240. The logical radius271may be any radius within the physical radius272. In some implementations, more than one logical radius271may be set for each beacon240. In some implementations, crossing a logical radius271may cause an event, such as the delivery of supplemental content, to occur. Client devices102in different sections of the beacon's broadcast range may be treated differently. For example, different content may be delivered to client devices102within the logical radius271as compared to client devices102outside the logical radius271but within the physical radius272. In some implementations, the logical radius271may be set via the PSS120. Although the beacon240is represented as broadcasting a wireless signal in an omnidirectional manner, one of average skill in the art will recognize that the wireless signal may be tuned such that the wireless signal is not omnidirectional.

FIG. 2Billustrates client devices at three distances from a beacon240. As illustrated, client device102(1) is within the inner proximity zone270. Client devices102(2) are beyond the logical radius271but within the physical radius272, and therefore within a second proximity zone280. Client device102(3) is outside the physical radius272, and therefore not within one of the proximity zones. In some implementations, the PSS120may not deliver content to a client device102unless the device is within a logical radius271. In some implementations, the PSS120may determine that a client device102is leaving the proximity of the beacon240when the client device102progresses from the inner proximity zone270to an outer zone280In some implementations, the PSS120may deliver different supplemental content to the client device102responsive to if the client device102is entering or leaving the inner proximity zone270.

As described above, in some implementations, the beacon240does not communicate directly with the PSS120. The beacon may communicate with the PSS120via at least one client device102. In some implementations, the beacons240and a client device102may communicate with one another using a first wireless standard and then the client device102and the PSS120may communicate with a second communication standard. For example, the beacon240may transmit a packet containing data, which is received by the client device102(1), using the low power Bluetooth standard. The client device102(1) may then forward the data packet to the PSS120using a second communication standard. For example, the client device102(1) may use its cellular connection or a Wi-Fi connection to forward the data packet to the PSS120. In some implementations, the device102retransmits the data packet to the PSS120without accessing, reading, and/or modifying the data packet. In some implementations, the device102may append a device identifier, such as a MAC address to the data packet.

The data packet can include information related to the beacon identification number or other data pertaining to the beacon240. For example, the beacon240may relay information about its current power levels or conditions to the PSS120via the data packets. In some implementations, the beacon240transmits the data packet to a plurality of client devices102for forwarding to the PSS120.

In some implementations, the PSS120may transmit data back to the beacon240through the client device102. For example, the PSS120may select a client device102within the physical radius272(or logical radius271) of the beacon240. The PSS120may then send a data packet to the client device102using the second transmission protocol. The client device102may then forward the data packet to the beacon240using first data transmission standard. The PSS120may transmit the data packet to a plurality of client devices102within the physical radius272. The redundancy of the data transmission to the beacon240may ensure the data still arrives to the beacon240even if the first client device102leaves the physical radius272before the data is fully transferred to the beacon240. For example, if client device102(1) and client device102(2) both receive the data packet from the PSS120, if client device102(2) leaves the physical radius272before the data packet can be forwarded to the beacon240, client device102(1) can still forward the data packet to the beacon240. In some implementations, the data that the PSS120transmits to a beacon240can include configuration files or firmware updates.

FIG. 3Ais a flow chart of an example method300for determining the location of a client device102and providing to the client device102with supplement content. The method300includes receiving, by the client, a beacon identification number (step301). The client then transmits the beacon identification number (step302) to the PSS120. Responsive to transmitting the beacon identification number, the client receives supplemental content (step303) from the PSS120. Responsive to receiving the supplemental content, the supplemental content is displayed on the client (step304).

As set forth above, at step301, the client device102receives a beacon identification number. In some implementations, the beacon identification number is received by the wireless module223of the client device102. In other implementations, the client102may receive the beacon identification number by taking a picture of a QR code placed on or the beacon240or through some other non-wireless transmission means. For example, the user may manually enter the beacon identification number into a computer programming running on the client device102. As discussed in relation toFIG. 2A, the beacon identification number may be accompanied by a data packet that may include beacon statistics or other data.

At step302, the client device102transmits the beacon identification number to the PSS120. In some implementations, the client device102is Internet enabled and transmits the beacon identification number to the PSS120. The client device102may add a client and/or user identification to the beacon identification number when forwarding data to the PSS120from the beacon240. Transmitting the beacon identification number may also include transmitting additional client device102or user230information to the PSS120. For example, when a beacon identification number is transmitted, the client may also transmit shopping preferences the user recently entered into a computer program executing on the client device102. In other implementations, the beacon240is Internet enabled, and transmits client identification to the PSS120directly responsive to detecting a client device102in the proximity zone.

At step303, in some implementations, the client device102receives supplemental content. The supplemental content may be delivered to the client device102from the PSS120. As discussed above, the supplemental content may be a coupon, offer, or other information. For example, the supplemental content may be a coupon for the supplemental content251near the beacon240, an offer for a competitor of the content provider250currently providing the content which the client device102is near, or the supplemental content may be information indicating to the user additional supplemental content251that may complement the currently viewed supplemental content251.

At step304, the supplemental content is displayed to the user. In some implementations, the supplemental content is displayed to the user230via a computer program executing on the client device102. The user230may only receive the supplemental content if the user230is actively using the computer program. In other implementations, the supplemental content may be pushed to the client device102and displayed to the user regardless if the user230is actively using the computer program. In yet other implementations, the user may only receive the supplemental content if the user is using the computer program and specifically requests the supplemental content to be delivered. For example, a user230may be viewing a sweater located near a beacon240. The user230may wish to see if the store is selling any pants that would match the sweater. The user230may then activate the computer programming running on the client device102and request the PSS120to provide the user230with a plurality of matching pants in the current and/or competing stores. In some implementations, the plurality of matching pants, or other supplemental content, is ranked based on the user's preferences stored in the user preference database267.

FIG. 3Bis a flow chart of a method350for determining the location of a client device. The PSS120receives a data packet (step351). The PSS120determines which beacon240generated the data packet (step352). The PSS120then determines the location of the of the beacon240that generated the data packet (step352). The PSS120then associates the location of the beacon240that generated the data packet with the client device102.

As set forth above, the method350begins when the PSS120receives a data packet. In some implementations, the data packet is generated by a beacon240that is one of a plurality of beacons240. The data packet can be transmitted from the beacon240to the client device102using a first wireless standard, and then the client device102forwards the data packet to the PSS120using a second wireless standard. In some implementations, the client device102may append a client device identifier to the data packet when the client device102forwards the data packet to the PSS120.

At step352, the PSS120determines which one of the plurality of beacons240generated the data packet. In some implementations, the data packet received by the PSS120includes a beacon identifier. The PSS120can use the beacon identifier to determine which one of the beacons240generated the data packet. In some implementations, the client device102that forwards the data packet to the PSS120may be within the physical radius272of a plurality of beacons240. In these implementations, the client device102may receive a data packet from each of the plurality of beacons240. The client device102or PSS120may determine with which of the plurality of beacons240has the strongest wireless connection. The client device102may forward only the data packet from the beacon240with which it has the strongest data connection to the PSS120. In some implementations, the client device102may rank the strength of the connections to each of the plurality of beacons240and then forward an indication of the ranking to the PSS120. The PSS120may use the indication of the ranking to better determine the position of the client device102.

At step353, the PSS120determines the location of the beacon240that generated the data packet. As described above, the location of each of the beacons240can be saved into the beacon location database265. The PSS120can access the beacon location database265and search the beacon location database265to retrieve the location of the beacon240that generated the data packet.

At step354, the PSS120associates the location of the beacon240with the client device102. For example, determining that the client device102forwarded a data packet from a beacon240that is located within the men's section of a store, the PSS120may determine the client device102is also within the men's section of the store. As described, above in relation to step352, in some implementations, the client device102may receive and forward a plurality of data packets from a plurality of beacons240. The PSS120may use the ranked list of connection strength to each of the beacons240to triangulate a more specific location of the client device102. In some implementations, when only data packets form a single beacon240are forwarded to the PSS120, the PSS120may determine how far the client device102is from the beacon240response to the signal strength of the connection the client device102establishes with the beacon240. For example, the PSS120may determine if the beacons240is within a specific logical radius271of the beacon240.

As described above, in some implementations, the communications between the beacon240, client102, and PSS120are encrypted. The signal broadcast by the beacon240, for example, a Bluetooth low energy signal, can be detected by devices not part of the PN200. For example, the signal may be detected by a laptop running packet sniffing software or the signal may be detected by third party applications executing on the client device102. For example, a third party may attempt to maliciously determine the user's location by loading software onto the client device102and recording the beacon IDs detected as the client device102visits different locations using the PN200. To protect the privacy of users and to ensure the authenticity of communications, the beacon240, client102, and PSS120may encrypt their communications such that even if a third party did detect the signal from a beacon240it would not be able to ascertain useable information from the signal.

FIG. 3Cis a flow chart of an example method370for encrypting data transmissions when determining the micro-location of a client device. At step371, the PSS120receives data from the client device102. In some implementations, the data includes an encrypted portion and an unencrypted portion. As described below, in some implementations, the data originates from a beacon240. The data is broadcast by the beacon240and received by the client device102, which forwards the data to the PSS120.

The above discussed beacon identifier is stored in the encrypted portion of the data packet. Other data that can be used to ensure the authenticity of the communication is also stored in the encrypted portion. For example, an indication of the time the data packet was transmitted, the up-time of the beacon240, or similar data may be stored in the encrypted portion. In some implementations, the beacon identifier includes GPS coordinates or a text string that identifies the beacon240to the PSS120. The encrypted portion of the data can also include information regarding the beacon240, such as, but not limited to, battery level and firmware version. In some implementations, the beacon240repeatedly transmits the same encrypted portion for a predetermined amount of time. For example, the beacon240may encrypt and broadcast its current up time and beacon identification number for five minutes. After the five-minute period, the beacon240may generate a new encrypted portion that includes the beacon identification number and the present up time.

During manufacture, the beacon240is coded with a key, for example a 16 bit-AES key. When broadcasting data, the beacon240uses the key to encrypt data that it broadcasts. In some implementations, the beacon's key is updated randomly or periodically. For example, the beacon240may include a shared secret that is hashed with a challenge (e.g., the current time) to create a new key.

The unencrypted portion of the data may include a key hint and a local-ID. As described in greater detail in relation to step372, the PSS120may select a key to decrypt the encrypted portion of the data using the key hint. The local-ID may be used by the client device102to determine if it has recently received data from a specific beacon240. As the actual identification of the beacon240is securely stored within the encrypted portion of the data, the client device can identify broadcasts from beacons240by the local-ID and does not have to decrypt the data. For example, a client device102may receive three data packets, the first with a local—ID of A, the second with a local ID of B, and a third with a local ID of A. Responsive to the local ID, the client device102can determine that the first and third data packets came from the same beacon240. In some implementations, the client device102may disregard the third data packet since it already received a data packet from that beacon in the recent past. In some implementations, the local-ID is a 16-bit identifier. At random intervals, each beacon240updates its local ID.

At step372, the PSS120selects a key to decrypt the encrypted portion of the data. In some implementations, when the PSS120receives encrypted data from a client102, the PSS120does not know which beacon240in the PN200generated the data. As each beacon240in the PN200encrypts its data with a unique key, the PSS120must determine which key to use to decrypt the data. The PSS120stores each of the keys required to decrypt data sent from each of the beacons240PN200. In some implementations, the key hint is part of a key-value pair, and once the key-hint is received by the PSS120, the key-hint may be passed through a hash function to retrieve the decrypt key from a hash table. In some implementations, the key hint is not unique, such that the location of the beacons240cannot be mapped by a third party. In some implementations, a geo-hash, or another indication of the beacon's general location, is transmitted in the unencrypted portion. The PSS120may use the geo-hash in combination with the key hint to determine which key to use to decrypted the data. For example, a PSS120may receive a key hint of “DFCD 3454.” The PSS120may then use the key hint to determine that beacon A has a key of “DFCD 3454 XBEA 788A 351A” and is located in California, beacon B has a key of “DFCD 3454 DPIO 89VA 478B” and is located in Massachusetts, and beacon C has a key of “DFCD 3454 78DA DPE7 3487” and is located in Georgia. The PSS120may then determine that the geo-hash is associated with Massachusetts and select the key of “DFCD 3454 DPIO 89VA 478B”, associated with Beacon B, to decrypt the data. In some implementations, the PSS120may not require a geo-hash, and may iterative try each of the keys located with the key hint.

At step373, the data is decrypted. Using the key selected in step371, the PSS120decrypts the encrypted portion of the data. In some implementations, the PSS120also authenticates the sender (i.e., the client device or application) transmitting the data to the PSS120. The PSS120may determine if the user of the client device102has agreed for their location to be determined and that the application that forwarded the data to the PSS is allowed to receive location data.

At step374, the beacon identification number is retrieved from the decrypted portion of the data, and at step375the PSS120determines the micro-location of the beacon associated with the beacon identification number. The method for determining the micro-location of the client device102is described above in relation to method350.

D. Smart Store

FIG. 4Aillustrates a schematic overview of a smart store using beacons240. In some implementations, the beacons240are used by the PSS120to determine the relative location of client devices102within a store or other premise and deliver content to the client device102responsive to the client device's location.FIG. 4Aillustrates a smart store400. Three beacon240(1)-240(3) (generally referred to as beacons240) are place within the store400. Beacon240(1) is placed near the entrance to the store400. Beacon240(2) is placed near the display402(1), which is displaying produces404(1) and404(2). Beacon240(3) is placed near the display402(2), which is displaying products404(3) and404(4). A client device102(1) is within the physical radius406(3) of beacon240(3) and a client device102(2) is within the physical radius406(1) of beacon240(1). As illustrated there is no client device102within the physical radius of beacon240(2). The client devices102(1) and102(2) have established a wireless connection with beacons240(1) and240(3), respectively. The client devices102(1) and102(2) have also established a connection with the PSS120through the network104. The PSS120includes the same components as the PSS120descried in relation toFIG. 2A.

In the example illustrated inFIG. 4A, the beacon240(1) is placed near the entrance of the store400such that it can detect when a new client device102enters the store400. As illustrated, the client device102(2) has just entered the store400and is within the physical radius406(1) of the beacon240(1). While within the physical radius406(1) of the beacon240(1), the client device102(2) may receive data packets with beacon identifiers from the beacon240(1). The client device102(2) may then forward data packets to the PSS120through the network104. As described above, the PSS120may then lookup the location of the beacon240identified by the beacon identifier that was transmitted to the PSS120by the client device102(2). For example, after receiving the data packet and beacon identifier from the client device102(2), the PSS120may determine that the client device102(2) is near beacon240(1) and is therefore near the entrance of the store400.

The client device102(1) may transmit data packets with deacon identifiers associated with beacon240(3), and the PSS120may determine that the user of the client device102(1) is viewing products404(3) and404(4). As described above, the PSS120may transmit supplemental content related to the products404(3) and404(4) to the client device102(1). In some implementations, the PSS120may send supplemental content generally related to the store400to client device102(2) when the PSS120determines that the client device102(2) entered the store. For example, the PSS120may transmit a coupon for 15% off any product404in the store400to client device102(2). The supplemental content deliver to client device102(1) may relate more specifically to the products404(3) and404(4). For example, the PSS120may deliver a coupon for 15% off of product404(4) to the client device102(1) or the PSS120may deliver additional information regarding product404(4) to the client device102(1).

In some implementations, supplemental content can be advertisements, coupons, additional information, or suggested products. The PSS120may determine what type of supplemental content to deliver to a client device102responsive to the user preferences of the user associated with the client device102or the preferences of the owners and managers of the store400. For example, the store owners may wish to reward repeat customers. In this example, a coupon may be delivered to a client device102if the client device102is determined to be near the location of beacon240(1) a predetermined number of times within a predetermined number of days. For example, the PSS120may deliver a 20% off coupon to a user if the user visits the store five times in one month. In some implementations, beacons240may be placed outside of a store or in a location within the store400such that the physical radius406of the beacon240may cover areas outside the store400. For example, the owner of the store400may place a beacon240outside the store400such that the PSS120can determine when a registered client device102is walking by the store and deliver supplemental content to the client device102.

FIG. 4Bis a flow chart of a method450for delivering supplemental content to a client device102in a smart store environment. The method450includes receiving user preferences (step451) and receiving content provider preferences (step452). The method450further includes associating a beacon with a location (step453). The method450can also include receiving a beacon identification number from a client device (step454). Responsive to receiving the beacon identification number, it is determined that the client device is within a predetermined radius of the location (step455). The type of supplemental content or response that should be provided to the client is then determined (step456). Responsive to the response determination, the supplemental content is delivered to the client device (step457).

As set forth above, the method includes receiving user preferences (step451) and content provider preferences (step452). In some implementations, the preferences of the user230and/or content provider250may be updated, added, or removed at any time. For example, the user may see an item for sale online and save it to their account to update the user's preferences. The content provider's preferences may include, but are not limited to, notifications regarding discounts on content, global use coupons, a list of competitors and/or collaborators, a list of preferred users, content inventory, or any combination thereof. The list of collaborators may be business associations that sell complementary items. For example, near Valentine's Day a local florist may enter into collaboration with a local confectioner, such that if a user230purchases content at one of the stores, the user230will automatically receive a coupon at the other store. Similarly, the content provider250may wish to keep a list of customers that, on average, spend a set dollar amount with the content provider each month, quarter or year. In turn, the content provider may have a preference to automatically provide those customers with discounts, coupons, benefits, or other supplemental content.

At step453, a location is associated with the beacon. The location of the beacon is stored in the beacon location database265. As described above, responsive to receiving a beacon identification number, the PSS120looks up the beacon location with the beacon identification number in the beacon location database265. The PSS120then associates the location of the beacon with the location of the client device102. In some implementations, before the PSS120can associate the location of the beacon240with the client device102, the PSS120needs to be provided the location of the beacon240.

At step454, the PSS120receives the beacon identification number from a client device102. As discussed above in relation to method350, in some implementations, the beacon identification number is accompanied by a user identification number.

At step455, responsive to receiving the beacon identification number, the PSS120determines the location of the client device102(step454). In some implementations, the PSS120compares the received beacon indemnification number with a table of beacon identification numbers stored in the beacon location database265. The beacon location database265may then provide the PSS120with the location of the beacon240. In some implementations, the location includes a physical location of the content provider250and/or the location of the beacon240within the content provider250. Responsive to determining the location and/or location of the beacon240, the PSS120may cross reference the determined location of the beacon240with the current location of the client device102to authenticate the received beacon identification number. In some implementations, the client device102may deliver to the PSS120the strength of its connection with the beacon240such that the PSS120can determine if the client device102is within a logical radius of the beacons. In some implementations, the PSS120may wait for the client device102to be within the logical radius of the beacon240before transmitting supplemental content to the client device102.

At step465, the PSS120determines a response based on location, user preferences, and content provider preferences. In some implementations, the calculated response is a determination of the type of supplemental content to be sent to the client device102. In some implementations, the response based on the location of the beacon240, the user's preferences, the content provider's preferences, or any combination thereof. In some implementations, the user230may specify the type of response the user230would like to receive. For example, the user230may request a necklace to complement the currently viewed dress based on the preferences the user has uploaded to the PSS120. As another example, the user may request a coupon for the currently view content or a list of similar items the user is currently viewing.

At step457, responsive to determining the response, the PSS120transmits the response to the client device102. As discussed in reference to method300, in some implementations, the response is transmitted to the client only when requested by the user230. In other implementations, the response may be automatically calculated and delivered to the client device102without intervention by the user.

The skilled artisan will understand that, although the method steps above are shown in a particular order, they can be done in any order, or certain steps may be skipped entirely.

E. Exemplary Implementations of the System

Having described the components of the system, an example of a user230interacting with the system200may provide further details and context for understanding the system and methods disclosed herein. While the below example particularly show and describe specific implementations, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the system and methods described in this disclosure.

As a basis for the example, the PSS120hosts a website that the user230may access via a client device102, such a web enabled smart phone or home computer. Furthering the example, the content providers250may be a clothing merchant that sells clothing through its retail outlets or stores. Within those outlets the clothing merchant places beacons240throughout the store. The merchant may then list the merchandise available at the store with the PSS120. Additionally, the PSS may gather images of merchandise from non-content providers, such from the website of fashion magazines.

In this example, a user may view clothing, accessories and other merchandise on the website hosted by the PSS120. As the user views the items on the website, the user may mark items they like or dislike. The system may then use the characteristics of these items to update the user's shopping and merchandise preferences. The website saves the user's preferences and “liked” items so the user may view details about them at a later time or share the details with friends via the website. For example, a group of friends may send each other images of dresses they like for an event, or a user may view the items save by a fashion forward movie star or other fashion opinion leader.

These details may also be saved, synced, and/or accessed by the user's smart phone. In this example, the user's smart phone may include a computer program that syncs with the PSS120. Additionally, the smart phone may be Bluetooth enabled such that it can detect the presence of a beacon.

Now referring back to the clothing store of content provider. The merchant can place a number of beacons around the store, for example, at the entrance to the store and near a table of dresses. In a manner completely transparent to the user, when the user enters a beacon-enabled, clothing store the user's phone may recognize the beacon. The beacon may send the phone an identifier, which the phone retransmits to the PSS120. The PSS120resolves the identifier and determines in which store the beacon is located and the beacon's location within the store. Accessing the user's preferences, the PSS120may determine specific items the user may like.

As this process is transparent to the user, the user's experience of walking into a beacon-enabled store is as follows. Within a few moments of walking into the store, the user's phone alerts the user that the store has a dress similar to the dress the user recently indicated liking on the website hosted by the PSS120. Additionally, the user may receive information about the dress such as availability, location with the store, and price. The user may also receive a coupon for 10% off from the merchant as a thank you for having visited the store multiple times within the last week.

Next, the user may walk to table displaying the dress. The table contains a beacon. As the user nears the table the user's phone detects the beacon and, as described above, relays the beacon's identification to the PSS120. Knowing the location of the beacon, the PSS120can estimate that the user is viewing the dress.

Not seeing the dress in the user's size, the user may request assistance from a store employee via the program running on the phone. Additionally, if the user accesses the program while in the store the program may automatically display information about the merchandise at the nearest beacon. In this example, rather than asking for assistance from an employee, the user may access the program on the user's phone, which automatically reveals information about the dress the user is viewing. This information may reveal to the user the store currently has three of the dresses in the user's size in the store's back storage area.

The system, having noticed the user has been near the beacon corresponding to the dress for some time without moving on, may predict the user has mixed feelings about purchasing the dress. After the user has been in close proximity to the dress for a few minutes, the PSS120may automatically deliver to the user's phone a coupon for the dress that is valid for only the next 10 minutes.

F. Exemplary Implementations of a User Interface

As discussed above, the PSS120includes an interface module263. In some implementations, the interface module263generates a user interface and a content provider interface. The interfaces may be a website executing on the PSS120and/or another central web server. In some implementations, the client device102executes a computer program that interfaces with the PSS120. In other implementations, the client device102includes a web browser that views the website pages provided by the PSS120and/or other central web server. The exemplary implementations below represent a possible user interfaces that may be viewed as a webpage and/or as a graphical user interface of a computer program interacting with the PSS120.

FIG. 5Ais a first page of an exemplary implementation of a user interface. The user interface displays a plurality of content items501that are available from one or more content providers250. In some implementations, the displayed content items501can be filtered. For example, the user230may request that only men's fashions be displayed or only supplemental content251from a particular content provider250be displayed. The user interface also includes a number of buttons502(1)-502(n). The exemplary implementation ofFIG. 5includes 5 buttons. The buttons may be “soft buttons” that update according to the current page of the user interface that is currently displayed. In other implementations, the buttons502are constant throughout the plurality of pages of the user interface. In some implementations, the user may select displayed content. Selecting the displayed content add and/or updates the user's preferences.

Similarly, inFIG. 5Bthe exemplary user interface is displaying a plurality of content providers250. In some implementations, the plurality of content providers250is all content providers250that are in the PN200. In other implementations, the displayed content providers250are a sub-population of the total number of content providers250. For example, the user230may wish to only display content providers250that have been selected by the user230and/or only content providers250that are within a given distance of the current location of the user230. In some implementations, the user may select content providers to add to the user's preferences.

FIG. 5Cis an exemplary implementation of the user interface displaying content providers250within a given location of the user230. In some implementations, the nearby content providers250are displayed on a map504. The content providers250may be marked on the map504with an indicator505. The user230may set the scale of the map504, and the number of displayed content providers250may update as the user230pans and zooms the view of the map504.

In some implementations, the choice of content provider250to display on the map504is responsive to the user preference and/or content provider preferences stored in the PSS120. For example, the user interface may only display content providers250that the PSS120has determined the user has a high probability of having an interest. In other implementations, the selection of the content providers250to display may be based on the preferences of the content providers250. For example, the content providers may wish to have the PSS120provide, via the user interface, coupons to a specific demographic of user within a 2-mile radius of the content provider.

FIG. 5Dis an exemplary implementation of the user interface displaying additional information regarding a content provider250. In some implementations, responsive to selecting an indicator505on the map504, additional information is provided to the user regarding the selected content provider250. Additional information about the content provider250may be displayed in a window506that is overlaid on the map504. The window506may display, but is not limited to displaying, the content provider's name, location, contact information, availability of content, and available supplemental content.

FIG. 5Eis an exemplary implementation of the user interface for displaying supplemental content to a user230.FIG. 5Dlists a plurality of supplemental content507currently available to the user230. In some implementations, the user230may save specific supplemental content for later use. As described above, in some implementations, the displayed supplemental content507is global supplemental content. Global supplemental content may be supplemental content that is available to all users of the PN100. In other implementations, the displayed supplemental content includes supplement content507that is specifically selected for and/or by the user230.

FIG. 5Eis an exemplary implementation of the user interface for displaying the user's profile. In some implementations, the profile page may act as the hub of the user interface. For example, the user may add, remove, or change preferences. In some implementations, the user230may change system preferences on the profile page. In some implementations, system preferences may change the way the user230interacts with the user interface or how content providers250are allowed to interact with the user230. In some implementations, the profile page includes a window508that displays current or recent activity. The number of new items may also be presented to the user as a notification icon509that is always viewable to the user230when the user230is using the user interface.

G. Exemplary Implementations of a Backend System

As described above, the PSS120includes an interface module263. In addition to the user interface descried above, the PSS120may also provide a content provider interface and system management interface. The content provider interface may provide content providers250with an interface for performing actions such as updating supplemental content (e.g., coupons) and changing beacon parameters (e.g., logical radii settings). The system management interface may allow the manager of the PSS120to perform functions such as, but not limited to, adding new content provider accounts and associating beacons240with specific content providers250.

Management of Content Providers

The interface module263may provide the manager of the PSS120with a system management interface (also referred to as the console) for managing various aspects of the PSS120. These aspects may include adding and removing content providers250from the PSS120and associating beacons240with specific content providers250. As described above, the console or other interface may be provided in the form of a webpage, web application, and/or computer program. The interface may be accessed and/or executed by various types of computing devices, such as desktop computers, laptops, smart phones and/or tablet computers.

In some implementations, the PSS manager may use the console to add content providers250to the PSS120. For example, the PSS120may be managed by a company that sells and/or licenses accounts to content providers250. The manager of the PSS120may create a PSS account for the content provider250responsive to selling and/or licensing a PSS account to the content provider250. The content provider250may provide information to the PSS manger. The PSS manger may then use the information to setup a PSS account for the content provider250. The information may include an account name, account manager information, number of properties (e.g., stores) in which the content provider250may be using the beacons240, the number of beacons240the content provider250is requesting (or purchasing), number of user logins to be associated with the PSS account, and any special instructions for the PSS manager. The PSS manager may future associate licensing restrictions with the content provider's250PSS account. The licensing restrictions may include the length of the license and the features of the PSS120the content provider250is licensed to use. Optional features to license may include content management and publishing, offers management, in-store beacon management, and analytics capabilities.

Responsive to creating the content provider's250PSS account, the PSS manager may associate an account administrator to the PSS account. The account administrator may be an employee of the content provider250responsible for managing the PSS account. Managing a PSS account may include adding and removing authorized account users and managing the content provider's250PSS preferences.

As described above, the content provider250may be a store. In some embodiments, the content provider250may own or manage a plurality of properties. For example, the content provider250may be a chain, which operates one or more stores in one or more cities. In some embodiments, the account administrator may group its plurality of properties responsive to set criteria. For example, the plurality of stores may be grouped responsive to a geographic location. In some embodiments, the account administrator may group its plurality of properties based on a scheme that mirrors the content provider's250business structure. For example, the content provider250may divide its stores into sales regions. When grouping the plurality of properties associated with the PSS account, the account administrator may group the plurality of properties such that the groups align with the sales region.

In some implementations, one type of authorized user may be a group administrator. The group administrator may be responsible for one or more groups associated with the content provider's250PSS account. Continuing the above example, the system user responsible for a group may be a regional manager for a sales region. Another type of authorized user may be the role authorized user. The group administrators may create role authorized users and assign predetermined responsibilities to the role authorized users. Example responsibilities (or roles) may include content creator, offers manager, data analyst manager, and beacon manager. In some implementations, the content creator may create, manage, and publish content provider assets and product merchandising. The offers manager may create and manage the personalized supplemental content provided to users230. The data analysis manager may generate and view reports created by the PSS120and the analysis module264. The beacon manager may activate and deactivate beacons240and set beacon parameters such as location and the above described logical radius271. In some implementations, authorized users may be created which are not assigned specific roles. These authorized users may log into a content provider's250PSS account to view information, but may not be authorized to perform tasks associated with the above described roles.

One or more of the authorized user types may be authorized to perform various administrative functions. For example, an administrative function may include sending messages to the authorized users associated with the content provider's250PSS account. In some implementations, the messages may be sent to a specific type of authorized user. For example, the messages may be sent to only the beacon managers. Administrative functionality may also include resetting and/or retrieving passwords, performing system audits, and creating user directories.

FIG. 6is a flow chart of the hierarchical relationship between the authorized user types described above. As an overview, the PSS manager600is the highest level authorized user. The PSS manager600may manage the PSS120. The PSS manager600may sell the services of the PSS120to n content providers250. For each content provider250, the PSS manager600may create an account manager601. The account manager601may then create one or more group managers602. Each group manager602may then create one or more role authorized users603. The role authorized users603may then create one or more authorized users604. In some implementations, a user type may create and/or manage user types below it on the relationship tree.

Management of Beacons

In some embodiments, the PSS manager licenses and/or sells the beacons240to content providers250. In some embodiments, specific functions of the beacons240may need to be managed by the content provider250and/or the PSS manager. For example, the PSS manager may activate and deactivate beacons240responsive to the start and end of a licensing agreement with a content provider250. The content provider250may manage beacon parameters such as the logical radius271. In some implementations, beacons240may be managed by one or more of the above described authorized user types.

In some implementations, the PSS manager may maintain a database of the beacons240within the PN200. The database may include the beacon's240serial number, MAC address, manufacturing data, manufacturer, version number, firmware version number, shipment date, associated content provider250and case type. The PSS manager may populate the database prior to sending the beacons240to the content provider250.

Responsive to receiving the beacons240from a PSS manager, the content provider250may log into the console and set various beacon parameters. In some embodiments, the parameters may include beacon placement, the size of the logical radius271, and the active/inactive state. In some embodiments, via the console, the beacon manager may also view beacon status reports for the beacons240under its management. The information may include the version number of the beacon240, battery level, activation state, and up time.

Management of Supplemental Content

An authorized user may manage the content provider's250supplemental content and the content's distribution through the console. The content provider250may create and manage conditions that govern the distribution of supplemental content. The conditions may include store segments, audience segments, event triggers, and user parameters. As described below, the conditions may be created and applied to one or more supplemental content items. By reusing conditions and rules, the authorized users may reduce the time required to create supplemental content.

One exemplary embodiment of a condition is a store segment condition. In some embodiments, the above described groups may also be further divided into store segments to provide greater control in where supplemental content is distributed. The store segments may incorporate one or more parameters. For example, a content provider's250stores may be segments based on the store's performance and/or location. In some implementations, a store may belong to more than one segment. For example, a content provider's250store in New York City may belong to a New England segment, a New York state segment, a New York City segment, and a high performance segment.

An audience segment condition may be another exemplary embodiment of a condition. The audience segment may allow supplemental content to be provided to only specific users230. Audience segments may include one or more parameters such as, but not limited to, the number of visits within a given time range, the age of the user230, and the gender of the user230. For example, a user230may be included in a first audience segment if the user230visits the content provider250more than three times in the last month, is between the ages of 18 and 34, and is female.

The delivery of supplemental content may be triggered responsive to an event condition. These event conditions may be referred to as offer trigger events. A number of parameters may be associated with the offer trigger. The parameters may include location, beacon reference, delay time, dwell time, and default status. For example, an offer trigger that occurs when a user230enters a content provider's250store may include the parameters: title=Walk in Instant; Beacons=All; Delay time=0 sec; default=yes.

Having created the conditions that may control the distribution of the supplemental content, the authorized users may create the supplemental content. The supplemental content may be placed in an offer queue that dispenses the supplemental content. In some implementations, multiple offer queues may be created. In some implementations, multiple offer queues may be created; however, only one may be active at a given time. For example, an offer manager may create offer queues for each season and then activate the seasonal offer queue during the correct season. The supplemental content may include one or more parameters. The parameters may include supplemental content value (e.g., 30% off or $10 off a purchase of $50), start date, end date, start time, end time, barcode image, supplemental content code, expiration time, exclusions, frequency cap, sharing option, and template. The template may layout and design (i.e., the visual presentation) of the supplemental content. In some implementations, the PSS120may verify one or more the supplemental content parameters before distributing the supplemental content. For example, the frequency cap of one supplemental content item may be set to 1,000. In this example, if the supplemental content has already been distributed 1,000 times, the PSS120may look for another supplemental content item in the offer queue to distribute to the user230. Responsive to creating the supplemental content, the supplemental content may be associated with an audience segment condition, store segment condition, and/or trigger event condition.

In some implementations, the PSS120may determine that a user230meets the conditions to receive more than one supplemental content item. In some embodiments, a priority level condition may be assigned to each supplemental content item. The priority level may be used to determine which supplemental content item the user230should receive. For example, the offer manager may create supplemental content for loyal customers and give it a higher priority than supplemental content for the general public. Accordingly, in this example, the loyal customer may receive the supplemental content intended for loyal customers over the supplemental content intended for the general public.

In some embodiment, the PSS120may include a mechanism for approving supplemental content. In some implementations, offers reducing the price of supplemental content251by a percentage or amount over a predetermined limit require approval before the PSS120distributes the supplemental content to users230. The PSS120may seek approval for supplemental content my sending a message (e.g., an email message) to the account manager or other authorized user authorized to approval supplemental content.

FIG. 7is a flow chart of a method700for creating, managing, and delivering supplemental content. At step701, the method700includes creating one or more conditions. As described above, the conditions may include audience segment conditions, store segment conditions, and event trigger conditions. In some implementations, the PSS120stores the conditions such that they may be used with multiple supplemental content items. At step702, the supplemental content is created. Creating supplemental content may include associating predetermined parameters with an offer.

At step703, the supplemental content is approved. In some implementations, the supplemental content may not require approval, and in other implementations, the supplemental content may require approval if the supplemental content includes an offer over a predetermined dollar value.

At step704, one or more conditions are associated with the supplemental content. As described above, the conditions may include one or more parameters. The PSS120may use the parameters within the conditions to determine what supplemental content to deliver to a user's230client device102.

At step705, the PSS120receives a beacon identification number from a client device102. In some implementations, step705may mirror step453of method450described above. As described above, when a client device102is within a predetermined range of a beacon240, the client device102may detect the beacon's204beacon identification number. The client device102may then transmit the beacon identification number and client device identification number to the PSS120. Responsive to the beacon identification number and client device identification number, the PSS120may retrieve supplemental content that may be appropriate to deliver to the client device102.

At step706, the PSS120determines which of the supplemental content items retrieved in step705should be delivered to the client device102. The determination may be responsive to the conditions associated with each of the supplemental content items. For example, in step705the PSS120may retrieve a first supplemental content item with the condition it is to be delivered to female user and a second supplemental content item with the condition it is to be delivered to a male user. The PSS120may review these conditions and determine that as the client device102is associated with a male user, the second condition should be delivered. At step707, the supplemental content is delivered to the client device102.

The skilled artisan will understand that, although the method steps above are shown in a particular order, they can be done in any order, or certain steps may be skipped entirely.

H. AD Auction

As described above, in some implementations, a beacon240can be placed in a store. In some implementations, the store may sell a plurality of products from a plurality of venders (or content providers). For example, a home improvement store may sell ten different types of lawn mowers produced by three different venders. As described above, the PSS120may send supplemental content to a client device102when the client device102is within a predetermined range of a beacon240. In implementations, when the beacon is placed near the products of a plurality of venders, the PSS120may hold a content auction to determine what supplemental content is delivered to the client device102.

FIG. 8illustrates an example environment800for a content auction. As illustrated, products801(1)-801(4) (collectively referred to as products801) are for sale in store802. A beacon240is placed near the products801. The beacon240can communicate with a client device102within the beacon's physical radius803. As described above, the client device102is in communication with the PSS120through the network104. The PSS120ofFIG. 8is illustrated including a content database804, a transaction database805, and an auction module806. Any component described in relation to a PSS120can be included in any other PSS120described herein. The environment800also includes a plurality of content providers807that generate supplemental content to be delivered to the client device102. In some implementations, the content provider807are the venders of, or otherwise associated with, the products801.

InFIG. 2A, the PSS120ofFIG. 8can also include a content database804. The content database804can be database where the PSS120stores the supplemental content generated by the content providers807. The content stored in the content database804can be stored in the content database804in association with a bid price and at least one beacon240or beacon location. For example, a content provider807may be willing to pay $3.00 for one of its supplemental content items to be delivered to client device102when the client device102is near the content provider's product801.

The PSS120may store the results of past auctions in the transaction database805. In some implementations, the content providers807may set a cap on the amount of money they wish to spend on auctions within a predetermined amount of time. The PSS120may store this information in the transaction database805and determine if the content provider807has enough money left in their allowance to place a bid in an active auction. For example, a content provider807may wish to spend no more than $1,000 on auctions per month. In this example, if the content provider807has already spent $998.00 on auctions in the month, the transaction database805may prohibit a $3.00 bid from being placed for the content provider's account. The transaction database805may also be used to general reports for billing purposes at the predetermined intervals. For example, the owner of the PSS120may create invoices for each of the content providers807using an interface to the transaction database805.

The auction module806may conduct the auction to determine what supplement content is to be delivered to the client device102. For example, responsive to the PSS120determining the client device102is within the physical radius803of the beacon240, the PSS120may transmit supplemental content to the client device102. The PSS120can access to the content database804to determine what content is associated with the beacon240. In some implementations, the auction module806may access the transaction database805to determine if the content associated with the beacon240is eligible for an auction. Content may be ineligible for an auction if, for example, the content provider807wishes to spend a predetermined amount on auctions per month and that amount has been met for the month. The content provider's content may not be eligible for auctions until the content provider's budget renews at the beginning of the next month.

Responsive to determining what content is associated with the beacon240, the auction module806conducts the ad auction. In some implementations, the auction module806iteratively increase the price for sending the supplemental content item to the client device102until a winner of the auction is determined. For example, if the auction module806determines that content item A, B, C, and D are associated with products801(1),801(2),801(3), and801(4), respectively, it may enter the content items A, B, C, and D into the ad auction. In this example, if content item A has a maximum bid price of $3.00, content item B a maximum bid price of $5.00, content item C a maximum bid price of $2.00, and content item maximum D a bid price of $3.00. The auction module806may increase the bid price of the auction until a winner is determined. The increase in bid price may be a fixed or variable amount. Furthering the above example, assume the increase price is $0.10. In this example, content item C would drop out once the bid price reaches 2.00 and content items A and D would drop out when the bid priced reaches 3.00. Content item B would win the auction at a price of 3.10. In some implementations, auction module806calculates the winning price as the second maximum highest bid price, which is to be paid by the content provider associated with the highest bid price. In this example, the second highest bid price is $3.00, which would be charged for displaying content item B. In some implementations, if the highest bid price is associated with more than one content item (for example, if the above example action also included content item E with a maximum bid price of $5.00), the winner of the auction may be determined by randomly selecting one of the content items that has the highest maximum bid price. In some implementations, with multiple highest maximum bids, each of the content items with the highest maximum bid may be queued for subsequent delivery to client devices102. For example, content item D may be delivered to the first client device102and content item E may be queued for display to the next client device102that enters the physical radius803. Once the queue is empty ad auctions may resume to determine which content items are delivered to client device102entering the physical radius803.

FIG. 9is a flow chart of a method900for conducting an ad auction. At step901, the PSS120receives a plurality of supplemental content items. The plurality of supplemental content items can be received from one or more content providers807. In some implementations, a maximum bid price and a specific beacon240are associated with each of the supplemental content items. In some implementations, the supplemental content items can be associated with a plurality of beacons240. For example, a content provider807may sell grills through a national retailer. In this example, the content provider may associate their supplemental content items with each of the beacons located near the grilling section of each of the national retailer's stores. As described above, the maximum bid price is the maximum price the content provider807is willing to pay for the supplemental content item to be delivered to the client device102.

At step902, the PSS120receives an indication of a client device102location. As described above in relation toFIG. 8, the PSS120may determine the location of a client device102by receiving a beacon identification from the client device102once the beacon240has crossed the physical radius803. The PSS120may then determine the location of the beacon240that generated the beacon identification number and then associate the location of the beacon240with the client device102.

At step903, the PSS120selects a portion of the plurality of supplemental content items responsive to the location of the client device102. For example, the auction module806, may search the content database804for content items that are associated with the location indicated in step902. The PSS120may then enter the selected content items into an ad auction to determine which content item is to delivered to the client device102.

At step904, the PSS120selects a supplemental content item responsive to the bids associated with the each of the plurality of supplemental content items selected in step903. As described above, in some implementations, the supplemental content item is selected through an ad auction. In some implementations, responsive to multiple content items having the same maximum bid price, the ad auction can have a plurality of winners. In these instances, the content item to be delivered can be randomly selected from the plurality of winners or the winning content items may be queued for display to subsequent client devices as they enter the physical radius803of the beacon240. Once a content item is selected for display to the client device102, the price of the winning bid is charged to the account of the content provider associated with the winning content item.

At step905, the selected supplemental content item is delivered to the client device. The content item may be delivered to the client device via Wi-Fi or a cellular connection of the client device. In some implementations, the content item is only delivered to the client device is actively running an application associated with the PSS120. In other implementations, the content item may be delivered to the client device102as a push notification, and the software application associated with the PSS120does not need to be open or active. In some implementations, if the client device102remains within the physical radius of the beacon240for a predetermined amount of time, the PSS120may conduct a second ad auction to deliver a second supplemental content item.

I. Distributed Updates

In some embodiments, a great number of un-networked beacons can be managed and/or receive firmware upgrade from a central server via an intermediary client device. In this way, the beacons can be designed without Internet capabilities to save production cost. For example, large organizations may have thousands of locations with each location containing hundreds of beacons, each of which broadcasts a signal to support micro location detection. In this case, managing the status of the beacons and performing firmware upgrade can be challenging. The systems and methods of the present disclosure, for example as shown inFIGS. 10 and 11, enable the management of a fleet of unconnected beacons using a network of unsecured (e.g. without any specific or dedicated authentication or other security features), networked client devices that periodically check on the health and upgrade status of each beacon. For example, firmware upgrade for beacons can be downloaded at a client device via the Internet, which may in turn transmit the upgrade data to the beacon via a local connection (e.g., Bluetooth).

In some examples, the client device acts as an intermediary device to convey an encrypted message including firmware upgrade data from a central server to the beacon. For example, when a large number of client devices may be used as potential intermediary devices for firmware upgrade for beacons, registering each and every client device with the server may be inefficient and impractical. When there is no required trust relationship between the client device and beacon or even the client device and server, the update messages could be distributed over an insecure network. In this way, the client device may not need to be registered with the central server, which may allow a large variety of client devices to serve the role of providing firmware upgrade for beacons without any pre-registration or pre-authorization with the central server.

In some embodiments, the client device may instantiate a provided client component, such as configuration utility applications (e.g., a mobile app installed on the device, etc.), created to manage these large beacon deployments or consumer applications that perform beacon maintenance as a background process on the device. This approach may allow a group of employees or consumers to securely perform crowd-sourced configuration of beacons without any authentication or even knowledge of the updates and without any direct connection between the beacons and the server.

In further embodiments, the systems and methods disclosed herein may be applied to any non-networked or distributed devices capable of communication over a local area wireless communication protocol, such as sensors, smart devices, single board computers, devices considered part of the internet-of-things, or any other embedded computing or BLE device.

FIG. 10shows a block diagram illustrating data flows between various entities that may be used to provide updates to beacons, according to some embodiments. As shown inFIG. 10, messages are passed between a beacon240(e.g. seeFIGS. 2A and 2B), a client device102(e.g. seeFIG. 2B), a Pinpoint System Server (PSS)120(e.g. seeFIG. 2A), and a role authorized user603(e.g. seeFIG. 6). In some implementations, the role authorized user603is a beacon manger or any person or group who are authorized to provide updates to the beacon240. In another implementation, the role authorized user603can include or be affiliated with any of an upgrade server, storage server, cloud server, and/or the like. Updates are included in a beacon configuration update message1002, and can be used to change any of the parameters that are configurable by the beacon. For example, the configurable parameters altered by an update may include, but are not limited to, the status of logical radii, daisy chaining of beacons, the physical broadcast radius, power-saving parameters, system update information, and/or the like. The beacon configuration update message1002may also contain updates to the firmware running on beacon240. In some implementations, firmware updates can be provided by the role authorized user603.

Beacon configuration update message1002may be communicated to PSS120constantly, intermittently or periodically through a network message or any suitable interface, such as a keyboard and mouse. In an alternative implementation, the beacon configuration update1002may be triggered when the PSS120sends an update request to the role authorized user603. Updates pending for each beacon are stored in association with each beacon's record in the beacon location database265within the PSS120. Updates may be stored entirely within the database record or may be referenced by a pointer and stored in a suitable file system. The PSS120will also keep a record of a desired status indication, such as a version number that should be contained within beacon status message1004bor a record of which updates have been acknowledged as successfully applied and which updates are unacknowledged. In some implementations, contents of the beacon update message1006amay be atomically packaged into one or more data units at the PSS120, which may divide and/or combine the updates in any suitable manner so that they may be applied in individual, atomic data units, segments, batches or messages. Updates submitted by role authorized user603may be divided into multiple updates that fit in individual data packets that are sized according to the parameters of the local and wide area network communication protocols. In some implementations, the PSS120includes an indication an update message1006ais part of a series of messages that cover a single update (e.g. a firmware file divided into multiple packets). The transmission of updates is described in greater detail with respect toFIGS. 11 and 12. The beacon update message1006amay be atomically transmitted to the client device when the network connection is available. For example, the client device may halt the downloading of the update message1006afrom PSS120when a network problem occurs, but may be able to resume downloading once the network connection is recovered without re-downloading the entire update message1006a. The beacon update messages1006aand1006bmay be referred to herein as an encrypted update data message since they includes the data required to update a beacon and are encrypted according to the methods disclosed herein. The PSS120may assign an update id number to each atomic update that is received by the client device102. The beacon location database265(e.g. seeFIG. 2A) can list the update id numbers of each pending update, which may be independently and individually removed from the list, for example as they are applied and acknowledged. In some implementations, a version number will serialize the pending updates and the beacon status message1004bwill indicate the update id number of the most recent update to be received contiguously with earlier updates.

Beacon240may periodically, constantly or intermittently broadcast a wireless message, which may be encrypted, that includes beacon status data, such as a beacon id or configuration version number, and is used to enable micro-location. This encrypted packet including beacon status data may be referred to herein as an encrypted status data packet. The beacon status data may be referred to herein as a status indication and includes but is not limited to version number, an identification of the most recent update to be applied contiguously with previous updates, or any other suitable indication of the updates applied by the beacon240. For illustrative purpose only,FIG. 10shows that the beacon status message1004ais broadcast from beacon240after the beacon configuration update1002. The beacon configuration update1002received by PSS120, and the beacon240broadcasting the beacon status message1004amay occur simultaneously, in parallel, or in any possible order. In some implementations, beacon status message1004aincludes a status indication contained within the broadcasts. In some implementations, beacon status message1004ais a separate broadcast. In some implementations, beacon status message1004ais unencrypted (e.g. the contents of the message can be understood by devices operating on the same communication medium). Beacon status message1004ais transmitted wirelessly over a local wireless communication protocol, such as Bluetooth, to client device102, which receives the beacon status message using a client component and forwards the data from beacon status message1004aover a suitably wide area network, such as the Internet or the local wireless communication protocol where suitable, to the PSS120. The PSS120decrypts the beacon status message1004bto extract an indication of the status (e.g. current firmware or OS version) of the beacon240, which is used to determine if there are pending updates. In the event that there are updates pending, the PSS120packages the update into an encrypted beacon update message1006a, which is transmitted to client device102over the wide area network. Once a client device102arrives within a detectable range of the beacon240(e.g., within a Bluetooth communication range, etc.), and receives the beacon status message1004a, the client device102may detect the beacon, e.g., as discussed in relation toFIG. 2B. In some implementations, the client device102may then determine whether an update for the beacon is available, and then forward the data to the beacon240over the local wireless communication protocol as beacon status message1006b.

In some implementations, the beacon240is configured to expand its broadcast radius during a predetermined time referred to herein as an administrative window. The expanded broadcast range may allow for a single client device102to communicate with multiple beacons from a single location that might otherwise be outside of the range of the beacons. For example,FIG. 2Bshows a client device102(3) between the physical radii of two beacons240. During the administrative window, the beacons240may expand their physical radii so that client device102(3) may update both beacons240without moving. For example, each beacon240may track an administrative window, which may be configured to have the same or different parameters (e.g., a start time, a duration, an end time, etc.) for all beacons, using a local clock or timer. At the start time of an administrative window, the beacon240may increase the power level of its local area wireless signal to a configurable level, which in turn expands the physical broadcast radius of the beacon240for the duration of the administrative window. In some locations, this will allow for a stationary device, such as a Bluetooth enabled point-of-sale device, to ensure that beacons are updated. In some implementations, the administrative window will allow for an administrator with a mobile client device102to do minimal travel. In some implementations, an administrative client device102may guide an administrator to beacons, for example by using micro-location or providing a map indicating beacon statuses, that require pending updates, as indicated by records of updates that can be transmitted to the administrative client device102from the PSS120. The administrative client device102can also display an indication of which beacon240is being updated and the progress of the update, e.g. the progress of transmitting beacon update message1006bor a series of beacon update messages. In some implementations, the PSS120transmits a prompt to role authorized user603requesting an update. For example, the prompt may be transmitted prior to the administrative window or in response to a beacon status message1004b.

FIG. 11shows a logic flow diagram illustrating distributing an update to a beacon. At1102, role authorized user603submits a beacon update, which may specify a change to be made to any of the configurable settings of a beacon, include new software or firmware to be stored on the beacon, or any other suitable data that needs to be transmitted to the beacon by an authorized user, such as a retailer, a beacon manager, a manufacturer, or a software provider. At1104, the submitted beacon update is stored by the PSS120, or any suitable storage system, and associated with the beacon that requires the update, e.g. by storing information related to the update in the beacon location database265or another suitable database, key value store, or storage means. In some implementations, updates that apply to multiple beacons may be de-duplicated in storage, for example by storing a pointer to a single firmware update file instead of storing a copy of the firmware for each beacon. At1106, the PSS120will update its records to indicate that there is an update pending for a beacon240. The PSS120may store a desired status or version number for beacon240, a list of updates that are pending, or any suitable indication that a stored update has not yet been applied by the beacon240.

At1108, the beacon240, which in this example has not yet received the update submitted at1102, encrypts an indication of its status. The beacon status indication may be a version number, an identification of the most recent update to be applied contiguously with previous updates, or any other suitable indication of the updates applied by the beacon. In some implementations, the beacon status indication is omitted, and the tracking of which updates are pending or applied is done solely by the PSS120. In some implementations, the status indication is contained in an unencrypted portion of a broadcast sent from the beacon.

At1110, the beacon240encrypts the indication of its status and broadcasts beacon status message1004a(as shown inFIG. 10), as described above, over a local wireless communication protocol, such as Bluetooth. The beacon status message1004amay be included in the encrypted messages used for providing micro-location services. At1112, the beacon status message1004ais received by a client device102within the broadcast range of the local wireless communication protocol. The beacon status message1004acan be kept confidential from the client device to avoid information leak for security concerns. For example, the beacon240may encrypt the beacon status message1004a(at1108) using an encryption key that is unknown to the client device. In this way, the client device may be prevented from reading the encrypted contents of the beacon status message1004aas the data in the encrypted portion of the beacon status message1004awill be obscured (e.g. by a cryptographic hash function). In this way, the client device acts as a conduit to transfer the beacon status message1004ato the PSS without any need to decrypt/process the received status message, and thus does not need to install or be configured with any additional software components. Consequently, the client device102may not need to be secured or to be trusted to participate, and may act as an intermediary device between the PSS and the beacon by relaying encrypted data but without decrypting any of the encrypted data. In some implementations, a trusted and securely authenticated client device102may be used. In some implementations, the client device102may decrypt an encrypted beacon status message1004ain order to determine whether the status indication of the beacon240was previously transmitted to the PSS120within a threshold amount of time. In step1114, the client device102retransmits beacon status message1004aas beacon status message1004bover a sufficiently wide area network, such as a wired or wireless internet connection, to the PSS120, which receives the data at116.

At1118, the PSS120decrypts the beacon status message1004b. As described above, decryption is done with a shared secret key (e.g. a key that is known to both the beacon240and PSS120) that is associated with the beacon240and possibly an indication of the location of beacon240. In some implementations, the beacon240and the PSS120use their own pairs of public and private encryption keys, for example each beacon could be programmed with a public key for the PSS120and use the beacon id as a public key. At1120, the PSS120extracts the beacon status indication from the decrypted beacon status message1004band compares the beacon status indication against the desired beacon status or checks for indications of pending updates to determine if the beacon240is in need of an update. At1122, the update is packaged into one or more beacon update messages1006a, which may be generated differently for small configuration changes and larger firmware updates. The process of packaging and transmitting updates is described in greater detail in relation toFIG. 12.

At1124, the PSS120transmits beacon update message1006ato client device102. In some implementations, PSS120stores, for example in beacon location database265, the network addresses of the client devices that have recently forwarded a message from the beacon240. The PSS120may send beacon update message1006ato a different client that is likely to be within range of a beacon. For example, the beacon status message1004bcan indicate that the forwarding client device102received the message because it was leaving the range of beacon240and is therefore unlikely to be suitable for forwarding the update. In some implementations, when there are multiple beacon status messages1006afor a single update, the PSS120may forward the messages through multiple client devices, and the beacon240may combine packets from the clients such as in a torrent or peer to peer download model. In some implementations, PSS120forwards beacon update message1006ato a known access point, e.g. a point of sale device enabled to access the local area communication protocol. Such known access point may be used to relay the updates to beacons when the client device is beyond the communication range of the beacon. For example, an access point may have a large broadcast range, such as 10 meters, 20 meters, or 30 meters or more. Any client device within the communication range of the access point may transmit the beacon updates to the access point first, and then the updates can be sent to the beacon from the access point. The client device receives beacon update message1006aover the wider area network and forwards the message to the beacon240as beacon update message1006bover the local area communication protocol in step1128.

At1130, the beacon240receives beacon update message1006b, which is unpackaged and applied at1132. The beacon240decrypts the beacon update message1006b, and extracts information related to the update, e.g. a nonce, that can be used to determine both that the update is valid (e.g. that the update was issued by the PSS and is intended for the beacon240) and whether it has been applied previously, for example if the update was sent to two different clients by the PSS perhaps due to a lost acknowledgement. The beacon240may also check that it has received all of the messages that comprise a complete update before applying the update. In some implementations, the beacon240will cache updates that it receives and commit the updates to memory in the order created by the PSS numbering. Unpacking and applying updates is discussed in more detail in relation toFIG. 13. Once an update has been applied by the beacon240, at1134, the beacon240will transmit an acknowledgement of the update to client device102, which, at1136, receives and forwards the acknowledgement to PSS120. At1138, PSS120records that the update was completed and is no longer pending. In some implementations the update is considered complete when it is stored in its entirety in memory in the beacon. In some implementations, the update is considered complete when the acknowledgement of the update is received by the PSS120.

FIG. 12shows a flow chart illustrating an exemplary process of transmitting beacon updates, according to some embodiments. In one embodiment, the process1200involves the PSS120comparing a status indication received from a beacon240to a desired status indication (1202), retrieving any pending updates for the beacon240from memory, and iteratively generating beacon update messages, such as1006a. The iterative update message generation involves generating a nonce for the beacon update message1006a(1206), filling a data packet with the nonce and update data (1208), encrypting and transmitting the beacon update message1006a(1210), and iterating if the complete has not yet been sent (1212).

At1202, PSS120compares a status indication received from a beacon240, such as at1118inFIG. 11, to a desired status such as a latest firmware and/or configuration update status the PSS120obtained from the role authorized user603(e.g., seeFIG. 6) and retrieved from a database. If the PSS120record for desired status, such as may be stored in beacon location database265, does not match the status indication, the PSS120may determine that there is an update pending that has not been applied by the beacon240. In some implementations, the PSS120will record which updates have been acknowledged by the beacon240and will discard status indications that do not indicate the most recent version. For example, the beacon240may apply and acknowledge two updates, and the PSS120may discard any stale messages including a status indication reflecting only the first update to be applied.

At1204, the PSS120retrieves a previously stored update from memory. As described above, the update may be stored in the beacon location database265or any suitable file system. In some implementations, updates may be submitted to PSS120simultaneously by role authorized user603in beacon configuration update1002. The PSS120may divide simultaneously received updates into individual updates that may be atomically applied. For example, role authorized user603may use a web interface, such as a website that is configured to assist with beacon management, to submit configuration updates to beacon240that update the physical radius, change the power saving settings, and include the beacon240in a daisy chain. The PSS120may divide and/or combine the updates in any suitable manner so that they may be applied in individual, atomic messages. In some implementations, the PSS120will check for conflicting updates and order or delete pending updates to avoid transmissions or reordering client updates in a way that introduces erroneous behavior. For example, if role authorized user603submits two updates to the physical radius of beacon240, the PSS120may not send the earlier submitted update because its effect would be nullified by the later submitted update. In some implementations, the PSS120will prompt role authorized user603if they would like to rescind a submitted update. In some implementations, the role authorized user can directly cancel pending updates with the PSS120.

At1206, the PSS120generates a nonce, which can include any information used to uniquely identify a packet or update. The nonce may be a unique packet or update id, an expected beacon status, e.g. battery level or uptime, a repeat of the information used for anti-spoofing, or any suitable information that will prevent updates in duplicated packets from being applied more than once. In some implementations, when an update does not fit in a single local or wide area network packet, the PSS120will generate an update id nonce for the update and a packet id nonce for each packet. At1208, the PSS120generates a data packet that includes the nonce and a suitable amount of update data. For example, the PSS120may fit the entire update into a single packet or constrain the size of the update to the maximum or minimum size of data packets in either network standard. In some implementations, the PSS120will allow the beacon240to ensure the integrity of the packet data by including a checksum or some other suitable means.

At1210, the PSS encrypts the data packet and transmits the data packet to a client device102. The encryption is performed as described above. In some implementations, the PSS120and beacon240share an encryption key, which may update routinely. In some implementations, the PSS120and beacon240have individual pairs of public and private keys that are used to encrypt update packets, such as beacon update message1006ainFIG. 10. In some implementations, the update will be encrypted by the PSS120prior to being split into data packets and decrypted by the beacon240once all of the update packets have been received. This may allow for the PSS120to prepare updates, e.g. when the local network packet size is unknown, such that the updates can be repackaged or resized for the local network by the client device102.

The PSS120transmits the encrypted update packet to a client device102, such as the device that forwarded beacon status message1004binFIG. 10. In some implementations, PSS120stores, for example in the beacon location database265, the network addresses of the client devices that have recently forwarded a message from the beacon240. The PSS120may use timestamps, a queue, or any other suitable means to determine which client devices102forwarded beacon messages most recently. The PSS120may send beacon update message1006ato a different client that is likely to be within range of a beacon. For example, the beacon status message1004bcan indicate that the forwarding client device102received the message because it was leaving the range of beacon240and is therefore unlikely to be suitable for forwarding the update. In some implementations, when there are multiple beacon status messages1006afor a single update, the PSS120may forward the messages through multiple client devices, and the beacon240may combine packets from the clients such as in a torrent or peer to peer download model. The PSS120may also use a single client device102with unreliable network connectivity. Since updates are accounted for at a per message level, the client device102can lose and regain connectivity with the either of the local or wide area networks in the middle of transmitting an update without needing to re-download the entire update. In some implementations, PSS120forwards beacon update message1006ato a known access point, e.g. a point of sale (POS) device (e.g. a register) enabled to access the local area communication protocol. A known access point may have a large broadcast range that may be used to reliably send updates to beacons in an area relatively large compared to the physical radius of beacon240. In some implementations, the beacon240may be configured to expand its physical radius in response to receiving a broadcast from the known access point. At1212, the PSS120determines whether the entire update has been transmitted, e.g. if fewer than the required number of packets were sent, and returns to1206to continue transmitting the remaining update data.

FIG. 13shows a flow chart illustrating an exemplary process of receiving and unpacking an update at a beacon, according to some embodiments. In general, the process1300involves a beacon240receiving one or more beacon update messages1006bfrom one or more client devices102(as inFIG. 10), decrypting and verifying the beacon update messages1006b, and committing the update to memory once all update data has been received. As shown, the process1300includes receiving a beacon update message (1302) and decrypting the received beacon update message (1304). Once the update message is decrypted, the beacon240verifies that the message is an authentic update from the PSS120that needs to be applied (1306). The beacon240also checks whether it has received all of the messages in the update (1308), and, if yes, commits the decrypted update data to memory to apply the update (1310).

At1302, the beacon240receives a beacon update messages1006bfrom one or more client devices102(as inFIG. 10). The beacon update message1006bis received over the local area communication protocol, e.g. Bluetooth, and can be used to change any of the parameters that are configurable by the beacon. For example, the configuration parameters may include, but are not limited to the status of logical radii, the physical broadcast radius, power-saving parameters, system update information, and/or the like. The beacon update message1006bmay also contain all or part of an update to the firmware running on beacon240. At1304, the beacon240decrypts beacon update message1006b. The decryption may be performed using a secret key that is shared with the PSS120, a private key held on the beacon, or any other suitable decryption means.

At1306, the beacon240checks the nonce in the update message1006bin order to validate the update message, which includes determining whether the update is new, intended for the beacon240, and otherwise suitable for being applied to memory. In some implementations, the update message nonce is a unique sequence number given to each update message. The beacon240uses the nonce to determine whether the update message1006bhas been previously received by comparing the nonce to previously received nonces, for example if the network errors lead to re-transmissions or if a nefarious device is replaying an update message. Previously received update messages1006bmay be discarded if the update payload was previously applied, and, in some implementations, the beacon240acknowledges duplicated updates to counter the effect of lost acknowledgements. In some implementations, the beacon240applies updates in the order they were received by the PSS120, e.g. as indicated by increasing sequence number or nonce. Update messages that are not contiguous with previously applied updates may be cached in memory by the beacon240and applied when any cached update is determined to be the next update in the sequence. In some implementations, the beacon update message1006bincludes a checksum, which may be in the encrypted portion of the message that can be used to detect or correct errors in the unencrypted update data. This prevents network errors or tampering client devices from corrupting the configuration of beacon240by corrupting the encrypted update message1006b. The checksum may be a hash function output, parity data, an error correcting code, or any suitable means.

At1308, the beacon240checks whether the entire update has been received. In some implementations, the beacon240looks for a terminating character that indicates the end of an update. In some implementations, the PSS120includes an indication of the size of the update, the number of packets used to transmit the updates, or any other suitable metadata that can be used by the beacon240to determine the necessary details of an update. If the update has not been received in its entirety, the beacon240stores the received update data in a cache or buffer in persistent or volatile local memory and waits for the missing update messages containing the remaining update data. In some implementations, updates involving multiple messages are cached, and not applied, until the entire update is received to avoid the possibility of corrupting memory or configuration settings with a partial update. At1310, once the beacon240determines that the entire updates has been received and verified, the update is performed by committing the update data to memory such that the changes specified in update are made effective.

In some implementations, the beacon240is in communication with other beacons over the local area communication protocol. The beacons may be configured to collect routing information and otherwise act in order to form a mesh network that allows for communication between groups of beacons that can be reached over the local area communication protocol. The beacons may use distance-vector routing, link state routing, or any suitable routing protocol. The beacon240may also record the senders of broadcasts that the beacon240observes over the local communication protocol and transmit a list of the observed beacons to the PSS120, which can use the information to construct a network topology that indicates the ranges of neighboring nodes. The PSS may also automatically construct such a network topology by using records, e.g. entries in the beacon location database265, of beacon location, beacon id, and beacon physical radii to determine which beacons are likely to be within range of one another. Once a suitable network topology, which may be limited to a beacon240being aware of its neighboring beacons, is determined, the beacon240can be used to forward updates to other beacons. The PSS120may include in beacon update message1006ban indication of which beacons should receive the update, instructions for forwarding the message, which may be encrypted as in an onion routing protocol, or any information suitable for distributing updates through the mesh network.

While various embodiments of the present disclosure have been shown and described herein, it will be apparent to those skilled in the art that such embodiments are provided by way of example only. Numerous variations, changes, and substitutions will now occur to those skilled in the art without departing from the disclosure. It should be understood that various alternatives to the embodiments of the disclosure described herein may be employed in practicing the disclosure. Generally, the computerized systems described herein may comprise one or more local or distributed engines, which include a processing device or devices, such as a computer, microprocessor, logic device or other device or processor that is configured with hardware, firmware, and software to carry out one or more of the computerized methods described herein.