Head unit remote control

Abstract

A head unit control system (102) for controlling at least one vehicle function in a vehicle (200) from a user equipment, UE (300), the at least one vehicle function involving the use of a set of vehicle devices (210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the head unit control system (102) is configured to selectively have, for each vehicle function, an onboarding / offboarding mode switchable (111) between an onboarding mode and an offboarding mode based on a reception, from a remote entity (400), of onboarding state information indicating that the UE (300) has been authenticated, so as to switch to the onboarding mode, the head unit control system (102) comprising a controller (130) to control the at least one vehicle function, wherein in the onboarding mode, a control connection is activated (111) through which the head unit control system (102) interfaces both the UE (300) and the at least one vehicle function, so that the controller (130) receives control data from the UE (300) and controls the at least one vehicle function based on the control data received from the UE (300), and in the offboarding mode, the control connection is deactivated.

Description

[0001] Head unit remote control

[0002] Description

[0003] Vehicle functions can sometimes be controlled by user equipments (UEs), e.g. mobile phones. However, it is difficult to render a UE compliant with a particular vehicle.

[0004] Summary

[0005] In accordance to an example, there is provided a head unit control system for controlling at least one vehicle function in a vehicle from a user equipment, UE , the at least one vehicle function involving the use of a set of vehicle devices, the set of vehicle devices having at least one vehicle device, wherein the head unit control system is configured to selectively have, for each vehicle function, an onboarding / off- boarding mode switchable between an onboarding mode and an offboarding mode based on a reception, from a remote entity , of onboarding state information indicating that the UE has been authenticated, so as to switch to the onboarding mode, the head unit control system comprising a controller to control the at least one vehicle function, wherein in the onboarding mode, a control connection is activated through which the head unit control system interfaces both the UE and the at least one vehicle function, so that the controller receives control data from the UE and controls the at least one vehicle function based on the control data received from the UE, and in the offboarding mode, the control connection is deactivated.

[0006] In accordance to an example, there is provided a head unit control remote provider for remotely controlling a vehicle function in a vehicle, configured for: authenticating a user equipment, UE, by comparing UE’s authenticating information, received from the UE, with authenticating information associated with a vehicle; and, in case of positive authentication: providing the UE with a user interface or code executable by the UE causing the code to provide a user interface to remotely control at least one vehicle function; receiving from the UE control data inputted through the user interface; providing the control data to the head unit control system, so that the head unit control system controls the at least one vehicle function.

[0007] In accordance to an example, there is provided a user equipment, UE , for controlling at least one vehicle function through a head unit control system installed in a vehicle, the UE including: a user interface for interacting with a user; an acquiring unit for acquiring authenticating information received from an output unit controlled by the head unit control system ; an authentication unit to perform, through a remote connection , a remote authentication process providing the authenticating information to a head unit remote control provider , and to receive an authorization result from the head unit remote control provider; a remote control unit to control the at least one vehicle function through the remote connection and the head unit control provider, the at least one vehicle function involving the use of a set of vehicle devices, the set of vehicle devices having at least one vehicle device, wherein the UE is configured to selectively have, for each vehicle function, an onboarding / offboarding mode switchable between an onboarding mode and an offboarding mode based on the authorization based on the authorization result, so as to switch to the onboarding mode, wherein in the onboarding mode, a control connection is activated through which the UE interfaces with the remote entity to control the at least one function, and in the offboarding mode, the control connection is deactivated.

[0008] In accordance to an example, there is provided a method for a head unit control system controlling at least one vehicle function in a vehicle from a user equipment, UE , the at least one vehicle function involving the use of a set of vehicle devices , the set of vehicle devices having at least one vehicle device, wherein the head unit control system selectively has, for each vehicle function, an onboarding / offboarding mode switchable between an onboarding mode and an offboarding mode based on a reception, from a remote entity, of onboarding state information indicating that the UE has been authenticated, so as to switch to the onboarding mode, the method including controlling the at least one vehicle function, wherein in the onboarding mode, a control connection is activated through which the head unit control system interfaces both the UE and the at least one vehicle function, so as to receive control data from the UE and control the at least one vehicle function based on the control data received from the UE , and in the offboarding mode, the control connection is deactivated.

[0009] In accordance to an example, there is provided a method for remotely controlling a vehicle function in a vehicle, comprising: authenticating a user equipment, UE, by comparing UE’s authenticating information, received from the UE, with authenticating information associated with a vehicle; and, in case of positive authentication: controlling providing the UE with a user interface or code executable by the UE causing the code to provide a user interface to remotely control at least one vehicle function; receiving from the UE control data inputted through the user interface; providing the control data to the head unit control system, so that the head unit control system controls the at least one vehicle function.

[0010] In accordance to an example, there is provided a method for controlling at least one vehicle function through a head unit control system installed in a vehicle, the method including: interacting with a user through a user interface at a user equipment, UE; acquiring authenticating information received from an output unit controlled by the head unit control system; performing, through a remote connection , a remote authentication process providing the authenticating information to a head unit remote control provider , and receiving an authorization result from the head unit remote control provider; controlling the at least one vehicle function through the remote connection and the head unit control provider, the at least one vehicle function involving the use of a set of vehicle devices, the set of vehicle devices having at least one vehicle device, wherein the involves selectively having, for each vehicle function, an onboarding / offboarding mode switchable between an onboarding mode and an off- boarding mode based on the authorization based on the authorization result, so as to switch to the onboarding mode, wherein in the onboarding mode, a control connection is activated through which the UE interfaces with the remote entity to control the at least one function, and in the offboarding mode, the control connection is deactivated.

[0011] Figures

[0012] Figs. 1A, IB, 1C, 2, 3, and 4 show examples according to the present technique.

[0013] Examples

[0014] Fig. 1A shows an example according to the invention. A vehicle environment (e.g., a car 200) is shown. The vehicle 200 has a head unit control system 102, which may include (or may be included in) the vehicle’s dashboard. The vehicle 200 has an internal space (e.g., car cockpit 220). The vehicle 200 has multiple vehicle units (e.g. vehicle devices) 210a, 210b, 210c, 210d which may be understood as forming a set 210 of vehicle units. The set 210 of vehicle units may have at least one vehicle unit (e.g., a plurality of vehicle units 210a, 210b, 210c, 210d). Examples of vehicle units 210a, 210b, 210c, 210d will be provided later. However, it is already anticipated that in at least one example they can be devices associated to the heating, ventilation, air conditioning (HVAC) of the vehicle, and can therefore include sensors and / or actuators (such as temperature sensors current sensor, and so on, as well as ventilators, heating actuators, air conditioning actuators, refrigerators, and so on). In addition or as an alternative, the set 210 of vehicle units 210a-210d may be or include media devices (e.g., displays, loudspeakers, and so on) and / or at least one sensor device(s) (e.g., at least one microphone(s)). The vehicle units 210a- 210d may in addition or alternatively include at least one counting device (e.g., for taxi, cabs, and other commercial vehicles), and at least one positioning device (which may provide the position of the vehicle 200), at least one speed indicator (e.g., obtained from the engine or other mechanical parts of the vehicle 200), at least one timer (e.g., actioned by the taxi driver), and so on.

[0015] The set 210 of vehicle units 210a-210d may be involved for the use in at least one vehicle function. A vehicle function may be, for example, the function of air conditioning and / or temperature regulating (and therefore the set 210 of vehicle units 210a-210d may include units of the HVAC). A vehicle function can be the rendering of media content (e.g. audio and / or video content), the set 210 of vehicle units 210a-210d may mostly include at least one display device(s) and / or at least one loudspeaker(s)). A vehicle function can be accounting of the taxi operations (and in that case, the set 210 of vehicle units 210a-210d may include at least one positioning unit(s), at least one counter (s), at least one timer, and so on). Other functions to be performed in the vehicle 200 may be performed. Therefore, for each function, a predetermined number of vehicle units 210a-210d may be known a priori.

[0016] Fig. 1 A shows that a user equipment (UE) 300 (e.g. mobile device). The UE 300 may be property of a particular human user. The UE 300 can be positioned within the internal space 210 of the vehicle 200. (It is possible, in some examples, that the UE 300 is placed in direct proximity of the vehicle 200, despite being directly outside of it.) In principle, the UE 300 is not necessarily pre-associated to the vehicle 200. It may be that the owner of the UE 300 is not the owner of the vehicle 200, but of his friend. It will be shown how the UE 300 can be admitted to control at least one vehicle function, and in particular, the vehicle units 210a-210d.

