Mobile device interface for trailer backup assist

Abstract

Methods and apparatuses for "Mobile device interface for trailer backup assist" are disclosed. An example vehicle system includes a vehicle and a mobile device. The mobile device includes a touchscreen, a communication module, and a controller. The controller is to present, via the touchscreen, an interface for trailer backup assist, and detect a swipe while presenting the interface. The controller is also to command, via the communication module, the vehicle to move in a direction corresponding to the swipe, and continue to command the vehicle to move in the direction when a continuous track action extending from the swipe is detected.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to trailers, and more particularly, to mobile device interfaces for trailer backup assist. BACKGROUND

[0002] Many vehicles include features in which at least some power functions of the vehicle are controlled autonomously and / or semi-autonomously by the vehicle. For example, some vehicles include cruise control features (e.g., adaptive cruise control features) in which the vehicle controls acceleration and / or deceleration of the vehicle such that a speed of the vehicle is maintained. Some vehicles include parking assist features in which the vehicle autonomously and / or semi-autonomously controls power functions of the vehicle to park the vehicle into a parking space. Further, some vehicles include trailer backup assist features in which the vehicle autonomously and / or semi-autonomously controls power functions of the vehicle to back up a trailer coupled to the vehicle to a desired position. SUMMARY

[0003] The accompanying claims define the application. The summary of the disclosure sets forth aspects of the embodiments and is not to be used to limit the claims. Other implementations are contemplated in accordance with the techniques described herein, and are intended to fall within the scope of the application, as will become apparent to those of ordinary skill in the art upon examination of the following figures and detailed description.

[0004] Example embodiments of a mobile device interface for trailer backup assist are shown. The disclosed example vehicle system includes a vehicle and a mobile device. The mobile device includes a touchscreen, a communication module, and a controller. The controller is to present, via the touchscreen, an interface for trailer backup assist, and detect a swipe while presenting the interface. The controller is also to command, via the communication module, the vehicle to move in a direction corresponding to the swipe, and continue to command the vehicle to move in the direction when a continuous track action extending from the swipe is detected.

[0005] In some examples, the vehicle includes a hitch, a hitch sensor to monitor the hitch, and a second communication module to wirelessly communicate with the communication module of the mobile device. In some such examples, the controller is to present the interface for trailer backup assist in response to receiving a signal indicating that the hitch sensor detects that a trailer is coupled to the hitch of the vehicle. In some such examples, the controller is to present a second interface for remote parking assist in response to receiving a signal indicating that the hitch sensor detects that the trailer is not coupled to the hitch of the vehicle. In some such examples, the vehicle includes an autonomous unit, and the controller is to command the autonomous unit to perform trailer backup assist in response to detecting a user input while presenting the interface.

[0006] The disclosed example method includes presenting, via a touchscreen of a mobile device, an interface for trailer backup assistance, and detecting a swipe on the touchscreen while presenting the interface. The disclosed example method also includes commanding, via a communication module of the mobile device, a vehicle to move in a direction corresponding to the swipe, and continuing to command the vehicle to move in the direction when a continuous track action extending from the swipe is detected.

[0007] In some examples, the interface is presented in response to receiving a signal indicating that a trailer is coupled to the vehicle. Some examples also include commanding the vehicle to stop moving in response to detecting at least one of that the continuous track action has stopped and that the swipe has stopped prior to transitioning to the continuous track action. Some examples also include commanding the vehicle to adjust a vehicle speed in response to detecting a change in speed of the continuous track action. Some examples also include commanding the vehicle to adjust a turning radius in response to detecting a change in radius of the continuous track action. In some examples, commanding the vehicle to move includes commanding a straight forward movement in response to detecting an upward swipe, commanding a straight reverse movement in response to detecting a downward swipe, turning left in response to detecting a leftward swipe, and turning right in response to detecting a rightward swipe.

[0008] Some examples also include presenting, via the touchscreen, a second interface for remote parking assistance in response to receiving a signal indicating that the trailer is not coupled to the vehicle. Some such examples also include commanding an autonomous unit of the vehicle to perform remote parking assistance in response to detecting a user input while presenting the second interface.

[0009] Some examples also include commanding the vehicle to stop moving in response to detecting that the continuous track action is outside of an action track of the interface. Some such examples also include defining the action track based on a plurality of action paths received from a user via the touchscreen.

[0010] The disclosed example tangible computer-readable medium includes instructions that, when executed, cause a machine to present, via a touchscreen, an interface for trailer backup assistance and to detect a swipe on the touchscreen while presenting the interface. The instructions, when executed, also cause the machine to command, via a communication module, a vehicle to move in a direction corresponding to the swipe, and to continue to command the vehicle to move in the direction when a continuous track action extending from the swipe is detected.

[0011] In some examples, the instructions, when executed, cause the machine to present the interface in response to receiving a signal indicating that the trailer is coupled to the vehicle. In some examples, the instructions, when executed, further cause the machine to command the vehicle to stop moving in response to detecting at least one of that the continuous track motion has stopped and that the sliding has stopped prior to transitioning to the continuous track motion. In some examples, the instructions, when executed, further cause the machine to adjust a vehicle speed in response to detecting a change in speed of the continuous track motion. In some examples, the instructions, when executed, further cause the machine to adjust a turning radius in response to detecting a change in radius of the continuous track motion. BRIEF DESCRIPTION OF DRAWINGS

[0012] For a better understanding of the present application, reference can be made to the embodiments illustrated in the following drawings. The components in the drawings are not necessarily to scale, and related elements can be omitted, or in some instances can be exaggerated for the sake of clarity. Additionally, as known in the art, system components could be different from those illustrated in the drawings. Furthermore, in the drawings, like reference numerals can designate corresponding parts throughout the several views.

[0013] Figure 1 An example mobile device for trailer backup assist for a vehicle and trailer in accordance with the teachings herein is shown.

[0014] Figure 2 Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown. Figure 1

[0015] Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown. Figure 3 Figure 1 Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown.

[0016] Figure 4 Figure 1 Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown.

[0017] Figure 5 Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown. Figure 1

[0018] Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown. Figure 6 Figure 1 Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown.

[0019] Figure 7 Figure 1 Another example interface presented via a mobile device for trailer backup assist in accordance with the teachings herein is shown.

[0020] Figure 8 ​​​​Another example interface presented by a mobile device of Figure 1 Another example interface presented by a mobile device of

[0021] Figure 9 Another example interface presented by a mobile device of Figure 1 Another example interface presented by a mobile device of

[0022] Figure 10 is a block diagram of electronic components of a vehicle of Figure 1 is a block diagram of electronic components of a vehicle of

[0023] Figure 11 is a block diagram of electronic components of a vehicle of Figure 1 is a block diagram of electronic components of a vehicle of

[0024] Figure 12 is a flowchart for initiating trailer backup assist and remote parking assist according to the teachings herein. DETAILED DESCRIPTION

[0025] While the application can be susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. It should be understood that the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the application as defined by the appended claims.

