System and method for over-the-air application of vehicle operation rules on demand - Patents.com
The system allows vehicle owners to remotely set and enforce operational rules for shared vehicles, enhancing safety by restricting use and ensuring compliance with predefined conditions.
Patent Information
- Application Number
- JP2024015191
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2023-03-08
- Filing Date
- 2024-02-02
- Publication Date
- 2025-05-07
- Estimated Expiration
- 2044-02-02
AI Technical Summary
Vehicle owners face challenges in remotely applying operational rules to vehicles shared with others, particularly to restrict use or ensure safe driving practices.
A system and method that allow users to remotely set and implement operational rules for vehicles via a client terminal, using radio transmission to control various vehicle components based on conditions such as occupancy, location, and driving behavior.
Enables vehicle owners to restrict or control vehicle use on demand, preventing unsafe driving by careless or unfamiliar drivers, while allowing for flexible configuration of operational rules.
Smart Images

Figure 0007672525000001 
Figure 0007672525000002 
Figure 0007672525000003
Abstract
Description
[Technical field]
[0001] Systems and methods consistent with exemplary embodiments of the present disclosure relate to vehicles, and more particularly, to systems and methods for applying vehicle operation rules wirelessly on demand. [Background technology]
[0002] A vehicle may be shared by multiple people; for example, the owner of a vehicle may allow another person to borrow the vehicle. However, the owner may only intend for limited use of the vehicle for the borrower. For example, the owner may allow his or her child to borrow his or her car, or allow a garage attendant or parking attendant to use the car to park the car, for limited uses or purposes. 。
[0003] There is therefore a need for vehicle owners to be able to apply operating rules wirelessly on demand when allowing others to drive the vehicle. Summary of the Invention
[0004] According to embodiments, methods, systems, and devices are provided for applying vehicle behavior rules wirelessly on demand. By allowing a user to remotely configure vehicle behavior rules from a client terminal (e.g., a mobile phone) and implementing the behavior rules on the fly by wireless transmission to the vehicle, the vehicle owner can limit or otherwise control the use of the vehicle on demand. Can do.
[0005] According to an embodiment, a method may be provided that may be implemented by programming one or more processors at a client terminal to set operation rules for a vehicle. The method may include outputting a user interface for setting operation rules to control one or more components of the vehicle, receiving operation rule settings via user input to the user interface, and transmitting the received settings to a server for implementing the operation rules on the fly by wireless transmission to the vehicle.
[0006] Outputting the user interface may include outputting a user interface based on successful authentication of the user.
[0007] Successful authentication of a user may be verified based on one of a login procedure and / or biometric authentication.
[0008] The one or more components may include at least one of an infotainment system, temperature settings, volume settings, seat positioning, window locks, door locks, trunk locks, hood locks, passenger compartment locks, high beams, Bluetooth or hands-free phone functionality, and autonomous driving controls.
[0009] The operational rules may include conditions and controls to be performed based on the conditions. The conditions may also include at least one of number of occupants, location, distance traveled, duration of travel, time of day, detection of drowsiness, and detection of distracted driving.
[0010] The method may further include receiving a notification from the server that the condition has been met.
[0011] According to an embodiment, an apparatus may be provided for managing a configuration schema for setting operation rules for a vehicle, the apparatus may include at least one memory that stores computer-executable instructions; and at least one processor configured to execute the computer-executable instructions to output a user interface for setting operation rules to control one or more components of the vehicle, receive operation rule settings via user input to the user interface, and transmit the received settings to a server for implementing the operation rules on the fly by wireless transmission to the vehicle.
[0012] The at least one processor is further configured to execute the computer-executable instructions to output the user interface by outputting the user interface based on successful authentication of the user.
[0013] Additionally, the at least one processor is further configured to execute the computer-executable instructions to receive a notification from the server that the condition has been met.
[0014] Additional aspects will be set forth in part in the description that follows, and in part will be apparent from the description, or may be realized by practice of the presented embodiments of the present disclosure. [Brief description of the drawings]
[0015] The features, advantages and importance of preferred embodiments of the present disclosure will now be described with reference to the accompanying drawings, in which like reference numerals refer to like elements, and in which: [Figure 1] FIG. 1 illustrates a block diagram of an exemplary system for communicating with one or more vehicles using client terminals and a server according to one or more embodiments. [Diagram 2] FIG. 2 illustrates an example components diagram of a server according to one or more embodiments. [Diagram 3]FIG. 3 illustrates a flow diagram of an example method for setting operating rules for operating a vehicle according to one or more embodiments. [Figure 4] FIG. 4 illustrates a diagram of example components of a vehicle, according to one or more embodiments. [Diagram 5] FIG. 5 illustrates an example of an operational rule table according to one or more embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] The following detailed description of the preferred embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementation to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementation. Furthermore, one or more features or components of one embodiment may be incorporated in or combined with another embodiment (or one or more features of another embodiment). Furthermore, in the flowcharts and descriptions of operations provided below, it is understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed (at least partially) simultaneously, and the order of one or more operations may be switched.
[0017] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement the systems and / or methods is not a limitation of the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.
[0018] Although a particular combination of features is recited in a claim and / or disclosed herein, that combination is not intended to limit the disclosure of possible implementations. Indeed, many of the features may be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim set.
[0019] No element, act, or instruction used herein should be construed as critical or required unless expressly stated otherwise. Additionally, the articles "a" and "an" as used herein are intended to include one or more items and may be used interchangeably with "one or more." When only one item is intended, the term "a" or similar terms are used. Additionally, the terms "has," "have," "having," "include," "including," or the like as used herein are intended to be open-ended terms. Additionally, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise. Additionally, phrases such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood as including only A, only B, or both A and B.
[0020] References throughout this specification to "one embodiment," "an embodiment," "a non-limiting preferred embodiment," or similar terms mean that the particular feature, structure, or characteristic described in connection with the illustrated embodiment is included in at least one embodiment of the solution. Thus, the phrases "in one embodiment," "in an embodiment," "a non-limiting preferred embodiment," and similar terms throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0021] Furthermore, the described features, advantages, and characteristics of the present disclosure may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present disclosure.
[0022] Exemplary embodiments of the present disclosure provide a method and system for applying vehicle behavior rules wirelessly on demand. By allowing a user to remotely set vehicle behavior rules from a client terminal (e.g., a mobile phone) and implementing the behavior rules on the fly by wireless transmission to the vehicle, vehicle owners may limit or otherwise control vehicle usage on demand, thereby preventing unsafe driving by careless or inexperienced drivers.
[0023] Examples of vehicle components that may be controlled include, but are not limited to, one or more (e.g., all) of the following functions: infotainment system, sound system volume control, temperature control, seat positioning, windows, sunroof, locks, trunk access, hood access, vehicle speed, passenger compartment access, high beams, autonomous driving control, etc. Examples of operating rules include, but are not limited to, limits on the number of occupants, restrictions on the infotainment system, restrictions on the use of high beams, restricting access to the trunk or front hood (e.g., by keeping it locked), locking all doors except the driver's door and / or one or more passenger doors, etc.
[0024] Additionally, operational rules may include compound or conditional rules (e.g., if X then Y), such as limiting or restricting certain uses or operations of the vehicle based on certain conditions being met (e.g., disabling specified features of the vehicle based on location parameters (e.g., designated no-go zones and / or designated zones where use is permitted) or the number of occupants detected in the vehicle). Examples of conditional parameters include, but are not limited to, location, occupancy limits / number (e.g., detected by under-seat weight sensors, optical sensors, or other means), safe driving parameters (e.g., detected based on lane sway sensors, drowsiness detection, hard braking detection, following distance detection, distracted driving detection, etc.), driver alertness parameters, driving distance, driving time, time of day, etc. Location may be provided as a specific latitude and longitude, or as a range or area.
[0025] 1 illustrates a block diagram of an example system 100 for communicating with vehicles via a server and client terminals according to one or more embodiments. With reference to FIG. 1, the system 100 may include a server 110, a network 120, a client terminal 130, and a vehicle 140.
[0026] The server 110 may be communicatively connected to the client terminal 130 via the network 120. The server 110 and the client terminal 130 may be configured to send and receive information from each other. The server 110 may also be communicatively connected to the vehicle 140 via the network 120. The server 110 and the vehicle 140 may be configured to send and receive information from each other. Information may be exchanged between the server 110 and the client terminal 130 and / or vehicle 140 in the form of signals, network data, and any other suitable form.
[0027] Network 120 may include one or more data links that enable the transport of electronic data between server 110 and client terminal 130 and / or vehicle 140 (and components or systems contained therein). In this regard, network 120 may include one or more wired and / or wireless networks. For example, network 120 may include a cellular network (e.g., a fifth generation (5G) network, a long term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a wireless fidelity (WiFi) network, a private network, a Bluetooth® network, an ad-hoc network, an intranet, the Internet, an optical fiber-based network, or the like, and / or a combination of these or other types of networks. According to other embodiments, the server 110 may be configured to broadcast or multicast a signal containing information regarding operating rules for operating the vehicle. The signal may be transmitted to the vehicle 140 on demand or by over-the-air (OTA) transmission using the network 120.
[0028] Server 110 may include one or more devices capable of receiving, generating, storing, processing, computing, and / or providing information or data. According to an embodiment, server 110 may include a cloud server or a group of cloud servers (e.g., a server cluster, etc.). According to an embodiment, server 110 may be comprised of multiple servers, some of which may be deployed in different locations. For example, server 110 may include edge servers deployed close to vehicle 140, central servers deployed far from vehicle 140, and the like.
[0029] The client terminal 130 may include one or more devices (e.g., a mobile phone, a desktop computer, etc.) that may enable a user to input data. Additionally, the client terminal 130 may be configured to provide a user interface by a mobile phone application, a browser web page, or any other suitable means that allows a user to input data to set operating rules for operating the vehicle. The user interface may be provided to the client terminal 130 via the server 110. According to an embodiment, the user interface may be accessible only by authenticated / registered users (i.e., owners). Verification of the user authentication / registration may be performed by logging in (e.g., by transmitting the authenticated / registered user's username and password, or by biometric authentication). The user interface may be configured to transmit the entered user data to the server 110, which may then be transmitted to the vehicle 140.
[0030] 2 illustrates an example component diagram of a device 200 according to one or more embodiments. The device 200 may be used to implement the server 110 or the client terminal 130 in FIG. 1, and therefore descriptions corresponding to the device 200, the server 110, and the client terminal 130 may be applicable to one another unless expressly stated otherwise.
[0031] With reference to FIG. 2, device 200 may include a bus 210, a processor 220, a memory 230, a storage component 240, an input component 250, an output component 260, and a communication interface 270.
[0032] The bus 210 may include one or more components that allow communication between the components of the device 200. The processor 220 may be implemented in hardware, firmware, or a combination of hardware and software. The processor 220 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or another type of processing or computing component. In some implementations, the processor 220 may include one or more processors that are programmable to perform functions. The memory 230 may include a random access memory (RAM), a read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions used by the processor 220.
[0033] Storage component 240 may store information and / or software related to the operation and use of device 200. For example, storage component 240 may include a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, and / or solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium along with a corresponding drive.
[0034] Input components 250 may include one or more components (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone, etc.) that allow device 200 to receive information, such as via user input. Additionally or alternatively, input components 250 may include sensors that detect information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 260 may include one or more components (e.g., a display, a speaker, and / or one or more light emitting diodes (LEDs)) that provide output information from device 200.
[0035] Communications interface 270 may include transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communications interface 270 may allow device 200 to receive information from and / or provide information to another device (e.g., devices included in multiple vehicles, etc.). For example, communications interface 270 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.
[0036] Device 200 may perform one or more processes described herein in response to processor 220 executing software instructions stored by a non-transitory computer-readable medium, such as memory 230 and / or storage component 240. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spanning multiple physical storage devices.
[0037] Software instructions may be read into memory 230 and / or storage component 240 from another computer-readable medium or from another device via communications interface 270. When executed, the software instructions stored in memory 230 and / or storage component 240 may cause processor 220 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
[0038] FIG. 3 illustrates a flow diagram of an example method 300 for setting operating rules for operating a vehicle according to one or more embodiments.
[0039] 3, at operation S310, a user interface for setting one or more operating rules to control one or more components of the vehicle is output to a user. The user interface may be a web portal or may be provided from the server 110 to the client terminal 130 (e.g., a mobile phone application, a web browser page, etc.). According to an exemplary embodiment, to verify that the user is an authorized user (i.e., the owner of the vehicle), the user may be required to perform an authentication procedure before accessing the user interface. The authentication procedure may be, but is not limited to, a login username and password, biometric authentication, etc.
[0040] At operation S320, user input for setting the operation rule is received from the user interface. The user input may be received from any suitable means (e.g., physical or virtual keyboard, touch screen, etc.) by the client terminal 130. According to an exemplary embodiment, the user interface may allow the user to define customized operation rules. This may be done by allowing the user to select one or more relevant vehicle components (functions such as infotainment system, sound system volume control, seat positioning, windows, sunroof, locks, trunk access, hood access, vehicle speed, passenger compartment access, high beams, autonomous driving control, etc.) and select from predefined parameters (e.g., "on" or "off" options) and / or by defining specific parameters (defining a specific location, speed limit for the vehicle, etc.). The user may be allowed to further select predefined parameters that impose conditions for applying the operation rule (e.g., number of passengers / occupancy limit, accumulated driving time, usage time, driving distance, etc.). Alternatively, the user may only select from predefined operation rules. According to an exemplary embodiment, a service provider (e.g., a vehicle manufacturer) may provide an entire set of default operating rules to allow a user to immediately configure a vehicle. It should be understood that multiple operating rules may be combined into a single option for the user to enter. For example, a "learning mode" may be an option where the vehicle's speed is limited to be below a predetermined speed, and may include an option to autonomously guide the vehicle to a safe location if it is determined that the vehicle has left some designated location.
[0041] The user may also be able to implement or set operational rules in real time (e.g., real-time training or control). For example, the server 110 may send a notification / alert to the user via the client terminal 130 that the vehicle 140 meets some condition (which may be detected by a sensor in the vehicle). This condition may be pre-specified by the user in the user interface or may be triggered by default (e.g., if a speed limit is exceeded, a notification may be sent by default). Based on receiving the notification / alert, the user may be provided with an option to set operational rules.
[0042] For example, the vehicle's navigation system may detect that the operator of the vehicle 140 has left a designated location (which may have been pre-set by the user via a user interface). Thus, the vehicle 140 may send a signal to the server 110 indicating that the vehicle has left the designated location, and the server 110 may send a notification / alert to the user via the client terminal 130. The user may then be presented with options to set operation rules to restrict the operation of the vehicle. This may include, but is not limited to, putting the vehicle into a limp mode where the speed does not exceed a predetermined speed, limiting the vehicle speed to the speed limit of the current road the vehicle is traveling on, limiting the vehicle speed to some predetermined speed below the speed limit of the current road, outputting navigation controls instructing or guiding the user to return to the designated location, activating the vehicle's autonomous controls to return the vehicle to the designated location or to guide the vehicle to a safe parking location, disabling the infotainment system, etc.
[0043] At operation S330, the settings received for the operation rule from the user input at operation S320 are transmitted to the vehicle to implement the operation rule. Specifically, the client terminal 130 may transmit the received settings to the server 110. According to one embodiment, the settings may be processed by the server (e.g., to verify that the settings are valid, that the vehicle 140 is available to receive the settings, etc.). The server 110 may also store the received settings in memory / storage. The server 110 may then transmit the received settings for the operation rule to the vehicle 140. According to one embodiment, the vehicle 140 may process the received settings for the operation rule (e.g., to verify that the settings are received from a valid source, to convert the settings into a usable form, etc.). The vehicle 140 may also store the received settings in memory / storage. The vehicle 140 may then implement the operation rule.
[0044] For example, if a user sets an operational rule to restrict use of the infotainment system when multiple people are occupying the vehicle (e.g., when one or more passengers are in the vehicle in addition to the driver), after receiving the setting for the operational rule, the vehicle may receive sensor information from a weight sensor under the vehicle seat or image sensor information (processed to detect occupants) to determine whether a condition is met, i.e., whether one or more passengers are occupying the vehicle. Based on the determination, a controller in the vehicle may be configured to deactivate the infotainment system.
[0045] 4 illustrates a diagram of example components of a vehicle 400, according to one or more embodiments. Vehicle 400 may be similar to vehicle 140 in FIG. 1, and thus descriptions corresponding to vehicle 400 and vehicle 140 may be applicable to one another unless expressly stated otherwise.
[0046] Additionally, vehicle 400 may include any motorized and / or mechanical machine capable of carrying or transporting people and / or cargo, such as cars, trucks, motorcycles, buses, bicycles, mobility scooters, air vehicles, and the like.
[0047] 4, the vehicle 400 may include a bus 410, a processor 420, a memory 430, a storage component 440, a sensor 450, a vehicle control interface 460, and a communication interface 470. The general functions and roles of the bus 410, the processor 420, the memory 430, the storage component 440, and the communication interface 470 may be similar to the bus 210, the processor 220, the memory 230, the storage component 240, and the communication interface 270 described above with reference to FIG. 2, respectively. Therefore, redundant descriptions corresponding thereto may be omitted herein for brevity. Furthermore, it may be understood that the vehicle 400 may also include input components and output components having similar functions and roles to the input component 250 and the output component 260 without departing from the scope of the present disclosure.
[0048] 4, vehicle 400 may include at least one sensor 450 configured to detect, measure, and capture respective data (which may be referred to herein as "sensor data"), such as an accelerometer that measures and captures data associated with vehicle acceleration / deceleration, vehicle speed, and / or vehicle distance traveled, an image sensor (e.g., a camera, etc.) that detects and captures image data around or near the vehicle, a Light Detection and Ranging (LiDAR) sensor that detects and captures data associated with light in one or more light spectrums, such as the visible spectrum, the infrared spectrum, the ultraviolet spectrum, and / or any other light spectrum, an audio sensor (e.g., a microphone, etc.) that may detect and capture audio data inside and / or outside the vehicle, and a temperature sensor (e.g., a microphone, etc.) that may measure and capture data associated with temperature inside and / or outside the vehicle. The vehicle sensors may include temperature sensors to measure and capture data associated with the location, position, and / or orientation of the vehicle, location sensors (e.g., Global Positioning System (GPS), Inertial Measurement Unit (IMU), etc.) to measure and capture data associated with the location, position, and / or orientation of the vehicle, contact sensors (e.g., pressure detectors, impact detectors, etc.) to detect and capture data associated with parts of the vehicle and between objects, air sensors to measure and capture data associated with the air inside and / or outside the vehicle (e.g., oxygen levels, pollution levels, humidity levels, etc.), weight sensors to determine if an occupant is present (e.g., weight sensors deployed under the seat), and any other sensors suitable for deployment in the vehicle.
[0049] The sensor data may be stored (e.g., in memory 430 and / or storage component 440, etc.) in vehicle 400 permanently or semi-permanently for a predetermined period of time. The sensor data may be captured periodically, continuously, intermittently, or based on a trigger event (e.g., loud voices, horn activation, sudden deceleration or hard braking, sudden turns, etc.). Additionally, some or all of the sensor data may be processed by processor 420 before and / or after storage in a storage medium.
[0050] With reference to operation S330 in FIG. 3, the sensor data may be interpreted by the processor 420 as to whether it matches any of the conditions set by the user.
[0051] 4, the vehicle 400 may include a vehicle control interface 460. The vehicle control interface 460 may be used to control certain components used in vehicle operation (e.g., steering, vehicle speed, etc.) or vehicle accessories (e.g., infotainment system, seat settings, etc.). The vehicle control interface 460 may receive instructions from the processor 420 based on the operation rules, and for example, when a condition set by a user is triggered with reference to the operation rules, the vehicle control interface 460 may send control signals to control certain vehicle components based on the operation rules. According to one embodiment, the vehicle control interface 460 may operate directly in response to sensor data transmitted from the sensor 450.
[0052] 5 illustrates an example of an operation rule table 500 according to one or more embodiments. The operation rule table 500 may be implemented in any of the server 110, the client terminal 130, or the vehicle 140. For example, the operation rule table 500 may be transmitted from the client terminal 130 to the server 110 and then transmitted to the vehicle 140, 400. According to another embodiment, the operation rule table 500 may be stored and updated in the vehicle 140, 400 (e.g., in the memory 430 and / or the storage component 440, etc.) based on operation rules received from the server 110.
[0053] An operational rule may be stored based on which components it applies to, what the settings are, and what the conditions for applying the operational rule are (if applicable). For example, as shown in FIG. 5, a first operational rule may relate to the vehicle's infotainment system, the setting is "off" (e.g., this indicates that the radio in the vehicle may be turned on and / or music may be played), and the condition is if an occupant is present (this may be determined based on weight sensors in the vehicle's seats and the like). Another operational rule may not have any conditions. Still referring to FIG. 5, another operational rule may relate to Bluetooth or hands-free phone functionality, and the setting is "always on" without any conditions.
[0054] It should be understood that the behavior rules table 500 is an example of how data may be stored, and alternatively, each behavior rule may be stored as a separate data / file for each component. It should also be understood that the behavior rules shown in FIG. 5 are merely examples, and exemplary embodiments of the present disclosure are not limited thereto.
[0055] In view of the above, exemplary embodiments of the present disclosure provide a method and system for applying operational rules for a vehicle wirelessly on demand. By allowing a user to remotely set operational rules for a vehicle from a client terminal (e.g., a mobile phone) and implementing the operational rules on the fly by wireless transmission to the vehicle, a vehicle owner may limit or otherwise control the use of the vehicle on demand, thereby preventing unsafe driving by careless or inexperienced drivers.
[0056] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed herein is an example of an example approach. Based on design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying methods claim elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
[0057] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail of integration. Furthermore, one or more of the above components described above may be implemented as instructions stored in a computer-readable medium and executable by at least one processor (and / or may include at least one processor). The computer-readable medium may include a computer-readable non-transitory storage medium (or media) having computer-readable program instructions for causing a processor to perform operations.
[0058] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the above. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: portable computer diskettes, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), static random access memories (SRAM), portable compact disk read-only memories (CD-ROM), digital versatile disks (DVD), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge structures in grooves with instructions recorded on them, and any suitable combination of the above. As used herein, computer-readable storage media should not be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted over wires.
[0059] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium into each computing / processing device, or may be downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may comprise copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing / processing device.
[0060] The computer readable program code / instructions for performing the operations may be either source code or object code written in any combination of one or more programming languages, including assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, configuration data for integrated circuits, or object oriented programming languages such as Smalltalk, C++, or the like, and procedural programming languages such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or wide area network (WAN), or a connection to an external computer may be made (e.g., through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may execute computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry to perform an aspect or operation.
[0061] The computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing apparatus produce means for implementing the function / act specified in the block or blocks of the flowcharts and / or block diagrams. The computer-readable program instructions may also be stored in a computer-readable storage medium that may direct a computer, programmable data processing apparatus, and / or other device to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions that implement an aspect of the function / act specified in the block or blocks of the flowcharts and / or block diagrams.
[0062] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or another device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to generate a computer-implemented process, such that the instructions executing on the computer, other programmable apparatus, or other device implement the function / act specified in the block or blocks of the flowcharts and / or block diagrams.
[0063] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in the flowcharts or block diagrams may represent a module, segment, or portion of instructions comprising one or more executable instructions that implement a specified logical function. The methods, computer systems, and computer-readable media may include additional, fewer, different, or differently arranged blocks compared to those depicted in the figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed simultaneously or substantially simultaneously, or the blocks may be executed in the reverse order depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart illustrations, as well as combinations of blocks and / or flowchart illustrations of the block diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or acts or executes a combination of dedicated hardware and computer instructions.
[0064] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement the systems and / or methods is not a limitation of the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.
Claims
1. 1. A method implemented by one or more programmed processors in a client terminal for setting vehicle operation rules, the method comprising: outputting a user interface for setting operational rules to control one or more components of the vehicle; receiving a configuration of the operating rules via a user input to the user interface; transmitting the received configuration to a server for implementing the operating rules on-the-fly by wireless transmission to the vehicle; Including, The operation rule includes a condition and a control to be performed when the condition is satisfied based on the condition; The method of claim 1, wherein said implementation of said operational rules in said vehicle generates control signals for controlling particular vehicle components based on said operational rules if said condition is satisfied.
2. The method of claim 1 , wherein the outputting of the user interface comprises outputting the user interface based on successful authentication of the user.
3. The method of claim 2 , wherein the successful authentication of the user is verified based on one of a login procedure and / or biometric authentication.
4. 4. The method of claim 1, wherein the one or more components comprise at least one of an infotainment system, temperature settings, volume settings, seat positioning, window locks, door locks, trunk locks, hood locks, passenger compartment locks, high beams, Bluetooth or hands-free phone functionality, and autonomous driving controls.
5. The method of claim 1 , wherein the conditions comprise at least one of number of occupants, location, distance traveled, duration of travel, time of day, detection of drowsiness, and detection of distracted driving.
6. The method of claim 1 , further comprising receiving a notification from the server that the condition has been met.
7. A device for managing a configuration for setting operation rules for a vehicle, the device comprising: at least one memory storing computer executable instructions; At least one processor executing the computer-executable instructions to: Outputting a user interface for setting operational rules to control one or more components of the vehicle; receiving a configuration of the operating rules via a user input to the user interface; at least one processor configured to transmit the received configuration to a server for implementing the operating rules on the fly by wireless transmission to the vehicle; Equipped with The operation rule includes a condition and a control to be performed when the condition is satisfied based on the condition; The implementation of the operational rule in the vehicle generates a control signal that controls a particular vehicle component based on the operational rule if the condition is satisfied.
8. The apparatus of claim 7 , wherein the at least one processor is further configured to execute the computer-executable instructions to output the user interface based on successful authentication of the user.
9. The apparatus of claim 8 , wherein the successful authentication of the user is verified based on one of a login procedure and / or biometric authentication.
10. 10. The apparatus of claim 7, wherein the one or more components comprise at least one of an infotainment system, temperature settings, volume settings, seat positioning, window locks, door locks, trunk locks, hood locks, passenger compartment locks, high beams, Bluetooth or hands-free phone functionality, and autonomous driving controls.
11. The apparatus of claim 7 , wherein the conditions comprise at least one of number of occupants, location, distance traveled, duration of travel, time of day, detection of drowsiness, and detection of distracted driving.
12. The apparatus of claim 7 , wherein the at least one processor is further configured to execute the computer-executable instructions to receive a notification from the server that the condition has been met.
13. 1. A non-transitory computer-readable recording medium having stored thereon instructions executable by at least one processor, the non-transitory computer-readable recording medium causing the at least one processor to perform a method for outputting a user interface for setting operational rules for controlling one or more components of a vehicle, the non-transitory computer-readable recording medium comprising: The method comprises: receiving a configuration of the operating rules via a user input to the user interface; transmitting the received configuration to a server for implementing the operating rules on-the-fly by wireless transmission to the vehicle; Including, The operation rule includes a condition and a control to be performed when the condition is satisfied based on the condition; The implementation of the operating rule in the vehicle generates a control signal that controls a particular vehicle component based on the operating rule if the condition is satisfied.
14. The non-transitory computer-readable medium of claim 13 , wherein the outputting of the user interface comprises outputting the user interface based on successful authentication of the user.
15. The non-transitory computer-readable medium of claim 14 , wherein the successful authentication of the user is verified based on one of a login procedure and / or biometric authentication.
16. 16. The non-transitory computer readable storage medium of claim 13, wherein the one or more components comprise at least one of an infotainment system, temperature settings, volume settings, seat positioning, window locks, door locks, trunk locks, hood locks, passenger compartment locks, high beams, Bluetooth or hands-free phone functionality, and autonomous driving controls.
17. 16. The non-transitory computer readable medium of claim 15, wherein the conditions comprise at least one of number of occupants, location, distance traveled, duration of travel, time of day, detection of drowsiness, and detection of distracted driving.
Citation Information
Patent Citations
Portable terminal equipment
JP2002027040A
Navigation system
JP2004294263A
Remote control system and terminal device
JP2014045232A
Control system, communication apparatus, control method, and program
JP2018019313A
Sharing system
JP2019105881A