[0017] The head unit control system 102 may include a controller 130 (e.g. local controller). The controller 130 may be understood as controlling at least one (or preferably most of or in some cases all) the functions of the head unit control system 102. The controller 130 may, in some examples, control the at least one vehicle function and / or may have some capabilities for controlling the authorization of a user to control a function.

[0018] The head unit control system 102 may include a communication controller (e.g. a communication controller for remote connection 404) 140. The communication controller 140 may be connected to an external entity 400 (which may be a head unit remote control provider) through a remote connection 404 (e.g., LTE, 3G, 4G, 5G, or more in general a mobile phone connection, e.g. through TCP / IP). The controller 130 may be connected to the communication controller 140 through a connection line 141. The communication controller 140 may be or control at least one controller antenna (e.g., an antenna array) for the remote connection 404 (e.g. through at least one base station, and subsequently through a backhaul network). The communication controller 140 may also operate as a server, and may provide application programming interfaces (APIs), in some examples, to a user equipment (UE) 300.

[0019] The head unit control system 102 may include for each vehicle function an onboarding / offboard- ing mode 110, e.g. a mode which may be selectably and onboarding mode or an offboarding mode. The head unit control system 102 (and in particular the controller 130) may be connected to the vehicle units 210a-210d of the set 210 through a line 115. Fig. 1 shows that through the line 115 a control connection of the at least one function may selectively be activated and deactivated through an action 111 based on the onboarding / offboarding mode 110. When the line 115 is deactivated then the line 115 does not control the vehicle units 210a-210d, which can be controlled (for example) through the controller 130 autonomously (without any control data from the UE) or through another controller (not shown) which controls the vehicle units 210a-210d autonomously (without any control data from the UE). Instead, when the line 115 is activated, the vehicle units 210a-210d are controlled by the controller 130 (and in turn, as will be apparent later, by the UE 300). It is anticipated that when the UE 300 is authenticated, then the control connection is activated (onboarding mode), and when the UE 300 is not authenticated (or not present at all), the control connection between the controller 130 and the vehicle units 210a-210d is deactivated (offboarding mode). It is noted that the line 115 is in this case to be understood as a logical connection: it may include one or a plurality of lines, each of which may be wired or not wired, wireless, and totally independent from the other connections. Anyway, it has to be understood that the vehicle units 210a-210d of the set 210 cooperate to perform a particular vehicle function. (It is to be noted that the onboarding / offboarding mode 110 is a mode which can be instantiated by an offboarding mode and an onboarding mode in exclusive way. The onboarding / offboarding mode 110 is not to be understood as a physical unit, but more as a condition of the communication and / or of the system 102: in the case that the control data is not received, then the offboarding mode can be achieved. Of course, the onboarding / offboarding mode 110 is known by the controller 130, which in some examples shall take over the control of the function.) As shown by line 144, the onboarding / offboarding mode 110 may be controlled by the communication controller 140. In addition or alternatively, the onboarding / offboarding mode 110 may be controlled by the communication controller 140

[0020] The UE 300 may be connected to a head unit remote control provider 400 (or in general, the external entity) through a remote connection 403 (which can also be LTE, 3G, 4G, 5G, or another mobile phone network, e.g. through TCP / IP), which can be independent from the above-discussed remote connection 404 between the external entity 400 and the head unit control system 102 (e.g., the remote connections 403 and 404 operate through different, parallel communication channels which are independent from each other). However, with the invention is it possible to allow the UE 300 to control the functions) involving the set 210 of vehicle units 210a-210d. Indeed, the UE 300 may send control data to the head unit remote control provider 400, which in turn may route the control data to the head unit control system 102 (and in particular, to the controller 130). The controller 130 may provide the control data to the vehicle units 210a-210d. The vehicle units 210a-210d may provide feedback data to the head unit control system 102 (and in particular, the controller 130). The head unit control system 102 may provide the feedback data to the head unit remote control provider 400 (e.g., through the line 115 and the remote connection 403). The head unit control provider 400 may provide the feedback data to the UE 300 through the remote connection. The UE 300 may display the feedback data, or elaborated data, to the human user.

[0021] In the example of Fig. 1 A there is no wireless local connection between the UE 300 and the head unit control system 102 controlling the functions involving the set 210 of vehicle units 210a-210d. This technical choice can appear counter intuitive, since routing the control data and feedback data through the remote connections 404 and 403 in the cloud appears to complicate the operations. However, it has been understood that this choice permits to simplify the onboarding / offboarding operations and the compatibility of the UE 300 with the particular system. At first, entering a local network through Wi-Fi can be complicated, and require a password, etc. Further, the head unit control system 102 should provide information on all the functions of the vehicle units 210a-210d for performing the various vehicle functions. Or, in alternative, the UE 300 should be subjected to an installation process. The head unit control system 102 should provide application programming interfaces (APIs) to the UE 300 for launching an application adapted to the particular vehicle 200 (this would require the controller 130 to have a complete library of APIs for any type, operating system, etc., of UE 300, which would require a capable storage unit and which, further, should be regularly updated in long updating sessions only for downloading any kind of APIs which maybe will never be used).

[0022] To the contrary, the head unit control remote provider 400 may have both the knowledge of the head unit control system 102 and of the functions involving the set 210 of vehicle units 210a-210d.

[0023] In particular, the UE 300 may be provided, from the head unit remote control provider 400, with executable code causing the code to provide a user interface (e.g., graphic user interface) to remote control the at least one vehicle function. The UE 300 may receive application program interfaces (APIs) from the communication controller 140 (in the examples in which it operates as server), e.g. through the head unit remote control provider 400, or from the head unit remote control provider 400 (in the cases in which it is the head unit remote control provider 400 to operate as server) to the UE 300 and need from the head unit control system 102 to the UE 300. In some examples, the head unit remote control provider 400, having knowledge on the properties of the UE 300, may send exactly the executable code needed by the UE 300 among a bunch of executable codes.

[0024] It is to be noted that the vehicle units 210a-210d are not necessarily uniquely sensors or actuators, but can also include function control units, to control a vehicle function. For example, the vehicle unit 210a can control the air conditioning.

[0025] The onboarding / offboarding mode 110 may switch between an onboarding mode and an offboard- ing mode (see action 111). In the offboarding mode the data line 115 is open, thereby deactivating the UE’s control of the function (and of the vehicle units 210a-210d). In the onboarding mode, the data line 115 is closed, and the UE can control the vehicle units 210a-210d (e.g. through the head unit remote control provider 400).

[0026] In several examples: in the onboarding mode, control data (originated by the UE 300) are received by the communication controller 140 from the head unit remote control provider 400 (and the controller 130 will use the control data to control the vehicle devices 210a-210d); and in the onboarding mode, control data (originated by the UE 300) are not received by the communication controller 140 from the head unit remote control provider 400 for controlling the vehicle devices 210a-210d (and wither the controller 130 will have to control the vehicle devices 210a-210d autonomously only using local settings and / or control data, or another, not shown, external local controller will take over to control the vehicle devices 210a-210d autonomously only using local settings and / or control data), or, in some example, control data are received, but not used for actually controlling the vehicle devices 210a-210d. The onboarding / offboarding mode 110 may be controlled based on an authorization process: when a user is authenticated, then it may be in onboarding mode, and when he / she is not authenticated, then it may be in offboarding mode.

[0027] In practice, if the authentication is not successful, the control provider 400 (or the communication controller) will prevent the UE 300 from sending control data accessing the communication controller 140, such that no control data are received via remote connection 403 and 404 from the UE 300.

[0028] The onboarding / offboarding mode 110 may switch, for each UE 300 (or for which group of UEs destined to exert a same function), between the offboarding mode and the onboarding mode based on an authentication of the UE 300 by the head unit remote control provider 400. If the UE 300 is authenticated, then the head unit remote control provider 400 will provide an authentication information indicative of the UE 300 being correctly authenticated, so that the onboarding / offboarding mode 110 switches to the onboarding mode for the UE 300. On the other side, if the UE 300 is not authenticated, then the head unit report control 400 may provide an unsuccessful authentication information indicative of the UE 300 not being correctly authenticated, or may simply give up sending control data. In case of the negative authentication information or in case of no information from the unit remote control provider 400 at all, the onboarding / offboarding mode 110 will be switched (111) to the offboarding mode for that determined UE 300, preventing the UE 300 from controlling the functions involving the vehicle units 210a-210d.