[0026] Many vehicles include features in which at least some power functions of the vehicle are controlled autonomously and / or semi-autonomously by the vehicle. For example, some vehicles include cruise control features (e.g., adaptive cruise control features) in which the vehicle controls acceleration and / or deceleration of the vehicle such that a speed of the vehicle is maintained. Some vehicles include parking assist features in which the vehicle autonomously and / or semi-autonomously controls power functions of the vehicle to park the vehicle into a parking space. Further, some vehicles include trailer backup assist features in which the vehicle autonomously and / or semi-autonomously controls power functions of the vehicle to back up a trailer coupled to the vehicle to a desired location.

[0027] Some parking assist systems and trailer backup assist systems are remote systems in which the vehicle autonomously and / or semi-autonomously performs a powered function of the vehicle when an operator of the vehicle (e.g., a driver of the vehicle) has exited the vehicle cabin. For example, a remote parking assist system enables the operator to exit the vehicle before the vehicle is parked in a small parking spot (e.g., from which the operator can have difficulty exiting the vehicle cabin). A remote trailer backup assist system can enable the operator to clearly monitor the vehicle and trailer as the vehicle backs up the trailer to a desired location. In some cases, the vehicle can potentially continue to autonomously and / or semi-autonomously perform the powered function of the vehicle when it is not desired to do so. For example, the vehicle can potentially perform the powered function for too long after the operator presses a button on a mobile device to initiate the powered function. Moreover, if there is a lag in communication between the mobile device and the vehicle, the vehicle can potentially continue to perform the powered function in an undesirable manner.

[0028] Exemplary methods and apparatus disclosed herein include a remote trailer backup assist system configured to autonomously perform a powered function of a vehicle when a trailer is coupled to the vehicle. Moreover, some exemplary methods and apparatus disclosed herein include a remote parking assist system configured to autonomously perform a powered function of a vehicle when a trailer is not coupled to the vehicle. To prevent the vehicle from autonomously performing the powered function when the user does not intend to utilize the function, the system disclosed herein commands the vehicle to move as long as the user's mobile device is receiving continuous motion input.

[0029] Examples disclosed herein include a remote trailer backup assist system for controlling a vehicle while a trailer is attached. The system includes an application (also referred to as an app) operating on a mobile device that is used by an operator of the vehicle to control a powered function of the vehicle when a trailer is coupled to the vehicle. The system causes the vehicle to perform the powered function in response to the operator providing continuous motion input via a touchscreen of the mobile device. For example, if the user swipes up and continues in a circular motion, the vehicle moves forward in a straight path; if the user swipes down and continues in a circular motion, the vehicle moves in reverse in a straight path; if the user swipes right and continues in a circular motion, the vehicle turns right; and if the user swipes left and continues in a circular motion, the vehicle turns left. In some examples, the vehicle adjusts a turn radius as the operator adjusts a radius of the circular motion on the touchscreen of the mobile device and / or adjusts a vehicle speed as the operator adjusts a speed of the circular motion on the touchscreen of the mobile device.

[0030] As used herein, “trailer backup assist” refers to a system in which a vehicle performs autonomous and / or semi-autonomous power functions while a trailer is coupled to the vehicle to enable the vehicle to back up the trailer to a desired location (e.g., the desired location is identified via user input). As used herein, “trailer backup assist” refers to a system that is initiated and partially controlled by a driver located outside of the vehicle, in which the vehicle performs autonomous and / or semi-autonomous power functions while a trailer is coupled to the vehicle to enable the vehicle to back up the trailer to a desired location (e.g., identified via user input).

[0031] As used herein, “remote parking,” “vehicle remote parking assist,” “remote parking assist,” and “RePA” refer to a vehicle controlling power functions of the vehicle without direct manipulation or speed input from a driver to autonomously park the vehicle into a parking spot while the driver is located outside of the vehicle. For example, a remote parking assist system of an autonomous unit controls power functions of the vehicle to remotely park the vehicle into a parking spot upon initiation from a driver.

[0032] Referring to the drawings, Figure 1 An example vehicle 100 and an example trailer 102 in accordance with the teachings herein are shown. The vehicle 100 can be a standard gasoline-powered vehicle, a hybrid vehicle, an electric vehicle, a fuel cell vehicle, and / or any other type of vehicle of mobile tool. The vehicle 100 includes mobility-related components, such as a powertrain system having an engine, a transmission, a suspension, drive axles, and / or wheels, etc. The vehicle 100 can be semi-autonomous (e.g., the vehicle 100 controls some conventional power functions) or autonomous (e.g., power functions are controlled by the vehicle 100 without direct driver input).

[0033] In the illustrated example, the vehicle 100 includes a hitch 104 that enables the trailer 102 to be coupled to the vehicle 100. The trailer 102 is coupled to the vehicle 100 via the hitch 104 to transport objects from one location to another. For example, the trailer 102 is used to transport objects when storage areas (e.g., trunk, flatbed, back seat, etc.) within the vehicle 100 cannot accommodate those objects. The hitch 104 of the illustrated example (also referred to as a tow hitch, a tow bar, a trailer hitch, etc.) is positioned toward a rear of the vehicle 100. For example, the hitch 104 is coupled to and / or extends from a chassis of the vehicle 100. The hitch 104 is configured to receive a trailer connector of the trailer 102 to couple the trailer 102 to the vehicle 100. In other words, the hitch 104 enables the vehicle 100 to tow the trailer 102.

[0034] The vehicle 100 of the illustrated example includes a hitch sensor 106, a proximity sensor 108, a camera 110, a proximity sensor 112, and a camera 114. The hitch sensor 106 detects when the trailer 102 is coupled to the hitch 104 of the vehicle 100. For example, the hitch sensor 106 is a capacitive sensor, a piezoelectric sensor, a magnetoelastic sensor, and / or any other sensor configured to detect coupling of the trailer 102 to the hitch 104. The proximity sensor 108, the camera 110, the proximity sensor 112, and the camera 114 are sensing devices that monitor an area surrounding the vehicle 100. In the illustrated example, the proximity sensor 108 (also referred to as a rear proximity sensor) and the camera 110 (also referred to as a rear camera) are rear sensing devices that monitor an area and / or objects (e.g., the trailer 102) rearward of the vehicle 100. The proximity sensor 112 (also referred to as a front proximity sensor) and the camera 114 (also referred to as a front camera) are front sensing devices that monitor an area and / or objects forward of the vehicle 100. For example, the proximity sensor 108 is configured to detect the presence, relative position, and / or distance of an object located rearward of the vehicle 100. The camera 110 is configured to capture images and / or video used to detect the presence, relative position, and / or distance of an object located rearward of the vehicle 100. The proximity sensor 112 is configured to detect the presence, relative position, and / or distance of an object located forward of the vehicle 100. Further, the camera 114 is configured to capture images and / or video used to detect the presence, relative position, and / or distance of an object located forward of the vehicle 100.

[0035] The vehicle 100 of the illustrated example also includes a communication module 116. For example, the communication module 116 includes a wired or wireless network interface to enable communication with other devices and / or external networks. The external networks can be public networks, such as the Internet, private networks, such as an intranet, or a combination thereof, and can utilize various networking protocols now available or later developed including, but not limited to, TCP / IP based networking protocols. The communication module 116 also includes hardware (e.g., processors, memory, storage, antennas, etc.) and software to control the wired or wireless network interface. For example, the communication module 116 includes one or more communication controllers for cellular networks, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Code Division Multiple Access (CDMA).

