Electric vehicle (EV) charge unit reservations

Information

  • Patent Grant
  • 11518245
  • Patent Number
    11,518,245
  • Date Filed
    Tuesday, August 27, 2019
    4 years ago
  • Date Issued
    Tuesday, December 6, 2022
    a year ago
Abstract
A computer implemented method for managing charge availability of a charge unit (CU) to obtain charge for a battery of an electric vehicle (EV) is provided. The CU includes a computer for processing at least part of the method and for communicating with a server over a network. The method includes receiving, by the server, status information from the computer of the CU. The method includes sending to the computer of the CU instructions to make a reservation for the CU. The reservation is for a user account that has requested a desire to charge the battery of the electric vehicle of the user at the CU or another CU. The method includes sending, by the server, a confirmation for the reservation to the user account. The confirmation is viewable via a device having access to the server via the user account. The method includes sending, by the server, a data regarding a time of availability of the CU to the user account for the reservation. The computer of the CU is configured to display a visual indicator regarding the reservation of the CU.
Description
FIELD OF THE EMBODIMENTS

The present invention relates to systems and methods that enable operators of electric vehicles (EV) to obtain charge and information regarding charge availability.


BACKGROUND

Electric vehicles have been utilized for transportation purposes and recreational purposes for quite some time. Electric vehicles require a battery that powers an electric motor, and in turn propels the vehicle in the desired location. The drawback with electric vehicles is that the range provided by batteries is limited, and the infrastructure available to users of electric vehicles is substantially reduced compared to fossil fuel vehicles. For instance, fossil fuel vehicles that utilize gasoline and diesel to operate piston driven motors represent a majority of all vehicles utilized by people around the world. Consequently, fueling stations are commonplace and well distributed throughout areas of transportation, providing for easy refueling at any time. For this reason, fossil fuel vehicles are generally considered to have unlimited range, provided users refuel before their vehicles reach empty.


On the other hand, owners of electric vehicles must carefully plan their driving routes and trips around available recharging stations. For this reason, many electric vehicles on the road today are partially electric and partially fossil fuel burning. For those vehicles that are pure electric, owners usually rely on charging stations at their private residences, or specialty recharging stations. However specialty recharging stations are significantly few compared to fossil fuel stations. In fact, the scarcity of recharging stations in and around populated areas has caused owners of electric vehicles to coin the phrase “range anxiety,” to connote the possibility that their driving trips may be limited in range, or that the driver of the electric vehicle will be stranded without recharging options. It is this problem of range anxiety that prevents more than electric car enthusiasts from switching to pure electric cars, and abandoning their expensive fossil fuel powered vehicles.


It is in this context that embodiments of the invention arise.


SUMMARY

In one embodiment, methods, systems, charge units, computer readable media, and combinations thereof are provided, to enable color coding of charging units (CUs), to provide a visual indication to users of when a CU is available, unavailable, in progress, out of service, etc.


In one embodiment, a computer implemented method is provided. The method includes detecting, by a computer of a charging unit (CU), a connection of a charging connector of the CU to a vehicle charge port of an electric vehicle (EV). The detecting of the connection includes processing a data exchange between electronics of the EV and the computer of the CU. The method includes receiving, by the computer of the CU, charge status of the EV while the charging connector is connected to the CU. The received charge status of the EV changes as charge is provided from the CU to a battery of the EV. The method includes sending a notification by server to a user account that was used to obtain charge for the EV at the CU. The notification provides data for a graphical user interface that shows the charge status of the EV. The method includes receiving instructions from a device associated with the user account, to make payment of a fee or receive a fee charge, to instruct the CU to indicate an in progress or in-use state even when the EV is at a full level of charge while the EV is occupying the CU and is preventing others from access to the CU that is provided for public use of users with user accounts. The method includes sending data by the server to the computer of the CU to display an in progress or in-use state, wherein the server communicates over the internet with the device.


In some embodiments, the computer of the CU and the server are part of a system, and the user accounts include access privileges to the CU and other CUs that are part of the system. The user accounts are linked to electronic payment for debits of fees while using the CUs.


In some embodiments, detecting connection includes initiation and processing of data exchange between the EV and CU. The exchange of data is through a data line integrated with the charging connector or a wireless link between the EV and CU, or a wireless link between the user device and the CU or server, or a wireless link between the user device and server and EV, a combination thereof.


In some embodiments, the server is provided with communication to a plurality of CUs at one or more geo-locations. Then, receiving, a request to find a CU at the server, from an EV that is geographically local to or along a driving path of one or more CUs. The method includes sending instructions, by the server to an available CU to make a reservation of the CU for use by an EV associated with the user account used to make the reservation of the CU.


In one embodiment, a method includes detecting connection of a charging connector of the charge unit to a vehicle charge port of the EV. The method includes receiving charge status of the EV while the charging connector is connected to the CU and activating a visual indicator at the CU. The visual indicator is set indicative of the charge status of the EV. The method includes changing the visual indicator as the charge status of the EV changes. The method enables a user device to receive notifications of charge status and communicate with cloud processing to request changing of the visual indicator of the CU to a non-full state even when the EV is at a full state of charging.


In one embodiment, a method for managing charge status of an electric vehicle (EV) at a charge unit (CU) is provided. The method includes detecting connection of a charging connector of the charge unit to a vehicle charge port of the EV. The method also includes receiving charge status of the EV while the charging connector is connected to the CU and activating a light at the CU. The light is set to a color that is indicative of the charge status of the EV. The method then includes changing the color of the light as the charge status of the EV changes. The method executed by a processor at a charge unit or on cloud processing logic over the Internet, or combinations thereof.


In one embodiment, detecting connection includes establishing initiation of data exchange between the EV and CU, the exchange of data can be through a data line in the charging connector or a wireless link between the EV and CU.


In one embodiment, the charge status includes determining a level of charge of a battery of the EV.


In one embodiment, the light at the CU is either connected to the CU or is proximate to the CU, and the color is set by a color shade on a light, a light emitting diode (LED) with a color shared that moves to different colors, a colored LED, or a plurality of colored LEDs that turn on a different times depending on the desired color for the charge status.


In one embodiment, a color is assigned to levels of charge of the vehicle, including a color to indicate a full level of charge of the EV, and wherein, a notification is generated and sent to a user account that was used to obtained charge for the EV at the CU.


In one embodiment, the notification is sent for one of a progress of charge, or to indicate that the EV has reached the full level of charge.


In one embodiment, the method also includes enabling a user account that was used to obtained charge for the EV at the CU to pay a fee, from a remote device, to change the color of the CU to a non-full state even when the EV is at the full level.


In one embodiment, the method also includes enabling sending a notification to a user account that was used to obtained charge for the EV at the CU, the notification providing a status of charge of the EV.


In one embodiment, the status of charge of the EV is published to a user account that is accessible over the Internet using a device having access to the Internet.


In one embodiment the color is illustrated on a graphical user interface on a display, when the user account is accessed to view the status of charge of the EV.


In one embodiment the CU includes a push notification function to enable users proximate to the CU to send a notification to the user account requesting that the EV be moved when the color indicates that the EV has reached a full state of charge and is not moved from a spot that is occupying the CU.


In one embodiment, the method also includes receiving a request from a local EV to locate a CU, and an available CU is activated to blink the color to enable visual identification from an area proximate to the CU.


In one embodiment, the method is executed by a CU having electronics, communication links to the Internet to access cloud processing logic, or can be executed partially by cloud processing logic and logic of the CU, or also process can be made or assisted by processing logic of electronics of the EV connected to the CU, or combinations thereof. Computer readable media can also be provided, which will hold processing instructions for carrying out any one of the method operations, as instructions, or by circuit or chips that are programmed to execute instructions or chips or circuits that communicate with a network, such as the internet.





BRIEF DESCRIPTION OF DRAWINGS


FIG. 1 illustrates a charge unit having a color indicator, which projects the charge state of an electric vehicle (EV) connected to the CU, in accordance with one embodiment.



FIG. 2 illustrates an example of a charge bank of CUs, and various color indicators, and codes for notifying users of charge state, in accordance with one embodiment.



FIG. 3 illustrates an example of a user mobile device, and notifications that can be provided, along with color indicators, in accordance with one embodiment.



FIG. 4 illustrates an example of color codes used in a parking area, where color is used to identify open spaces with CUs that are available, in accordance with one embodiment.



FIG. 5 illustrates an example flow chart of a method, to provide color indicators on CUs, notifications for status, remote pay to extend use of a CU, in accordance with one embodiment.



