Patent Application
20160192318
Wireless telecommunication networks, such as cellular networks, may provide cellular service via base stations. The coverage offered by base stations may be interrupted or otherwise degraded based on the presence of structures (such as buildings), topography (such as mountains), or other factors. Femtocells may be deployed in areas where cellular coverage is relatively poor. User devices (such as cellular telephones) may connect to the cellular network via femtocells, in order to obtain wireless service.
The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
Femtocells may augment the coverage of a wireless telecommunications network, by allowing wireless coverage to be provided to areas the ordinarily would not be serviced by the wireless telecommunications network. For example, buildings or terrain may interfere with wireless coverage provided by cells of a wireless telecommunications network, certain areas may be out of range of cells of a wireless telecommunications network, radio frequency (“RF”) interference may degrade cell coverage, etc. Femtocells may be deployed by individuals or businesses, and the locations of deployed femtocells may not necessarily be known to an operator of the wireless telecommunications network. It may be beneficial for the locations of femtocells to be known, so that messages or other communications can be sent via particular femtocells.
For example, emergency messages may be relevant to a particular building, city block, or other localized region (e.g., a fire alarm, a flood warning, etc.). Femtocells, that service the localized region, may be used to broadcast emergency messages to user devices (e.g., cellular telephones) within the localized region, thereby increasing the chance that these user devices receive the emergency messages. As another example, the operator of the wireless network may use location information, for a particular femtocell, to determine a billing rate associated with the femtocell. For example, a femtocell in a high rise commercial building may be associated with a higher billing rate (e.g., a monthly subscription for leasing or operating the femtocell), while a femtocell in a rural home may be associated with a lower billing rate. As yet another example, the operator of the wireless network may use location information, for a particular femtocell, to determine whether the particular femtocell is authorized to be operated in a particular location. For instance, a user may be authorized to deploy a femtocell only within the user's home, or certain areas may exist where the use of femtocells is not authorized (e.g., stadiums, government facilities, etc.). Since femtocells typically do not include the capability to determine and/or report location information, it may be difficult or impossible to determine the locations of deployed femtocells.
Some implementations, described herein, may allow the locations of femtocells to be determined. For example, as described below, location information, signal quality, and/or other information, may be received from user devices, that attach to femtocells (and/or from femtocell gateways, or the femtocells themselves). This information may be aggregated and used to determine the location of femtocells. In some implementations, as shown in
While the term “femtocell” is used herein, similar techniques may apply to “small cells” in general. For instance, techniques described herein may apply to microcells, picocells, nanocells, and/or other types of devices that provide wireless access to a wireless telecommunications network.
Environment 200 may include an evolved packet system (“EPS”) that includes a long term evolution (“LTE”) network and/or an evolved packet core (“EPC”) network that operate based on a third generation partnership project (“3GPP”) wireless communication standard. The LTE network may be, or may include, a radio access network (“RAN”) that includes one or more base stations 210, some or all of which may take the form of an evolved node B (“eNB”), via which user device 205 may communicate with the EPC network. The EPC network may include one or more SGWs 230, PGWs 235, and/or MMEs 240, and may enable user device 205 to communicate with PDN 260 and/or an Internet protocol (“IP”) multimedia subsystem (“IMS”) core network. The IMS core network may include HSS/AAA server 250, and may manage authentication, session initiation, account information, a user profile, etc., associated with user device 205.
User device 205 may include a computation and communication device, such as a wireless mobile communication device that is capable of communicating with base station 210, femtocell 215, and/or PDN 260. For example, user device 205 may include a radiotelephone; a personal communications system (“PCS”) terminal (e.g., a device that combines a cellular radiotelephone with data processing and data communications capabilities); a personal digital assistant (“PDA”) (e.g., that can include a radiotelephone, a pager, Internet/intranet access, etc.); a smart phone; a laptop computer; a tablet computer; a camera; a personal gaming system, or another type of mobile computation and communication device. User device 205 may send traffic to and/or receive traffic from PDN 260 via base station 210, femtocell 215, femtocell gateway 220, SGW 230, and/or PGW 235.
Base station 210 may include one or more network devices that receive, process, and/or transmit traffic, such as calls, audio, video, text, and/or other data, destined for and/or received from user device 205. In one example, base station 210 may be an eNB device and may be part of the LTE network. Base station 210 may receive traffic from and/or send traffic to user device 205 via SGW 230, PGW 235, and/or PDN 260. Base station 210 may send traffic to and/or receive traffic from user device 205 via, for example, an air interface (e.g., a cellular air interface).
Femtocell 215 may also include one or more network devices that receive process, and/or transmit traffic, such as calls, audio, video, text, and/or other data, destined for and/or received from user device 205. In one example, femtocell 215 may include a portable device that may be deployed (e.g., physically placed and/or installed) by an end user (e.g., an individual or business that is separate from an entity that owns and/or operates the LTE network). Femtocell 215 may be directly communicatively coupled to MME 240, and/or maybe indirectly coupled to SGW 230 and/or MME 240 (e.g., via femtocell gateway 220). Femtocell 215 (and/or femtocell gateway 220) may, in some implementations, be communicatively coupled to SGW 230 and/or MME 240 via PDN 260.
Femtocell 215 may generally provide connectivity, to the LTE network, in locations where LTE coverage (e.g., as provided by one or more base stations 210) is poor or is non-existent. For example, a customer may place femtocell 215 in an office building, in which LTE coverage is poor, or in a rural residence, in which LTE coverage is non-existent. As mentioned above, the term “femtocell,” as used herein, may refer to a small cell that provides connectivity to a wireless telecommunications network. The coverage area, associated with femtocell 215, may be smaller than the coverage area associated with base station 210. For instance, base station 210 may have a range of up to 35 kilometers, while femtocell 215 may have a range of 200 meters, 10 meters, or some other range. In 3GPP terminology, a femtocell may be a Home Node B (“HNB”) or a Home eNB (“HeNB”).
Femtocell gateway 220 may include one or more network devices, via which one or more femtocells 215 may be communicatively coupled to MME 240 and/or to SGW 230. For example, femtocell gateway 220 may include one set of interfaces to communicate with SGW 230 and/or MME 240, and another set of interfaces (e.g., interfaces of a different type) to communicate with one or more femtocells 215. Femtocell gateway 220 may aggregate control information (e.g., identifiers of femtocells 215 to which user devices 205 are connected, identifiers of user devices 205 that are connected to femtocells 215, handover/hand-in/hand-out instructions, etc.) from multiple femtocells 215, and may report the information to FMS 225 and/or MME 240. Additionally, or alternatively, femtocell gateway 220 may aggregate user plane data (e.g., substantive traffic, such as call traffic, audio/video streaming traffic, web traffic, etc.) and/or user plane data to and/or from multiple femtocells 215.
FMS 225 may include one or more devices that generate a map (e.g., a three-dimensional map) of femtocells 215. As described below, FMS 225 may generate the map based on location information received from one or more user devices 205, control information received from femtocell 215 and/or femtocell gateway 220, information received from MME 240, and/or other information. In some implementations, FMS 225 may be implemented as a standalone device that is separate from femtocell gateway 220 and MME 240. In other implementations, some or all of the functionality, associated with FMS 225, may be integrated within femtocell gateway 220, MME 240, and/or another device. FMS 225 may include a hardware interface, such as wired and/or wireless circuitry that enables FMS 225 to communicate with user device 205, femtocell 215, femtocell gateway 220, MME 240, and/or other devices.
SGW 230 may include one or more network devices that gather, process, search, store, and/or provide information in a manner described herein. SGW 230 may, for example, aggregate traffic received from one or more base stations 210, femtocells 215, and/or femtocell gateways 220, and may send the aggregated traffic to PDN 260 via PGW 235.
PGW 235 may include one or more network devices that gather, process, search, store, and/or provide information in a manner described herein. PGW 235 may aggregate traffic received from one or more SGWs 230, etc. and may send the aggregated traffic to PDN 260. PGW 235 may also, or alternatively, receive traffic from PDN 260 and may send the traffic toward user device 205 via base station 210, femtocell 215, femtocell gateway 220, and/or SGW 230.
MME 240 may include one or more computation and communication devices that perform operations to register user device 205 with the EPS, to establish bearer channels associated with a session with user device 205, to hand off user device 205 from the EPS to another network, to hand off user device 205 from the other network to the EPS, and/or to perform other operations. MME 240 may perform policing operations on traffic destined for and/or received from user device 205.
PCRF 245 may include one or more devices that aggregate information to and from the EPC network and/or other sources. PCRF 245 may receive information regarding policies and/or subscriptions from one or more sources, such as subscriber databases and/or from one or more users (such as, for example, an administrator associated with PCRF 245).
HSS/AAA server 250 may include one or more devices that manage, update, and/or store, in a memory associated with HSS/AAA server 250, profile information associated with a subscriber. The profile information may identify applications and/or services that are permitted for and/or accessible by the subscriber; a mobile directory number (“MDN”) associated with the subscriber; bandwidth or data rate thresholds associated with the applications and/or services; information associated with the subscriber (e.g., a username, a password, etc.); rate information; minutes allowed for a subscriber (e.g., a subscriber associated with user device 205); information regarding services to which particular subscribers are subscribed (e.g., communication services, such as video conferencing services, voice chat services, etc.); and/or other information. Additionally, or alternatively, HSS/AAA server 250 may perform authentication, authorization, and/or accounting operations associated with the subscriber and/or a communication session with user device 205.
CSCF 255 may perform session control, authentication, and/or other functions associated with IMS services, on behalf of user device 205. In some implementations, CSCF may include multiple components, such as a proxy-CSCF (“P-CSCF”), a serving-CSCF (“S-CSCF”), and/or an interrogating-CSCF (“I-CSCF”). The S-CSCF may maintain correlations between user device 205 IP addresses and Session Initiation Protocol (“SIP”) addresses, determine application servers to which traffic should be forwarded, provide routing services, and/or perform other functions. The I-CSCF may serve as a forwarding point for outside traffic to the IMS core network and/or to the S-CSCF, and may have a published IP address (e.g., the IP address may be registered with a Domain Name System (“DNS”) server). The P-CSCF may serve as an SIP proxy that may aid I n the initial registration of user device 205 with the IMS core network.
PDN 260 may include one or more wired and/or wireless networks. For example, PDN 260 may include an Internet Protocol (“IP”)-based PDN, a wide area network (“WAN”) such as the Internet, a core network of a telecommunications provider, a private enterprise network, and/or one or more other networks. User device 205 may connect, through PGW 235, to data servers, application servers, other user devices 205, and/or to other servers or applications that are coupled to PDN 260. PDN 260 may be connected to one or more other networks, such as a public switched telephone network (“PSTN”), a public land mobile network (“PLMN”), and/or another network. While “direct” connections are shown in
Central FMS 515 may be a “central” FMS, in that central FMS 515 may receive information from one or more FMSs 225. For instance, FMSs 225 may be deployed in a hierarchical manner, such as in the example implementation shown in
Femtocell attach event module 605 may detect attach events related to femtocells 215. An “attach event,” as used herein, may refer to when user device 205 has attached to a particular femtocell 215, when user device 205 has detached from femtocell 215, when user device 205 has been handed over from one femtocell 215 to another femtocell 215, when user device 205 has been handed over from base station 210 to femtocell 215, when user device 205 has been handed over from femtocell 215 to base station 210, when user device 205 has detected the presence of femtocell 215, or the like. Femtocell attach event module 605 may determine an identifier associated with the femtocell(s) associated with the attach event. In some implementations, the identifier, for a particular femtocell, may be a Cell Global Identity (“CGI”), an Evolved CGI (“ECGI”), and/or another unique identifier.
Location module 610 may determine a geographic location associated with user device 205. Location module 610 may, for example, use Global Positioning System (“GPS”) techniques, assisted GPS (“A-GPS”) techniques, network-based techniques (e.g., by requesting a location from a wireless telecommunications network), and/or one or more other techniques. In some implementations, location module 610 may periodically, continuously, or intermittently monitor the location of user device 205. Location module 610 may, in some implementations, determine a height of user device 205. For example, location module 610 may determine an altitude, a floor of a building in which user device 205 is located, etc. Location module 610 may make use of an altimeter, and/or may use another technique in order to determine the height of user device 205. In some implementations, location module 610 may determine the location of user device 205 at the time that an attach event is detected by femtocell attach event module 605.
Femtocell signal quality module 615 may determine a signal quality between user device 205 and one or more femtocells 215 (e.g., the femtocell(s) 215 associated with an attach event detected by femtocell attach event module 605). The signal “quality” may refer to a signal strength, which may be in terms of signal to interference and noise ratio (“SINR”), signal to noise ratio (“SNR”), or the like. For instance, a relatively low SINR value may indicate a relatively weak signal, while a relatively high SINR value may indicate a relatively strong signal.
In some implementations, signal “quality” may additionally, or alternatively, refer to other measures or indicators of the quality of a signal, such as a Channel Quality Index (“CQI”), reported by user device 205, and/or other quality indicators. As described below, signal quality may be used, in some implementations, to approximate the distance of user device 205 from a particular femtocell 215.
FMS interface 620 may include an implementation of a particular application programming interface (“API”), an IP interface, and/or another type of interface, via which user device 205 may communicate with FMS 225. For example, in some implementations, user device 205 may communicate with FMS 225 via PDN 260. In some such implementations, FMS interface 620 may utilize an IP address (and/or another identifier), associated with FMS 225, in order to communicate with FMS 225. In some implementations, user device 205 may communicate with FMS 225 via the LTE network (e.g., by augmenting or supplementing standard interfaces that are present in current 3GPP standards). Via FMS interface 620, user device 205 may output information regarding attach events (e.g., an ECGI of femtocell 215 associated with the attach event, an identifier associated with user device 205 (e.g., an International Mobile Subscriber Identity (“IMSI”) value, an International Mobile Station Equipment Identity (“IMEI”), etc.), a signal quality/strength, a time at which the attach event occurred, a location of user device 205 when the attach event occurred, and/or other information).
Femtocell attach event module 705 may receive information from one or more femtocells 215 (e.g., femtocells that are connected to femtocell gateway 220), regarding an attach event associated with the one or more femtocells 215. The information may include, for example, an identifier of femtocell 215, an identifier of a particular user device 205 associated with the attach event, a signal quality/strength between femtocell 215 and user device 205, or the like).
FMS interface 710 may include an implementation of an API, an IP interface, and/or another type of interface, via which femtocell gateway 220 may communicate with FMS 225. For example, in some implementations, femtocell gateway 220 may communicate with FMS 225 via PDN 260. In some implementations, femtocell gateway 220 may communicate with FMS 225 via the LTE network (e.g., by augmenting or supplementing standard interfaces that are present in current 3GPP standards). Via FMS interface 710, user device 205 may output information regarding attach events (e.g., as received from one or more femtocells 215, via femtocell attach event module 705).
User device interface 805, femtocell gateway interface 810, and MME interface 815 may include interfaces, via which FMS 225 communicates with one or more user devices 205, one or more femtocell gateways 220, and MME 240, respectively. User device interface 805, femtocell gateway interface 810, and MME interface 815 may each include an implementation of an API, an IP interface, and/or another type of interface. In some implementations, femtocell gateway interface 810 may communicate with one or more femtocells 215 (e.g., without an intervening femtocell gateway 220).
Attach event information repository 820 may store information regarding attach events (e.g., as received from user devices 205, femtocells 215, and/or femtocell gateways 220). As shown, the information may include a user device identifier (“UD ID”), a user device location, a femtocell identifier, signal quality/strength information, and information regarding the type of attach event. As described above, the user device identifier may include an IMSI value, an IMEI value, and/or another type of identifier that may be used to identify user device 205.
The user device location field may store information regarding user device 205, at the time of (e.g., at the exact same time, or within a particular window of time, such as within one second, within ten seconds, within a minute, etc.) a particular attach event. The location information may, in some implementations, be received from user device 205. Additionally, or alternatively, the location information may be received from MME 240, and/or another source. For example, FMS 225 may request (via MME interface 815) location information from MME 240, MME 240 may push location information to FMS 225, and/or location information may be received from a service or device that tracks the location of user device 205.
The femtocell identifier field may store information regarding one or more femtocells, associated with the attach event. As mentioned above, the femtocell identifier may include a CGI, an ECGI, and/or another type of identifier. As described further below, in some situations, a particular attach event may include the simultaneous detection of the presence of two or more femtocells 215. In these situations, the femtocell identifier field may store multiple identifiers, which respectively correspond to the two or more femtocells 215.
The signal strength field may store signal strength information associated with the attach event. As mentioned above, the signal strength field may include an SNR value, an SINR value, and/or another type of value. While not shown here, attach event information repository may additionally, or alternatively, include other types of information related to signal strength and/or quality, such as CQI values.
The attach event type field may include information regarding the type of the attach event. For instance, this field may store information indicating whether the attach event is an attachment to femtocell 215, a detachment from femtocell 215, a handover from femtocell 215 to another femtocell 215, a handover from base station 210 to femtocell 215, a handover from femtocell 215 to base station 210, and/or a detection of the presence of one or more femtocells 215. As described below, this information may useful in determining spatial relationships of femtocells 215, determining cell edges of femtocells 215, identifying overlapping coverage areas of femtocells 215, etc.
Femtocell mapping logic 825 may identify locations of femtocells 215, based on the information stored by attach event information repository 820. For example, femtocell mapping logic 825 may estimate the location of a particular femtocell 215, based on location information, signal quality/strength information, etc., received from multiple user devices 205 that have attached to femtocell 215. Examples of the determination of the locations of femtocells 215, by femtocell mapping logic 825, are described below in greater detail.
Femtocell mapping logic 825 may generate a map (e.g., a visual map, similar to the example shown in
In some implementations, femtocell mapping logic 825 may modify an existing map based on retrieved information. For instance, in the situation where a particular femtocell 215 is moved, femtocell mapping logic 825 may begin to receive location information that conflicts with previously received location information that corresponds to femtocell 215. After receiving enough location information to substantiate the inference that femtocell 215 has been moved (e.g., after receiving at least a threshold amount of location information regarding user devices 205 that have attached to, or detected, femtocell 215 in the new location), femtocell mapping logic 825 may modify a previous map to reflect the new location of femtocell 215.
Further, femtocell mapping logic 825 may refine an existing map based on retrieved information. For instance, assume that femtocell mapping logic 825 has identified a location of a particular femtocell 215, with an accuracy of 15 meters (e.g., in a scenario where user devices 205 within a 15 meter radius have provided location information). Further assume that femtocell mapping logic 825 begins to receive location information from user devices 205, corresponding to femtocell 215, within a 5 meter radius. Femtocell mapping logic 825 may determine that the location of femtocell 215 with an accuracy of 5 meters (e.g., a refinement as compared to 15 meters), based on the new location information.
Femtocell gateway 220 may forward (at 915) the user device identifier and the femtocell identifier to FMS 225. FMS 225 may request (at 920) additional information from user device 205. For instance, FMS 225 may request a location of user device 205 at the time of the attachment, a signal quality (e.g., signal strength or other measure of quality) between user device 205 and femtocell 215, and/or other information. User device 205 may provide (at 925) the requested information to FMS 225. In some implementations, user device 205 may “push” the information to FMS 225 (e.g., without a request from FMS 225). For instance, user device 205 may push the information based on attaching to femtocell 215, and/or may push the information on a periodic or intermittent basis. Additionally, or alternatively, while not shown in this figure, FMS 225 may request information from one or more other sources. For instance, as mentioned above, FMS 225 may request location information, regarding user device 205, from MME 240 and/or one or more other devices. FMS 225 may use the information, provided by user device 205, femtocell gateway 220, and/or the one or more other devices, in order to determine a location (or an approximate location) of femtocell 215.
Process 1000 may further include determining (at 1010) a location of user device 205. For instance, as described above with respect to location module 610, user device 205 may determine its location using GPS techniques, A-GPS techniques, network-based techniques, etc.
Process 1000 may also include storing and/or outputting (at 1015) the location information and the attach event information. For example, user device 205 may output information identifying the type of attach event (e.g., attachment, detachment, presence detection, etc.) to FMS 225. Additionally, or alternatively, user device 205 may output location information at the time of the attach event, an identifier associated with user device 205, an identifier associated with the one or more femtocells 215, etc., to FMS 225.
Process 1100 may also include determining (at 1110) an identifier of a particular user device 205, with which the attach event is associated. For example, femtocell 215 and/or femtocell gateway 220 may identify an IMSI, an IMEI, and/or another identifier of user device 205. The user device identifier may be received, for instance, as part of an attachment or handover procedure.
Process 1100 may further include storing and/or outputting (at 1115) information regarding the attach event, user device 205, and/or the one or more femtocells 215. For example, femtocell 215 and/or femtocell gateway 220 may output information identifying the type of attach event (e.g., attachment, detachment, handover, etc.) to FMS 225. Additionally, or alternatively, user device 205 may output an identifier associated with user device 205, an identifier associated with the one or more femtocells 215, etc., to FMS 225.
In some implementations, multiple sources may provide information regarding the same attach event. For instance, user device 205 and femtocell gateway 220 may provide information regarding the same particular attach event. In some implementations, FMS 225 may identify that the information, from the multiple sources, pertains to the same attach event, and may stitch the information together, in lieu of creating multiple data records. For instance, FMS 225 may identify that the information is associated with the same time, the same user device 205, the same femtocell(s) 215, etc.
Process 1200 may also include generating (at 1210) and/or modifying a map of femtocells 215, based on the received information. For instance, as described above, FMS 225 may generate one or more maps (e.g., three-dimensional maps), overlays, and/or other types of representations regarding femtocells 215, based on the information received at 1215.
In some implementations, FMS 225 may identify spatial relationships of femtocells 215, based on the received information.
Further, assume that user device 205 subsequently moves to coverage area 1305-3, and is thus handed over to femtocell 215-12. Based on identifying this handover, it may be inferred (e.g., by FMS 225) that femtocell 215-11 and femtocell 215-12 are located close enough to each other that a handover is possible from femtocell 215-11 to femtocell 215-12, without interruption. It may further be inferred that femtocell 215-11 is closer to femtocell 215-10 than femtocell 215-12 is (e.g., that femtocell 215-11 is an intervening femtocell 215 in between femtocell 215-10 and femtocell 215-2).
As shown in
As further shown, user device 205 may subsequently move in to coverage area 1405-2 (e.g., may be “handed in” to femtocell 215-14). Based on the fact that user device 205 was handed out of coverage area 1405-1 without being handed over to another femtocell 215, it may be inferred that femtocell 215-13 is not relatively close to another femtocell 215 (e.g., to femtocell 215-14). This inference may be made, for instance, because coverage area 1405-1, associated with femtocell 215-13, may not overlap with the coverage area of another femtocell 215 (e.g., with coverage area 1405-2).
Bus 1610 may include one or more communication paths that permit communication among the components of device 1600. Processor 1620 may include a processor, microprocessor, or processing logic that may interpret and execute instructions. Memory 1630 may include any type of dynamic storage device that may store information and instructions for execution by processor 1620, and/or any type of non-volatile storage device that may store information for use by processor 1620.
Input component 1640 may include a mechanism that permits an operator to input information to device 1600, such as a keyboard, a keypad, a button, a switch, etc. Output component 1650 may include a mechanism that outputs information to the operator, such as a display, a speaker, one or more light emitting diodes (“LEDs”), etc.
Communication interface 1660 may include any transceiver-like mechanism that enables device 1600 to communicate with other devices and/or systems. For example, communication interface 1660 may include an Ethernet interface, an optical interface, a coaxial interface, or the like. Communication interface 1660 may include a wireless communication device, such as an infrared (“IR”) receiver, a Bluetooth® radio, or the like. The wireless communication device may be coupled to an external device, such as a remote control, a wireless keyboard, a mobile telephone, etc. In some embodiments, device 1600 may include more than one communication interface 1660. For instance, device 1600 may include an optical interface and an Ethernet interface.
Device 1600 may perform certain operations relating to one or more processes described above. Device 1600 may perform these operations in response to processor 1620 executing software instructions stored in a computer-readable medium, such as memory 1630. A computer-readable medium may be defined as a non-transitory memory device. A memory device may include space within a single physical memory device or spread across multiple physical memory devices. The software instructions may be read into memory 1630 from another computer-readable medium or from another device. The software instructions stored in memory 1630 may cause processor 1620 to perform processes described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
The foregoing description of implementations provides illustration and description, but is not intended to be exhaustive or to limit the possible implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.
For example, while series of blocks and/or signals have been described with regard to
The actual software code or specialized control hardware used to implement an embodiment is not limiting of the embodiment. Thus, the operation and behavior of the embodiment has been described without reference to the specific software code, it being understood that software and control hardware may be designed based on the description herein.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of the possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one other claim, the disclosure of the possible implementations includes each dependent claim in combination with every other claim in the claim set.
Further, while certain connections or devices are shown, in practice, additional, fewer, or different, connections or devices may be used. Furthermore, while various devices and networks are shown separately, in practice, the functionality of multiple devices may be performed by a single device, or the functionality of one device may be performed by multiple devices. Further, multiple ones of the illustrated networks may be included in a single network, or a particular network may include multiple networks. Further, while some devices are shown as communicating with a network, some such devices may be incorporated, in whole or in part, as a part of the network.
To the extent the aforementioned embodiments collect, store or employ personal information provided by individuals, it should be understood that such information shall be used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage and use of such information may be subject to consent of the individual to such activity, for example, through well known “opt-in” or “opt-out” processes as may be appropriate for the situation and type of information. Storage and use of personal information may be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.
Some implementations described herein may be described in conjunction with thresholds. The term “greater than” (or similar terms), as used herein to describe a relationship of a value to a threshold, may be used interchangeably with the term “greater than or equal to” (or similar terms). Similarly, the term “less than” (or similar terms), as used herein to describe a relationship of a value to a threshold, may be used interchangeably with the term “less than or equal to” (or similar terms), As used herein, “exceeding” a threshold (or similar terms) may be used interchangeably with “being greater than a threshold,” “being greater than or equal to a threshold,” “being less than a threshold,” “being less than or equal to a threshold,” or other similar terms, depending on the context in which the threshold is used,
No element, act, or instruction used in the present application should be construed as critical or essential unless explicitly described as such. An instance of the use of the term “and,” as used herein, does not necessarily preclude the interpretation that the phrase “and/or” was intended in that instance. Similarly, an instance of the use of the term “or,” as used herein, does not necessarily preclude the interpretation that the phrase “and/or” was intended in that instance. Also, as used herein, the article “a” is intended to include one or more items, and may be used interchangeably with the phrase “one or more.” Where only one item is intended, the terms “one,” “single,” “only,” or similar language is used. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