[0036] In the illustrated example, communication module 116 includes hardware and firmware for establishing a wireless connection with a mobile device 118 (e.g., smartphone, wearable device, smartwatch, tablet, etc.) of a user 120 (e.g., an operator, such as a driver) of vehicle 100. For example, communication module 116 is a Wireless Personal Area Network (WPAN) module that wirelessly communicates with the user's keychain and / or mobile device (e.g., user 120's mobile device 118) via a short-range wireless communication protocol. In some examples, communication module 116 implements... and / or Low-power (BLE) protocol. and the BLE protocol in Technology Alliance maintained This is described in Volume 6 (and subsequent versions) of specification 4.0. Alternatively, communication module 116 is configured to communicate via... Near Field Communication (NFC), UWB (Ultra Wideband), and / or any other short-range and / or local wireless communication protocol (e.g., IEEE 802.11a / b / g / n / ac) enables the communication module 116 to be communicatively coupled to the mobile device 118 of the user 120.

[0037] The vehicle 100 illustrated also includes an autonomous unit 122 that performs autonomous and / or semi-autonomous driving maneuvers on the vehicle 100, such as trailer reversing assistance and / or remote parking assistance. For example, the autonomous unit 122 performs autonomous and / or semi-autonomous driving functions based at least in part on images and / or videos captured by cameras 110 and / or 114, data collected by proximity sensors 108 and / or 112, and / or instructions received from the mobile device 118.

[0038] In the illustrated example, vehicle 100 includes a vehicle assistance controller 124 that operates a remote assistance app on mobile device 118 to enable user 120 to activate remote parking assistance and / or remote trailer reversing assistance features of vehicle 100. Alternatively, mobile device 118 is configured to include vehicle assistance controller 124. For example, when user 120 activates the app on mobile device 118, vehicle assistance controller 124 is activated via the touchscreen of mobile device 118 (e.g., ...). Figure 10 The touchscreen 1006 presents the interface.

[0039] If the vehicle assistance controller 124 identifies that the trailer 102 is coupled to the vehicle 100, the vehicle assistance controller 124 presents an interface (e.g., a first interface) for operating trailer backup assistance. For example, the vehicle assistance controller 124 presents the interface for trailer backup assistance in response to receiving a signal indicating that the hitch sensor 106, the proximity sensor 108, and / or the camera 110 detected that the trailer 102 is coupled to the hitch 104 of the vehicle 100. When the interface for trailer backup assistance is presented via the mobile device 118, the vehicle assistance controller 124 detects when the user 120 provides a swipe (also referred to as a swipe input, swipe action, swipe action input) along the touchscreen of the mobile device 118. Upon detecting the swipe, the vehicle assistance controller 124 commands, via the communication module (e.g., the communication module 1008) of the mobile device 118, the autonomous unit 122 of the vehicle 100 to perform trailer backup assistance by moving in a direction corresponding to the swipe. Moreover, when a continuous action (e.g., a continuous track action) extending from the swipe is detected, the vehicle assistance controller 124 continues to command the autonomous unit 122 of the vehicle 100 to move in the direction. That is, as long as the touchscreen of the mobile device 118 detects a continuous input action comprising the swipe and the track action (e.g., a circular action) extending from the swipe, the vehicle assistance controller 124 commands the vehicle 100 to perform trailer backup assistance. Additionally, the vehicle assistance controller 124 commands the vehicle 100 to stop moving in response to detecting that the continuous input action has stopped (e.g., due to the user 120 removing his or her finger from the touchscreen, the user 120 holding his or her finger stationary on the touchscreen, a lag in communication between the communication module 116 and the mobile device 118, etc.). That is, the vehicle assistance controller 124 commands the vehicle 100 to stop moving in response to detecting that the continuous track action has stopped and / or the swipe has stopped prior to transitioning to the continuous track action. Figure 10

[0040] Moreover, if the vehicle assistance controller 124 identifies that the trailer 102 is not coupled to the vehicle 100, the vehicle assistance controller 124 presents an interface (e.g., a second interface) for operating remote parking assistance. For example, the vehicle assistance controller 124 presents the interface for remote parking assistance in response to receiving a signal indicating that the hitch sensor 106, the proximity sensor 108, and / or the camera 110 detected that the trailer 102 is not coupled to the hitch 104 of the vehicle 100. When the interface for remote parking assistance is presented via the mobile device 118, the vehicle assistance controller 124 detects when the user 120 provides an input via the touchscreen of the mobile device 118. Upon detecting the input via the touchscreen, the vehicle assistance controller 124 commands, via the communication module of the mobile device 118, the autonomous unit 122 of the vehicle 100 to perform a remote parking assistance power function.

[0041] ​Figure 2 An example interface 200 for remote trailer backup assist presented via the mobile device 118 is shown. The interface 200 depicts user input received via a touchscreen (e.g., touchscreen 1006) of the mobile device 118. For example, the user 120 interacts with the touchscreen of the mobile device 118 by drawing a path via a finger, stylus, etc. on the touchscreen. As shown, the user input includes a swipe 202 and a continuous action 204 extending from the swipe 202. For example, the vehicle assist controller 124 presents the swipe 202 and the continuous action 204 via the interface 200 upon detecting the respective path drawn via the user 120 on the touchscreen. In the example shown, the swipe 202 is a swipe-down action, and the continuous action 204 is a continuous track (e.g., circular) action in a clockwise direction. Alternatively, the continuous action 204 can be a continuous track action in a counterclockwise direction. Figure 10 Figure 2

[0042] In operation, as the touchscreen of the mobile device 118 continuously detects the swipe 202 and / or the continuous action 204, the vehicle assist controller 124 continuously commands the vehicle 100 to move backward in a straight path for trailer backup assist. That is, the vehicle assist controller 124 commands the autonomous unit 122 to move the vehicle 100 straight backward in response to detecting the swipe-down and / or the track action as a continuous action extending from the swipe-down. Further, the vehicle assist controller 124 commands the vehicle 100 to stop moving in response to the touchscreen detecting a stop and / or an interruption of the swipe 202 and / or the continuous action 204.

[0043] Figure 3 Another example interface 300 for remote trailer backup assist presented via the mobile device 118 is shown. The interface 300 depicts user input received via a touchscreen (e.g., touchscreen 1006) of the mobile device 118. As shown, the user input includes a swipe 302 and a continuous action 304 extending from the swipe 302. For example, the vehicle assist controller 124 presents the swipe 302 and the continuous action 304 via the interface 300 upon detecting the respective path drawn via the user 120 on the touchscreen as user input. In the example shown, the swipe 302 is a swipe-up action, and the continuous action 304 is a continuous track (e.g., circular) action in a clockwise direction. Alternatively, the continuous action 304 can be a continuous track action in a counterclockwise direction. Figure 10 Figure 3

[0044] ​​​​In operation, as the touchscreen of the mobile device 118 continuously detects the swipe 302 and / or the continuous action 304, the vehicle assist controller 124 continuously commands the vehicle 100 to move forward in a straight path for trailer backing assist. That is, the vehicle assist controller 124 commands the autonomous unit 122 to move the vehicle 100 straight forward in response to detecting the upward swipe and / or the track action extending as a continuous action from the upward swipe. Further, the vehicle assist controller 124 commands the vehicle 100 to stop moving in response to the touchscreen detecting a stop and / or an interruption of the swipe 302 and / or the continuous action 304.

