Vehicle-based external power and remote authorization control system

Abstract

The invention provides a vehicle-based external power and remote authorization control system. A vehicle having a vehicle power system is disclosed. The vehicle may include a battery and the vehicle power system configured to transfer power from the battery to an external accessory connected to the vehicle power system. The vehicle may also include a processor configured to obtain a set of vehicle power system usage rules or a vehicle power system usage request using the vehicle power system from a user device associated with a user via a wireless communication network. The processor may also be configured to control operation of a vehicle power system based on the set of vehicle power system usage rules or the vehicle power system usage request.

Description

Technical Field

[0001] The present disclosure relates to a vehicle-based external power system, and more particularly, to systems and methods for facilitating remote authorization of use of a vehicle-based external power system. Background Art

[0002] Modern vehicles have external power systems to power auxiliary accessories such as compressors, saws, electronic devices, etc. For example, some modern vehicles have a power take-off (PTO), electric PTO (ePTO), etc., which facilitates powering auxiliary accessories. The PTO transfers mechanical power from the vehicle engine to accessories that may not have their own engine or motor to operate. The vehicle operator may need to ensure that the vehicle engine is operational in order for the PTO to transfer mechanical power to the accessories.

[0003] The ePTO decouples auxiliary functions, such as powering accessories, from vehicle engine use. In other words, the ePTO enables the vehicle operator to power accessories even when the vehicle engine may not be able to operate. The ePTO may include an inverter and an electric motor powered by a DC power source, such as a battery, which may be used to power accessories. Summary of the invention

[0004] The present disclosure describes a power management system and method for facilitating remote authorization of vehicle-based external power system use. The power management system may include a vehicle power system that may be disposed in a vehicle. The vehicle power system may be an electric power output device (ePTO) that may be configured to transfer power from a vehicle battery to an external accessory (e.g., a power tool, a lighting device, etc.). The power management system may also include a processor that may be configured to obtain a vehicle power system use request or a vehicle power system use rule set to use / control the vehicle power system. The processor may also be configured to control the operation of the vehicle power system based on the vehicle power system use request or the vehicle power system use rule set. For example, the processor may start or disable the vehicle power system or limit the discharge rate based on the vehicle power system use request or the vehicle power system use rule set.

[0005] In some aspects, the vehicle power system usage rule set may include one or more conditions / criteria for controlling the operation of the vehicle power system. For example, the vehicle power system usage rule set may include at least one of the following: a rule set for starting the vehicle power system within a predefined duration, a rule set for starting the vehicle power system between a first timestamp and a second timestamp, a rule set for starting the vehicle power system for a predefined threshold energy usage value, a rule set for starting the vehicle power system in a predefined geo-fenced area of ​​the vehicle, etc.

[0006] In some aspects, the processor may also be configured to obtain input from a vehicle camera (or vehicle sensor) when the vehicle power system may be activated, and monitor vehicle power system usage based on the obtained input. Based on the monitoring, the processor may be configured to determine improper use of the vehicle power system. In response to determining that the vehicle power system may be improperly used, the processor may deactivate the vehicle power system.

[0007] In a further aspect, the processor may be configured to obtain another vehicle power system usage request from a third-party user device. The other vehicle power system usage request may include request details, such as information associated with the vehicle power system socket to be used, the duration of use of the socket, information associated with the external accessories to be powered by use of the vehicle power system, and expected power consumption. In response to obtaining the request, the processor may correlate the other vehicle power system usage request with the vehicle power system usage rule set, and may control the operation of the vehicle power system based on the correlation.

[0008] The present disclosure discloses systems and methods for facilitating remote monitoring and control of a vehicle power system. The system prevents misuse of the vehicle power system. The system also enables a vehicle owner to provide remote authorization to activate or deactivate the vehicle power system. In other words, the system enables a vehicle owner to control or use the vehicle power system via a wireless network. The system also facilitates third party use of the vehicle power system when the vehicle owner may be away from the vehicle.

[0009] These and other advantages of the present disclosure are provided in detail herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Detailed description is set forth with reference to the accompanying drawings. The use of the same reference numerals may indicate similar or identical items. Various embodiments may utilize elements and / or components other than those shown in the accompanying drawings, and some elements and / or components may not be present in various embodiments. The elements and / or components in the accompanying drawings are not necessarily drawn to scale. Throughout this disclosure, singular and plural terms may be used interchangeably, depending on the context.

[0011] Figure 1 Depicted are examples of environments in which techniques and structures for providing the systems and methods disclosed herein may be implemented.

[0012] Figure 2 A block diagram of an example of a system for facilitating remote authorization of a vehicle power system according to the present disclosure is depicted.

[0013] Figure 3 An example of an embodiment according to the present disclosure for controlling operation of a vehicle power system is depicted.

[0014] Figure 4 An example of an embodiment according to the present disclosure for controlling operation of a vehicle power system is depicted.

[0015] Figure 5 A flow chart of an example of a first method for facilitating remote authorization of a vehicle power system according to the present disclosure is depicted.

[0016] Figure 6 A flow chart of an example of a second method for facilitating remote authorization of a vehicle power system according to the present disclosure is depicted. DETAILED DESCRIPTION

[0017] The present disclosure will be described more fully hereinafter with reference to the accompanying drawings, in which example embodiments of the disclosure are shown and which are not intended to be limiting.

[0018] Figure 1 An example of an environment 100 in which techniques and structures for providing the systems and methods disclosed herein may be implemented is depicted. The environment 100 may include a vehicle 105, which may be a truck, a van, a truck trailer, etc. The vehicle 105 may include any powertrain, such as a gasoline engine, one or more electrically actuated motors, a hybrid powertrain, etc. In addition, the vehicle 105 may be a manually driven vehicle, and / or configured and / or programmed to operate in a fully autonomous (e.g., driverless) mode (e.g., Level 5 autonomy) or in one or more partially autonomous modes that may include driver assistance technologies.