FIG. 6 shows an example of a user with a mobile device approaching a CU, next to an EV, in accordance with one embodiment of the present invention.



FIG. 7 shows a user accessing a QR code of the CU, in accordance with one embodiment.



FIG. 8 shows an example screen with instructions, so the user can sync with the device and select the level of charge, in accordance with one embodiment.





DETAILED EMBODIMENTS

In one embodiment, method are provided to enable color coding of charging units (CUs), to provide a visual indication to users of when a CU is available, unavailable, in progress, out of service, etc. The visual indicators, in one embodiment are color coded. The color coding can, in one embodiment, be visible to drivers or users in proximity to the CU. In other embodiments, the color indicators can also be published to the internet to allow remote users to quickly identify proximate CUs and identify their current use state. In other embodiments, users, via applications (on mobile devices or on the vehicle) can identify proximate CUs, their status, make reservations for particular CUs, and receive notifications of the progress. In one embodiment, be making reservations ahead of arriving at a CU, the user is best assured of having access to connect the EV to the CU, so that the charging process can be optimized.


A number of embodiments are described below, with reference to specific inventive topics and/or sub-embodiments that relate to electric vehicles, charging methods, wireless device synchronization to exchange information regarding charging events, cloud based processing technologies to share charge availability information, discounts across a charge supply grid, geo-location mapping and charge finding, user interfaces, charge unit identification systems, user interfaces to unify acquisition of charge, reservation of charge, charge units with color indicators to signal charge status and availability, charge supply systems and infrastructure for connecting charge to electric vehicles (EVs), cloud based databases and distributed data centers for tracking charge usage and sharing charge usage with charge providers, utilities, drivers of EVs, owners of charge units (CUs) and owners or managers of charge unit install points (CUIPs).


In one implementation, the listed embodiments may be viewed broadly to define separate defined embodiments. In other implementation, the listed embodiments may be combined with one or more of the respectively listed embodiments to define unified embodiments.


Payment for charge can, in one embodiment, be unified by a process or application that shares charge activity and provides revenue back to the suppliers of the CU. Payment can further be unified by enabling wireless payment at a CU. In one example, when an EV reaches a location of a CU, an application can be surfaced to the electronics of the vehicle or to a user's portable device. The application can provide the user with options to login or simply accept to proceed with automatic payment for charge consumed at the CU. Cloud services, which may run one or more applications, can maintain logs for the user to show historical charge activities and costs.


On the CU side, the supplier of the charge can also receive payment from the EV drivers and can be provided with metrics of charge utilization at the one or more CUs in a network of CUs owned or operated by the CU supplier.


Utility companies or power suppliers can also be provided with metrics of charge use at various CUs, historical charge loads, and times of peak and lows for the various geographically distributed CUs. Utilities can therefore manage power supplies and power rates more effectively and can further populate real time cost per charge rates to EV users, which may discourage EV users from seeking charge during peak or more expensive times of day.


In one embodiment, methods and systems are provided, which include charge units (CUs), which include a color indicator on the charge unit (or station) or next to the charge unit. The color indicator, in one embodiment, is visible so that people in the parking lot or vicinity of charging can identify if cars that are connected to a charge station are already charged (or status of charging) and simply taking up space. The charge color indicator can be any color and can be provided with letters or signs to also communicate information, such as CU available, CU busy, CU out of service, CU in progress. The information can also be for information about the EV charging state, such as empty, 10% charged, 20% charged, 30% charged 70% charged, 100% charged, etc. If a color is used, example colors can be yellow 10A (see FIG. 1) to indicate less than 20% full, orange 10B to communicate ˜50% full, light red 10C to communicate ˜90% full, red 10D to communicate 100% full (or no service available).


The lights can be activated by a method or circuit to turn on or off, blink, pulse, trigger, or control operation. The lighting can be incandescent lighting, lighting with color coded shields, light emitting diodes (LEDs), colored LEDs, and the color can change from one color to another as the charging of an EV progresses (e.g., from yellow to RED, when full). When users drive up to an area or a parking lot with charge stations (or location of charge), EVs connected to the stations publicly show their fill state. If an EV is full, for example, it will be evident that the EV is simply taking up a space.


If the car (e.g., EV) is taking up space and the owner of the EV walked away, a color code at the charge station can be activated. In one embodiment, when an EV is connected to a CU, the user can be provided a code for the CU. The code can be, for example, a QR code, a number, a key, a bar code, etc. In addition to the code being used by the user of the EV, this code can also be used by any person to cause cloud services to send a ping or notification to the user/owner of the car.


For instance, if the user has left temporarily to shop while the car charges, the user may return quickly upon being notified that the charging is complete or is about to complete. As noted, this notification may be in addition to an automatic notification of charge state or completion. That is, an additional notification may be sent by frustrated users that may want to park in the spot that is taken up by the car. To avoid abuse, the notification may be limited to a set number of notifications.


In one embodiment, the charge stations may have an ID (like a QR Code, number, text ID, etc.) that the user can use to sync to when plugging in the car. The ID can be used to notify the user when the charge level reaches full or progresses to charge. If the user does not come back to move the car, the user can pay a fee to stay in the spot to avoid citation. In one embodiment, by paying a fee (e.g., remotely by a mobile device), the color indicator on the charge spot can be kept at a color that is other than full. This will signal to others in the area that the user taking up the spot is legitimately taking up the spot.


In one embodiment, the user may be parked/plugged in at a charge unit (CU) located at or proximate to a store (the CU at that location is registered as a charge unit install point (CUIP)). In this embodiment, the store (e.g., a target) can give the user a discount on the charge or space time if they buy X in the store, etc. This method allows for proximate retailers to sponsor EV drivers to park proximate to the retailers. This sponsorship or promotion can be published to cloud services, which allows EV users to know when such promotions are available. If the user of the EV is looking for charge and the user also needs particular services, and publishing discounts or promotions will allow EV drivers to select certain CUs over other CUs.


In another embodiment, the user may be at work and plugged in to the employer's charge spot. If the user leaves the car plugged in past the time it needs to fill and charge the battery of the electric vehicle (EV), that user may be taking up space that could be used by other co-workers. In one embodiment, when the user plugs into the CU, the user can capture the ID of the CU and register to that charge session. In this manner, the user can be provided notifications as the charge level progresses. The notifications can be by application icons, buzzing, sounds, texts, phone calls, instant messaging, etc. At the time the CU is connected to the user's EV, the user can define how notifications will be sent to the user. The color indicator of the CU can also change as the EV progresses to charge. The same color indicators can be transferred to the owner of the EV as the colors progress to the various colors of charge. In one embodiment, notifications allow users to move their vehicles timely, to allow others to use the CU. In addition, the color indicators provide a way to locally alert people driving EVs if the CUs are actually being used fairly in a particular location, whether private or pubic.



FIG. 1 shows how one user can identify the color state of a CU while the EV progresses to a charge state. In FIG. 2, a charge bank A, can be a location where more than one CU is arranged for charging EVs. If a user drives up to a charge bank A and sees that all slots are taken and the color indicators on the CUs show in-progress charging, the user can capture or input a code of the charge bank A. The code can be used to communicate progress information back to the user while the user waits for a charging spot to open up. Instead of having to be physically present to see the charge state of the CUs in charge bank A, the user can login to cloud services to find charge bank A. As shown in FIG. 3, from a remote location, therefore, a user can see the CUs that are located at the charge bank A, and also see the color indicators of each CU. This can be used ahead of time by the driver of the EV to determine whether he/she wishes to go to charge bank A for charge. For instance, if it looks like spots are available now or the vehicles are nearly all full, the user can opt to drive to the EV to obtain charge from charge bank A.


Cloud services can also provide an approximation of when a CU will be available at bank A, or any other location. Still further, an EV driver can be provided with a list of CUs in the geo-location of the vehicle, based on which CUs will be available.


Notifications regarding charge bank A or other charge banks, can be provided to the user as the charge levels change for the CUs. This provides a dynamic level of information that can be communicated to users regarding current state and projected states of charge. For example, probability and other logic can be used to estimate available of charge particular CUIPs along the users projected path of driving or based on the users heading. This information can be provided to the driver so he/she can select where to attempt to get charge and wait the least amount of time. Users can also remotely reserve a CU, so that the CU is available when the driver arrives.