[0045] Figure 4 Another example interface 400 for remote trailer backing assist presented via the mobile device 118 is shown. The interface 400 depicts user input received via the touchscreen (e.g., the touchscreen 1006) of the mobile device 118. As shown, the user input includes a swipe 402 and a continuous action 404 extending from the swipe 402. For example, the vehicle assist controller 124 presents the swipe 402 and the continuous action 404 via the interface 400 upon detecting a corresponding path drawn by the user 120 on the touchscreen as user input. In the illustrated example, the swipe 402 is a leftward swipe action, and the continuous action 404 is a continuous track (e.g., a circumference) action in a counterclockwise direction. Alternatively, the continuous action 404 can be a continuous track action in a clockwise direction. Figure 10 Figure 4 As shown, the user input includes a swipe 402 and a continuous action 404 extending from the swipe 402. For example, the vehicle assist controller 124 presents the swipe 402 and the continuous action 404 via the interface 400 upon detecting a corresponding path drawn by the user 120 on the touchscreen as user input. In the illustrated example, the swipe 402 is a leftward swipe action, and the continuous action 404 is a continuous track (e.g., a circumference) action in a counterclockwise direction. Alternatively, the continuous action 404 can be a continuous track action in a clockwise direction.

[0046] In operation, as the touchscreen of the mobile device 118 continuously detects the swipe 402 and / or the continuous action 404, the vehicle assist controller 124 continuously commands the vehicle 100 to turn left for trailer backing assist. That is, the vehicle assist controller 124 commands the autonomous unit 122 to turn the vehicle 100 left in response to detecting the leftward swipe and / or the track action extending as a continuous action from the leftward swipe. Further, the vehicle assist controller 124 commands the autonomous unit 122 to turn the vehicle 100 left while moving in reverse in response to determining that the vehicle is currently moving in reverse and / or was most recently moving in reverse prior to beginning the turning action. The vehicle assist controller 124 commands the autonomous unit 122 to turn the vehicle 100 left while moving forward in response to determining that the vehicle is currently moving forward and / or was most recently moving forward prior to beginning the turning action. Additionally, the vehicle assist controller 124 commands the vehicle 100 to stop moving in response to the touchscreen detecting a stop and / or an interruption of the swipe 402 and / or the continuous action 404.

[0047] Figure 5 Another example interface 500 for remote trailer backing assist presented via the mobile device 118 is shown. The interface 500 depicts user input received via the touchscreen (e.g., the touchscreen 1006) of the mobile device 118. As shown, the user input includes a swipe 502 and a continuous action 504 extending from the swipe 502. For example, the vehicle assist controller 124 presents the swipe 502 and the continuous action 504 via the interface 500 upon detecting a corresponding path drawn by the user 120 on the touchscreen as user input. In the illustrated example, the swipe 502 is a rightward swipe action, and the continuous action 504 is a continuous track (e.g., a circumference) action in a clockwise direction. Alternatively, the continuous action 504 can be a continuous track action in a counterclockwise direction.​Figure 10 user input received via a touchscreen (e.g., touchscreen 1006) of the mobile device 118. As shown, the user input includes a swipe 502 and a continuous action 504 extending from the swipe 502. For example, the vehicle assist controller 124 presents the swipe 502 and the continuous action 504 via the interface 500 upon detecting a corresponding path drawn by the user 120 on the touchscreen as user input. In the illustrated example, the swipe 502 is a swipe action to the right, and the continuous action 504 is a continuous track (e.g., a circular perimeter) action in a clockwise direction. Alternatively, the continuous action 404 can be a continuous track action in a counterclockwise direction. Figure 5

[0048] In operation, as the touchscreen of the mobile device 118 continuously detects the swipe 502 and / or the continuous action 504, the vehicle assist controller 124 continuously commands the vehicle 100 to turn right for trailer backup assist. That is, the vehicle assist controller 124 commands the autonomous unit 122 to turn the vehicle 100 right in response to detecting a swipe to the right and / or a track action extending from the swipe to the right as a continuous action. Further, the vehicle assist controller 124 commands the autonomous unit 122 to turn the vehicle 100 left while moving in reverse in response to determining that the vehicle is currently moving in reverse and / or was most recently moving in reverse prior to initiating the turning action. The vehicle assist controller 124 commands the autonomous unit 122 to turn the vehicle 100 left while moving forward in response to determining that the vehicle is currently moving forward and / or was most recently moving forward prior to initiating the turning action. Additionally, the vehicle assist controller 124 commands the vehicle 100 to stop moving in response to the touchscreen detecting a stop and / or an interruption of the swipe 502 and / or the continuous action 504.

[0049] Figure 6 Another example interface 600 for remote trailer backup assist presented via the mobile device 118 is shown. The interface 600 depicts user input received via a touchscreen (e.g., touchscreen 1006) of the mobile device 118. As shown, the user input includes a continuous action including a first portion 602 (e.g., a first continuous action portion, an outer continuous action portion) and a second portion 604 (e.g., a second continuous action portion, an inner continuous action portion) extending from the first portion 602. For example, the first portion 602 is a portion of the continuous action extending from a lateral swipe that initiates a turning action of the vehicle (e.g., swipe 402 initiating a left turn, swipe 502 initiating a right turn). As shown, the second portion 604 is a portion of the continuous action extending from the first portion 602 that initiates a direction of the turning action of the vehicle (e.g., a clockwise direction 606, a counterclockwise direction 608). Figure 10 Figure 6 Figure 6 ​​​As shown, the first portion 602 of the user input has a larger radius than the second portion 604, such that the continuous action forms a spiral pattern having a decreasing radius. For example, the vehicle assist controller 124 presents the first portion 602 and the second portion 604 of the continuous action via the interface 600 upon detecting the corresponding path drawn by the user 120 on the touchscreen as user input. In the illustrated example, the first portion 602 and the second portion 604 of the continuous action extend in a counterclockwise direction. Alternatively, the first portion 602 and the second portion 604 can extend in a clockwise direction.

[0050] In operation, the vehicle assist controller 124 commands the autonomous unit 122 to adjust the turning radius of the vehicle 100 based on the first portion 602 and the second portion 604. That is, because the turning radius of the vehicle 100 corresponds to the continuous action provided by the user 120, the vehicle assist controller 124 commands the vehicle 100 to adjust the turning radius in response to detecting a change in the radius of the continuous action. In the illustrated example, the second portion 604 of the continuous action has a smaller radius than the first portion 602 of the continuous action. In turn, when the continuous action transitions from the first portion 602 to the second portion 604, the vehicle assist controller 124 commands the autonomous unit 122 to decrease the turning radius of the vehicle 100.

