The disclosed implementations relate generally to Heating, Ventilation, and Air Conditioning (HVAC) climate control systems for a fleet of vehicles. In particular, the disclosed implementations relate to systems and methods for remotely controlling climate control systems of a fleet of vehicles.
Climate control systems, such as Heating, Ventilation, and Air Conditioning (HVAC) systems are generally installed in vehicles (e.g., trucks) to maintain perishable goods at a desirable temperature, or to maintain the internal temperature for the vehicle occupants. The climate control systems may include mechanically driven compressor(s) and/or electrically driven compressor(s). The mechanically driven compressor(s) are typically powered by the vehicle engine when the vehicle engine is in operation. The electrical compressor(s) are typically powered by an auxiliary power source such as a battery pack. Thus, power can be supplied to the electrical compressor(s) even when the vehicle is off and in a “no idle state.” Because such climate control systems require power to be provided when the engine is off and in a “no idle state,” the auxiliary power source may be easily drained. Continuous use of the power from the auxiliary power source under these conditions may lead to excessive draining of the auxiliary power source, resulting in insufficient power to operate the HVAC system or in some instances even start the vehicle.
As a result, it is desirable to operate climate control systems efficiently to extend the capacity of the auxiliary power source(s) of the vehicle. One way to extend the capacity of the auxiliary power source(s) is by locally controlling the operational settings of the climate control system. The success of such a climate control system, however, is user dependent. For example, a driver of the vehicle may independently decide to operate the vehicle HVAC system inefficiently when the control of the climate control system is locally accessible. Moreover, HVAC systems are typically controlled for one vehicle at a time. Such systems fail to provide fleet operators with overall control of energy use of their fleet of vehicles. As such it would be desirable to provide a system that addresses these shortcomings.
The following provides a description of systems and methods that allow for remote climate control system (HVAC) management of a fleet of vehicles from a central management system by monitoring a broad range of specific parameters affecting functions of the climate control systems and controlling the climate control systems accordingly. Remotely managing a wide range of parameters for a fleet of vehicles provides a reliable method of identifying vehicles having potential climate control system performance inefficiencies based on a comparison of parameters measured and reported in real time with those from similarly situated vehicles operating efficiently. Furthermore, some implementations of the present invention allow for analysis and comparison of historical parameter data gathered over time for all vehicles in the fleet. Moreover, some implementations provide visual indicators signaling a degree of energy conservation or depletion based on performance efficiency or inefficiency of the climate control system of each vehicle to quickly identify and correct the inefficiencies.
Some implementations provide a method for simultaneously managing climate control systems of a fleet of vehicles. In some implementations, the method is implemented at a fleet server system that is remote from a fleet of vehicles having one or more processors and memory for storing one or more programs for execution by the one or more processors. The method includes receiving, from each vehicle of the fleet of vehicles, at least one parameter relaying information about a performance of a climate control system of the respective vehicle. Each climate control system includes an electrically driven compressor. The method also includes determining whether at least one performance inefficiency exists for the climate control system of at least one vehicle of the fleet of vehicles based on the at least one parameter received from the at least one vehicle. Further, the method includes determining an efficient operational setting that reduces the performance inefficiency of the climate control system of the at least one vehicle of the fleet of vehicles. Determining the efficient operational setting occurs when it is determined that performance inefficiency exists for the climate control system of the at least one vehicle. Furthermore, the method includes transmitting an operational setting instruction to the at least one vehicle to control the climate control system of the at least one vehicle.
Some implementations provide a method for displaying energy parameters or characteristics of a vehicle climate control system of at least one vehicle having a controller coupled to an electrically driven compressor that is powered by an auxiliary power source. This method includes receiving, at the controller, from a server remote from the at least one vehicle, at least one graphics instruction relating to a state of the at least one vehicle's auxiliary power source. In some implementations, the method further includes displaying a parameter associated with the climate control system of the at least one vehicle on a graphical user interface (GUI). In addition, a ring surrounding the parameter is displayed on the graphical user interface. The ring represents the state of the auxiliary power source and changes color, intensity, or size based on a degree of energy efficiency of the climate control system of the at least one vehicle.
Some implementations provide a system for simultaneously managing climate control systems of at least one vehicle of a fleet of vehicles. In some implementations, the system is remote from the fleet of vehicles and includes a receiver and a transmitter coupled to one or more processors, a memory coupled to the one or more processors in which the memory stores programs configured to be executed by the one or more processors, in which the one or more programs include instructions for receiving, from each vehicle of the fleet of vehicles, at least one parameter relaying information about a performance of a climate control system of the respective vehicle. Each climate control system includes an electrically driven compressor. The one or more programs also include instructions for determining whether a performance inefficiency exists for the climate control system of at least one vehicle of the fleet of vehicles based on the at least one parameter received from the at least one vehicle. Further, the one or more programs include instructions for determining an efficient operational setting that reduces the performance inefficiency of the climate control system of the at least one vehicle of the fleet of vehicles. Determining the efficient operational setting occurs when it is determined that performance inefficiency exists for the climate control system of the at least one vehicle. Furthermore, the one or more programs include instructions for transmitting an operational setting instruction to the at least one vehicle to control the climate control system of the at least one vehicle.
Some implementations provide a method for displaying energy parameters or characteristics of a climate control system of at least one vehicle of a fleet of vehicles. In some implementations, the method is implemented at a server system remote from a fleet of vehicles in which the server system includes a receiver and a transmitter coupled to one or more processors and a memory coupled to the one or more processors. The memory stores programs configured to be executed by the one or more processors. The one or more programs include instructions for receiving, from a controller coupled to an electrically driven compressor of the climate control system, information relating to a state of an auxiliary power source powering the electrically driven compressor. The one or more programs also include instructions for determining the degree of energy efficiency and a remaining runtime based on the state of the auxiliary power source. Further, the one or more programs include instructions for generating a graphics instruction based on the state of the auxiliary power source and for transmitting the graphics instruction to be displayed on a graphical user interface (GUI). For example, a parameter associated with the climate control system of the at least one vehicle is displayed on the graphical user interface. In addition, a ring surrounding the parameter is displayed on the graphical user interface. The ring represents the state of the auxiliary power source and changes color, intensity, or size based on a degree of energy efficiency of the climate control system of the at least one vehicle.
The systems and methods of the present invention(s) provide(s) advantages of having a central server simultaneously monitoring and controlling the climate control systems of a fleet of vehicles as this allows system wide limitations to be set for the fleet, to reliably identify and correct any outlier vehicles within the fleet (sometimes using operational settings of similarly situated vehicles in the fleet to correct the outlier vehicle operational settings), and to ensure the systems are performing as consistently and as efficiently as possible. The fleet operator or the user (i.e. the driver) in this case is also able to detect issues with any outliers before actual failure of any HVAC parts thereby reducing potential repair/replacement costs.
Performance inefficiencies can be identified and corrected through the central fleet server sending out a control signal with instructions in real time either to the vehicle to control the operational settings of the climate control system to the more efficient settings, or to a “smart” mobile device of a fleet operator to remotely change the settings based on some visual instruction generated on the mobile device as a result of the control instruction. For example, the fleet operator can execute unique commands in response to the control signal from the central server, including, but not limited to limiting a temperature set by the user of the vehicle, or lowering blower speed of a condenser fan, and the like. Furthermore, by virtue of controlling a fleet versus an individual vehicle, the fleet operator can monitor in real time fuel saved and other efficiency data of the entire fleet to easily compare this to company goals and make adjustments in real time in a continuous effort to achieve company goals.
The implementations disclosed herein are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings. Like reference numerals refer to corresponding parts throughout the drawings.
Attention is now directed to the figures, and in particular to
In some implementations, the remote device 103-1 communicates with one or both of the fleet server 104 and the vehicle 102-1. The remote device 103-1 and the functions and methods that it performs are discussed herein. Any description(s) of the remote device 103-1, or of the functions or methods performed by the remote device 103-1, apply equally to any or all instances of the remote devices 103-1 . . . 103-n. Exemplary remote devices include a desktop computer, a laptop computer, a tablet computer, a mobile electronic device, a server computer (or server computer system), a mobile phone, a digital media player, or any other appropriate electronic device. Exemplary devices include vehicles that contain such devices including cars, airplanes, trains and the like.
In some implementations, the fleet server 104 includes at least one processor 105, and is any of: a desktop computer, a laptop computer, a tablet computer, a server computer (or server system), a mobile electronic device, a mobile phone, a digital media player, or any other appropriate electronic device.
The network 110, and the functions and methods performed within the network environment, are discussed herein. Any description(s) of the vehicle 102-1, or of the functions or methods performed by the vehicle 102-1, apply equally to any or all instances of the vehicles 102-1 . . . 102-n. Exemplary vehicles include a truck, a lorry, a van, a train, a car or any other appropriate vehicle. Each vehicle includes the hardware and software described in relation to the figure below.
The network 110 includes any of a variety of networks, including a wide area network (WAN), local area networks (LAN), Personal Area Networks, metropolitan area networks, VPNs, local peer-to-peer, ad-hoc connections, wireless networks, wired networks, the Internet, or a combination of such networks.
The vehicle 102-1 is operated by a user (e.g., a driver). The user of the vehicle can control some aspects of the climate control system for his/her vehicle locally at the vehicle. In some implementations, the vehicle 102-1 includes a client application 112 that facilitates the transmission of one or more parameters to other devices, such as the fleet server 104 and/or remote devices 103-1 . . . 103-n. In some implementations, the client application 112 also facilitates receipt of information (e.g., operational settings of the climate control system and/or other instructions/alerts) from other devices, such as the fleet server 104 and/or remote devices 103-1 . . . 103-n or other servers including, but not limited to navigation server 107 and climate/weather condition server 108. In some implementations, the parameters transmitted from the vehicle 102-1 to other devices includes information associated with the operational settings of the vehicle 102-1 (e.g., ambient temperature, location coordinates, location information, oil pressure, tire pressures, battery voltage, engine calibration, and the number of diagnostic trouble codes, etc.). In some implementations, the parameters transmitted from the vehicle 102-1 to other devices includes information received by the vehicle 102-1 from other devices and/or peripherals, such as the navigation server 107, climate/weather conditions server 108, other vehicles, etc.
In some implementations, the vehicle 102-1 can also share the parameters from the vehicle 102-1 to other vehicles and/or entities, and/or share parameters between third-parties. For example, a user may be prompted, via a user interface of the vehicle 102-1 or the user's connected smart phone, to approve or deny a request for one third-party to share that user's parameters or operational settings with a third-party.
In some implementations, a desired operational setting of the climate control system of the vehicle 102-1 is determined based on measured or determined parameters or other related indications, such as time of day, device or application usage, location (e.g., from the navigation server 107 or otherwise), ambient light, ambient temperature, infrared energy emitted (e.g., from a thermal imaging device), connected devices/accessories, and the like. In some implementations, other devices in addition to, or instead of, the vehicle 102-1, remotely control or facilitate control of the operational settings of the climate control system of the vehicle 102-1. For example, the fleet server 104 communicates with the vehicle 102-1, through processor 105, to control the operational settings of the vehicle 102-1. As another example, peripheral devices (e.g., navigation server 107, climate/weather condition server 108, other vehicles 102-2 . . . 102-n, remote devices 103-1 . . . 103-n) provide signals to the vehicle 102-1 and/or the fleet server 104. These signals may be parameters or support information for determining desired operational settings, and can be used, alone or in combination with other signals (e.g., parameters from the vehicle 102-1), to determine desired operational settings for the climate control system of the vehicle 102-1.
In some implementations, the remote device 103-1 is associated with an entity that receives, stores, uses, or otherwise accesses information associated with the operational settings of the fleet of vehicles 102-1 . . . 102-n. For example, the remote device may be a laptop or a cell phone of an interested third party, such as an operator of the fleet of vehicles (fleet operator).
In some implementations, the fleet server 104 is configured to communicate, via the network 110 and/or other communication means, with multiple, i.e., a fleet of vehicles 102-1 . . . 102-n and multiple remote devices 103-1 . . . 103-n to provide information associated with the operational settings of the climate control systems of the fleet of vehicles (e.g., 102-n). In some implementations, the fleet server 104 includes and/or communicates with a database 106. As described herein, the database 106 stores information associated with the operational settings of the fleet of vehicles.
The fleet server 104 typically includes one or more processors or CPUs 105, a user interface 206, at least one network communications interface 212 (wired and/or wireless), memory 214, and at least one communication bus 202 for interconnecting these components. Each communication bus 202 includes circuitry (sometimes called a chipset) that interconnects and controls communications between system components. In some implementations, the user interface 206 includes a display 208 and input device(s) 210 (e.g., keyboard, mouse, touchscreen, keypads, etc.).
Memory 214 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 214 may optionally include one or more storage devices remotely located from the CPU(s) 204. Memory 214, or alternately the non-volatile memory device(s) within memory 214, includes a non-transitory computer readable storage medium. In some implementations, memory 214 or the computer readable storage medium of memory 214 stores the following programs, modules and data structures, or a subset thereof:
In some implementations, the vehicle 102-1 is any of a truck, a lorry, a van, a train, a car or any other appropriate vehicle.
The vehicle 102-1 typically includes a computing device including one or more controllers, processors or CPUs 304, a user interface 306, at least one network communications interface 312 (wired and/or wireless), one or more sensors 314, an auxiliary power source load tester/monitor 315, a global positioning system 316, a thermal imaging device 317, memory 318, and at least one communication bus 302 for interconnecting these components. Each communication bus 302 typically includes circuitry (sometimes called a chipset) that interconnects and controls communications between system components. In some implementations, the user interface 306 includes a display 308 and input device(s) 310 (e.g., keyboard, mouse, touchscreen, keypads, etc.).
The sensors 314 are any devices capable of measuring internal, external, ambient temperatures relative to the cab of the vehicle, fan speeds of the climate control system of the vehicle, internal and external pressures relative to the cab of the vehicle, and the like.
The auxiliary power source load tester/monitor 315 is any device capable of measuring and/or monitoring a voltage, current, and/or power of an auxiliary power source used to power the climate control (e.g. HVAC) system of the at least one vehicle 102-1, e.g. solar power, a waste heat recovery (WHR) system, or a battery pack driving a compressor of the climate control (HVAC) system.
The global positioning system 316 includes devices and/or components for determining the location of the vehicle 102-1, including but not limited to global positioning system (GPS) sensors, radio receivers (e.g., for cell-tower triangulation, WiFi-based positioning, etc.), inertial sensors, and accelerometers. In some implementations, the client device 102-1 does not include (or does not rely on) a separate positioning system 316. For example, where the vehicle 102-1 is connected to the Internet (e.g., via the network communications interface 212), the location of the vehicle 102-1 can be determined using IP address geolocation techniques. Other techniques for determining the location of the vehicle 102-1, including those that rely on a built-in or connected positioning system and those that do not, are also contemplated. In some implementations, location is determined by the network being connected to (e.g., in an airplane, train, building or cell phone tower) other sensor information which might identify location.
The thermal imaging device and infrared sensor 317 includes devices and/or components for capturing infrared radiation emitted from objects. In some implementations, the thermal imaging device detects infrared radiation emitted and is capable of identifying warmer zones of a vehicle where a person is located.
Memory 318 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 318 may optionally include one or more storage devices remotely located from the CPU(s) 304 (e.g., a network-connected storage device or service, such as a “cloud” based storage service). Memory 318, or alternately the non-volatile memory device(s) within memory 318, includes a non-transitory computer readable storage medium. In some implementations, memory 218 or the computer readable storage medium of memory 218 stores the following programs, modules and data structures, or a subset thereof:
In some implementations, the client vehicle 102-1 includes a subset of the components and modules shown in
In some implementations, any or all of the communications between devices described with respect to the figures, are secured and/or encrypted using any appropriate security and/or encryption techniques, including but not limited to Hypertext Transport Protocol Secure (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), Secure Shell (SSH), Internet Protocol Security (IPSec), public key encryption, and the like (including any appropriate yet to be developed security and/or encryption method).
In some implementations, the method for remotely managing climate control systems of at least one vehicle of a fleet of vehicles are implemented at the fleet server that is remote from the at least one vehicle. In some implementations, each climate control system includes an electrically driven compressor driven by an auxiliary power source, such as an auxiliary battery pack separate from the vehicle's regular battery.
In some implementations, as illustrated in
In some implementations, the method for remotely managing climate control systems of the at least one vehicle of a fleet of vehicles includes determining, by the processor 105, whether performance inefficiencies exist for the climate control system of the at least one vehicle of the fleet of vehicles, as shown in step 420. The determination is based on at least one parameter received from the at least one vehicle 102-1 and/or at least one external parameter received from at least one other server 107, 108.
In some implementations, as illustrated in
In other implementations, the processor 105 compares the parameter(s) received from the vehicle(s), e.g. TI and TSP, to parameter(s) of a similarly situated vehicle. In some implementations, the parameters of the similarly situated vehicle indicate an efficiently operating climate control system and are therefore used as reference parameters for determining desirable operational settings of other climate control systems of other vehicles. A similarly situated vehicle is typically one that is subject to similar conditions as another vehicle. For example, similarly situated vehicles of the fleet of vehicles may operate under same or similar conditions, such as same or similar temperatures, travelling route, location, weather conditions, terrain and/or traffic conditions. For example, received parameters corresponding to a reference vehicle with a climate control system with desirable operational setting may set the current operational settings for vehicles subjected to similar conditions (e.g., weather conditions).
Accordingly, the fleet server 104 determines desirable operational setting(s) i.e., efficient settings for the parameter(s) received from the vehicle(s).
In some implementations, the fleet server 104 transmits instructions of the desirable operational setting(s) (e.g., temperature settings) to the one or more vehicles to inform the user of the vehicle(s) of the desirable operational setting(s) (e.g., efficient operation settings), as shown by step 460. That is, the operational settings of the climate control system of the at least one vehicle can be controlled to improve the duration of operation of the auxiliary power supply for supporting the climate control system, especially when the vehicle's engine is turned off.
The received parameter(s) and the operational settings determined or selected based on the received parameter(s) are stored in the memory 214 of the fleet server 104 for future use. The stored parameters and corresponding operational settings may be used as reference values for determining efficient operational settings for other vehicles having an inefficiently operating climate control system.
In some implementations, the fleet server 104 receives other parameters from other devices independent of the fleet of vehicles. For example, the fleet server receives external parameters from the navigation server 107 and the climate conditions server 108. The external parameters may include traffic conditions and/or weather condition parameters along a route of the vehicle(s). The processor 105 of the fleet server 104 determines the desirable operational settings of the at least one vehicle based on the external parameters along with the parameters received from the at least one vehicle. For example, the climate conditions server 108 provides parameters relating to climate conditions along the route of the vehicle. The processor 105 of the fleet server 104 processes the parameters and determines the desirable operational settings of the at least one vehicle 102-1 in order to account for changes in weather conditions along the route. In this way, the fleet server 104 modifies the settings of the climate control system in order to ensure maximum life of the auxiliary power source.
For example, an outside temperature (98° F.) may be received from a climate conditions server 108 instead of the vehicle 102-1 while the set point temperature (65° F.) is received from the vehicle. In this case, the desirable operational setting is determined for set point temperature when the outside temperature is 98° F. The determination of the desirable, i.e., efficient operational settings when a performance inefficiency exists is based on the external parameters and the parameters received from the vehicle. As noted, the reference parameters are stored in database or the memory 212 of the fleet server 104.
The following are exemplary implementations for various parameters received by the fleet server 104 from the vehicle(s). The implementations are discussed with reference to steps 402-414 of
In some implementations, the predetermined parameter reference value(s) or ranges of reference parameter values may be based on historical performance data of each vehicle of the fleet of vehicles stored in the memory 214. For example, historical performance data may include reference parameter values of efficiently performing climate control systems under various external conditions, parameter values of similarly situated reference vehicles with efficiently performing climate control systems, reference parameter values of the fleet of vehicles based on company overall efficiency data and company target data with respect to the one or more parameters.
In some implementations, as shown in step 404, when the parameter received from the vehicle is associated with ambient weather conditions, one of the sensors 314 of the vehicle senses an ambient temperature, TAMB surrounding the vehicle and transmits the parameter to the fleet server 104. The fleet server 104 receives the parameter and then compares TAMB to a reference ambient control parameter TAMB(REF) to determine whether the climate control system of the vehicle is operating inefficiently based on the difference between TAMB and TAMB(REF) similar to the implementation discussed with respect to the difference between ΔT and ΔTREF described above.
Performance inefficiencies associated with the ambient weather conditions parameter may indicate that the vehicle climate control system is not performing efficiently with respect to weather conditions surrounding the vehicle. For example, the climate control system may be heating an inside of a vehicle even though the ambient temperature surrounding the vehicle is already very high.
In some implementations, as shown in step 406, when the parameters received from the vehicle are obtained from a thermal image profile of an occupant of the vehicle, the parameters may include infrared energy emitted, EINF, by a user and captured by infrared sensors and/or thermal imaging devices 317 of the vehicle. Parameter(s) for infrared energy emitted indicate portions of the vehicle where a user may be located due to higher radiation emissions sensed based on body heat/temperature of a user or other occupants in comparison to unoccupied spaces of the vehicle. The fleet server 104 compares the infrared energy emitted, EINF to reference parameter value or a range of parameter values for infrared energy emitted, EINF(REF) In some implementations, the climate control system of the vehicle with these parameters is deemed to be operating efficiently when a difference between EINF and EINF(REF) is approximately zero or is within a predetermined threshold range. However, if a difference is not approximately zero or is outside the threshold range, then it is determined that the climate control system of the vehicle is operating inefficiently. For example, the server 104 may determine that a predetermined reference value or range of reference values for infrared energy emitted indicate an occupied space of the vehicle. If it is determined that the HVAC system is heating or cooling a space in the vehicle where the infrared energy emitted does not fall within the predetermined range of values or is not approximately equal to the predetermined reference value, the server determines that the HVAC system is heating or cooling an unoccupied space in the vehicle and therefore a performance inefficiency exists in the climate control system.
Performance inefficiencies with respect to the infrared energy emitted parameter EINF could indicate that climate control system is not effectively cooling or heating only occupied spaces in the vehicle, but instead wasting energy heating or cooling unoccupied spaces.
In some implementations, as shown in step 408, when the parameters received from the vehicle are associated with a loading of a condenser, the parameters typically include refrigerant pressure, refrigerant temperature, condenser temperature and an ambient temperature surrounding the condenser, to modulate condenser fan speed to save power when necessary. The fleet server 104 receives these parameters associated with a loading of the condenser from the vehicle and receives or identifies corresponding reference parameters from the database 106 as described previously for other reference parameters. The fleet server 104 compares the condenser loading parameters with corresponding condenser loading reference parameters, in a similar manner as described above with respect to other parameters. The fleet server 104 then determines whether performance inefficiencies exist in the climate control system of the vehicle based on the comparison of received and reference parameters and initiates the process to facilitate mitigation of the inefficiencies as described in further detail below.
In some implementations, the performance inefficiencies with respect to condenser loading may indicate that a condenser fan speed is too high (thus draining too much power from an auxiliary power source powering the climate control system) or too slow (thus providing insufficient cooling) for climate control system operations.
In some implementations, as shown in step 410, when the parameters received from the vehicle are associated with air conditioning operating conditions, the received parameters typically include air conditioning operating pressures and/or temperatures. Thus, the server 104 receives these parameters associated with air conditioning operating conditions from the vehicle and receives or identifies corresponding reference parameters (e.g., predetermined reference parameters or real time reference parameters) from the database 106 or from other sources in a similar manner as described previously for other reference parameters. The fleet server 104 compares the air conditioning operating pressures and/or temperatures with the corresponding predetermined air conditioning reference parameter(s), in a similar manner as described above with respect to other parameters. The fleet server 104 then determines whether performance inefficiencies exists in the climate control system of the vehicle based on the comparison and initiates the process to facilitate mitigation of the performance inefficiencies as described in further detail below.
Performance inefficiencies with respect to air conditioning operating pressures and/or temperatures may indicate that the air conditioning system is draining too much power or cooling insufficiently, which prevents the climate control system from functioning efficiently.
In some implementations, as shown in step 412, when the parameter(s) are associated with available power or voltage of an auxiliary battery coupled to an electrically powered compressor of the climate control system, the parameters typically include an energy rate consumption parameter. The fleet server 104 receives the parameter(s) associated with available power or voltage from the auxiliary power source load tester/voltage monitor 315 of the vehicle 102-1 and receives corresponding reference parameters from the database 106 in a similar manner as described previously for other reference parameters. The fleet server 104 compares the at least one parameter associated with available power or voltage from the vehicle with corresponding predetermined reference parameter(s), in a similar manner as described above with respect to other parameters. The fleet server 104 then determines whether performance inefficiencies exist in the climate control system of the vehicle based on the comparison and initiates the process to facilitate mitigation of the inefficiencies as described in further detail below.
In some implementations, as shown in step 414, when the parameters are associated with one or more zones of the vehicle, the parameters may include location coordinates corresponding to where in the vehicle a user or occupant may be located, measured e.g., by one of the sensors 314, i.e. an occupancy sensor, in relation to actual zones being cooled or heated. The zoning parameters facilitate determining whether the climate control system is efficiently cooling or heating the occupied spaces. The fleet server 104 receives these parameters associated with zoning from the vehicle and receives or identifies corresponding reference parameters from the database 106 (as described previously for other parameters) indicating coordinates of zones that should be cooled or heated given the parameters received from the vehicle. The fleet server 104 compares the zoning parameters with corresponding zoning reference parameter(s), as described above with respect to other parameters. The fleet server 104 then determines whether performance inefficiencies exist in the climate control system of the vehicle and in a similar manner as described for other parameters and initiates the process to facilitate mitigation of the inefficiencies as described for other parameters. Performance inefficiencies in the zoning parameters indicate that the vehicle may be wasting energy cooling or heating unoccupied zones of the vehicle.
In general, in the methods illustrated in
If it is determined, at step 423, that parameters(s) received from the at least one vehicle 102-1 and/or parameter(s) received from the at least one other server 107, 108 are approximately equal to the predetermined reference parameter value(s) or within the predetermined range of reference parameter values, then the climate control system is performing efficiently with respect to the vehicle parameter(s) and/or the external parameter(s) from the at least one other server 107, 108, and the parameter(s) are stored in the database 106 for future use or reference as shown by step 425. Otherwise, it is determined that the climate control system is performing inefficiently, as shown by step 427. For example, at step 427, the processor 105 of the fleet server 104 determines that a performance inefficiency exists in the climate control system of the at least one vehicle 102-1 when the parameter(s) received from the at least one vehicle 102-1 and/or parameter(s) received from the at least one other server/source 107, 108 are not approximately equal to the predetermined reference parameter value(s) or not within the predetermined range of reference parameter values.
In some implementations, the server 104 determines that performance inefficiencies exist in the climate control system(s) when the remaining power of the auxiliary power source(s) is less than that required to power the climate control system(s) to a final destination based on a processing of the parameters received from the at least one vehicle 102-1 at steps 402-414 along with the external parameters received from the other servers or sources 107, 108 at steps 416-418.
As described above, in some implementations, the fleet server 104 optionally receives at least one external parameter from the at least one other server or source remote from the fleet of vehicles, as shown by steps 415-418. The at least one external parameter received from the at least one other server 107, 108 or source is selected from the group consisting of a global positioning system (GPS), a weather prediction system, a map provider, a road and traffic conditions system, and a combination of any of the aforementioned.
At step 416, the fleet server 104 receives at least one external parameter relating to predicted weather conditions along a route of the vehicle(s) which may affect the parameters received from the vehicle(s) and the performance of the climate control system(s) of the vehicle. The fleet server 104 processes the external parameter(s) along with all or any of the parameter(s) received from the vehicle(s) at steps 402-414 to determine whether a performance inefficiency exists for the climate control system of the vehicle(s). For example, the processor 105 of the fleet server 104 processes external parameters associated with a route having an extremely difficult terrain and/or heavy traffic conditions along with a parameter(s) received from the vehicle, e.g. TSP, and determines whether performance inefficiencies exist for the climate control system(s) based on remaining power of the auxiliary power source(s) powering the climate control system(s). Performance inefficiencies exist for example, when the remaining power of the auxiliary power source(s) is less than that required to power the climate control system(s) to a final destination based on the parameters received from the vehicle along with the external parameters.
In another example, the fleet server 104 instead processes at least one of the parameters received from the vehicle associated with loading of the condenser(s) described above along with the external parameters from the other servers or sources 107, 108 described above and determines whether performance inefficiencies exist for the climate control system(s) when the remaining power of the auxiliary power source(s) is less than that required to power the climate control system(s) to a final destination based on the parameters received from the vehicle 102-1 along with the external parameters, as described above.
In some implementations, the fleet server 104 initiates a fault detection procedure when a performance inefficiency exists in the climate control system of the at least one vehicle 102-1 of the fleet of vehicles, as shown by steps 429, 431, 433 and 435 of
In other implementations, after a predetermined period of time or after determining that the climate control system of the at least one vehicle has been operating efficiently, the fleet server 104 transmits an override signal to the at least one vehicle to restore the user's ability to adjust the operational settings of the climate control system.
The fleet server 104, at step 431, also stores the faulty information and/or corresponding parameters indicating the fault in the database 106 for future inefficiency/failure prediction. Further, procedures are initiated by the fleet server to facilitate replacement or repair of the faulty part, as described in
In other implementations as illustrated in
The aforementioned comparison is performed to determine whether the difference in parameter values of the at least one vehicle and the at least one similarly situated reference vehicle is within a predetermined threshold value. For example, it is determined that the climate control system of the at least one vehicle is performing efficiently when the difference is less than or equal to the predetermined threshold value, as shown in step 425. The predetermined threshold value is based on, but not limited to, historical experimental performance data, company overall efficiency data, and company target data. Otherwise, it is determined that the climate control system of the similarly situated vehicle is inefficient when the difference is greater than the predetermined threshold value, as shown in step 427. Similar to the implementation of
The implementations of the present invention(s) provide(s) the advantage that by monitoring performance parameters of a climate control system of an individual vehicle of an entire fleet of vehicles, it is possible to identify outliers, i.e. individual vehicles in the fleet performing differently than similarly situated vehicles in the fleet and identify performance inefficiencies on this basis. In this sense, a fleet operator monitoring the conditions and performance efficiencies of multiple vehicles in a fleet of vehicles, may quickly and reliably identify issues with the outliers and be able to correct or adjust the operational settings of the outliers to ensure maximum efficiency within the fleet. The fleet operator or the user (i.e. the driver) in this case is also able to detect issues with any outliers before actual failure of any HVAC parts thereby reducing potential repair/replacement costs.
In some implementations, upon determination that a performance inefficiency exist in the climate control (e.g., HVAC) system of the at least one vehicle 102-1 at step 427, the fleet server 104 determines that the inefficiencies are based on faulty software or a faulty part that needs replacement or repair at step 429. The fleet server 104 then initiates a replacement or repair procedure and/or notifies a user of the vehicle or an interested third party, e.g., the fleet operator of the faulty part or application of the vehicle. For example, the fleet server 104 transmits a signal to remote device(s), e.g. 103-1 informing the fleet operator that a faulty part exists that is interfering with the performance efficiency of the climate control system(s) of the vehicle(s). As illustrated in
As further illustrated in
As illustrated in
At step 456, the remote fleet server 104 determines a current location of at least one of the vehicles 102-1 based on the at least one location parameter received from each of the vehicles of the fleet of vehicles or from at least one of the other servers/sources at step 418. The location parameter may include location coordinates such as latitude and longitude indicating the location of at least one vehicle. At step 458, the fleet server determines a route of the at least one vehicle based on the at least one received route parameters from the GPS 316 of the at least one vehicle. The route parameter(s) are based on origination coordinates, destination coordinates, and route preferences (e.g. fastest time, shortest distance, avoidance preferences (e.g., avoid freeways). Alternatively, the route of the at least one vehicle is determined by the at least one other server/source at step 418 (e.g., navigation server 107) and sent to the fleet server 104.
At step 459, the fleet server processes the current HVAC conditions, energy use rate of auxiliary power source for the HVAC system, and/or the current location and route, and determines an efficient performance operational setting based on the determined current HVAC conditions in conjunction with the energy use rate, and/or the current location, and current route.
The efficient performance operational setting is based on, but not limited to the aforementioned parameters, and in some implementations is based on at least one other parameter or factor.
Alternatively, the fleet server 104 determines an efficient performance operational setting for an individual vehicle based on overall performance efficiency target rates of the fleet set by the operator of the fleet, or based on operational settings of efficiently performing vehicles in the fleet, adjusted by a factor to compensate for varying geographic and climate conditions.
Therefore, the present invention offers the advantage of positive reinforcement controls, i.e., the fleet server 104 sends a control signal that notifies the user(s) or the operator of the fleet of vehicles what the energy efficient operational settings will be for each climate control system based on the received parameters under the given conditions. In some implementations, the server 104 does not mandate the efficient operational settings but helps inform the user of the optimum settings for any of the settings described above, i.e. temperature set by a user in relation to ambient temperature in the vehicle and/or outside temperature surrounding the vehicle, ambient climate conditions, and all other parameters previously described.
Referring to
In some implementations, as illustrated in
At step 550, the parameter associated with the climate control system of the at least one vehicle is displayed, and at step 560, a ring surrounding the parameter is displayed at the GUI, in which the ring represents a state of the auxiliary power source. In some implementations, the ring changes color, intensity, or size based on a degree of energy efficiency of the climate control system of the at least one vehicle.
In some implementations, the parameter associated with the climate control system of the at least one vehicle and which is displayed inside the ring is selected from a group including a percentage efficiency e.g., 808 at which the climate control system for the at least one vehicle of the fleet of vehicles operates, ambient conditions in the vehicle, e.g., 822, remaining power of the auxiliary power source, remaining runtime, e.g., 826, and system health of the climate control system for the at least one vehicle.
The energy efficiency information represents current and improved operational settings of the climate control systems. Displaying the energy efficiency information on the GUI allows the user, (e.g. the driver) or the fleet operator to be able to view the current operational settings of the climate control system of a corresponding vehicle. When informed through the GUI, the fleet operator and/or the user can also adjust operational settings of the climate control system. The graphics instruction may be displayed on the GUI of the vehicle, e.g. dashboard display or the GUI of a mobile device monitored by the fleet operator.
In some implementations, as illustrated in
The systems and methods of the present invention provide advantages of having a central server simultaneously monitoring and controlling the climate control systems of a fleet of vehicles as this allows system wide limitations to be set for the fleet to reliably identify and correct any outlier vehicles within the fleet (sometimes using operational settings of similarly situated vehicles in the fleet to correct the outlier vehicle operational settings) and to ensure the systems are performing as consistently and as efficiently as possible. Performance inefficiencies can be identified and corrected through the central fleet server sending out a control signal with instructions in real time either to the vehicle to control the operational settings of the climate control system to the more efficient settings, or to a “smart” mobile device of a fleet operator to remotely change the settings based on some visual instruction generated on the mobile device as a result of the control instruction. For example, the fleet operator can execute unique commands in response to the control signal from the central server, including, but not limited to limiting a temperature set point of the vehicle, or lowering blower speed of a condenser fan, and the like. Furthermore, by virtue of controlling a fleet versus an individual vehicle, the fleet operator can monitor in real time fuel saved and other efficiency data of the entire fleet to easily compare this to company goals and make adjustments in real time in a continuous effort to achieve company goals.
In some implementations of the present invention, the server institutes advanced control aspects, including but not limited to run time calculators, eco modes, addition of badges, and positive reinforcement as described above. Runtime calculators are displayed on a GUI as described above and operate as a visual indicator to a user of runtime until final destination. The addition of badges and gamification act in the context of the invention as an incentive for users to operate the climate control systems of the vehicles in the fleet as efficiently as possible. Through gamification and different levels achievable depending on the level of efficient climate control system operation of each user, competition is created among the users (i.e. drivers) to achieve certain levels and reap rewards for their efforts in maintaining efficient climate control conditions in their respective vehicles.
In some implementations, the server runs an algorithm which determines a level of efficiency of each vehicle and assigns a certain weight to it. The weight assigned may correspond to the amount of energy savings rewards that a user unlocks for use at a time of their choosing, i.e. the user can use the energy savings rewards to indulge and run the system inefficiently if he/she so chooses expending an energy amount up to the energy savings rewards amount. For example, if the user desires a temperature inside the vehicle to be cooler than a current efficient setting, the user having the energy savings reward can override the efficient setting and run the climate conditioning system at a less efficient setting using up more energy to cool the vehicle interior to his/her desired level. The user may in this sense run the climate control system of the vehicle inefficiently for his/her benefit until his/her energy saving rewards amount is expended.
A description of badge examples and the various levels attainable by the users through gamification is provided below according to teachings of the present invention.
Levels:
In some implementations, the levels can be shared through social media, and used for promotional purposes.
Badges:
Badge Examples:
The Scheduler: User uses the climate control system around the same time every day for a predetermined period, e.g. 10 days, unlocks a “NITE” no idle system alarm clock function.
Eco Monster: User runs “NITE” unit under optimum settings for a certain amount of hours, unlocks run time calculator. Available for Immediate purchase
5 Day Stretch: User uses “NITE” system 5 days in a row. Unlocks screen customizations within app.
Weekend Warrior: User uses no idle system over the weekend. Sends user the opportunity to purchase a battery charger at reduced price.
Full Power: User has batteries fully charged before NITE system use 85% over last 30 days. Unlocks ability to purchase an Extended Run Time (XRT) function, i.e. function allowing the climate control system to dip below the cutoff voltage on the auxiliary batteries or the cutoff on the starting batteries to allow the system to run longer. The XRT function temporarily lowers the Low Voltage Disconnect (LVD), i.e. the voltage at which the system turns off to protect the batteries.
Other badge examples which can be earned include, but are not limited to the night watchmen 1002, day breaker 1004 and an energy savings bank, porkins 1006.
As illustrated in
The methods illustrated in
Plural instances may be provided for components, operations, or structures described herein as a single instance. Finally, boundaries between various components, operations, and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within the scope of the implementation(s). In general, structures and functionality presented as separate components in the example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the implementation(s).
It will also be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, which changing the meaning of the description, so long as all occurrences of the “first contact” are renamed consistently and all occurrences of the second contact are renamed consistently. The first contact and the second contact are both contacts, but they are not the same contact.
The terminology used herein is for the purpose of describing particular implementations only and is not intended to be limiting of the claims. As used in the description of the implementations and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in accordance with a determination” or “in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase “if it is determined (that a stated condition precedent is true)” or “if (a stated condition precedent is true)” or “when (a stated condition precedent is true)” may be construed to mean “upon determining” or “in response to determining” or “in accordance with a determination” or “upon detecting” or “in response to detecting” that the stated condition precedent is true, depending on the context.
The foregoing description included example systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative implementations. For purposes of explanation, numerous specific details were set forth in order to provide an understanding of various implementations of the inventive subject matter. It will be evident, however, to those skilled in the art that implementations of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures and techniques have not been shown in detail.
The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen and described in order to best explain the principles and their practical applications, to thereby enable others skilled in the art to best utilize the implementations and various implementations with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. patent application Ser. No. 16/546,141, filed Aug. 20, 2019, which is a continuation of U.S. patent application Ser. No. 15/722,860, filed Oct. 2, 2017, now U.S. Pat. No. 10,427,496, which is a continuation of U.S. patent application Ser. No. 15/064,552, filed Mar. 8, 2016, now U.S. Pat. No. 9,783,024, which claims priority to U.S. Provisional Patent Application No. 62/130,399, filed Mar. 9, 2015, each of which is herein incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
2722050 | Shank | Nov 1955 | A |
2789234 | Lambert et al. | Jun 1956 | A |
3176502 | Cizek et al. | Apr 1965 | A |
3225819 | Stevens | Dec 1965 | A |
3360958 | Miner | Jan 1968 | A |
3590910 | Lorenz | Jul 1971 | A |
3627030 | Lorenz | Dec 1971 | A |
3807087 | Staats | Apr 1974 | A |
3844130 | Wahnish | Oct 1974 | A |
3880224 | Weil | Apr 1975 | A |
3885398 | Dawkins | May 1975 | A |
3938349 | Ueno | Feb 1976 | A |
3948060 | Gaspard | Apr 1976 | A |
3995443 | Iversen | Dec 1976 | A |
4015182 | Erdman | Mar 1977 | A |
4034801 | Bermstein | Jul 1977 | A |
4071080 | Bridgers | Jan 1978 | A |
4217764 | Armbruster | Aug 1980 | A |
4266405 | Trask | May 1981 | A |
4271677 | Harr | Jun 1981 | A |
4280330 | Harris et al. | Jul 1981 | A |
4324286 | Brett | Apr 1982 | A |
4359875 | Ohtani | Nov 1982 | A |
4383802 | Gianni et al. | May 1983 | A |
4391321 | Thunberg | Jul 1983 | A |
4412425 | Fukami et al. | Nov 1983 | A |
4448157 | Eckstein et al. | May 1984 | A |
4459519 | Erdman | Jul 1984 | A |
4577679 | Hibshman | Mar 1986 | A |
4604036 | Sutou et al. | Aug 1986 | A |
4617472 | Slavik | Oct 1986 | A |
4641502 | Aldrich et al. | Feb 1987 | A |
4658593 | Stenvinkel | Apr 1987 | A |
4667480 | Bessler | May 1987 | A |
4694798 | Kato et al. | Sep 1987 | A |
4748825 | King | Jun 1988 | A |
4825663 | Nijar et al. | May 1989 | A |
4841733 | Dussault et al. | Jun 1989 | A |
4856078 | Konopka | Aug 1989 | A |
4893479 | Gillett et al. | Jan 1990 | A |
4897798 | Cler | Jan 1990 | A |
4905478 | Matsuda et al. | Mar 1990 | A |
4945977 | D'Agaro | Aug 1990 | A |
4947657 | Kalmbach | Aug 1990 | A |
4952283 | Besik | Aug 1990 | A |
4982576 | Proctor et al. | Jan 1991 | A |
5025634 | Dressier | Jun 1991 | A |
5046327 | Walker | Sep 1991 | A |
5067652 | Enander | Nov 1991 | A |
5095308 | Hewitt | Mar 1992 | A |
5125236 | Clancey et al. | Jun 1992 | A |
5170639 | Datta | Dec 1992 | A |
5205781 | Kanno et al. | Apr 1993 | A |
5230719 | Berner et al. | Jul 1993 | A |
5269153 | Cawley | Dec 1993 | A |
5275012 | Dage et al. | Jan 1994 | A |
5307645 | Pannell | May 1994 | A |
5316074 | Isaji et al. | May 1994 | A |
5324229 | Weisbecker | Jun 1994 | A |
5327997 | Nash, Jr. et al. | Jul 1994 | A |
5333678 | Mellum et al. | Aug 1994 | A |
5361593 | Pauvergne | Nov 1994 | A |
5376866 | Erdman | Dec 1994 | A |
5396779 | Voss | Mar 1995 | A |
5402844 | Elluin | Apr 1995 | A |
5404730 | Westermeyer | Apr 1995 | A |
5426953 | Meckler | Jun 1995 | A |
5465589 | Bender et al. | Nov 1995 | A |
5497941 | Numazawa et al. | Mar 1996 | A |
5501267 | Iritani et al. | Mar 1996 | A |
5502365 | Nanbu et al. | Mar 1996 | A |
5524442 | Bergmen, Jr. et al. | Jun 1996 | A |
5528901 | Willis | Jun 1996 | A |
5537003 | Bechtel | Jul 1996 | A |
5562538 | Suyama | Oct 1996 | A |
5586613 | Ehsani | Dec 1996 | A |
5641016 | Isaji et al. | Jun 1997 | A |
5647534 | Kelz et al. | Jul 1997 | A |
5657638 | Erdman et al. | Aug 1997 | A |
5682757 | Peterson | Nov 1997 | A |
5720181 | Karl et al. | Feb 1998 | A |
5727396 | Boyd | Mar 1998 | A |
5752391 | Ozaki et al. | May 1998 | A |
5761918 | Jackson et al. | Jun 1998 | A |
5775415 | Yoshini et al. | Jul 1998 | A |
5782610 | Ikeda | Jul 1998 | A |
5819549 | Sherwood | Oct 1998 | A |
5896750 | Karl | Apr 1999 | A |
5898995 | Ghodbane | May 1999 | A |
5899081 | Evans et al. | May 1999 | A |
5901572 | Peiffer et al. | May 1999 | A |
5901780 | Zeigler et al. | May 1999 | A |
5921092 | Behr et al. | Jul 1999 | A |
5934089 | Magakawa et al. | Aug 1999 | A |
5982643 | Phlipot | Nov 1999 | A |
5996363 | Kurachi et al. | Dec 1999 | A |
6016662 | Tanaka et al. | Jan 2000 | A |
6021043 | Horng | Feb 2000 | A |
6028406 | Birk | Feb 2000 | A |
6029465 | Bascobert | Feb 2000 | A |
6038877 | Peiffer et al. | Mar 2000 | A |
6038879 | Turcotte | Mar 2000 | A |
6059016 | Rafalovich et al. | May 2000 | A |
6072261 | Lin | Jun 2000 | A |
6073456 | Kawai et al. | Jun 2000 | A |
6111731 | Cepynsky | Aug 2000 | A |
6112535 | Hollenbeck | Sep 2000 | A |
6125642 | Seener et al. | Oct 2000 | A |
6134901 | Harvest et al. | Oct 2000 | A |
6152217 | Ito et al. | Nov 2000 | A |
6185959 | Zajac | Feb 2001 | B1 |
6193475 | Rozek | Feb 2001 | B1 |
6205795 | Backman et al. | Mar 2001 | B1 |
6205802 | Drucker et al. | Mar 2001 | B1 |
6209333 | Bascobert | Apr 2001 | B1 |
6209622 | Lagace et al. | Apr 2001 | B1 |
6213867 | Yazici | Apr 2001 | B1 |
6230507 | Ban et al. | May 2001 | B1 |
6232687 | Hollenbeck et al. | May 2001 | B1 |
6253563 | Ewert et al. | Jul 2001 | B1 |
6265692 | Umebayahi et al. | Jul 2001 | B1 |
6276161 | Peiffer et al. | Aug 2001 | B1 |
6282919 | Rockenfeller | Sep 2001 | B1 |
6318103 | Rieger et al. | Nov 2001 | B1 |
6351957 | Hara | Mar 2002 | B2 |
6405793 | Ghodbane et al. | Jun 2002 | B1 |
6411059 | Frugier et al. | Jun 2002 | B2 |
6453678 | Sundhar | Sep 2002 | B1 |
6457324 | Zeigler et al. | Oct 2002 | B2 |
6467279 | Backman et al. | Oct 2002 | B1 |
6474081 | Feuerecker | Nov 2002 | B1 |
6490876 | Derryberry et al. | Dec 2002 | B2 |
6530426 | Kishita et al. | Mar 2003 | B1 |
6543245 | Waldschmidt | Apr 2003 | B1 |
6571566 | Temple et al. | Jun 2003 | B1 |
6575228 | Ragland et al. | Jun 2003 | B1 |
6626003 | Kortüm et al. | Sep 2003 | B1 |
6651448 | Ross | Nov 2003 | B2 |
6662592 | Ross | Dec 2003 | B2 |
6675601 | Ebara | Jan 2004 | B2 |
6684863 | Dixon et al. | Feb 2004 | B2 |
6725134 | Dillen et al. | Apr 2004 | B2 |
6745585 | Kelm et al. | Jun 2004 | B2 |
6748750 | Choi | Jun 2004 | B2 |
6758049 | Adachi et al. | Jul 2004 | B2 |
6889762 | Zeigler et al. | May 2005 | B2 |
6932148 | Brummett et al. | Aug 2005 | B1 |
6939114 | Iwanami et al. | Sep 2005 | B2 |
6965818 | Koenig et al. | Nov 2005 | B2 |
6981544 | Iwanami et al. | Jan 2006 | B2 |
6992419 | Kim et al. | Jan 2006 | B2 |
7131281 | Salim et al. | Nov 2006 | B2 |
7135799 | Rittmeyer | Nov 2006 | B2 |
7150159 | Brummett et al. | Dec 2006 | B1 |
7246502 | Hammonds et al. | Jul 2007 | B2 |
7316119 | Allen | Jan 2008 | B2 |
7350368 | Heberle et al. | Apr 2008 | B2 |
7385323 | Takahashi et al. | Jun 2008 | B2 |
7591143 | Zeigler et al. | Sep 2009 | B2 |
7591303 | Ziegler et al. | Sep 2009 | B2 |
7614242 | Quesada Saborio | Nov 2009 | B1 |
7637031 | Salim et al. | Dec 2009 | B2 |
7765824 | Wong et al. | Aug 2010 | B2 |
7821175 | Ionel et al. | Oct 2010 | B2 |
7932658 | Ionel | Apr 2011 | B2 |
8001799 | Obayashi et al. | Aug 2011 | B2 |
8141377 | Connell | Mar 2012 | B2 |
8156754 | Hong et al. | Apr 2012 | B2 |
8276892 | Narikawa et al. | Oct 2012 | B2 |
8492948 | Wang et al. | Jul 2013 | B2 |
8517087 | Zeigler et al. | Aug 2013 | B2 |
8821092 | Nambara et al. | Sep 2014 | B2 |
8841813 | Junak et al. | Sep 2014 | B2 |
8905071 | Coombs et al. | Dec 2014 | B2 |
8919140 | Johnson et al. | Dec 2014 | B2 |
8947531 | Fischer | Feb 2015 | B2 |
9157670 | Kreeley et al. | Oct 2015 | B2 |
9216628 | Self et al. | Dec 2015 | B2 |
9221409 | Gauthier et al. | Dec 2015 | B1 |
9327578 | Itoh | May 2016 | B2 |
9670933 | Yoo et al. | Jun 2017 | B2 |
9783024 | Connell | Oct 2017 | B2 |
9878591 | Taniguchi et al. | Jan 2018 | B2 |
10267546 | Evans et al. | Apr 2019 | B2 |
10967709 | Connell | Apr 2021 | B2 |
20010010261 | Oomura et al. | Aug 2001 | A1 |
20010013409 | Burk | Aug 2001 | A1 |
20010015070 | Junichiro | Aug 2001 | A1 |
20020020183 | Hayashi | Feb 2002 | A1 |
20020026801 | Yamashita | Mar 2002 | A1 |
20020036081 | Ito et al. | Mar 2002 | A1 |
20020042248 | Vincent et al. | Apr 2002 | A1 |
20020078700 | Keim et al. | Jun 2002 | A1 |
20020084769 | Iritani et al. | Jul 2002 | A1 |
20020108384 | Higashiyama | Aug 2002 | A1 |
20020112489 | Egawa et al. | Aug 2002 | A1 |
20020157412 | Iwanami et al. | Oct 2002 | A1 |
20020157413 | Iwanami et al. | Oct 2002 | A1 |
20030041603 | Tada et al. | Mar 2003 | A1 |
20030105567 | Koenig et al. | Jun 2003 | A1 |
20030106332 | Okamoto | Jun 2003 | A1 |
20040060312 | Hom et al. | Apr 2004 | A1 |
20040079098 | Uno et al. | Apr 2004 | A1 |
20040112074 | Komura et al. | Jun 2004 | A1 |
20040168449 | Homan et al. | Sep 2004 | A1 |
20040216477 | Yamasaki et al. | Nov 2004 | A1 |
20040221599 | Hille et al. | Nov 2004 | A1 |
20040250560 | Ikura et al. | Dec 2004 | A1 |
20040256082 | Bracciano | Dec 2004 | A1 |
20050016196 | Kadle et al. | Jan 2005 | A1 |
20050109499 | Iwanami et al. | May 2005 | A1 |
20050161211 | Zeigler et al. | Jul 2005 | A1 |
20050230096 | Yamaoka | Oct 2005 | A1 |
20050235660 | Pham | Oct 2005 | A1 |
20050257545 | Ziehr et al. | Nov 2005 | A1 |
20060042284 | Heberle et al. | Mar 2006 | A1 |
20060080980 | Lee et al. | Apr 2006 | A1 |
20060102333 | Zeigler et al. | May 2006 | A1 |
20060118290 | Klassen et al. | Jun 2006 | A1 |
20060151163 | Zeigler et al. | Jul 2006 | A1 |
20060151164 | Zeigler et al. | Jul 2006 | A1 |
20060254309 | Takeuchi et al. | Nov 2006 | A1 |
20060277936 | Norden | Dec 2006 | A1 |
20070039336 | Wu | Feb 2007 | A1 |
20070070605 | Straznicky et al. | Mar 2007 | A1 |
20070101760 | Bergander | May 2007 | A1 |
20070103014 | Sumiya et al. | May 2007 | A1 |
20070131408 | Zeigler et al. | Jun 2007 | A1 |
20070144723 | Aubertin et al. | Jun 2007 | A1 |
20070144728 | Kinmartin et al. | Jun 2007 | A1 |
20070163276 | Braun et al. | Jul 2007 | A1 |
20070227167 | Shapiro | Oct 2007 | A1 |
20070295017 | Pannell | Dec 2007 | A1 |
20080017347 | Chung et al. | Jan 2008 | A1 |
20080110185 | Veettil et al. | May 2008 | A1 |
20080156887 | Stanimirovic | Jul 2008 | A1 |
20080196436 | Connell | Aug 2008 | A1 |
20080196877 | Zeigler et al. | Aug 2008 | A1 |
20080209924 | Yoon et al. | Sep 2008 | A1 |
20080295535 | Robinet | Dec 2008 | A1 |
20090140590 | Hung | Jun 2009 | A1 |
20090211280 | Alston | Aug 2009 | A1 |
20090229288 | Alston et al. | Sep 2009 | A1 |
20090241592 | Stover | Oct 2009 | A1 |
20090249802 | Nemesh et al. | Oct 2009 | A1 |
20090301702 | Zeigler et al. | Dec 2009 | A1 |
20100009620 | Kawato et al. | Jan 2010 | A1 |
20100019047 | Flick | Jan 2010 | A1 |
20100127591 | Court et al. | May 2010 | A1 |
20100186433 | Galante et al. | Jul 2010 | A1 |
20100218530 | Melbostad et al. | Sep 2010 | A1 |
20100263395 | Adachi et al. | Oct 2010 | A1 |
20100293966 | Hi | Nov 2010 | A1 |
20100297517 | Maier | Nov 2010 | A1 |
20110000240 | Yamada et al. | Jan 2011 | A1 |
20110088417 | Kayser | Apr 2011 | A1 |
20110120146 | Ota et al. | May 2011 | A1 |
20110126566 | Jones et al. | Jun 2011 | A1 |
20110174014 | Scarcella et al. | Jul 2011 | A1 |
20110308265 | Phannavong | Dec 2011 | A1 |
20120023982 | Berson et al. | Feb 2012 | A1 |
20120047930 | Uselton | Mar 2012 | A1 |
20120102779 | Beers et al. | May 2012 | A1 |
20120118532 | Jentzsch et al. | May 2012 | A1 |
20120133176 | Ramberg | May 2012 | A1 |
20120247135 | Fakieh | Oct 2012 | A1 |
20120297805 | Kamada et al. | Nov 2012 | A1 |
20120318014 | Huff et al. | Dec 2012 | A1 |
20130040549 | Douglas et al. | Feb 2013 | A1 |
20130091867 | Campbell et al. | Apr 2013 | A1 |
20130145781 | Liu | Jun 2013 | A1 |
20130167577 | Street | Jul 2013 | A1 |
20130181556 | Li et al. | Jul 2013 | A1 |
20130298583 | O'Donnell | Nov 2013 | A1 |
20130319630 | Yamamoto | Dec 2013 | A1 |
20140066572 | Corveleyn | Mar 2014 | A1 |
20140075973 | Graaf et al. | Mar 2014 | A1 |
20140102679 | Matsudaira et al. | Apr 2014 | A1 |
20140241926 | Fraser | Aug 2014 | A1 |
20140245770 | Chen | Sep 2014 | A1 |
20140260358 | Leete et al. | Sep 2014 | A1 |
20140260403 | Connell | Sep 2014 | A1 |
20140290299 | Nakaya | Oct 2014 | A1 |
20150059367 | Emo et al. | Mar 2015 | A1 |
20150064639 | Drumbreck | Mar 2015 | A1 |
20150158368 | Herr-Rathke et al. | Jun 2015 | A1 |
20150202986 | Hatakeyama et al. | Jul 2015 | A1 |
20150210287 | Penilla et al. | Jul 2015 | A1 |
20150236525 | Aridome | Aug 2015 | A1 |
20150239365 | Hyde et al. | Aug 2015 | A1 |
20150306937 | Kitamura et al. | Oct 2015 | A1 |
20160089958 | Powell | Mar 2016 | A1 |
20160144685 | Ochiai et al. | May 2016 | A1 |
20160146554 | Bhatia et al. | May 2016 | A1 |
20160229266 | Maeda et al. | Aug 2016 | A1 |
20170067676 | Munk | Mar 2017 | A1 |
20170211855 | Fraser et al. | Jul 2017 | A1 |
20170350632 | Hirao | Dec 2017 | A1 |
20180001731 | Vehr | Jan 2018 | A1 |
Number | Date | Country |
---|---|---|
1468409 | Jan 2004 | CN |
2883071 | Mar 2007 | CN |
201872573 | Jun 2011 | CN |
102398496 | Apr 2012 | CN |
103547466 | Jan 2014 | CN |
104105610 | Oct 2014 | CN |
105071563 | Nov 2015 | CN |
105186726 | Nov 2015 | CN |
4440044 | May 1996 | DE |
197 45 028 | Apr 1999 | DE |
10014483 | Nov 2000 | DE |
199 42 029 | Mar 2001 | DE |
199 54 308 | Jul 2001 | DE |
102005004950 | Aug 2006 | DE |
10 2007 028851 | Dec 2008 | DE |
102010054965 | Jun 2012 | DE |
10 2012 022564 | May 2014 | DE |
11 2015 000552 | Nov 2016 | DE |
0516413 | Dec 1992 | EP |
0958952 | Nov 1999 | EP |
1024038 | Aug 2000 | EP |
1 400 764 | Mar 2004 | EP |
1 477 748 | Nov 2004 | EP |
1 700 725 | Sep 2006 | EP |
L 703 231 | Sep 2006 | EP |
L 970 651 | Sep 2008 | EP |
2048011 | Apr 2009 | EP |
2196748 | Jun 2010 | EP |
2320160 | Nov 2011 | EP |
2894420 | Jul 2015 | EP |
0963895 | Dec 2015 | EP |
3118035 | Jan 2017 | EP |
2966391 | Apr 2012 | FR |
H02-128915 | May 1990 | JP |
5032121 | Feb 1993 | JP |
H07186711 | Jul 1995 | JP |
H97-76740 | Mar 1997 | JP |
H09318177 | Dec 1997 | JP |
H10281595 | Oct 1998 | JP |
2000108651 | Apr 2000 | JP |
2005044551 | Apr 2000 | JP |
2002081823 | Mar 2002 | JP |
2005-033941 | Feb 2005 | JP |
2005-081960 | Mar 2005 | JP |
2006-264568 | Oct 2006 | JP |
2008220043 | Sep 2008 | JP |
2012017029 | Jan 2012 | JP |
2014226979 | Dec 2014 | JP |
20090068136 | Jun 2009 | KR |
WO 8909143 | Oct 1989 | WO |
WO 9961269 | Dec 1999 | WO |
WO 0000361 | Jan 2000 | WO |
WO 2004011288 | Feb 2004 | WO |
WO 2006082082 | Aug 2006 | WO |
WO 2012158326 | Nov 2012 | WO |
WO 2013113308 | Aug 2013 | WO |
WO 2014112320 | Jul 2014 | WO |
WO 2014180749 | Nov 2014 | WO |
WO 2014209780 | Dec 2014 | WO |
WO 2015076872 | May 2015 | WO |
Entry |
---|
Connell, Notice of Allowance, U.S. Appl. No. 16/941,495, dated Jul. 5, 2022, 8 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 17/560,216, dated Mar. 9, 2023, 8 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 16/922,855, dated Jun. 20, 2022, 8 pgs. |
Zeigler, Office Action, U.S. Appl. No. 17/948,999, dated May 1, 2023, 24 pgs. |
Alfa Laval Website http://www.alfalaval.com/ecore-Java/WebObjects/ecoreJava.woa/wa/shoNode?siteNodelID=1668&cont . . . ; date last visited May 18, 2007; 1 page. |
Anonymous: “NITE Connected Climate Controlled Transport Monitoring/Mobile Internet of Things UI Design/Mobil UI: Progress/Printeres/Internet of Things, User Inter . . . ,” Oct. 19, 2016 retrieved from: URL:htps://za.pinterest.com/pin/192810427773981541/, 1 pg. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2014/026687, dated Jul. 28, 2014, 12 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2014/026687, dated Sep. 15, 2015, 7 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2014/026683, dated Jul. 3, 2014 12 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2014/026683, dated Sep. 15, 2015, 6 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2013/068331, dated Nov. 7, 2014, 9 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2013/068331, dated May 10, 2016, 6 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2016/021602, dated Nov. 3, 2016, 7 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2016/021602, dated Sep. 12, 2017, 11 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2017/021346, dated Jul. 25, 2017, 11 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2016/065812, dated Mar. 22, 2017, 12 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2016/065812, dated Jun. 12, 2018, 8 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2018/044093, dated Oct. 25, 2018, 13 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion, PCT/US2017049859, dated Nov. 12, 2017, 4 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2017049859, dated Mar. 5, 2019, 6 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion PCT/US2017053196, dated Sep. 3, 2018, 17 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2017053196, dated Apr. 2, 2019, 11 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion PCT/US2016/423326, dated Sep. 27, 2016, 8 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability PCT/US2016/423326, dated Jan. 16, 2018, 7 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion PCT/US2016/42307, dated Oct. 7, 2016, 8 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability PCT/US2016/42307, dated Jan. 16, 2018, 7 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion PCT/US2016/42314, dated Sep. 30, 2016, 7 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability, PCT/US2016/42314, dated Jan. 16, 2018, 6 pgs. |
Bergstrom, Inc., International Search Report and Written Opinion PCT/US2016/42329, dated Sep. 30, 2016, 6 pgs. |
Bergstrom, Inc., International Preliminary Report on Patentability PCT/US2016/42329, dated Jan. 16, 2018, 5 pgs. |
Bergstrom, Inc., Communication Pursuant to Rules 161(2) and 162 EPC, EP14717604.4, dated Oct. 23, 2015, 2 pgs. |
Bergstrom, Inc., Communication Pursuant to Article 94(3), EP14717604.4, dated Jun. 2, 2017, 12 pgs. |
Bergstrom, Inc., Communication Pursuant to Article 94(3), EP14717604.4, dated Feb. 4, 2019, 5 pgs. |
Bergstrom, Inc., Communication Pursuant to Rules 161(2) and 162 EPC, EP14722438.0, dated Nov. 2, 2015. 2 pgs. |
Bergstrom, Inc. Communication Pursuant to Article 94(3), EP14722438.0, dated Jan. 24, 2018, 5 pgs. |
Bergstrom, Inc., Communication Pursuant to Rules 161(2) and 162 EPC, EP13795064.8, dated Jun. 22, 2016, 2 pgs. |
Bergstrom, Inc. Extended European Search Report, EP16204254.3, dated Jul. 25, 2017, 8 pgs. |
Bergstrom, Inc. Partial European Search Report, EP16204259.2, dated May 30, 2017, 14 pgs. |
Bergstrom, Inc. Extended European Search Report, EP16204259.2, dated Oct. 25, 2017, 15 pgs. |
Bergstrom, Inc. Corrected Extended European Search Report, EP16204259.2, dated Nov. 24, 2017, 15 pgs. |
Bergstrom, Inc. Partial European Search Report, EP16204256.8, dated Jul. 13, 2017, 14 pgs. |
Bergstrom, Inc. Extended European Search Report, EP16204256.8, dated Jan. 12, 2018, 11 pgs. |
Bergstrom, Inc. Extended European Search Report, EP16204256.8, dated Dec. 1, 2017, 13 pgs. |
Bergstrom, Inc. Extended European Search Report, EP16204267.5, dated Jul. 11, 2017, 8 pgs. |
Bergstrom, Inc., Communicaton Pursuant to Article 94(3), EP16820096.2, dated Aug. 12, 2019, 7 pgs. |
Bergstrom, Inc., Communicaton Pursuant to Article 94(3), EP16820096.2, dated Jan. 18, 2022, 5 pgs. |
Bergstrom, Inc. Extended European Search Report, EP18177850.7, dated Nov. 28, 2018. 8 pgs. |
Bergstrom, Inc., Communication Pursuant to Rules 161(1) and 162, EP17780954.8, dated May 10, 2019, 3 pgs. |
Bergstrom, Inc., Communication Pursuant to Article 94(3), EP17780954.8, dated Jul. 30, 2020, 6 pgs. |
Bergstrom, Inc., Extended European Search Report, EP19166779.9, dated Aug. 30, 2019, 8 pgs. |
Bergstrom, Inc., Office Action, CN201480027137.4, dated Mar. 3, 2017, 15 pgs. |
Bergstrom, Inc., 2nd Office Action, CN201480027137.4, dated Jul. 13, 2017, 10 pgs. |
Bergstrom, Inc., 3rd Office Action, CN201480027137.4, dated Jan. 17, 2018, 19 pgs. |
Bergstrom, Inc., 4th Office Action, CN201480027137.4, dated Jul. 26, 2018, 8 pgs. |
Bergstrom, Inc., Notification of Grant, CN201480027137.4, dated Feb. 21, 2019, 1 pg. |
Bergstrom, Inc., Patent Certificate CN201480027137.4, dated May 31, 2019, 4 pgs. |
Bergstrom, Inc., Office Action, CN201480027117.7, dated Mar. 9, 2017, 8 pgs. |
Bergstrom, Inc., Patent Certificate, CN201480027117.7, dated Nov. 21, 2017, 3 pgs. |
Bergstrom, Inc., 2nd Office Action, CN201380081940.1, dated Jan. 17, 2018, 13 pgs. |
Bergstrom, Inc., 3rd Office Action, CN201380081940.1, dated Jul. 30, 2018, 7 pgs. |
Bergstrom, Inc., 1st Office Action, CN201680002224.3, dated Dec. 11, 2018, 5 pgs. |
Bergstrom, Inc., Letters Patent, CN201680002224.3, dated Sep. 10, 2019, 2 pgs. |
Connell, Office Action, U.S. Appl. No. 14/209,877, dated Nov. 27, 2015, 19 pgs. |
Connell, Final Office Action, U.S. Appl. No. 14/209,877, dated Jun. 22, 2016, 17 pgs. |
Connell, Office Action, U.S. Appl. No. 14/209,877, dated Dec. 29, 2016, 21 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 14/209,877, dated May 16, 2017, 5 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 14/209,877, dated Aug. 4, 2017, 7 pgs. |
Connell, Office Action, U.S. Appl. No. 14/209,961, dated Dec. 2, 2015, 14 pgs. |
Connell, Final Office Action, U.S. Appl. No. 14/209,961, dated Jul. 25, 2016, 15 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 14/209,961, dated Jun. 15, 2017, 10 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/064,552, dated Jun. 1, 2017, 9 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 14/995,119, dated Aug. 31, 2017, 7 pgs. |
Connell, Office Action, U.S. Appl. No. 14/965,142, dated Aug. 29, 2017, 12 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 14/965,142, dated Feb. 26, 2018, 8 pgs. |
Connell, Office Action, U.S. Appl. No. 15/280,876, dated Dec. 14, 2017, 23 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/280,876, dated Jun. 21, 2018, 8 pgs. |
Connell, Office Action, U.S. Appl. No. 15/791,243, dated May 8, 2018, 12 pgs. |
Connell, Office Action, U.S. Appl. No. 15/065,745, dated May 31, 2018, 44 pgs. |
Connell, Final Office Action, U.S. Appl. No. 15/065,745, dated Dec. 17, 2018, 27 pgs. |
Connell, Office Action, U.S. Appl. No. 15/065,745, dated May 9, 2019, 28 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/065,745, dated Nov. 14, 2019, 9 pgs. |
Connell, Office Action, U.S. Appl. No. 15/283,150, dated Sep. 27, 2018, 21pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/283,150, dated Mar. 22, 2019, 8 pgs. |
Connell, Office Action, U.S. Appl. No. 16/894,728, dated May 26, 2021, 7 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 16/894,728, dated Sep. 22, 2021, 8 pgs. |
Connell, Office Action, dated Oct. 19, 2018, U.S. Appl. No. 15/722,860, 7 pgs. |
Connell, Notice of Allowance, dated Feb. 7, 2019, U.S. Appl. No. 15/722,860, 5 pgs. |
Connell, Notice of Allowance, dated May 20, 2019, U.S. Appl. No. 15/722,860, 5 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 16/546,141, dated Dec. 2, 2020, 5 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/791,243, dated Jan. 24, 2019, 7 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/791,243, dated May 15, 2019, 7 pgs. |
Connell, Office Action, dated Apr. 18, 2019, U.S. Appl. No. 15/816,993, 17 pgs. |
Connell, Notice of Allowance, dated Sep. 26, 2019, U.S. Appl. No. 15/816,993, 8 pgs. |
Connell, Office Action, U.S. Appl. No. 15/439,865, dated Sep. 24, 2019, 6 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/439,865, dated Jan. 30, 2020, 8 pgs. |
Connell, Office Action, U.S. Appl. No. 15/660,734, dated Oct. 30, 2019, 24 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 15/660,734, dated Mar. 9, 2020, 8 pgs. |
Connell, Notice of Allowance, U.S. Appl. No. 16/133,599, dated Mar. 3, 2020, 9 pgs. |
Connell, Office Action, U.S. Appl. No. 16/941,495, dated Feb. 1, 2022, 12 pgs. |
Connell, Office Action, U.S. Appl. No. 17/560,216, dated Nov. 21, 2022, 10 pgs. |
FlatPlate Heat Exchangers; GEA FlatPiate Inc.; website—http://www.flatplate.com/profile.html; date last visited Aug. 9, 2007; 3 pages. |
Glacier Bay Inc., Glacier Bay's Home Page, page printed from a website, htt(?:i/web.archive.org/web/19990417062255/htt[2://www.glacierbay.com/, apparent archive date: Apr. 17, 1999, 1 page. |
Glacier Bay Inc., Darpa/Glacier Bay ECS, pages printed from a website, httir//web.archive.org/web/19991104132941/wvvw .glacierbay.com/darQatxt. htm, apparent archive date: Nov. 4, 1999, 2 pages. |
Glacier Bay Inc., Glacier Bay ECS DARPA Project—Final Report, pages printed from a website, httn://web.archive.or_gjweb/19991103001512/v⋅vww ,_g.Jacierbay.com/Darnhtm.htm, apparent archive date: Nov. 3, 1999, 9 pages. |
Glacier Bay Inc., Glacier Bay ECS DARPA Project—Project Photos, pages printed from a website, httg://web.archive.org/web/1999 ″1103012854/www .glacierbay.com/Dargghotos.htm, apparent archive date: Nov. 3, 1999, 2 pages. |
Glacier Bay Inc., Glacier Bay ECS DARPA Project—Operational Video, page printed from a website, httQ://web.archive.orq/web/19991022221040/wvvw .qlacierbay.com/DarQvid.htm, apparent archive date Oct. 22, 1999; 1 page. |
Glacier Bay Inc., R & D, pages printed from a website, htt ://web.archive.org/web/20000121130306/www.glacierbay.com/R&D.htm, apparent archive date: Jan. 21, 2000, 2 pages. |
Glacier Bay Inc., Company History, pages printed from a website, httg://web.archive.org/web/20000301153828/www .g!acierbay.com/History:.htm, apparent archive date: Mar. 1, 2000; 2 pages. |
Glacier Bay Inc., Contact, page printed from a website, httQ://web.archive.orq/web/19990508104511/W\′′′I!V .qlacierba:t.com/Contact.htm, apparent archive date: May 8, 1999; 1 page. |
Hansson, Office Action dated Oct. 5, 2018, U.S. Appl. No. 15/256,109, 14pgs. |
Hansson, Final Office Action, U.S. Appl. No. 15/256,109, dated May 2, 2019, 14 pgs. |
Hansson, Notice of Allowance, U.S. Appl. No. 15/256,109, dated Sep. 24, 2019, 9 pgs. |
Michael Löhle, Günther Feuerecker and Ulrich Salzer; Non Idling HVAC-modufe tor Long Distance Trucks;SAE TechnicalPaper Series 1999-01-1193; International Congress and Exposition, Detroit, Michigan; Mar. 1-4, 1999; 8 pages. |
Mahmoud Ghodbane; On Vehicle Performance of a Secondary Loop A/C System; SAE Technical Paper Series 2000-01-1270; SAE 2000 World Congress, Detroit, Michigan; March Jun. 9, 2000; 6 pages. |
Masami Konaka and Hiroki Matsuo; SAE Technical Paper Series 2000-01-1271; SAE 2000 World Congress, Detroit, Michigan; March Jun. 9, 2000; 6 pages. |
Mayo Mayo, Office Action, U.S. Appl. No. 15/034,517, dated Feb. 21, 2018, 22 pgs. |
Mayo Mayo, Final Office Action, U.S. Appl. No. 15/034,517, dated Aug. 28, 2018, 9pgs. |
Mayo Mayo, Final Office Action, U.S. Appl. No. 15/034,517, dated Nov. 30, 2018, 7 pgs. |
Frank Stodolsky, Linda Gaines, and Anant Vyas; Analysis of Technology Options to Reduce the Fuel Consumption of Idling Tracks; Paper-Center for Transportation Research, Energy Systems Division, Argonne National Laboratory,9700 South Cass Avenue, Argonne, Illinois 60439;Jun. 2000; 30 pages. |
Paper No. 26 in IPR2012-00027, Jun. 11, 2013, 12 pgs. (U.S. Pat. No. 7,591,303). |
Patricia Gardie and Vincent Goetz; Thermal Energy Storage System by Solid Absorption for Electric Automobile Heating and Air-Conditioning; Paper; 5 pages, date unknown. |
TropiCool No-idle Heating & Cooling, 110V/12V High-efficiency, Self-contained, Electrified Heating/AC System; ACC Climate Control Brochure, Elkhart, Indiana; 205, 1 page. |
TropiCool Power Plus, More comfort. More efficiency. More options.; ACC Climate Control Brochure, Elkhart, Indiana; 2006, 3 pages. |
TYCO Electronics Corporation, “MAG-MATE Connector with Multispring Pin,” Datasheet, 2013, pp. 1-2 from <URL: http://datasheet.octopart.com/1247003-2-TE-Connectivity-datasheet-14918754.pdf>. |
Packless Industries, the leader in refrigerant to water coaxial heat exchangers, flexible hoses and sucti . . . ; website—http://www.packless.com/profile.htmle: date last visited Aug. 9, 2007; 1 page. |
Xi, Office Action, U.S. Appl. No. 16/370,741, dated Jun. 29, 2021, 17 pgs. |
Xi, Final Office Action, U.S. Appl. No. 16/370,741, dated Dec. 1, 2021, 7 pgs. |
Xi, Notice of Allowance, U.S. Appl. No. 16/370,741, dated Apr. 18, 2022, 8 pgs. |
Zeigler, Office Action, U.S. Appl. No. 13/661,519, dated Mar. 11, 2013, 8 pgs. |
Zeigler, Final Office Action, U.S. Appl. No. 13/661,519, dated Sep. 18, 2013, 15 pgs. |
Zeigler, Office Action, U.S. Appl. No. 13/661,519, dated Apr. 9, 2014, 20 pgs. |
Zeigler, Final Office Action, U.S. Appl. No. 13/661,519, dated Sep. 26, 2014, 23 pgs. |
Zeigler, Office Action, U.S. Appl. No. 13/661,519, dated Oct. 28, 2015, 20 pgs. |
Zeigler, Notice of Allowance, U.S. Appl. No. 13/661,519, dated Jun. 17, 2016, 8 pgs. |
Zeigler, Office Action, U.S. Appl. No. 16/046,711, Feb. 6, 2020, 17 pgs. |
Zeigler, Final Office Action, U.S. Appl. No. 16/046,711, dated Jul. 23, 2020, 17 pgs. |
Zeigler, Advisory Action, U.S. Appl. No. 16/046,711, dated Oct. 27, 2020, 5 pgs. |
Zeigler, Office Action, U.S. Appl. No. 16/046,711, dated Aug. 31, 2021, 16 pgs. |
Number | Date | Country | |
---|---|---|---|
20210291624 A1 | Sep 2021 | US |
Number | Date | Country | |
---|---|---|---|
62130399 | Mar 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16546141 | Aug 2019 | US |
Child | 17224052 | US | |
Parent | 15722860 | Oct 2017 | US |
Child | 16546141 | US | |
Parent | 15064552 | Mar 2016 | US |
Child | 15722860 | US |