[0029] The UE’s remote control may be exerted through the head unit remote control provider 400. An example of the head unit remote control provider 400 is shown in Fig. IB (and a variant in Fig. 1C). As can be seen, the head unit remote control provider 400 may include a remote controller 430 for sending control data 416 to the head unit control system 102 (and in particular to the controller 130 through the remote connection 403 and the communication controller 140), which will subsequently be routed to the control data line 115 to the vehicle devices 210a-210d. In turn, feedback data may be routed from the vehicle devices 210a-210d through the control data line 115, the communication controller 140, towards the remote controller 430.

[0030] Under some points of views, it may be assumed that the remote controller 430 provides settings (as an example of the control data) for the vehicle function to the controller 130: the remote controller 430 may receive settings from the UE 300 and route the settings to the controller 130, which will exert a feedback-based local control loop locally based on the settings received from the remote controller 430 and the UE 300. For example, in the case of HVAC, the UE may simply set a particular temperature as required value (setting), the remote controller 430 will sent the information of the setting (particular requested temperature) to the controller 130, and the controller 130 will control the power of the vehicle devices 210a-210d (intended as cooling units, etc.), e.g. by controlling the cooling power of each the vehicle devices 210a-210d towards the requested temperature, e.g. stopping the cooling power of the vehicle devices 210a-210d when the requested temperature is reached (e.g. measured from thermometers, which may also be some of the vehicle devices 210a-210d) and / or by incrementing the requested cooling power when the distance of the measured temperature, as compared to the requested temperature, increases.

[0031] In some examples, however, a feedback-based local control loop may be closed in the remote controller 430. In the example of HVAC, based on a setting from the UE 300, the remote controller 430 may itself control the power of the cooling actuators 210a-210d, while the controller 130 may be simply a router of requested power values to the cooling actuators 210a-210d, and a router of feedback (in terms of temperature measured) from the thermometers, and the remote controller 430 may decide itself which power to set for each cooling actuator to reach the requested temperature.

[0032] In some other examples, the feedback-based local control loop may be closed in the UE 300, and the controller 130 and the remote controller 130 simply operate as routers of information.

[0033] In some examples, in the feedback-based local control loop may be controlled by the vehicle devices independently (e.g., one of them may perform a feedback-based control loop based on settings provided by the controller 130).

[0034] The head unit remote control provider 400 may comprise a remote authenticator 460. The remote authenticator 460 may send authenticating information (e.g. QR code) to the head unit control system 102 and receive UE’s authenticating information 253 from the UE 300. The head unit remote control provider 400 may check whether the UE’s authenticating information 253 from the UE 300 is valid, therefore authenticating (based on the result 451 of the authentication) the UE 300, and permitting the control of the vehicle function. Otherwise, the UE 300 is not authenticated and has not access to the control of the vehicle function.

[0035] The head unit remote control provider 400 may comprise a remote onboarding / offboarding unit 410, which decides the onboarding / offboarding mode 110 for each function, based on the result 451 of the authentication. An action 411 is shown which substantially indicates whether the control data are transmitted to the head unit control system 102 (in the case of onboarding more, following a successful authentication) or not transmitted to the head unit control system 102 (in the case of offboarding mode, following a successful authentication).

[0036] In some examples, a negative or positive authentication information 254 may be transmitted to the head unit control system 102, to make the head unit control system 102 (and in particular the controller 130) of the mode chosen by the remote onboarding / offboarding unit 410. In some examples however, only the positive authentication information 254 may be sent: in case of negative authentication, the controller 130 may simply controlling the function locally, or another controller may control the function without even knowing that the authentication had negative result.

[0037] In general terms, the onboarding / offboarding mode may be defined, in the head unit control system 102, based on the reception or non-reception (e.g. for a span of time of pre -defined time length) of the control data 416 (in case of reception, then the onboarding mode being selected, and in the case of non-reception for more than the span of time of pre -defined time length, then in offboarding mode). The offboarding mode may be the default mode. Therefore, the authentication information 254 may be an implicit information derived by the reception or non-reception of the control data 416, without necessity of sending a message indicating the onboarding / offboarding mode. In other examples, the authentication information 254 may be explicitly sent in a dedicated message or in a dedicated data field of a particular message in the remote connection 404.

[0038] It is now explained how to perform an authentication of the UE 300. The vehicle 200 (or in particular the head unit control system 200) may include at least one output unit (e.g., a display unit) 252. The output unit 252 may visualize the authenticating information 251 (e.g. QR code), e.g. the one generated by the remote authenticator 460 in Fig. IB, while Fig. 1C shows the same example in which the QR code is, instead, generated by the communication controller or by the controller 130. The authenticating information 251 may be unique information, such as a QR code, a barcode, or another code. The authenticating information 251 may be displayed as a static image, in some examples. The authenticating information 251 may be acquired by the UE 300. For example, the UE 300 may have an embedded camera 305 acquiring the authentication information 251 (the QR code, a barcode, or another code), e.g. under the user’s command. The UE 300 may therefore decode the authenticating information 251 (e.g., as code obtained from the QR code) and route the UE’s authenticating information 253 to the head unit remote control provider 400. The authenticating information 251 may provide at least partially encrypted information, but the UE 300 may notwithstanding send the UE’s authenticating information 253 as encrypted information without decrypting it. A password may be encompassed in the authenticating information 251. An example of the UE’s authenticating information 253 may be a URL or another type of address of a web page. The authenticating information may therefore open a particular webpage from the head unit remote control provider 400. The webpage may provide an executable code for providing a user interface for controlling the vehicle functions and / or for receiving feedback data.

[0039] The authenticating information 251 may be generated (or at least stored) by the communication controller or by the controller 130. In alternative, the authenticating information 251 may be generated (or at least stored) by the remote authenticator 430. The authenticating information 251 is in principle uniquely associated with the vehicle 200. The head unit remote control provider 400 (e.g. at disposal of the remote authenticator 430) may therefore compare the UE’s authenticating information 253 as received from the UE 300 with the authenticating information 251 as expected and, in case of a positive comparison (i.e., in case the UE’s authenticating information is the same of the expected authenticating information or differs for a negligible amount, e.g. for less than a predetermined threshold), then the authentication information is positive, so that the embodying of body unit 210 can switch to the onboarding mode for the UE 300, the control data line 115 is closed, and the function can be controlled by the UE 300. In case of negative result of the comparison (i.e., in case the UE’s authenticating information differs from the expected authenticating information, or differs for a non-negligible amount, e.g. for more than a predetermined threshold), then a negative authentication information may be provided to the head unit control system 102 or no authentication information at all. The difference between the example of Fig. IB and that of Fig. 1C is that in Fig. IB the authenticating information 251 is generated (or stored) by the controller 130 or communication controller 140, and is provided to the remote authenticator 460, and in that in Fig. 1C the authenticating information 251 is generated (or stored) by the remote authenticator 460 to the controller 130 or communication controller 140.

[0040] The authenticating information 251 (e.g. QR code) may in principle constantly be the same for the same vehicle 200 and in theory never change (in this case, the remote authenticator 460 does not generate the authenticating information 251 , but simply access it from a protected storage to validate the UE’s authenticating information 253). In theory, the authenticating information 251 can be prestored in a read only memory (ROM) of the head unit control system 102 (and replicated in the database accessed by the remote authenticator 460). In some examples, however, the authenticating information 251 may be subsequently updated (e.g. by the remote authenticator 460). Accordingly for example, the remote authenticator 460 may provide an update authenticating information as the authenticating information 251 to the head unit control system 102, or it may be the head unit control system 102 (and in particular the communication controller or by the controller 130) which provides the update authenticating information as the authenticating information 251 to the remote authenticator 460. The update authenticating information 251 may be for example a new authenticating information 251 (e.g. a new QR code, distinct from the previous one). In other examples, the authenticating information 251 is modified only partially (e.g., only part of the QR code is modified, or some other kind of incremental modification may be performed) by the remote authenticator 460 or by the head unit control system 102 (according to the example). After the update the authenticating information 251 has been provided from the head unit remote control provider 400, the authenticating information 251 changes (and the authenticating information as expected at the head unit remote control provider 400 changes, as well). Therefore, if the UE 300 tries to use an old authenticating information 251 (e.g., a QR code of the day before), it may be that the UE’s authenticating information 254 is not recognized anymore as authentic, and the UE 300 is not given the control of the vehicle function. In addition, or in alternative, update authenticating information may be generated locally by the head unit control system 102 (in particular by the controller 130). For example, the update may be deterministic, in the sense that the update may be foreseen according to a pre -determined algorithm: it is therefore not necessary that the remote authenticator 460 is informed or informs of it of the update. An example of deterministic update may be a counter, which is a data which is incremented any time an authentication result is positive: hence, both the remote authenticator 460 and the controller 130 may update autonomously, simply by relying on their knowledge of the pre-determined algorithm. Another possibility is that the pre-defined algorithm relies on time -related information, such as information deterministically determined based on the time (e.g., the particular date, or the particular time), known both by the controller 130 and by the remote authenticator 460. In this way, the UE 300 will be authenticated only in the case that the timing related information is correctly associated to the date or time. Hence, the remote authenticator 460 and the controller 130 may cooperate, according to a pre-defined algorithm, to vary the authenticating information 251, thereby increasing security.