[0051] Figure 7 Another example interface 700 for remote trailer backup assist presented via the mobile device 118 is shown. The interface 700 depicts user input received via the touchscreen (e.g., touchscreen 1006) of the mobile device 118. As shown, the user input includes a continuous action that includes a first portion 702 (e.g., a first continuous action portion, an inner continuous action portion) and a second portion 704 (e.g., a second continuous action portion, an outer continuous action portion) extending from the first portion 702. For example, the first portion 702 is a portion of the continuous action extending from a lateral swipe that initiates a turning action of the vehicle (e.g., swipe 402 initiating a left turn, swipe 502 initiating a right turn). As shown, the first portion 702 of the user input has a smaller radius than the second portion 704, such that the continuous action forms a spiral pattern having an increasing radius. For example, the vehicle assist controller 124 presents the first portion 702 and the second portion 704 of the continuous action via the interface 700 upon detecting the corresponding path drawn by the user 120 on the touchscreen as user input. In the illustrated example, the first portion 702 and the second portion 704 of the continuous action extend in a counterclockwise direction. Alternatively, the first portion 702 and the second portion 704 can extend in a clockwise direction. Figure 10 Figure 7 Figure 7

[0052] ​​​In operation, the vehicle assistance controller 124 commands the autonomous unit 122 to adjust the turning radius of the vehicle 100 based on the first portion 702 and the second portion 704. That is, because the turning radius of the vehicle 100 corresponds to the continuous motion provided by the user 120, the vehicle assistance controller 124 commands the vehicle 100 to adjust the turning radius in response to detecting a change in the radius of the continuous motion. In the illustrated example, the radius of the second portion 704 of the continuous motion is greater than the radius of the first portion 702 of the continuous motion. In turn, when the continuous motion transitions from the first portion 702 to the second portion 704, the vehicle assistance controller 124 commands the autonomous unit 122 to increase the turning radius of the vehicle 100.

[0053] Additionally or alternatively, the vehicle assistance controller 124 commands the autonomous unit 122 to adjust the speed at which the vehicle 100 travels based on the speed of the user input detected via the touchscreen of the mobile device 118. That is, the vehicle assistance controller 124 commands the autonomous unit 122 to adjust the vehicle speed of the vehicle 100 in response to detecting a change in the speed of the user 120 drawing a swipe (e.g., swipe 202, swipe 302, swipe 402, swipe 502) and / or the continuous motion extending from the swipe (e.g., continuous motion 204, continuous motion 304, continuous motion 404, continuous motion 504, first portion 602, second portion 604, first portion 702, second portion 704) on the touchscreen of the mobile device 118. For example, the vehicle assistance controller 124 causes the vehicle 100 to speed up in response to detecting that the user 120 is providing input on the touchscreen at an accelerated rate, and / or causes the vehicle 100 to slow down in response to detecting that the user 120 is providing input on the touchscreen at a decelerated rate.

[0054] Figure 8 Another example interface 800 presented via the touchscreen of the mobile device 118 is shown. The interface 800 includes a motion track 802 in which the user 120 is to draw a continuous motion to command the autonomous unit 122 to move the vehicle 100. For example, the vehicle assistance controller 124 presents the interface 800 including the motion track 802 for remote parking assistance and / or remote trailer backing assistance. The vehicle assistance controller 124 sends instructions to the autonomous unit 122 of the vehicle 100 to perform a power function of the vehicle 100 for remote parking assistance and / or remote trailer backing assistance in response to detecting that the user 120 is providing a continuous motion (e.g., continuous track motion) within the motion track 802 on the touchscreen. The vehicle assistance controller 124 sends instructions to cause the vehicle 100 to stop moving in response to detecting that the continuous motion provided by the user 120 has stopped and / or been interrupted. Further, the vehicle assistance controller 124 sends instructions to cause the vehicle 100 to stop moving in response to detecting that the continuous motion provided by the user 120 has extended outside of the motion track 802 of the interface 800.

[0055] Figure 9 Another example interface 900 presented via the touchscreen of the mobile device 118 is shown. The interface 900 includes a plurality of action paths 902 received from the user 120 via the touchscreen of the mobile device 118 and used to define the position and shape of the action trail 802 of the interface 800. For example, to enable the user 120 to define the shape and position of the action trail 802 of the interface 800, the user 120 draws a first action path 902a, a second action path 902b, and a third action path 902c. In the illustrated example, the touchscreen of the mobile device 118 detects the first action path 902a, the second action path 902b, and the third action path 902c provided by the user 120 in one continuous action that begins at an initial point 904. The vehicle assistance controller 124 determines the action trail 802 of the interface 800 based on the position and shape of each action path 902 of the interface 900 (e.g., by averaging the position and / or shape of the action paths 902 together). In some examples, the variance between the action paths 902 is used to determine the width of the action trail 802. For example, the smaller the width of the action trail 802, the more similar the shape and position of each action path 902 to one another, and the greater the width of the action trail 802, the less similar the shape and position of each action path 902 to one another.

[0056] Figure 10 is a block diagram of an electronic component 1000 of the mobile device 118. As shown, the electronic component 1000 includes a controller or processor 1002, a memory 1004, a touchscreen 1006, and a communication module 1008. Figure 10

[0057] In the illustrated example, the processor 1002 is structured to include the vehicle assistance controller 124. The processor 1002 can be any suitable processing device or group of processing devices, such as but not limited to a microprocessor, a microcontroller-based platform, an integrated circuit, one or more field-programmable gate arrays (FPGAs), and / or one or more application-specific integrated circuits (ASICs). The memory 1004 can be a volatile memory (e.g., a RAM, including a non-volatile RAM, a magnetic RAM, a ferroelectric RAM, etc.), a non-volatile memory (e.g., a magnetic disk storage, a flash memory, an EPROM, an EEPROM, a memristor-based non-volatile solid-state memory, etc.), a non-changeable memory (e.g., an EPROM), a read-only memory, and / or a high-capacity storage device (e.g., a hard disk drive, a solid-state drive, etc.). In some examples, the memory 1004 includes multiple types of memory, particularly volatile memory and non-volatile memory.

[0058] ​Memory 1004 is a computer readable medium on which one or more sets of instructions, such as software for operating the methods of the present disclosure, can be embedded. The instructions, in which a or more methods or logic as described herein can be embodied, may, for example, reside completely, or at least partially, within memory 1004, any one or more of the computer readable media, and / or within processor 1002 during execution thereof.

[0059] The terms "non-transitory computer-readable medium" and "computer-readable medium" include a single medium or multiple media, such as a centralized or distributed database, and / or associated caches and servers, which store one or more sets of instructions. Further, the terms "non-transitory computer- readable medium" and "computer-readable medium" include any tangible medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a system to perform any one or more of the methodologies of the present disclosure. As used herein, the term "computer readable medium" is expressly defined to include any type of computer readable storage device and / or storage disk and to exclude propagating signals.

[0060] Touch screen 1006 of the illustrated example provides an interface between user 120 and mobile device 118 to enable user 120 to utilize trailer backup assist and / or remote parking assist of vehicle 100. Touch screen 1006 is, for example, a resistive touch screen, a capacitive touch screen, and / or any other type of touch screen that displays output information to user 120 of mobile device 118 and tactilely receives input information therefrom. In some examples, electronic components 1000 of mobile device 118 also include other input devices (e.g., buttons, knobs, microphones, etc.) and / or output devices (e.g., speakers, LEDs, etc.) to receive input information from and / or provide output information to user 120 of mobile device 118. User 120 interacts with touch screen 1006 to utilize trailer backup assist and / or remote parking assist via mobile device 118. Based on input received from user 120 via touch screen 1006, communication module 1008 of mobile device 118 wirelessly communicates with communication module 116 of vehicle 100 to initiate power functions of vehicle 100 to perform trailer backup assist and / or remote parking assist.