This information can also be blended with cost of charge, in case the user is looking for a lower charge alternative. The notifications can be sent to the user's mobile device (e.g., smartphone or the like), or the vehicle electronics of the vehicle and associated displays and GUIs. The notifications can be sent with color codes or indicators that show the level of charge of the CUs for which the user is interested. The color notifications can, in real time, be updated as the charge level status changes at the CUs.


In one embodiment, a method and system for providing parking slot location identification for securing charge, is provided. The method includes defining a map of a parking lot with one or more charge units (CUs). The CUs, as shown in FIG. 4, can be located throughout a parking lot or area. The CUs, in one embodiment, will include a light indicator. The light indictors can be, for example, on top regions of the CUs or on poles next to the CUs, or simply proximate to the CU. The lights can light up, for example, above the level of the cars that are parked in the lot, or, for example, above 3-8 feet from the ground. A driver of an EV can drive into a parking lot, see the lighting of an available CU (e.g., by color code; green available; red occupied, etc.). The lights can have a blinking function, to signify where CUs are available. The location of available CUs can also be populated as displayable data to the display screen of an EV (or mobile device) when the EV gets in proximity to CUs that maybe be available.


The indication of availability can also be transferred to the user's mobile device, to signify which CUs are available at a particular location. In one embodiment, the CUs and the status of the CUs can communicate such data to cloud processing, over the internet. Drivers of EVs, connected to the internet can also identify where CUs are located in a particular parking area having CUs.


In some embodiments, the color indicators can be provided on CUs, when not in parking lots. For example, if particular CUs are located outside of a business, the color indicators can have various color shades. Some colors may indicated availability, in-use, reserved, out-of-service, almost done charging, etc. The color indicators can also be communicated to users via notifications. The notifications can be to the displays of EVs or portable devices of the user or to third parties.



FIG. 5 illustrates an example flow chart of a method, wherein colors are used to indicate and convey information regarding charge state of an EV, for one embodiment. The method includes detecting that a charge unit is connected to a vehicle for charging. The charge level of the vehicle is then detected. The charge level can be identified, for example, by obtaining data from the vehicle. This data can be obtained by the CU either by a wired connection to the vehicle, such as a data connection line along the charging connector.


The data can also be obtained wirelessly by the CU, such as by allowing the vehicle to wirelessly transfer data to the CU as the charge progresses. This wireless communication can include a pairing process or sync or pairing after a user enters in a code or accepts the conditions or payment options for charge with the CU. The method then includes allowing a color to be activated on the charge unit (CU). As noted above, this process can be allowed, such that the color indicator in the proximity of the CU is lit or activated so that users in the proximate location can see what state the connected EV is, in its charging process. The color can also be transmitted to a user via a notification, such as during the charging process, etc., as noted in this disclosure.


The method also includes changing the color indicator during the charge progress to provide the visual status of charging of the vehicle. The method includes optionally providing notifications to the user or diver of the EV during the progress or after a period of time, or when charging is complete. The method can allow payment to be received from the EV driver if time is needed to allow the user to move the vehicle after the charging is complete. This will, in one embodiment, cause the light indicators to change to an in-progress state. This will also assist in local users to not be frustrated, as they will think the EV is still charging and not done.


As noted above, if the EV is done, and the light indicator shows the EV charging done, a person that wants the spot can walk up to the CU and push a button to request the EV owner to move the car. In one embodiment, if the user pushes the button or does some other input to cause the request, the cloud services can send a notification to the EV owner indicating that people or others wish to use the spot and the EV should be moved.



FIG. 6 shows an example of a user with a mobile device 12 approaching a CU 10, next to an EV, in accordance with one embodiment of the present invention. The CU 10 may, in one example include a screen or display. In FIG. 7, the user is able to follow directions for obtaining charge from the CU 10. The user, in one embodiment, can scan a QR code, and set the charging instructions, as shown in FIG. 8.


Methods and systems are provided to synchronize user devices with charge units (CUs) to being a charging session. As shown in FIG. 6, the user can arrive to a CU 10 with a device 12. The CU can have a display, which can provide instructions for adding charge to the electric vehicle (EV). FIG. 7 shows a user that has plugged the charging cord to the vehicle, and has scanned a QR code. The cord, in this example, is a charging connector that connects to the CU and also allows connection to the EV at a charge port. If the socket on the charging connector does not mate to the EV charge port, a universal plug or adapter can be used. An adapter can also be used, depending on the type of charging voltage, or process needed to charge particular vehicles, as some EV manufacturers use proprietary plugs or interfaces. Although QR codes are described, other ways to sync the device to a CU to establish a charge session are possible. For example, the CU can provide a phone number, a credit card reader, a password input, a user input interface or touch screen, a bar code, a wireless link via WiFi, internet, or Bluetooth, or other connection interfacing methods and protocols. The CU may also omit having a display, and the EV can simply detect the presence of the CU and ask the user/driver via an on-board screen if the user wishes to obtain charge at the CU that is proximate to the vehicle. The EV screens and apps can also ask the user if they wish to accept a link or pairing with a proximate CU, and then enable screens and GUIs to allow the user to enter codes, sync with payment systems or interfaces and complete the transaction to obtain charge.



FIG. 8 shows an example screen with instructions, so the user can sync with the device and select the level of charge. The sync operation can also be by way of accessing an app over the internet or entering a code of the CU into an app, which is connected to the internet. Notifications for the user, once charge has begun can also be set, either at the CU or on the user's device graphical user interface, or any device connected to the Internet.


A number of embodiments are described below, with reference to specific implementations that refer to vehicles, but such implementations should be broadly construed to include any type of vehicle, structure or object. Without limitation, vehicles can include any type of moving object that can be steered, and can include vehicles that are for human occupancy or not. Vehicles can include those that are privately owned, owned by corporations, commercially operated vehicles, such as buses, automobiles, trucks, cars, buses, trains, trolleys, etc. Example vehicles can include those that are combustion engine based, electric engine (EV) based, hybrids, or other types of energy source vehicles.


A cloud processing system, as described herein, will include systems that are operated and connected to the Internet or to each other using local networking communication protocols. A cloud processing system can be defined as an interconnected and distributed physical or virtual software defined network that utilizes virtual or physical processing and storage machines that enable various applications and operating systems to facilitate the communication with and between various client devices (vehicles, user devices, structures, objects etc.). The communication with and between the various client devices will enable the cloud processing system to deliver additional processing information, data, and real-time metrics concerning data obtained from other processing systems as well as client feedback data. The distributed nature of the cloud processing system will enable users of various vehicles, structures and objects to access the Internet, and be presented with more flexible processing power that will provide the requested services in a more effective manner.


The processing systems can be defined from various data centers that include multiple computing systems that provide the processing power to execute one or more computer readable programs. The processing of the computer readable programs can produce operations that can respond to requests made by other processing systems that may be local to a vehicle's electronic system. For example, a vehicle can include electronics that utilize memory and a processor to execute program instructions to provide services.


In other embodiments, the electronics of a vehicle can synchronize with a user's portable electronics. The user's electronics can include, for example mobile devices that include smart phones, tablet computers, laptop computers, general-purpose computers, special purpose computers, etc. The various computing devices of the vehicle, and or the computing devices of the user (smart devices) can be connected to the Internet or to each other. Provided that a user has access or account access to the cloud service, the cloud processing services on the Internet can provide additional processing information to the electronics of the vehicle.


The wireless communication can include cellular tower communication that couples and communicates through various networks to the Internet, to provide access to cloud processing. Other methods can include providing Wi-Fi communication to local Wi-Fi transmitters and receivers, which communicate with cloud processing 120. Other types of communication can include radio frequency communication, such as Bluetooth communication or combinations of Wi-Fi and Bluetooth. It should be understood that vehicle electronics can communicate with cloud processing 120 via any number of communication methods, so long as exchanges of data can be made with cloud processing 120 from time to time.


The communication can be made by vehicle electronics while the vehicle is on or when the vehicle is off, so long as communication and processing circuitry of vehicle electronics has a power source. The power source can include battery power that powers vehicle electronics to communicate with cloud processing 120 when vehicle is turned off. When vehicle is turned on, the battery that drives vehicle electronics can be recharged.


In one embodiment, at a remote location, a user is able to access a user interface for an application, which provides users access to their user accounts. A user account can be for a user and the user can add one or more vehicles, objects, data or appliances for remote reporting, viewing and control. In one embodiment, a user is an owner or user of a vehicle. The user can register the vehicle with a remote service.


