Patent Grant
10715961
A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
The invention relates generally to the field of data and content distribution and delivery. In one exemplary aspect, the invention relates to enabling location identification services within a premises.
Content distribution networks (such as e.g., Cable Television (CATV), satellite, or hybrid fiber/copper (HFCu) systems) provide content from various content sources at a network headend to a plurality of subscriber devices. In a typical “managed” network, a network operator (e.g., multiple systems operator or MSO) provides access to content via the network. Generally, the MSO provides audio/video content to subscribers from the network headend via the distribution network.
Recent advances in digital information processing and technology have made a wide range of additional services and functions available for delivery to consumers at various types of devices for very reasonable prices or subscription fees. These services and functions include delivery of digital content or programming (movies, etc.), digital video-on-demand (VOD) services, personal video recorder (PVR) and networked PVR (nPVR) services, Internet Protocol television (IPTV), digital media playback and recording, as well high speed Internet access (including so-called “Internet TV”, where television programming is delivered over the Internet), IP-based telephony (e.g., VoIP), and access to client applications via mobile devices. Other services available to network users include without limitation access to, and recording of, digital music (e.g., MP3 files), and submission of “organic” media (e.g., home-grown Youtube™ videos, etc.).
Currently, many of these services are provided to users via a wide variety of different equipment environments and delivery paradigms including, inter alia, cable or satellite modems or QAMs, HFCu (i.e., Hybrid Fiber-copper distribution via indigenous POST/PSTN and/or coaxial wiring in a premises), optical fiber such as FTTC, FTTH, etc., Wi-Fi™ hubs, Ethernet hubs, gateways, switches, and routers, and to a plurality of user equipment types (e.g., set-top boxes, personal (desktop) computers, laptop computers, other mini-computers such as so-called “netbooks” and mini-notebook computers, and/or other devices). Recent advances in consumer electronics have also led to the widespread introduction of a variety of portable media devices (PMDs) such as, inter alia, portable digital music devices such as the well known Apple iPod™, and other so-called “MP3 players”, cellular telephones/smartphones, handheld computers, tablets such as the Kindle™ and Nook™ and iPad™, and personal digital assistants (PDA), which allow users to store and playback audio and video files.
Various device applications provide or incorporate services which vary based on a location of a portable media device (or user thereof) within a given premises. For example, certain applications may have modified volume, brightness, etc. settings based on what room a person is in. Additionally, power-saving systems rely on a location of a person within the home. For example, if it can be determined that no one is in e.g., the family room, power to a rendering or other device in that room may be cut. These systems, however, require a user to manually enter a location via a user interface or otherwise require advanced detection technologies (e.g., infrared or motion detectors) to be installed within a premises.
Hence, methods and apparatus are needed which enable location-based services to function independent of manual entry of a location and using services and functions of devices currently existing within a home network. Such location identification methods and apparatus would ideally be provided across multiple client devices within a premises, and would be readily downloadable or made otherwise accessible to existing user devices.
The present invention provides, inter alia, apparatus and methods for enabling location identification services within a premises.
In a first aspect of the invention, a method of providing location-based services within a consumer premises is disclosed. In one embodiment, the method includes generating a plurality of profiles, each of said plurality of profiles comprising a plurality of device-specific data obtained from respective individual ones of a plurality of devices within said consumer premises. In one variant, the method further includes: assigning an identification of a location within said consumer premises to each of said profiles; storing said plurality of profiles with said respective assigned identification at a storage entity; receiving a location request from an application running on at least one of said plurality of devices within said consumer premises, said location request comprising a plurality of second device-specific data, said second device-specific data being specific to said at least one of said plurality of devices within said consumer premises; and in response to said request, examining said plurality of second device-specific data and said plurality of profiles to determine an identification indicative of a current location of said at least one device within said consumer premises.
In a second aspect of the invention, a method of generating a client device-specific profile is disclosed. In one embodiment, the profile relates a client device to a position thereof within a given area, and said method includes: transmitting at least one request signal from a gateway device to the client device, said at least one request signal being transmitted to said client device when said client device is located at a position within said given area; receiving, in response to said transmitted at least one request signal, a response signal from said client device indicating one or more device-specific characteristics; and storing a profile comprising an association of said one or more device-specific characteristics to said position within said given area.
In a third aspect of the invention, a method of correlating a mobile client device to a particular location within a user premises is disclosed. In one embodiment, the method comprises: (i) receiving from an intermediary device a first communication, the first communication comprising information identifying the intermediary device and the mobile client device, (ii) evaluating the information identifying the intermediary device against pre-stored information associating a plurality of intermediary devices to individual ones of known locations to determine the particular location of the intermediary device, and (iii) correlating the mobile client device to the particular location of the intermediary device.
In a fourth aspect of the invention, a gateway apparatus is disclosed. In one embodiment, the gateway apparatus comprises: at least one interface configured for wireless communication within a consumer premises, a processor configured to run at least one computer program thereon, and a storage apparatus in data communication with the processor and the at least one interface and having the at least one computer program stored thereon, the at least one program comprising a plurality of instructions which are configured to, when executed by the processor: (i) generate a device profile for each of a plurality of mobile devices associated to the consumer premises, each of the device profiles correlating a particular mobile device to a particular location within the premises, (ii) for each of the particular locations, assign an identifier, (iii) associate the plurality of profiles with the respective assigned identifiers, (iv) receive a communication from an individual one of the plurality of mobile devices via the at least one interface, and (v) utilize information within the communication to identify a profile associated to the individual one of the mobile devices, the profile associated to a particular one of the plurality of locations within the premises.
In a fifth aspect of the invention, a mobile user wireless device configured for location-specific operation is disclosed. In one embodiment, the device includes: a processor; a wireless transceiver in data communication with the processor; and a storage device in data communication with the processor and having a computer program disposed thereon. In one variant, the program is configured to, when executed: generate, in response to a first transmission received at the transceiver, a reply uniquely identifying the mobile device; cause transmission of the reply to a gateway device; receive a second transmission including location information of the mobile device within a premises; and based at least in part on the location information, cause adjustment of at least one user interface so as to provide at least one location-specific content element to a user of the device.
In a sixth aspect of the invention, a system configured for location-specific operation of one or more client or user devices is disclosed.
In a seventh aspect of the invention, a computer readable apparatus having at least one program disposed thereon is disclosed. In one embodiment, the at least one program is configured for location-specific operation of one or more client or user devices.
These and other aspects of the invention shall become apparent when considered in light of the disclosure provided herein.
All Figures©Copyright 2012 Time Warner Cable, Inc. All rights reserved.
Reference is now made to the drawings wherein like numerals refer to like parts throughout.
As used herein, the term “application” refers generally and without limitation to a unit of executable software that implements a certain functionality or theme. The themes of applications vary broadly across any number of disciplines and functions (such as on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculator etc.), and one application may have more than one theme. The unit of executable software generally runs in a predetermined environment; for example, the unit could comprise a downloadable Java Xlet™ that runs within the JavaTV™ environment.
As used herein, the terms “client device” and “end user device” include, but are not limited to, set-top boxes (e.g., DSTBs), gateways, modems, personal computers (PCs), and minicomputers, whether desktop, laptop, or otherwise, and mobile devices such as handheld computers, PDAs, personal media devices (PMDs), tablets, and smartphones.
As used herein, the term “codec” refers to a video, audio, or other data coding and/or decoding algorithm, process or apparatus including, without limitation, those of the MPEG (e.g., MPEG-1, MPEG-2, MPEG-4/H.264, etc.), Real (RealVideo, etc.), AC-3 (audio), DiVX, XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, 9, 10, or 11), ATI Video codec, or VC-1 (SMPTE standard 421M) families.
As used herein, the term “computer program” or “software” is meant to include any sequence or human or machine cognizable steps which perform a function. Such program may be rendered in virtually any programming language or environment including, for example, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML, VoXML), and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA), Java™ (including J2ME, Java Beans, etc.), Binary Runtime Environment (e.g., BREW), and the like.
The terms “consumer premises equipment (CPE)” and “host device” refer without limitation to any type of electronic equipment located within a consumer's or user's premises and connected to a network. The term “host device” includes terminal devices that have access to digital television content via a satellite, cable, or terrestrial network. The host device functionality may be integrated into a digital television (DTV) set. The term “consumer premises equipment” (CPE) includes such electronic equipment such as set-top boxes, televisions, Digital Video Recorders (DVR), gateway storage devices (Furnace), and ITV Personal Computers.
As used herein, the term “DOCSIS” refers to any of the existing or planned variants of the Data Over Cable Services Interface Specification, including for example DOCSIS versions 1.0, 1.1, 2.0 and 3.0.
As used herein, the term “gateway” includes, without limitation, devices configured to interface with a network, and pass signals to or exchange signals with, another device in communication therewith. Various exemplary gateways are described in, inter alia, co-owned U.S. Pat. No. 7,954,131 issued on May 31, 2011 entitled “PREMISES GATEWAY APPARATUS AND METHODS FOR USE IN A CONTENT-BASED NETWORK”, U.S. patent application Ser. No. 12/582,619 filed on Oct. 20, 2009 entitled “GATEWAY APPARATUS AND METHODS FOR DIGITAL CONTENT DELIVERY IN A NETWORK”, and issued as U.S. Pat. No. 9,027,062 on May 5, 2015, and U.S. patent application Ser. No. 12/480,597 filed on Jun. 8, 2009 entitled “MEDIA BRIDGE APPARATUS AND METHODS”, and issued as U.S. Pat. No. 9,602,864 on Mar. 21, 2017, each of the foregoing being incorporated herein by reference in its entirety.
As used herein, the term “headend” refers generally to a networked system controlled by an operator (e.g., an MSO or multiple systems operator) that distributes programming to MSO clientele using client devices. Such programming may include literally any information source/receiver including, inter alia, free-to-air TV channels, pay TV channels, interactive TV, and the Internet.
As used herein, the terms “Internet” and “internet” are used interchangeably to refer to inter-networks including, without limitation, the Internet.
As used herein, the terms “microprocessor” and “digital processor” are meant generally to include all types of digital processing devices including, without limitation, digital signal processors (DSPs), reduced instruction set computers (RISC), general-purpose (CISC) processors, microprocessors, gate arrays (e.g., FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors, secure microprocessors, and application-specific integrated circuits (ASICs). Such digital processors may be contained on a single unitary IC die, or distributed across multiple components.
As used herein, the terms “MSO” or “multiple systems operator” refer without limitation to a cable, fiber to the home (FTTH), fiber to the curb (FTTC), satellite, Hybrid Fiber Copper (HFCu), or terrestrial network provider having infrastructure required to deliver services including programming and data over those mediums.
As used herein, the terms “network” and “bearer network” refer generally to any type of telecommunications or data network including, without limitation, hybrid fiber coax (HFC) networks, HFCu networks, satellite networks, telco networks, and data networks (including MANs, WANs, LANs, WLANs, internets, and intranets). Such networks or portions thereof may utilize any one or more different topologies (e.g., ring, bus, star, loop, etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeter wave, optical, etc.) and/or communications or networking protocols.
As used herein, the term “network interface” refers to any signal, data, or software interface with a component, network or process including, without limitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g., USB2), Ethernet (e.g., 10/100, 10/100/1000 (Gigabit Ethernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radio frequency tuner (e.g., in-band or OOB, cable modem, etc.), Wi-Fi (802.11), WiMAX (802.16), PAN (e.g., 802.15), cellular (e.g., 3G, LTE/LTE-A/TD-LTE, GSM, etc.) or IrDA families.
As used herein, the term “node” refers to any functional entity associated with a network, such as for example an OLT or ONU, whether physically discrete or distributed across multiple locations.
As used herein, the term “QAM” refers to modulation schemes used for sending signals over cable networks. Such modulation scheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM, 256-QAM, etc.) depending on details of a cable network. A QAM may also refer to a physical channel modulated according to the schemes.
As used herein, the term “server” refers to any computerized component, system or entity regardless of form which is adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer system or network.
As used herein, the term “service”, “content”, “program” and “stream” are sometimes used synonymously to refer to a sequence of packetized data that is provided in what a subscriber may perceive as a service. A “service” (or “content”, or “stream”) in the former, specialized sense may correspond to different types of services in the latter, non-technical sense. For example, a “service” in the specialized sense may correspond to, among others, video broadcast, audio-only broadcast, pay-per-view, or video-on-demand. The perceivable content provided on such a “service” may be live, pre-recorded, delimited in time, undelimited in time, or of other descriptions. In some cases, a “service” in the specialized sense may correspond to what a subscriber would perceive as a “channel” in traditional broadcast television.
As used herein, the term “service group” refers without limitation to either a group of service users (e.g. subscribers), or the resources shared by them in the form of for example entire cable RF signal, only the RF channels used to receive the service or otherwise treated as a single logical unit by the network for resource assignment.
As used herein, the term “Wi-Fi” refers to, without limitation, any of the variants of IEEE-Std. 802.11 or related standards including 802.11 a/b/g/n/s/v/ac or 802.11-2012.
As used herein, the term “wireless” means any wireless signal, data, communication, or other interface including without limitation Wi-Fi, Bluetooth, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20, narrowband/FDMA, OFDM, PCS/DCS, LTE/LTE-A/TD-LTE, analog cellular, CDPD, satellite systems, millimeter wave or microwave systems, acoustic, and infrared (i.e., IrDA).
Overview
In one salient aspect, the present invention discloses methods and apparatus for enabling location identification services within a premises. In one exemplary embodiment, location identification services are provided via a gateway device, and utilize beamforming technology as set forth in IEEE standard 802.11ac™ entitled “Very High Throughput 5 GHz” (currently in draft form) and its supporting documentation, all of which is incorporated herein by reference in its entirety. Using beamforming technology, signals sent between multiple antennas (up to 8 in the exemplary 802.11ac implementation) of the gateway device and client devices are coordinated to combine constructively at the device receiving the signal. Information is extracted during this process which is used to identify a location within a user's home. For example, various data relating to e.g., antenna receive power (pr), the error rate (er), and the client transmit power (pt), signal quality, and amplification needed to transmit signals to and/or receive signals from individual ones of the devices is collected. The data is then used to estimate a location of a device (such as based on comparison to previously gathered data and/or standard or reference data).
In another embodiment, infrared (IR) or other short range wireless signals are broadcast from the client devices to the STB, the STB or gateway then correlates the messages from the devices to a location within the premises.
In yet another embodiment, a wireless user device with beamforming capability is used to derive and provide location information (e.g., relative to a known fixed location).
A profiling process may also be performed for each designated location within a premises. In one variant, a Location Profiler (LOCP) application running on at least one of the gateway or STB is used to establish a “qualifier” (or location name) for specific locations in a premises using an initial profile process to gather data regarding devices at the specific locations within the premises. The gateway (and/or STB) is then able to automatically provide a location name to the devices when providing location services thereto.
In one embodiment, the location-based services include services which enable particular applications and/or content to be automatically loaded or provided when the user enters a particular location. In another embodiment, the location-based services include services which provide information and/or advertisement opportunities when the user is near a particular public or business location. The location-based services of the present invention may be further utilized to optimize content delivery to multiple user devices.
Additionally, a device associated with the user's person (such as e.g., a mobile device) may indicate where the user is within a premises, the system may then automatically transfer content to the devices within the general location of the user, and/or predict a pattern of movement within the user premises (which can be used to further predict where content should be moved in order to follow the user throughout the premises).
Exemplary embodiments of the apparatus and methods of the present invention are now described in detail. While these exemplary embodiments are described in the context of the aforementioned hybrid fiber/coax (HFC) cable system architecture having a multiple systems operator (MSO), digital networking capability, IP delivery capability, and plurality of client devices/CPE, the general principles and advantages of the invention may be extended to other types of networks and architectures, whether broadband, narrowband, wired or wireless, managed or unmanaged, or otherwise, the following therefore being merely exemplary in nature. For example, the invention may be practiced over a fiber-to-the-home (FTTH) or fiber-to-the-curb (FTTC) system, HFCu networks, or over satellite or millimeter wave-based networks.
It will also be appreciated that while described generally in the context of a consumer (i.e., residential) end user domain, the present invention may be readily adapted to other types of environments (e.g., commercial/enterprise, government/military, etc.) as well. Myriad other applications are possible.
It is further noted that while exemplary embodiments are described primarily in the context of a hybrid fiber/conductor (e.g., cable) system with legacy 6 MHz RF channels, the present invention is applicable to literally any network topology or paradigm, and any frequency/bandwidth. Furthermore, as referenced above, the invention is in no way limited to traditional cable system frequencies (i.e., below 1 GHz), and in fact may be used with systems that operate above 1 GHz band in center frequency or bandwidth, to include without limitation so-called ultra-wideband systems.
Other features and advantages of the present invention will immediately be recognized by persons of ordinary skill in the art with reference to the attached drawings and detailed description of exemplary embodiments as given below.
Network—
The data/application origination point 102 comprises any medium that allows data and/or applications (such as a VOD-based or “Watch TV” application) to be transferred to a distribution server 104. This can include for example a third party data source, application vendor website, CD-ROM, external network interface, mass storage device (e.g., RAID system), etc. Such transference may be automatic, initiated upon the occurrence of one or more specified events (such as the receipt of a request packet or ACK), performed manually, or accomplished in any number of other modes readily recognized by those of ordinary skill.
The application distribution server 104 comprises a computer system where such applications can enter the network system. Distribution servers are well known in the networking arts, and accordingly not described further herein.
The VOD server 105 comprises a computer system where on-demand content can be received from one or more of the aforementioned data sources 102 and enter the network system. These servers may generate the content locally, or alternatively act as a gateway or intermediary from a distant source.
The CPE 106 includes any equipment in the “customers' premises” (or other locations, whether local or remote to the distribution server 104) that can be accessed by a distribution server 104.
Referring now to
The exemplary architecture 150 of
It will also be recognized, however, that the multiplexing operation(s) need not necessarily occur at the headend 150 (e.g., in the aforementioned MEM 162). For example, in one variant, at least a portion of the multiplexing is conducted at a BSA switching node or hub (see discussion of
Content (e.g., audio, video, data, files, etc.) is provided in each downstream (in-band) channel associated with the relevant service group. To communicate with the headend or intermediary node (e.g., hub server), the CPE 106 may use the out-of-band (OOB) or DOCSIS channels and associated protocols. The OCAP 1.0, 2.0, 3.0 (and subsequent) specification provides for exemplary networking protocols both downstream and upstream, although the invention is in no way limited to these approaches.
“Switched” Networks—
Switching architectures allow improved efficiency of bandwidth use for ordinary digital broadcast programs. Ideally, the subscriber is unaware of any difference between programs delivered using a switched network and ordinary streaming broadcast delivery.
Co-owned U.S. patent application Ser. No. 09/956,688 filed Sep. 20, 2001 entitled “TECHNIQUE FOR EFFECTIVELY PROVIDING PROGRAM MATERIAL IN A CABLE TELEVISION SYSTEM”, and issued as U.S. Pat No. 8,713,623 on Apr. 29, 2014, incorporated herein by reference in its entirety, describes one exemplary broadcast switched digital architecture useful with the present invention, although it will be recognized by those of ordinary skill that other approaches and architectures may be substituted.
In addition to “broadcast” content (e.g., video programming), the systems of
Referring again to
The edge switch 194 forwards the packets receive from the CMTS 199 to the QAM modulator 189, which transmits the packets on one or more physical (QAM-modulated RF) channels to the CPE. The IP packets are typically transmitted on RF channels that are different that the RF channels used for the broadcast video and audio programming, although this is not a requirement. The CPE 106 are each configured to monitor the particular assigned RF channel (such as via a port or socket ID/address, or other such mechanism) for IP packets intended for the subscriber premises/address that they serve.
“Packetized” Networks—
While the foregoing network architectures described herein can (and in fact do) carry packetized content (e.g., IP over MPEG for high-speed data or Internet TV, MPEG2 packet content over QAM for MPTS, etc.), they are often not optimized for such delivery. Hence, in accordance with another embodiment of the present invention, a “packet optimized” delivery network is used for carriage of the packet content (e.g., IPTV content).
Exemplary Premises Network Architecture—
Referring now to
As illustrated, the network 200 generally comprises a gateway device 202, a storage entity 204, a plurality of mobile client devices 210a-210n, and a plurality of fixed location client devices 212a-212n. In the illustrated embodiment, the network 200 also comprises a client set-top box (STB) 206. The gateway device 202 and STB 206 communicate with the content delivery network 101, as well as to each of the client devices 210, 212 as discussed in greater detail below.
Each of the foregoing components cooperates to provide location identification and other location-based services to the mobile client devices 210 and/or the fixed client devices 212.
In one embodiment, location identification services are provided via the gateway device 202 and utilize beamforming technology as set forth in IEEE standard 802.11ac™ entitled “Very High Throughput 5 GHz”, previously incorporated herein by reference in its entirety.
As a brief aside, beamforming is a signal processing technology that is used to direct the reception or transmission (the signal energy) on a transducer array in a chosen angular direction (i.e., directional signal transmission or reception). Beamforming concentrates the array to sounds coming from only one particular direction to listen to signals in one direction and ignore signals in other directions, such as by combining elements in the array in such a way that signals at particular angles experience constructive interference while others experience destructive interference, akin to the well known “phased array”. Devices leveraging beamforming technology are therefore able to focus wireless signals directly to a particular device, as opposed to wireless hotspots which “radiate” wireless signals indiscriminately. In other words, beamforming technologies enable a wireless access point to recognize devices that need wireless access and focus the wireless signals directly to the device or devices which need them. By utilizing beamforming technologies, the gateway 202 is able to beam signals around corners and through walls.
In one embodiment, the exemplary gateway device 202 takes advantage of the multiple transmit antennas available in a multiple-input multiple-output (MIMO) system. Signals are sent between multiple antennas of the gateway device 202 and client devices 210, 212; the signals are coordinated to combine constructively at the device receiving the signal (either the gateway device 202 or client devices 210, 212). Specifically, using beamforming technology, for each client device 210, 212, the phases of the transmit signals are manipulated to improve directivity thereto. Efficient steering of individual streams in such a system provides overall signal gain. This can be achieved through knowledge of the channel between the transmitter and receiver. As will be discussed below, information may be extracted during this process which is used to identify a location within a user's premises. For example, various data relating to the signal quality and amplification needed to transmit signals to and/or receive signals from individual ones of the devices 210, 212 is collected. The data may include e.g., Wi-Fi channel state, RF power, delay, signal phase, signal quality, amplification, etc. The data is then used to estimate a location of a device 210, 212 (such as based on comparison to previously gathered data and/or standard or reference data).
In another embodiment, in addition to or as an alternative to the beamforming technologies utilized by the gateway device 202, location-based services are provided by leveraging infrared (IR) ports or other short-range wireless technology on a set-top box (STB) 206. According to this embodiment, IR signals are broadcast from the client devices 210 to the STB 206; the STB 206 or gateway 202 then correlates the signals to a location within the premises (i.e., the known location of the STB 206). In other words, the location of the STB 206 is known by the gateway device 202. Thus, when a signal is broadcast from the client device 210 to the STB 206 and is re-broadcast to the gateway 202, the gateway 202 is able to associate the device 210 to the known location of the STB 206 which re-broadcast the signal.
The client devices 210, 212 of the exemplary network 200 of
As will be discussed elsewhere herein, an exemplary profiling process is performed for each designated location within a premises. In one embodiment, a user uses a Location Profiler (LOCP) application to establish a “qualifier” for specific locations in a premises. The LOCP utilizes an initial profile process to gather data regarding devices at the specific locations within the premises. The qualifier (which includes a location name) is then associated to the devices by the LOCP when the device is at the particular location. The gateway 202 (and/or STB 206) is then able to automatically provide a location name to the devices 210, 212 when providing location services thereto.
The following exemplary methods may be utilized (alone or in combination) to enable the gateway 202 and/or STB 206 to learn device locations and enable location-based services.
Exemplary Location-Based Services Method—
Next, at step 304, a qualifier is assigned to each location. For example, in a user premises, the locations may be assigned qualifiers such as “kitchen”, “family room”, “dining room”, “bedroom”, etc. It is further appreciated that each location may be associated with more than one location profile. For example, if a family room is particularly large, the user may seek to generate a location profile for multiple spots within the family room (such as e.g., all four corners, etc.) to enable the system to adequately outline the borders of the room and therefore estimate when a device 210, 212 is within a given room more accurately. The user can then identify each profile as belonging to the family room (such as by labeling them “family room-1”, “family room-2”, etc.). The profiles with assigned qualifiers are then stored (step 306) at e.g., the storage entity 204.
Moreover, in “open” building architectures such as those where the boundaries between particular rooms are less salient, wireless accessibility to devices may occur from multiple locations (e.g., from one “room” to another).
At step 308, a location request is received at the gateway 202 and/or STB 206. The location request may be received in the context of an application running on a client device 210, 212. For example, an application may be running on the device which causes other applications on the device to load based on what room of a home a mobile device 210 is currently in. In one example, a recipe application, grocery shopping list application, and/or other cooking-related applications are automatically loaded on e.g., the user's mobile device 210 (such as e.g., an iPad®) when it is determined that the device is in the kitchen. In order to cause the appropriate applications to load, the application running on the mobile device 210 sends a request to the gateway 202 querying what room it is in periodically. The request can also be triggered upon an event, such as for example motion within the mobile device (e.g., using an extant accelerometer or other comparable device) indicating that the user is on the move, and hence an update is required. This latter approach in some cases saves mobile device battery power, since the transponder (e.g., Bluetooth, Wi-Fi, or other radio interface) need only wake up and transmit when motion is detected.
In another example, an energy-saving application running on the mobile client device 210 may cause non-essential or otherwise identified electronic devices to be shut down (or placed in a “sleep” mode) when the user is no longer in the vicinity of the devices. For instance, a user may carry a mobile device 210 on his/her person; when the user walks out of the living room and is gone for a pre-determined period of time, devices in the living room may be shut down (such as e.g., a television, lights, etc.). This is accomplished by the mobile device 210 application periodically (or otherwise) transmitting a location request to the gateway 202. These and other exemplary location-based services useful with the present invention will be discussed in greater detail below.
In another alternative, an application running on the gateway 202 itself may request that one or more devices in the premises be located as discussed herein, such as on an periodic or event-driven basis.
Per step 310, the gateway 202 examines the stored profiles to determine a location from which the request originated. Alternatively, the gateway 202 pings the devices of interest and awaits a return message, which is compared to the stored information at step 310. The location is identified and provided to the requesting device (such as to an application running on the mobile device 210 or running on the gateway 202 or STB 206) at step 312. It is appreciated that, in one embodiment, the user of the requesting device may be provided with the identified location (such as via a user interface). The user may be given an opportunity to affirm a correctly identified location and/or manually select a correct location in the instance the identified location is incorrect. Additionally, the system may be configured to “learn” locations as entered by a user. In other words, at the time a user manually enters a location, the gateway 202 may be configured to use the previously received information (from the location request and/or the ping response) or may ping the device 210 and use information extracted from the device response message to override any previously stored profile information for the user-entered location.
The foregoing concept can be extended to enable the application to speculate on the user's next location as well. For example, as discussed in greater detail below with respect to
As noted above, various methods may be utilized to generate location profiles (step 302), as will be discussed in greater detail subsequently herein.
Exemplary Device Profiling Methods—
Per step 402, a request message is transmitted to a device 210, 212 from the gateway 202. The request message (or “client ping”) requests a response from the device 210, 212. At step 404, a response to the request message is provided from the client device 210, 212 to the gateway 202. The response in one embodiment comprises information generally used for beamforming analysis as well as other information useful in characterizing a signal (such as e.g., receiver power, transmitter power, error rate (e.g., BER, PER, etc.), Wi-Fi channel state, RF power or signal strength (e.g., RSSI), delay, signal phase, etc.). Many of these parameters are already measured or determined as part of the extant underlying RF standard (e.g., Wi-Fi), and hence no special measures are necessary in many cases to obtain the parameters for transmission.
In an alternative embodiment, the client device 210, 212 may automatically provide a transmission to the gateway 202 (i.e., without first receiving a request from the gateway), the transmission comprising aforementioned characterization information. Such transmission may be period or event driven (e.g., motion of the device), or according to any other scheme. As noted above, the exemplary IEEE 802.11ac standard provides a mechanism for utilizing the data received at the antenna to a location of the device, although it will be appreciated that this is but one possible implementation of the invention.
In one embodiment, the gateway 202 comprises a Wi-Fi interface, and the request message (or “client ping”) is provided using multiple antennae thereof (e.g., part of a MIMO or other multi-antenna or spatial diversity array), as illustrated in
The response, as illustrated in
In one embodiment, an antenna profile is generated for each device at each location within a premises (the locations being for example designated by the user). When a particular device sends a request for location-based services (see e.g.,
At step 406, application data is used to associate the location information or antenna profile to a particular location (e.g., the room or location name in the home). In one variant, a steering matrix or table is created using the antenna profile information. An exemplary steering table is illustrated in Table 1 below. The steering table enables the gateway 202 to establish a range of values for each measured characteristic (e.g., pr, er, pt, etc.) for each antenna (e.g., α1, α2, α3, etc.); the range of values is established to include all possible values which may be received when a device is within a given location (e.g., family room, bed room, kitchen, etc.). Therefore, the steering matrix may be generated based on information received from the devices, while taking into consideration an acceptable tolerance range outside a received value. The steering matrix may be further comprised of transmitter and receiver characteristics covering the Wi-Fi channel state, RF power, delay, signal phase, signal quality, amplification, etc. Other profiling information may include information regarding a nearby Wi-Fi hotspot (such as a neighbor's Wi-Fi hotspot or AP). The combination of this information for the same client device 210 from multiple antennas may then be used for providing location-based services.
The gateway 202 then stores the location information Σ, for that client (comprised of the information from each antenna profile as correlated to a particular location), into a location database 204, such as on a storage device of the gateway 202. As noted previously with respect to
Next, at step 408, it is determined whether a profile should be generated for any additional locations. If additional locations are needed, the process begins again at step 402.
Although discussed herein with respect to generating antenna profile for mobile devices 210, it is appreciated that the herein-described methods may also be utilized to generate antenna profile for fixed devices 212 where necessary. Such methods are further configured to indicate (such as in the steering table) that antenna profile of fixed devices 212 need not be collected regularly (i.e., may be conducted less frequently, only upon installation or startup, etc.).
In another embodiment, more antennas may be placed within a premises thereby increasing the amount of data collected by each response message which in turn enables the system to more accurately predict a location of a device 210. In one variant, the additional antennas may be placed within the same gateway device 202 and controlled thereby. Alternatively, additional antennas may be stationed within one or more second gateway devices 202 or other entities placed elsewhere in the premises. The one or more second gateway devices 202 are in communication with and controlled by the primary or master gateway 202.
In yet another variant, one or more stand-alone antenna devices may be placed in various locations throughout the premises. The one or more stand-alone antennas are in communication with the gateway 202 and communicate therewith via e.g., wireless (e.g., UWB), wired (e.g., CAT-5) or fiber optical connections.
A higher resolution for determining a device location may also be provided by increasing the sounding frequency (i.e., the frequency with which the gateway 202 pings devices 210 in the premises). This approach may be implemented both during use and during the optional “learning mode” (discussed supra), so as to increase the granularity of the location determination.
In yet another embodiment, the system is further configured to generate dynamic or moving profiles. In other words, the gateway device 202 characterizes movement or predictable pathways within a premises. For example, in the illustration of
It is also appreciated that while many of the embodiments set forth herein are described in terms of an indoor paradigm (e.g., within a house, office building, shopping mall, etc.), the various aspects of the invention are in no way so limited, and may readily be applied to outdoor or hybrid indoor/outdoor applications.
It is further noted that the generated profiles may be correlated to a particular time of day and/or day of the week, or user context. For instance it may be noted that between 6:00 PM and 8:00 PM on weekdays, the user is generally found in the family room. Hence, the system can predicatively load applications and/or provide content (such as network 101 content, DVR content, etc.) designated or related to the predicted location. Likewise, it may be known that a user is typically working at home on Mondays and Fridays between 9:00 AM and 5:00 PM, and hence uses during that time period are likely business related, and hence applications or content loaded for those times can likewise be business-related in nature. At other times, the “context” changes to personal uses, and hence at least some different applications and/or content choices are provided to better suit the personal context.
Moreover, the “premises” may in fact be a workplace, and hence the contexts may be e.g., “in a meeting” (e.g., when in the main conference room of the business), “at my desk” (when in their own personal office), and so forth. The same mobile device may also traverse different premises, such that the aforementioned work-related contexts are all available when the user is at work (first premises), and the “personal” contexts are available when the user is physically located at their home (second premises).
Context may also be derived from user actions or events, or even affirmative user inputs. For instance, the user's invocation of a particular application dealing with one context (e.g., something work-related, such as a client-specific billing program) can be used as an indirect indicator of context, or at least one input to a decision process which determines context based on multiple factors such as time of day, location, etc. Hence, the user's interface (or other aspects, such as contents of an EPG, on-screen display, content availability/choices, etc.) can then be adjusted to suit that context. For example, if a work context is identified, the user's EPG choices may be geared towards more informational channels (e.g., CNN, Financial news, instructional or educational programming, etc.), whereas a personal context would be geared more towards entertainment or the like. A VoIP call or email directed to or received from someone listed in the user's “work contacts” directory or email client might also invoke the “work” context.
As another example, a user's mobile device may be configured to receive user input (such as touching a software-generated icon on a touch-screen display) to indicate a status or context (e.g., “at work” or “down time”), akin to user status identifiers associated with extant chat or messaging programs such as Yahoo® Instant Messenger or the like. Depending on context, the user's mobile device 210 (e.g. an application running thereon) can identify the context and implement loading of one or more other applications, functions, content, or features applicable to that context. In another variant, the determined context can be forwarded to the gateway 202, the latter which signals the STB or other entity regarding content or menus to be provided the user on a rendering device (e.g., configuring EPGs or on-screen displays based on the user's context (and/or location). In one such scenario, the user using their tablet computer selects “at work” as their current context, and this information is passed to the gateway (and various DSTBs distributed throughout the user's premises.
It is further appreciated that a user's mobile device may apply a passive status or context to the user based on inactivity and lack of movement. For example, when it is determined that a particular device (and therefore user) is located in a bedroom, and no activity has occurred or action has been taken with respect to the devices in that bedroom, it may be inferred that the user is asleep or occupied outside of his/her devices, and therefore the settings of the devices may be adjusted accordingly. For example, based on a time of day, devices may be shut down automatically upon user inactivity, or set to sleep mode; other settings may also be altered such as to decrease volume and/or brightness, etc. These settings may also be configured to be altered (e.g., all or portions of the device or its indigenous processes “woken up” upon detection of movement, touching the screen, detecting certain audible sounds, sensing exposure to light (e.g., the user waking up and turning on the room lights, or opening blinds in the morning), etc.
In a further variant, a lack of movement and/or interaction with client devices for a pre-determined extended length of time (which may vary based on time of day) may be utilized for home health monitoring purposes. That is, upon expiration of an extended period of time with no user activity and/or movement detected, an alert message may be transmitted from the gateway 202 to another device capable of alerting a doctor, neighbor, friend, or family member of the user. The alert may indicate the inactivity period and remind the friend or doctor to call or otherwise check in on the inactive user. Moreover, the client device audio system may be programmed to identify certain acoustic frequencies, patterns, etc. that correspond to a need for assistance; e.g., sounds corresponding to extended coughing, screams, or the word “help” recognized by a speech recognition system may also be used to trigger responses such as wake-up, transmission of a message, dialing 911 via e.g., a VoIP telephony connection, etc.
In another variant, error rate information may be obtained while data is being delivered to the mobile device 210. Generally, error rate information is used to determine whether a change in coding scheme is necessary in order to more effectively provide data services to a mobile device 210. However, in the exemplary embodiment of the present invention, the error rate information may be further used to determine when a device 210 is moving within a premises. When the device 210 is moved from a location which data delivery has been optimized for, the error rate may change; this change in error rate can be used to indicate device movement to the gateway 202. Error rate statistics over time may be correlated to a location or pathway as discussed above. For example, if movement between rooms A and B historically affects device performance according to a first profile, when the gateway 202 recognizes performance degradation according to the first profile, it can predict subsequent location.
Referring now to
At step 704, the IR signal is received at an IR receiver of the STB 206. The STB 206 can automatically identify the presence of any device 210 within its line of sight or range.
The STB 206 is in this embodiment associated with a room; hence, when the STB 206 receives the IR signal, it can optionally automatically assign a location to the device (i.e., the known location of the STB 206) as per step 706. In other words, prior to re-transmitting the signal received from the device 210 to the gateway 202, the STB 206 can attach information identifying the location of the STB 206 thereto. In this manner, when the re-transmitted signal is received at the gateway 202, it will have enough information to enable the gateway 202 to identify the device 210 and associate it to a location (i.e., the location of the STB 206). Alternatively, the correlation or association of the device 210 to the known location of the STB 206 may be performed at the gateway 202. The gateway 202 may be provided (in the re-transmitted signal) information identifying the device 210. The gateway 202 additionally uses information in the re-transmitted signal to identify the STB 206 from which the signal came, then, based on information already known to the gateway 202 about the location of the STB 206, the gateway 202 can assign a location to the device 210.
The device 210 location (or alternatively a retransmission of the IR signal indicating the device 210 identity and the STB 206 identity) is then transmitted from the STB 206 to the gateway 202 (step 708). Transmission may occur wirelessly, such as over Wi-Fi, Bluetooth, UWB, etc. or via a wired connection such as a CAT-5 cable, coaxial cable (e.g., MoCA arrangement), or other medium. In this manner, IR is used to automatically sense the location of a device 210.
The gateway 202 further correlates the message received from the STB 206 (i.e., the retransmission of the message originally sent from the mobile device) with the steering profile of the client device 210 (identified in the signal) to automatically associate any messages from that STB 206 to a particular (i.e., known) location. The gateway 202 may store the transmitted information at the storage entity 204 in the place of or in addition to a previously generated profile for that device 210. In other words, the profile of signal characteristics is not affected by the IR signal retransmission; rather, the location is simply stored as a current location of the device 210. The current location information is not permanent, but rather as additional IR signals are received and analyzed by the STB 206 and transmitted to the gateway 202, the device 210 current location is updated.
In yet another embodiment, additional IR receivers may be established within the premises, each being assigned a particular known location and each being in communication with the gateway device 202 (such as via any of the aforementioned wireless or wired communication mediums). It is appreciated that while discussed herein with respect to a STB 206, the IR receiver may be a component of any number of devices. For example, the IR receiver may be a device having only IR receiver capabilities and transmission capabilities (for communication to the gateway 202).
The foregoing embodiment may be useful, for example, in large public spaces having multiple distinct sub-sections (such as e.g., bookstores, malls, coffee shops, food courts, museums, sports arenas, conventions, job fairs, etc.). The IR mechanism discussed above is particularly useful for enabling close range location-based services. The close-range needed to make use of the IR feature ensures close proximity of the device to a particular booth, store, exhibit, etc. With direct knowledge of a device location within a small distance, content relating specifically to a precise location may be provided (such as e.g., coupons, additional information, updates, etc.).
In yet another embodiment, the applications discussed herein may further make use of a mechanism for identifying a device location based on radio frequency identification (RFID) and/or near field communication (NFC) standards. For instance, the protocols disclosed in “EPC™ Radio-Frequency Identity Protocols Class-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960 MHz Version 1.2.0” dated Oct. 23, 2008, International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) standard 18000-3 entitled “Information technology—Radio frequency identification for item management, Part 3: Parameters for air interface communications at 13.56 MHz” Third Edition, dated Nov. 15, 2011, ISO/IEC standard 14443-2 entitled “Identification cards—Contactless integrated circuit(s) cards—Proximity cards, Part 2: Radio frequency power and signal interfaces” dated Mar. 26, 1999, and ISO/IEC standard 14443-4 entitled “Identification cards—Contactless integrated circuit(s) cards—Proximity cards, Part 4: Transmission protocol” dated Mar. 10, 2000, which are each incorporated herein by reference in their entirety, may be utilized.
In one implementation, the gateway 202 is configured to act as an interrogator with respect to the RF (e.g., NFC or RFID) chips disposed within mobile phones and other mobile or wireless devices (user devices 210). It is appreciated that many devices are currently manufactured to have indigenous NFC chips, however a passive or active RFID tag (including those as a part of an NFC suite) may be provided to a device 210 after purchase thereof. The gateway 202 interrogates all tags (devices) within range to find a device identifier. The range within which the gateway 202 may interrogate may be tuned such as by adjusting the transmit power, receiver sensitivity, operational frequency, or other antenna or transceiver features. In the exemplary passive implementation, each device backscatters the interrogation signal and includes its unique identifier. Subsequently, the gateway 202 may address the individual devices, and read and write to the contents of the memory of each. As noted above, the range of interrogation by the gateway 202 can be manipulated to a known distance. Thus, the gateway 202 may provide information to the devices regarding a means for accessing content which is specific to the particular known location or otherwise providing location-based services thereto. For example, coupons for a nearby business and/or information regarding the particular location (such as movie show times, maps, hours of operation, etc.) may be provided.
It is appreciated that mere response from the interrogated device can be used as an indication of location. For instance, if the effective range of the interrogator at 13.5 KHz is 10 feet, and a given device backscatters the interrogation signal, then it is presumed to be within ten feet of the interrogator, and hence its location is known to that level of precision.
Moreover, so-called “range gating” can be employed, such as where the interrogator has longer, intermediate, and shorter range transceivers or modes. In this case, a first reply at the longer range mode indicates that the responsive device is within the longer range. Hence, a reply to follow up interrogation at the intermediate range (but not to one at the shorter range) indicates that the device is located between the maximum range of the intermediate mode and the maximum range of the shorter mode. Such gating can be used to, inter alia, further refine a range/position estimate, and to detect movement towards or away from the interrogator (i.e., at least the radial or range component of movement of the mobile device can be resolved).
In yet another embodiment, the well known Bluetooth technology may be utilized for communication between the gateway 202 and a device 210. For instance, data may be exchanged over short distances (using short-wavelength radio transmissions in the ISM band from 2400-2480 MHz) to cause pairing of the gateway 202 and device 210. Thus, when a device 210 is close enough to be paired to the gateway 202, it will be known to the gateway 202 that the device 210 is within a given distance of the device. As discussed elsewhere herein, once the location of the device is known, the gateway 202 may provide location-based services (such as enabling the device to load particular applications, receive information and/or advertisements or coupons targeted to the location, etc.).
Exemplary Gateway Device—
In the illustrated embodiment, the processor 908 is configured to run at least a profile generation application 910, a location assignment application 912, and a retrieval and delivery application 914 thereon, although other software/logic architectures may readily be substituted. The profile generation application 910 is a computer application configured to generate individual device profiles. As discussed previously, the individual device profiles comprise a plurality of data received from a device 210, 212 when the device 210, 212 is located at a particular location within a premises.
In one embodiment, the profile generation application 910 after pinging the client devices 210, receives response messages therefrom. The response messages comprise information generally used for beamforming analysis as well as other information useful in characterizing a signal. The reported information may include e.g., whether a hot-spot is nearby, error rate information obtained during data delivery, Wi-Fi channel state, RF power, delay, signal phase, signal quality, amplification, etc. The device profile may include the previously referenced “antenna profile”, Σ, which is generated for each device at each location within a premises. The device profile may further comprise a steering table or matrix. The steering table enables the gateway 202 to, inter alia, establish a tolerance range for the measured values for each of e.g., pr, er, pt, etc. for each antenna; the range of values is established to include all possible values which may be received when a device is within a given location (e.g., family room, bed room, kitchen, etc.).
The profile generation application 910 may further receive a re-transmission of IR broadcast signals received at a STB 206 (or other IR receiver) from a plurality of client devices 210, 212. As discussed above, the re-transmission comprises information uniquely identifying the device from which the IR broadcast signal was received and information identifying the STB 206 which re-transmitted the signal.
The location assignment application 912 is in one embodiment configured to associate a qualifier (e.g., name) to the locations in the premises. As indicated above, the locations are identified and/or designated by the user. The location assignment application 912 associates the data received at the profile generation application 910 to a particular location. One or more profiles are therefore associated, via the location assignment application 912, to a particular user-determined location. For example, the locations may be assigned qualifiers such as “kitchen”, “family room”, “dining room”, “bedroom”, etc. In addition, the location assignment may cover a range of data extracted from multiple profiles which were used to determine an overall space that is to be considered associated to a particular location (or room within a premises).
It is further appreciated that the gateway device 202 may be provided with location assignment information from e.g., a STB 206 or other IR transceiver in the form of a re-transmission of a device 210 IR broadcast. In one embodiment, the location assignment application 912 associates the device 210 information to a known location of the STB 206 (or IR transceiver).
The retrieval and delivery application 914 is configured to retrieve stored information regarding the location of a device 210, 212 (such as by performing a query of a storage entity).
One or more additional applications or modules may be provided to, inter alia, enable a user to manually correct an incorrectly identified device location, and subsequently store an updated device profile and location assignment. Additionally, applications or modules may be provided to enable the gateway 202 to “learn” locations as entered by a user. For example, at the time a user manually enters a location, the application may be configured cause the device 210 to be pinged, and subsequently use information extracted from the most recent device response message to override any previously stored profile information for the user-entered location.
In yet another embodiment, one or more applications configured to analyze information extracted from the device 210 return messages over time may be provided in order to generate one or more rules for which locations within a premises are near one another. The application(s) then utilize the rules to estimate or predict movement between locations within the premises.
A network interface 902 and a premises interface 904 are further illustrated. The network interface 902 is in the exemplary embodiment configured to provide content and data delivery to and from the MSO network 101. The premises interface 904 provides communication between the gateway 202 and various devices within a premises, such as e.g., client mobile devices 210, fixed devices 212, and STB 206. For example, the premises interface 904 enables communication of client ping messages, as well as receipt of response messages and location requests. Communication between the client devices 210 and premises interface 904 may occur via a wired or wireless communication therewith, such as via e.g., IEEE-1394 (so called “FireWire”), USB, LAN/WAN, Wireless, HDTV, NTSC, etc. communications.
Exemplary Set-top Box—
The network interface 1002 provides, inter alia, content and data delivery to and from the MSO network 101, such as the herein described HFC network, an internetwork, etc. The premises interface 1004 provides inter alia, communication between the STB 206 and various devices within a premises, such as e.g., client mobile devices 210, fixed devices 212, and the gateway 202. For example, the premises interface 1004 enables receipt of IR broadcast messages from the devices 210 (via the IR receiver 1012), as well as re-transmission of the device messages to the gateway 202 via e.g. IEEE-1394 (so called “Firewire”), USB, LAN/WAN, Wireless, HDTV, NTSC, etc. communication therewith.
In the illustrated embodiment, the processor 1008 is configured to run at least a location-based services application 1010 thereon. The location-based services application 1010 is configured to, when IR signals are received (i.e., signals which were broadcast from one or more client devices 210), identify the device 210 from which they were received (such as via an embedded identifier or other such identifying information within the signal). In a first embodiment, the location-based services application 1010 causes the received IR signal to be re-transmitted to a gateway apparatus 202 without modification thereof (i.e., acts as a repeater). A Wi-Fi premises interface 1004 or other air interface (e.g., Bluetooth, UWB, etc.) may be utilized for wirelessly communicating the re-transmission signal. It is appreciated, however, that the premises interface 1004 and/or communication with the gateway 202 may occur via any number of wired and/or wireless communications modalities of the type previously set forth herein. According to this embodiment, and as discussed previously, the gateway 202 assigns a location to the uniquely identified device 210, which matches the location of the STB 206 from which the re-transmission was received.
Alternatively, the location-based services application 1010 may be configured to append the message to additionally include an assigned location. In other words, the application 1010 appends a previously determined location identifier to the received messages. The location identifier may be previously determined by the gateway apparatus 202 (as discussed above with respect to
Exemplary Applications and Implementations—
The herein described apparatus and methods may advantageously be used to provide location-based services in any number of different use cases or scenarios.
In one such case, the location-based services include services which enable particular applications and/or content to be automatically loaded or provided when the user enters a particular location (e.g., a particular room in their house) or a context (e.g., business versus personal).
In a first variant, an application is run on a client mobile device 210 which is configured to, when it is informed by the gateway 202 of the location of the device 210, load particular applications. For example, when the device 210 receives information from the gateway 202 that the device is in the user's kitchen, a grocery shopping list and/or recipe or cooking application are loaded on the device. The device may additionally load content such as most recent content from a cooking-related site, programming content (such as from the Internet and/or an MSO network 101), etc.
In another example, if the device is instead entering a bedroom, the device may load games, educational tools, etc. Generally, the applications and/or content which are caused to be loaded or delivered to the devices are related to the context of the location of the device or user (or that user's use context based on a temporal or other parameter, which may also consider or be irrespective of location). The applications and/or content to be delivered based on location may be manually selected by a user of the application running on the mobile device 210, and/or may be pre-set within the application itself, or according to other methods previously described herein.
It is further appreciated that the foregoing application may instead be run on the gateway 202 or STB 206, thus enabling control of the mobile devices 210 thereby. In addition, the user may create custom home screens for different rooms that feature different applications (recipe files, books, etc.) or select from among network pre-configured home screens for each room type (e.g., bedroom, kitchen, living room, etc.).
In another variant, an energy-saving application is run on a client mobile device 210 which is configured to, when it is informed by the gateway 202 of the location of the device 210, cause non-essential or otherwise identified electronic devices to be shut down (or placed in a “sleep” mode) when the user is no longer in the vicinity of these devices, and/or turn certain devices on when the user is located nearby. According to this variant, the location of a mobile device 210 associated with the user's person is tracked throughout the premises as discussed above. Powering on/off and/or changing the settings (such as air conditioner/heater settings) of the devices may be accomplished via e.g., wireless or wired communication of a command message thereto from e.g., the gateway 202, the mobile device 210, and/or the STB 206.
In another embodiment, the location-based services include services which provide information and/or advertisement opportunities when the user is near a particular public or business location. For example, in large public spaces, such as a zoo, museum, sports arena, convention, job fair, or park, the proximity of a user device 210 to a particular exhibit, ride, or information point (having an IR or other wireless receiver as discussed above). In this manner, information regarding the exhibit, ride, or public area generally (such as maps, emergency information, etc.) may be automatically provided to the device 210. In another example, businesses such as malls, bookstores, coffee shops, food courts, etc. may use the herein-described apparatus and methods to provide e.g., coupons, additional information, updates, etc. relating to a particular location (booth, store, item for sale, etc.).
In yet another embodiment, the apparatus and methods disclosed in co-owned, co-pending U.S. patent application Ser. No. 12/631,713 filed on Dec. 4, 2009 entitled “APPARATUS AND METHODS FOR MONITORING AND OPTIMIZING DELIVERY OF CONTENT IN A NETWORK”, and issued as U.S. Pat. No. 9,519,728 on Dec. 13, 2016, which is incorporated herein by reference in its entirety, is utilized consistent with the location-based services of the present invention to optimize content delivery to multiple user devices. Methods and apparatus for providing location-based services further provide the user (e.g., a subscriber of an IP, cable or satellite network) with the best possible “user experience” at all times, depending on the various hardware/software environments they have available to them, and their current usage needs and preferences. In one implementation of the foregoing, an optimization and monitoring entity (OME) is utilized in conjunction with other network and user premises components to provide the aforementioned functionality. The OME includes one or more software applications which work in conjunction with one another (and with one or more content servers) to determine, evaluate, and provide notification to a user of one or more alternative content delivery platforms (based on e.g., the user's location within a premises), such as for example when a request for content is received. Alternative services, transports, and delivery models, may also be recommended in another variant of the invention, so as to optimize the user's experience in any given scenario within the limitations of the available devices and technology.
In one exemplary use case, requests for content are received at a content server, and forwarded to the OME. The content server may satisfy the request, or may first require selection of a delivery platform. Information identifying the requesting device (such as IP address, MAC address, etc.) and/or the subscriber account or specific user (such as account number, physical address, login/password information, etc.) is derived from or embedded in the content requests, or otherwise retrieved from information contained within the request. Information identifying the user's location within a premises is also provided via the methods and apparatus described herein. The OME uses the collected information to determine whether the requesting device is registered to a known user account by comparing the identification to a database of registered accounts and devices. The OME further uses the aforementioned database to compile a list of all of the other known client devices in a specific user's account. Software applications running on the OME differentiate the various features and capabilities of the different types of client devices registered to the user account, and which may be used to receive content (including e.g., supported codecs, etc.). Additionally, the location of the various client devices may be identified, thereby enabling location-based services to be provided as discussed elsewhere herein.
In another variant, the OME further comprises a “recommendation engine” such as that disclosed in co-owned, co-pending U.S. patent application Ser. No. 12/414,576 filed on Mar. 30, 2009 and entitled “RECOMMENDATION ENGINE APPARATUS AND METHODS”, which is incorporated herein by reference in its entirety. The OME recommendation engine determines whether requested content may be provided to the same user on a different platform; e.g., on a different one of the client devices associated with the user's account. Such an alternative device may be recommended based on e.g., location of the user and/or devices, video/audio quality, picture size, bandwidth availability, and/or any other additional capabilities of the recommended client device, or may be recommended based on historical usage or other information about the user (or a specification of user preferences associated with the account and accessed by the OME).
In one implementation, a list of the alternative delivery platforms and/or modes is presented to a user via a notification generated by the OME (or generated by the CPE after being triggered by the OME). The notifications sent to the client device(s) indicate which, if any, of the user's other devices may receive the content alternatively (or in addition to) the content being received at the requesting device and may additionally include a location of each. Alternatively, the list of devices may be filtered to include only those devices within the same general location within the premises. The notifications generated/triggered by the OME are, in one embodiment, interactive in nature and provide a user the ability to select one or more of the presented content delivery platforms, as well as features or configurations associated therewith.
The client devices requesting content and/or being recommended for the delivery of content include, inter alia, consumer premises devices (CPE) 106 (such as digital set top boxes (STB), IPTV devices, media bridges (MB), converged premises devices (CPD), etc.), personal video recorders (PVR), digital video recorders (DVR), network DVR, computer devices (such as personal computers and laptop computers), and mobile devices (including personal media devices (PMD), tablets, and mobile telephones/smartphones). In one variant of the invention (so-called “chain mode”), the recommendation engine evaluates two or more communicating client devices along a “rendering path” to determine the ultimate delivery configuration to the user (e.g., to prevent instances where the first device encountered in the chain provides the recommendation engine with a false representation of the quality of the entire rendering chain of devices), thereby making selection based on the “weakest link” of the chain.
In another aspect of the invention, a centralized control device is disclosed which permits the transfer or migration of content delivery sessions (e.g., SIP-based IPTV sessions or the like) between two or more devices. In one implementation, the user's premises gateway or DSTB or PC is used as the host device for a user interface which shows the various premises (and “off-net”) devices associated with the user/subscriber account or premises network, and their interconnectivity. UI functionality (e.g., a multi-touch-screen GUI, drag-and-drop, speech recognition application, or other interface/input device) allows the user to rapidly designate particular devices for communication, establishment of a session/delivery of content, and/or transfer of existing communication sessions between capable devices (such as may be determined by the OME recommendation engine). Additionally, the herein-described methods and apparatus may be used to enable the system to automatically follow the user as they move between rooms. That is to say, a device associated with the user's person (such as e.g., a mobile device 210) indicates to the OME, gateway 202, etc. where the user is within a premises. The system then automatically transfers content to the devices within the general location of the user. As noted above, various profiles may be utilized to predict a pattern of movement within the user premises, and may further be used to predict where content should be moved in order to follow the user.
For example, when a user who is viewing content on a mobile device enters their living room, the content is automatically presented on a television in that room (either in place of delivery to the mobile device, or in addition thereto); when the user moves to the bedroom, a device in the bedroom (such as e.g., a desktop or laptop computer, another television, and/or a tablet computer) may pick up delivery of the content.
Additional location-based services which may utilize the herein-described methods and apparatus include, e.g., providing parental controls based on a known location of a child or children within a premises. For instance, the mechanisms discussed above may be utilized to determine that a particular device which is associated to a child (e.g., their tablet computer) has entered a particular room (e.g., the family room, a bedroom, etc.). Once the gateway 202 determines that the child has entered the room, a message is transmitted from the gateway 202 to one or more devices in the room indicating the presence of the child, and thereby causing a set of rules or parental controls to be implemented. The rules or parental controls may be pre-configured by the subscriber and may include e.g., ratings requirements (no content rated R, etc.), time limits for use of the device, designated hours of acceptable use of certain devices, automatic recording of viewed programming, generation or reports or data relating to device usage, content forwarding or mirroring at an established monitor device (such as a device known to be in use by a parent via the same mechanism used to establish a location of the child), restrictions on Internet URLs, etc.
Additionally, the location-based services may include providing a device profile based on location. For example, the brightness or volume settings of a particular device may be adjusted to user pre-determined settings based on where the device is located. In other words, the user may establish settings that a device to have decreased volume and/or brightness when it is determined that the device is currently in a bedroom, and increased volume and/or brightness when it is determined that the device has left the user's premises (i.e., is outside of the home). Moreover, indigenous light sensing apparatus on the user device (e.g., a CMOS or CCD imager) can be used to detect ambient light conditions of the current location, and adjust one or more device settings accordingly. For example, when a user transitions from a bright ambient setting to a dim one, the screen brightness (and any control backlighting) may be intensified.
Similar logic can be applied to acoustic attributes; e.g., where a heavy background “din” is present, the volume level of any audible emanations from the device is increased to aid the user hearing them over the din.
In another variant, the determination that a device is leaving or has left a premises causes the device to enter a protected or theft deterrence mode. That is, when the device goes out of range, password protection is implemented and the password is required to reactivate use.
In yet another variant, when the location determination (discussed above) identifies that the user device is within range of a set-top box, gateway, or other MSO-enabled device, a message indicating the location causes the user device to run a program that enables a remote control mode. In other words, the device can be used as a handheld control device for the set-top box when it is determined to be near to the set-top box.
Still further, location-based services may be implemented to enable individual customization of a viewing experience. In one such implementation, when it is determined that a device (such as a mobile device) associated to a particular user is within a given distance to a set-top box or other such device, the gateway 202 notifies the set-top box of the identity of the particular individual currently viewing content thereat. The set-top box may then utilize the identity of the individual to access a customized profile including content, playlists, recommendations, URLs or functions, display theme/settings/layout, etc. specific to that viewer. In the instance more than one individual is identified, a modified profile may be used to find content, playlists, recommendations, settings, etc. which are more widely applicable. Alternatively, the viewers may be asked to select from among the available profiles.
In addition, the identification of movement of the user away from a set-top box may trigger the mobile device to obtain content currently being viewed by the user for mobile delivery thereof. In other words, identified movement of the user device away from the set-top box in one variant causes the gateway 202 to transmit a message to the mobile device including information relating to the currently viewed programming content. The mobile device uses this information to access the content and provide it to the user “to go”, such as via a WLAN (e.g., Wi-Fi), WiMAX, LTE, or other high-bandwidth wireless interface available on the user device. In one embodiment, playback of the content may begin immediately, and synchronize with the playback on the set-top box so as to provide uninterrupted content delivery.
Movement of the user away from the set-top box and/or gateway may further trigger a message to be displayed to the user indicating that they are leaving the range of their Wi-Fi network, moving into another network, etc.
In another embodiment, location-based services provide a mechanism whereby content stored at the user's DVR (or other storage entity) is automatically synchronized to the user's device based on the device being identified as currently near the DVR. For example, the user may authorize that all new episodes of his/her favorite show be pushed to his/her user mobile device any time the device is sufficiently near to the DVR which has stored the episodes thereon (the proximity being based in one embodiment on the extant wireless capabilities of the user device, such as WLAN range limitations). Additionally, when a device is identified as nearing a public or other Wi-Fi hotspot not particularly associated with the user of the device, the device may be triggered to request content updates (such as the aforementioned “new episodes”) from the network for storage at the device.
Still further, the present invention may be implemented in conjunction with a home security system having sensors (such as e.g., those of Zigbee® which use two-way wireless technology and Wi-Fi cameras) established at user-designated locations in the home. One such implementation may utilize the so-called “Intelligent Home” service of the Assignee herein. As used therein, various sensors and/or cameras are established throughout a user's home and labeled according to the room where each is placed. They each communicate wirelessly to a control device. In one embodiment, the control device may further communicate to a client device (e.g., wireless-enabled mobile device). The wireless profile or physical signature (e.g., that discussed with respect to
It will be recognized that while certain aspects of the invention are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods of the invention, and may be modified as required by the particular application. Certain steps may be rendered unnecessary or optional under certain circumstances. Additionally, certain steps or functionality may be added to the disclosed embodiments, or the order of performance of two or more steps permuted. All such variations are considered to be encompassed within the invention disclosed and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the invention as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the invention. The foregoing description is of the best mode presently contemplated of carrying out the invention. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of the invention. The scope of the invention should be determined with reference to the claims.
This application is a divisional of and claims priority to co-owned and co-pending U.S. patent application Ser. No. 15/728,452 of the same title filed Oct. 9, 2017, issuing as U.S. Pat. No. 10,278,008 on Apr. 30, 2019, which is a divisional of and claims priority to U.S. patent application Ser. No. 14/511,079 of the same title filed Oct. 9, 2014, issued as U.S. Pat. No. 9,788,149 on Oct. 10, 2017, which is a divisional of and claims priority to co-owned U.S. patent application Ser. No. 13/600,064 of the same title filed Aug. 30, 2012, issued as U.S. Pat. No. 8,862,155 on Oct. 14, 2014, each of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4521881 | Stapleford et al. | Jun 1985 | A |
| 4546382 | McKenna et al. | Oct 1985 | A |
| 4602279 | Freeman | Jul 1986 | A |
| 4905080 | Watanabe et al. | Feb 1990 | A |
| 4930120 | Baxter et al. | May 1990 | A |
| 5155591 | Wachob | Oct 1992 | A |
| 5313454 | Bustini et al. | May 1994 | A |
| 5373315 | Dufresne et al. | Dec 1994 | A |
| 5481294 | Thomas et al. | Jan 1996 | A |
| 5497185 | Dufresne et al. | Mar 1996 | A |
| 5600364 | Hendricks et al. | Feb 1997 | A |
| 5675647 | Garneau et al. | Oct 1997 | A |
| 5734720 | Salganicoff | Mar 1998 | A |
| 5758257 | Herz et al. | May 1998 | A |
| 5774170 | Hite et al. | Jun 1998 | A |
| 5793409 | Tetsumura | Aug 1998 | A |
| 5812642 | Leroy | Sep 1998 | A |
| 5862312 | Mann et al. | Jan 1999 | A |
| 5878324 | Borth et al. | Mar 1999 | A |
| 5914945 | Abu-Amara et al. | Jun 1999 | A |
| 5926205 | Krause et al. | Jul 1999 | A |
| 5929849 | Kikinis | Jul 1999 | A |
| 5935206 | Dixon et al. | Aug 1999 | A |
| 5956037 | Osawa et al. | Sep 1999 | A |
| 5963844 | Dail | Oct 1999 | A |
| 5974299 | Massetti | Oct 1999 | A |
| 6002393 | Hite et al. | Dec 1999 | A |
| 6029045 | Picco et al. | Feb 2000 | A |
| 6047327 | Tso et al. | Apr 2000 | A |
| 6081830 | Schindler | Jun 2000 | A |
| 6088722 | Herz et al. | Jul 2000 | A |
| 6092178 | Jindal et al. | Jul 2000 | A |
| 6124878 | Adams et al. | Sep 2000 | A |
| 6128316 | Takeda et al. | Oct 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6161142 | Wolfe et al. | Dec 2000 | A |
| 6169728 | Perreault et al. | Jan 2001 | B1 |
| 6177931 | Alexander et al. | Jan 2001 | B1 |
| 6182050 | Ballard | Jan 2001 | B1 |
| 6202210 | Ludtke | Mar 2001 | B1 |
| 6211901 | Imajima et al. | Apr 2001 | B1 |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6219840 | Corrigan et al. | Apr 2001 | B1 |
| 6240553 | Son et al. | May 2001 | B1 |
| 6249680 | Wax | Jun 2001 | B1 |
| 6272176 | Srinivasan | Aug 2001 | B1 |
| 6282713 | Kitsukawa et al. | Aug 2001 | B1 |
| 6330609 | Garofalakis et al. | Dec 2001 | B1 |
| 6353626 | Sunay et al. | Mar 2002 | B1 |
| 6359711 | Cole | Mar 2002 | B1 |
| 6378130 | Adams | Apr 2002 | B1 |
| 6389538 | Gruse et al. | May 2002 | B1 |
| 6396055 | Biedendorf | May 2002 | B1 |
| 6434141 | Oz et al. | Aug 2002 | B1 |
| 6446261 | Rosser | Sep 2002 | B1 |
| 6463585 | Hendricks et al. | Oct 2002 | B1 |
| 6467089 | Aust et al. | Oct 2002 | B1 |
| 6498783 | Lin | Dec 2002 | B1 |
| 6502076 | Smith | Dec 2002 | B1 |
| 6549718 | Grooters et al. | Apr 2003 | B1 |
| 6560578 | Eldering | May 2003 | B2 |
| 6590865 | Ibaraki et al. | Jul 2003 | B1 |
| 6601237 | Ten et al. | Jul 2003 | B1 |
| 6604138 | Virine et al. | Aug 2003 | B1 |
| 6615039 | Eldering | Sep 2003 | B1 |
| 6615251 | Klug et al. | Sep 2003 | B1 |
| 6647548 | Lu et al. | Nov 2003 | B1 |
| 6671736 | Virine et al. | Dec 2003 | B2 |
| 6681393 | Bauminger et al. | Jan 2004 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6700624 | Yun | Mar 2004 | B2 |
| 6704930 | Eldering et al. | Mar 2004 | B1 |
| 6711148 | Hills | Mar 2004 | B1 |
| 6718551 | Swix et al. | Apr 2004 | B1 |
| 6725461 | Dougherty et al. | Apr 2004 | B1 |
| 6738978 | Hendricks et al. | May 2004 | B1 |
| 6742187 | Vogel | May 2004 | B1 |
| 6763391 | Ludtke | Jul 2004 | B1 |
| 6771290 | Hoyle | Aug 2004 | B1 |
| 6775843 | McDermott | Aug 2004 | B1 |
| 6799047 | Bahl et al. | Sep 2004 | B1 |
| 6813776 | Chernock et al. | Nov 2004 | B2 |
| 6842783 | Boivie et al. | Jan 2005 | B1 |
| 6859845 | Mate | Feb 2005 | B2 |
| 6891841 | Leatherbury et al. | May 2005 | B2 |
| 6898762 | Ellis et al. | May 2005 | B2 |
| 6901606 | Wright et al. | May 2005 | B2 |
| 6909837 | Unger | Jun 2005 | B1 |
| 6915528 | McKenna, Jr. | Jul 2005 | B1 |
| 6986156 | Rodriguez et al. | Jan 2006 | B1 |
| 6990680 | Wugofski | Jan 2006 | B1 |
| 7007170 | Morten | Feb 2006 | B2 |
| 7017179 | Asamoto et al. | Mar 2006 | B1 |
| 7024676 | Klopfenstein | Apr 2006 | B1 |
| 7039928 | Kamada et al. | May 2006 | B2 |
| 7065216 | Benaloh et al. | Jun 2006 | B1 |
| 7069573 | Brooks et al. | Jun 2006 | B1 |
| 7075945 | Arsenault et al. | Jul 2006 | B2 |
| 7086077 | Giammaressi | Aug 2006 | B2 |
| 7100183 | Kunkel et al. | Aug 2006 | B2 |
| 7109848 | Schybergson | Sep 2006 | B2 |
| 7143431 | Eager et al. | Nov 2006 | B1 |
| 7146627 | Ismail et al. | Dec 2006 | B1 |
| 7152237 | Flickinger et al. | Dec 2006 | B2 |
| 7155508 | Sankuratripati et al. | Dec 2006 | B2 |
| 7165268 | Moore et al. | Jan 2007 | B1 |
| 7174126 | McElhatten et al. | Feb 2007 | B2 |
| 7191461 | Arsenault et al. | Mar 2007 | B1 |
| 7197472 | Conkwright et al. | Mar 2007 | B2 |
| 7213036 | Apparao et al. | May 2007 | B2 |
| 7222078 | Abelow | May 2007 | B2 |
| 7228555 | Schlack | Jun 2007 | B2 |
| 7237250 | Kanojia et al. | Jun 2007 | B2 |
| 7240355 | Eldering et al. | Jul 2007 | B1 |
| 7242988 | Hoffberg et al. | Jul 2007 | B1 |
| 7246150 | Donoho et al. | Jul 2007 | B1 |
| 7246172 | Yoshiba et al. | Jul 2007 | B2 |
| 7248694 | Husemann et al. | Jul 2007 | B2 |
| 7266836 | Anttila et al. | Sep 2007 | B2 |
| 7280737 | Smith | Oct 2007 | B2 |
| 7281261 | Jaff et al. | Oct 2007 | B2 |
| 7308415 | Kimbrel et al. | Dec 2007 | B2 |
| 7317728 | Acharya et al. | Jan 2008 | B2 |
| 7327692 | Ain et al. | Feb 2008 | B2 |
| 7334044 | Allen | Feb 2008 | B1 |
| 7340759 | Rodriguez | Mar 2008 | B1 |
| 7346688 | Allen et al. | Mar 2008 | B2 |
| 7352775 | Powell | Apr 2008 | B2 |
| 7353543 | Ohmori et al. | Apr 2008 | B2 |
| 7355980 | Bauer et al. | Apr 2008 | B2 |
| 7356751 | Levitan | Apr 2008 | B1 |
| 7357775 | Koh | Apr 2008 | B1 |
| 7363371 | Kirby et al. | Apr 2008 | B2 |
| 7363643 | Drake et al. | Apr 2008 | B2 |
| 7367043 | Dudkiewicz et al. | Apr 2008 | B2 |
| 7369750 | Cheng et al. | May 2008 | B2 |
| 7379494 | Raleigh et al. | May 2008 | B2 |
| 7444655 | Sardera | Oct 2008 | B2 |
| 7457520 | Rosetti et al. | Nov 2008 | B2 |
| 7464179 | Hodges et al. | Dec 2008 | B2 |
| 7487363 | Alve et al. | Feb 2009 | B2 |
| 7567565 | La Joie | Jul 2009 | B2 |
| 7567983 | Pickelsimer et al. | Jul 2009 | B2 |
| 7577118 | Haumonte et al. | Aug 2009 | B2 |
| 7602820 | Helms et al. | Oct 2009 | B2 |
| 7603529 | MacHardy et al. | Oct 2009 | B1 |
| 7650319 | Hoffberg et al. | Jan 2010 | B2 |
| 7712125 | Herigstad et al. | May 2010 | B2 |
| 7720432 | Colby et al. | May 2010 | B1 |
| 7729940 | Harvey et al. | Jun 2010 | B2 |
| 7730509 | Boulet et al. | Jun 2010 | B2 |
| 7783316 | Mitchell | Aug 2010 | B1 |
| 7801803 | Forlai | Sep 2010 | B2 |
| 7860507 | Kalika et al. | Dec 2010 | B2 |
| 7870599 | Pemmaraju | Jan 2011 | B2 |
| 7900052 | Jonas et al. | Mar 2011 | B2 |
| 7900229 | Dureau | Mar 2011 | B2 |
| 7930558 | Hori | Apr 2011 | B2 |
| 7930715 | Hendricks et al. | Apr 2011 | B2 |
| 7954131 | Cholas et al. | May 2011 | B2 |
| 8028322 | Riedl et al. | Sep 2011 | B2 |
| 8041785 | Mazur et al. | Oct 2011 | B2 |
| 8042131 | Flickinger | Oct 2011 | B2 |
| 8065703 | Wilson et al. | Nov 2011 | B2 |
| 8084792 | Lehmann et al. | Dec 2011 | B2 |
| 8099757 | Riedl et al. | Jan 2012 | B2 |
| 8205226 | Ko et al. | Jun 2012 | B2 |
| 8214256 | Riedl et al. | Jul 2012 | B2 |
| 8296185 | Isaac | Oct 2012 | B2 |
| 8306634 | Nguyen et al. | Nov 2012 | B2 |
| 8341242 | Dillon et al. | Dec 2012 | B2 |
| 8347341 | Markley et al. | Jan 2013 | B2 |
| 8365213 | Orlowski | Jan 2013 | B1 |
| 8380226 | Clipsham | Feb 2013 | B2 |
| 8396055 | Patel et al. | Mar 2013 | B2 |
| 8396056 | Dalton, Jr. et al. | Mar 2013 | B2 |
| 8442265 | Bosworth et al. | May 2013 | B1 |
| 8458125 | Chong, Jr. et al. | Jun 2013 | B1 |
| 8484511 | Engel et al. | Jul 2013 | B2 |
| 8516529 | Lajoie et al. | Aug 2013 | B2 |
| 8561113 | Cansler et al. | Oct 2013 | B2 |
| 8571931 | Riedl et al. | Oct 2013 | B2 |
| 8583484 | Chalawsky et al. | Nov 2013 | B1 |
| 8621501 | Matheny et al. | Dec 2013 | B2 |
| 8713623 | Brooks | Apr 2014 | B2 |
| 8769559 | Moon et al. | Jul 2014 | B2 |
| 8862155 | Stern et al. | Oct 2014 | B2 |
| 8866911 | Sivertsen | Oct 2014 | B1 |
| 8898270 | Stack et al. | Nov 2014 | B1 |
| 8997136 | Brooks et al. | Mar 2015 | B2 |
| 9003436 | Tidwell et al. | Apr 2015 | B2 |
| 9027062 | Patel et al. | May 2015 | B2 |
| 9071859 | Lajoie | Jun 2015 | B2 |
| 9215423 | Kimble et al. | Dec 2015 | B2 |
| 1047734 | Sinha et al. | Nov 2019 | A1 |
| 20010001160 | Shoff et al. | May 2001 | A1 |
| 20010013123 | Freeman et al. | Aug 2001 | A1 |
| 20010030785 | Pangrac et al. | Oct 2001 | A1 |
| 20010050901 | Love et al. | Dec 2001 | A1 |
| 20020004912 | Fung | Jan 2002 | A1 |
| 20020013772 | Peinado | Jan 2002 | A1 |
| 20020026496 | Boyer et al. | Feb 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020049902 | Rhodes | Apr 2002 | A1 |
| 20020054589 | Ethridge et al. | May 2002 | A1 |
| 20020055978 | Joon-Bo et al. | May 2002 | A1 |
| 20020059577 | Lu et al. | May 2002 | A1 |
| 20020059619 | Lebar | May 2002 | A1 |
| 20020063621 | Tseng et al. | May 2002 | A1 |
| 20020069404 | Copeman et al. | Jun 2002 | A1 |
| 20020073419 | Yen et al. | Jun 2002 | A1 |
| 20020078441 | Drake et al. | Jun 2002 | A1 |
| 20020078444 | Krewin et al. | Jun 2002 | A1 |
| 20020087975 | Schlack | Jul 2002 | A1 |
| 20020087976 | Kaplan et al. | Jul 2002 | A1 |
| 20020095684 | St. John et al. | Jul 2002 | A1 |
| 20020100063 | Herigstad et al. | Jul 2002 | A1 |
| 20020104083 | Hendricks et al. | Aug 2002 | A1 |
| 20020112240 | Bacso et al. | Aug 2002 | A1 |
| 20020120498 | Gordon et al. | Aug 2002 | A1 |
| 20020123928 | Eldering et al. | Sep 2002 | A1 |
| 20020124182 | Bacso et al. | Sep 2002 | A1 |
| 20020129378 | Cloonan et al. | Sep 2002 | A1 |
| 20020144262 | Plotnick et al. | Oct 2002 | A1 |
| 20020144263 | Eldering et al. | Oct 2002 | A1 |
| 20020147984 | Tomsen et al. | Oct 2002 | A1 |
| 20020152393 | Thoma et al. | Oct 2002 | A1 |
| 20020154655 | Gummalla et al. | Oct 2002 | A1 |
| 20020163928 | Rudnick et al. | Nov 2002 | A1 |
| 20020166119 | Cristofalo | Nov 2002 | A1 |
| 20020174430 | Ellis et al. | Nov 2002 | A1 |
| 20020178445 | Eldering et al. | Nov 2002 | A1 |
| 20020178447 | Plotnick et al. | Nov 2002 | A1 |
| 20020184629 | Sie et al. | Dec 2002 | A1 |
| 20020184634 | Cooper | Dec 2002 | A1 |
| 20020184635 | Istvan | Dec 2002 | A1 |
| 20030002862 | Rodriguez et al. | Jan 2003 | A1 |
| 20030004810 | Eldering | Jan 2003 | A1 |
| 20030005446 | Jaff et al. | Jan 2003 | A1 |
| 20030005453 | Rodriguez et al. | Jan 2003 | A1 |
| 20030007516 | Abramov et al. | Jan 2003 | A1 |
| 20030018977 | McKenna | Jan 2003 | A1 |
| 20030020744 | Ellis et al. | Jan 2003 | A1 |
| 20030030751 | Lupulescu et al. | Feb 2003 | A1 |
| 20030033199 | Coleman | Feb 2003 | A1 |
| 20030046704 | Laksono et al. | Mar 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030061619 | Giammaressi | Mar 2003 | A1 |
| 20030071117 | Meade | Apr 2003 | A1 |
| 20030077067 | Wu et al. | Apr 2003 | A1 |
| 20030093311 | Knowlson | May 2003 | A1 |
| 20030093784 | Dimitrova et al. | May 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030093792 | Labeeb et al. | May 2003 | A1 |
| 20030099212 | Anjum et al. | May 2003 | A1 |
| 20030101449 | Bentolila et al. | May 2003 | A1 |
| 20030101451 | Bentolila et al. | May 2003 | A1 |
| 20030101454 | Ozer et al. | May 2003 | A1 |
| 20030110499 | Knudson et al. | Jun 2003 | A1 |
| 20030110503 | Perkes | Jun 2003 | A1 |
| 20030114162 | Chheda et al. | Jun 2003 | A1 |
| 20030115601 | Palazzo et al. | Jun 2003 | A1 |
| 20030115612 | Mao et al. | Jun 2003 | A1 |
| 20030135513 | Quinn et al. | Jul 2003 | A1 |
| 20030139980 | Hamilton | Jul 2003 | A1 |
| 20030140351 | Hoarty et al. | Jul 2003 | A1 |
| 20030145323 | Hendricks et al. | Jul 2003 | A1 |
| 20030149975 | Eldering et al. | Aug 2003 | A1 |
| 20030149990 | Anttila et al. | Aug 2003 | A1 |
| 20030149993 | Son et al. | Aug 2003 | A1 |
| 20030163739 | Armington et al. | Aug 2003 | A1 |
| 20030172376 | Coffin | Sep 2003 | A1 |
| 20030174838 | Bremer | Sep 2003 | A1 |
| 20030179773 | Mocek et al. | Sep 2003 | A1 |
| 20030208767 | Williamson et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20030220100 | McElhatten et al. | Nov 2003 | A1 |
| 20030221100 | Russ et al. | Nov 2003 | A1 |
| 20030229681 | Levitan | Dec 2003 | A1 |
| 20030237090 | Boston et al. | Dec 2003 | A1 |
| 20040019691 | Daymond et al. | Jan 2004 | A1 |
| 20040034873 | Zenoni | Feb 2004 | A1 |
| 20040047599 | Grzeczkowski | Mar 2004 | A1 |
| 20040060076 | Song | Mar 2004 | A1 |
| 20040073915 | Dureau | Apr 2004 | A1 |
| 20040078809 | Drazin | Apr 2004 | A1 |
| 20040109569 | Ellison et al. | Jun 2004 | A1 |
| 20040109672 | Kim et al. | Jun 2004 | A1 |
| 20040113936 | Dempski | Jun 2004 | A1 |
| 20040117817 | Kwon et al. | Jun 2004 | A1 |
| 20040133467 | Siler | Jul 2004 | A1 |
| 20040133907 | Rodriguez et al. | Jul 2004 | A1 |
| 20040138909 | Mayer | Jul 2004 | A1 |
| 20040146006 | Jackson | Jul 2004 | A1 |
| 20040148625 | Eldering et al. | Jul 2004 | A1 |
| 20040163109 | Kang et al. | Aug 2004 | A1 |
| 20040163111 | Palazzo et al. | Aug 2004 | A1 |
| 20040166881 | Farchmin | Aug 2004 | A1 |
| 20040177383 | Martinolich et al. | Sep 2004 | A1 |
| 20040181811 | Rakib | Sep 2004 | A1 |
| 20040186774 | Lee | Sep 2004 | A1 |
| 20040187159 | Gaydos et al. | Sep 2004 | A1 |
| 20040193609 | Phan et al. | Sep 2004 | A1 |
| 20040194134 | Gunatilake et al. | Sep 2004 | A1 |
| 20040199789 | Shaw et al. | Oct 2004 | A1 |
| 20040230994 | Urdang et al. | Nov 2004 | A1 |
| 20050007278 | Anson | Jan 2005 | A1 |
| 20050022237 | Nomura | Jan 2005 | A1 |
| 20050027696 | Swaminathan et al. | Feb 2005 | A1 |
| 20050028208 | Ellis et al. | Feb 2005 | A1 |
| 20050034171 | Benya | Feb 2005 | A1 |
| 20050034173 | Hatanaka | Feb 2005 | A1 |
| 20050039205 | Riedl | Feb 2005 | A1 |
| 20050047596 | Suzuki | Mar 2005 | A1 |
| 20050055685 | Maynard et al. | Mar 2005 | A1 |
| 20050060742 | Riedl et al. | Mar 2005 | A1 |
| 20050060745 | Riedl et al. | Mar 2005 | A1 |
| 20050066339 | Thoen | Mar 2005 | A1 |
| 20050086334 | Aaltonen et al. | Apr 2005 | A1 |
| 20050086691 | Dudkiewicz et al. | Apr 2005 | A1 |
| 20050091173 | Alve | Apr 2005 | A1 |
| 20050105396 | Schybergson | May 2005 | A1 |
| 20050111844 | Compton et al. | May 2005 | A1 |
| 20050114141 | Grody | May 2005 | A1 |
| 20050114686 | Ball et al. | May 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050123001 | Craven et al. | Jun 2005 | A1 |
| 20050125832 | Jost et al. | Jun 2005 | A1 |
| 20050144635 | Boortz et al. | Jun 2005 | A1 |
| 20050168323 | Lenoir et al. | Aug 2005 | A1 |
| 20050176444 | Tanaka | Aug 2005 | A1 |
| 20050198686 | Krause et al. | Sep 2005 | A1 |
| 20050210502 | Flickinger et al. | Sep 2005 | A1 |
| 20050223409 | Rautila et al. | Oct 2005 | A1 |
| 20050229209 | Hildebolt et al. | Oct 2005 | A1 |
| 20050234998 | Lesandrini et al. | Oct 2005 | A1 |
| 20050235318 | Grauch et al. | Oct 2005 | A1 |
| 20050262542 | Deweese et al. | Nov 2005 | A1 |
| 20050268107 | Harris et al. | Dec 2005 | A1 |
| 20050273629 | Abrams et al. | Dec 2005 | A1 |
| 20050273819 | Knudson et al. | Dec 2005 | A1 |
| 20050276284 | Krause et al. | Dec 2005 | A1 |
| 20050289588 | Kinnear | Dec 2005 | A1 |
| 20050289618 | Hardin | Dec 2005 | A1 |
| 20050289619 | Melby | Dec 2005 | A1 |
| 20060004662 | Nadalin et al. | Jan 2006 | A1 |
| 20060019702 | Anttila et al. | Jan 2006 | A1 |
| 20060031883 | Ellis et al. | Feb 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060037060 | Simms et al. | Feb 2006 | A1 |
| 20060080408 | Istvan et al. | Apr 2006 | A1 |
| 20060117341 | Park | Jun 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060154674 | Landschaft et al. | Jul 2006 | A1 |
| 20060165197 | Morita | Jul 2006 | A1 |
| 20060171390 | La Joie | Aug 2006 | A1 |
| 20060171423 | Helms et al. | Aug 2006 | A1 |
| 20060190336 | Pisaris-Henderson et al. | Aug 2006 | A1 |
| 20060197828 | Zeng et al. | Sep 2006 | A1 |
| 20060218604 | Riedl et al. | Sep 2006 | A1 |
| 20060218632 | Corley et al. | Sep 2006 | A1 |
| 20060236131 | Vauclair | Oct 2006 | A1 |
| 20060248555 | Eldering | Nov 2006 | A1 |
| 20060253328 | Kohli et al. | Nov 2006 | A1 |
| 20060253584 | Dixon et al. | Nov 2006 | A1 |
| 20060253864 | Easty | Nov 2006 | A1 |
| 20060259924 | Boortz et al. | Nov 2006 | A1 |
| 20060277569 | Smith | Dec 2006 | A1 |
| 20060288374 | Ferris et al. | Dec 2006 | A1 |
| 20060294259 | Matefi et al. | Dec 2006 | A1 |
| 20070022459 | Gaebel, Jr. et al. | Jan 2007 | A1 |
| 20070029379 | Peyer | Feb 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070061023 | Hoffberg et al. | Mar 2007 | A1 |
| 20070061197 | Ramer et al. | Mar 2007 | A1 |
| 20070074258 | Wood et al. | Mar 2007 | A1 |
| 20070076696 | An | Apr 2007 | A1 |
| 20070076728 | Rieger et al. | Apr 2007 | A1 |
| 20070089127 | Flickinger et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070101370 | Calderwood | May 2007 | A1 |
| 20070113243 | Brey | May 2007 | A1 |
| 20070115389 | McCarthy et al. | May 2007 | A1 |
| 20070118852 | Calderwood | May 2007 | A1 |
| 20070150919 | Morishita et al. | Jun 2007 | A1 |
| 20070157242 | Cordray et al. | Jul 2007 | A1 |
| 20070157262 | Ramaswamy et al. | Jul 2007 | A1 |
| 20070180230 | Cortez | Aug 2007 | A1 |
| 20070204310 | Hua et al. | Aug 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070233857 | Cheng et al. | Oct 2007 | A1 |
| 20070244760 | Bodnar et al. | Oct 2007 | A1 |
| 20070266395 | Lee et al. | Nov 2007 | A1 |
| 20070274400 | Murai et al. | Nov 2007 | A1 |
| 20070276926 | Lajoie et al. | Nov 2007 | A1 |
| 20070280298 | Hearn et al. | Dec 2007 | A1 |
| 20070294178 | Pinder et al. | Dec 2007 | A1 |
| 20080016526 | Asmussen | Jan 2008 | A1 |
| 20080021836 | Lao | Jan 2008 | A1 |
| 20080052157 | Kadambi et al. | Feb 2008 | A1 |
| 20080092181 | Britt | Apr 2008 | A1 |
| 20080101460 | Rodriguez | May 2008 | A1 |
| 20080104634 | Gajdos | May 2008 | A1 |
| 20080109307 | Ullah | May 2008 | A1 |
| 20080115169 | Ellis et al. | May 2008 | A1 |
| 20080124056 | Concotelli et al. | May 2008 | A1 |
| 20080134274 | Derrenberger et al. | Jun 2008 | A1 |
| 20080141317 | Radloff et al. | Jun 2008 | A1 |
| 20080141353 | Brown | Jun 2008 | A1 |
| 20080147497 | Tischer | Jun 2008 | A1 |
| 20080155588 | Roberts et al. | Jun 2008 | A1 |
| 20080155614 | Cooper et al. | Jun 2008 | A1 |
| 20080163305 | Johnson et al. | Jul 2008 | A1 |
| 20080170551 | Zaks | Jul 2008 | A1 |
| 20080182591 | Krikorian | Jul 2008 | A1 |
| 20080183705 | Shivaji-Rao et al. | Jul 2008 | A1 |
| 20080192820 | Brooks et al. | Aug 2008 | A1 |
| 20080229354 | Morris et al. | Sep 2008 | A1 |
| 20080244667 | Osborne | Oct 2008 | A1 |
| 20080263578 | Bayer et al. | Oct 2008 | A1 |
| 20080271068 | Ou et al. | Oct 2008 | A1 |
| 20080273591 | Brooks et al. | Nov 2008 | A1 |
| 20080306903 | Larson et al. | Dec 2008 | A1 |
| 20080313671 | Batrouny et al. | Dec 2008 | A1 |
| 20080313691 | Cholas et al. | Dec 2008 | A1 |
| 20090025027 | Craner | Jan 2009 | A1 |
| 20090025075 | Chow et al. | Jan 2009 | A1 |
| 20090030802 | Plotnick et al. | Jan 2009 | A1 |
| 20090064251 | Savoor et al. | Mar 2009 | A1 |
| 20090086643 | Kotrla et al. | Apr 2009 | A1 |
| 20090132346 | Duggal et al. | May 2009 | A1 |
| 20090133048 | Gibbs et al. | May 2009 | A1 |
| 20090150917 | Huffman et al. | Jun 2009 | A1 |
| 20090170479 | Jarenskog | Jul 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090210899 | Lawrence-Apfelbaum et al. | Aug 2009 | A1 |
| 20090244290 | McKelvey et al. | Oct 2009 | A1 |
| 20090319379 | Joao | Dec 2009 | A1 |
| 20090320059 | Bolyukh | Dec 2009 | A1 |
| 20100005527 | Jeon | Jan 2010 | A1 |
| 20100014496 | Kalika et al. | Jan 2010 | A1 |
| 20100027560 | Yang et al. | Feb 2010 | A1 |
| 20100070867 | Lemmers | Mar 2010 | A1 |
| 20100081416 | Cohen | Apr 2010 | A1 |
| 20100082983 | Shah et al. | Apr 2010 | A1 |
| 20100115091 | Park et al. | May 2010 | A1 |
| 20100122276 | Chen | May 2010 | A1 |
| 20100122288 | Minter et al. | May 2010 | A1 |
| 20100125658 | Strasters | May 2010 | A1 |
| 20100150027 | Atwal et al. | Jun 2010 | A1 |
| 20100151816 | Besehanic | Jun 2010 | A1 |
| 20100159951 | Shkedi | Jun 2010 | A1 |
| 20100161492 | Harvey et al. | Jun 2010 | A1 |
| 20100175084 | Ellis et al. | Jul 2010 | A1 |
| 20100175584 | Kusaka et al. | Jul 2010 | A1 |
| 20100218231 | Frink et al. | Aug 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100251305 | Kimble et al. | Sep 2010 | A1 |
| 20100262488 | Harrison et al. | Oct 2010 | A1 |
| 20100269131 | Newberry et al. | Oct 2010 | A1 |
| 20100280641 | Harkness et al. | Nov 2010 | A1 |
| 20100293165 | Eldering et al. | Nov 2010 | A1 |
| 20100309051 | Moshfeghi | Dec 2010 | A1 |
| 20100313225 | Cholas et al. | Dec 2010 | A1 |
| 20100313226 | Cholas et al. | Dec 2010 | A1 |
| 20110009122 | Kalavade | Jan 2011 | A1 |
| 20110015989 | Tidwell et al. | Jan 2011 | A1 |
| 20110016479 | Tidwell et al. | Jan 2011 | A1 |
| 20110016482 | Tidwell et al. | Jan 2011 | A1 |
| 20110090898 | Patel et al. | Apr 2011 | A1 |
| 20110093900 | Patel et al. | Apr 2011 | A1 |
| 20110099017 | Ure | Apr 2011 | A1 |
| 20110103374 | Lajoie et al. | May 2011 | A1 |
| 20110107364 | Lajoie et al. | May 2011 | A1 |
| 20110107379 | Lajoie et al. | May 2011 | A1 |
| 20110107389 | Chakarapani | May 2011 | A1 |
| 20110110515 | Tidwell et al. | May 2011 | A1 |
| 20110112717 | Resner | May 2011 | A1 |
| 20110138064 | Rieger et al. | Jun 2011 | A1 |
| 20110163888 | Goedde | Jul 2011 | A1 |
| 20110167440 | Greenfield | Jul 2011 | A1 |
| 20110178880 | Karaoguz et al. | Jul 2011 | A1 |
| 20110178943 | Motahari et al. | Jul 2011 | A1 |
| 20110197070 | Mizrah | Aug 2011 | A1 |
| 20110206136 | Bekedam et al. | Aug 2011 | A1 |
| 20110225619 | Kesireddy et al. | Sep 2011 | A1 |
| 20110231265 | Brown et al. | Sep 2011 | A1 |
| 20110235577 | Hintermeister et al. | Sep 2011 | A1 |
| 20110247029 | Yarvis et al. | Oct 2011 | A1 |
| 20110264530 | Santangelo et al. | Oct 2011 | A1 |
| 20110265116 | Stern et al. | Oct 2011 | A1 |
| 20110286437 | Austin et al. | Nov 2011 | A1 |
| 20110307339 | Russell et al. | Dec 2011 | A1 |
| 20110317977 | Harris | Dec 2011 | A1 |
| 20120005527 | Engel et al. | Jan 2012 | A1 |
| 20120011269 | Krikorian et al. | Jan 2012 | A1 |
| 20120023535 | Brooks | Jan 2012 | A1 |
| 20120030363 | Conrad | Feb 2012 | A1 |
| 20120030716 | Zhang et al. | Feb 2012 | A1 |
| 20120046049 | Curtis et al. | Feb 2012 | A1 |
| 20120054785 | Yang et al. | Mar 2012 | A1 |
| 20120079546 | Kalidindi et al. | Mar 2012 | A1 |
| 20120084813 | Dmitriev et al. | Apr 2012 | A1 |
| 20120110620 | Kilar et al. | May 2012 | A1 |
| 20120115501 | Zheng | May 2012 | A1 |
| 20120124606 | Tidwell et al. | May 2012 | A1 |
| 20120151549 | Kumar et al. | Jun 2012 | A1 |
| 20120159603 | Queck | Jun 2012 | A1 |
| 20120167173 | Nadalin et al. | Jun 2012 | A1 |
| 20120202447 | Edge | Aug 2012 | A1 |
| 20120203853 | Davis | Aug 2012 | A1 |
| 20120222081 | Schaefer et al. | Aug 2012 | A1 |
| 20120302259 | Busch | Nov 2012 | A1 |
| 20120330759 | Aggarwal et al. | Dec 2012 | A1 |
| 20130023247 | Bolon | Jan 2013 | A1 |
| 20130045681 | Dua | Feb 2013 | A1 |
| 20130046623 | Moritz | Feb 2013 | A1 |
| 20130060385 | Leen et al. | Mar 2013 | A1 |
| 20130081097 | Park et al. | Mar 2013 | A1 |
| 20130095848 | Gold et al. | Apr 2013 | A1 |
| 20130100818 | Qiu et al. | Apr 2013 | A1 |
| 20130227283 | Williamson et al. | Aug 2013 | A1 |
| 20130227608 | Evans et al. | Aug 2013 | A1 |
| 20130254787 | Cox et al. | Sep 2013 | A1 |
| 20130325995 | Ispas et al. | Dec 2013 | A1 |
| 20130347089 | Bailey et al. | Dec 2013 | A1 |
| 20140020017 | Stern et al. | Jan 2014 | A1 |
| 20140046624 | Miettinen | Feb 2014 | A1 |
| 20140066098 | Stern et al. | Mar 2014 | A1 |
| 20140215506 | Kalmes et al. | Jul 2014 | A1 |
| 20140282721 | Kuncl et al. | Sep 2014 | A1 |
| 20140309868 | Ricci | Oct 2014 | A1 |
| 20140359649 | Cronk et al. | Dec 2014 | A1 |
| 20150058883 | Tidwell et al. | Feb 2015 | A1 |
| 20150058909 | Miller et al. | Feb 2015 | A1 |
| 20150094098 | Stern et al. | Apr 2015 | A1 |
| 20150103685 | Butchko et al. | Apr 2015 | A1 |
| 20150106846 | Chen et al. | Apr 2015 | A1 |
| 20150185993 | Wheatley et al. | Jul 2015 | A1 |
| 20150189377 | Wheatley et al. | Jul 2015 | A1 |
| 20150365805 | Bajko et al. | Dec 2015 | A1 |
| 20150365833 | Stafford et al. | Dec 2015 | A1 |
| 20160006133 | Ganchrow et al. | Jan 2016 | A1 |
| 20160019103 | Basra | Jan 2016 | A1 |
| 20160066133 | Li et al. | Mar 2016 | A1 |
| 20160105780 | Hooker et al. | Apr 2016 | A1 |
| 20160127185 | McAllister et al. | May 2016 | A1 |
| 20160189193 | Toumayan et al. | Jun 2016 | A1 |
| 20170126614 | Sinha et al. | May 2017 | A1 |
| 20170164144 | Panchabhai et al. | Jun 2017 | A1 |
| 20170164378 | Gunasekara et al. | Jun 2017 | A1 |
| 20190052603 | Wu | Feb 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-0191474 | Nov 2001 | WO |
| Entry |
|---|
| Google Scholar Search Results. |
| Cisco Intelligent Network Architecture for Digital Video—SCTE Cable-Tec Expo 2004 information page, Orange County Convention Center, Jun. 2004, 24 pages. |
| Deering et al., Internet Protocol, Version 6 (IPv6) Specification, Dec. 1998, 39 pages. |
| Gomez, Conserving Transmission Power in Wireless Ad Hoc Networks, 2001, Network Protocols. |
| Griffith D.W., et al., “Resource Planning and Bandwidth Allocation in Hybrid Fiber-Coax Residential Networks,” National Institute of Standards and Technology (NIST), Oct. 1, 2005, 10 pages. |
| Lab—“Digital Video In-Stream Ad Format Guidelines,” 23 pages, released Jan. 8, 2016. |
| Lab—RTB Project—“Open RTB API Specification Version 2.4” (Final Draft) dated Mar. 2016, 75 pages. |
| Lab—RTB Project—“Open RTB Dynamic Native Ads API Specification Version 1”, 35 pages, dated Feb. 2015. |
| Lab—RTB Project—“Open RTB Dynamic Native Ads API Specification Version 1.1” dated Mar. 2016, 36 pages. |
| Lab—“Traffic Fraud: Best Practices for Reducing Risk to Exposure”, 12 pages, dated Jan. 30, 2014. |
| Lab “Open Direct API Specification Version 1.0”, 95 pages, finalized Jan. 2015. |
| Informal Standard, Document: id3v2.3, by: M. Nilsson, dated Feb. 3, 1999, 39 pages, http://id3.org/id3v2.3.0. |
| Internet Protocol Darpa Internet Program Protocol Specification, Sep. 1981, 51 pages. |
| Jicwebs “Traffic Fraud: Best Practices for Reducing Risk to Exposure”, 14 pages, Version 1, Issued Jun. 2015. |
| Kanouff, Communications Technology: Next-Generation Bandwidth Management—The Evolution of the Anything-to-Anywhere Network, 8 pages, Apr. 1, 2004. |
| Miao, et al., “Distributed interference-aware energy-efficient power optimization,” IEEE Transactions on Wireless Communications, Apr. 2011, vol. 10 (4), pp. 1323-1333. |
| Motorola DOCSIS Cable Module DCM 2000 specifications, 4 pages, copyright 2001. |
| Open Cable Specification entitled “Enhanced TV Binary Interchange Format 1 0” 0C-SP-ETV-131F1.0-106-110128 dated Jan. 28, 2011, 408 pages. |
| OpenVision Session Resource Manager—Open Standards-Based Solution Optimizes Network Resources by Dynamically Assigning Bandwidth in the Delivery of Digital Services article, 2 pages, (copyright 2006), (http://www.imake.com/hopenvision). |
| OpenVision Session Resource Manager features and information, 2 pages, (http://www.imake.com/hopenvision). |
| SCTE 130-1 2013. Part 1: Digital Program Insertion—Advertising Systems Interfaces, Part 1—Advertising Systems Overview, 20 pages. |
| SCTE Standards Document ANSI/SCTE 118-2 2007 entitled “Program-Specific Ad Insertion—Content Provider to Traffic Communication Applications Data Model,” 20 pages. |
| SCTE Standards Document ANSI/SCTE 130-2 2014 entitled “Digital Program Insertion—Advertising Systems Interfaces, Part 2—Core Data Elements,” 78 pages. |
| Tandberg Television specification entitled “AdPoint.RTM. Advanced Advertising Platform” dated Mar. 2008, 2 pages. |
| UTF-32, IBM, retrieved from http://publib.boulder/ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Fnls%2Frbagsutf32.htm on Aug. 28, 2013. |
| Number | Date | Country | |
|---|---|---|---|
| 20190268715 A1 | Aug 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15728452 | Oct 2017 | US |
| Child | 16397975 | US | |
| Parent | 14511079 | Oct 2014 | US |
| Child | 15728452 | US | |
| Parent | 13600064 | Aug 2012 | US |
| Child | 14511079 | US |