[0061] In addition, communication module 1008 includes a wired or wireless network interface to enable communication with other devices and / or external networks. The external network may be a public network, such as the Internet; a private network, such as an intranet; or a combination thereof, and may utilize various networking protocols available now or developed later, including but not limited to TCP / IP-based networking protocols. Communication module 1008 also includes hardware (e.g., processor, memory, storage device, antenna, etc.) and software for controlling the wired or wireless network interface. For example, communication module 1008 includes one or more communication controllers for cellular networks (such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Code Division Multiple Access (CDMA)). In the illustrated example, communication module 1008 includes a Wireless Personal Area Network (WPAN) module configured to wirelessly communicate with communication module 116 of vehicle 100 via a short-range wireless communication protocol. In some examples, communication module 1008 implements... and / or Low-power (BLE) protocol. and the BLE protocol in Technology Alliance maintained This is described in Volume 6 (and subsequent versions) of specification 4.0. Alternatively, the communication module 1008 is configured to communicate via... Near Field Communication (NFC), UWB (Ultra Wideband), and / or any other short-range and / or local wireless communication protocol (e.g., IEEE 802.11a / b / g / n / ac) enables wireless communication, allowing the communication module 1008 to be communicatively coupled to the communication module 116 of the vehicle 100.

[0062] Figure 11 This is a block diagram of the electronic component 1100 of vehicle 100. (Example) Figure 11 As shown, the electronic component 1100 includes an on-board computing platform 1102, a communication module 116, a camera 1104, a sensor 1106, an electronic control unit (ECU) 1108, and a vehicle data bus 1110.

[0063] The in-vehicle computing platform 1102 includes a microcontroller unit, controller, or processor 1112 and a memory 1114. In some examples, the processor 1112 of the in-vehicle computing platform 1102 is structured to include the vehicle auxiliary controller 124. Alternatively, in some examples, the vehicle auxiliary controller 124 is incorporated into another electronic control unit (ECU) with its own processor 1112 and memory 1114. The processor 1112 can be any suitable processing device or group of processing devices, such as but not limited to a microprocessor, a microcontroller-based platform, an integrated circuit, one or more field-programmable gate arrays (FPGAs), and / or one or more application-specific integrated circuits (ASICs). The memory 1114 can be volatile memory (e.g., RAM, including non-volatile RAM, magnetic RAM, ferroelectric RAM, etc.), non-volatile memory (e.g., disk storage, flash memory, EPROM, EEPROM, memristor-based non-volatile solid-state memory, etc.), unalterable memory (e.g., EPROM), read-only memory, and / or a high capacity storage device (e.g., a hard disk drive, a solid-state drive, etc.). In some examples, the memory 1114 includes multiple types of memory, particularly volatile memory and non-volatile memory.

[0064] The memory 1114 is a computer readable medium on which one or more sets of instructions, such as software for operating the methods of the present disclosure, can be embedded. The instructions can embody one or more methods or logic as described herein. For example, the instructions reside completely, or at least partially, within the memory 1114, any one or more of the computer readable media, and / or within the processor 1112 during execution of the instructions.

[0065] The camera 1104 of the illustrated example collects images and / or video of the area surrounding the vehicle 100. For example, the camera 1104 captures images and / or video that are used by the autonomous unit 122 to facilitate performance of autonomous and / or semi-autonomous driving maneuvers of the vehicle 100. As Figure 3 As illustrated, the camera 1104 includes a camera 110 and a camera 114. The camera 110 collects images and / or video of the area rearward of the vehicle 100, and the camera 114 collects images and / or video of the area forward of the vehicle 100.

[0066] The sensors 1106 are arranged in and around the vehicle 100 to monitor attributes of the vehicle 100 and / or the environment in which the vehicle 100 is located. One or more sensors 1106 can be installed to measure attributes of the environment surrounding the vehicle 100 outside. Additionally or alternatively, one or more sensors 1106 can be installed within the vehicle cabin of the vehicle 100 or in the vehicle body (e.g., engine compartment, wheel well, etc.) of the vehicle 100 to measure attributes of the vehicle 100 inside. For example, the sensors 1106 include accelerometers, odometers, tachometers, pitch and yaw sensors, wheel speed sensors, microphones, tire pressure sensors, biometric sensors, and / or any other suitable type of sensor.

[0067] In the illustrated example, the sensors 1106 include a hitch sensor 106, a proximity sensor 108, and a proximity sensor 112. The hitch sensor 106 detects whether the trailer 102 is coupled to the vehicle 100 via the hitch 104. The proximity sensor 108 monitors an area behind the vehicle 100 to detect the presence, location, and / or distance of an object (e.g., the trailer 102) behind the vehicle 100. Further, the proximity sensor 112 monitors an area in front of the vehicle 100 to detect the presence, location, and / or distance of an object in front of the vehicle 100. The proximity sensors (e.g., the proximity sensor 108, the proximity sensor 112) include radar sensors that detect and locate objects via radio waves, lidar sensors that detect and locate objects via laser, ultrasonic sensors that detect and locate objects via ultrasonic waves, and / or any other type of sensor configured to detect and locate nearby objects.

[0068] ECUs 1108 monitor and control subsystems of vehicle 100. For example, ECUs 1108 are discrete sets of electronics that include their own circuitry (e.g., integrated circuits, microprocessors, memory, storage devices, etc.) and firmware, sensors, actuators, and / or mounting hardware. ECUs 1108 communicate and exchange information via a vehicle data bus (e.g., vehicle data bus 1110). Additionally, ECUs 1108 can transmit properties (e.g., states of ECUs 1108, sensor readings, control states, error and diagnostic codes, etc.) to and / or receive requests from each other. For example, vehicle 100 can have seventy or more ECUs 1108 that are located at various locations around vehicle 100 and are communicatively coupled by vehicle data bus 1110. In the illustrated example, ECUs 1108 include autonomous unit 122 and speed control unit 1116. Autonomous unit 122 controls, for example, the performance of autonomous and / or semi-autonomous driving maneuvers of vehicle 100 based at least in part on images and / or video captured by camera 1104, data collected by sensors 1106, and / or instructions received from mobile device 118. Speed control unit 1116 controls, for example, the speed at which vehicle 100 moves autonomously and / or semi-autonomously based on instructions received from mobile device 118.

[0069] Vehicle data bus 1110 communicatively couples communication module 116, in-vehicle computing platform 1102, camera 1104, sensors 1106, and ECUs 1108. In some examples, vehicle data bus 1110 includes one or more data buses. Vehicle data bus 1110 can be implemented in accordance with a Controller Area Network (CAN) bus protocol defined by International Standards Organization (ISO) 11898-1, a Media Oriented Systems Transport (MOST) bus protocol, a CAN Flexible Data (CAN-FD) bus protocol (ISO 11898-7), and / or a K-Line bus protocol (ISO 9141 and ISO 14230-1), and / or an Ethernet bus protocol IEEE 802.3 (2002 and later). TM