The remote service can be accessed over the Internet, such as via a website or application of a portable device. The remote service can provide a multitude of cloud services for the user, such as remote control features, remote viewing services, remote alarm controls, remote camera activation, remote audio/video recording of the vehicle (i.e., areas around the vehicle and inside the vehicle). In one embodiment, the vehicle is able to connect to the Internet (e.g., when the vehicle engine is off, on, and/or is occupied or un-occupied) to allow a user, via a remote cloud service, to access features of the vehicle. The vehicle can be accessed when running, when parked, when stopped, when moving, etc. The vehicle and its audio recording devices and video cameras can be accessed from remote locations, to allow users to remotely communicate with the vehicle or with people riding or residing inside the vehicle.


The remote communication can also allow a person to communicate remotely with people standing outside (or inside) of a vehicle. For instance, if a user is accessing his or her vehicle from a remote location, cameras installed in and/or on the vehicle allow the remote user to see a person standing proximate to the vehicle. The remote user can then communicate with a person standing proximate to the vehicle using microphones and speakers of the vehicle.


In some embodiments described herein, vehicles, structures and objects may include circuitry and communication logic to enable communication with a cloud processing system over the Internet.


In one embodiment, the services provided by the electronic systems of a vehicle can include services that access the various components or subsystems of a vehicle, such as door locks, service histories, user profiles, audio settings, entertainment settings, mapping functions, communications systems, telecommunication synchronization systems, speakers, heating and cooling functions, auto-engine start/shut-off remotely via smart devices, remote heating/cooling initiation, remote face-to-face conferencing, etc. The electronic systems within a vehicle can also provide a user interface, such as a graphical user interface. The graphical user interface can include a plurality of buttons, controls and transceivers to receive input from a user. The input from a user can also be provided by voice input, facial recognition, eye-retina scans, fingerprint scans, a combination of biometrics, or via a capacitive or regular touchscreen contained or displayed within the vehicle, the vehicle's glass, doors, dashboard etc.


In one embodiment, vehicles can maintain information regarding where they are, where they are heading and their destination maintained which is maintained by GPS and navigation systems on board. The information collected and maintained by every vehicle may be mutually exclusive, meaning that only each individual vehicle is aware of its own heading, rate of speed and current location. This information, in one embodiment is crowd sourced and/or crowd shared/consumed for use in for accident avoidance or other communication. By networking vehicles within a certain radius together, all individually location-aware vehicles become aware of all other vehicles in their sphere of influence. Vehicles may network with vehicles in their range using wireless communication systems such as but not limited to Wi-Fi, Wi-Gig LTE, cellular, radio, near field communication or other methods.


In one embodiment, the communications of the vehicle and electronics of the vehicle will enable direct communication with a user of the vehicle. The user of the vehicle can include, for instance, the owner of the vehicle, a driver of the vehicle, or any third party having access to the vehicle (either to drive the vehicle, to monitor the vehicle remotely, etc.)


The access to the data can also be encrypted to prevent unauthorized access to the data. GPS and mapping services can also be in communication with the cloud processing provide data concerning the locations of the vehicles and activities that occurred to the vehicles when at particular locations. The cloud processing can be access by the vehicles themselves using their electronics and communications, via mobile devices, from home, from work, etc.


In some embodiments, the vehicles may establish peer-to-peer links to facilitate fast transfer of data. In other embodiments, vehicles may link to each other using pairing algorithms that allow the vehicles to exchange data using WiFi, Bluetooth, near field communication (NFC), or some other short range communication protocol.


A user's APP homepage may also include dynamically updating sections in which the most important information at a given time may be displayed or surfaced to a user. If a user has parked in a certain parking area, he or she may want to monitor metrics related to incidents that may have occurred to his or her vehicle, vehicles around his or her vehicle, any dynamically received alerts, as well as precaution levels. Additionally, a user may choose to configure his or her APP homepage to display the most pertinent audio and video feeds to their needs.


In one embodiment, the vehicles can communicate directly with each other via a temporary pairing process. The temporary pairing process can be automatically enabled when vehicles become too close to each other, for example. When this happens, local communication between the vehicles, such as a peer-to-peer connection, Wi-Fi connection, NFC connection, or Bluetooth connection can be established to enable the vehicles to share information concerning their proximity to one another. This local communication will enable one or both vehicles to take correction actions or alert a driver to change course or trigger automatic collision prevention measures (e.g., more aggressive notifications to one or both operators, slow the speed of one or more vehicles, change the driving direction of one or more vehicles, etc.). Once the close proximity communication occurs and some corrective action is made, the data regarding the occurrence and the actions taken can be communicated to the cloud system for storage. The information can then be viewed by a registered user having access to an account for the vehicle(s).


Another embodiment is for a method for providing charge options to drivers of electric vehicles. The method includes receiving data concerning charge providing availability from charge locations, receiving a request from processing logic of an electric vehicle, the request identifying a desire to obtain charge, and determining a current location of the electric vehicle. The method further includes determining identification of charge locations in proximity to the electric vehicle and determining any sponsored rewards offered by the charge locations. The method communicates to the electric vehicle a path to one of the charge locations, the path identifying a sponsored reward offered at the charge location for the path.


Yet another embodiment, a computer processed method for providing charge options to drivers of electric vehicles is provided. The electric vehicles have wireless access to a computer network. The method includes receiving data concerning charge providing availability from charge locations and receiving data concerning sponsored rewards offered by the charge locations and rules for offering the sponsored rewards. The method receives a request from processing logic of an electric vehicle, and the request identifies a desire to obtain charge in route between a current location of the vehicle and a destination location. The method includes generating a plurality of paths that can be traversed by the electric vehicle between the current location and the destination location, where each of the paths identify possible charge locations at which the electric vehicle can be charged. Each of the possible charge locations identifying any sponsored rewards offered if the electric vehicle obtains charge at the possible charge locations. The method includes forwarding the plurality of paths as options to the user of the electric vehicle via a user interface. The sponsored rewards are identified to the user to enable tradeoffs between length of path and reward obtained.


Methods and systems for providing charge options to drivers of electric vehicles are provided. One example method includes receiving data concerning charge providing availability from charge locations and receiving a request from processing logic of an electric vehicle, the request identifying a desire to obtain charge. The method includes determining a current location of the electric vehicle and determining identification of charge locations in proximity to the electric vehicle. The method further includes determining any sponsored rewards offered by the charge locations and communicating to the electric vehicle a path to one of the charge locations, where the path is identified with a sponsored reward offered at the charge location if the path is selected and charge is obtained. The method can be processed by a server and paths are communicated to vehicles to alert drivers of the electric vehicles of rewards or discounts if charge is obtained from certain locations. Other embodiments that compliment sponsored paths for obtaining charge are described below, and relate to electric vehicle charging and reduction of range anxiety.


Embodiments are also described for methods and systems for providing auxiliary charging mechanisms that can be integrated or coupled to a vehicle, to supplement the main battery of a vehicle. The auxiliary charging mechanism can be in the form of an auxiliary battery compartment that can receive a plurality of charged batteries. The auxiliary battery compartment can be charged with or without the vehicle, and can be installed or placed in the vehicle to provide supplemental charge to the vehicles main battery. Thus, if the main battery becomes depleted, the auxiliary battery compartment, having a plurality of charged batteries, can resume providing charge to the vehicle.


In other embodiments, the auxiliary battery can be one compartment that has multiple smaller compartments for receiving volt bars (charging units), or other battery type charging devices. Further, the auxiliary battery is interconnected to the main battery of the vehicle, or to a battery distribution or charge distribution-handling unit. In other embodiments, the auxiliary battery can be inserted into side panels of the vehicle, in the front compartment of the vehicle, the floorboard of the vehicle, the site support structure of the vehicle, etc.


Cloud processing technology is also provided, which provides processing resources to connected vehicles through a distributed network. In one embodiment, the cloud processing can communicate with various charging stations using Internet connections, where charge Station metrics can be uploaded to the cloud processing system. The charge Station metrics can include availability of charge pumps, charge handles, charge plugs, charge mats (for wireless charging), volt bars, or other charge providing facilities.


Examples of such metrics can include the number of charge pumps available at particular period of time, historical availability times of the charge pumps, typical charge time estimates at particular charging stations, prices associated with the charge at the particular charging stations, feedback from customers through social networks, concerning the charging stations, and the like. The cloud processing can then process the charge Station status, traffic information associated with locations around or between charging stations and a user's current location, and provide specific suggested routes. The route generator can provide guided routes to the various charging stations (e.g., charge locations), based on the users immediate needs, desire for discounts, sponsored rewards, or the amount of time it will take to obtain access to a charge pump at a particular point in time. Broadly speaking, a discount is a reward and a reward is a discount, and a sponsored reward is a discount that is at least partially paid by another party for the benefit of the recipient of the reward.


