Patent Grant
11202171
This invention relates generally to the wireless communication field, and more specifically to a new and useful system and method for providing contextual content in the wireless communication field. This invention relates generally to the portable display field, and more specifically to a new and useful portable card display in the information display field.
The following description of the preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.
1. Overview
As shown in
2. Application Examples
In one variation of the method 100, a beacon system 405 is connected to a user output (e.g., display), where the beacon controls content presented by the output device. The output device can additionally power the beacon. Upon user device wireless connection with the beacon system 405 (e.g., upon user device entry into the beacon system's communication range), the beacon system 405 can wirelessly connect with the user device and control the output device to present contextual content specific to the user associated with the user device. Upon user device disconnection from the beacon system 405 (e.g., upon user device egress from the beacon system's communication range), the beacon system 405 can switch to operation in a standby mode, where the beacon system 405 controls the output device to present standby content (e.g., default content).
In a first example of the method 100 (example shown in
In the first example, the beacon preferably operates as a slave device in a standby mode and broadcasts a unique identifier associated with the beacon system 405. Upon user device entry into the beacon system's communication range, the user device receives the unique identifier from the beacon system 405, requests authorization to connect to the beacon system 405 from a remote computing system (e.g., remote server system), and connects to the beacon system 405 upon authorization. The user device can additionally be concurrently connected to, and receive data from (e.g., sensor data), supplementary beacon systems 408. Upon user device connection to the primary and supplementary beacon systems 408, the remote computing system can determine (e.g., generate, select, etc.) contextually-relevant retail content for the user and send the content to the beacon system 405 (e.g., directly to the beacon system 405 or indirectly, through the user device), where the beacon system 405 controls the display to display the contextually-relevant retail content to the user in near-real time.
Additionally or alternatively, the beacon system 405 can operate as a master device in the standby mode, and monitor (e.g., detect, scan), update, and/or otherwise manage supplementary beacon systems 408 within the physical area (example shown in
In specific examples, the beacon system 405 can be used for presenting alerts, maps, and/or other relevant information to users. The beacon system 405 can be used in one or more of: urban landscapes (e.g., city maps depicting the geographic locations of destinations marked as favorites in a user device; alerts regarding nearby public transportation; etc.), arenas (e.g., maps of sports venues, concert venues, and/or other recreational venues to guide a user to the seat number designated in their user device, etc.), museums (e.g., providing user-tailored content for an exhibit), airports (e.g., multiple screens displaying personalized flight information and updates tailored to where the user is going as the user passes by the screens, etc.), industrial settings (e.g., presenting hands-free information such as schedules or tasks to industrial workers, etc.), events (e.g., presenting updates to agendas, etc.), meetings (e.g., displaying the tasks completed and the future action items for each of the individuals in the meeting, etc.), advertising (e.g., targeted advertising to consumers based on their user device information, etc.), and/or any other suitable applications.
3. Benefits.
The beacon system can confer several benefits over conventional systems. First, the beacon system can be configured to receive and control the presentation of user-specific content on a connected user output, which functions to present curated, personalized information to the user in near-real time in a format different than that permitted by the user device.
Second, by using a short-range communication technology, the beacon system can be associated with a limited physical area. This can allow beacon connection with a user device to be used as a proxy for physical user proximity to the beacon and/or physical area associated with the beacon.
Third, in some variations, the beacon system can operate as a slave device when connected to the user device. This can function to limit the number of user devices concurrently connected to the beacon system, which can function to limit the presented contextual information to that of a single user. This can have the additional benefit of minimizing customer confusion. Fourth, in some variations, the beacon system application can motivate a user to leave the beacon system substantially constantly physically plugged into a power source (e.g., a display), which can remove the energy constraint encountered by conventional beacon systems. By removing this energy constraint, the beacon can transmit, scan, and/or perform other energy-intensive tasks at a higher frequency, even constantly.
Fourth, in some variations, a single beacon system can operate within a network of multiple supplementary beacons, user devices, applications executing on the user devices, output devices and/or any other suitable number of auxiliary devices. In some variations, multiple beacon systems can communicate within the network to schedule content display amongst corresponding output devices, display complementary content, and/or be used for any other suitable purpose.
Fifth, the technology can confer an improvement to the functioning of computer-related technology. In a first example, the technology can amount to an inventive distribution of functionality across a network of one or more: beacon systems (e.g., leveraging continuous power draw from the output device to support continuous broadcasting, monitoring of supplementary beacons, content transmission to the output device, and/or other suitable functions amounting to an improvement in the beacon system, etc.), supplementary beacons (e.g., offering portability by being able to be placed on different items, and contextual sensor data for determining contextual content), user devices (e.g., acting as a communication hub between the beacon system, supplementary beacons, and the content determination system), content determination systems (e.g., determining the contextual content), output devices (e.g., presenting the contextual content), and/or any other suitable components. In relation to the network, the technology can include determining supplementary beacon-output device interaction parameters (e.g., proximity, communication protocol, etc.), supplementary beacon-user device interaction parameters (e.g., proximity, relative motion), and/or any other interaction parameters. In a second example, the technology can facilitate performance of functions not previously performable (e.g., improving upon existing processes as opposed to applying a tool to perform an existing process). The technology can apply computer-implemented rules (e.g., content determination rules, beacon network communication rules, etc.) with improvements in beacon technology (e.g., the beacon system continuously drawing power from the output device in order to enable the power-intensive transmission of content to the output device; micro-location determination; beacon communication through Bluetooth Low Energy, etc.) to determine and deliver contextual content. In a third example, the technology can improve beacon network security, such as by limiting communication of the beacon system with user devices using cloud-based authentication, data-exchange protocols with enterprise-grade encryption and security algorithms, and/or applications implementing a first party (e.g., Estimote™) software development kit (SDK). In a fourth example, the technology can improve digital privacy associated with delivering contextualized content, such as by enabling permission-based user preferences for shared data, content determination, content presentation (e.g., permitting specific third party entities to display content; permitting specific content; controlling presentation parameters such as presentation duration; etc.).
Sixth, the technology can transform a particular article to another state or thing. For example, the technology can transform one or more of: an output device (e.g., controlling an output device to display standby content and/or contextual content using the beacon system, etc.), a beacon system (e.g., controlling the beacon system to operate between master and slave modes to fulfill different purposes, etc.), and/or other suitable components.
However, the technology can provide any other suitable benefits in the context of using non-generalized systems for contextualizing and/or delivering content.
4. Auxiliary Devices.
The method 100 is preferably performed in whole or in part with one or more auxiliary devices, which can include any one or more of: output devices, user devices, remote computing systems, supplementary beacons 408, merchant devices (e.g., point-of-sale devices, merchant smartphones, merchant appliances, etc.), and/or any other suitable auxiliary devices. The system 400 can include or omit auxiliary devices.
The method 100 can be performed in whole or in part with an output device, which functions to output data provided by the beacon system 405. The output device can additionally function to output any other suitable information. The output device is preferably an output display, but can be any suitable output device. The output device is preferably associated with a third party entity (e.g., a retailer, airport, etc.), but can additionally or alternatively be associated with a user, application provider (e.g., developer), and/or any other suitable entity. The output device is preferably physically connected to the beacon system 405 (e.g., the data connector 440 of the beacon system 405), but can additionally or alternatively wirelessly connect to the beacon system 405 and/or otherwise connect to the beacon system 405. The output device is preferably statically mounted to a wall, door, and/or other physical boundary of a physical space, where the beacon is associated with the physical position of the output device within the physical space. Alternatively, the output device can be mobile, such that the beacon-display assembly functions as a roaming contextual device. Examples of the output device include a display, microphone, and/or any other suitable user output. Examples of the display include: a television, projection system, speakers, and/or any other suitable output system capable of presenting information. However, the output device can be otherwise configured.
The method 100 can additionally be performed in whole or in part with a user device, which functions to detect and/or temporarily connect to the beacon system 405 when physically proximal the beacon system 405. The user device can additionally function to concurrently detect and/or temporarily connect to one or more supplementary beacon systems 408. The user device can additionally function to send and/or receive data from a remote computing system, send and/or receive data from the beacon system 405 and/or supplementary beacons 408, generate the contextual content, and/or perform any other suitable functionality. The user device can be a tablet, smartphone, smartwatch, mobile phone, laptop, watch, wearable device (e.g., glasses), and/or be any other suitable user device. The user device preferably includes power storage 460 (e.g., a battery) and a processor, and can additionally include a display, a user input (e.g., a keyboard, touchscreen, accelerometer, microphone, etc.), a location system (e.g., a GPS system), a data communication system (e.g., a WiFi module, cellular module, etc.), and/or any other suitable component. The user device can execute one or more native applications, where one or more of the native applications can be associated with the third party entity. However, the user device can be otherwise configured.
The method 100 can additionally be performed in whole or in part with a content determination system (e.g., remote computing system), which functions to control application access permissions to the beacon system 405 and/or user information, generate contextual content, transmit contextual content, manage beacon identifiers, and/or perform any other suitable functionality. The content determination system preferably includes a remote computing system, which can include a remote server system, but can alternatively be a set of user devices (e.g., a distributed network of user device), a set of beacon systems, and/or be any other suitable set of networked computing systems. However, the content determination system can be otherwise configured.
The method 100 can additionally be performed in whole or in part with one or more supplementary beacons 408, which function to identify physical objects and/or locations within the physical space. The supplementary beacons 408 preferably function as slave devices, but can constantly or periodically function as master devices as well. The supplementary beacons 408 are preferably identified by a unique supplementary beacon identifier, but can alternatively be otherwise identified. The supplementary beacons 408 preferably broadcast the supplementary beacon identifier periodically, continuously, when a trigger event occurs, and/or at any other suitable time. The broadcast supplementary beacon identifier can be received by the user device, beacon system(s), other supplementary beacons 408, and/or by any other suitable device proximal the supplementary beacon 408. In a variation, the broadcast supplementary beacon identifier can include supplementary beacon sensor data. In another variation, the supplementary beacon 408 can broadcast sensor data and/or other suitable data independently of the supplementary beacon identifier. The supplementary beacons 408 can include a radio 420 (e.g., sharing the same band or technology as the beacon system 405), power source 430 (e.g., battery), sensors (e.g., accelerometers, gyroscopes, temperature sensors, etc.), mounting mechanism (e.g., adhesive), and/or any other suitable component. Additionally or alternatively, the supplementary beacon 408 can be defined in any manner analogous to that described in U.S. application Ser. No. 15/288,302 filed on 7 Oct. 2016. However, supplementary beacons 408 can be configured in any suitable manner. Further, any type of auxiliary device can be configured in any suitable manner.
5. Beacon System.
As shown in
The system 400 functions to present contextually-relevant content to a user on one or more screens in real- or near-real time. However, the method 100 can be performed with any other suitable system. The system 400 can additionally function to monitor slave beacons within the physical space, such that missing beacons can be automatically identified and reported to an entity associated with the physical space. The system 400 can additionally manage slave beacons within the physical space, such as by pushing updates to the slave beacons, receiving operation data from the slave beacons, forwarding slave beacon data (e.g., accelerometer data, etc.) to the remote computing system, and/or otherwise managing the slave beacons within the space. The system 400 can additionally function as a substantially static physical marker, such that a user to easily create geofences within the physical space using the relative member locations of a beacon population. The system 400 can additionally function as a repeater or node of a mesh network, such that the system 400 can physically extend the data connectivity and transmission range of a beacon population. However, the system 400 can perform any other suitable function.
The beacon system 405 is preferably operable between one or more modes. In one example, the beacon system 405 can be operable between: a standby mode, when the beacon system 405 is not connected to any user devices and/or supplementary beacons 408, and a connected mode, when the beacon system 405 is connected to one or more: user devices and/or supplementary beacons 408. The beacon system 405 preferably functions as a slave device in both modes, but can additionally or alternatively function as a master in one or both modes. The beacon system 405 can additionally or alternatively be operable in a monitoring mode, where the beacon system 405 can function as a master device and scan for supplementary beacon identifiers within the beacon system's communication range. The beacon system 405 can be periodically switched between the operation modes, change operation modes in response to the occurrence of a trigger event (e.g., user device connection), and/or change operation modes in any other suitable manner. System operation mode transition can be controlled by: the beacon system 405 itself, the beacon system 405, the remote computing system, the user device, a supplementary beacon 408, a combination thereof, and/or be controlled by any other suitable computing system. In a variation, the beacon system 405 can operate concurrently in a plurality of modes using a plurality of radios (e.g., one for each mode). For example, the beacon system 405 can concurrently operate in a connected mode (e.g., connected to a user device), a monitoring mode (e.g., monitoring for broadcasts of supplementary beacon identifiers from supplementary beacons 408), and a broadcasting mode (e.g., broadcasting a beacon identifier identifying the beacon system 405 in a slave mode). However, the beacon system 405 can be operable in any number of and/or types of suitable modes using any suitable number of radios.
The beacon system 405 is preferably identified by one or more beacon identifiers. The beacon identifier can be locally unique, globally unique, or non-unique. The beacon identifier can be public, private, semi-private (e.g., available to many, but not all, user accounts or applications), and/or have any other suitable set of permissions. In one variation, the beacon system 405 is preferably identified by both a temporary short identifier and a permanent long identifier, where the short identifier is broadcast and/or otherwise sent to other devices and the permanent long identifier is used by the beacon identifying system to uniquely identify the beacon system 405. Alternatively, the beacon system 405 can be associated with a single identifier. When the identifier is temporary, the identifier or rules for identifier generation can be assigned to the specific beacon system 405 by the identifying system, and/or be otherwise determined. The one or more beacon identifiers can be modified (e.g., customized to a custom identifier; to include beacon sensor data; etc.) by an authorized entity (e.g., a third party entity owning the beacon tracked for identified by the beacon identifier). Modifications to beacon identifiers can be tracked by the content determination system (e.g., by associating the modified beacon identifier with content for display at an output device). In a specific example, the beacon identifier can be managed in the manner disclosed in U.S. application Ser. No. 14/463,597 filed 19 Aug. 2014, which is incorporated in its entirety by this reference. In a variation, the different beacon identifiers can be associated with different content (e.g., to be displayed at a corresponding output device). For example, the system 400 can include a first beacon system 405′ identified by a first beacon identifier associated with a first content template, and a second beacon system 405″ identified by a second beacon identifier associated with a second content template. However, beacon identifiers can be otherwise defined and/or managed.
The radio 420 of the beacon system 405 functions to transmit and/or receive data. The data can include a unique identifier identifying the beacon system 405, unique identifiers identifying supplementary beacons 408, beacon system parameters (e.g., beacon sensor data, beacon operation history, etc.), content data, and/or any other suitable data. The data can be transmitted to and/or received from: the user device, the remote system, a supplementary beacon 408, a second beacon system 405″, the output device, and/or any other suitable endpoint. The data can be broadcast or advertised (e.g., to any listening or scanning device), sent to a targeted endpoint, and/or be otherwise communicated. The beacon system 405 preferably includes one or more radios 420, where multiple radios 420 can be of the same or different type (e.g., a Bluetooth radio and a WiFi radio). The radio 420 is preferably for a short-range communication technology, but can additionally or alternatively be for a long-range communication technology. Examples of the radio 420 include: a Bluetooth radio (e.g., Bluetooth low energy radios), a WiFi radio, a WLAN radio, a WiMAX radio, a Zigbee radio, a NFC radio, and/or any other suitable short or long range repeater, extender, protocol translator, and/or other suitable means for conducting a one-way or two-way communication protocol. In a specific example, the radio includes a 2.4 GHz BLE radio. The beacon system 405 can include any number of radios typifying any suitable type. In a specific example, as shown in
The radio 420 preferably includes a transceiver and an antenna 422, but can additionally or alternatively include any other suitable component. The transceiver can be integrated in to the processing system 450, or be separate. The antenna 422 can extend along the beacon system length (e.g., along the longitudinal axis, along the inner or outer perimeter, etc.), extend along the beacon system width, and/or extend along any other suitable portion of the beacon system 405. In a specific example, the radio 420 can be arranged within a rigid segment of the flexible housing, where the radio 420 includes an antenna extending through a flexible segment of the flexible housing. The antenna 422 is preferably arranged distal the data connector (e.g., to avoid electromagnetic interference), but can alternatively be arranged proximal the data connector 440 and/or be arranged in any other suitable location on the beacon system 405. However, the radio 420 can include any suitable components configured in any suitable manner.
The power source 430 of the beacon system 405 functions to power the beacon system components. The power source 430 is preferably wired to the powered components, but can alternatively be wirelessly connected to the powered components (e.g., via induction). The beacon system 405 can include one or more power sources 430 of the same or different type. In a first variation, the power source 430 is a battery housed within the beacon system 405. The battery is preferably a secondary battery (e.g., rechargeable battery), but can alternatively be a primary battery or be any other suitable battery. Examples of the battery can include lithium chemistry batteries, nickel cadmium batteries, CR2477 batteries, or any other suitable battery. As shown in
The data connector 440 of the beacon system 405 functions to transfer data from the beacon system 405 to the output device. The data connector 440 can additionally or alternatively function to receive data from the output device, function as a structural component that mounts the beacon system 405 to the output device, function to power the beacon system components, and/or perform any other suitable functionality. The beacon system 405 can include one or more data connectors 440 of the same or different type. The data connector 440 is preferably wired, but can alternatively be wireless. The data connector 440 can include: a video connector, an audio connector, and/or a connector for any other suitable data. The data connector 440 is preferably arranged along a first end of the beacon system 405, but can alternatively be arranged along the beacon system body and/or along any other suitable portion of the beacon system 405. Examples of the data connector 440 include an HDMI connector, Thunderbolt™ connector, VGA connector, Apple™ display connector, DVI connector, antenna plug, NBC connector, C connector, GR connector, DIN connector, RCA connector, audio jack, and/or any other suitable connector. However, the data connector 440 can be configured in any suitable manner.
The processing system 450 of the beacon system 405 functions to control unique identifier broadcasting, control data transfer between the beacon system 405 and the user device, control data transfer between the beacon system 405 and remote computing system, manage beacon system operation between the set of operation modes, and/or perform any other suitable functionality. The beacon system 405 can include one or more processing systems 450 of the same or different type. The processing system 450 can be a CPU, GPU, microprocessor, or be any other suitable processing system 450. The processing system 450 can additionally include memory (e.g., RAM, flash), and/or include any other suitable component. In a variation, the processing system 450 can function to determine contextual content to transmit to the output device to serve to a user. In this variation, the beacon system 405 can act as the content determination system. In an example, the processing system 450 can receive supplementary beacon information (e.g., supplementary beacon identifiers, supplementary beacon parameters, etc.) and/or user device information (e.g., user device identifiers, application identifiers, sensor data, etc.) transmitted to the beacon system 405 (e.g., at the radio); determine contextual content (e.g., extracting values from the supplementary beacon information and/or user device information; fill content templates stored at storage 460 of the beacon system 405 with the values; etc.), and transmit the contextual content to the output device (e.g., through a wired HDMI connector). In another variation, the processing system can 450 can determine default standby content to transmit to the output device. In another variation, the processing system manages beacon identifier broadcasting and/or receipt, wherein content determination is performed by a remote computing system (e.g., server system). However, the beacon system 405 can otherwise perform any suitable functionality associated with the content determination system.
The beacon system 405 and/or supplementary beacons 408 can additionally include a set of sensors that function to monitor beacon operation parameters (e.g., beacon system parameters, supplementary beacon parameters). Beacon operation parameters can include beacon parameters (e.g., power storage SOC, user connection frequency, connection status to other devices, internal temperature, physical orientation, etc.), environmental parameters (e.g., ambient temperature, ambient light, ambient noise, etc.), motion parameters, and/or include any other suitable parameter. The beacons (e.g., beacon system 405, supplementary beacons 408, etc.) can include one or more sensors of the same or different type. The sensors can include one or more of: an accelerometer, gyroscope, altimeter, microphone, transducer, temperature sensor, light sensor, and/or be any other suitable sensor.
As shown in
Additionally or alternatively, the beacon system 405 can be integrated (e.g., built into) the output. However, the beacon system 405 can include any other suitable component (e.g., storage 460), and/or be configured in any suitable manner.
6. Method.
As shown in
In a first embodiment, the method 100 for personalizing and delivering content using beacons can include, while a beacon system is communicably coupled to an output display: a) broadcasting a beacon identifier identifying the beacon system from the beacon system to a user device; b) receiving the beacon identifier (and/or user identifier) at a content determination system from the user device; c) determining contextual content at the content determination system based on the beacon identifier (and/or user identifier); d) transmitting the contextual content from the content determination system to the user device, where the user device automatically transmits the contextual content to the first beacon system in response to receiving the contextual content; e) receiving the contextual content at the beacon system from the user device; and f) controlling the output display with the beacon system to present the contextual content. In this or other embodiments, any portions of the method 100 can be performed concurrently, serially, and/or in any suitable temporal relationship with other portions of the method 100. For example, in the first embodiment, the method 100 can include: concurrently with performing a) through f), continuously broadcasting the beacon identifier with the beacon system for receipt by a second user device.
In a second embodiment, the method 100 can include, while a beacon system is drawing power from an output display through a wired connection: receiving, at a content determination system, a beacon identifier identifying a beacon; determining contextual content with the content determination system based on the beacon identifier; receiving the contextual content at the beacon system; and sending the contextual content from the beacon system to the output display through a second wired connection. In this embodiment, the beacon can be the beacon system, a supplementary beacon, and/or other suitable beacon. Additionally or alternatively, the content determination system can be the beacon system, a remote computing system, and/or other suitable component.
The method 100 functions to present contextually-relevant content to a user on one or more screens in real- or near-real time. The method 100 can additionally function to monitor slave beacons within the physical space, such that missing beacons can be automatically identified and reported to an entity associated with the physical space, updates can be pushed to the slave beacons, slave beacon operation data can be received from the slave beacons, and/or perform any other suitable functionality. The method 100 is preferably performed using the system described above, but can additionally or alternatively be used with any other suitable system.
Receiving a beacon identifier associated with a physical space S100 functions to associate the user device with beacon system, such that targeted content can be generated for the user associated with the user device. Receiving the beacon identifier can additionally function to associate the user device with the physical location or volume proximal the beacon system. The beacon identifier is preferably received by a content determination system (e.g., remote computing system), but can additionally or alternatively be received by any other suitable endpoint. The content determination system can receive the beacon identifier from the master device (e.g., the beacon system or the user device, etc.), an intermediate entity (e.g., an application executing on the master device, the output device, etc.), and/or from any other suitable endpoint. The beacon identifier is preferably a beacon packet using the beacon protocol, but can alternatively be audio patterns, light patterns, and/or any other suitable signal emitted by the beacon or by a connected output device. However, the unique identifier can be received in any other suitable manner.
Receiving the beacon identifier can additionally or alternatively include receiving a user device identifier, which functions to identify the user associated with the user device. The user device identifier is preferably received by the content determination system via the master device (e.g., the user device or the beacon system), but can additionally or alternatively be received by any other suitable endpoint. In a first variation in which the user device is the master device, the user device can send the user device identifier with the received beacon identifier to the content determination system. The user device can additionally send an entity identifier associated with an entity (e.g., Nike™) or application identifier for the application that received the beacon identifier (e.g., Nike™ application) to the content determination system. In a second variation in which the beacon system is the master device, the beacon system can send the received user device identifier to the content determination system with the beacon identifier. However, the user device identifier can be otherwise received.
The method 100 can additionally or alternatively include receiving a supplementary beacon identifier, which functions to identify that a physical object or location associated with the supplementary beacon is proximal the master device. The supplementary beacon identifier is preferably received by the content determination system via the master device (e.g., the user device or the beacon system), but can additionally or alternatively be received by any other suitable endpoint. In an example, the method 100 can include continuously monitoring (e.g., with a beacon system; with the master device; etc.) for beacon identifiers (e.g., supplementary beacon identifiers broadcast by a supplementary beacon; other beacon system identifiers; etc.), which can be performed concurrently with any other suitable portion of the method 100. The supplementary beacon identifier is preferably received from within a predetermined time frame from beacon identifier receipt (e.g., 1 minute before or after beacon identifier receipt), but can alternatively be received outside of the time frame. The predetermined time frame is preferably equal to or otherwise determined based on the broadcasting frequency of the supplementary beacon or beacon system, but can be manually set or otherwise determined. The supplementary beacon identifier is preferably received from the same master device, but can additionally or alternatively be received from a different device. In a first variation in which the user device is the master device, the user device can detect both the supplementary beacon and beacon system (concurrently or serially) and send the respective identifiers to the content determination system (concurrently or serially). In a second variation in which the beacon system is the master device, the beacon system can detect the user device and/or the supplementary beacon (concurrently or serially). In this variation, the respective information (e.g., user device information, supplementary beacon information, etc.), can be transmitted from the beacon system to the content determination system (e.g., concurrently or serially; directly or indirectly such as through the user device); used by the beacon system in directly determining contextual content (e.g., where the beacon system acts as the content determination system); and/or used in any suitable manner. However, the supplementary beacon identifier can be otherwise received.
Receiving the supplementary beacon identifier can additionally include receiving supplementary beacon parameters (e.g., supplementary beacon sensor data), which functions to provide context about the physical object or location tagged with the supplementary beacon. In one example, the supplementary beacon parameters can be used to determine whether a user (associated with the user device) has physically picked up a product tagged with the supplementary beacon. However, receiving supplementary beacon parameters can be otherwise performed.
Determining content S200 functions to select or generate contextual content relevant to a user. The content (e.g., contextual content) is preferably automatically determined by the content determination system, but can alternatively be manually selected or determined by any other suitable system. The content determination system can be the remote computing system, the user device, the beacon system, a supplementary beacon, combination of the above, and/or any other suitable computing system.
The content can be determined using machine learning techniques (e.g., regression, classification, etc.), probabilistically, deterministically, and/or otherwise determined. When machine learning techniques are used, the machine learning modules can be updated periodically; in response to and based on subsequent user action (or non-action), as determined based on the user purchase history; or updated in any other manner at any suitable time. The content is preferably generated, but can alternatively be selected from a predetermined set of content, or be otherwise determined. The content is preferably generated from the predetermined set of content pieces, but can alternatively or additionally be generated from social network streams (e.g., associated with the product entity, physical space entity, user, etc.) and/or any other suitable content source. The predetermined set of content pieces can include stock images, content templates, or any other suitable set of content. The predetermined set of content pieces can be received from a third party (e.g., an entity associated with the physical space, product, output device, advertiser, etc.), and/or be otherwise provided. The content can be generated using machine learning techniques (e.g., regression or classification), using a predefined formula, and/or be otherwise generated. The content can be generated based on one or more of: beacon system information (e.g., beacon identifier, beacon system parameters such as beacon system location and/or beacon sensor data), entity associated with the beacon (e.g., the merchant), entity preferences associated with the entity, entity associated with the application executing on the user device, the identifier for the application executing on the user device, user device information (e.g., sensor data, user device identifier; can be read from user device or sent by user device to server), user profile associated with the user device (purchase history, preferences, physical browse history, upcoming flights, automatically generated from social media, etc.), supplementary beacon information (supplementary beacon identifier, supplementary beacon parameters, etc.), interaction duration, general contextual information (e.g., time of day, weather, etc.), user contextual information (e.g., calendar, social media, etc.), and/or any other suitable information.
In a first variation, the content is determined based on beacon system information (e.g., beacon identifiers, beacon system parameters, etc.). In a first embodiment, the content is determined from the predetermined set of content or content pieces associated with the beacon identifier. In this embodiment, the content determination system can store the predetermined set of content or content pieces in association with the beacon identifier and/or otherwise access the predetermined content set. For example, a video for a retail store can be selected for a beacon identifier associated with the retail store. In a second embodiment, the content is generated based on content or content pieces associated with a context, where the context is associated with the beacon identifier. The context can be provided by the third party, be automatically determined (e.g., based on subsequent user device history after beacon connection or beacon identifier detection), and/or be otherwise determined. For example, a cooking video can be selected for a beacon identifier associated with kitchens. However, determining content based on beacon system information can be performed in any suitable manner.
In a second variation, the content is generated based on user device information (e.g., user device identifiers, application identifiers, sensor data, etc.). In a first embodiment, the beacon identifier is associated with the content template and types of content to retrieve, and the user device identifier is associated with the content source. The content source can be: a social network stream (e.g., the social network account associated with the user device), a social network (e.g., connections of the user on the social network account), content associated with the user purchase history or user browsing history (e.g., based on the products associated with supplementary beacons that the user had historically interacted with, picked up, loitered near, etc.), and/or be any other suitable content source. In this embodiment, determining the content can include filing out the template with content from the content source. For example, in response to receipt of a beacon identifier associated with a retail brand, the system can generate a composite image from photographs of the user's friends wearing the brand products extracted from the user's social networking system content stream.
In a second embodiment of the second variation, the beacon identifier can be associated with a set of content, and the user device identifier can be associated with a data source, where the content is selected from the set of content based on parameters extracted from the data source. The set of content can be provided by the third party, retrieved from the content source as discussed above, and/or be any other suitable content. The data source can include: the content source as discussed above, a user profile (e.g., manually entered by the user, automatically generated, etc.), a calendar associated with the user, communiqué associated with the user (e.g., emails), and/or any other suitable data source. The data source can be stored by the content determination system, received from a third party, received from the user device, retrieved based on permissions received from the user device, and/or otherwise obtained. In this embodiment, determining the content can include extracting feature values from the data source, classifying the user based on the feature values, and selecting the content based on the determined user class. In a first example, the user associated with the user device can be classified as a dog owner, based on purchase history, products historically interacted with, and digital browsing history. The type of dog can additionally be verified based on the user's social network stream. In this example, determining the content can include selecting content targeted toward or having a high conversion rate with dog owners. In a second example, when the beacon system is associated with an airport, the user's email can be filtered for confirmations of flights within a predetermined time duration of a reference time (e.g., time that the beacon identifier was recorded by the user device, the instantaneous time, etc.), and the flight information for the confirmed flight is retrieved as the content.
In a third embodiment of the second variation, the content can mirror application content served by and/or generated by one more applications executing on the user device. In an example, the method 100 can include providing a software development kit for developing applications interacting with the beacon system; and mirroring, with the beacon system controlling the output device, content generated by an application developed using the software development kit and executed by the user device. However, the content can be otherwise determined based on user device information.
In a third variation, the content is determined based on supplementary beacon information (e.g., supplementary beacon identifiers, supplementary beacon parameters, etc.). The supplementary beacon identifier can be received from the user device, the beacon system, and/or any other suitable device. The content is preferably selected from a set of predetermined content associated with the supplementary beacon identifier and/or parameters, but can alternatively or additionally be determined based on the demographic population associated with the product or location tagged with the supplementary beacon identifier, the user's demographics, and/or based on any other suitable information. In one example, the system selects the content associated with the product identified by the supplementary beacon identifier. In a second example, the system receives a first and second supplementary beacon identifier, determines that the first product is being held by a user (e.g., based on the temperature and accelerometer data recorded by the first supplementary beacon identifier within a predetermined time frame of first supplementary beacon identifier recordation), and selects content for the product associated with the first supplementary beacon identifier (e.g., to the exclusion of the content for the product associated with the second supplementary beacon identifier). In embodiments, content determination can be based on supplementary beacon information associated with a plurality of supplementary beacons. For example, the method 100 can include one or more of: selecting a subset of supplementary beacon information (e.g., filtering information from supplementary beacons attached to products irrelevant to a user based on user device information, etc.) from which contextual content can be generated; weighing different pieces of supplementary beacon information (e.g., more heavily weighting information associated with supplementary beacons proximal user devices) in determining contextual content; and/or any other suitable operation. In a specific example, the method 100 can include associating (e.g., at the content determination system) each beacon system of a plurality of beacon systems to subsets of supplemental beacons (e.g., assigning supplemental beacons to proximal beacon systems); receiving supplemental beacon information (e.g., supplemental beacon location parameters) at the beacon system from supplemental beacons associated with the beacon system; transmitting supplemental beacon information from the beacon systems to the content determination system; and determining content based on the supplemental beacon information (e.g., content illustrating the locations of contextually relevant products with supplemental beacons attached). However, determining content based on supplementary beacon information can be performed in any suitable manner.
As shown in
Determining content S200 is preferably performed in response to receiving an identifier (e.g., beacon identifier, supplementary beacon identifier, user device identifier) S100. Additionally or alternatively, determining content 200 can be performed in response to occurrence of a trigger event. Trigger events can include any one or more of: motion of a device (e.g., beacon system, user device, supplementary beacon), device connection (e.g., establishment of a communication connection between beacon system and user device), beacon operation parameter conditions, and/or any other suitable events. In a variation, a trigger event can be based on device motion (e.g., motion beyond a threshold motion parameter; movement of the device into a threshold distance from the beacon system, etc.). In a first example, detecting device motion can include: connecting (e.g., wirelessly) to a device (e.g., supplementary beacon, user device, etc.) with the beacon system; monitoring signal of the connection; determining device motion based on signal parameters (e.g., strength, direction with an directional antenna, etc.). In a second example, detecting device motion can include: sampling motion data at motion sensors (e.g., accelerometers, gyroscopes, etc.) of the device (e.g., supplementary beacon, user device, etc.). The motion data can be transmitted to any suitable component, compared to motion parameter conditions (e.g., thresholds, patterns, etc.), and/or otherwise manipulated. However, determining content can be performed at any suitable time based on any suitable criteria.
Presenting the content on an output connected to the beacon system S300 functions to present the determined content to the user. Content presentation is preferably controlled by the beacon system, but can additionally or alternatively be controlled by the user device, by a second beacon system, by a supplementary beacon, the output device itself, by a second output device, and/or be otherwise presented. The content is preferably presented on the output device, but can additionally or alternatively be presented on the user device, second output device, beacon system, and/or on any other suitable output. The content is preferably received from the content determination system, but can alternatively be received from any other suitable source. The content is preferably received by the master device, but can alternatively be received by the slave device and/or by any other suitable device. The content is preferably displayed (or determined) after verifying entity permission to display the contextual content, but can alternatively be displayed without verifying permissions or after any other suitable set of conditions has been satisfied. Presenting content preferably includes presenting contextual content determined by the content determination system, but can alternatively include presenting standby content (e.g., prior to and/or after presenting contextual content at the output device). Standby content can be stored in storage of the beacon system, determined by the processing system of the beacon system, and/or be otherwise determined. However, any suitable content can be presented at any suitable time in relation to any portions of the method 100.
In a first variation in which the user device is the master device, the content is sent from the content determination system to the user device, from the user device to the beacon system, and from the beacon system to the output device (e.g., the connected display). In a second variation, the content can be directly sent to the beacon system (e.g., where the beacon system can be the master device or a slave device), where the beacon system can be connected to a second network (e.g., a long-range network, such as a WiFi network). In a third variation, the content can be directly sent to the output device, where the output device identifier is associated with the beacon system (e.g., where the beacon system reads the output device identifier upon initialization). However, transmitting content to the output device can be performed through any suitable transmission scheme involving any suitable components.
In a fourth variation, the content can be transmitted to a second beacon system different from a first beacon system identified by the beacon identifier received in S100 and/or used in determining contextual content in S200. Selecting a second beacon system to present the content can be based on user location (e.g., transmitting content to a second beacon system in response to determining a user location more proximal the second beacon system than the first beacon system, etc.), user focus (e.g., transmitting content to a beacon system that a user is facing, which can be determined based on user device information such as compass data; supplementary beacon information such as sensor data; etc.), availability of output device and/or beacon system (e.g., transmitting content to a second beacon system in response to unavailability of the first beacon system, such as when the first beacon system is already controlling the output device to display contextual content for a different user, etc.), supplementary beacon information (e.g., selecting a beacon system for content transmission based on a product identifier associated with a supplementary beacon interacted with by a user, etc.), other beacon system information (e.g., beacon system sensor data), other user device information (e.g., user device sensor data), and/or any other suitable criteria. For example, the method can include, receiving a second beacon identifier (e.g., within a predetermined time period of first beacon identifier receipt) at the content determination system from a user device; determining a location parameter for the user based on the first and the second beacon identifiers; and selecting, based on the location parameter, a beacon system from the first and the second beacon systems to control presentation of the contextual content (e.g., performing any portions of the method 100 associated with transmission and presentation of contextual content). This variation can be useful if the user has physically moved to another part of the physical space while the content was being determined. The beacon system currently proximal the user can be: the beacon system currently connected to the user device; the beacon system whose identifier is currently being detected by the user device; the beacon system estimated to be within the user's line of sight, based on the user device heading and/or trajectory; and/or be any other suitable beacon system. However, content can be transmitted to any number of beacon systems (e.g., both the first and second beacon systems) for display at any number of output devices.
In a fifth variation, content can be presented at the user device. The content can be the same or different from the content presented at the output device. In an example, the method 100 can include determining user device content at the content determination system based on the first beacon identifier; and transmitting the user device content from the content determination system to the user device for presentation (e.g., concurrently with controlling the output device to present contextual content generated for the output device). However, generating and/or presenting user device content can be performed in any suitable manner.
As shown in
In a second variation, the beacon system accommodates multiple concurrent users by concurrently presenting multiple pieces of content. In a first embodiment, the beacon system receives different content for each user device connected to the beacon system (e.g., from the respective user device, from the remote system, etc.), selects a template, and displays the received content according to the template (example shown in
The method 100 can additionally include facilitating user actions through physical proximity to a beacon (e.g., beacon system, supplementary beacon) or output device. Physical proximity to the beacon can be measured through beacon signal strength (e.g., as measured by a scan/response service on the beacon, separate from the communication antenna), through trilateration, through comparison between a known beacon location and the user device location (e.g., through GPS), through the output's sensors, and/or otherwise determined. User actions can include facilitating purchases, triggering downstream actions, performance of a task, and/or any other suitable actions. Facilitating user actions can include: prompting the user with contextual content to perform an action (e.g., with the user device); detecting performance of the action (e.g., using the beacon system, user device, supplementary beacon, etc.; based on changes in signal strength, user device orientation sensor data, etc.); performing functions in response to performing the action; and/or any performing any suitable function. In one example, shown in
The method 100 can additionally include tracking user device progression through a physical space using the beacon systems. This information can be subsequently used to identify high-thoroughfare regions within the space, determine product placement locations, determine floor layouts, and/or be used for any other suitable purpose (e.g., by the manager). The information can additionally be used to determine advertising or promotional campaign efficacy, conversion rate, and/or any other suitable promotional metric. User device progression is preferably tracked by the remote computing system, but can additionally or alternatively be tracked by the user device (e.g., the application), the beacon systems, and/or by any other suitable system. In a first variation, tracking user device progression through a physical space includes: receiving a set of beacon identifiers from the user device over time and mapping user device location within the space across time based on the relative positions of the beacons identified by the beacon identifiers within the physical space (e.g., where the beacon identifiers are associated with static locations within the physical space). This variation can optionally include determining the items purchased by the user (e.g., based on collocation of the user device at the point of sale system during the checkout process, etc.) and determining the content presented by each beacon system while the user device was proximal the respective beacon system, where the relationship between the user purchase and content can be subsequently analyzed to determine the efficacy of a promotional campaign. In a second variation, tracking user device progression through the physical space can include tracking the beacon identifiers from which the user device identifier was received over time, and mapping user device location within the space over time based on the relative locations associated with the beacon identifiers. However, user device progression throughout the space can be otherwise determined.
The method 100 can additionally include selectively operating the beacon system as a master device or a slave device. This can function to confer the benefits of both operation as a slave (e.g., unitary user device connection and/or communication, etc.) and operation as a master (e.g., supplementary beacon monitoring, second beacon system communication and control, etc.). The beacon system can be toggled between the two control states periodically, upon occurrence of a trigger event (e.g., switched to operation as a slave upon user device detection), or at any other suitable time.
In one variation, when a plurality of beacon systems are used within the same physical space, a central control system (e.g., the remote computing system, the population of beacon systems themselves) can coordinate beacon system operation such that one beacon system operates as a master and the remainder operate as slaves. The master can monitor the supplementary beacons within the space, while the slaves can connect to the user device(s). The plurality of beacon systems can be constantly operated in this manner, with at least one of the plurality as a master, or be periodically operated in this manner, where the plurality are typically operated as slaves and only occasionally operated with one as the master. However, the plurality of beacon systems can be otherwise operated. The central control system can directly communicate with and/or control each beacon system (e.g., when every beacon system functions as a client device); directly connect to a beacon system of the plurality, where the beacon system communicates and/or controls the remainder of the beacon systems (e.g., where the first beacon functions as a client device and the remainder function as server devices); control beacon system operation through the user device (e.g., where the user device connects to and controls the beacon systems); and/or otherwise control beacon system operation.
In one embodiment, the plurality of beacon systems can be divided into one or more groups, where one beacon system of the group can function as the master and the remainder function as the slaves (example shown in
The method 100 can additionally or alternatively include providing a development kit, which can function to enable developers to: develop applications for user devices to modify interaction with the beacon system and/or the content to be displayed; modify beacon system parameters (e.g., type of displayed content, presentation parameters such as content presentation scheduling, beacon system selection to display content, etc.); and/or perform any other suitable modification to the configuration of beacon systems, supplementary beacons, content determination systems, and/or other components. However, providing a development kit can be otherwise performed.
An alternative embodiment preferably implements the above methods in a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with a beacon management system. The beacon management system can include a beacon identification system that functions to identify a set of content associated with a received beacon identifier, a content determination system that functions to determine which content of the set to present based on secondary information (e.g., user information, supplementary beacon information, etc.), and a content presentation system that functions to present the determined content to the user. The computer-readable medium may be stored on any suitable computer readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device.
Although omitted for conciseness, the preferred embodiments include every combination and permutation of the various system components and the various method processes, where the method processes can be performed in any suitable order, sequentially or concurrently. The methods and systems include every combination and permutation of the various system components and the various method processes, including any variations, embodiments, examples, and specific examples.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.
This application is a continuation of U.S. application Ser. No. 15/971,151, filed 4 May 2018, which is a divisional of U.S. application Ser. No. 15/436,564, filed 17 Feb. 2017, which is a continuation-in-part of prior U.S. application Ser. No. 15/288,302 filed on 7 Oct. 2016, which is a continuation of U.S. patent application Ser. No. 14/956,209 filed 1 Dec. 2015, now issued as U.S. Pat. No. 9,491,586, which is a continuation of U.S. patent application Ser. No. 14/463,582, filed on 19 Aug. 2014, now issued as U.S. Pat. No. 9,202,245, which claims the benefit of U.S. Provisional Application No. 61/867,493, filed on 19 Aug. 2013 and to U.S. Provisional Application No. 61/867,498, filed on 19 Aug. 2013, all of which are incorporated in their entireties by this reference. This application additionally claims the benefit of U.S. Provisional Application Ser. No. 62/393,903 filed on 13 Sep. 2016, U.S. Provisional Application Ser. No. 62/318,857 filed on 6 Apr. 2016, and U.S. Provisional Application Ser. No. 62/296,254, filed on 17 Feb. 2016, which are each incorporated in their entireties by this reference. This application is related to U.S. application Ser. No. 14/463,597 filed 19 Aug. 2014, which is incorporated in its entirety by this reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6091358 | Maniscalco et al. | Jul 2000 | A |
| 6362778 | Neher | Mar 2002 | B2 |
| 6775258 | Van et al. | Aug 2004 | B1 |
| 6873258 | Marples et al. | Mar 2005 | B2 |
| 6965575 | Srikrishna et al. | Nov 2005 | B2 |
| 7027808 | Wesby | Apr 2006 | B2 |
| 7038584 | Carter | May 2006 | B2 |
| 7072671 | Leitch | Jul 2006 | B2 |
| 7146178 | Lehikoinen et al. | Dec 2006 | B2 |
| 7283846 | Spriestersbach et al. | Oct 2007 | B2 |
| 7312752 | Smith et al. | Dec 2007 | B2 |
| 7366113 | Chandra et al. | Apr 2008 | B1 |
| 7458825 | Atsmon et al. | Dec 2008 | B2 |
| 7499462 | MacMullan et al. | Mar 2009 | B2 |
| 7639131 | Mock et al. | Dec 2009 | B2 |
| 7705728 | Mock et al. | Apr 2010 | B2 |
| 7706282 | Huang | Apr 2010 | B2 |
| 7835505 | Toyama et al. | Nov 2010 | B2 |
| 7855679 | Braiman | Dec 2010 | B1 |
| 7865306 | Mays | Jan 2011 | B2 |
| 7916084 | Dutruc | Mar 2011 | B2 |
| 7983677 | Dacosta | Jul 2011 | B2 |
| 8058988 | Medina et al. | Nov 2011 | B1 |
| 8139945 | Amir et al. | Mar 2012 | B1 |
| 8160056 | Van et al. | Apr 2012 | B2 |
| 8228196 | Thornton | Jul 2012 | B1 |
| 8260320 | Herz | Sep 2012 | B2 |
| 8265621 | Kopikare et al. | Sep 2012 | B2 |
| 8407417 | Matsuda et al. | Mar 2013 | B2 |
| 8489112 | Roeding et al. | Jul 2013 | B2 |
| 8520648 | Cordeiro | Aug 2013 | B2 |
| 8559975 | Basu et al. | Oct 2013 | B2 |
| 8566839 | Johnson et al. | Oct 2013 | B2 |
| 8594850 | Gourlay et al. | Nov 2013 | B1 |
| 8600341 | Johnson | Dec 2013 | B2 |
| 8612604 | Beatty et al. | Dec 2013 | B2 |
| 8634796 | Johnson | Jan 2014 | B2 |
| 8639267 | Johnson | Jan 2014 | B2 |
| 8644255 | Burcham et al. | Feb 2014 | B1 |
| 8694060 | Vanderaa et al. | Apr 2014 | B2 |
| 8694782 | Lambert | Apr 2014 | B2 |
| 8718598 | Johnson | May 2014 | B2 |
| 8723720 | Moffatt et al. | May 2014 | B2 |
| 8750823 | Johnson | Jun 2014 | B2 |
| 8750841 | Johnson et al. | Jun 2014 | B2 |
| 8761751 | Johnson et al. | Jun 2014 | B2 |
| 8761804 | Johnson | Jun 2014 | B2 |
| 8781502 | Middleton et al. | Jul 2014 | B1 |
| 8791901 | Mallinson | Jul 2014 | B2 |
| 8797214 | Taylor et al. | Aug 2014 | B2 |
| 8844007 | Vicente et al. | Sep 2014 | B2 |
| 8847754 | Buchheim et al. | Sep 2014 | B2 |
| 8855922 | Starenky et al. | Oct 2014 | B1 |
| 8867993 | Perkins et al. | Oct 2014 | B1 |
| 8868133 | Rosenbaum et al. | Oct 2014 | B1 |
| 8886226 | Johnson | Nov 2014 | B2 |
| 8886230 | Sydir et al. | Nov 2014 | B2 |
| 8887177 | Johnson et al. | Nov 2014 | B2 |
| 8896485 | Mendelson | Nov 2014 | B2 |
| 8897741 | Johnson | Nov 2014 | B2 |
| 8897742 | Johnson | Nov 2014 | B2 |
| 8911932 | Sun | Dec 2014 | B2 |
| 8923806 | Johnson | Dec 2014 | B2 |
| 8934389 | Kuehnel et al. | Jan 2015 | B2 |
| 8938196 | Bradish et al. | Jan 2015 | B2 |
| 8942693 | Johnson | Jan 2015 | B2 |
| 8942732 | Johnson | Jan 2015 | B2 |
| 8942733 | Johnson | Jan 2015 | B2 |
| 8971850 | Klein et al. | Mar 2015 | B2 |
| 8971932 | Mapes | Mar 2015 | B2 |
| 8988221 | Raji et al. | Mar 2015 | B2 |
| 8996030 | Grainger et al. | Mar 2015 | B2 |
| 9014658 | Johnson | Apr 2015 | B2 |
| 9014715 | Alizadeh-Shabdiz et al. | Apr 2015 | B2 |
| 9026134 | Edge | May 2015 | B2 |
| 9033255 | Tessier et al. | May 2015 | B2 |
| 9036792 | Cacioppo et al. | May 2015 | B2 |
| 9055406 | Johnson | Jun 2015 | B2 |
| 9063212 | Jones | Jun 2015 | B2 |
| 9078095 | Johnson | Jul 2015 | B2 |
| 9088868 | Johnson | Jul 2015 | B2 |
| 9088869 | Johnson | Jul 2015 | B2 |
| 9100792 | Johnson | Aug 2015 | B2 |
| 9113295 | Johnson | Aug 2015 | B2 |
| 9113309 | Uilecan et al. | Aug 2015 | B2 |
| 9113343 | Moshfeghi | Aug 2015 | B2 |
| 9140796 | Zhou | Sep 2015 | B2 |
| 9143890 | Jose et al. | Sep 2015 | B2 |
| 9154565 | Monighetti | Oct 2015 | B2 |
| 9202245 | Kostka et al. | Dec 2015 | B2 |
| 9204275 | Johnson et al. | Dec 2015 | B2 |
| 9253597 | Johnson | Feb 2016 | B2 |
| 9258674 | Chen | Feb 2016 | B2 |
| 9282436 | Chitre et al. | Mar 2016 | B2 |
| 9282582 | Dunsbergen et al. | Mar 2016 | B1 |
| 9307355 | Nehrenz et al. | Apr 2016 | B2 |
| 9338585 | Kehm | May 2016 | B2 |
| 9351114 | Chatterjee et al. | May 2016 | B2 |
| 9361630 | Goswami | Jun 2016 | B1 |
| 9392408 | Johnson | Jul 2016 | B2 |
| 9398422 | Zampini | Jul 2016 | B2 |
| 9408060 | Helms et al. | Aug 2016 | B2 |
| 9424699 | Kusens et al. | Aug 2016 | B2 |
| 9445238 | Johnson et al. | Sep 2016 | B2 |
| 9445305 | Lyon et al. | Sep 2016 | B2 |
| 9456303 | Johnson | Sep 2016 | B2 |
| 9462469 | Hillyard | Oct 2016 | B2 |
| 9471917 | Govindarajan et al. | Oct 2016 | B2 |
| 9474962 | Barney et al. | Oct 2016 | B2 |
| 9491575 | Edge et al. | Nov 2016 | B2 |
| 9544744 | Postrel | Jan 2017 | B2 |
| 9551774 | Ishida et al. | Jan 2017 | B2 |
| 9558507 | Zilkha | Jan 2017 | B2 |
| 9571957 | Granbery | Feb 2017 | B2 |
| 9584993 | Johnson et al. | Feb 2017 | B2 |
| 9591570 | Kubo et al. | Mar 2017 | B2 |
| 9609487 | Alshihi | Mar 2017 | B2 |
| 9621446 | Pugh et al. | Apr 2017 | B2 |
| 9622046 | Otis et al. | Apr 2017 | B2 |
| 9622208 | Mycek et al. | Apr 2017 | B2 |
| 9629064 | Graves et al. | Apr 2017 | B2 |
| 9634928 | Choudhury et al. | Apr 2017 | B2 |
| 9642173 | Granbery | May 2017 | B2 |
| 9648662 | Herrala et al. | May 2017 | B2 |
| 9652124 | Cotier et al. | May 2017 | B2 |
| 9684826 | Dubuque | Jun 2017 | B2 |
| 9684925 | Khalid et al. | Jun 2017 | B2 |
| 9689955 | Rosenbaum | Jun 2017 | B2 |
| 9712967 | Kostka et al. | Jul 2017 | B2 |
| 9826356 | Mycek et al. | Nov 2017 | B2 |
| 9843591 | Bliss | Dec 2017 | B2 |
| 9866996 | Krzych et al. | Jan 2018 | B1 |
| 9867009 | Mycek et al. | Jan 2018 | B2 |
| 9898039 | Moore et al. | Feb 2018 | B2 |
| 9922294 | Raina et al. | Mar 2018 | B2 |
| 9998863 | Mycek et al. | Jun 2018 | B2 |
| 9998867 | Keithley | Jun 2018 | B2 |
| 10111034 | Johnson | Oct 2018 | B2 |
| 10292011 | Johnson | May 2019 | B2 |
| 20010026240 | Neher | Oct 2001 | A1 |
| 20020167919 | Marples et al. | Nov 2002 | A1 |
| 20020170961 | Dickson | Nov 2002 | A1 |
| 20020176388 | Rankin et al. | Nov 2002 | A1 |
| 20030084539 | Wartian | May 2003 | A1 |
| 20030100315 | Rankin | May 2003 | A1 |
| 20030146835 | Carter | Aug 2003 | A1 |
| 20030148775 | Spriestersbach et al. | Aug 2003 | A1 |
| 20040008663 | Srikrishna et al. | Jan 2004 | A1 |
| 20040190447 | Dacosta | Sep 2004 | A1 |
| 20040264372 | Huang | Dec 2004 | A1 |
| 20040264466 | Huang | Dec 2004 | A1 |
| 20050162271 | Leitch | Jul 2005 | A1 |
| 20050222933 | Wesby | Oct 2005 | A1 |
| 20060059049 | Morris | Mar 2006 | A1 |
| 20060163349 | Neugebauer | Jul 2006 | A1 |
| 20060209745 | MacMullan et al. | Sep 2006 | A1 |
| 20060259942 | Toyama et al. | Nov 2006 | A1 |
| 20060290519 | Boate et al. | Dec 2006 | A1 |
| 20070007337 | Clark | Jan 2007 | A1 |
| 20070067104 | Mays | Mar 2007 | A1 |
| 20070069923 | Mendelson | Mar 2007 | A1 |
| 20070243769 | Atsmon et al. | Oct 2007 | A1 |
| 20070247366 | Smith et al. | Oct 2007 | A1 |
| 20080027796 | Chaves | Jan 2008 | A1 |
| 20080056215 | Kopikare et al. | Mar 2008 | A1 |
| 20080062891 | Van et al. | Mar 2008 | A1 |
| 20080068519 | Adler et al. | Mar 2008 | A1 |
| 20080139306 | Lutnick et al. | Jun 2008 | A1 |
| 20080143516 | Mock et al. | Jun 2008 | A1 |
| 20080143604 | Mock et al. | Jun 2008 | A1 |
| 20080231460 | Owen et al. | Sep 2008 | A1 |
| 20090005079 | Shields et al. | Jan 2009 | A1 |
| 20090009398 | Taylor et al. | Jan 2009 | A1 |
| 20090131079 | Sekhar | May 2009 | A1 |
| 20090311976 | Vanderaa et al. | Dec 2009 | A1 |
| 20090327135 | Nguyen et al. | Dec 2009 | A1 |
| 20100019924 | D et al. | Jan 2010 | A1 |
| 20100093374 | Dacosta | Apr 2010 | A1 |
| 20100099435 | Druzinic-Fiebach et al. | Apr 2010 | A1 |
| 20100100582 | Beatty et al. | Apr 2010 | A1 |
| 20100105353 | Cacioppo et al. | Apr 2010 | A1 |
| 20100120450 | Herz | May 2010 | A1 |
| 20100168924 | Tessier et al. | Jul 2010 | A1 |
| 20100317371 | Migos et al. | Dec 2010 | A1 |
| 20110028160 | Roeding et al. | Feb 2011 | A1 |
| 20110029359 | Roeding et al. | Feb 2011 | A1 |
| 20110102171 | Raji et al. | May 2011 | A1 |
| 20110238188 | Washiro | Sep 2011 | A1 |
| 20110305228 | Cordeiro | Dec 2011 | A1 |
| 20110306357 | Alizadeh-Shabdiz et al. | Dec 2011 | A1 |
| 20120057518 | Herrala et al. | Mar 2012 | A1 |
| 20120095805 | Ghosh et al. | Apr 2012 | A1 |
| 20120112055 | Castro-Perez et al. | May 2012 | A1 |
| 20120172055 | Edge | Jul 2012 | A1 |
| 20120190386 | Anderson | Jul 2012 | A1 |
| 20120258730 | Tinnakornsrisuphap et al. | Oct 2012 | A1 |
| 20120260323 | San Vicente et al. | Oct 2012 | A1 |
| 20120262365 | Mallinson | Oct 2012 | A1 |
| 20120280862 | Moffatt et al. | Nov 2012 | A1 |
| 20120284517 | Lambert | Nov 2012 | A1 |
| 20120295535 | Bradish et al. | Nov 2012 | A1 |
| 20120309256 | Theodore | Dec 2012 | A1 |
| 20120316960 | Yang | Dec 2012 | A1 |
| 20120320815 | Massena | Dec 2012 | A1 |
| 20130023282 | Lin et al. | Jan 2013 | A1 |
| 20130030915 | Statler et al. | Jan 2013 | A1 |
| 20130063303 | Zhou | Mar 2013 | A1 |
| 20130065584 | Lyon et al. | Mar 2013 | A1 |
| 20130165157 | Mapes | Jun 2013 | A1 |
| 20130182625 | Kuehnel et al. | Jul 2013 | A1 |
| 20130184002 | Moshfeghi | Jul 2013 | A1 |
| 20130203445 | Grainger et al. | Aug 2013 | A1 |
| 20130225197 | Mcgregor et al. | Aug 2013 | A1 |
| 20130288668 | Pragada et al. | Oct 2013 | A1 |
| 20130295879 | Mahalingam | Nov 2013 | A1 |
| 20130337771 | Klein et al. | Dec 2013 | A1 |
| 20140018002 | Jose et al. | Jan 2014 | A1 |
| 20140052676 | Wagner et al. | Feb 2014 | A1 |
| 20140087758 | Maor | Mar 2014 | A1 |
| 20140106782 | Chitre et al. | Apr 2014 | A1 |
| 20140122703 | Pugh et al. | May 2014 | A1 |
| 20140122855 | Maneval | May 2014 | A1 |
| 20140135042 | Buchheim et al. | May 2014 | A1 |
| 20140148196 | Bassan-Eskenazi et al. | May 2014 | A1 |
| 20140149577 | Monighetti | May 2014 | A1 |
| 20140180817 | Zilkha | Jun 2014 | A1 |
| 20140219118 | Middleton et al. | Aug 2014 | A1 |
| 20140220883 | Emigh et al. | Aug 2014 | A1 |
| 20140228044 | Jones | Aug 2014 | A1 |
| 20140277654 | Reinhardt et al. | Sep 2014 | A1 |
| 20140302869 | Rosenbaum et al. | Oct 2014 | A1 |
| 20150005011 | Nehrenz et al. | Jan 2015 | A1 |
| 20150031388 | Chatterjee et al. | Jan 2015 | A1 |
| 20150038171 | Uilecan et al. | Feb 2015 | A1 |
| 20150058355 | Naqvi | Feb 2015 | A1 |
| 20150079942 | Kostka et al. | Mar 2015 | A1 |
| 20150081474 | Kostka et al. | Mar 2015 | A1 |
| 20150094140 | Barney et al. | Apr 2015 | A1 |
| 20150106196 | Williams et al. | Apr 2015 | A1 |
| 20150163828 | Vandwalle et al. | Jun 2015 | A1 |
| 20150245305 | Camps Mur | Aug 2015 | A1 |
| 20150248667 | Govindarajan et al. | Sep 2015 | A1 |
| 20150276432 | Repyevsky et al. | Oct 2015 | A1 |
| 20150279115 | Vukicevic | Oct 2015 | A1 |
| 20150289207 | Kubo et al. | Oct 2015 | A1 |
| 20150294398 | Khalid et al. | Oct 2015 | A1 |
| 20150295333 | Shibuya et al. | Oct 2015 | A1 |
| 20150296048 | Gerding et al. | Oct 2015 | A1 |
| 20150296333 | Chen | Oct 2015 | A1 |
| 20150334548 | Liu et al. | Nov 2015 | A1 |
| 20150347959 | Skaaksrud | Dec 2015 | A1 |
| 20150351008 | Mayor | Dec 2015 | A1 |
| 20150355308 | Ishida et al. | Dec 2015 | A1 |
| 20150365790 | Edge et al. | Dec 2015 | A1 |
| 20150379576 | Otis et al. | Dec 2015 | A1 |
| 20150382153 | Otis et al. | Dec 2015 | A1 |
| 20160006837 | Reynolds et al. | Jan 2016 | A1 |
| 20160007315 | Lundgreen et al. | Jan 2016 | A1 |
| 20160014609 | Goel et al. | Jan 2016 | A1 |
| 20160021687 | Granbery | Jan 2016 | A1 |
| 20160042767 | Araya et al. | Feb 2016 | A1 |
| 20160049028 | Kusens et al. | Feb 2016 | A1 |
| 20160055428 | Raina et al. | Feb 2016 | A1 |
| 20160063550 | Caldwell | Mar 2016 | A1 |
| 20160086029 | Dubuque | Mar 2016 | A1 |
| 20160086460 | King et al. | Mar 2016 | A1 |
| 20160094398 | Choudhury et al. | Mar 2016 | A1 |
| 20160094598 | Gedikian | Mar 2016 | A1 |
| 20160094946 | Keithley | Mar 2016 | A1 |
| 20160099758 | Bell et al. | Apr 2016 | A1 |
| 20160105788 | Helms et al. | Apr 2016 | A1 |
| 20160123745 | Cotier et al. | May 2016 | A1 |
| 20160127875 | Zampini | May 2016 | A1 |
| 20160188919 | Gao et al. | Jun 2016 | A1 |
| 20160192407 | Fyfe et al. | Jun 2016 | A1 |
| 20160277999 | Graves et al. | Sep 2016 | A1 |
| 20160291127 | Huang et al. | Oct 2016 | A1 |
| 20160345126 | Granbery | Nov 2016 | A1 |
| 20170019765 | Hoyer et al. | Jan 2017 | A1 |
| 20170064667 | Mycek et al. | Mar 2017 | A1 |
| 20170079001 | Lewis | Mar 2017 | A1 |
| 20170099567 | Kwon et al. | Apr 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2016101053 | Aug 2016 | AU |
| 102819804 | Dec 2012 | CN |
| 20030084539 | Nov 2003 | KR |
| 101113052 | Feb 2012 | KR |
| 0221429 | Mar 2002 | WO |
| 2008135432 | Nov 2008 | WO |
| 2015026862 | Feb 2015 | WO |
| 2016043388 | Mar 2016 | WO |
| 2017040690 | Mar 2017 | WO |
| Entry |
|---|
| Burnside, Matt, et al. “Proxy-based security protocols in networked mobile devices.” Proceedings of the 2002 ACM symposium on Applied computing. ACM, 2002. (Year 2002). |
| EPO Examination Report for Application No. 14838745.9, dated Jul. 11, 2018. |
| International Search Report and the Written Opinion of the International Searching Authority, Application No. PCT/IB2018/000692, dated Sep. 28, 2018. |
| International Search Report and Written Opinion for International Application No. PCT/US2017/031811 dated Sep. 1, 2017. |
| Park, et al. “Multiscale Entropy Analysis of EEG from Patients Under Different Pathological Conditions.” Fractais 15, 399 (2007). |
| U.S. Appl. No. 16/375,836. |
| Jung, Chanhsu , et al., “Topology Configuration and Multihop Routing Protocol for Bluetooth Low Energy Networks”, IEEE Access, Dec. 13, 2017, 9587-9598. |
| Jung, Chanhsu , et al., “Maximum Power Plus RSSI Based Routing Protocol for Bluetooth Low Energy Ad Hoc Networks”, Wireless Communications and Mobile Computing, Dec. 13, 2017, 1-13. |
| Number | Date | Country | |
|---|---|---|---|
| 20200186966 A1 | Jun 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61867493 | Aug 2013 | US | |
| 61867498 | Aug 2013 | US | |
| 62393903 | Sep 2016 | US | |
| 62318857 | Apr 2016 | US | |
| 62296254 | Feb 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15436564 | Feb 2017 | US |
| Child | 15971151 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15971151 | May 2018 | US |
| Child | 16793259 | US | |
| Parent | 14956209 | Dec 2015 | US |
| Child | 15288302 | US | |
| Parent | 14463582 | Aug 2014 | US |
| Child | 14956209 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15288302 | Oct 2016 | US |
| Child | 15436564 | US |