[0070] Figure 12 is a flowchart representation of an example method 1200 for initiating trailer backup assist and remote parking assist in accordance with the teachings herein. Figure 12 is a flowchart representation of machine readable instructions stored in a memory, such as memory 1114 of Figure 11 is a flowchart representation of machine readable instructions stored in a memory, such as memory 1114 of Figure 11 is a flowchart representation of machine readable instructions stored in a memory, such as memory 1114 of Figure 10 is a flowchart representation of machine readable instructions stored in a memory, such as memory 1114 of Figure 1 and Figure 11 ​An exemplary vehicle assistance controller 124. Although referenced Figure 12 The flowchart shown describes an exemplary procedure, but many other methods implementing the exemplary processor 1002 and / or the exemplary vehicle assistance controller 124 can be used alternatively. For example, the execution order of the combo boxes can be rearranged, changed, eliminated, and / or executed to perform method 1200. Furthermore, because of the combination... Figures 1 to 11 The components disclosed method 1200, so some of the functions of those components will not be described in detail below.

[0071] Initially, at box 1202, the vehicle assistance controller 124 determines whether the remote assistance app is active on the mobile device 118. If the vehicle assistance controller 124 determines that the remote assistance app is inactive, method 1200 remains at box 1202. Otherwise, if the vehicle assistance controller 124 determines that the remote assistance app is active, method 1200 proceeds to box 1204.

[0072] At block 1204, vehicle assistance controller 124 determines whether mobile device 118 is communicatively coupled to vehicle 100. For example, vehicle assistance controller 124 determines whether communication module 1008 of mobile device 118 is wirelessly coupled to communication module 116 of vehicle 100. In response to vehicle assistance controller 124 determining that mobile device 118 and vehicle 100 are not communicatively coupled, method 1200 returns to block 1202. Otherwise, in response to vehicle assistance controller 124 determining that mobile device 118 and vehicle 100 are communicatively coupled, method 1200 proceeds to block 1206. At block 1206, vehicle assistance controller 124 sends an app status to vehicle 100 indicating that the remote assistance app of mobile device 118 is activated for use by user 120. For example, vehicle assistance controller 124 sends the app status from communication module 1008 of mobile device 118 to communication module 116 of vehicle 100.

[0073] At frame 1208, the hook-up sensor 106, proximity sensor 108, camera 110, and / or any other sensor or camera of vehicle 100 detect whether trailer 102 is attached to hook-up 104 of vehicle 100. In response to the sensors and / or cameras detecting that trailer 102 is attached to vehicle 100, method 1200 proceeds to frame 1210.

[0074] At block 1210, the autonomous unit 122 initiates remote trailer backup assist for the vehicle 100. In addition, the communication module 116 of the vehicle 100 sends a signal to the communication module 1008 of the mobile device 118 indicating that remote trailer backup assist has been initiated for the vehicle 100. At block 1212, the vehicle assist controller 124 presents a trailer backup assist interface (e.g., interface 200, interface 300, interface 400, interface 500, interface 600, interface 700, interface 800) via the touchscreen 1006 of the mobile device 118.

[0075] At block 1214, the vehicle assist controller 124 determines whether the touchscreen 1006 has received a continuous motion input, including a swipe (e.g., swipe 202, swipe 302, swipe 402, swipe 502) and / or a continuous motion extending from the swipe (e.g., continuous motion 204, continuous motion 304, continuous motion 404, continuous motion 504, first portion 602, second portion 604, first portion 702, second portion 704) from the user 120 of the mobile device 118. In response to the vehicle assist controller 124 determining that the touchscreen 1006 has not received a continuous motion input, the method 1200 returns to block 1202. Otherwise, in response to the vehicle assist controller 124 determining that the touchscreen 1006 is receiving a continuous motion input, the method 1200 proceeds to block 1216.

[0076] At block 1216, the vehicle assist controller 124 sends an instruction to the communication module 116 via the communication module 1008 to instruct the autonomous unit 122 of the vehicle 100 to perform a power function in a direction corresponding to the swipe input for remote trailer backup assist. At block 1218, the autonomous unit 122 performs the power function in a direction corresponding to the swipe input for remote trailer backup assist. The method 1200 returns to block 1214 until the continuous motion input detected by the touchscreen 1006 ceases, discontinues, and / or extends beyond a designated motion trajectory (e.g., motion trajectory 802).

[0077] Returning to block 1208, the method 1200 proceeds to block 1220 in response to the vehicle sensors and / or camera detecting that the trailer 102 is not coupled to the vehicle 100. At block 1220, the autonomous unit 122 initiates remote parking assist for the vehicle 100. In addition, the communication module 116 of the vehicle 100 sends a signal to the communication module 1008 of the mobile device 118 indicating that remote parking assist has been initiated for the vehicle 100. At block 1222, the vehicle assist controller 124 presents a remote parking assist interface (e.g., interface 800) via the touchscreen 1006 of the mobile device 118.

[0078] At block 1224, the vehicle assist controller 124 determines whether the touchscreen 1006 has received a continuous motion input from the user 120 of the mobile device 118. In response to the vehicle assist controller 124 determining that the touchscreen 1006 has not received a continuous motion input, the method 1200 returns to block 1202. Otherwise, in response to the vehicle assist controller 124 determining that the touchscreen 1006 is receiving a continuous motion input, the method 1200 proceeds to block 1226. At block 1226, the vehicle assist controller 124 sends an instruction to the communication module 116 via the communication module 1008 to command the autonomous unit 122 of the vehicle 100 to perform a power function for remote parking assistance. At block 1228, the autonomous unit 122 performs the power function for remote parking assistance. The method 1200 returns to block 1224 until the continuous motion input detected by the touchscreen 1006 ceases, interrupts, and / or extends beyond a designated motion trajectory (e.g., the motion trajectory 802).

[0079] In this application, the use of the transitional phrase "comprising" is intended to be open- ended and non-limiting. The use of the terms "including" and "having" are also intended to be open-ended and non-limiting. The use of "including" and "having" also

[0080] The above embodiments, and particularly any "preferred" embodiments, are possible examples of implementations and merely set forth the possible examples of implementations merely to explain the principles of the present application. Many changes and modifications within the spirit and principles of the disclosed technology can be made by those skilled in the art, which change and modifications to be included within the scope of the disclosure and within the scope of the claims below. The above detailed description has shown, by way of example, implementations of the present application.

[0081] According to the present application, there is provided a vehicle system having: a vehicle; and a mobile device comprising: a touchscreen; a communication module; and a controller to present, via the touchscreen, an interface for trailer reversing assistance; to detect a swipe while presenting the interface; to command, via the communication module, the vehicle to move in a direction corresponding to the swipe; and to continue to command the vehicle to move in the direction when a continuous trajectory motion extending from the swipe is detected.

[0082] According to an embodiment, the vehicle includes a hitch, a hitch sensor for monitoring the hitch, and a second communication module for wireless communication with a communication module of a mobile device.

[0083] According to an embodiment, the controller presents an interface for trailer backup assist in response to receiving a signal indicating that the hitch sensor detects that a trailer is coupled to the hitch of the vehicle.

[0084] According to an embodiment, the controller presents a second interface for remote parking assist in response to receiving a signal indicating that the hitch sensor detects that a trailer is not coupled to the hitch of the vehicle.

