Patent Grant
11540148
The present application is related to co-owned U.S. patent application Ser. No. 13/600,064 filed on Aug. 30, 2012 and entitled “APPARATUS AND METHODS FOR ENABLING LOCATION-BASED SERVICES WITHIN A PREMISES”, which is now U.S. Patent Publication No. 2014/0066098, and which is incorporated herein by reference in its entirety.
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 present disclosure relates generally to the field of data and content distribution and delivery. In one exemplary aspect, the disclosure relates to determining a desirable or optimal location for an access point or other wireless interface within a premises.
Extant wireless installations generally rely on a manual means of determining the best location for an access point (sometimes call an “AP” or “WAP”, hereinafter “AP”). As is well known, an AP allows for effectively simultaneous communication with multiple wireless-enabled user or client devices in various locations within range of the AP for a given air interface (e.g., Wi-Fi under IEEE Std. 802.11x). The optimal location of the AP is sometimes a three-dimensional spatial problem, as client devices that will communicate with the AP can be located on the same floor of a building or structure in any direction, and also on different floors above and below the AP's position. In addition, at any of the locations where a client device is located, other local factors affecting the client's ability to communicate with the AP may also exist, such as radio frequency (RF) signal path loss/attenuation (such as due to interposed materials), signal reflections, fading, localized “shading” and interference from other RF or electromagnetic sources.
Additionally, the characteristics of an AP and the client devices are such that they may have directional RF properties due to, e.g., variances in antenna gain in different directions.
Furthermore, the construction of buildings has an effect on determining an optimal location, as such construction involves the use of different materials that have different attenuation properties at exemplary radio frequencies used in wireless systems (e.g., 2.4 GHz, 3.6 GHz and 5 GHz), such as concrete, brick, dry-wall, wood, glass, metal framing, etc. Also, signals at these frequencies create multi-path propagation throughout the building, especially at increasing distances from the AP, and can be quite unpredictable. Thus, all the client device locations are individually different in terms of the propagation path to and from the AP.
In addition, even the most advanced tools today rely on an installer or user placing the AP at a ‘best guess’ position, then making measurements throughout the structure to verify that the entire structure (or at least the portions of greatest importance to the user) is covered adequately in terms of signal strength. Usually the first location that the user or installer places the AP is not optimal, or worse, the user/installer does not have enough information about the system's wireless link performance to make a proper adjustment to the initial location, and hence must make an “educated guess” as to what location might be better. This placement process is iterative, in that the installer will need to make several measurements, then move the AP to another location to improve on the last set of results, until the links to all client devices within the building are deemed sufficient for the final application (streaming video, internet browsing, etc.). In the event that all “critical” locations/applications cannot be serviced with adequate signal, a second AP may even be required, thereby further complicating the installation, and in some cases necessitating hand-offs between one AP and the other when, e.g., a user moves from one location to the other during use.
Therefore, what are needed are improved apparatus and methods for enabling a user to position an access point for optimal connectivity to client devices within a premises, taking into account RF signal path loss/attenuation, signal reflections, fading, localized shading, and interference. Such improved access point location identification methods and apparatus would ideally be provided across multiple client devices within a premises, and would be implemented using mechanisms readily available to a user, thereby obviating use of a specialist such as an installer.
The present disclosure addresses the foregoing needs by providing, in various embodiments, methods and apparatus for determining a desired/optimal location for an access point.
In a first aspect, a method of determining a desired location within a premises for a wireless access point is disclosed. In one embodiment, the method includes placing each of a plurality of wireless-enabled client devices in respective ones of a plurality of locations within the premises; utilizing the plurality of client devices to exchange signals between one another to collect data relating to one or more radio frequency characteristics at each of the plurality of locations; and utilizing the collected data to determine the desired location.
In a second aspect, a computer readable apparatus comprising at least one computer program is disclosed. In one embodiment, the computer program comprises a plurality of instructions which are configured to, when executed, access a plurality of link data obtained from a plurality of wireless client devices, at least a portion of the data gathered by each of the wireless client devices while monitoring wireless signals from at least one other of the plurality of client devices. In one variant, the plurality of link data is evaluated to identify at least one optimized location from a plurality of candidate locations, the optimized location meeting at least one acceptance criteria for wireless performance.
In a third aspect, a method of remotely installing a wireless access point within a user premises is disclosed. In one embodiment, the method includes: causing a user to place each of a plurality of wireless-enabled client devices in respective ones of a plurality of locations within the user premises, and utilize the plurality of client devices to exchange signals between one another to collect data relating to one or more radio frequency characteristics at each of the plurality of locations. The collected data is received and utilized for determining a desired location. In one variant, the information relating to the determined desired location is provided to the user, the information enabling the user to place the wireless access point within the user premises at the desired location.
In a fourth aspect, a method of determining an optimized placement of a wireless access point at a premises is disclosed. In one embodiment, the method includes utilizing a plurality of wireless enabled devices to transmit and receive signals in a substantially round-robin fashion in order to characterize a performance of each of a plurality of wireless links between the wireless enabled devices. The characterizations of the plurality of wireless link performances are utilized for identifying at least one location where the performance of the plurality of wireless links is optimized when considered in an aggregate.
In a fifth aspect, a method of identifying radio frequency link changes over time is disclosed. In one embodiment, the method includes, at a first time, placing a plurality of wireless devices in a first prescribed spatial configuration, and using each of the wireless devices, including characterizing wireless links between the plurality of wireless devices when placed in the first prescribed spatial configuration so as to produce first characterization data. At a second time subsequent to the first time: the plurality of wireless devices are placed in a second prescribed spatial configuration, and each of the plurality of wireless devices are used, including characterizing the wireless links between the plurality of client devices when placed in the second prescribed spatial configuration so as to produce second characterization data. The first and second data are compared to, inter alia, identify one or more changes in performance of one or more of the wireless links.
Other features and advantages of the present disclosure 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.
All Figures © Copyright 2014 Time Warner Cable Enterprises LLC. 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 term “client device” includes, but is 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 “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.
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.
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 “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 “Wi-Fi” refers to, without limitation, any of the variants of IEEE-Std. 802.11 or related standards including 802.11a/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.), FUSS, 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
The present disclosure provides, inter alia, methods and apparatus for determining at least one desired or optimal access point location within a premises. In one embodiment, software (e.g., an application) is downloaded to or otherwise disposed on one or more devices in a user premises. The software application enables each of the devices to communicate with one another (e.g., in “round robin” fashion) and collect a plurality of data. An access point (AP) is then introduced to the system; the access point uses the data collected from the plurality of user devices to determine a desirable or optimal location for the placement of the AP. In one variant, one or more of the user devices is configured to analyze the collected data in support of AP location determination. Alternatively, all or a portion of the collected data may be provided to a network (e.g., managed network headend) entity or third party for analysis thereat.
The foregoing exemplary embodiment of the methodology in effect turns the prior art paradigm of AP placement “on its head”, in that inter alia, one or more client devices are leveraged as mock access points, thereby allowing for much more efficient and richer RF signal characterization of a given space/structure than under the prior art iterative approach of placing the AP at a first location, measuring signal strength at multiple possible use locations, placing the AP at a second location, repeating, and so forth.
Once the desired/optimal location is determined, the access point is placed thereat, and the client devices returned to a normal operation. In one variant, further or ongoing data may be collected as the system operates to ensure that the location selected remains suitable/optimal. In the instance that changes in the topology of the user premises (or other changes, such as to the client device capabilities) cause significant alterations to the signals received at the various client devices (or vice-versa, at the AP), a new desired/optimal location for the access point(s) may be determined.
Methods of operating the network(s), client devices, and business models using the network and techniques referenced above, are also described.
The various aspects of the present disclosure may be useful in, inter alia, 802.11b/g/n/ac systems involving a single access point (or even multiple access points) and one or more client devices, such as a residential Wi-Fi installation. For example, the various aspects disclosed herein are useful to cable service companies, Telco, and other high-speed data (HSD) service providers and Video-over Wi-Fi (VoW) service installations.
Detailed Description of Exemplary Embodiments
Exemplary embodiments of the apparatus and methods of the disclosure are now described in detail. While these exemplary embodiments are described in the context of the aforementioned WLAN (e.g., Wi-Fi) technology, it will be appreciated that the apparatus and techniques described herein may be utilized in any number of other applications, including without limitation in other types of wireless networks (e.g., personal area networks or PANs, mesh networks, or piconets) or radio frequency communications systems.
Moreover, while some embodiments are described herein in the context of a managed content distribution network (e.g., 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 present disclosure 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.
It will also be appreciated that while described generally in the context of a consumer (i.e., home) end user domain, the present disclosure may be readily adapted to other types of environments (e.g., commercial/enterprise, government/military, etc.) as well. Myriad other applications are possible.
Also, while certain aspects are described primarily in the context of the well-known Internet Protocol, it will be appreciated that the present disclosure may utilize other types of protocols (and in fact bearer networks to include other internets and intranets) to implement the described functionality.
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 disclosure are in no way so limited, and may readily be applied to outdoor or hybrid indoor/outdoor applications.
Other features and advantages of the present disclosure 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 Architecture—
As noted above, exemplary bearer networks 101 useful with the present disclosure include any form of managed or unmanaged networks, such as e.g., those described in U.S. Patent Application Publication No. 2003/0056217, entitled “TECHNIQUE FOR EFFECTIVELY PROVIDING PROGRAM MATERIAL IN A CABLE TELEVISION SYSTEM”, published Mar. 20, 2003, issued as U.S. Pat. No. 8,713,623 on Apr. 29, 2014, and incorporated herein by reference in its entirety (describing one exemplary broadcast switched digital architecture), U.S. Patent Publication No. 2012/0023535 entitled “APPARATUS AND METHODS FOR PACKETIZED CONTENT DELIVERY OVER A BANDWIDTH-EFFICIENT NETWORK”, published Jan. 26, 2012, issued as U.S. Pat. No. 8,997,136 on Mar. 31, 2015, which is incorporated herein by reference in its entirety (describing delivery of packetized content via a bandwidth-optimized network), and U.S. Patent Application Publication No. 2011/0103374 filed on Apr. 21, 2010, and entitled “METHODS AND APPARATUS FOR PACKETIZED CONTENT DELIVERY OVER A CONTENT DELIVERY NETWORK”, and issued as U.S. Pat. No. 10,264,029 on Apr. 16, 2019, incorporated herein by reference in its entirety (describing inter ally, a 3GPP IMS (IP Multimedia Subsystem) network with common control plane and service delivery platform (SDP)). It will be appreciated that the methods and apparatus of the present disclosure advantageously are effectively agnostic to the bearer network architecture, thereby providing a large degree of applicability in various user/subscriber applications.
Exemplary Premises Network Architectures—
Referring now to
It will be appreciated that as used herein, the terms “desired” and “optimal” and “best” are used without limitation to refer to a location, installation or condition which is desirable or useful, whether or not fully optimized for all parameters under consideration (e.g., all signal strengths). For instance, it may be that there is no truly “optimal” location for an AP in a given premises; i.e., the user may have to sacrifice performance, convenience, and/or other considerations based on the particular attributes of the installation.
It is also appreciated that terms such as “optimal”, “best” etc. as used herein may be relative, and based on any number of considerations which may or may not relate to performance of a wireless link or similar functionality. For example, a “best” position for an AP for a given user may be one which maximizes both link performance and ergonomics/utility/aesthetics for the user; such as where a user sacrifices some level of link performance to have the AP placed in a location which is not inconvenient or an eyesore (i.e., it is not the “best” with respect to RF parameters/link quality, but is the best optimization of multiple considerations). As illustrated in
In the illustrated embodiment, the premises network 200 may also comprise a storage device 204. This storage device may be “stand alone” (e.g., a separate mass storage device such as a disk or flash drive, RAID array etc.), or may be incorporated into the form factor of any of the other components, or yet others (such as a local PC, gateway device, smart TV or TV support apparatus, etc.). The storage device may also be part of or associated with the access point device 202. As illustrated, the client devices 210 are in “logical” communication with the storage device 2014, which may comprise direct or indirect physical communication (such as via an intermediary process, device, or via a proxy) between the entities so as to enable exchange of data/applications,
The access point device 202 communicates with the content delivery network 101 via the interface 206, as well as to each of the client devices 210 as discussed in greater detail below. It is further appreciated that the access point device 202 and/or the client devices 210 may communicate with other networks including e.g., an interne (such as the Internet 111), long-range (e.g., cellular or WiMAX) wireless networks, satellite networks, mesh networks, etc.
In one exemplary embodiment, the client devices 210 of the premises network 200 comprise mobile devices (i.e., devices which may move within a premises or beyond) as well as fixed devices (i.e., devices which are associated to a single, static location, such as a server or PC). The client devices 210 are in one variant configured to allow a user to download one or more applications thereto (e.g., via the aforementioned logical/physical connections), although it will be appreciated that other mechanisms for placing a given application on the clients may be utilized consistent with the present disclosure, including e.g., having the applications prepositioned on the devices at time of manufacture or provisioning (e.g., by a wireless carrier when the mobile device/subscription is purchased), via “hard” media such as a CD-ROM, flash drive, or via download from a third-party provider via the Internet (such as from an “app store”).
In one embodiment, after the one or more applications have been downloaded or otherwise accessed, the subscriber can use a location profile application (from among the downloaded one or more applications, described in greater detail subsequently herein) to establish specific locations within the premises (e.g., living room, kitchen, bedroom, bathroom, etc.) where the subscriber uses one or more of the client devices 210. In addition, for each of the client devices 210, the user may prioritize or otherwise allocate usage for the locations based on an estimated or actual use of the client device 210 at each specific location. Such prioritization may be on any type of scale or according to any scheme, such as e.g., “fuzzy” variables such as “frequently”, “never”, “high”, or “low”, or discrete variables such as “1 to 10” or “75% of the time”. For example, a user might never use their laptop in the kitchen (“never”), but frequently use the same laptop in the office or bedroom (“frequently”). Likewise, a specific user might prioritize signal strength/bandwidth (roughly related to download/upload speed) over convenience or aesthetics (e.g., “I don't care where it is, so long as it's fast as possible”, such as for a chronic high-bandwidth consumer, or “I am willing to sacrifice speed for having access (albeit slower) at more locations within the premises” for a less bandwidth-intensive, convenience-oriented user.)
The prioritized/allocated list allows the client device 210 or the access point device 202 have better granularity when determining the most optimal location for the access point device 202. Specifically, the optimization process can better balance the various competing considerations and trade-offs by virtue of knowing what the relative importance of each is, and its magnitude or scale.
It will be appreciated that depending on the protocol used for wireless (local) communication between the client devices 210 and the access point device 202, the individual client devices 210 may be able to (i) communicate wirelessly directly with each other, in addition to communicating with the access point; (ii) communicate wirelessly with each other, yet only via communication with the access point; or (iii) both (i) and (ii). The exemplary embodiment assumes at least (i) above, although this is by no means a prerequisite for practicing the techniques described here, and the methodologies of the present disclosure may be readily adapted by those of ordinary skill to enable indirect communication for example. For instance, the radio transceiver/front-end of a given client may be able to sense and record/evaluate RF signals generated by another client, yet not be able to use those signals (or others) to communicate directly with the originating client device, based upon the topology of the underlying wireless protocol (e.g., one “master” with multiple “slaves”), the latter which can only communicate with the master bi-directionally.
One or more applications provided to the client devices 210 (which may be part of the same application discussed above) causes each of the client devices 210 to act as an access point, or operate in an ad-hoc network mode. The client device 210, when acting as the access point, communicates wirelessly with all of the other client devices 210 within the premises (and within range of its air interface) to gather/access link data for each of the other client devices 210. The link data may include e.g. (and without limitation), Service Set Identifier (SSID), received signal level/strength (e.g., RSSI), physical link rate, link quality, missed beacons, packet loss, bit error rate (BER), packet error rate PER, etc. The link data may relate to the connectivity of the accessed client device 210 over a given time period of time (e.g., ranging from a few seconds, or up to a few minutes, or even hours or more, such as where historical data for that particular location is available).
Note that the client devices 210 may communicate using any well-known communications protocol, whether wired or wireless (e.g., LAN/WAN, Ethernet, Wi-Fi, Bluetooth, etc.) when acting as the access point, to communicate relevant data for the other client devices 210 or the storage device 204.
The client device 210 acting as the access point, in one embodiment, builds a table or other data structure of link data/statistics internally (using the application software present thereon), from data collected from the other client devices 210 in the premises network 200. The collected data (which may include e.g., SSID, received signal level/RSSI, physical link rate, link quality, missed beacons, packet loss, BER/PER, etc.) demonstrates how the client device 210 which is acting as the access point “views” each of the connected client devices 210 within the premises network 200 from a RF signal standpoint. The client device 210 may obtain a higher resolution or more detailed profile of the connectivity (link) data of each of the connected client devices 210 by increasing the sounding frequency (i.e., the frequency with which the client device 210 acting as the access point samples or “pings” the client devices 210 in the premises to obtain data therefrom). This approach may be implemented so as to increase the accuracy of the desired optimal access point location determination. For example, a single sampling or data point for a given client device may or may not be representative of the actual link performance over time, since variations in link performance as sensed by the “AP” client device may occur as a function of time due to, e.g., variations in the status/presence of interfering emitters, fading and path artifacts, etc. Hence, an averaged or otherwise multi-data-point evaluation will increase the likelihood that the characterization of the link is accurate.
In another embodiment, the client device 210 acting as the access point transmits the collected connectivity data to the network 101 (e.g., to a server or process managed by the operator of the network 101), where the network server/process builds the table of link statistics.
In yet another embodiment, the client device 210 acting as the access point transmits the collected connectivity data to the storage device 204 for subsequent analysis by, e.g., an application running on the user's PC, a gateway (if present), or other device in communication with the storage device 204.
As will be discussed in greater detail below, information may be extracted during the foregoing process which is used to identify a location within a user's premises at which placement of the access point will ensure the best (or optimal) communication to the connected devices. 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 client devices 210 is collected. The data may include e.g., Wi-Fi channel state, RF power/RSSI, delay, signal phase, signal quality, amplification, etc. The data is then compared for each client device 210 location within the premises (such as based on comparison to previously gathered data and/or standard or reference data, or minimum acceptability criteria), such that the client device 210 for which communication to the other devices is best may be selected for placement of the access point device 202.
Exemplary Methodology—
As shown, the method 300 generally comprises causing or allowing a user to access (e.g., download and install) one or more applications to each of the user's client devices 210 (step 302). In one variant, the applications are downloaded directly from the network 101 (such as via a hub or headend entity). In another variant, the application may be downloaded from the Internet 111. As previously noted, the application(s) may also be prepositioned on the relevant devices, or yet other approaches used (e.g., peer-to-peer (P2P) sharing, etc.).
Next, per step 304, the “provisioned” client devices 210 are placed at positions within the premises that the subscriber would normally use the client devices 210. In one variant, the user generates a plurality of location profiles for each of the client devices 210 within the premises. The location profiles, in one embodiment, include a location name (for example, office, bedroom, living room, kitchen, bathroom, etc.), and a subscriber's use ranking (or other priority/allocation structure as described supra) thereat. The use ranking/allocation may be for instance based on an estimate and/or actual use of the client devices 210 at each location. In another embodiment, the location profile further includes link (connectivity) data as will be discussed elsewhere herein.
The user then accesses the downloaded application and initiates an installation mode. In one embodiment, the installation mode of the exemplary embodiment causes each of the client devices 210 to act as the access point via an ad-hoc network mode of operation (step 306).
In another embodiment, the access point device 202 issues a beacon signal. The beacon signal “pings” the client devices 210 making the client devices 210 visible to the access point device 202. The access point device 202 then determines that the client devices 210 are above a valid threshold for data transmission between the access point device 202 and the client devices 210. The client devices 210 that are below the minimum threshold for communication can be recorded by the access point device 202 as too distant from the access point device 202. The access point device then transmits this information to the client devices 210, which allows the client device 202 acting as the ad hoc access point know when it has finished “pinging” the other client devices 202 within the premises 200, as will be discussed elsewhere herein.
The client device 210 acting as the ad hoc access point connects to or “pings” all of the other client devices 210 to generate the location profile and/or the connectivity data (e.g., Service Set Identifier (SSID) received signal level/RSSI, physical link rate, link quality, missed beacons, packet loss, etc.). As previously noted, the connectivity data may represent signal quality over a duration of a few seconds, a few minutes, or according to yet other schemes (e.g., including historical or even extrapolated data). In one embodiment, the client device 210 acting as the access point builds a table of link statistics from the collected data. The data is illustrative of how the client device 210 acting as the access point “views” each of the connected client devices 210 from a radio frequency perspective.
In another embodiment, an entity of the network 101 (e.g., network side server with application software running thereon) builds the table of link statistics from data collected by the client device 210 when acting as the access point (and using data from other client devices, so as to provide one comprehensive characterization of the premises). In one variant, each of the client devices 210 transmits its collected data relating to the links to the network entity via e.g., an upstream channel such as via the network interface 206 (e.g., DOCSIS modem, out-of-band HFC channel, etc.), or via another interface such as a cellular, WLAN, or WiMAX interface separate from the network interface 206.
In yet another embodiment, the client device 210 acting as the access point transmits the collected connectivity data to the storage entity 204, where the data can be compiled (i.e., data from each of the different clients acting as access points stored), and accessed by any connected device or process, such as a gateway, wired or wireless tablet or laptop or PC, smartphone or smart TV, or even the access point device 202 itself, which then utilizes the stored data to determine the desired/optimal placement of the AP.
In yet another embodiment, the premises network 200 is further configured to generate dynamic or “moving” tables based on, for example, data such as that described in co-owned, co-pending U.S. Patent Publication No. 2014/0066098 entitled “APPARATUS AND METHODS FOR ENABLING LOCATION-BASED SERVICES WITHIN A PREMISES”, published Mar. 6, 2014, issued as U.S. Pat. No. 8,862,155 on Oct. 14, 2014, incorporated herein by reference in its entirety. The foregoing application discloses, inter alia, improved methods and apparatus for enabling location identification services within a premises. In one embodiment of the present disclosure, the client device 210 acting as the access point characterizes movement or predictable pathways within the premises. To do so, the user assigns qualifiers for each room within the premises, such as, “kitchen”, “family room”, “dining room”, “bedroom”, etc. In addition, each location may be associated with more than one location profile. For example, if a family room is large, the user may seek to generate a location profile for multiple spots within the family room.
The foregoing concepts may be applied herein, as illustrated in the exemplary premises of
The foregoing “moving” profiles are useful, among other things, from the standpoint that fixed placement measurements of link properties may not capture or accurately characterize interstitial or alternate locations in terms of signal quality. For example, if a user places four (4) client devices at four discrete locations in the premises, and selects an “optimal” AP location based on data obtained from these four devices, the behavior of the client devices while (i) in different locations than those where the individual clients were placed, and (ii) moving from location to location, may not be accurately reflected. It may in fact be the case that one or more of the clients lose signal/connectivity with the AP when moving between rooms, or relocating to another point within e.g., a large room. If a common use case for the given user is to be mobile while using their client device (e.g., video chatting while roaming between rooms), then a “static” characterization may not optimize the AP placement for this use case.
Referring back to
In another embodiment, the client device 210 acting as the access point knows when it has finished “pinging” the other client devices 210 within the premises 200 based on the information received from the access point device 202 during the installation mode. During the installation mode the access point device 202 issues a beacon signal, which “pings” the client devices 210 making the client devices 210 visible to the access point device 202. The access point device 202 then determines and records which of the client devices 210 are above a valid threshold for data transmission between the access point device 202 and the client devices 210. The access point device 202 then transmits the information to the client devices 210 within the premises.
In yet another embodiment, when the client device 210 acting as the access point cannot ping or connect, or loses a signal with at least one of the client devices 210, it moves on to the next client device 210 within the premises, and records that the client devices 210 that could not be reached are too distant (or could not be communicated with for other reasons) from the client device 210 acting as the access point.
In yet another embodiment, when the client device 210 acting as the access point cannot ping or connect, or loses a signal with at least one of the client devices 210, it relinquishes the role as the access point. In this embodiment, the location of the client device 210 acting as the access point is removed from consideration in the determination of optimal access point location within the premises.
Next, at step 310, it is determined whether all of the client devices 210 have had an opportunity to act as the access point (and collect connectivity data from the other devices). If not, the next or remaining client devices 210 begin again at step 306 to act as the ad hoc access point, and collect connectivity data from each of the other client devices 210 within the premises.
Once it has been determined that all of the client devices 210 have acted as the ad hoc access point, it is further determined whether the subscriber uses one or more of the devices at yet other, different location within the premises per step 312. Stated differently, the user may have only a limited number of actual client devices, but may use one or more of these devices as multiple locations. If so, the user may optionally move one or more of the client devices 210 to one or more new locations within the premises (step 304), and each of the client devices 210 acts as the ad hoc access point and collects connectivity data from the other client devices 210 within the premises at the new location(s) (step 306). The user continues to move the client devices 210 to new locations within the premises until all the client devices 210 have been placed at locations within the premises that the user typically or may use the client devices 210.
It is also appreciated that, under the foregoing process of step 312, a given client device or type of client device may act as a proxy for another device/type. For instance, a user could feasibly use the Wi-Fi transceiver on a smartphone to “stand in” for a Wi-Fi enabled tablet or laptop, or vice versa, if the actual device to be used at the location is unavailable or incapable of completing the process described above for some reason (e.g., the user hasn't purchased it yet). While use of the actual device that will ultimately be used at a given location in the premises for conducting the optimization process described herein is ideal, other similarly equipped devices can provide a good approximation. Hence, in one implementation, when a user is placing heterogeneous client devices (e.g., smartphone, tablet, laptop, etc.) in the premises for subsequent characterization/determination of optimal AP location, they place the same device that will be used in a given location most often at that same location (and ideally in the same position/orientation as when used), so as to most accurately characterize link performance.
Moreover, it may be the case that a user desires to use multiple different devices at the same location, whether (effectively) concurrently, or at different times, and each of these devices may have variations in their response/performance. For example, WLAN-enabled tablet with multiple-input multiple-output (MIMO) capability may perform more robustly than a non-MIMO enabled smartphone at the same location. Other varying device characteristics include e.g., good versus poor antennas, different powered transmitters, different receiver sensitivity, 1×2, 2×2 spatial stream capability, etc. Hence, in one embodiment, the aforementioned process is conducted using multiple devices at the same location (whether in tandem or sequentially), so that the links for each combination of devices can be evaluated. In another alternative, the system may be configured to utilize a “margin of error” or otherwise account for such differences between devices at the same location. In either instance, the reported information remains valuable to determining the optimal path (i.e., does not affect the performance of the optimal path algorithm).
Once it has been determined that all of the client devices 210 have acted as the ad hoc access point and have been moved to each location where use thereof is anticipated, a table or compilation of link statistics is created using the location profile and connectivity data collected. That is, the connectivity data collected by each of the client devices 210 acting as the access point may be stored for later use, such as in the form of individual tables or other data structures (e.g., tuples) on each client device 210. Alternatively, the connectivity data from all of the client devices 210 may be combined to a single table/structure at one of the client devices 210 and/or the storage entity 204, or as another option sent to a network entity (e.g., server within a managed network) for compilation and optional analysis.
An exemplary table of link statistics is illustrated in Table 1 below. The table of link statistics provides the client devices 210, the access point device 202, and/or the network entity with discrete values for each measured characteristic such as 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 each of the client devices 210, at each of the locations. The discrete values are established to include all possible values which may be received when at least one of the client devices 210 is within a given location (e.g., family room, bedroom, kitchen, etc.). The table of link statistics may be further comprised of transmitter and receiver characteristics covering Wi-Fi channel state, RF power, delay, signal phase, signal quality, amplification, MIMO, beamforming, etc. Other profiling information may include information regarding a nearby Wi-Fi hotspot (such as a neighbor's Wi-Fi hotspot, AP, RF channel(s) in use, SSID power level, air-time usage, etc.). The combination of this information for the client devices 210 may then be used for determining the optimal location or locations for the access point device 202.
As noted above, once all of the client devices 210 have acted as the ad hoc access point, the user installs the access point device 202 at any location within the premises. In one embodiment, the access point device 202 connects to each of the client devices 210 via wireless or wireline link to capture their positions and collect the tables built by each of the client devices 210 (when they acted as the access point). This may occur via a push or pull mechanism, or other means (such as periodic polling). Alternatively, as noted elsewhere herein, the collected data may be stored at the storage entity 204 and be made accessible to the newly connected access point device 202.
It will be appreciated that at this stage, connection of the access point to the clients (or storage entity) can occur via any type of interface suitable for exchanging data, since the AP is at this point merely gathering data obtained by the client devices 210 to utilize in its determination of the optimal AP placement location.
In another variant, use of the AP at this stage is obviated through use of a DSTB, gateway or other device (e.g., PC) which communicates with a network-side entity (e.g., the aforementioned server) to pass the data thereto for analysis. In one implementation, the DSTB, gateway or PC runs application software which gathers the collected data from the client devices 210 (such as via a WLAN or PAN interface), and transmits this data upstream to the server, where the data is collected and analyzed. The server then communicates information back to the DSTB/gateway/PC application, which the user can then access (such as via a graphical on-screen display or the like) to place the AP at the optimal location within the premises. This approach relieves the user of having to do the analysis themselves, although it will be appreciated that a similar analysis application can be utilized by the user at the premises as well (e.g., the DSTB/gateway/PC itself analyzes the collected data and instructs the user as to the optimal location, without resort to the network entity). Salient benefits of the use of the network entity, however, include (i) the network manager (e.g., MSO), if any, can store the data and use it for subsequent troubleshooting or other service/maintenance functions when the user is having problems; and (ii) the data from the premises in question can be compared or analyzed in light of similar data from other premises, such as to identify common problems, behaviors, etc.
Returning again to
The most optimal location to place the access point device 202 within the premises is in one implementation determined via an optimal path algorithm. The algorithm in one embodiment uses the physical link rates for both the upstream and downstream data flow for transmitting and receiving information between the client devices 210 and the access point device 202. The location with the “best” upstream and downstream of data flow is designated as the “optimal” location. In one variant, the downstream data flow can be weighted (e.g., weighted more heavily) depending on the service type reliance, such as where downstream traffic from the AP to the client devices is more critical or a more prevalent use case.
The most optimal location to place the access point device 202 within the premises is in another implementation determined via a simple weighted scoring algorithm. Specifically, the weights associated with each location are multiplied by the performance data for that location for each of the clients (either individually, or in the aggregate) where multiple clients are tested at the same location, and a net “score” developed for each location. The location with the highest score is designated as the “optimal” location.
So, as a very simple example of the foregoing, a premises with three (3) locations where a first location is weighted at 45%, and the use of the other locations at 35% and 20% respectively, might be analyzed as follows:
Hence, the data in Table 2 shows that the link (AP location) which provides the best overall performance is that with the highest aggregated score, and is hence “optimal”. Specifically, in this example, placing the AP in the Office scores an aggregate value of 8.4, in the Bedroom scores 7.8, and the Kitchen 8.85, thereby indicating that the Kitchen is the “optimal” place to locate the AP. Note that (i) use of a wireless client device in the same location as the AP is presumed to have highest possible performance (i.e., a “10” on this exemplary rating scale) for sake of simplicity, and (ii) links are assumed to be fully symmetric in terms of directionality.
Table 3 below illustrates another example with the same assumptions and rooms of the premises, yet where greater disparity between link performance exists:
In this example the Office scores an aggregated value of 5.95, the Bedroom 6.45, and the Kitchen 5.7. So, in this example, the AP is best placed in the Bedroom, the difference in result from the example of Table 2 being due to the different link performances.
In one variant, the software application (whether disposed on client, DSTB/gateway/PC, or other) gives the user the opportunity to view the tables and to affirm a correctly identified location (i.e., one associated with a given client device placement), and/or manually select a correct location in the instance the identified location is incorrect (e.g., the “Office” is erroneously identified as the “Kitchen”). Additionally, the premises network 200 may be configured to tag locations and/or “learn” locations as entered by a user. In other words, at the time a user manually enters a location the premises network 200 may be configured to use the previously received information (from the location request and/or the ping response) or may ping the client devices 210 and use information extracted from the client device 210 to override any previously stored location profile information for the user-entered location.
The application may also optionally be configured to allow the user to model, re-optimize, or “iterate” various configurations, such as by inserting different weighting factors or operational conditions for each location. For instance, a user could perform a sensitivity analysis based on weighting; e.g., “does the choice of where to place the AP change when I weight the Office use differently?” As another example, the user might make link quality measurements in the kitchen with the microwave oven (which operates at a nominal 2.4 GHz, similar to that of Wi-Fi lower band and Bluetooth frequency) both on and off, so as to see the potential impact of placing the AP in the kitchen close to the microwave. Similar logic applies to any cellular femtocells, repeaters, or a secondary access point, such as a MoCA-to-Wi-Fi Bridge, which may be placed at the premises.
After, the collected data has been analyzed (via whatever device/entity), a particular one of the locations is identified per step 314 as the optimal location (i.e., the location within the premises for which the “best” communication to all of the client devices 210 is determined). The determination specifies a particular location within the user premises and/or identifies the particular client device 210 (and a location thereof) at which the access point should be placed. As noted above, such information can be communicated to the user graphically (e.g., via an on-screen map or listing of locations, with the placement location being highlighted or otherwise denoted), verbally (such as communication with a remote network operator), or via any other means available. It will be appreciated that such communication to the user effectively obviates the need for any specialized installer or “truck roll”, thereby reducing installation latency and cost, and increasing user experience and satisfaction.
In addition, the second and third most optimal locations for the access point device 202 are also known from the connectivity table/application, and these locations may be used when the optimal (first) location is not practicable. The second and/or third optimal locations may be further utilized for placement of additional access points within the premises (as discussed with respect to
The user may then install the access point device 202 at the location of the client device 210 which was determined to be the optimal location (or a location proximate to the optimal location). The access point device 202, in one embodiment, runs a test after installation (e.g., upon initial provisioning) by collecting connectivity data from the client devices 210 at the various locations. This data is compared to the previously collected data (e.g., from the client device 210 which acted as an access point at this same location previously). Results of this test may be reported to the network 101 for, inter cilia, back-end monitoring and premises characterization purposes, and to provide a “snap-shot” of the most optimal location which can be compared to subsequently obtained data to determine if there are any degradation or other “shifts” in link performance over time for that AP installation location.
In one variant, it may be determined by the analysis (e.g., software application, or even human analysis) that one single location would not suffice to provide optimal or suitable coverage for all the client devices 210 within the premises. The user may be notified that a single access point is not recommended in this instance, however the user may still be provided with a single access point location determination.
Alternatively, more than one optimal location can be identified (i.e., the devices which together provide the best coverage for all of the client devices 210 in the premises); see again
In another embodiment, after the access point device 202 has been installed, error rate information (e.g., BER, PER) may be obtained while data is being delivered to the client devices 210 by the access point device 202. 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 the client devices 210 (e.g., within the PHY of the WLAN link). However, in the exemplary embodiment of the present disclosure, the error rate information may be further used to determine that the current optimal location for the access point device 202 is no longer optimal. Error rate statistics over time may be correlated to a location, so as to e.g., alert the user or network operator of a degradation of link quality (such as due to installation of an interferer on the premises or a nearby premises), thereby prompting a re-evaluation and possible AP re-location in order to optimize user experience and performance. Changes in link performance may be very insidious, and go unnoticed by the user for a long period of time without the periodic monitoring/corrective functionality described herein.
Exemplary Access Point Device—
In the previously described embodiment, wherein the access point device 202 is configured to generate a plurality of location profiles, the application 510 further comprises a software module configured to generate these individual profiles. Alternatively, the client devices 210 create the location profiles themselves and transmit these to the access point device 202. The location profiles may comprise information which is used for analysis and characterization of 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/RSSI, delay, signal phase, signal quality, amplification, beamforming data, link quality, channel noise, signal-to-noise ratio (SNR) etc. The location profile may further include a user entered or automatically generated location name, associated to the data collected thereat, or vendor and/or manufacturer and model number of the client device 210, or alternatively device IDs such as a MAC address or the like may be used for device identification of a device which can then be correlated to a location via other means (such as a lookup table).
The location assignment module 512 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 512 associates the data received at the profile generation application 510 to a particular location across multiple client devices 210. One or more profiles are therefore associated, via the location assignment application 512, to a particular user-determined location. For example, the locations may be assigned qualifiers such as “kitchen”, “family room”, “dining room”. “bedroom”, etc. at the user level, while other designations may be used at the device level (e.g., a given location such as the user's office is “001” for all devices accessing the data).
The retrieval and delivery software module 514 is configured to retrieve stored information regarding the location of the client devices 210 (such as by performing a query of a storage entity). The retrieval and delivery module 514 may be used in the instance the information is not pushed to the access point device 202 (or pulled by the access point device 202) directly from the client devices 210.
One or more additional applications or modules may be provided to, inter cilia, 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 access point device 202 to “learn” locations as entered by a user. For example, at the time a user manually enters a location name or designation, the application may be configured cause the client 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.
A network interface 502 and a premises interface 504 are further illustrated as part of the exemplary AP. The network interface 502 is in one embodiment configured to provide content and data delivery to and from the network 101, and may comprise for example a DOCSIS modem interface, HFC “in band” RF interface, DSL (e.g., copper telephony and modem) interface, optical fiber interface, wireless satellite (e.g., DSS) interface, WiMAX interface, or yet others.
The premises interface 504 provides communication between the access point device 202 and various client devices 210 within a premises. For example, the premises interface 504 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 504 may occur via a wired or wireless communication therewith, such as via e.g., IEEE-1394 (so called “FireWire”), USB, LAN/WAN, Wireless, etc. communications. In one exemplary configuration, a WLAN (Wi-Fi) interface is used both as the data carrier (between AP and client) and the interface being evaluated for RSSI/link quality, such as where a given client device, acting as ad hoc AP, evaluates the RF link between itself and another client device, and also uses that link to communicate the data and or evaluation results obtained via the software application.
It will be appreciated that the access point may also be combined with other functions and/or form factors, such as existing premises components such as wireless routers, gateways, computers, settop boxes (e.g., DSTBs), and the like.
Exemplary Client Device—
The external network interface 602 (if present) provides, inter alia, content and data delivery to and from an external network, such as a cellular network, WiMAX network, etc. For instance, the client device 210 may comprise a cellular or WIMAX enabled smartphone, which can communicate independently of its premises interface (e.g., WLAN).
The premises interface 604 provides inter alia, communication between the client device 210 and various devices within a premises, such as e.g., other client devices 210, and the access point device(s) 202. For example, the premises interface 604 in one variant comprises an 801.11 compliant interface that enables gathering of and optionally transmission/receipt of, connectivity data relating to one or more of the other client devices 210, as well as transmission of the table of link statistics to the access point device 202 via e.g. IEEE-1394, USB, wired LAN/WAN, Wireless, Wi-Fi, etc.
In the illustrated embodiment, the processor 608 is configured to run a software application (e.g., the user-downloaded application previously described) 610 thereon. The user downloaded client application 610 is configured to enable a user to gather and receive/send link statistics information as well as information identifying the client device 210 from which they were received (such as via an embedded identifier or other such identifying information within the signal). In this fashion, each client device 210 running the application can, if desired, both provide the data it gathers relating to link quality to other clients (and/or the AP 202), as well as acting as a recipient and analyzer of the data from other clients (as well as its own). Hence, when the exemplary application is installed on all the user's client devices 210, the user need not worry about which client goes first, last, etc.; any of the clients can aggregate the data and either analyze it in situ, or forward it to another entity (client, gateway/DSTB/PC, network entity, etc.) for evaluation and/or storage. However, it will further be appreciated that use of heterogeneous client applications may be used consistent with the disclosure if desired; e.g., so as to designate a “master” client device, or achieve other goals afforded by such heterogeneous software (such as use of very “thin” software on minimal capability devices).
Specifically, in a first embodiment, the client application 610 causes the received link statistics to be re-transmitted to the access point device 202 without modification thereof (i.e., acts as a repeater). Alternatively, this data may be transmitted to a storage entity 204, or to another client device 210 or entity within the network. A Wi-Fi premises interface 604 or other air interface (e.g., Bluetooth, UWB, etc.) may be utilized for wirelessly communicating the link statistics. It is appreciated, however, that the premises interface 604 and/or communication with the access point device 202 may occur via any number of wired and/or wireless communications modalities of the type previously set forth herein.
In another embodiment, the client application 610 may be further configured to enable the client device 210 to analyze collected data in order to determine an optimal location for placement of the access point 202 within the premises according the methods disclosed herein. According to this embodiment, data may be received at e.g., the premises interface 604 via communication with the other client devices 210 in the premises. The data is stored (e.g., in RAM 606 or a mass storage device such as flash memory or HDD) for the aforementioned analysis and storage of results.
It will be recognized that while certain aspects of the present disclosure are described in terms of a specific sequence of steps of a method, these descriptions are only illustrative of the broader methods, 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 present disclosure and claimed herein.
While the above detailed description has shown, described, and pointed out novel features of the disclosure 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 ideas set forth herein. The foregoing description is of the best mode presently contemplated of carrying out the disclosure. This description is in no way meant to be limiting, but rather should be taken as illustrative of the general principles of. The scope of the disclosure should be determined with reference to the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5313454 | Bustini et al. | May 1994 | A |
| 5369707 | Follendore, III | Nov 1994 | A |
| 5528284 | Iwami et al. | Jun 1996 | A |
| 5577209 | Boyle et al. | Nov 1996 | A |
| 5708961 | Hylton et al. | Jan 1998 | A |
| 5715403 | Stefik | Feb 1998 | A |
| 5774170 | Hite et al. | Jun 1998 | A |
| 5787172 | Arnold | Jul 1998 | A |
| 5818438 | Howe et al. | Oct 1998 | A |
| 5828832 | Holden et al. | Oct 1998 | A |
| 5862312 | Mann et al. | Jan 1999 | A |
| 5870474 | Wasilewski et al. | Feb 1999 | A |
| 5878324 | Borth et al. | Mar 1999 | A |
| 5897635 | Torres et al. | Apr 1999 | A |
| 5926205 | Krause et al. | Jul 1999 | A |
| 5935206 | Dixon et al. | Aug 1999 | A |
| 5982412 | Nulty | Nov 1999 | A |
| 6002393 | Hite et al. | Dec 1999 | A |
| 6009103 | Woundy | Dec 1999 | A |
| 6092178 | Jindal et al. | Jul 2000 | A |
| 6128316 | Takeda et al. | Oct 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6148400 | Arnold | Nov 2000 | A |
| 6154844 | Touboul et al. | Nov 2000 | A |
| 6157719 | Wasilewski et al. | Dec 2000 | A |
| 6167432 | Jiang | Dec 2000 | A |
| 6167521 | Smith et al. | Dec 2000 | A |
| 6169728 | Perreault et al. | Jan 2001 | B1 |
| 6181697 | Nurenberg et al. | Jan 2001 | B1 |
| 6211901 | Imajima et al. | Apr 2001 | B1 |
| 6212636 | Boyle et al. | Apr 2001 | B1 |
| 6219710 | Gray et al. | Apr 2001 | B1 |
| 6219840 | Corrigan et al. | Apr 2001 | B1 |
| 6233341 | Riggins | May 2001 | B1 |
| 6233687 | White | May 2001 | B1 |
| 6240553 | Son et al. | May 2001 | B1 |
| 6249680 | Wax et al. | Jun 2001 | B1 |
| 6256393 | Safadi et al. | Jul 2001 | B1 |
| 6259701 | Shur et al. | Jul 2001 | B1 |
| 6266421 | Domyo et al. | Jul 2001 | B1 |
| 6330609 | Garofalakis et al. | Dec 2001 | B1 |
| 6353626 | Sunay et al. | Mar 2002 | B1 |
| 6359711 | Cole et al. | Mar 2002 | B1 |
| 6378130 | Adams | Apr 2002 | B1 |
| 6434141 | Oz et al. | Aug 2002 | B1 |
| 6456716 | Arnold | Sep 2002 | B1 |
| 6463585 | Hendricks et al. | Oct 2002 | B1 |
| 6498783 | Lin | Dec 2002 | B1 |
| 6519062 | Yoo | Feb 2003 | B1 |
| 6523696 | Saito et al. | Feb 2003 | B1 |
| 6590865 | Ibaraki et al. | Jul 2003 | B1 |
| 6601171 | Carter et al. | Jul 2003 | B1 |
| 6640145 | Hoffberg et al. | Oct 2003 | B2 |
| 6657991 | Akgun et al. | Dec 2003 | B1 |
| 6687735 | Logston et al. | Feb 2004 | B1 |
| 6694145 | Riikonen et al. | Feb 2004 | B2 |
| 6711148 | Hills | Mar 2004 | B1 |
| 6718551 | Swix et al. | Apr 2004 | B1 |
| 6738978 | Hendricks et al. | May 2004 | B1 |
| 6742116 | Matsui et al. | May 2004 | B1 |
| 6760768 | Holden et al. | Jul 2004 | B2 |
| 6763391 | Ludtke | Jul 2004 | B1 |
| 6782550 | Cao | Aug 2004 | B1 |
| 6785810 | Lirov et al. | Aug 2004 | B1 |
| 6788676 | Partanen et al. | Sep 2004 | B2 |
| 6799047 | Bahl | Sep 2004 | B1 |
| 6807573 | Saito et al. | Oct 2004 | B2 |
| 6813505 | Walley et al. | Nov 2004 | B2 |
| 6842783 | Boivie et al. | Jan 2005 | B1 |
| 6859535 | Tatebayashi et al. | Feb 2005 | B1 |
| 6891841 | Leatherbury et al. | May 2005 | B2 |
| 6898708 | Hori et al. | May 2005 | B2 |
| 6910064 | Astarabadi et al. | Jun 2005 | B1 |
| 6925257 | Yoo | Aug 2005 | B2 |
| 6944150 | McConnell et al. | Sep 2005 | B1 |
| 6948183 | Peterka | Sep 2005 | B1 |
| 6954632 | Kobayashi | Oct 2005 | B2 |
| 6957261 | Lortz | Oct 2005 | B2 |
| 6957328 | Goodman et al. | Oct 2005 | B2 |
| 6973576 | Giobbi | Dec 2005 | B2 |
| 6975730 | Kuroiwa et al. | Dec 2005 | B1 |
| 6985355 | Allirot | Jan 2006 | B2 |
| 6986156 | Rodriguez et al. | Jan 2006 | B1 |
| 6996544 | Sellars et al. | Feb 2006 | B2 |
| 7006881 | Hoffberg et al. | Feb 2006 | B1 |
| 7007170 | Morten | Feb 2006 | B2 |
| 7009972 | Maher et al. | Mar 2006 | B2 |
| 7016963 | Judd et al. | Mar 2006 | B1 |
| 7017189 | Demello et al. | Mar 2006 | B1 |
| 7027460 | Iyer et al. | Apr 2006 | B2 |
| 7039048 | Monta et al. | May 2006 | B1 |
| 7054443 | Jakubowski et al. | May 2006 | B1 |
| 7054902 | Toporek et al. | May 2006 | B2 |
| 7055040 | Klemba et al. | May 2006 | B2 |
| 7065216 | Benaloh et al. | Jun 2006 | B1 |
| 7068639 | Varma et al. | Jun 2006 | B1 |
| 7069449 | Weaver et al. | Jun 2006 | B2 |
| 7069573 | Brooks et al. | Jun 2006 | B1 |
| 7072950 | Toft | Jul 2006 | B2 |
| 7073199 | Raley | Jul 2006 | B1 |
| 7075945 | Arsenault et al. | Jul 2006 | B2 |
| 7086077 | Giammaressi | Aug 2006 | B2 |
| 7092397 | Chandran et al. | Aug 2006 | B1 |
| 7099308 | Merrill et al. | Aug 2006 | B2 |
| 7103181 | Ananth | Sep 2006 | B2 |
| 7106382 | Shiotsu | Sep 2006 | B2 |
| 7107326 | Fijolek et al. | Sep 2006 | B1 |
| 7143431 | Eager et al. | Nov 2006 | B1 |
| 7149772 | Kalavade | Dec 2006 | B1 |
| 7154912 | Chong et al. | Dec 2006 | B2 |
| 7165268 | Moore et al. | Jan 2007 | B1 |
| 7174126 | McElhatten et al. | Feb 2007 | B2 |
| 7174127 | Otten et al. | Feb 2007 | B2 |
| 7174371 | Elo et al. | Feb 2007 | B2 |
| 7174385 | Li | Feb 2007 | B2 |
| 7194756 | Addington et al. | Mar 2007 | B2 |
| 7209458 | Ahvonen et al. | Apr 2007 | B2 |
| 7225333 | Peinado et al. | May 2007 | B2 |
| 7228427 | Fransdonk | Jun 2007 | B2 |
| 7228555 | Schlack | Jun 2007 | B2 |
| 7237112 | Ishiguro et al. | Jun 2007 | B1 |
| 7242960 | Van Rooyen et al. | Jul 2007 | B2 |
| 7248694 | Husemann et al. | Jul 2007 | B2 |
| 7254608 | Yeager et al. | Aug 2007 | B2 |
| 7257227 | Chen et al. | Aug 2007 | B2 |
| 7266726 | Ladd et al. | Sep 2007 | B1 |
| 7289534 | Bailey et al. | Oct 2007 | B1 |
| 7299502 | Schmeling et al. | Nov 2007 | B2 |
| 7305460 | Park | Dec 2007 | B2 |
| 7308415 | Kimbrel et al. | Dec 2007 | B2 |
| 7313611 | Jacobs et al. | Dec 2007 | B1 |
| 7324531 | Cho | Jan 2008 | B2 |
| 7325073 | Shao et al. | Jan 2008 | B2 |
| 7330483 | Peters, Jr. et al. | Feb 2008 | B1 |
| 7330967 | Pujare et al. | Feb 2008 | B1 |
| 7334044 | Allen | Feb 2008 | B1 |
| 7340759 | Rodriguez | Mar 2008 | B1 |
| 7346688 | Allen et al. | Mar 2008 | B2 |
| 7353543 | Ohmori et al. | Apr 2008 | B2 |
| 7363371 | Kirby et al. | Apr 2008 | B2 |
| 7373506 | Asano et al. | May 2008 | B2 |
| 7376386 | Phillips et al. | May 2008 | B2 |
| 7376976 | Fierstein et al. | May 2008 | B2 |
| 7379494 | Raleigh et al. | May 2008 | B2 |
| 7409546 | Platt | Aug 2008 | B2 |
| 7457520 | Rosetti et al. | Nov 2008 | B2 |
| 7464179 | Hodges et al. | Dec 2008 | B2 |
| 7472280 | Giobbi | Dec 2008 | B2 |
| 7486869 | Alexander et al. | Feb 2009 | B2 |
| 7487363 | Alve et al. | Feb 2009 | B2 |
| 7506367 | Ishibashi | Mar 2009 | B1 |
| 7567565 | La Joie | Jul 2009 | B2 |
| 7577118 | Haumonte et al. | Aug 2009 | B2 |
| 7592912 | Hasek et al. | Sep 2009 | B2 |
| 7602820 | Helms et al. | Oct 2009 | B2 |
| 7673004 | Sherstinsky et al. | Mar 2010 | B1 |
| 7690020 | Lebar | Mar 2010 | B2 |
| 7693171 | Gould | Apr 2010 | B2 |
| 7707644 | Choi et al. | Apr 2010 | B2 |
| 7721314 | Sincaglia et al. | May 2010 | B2 |
| 7730321 | Gasparini et al. | Jun 2010 | B2 |
| 7742074 | Minatogawa | Jun 2010 | B2 |
| 7752617 | Blinick et al. | Jul 2010 | B2 |
| 7757101 | Nonaka et al. | Jul 2010 | B2 |
| 7783891 | Perlin et al. | Aug 2010 | B2 |
| 7809942 | Baran et al. | Oct 2010 | B2 |
| 7860507 | Kalika et al. | Dec 2010 | B2 |
| 7865440 | Jaquette | Jan 2011 | B2 |
| 7870599 | Pemmaraju | Jan 2011 | B2 |
| 7925592 | Issa et al. | Apr 2011 | B1 |
| 7930558 | Hori | Apr 2011 | B2 |
| 7930715 | Hendricks et al. | Apr 2011 | B2 |
| 7954131 | Cholas et al. | May 2011 | B2 |
| 7983418 | Oyama et al. | Jul 2011 | B2 |
| 8041785 | Mazur et al. | Oct 2011 | B2 |
| 8084792 | Lehmann et al. | Dec 2011 | B2 |
| 8166508 | Mitsuji et al. | Apr 2012 | B2 |
| 8181262 | Cooper et al. | May 2012 | B2 |
| 8234387 | Bradley et al. | Jul 2012 | B2 |
| 8280982 | La Joie et al. | Oct 2012 | B2 |
| 8306634 | Nguyen et al. | Nov 2012 | B2 |
| 8332370 | Gattegno et al. | Dec 2012 | B2 |
| 8341242 | Dillon et al. | Dec 2012 | B2 |
| 8380226 | Clipsham | Feb 2013 | B2 |
| 8442265 | Bosworth et al. | May 2013 | B1 |
| 8583484 | Chalawsky et al. | Nov 2013 | B1 |
| 8713623 | Brooks | Apr 2014 | B2 |
| 8862155 | Stern et al. | Oct 2014 | B2 |
| 8866911 | Sivertsen | Oct 2014 | B1 |
| 8898270 | Stack et al. | Nov 2014 | B1 |
| 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 |
| 9300919 | Cholas et al. | Mar 2016 | B2 |
| 9935833 | McAllister | Apr 2018 | B2 |
| 20010004768 | Hodge et al. | Jun 2001 | A1 |
| 20010014946 | Ichinoi et al. | Aug 2001 | A1 |
| 20010019614 | Madoukh et al. | Sep 2001 | A1 |
| 20010029581 | Knauft | Oct 2001 | A1 |
| 20010030785 | Pangrac et al. | Oct 2001 | A1 |
| 20010053223 | Ishibashi et al. | Dec 2001 | A1 |
| 20010053226 | Akins et al. | Dec 2001 | A1 |
| 20010056541 | Matsuzaki et al. | Dec 2001 | A1 |
| 20020013772 | Peinado | Jan 2002 | A1 |
| 20020026575 | Wheeler et al. | Feb 2002 | A1 |
| 20020027883 | Belaiche | Mar 2002 | A1 |
| 20020032754 | Logston et al. | Mar 2002 | A1 |
| 20020049902 | Rhodes | Apr 2002 | A1 |
| 20020054589 | Ethridge et al. | May 2002 | A1 |
| 20020055978 | Joon-Bo | May 2002 | A1 |
| 20020056125 | Hodge et al. | May 2002 | A1 |
| 20020059619 | Lebar | May 2002 | A1 |
| 20020062440 | Akama | May 2002 | A1 |
| 20020063621 | Tseng et al. | May 2002 | A1 |
| 20020066033 | Dobbins et al. | May 2002 | A1 |
| 20020077984 | Ireton | Jun 2002 | A1 |
| 20020087976 | Kaplan et al. | Jul 2002 | A1 |
| 20020123928 | Eldering et al. | Sep 2002 | A1 |
| 20020126654 | Preston et al. | Sep 2002 | A1 |
| 20020129358 | Buehl et al. | Sep 2002 | A1 |
| 20020129378 | Cloonan et al. | Sep 2002 | A1 |
| 20020147771 | Traversat et al. | Oct 2002 | A1 |
| 20020152299 | Traversat et al. | Oct 2002 | A1 |
| 20020152393 | Thoma et al. | Oct 2002 | A1 |
| 20020183985 | Hori et al. | Dec 2002 | A1 |
| 20020188744 | Mani | Dec 2002 | A1 |
| 20020188869 | Patrick | Dec 2002 | A1 |
| 20020199105 | Ishiguro et al. | Dec 2002 | A1 |
| 20030002862 | Rodriguez et al. | Jan 2003 | A1 |
| 20030005453 | Rodriguez et al. | Jan 2003 | A1 |
| 20030007516 | Abramov et al. | Jan 2003 | A1 |
| 20030009681 | Harada et al. | Jan 2003 | A1 |
| 20030021421 | Yokota et al. | Jan 2003 | A1 |
| 20030041336 | Del Sordo et al. | Feb 2003 | A1 |
| 20030046560 | Inomata et al. | Mar 2003 | A1 |
| 20030046704 | Laksono et al. | Mar 2003 | A1 |
| 20030048380 | Tamura | Mar 2003 | A1 |
| 20030056217 | Brooks | Mar 2003 | A1 |
| 20030061619 | Giammaressi | Mar 2003 | A1 |
| 20030069965 | Ma et al. | Apr 2003 | A1 |
| 20030071117 | Meade | Apr 2003 | A1 |
| 20030074571 | Fujiwara et al. | Apr 2003 | A1 |
| 20030084003 | Pinkas et al. | May 2003 | A1 |
| 20030097340 | Okamoto et al. | May 2003 | A1 |
| 20030099212 | Anjum | May 2003 | A1 |
| 20030114162 | Chheda et al. | Jun 2003 | A1 |
| 20030115267 | Hinton et al. | Jun 2003 | A1 |
| 20030139980 | Hamilton | Jul 2003 | A1 |
| 20030140227 | Asano et al. | Jul 2003 | A1 |
| 20030163697 | Pabla et al. | Aug 2003 | A1 |
| 20030163739 | Armington et al. | Aug 2003 | A1 |
| 20030165241 | Fransdonk | Sep 2003 | A1 |
| 20030166401 | Combes et al. | Sep 2003 | A1 |
| 20030174838 | Bremer | Sep 2003 | A1 |
| 20030179773 | Mocek et al. | Sep 2003 | A1 |
| 20030187799 | Sellars et al. | Oct 2003 | A1 |
| 20030205763 | Park et al. | Nov 2003 | A1 |
| 20030208763 | McElhatten et al. | Nov 2003 | A1 |
| 20030208767 | Williamson et al. | Nov 2003 | A1 |
| 20030217137 | Roese et al. | Nov 2003 | A1 |
| 20030217365 | Caputo | Nov 2003 | A1 |
| 20040019691 | Daymond et al. | Jan 2004 | A1 |
| 20040024688 | Bl et al. | Feb 2004 | A1 |
| 20040034877 | Nogues | Feb 2004 | A1 |
| 20040045032 | Cummings et al. | Mar 2004 | A1 |
| 20040045035 | Cummings et al. | Mar 2004 | A1 |
| 20040045037 | Cummings et al. | Mar 2004 | A1 |
| 20040078602 | Rothbarth et al. | Apr 2004 | A1 |
| 20040088558 | Candelore | May 2004 | A1 |
| 20040106403 | Mori et al. | Jun 2004 | A1 |
| 20040109569 | Ellison et al. | Jun 2004 | A1 |
| 20040117836 | Karaoguz et al. | Jun 2004 | A1 |
| 20040123129 | Ginter et al. | Jun 2004 | A1 |
| 20040128499 | Peterka et al. | Jul 2004 | A1 |
| 20040133907 | Rodriguez et al. | Jul 2004 | A1 |
| 20040133923 | Watson et al. | Jul 2004 | A1 |
| 20040137918 | Varonen et al. | Jul 2004 | A1 |
| 20040146006 | Jackson | Jul 2004 | A1 |
| 20040166881 | Farchmin | Aug 2004 | A1 |
| 20040181800 | Rakib et al. | Sep 2004 | A1 |
| 20040187159 | Gaydos et al. | Sep 2004 | A1 |
| 20040193609 | Phan et al. | Sep 2004 | A1 |
| 20040193680 | Gibbs et al. | Sep 2004 | A1 |
| 20040224425 | Gjerde et al. | Nov 2004 | A1 |
| 20040240478 | Goren et al. | Dec 2004 | A1 |
| 20040250273 | Swix et al. | Dec 2004 | A1 |
| 20040260798 | Addington et al. | Dec 2004 | A1 |
| 20040261093 | Rebaud et al. | Dec 2004 | A1 |
| 20040268386 | Logan et al. | Dec 2004 | A1 |
| 20050005287 | Claussen | Jan 2005 | A1 |
| 20050007278 | Anson et al. | Jan 2005 | A1 |
| 20050015810 | Gould et al. | Jan 2005 | A1 |
| 20050021985 | Ono et al. | Jan 2005 | A1 |
| 20050022227 | Shen et al. | Jan 2005 | A1 |
| 20050034171 | Benya | Feb 2005 | A1 |
| 20050039205 | Riedl | Feb 2005 | A1 |
| 20050039212 | Baran et al. | Feb 2005 | A1 |
| 20050049886 | Grannan et al. | Mar 2005 | A1 |
| 20050055220 | Lee et al. | Mar 2005 | A1 |
| 20050060742 | Riedl et al. | Mar 2005 | A1 |
| 20050060745 | Riedl et al. | Mar 2005 | A1 |
| 20050065888 | Benaloh | Mar 2005 | A1 |
| 20050086683 | Meyerson | Apr 2005 | A1 |
| 20050086691 | Dudkiewicz et al. | Apr 2005 | A1 |
| 20050091173 | Alve | Apr 2005 | A1 |
| 20050097006 | Nyako | May 2005 | A1 |
| 20050108763 | Baran et al. | May 2005 | A1 |
| 20050111844 | Compton et al. | May 2005 | A1 |
| 20050114686 | Ball et al. | May 2005 | A1 |
| 20050114900 | Ladd et al. | May 2005 | A1 |
| 20050125832 | Jost et al. | Jun 2005 | A1 |
| 20050138357 | Swenson et al. | Jun 2005 | A1 |
| 20050168323 | Lenoir et al. | Aug 2005 | A1 |
| 20050169468 | Fahrny et al. | Aug 2005 | A1 |
| 20050172127 | Hartung et al. | Aug 2005 | A1 |
| 20050176444 | Tanaka | Aug 2005 | A1 |
| 20050177740 | Athaide et al. | Aug 2005 | A1 |
| 20050177741 | Chen et al. | Aug 2005 | A1 |
| 20050177855 | Maynard et al. | Aug 2005 | A1 |
| 20050182931 | Robert et al. | Aug 2005 | A1 |
| 20050188210 | Perlin et al. | Aug 2005 | A1 |
| 20050190912 | Hopkins et al. | Sep 2005 | A1 |
| 20050195975 | Kawakita | Sep 2005 | A1 |
| 20050198693 | Choi et al. | Sep 2005 | A1 |
| 20050268107 | Harris et al. | Dec 2005 | A1 |
| 20050273629 | Abrams et al. | Dec 2005 | A1 |
| 20050278259 | Gunaseelan et al. | Dec 2005 | A1 |
| 20050289618 | Hardin | Dec 2005 | A1 |
| 20050289619 | Melby | Dec 2005 | A1 |
| 20060002551 | Brown et al. | Jan 2006 | A1 |
| 20060004662 | Nadalin et al. | Jan 2006 | A1 |
| 20060008256 | Khedouri et al. | Jan 2006 | A1 |
| 20060020786 | Helms et al. | Jan 2006 | A1 |
| 20060020950 | Ladd et al. | Jan 2006 | A1 |
| 20060021004 | Moran et al. | Jan 2006 | A1 |
| 20060036750 | Ladd et al. | Feb 2006 | A1 |
| 20060041903 | Kahn et al. | Feb 2006 | A1 |
| 20060047801 | Haag et al. | Mar 2006 | A1 |
| 20060047957 | Helms et al. | Mar 2006 | A1 |
| 20060064583 | Birnbaum et al. | Mar 2006 | A1 |
| 20060095940 | Yearwood | May 2006 | A1 |
| 20060130099 | Rooyen | Jun 2006 | A1 |
| 20060130107 | Gonder et al. | Jun 2006 | A1 |
| 20060130113 | Carlucci et al. | Jun 2006 | A1 |
| 20060136964 | Diez et al. | Jun 2006 | A1 |
| 20060137005 | Park | Jun 2006 | A1 |
| 20060137015 | Fahrny et al. | Jun 2006 | A1 |
| 20060148362 | Bridges | Jul 2006 | A1 |
| 20060149850 | Bowman | Jul 2006 | A1 |
| 20060154674 | Landschaft et al. | Jul 2006 | A1 |
| 20060161635 | Lamkin et al. | Jul 2006 | A1 |
| 20060165090 | Kalliola et al. | Jul 2006 | A1 |
| 20060165197 | Morita et al. | Jul 2006 | A1 |
| 20060168219 | Ahluwalia et al. | Jul 2006 | A1 |
| 20060171390 | La Joie | Aug 2006 | A1 |
| 20060171423 | Helms et al. | Aug 2006 | A1 |
| 20060179138 | Van Gassel et al. | Aug 2006 | A1 |
| 20060184972 | Rafey et al. | Aug 2006 | A1 |
| 20060187900 | Akbar | Aug 2006 | A1 |
| 20060200856 | Salowey et al. | Sep 2006 | A1 |
| 20060206712 | Dillaway et al. | Sep 2006 | A1 |
| 20060209799 | Gallagher et al. | Sep 2006 | A1 |
| 20060212400 | Kamperman et al. | Sep 2006 | A1 |
| 20060218604 | Riedl et al. | Sep 2006 | A1 |
| 20060218632 | Corley et al. | Sep 2006 | A1 |
| 20060236131 | Vauclair | Oct 2006 | A1 |
| 20060248553 | Mikkelson et al. | Nov 2006 | A1 |
| 20060248555 | Eldering | Nov 2006 | A1 |
| 20060253328 | Kohli et al. | Nov 2006 | A1 |
| 20060253864 | Easty | Nov 2006 | A1 |
| 20060259927 | Acharya et al. | Nov 2006 | A1 |
| 20060277569 | Smith | Dec 2006 | A1 |
| 20060291506 | Cain | Dec 2006 | A1 |
| 20070011335 | Burns et al. | Jan 2007 | A1 |
| 20070019645 | Menon | Jan 2007 | A1 |
| 20070022459 | Gaebel et al. | Jan 2007 | A1 |
| 20070022469 | Cooper et al. | Jan 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070046791 | Wang et al. | Mar 2007 | A1 |
| 20070049245 | Lipman | Mar 2007 | A1 |
| 20070067851 | Fernando et al. | Mar 2007 | A1 |
| 20070076696 | An et al. | Apr 2007 | A1 |
| 20070076728 | Rieger et al. | Apr 2007 | A1 |
| 20070079381 | Hartung et al. | Apr 2007 | A1 |
| 20070089127 | Flickinger et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070098178 | Raikar | May 2007 | A1 |
| 20070113243 | Brey | May 2007 | A1 |
| 20070115900 | Liang et al. | May 2007 | A1 |
| 20070121678 | Brooks et al. | May 2007 | A1 |
| 20070124488 | Baum et al. | May 2007 | A1 |
| 20070157295 | Mangalore et al. | Jul 2007 | A1 |
| 20070174888 | Rubinstein | Jul 2007 | A1 |
| 20070192615 | Varghese et al. | Aug 2007 | A1 |
| 20070195727 | Kinder et al. | Aug 2007 | A1 |
| 20070204314 | Hasek et al. | Aug 2007 | A1 |
| 20070206799 | Wingert et al. | Sep 2007 | A1 |
| 20070209059 | Moore et al. | Sep 2007 | A1 |
| 20070217436 | Markley et al. | Sep 2007 | A1 |
| 20070219910 | Martinez | Sep 2007 | A1 |
| 20070220024 | Putterman et al. | Sep 2007 | A1 |
| 20070233857 | Cheng et al. | Oct 2007 | A1 |
| 20070250872 | Dua | Oct 2007 | A1 |
| 20070250880 | Hainline | Oct 2007 | A1 |
| 20070261116 | Prafullchandra et al. | Nov 2007 | A1 |
| 20070266395 | Lee et al. | Nov 2007 | A1 |
| 20070276925 | La Joie et al. | Nov 2007 | A1 |
| 20070276926 | LaJoie et al. | Nov 2007 | A1 |
| 20070294178 | Pinder et al. | Dec 2007 | A1 |
| 20080008321 | Gagnon et al. | Jan 2008 | A1 |
| 20080008371 | Woods et al. | Jan 2008 | A1 |
| 20080021836 | Lao | Jan 2008 | A1 |
| 20080022012 | Wang | Jan 2008 | A1 |
| 20080037493 | Morton | Feb 2008 | A1 |
| 20080059804 | Shah et al. | Mar 2008 | A1 |
| 20080066112 | Bailey et al. | Mar 2008 | A1 |
| 20080091805 | Malaby et al. | Apr 2008 | A1 |
| 20080091807 | Strub et al. | Apr 2008 | A1 |
| 20080098212 | Helms et al. | Apr 2008 | A1 |
| 20080101460 | Rodriguez | May 2008 | A1 |
| 20080103976 | Read et al. | May 2008 | A1 |
| 20080103977 | Khosravy et al. | May 2008 | A1 |
| 20080104634 | Gajdos et al. | May 2008 | A1 |
| 20080109307 | Ullah | May 2008 | A1 |
| 20080112405 | Cholas et al. | May 2008 | A1 |
| 20080117920 | Tucker | May 2008 | A1 |
| 20080123862 | Rowley | May 2008 | A1 |
| 20080133551 | Wensley et al. | Jun 2008 | A1 |
| 20080134274 | Derrenberger et al. | Jun 2008 | A1 |
| 20080141317 | Radloff et al. | Jun 2008 | A1 |
| 20080141353 | Brown | Jun 2008 | A1 |
| 20080148362 | Gilder et al. | Jun 2008 | A1 |
| 20080155059 | Hardin et al. | Jun 2008 | A1 |
| 20080155614 | Cooper et al. | Jun 2008 | A1 |
| 20080162353 | Tom et al. | Jul 2008 | A1 |
| 20080165460 | Whitby-Strevens | Jul 2008 | A1 |
| 20080177998 | Apsangi et al. | Jul 2008 | A1 |
| 20080182591 | Krikorian | Jul 2008 | A1 |
| 20080183705 | Shivaji-Rao et al. | Jul 2008 | A1 |
| 20080192820 | Brooks et al. | Aug 2008 | A1 |
| 20080212945 | Khedouri et al. | Sep 2008 | A1 |
| 20080222684 | Mukraj et al. | Sep 2008 | A1 |
| 20080229354 | Morris et al. | Sep 2008 | A1 |
| 20080235746 | Peters et al. | Sep 2008 | A1 |
| 20080244667 | Osborne | Oct 2008 | A1 |
| 20080256510 | Auerbach | Oct 2008 | A1 |
| 20080270307 | Olson et al. | Oct 2008 | A1 |
| 20080273591 | Brooks et al. | Nov 2008 | A1 |
| 20080282299 | Koat et al. | Nov 2008 | A1 |
| 20080288618 | Vardi et al. | Nov 2008 | A1 |
| 20090007234 | Birger et al. | Jan 2009 | A1 |
| 20090025027 | Craner | Jan 2009 | A1 |
| 20090025075 | Chow et al. | Jan 2009 | A1 |
| 20090028182 | Brooks et al. | Jan 2009 | A1 |
| 20090031371 | Munsell et al. | Jan 2009 | A1 |
| 20090064251 | Savoor et al. | Mar 2009 | A1 |
| 20090083813 | Dolce et al. | Mar 2009 | A1 |
| 20090094648 | Patel et al. | Apr 2009 | A1 |
| 20090098861 | Kalliola et al. | Apr 2009 | A1 |
| 20090100459 | Riedl et al. | Apr 2009 | A1 |
| 20090102983 | Malone et al. | Apr 2009 | A1 |
| 20090125374 | Deaton et al. | May 2009 | A1 |
| 20090151006 | Saeki et al. | Jun 2009 | A1 |
| 20090170479 | Jarenskog | Jul 2009 | A1 |
| 20090182815 | Czechowski, III et al. | Jul 2009 | A1 |
| 20090185576 | Kisel et al. | Jul 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090201917 | Maes et al. | Aug 2009 | A1 |
| 20090210899 | Lawrence-Apfelbaum et al. | Aug 2009 | A1 |
| 20090210912 | Cholas et al. | Aug 2009 | A1 |
| 20090225760 | Foti | Sep 2009 | A1 |
| 20090244290 | Mckelvey et al. | Oct 2009 | A1 |
| 20090265750 | Jones et al. | Oct 2009 | A1 |
| 20090282241 | Prafullchandra et al. | Nov 2009 | A1 |
| 20090282449 | Lee | Nov 2009 | A1 |
| 20090292922 | Park | Nov 2009 | A1 |
| 20090293101 | Carter et al. | Nov 2009 | A1 |
| 20100014496 | Kalika | Jan 2010 | A1 |
| 20100030578 | Siddique et al. | Feb 2010 | A1 |
| 20100031299 | Harrang et al. | Feb 2010 | A1 |
| 20100042478 | Reisman | Feb 2010 | A1 |
| 20100070867 | Lemmers | Mar 2010 | A1 |
| 20100081416 | Cohen | Apr 2010 | A1 |
| 20100082983 | Shah et al. | Apr 2010 | A1 |
| 20100083329 | Joyce et al. | Apr 2010 | A1 |
| 20100088236 | Karabulut et al. | Apr 2010 | A1 |
| 20100088292 | Tirpak et al. | Apr 2010 | A1 |
| 20100106846 | Noldus et al. | Apr 2010 | A1 |
| 20100122288 | Minter et al. | May 2010 | A1 |
| 20100131973 | Dillon et al. | May 2010 | A1 |
| 20100138900 | Peterka et al. | Jun 2010 | A1 |
| 20100150027 | Atwal | Jun 2010 | A1 |
| 20100151816 | Besehanic et al. | Jun 2010 | A1 |
| 20100159951 | Shkedi | Jun 2010 | A1 |
| 20100167743 | Palanki et al. | Jul 2010 | A1 |
| 20100169977 | Dasher et al. | Jul 2010 | A1 |
| 20100185855 | Margolus et al. | Jul 2010 | A1 |
| 20100198888 | Blomstedt et al. | Aug 2010 | A1 |
| 20100217837 | Ansari et al. | Aug 2010 | A1 |
| 20100251305 | Kimble et al. | Sep 2010 | A1 |
| 20100287609 | Gonzalez et al. | Nov 2010 | A1 |
| 20100309051 | Moshfeghi | Dec 2010 | A1 |
| 20100312826 | Sarosi et al. | Dec 2010 | A1 |
| 20100313225 | Cholas et al. | Dec 2010 | A1 |
| 20100313226 | Cholas et al. | Dec 2010 | A1 |
| 20110015989 | Tidwell et al. | Jan 2011 | A1 |
| 20110071841 | Fomenko et al. | Mar 2011 | A1 |
| 20110078721 | Wang et al. | Mar 2011 | A1 |
| 20110093900 | Patel et al. | Apr 2011 | A1 |
| 20110103374 | Lajoie et al. | May 2011 | A1 |
| 20110107389 | Chakarapani | May 2011 | A1 |
| 20110112717 | Resner | May 2011 | A1 |
| 20110138064 | Rieger et al. | Jun 2011 | A1 |
| 20110163888 | Goedde | Jul 2011 | A1 |
| 20110164753 | Dubhashi et al. | Jul 2011 | A1 |
| 20110167440 | Greenfield | Jul 2011 | A1 |
| 20110169977 | Masuda | Jul 2011 | A1 |
| 20110197070 | Mizrah | Aug 2011 | A1 |
| 20110206136 | Bekedam et al. | Aug 2011 | A1 |
| 20110213688 | Santos et al. | Sep 2011 | A1 |
| 20110219229 | Cholas et al. | Sep 2011 | A1 |
| 20110225619 | Kesireddy et al. | Sep 2011 | A1 |
| 20110235577 | Hintermeister et al. | Sep 2011 | A1 |
| 20110247029 | Yarvis et al. | Oct 2011 | A1 |
| 20110252236 | De Atley et al. | Oct 2011 | A1 |
| 20110252243 | Brouwer et al. | Oct 2011 | A1 |
| 20110286437 | Austin et al. | Nov 2011 | A1 |
| 20120008786 | Cronk et al. | Jan 2012 | A1 |
| 20120011567 | Cronk et al. | Jan 2012 | A1 |
| 20120023535 | Brooks et al. | Jan 2012 | A1 |
| 20120030716 | Zhang et al. | Feb 2012 | A1 |
| 20120046049 | Curtis et al. | Feb 2012 | A1 |
| 20120054785 | Yang et al. | Mar 2012 | A1 |
| 20120079531 | Hasek et al. | Mar 2012 | A1 |
| 20120079546 | Kalidindi et al. | Mar 2012 | A1 |
| 20120115501 | Zheng | May 2012 | A1 |
| 20120151549 | Kumar et al. | Jun 2012 | A1 |
| 20120159603 | Queck | Jun 2012 | A1 |
| 20120167173 | Nadalin et al. | Jun 2012 | A1 |
| 20120202447 | Edge et al. | Aug 2012 | A1 |
| 20120203822 | Floyd et al. | Aug 2012 | A1 |
| 20120203853 | Davis et al. | Aug 2012 | A1 |
| 20120222081 | Schaefer et al. | Aug 2012 | A1 |
| 20120291062 | Pearson et al. | Nov 2012 | A1 |
| 20120302259 | Busch | Nov 2012 | A1 |
| 20120330759 | Aggarwal et al. | Dec 2012 | A1 |
| 20130016648 | Koskela et al. | Jan 2013 | A1 |
| 20130023247 | Bolon et al. | Jan 2013 | A1 |
| 20130045681 | Dua | Feb 2013 | A1 |
| 20130046623 | Moritz et al. | Feb 2013 | A1 |
| 20130081097 | Park et al. | Mar 2013 | A1 |
| 20130095848 | Gold et al. | Apr 2013 | A1 |
| 20130100818 | Qiu | Apr 2013 | A1 |
| 20130132789 | Watford et al. | May 2013 | A1 |
| 20130145152 | Maino et al. | Jun 2013 | A1 |
| 20130235774 | Jo et al. | Sep 2013 | A1 |
| 20130254787 | Cox et al. | Sep 2013 | A1 |
| 20130308622 | Uhlik | Nov 2013 | A1 |
| 20130317892 | Heerboth | Nov 2013 | A1 |
| 20130347089 | Bailey et al. | Dec 2013 | A1 |
| 20140010219 | Dor et al. | Jan 2014 | A1 |
| 20140046624 | Miettinen | Feb 2014 | A1 |
| 20140066098 | Stern et al. | Mar 2014 | A1 |
| 20140177611 | Corrales | Jun 2014 | A1 |
| 20140213256 | Meylan et al. | Jul 2014 | A1 |
| 20140215506 | Kalmes et al. | Jul 2014 | A1 |
| 20140242991 | Yanover et al. | Aug 2014 | A1 |
| 20140274110 | Mehta et al. | Sep 2014 | A1 |
| 20140281489 | Peterka et al. | Sep 2014 | A1 |
| 20140282721 | Kuncl et al. | Sep 2014 | A1 |
| 20140283137 | Rebaud et al. | Sep 2014 | A1 |
| 20140309868 | Ricci | Oct 2014 | A1 |
| 20140328257 | Kamlani | Nov 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 | Apr 2015 | A1 |
| 20150106501 | Malets et al. | Apr 2015 | A1 |
| 20150106846 | Chen et al. | Apr 2015 | A1 |
| 20150146537 | Panaitopol et al. | May 2015 | A1 |
| 20150156129 | Tsuruoka | Jun 2015 | A1 |
| 20150189377 | Wheatley et al. | Jul 2015 | A1 |
| 20150288617 | Dasher et al. | Oct 2015 | A1 |
| 20150288732 | Phillips et al. | Oct 2015 | A1 |
| 20150365833 | Stafford et al. | Dec 2015 | A1 |
| 20160019103 | Basra | Jan 2016 | A1 |
| 20160066234 | Cho et al. | Mar 2016 | A1 |
| 20160127185 | Mcallister | May 2016 | A1 |
| 20160301525 | Canard et al. | Oct 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 1139198 | Oct 2001 | EP |
| 2113860 | Nov 2009 | EP |
| 2381709 | May 2003 | GB |
| H08263440 | Oct 1996 | JP |
| 2000156676 | Jun 2000 | JP |
| 2000332746 | Nov 2000 | JP |
| 2001243707 | Sep 2001 | JP |
| 2001274786 | Oct 2001 | JP |
| 2001274788 | Oct 2001 | JP |
| 2001285821 | Oct 2001 | JP |
| 2002163396 | Jun 2002 | JP |
| 2002352094 | Dec 2002 | JP |
| 2003058657 | Feb 2003 | JP |
| 2003162600 | Jun 2003 | JP |
| 2003233690 | Aug 2003 | JP |
| 2003248508 | Sep 2003 | JP |
| 2003296484 | Oct 2003 | JP |
| 2003348508 | Dec 2003 | JP |
| 2004030111 | Jan 2004 | JP |
| 2004072721 | Mar 2004 | JP |
| 2004120736 | Apr 2004 | JP |
| 2004120738 | Apr 2004 | JP |
| 2004303111 | Oct 2004 | JP |
| 2005506627 | Mar 2005 | JP |
| 2005519365 | Jun 2005 | JP |
| 2005519501 | Jun 2005 | JP |
| 2005339093 | Dec 2005 | JP |
| 2006185473 | Jul 2006 | JP |
| 2006311267 | Nov 2006 | JP |
| 2007020144 | Jan 2007 | JP |
| 2008005047 | Jan 2008 | JP |
| 2008015936 | Jan 2008 | JP |
| 2008021293 | Jan 2008 | JP |
| 2008507905 | Mar 2008 | JP |
| 2008167018 | Jul 2008 | JP |
| 2008186272 | Aug 2008 | JP |
| 2008206039 | Sep 2008 | JP |
| 2009071786 | Apr 2009 | JP |
| 2009515238 | Apr 2009 | JP |
| 2009176060 | Aug 2009 | JP |
| 2009211632 | Sep 2009 | JP |
| 2010502109 | Jan 2010 | JP |
| 2010079902 | Apr 2010 | JP |
| 2012505436 | Mar 2012 | JP |
| 2012523614 | Oct 2012 | JP |
| WO-0103410 | Jan 2001 | WO |
| WO-0110125 | Feb 2001 | WO |
| WO-0137479 | May 2001 | WO |
| WO-0169842 | Sep 2001 | WO |
| WO-0177778 | Oct 2001 | WO |
| WO-0213032 | Feb 2002 | WO |
| WO-0221841 | Mar 2002 | WO |
| WO-0242966 | May 2002 | WO |
| WO-02080556 | Oct 2002 | WO |
| WO-03038704 | May 2003 | WO |
| WO-03087799 | Oct 2003 | WO |
| WO-03093944 | Nov 2003 | WO |
| WO-2004027622 | Apr 2004 | WO |
| WO-2005015422 | Feb 2005 | WO |
| WO-2006020141 | Feb 2006 | WO |
| WO-2008080556 | Jul 2008 | WO |
| WO-2009020476 | Feb 2009 | WO |
| WO-2012021245 | Feb 2012 | WO |
| Entry |
|---|
| Deering et al., Internet Protocol, Version 6 (Ipv6) Specification, IETF RFC 2460 (Dec. 1998). |
| Internet Protocol DARPA Internet Program Protocol Specification, IETF RFC 791 (Sep. 1981). |
| 5C Digital Transmission Content Protection White Paper, Hitachi, Ltd., et al., dated Jul. 14, 1998, 15 pages. |
| Cantor, et al., Assertions and Protocols for the OASIS Security Assertion Markup Language (SAML) V2.0, OASIS Standard, Mar. 15, 2005. Document ID: saml-core-2.0-os (http://docs.oasis-open.Org/securit/saml/v2.0/saml-core-2.0-os.pdf). |
| Cantor, et al., Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0, OASIS Standard, Mar. 2005 (http://docs.oasis-open.org/security/saml/v2.0/). |
| Cisco Intelligent Network Architecture for Digital Video—SCTE Cable-Tec Expo 2004 information page, Orange County Convention Center, Jun. 2004, 24 pages. |
| DCAS Authorized Service Domain, Version 1.2, dated Nov. 30, 2005, 54 pages. |
| DCAS Licensed Specification Abstracts, CableLabs Confidential Information, Jan. 12, 2006, 4 pages. |
| Digital Video Broadcasting (DVB); DVB SimulCrypt; Part 1: “Head-end architecture and synchronization” Technical Specification—ETSI TS 101 197 V1.2.1 (Feb. 2002), 40 pages. |
| DVB (Digital Video Broadcasting), DVB Document A045 Rev. 3, Jul. 2004, “Head-end Implementation of SimulCrypt,” 289 pages. |
| Federal Information Processing Standards Publication, US FIPS PUB 197, Nov. 26, 2001, “Advanced Encryption Standards (AES),” 47 pages. |
| Griffith, et al.,Resource Planning and Bandwidth Allocation in Hybrid Fiber-Coax Residential Networks, National Institute of Standards and Technology (NIST), 10 pages, no date. |
| Gupta V., et al., “Bit-Stuffing in 802.11 Beacon Frame: Embedding Non-Standard Custom Information,” International Journal of Computer Applications, Feb. 2013, vol. 63 (2), pp. 6-12. |
| High-bandwidth Digital Content Protection System, Revision 1.091, dated Apr. 22, 2003, Digital Content Protection LLC Draft, 78 pages. |
| Kanouff, Communications Technology: Next-Generation Bandwidth Management—The Evolution of the Anything-to-Anywhere Network, 8 pages, Apr. 1, 2004. |
| Marusic, et al., “Share it!—Content Transfer in Home-to-Home Networks.” IEEE MELECON 2004, May 12-15, 2004, Dubrovnik, Croatia. |
| Media Server; 1 Device Template Version 1.01 Jun. 25, 2002. |
| Motorola DOCSIS Cable Module DCM 2000 specifications, 4 pages, no date. |
| OpenCable Application Platform Specification, OCAP 2.0 Profile, OC-SP-OCAP2.0-I01-020419, Apr. 19, 2002. |
| OpenCable Application Platform Specifications, OCAP Extensions, OC-SP-OCAP--HNEXT-I03-080418, 2005-2008. |
| OpenCable Host Device, Core Functional Requirements, OC-SP-HOST-CFR-I13-030707, Jul. 7, 2003. |
| Opencable, HOST-POD Interface Specification, OC-SP-HOSTPOD-IF-113-030707, Jul. 7, 2003. |
| OpenCable Specification, Home Networking Protocol 2.0, OC-SP-HNP2.0-I01-08418, 2007. |
| OpenCable Specifications, Home Networking Security Specification, OC-SP-HN-SEC-DO1-081027, draft (Oct. 27, 2008). |
| 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, no date, (http://www.imake.com/hopenvision). |
| Primergy BX300 Switch Blade user's manual, Fujitsu Corp., Sep. 30, 2002, first edition, pp. 1 to 20. |
| Real System Media Commerce Suite (Technical White Paper), at http://docs.real.com/docs/drm/DRM.sub-WP1.pdf, 12 pages, Nov. 2001. |
| Van Moffaert, K., et al. (“Digital Rights Management: DRM is a key enabler for the future growth of the broadband access market and the telecom/networking market in general”, Alcatel Telecommunications Review, Alcatel, Paris Cedex FR, Apr. 1, 2003, XP007005930ISSN; 8 pages. |
| Zhang, et al., A Flexible Content Protection System for Media-on-Demand, ISM China Research Lab, Proceedings of the IEEE Fourth International Symposium on Multimedia Software Engineering (MSE'02), 6 pages. |
| Google search results. |
| Number | Date | Country | |
|---|---|---|---|
| 20150365833 A1 | Dec 2015 | US |