The driver location processor can communicate the information concerning drivers to the cloud processing logic, so as to provide the most effective information concerning charge availability to the various drivers. For example, users in their particular vehicles may have a connected display or a portable device having access to the Internet. Based on the user's location and charging needs, (and optionally the destination) the user can be provided with route options (e.g., one or more optional paths). The route options can be, for example, the fastest and most available charge Station (or charge providing devices) to the users current location, the cheapest charge available at a particular point in time, or information regarding charge prices for a particular future point in time.


Once the user selects a route option, the route generator can provide information concerning the charging station, and can also prepay or book a charging station slot. A charging station slot can include, for example a parking spot in front of a charging station. The charging station slot can be reserved if the user decides to prepay for the charging station, as a convenience. For example, if charging slots at a particular charge station appear to be heavily used, a user can pre-reserve charging slot(s) ahead of time, so that when the user arrives at the charging station, the charging slot will be immediately available. This could be considered a convenience fee associated with pre-reserving of a charging slot, along a particular route. In another embodiment, the charging station can provide incentives to users to come to the particular charging station.


For example, if the user prepays for charge at a particular charging station, the charging station can provide a discount on the charge provided. For example, if the charging station wishes to fill a plurality a charging slots during a particular slow time, the charging station can communicate with the cloud processing and publish availability of its charging stations per particular period of time. A database associated with cloud processing will hold this information so it can be dynamically updated and accessed in real-time by users to fill their charging needs of their electric vehicles. During that particular period of time, the charging station can offer discounts or rewards to users so that drivers can decide to visit the charging station instead of another charging station. Still further, charging stations can offer discounts for users to use the particular charging station, and the discounts can be offered by more than one party or entity. For instance, if the charging stations are located near a particular business, that particular business can sponsor discounts or rewards at the charging station to drive traffic to or near that particular business. When users are charging their vehicles at the particular station near the particular business, users can spend their time at the particular business while their vehicle is being charged.


Potentially, the owners of the particular business that sponsored the discounts can increase traffic to their business and increase sales. In another embodiment, the owners of the particular business can offer discounts to their business products or services, if the business products or services or located near or beside the charging station. As will be described below, other embodiments can include having charging station pumps or handles or plugs, located in nontraditional charging station configurations. For example, charging plugs can be installed at various nontraditional locations, such as parking lots of retail stores. Other examples locations can include, without limitation, parks, city streets, parking garages, post offices, government areas, schools, offices complexes or campuses, coffee shops, malls, strip malls, box store parking lots, beach parking, homes, public roads, etc. If a large retail store has a large parking lot, a portion of that parking lot can be dedicated for charging plugs, which can be used by customers while the customers shop at the retail location. In such a situation, the owners of the retail store that have charging plugs assigned to particular parking spots, can publish availability of those charging plugs through the cloud processing network.


The cloud-processing network can then publish availability and prices for users that may be driving around, or may be passing by the retail store along a particular path or route. In some embodiments, the retail store can offer significant discounts for charge, if users charge their vehicles at the charging plugs of the retail store. While the users charge their vehicles, the users may visit the retail store and purchase goods or services, which is a reward for the retailer that is offering the discount for the charge. In still another embodiment, retail stores having charge plugs can advertise availability of the charge plugs (and parking spots) in real time, and provide discounts or deals to users that may wish to charge at the particular retail location.


The discounts can be for the goods and services of the retail store, or simple discounts on the charge provided by the charge plugs of the retail store. As noted above, one embodiment would allow the parking spots having the charge plugs to be reserved and advance, to provide additional convenience to users. In such a configuration, the parking spots can include mechanical barriers that lift and close to allow vehicles to come into and leave the particular parking spots. Thus if a parking spot is reserved, the mechanical barrier can remain closed until the vehicle having the code can communicate access to lift the mechanical barrier so that charging can commence immediately upon arriving at the reserved parking spot. In another embodiment, the charging station or plug can include a monitor or display that indicates whether or not the charging plug is reserved.


If the charging plug is reserved, no other user can park in front of the parking spot, or else received a ticket or fine for parking in a parking spot that's been reserved. The parking spot reservation for charge can be made in advance; such as while user is driving around smart phone, or an integrated device of the vehicle that has access to the Internet makes looking for charge and the reservation. The transaction can also allow a user that is searching for charge to prepay for the charge using a graphical user interface or other exchange mechanism, associated with the route and reservation of a particular charge station or slot. In some embodiments, the charge stations or plugs can be placed in shared parking lots or locations where multiple retail outlets reside.


In such a case, multiple retailers can provide discounts to users to come and use the charging stations located at the retailer's locations. These discounts can then be published to the cloud processing logic. These discounts can also be published dynamically at the request of the provider of the charge, using an Internet portal that allows the user to participate in a network of charge stations that provide discounts. In such embodiments, the discounts can be provided by multiple retailers for their goods and services, and the plug can be located in the shared parking lot. Having this information, the cloud processing can communicate with a route generator to generate various routes (e.g., paths) that are optimized to the user's desired outcome.


The optimization can be to route a user for charge along a plurality of charge stations or plugs that provide discounts. If this is the goal of the user, the route may be longer than other routes, but the discounts may be greater. Such routes may be viewed as a sponsored path that requires a user to traverse a particular route in order to obtain charge for their vehicle. The sponsored routes can change dynamically over time, as sponsors decide to add or remove discounts. Thus, a user that finds a good path may wish to buy now, to avoid losing the discount. If a particular charge station or chart plug has a lot of customers during a particular period to time, the discounts may drop dynamically. If the charge plug for station experiences low activity, the discounts may be increased dynamically. The dynamic adjustment of discounts can occur based on a preset number of rules (e.g., what discount, where offered, when offered, how long it lasts, incentives for fast buy, logic for combining discounts, logic for sharing costs of discounts with others, logic for reducing the cost of the charge, etc.), as set by the provider the charge and/or the sponsor.


The cost for the charge can also be provided with a green rating, which signifies how efficient the charge station is in supplying charge, and the location and source of the charge provided by the charging station. If the charging station obtains charge from wind power, the green rating would be high. If the charge station receives its charge from fossil fuels, the green rating may be lower. If the charging station receives is charge from a variety of different sources, whether solar, wind, or fossil fuel, the green rating can be adjusted. This metric information can then be provided to the cloud processing to allow users of electric vehicles to decide whether or not to visit a particular charge station or charge plug.


In some embodiments, the price of the charge may be more expensive if the green rating is very high, but the charge value to the user may be high, if the user wishes to obtain a very high green rating, and a lower carbon footprint.


For example if the user wishes to replace the vehicle, the user can simply click a button, select an icon, touch a screen, speak a command, gesture an input, etc., to figure out what his vehicle value is, the cost of a replacement vehicle, and the total cost after exchange. This information can be useful to the user in deciding whether or not to trade in the vehicle or remain with the current vehicle and make investments in repairs. As shown, the data exchange between vehicles and the vehicles and the cloud processing can be extensive, but such information can be made available to drivers of those vehicles to make informed decisions.


The drivers can also be provided with information of the duration of the discount, so that drivers can obtain the discount if they have the time to traversed the path, or avoid the path if the discount will not be present when the driver arrives at that application. In another embodiment, the logic in the vehicle or the processing system in the cloud processing can determine whether or not the user would be able to arrive at each of the charging stations or plugs to receive the sponsor discounts. This analysis can include, for example, reviewing traffic patterns, travel speeds and estimates to traverse the different distances, time of day, etc.


In some embodiments, the discounts are provided by a combination of the charge station and retail shops nearby. In other embodiments, the retail shops and plugs/charge providers can provide combined packages of discounts, which could drive users to their location. Accordingly, it should be understood that the dynamic generation of paths could be sponsored, such that the user can be provided with identification of charging locations along a particular path, and the discounts that may be provided along those particular paths.


Again, the information displayed to the user can be displayed in the vehicle's display screen or can be displayed on the users display device (e.g. smart phone, computer, tablet, etc.).


