Streaming devices associated with display devices, such as televisions, may be used to stream or otherwise present a variety of content to users. However, streaming devices and associated display devices may utilize conventional techniques to conserve power. Such conventional techniques include requiring an interaction, such as a touch input from a user or a commend from a control device, to initially be turned on. A similar operation may be required to turn off the display device. Some display devices may utilize a period of time of non-interaction by the user to automatically turn off the display. However, this can result in a display device automatically turning off even though a user is using the display device but not actively interacting with it. For example, a user may be watching a movie on the display device without actually providing any input to the display device.
Various embodiments in accordance with the present disclosure will be described with reference to the drawings, in which:
In the following description, various embodiments will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the embodiments. However, it will also be apparent to one skilled in the art that the embodiments may be practiced without the specific details. Furthermore, well-known features may be omitted or simplified in order not to obscure the embodiment being described.
Embodiments of the present disclosure are directed to, among other things, implementing a dynamic radar mode modulation feature for modulating a mode of a radar and operating a display device to change states. For example, a computer system (streaming device) communicatively coupled to a radar sensor and the display device may receive data captured by the radar sensor to determine events associated with an object being detected by the radar sensor. In an embodiment, the computer system implementing the dynamic radar mode modulation feature may utilize one or more algorithms with different configurations of parameters and thresholds to determine events associated with the object detected within the field of view of the radar sensor. For example, the computer system may determine a presence of an object in the field of view of the radar sensor (an ingress event), an absence of the object in the field of view of the radar sensor (an egress event), or a static presence of the object in the field of view of the radar sensor (static presence event). In accordance with at least one embodiment, a streaming device configured to receive and present content via the display device may be an example of the computer system. The computer system may include one or more applications or modules for instructing or otherwise controlling the operating state of the display device.
In accordance with at least one embodiment, the computer system may modulate, dynamically, a radar configuration utilized by the radar sensor to detect an event associated with an object in the field of view of the object, the algorithm used to process the data received by the radar sensor, and a state of the display device (e.g., on, off, remain on). For example, the presence of an object, such as a person sitting on a couch in front of their television, may be determined by the computer system based on the data received from the radar sensor. The computer system may utilize a particular configuration of an algorithm to process the data received from the radar sensor to determine the presence of the object (e.g., an ingress event) and generate instructions to modulate various components of the system. To continue the example, in response to determining a presence of an object, the computer system may generate and implement instructions to modulate the radar configuration utilized by the radar sensor such that the radar sensor utilizes a different frame per second rate and threshold of difference, modulate the algorithm to utilize different parameters for another event, such as a static presence event, and operate a state of the display device to turn on. By modulating the operating mode of the radar sensor, display device, and algorithm utilized, the computer system can efficiently turn on or off the display device to facilitate consuming content presented by the display device and thereby conserve power utilized by the display device.
In embodiments, the display device may include, but is not limited to, a television, a monitor, a mobile device, a desktop computer, a laptop, a video game console, a tablet computer, a projector, and/or any other type of device that is able to provide content. The computer system (streaming device) may be associated with, communicatively coupled to the display device, or otherwise integrated into the display device. The radar sensor may include sensors, such as a radar sensor(s), lidar sensor(s), distance sensor(s), imaging device(s), and/or time of flight sensor(s). In accordance with at least one embodiment, the radar sensor is configured to detect objects that are located within a range of the sensor capabilities of the radar sensor and within a field of view of the radar sensor. As will be described herein, the radar sensor, computer system, and display device may operate in various modes, an ingress mode, an egress mode, and a static presence mode. Each mode may be determined by the computer system and modulated between the modes by the computer system based on data received and processed from the radar sensor. As used herein, an “ingress mode/first mode” or “ingress event” corresponds to an event where an object, such as a user, is detected by the radar sensor and the computer system determines that the object is within the field of view of the radar and that the display device should change state—go from an off state to an on state.
The determination of an event or mode by the computer system results in modulating to a different mode or state to prime the radar sensor and computer system to detect a subsequent event. For example, once an ingress event has been determined by the computer system and the display device is turned on, the computer system may generate and implement instructions to modulate the algorithm used to process subsequently received radar data as well as the radar configuration used by the radar sensor to process incoming data. This can result in a dynamic modulation of the devices to conserve power and for the display device as well as react to the user's presence without requiring the user to provide any kind of input or interact with the display device and/or streaming device. As used herein, an “egress mode/third mode” or “egress event” corresponds to an event where an absence of an object, such as a user, is detected by the radar sensor and the computer system determines that no object is within the field of view of the radar. An egress event results in the computer system modulating the algorithm and radar configuration utilized by the radar sensor as well as changing the operating state of the display device to turn off.
As used herein, a “static presence mode/second mode” or “static presence event” corresponds to an event where the radar sensor detects an object within the field of view but very little movement or energy is detected by the radar sensor. A static presence event can correspond to a user sitting or laying down on a couch or chair in view of the display device while consuming content. The minimal movements by the user while consuming the content must be properly interpreted by the computer system or else the computer system may determine an egress event has occurred which would result in the display device turning off. However, upon determining a static presence event has occurred the computer system may instruct the display device to remain in an on state to continue presenting content and avoid turning off the display device while the user is consuming the content. By performing the processes described herein, the computer system and display device are able to switch between various modes using the dynamic radar mode modulation feature to modulate between operating states of the display device and the radar configuration utilized by the radar sensor. The dynamic modulation of these devices, configurations, and implemented algorithms can result in efficient use of the devices to turn on, turn off, or remain on which not only conserves power but results in a pleasurable viewing experience for the user. The user does not have to provide any input or interact with the devices to change the state of the device and instead can focus on viewing the content, leaving the viewing session when they want, or starting a new viewing session by merely moving within detection range or the field of view of the radar sensor. Each mode may be associated with presenting various content. For example, during an ingress event or ingress mode the display device may be configured to present a first set of content that corresponds to content stored locally on the device such as pictures or screen savers. During a static presence event or static presence mode the display device may be configured to present a second set of content that corresponds to streaming content either stored locally or received or retrieved via a network.
Scenario 1 of
Scenario 2 of
Scenario 3 of
As described below with reference to
In embodiments, the presence detection algorithm 216 may be configured, along with the presence algorithm configuration module 224 to update the radar configuration 226 utilized by radar sensor 204. For example, the radar configuration 226 module may be configured to instruct or otherwise change an operating mode for the radar sensor 204 to utilize different frame per second rates, thresholds of difference, and time windows to capture data. In embodiments, the presence algorithm configuration module 224 may be configured to update the presence detection algorithm 216 to utilize different parameters, functions, or thresholds to properly analyze data provided by the sensor 204 which corresponds to the current mode set for the computer system 202 and sensor 204. For example, a first radar configuration and algorithm may be implemented to properly detect an ingress event which is different from a second radar configuration and updated algorithm which is implemented to properly detect a static presence event. In embodiments, OS components 228 may be configured to interact with the computer system 202 and/or display device at an operating system level such as to present content. The frameworks service module 230 and radar support 218 may be configured to communicate with presence algorithm configuration module 224 to provide state information for the display device as well as whether an instructed command for operating the display device was properly executed.
For example, the threshold 314 may be generated using one or more algorithms, such as a constant false alarm rate (CFAR) algorithm. For instance, the threshold may be generated by taking an average 316 of the magnitudes detected by the radar sensor over a period of time such as one minute, five minutes, one hour, one day, etc. In some embodiments, the threshold 314 may be generated by multiplying the average 316 by a given multiplier such as 1.2, 1.5, 2, 3, and/or any other multiplier. The radar sensor may analyze the output 312 to identify at least one peak magnitude that satisfies the threshold 314. The difference between peak magnitudes 312 of consecutive frames generated by the radar sensor within a certain time window may be provided to the computer system for determining whether an object has been detected within the field of view of the radar sensor.
For example, during a certain radar configuration which corresponds to an ingress mode, which would result in the radar sensor utilizing a high threshold 314 as well as greater frame per second rate (e.g., 10 FPS), may result in providing to the computer system large differences between peak magnitudes detected by the radar sensor. The large difference between the peak magnitudes may be compared to a currently utilized threshold of difference. The difference between peak magnitudes of consecutive frames may correspond to the post processed data provided by the radar sensor to the computer system via the I2C driver bridge or I2C bridge. As described herein, the computer system may utilize certain algorithm parameters for certain algorithms which correspond to certain modes which include using certain thresholds of difference to determine whether a predicted event has occurred. For example, an egress event would correspond to a low threshold of difference occurring over a large period of time. To continue the example, an ingress event would correspond to a high threshold of difference being exceeded by differences between peak magnitudes over a shorter period of time. The computer system may instruct a radar sensor to utilize different radar configurations to detect different events which may occur given a current event state for the components implementing the dynamic radar mode modulation feature.
Once the computer system and radar sensor are configured for a static presence mode 404, the radar sensor continues to receive data and the computer system analyzes the data using the algorithm parameters or configuration for detecting a static presence event. This can result in detecting and analyzing micromotions or small movements generated by a user as they breath or slightly move during viewing of content presented by a display device. Detecting the static presence event results in maintaining an on operating state for the display device. The workflow 400 of
The flowchart 500 includes communicating with the radar controller at 512 to read detection results from the radar sensor, such as differences between consecutive frames of peak magnitudes. At 514 of the flowchart 500 a determination is made to reset the presence handle rate change flag for the radar sensor. If the flag sensor is set to 1, then the radar sensor continues setting and the flowchart 500 returns to step 506. If however, the flag is set to 1, then the radar sensor stops sensing at 516 of the flowchart 500. The stopping of the sensing at 516 provides an opportunity to update the parameters or configuration utilized by the radar sensor to detect objects within the field of view of the radar sensor. For example, during a transition between an ingress mode to a static presence mode. The flowchart 500 includes calling an API radar update parameter function at 518 to update the configuration for the radar sensor, followed by an instruction to begin sensing again at 520 by the radar sensor for objects within the field of view. The flowchart 500 then continues at 522 by resetting the presence handle rate change flag to 0 such that the radar sensor will continue detecting objects within the field of view and collecting data until a determination that an event has occurred which results in setting the flag to 1.
The flow includes, at 604, receiving first data from the radar sensor that is using the first radar configuration. As described herein, the radar sensor may be configured to process the raw data obtained by the radar sensor and provide post processed data to the computer system which includes differences between frames of signals generated by the radar sensor within a certain time window.
The flow includes, at 606, determining a presence of a user within a field of view of the radar sensor based at least in part on the first data and a first difference threshold. In embodiments, an algorithm may be instructed to utilize certain parameters or expect certain data that corresponds to the first radar configuration and the first data in order to properly determine an ingress event is occurring. For example, the differences in magnitudes of signals in the first data may need to exceed the first difference threshold in order for the computer system to determine a presence of the object.
The flow includes, at 608, instructing the television to turn on based on determining the presence of the user. In embodiments, the computer system may utilize several architecture layers such as a kernel layer, middleware, etc., which requires communication to certain applications in order to interact with the hardware (e.g., turn on the television). In embodiments, a software application may be located or implemented in an application layer of the computer system which directly interacts with an operating system of the computer system and can implement instructions such as turning on the display device (television) or turn off the display device.
The flow includes, at 610, receiving second data from the radar sensor in the first radar configuration. In embodiments, the computer system and radar sensor continue to utilize a radar configuration and algorithm for detecting ingress events.
The flow includes, at 612, determining an absence of the user within the field of view of the radar sensor based at least in part on the second data and the first difference threshold. The computer system may determine, using the parameters, thresholds, and algorithm analysis associated with an ingress event that a user is no longer moving or providing a large motion associated with an ingress event. This determination can lead to transitioning the algorithm and radar sensor to a configuration better suited to detect a static presence event.
The flow includes, at 614, instructing the radar sensor to use a second radar configuration associated with a static presence mode in response to determining the absence of the user. In embodiments, the second radar configuration comprises a second frame per second rate and a second difference threshold.
The flow includes, at 616, receiving third data from the radar sensor that is using the second radar configuration.
The flow includes, at 618, determining a static presence of the user within the field of view of the radar sensor based on the third data and a second difference threshold of the second radar configuration. In embodiments, the computer system may instruct an algorithm to update (updated algorithm) such that it utilizes certain parameters and/or expects certain data to determine that a static presence event is occurring.
The flow includes, at 620, instructing the television to maintain an on state based at least in part on determining the static presence of the user.
The flow includes, at 704, receiving, by the computer system, first data from the radar sensor in the first radar configuration.
The flow includes, at 706, determining, by the computer system, a presence of an object within a field of view of the radar sensor based on the first data and the first difference threshold.
The flow includes, at 708, instructing, by the computer system, the device to turn on based on determining the presence of the user.
The flow includes, at 710, instructing, by the computer system, the radar sensor to implement a second radar configuration associated with a static presence (second) mode based at least in part on determining an absence of the object using second data received from the radar sensor using the first radar configuration and the first difference threshold, the second radar configuration comprising a second FPS rate and a second difference threshold. In embodiments, the computer system may be configured to determine that an egress event has occurred (the object has left the field of view of the radar sensor and data received by the radar sensor does not exceed the second difference threshold). For example, the computer system may receive third data from the radar sensor in the second radar configuration. The computer system may determine an absence of the object within the field of view of the radar sensor based on the third data and the second difference threshold.
In response to determining the absence of the user the computer system may instruct the device to turn off the device. As described herein, the computer system may implement certain hardware and/or software modules at different system architecture levels. For example, the computer system may implement a radar support module in a middleware layer of the computer system that is configured to transmit the instructions to the software application of the device for turning the display device on or off or presenting content. In an embodiment, the computer system may implement a presence algorithm configuration module in a kernel layer of the computer system that is configured to update the radar configurations utilized by the radar sensor in response to the instructions by the computer system. The algorithm utilized by the computer system may be implemented in the kernel layer of the computer system.
The flow includes, at 804, receiving second data from the radar sensor in the second radar configuration. In embodiments, the first data, second data, and third data are transmitted, by the radar sensor and to the computer system, via an inter-integrated circuit (I2C) driver bridge or bridge.
The flow includes, at 806, determining the static presence of an object within the field of view of the radar sensor based on the second data and the second difference threshold.
The flow includes, at 808, instructing the radar sensor to implement a first radar configuration associated with an ingress mode in response to determining the static presence of the object, the first radar configuration comprising a first FPS rate and a first difference threshold.
In embodiments, the computer system 902 may implement one or more applications 912 which include radar support 914, presence algorithm configuration 916, radar configuration 918, and presence detection algorithm 920. Although the computer system 902 of
In embodiments, the presence algorithm configuration 916 may be configured to generate and transmit instructions to the radar configuration 918 for updating a radar configuration to use by the radar sensor 904 as well as update the parameters, functions, thresholds, and/or input utilized by presence detection algorithm 920 for processing the received data from the radar sensor 904 via bridge 908. For example, the presence algorithm configuration 916 may maintain one or more radar configurations as well as one or more algorithms to utilize based on the mode determined by the computer system 902 to utilize (e.g., ingress, egress, static mode). As described above, the radar configuration 918 may be configured to maintain, update, and instruct or otherwise update the frame rate per second rate and thresholds utilized by the radar sensor 904 to process incoming data captured by the radar sensor 904.
The presence detection algorithm 920 may be configured to receive and process data from the radar sensor 904 transmitted via bridge 908 and determine, using a certain radar configuration, an event associated with the data. For example, the presence detection algorithm 920 may be configured to determine a presence of an object (ingress event), an absence of an object (egress event), or a static presence of an object (static presence event) based on the particular implemented algorithm, the current radar configuration, and the received data from the radar sensor 904. Based on determining a certain state of an object or occurrence of an event, instructions may be generated by the presence detection algorithm 920 and computer system 902 to update the current radar configuration (radar configuration 918), the current algorithm utilized (presence algorithm configuration 916) as well as tasks to be performed with the display 906 via the radar support 914 and operating system applications 910.
In accordance with at least one embodiment, the radar sensor 904 and location component 928 may use the output data 938 to determine a distance of a possible object relative to the display 906 and/or radar sensor 904. For example, since the output data 938 represents the magnitude for all objects, a static object canceller 940 may be configured to subtract output data 938 representing a previous frame (and/or output data 938 representing more than one previous frame) from current output data 938. Based on the subtraction, the static object canceller 940 may generate an output that represents a magnitude of dynamic objects within the field of view of radar sensor 904. In embodiments, the threshold generator 942 may use one or more thresholds of difference to determine if an object is detected by determining whether a detected magnitude exceeds the threshold. In embodiments the detector 944 may determine a difference between magnitude peaks of frames according to a specified frame per second rate and provide the differences between the magnitude peaks as data to the computer system 902 via bridge 908 for processing using the presence detection algorithm 920. In embodiments, the bridge 908 may include an I2C bridge. The presence detection algorithm 920 may use the data to determine a presence of an object, absence of an object, or static presence of an object and perform modulation of a radar mode for the radar sensor 904 as well as perform an operation via the display 906 such as turning the display 906 on or off. In embodiments, the detector 944 may analyze the output data 938 to determine a distance to the object from the display 906 and/or radar sensor 904.
In some examples, cell phones (or, more broadly, mobile phones) may be one specific type of mobile device that is an example of the electronic client device 1002. In some instances, a user's mobile device may be considered their primary client device. Other example mobile devices include wearables, such as watches, worn sensors (e.g., rings, bracelets, etc.), cameras, eyeglasses, and the like, which may be considered “connected” auxiliary devices. In some examples, the combination of a user's primary mobile device and all or some of their connected, auxiliary devices, may make up a single mobile system configured to communicate with the Web server 1006 or other servers over the network 1004 or other networks.
The illustrative environment includes at least one application server 1008 and a data store 1010. It should be understood that there can be several application servers, layers, or other elements, processes, or components, which may be chained or otherwise configured, which can interact to perform tasks such as obtaining data from an appropriate data store. As used herein the term “data store” refers to any device or combination of devices capable of storing, accessing, and retrieving data, which may include any combination and number of data servers, databases, data storage devices, and data storage media, in any standard, distributed, or clustered environment. The application server can include any appropriate hardware and software for integrating with the data store as needed to execute aspects of one or more applications for the client device, handling a majority of the data access and business logic for an application as well as generating or otherwise providing content, implementing and updating algorithms or other tasks described herein with reference to the computer system. The application server provides access control services in cooperation with the data store and is able to generate content such as text, graphics, audio, and/or video to be transferred to the user, which may be served to the user by the Web server in the form of HyperText Markup Language (“HTML”), Extensible Markup Language (“XML”), or another appropriate structured language in this example. The handling of all requests and responses, as well as the delivery of content between the client device 1002 and the application server 1008, can be handled by the Web server. It should be understood that the Web and application servers are not required and are merely example components, as structured code discussed herein can be executed on any appropriate device or host machine as discussed elsewhere herein.
The data store 1010 can include several separate data tables, databases or other data storage mechanisms and media for storing data relating to a particular aspect. For example, the data store illustrated includes mechanisms for storing algorithm configuration(s) 1012 and thresholds 1016, which can be used to serve content for the production side as well as configure implemented algorithms to utilize certain parameters or data such as particular thresholds from the thresholds 1016 which correspond to different radar configurations (1014) and radar modes for detecting or determining different events (e.g., ingress, static presence, or egress). The data store also is shown to include a mechanism for storing radar configuration(s) 1014, which can be used for reporting, analysis, or other such purposes such as specifying instructions and parameters for a radar sensor to utilize when obtaining data (first data, second data, and/or third data). It should be understood that there can be many other aspects that may need to be stored in the data store, such as for page image information and to access right information, which can be stored in any of the above listed mechanisms as appropriate or in additional mechanisms in the data store 1010. The data store 1010 is operable, through logic associated therewith, to receive instructions from the application server 1008 and obtain, update or otherwise process data in response thereto. In one example, a user might submit a search request for a certain type of item. In this case, the data store might access the user information to verify the identity of the user and can access the catalog detail information to obtain information about items of that type. The information then can be returned to the user, such as in a results listing on a Web page that the user is able to view via a browser on the user device 1002. Information for a particular item of interest can be viewed in a dedicated page or window of the browser. In another example, the radar sensor, through the client device 1002 and network 1004, may provide data obtained by the radar sensor using a certain radar configuration from the radar configuration(s) 1014, to the web server 1006 and application server 1008. In embodiments, the web server 1006 and/or application server 1008 may utilize one or more implemented algorithms along with parameters or attributes specified by the algorithm configuration(s) 1012 to determine an event associated with the data along with comparing the data to a threshold of difference as specified in thresholds 1016. For example, the algorithm may determine a presence of an object using the specific algorithm, data, and threshold. In response to determining an event has occurred (ingress, egress, static presence) the web server 1006 and/or application server 1008 may update the algorithm configuration 1012 to be utilized, obtain a radar configuration from radar configuration 1014, and a certain threshold 1016. The web server 1006 and/or application server 1008 may transmit instructions, via network 1004, to update the radar configuration utilized by the radar sensor associated with the client device 1002 as well as the threshold to utilize.
Each server typically will include an operating system that provides executable program instructions for the general administration and operation of that server and typically will include a computer-readable storage medium (e.g., a hard disk, random access memory, read only memory, etc.) storing instructions that, when executed by a processor of the server, allow the server to perform its intended functions. Suitable implementations for the operating system and general functionality of the servers are known or commercially available and are readily implemented by persons having ordinary skill in the art, particularly in light of the disclosure herein.
The environment in one embodiment is a distributed computing environment utilizing several computer systems and components that are interconnected via communication links, using one or more computer networks or direct connections. However, it will be appreciated by those of ordinary skill in the art that such a system could operate equally well in a system having fewer or a greater number of components than are illustrated in
The various embodiments further can be implemented in a wide variety of operating environments, which in some cases can include one or more user computers, computing devices or processing devices which can be used to operate any of a number of applications. User or client devices can include any of a number of general purpose personal computers, such as desktop or laptop computers running a standard operating system, as well as cellular, wireless, and handheld devices running mobile software and capable of supporting a number of networking and messaging protocols. Such a system also can include a number of workstations running any of a variety of commercially-available operating systems and other known applications for purposes such as development and database management. These devices also can include other electronic devices, such as dummy terminals, thin-clients, gaming systems, and other devices capable of communicating via a network.
Most embodiments utilize at least one network that would be familiar to those skilled in the art for supporting communications using any of a variety of commercially-available protocols, such as Transmission Control Protocol/Internet Protocol (“TCP/IP”), Open System Interconnection (“OSI”), File Transfer Protocol (“FTP”), Universal Plug and Play (“UpnP”), Network File System (“NFS”), Common Internet File System (“CIFS”), and AppleTalk. The network can be, for example, a local area network, a wide-area network, a virtual private network, the Internet, an intranet, an extranet, a public switched telephone network, an infrared network, a wireless network, and any combination thereof.
In embodiments utilizing a Web server, the Web server can run any of a variety of server or mid-tier applications, including Hypertext Transfer Protocol (“HTTP”) servers, FTP servers, Common Gateway Interface (“CGI”) servers, data servers, Java servers, and business application servers. The server(s) also may be capable of executing programs or scripts in response to requests from user devices, such as by executing one or more Web applications that may be implemented as one or more scripts or programs written in any programming language, such as Java®, C, C#, or C++, or any scripting language, such as Perl, Python, or TCL, as well as combinations thereof. The server(s) may also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, and IBM®.
The environment can include a variety of data stores and other memory and storage media as discussed above. These can reside in a variety of locations, such as on a storage medium local to (and/or resident in) one or more of the computers or remote from any or all of the computers across the network. In a particular set of embodiments, the information may reside in a storage-area network (“SAN”) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers, servers, or other network devices may be stored locally and/or remotely, as appropriate. Where a system includes computerized devices, each such device can include hardware elements that may be electrically coupled via a bus, the elements including, for example, at least one central processing unit (“CPU”), at least one input device (e.g., a mouse, keyboard, controller, touch screen, or keypad), and at least one output device (e.g., a display device, printer, or speaker). Such a system may also include one or more storage devices, such as disk drives, optical storage devices, and solid-state storage devices such as random access memory (“RAM”) or read-only memory (“ROM”), as well as removable media devices, memory cards, flash cards, etc.
Such devices also can include a computer-readable storage media reader, a communications device (e.g., a modem, a network card (wireless or wired)), an infrared communication device, etc.), and working memory as described above. The computer-readable storage media reader can be connected with, or configured to receive, a computer-readable storage medium, representing remote, local, fixed, and/or removable storage devices as well as storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information. The system and various devices also typically will include a number of software applications, modules, services, or other elements located within at least one working memory device, including an operating system and application programs, such as a client application or Web browser. It should be appreciated that alternate embodiments may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
Storage media computer readable media for containing code, or portions of code, can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, Electrically Erasable Programmable Read-Only Memory (“EEPROM”), flash memory or other memory technology, Compact Disc Read-Only Memory (“CD-ROM”), digital versatile disk (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a system device. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the various embodiments.
The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the disclosure as set forth in the claims.
Other variations are within the spirit of the present disclosure. Thus, while the disclosed techniques are susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the disclosure to the specific form or forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the disclosure, as defined in the appended claims.
The use of the terms “a” and “an” and “the” and similar referents in the context of describing the disclosed embodiments (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (i.e., meaning “including, but not limited to,”) unless otherwise noted. The term “connected” is to be construed as partly or wholly contained within, attached to, or joined together, even if there is something intervening. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate embodiments of the disclosure and does not pose a limitation on the scope of the disclosure unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.
Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is intended to be understood within the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
Preferred embodiments of this disclosure are described herein, including the best mode known to the inventors for carrying out the disclosure. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventors expect skilled artisans to employ such variations as appropriate and the inventors intend for the disclosure to be practiced otherwise than as specifically described herein. Accordingly, this disclosure includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.
All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.