[0019] The vehicle 105 may include a vehicle power system (in Figure 2 The vehicle power system can be configured to provide / supply power to the external accessory 110. In some aspects, the vehicle power system can be a power output device (ePTO), which can be configured to transfer power from the battery (in Figure 2 The battery 242 is shown in the figure as a battery 242 to the accessory 110. The battery can be located in the vehicle 105. The accessory 110 can include, but is not limited to, a plasma cutter, a TiG welder, a cut saw, an air compressor, an angle grinder, a jackhammer, a projector, a speaker, a lighting device, a cement mixer, a mini refrigerator, etc. The vehicle power system can include one or more electrical outlets 115 or any type of hard-wired connection between the vehicle power system and the accessory 110, such as a fixed hard-wired connection. In some aspects, the outlet 115 can be located near the vehicle cargo compartment or the vehicle tailgate, such as Figure 1 As depicted in .

[0020] The environment 100 may also include a user device 120 that may be associated with a user 125. The user 125 may be associated with the vehicle 105 and may include a vehicle manager, a fleet manager, or a vehicle owner. The user device 120 may include a mobile device, a tablet computer, a laptop computer, a smart watch, or any other device with communication capabilities. The vehicle 105 and the user device 120 may be communicatively coupled to each other via one or more networks 130.

[0021] The network 130 illustrates an example of a communication infrastructure in which the connected devices discussed in various embodiments of the present disclosure may communicate. The network 130 may be and / or may include the Internet, a private network, a public network, or other configurations operating using any one or more known communication protocols, such as Transmission Control Protocol / Internet Protocol (TCP / IP), Wi-Fi, UWB, and cellular technologies based on the Institute of Electrical and Electronics Engineers (IEEE) standard 802.11, such as Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), High Speed ​​Packet Access (HSPDA), Long Term Evolution (LTE), Global System for Mobile Communications (GSM), and Fifth Generation (5G), to name a few examples.

[0022] The vehicle 105 may include a vehicle power management system (in Figure 2 105). Specifically, the vehicle power management system ("system") may be configured to receive requests or inputs from user devices 120 via network 130, and to control the operation of the vehicle power system based on the received requests or inputs. For example, the system may receive (wirelessly via user device 120) a request to activate or deactivate the vehicle power system from a user 125 who may be located remotely from vehicle 105. In other words, user 125 may be configured to remotely or wirelessly monitor and control activation or deactivation of the vehicle power system via user device 120 and network 130.

[0023] In some aspects, the input received from the user device 120 may include a rule set that includes predetermined conditions / criteria that can facilitate the system to control the operation or use of the vehicle power system. For example, the system may receive a rule set for: activating or deactivating a specific outlet associated with the vehicle power system, limiting / controlling a discharge rate associated with the vehicle power system, activating the vehicle power system between a first timestamp (e.g., 9 a.m.) and a second timestamp (e.g., 5 p.m.), activating the vehicle power system within a predefined duration (e.g., 4 hours), activating the vehicle power system within a first predefined threshold energy usage value, activating the vehicle power system within a predefined geo-fenced area of ​​the vehicle, etc.

[0024] The vehicle 105 and / or vehicle operator / user may implement and / or perform operations as described herein in the present disclosure in accordance with the owner's manual and safety guidelines.

[0025] Combined with the following Figure 2 Describe the functional details of the vehicle power management system.

[0026] Figure 2 A block diagram of an example of a system 200 for facilitating remote authorization of a vehicle power system according to the present disclosure is depicted. Figure 2 When you can refer to Figure 3 and Figure 4 .

[0027] System 200 may include vehicle 202, which may be the same as vehicle 105. Vehicle 202 may include a vehicle computer 204, a vehicle control unit (VCU) 206, and a vehicle power management system 208 (or power management system 208, in conjunction with Figure 1 The VCU 206 may include a plurality of electronic control units (ECUs) 210 configured to communicate with the vehicle computer 204 .

[0028] The system 200 may also include a mobile device 212 or user device 212 that may connect to the vehicle computer 204 and / or the vehicle power management system 208 using wired and / or wireless communication protocols and transceivers. In some aspects, the mobile device 212 may be associated with the user 125. The mobile device 212 may be communicatively coupled to the vehicle 202 via one or more networks 214. The network 214 may be the same as the network 130.

[0029] In some aspects, according to the present disclosure, the vehicle computer 204 and / or the vehicle power management system 208 may be installed in the vehicle engine compartment (or elsewhere in the vehicle 202). In addition, the vehicle computer 204 may operate as a functional part of the vehicle power management system 208. The vehicle computer 204 may be or include an electronic vehicle controller having one or more processors 216 and a memory 218. In addition, the vehicle power management system 208 may be separate from the vehicle computer 204 (e.g., Figure 2 ), or may be integrally formed as part of the vehicle computer 204.

[0030] The processor 216 may be configured to communicate with one or more memory devices (eg, memory 218 and / or Figure 2The processor 216 may utilize the memory 218 to store programs and / or store data in the form of code to execute various aspects of the present disclosure. The memory 218 may be a non-transitory computer-readable memory that stores vehicle power management program code. The memory 218 may include any one or combination of volatile memory elements (e.g., dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc.), and may include any one or more non-volatile memory elements (e.g., erasable programmable read-only memory (EPROM), flash memory, electronically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), etc.).

[0031] In some aspects, the vehicle computer 204 and / or the vehicle power management system 208 can be configured to communicate with one or more servers 220 and the mobile device 212 via the network 214. In some aspects, the server 220 can be part of a cloud-based computing infrastructure and can be associated with and / or include a telematics service delivery network (SDN) that provides services to the vehicle 202 and other vehicles that may be part of a fleet of vehicles ( Figure 2 ) provides digital data services.

[0032] According to some aspects, the VCU 206 can share a power bus with the vehicle computer 204 and can be configured and / or programmed to coordinate systems of the vehicle 202, a connected server (e.g., server 220), and other vehicles operating as part of a vehicle platoon (e.g., Figure 2The VCU 206 may include or communicate with any combination of ECUs 210, such as, for example, a body control module (BCM) 222, an engine control module (ECM) 224, a transmission control module (TCM) 226, a telematics control unit (TCU) 228, a driver assistance technology (DAT) controller 230, etc. The VCU 206 may also include and / or communicate with a vehicle perception system (VPS) 232, which connects and / or controls one or more vehicle sensing systems 234. The vehicle sensing system 234 may include one or more vehicle sensors, including, but not limited to: a radio detection and ranging (RADAR or "radar") sensor configured to detect and locate objects inside and outside the vehicle 202 using radio waves; a seat area lock sensor; a seat area sensor; a light detection and ranging (LiDAR or "laser radar") sensor; a door sensor; a proximity sensor; a temperature sensor; a weight sensor; a wheel sensor; a camera inside or outside the vehicle; a vehicle external power usage sensor, etc. In some aspects, the vehicle external power usage sensor can be configured to detect vehicle power system usage, such as the amount of energy drawn, the duration that energy can be drawn, the rate at which energy can be drawn, and the like.

[0033] In some aspects, the VCU 206 may control operational aspects of the vehicle 202 and implement one or more instruction sets received from the mobile device 212 , from one or more instruction sets stored in the computer memory 218 of the vehicle computer 204 , including instructions that may operate as part of the vehicle power management system 208 .

[0034] The TCU 228 may be configured and / or programmed to provide vehicle connectivity to wireless computing systems on and off the vehicle 202 and may include a navigation (NAV) receiver 236 for receiving and processing GPS signals, module (BLEM) 238, a Wi-Fi transceiver, a UWB transceiver, and / or may be configured to communicate between the vehicle 202 and other systems (e.g., a vehicle key fob, Figure 2 Not shown), other wireless transceivers for wireless communication between the computer and the module ( Figure 2 2. The TCU 228 may be configured to communicate with the ECU 210 via a bus.

[0035] The ECU 210 may control various aspects of vehicle operation and communication using input from a human driver, input from an autonomous vehicle controller, the vehicle power management system 208, and / or via wireless signal input received over a wireless connection from other connected devices (such as a mobile device 212, a server 220, etc.).

[0036] The BCM 222 typically includes sensors, vehicle performance indicators, and an integrated formation of varactors associated with vehicle systems, and may include processor-based power distribution circuitry that may control functions associated with the vehicle body, such as lights, windows, security devices, cameras, audio systems, speakers, door locks and access controls (including vehicle power system controls), and various comfort controls. The BCM 222 may also operate as a gateway for bus and network interfaces to communicate with remote ECUs ( Figure 2 (not shown) to interact.

[0037] The DAT controller 230 may provide Level 1 to Level 3 autonomous driving and driver assistance functions, which may include, for example, active park assist, vehicle back-up assist, adaptive cruise control, and / or lane keeping, among other features. The DAT controller 230 may also provide various aspects of user and environmental input that may be used for user authentication.

[0038] In some aspects, the vehicle computer 204 can be connected to an infotainment system 240, which can include a touch screen interface portion and can include voice recognition features, biometric capabilities that can identify a user based on facial recognition, voice recognition, fingerprint recognition, or other biometric means. In other aspects, the infotainment system 240 can also be configured to receive user commands via the touch screen interface portion, and / or display notifications, navigation maps, etc. on the touch screen interface portion.

[0039] The computing system architecture of the vehicle computer 204, VCU 206 and / or vehicle power management system 208 may omit certain computing modules. Figure 2 The computing environment depicted in FIG. 1 is an example of possible implementations according to the present disclosure and, therefore, should not be considered limiting or exclusive.

[0040] The vehicle 202 may also include a battery 242 configured to store electricity. The vehicle 202 may additionally include an electric power output device (ePTO) 244 (or vehicle power system 244) configured to transfer electricity from the battery 242 to an external accessory. The external accessory may be combined with Figure 1 The accessory 110 described is the same. In some aspects, the ePTO 244 can include an inverter and an electric motor (not shown) that can be powered by the battery 242.

[0041] According to some aspects, the vehicle power management system 208 can be formed integrally with and / or executed as part of the ECU 210. The vehicle power management system 208, whether formed integrally with the vehicle computer 204 or the ECU 210, or whether operating as a standalone computing system in the vehicle 202, can include a transceiver 246, a processor 248, and a computer readable memory 250.

[0042] The transceiver 246 may be configured to receive information / input from one or more external devices or systems (e.g., the mobile device 212, the server 220, etc.) via the network 214. For example, the transceiver 246 may be configured to wirelessly receive a user request and / or user input / instructions from the mobile device 212 (directly or via the server 220) to control the vehicle power system 244. In some aspects, the user input may include a rule set for controlling the operation of the vehicle power system. For example, the rule set may include a rule set for: activating or deactivating a specific socket associated with the vehicle power system 244, limiting / controlling a discharge rate associated with the vehicle power system 244, activating the vehicle power system 244 between a first timestamp (e.g., 9 a.m.) and a second timestamp (e.g., 5 p.m.), activating the vehicle power system 244 within a predefined duration (e.g., 4 or 5 hours), activating the vehicle power system 244 within a first predefined threshold energy usage value, and activating the vehicle power system 244 within a predefined geo-fenced area of ​​the vehicle, etc. In some aspects, transceiver 246 may be configured to store received user input / instructions in memory 250 .

[0043] In addition, the transceiver 246 can transmit notifications (e.g., alert / alarm signals) or information to an external device or system. In addition, the transceiver 246 can be configured to receive information / input from a vehicle 202 component (such as the infotainment system 240, the vehicle sensing system 234, etc.). In addition, the transceiver 246 can transmit notifications (e.g., warning / alarm signals) to a vehicle 202 component (such as the infotainment system 240).

[0044] The processor 248 and the memory 250 may be the same or similar to the processor 216 and the memory 218, respectively. Specifically, the processor 248 may utilize the memory 250 to store programs and / or store data in code form to perform various aspects according to the present disclosure. The memory 250 may be a non-transitory computer-readable memory that stores vehicle power management program code.

[0045] In addition to user input, memory 250 may also be configured to store details of users ("authorized users," including user 125) who may be authorized to operate vehicle 202 and / or vehicle power system 244. For example, memory 250 may store images of authorized users (such as images of employees of a fleet operating company that may own vehicle 202), details associated with user devices (including user device 120) associated with authorized users, etc. Memory 250 may also store details associated with power consumption rates and / or capacities (or expected power consumption rates) of different accessories that may be connected to vehicle power system 244 to draw power.

[0046] In operation, the processor 248 may be configured to remotely obtain a user request from the mobile device 212 to control operation of the vehicle power system. In some aspects, the processor 248 may obtain the user request via the transceiver 246 and the network 214. The user request may include at least one of: a request to activate or deactivate the vehicle power system 244, a request to activate or deactivate a socket associated with the vehicle power system 244 (such as the socket 115), and a request to limit a discharge rate associated with the vehicle power system 244. In response to obtaining the user request, the processor 248 may be configured to control operation of the vehicle power system 244 based on the user request. In this manner, the processor 248 may be configured to provide remote authorization to the user 125 (via the mobile device 212) to control the vehicle power system 244. Aspects of the remote authorization may be combined with Figure 3 Come to understand.

[0047] Specifically, Figure 3 An example of an embodiment for controlling a vehicle power system 244 according to the present disclosure is depicted. Figure 3 In the exemplary aspect depicted in FIG. 1 , a user 125 may be using a vehicle 202 (specifically, a vehicle power system 244) to drain / draw water from a pool 302 via a motor 304. The motor 304 may be an external or auxiliary accessory that may be connected to the vehicle 202 to drain water from the pool 302. In some aspects, the vehicle power system 244 associated with the vehicle 202 may be configured to provide or supply power to the motor 304 to draw water from the pool 302.

[0048] In some aspects, the user 125 can be configured to remotely transmit instructions or requests to the transceiver 246 via the mobile device 212 to control the vehicle power system 244 when the motor 304 may be drawing water from the pool 302. For example, the user 125 can remotely transmit a request via the mobile device 212 to deactivate the vehicle power system 244 when the motor may be drawing water from the pool 302. In response to receiving the request, the transceiver 246 can send the request to the processor 248. The processor 248 can obtain the request and deactivate the vehicle power system 244 in response to obtaining the request. Thus, the user 125 can remotely access and control the vehicle power system 244 (and therefore the operation of the accessory 110) by using the mobile device 212 and the power management system 208.

[0049] In other aspects, the transceiver 246 can be configured to receive real-time vehicle power system usage, battery power, etc. from the vehicle sensing system 234 (e.g., a vehicle external power usage sensor), and can transmit real-time vehicle power system usage, battery power, etc. to the mobile device 212 and / or the server 220 for monitoring purposes. The user 125 can monitor the real-time vehicle power system usage, battery power, etc. via the mobile device 212. Based on the monitoring, the user 125 can transmit a request to deactivate the vehicle power system 244 or limit the discharge rate via the mobile device 212. The transceiver 246 can receive such a request and send the request to the processor 248. The processor 248 can obtain the request and deactivate the vehicle power system 244 or limit the discharge rate in response to obtaining the request. In some aspects, the processor 248 can be configured to indicate to the user 125 via the vehicle speaker system (e.g., an external sound exciter), the vehicle to the phone communication or the infotainment system 240 that the vehicle power system 244 can be deactivated.

[0050] In further aspects, the processor 248 can be configured to obtain user input associated with vehicle power system usage or operation via the transceiver 246. In this case, the user 125 can transmit the user input to the transceiver 246 via the mobile device 212, and the transceiver 246 can send the user input to the memory 250 for storage purposes and / or directly to the processor 248. When the user input is stored in the memory 250, the processor 248 can be configured to obtain the user input from the memory 250.

[0051] Processor 248 may control vehicle power system usage or operation based on user input. As described above, user input may include a set of rules for controlling the operation of the vehicle power system, which may ensure that vehicle power system 244 is not abused.

[0052] As an example of the above rule set, the user 125 can set a timer in the vehicle 202 to deactivate the vehicle power system 244 after a predefined duration of use. In this case, when (or after) the user 125 starts the vehicle power system 244 (e.g., to draw water from the pool 302 by using the motor 304), the user 125 can set a duration via the mobile device 212, after which the power management system 208 can deactivate the vehicle power system 244. For example, the user 125 can set the timer to 15 minutes to deactivate the vehicle power system 244. In this case, the processor 248 can deactivate the vehicle power system 244 after 15 minutes based on the rule set (e.g., duration of use) obtained from the mobile device 212.

[0053] As another example of a rule set, the user 125 may set a threshold energy consumption value for the vehicle power system 244. For example, the user 125 may set a threshold energy consumption value of 5 KW via the mobile device 212 to deactivate the vehicle power system 244. In this case, when the motor 304 draws 5 KW of power from the vehicle power system 244, the processor 248 may deactivate the vehicle power system 244.

[0054] As another example of a rule set, the user 125 may set a timer to start the vehicle power system 244 between the first timestamp and the second timestamp. For example, the user 125 may set a timer via the mobile device 212 to start the vehicle power system 244 within the allowed hours of operation, such as between 9 a.m. (i.e., the first timestamp) and 5 p.m. (i.e., the second timestamp). In this case, the processor 248 may start the vehicle power system 244 between 9 a.m. and 5 p.m.

[0055] As another example of a rule set, the user 125 may define or indicate via the mobile device 212 a geofenced area in which the vehicle power system 244 may be activated. For example, the user 125 may authorize activation of the vehicle power system 244 only when the vehicle 202 may be located at a work location. In this case, the processor 248 may obtain the real-time vehicle geographic location from the TCU 228, and may activate the vehicle power system 244 when the vehicle 202 may be located at a work location, and / or may not activate the vehicle power system 244 when the vehicle 202 may be located at any other location.

[0056] As described above, the processor 248 can be configured to obtain user input / rule sets from the memory 250 and / or the mobile device 212, and be configured to control the operation of the vehicle power system 244 (such as starting / deactivating / limiting the discharge rate of the vehicle power system 244) based on the user input / rule set.

[0057] As another example of a rule set, the user 125 may set a threshold associated with the state of charge (SoC) associated with the battery 242 via the mobile device 212, below which the vehicle power system 244 may not operate. For example, the user 125 may provide a rule set to deactivate the vehicle power system 244 when the SoC may be less than 30%. In this case, the processor 248 may obtain the real-time SoC level associated with the battery 242 from the VCU 206 and determine that the real-time SoC may be less than the threshold. In response to such a determination, the processor 248 may deactivate the vehicle power system 244.

[0058] In further aspects, the processor 248 can be configured to obtain input from the vehicle sensing system 234, such as when the vehicle power system 244 can operate or provide power to an external accessory (e.g., the motor 304). In some aspects, the processor 248 can obtain input from the vehicle sensing system 234 (such as a vehicle exterior camera) at a predetermined frequency via the transceiver 246. The processor 248 can be configured to monitor vehicle power system usage based on the input obtained from the vehicle sensing system 234 and determine whether the vehicle power system 244 can be used in an intended or authorized manner.

[0059] For example, processor 248 may obtain input from a vehicle exterior camera and determine whether vehicle power system 244 may be used by an authorized user, such as user 125 or a fleet employee. Specifically, processor 248 may compare an image of a user using vehicle power system 244 obtained from a vehicle exterior camera with pre-stored images of authorized users (which may be pre-stored in memory 250). Processor 248 may determine that an authorized user may be using vehicle power system 244 based on the comparison. For example, when an image of the user obtained from a vehicle exterior camera matches at least one pre-stored image of an authorized user, processor 248 may determine that the user using vehicle power system 244 may be an authorized user. On the other hand, if the images do not match, processor 248 may determine that the user is an unauthorized user.

[0060] Processor 248 may be configured to control vehicle power system usage / operation based on a determination of user authorization. For example, processor 248 may disable vehicle power system 244 when an unauthorized user may be using vehicle power system 244.

[0061] In further aspects, processor 248 can be configured to automatically pre-authorize vehicle power system use and can obtain input from a vehicle exterior camera and store it in server 220 or memory 250. In further aspects, processor 248 can authorize vehicle power system use when more than one person may be located near vehicle 202 (as determined using vehicle sensing system 234), which can reduce the likelihood of misuse.

[0062] Figure 4 Another example of an embodiment for controlling the operation of the vehicle power system 244 according to the present disclosure is depicted. In some aspects, for example, when the user 125 may be away from the vehicle 202, the user 125 can enable or allow other users or third parties (e.g., whose images may not be pre-stored in the memory 250) to use the vehicle power system 244. In such a scenario, the vehicle 202 can indicate that the vehicle power system 244 can be configured (or turned on) to receive requests from other users to power accessories (including the accessory 110). Such indications can include, for example, flashing of vehicle lights, audio signals output from vehicle speakers, etc.

[0063] In this case, when the user / third party desires to power an accessory, the user may transmit a request to use the vehicle power system 244 to the transceiver 246 via a user device associated with the user. The transceiver 246 may receive the request via the network 214 and may transmit the request to the processor 248. In other aspects, the user may also transmit the request by pressing or activating an “on” button / actuator associated with the vehicle power system 244 that may be provided on the vehicle 202.

[0064] exist Figure 4 In the exemplary aspect depicted in FIG. 2 , a user 402 (which may be the “other user” described above) may transmit a user request to use the vehicle power system 244 to the transceiver 246 via a user device 404. The user 402 may be different from the user 125, and thus the user device 404 may be different from the user device 120 or 212. The user request may include at least one of the following: information associated with a socket (e.g., the socket 115) that the user 402 may desire to use, a duration of use of the socket 115, information associated with an external accessory to be powered, expected power consumption, etc., and optionally, user personal information (e.g., a user image) and / or contact information.

[0065] The processor 248 may obtain the user request from the transceiver 246. In response to obtaining the user request, the processor 248 may obtain the user input / rule set from the memory 250. As described above, the user input (provided by the user 125) may include a rule set for controlling the operation / use of the vehicle control system. In response to obtaining the user input, the processor 248 may correlate the user request with the user input. The processor 248 may be configured to control the operation of the vehicle power system based on the correlation.

[0066] For example, user 402 may request to charge user device 404 for one hour between 4pm and 5pm. In response to receiving such a request, processor 248 may correlate the request with the user input. When the user input indicates that processor 248 may only enable phone charging for up to 30 minutes, processor 248 may deny the user request for one hour of charging. On the other hand, when the user input indicates that processor 248 may allow up to 2 hours of phone charging between 9am and 5pm, processor 248 may accept the user request and may activate vehicle power system 244 for user 402 to charge user device 404. In this manner, processor 248 may automatically control the operation of the vehicle power system based on user input that may be pre-stored in memory 250.

[0067] In some aspects, in response to obtaining the user request, the processor 248 may obtain authorization from the user 125 before enabling the user 402 to use the vehicle power system 244. For example, when the user 402 transmits a request to power a heavy accessory via the vehicle power system 244 and the processor 248 may not be able to determine (based on pre-stored user input / rule sets) whether such a request can be allowed or enabled, the processor 248 may transmit a request to obtain authorization for the received user request from the user 125 to the mobile device 212 via the transceiver 246. The processor 248 may also be configured to obtain authorization from the mobile device 212, and may control the operation of the vehicle power system based on the authorization. For example, the processor 248 may activate the vehicle power system 244 when the user 125 accepts the request, and may deny the user request (i.e., keep the vehicle power system 244 disabled) when the user 125 denies the user request.

[0068] In other aspects, the processor 248 can be configured to obtain input from the vehicle sensing system 234 (specifically, the vehicle external camera), for example, when the vehicle power system 244 can be started based on a user request. In some aspects, when the vehicle power system 244 can be started, the processor 248 can obtain input from the vehicle external camera at a predetermined frequency. The processor 248 can monitor the use of the vehicle power system based on the input obtained from the vehicle sensing system 234, and determine whether the vehicle power system 244 can be used in the manner indicated in the user request or whether the vehicle power system 244 may be misused. For example, when the user 402 indicates in the user request that the user 402 expects to charge the user device 404 via the vehicle power system 244, the processor 248 can obtain input from the vehicle external camera and determine whether the user 402 is using the vehicle power system 244 to actually power the user device 404 or any other accessories (such as a compressor). The processor 248 can be configured to control the operation of the vehicle power system based on such a determination. For example, if user 402 uses vehicle power system 244 instead of user device 404 to power the compressor (ie, improper use or system misuse), processor 248 may deactivate vehicle power system 244 .

[0069] In further aspects, the processor 248 can be configured to obtain input from the TCU 228, for example, when the vehicle power system 244 can be activated based on a user request. Specifically, the processor 248 can be configured to obtain BLE information from the TCU 228, and can estimate the accessory location based on the BLE information. The processor 248 can also be configured to determine whether the vehicle power system 244 can be used in the manner indicated in the user request based on the estimated accessory location. The processor 248 can be configured to control the operation of the vehicle power system based on such a determination.

[0070] In addition, the processor 248 can be configured to characterize an accessory (such as a user device 404) profile based on actual user device power consumption and expected power consumption (from a user 402 request and / or expected power consumption associated with different accessories that may be pre-stored in the memory 250). The processor 248 can use artificial intelligence (AI) or machine learning (ML) based techniques or algorithms (which can be stored in the memory 250) to determine whether the user 402 may be improperly using the vehicle power system 244 (i.e., system abuse) based on the characterization, and can control the operation of the vehicle power system 244 accordingly. For example, when the user 402 connects the user device 404 to the vehicle power system 244, the processor 248 can determine the actual power consumption from the vehicle power system 244. The processor 248 can also obtain the expected user device power consumption (which can be pre-stored in the memory 250) and determine the difference between the actual power consumption and the expected user device power consumption. In response to determining the difference, the processor 248 can determine whether the user 402 may be improperly using the vehicle power system 244. For example, if the difference may be greater than a predefined threshold, processor 248 may determine that user 402 may be improperly using vehicle power system 244 (eg, using vehicle power system 244 to power any device other than user device 404 ).

[0071] In another aspect, processor 248 can be configured to monitor actual accessory power consumption and can predict accessory maintenance. Processor 248 can also be configured to transmit the prediction to mobile device 212, user device 404, or server 220 so that the accessory can be repaired (if necessary). Specifically, processor 248 can transmit the prediction when actual accessory power consumption may be less than (or greater than) a threshold.

[0072] In another aspect, the processor 248 may obtain input from a vehicle exterior camera and determine whether the vehicle power system 244 can be actually used by the user 402 (or any other user) when the vehicle power system 244 can be activated based on a user request obtained from the user 402. Specifically, the processor 248 may use an artificial intelligence (AI) or machine learning (ML)-based technique or algorithm (which may be stored in the memory 250) to compare an image obtained from the vehicle exterior camera with an image of the user 402 (which may be included in the user 402's request). The processor 248 may determine based on the comparison that the vehicle power system 244 may be used by the user 402. The processor 248 may be configured to control the operation of the vehicle power system based on the determination. For example, when the processor 248 determines based on the comparison that the vehicle power system 244 may be used by another user (rather than the user 402), the processor 248 may deactivate the vehicle power system 244.

[0073] In further aspects, the processor 248 may also be configured to estimate the amount of power associated with the use of the vehicle power system in response to receiving a user request from the user 402 / user device 404. In some aspects, the processor 248 may estimate the amount of power based on the user request and a predefined charging rate that may be pre-stored in the memory 250. In this case, the predefined charging rate may be obtained from the user 125 and may be pre-stored in the memory 250. The processor 248 may be configured to transmit the estimated amount of power to the user device 404 to receive a confirmation from the user 402 to continue using the vehicle power system 244. The user device 404 may receive the estimated amount of power from the processor 248 and may provide a confirmation to the processor 248. The processor 248 may receive the confirmation from the user device 404 and may start the vehicle power system 244 for the requested duration based on the received confirmation.

[0074] In another aspect, the processor 248 can be configured to transmit the estimated power to the mobile device 212 to receive authorization for the estimated power and the user request. When the mobile device 212 transmits an authorization signal to the processor 248 (via the transceiver 246 and the network 214), the processor 248 can obtain authorization and can enable the user 402 to use the vehicle power system 244.

[0075] Figure 5 A flow chart depicting an example of a first method 500 for facilitating remote authorization of a vehicle power system 244 according to the present disclosure. Figures 1 to 4 The previous figures are used to describe Figure 5 The following process is exemplary and is not limited to the steps described below. Furthermore, alternative embodiments may include more or fewer steps shown or described herein, and may include the steps in an order different from the order described in the example embodiments below.

[0076] The method 500 begins at step 502. At step 504, the method 500 may include obtaining, by the processor 248, from the mobile device 212 via the transceiver 246 and the network 214, a first vehicle power system usage request. The processor 248 may obtain the first vehicle power system usage request from the mobile device 212 associated with the user 125, and the first vehicle power system usage request may be to control / use the vehicle power system 244. The first vehicle power system usage request may include at least one of: a request to activate or deactivate the vehicle power system 244, a request to activate or deactivate a socket associated with the vehicle power system 244, and a request to limit a discharge rate associated with the vehicle power system 244.

[0077] At step 506, method 500 may include controlling, by processor 248, operation of the vehicle power system based on the first vehicle power system usage request. For example, when vehicle power system 244 may be providing power to motor 304 to drain water from pool 302, when motor 304 may be drawing water from pool 302, user 125 may use mobile device 212 to remotely deactivate vehicle power system 244 (by transmitting the first vehicle power system usage request).

[0078] Method 500 may end at step 508 .

[0079] Figure 6 A flow chart depicting an example of a second method 600 for facilitating remote authorization of a vehicle power system 244 according to the present disclosure. Figures 1 to 5 The previous figures are used to describe Figure 6 The following process is exemplary and is not limited to the steps described below. Furthermore, alternative embodiments may include more or fewer steps shown or described herein, and may include the steps in an order different from the order described in the example embodiments below.

[0080] The method 600 starts at step 602. At step 604, the method 600 may include obtaining, by the processor 248, a second vehicle power system usage request from a third-party user device (e.g., a user device 404 associated with the user 402). The second vehicle power system usage request may include at least one of the following: information associated with a socket to be used (e.g., the socket 115), a duration of using the socket 115, information associated with an external accessory to be powered (e.g., the user device 404), expected power consumption, etc.

[0081] At step 606, the method 600 may include obtaining, by the processor 248, a vehicle power system usage rule set from the mobile device 212. The vehicle power system usage rule set may include rules / standards for controlling the use / operation of the vehicle power system. For example, the vehicle power system usage rule set may include at least one of the following: a rule set for starting the vehicle power system 244 within a predefined duration, a rule set for starting the vehicle power system 244 between a first timestamp and a second timestamp, a rule set for starting the vehicle power system 244 for a first predefined threshold energy usage value, a rule set for starting the vehicle power system 244 in a vehicle predefined geo-fenced area, a rule set for limiting a discharge rate associated with the vehicle power system 244, and a rule set for activating or deactivating a socket associated with the vehicle power system 244.

[0082] At step 608, method 600 may include correlating, by processor 248, the second vehicle power system usage request with the vehicle power system usage rule set. Specifically, processor 248 may correlate the second vehicle power system usage request with the vehicle power system usage rule set, and determine whether processor 248 may approve / accept or deny the second vehicle power system usage request based on the vehicle power system usage rule set provided by user 125.

[0083] At step 610 , method 600 may include controlling, via processor 248 , operation / usage of the vehicle power system based on the correlation.

[0084] Method 600 may end at step 612 .

[0085] In the above disclosure, reference has been made to the accompanying drawings that form a part of the above disclosure, which illustrate specific embodiments in which the present disclosure can be practiced. It should be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present disclosure. References to "one embodiment," "embodiment," "example embodiment," etc. in this specification indicate that the described embodiment may include specific features, structures, or characteristics, but each embodiment may not necessarily include the specific features, structures, or characteristics. In addition, such phrases do not necessarily refer to the same embodiment. In addition, when features, structures, or characteristics are described in conjunction with an embodiment, whether or not explicitly described, those skilled in the art will recognize such features, structures, or characteristics in conjunction with other embodiments.

[0086] In addition, where appropriate, the functions described herein may be performed in one or more of the following: hardware, software, firmware, digital components, or analog components. For example, one or more application specific integrated circuits (ASICs) may be programmed to perform one or more of the systems and programs described herein. Certain terms are used throughout the specification and claims to refer to specific system components. As will be appreciated by those skilled in the art, components may be referred to by different names. This document is not intended to distinguish between components that have different names but the same function.

[0087] It should also be understood that the word "example" as used herein is intended to be non-exclusive and non-limiting in nature. More specifically, the word "example" used herein indicates one of several examples, and it should be understood that no undue emphasis or preference is placed on the specific example described.

[0088] Computer-readable media (also referred to as processor-readable media) include any non-transitory (e.g., tangible) media that participate in providing data (e.g., instructions) that can be read by a computer (e.g., by a processor of a computer). Such media can take many forms, including but not limited to non-volatile media and volatile media. A computing device may include computer-executable instructions, where the instructions are executable by one or more computing devices (such as those listed above) and stored on a computer-readable medium.

[0089] With respect to the processes, systems, methods, heuristics, etc. described herein, it should be understood that although the steps of such processes, etc. have been described as occurring according to a certain ordered sequence, such processes may be practiced by performing the described steps in an order different from the order described herein. It should also be understood that certain steps may be performed simultaneously, other steps may be added, or certain steps described herein may be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating various embodiments and should in no way be construed as limiting the claims.

[0090] Therefore, it should be understood that the above description is intended to be illustrative rather than restrictive. Upon reading the above description, many embodiments and applications other than the examples provided will be apparent. The scope should not be determined with reference to the above description, but should be determined with reference to the entire scope of the appended claims and equivalents to which such claims are entitled. It is anticipated and expected that the technology discussed herein will develop in the future, and the disclosed systems and methods will be incorporated into such future embodiments. In short, it should be understood that the present application is capable of modification and change.

[0091] Unless explicitly indicated to the contrary in this article, all terms used in the claims are intended to be given their ordinary meanings as understood by the skilled person described herein. Specifically, unless the claim states an explicit limitation to the contrary, the use of singular articles such as "one", "the", "said" and the like should be interpreted as describing one or more of the indicated elements. Unless otherwise specifically stated or understood in other ways within the context when used, conditional language such as, in particular, "can", "may", "can" or "may" is generally intended to express that certain embodiments may include certain features, elements and / or steps, while other embodiments may not include certain features, elements and / or steps. Therefore, such conditional language is generally not intended to imply that one or more embodiments require each feature, element and / or step in any way.

[0092] In one aspect of the present invention, the method includes: obtaining a second vehicle power system usage request from a second user device, wherein the second user device is associated with a third party, and wherein the second vehicle power system usage request includes at least one of the following: information associated with a socket to be used, a duration of use of the socket, information associated with an external accessory to be powered, and an expected power consumption; correlating the second vehicle power system usage request with the vehicle power system usage rule set; and controlling the operation of the vehicle power system based on the correlation.

[0093] In one aspect of the present invention, the method includes: estimating the amount of power associated with vehicle power system usage based on the second vehicle power system usage request and a predefined charging rate; and transmitting the estimated amount of power and the second vehicle power system usage request to the first user device to receive authorization from the first user.

[0094] In one aspect of the invention, the method includes: obtaining the authorization from the first user device; and controlling the operation of the vehicle power system based on the authorization.

[0095] In one aspect of the present invention, the method includes: obtaining additional input from a vehicle sensor when the vehicle power system is started in response to obtaining a request to use the second vehicle power system; monitoring the use of the vehicle power system based on the additional input; determining improper use of the vehicle power system by the third party based on the monitoring; and deactivating the vehicle power system based on the determination of improper use of the vehicle power system by the third party.

[0096] According to the present invention, a non-transitory computer-readable storage medium is provided, on which instructions are stored, which, when executed by a processor, cause the processor to perform the following operations: obtain a vehicle power system usage rule set or a first vehicle power system usage request for using a vehicle power system from a first user device associated with a first user via a wireless communication network, wherein the vehicle power system is configured to transfer power from a vehicle battery to an external accessory connected to the vehicle power system; and control the operation of the vehicle power system based on the vehicle power system usage rule set or the first vehicle power system usage request.

Claims

1. A vehicle comprising: Battery; a vehicle power system configured to transfer power from the battery to an external accessory connected to the vehicle power system; as well as A processor, the processor being configured to: obtaining, from a first user device associated with a first user, a vehicle power system usage rule set or a first vehicle power system usage request for using the vehicle power system; as well as Operation of a vehicle power system is controlled based on the vehicle power system usage rule set or the first vehicle power system usage request.

2. The vehicle of claim 1 , wherein the first vehicle power system use request comprises at least one of: a request to activate or deactivate the vehicle power system, a request to activate or deactivate a socket associated with the vehicle power system, and a request to limit a discharge rate associated with the vehicle power system.

3. The vehicle of claim 1 , wherein the vehicle power system usage rule set comprises at least one of: a rule set for starting the vehicle power system within a predefined duration, a rule set for starting the vehicle power system between a first timestamp and a second timestamp, a rule set for starting the vehicle power system for a first predefined threshold energy usage value, a rule set for starting the vehicle power system in a predefined geo-fenced area of ​​the vehicle, a rule set for limiting a discharge rate associated with the vehicle power system, and a rule set for activating or deactivating a socket associated with the vehicle power system.

4. The vehicle of claim 1, wherein the processor is further configured to: obtaining input from a vehicle sensor when activating the vehicle power system; monitoring said vehicle power system usage based on said input; determining improper usage of a vehicle power system based on the monitoring; and The vehicle power system is disabled based on a determination of improper use of the vehicle power system. 5 . The vehicle of claim 4 , wherein the determination of improper use of the vehicle power system comprises determining that the vehicle power system is being used by an unauthorized user.

6. The vehicle of claim 1, wherein the processor is further configured to: obtaining a second vehicle power system usage request from a second user device, wherein the second user device is associated with a third party, and wherein the second vehicle power system usage request includes at least one of: information associated with an outlet to be used, a duration of use of the outlet, information associated with the external accessory to be powered, and an expected power consumption; associating the second vehicle power system usage request with the vehicle power system usage rule set; and Operation of the vehicle power system is controlled based on the correlation.

7. The vehicle of claim 6, wherein the processor is further configured to: estimating an amount of power associated with vehicle power system usage based on the second vehicle power system usage request and a predefined charging rate; and The estimated amount of power and the second vehicle power system usage request are transmitted to the first user device to receive authorization from the first user.

8. The vehicle of claim 7, wherein the processor is further configured to: obtaining the authorization from the first user device; and Operation of the vehicle power system is controlled based on the authorization.

9. The vehicle of claim 6, wherein the processor is further configured to: obtaining additional input from a vehicle sensor when activating the vehicle power system in response to obtaining the second vehicle power system use request; monitoring vehicle power system usage based on the additional input; determining, based on the monitoring, improper use of the vehicle power system by the third party; as well as The vehicle power system is disabled based on a determination of improper use of the vehicle power system by the third party.

10. The vehicle of claim 1, wherein the vehicle is further configured to: obtaining a real-time state of charge (SoC) associated with the battery; determining that the real-time SoC is less than a threshold; and Operation of the vehicle power system is controlled based on the real-time SoC being less than a threshold.

11. A method of controlling a vehicle power system of a vehicle, the method comprising: obtaining, by a processor, from a first user device associated with a first user via a wireless communication network, a vehicle power system usage rule set or a first vehicle power system usage request to use a vehicle power system, wherein the vehicle power system is configured to transfer power from a vehicle battery to an external accessory connected to the vehicle power system; as well as Operation of a vehicle power system is controlled by the processor based on the vehicle power system usage rule set or the first vehicle power system usage request.

12. The method of claim 11, wherein the first vehicle power system use request comprises at least one of: a request to activate or deactivate the vehicle power system, a request to activate or deactivate a socket associated with the vehicle power system, and a request to limit a discharge rate associated with the vehicle power system.

13. The method of claim 11, wherein the vehicle power system usage rule set comprises at least one of: a rule set for starting the vehicle power system within a predefined duration, a rule set for starting the vehicle power system between a first timestamp and a second timestamp, a rule set for starting the vehicle power system for a first predefined threshold energy usage value, a rule set for starting the vehicle power system in a predefined geo-fenced area of ​​the vehicle, a rule set for limiting a discharge rate associated with the vehicle power system, and a rule set for activating or deactivating a socket associated with the vehicle power system.

14. The method of claim 11, further comprising: obtaining input from a vehicle sensor when activating the vehicle power system; monitoring vehicle power system usage based on the input; determining improper usage of a vehicle power system based on said monitoring; as well as The vehicle power system is deactivated based on a determination of improper use of the vehicle power system.

15. The method of claim 14, wherein determining improper use of the vehicle power system comprises determining that the vehicle power system is being used by an unauthorized user.

Images