[0041] What is discussed above is valid also for a plurality of UEs 300. Each UE 300 may be authenticated independently, and the onboarding / offboarding mode 110 may grant access to a specific function to each UE, independently of the other UEs.

[0042] In Fig. 2, two different UEs (at first UE 300a and a second unit 300b) are shown to be in the internal space 220 of the vehicle 200. The first UE 300a may control a first vehicle function involving a first set 210’ of vehicle units 210a, 210b, 210c, 210d. A second UE 300b may control a second function, involving a second set 210” of vehicle units 210e and 21 Of. Each of the UEs therefore may control a different function, each function involving different sets of vehicle units. In this case, the different sets 210’ and 210” are disjoint, in the sense that no vehicle units of the first set 210’ is also a vehicle unit of the second set 210”. In some examples, however, different sets may differ for at least one single vehicle unit (e.g., some vehicle units may be in both sets 210’ and 210”, and therefore different sets 210’ and 210” may differ for at least one single vehicle unit). Different sets 210’ and 210” are normally implied in different vehicle functions.

[0043] Different vehicle functions often occur, for example, for multimedia applications (where different users may intend to enjoy different media content) or for HVAC applications, (e.g., where different users want to have different temperature at their seats). Notably, in a HVAC application, multiple functions (e.g., ventilation and / or air conditioning of single positions) may have different sets of vehicle units which may have, for example, at least one common vehicle unit (e.g., different positions may be served by different ventilators, therefore different ventilation functions may be served by different sets of vehicle units, but there could be one single temperature sensor common to all the sets of vehicle units).

[0044] Each UE has a remote connection with the head unit control system 102 which is independent from the other, but both are connected to the head unit remote control provider 400. Each UE may receive executable code for providing a user interface for controlling different functions. The onboarding / offboarding mode 110 (which is shown in Fig. 2 as controlling two different switches) has a two instantiations: a first mode associated with the first UE 300a (selected between onboarding and off- boarding), and a second mode for the second UE 300b (selected between onboarding and offboarding). The onboarding / offboarding mode 110 is shown as switch (commanded through action I lla, 111b). The first set 210’ of vehicle units 210a-210d is controlled (through the switching action I l la). The second set 210” of vehicle units 210a-210d is controlled through the command line 115a, while the switching action 111b controls the vehicle units 210e and 21 Of. As can be seen in Fig. 2, the vehicle units of the first set 210’ are positioned in the vicinity of (e.g. inside) a first position 220a, while the vehicle units 210e-210f of the second set 210” are positioned in the vicinity (e.g. inside) of a second position 220b. So, each UE 300a, 300b controls the vehicle units of the set which is in their vicinity. In the case of multiple displays 252a and 252b, for example, it is possible to determine the position of each UE 300a, 300b in the case of different authenticating information (e.g. different QR codes, barcodes, etc.) 251a, 251b provided through different output units 252a, 252b. For example, different authenticating information (e.g., QR codes, barcodes etc.) will be provided to different displays 252a, 252b. The first display 252a may be positioned in the vicinity of (e.g. inside) the first position 220a. The second display 252b may be positioned in the vicinity of (e.g. inside) the second position 220b. The first authenticating information 251a may therefore indicative of the first UE 300a being in (or at least in the vicinity of) the first position 220a. Therefore, a second authenticating information 251b may therefore be indicative of a UE (the second UE 300b) being positioned in (or at least in the vicinity of) the second position 220b. The head unit remote control provider 400 therefore may distinguish between the positions of each UE, and therefore provide different user interfaces for the different UEs, and also provide different authenticating information (at first authenticating information and the second authenticating information) to the head unit control system. Accordingly, the onboarding / offboarding state 110 may switch (I l la, 111b) differently for different UEs or for different positions of each UE.

[0045] It is noted that it is not uniquely requested that all the vehicle unit 210a-210d close to the first position 220a are controlled by the first UE 300a and all the vehicle unit 210a, 210f close to the second position 220b are specifically controlled by the second UE 300b: it may be that in some cases that one UE has the privilege of also controlling some other vehicle units which are further away. This may happen, for example, in the case of the media rendering: it could be that each UE can control the video display closer to it (because each human user wants to see the same video content differently) but that only one UE (e.g. master UE) controls the audio, globally provided by a multiplicity of loudspeaker scattered through the vehicle 200. In this sense, each UE can control a proper subset (210’, 210”) of device units, but at least one UE may control also some device units which are not closer to its position, i.e. it controls them globally. In other cases, it may be that all the users have the privilege of controlling some functions (e.g., the volume of the loudspeaker). Accordingly, it may be that each UE controls at least one proper subset of the vehicle units, but at least one (but not necessarily all) vehicle units of its subset is close to its position.

[0046] More in general, it is possible for the head unit control system 102 to control multiple functions in the vehicle. The head unit control system 102 may receive, from a UE (300, 300a, 300b): a first authenticating information (251a) associated with a first function; and a second authenticating information (251b) associated with a second function. The onboarding mode is subdivided between at least: a first onboarding mode, following the UE (300) having been authenticated through the first authenticating information (251a) for the first function; and a second onboarding mode, following the UE (300) having been authenticated through the second authenticating information (215b) for the second function. The head unit control system (102) may: in the first onboarding mode, to control the first function (and in the first offboarding mode, to refrain from controlling it); and in the second onboarding mode, to control the second function (and in the second offboarding mode, to refrain from controlling it).

[0047] Analogously, the head unit control remote provider 400 may: provide the first authenticating information (251a) associated with a first function; and provide the second authenticating information (251b) associated with a second function.

[0048] The onboarding mode is subdivided between at least: a first onboarding mode, following the UE (300) having been authenticated through the first authenticating information (251a) for the first function; and a second onboarding mode, following the UE (300) having been authenticated through the second authenticating information (215b) for the second function.

[0049] The head unit control system (102) is configured: in the first onboarding mode, to activate a first control connection so as to control the first function (and in the first offboarding mode, to deactivate it); and in the second onboarding mode, to activate a second control connection so as to control the second function (and in the second offboarding mode, to deactivate it).

[0050] A version of the head unit control remote provider 400 is not shown, because it would merely replicate two instances of the head unit control remote provider 400 of Fig. IB.

[0051] The head unit control remote provider 400 may therefore: authenticate a user equipment, UE (300, 300a, 300b), by comparing UE’s authenticating information, received from the UE (e.g. through the remote connection 403), with authenticating information associated with a vehicle; only in case of positive authentication: inform (e.g. through the remote connection 404) the head unit control system 102 of the positive authentication; provide (e.g. through the remote connection 403) the UE (300, 300a, 300b) a user interface or with code executable by the UE causing the code to provide a user interface to remotely control at least one vehicle function; receive (e.g. through the remote connection 403) from the UE control data inputted by the user through the user interface; provide (e.g. through the remote connection 404) the control data to the head unit control system, so that the head unit control system controls the at least one vehicle function; in some examples: receive (e.g. through the remote connection 404) feedback data from the head unit control system 102, so that the head unit control system controls the at least one vehicle function; providing (e.g. through the remote connection 403), to the UE, the feedback data. In case of negative authentication, no information may be provided to the head unit control system 102, or only a negative information will be provided to the head unit control system 102, but in that case the control data will not be provided.

[0052] It is also possible to have an example in which two UEs 300a and 300b are both authenticated, e.g. the first UE 300a may be authenticated for a first function involving a first set 210’ of vehicle units 210a-210d, and a the second UE 300b may be authenticated for a second function involving a second set 210” of vehicle units 210e-210f. It may be that, for each UE, the onboarding / offboarding mode may be controlled locally (e.g. by the controller 130 through line 131, and not by the communication controller 130). In this case, the remote authenticator 460 sends, for each UE, an explicit authentication information 254 which may also indicate which function each UE can control. In this case, the control data 416 are sent for both controlling the first function and the second function: simply, the control data 416 are routed to the different sets of devices based on which UE sends each control data.