Broadly speaking and without limitation, obtaining charge will include plugging the vehicle into a charging receptacle so as to charge the native battery of the vehicle. In another embodiment, obtaining charge can also include refilling on volt bars to replenish volt bars that have been used during the vehicle usage. In other embodiments, charge can be transferred to a vehicle wirelessly (e.g., without plugging in an outlet or receptacle). Examples can include a transfer surface that the vehicle parts over, and the charge can be transferred wirelessly to the vehicle via conductors on the underside of the vehicle. The vehicle can simply park in the slot and once payment is made, the charge can start to flow capacitively or wirelessly to the electric vehicle.


As can be appreciated, the sponsored path process can provide a quick and efficient manner for allowing the user to identify their desired endpoint, and provide options for traversing a path to that and point. Along that endpoint, the user can be provided with discounts for charge by sponsors, which can influence or drive people to their charging outlets. The discounts can also be provided in a hybrid manner, such as providing discounts for the charge and discounts with in the retail outlets that are located proximate to the charging stations.


Providing this information to drivers in real time is efficient for both drivers and the retail locations. Drivers in their electric vehicles will need charge, and providers of the charge will benefit from driving users to their location. If the user is still progressing along their desired path, the providers of the discount are simply providing a service and driving customers to their location, where the drivers may purchase other goods and services while the vehicle is being charged.


In one embodiment, the sponsored paths may be generated on electronics and circuitry of the vehicle or by processing in the cloud processing system (e.g. networked Internet systems). In some embodiments, the sponsor paths may be processed partially on the vehicle and partially on the cloud processing system. In some embodiments, the sponsored paths would be dynamically generated on the cloud processing system, and the vehicle or smart phone of the user would simply connect to the cloud processing system.


The data exchange can therefore be dynamically set to be real time, such that providers of the discounts, providers of the charge, and drivers of the vehicles can exchange information. In this example, the provided to the charge can provide discount information, incentives, etc., and the drivers of the vehicles can provide information concerning their desired paths. The processing system can then generate a plurality of options for the user to traverse from point A to point B. For example, the user can select to traverse a sponsored path, to a particular address. The display the vehicle can then requested the user identify whether or not a sponsored path is desired.


It will be obvious, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process operations have not been described in detail in order not to unnecessarily obscure the present invention.


Embodiments of the present invention may be practiced with various computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. The invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.


With the above embodiments in mind, it should be understood that the invention could employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared and otherwise manipulated.


Any of the operations described herein that form part of the invention are useful machine operations. The invention also relates to a device or an apparatus for performing these operations. The apparatus can be specially constructed for the required purpose, or the apparatus can be a general-purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general-purpose machines can be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.


The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. The computer readable medium can also be distributed over a network-coupled computer system so that the computer readable code is stored and executed in a distributed fashion.


Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications can be practiced within the scope of the appended claims. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the description and claims.

Claims
  • 1. A computer implemented method for managing charge availability of a charge unit (CU), the CU including a computer for processing at least part of the method and for communicating with a server over a network, comprising: receiving, by the server, status information from the computer of the CU;sending to the computer of the CU, by the server, instructions to make a reservation for the CU, the reservation being for a first user account that has requested to charge a battery of a first electric vehicle (EV) at the CU;sending, by the server, a confirmation for the reservation to the first user account of the CU, the confirmation being viewable via a device having access to the server via the first user account, the confirmation of the reservation is associated with a wait time for accessing the CU based on the reservation; andsending, by the server, a notification to a second user account using the CU when the server determines from the CU that a second EV associated with the second user account has completed charging using the CU, the notification including a request that the second EV be moved to allow the first EV access to obtain charge at the CU associated with said reservation.
  • 2. The computer implemented method of claim 1, wherein the reservation is associated with a request to notify a first user of the first user account when the CU is available or when the second EV is done charging at the CU.
  • 3. The computer implemented method of claim 1, wherein the CU is part of a group of CUs in a charge unit install point (CUIP), and the reservation is for any one of the CUs of the CUIP.
  • 4. The computer implemented method of claim 1, wherein the server that manages the CU is programmable by an owner of the CU to set an amount of time the second EV can stay in a spot that connects to the CU after charging is complete of the second EV, such that the notification including the request that the second EV be moved is sent after the amount of time has passed.
  • 5. The computer implemented method of claim 1, further comprising, receiving, by the server, data from the first user account indicating that the second EV or another vehicle is blocking a spot for accessing charge from the CU, the server is configured to send a notification to the second user account or another user account to request access to the CU.
  • 6. The computer implemented method of claim 1, wherein the CU has an interface to communicate with the server, the interface enables sending a report that the second EV or another vehicle is blocking the CU.
  • 7. The computer implemented method of claim 1, wherein the CU is one of a plurality of charging units at a location.
CLAIM OF PRIORITY

The present application is continuation application of U.S. patent application Ser. No. 15/444,892, filed on Feb. 28, 2017, entitled “ELECTRIC VEHICLE (EV) CHARGE LOCATION NOTIFICATIONS AND PARKING SPOT USE AFTER CHARGING”, which is a continuation of U.S. patent application Ser. No. 14/880,970, filed on Oct. 12, 2015 (now U.S. Pat. No. 9,579,987, issued on Feb. 28, 2017), entitled “METHODS FOR ELECTRIC VEHICLE (EV) CHARGE LOCATION VISUAL INDICATORS, NOTIFICATIONS OF CHARGE STATE AND CLOUD APPLICATIONS”, which is a continuation application of U.S. patent application Ser. No. 13/797,974, filed on Mar. 12, 2013 (now U.S. Pat. No. 9,180,783, issued on Nov. 10, 2015), entitled “METHODS AND SYSTEMS FOR ELECTRIC VEHICLE (EV) CHARGE LOCATION COLOR-CODED CHARGE STATE INDICATORS, CLOUD APPLICATIONS AND USER NOTIFICATIONS”, which claims priority to U.S. Provisional Patent Application No. 61/745,729, filed on Dec. 24, 2012, and entitled “METHODS AND SYSTEMS FOR ELECTRIC VEHICLE (EV) CHARGING, CHARGING SYSTEMS, INTERNET APPLICATIONS AND USER NOTIFICATIONS”, which are herein incorporated by reference. U.S. patent application Ser. No. 13/797,974, filed on Mar. 12, 2013, entitled “METHODS AND SYSTEMS FOR ELECTRIC VEHICLE (EV) CHARGE LOCATION COLOR-CODED CHARGE STATE INDICATORS, CLOUD APPLICATIONS AND USER NOTIFICATIONS”, is a continuation-in-part of U.S. application Ser. No. 13/452,882, filed Apr. 22, 2012, (now issued as U.S. Pat. No. 9,123,035, issued on Sep. 1, 2015) and entitled “ELECTRIC VEHICLE (EV) RANGE EXTENDING CHARGE SYSTEMS, DISTRIBUTED NETWORKS OF CHARGE KIOSKS, AND CHARGE LOCATING MOBILE APPS”, which claims priority to U.S. Provisional Application No. 61/478,436, filed on Apr. 22, 2011, which are incorporated herein by reference.