[0085] According to an embodiment, the vehicle includes an autonomous unit, and the controller commands the autonomous unit to perform trailer backup assist in response to detecting a user input while presenting the interface.

[0086] According to the present invention, there is provided a vehicle system method of presenting an interface for trailer backup assist via a touchscreen of a mobile device; detecting a swipe on the touchscreen while presenting the interface; commanding a vehicle to move in a direction corresponding to the swipe via a communication module of the mobile device; and continuing to command the vehicle to move in the direction when a continuous track action extending from the swipe is detected.

[0087] According to an embodiment, the interface is presented in response to receiving a signal indicating that a trailer is coupled to the vehicle.

[0088] According to an embodiment, there is provided a vehicle system method including commanding a vehicle to stop moving in response to detecting at least one of that a continuous track action has stopped and that a swipe has stopped prior to transitioning to the continuous track action.

[0089] According to an embodiment, there is provided a vehicle system method including commanding a vehicle to adjust a vehicle speed in response to detecting a change in speed of a continuous track action.

[0090] According to an embodiment, there is provided a vehicle system method including commanding a vehicle to adjust a turning radius in response to detecting a change in radius of a continuous track action.

[0091] According to an embodiment, there is provided a vehicle system method of commanding a vehicle to move, and including commanding a straight forward movement in response to detecting an upward swipe; commanding a straight reverse movement in response to detecting a downward swipe; commanding a left turn in response to detecting a leftward swipe; and commanding a right turn in response to detecting a rightward swipe.

[0092] According to an embodiment, there is provided a vehicle system method including presenting a second interface for remote parking assist via a touchscreen in response to receiving a signal indicating that a trailer is not coupled to the vehicle.

[0093] According to an embodiment, a vehicle system method is provided that includes commanding an autonomous unit of a vehicle to perform remote parking assistance in response to detecting a user input while presenting a second interface.

[0094] According to an embodiment, a vehicle system method is provided that includes commanding a vehicle to stop moving in response to detecting a continuous track action outside of an action track of an interface.

[0095] According to an embodiment, a vehicle system method is provided that includes defining an action track based on a plurality of action paths received from a user via a touchscreen.

[0096] According to the present invention, a vehicle system is provided having a tangible computer-readable medium including instructions that, when executed, cause a machine to present an interface for trailer backup assistance via a touchscreen; detect a swipe on the touchscreen while presenting the interface; command a vehicle to move in a direction corresponding to the swipe via a communication module; and continue to command the vehicle to move in the direction when a continuous track action extending from the swipe is detected.

[0097] According to an embodiment, the instructions, when executed, cause a machine to present the interface in response to receiving a signal indicating that a trailer is coupled to the vehicle.

[0098] According to an embodiment, the instructions, when executed, further cause a machine to command the vehicle to stop moving in response to at least one of detecting that the continuous track action has stopped and that the swipe has stopped prior to transitioning to the continuous track action.

[0099] According to an embodiment, the instructions, when executed, further cause a machine to adjust a vehicle speed in response to detecting a change in speed of the continuous track action.

[0100] According to an embodiment, the instructions, when executed, further cause a machine to adjust a turning radius in response to detecting a change in radius of the continuous track action.

Claims

1. A vehicle system comprising: vehicle; as well as Mobile device, the mobile device comprising: touchscreen; Communication module; and Controller, the controller is used for: The touchscreen displays an interface for trailer reversing assistance; Detect swiping when the interface is displayed; Detect the sliding direction; The communication module commands the vehicle to move in a direction corresponding to the sliding direction; and When a continuous track motion adjacent to and extending from the slide is detected, the vehicle is commanded to continue moving in the direction corresponding to the slide direction, wherein the turning radius is adjusted based on the continuous track motion, wherein the continuous track motion includes a first motion portion extending from the slide, a second motion portion extending from the first motion portion, and a third motion portion extending from the second motion portion, the radii of the first motion portion, the second motion portion, and the third motion portion being different.

2. The vehicle system of claim 1, wherein the vehicle includes a hitch, a hitch sensor for monitoring the hitch, and a second communication module for wirelessly communicating with the communication module of the mobile device.

3. The vehicle system of claim 2, wherein the controller, in response to receiving a signal instructing the hook-up sensor to detect that the trailer is attached to the vehicle, presents the interface for trailer reversing assistance.

4. The vehicle system of claim 2, wherein the controller, in response to receiving a signal instructing the hook-up sensor to detect that the trailer is not connected to the hook-up of the vehicle, presents a second interface for remote parking assistance.

5. The vehicle system of claim 2, wherein the vehicle includes an autonomous unit, and the controller, in response to detecting user input when the interface is presented, commands the autonomous unit to perform the trailer reversing assistance.

6. A method for a vehicle, comprising: The interface for trailer reversing assistance is displayed via the touchscreen of a mobile device; Detect swiping on the touchscreen when the interface is displayed; Detect the sliding direction; The vehicle is commanded to move in a direction corresponding to the sliding direction via the communication module of the mobile device; as well as When a continuous track motion adjacent to and extending from the slide is detected, the vehicle is commanded to continue moving in the direction corresponding to the slide direction, wherein the turning radius is adjusted based on the continuous track motion, wherein the continuous track motion includes a first motion portion extending from the slide, a second motion portion extending from the first motion portion, and a third motion portion extending from the second motion portion, the radii of the first motion portion, the second motion portion, and the third motion portion being different.

7. The method of claim 6, wherein the interface is presented in response to receiving a signal indicating that a trailer is connected to the vehicle.

8. The method of claim 6, further comprising: The continuous track motion is detected to have stopped when at least one of the following occurs: the user's finger is removed from the touchscreen, the user's finger remains stationary on the touchscreen, or there is a communication lag between the communication module and the mobile device; in response to at least one of the following: the continuous track motion has stopped and the sliding has stopped before transitioning to the continuous track motion, the vehicle is commanded to stop moving.

9. The method of claim 6, further comprising: In response to the detection of a speed change in the continuous track movement, the vehicle is commanded to adjust its speed.

10. The method of claim 6, further comprising: In response to detecting a continuous change in motion from the second action portion to the third action portion, the vehicle is commanded to adjust its turning radius, the continuous change in motion corresponding to a continuous change in the radius from the second action portion to the third action portion.

11. The method of claim 6, wherein commanding the vehicle to move comprises: In response to detecting an upward slide, it commands the device to move forward in a straight line. In response to detecting a downward slide, a command is given to move in the opposite direction in a straight line; In response to detecting a leftward swipe, a command is given to turn left; as well as In response to detecting a rightward swipe, a command is given to turn right.

12. The method of claim 6, further comprising: In response to receiving a signal indicating that the trailer is not connected to the vehicle, a second interface for remote parking assistance is displayed via the touchscreen.

13. The method of claim 12, further comprising: In response to detecting user input when the second interface is presented, the autonomous unit of the vehicle is commanded to perform the remote parking assistance.

14. The method of claim 6, further comprising: In response to detecting that the continuous track motion is outside the motion trajectory of the interface, the vehicle is commanded to stop moving.

15. The method of claim 14, further comprising: The motion trajectory is defined based on multiple motion paths received from the user via the touchscreen.

Images