[0053] Also, there can be a master UE and a secondary UE: the master UE can have the onboarding mode having priority over the secondary UEs. For example, the master UE can selectively onboard in any (or in the broadest) set of devices (i.e. in any vehicle function or almost in any vehicle function), and when the master UE onboards on one function (i.e. onboarding / offboarding state for master UE and for that function being onboarding), then the state of the secondary UEs goes (for the same function) automatically to the offboarding mode.

[0054] Fig. 4 shows an example of a UE 300 (e.g. 300a, 300b) which could be used in the invention and which can be any of the precedingly-discussed UEs.

[0055] The UE may include a camera 305 (or another authenticating information acquisition unit) for acquiring the authenticating information 251 emitted by an output unit (e.g. display) 252 controlled by the head unit control system 102. The UE may have a visual recognizer, to recognize the authenticating information 251 (e.g., in form of numbers) and / or in graphic format (e.g. JPG, bitmap, etc.). The authenticating information 251 may be provided to an authentication unit 360, which may carry out the authenticating process with the head unit control provider 400, e.g. through the remote connection 403. The authentication unit 360 may also provide credentials previously established with the head unit remote control provider 400 and associated with the UE (e.g. a serial number of the UE) and / or with the user account of the user. The user account may have been previously associated with the credentials following a subscription.

[0056] The UE may receive an authentication information 404’ as soon as the head unit control provider 400 has recognized the validity of the UE’s authenticating information. Once in the authentication process is successfully completed, the authentication unit may change the UE’s offboarding / onboarding mode 310 from the offboarding mode to the onboarding mode, e.g. through the action 311. When in onboarding mode, the remote control unit 430 may exchange with the head unit control system (through the remote connection 403, the head unit remote control provider 400, and the remote connection 404) the control data 416 and feedback data. In this case, instead of the UE’s offboarding / onboarding mode 310, a UE’s offboarding / onboarding unit may be provided to exert the action 311.

[0057] It is noted that the modes or units 410, 310 210 can be replica with each other: once the authorization is achieved, the modes are meant to be the same for each UE and for each function (different UEs and / or different functions may have different states, like in Figs 2 and 3.

[0058] The UE 300 may have a user interface (e.g. application) 301 for allowing the user to control the UE. In Fig. 301 there is only shown that the user interface 301 receives commands and sends control data (e.g. to the remote controller 330), such as settings, and displays or otherwise provides feedback data (e.g., sensor results). Of course, the UE may have many other functions and connections which are here not shown for brevity.

[0059] As explained above, it is also possible to perform the link invitation.

[0060] Notably, the following advantages are reached:

[0061] 1) It is not necessary, for the UE 300, to have an application pre-installed

[0062] The UE 300 does not necessarily need to receive APIs.