US Referenced Citations (361)
Number Name Date Kind
3690397 Parker Sep 1972 A
3799063 Reed Mar 1974 A
3867682 Ohya Feb 1975 A
4052655 Vizza Oct 1977 A
4102273 Merkle et al. Jul 1978 A
4132174 Ziegenfus et al. Jan 1979 A
4162445 Campbell Jul 1979 A
4309644 Reimers Jan 1982 A
4347472 Lemelson Aug 1982 A
4383210 Wilkinson May 1983 A
4389608 Dahl et al. Jun 1983 A
4405891 Galloway Sep 1983 A
4433278 Lowndes et al. Feb 1984 A
4450400 Gwyn May 1984 A
4532418 Meese Jul 1985 A
4789047 Knobloch Dec 1988 A
4815840 Benayad-Cherif et al. Mar 1989 A
5049802 Mintus et al. Sep 1991 A
5121112 Nakadozono Jun 1992 A
5132666 Fahs Jul 1992 A
5184058 Hesse Feb 1993 A
5202617 Nor Apr 1993 A
5297664 Tseng et al. Mar 1994 A
5306999 Hoffman Apr 1994 A
5315227 Pierson May 1994 A
5327066 Smith Jul 1994 A
5343970 Severinsky Sep 1994 A
5422624 Smith Jun 1995 A
5434781 Alofs Jul 1995 A
5441122 Yoshida Aug 1995 A
5449995 Kohchi Sep 1995 A
5487002 Diler et al. Jan 1996 A
5488283 Doughert et al. Jan 1996 A
5492190 Yoshida Feb 1996 A
5548200 Nor et al. Aug 1996 A
5549443 Hammerslag Aug 1996 A
5555502 Opel Sep 1996 A
5563491 Tseng Oct 1996 A
5585205 Kohchi Dec 1996 A
5594318 Knor Jan 1997 A
5595271 Tseng Jan 1997 A
5596258 Kimura et al. Jan 1997 A
5612606 Guimarin et al. Mar 1997 A
5627752 Buck et al. May 1997 A
5636145 Gorman et al. Jun 1997 A
5642270 Green et al. Jun 1997 A
5666102 Lahiff Sep 1997 A
5691695 Lahiff Nov 1997 A
5694019 Uchida et al. Dec 1997 A
5701706 Kreysler et al. Dec 1997 A
5736833 Farris Apr 1998 A
5760569 Chase, Jr. Jun 1998 A
5778326 Moroto et al. Jul 1998 A
5790976 Boll et al. Aug 1998 A
5892598 Asakawa et al. Apr 1999 A
5916285 Alofs et al. Jun 1999 A
5974136 Murai Oct 1999 A
5998963 Aarseth Dec 1999 A
6014597 Kochanneck Jan 2000 A
6049745 Douglas et al. Apr 2000 A
6067008 Smith May 2000 A
6081205 Williams Jun 2000 A
6085131 Kim Jul 2000 A
6151539 Bergholz et al. Nov 2000 A
6175789 Beckert et al. Jan 2001 B1
6225776 Chai May 2001 B1
6234932 Kuroda et al. May 2001 B1
6236333 King May 2001 B1
6252380 Koenck Jun 2001 B1
6301531 Pierro Oct 2001 B1
6307349 Koenck et al. Oct 2001 B1
6330497 Obradovich et al. Dec 2001 B1
6330499 Chou et al. Dec 2001 B1
6370475 Breed et al. Apr 2002 B1
6373380 Robertson et al. Apr 2002 B1
6416209 Abbott Jul 2002 B1
6434465 Schmitt et al. Aug 2002 B2
6456041 Terada et al. Sep 2002 B1
6466658 Schelberg, Jr. et al. Oct 2002 B2
6480767 Yamaguchi Nov 2002 B2
6487477 Woestmanm et al. Nov 2002 B1
6498454 Pinlam Dec 2002 B1
6511192 Henion Jan 2003 B1
6586866 Ikedo Jul 2003 B1
6614204 Pellegrino et al. Sep 2003 B2
6629024 Tabata Sep 2003 B2
6727809 Smith Apr 2004 B1
6741036 Ikedo May 2004 B1
6765495 Dunning et al. Jul 2004 B1
6789733 Terranova Sep 2004 B2
6794849 Mori et al. Sep 2004 B2
6850898 Murakami Feb 2005 B1
6915869 Botti Jul 2005 B2
6922629 Yoshikawa et al. Jul 2005 B2
6937140 Outslay Aug 2005 B1
6940254 Nagamine Sep 2005 B2
7013205 Hafner Mar 2006 B1
7039389 Johnson, Jr. May 2006 B2
7084781 Chuey Aug 2006 B2
7201384 Chaney Apr 2007 B2
7269416 Guthrie et al. Sep 2007 B2
7289611 Iggulden Oct 2007 B2
7376497 Chen May 2008 B2
7379541 Iggulden et al. May 2008 B2
7402978 Pryor Jul 2008 B2
7532965 Robillard May 2009 B2
7565396 Hoshina Jul 2009 B2
7630802 Breed Dec 2009 B2
7650210 Breed Jan 2010 B2
7674536 Chipchase Mar 2010 B2
7683771 Loeb Mar 2010 B1
7693609 Kressner et al. Apr 2010 B2
7698078 Kelty et al. Apr 2010 B2
7740092 Bender Jun 2010 B2
7751945 Obata Jul 2010 B2
7778746 McLeod Aug 2010 B2
7796052 Katz Sep 2010 B2
7850351 Pastrick et al. Dec 2010 B2
7869576 Rodkey et al. Jan 2011 B1
7885893 Alexander Feb 2011 B2
7949435 Pollack May 2011 B2
7956570 Lowenthal Jun 2011 B2
7979198 Kim et al. Jul 2011 B1
7986126 Bucci Jul 2011 B1
7991665 Hafner Aug 2011 B2
8006793 Heichal et al. Aug 2011 B2
8027843 Bodin et al. Sep 2011 B2
8036788 Breed Oct 2011 B2
8054048 Woody Nov 2011 B2
8072318 Lynam Dec 2011 B2
8103391 Ferro et al. Jan 2012 B2
8256553 De Paschoal Sep 2012 B2
8262268 Pastrick et al. Sep 2012 B2
8265816 LaFrance Sep 2012 B1
8266075 Ambrosio et al. Sep 2012 B2
8294420 Kocher Oct 2012 B2
8333492 Dingman et al. Dec 2012 B2
8336664 Wallace et al. Dec 2012 B2
8350526 Dyer et al. Jan 2013 B2
8366371 Maniscalco et al. Feb 2013 B2
8392065 Tolstedt Mar 2013 B2
8405347 Gale Mar 2013 B2
8482255 Crombez Jul 2013 B2
8483775 Buck et al. Jul 2013 B2
8483907 Tarte Jul 2013 B2
8490005 Tarte Jul 2013 B2
8508188 Murtha et al. Aug 2013 B2
8521599 Rivers, Jr. et al. Aug 2013 B2
8527135 Lowrey et al. Sep 2013 B2
8527146 Jackson Sep 2013 B1
8552686 Jung Oct 2013 B2
8589019 Wallace et al. Nov 2013 B2
8624719 Klose Jan 2014 B2
8630741 Matsuoka et al. Jan 2014 B1
8635091 Amigo Jan 2014 B2
8643329 Prosser et al. Feb 2014 B2
8660734 Zhu et al. Feb 2014 B2
8686864 Hannon Apr 2014 B2
8694328 Gormley Apr 2014 B1
8706394 Trepagnier et al. Apr 2014 B2
8713121 Bain Apr 2014 B1
8717170 Juhasz May 2014 B1
8725551 Ambrosio et al. May 2014 B2
8751065 Kato Jun 2014 B1
8751271 Stefik et al. Jun 2014 B2
8760432 Jira et al. Jun 2014 B2
8799037 Stefik et al. Aug 2014 B2
8816845 Hoover et al. Aug 2014 B2
8818622 Bergholz et al. Aug 2014 B2
8818725 Ricci Aug 2014 B2
8819414 Bellur et al. Aug 2014 B2
8825222 Namburu et al. Sep 2014 B2
8836281 Ambrosio et al. Sep 2014 B2
20020064258 Schelberg et al. May 2002 A1
20020085043 Ribak Jul 2002 A1
20020133273 Lowrey et al. Sep 2002 A1
20030137277 Mori et al. Jul 2003 A1
20030153278 Johnson Aug 2003 A1
20030205619 Terranova et al. Nov 2003 A1
20030234325 Marino et al. Dec 2003 A1
20040046506 Mawai et al. Mar 2004 A1
20040064235 Cole Apr 2004 A1
20040092253 Simonds et al. May 2004 A1
20040093155 Simonds et al. May 2004 A1
20040265671 Chipchase et al. Dec 2004 A1
20050021190 Worrell et al. Jan 2005 A1
20050044245 Hoshina Feb 2005 A1
20050231119 Ito et al. Oct 2005 A1
20060125620 Smith et al. Jun 2006 A1
20060182241 Schelberg Aug 2006 A1
20060282381 Ritchie Dec 2006 A1
20060287783 Walker Dec 2006 A1
20070068714 Bender Mar 2007 A1
20070126395 Suchar Jun 2007 A1
20070282495 Kempton Dec 2007 A1
20080039979 Bridges et al. Feb 2008 A1
20080039989 Pollack et al. Feb 2008 A1
20080040129 Cauwels et al. Feb 2008 A1
20080040223 Bridges et al. Feb 2008 A1
20080040295 Kaplan et al. Feb 2008 A1
20080052145 Kaplan et al. Feb 2008 A1
20080086411 Olson et al. Apr 2008 A1
20080097904 Volchek Apr 2008 A1
20080155008 Stiles et al. Jun 2008 A1
20080180027 Matsushita et al. Jul 2008 A1
20080203973 Gale et al. Aug 2008 A1
20080228613 Alexander Sep 2008 A1
20080281663 Hakim Nov 2008 A1
20080294283 Ligrano Nov 2008 A1
20080312782 Berdichevsky Dec 2008 A1
20090011639 Ballard et al. Jan 2009 A1
20090021213 Johnson Jan 2009 A1
20090021385 Kelty et al. Jan 2009 A1
20090030712 Bogolea Jan 2009 A1
20090043519 Bridges et al. Feb 2009 A1
20090058355 Meyer Mar 2009 A1
20090066287 Pollack et al. Mar 2009 A1
20090076913 Morgan Mar 2009 A1
20090082957 Agassi et al. Mar 2009 A1
20090091291 Woody et al. Apr 2009 A1
20090092864 McLean Apr 2009 A1
20090144001 Leonard et al. Jun 2009 A1
20090157289 Graessley Jun 2009 A1
20090164473 Bauer Jun 2009 A1
20090174365 Lowenthal et al. Jul 2009 A1
20090177580 Lowenthal et al. Jul 2009 A1
20090210357 Pudar et al. Aug 2009 A1
20090287578 Paluszek Nov 2009 A1
20090312903 Hafner et al. Dec 2009 A1
20090313032 Hafner et al. Dec 2009 A1
20090313033 Hafner et al. Dec 2009 A1
20090313034 Ferro et al. Dec 2009 A1
20090313098 Hafner et al. Dec 2009 A1
20090313104 Hafner et al. Dec 2009 A1
20090313174 Hafner et al. Dec 2009 A1
20100013434 Taylor-Haw et al. Jan 2010 A1
20100017045 Nesler et al. Jan 2010 A1
20100017249 Fincham et al. Jan 2010 A1
20100042519 Dingler et al. Feb 2010 A1
20100049396 Ferro et al. Feb 2010 A1
20100049533 Ferro et al. Feb 2010 A1
20100049610 Ambrosio et al. Feb 2010 A1
20100049639 Ferro et al. Feb 2010 A1
20100049737 Ambrosio et al. Feb 2010 A1
20100057306 Ishii et al. Mar 2010 A1
20100112843 Heichal et al. May 2010 A1
20100141206 Agassi et al. Jun 2010 A1
20100161481 Littrell Jun 2010 A1
20100161482 Littrell Jun 2010 A1
20100169008 Niwa et al. Jul 2010 A1
20100198508 Tang Aug 2010 A1
20100198513 Zeng Aug 2010 A1
20100211340 Lowenthal et al. Aug 2010 A1
20100211643 Lowenthal Aug 2010 A1
20100222939 Namburu Sep 2010 A1
20100268426 Pathak Oct 2010 A1
20100280956 Chutorash et al. Nov 2010 A1
20100304349 Kunin Dec 2010 A1
20110032110 Taguchi Feb 2011 A1
20110057612 Taguchi et al. Mar 2011 A1
20110074350 Kocher Mar 2011 A1
20110074351 Bianco et al. Mar 2011 A1
20110077809 Leary Mar 2011 A1
20110106329 Donnelly et al. May 2011 A1
20110112969 Zaid et al. May 2011 A1
20110130885 Bowen et al. Jun 2011 A1
20110175569 Austin Jul 2011 A1
20110187521 Beruscha et al. Aug 2011 A1
20110191186 Levy et al. Aug 2011 A1
20110191265 Lowenthal et al. Aug 2011 A1
20110193522 Uesugi Aug 2011 A1
20110202218 Yano Aug 2011 A1
20110246252 Uesugi Oct 2011 A1
20110279083 Asai Nov 2011 A1
20110309929 Myers Dec 2011 A1
20120013300 Prosser et al. Jan 2012 A1
20120019204 Matsuo Jan 2012 A1
20120025765 Frey et al. Feb 2012 A1
20120028680 Breed Feb 2012 A1
20120041624 Stewart et al. Feb 2012 A1
20120053754 Pease Mar 2012 A1
20120074903 nakashima Mar 2012 A1
20120105197 Kobres May 2012 A1
20120123670 Uyeki May 2012 A1
20120136743 McQuade et al. May 2012 A1
20120136802 McQuade et al. May 2012 A1
20120158244 Talty et al. Jun 2012 A1
20120179323 Profitt-Brown et al. Jul 2012 A1
20120218128 Tieman et al. Aug 2012 A1
20120229056 Bergfjord Sep 2012 A1
20120229085 Lau Sep 2012 A1
20120232965 Rodriguez et al. Sep 2012 A1
20120233077 Tate et al. Sep 2012 A1
20120262002 Widmer et al. Oct 2012 A1
20120268068 Jung et al. Oct 2012 A1
20120268076 Danner Oct 2012 A1
20120268242 Tieman et al. Oct 2012 A1
20120280654 Kim Nov 2012 A1
20120296512 Lee et al. Nov 2012 A1
20120303397 Prosser Nov 2012 A1
20120306445 Park et al. Dec 2012 A1
20120310713 Mercuri et al. Dec 2012 A1
20120316671 Hammerslag et al. Dec 2012 A1
20130002876 Pastrick et al. Jan 2013 A1
20130020139 Kim et al. Jan 2013 A1
20130021162 DeBoer et al. Jan 2013 A1
20130029595 Widmer Jan 2013 A1
20130037339 Hickox Feb 2013 A1
20130099892 Tucker et al. Apr 2013 A1
20130103236 Mehrgan Apr 2013 A1
20130110296 Khoo et al. May 2013 A1
20130110632 Theurer et al. May 2013 A1
20130110653 Rivers et al. May 2013 A1
20130127247 Oh et al. May 2013 A1
20130135093 Araki May 2013 A1
20130144520 Ricci Jun 2013 A1
20130145065 Ricci Jun 2013 A1
20130179057 Fisher et al. Jul 2013 A1
20130204466 Ricci Aug 2013 A1
20130241720 Ricci et al. Sep 2013 A1
20130253746 Choi et al. Sep 2013 A1
20130280018 Meirer et al. Oct 2013 A1
20130300554 Braden Nov 2013 A1
20130317693 Jefferies et al. Nov 2013 A1
20130317694 Merg et al. Nov 2013 A1
20130328387 Venkateswaran Dec 2013 A1
20130338820 Corbett et al. Dec 2013 A1
20130342363 Paek et al. Dec 2013 A1
20140002015 Tripathi et al. Jan 2014 A1
20140019280 Medeiros et al. Jan 2014 A1
20140021908 McCool Jan 2014 A1
20140042968 hiroe Feb 2014 A1
20140047107 Maturana et al. Feb 2014 A1
20140066049 Cho et al. Mar 2014 A1
20140089016 Smullin et al. Mar 2014 A1
20140106726 Crosbie Apr 2014 A1
20140118107 Almomani May 2014 A1
20140120829 Bhamidipati May 2014 A1
20140125355 Grant May 2014 A1
20140142783 Grimm et al. May 2014 A1
20140163771 Demeniuk Jun 2014 A1
20140163774 Demeniuk Jun 2014 A1
20140164559 Demeniuk Jun 2014 A1
20140172192 Kato Jun 2014 A1
20140172265 Funabashi Jun 2014 A1
20140172727 Abhyanker et al. Jun 2014 A1
20140179353 Simon Jun 2014 A1
20140200742 Mauti et al. Jul 2014 A1
20140203077 Gadh et al. Jul 2014 A1
20140207333 Vandivier et al. Jul 2014 A1
20140214261 Ramamoorthy et al. Jul 2014 A1
20140214321 Kawamata et al. Jul 2014 A1
20140218189 Fleming et al. Aug 2014 A1
20140232331 Stamenic et al. Aug 2014 A1
20140236414 Droz et al. Aug 2014 A1
20140236463 Zhang et al. Aug 2014 A1
20140247019 Park Sep 2014 A1
20140253018 Kong et al. Sep 2014 A1
20140277936 El Dokor et al. Sep 2014 A1
20140278089 Gusikhin et al. Sep 2014 A1
20140300739 Mimar Oct 2014 A1
Related Publications (1)
Number Date Country
20190386502 A1 Dec 2019 US
Provisional Applications (2)
Number Date Country
61745729 Dec 2012 US
61478436 Apr 2011 US
Continuations (3)
Number Date Country
Parent 15444892 Feb 2017 US
Child 16552885 US
Parent 14880970 Oct 2015 US
Child 15444892 US
Parent 13797974 Mar 2013 US
Child 14880970 US
Continuation in Parts (1)
Number Date Country
Parent 13452882 Apr 2012 US
Child 13797974 US