[0063] In examples above, there is provided, inter alia, a head unit control system (e.g. 102) for controlling at least one vehicle function in a vehicle (200) from a user equipment, UE (300), the at least one vehicle function involving the use of a set of vehicle devices (210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the head unit control system (102) is configured to selectively have, for each vehicle function, an onboarding / offboarding mode switchable (111) between an onboarding mode and an offboarding mode based on a reception, from a remote entity (400), of onboarding state information indicating that the UE (300) has been authenticated, so as to switch to the onboarding mode, the head unit control system (102) comprising a controller (130) to control the at least one vehicle function, wherein in the onboarding mode, a control connection is activated (111) through which the head unit control system (102) interfaces both the UE (300) and the at least one vehicle function, so that the controller (130) receives control data from the UE (300) and controls the at least one vehicle function based on the control data received from the UE (300), and in the offboarding mode, the control connection is deactivated.

[0064] The head unit control system may further control at least one output unit (e.g.252) to provide authenticating information (e.g.251) to at least one user equipment, UE (e.g.300), to permit the UE (e.g.300) to authenticate.

[0065] The head unit control system may generate the authenticating information (e.g.251) and to send the authenticating information (e.g.251) to the remote entity (e.g.400).

[0066] The head unit control system may receive the authenticating information (e.g.251) from the remote entity (e.g.400). The authenticating information (e.g.251) may be a visual information, the least one output unit (e.g.252) being, or being connected to, a display unit to display the authenticating information (e.g.251).

[0067] The authenticating information (e.g.251) may be a QR code.

[0068] The head unit control system may receive, from the remote entity (e.g.400), update authenticating information which updates at least partially the authenticating information (e.g.251), so that the authenticating information (e.g.251) changes.

[0069] The head unit control system may generate, locally, update authenticating information which updates at least partially the authenticating information, so that the authenticating information (e.g.251) changes during time.

[0070] The head unit control system may send to the remote entity (e.g.400) information (e.g.253) on the update authenticating information, to permit the authentication of the UE.

[0071] The head unit control system may provide the authenticating information (e.g.251) as including information on a web address, so that the UE (e.g.300) can authenticate by connecting to the web address.

[0072] The at least one output unit (e.g.252) may control multiple output units (e.g.252a, 252b) positioned in at least a first position (e.g.220a) and a second position (e.g.220b) in the vehicle, thereby providing: a first authenticating information (e.g.251 a) to a first output unit (e.g.252a); and a second authenticating information (e.g.251b) to a second output unit (e.g.252b), the first output unit (e.g.252a) being closer to the first position (e.g.220a) than the second output unit (e.g.252b) and / or the second output unit (e.g.252b) being closer to the second output unit (e.g.252b) than the first output unit (e.g.252a), wherein the onboarding mode is subdivided between at least: a first onboarding mode switched, from a first offboarding mode, at a reception, from the remote entity (e.g.400), of first onboarding / offboarding state information indicating that the UE (e.g.300) has been authenticated through the first authenticating information (e.g.215a), so as to switch to the first onboarding mode; and a second onboarding mode switched, from a second offboarding mode, at a reception, from the remote entity (e.g.400), of second onboarding mode information indicating that the UE (e.g.300b) has been authenticated through the second authenticating information (e.g.215b), so as to switch to the second onboarding mode, wherein the head unit control system (e.g.102) is configured: in the first onboarding mode, to activate the control connection (e.g.H5a) so that the head unit control system (e.g.102) receives control data from the UE (e.g.300) and controls only a first, proper subset (e.g.210a, 210b, 210c, 210d) of the set of vehicle devices, at least one vehicle device in the first, proper subset (e.g.210a, 210b, 210c, 210d) is closer to the first position (e.g.220a) than at least one vehicle device (e.g.210e, 210f) which is not in the first, proper subset (e.g.210a, 210b, 210c, 210d); and in the second onboarding mode, to activate the control connection (e.g.H5b) so that the head unit control system (e.g.102) receives control data from the UE (e.g.300b) and controls only a second, proper subset (e.g.210e, 21 Of) of the set of vehicle devices, wherein at least one vehicle device (e.g.210e, 21 Of) in the second, proper subset is closer to the second position (e.g.220b) than at least one of the vehicle devices which is not in the second, proper subset (e.g.210e, 210f).

[0073] The head unit control system may control multiple functions in the vehicle, thereby receiving: a first authenticating information (e.g.251a) associated with a first function; and a second authenticating information (e.g.251b) associated with a second function, wherein the onboarding mode is subdivided between at least: a first onboarding mode, following the UE (e.g.300) having been authenticated through the first authenticating information (e.g.251a) for the first function; and a second onboarding mode, following the UE (e.g.300) having been authenticated through the second authenticating information (e.g.215b) for the second function, wherein the head unit control system (e.g.102) is configured: in the first onboarding mode, to activate a first control connection so as to control the first function; and in the second onboarding mode, to activate a second control connection so as to control the second function.

[0074] The head unit control system may control multiple functions in the vehicle, configured to have, authenticated, a master UE and at least one secondary UE, wherein the master UE has the onboarding mode which has priority against the onboarding mode of the at least one secondary UE, so that, as soon as the master UE has onboarding more for at least one determined function, then the at least one secondary UE consequently has the offboarding state for the at last one determined function.

[0075] The head unit control system of claim 12, wherein the first and second functions involve a different subset of vehicle devices.

[0076] The head unit control system may receive the control data from the UE through a remote connection.

[0077] The head unit control system may be permit multiple UEs to control multiple functions, wherein the onboarding / offboarding unit (e.g.110) is configured to switch (e.g. I l l) between an onboarding mode and an offboarding mode for each UE (e.g.300a, 300b), based on a reception, from a remote entity (e.g.400), of onboarding / offboarding state information for each that UE (e.g.300a, 300b).

[0078] The at least one vehicle function may include at least one heating, ventilation and / or air conditioning function.

[0079] The least one vehicle function may include at least one multimedia rendering function.

[0080] The at least one vehicle function may include at least one taxi billing function. The head unit control system may send, during an installation phase, a list of vehicle functions that can be performed, so as to subsequently remain waiting for control data regarding at least one of the vehicle functions.

[0081] The head unit control system may send, during an installation phase, a list of vehicle units that can be involved by functions or a list of sets of vehicle units which can perform functions, and receive, from the head unit remote control provider, a list of defined functions and of sets of vehicle units to be involved by each function.

[0082] The control data received from the UE may be setting values, wherein the controller (e.g.130) is configured to provide the setting values to at least one of the vehicle devices, so that the set of vehicle devices perform a feedback-based loop control independently.

[0083] The control data received from the UE may be setting values, wherein the controller (e.g.130) is configured to exert a feedback-based control loop by controlling actions of the vehicle devices based on feedback values obtained from the vehicle devices.

[0084] The head unit control system may switch to the offboarding mode in case of the vehicle being turned off.

[0085] The head unit control system may switch to the offboarding mode in case of a destination being reached according to a navigation system.

[0086] The head unit control system may switch to the offboarding mode in case of a pre-determined time being elapsed without any reception of control data.

[0087] The head unit control system may switch to the offboarding mode in case of UE equipment deviating for a pre-determined distance from the position of the vehicle.

[0088] In examples above, there is provide, inter alia, a head unit control remote provider (e.g.400) for remotely controlling a vehicle function in a vehicle, configured for: authenticating a user equipment, UE, by comparing UE’s authenticating information, received from the UE, with authenticating information associated with a vehicle; and, in case of positive authentication: providing the UE with a user interface or code executable by the UE causing the code to provide a user interface to remotely control at least one vehicle function; receiving from the UE control data inputted through the user interface; providing the control data to the head unit control system, so that the head unit control system controls the at least one vehicle function.

[0089] The head unit control remote provider may send, to an address corresponding to the UE (e.g.300), the authenticating information via link invitation.

[0090] The head unit control remote provider may perform a pre-authorization session of the UE (e.g.300), and, in case of successful pre-authorization, perform a setup session of receiving setup information from the UE (e.g.300) irrespective of the head unit control system (e.g.102) being currently remotely connected to the head unit remote control provider (e.g.400), and, in case of determining that the UE (e.g.300) is within the vehicle environment (e.g.220) and as soon as the head unit control system (e.g.102) is established remotely connected to the head unit remote control provider (e.g.400), providing the control data based on the setup information.

[0091] The setup information may include at least one of downloadable setup data.

[0092] The head unit control remote provider may further send authenticating information (e.g.251) to be provided to at least one user equipment, UE (e.g.300), to permit the UE (e.g.300) to authenticate.

[0093] The authenticating information (e.g.251) may be a visual information to be displayed by a display unit.

[0094] The authenticating information (e.g.251) may be a QR code.

[0095] The head unit control remote provider may send update authenticating information which updates at least partially the authenticating information (e.g.251), so that the authenticating information (e.g.251) changes.

[0096] The head unit control remote provider may control multiple functions in the vehicle, thereby providing: a first authenticating information (e.g.251 a) associated with a first function; and a second authenticating information (e.g.251b) associated with a second function, wherein the onboarding mode is subdivided between at least: a first onboarding mode, following the UE (e.g.300) having been authenticated through the first authenticating information (e.g.251 a) for the first function; and a second onboarding mode, following the UE (e.g.300) having been authenticated through the second authenticating information (e.g.215b) for the second function, wherein the head unit control system (e.g.102) is configured: in the first onboarding mode, to activate a first control connection so as to control the first function; and in the second onboarding mode, to activate a second control connection so as to control the second function.

[0097] The head unit control remote provider of claim 35, wherein the first and second functions involve a different subset of vehicle devices.

[0098] The head unit control remote provider may receive the control data from the UE through a remote connection.

[0099] The head unit control remote provider may permit multiple UEs to control multiple functions, wherein the onboarding / offboarding unit (e.g.410) is configured to switch (e.g. I l l) between an onboarding mode and an offboarding mode for each UE (e.g.300a, 300b), based on a reception, from a remote entity (e.g.400), of onboarding / offboarding state information for each that UE (e.g.300a, 300b).

[0100] The at least one vehicle function may include at least one heating, ventilation and / or air conditioning function. The at least one vehicle function may include at least one multimedia rendering function.

[0101] The at least one vehicle function may include at least one taxi billing function.

[0102] The head unit control remote provider may receive, during an installation phase, a list of vehicle functions that can be performed, so as to subsequently control the vehicle device to exert the function.

[0103] The head unit control remote provider may send, during an installation phase, a list of vehicle units that can be involved by functions or a list of sets of vehicle units which can perform functions, and receive, from the head unit remote control provider, a list of defined functions and of sets of vehicle units to be involved by each function.

[0104] The control data received from the UE may be setting values, wherein the controller (e.g.130) is configured to perform a feedback-based loop control based on feedback values from the the head unit remote control system (e.g.102) and to provide control data to the head unit remote control system (e.g.102).

[0105] The head unit control remote provider may provide, to the UE, the executable code without APIs.

[0106] The head unit control remote provider may provide, to the head unit control system, the command data without APIs.

[0107] The head unit control remote provider may switch to the offboarding mode in case of the vehicle being turned off as for information from the head unity control system.

[0108] The head unit control remote provider may switch to the offboarding mode in case of a destination being reached according to a navigation system connected to the head unit control remote provider.

[0109] The head unit control remote provider may switch to the offboarding mode in case of UE deviating for a pre -determined distance from the position of the vehicle based on positions determined for both the vehicle and the UE.

[0110] In examples above, there is provided, inter alia, a user equipment, UE (e.g.300), for controlling at least one vehicle function through a head unit control system (e.g.102) installed in a vehicle, the UE including: a user interface for interacting with a user; an acquiring unit for acquiring authenticating information (e.g.251) received from an output unit (e.g.252) controlled by the head unit control system (e.g.102); an authentication unit (e.g.360) to perform, through a remote connection (e.g.403), a remote authentication process providing the authenticating information (e.g.251) to a head unit remote control provider (e.g.400), and to receive an authorization result from the head unit remote control provider (e.g.400); a remote control unit (e.g.360) to control the at least one vehicle function through the remote connection and the head unit control provider, the at least one vehicle function involving the use of a set of vehicle devices (e.g.210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the UE (e.g.300) is configured to selectively have, for each vehicle function, an onboarding / offboarding mode (e.g.310) switchable (e.g.311) between an onboarding mode and an off- boarding mode based on the authorization based on the authorization result, so as to switch to the onboarding mode, wherein in the onboarding mode, a control connection is activated (e.g.311) through which the UE (e.g.300) interfaces with the remote entity (e.g.400) to control the at least one function, and in the offboarding mode, the control connection is deactivated.

[0111] The UE may receive, to an address corresponding to the UE (e.g.300), the authenticating information via link invitation.

[0112] The authenticating information (e.g.251) may be a QR code.

[0113] The at least one vehicle function may include at least one heating, ventilation and / or air conditioning function.

[0114] The at least one vehicle function may include at least one multimedia rendering function.

[0115] The at least one vehicle function may include at least one taxi billing function.

[0116] The UE may receive, from the remote entity, executable code without APIs.

[0117] In examples above, there is provided, inter alia, a method for a head unit control system (e.g.102) controlling at least one vehicle function in a vehicle (e.g.200) from a user equipment, UE (e.g.300), the at least one vehicle function involving the use of a set of vehicle devices (e.g.210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the head unit control system (e.g.102) selectively has, for each vehicle function, an onboarding / offboarding mode switchable (e.g. I l l) between an onboarding mode and an offboarding mode based on a reception, from a remote entity (e.g.400), of onboarding state information indicating that the UE (e.g.300) has been authenticated, so as to switch to the onboarding mode, the method including controlling the at least one vehicle function, wherein in the onboarding mode, a control connection is activated (e.g. I l l) through which the head unit control system (e.g.102) interfaces both the UE (e.g.300) and the at least one vehicle function, so as to receive control data from the UE (e.g.300) and control the at least one vehicle function based on the control data received from the UE (e.g.300), and in the offboarding mode, the control connection is deactivated.

[0118] In examples above, there is provided, inter alia, a method for remotely controlling a vehicle function in a vehicle, comprising: authenticating a user equipment, UE, by comparing UE’s authenticating information, received from the UE, with authenticating information associated with a vehicle; and, in case of positive authentication: controlling providing the UE with a user interface or code executable by the UE causing the code to provide a user interface to remotely control at least one vehicle function; receiving from the UE control data inputted through the user interface; providing the control data to the head unit control system, so that the head unit control system controls the at least one vehicle function.

[0119] In examples above, there is provided, inter alia, a method for controlling at least one vehicle function through a head unit control system (e.g.102) installed in a vehicle, the method including: interacting with a user through a user interface at a user equipment, UE; acquiring authenticating information (e.g.251) received from an output unit (e.g.252) controlled by the head unit control system (e.g.102); performing, through a remote connection (e.g.403), a remote authentication process providing the authenticating information (e.g.251) to a head unit remote control provider (e.g.400), and receiving an authorization result from the head unit remote control provider (e.g.400); controlling the at least one vehicle function through the remote connection and the head unit control provider, the at least one vehicle function involving the use of a set of vehicle devices (e.g.210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the involves selectively having, for each vehicle function, an onboarding / offboarding mode (e.g.310) switchable (e.g.311) between an onboarding mode and an offboarding mode based on the authorization based on the authorization result, so as to switch to the onboarding mode, wherein in the onboarding mode, a control connection is activated (e.g.311) through which the UE (e.g.300) interfaces with the remote entity (e.g.400) to control the at least one function, and in the offboarding mode, the control connection is deactivated.

Claims

Claims1. A head unit control system ( 102) for controlling at least one vehicle function in a vehicle (200) from a user equipment, UE (300), the at least one vehicle function involving the use of a set of vehicle devices (210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the head unit control system (102) is configured to selectively have, for each vehicle function, an onboarding / offboarding mode switchable (111) between an onboarding mode and an off- boarding mode based on a reception, from a remote entity (400), of onboarding state information indicating that the UE (300) has been authenticated, so as to switch to the onboarding mode, the head unit control system (102) comprising a controller (130) to control the at least one vehicle function, wherein in the onboarding mode, a control connection is activated (111) through which the head unit control system (102) interfaces both the UE (300) and the at least one vehicle function, so that the controller (130) receives control data from the UE (300) and controls the at least one vehicle function based on the control data received from the UE (300), and in the offboarding mode, the control connection is deactivated.

2. The head unit control system according to any of the preceding claims, further configured to control at least one output unit (252) to provide authenticating information (251) to at least one user equipment, UE (300), to permit the UE (300) to authenticate.

3. The head unit control system according to claim 2, configured to generate the authenticating information (251) and to send the authenticating information (251) to the remote entity (400).

4. The head unit control system according to claim 2, configured to receive the authenticating information (251) from the remote entity (400).

5. The head unit control system according to any of claims 2-4, the authenticating information (251) being a visual information, the least one output unit (252) being, or being connected to, a display unit to display the authenticating information (251).

6. The head unit control system according to claim 5, the authenticating information (251) being a QR code.

7. The head unit control system according to any of claims 2-6, configured to receive, from the remote entity (400), update authenticating information which updates at least partially the authenticating information (251), so that the authenticating information (251) changes.

8. The head unit control system according to any of claims 2-7, configured to generate, locally, update authenticating information which updates at least partially the authenticating information, so that the authenticating information (251) changes during time.

9. The head unit control system according to claim 8, configured to send to the remote entity (400) information (253) on the update authenticating information, to permit the authentication of the UE.

10. The head unit control system according to any of claims 2-9, configured to provide the authenticating information (251) as including information on a web address, so that the UE (300) can authenticate by connecting to the web address.

11. The head unit control system according to any of claims 2-10, wherein the at least one output unit (252) is configured to control multiple output units (252a, 252b) positioned in at least a first position (220a) and a second position (220b) in the vehicle, thereby providing: a first authenticating information (251a) to a first output unit (252a); and a second authenticating information (251b) to a second output unit (252b), the first output unit (252a) being closer to the first position (220a) than the second output unit (252b) and / or the second output unit (252b) being closer to the second output unit (252b) than the first output unit (252a), wherein the onboarding mode is subdivided between at least: a first onboarding mode switched, from a first offboarding mode, at a reception, from the remote entity (400), of first onboarding / offboarding state information indicating that the UE (300) has been authenticated through the first authenticating information (215a), so as to switch to the first onboarding mode; and a second onboarding mode switched, from a second offboarding mode, at a reception, from the remote entity (400), of second onboarding mode information indicating that the UE (300b) has been authenticated through the second authenticating information (215b), so as to switch to the second onboarding mode, wherein the head unit control system (102) is configured: in the first onboarding mode, to activate the control connection (115a) so that the head unit control system (102) receives control data from the UE (300) and controls only a first, proper subset (210a, 210b, 210c, 210d) of the set of vehicle devices, at least one vehicle device in the first, proper subset (210a, 210b, 210c, 210d) is closer to the first position (220a) than at least one vehicle device (210e, 210f) which is not in the first, proper subset (210a, 210b, 210c, 210d); and in the second onboarding mode, to activate the control connection (115b) so that the head unit control system (102) receives control data from the UE (300b) and controls only a second, proper subset (210e, 210f) of the set of vehicle devices, wherein at least one vehicle device (210e, 210f) in the second,proper subset is closer to the second position (220b) than at least one of the vehicle devices which is not in the second, proper subset (210e, 21 Of).

12. The head unit control system according to any of the preceding claims, configured to control multiple functions in the vehicle, thereby receiving: a first authenticating information (251a) associated with a first function; and a second authenticating information (251b) associated with a second function, wherein the onboarding mode is subdivided between at least: a first onboarding mode, following the UE (300) having been authenticated through the first authenticating information (251a) for the first function; and a second onboarding mode, following the UE (300) having been authenticated through the second authenticating information (215b) for the second function, wherein the head unit control system (102) is configured: in the first onboarding mode, to activate a first control connection so as to control the first function; and in the second onboarding mode, to activate a second control connection so as to control the second function.

13. The head unit control system according to any of the preceding claims, configured to control multiple functions in the vehicle, configured to have, authenticated, a master UE and at least one secondary UE, wherein the master UE has the onboarding mode which has priority against the onboarding mode of the at least one secondary UE, so that, as soon as the master UE has onboarding more for at least one determined function, then the at least one secondary UE consequently has the offboarding state for the at last one determined function.

14. The head unit control system of claim 12 or 13, wherein the first and second functions involve a different subset of vehicle devices.

15. The head unit control system of any of the preceding claims, configured to receive the control data from the UE through a remote connection.

16. The head unit control system of any of the preceding claims, configured to permit multiple UEs to control multiple functions, wherein the onboarding / offboarding unit (110) is configured to switch (111) between an onboarding mode and an offboarding mode for each UE (300a, 300b), based on a reception, from a remote entity (400), of onboarding / offboarding state information for each that UE (300a, 300b).

17. The head unit control system of any of the preceding claims, wherein the at least one vehicle function includes at least one heating, ventilation and / or air conditioning function.

18. The head unit control system of any of the preceding claims, wherein the at least one vehicle function includes at least one multimedia rendering function.

19. The head unit control system of any of the preceding claims, wherein the at least one vehicle function includes at least one taxi billing function.

20. The head unit control system of any of the preceding claims, configured to send, during an installation phase, a list of vehicle functions that can be performed, so as to subsequently remain waiting for control data regarding at least one of the vehicle functions.

21. The head unit control system of any of the preceding claims, configured to send, during an installation phase, a list of vehicle units that can be involved by functions or a list of sets of vehicle units which can perform functions, and receive, from the head unit remote control provider, a list of defined functions and of sets of vehicle units to be involved by each function.

22. The head unit control system of any of the preceding claims, wherein the control data received from the UE are setting values, wherein the controller (130) is configured to provide the setting values to at least one of the vehicle devices, so that the set of vehicle devices perform a feedback-based loop control independently.

23. The head unit control system of any of the preceding claims, wherein the control data received from the UE are setting values, wherein the controller (130) is configured to exert a feedback-based control loop by controlling actions of the vehicle devices based on feedback values obtained from the vehicle devices.

24. The head unit control system of any of the preceding claims, configured to switch to the off- boarding mode in case of the vehicle being turned off.

25. The head unit control system of any of the preceding claims, configured to switch to the off- boarding mode in case of a destination being reached according to a navigation system.

26. The head unit control system of any of the preceding claims, configured to switch to the off- boarding mode in case of a pre-determined time being elapsed without any reception of control data.

127. The head unit control system of any of the preceding claims, configured to configured to switch to the offboarding mode in case of UE equipment deviating for a pre -determined distance from the position of the vehicle.

28. A head unit control remote provider (400) for remotely controlling a vehicle function in a vehicle, configured for: authenticating a user equipment, UE, by comparing UE’s authenticating information, received from the UE, with authenticating information associated with a vehicle; and, in case of positive authentication: providing the UE with a user interface or code executable by the UE causing the code to provide a user interface to remotely control at least one vehicle function; receiving from the UE control data inputted through the user interface; providing the control data to the head unit control system, so that the head unit control system controls the at least one vehicle function.

29. The head unit control remote provider of claim 28, configured to send, to an address corresponding to the UE (300), the authenticating information via link invitation.

30. The head unit control remote provider of any of claims 28-29, configured to perform a preauthorization session of the UE (300), and, in case of successful pre-authorization, perform a setup session of receiving setup information from the UE (300) irrespective of the head unit control system (102) being currently remotely connected to the head unit remote control provider (400), and, in case of determining that the UE (300) is within the vehicle environment (220) and as soon as the head unit control system (102) is established remotely connected to the head unit remote control provider (400), providing the control data based on the setup information.

31. The head unit control remote provider of claim 30, wherein the setup information includes at least one of downloadable setup data.

32. The head unit control remote provider according to any of claims 28-31, further configured send authenticating information (251) to be provided to at least one user equipment, UE (300), to permit the UE (300) to authenticate.

33. The head unit control remote provider according to claim 32, the authenticating information (251) being a visual information to be displayed by a display unit.

34. The head unit control remote provider according to claim 33, the authenticating information (251) being a QR code.

35. The head unit control remote provider according to any of claims 32-34, configured to send update authenticating information which updates at least partially the authenticating information (251), so that the authenticating information (251) changes.

36. The head unit control remote provider according to any of claims 32-35, configured to control multiple functions in the vehicle, thereby providing: a first authenticating information (251a) associated with a first function; and a second authenticating information (251b) associated with a second function, wherein the onboarding mode is subdivided between at least: a first onboarding mode, following the UE (300) having been authenticated through the first authenticating information (251a) for the first function; and a second onboarding mode, following the UE (300) having been authenticated through the second authenticating information (215b) for the second function, wherein the head unit control system (102) is configured: in the first onboarding mode, to activate a first control connection so as to control the first function; and in the second onboarding mode, to activate a second control connection so as to control the second function.

37. The head unit control remote provider of claim 36, wherein the first and second functions involve a different subset of vehicle devices.

38. The head unit control remote provider of any of claims 32-37, configured to receive the control data from the UE through a remote connection.

39. The head unit control remote provider of any of claims 32-38, configured to permit multiple UEs to control multiple functions, wherein the onboarding / offboarding unit (410) is configured to switch (111) between an onboarding mode and an offboarding mode for each UE (300a, 300b), based on a reception, from a remote entity (400), of onboarding / offboarding state information for each that UE (300a, 300b).

40. The head unit control remote provider of any of claims 32-39, wherein the at least one vehicle function includes at least one heating, ventilation and / or air conditioning function.

41. The head unit control remote provider of any of claims 32-40, wherein the at least one vehicle function includes at least one multimedia rendering function.

42. The head unit control remote provider of any of claims 32-41, wherein the at least one vehicle function includes at least one taxi billing function.

43. The head unit control remote provider of any of claims 32-42, configured to receive, during an installation phase, a list of vehicle functions that can be performed, so as to subsequently control the vehicle device to exert the function.

44. The head unit control remote provider of any of claims 32-43, configured to send, during an installation phase, a list of vehicle units that can be involved by functions or a list of sets of vehicle units which can perform functions, and receive, from the head unit remote control provider, a list of defined functions and of sets of vehicle units to be involved by each function.

45. The head unit control remote provider of any of claims 32-44, wherein the control data received from the UE are setting values, wherein the controller (130) is configured to perform a feedback-based loop control based on feedback values from the head unit remote control system (102) and to provide control data to the head unit remote control system (102).

46. The head unit control remote provider of any of claims 32-45, configured to provide, to the UE, the executable code without APIs.

47. The head unit control remote provider of any of claims 32-46, configured to provide, to the head unit control system, the command data without APIs.

48. The head unit control remote provider of any of claims 32-47, configured to switch to the off- boarding mode in case of the vehicle being turned off as for information from the head unity control system.

49. The head unit control remote provider of any of claims 32-48, configured to switch to the off- boarding mode in case of a destination being reached according to a navigation system connected to the head unit control remote provider.

50. The head unit control remote provider of any of claims 32-49, configured to switch to the off- boarding mode in case of UE deviating for a pre -determined distance from the position of the vehicle based on positions determined for both the vehicle and the UE.

51. A user equipment, UE (300), for controlling at least one vehicle function through a head unit control system (102) installed in a vehicle, the UE including: a user interface for interacting with a user; an acquiring unit for acquiring authenticating information (251) received from an output unit (252) controlled by the head unit control system (102); an authentication unit (360) to perform, through a remote connection (403), a remote authentication process providing the authenticating information (251) to a head unit remote control provider (400), and to receive an authorization result from the head unit remote control provider (400); a remote control unit (360) to control the at least one vehicle function through the remote connection and the head unit control provider, the at least one vehicle function involving the use of a set of vehicle devices (210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the UE (300) is configured to selectively have, for each vehicle function, an onboard- ing / offboarding mode (310) switchable (311) between an onboarding mode and an offboarding mode based on the authorization based on the authorization result, so as to switch to the onboarding mode, wherein in the onboarding mode, a control connection is activated (311) through which the UE (300) interfaces with the remote entity (400) to control the at least one function, and in the offboarding mode, the control connection is deactivated.

52. The UE of claim 51 , configured to receive, to an address corresponding to the UE (300), the authenticating information via link invitation.

53. The UE of any of claims 51-52, wherein the authenticating information (251) being a QR code.

54. The UE of any of claims 51-53, wherein the at least one vehicle function includes at least one heating, ventilation and / or air conditioning function.

55. The UE of any of claims 51-54, wherein the at least one vehicle function includes at least one multimedia rendering function.

56. The UE of any of claims 51-55, wherein the at least one vehicle function includes at least one taxi billing function.

57. The UE of any of claims 51-56, configured to receive, from the remote entity, executable code without APIs.

58. A method for a head unit control system (102) controlling at least one vehicle function in a vehicle (200) from a user equipment, UE (300), the at least one vehicle function involving the use of a set of vehicle devices (210, 210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the head unit control system (102) selectively has, for each vehicle function, an onboard- ing / offboarding mode switchable (111) between an onboarding mode and an offboarding mode based on a reception, from a remote entity (400), of onboarding state information indicating that the UE (300) has been authenticated, so as to switch to the onboarding mode, the method including controlling the at least one vehicle function, wherein in the onboarding mode, a control connection is activated (111) through which the head unit control system (102) interfaces both the UE (300) and the at least one vehicle function, so as to receive control data from the UE (300) and control the at least one vehicle function based on the control data received from the UE (300), and in the offboarding mode, the control connection is deactivated.

59. A method for remotely controlling a vehicle function in a vehicle, comprising: authenticating a user equipment, UE, by comparing UE’s authenticating information, received from the UE, with authenticating information associated with a vehicle; and, in case of positive authentication: controlling providing the UE with a user interface or code executable by the UE causing the code to provide a user interface to remotely control at least one vehicle function; receiving from the UE control data inputted through the user interface; providing the control data to the head unit control system, so that the head unit control system controls the at least one vehicle function.

60. A method for controlling at least one vehicle function through a head unit control system (102) installed in a vehicle, the method including: interacting with a user through a user interface at a user equipment, UE; acquiring authenticating information (251) received from an output unit (252) controlled by the head unit control system (102); performing, through a remote connection (403), a remote authentication process providing the authenticating information (251) to a head unit remote control provider (400), and receiving an authorization result from the head unit remote control provider (400); controlling the at least one vehicle function through the remote connection and the head unit control provider, the at least one vehicle function involving the use of a set of vehicle devices (210,210a, 210b, 210c, 210d), the set of vehicle devices having at least one vehicle device, wherein the involves selectively having, for each vehicle function, an onboarding / offboarding mode (310) switchable (311) between an onboarding mode and an offboarding mode based on the authorization based on the authorization result, so as to switch to the onboarding mode, wherein in the onboarding mode, a control connection is activated (311) through which theUE (300) interfaces with the remote entity (400) to control the at least one function, and in the offboarding mode, the control connection is deactivated.

Images