Vehicle comprising a client device and server device

Abstract

A vehicle 12 comprising sensors 16 which send data 18 from the vehicles cabin to a client device 14. The client device detects a user 22 from features in the data 20 and selects a matching stored user

Description

FIELD OF THE INVENTION

[0001] The present invention relates to the field of automobiles. More specifically, the present invention relates to a vehicle comprising a client device for setting a release state of a set of vehicle deployed services of the vehicle as well as a corresponding server device. BACKGROUND INFORMATION

[0002] Certain services offered by a vehicle are locked by default and can only be used by the driver if the relevant service is released. At present, predefined set of vehicle deployed services are provided for release, which include a preset composition of the services. However, the composition of the services cannot be selected individually by the user. In addition, the set of vehicle deployed services must be selected when the vehicle is purchased or commissioned and cannot be changed subsequently.

[0003] Existing solutions therefore have a low level of fluidity because they cannot respond to individual user needs and changes in those needs. SUMMARY OF THE INVENTION

[0004] It is an object of the present invention to provide a vehicle as well as a server device enabling a fluid provision of services of a vehicle.

[0005] This object is solved by a vehicle as well as a server device according to the independent claims. Advantageous embodiments are presented in the dependent claims.

[0006] According to a first aspect of the present invention, a vehicle comprising a client device for setting a release state of a set of vehicle deployed services of the vehicle is provided.

[0007] The vehicle can be configured as a car or a truck. The vehicle may also include hybrid, electric, or any other type of powered automobile. The vehicle is configured to carry passengers. The client device is configured as a control unit configured to manage access to the services provided by the vehicle.

[0008] The release of each service of the set of services provided by the vehicle depends on the release status of the set of services provided by the vehicle. In other words, the vehicle provides the services. The services provided by the vehicle constitute the set of vehicle deployed services. The release state defines which of the services provided by the vehicle are currently enabled. Enabled may mean accessible or unlocked. The release state can therefore describe which of the services are currently locked and which of the services are currently unlocked.

[0009] The vehicle comprises sensor devices configured to monitor a cabin of the vehicle. The sensor devices may comprise camera devices, microphone devices, seat balance devices or radio devices. The sensor devices monitor the interior of the vehicle and generate corresponding sensor data. The sensor data may include images of the cabin, videos of the cabin, sounds recorded in the cabin, a weight on a seat in the cabin, or radio devices detected in the cabin.

[0010] The client device is configured to detect identification features in the sensor data. The identification features are features of the sensor data that are suitable for identifying a user. In other words, the client device is configured to search the sensor data for the identification features. The identification features are features for identifying a user. The identification features may be a face in an image, a voice in an audio, a weight on a seat or a detected radio device. In other words, the client device is configured to detect a face, voice or weight of a passenger as an identification feature in the sensor data. The client device is configured to use the identification features to identify the respective user. The identification may be performed by comparing the detected identification features with identification features of stored user profiles. The client device is configured to select the stored user profile of the identified user in a memory device of the client device. In other words, the client device is configured to use the identification features to identify the user in the cabin of the vehicle and to select the respective user profile of the user.

[0011] The client device is configured to set the release state of the set of vehicle deployed services of the vehicle according to a service release configuration of the selected user profile. In other words, the user profile is associated with the identified user and comprises the respective service release configuration. The service release configuration determines which service of the set of vehicle deployed services of the vehicle is released for the respective user.

[0012] The client device is configured to release the services provided by the vehicle according to the service release configuration of the selected user profile. The client device may release certain services of the set of vehicle deployed services of the vehicle and / or lock certain services of the set of vehicle deployed services of the vehicle according to the service release configuration.

[0013] The invention has the advantage that the service release configuration is linked to the user in the cabin of the vehicle identified by the client device and not to the vehicle. It is therefore possible to tailor the enabling of services to the user.

[0014] According to a further aspect of the present invention, the client device is configured to detect request features in the sensor data. The request features are related to a change in the release state of the set of vehicle deployed services of the vehicle, wherein the client device is configured to change the service release configuration of the selected user profile based on the detected request features.

[0015] According to a further aspect of the present invention, the client device is configured to generate a user profile associated with the passenger of the vehicle based on the detected identification features. The client device is configured to generate the service release configuration of the generated user profile according to a default service release configuration. The client device is configured to store the generated user profile in the memory device of the client device.

[0016] According to a further aspect of the present invention, the client device is configured to log a usage history of the usage of a service by the user in the user profile of the user.

[0017] According to a further aspect of the present invention, the client device is configured to control an output interface device of the vehicle to provide a proposition message to the user. The proposition message indicates a specific service of the set of vehicle deployed services of the vehicle that is locked in the service release configuration. The proposed service is selected based on the usage history and / or based on the identification features of the person.

[0018] According to a further aspect of the present invention, the client device is configured to receive input data of a user input interface of the vehicle and to change the service release configuration of the user profile based on the input data.

[0019] According to a further aspect of the present invention, the client device is configured to connect to a server device external to the vehicle and to synchronise the user profile stored in the memory device of the client device with a corresponding user profile stored on the server device.

[0020] According to a second aspect of the present invention, a server device is provided, the server device being configured to store a user profile in a server memory device of the server device. The user profile is associated with a user and comprises a release state configuration of the set of vehicle deployed services provided by the vehicle. The server device is configured to connect to a client device of the vehicle and to synchronise the user profile stored in the server memory device of the server device with the corresponding user profile stored in the memory device of the client device. According to a further aspect of the present invention, the server device comprises an interface device configured to receive control data relating to the user profile. The server device is configured to adjust the service release configuration of the selected user profile based on the received control data.

[0021] A computing unit may in particular be understood as a data processing device, which comprises processing circuitry. The computing unit can therefore in particular process data to perform computing operations. This may also include operations to perform indexed accesses to a data structure, for example a look-up table, LUT.

[0022] In particular, the computing unit may include one or more computers, one or more microcontrollers, and / or one or more integrated circuits, for example, one or more application-specific integrated circuits, ASIC, one or more field-programmable gate arrays, FPGA, and / or one or more systems on a chip, SoC. The computing unit may also include one or more processors, for example one or more microprocessors, one or more central processing units, CPU, one or more graphics processing units, GPU, and / or one or more signal processors, in particular one or more digital signal processors, DSP. The computing unit may also include a physical or a virtual cluster of computers or other of said units.

[0023] In various embodiments, the computing unit includes one or more hardware and / or software interfaces and / or one or more memory units.

[0024] A memory unit may be implemented as a volatile data memory, for example a dynamic random access memory, DRAM, or a static random access memory, SRAM, or as a non-volatile data memory, for example a read-only memory, ROM, a programmable read-only memory, PROM, an erasable programmable read-only memory, EPROM, an electrically erasable programmable read-only memory, EEPROM, a flash memory or flash EEPROM, a ferroelectric random access memory, FRAM, a magnetoresistive random access memory, MRAM, or a phase-change random access memory, PCRAM.

[0025] Further advantages, features, and details of the invention derive from the following description of preferred embodiments as well as from the drawings. The features and feature combinations previously mentioned in the description as well as the features and feature combinations mentioned in the following description of the figures and / or shown in the figures alone can be employed not only in the respectively indicated combination but also in any other combination or taken alone without leaving the scope of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The novel features and characteristic of the disclosure are set forth in the appended claims. The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and / or methods in accordance with embodiments of the present subject matter are now described below, by way of example only, and with reference to the accompanying figures.

[0027] The drawings show in:

[0028] Fig. 1 a schematic illustration of a service system;

[0029] Fig. 2 a schematic illustration of a client device; and

[0030] Fig. 3 a system comprising a vehicle provided with a client device and a server device.

[0031] In the figures the same elements or elements having the same function are indicated by the same reference signs. DETAILED DESCRIPTION

[0032] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0033] While the disclosure is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawing and will be described in detail below. It should be understood, however, that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.

[0034] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion so that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus preceded by “comprises” or “comprise” does not or do not, without more constraints, preclude the existence of other elements or additional elements in the system or method.

[0035] In the following detailed description of the embodiment of the disclosure, reference is made to the accompanying drawing that forms part hereof, and in which is shown by way of illustration a specific embodiment in which the disclosure may be practiced. This embodiment is described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

[0036] Fig. 1 shows a schematic illustration of a service system.

[0037] The service system 10 may comprise a vehicle 12 comprising a client device 14. The vehicle 12 may comprise sensor devices 16 configured to monitor a cabin of the vehicle 12 and to provide respective sensor data 18 to the client device 14. The sensor data 18 may be image data captured by a camera, radio frequency signals detected by an RFID reader, temperature readings from a thermal sensor, or pressure measurements from a load cell. The sensor data 18 may further comprise sound data recorded by a microphone inside the cabin.

[0038] In other words, the sensor data 18 may refer to information collected from the sensor devices 16 of the vehicle 12. The sensor devices 16 may monitor the cabin of the vehicle 12 and generate the corresponding sensor data 18. The sensor data 18 may comprise different types of data depending on the specific sensor devices 16 used. For example, image sensors such as cameras may capture visual data of the cabin and its occupants. Audio sensors may record sounds within the cabin, while temperature sensors may detect the temperature in various parts of the vehicle. Pressure sensors or load cells may measure weight or force exerted on seats, while radio sensors such as RFID readers may detect radio frequency signals from devices such as key fobs or smartphones.

[0039] Other examples of the sensor data 18 may include biometric readings such as a heart rate or a blood pressure, which may be received from wearable devices worn by the occupants. Motion sensors may track movements within the cabin, while infrared sensors may detect heat signatures of objects and the occupants in the vehicle 12.

[0040] The client device 14 may be configured to identify identification features 20 in the sensor data 18. The identification features 20 may comprise features of the sensor data 18 that may allow an identification of a user 22 of the vehicle 12 in the cabin. The identification features 20 that may be detected in the sensor data 18 by the client device 14 may be those characteristics of the users 22 that may be used to identify the respective users 22 uniquely. The identification features 20 may include, but are not limited to, facial recognition markers, barcode or QR code patterns, RFID tags, and unique biometric characteristics such as fingerprints or iris patterns.

[0041] The facial recognition markers refer to specific features of a user's 22 face that may be used to identify him. This could include the distance between his eyes, the width of his nose, or the shape of his jawline. The client device 14 may use a camera installed in the cabin of the vehicle 12 to capture images of the user's 22 face and then use facial recognition algorithms to detect these facial recognition markers and identify the user 22.

[0042] The identification features 20 may comprise a barcode or a QR code to identify the user 22. These barcodes or a QR codes may be scanned using a barcode reader or the camera installed in the cabin of the vehicle 12, and the unique barcode or QR code may be used to identify the user 22. The user 22 may show screen of a smartphone or an identity card with the barcode or the QR code to the camera for identification.

[0043] RFID tags are small devices that emit radio frequencies which may be detected by an RFID reader installed in the vehicle 12. These tags contain unique identifiers that may be used as the identification features 20 to identify the user 22. The RFID tags may embedded in a variety of objects, such as key fobs, wristbands, or smartcards.

[0044] Unique biometric characteristics, such as the fingerprints or iris patterns are unique to each individual user and cannot be easily replicated or changed. The client device 14 may receive sensor data 18 from a sensor device 16 configured as a biometric scanner installed in the vehicle 12 to detect these identification features 20 and identify the user 22.

[0045] In addition to the above, the client device 14 may also use other characteristics for user identification based on the sensor data 18 collected. For example, the system may use voice recognition algorithms to identify a user 22 by his speech pattern. The client device 14 may also use other sensors devices 16 installed in the vehicle 12, such as temperature sensors or pressure sensors, to detect unique identification features 20 of the user 22, such as his preferred seating temperature or weight distribution.The client device 14 may be configured to compare the identification features 20 with identification features 20 of user profiles 24 stored in a memory device 26 of the client device 14, wherein each of the user profiles 24 may be associated with the respective user 22. Each of the user profiles 24 may comprise a service release configuration defining a respective release state of services of a set of vehicle deployed services of the vehicle 12. The client device 14 may be configured to set the release state of the set of vehicle deployed services of the vehicle 12 according to the service release configuration of the selected user profile 24. In other words, some of the services may be locked for the user 22, while other of the services may be enabled for the user 22.

[0046] If the user profile 24 has not yet been generated for the respective user 22, the client device 14 is configured to generate a new user profile 24 for the respective user 22. The client device 14 may be configured to generate the service release configuration of the generated user profile 24 according to a default service release configuration. The client device 14 may be configured to store the generated user profile 24 in the memory device 26 of the client device 14.

[0047] The user 22 can use the released services of the vehicle 12. The client device 14 may be configured to record a usage history of the services used by the user in the user profile 24.

[0048] It may be that the user 22 wishes to enable a service of the vehicle 12. Therefore, the client device 14 may be configured to receive input data from a user input interface of the vehicle 12 to change the service release configuration of the user profile 24 based on the input data. For example, the user 22 may use the user input interface, such as a touch screen, to select the respective service of the set of vehicle deployed services to be enabled.

[0049] The client device 14 may be configured to detect request features 28 in the sensor data 18 wherein the request features 28 are related to a change of the release state of the set of vehicle deployed services of the vehicle 12. An example the user 22 may talk about a service to be released. The client device 14 may be configured to identify the user 22's voice and to detect the request feature 28 describing a service of the set of vehicle deployed services to be released. The client device 14 may identify the service to be released and change the service release configuration to release the service according to the request feature 28.

[0050] The client device 14 may be configured to analyse the usage history of the user 22 and / or to analyse the identification features 20 of the user 22 to provide a proposition message to the user 22 via a vehicle 12 output interface. The proposition message indicating a specific service of the set of vehicle deployed services currently locked in the service release configuration of the user 22. In other words, the client device 14 may propose the service to the user 22. The proposed service may depend on the user 22's usage history and / or identification feature 20. It may be that the client device 14 proposes the service which is similar to other services used by the user 22. The client device 14 may also propose the service based on the user 22's identification feature 20. It may be possible to propose certain services to the user 22 that are popular with users 22 of the same age as the user 22. The client device 14 may be configured to synchronise the user profile 24 in the memory device 26 of the client device 14 with a server memory device 32 of an external server device 30. Therefore, it is possible to provide the user profile 24 to the client device 14 of another vehicle 12 via the server device 30.

[0051] A policy for the user 22 may be provided in the client device 14. The policy for the user 22 may be a configurable file that may govern behavior of the client device 14 in various situations. The policy for the user 22 may be managed either by the user 22 or the server device 30. This policy allows the client device 14 to propose the services based on specific criteria such as the user’s 22 behavior, a current time and date, company or owner's promotions, or explicit actions of the user 22. The proposed service may be enabled permanently, for the duration of a car ownership, situationally, on-demand, subscription-based, or trial basis.

[0052] For example, if the user 22 frequently accelerates the vehicle 12 significantly at green lights, the client device 14 may propose an additional horsepower service. Alternatively, if it is currently dark outside vehicle 12, the client device 14 could propose a "blinding lights" package that increases headlight illumination. The client device 14 may also use out-of-band notifications such as email or text to inform the user 22 of new services, such as a recently enabled “Chicken Detection Service”.

[0053] Based on the policy, the client device 14 may also suggest promotions like free movie watching for the user 22 during a specific week. This promotion might appear in the user interface device 36 of the vehicle 12, or the user 22 may receive an in-or-out-of-band notification when starting the vehicle 12. The user 22 may explicitly enable or disable services through the user interface device 36, a website, or an app.

[0054] The service could be enabled situationally based on specific conditions such as driving at night or when the specific user 22 is driving the vehicle 22. The service may also be enabled on demand in certain situations like at night when driving in Utah.

[0055] Prices for these services could be fixed or fluctuate based on activity, circumstances, or current location. For example, a cost of a service might increase due to higher demand in Utah or during rainy weather.

[0056] In summary, the client device 14 may use the policy file to govern behavior and propose services to users 22 based on specific criteria. The client device 14 offers flexible options for enabling services, including permanent, situational, on-demand, subscriptionbased, or trial basis pricing. This approach allows users 22 to personalize their driving experience and take advantage of promotions and new services as they become available.

[0057] Fig. 2 shows a schematic illustration of a client device.

[0058] The client device 14 may be configured to receive the sensor data 18 from the sensor devices 16 of the vehicle 12. The sensor data 18 may comprise images, voices or other parameters of the cabin which may be used to identify a user 22 of the vehicle 12. The client device 14 may receive the sensor data 18 and analyse the sensor data 18 for the identification features 20. The client device 14 may be configured to identify a person based on the identification features 20 and to select the respective user profile 24 of the user 22. The identification may be performed by the client device 14 itself or by the server device 30.

[0059] Fig. 3 shows a system comprising a vehicle provided with a client device and a server device.

[0060] The server device 30 may comprise a server memory device 32 for storing user profiles 24 of the users 22. The user profiles 24 may be synchronised between the server device 30 and the client device 14 of the vehicle 12 via a mobile connection. A user 22 may use a user device 34 or a user interface device 36 of the vehicle 12 to send control data to the server device 30. The control data may be related to a change of the service release configuration of the user profile 24. Therefore, the server device 30 may change the service release configuration of the user profile 24.

[0061] Customization is a key for everyone to reach their perfect luxury driving experience. Customers should be able to easily do all these at the service or package levels. In particular, customers should be able to activate services and offerings via an app, in vehicle 12, or on their computer, all of which act as a central hub for service customization.

[0062] Customers should be able to activate services and offerings on an ephemeral basis for example, a satellite radio service may be activated just for one weekend. It should be passible to activate / deactivate the services depending on the driver / passengers. A first user 22 may want to use a satellite radio service, a second user 22 wants to use enhanced maps / weather services, but not the satellite radio service, etc.

[0063] The services may include not only entertainment digital offerings, but also more physical things like additional engine power / acceleration, off-road lighting.

[0064] Users 22 may want to have different tiers of service. Currently you either have it or not. But why can't we have the platinum, gold, silver, brass or whatever levels of the different services, all with different pricing, offerings, etc.

[0065] This may also provide ancillary services. One may elect to subscribe to the premium infotainment system or alternatively, procure the basic radio with a single satellite radio channel of particular interest.

[0066] The current implementation comprises three elements: user profiles 24, service IDs, and vehicle 12 information. These three elements are interrelated, enabling the determination of which customer has which service for which vehicle 12. In order to achieve further levels of service differentiation, it is necessary to implement different levels of services, such as basic autonomous driving versus advanced.

[0067] The device may also include a pay-as-you-use model, whereby services are only charged for when they are utilised. The customer is not required to enroll in or sign up for any services; they may simply be billed on a per-use basis.

[0068] The vehicle 12 should be able to recognise the driver and / or passengers via a combination of factors, utilising sensors within the car. These could include video cameras, which would register the weight of each passenger as they sit in their seat, or microphones, which would pick up voices. The vehicle 12 could also measure its overall weight as each passenger enters. This data would be used to create a profile of each person, based on their height, weight, and visual appearance. If necessary, this process could be conducted entirely within the vehicle 12 itself. However, more accurate predictive models could also be created by sending sensor data 18 back to the central server, where it would be generated and stored, as well as compared to other drivers or online data.

[0069] Subscription data is stored in both the vehicle 12 and the servers. These are kept in sync when updates occur, as well as when usage is made of the vehicle 12. This includes signing up for new services, for example.

[0070] The communication between vehicle 12 and server devices 30 is done wirelessly via any number of different conduits, including WiFi, MNOs, Bluetooth, and so on.

[0071] Currently, services are provided with the vehicle 12, and the licensing model is perpetual. In the near future, new vehicles 12 will be available with the subscription model described above. To enable atomic services, a pay-as-you-go model will be required, which means that the cost is not based on a day or month, but on the actual usage of the customer.

[0072] The device is capable of generating a dynamic profile based on the physical characteristics of the individuals involved. The vehicle 12 is equipped with cameras, seats that register weight, and microphones. These can be used to construct a profile of individuals in the vehicle 12. The processing of sensor readings is dependent on the selected model, although in theory, the entire process could be completed on-board or at the very least, captured locally. In a further optional step, the sensor or MUAI models are transmitted to the cloud, where they may undergo further processing or even be used to identify the user in other vehicles 12. For instance, if a user 22 rents a car, the system may recognize them from their previous vehicle 12. Furthermore, metadata can be employed to enhance this process. For instance, a rental agency may provide the car with the name of the driver, which can facilitate communication between the two and assist in identifying the driver from the server.

[0073] The entity's profile would be updated over time, with the intention of assisting in the identification of a user 22.

[0074] Upon initial use of the vehicle 12, the user 22 is presented with a range of options. Additional options may be accessed by interacting with the vehicle 12 via an app on a mobile phone, voice control, the physical controls available, and so forth.

[0075] It is anticipated that the user 22 will be able to simply request satellite radio service, or a similar service, and have it enabled with minimal delay, or as soon as the software allows. The same principle applies to the pausing or removal of a service.

[0076] It is possible that the device may generate a fictitious profile, which would serve to clarify the variables that contribute to the generation of the profile, including weight, height, seating position within the vehicle 12, and so forth. It is evident that this system must interact with a number of other services in order to generate a profile. These include a face recognition algorithm, a classification algorithm, and so forth. It is possible that additional modules may be required. For instance, if the backseat is occupied and the weight and height fall within a specified range, there is an 80% probability that the occupant is a child. The second component of the system, which is the provision of a list of services, may be implemented using conversational Al. signs service system vehicle client device sensor device sensor data identification feature user user profile memory device request feature server device server memory device user device user interface device

Claims

1. A vehicle (12) comprising a client device (14) for setting a release state of a set of vehicle deployed services of the vehicle (12), characterized in that- the vehicle (12) comprises sensor devices (16), configured to monitor a cabin of the vehicle (12), to generate respective sensor data (18) and to provide the respective sensor data (18) to the client device (14),- the client device (14) is configured to detect identification features (20) in the sensor data (18), wherein the identification features (20) are related to a user (22) of the vehicle (12),- the client device (14) is configured to select a stored user profile (24) in a memory device of the client device (14) based on the detected identification features (20), wherein the stored user profile (24) is assigned to the user (22) of the vehicle (12);and- the client device (14) is configured to set the release state of the set of vehicle deployed services of the vehicle (12) according to a service release configuration of the selected user profile (24).

2. The vehicle (12) according to claim 1, characterized in that- the client device (14) is configured to detect request features (28) in the sensor data (18), wherein the request features (28) are related to a change of the release state of the set of vehicle deployed services of the vehicle (12); and- the client device (14) is configured to change the service release configuration of the selected user profile (24) based on the detected request features (28).

3. The vehicle (12) according to claim 1 or 2, characterized in that- the client device (14) is configured to generate a user profile (24) assigned to the user (22) of the vehicle (12) based on the detected identification features (20), wherein- the client device (14) is configured to generate the service release configuration of the generated user profile (24) according to a default service release configuration, and- the client device (14) is configured to store the generated user profile (24) in the memory device of the client device (14).

4. The vehicle (12) according to any one of the preceding claims, characterized in that- the client device (14) is configured to log a usage history of a service by the person in the user profile (24).

5. The vehicle (12) according to any one of the preceding claims, characterized in that- the client device (14) is configured to control an output interface device of the vehicle (12) to provide a proposition message to the user (22), wherein the proposition message indicates a specific service of the set of vehicle deployed services locked in the service release configuration, selected based on the usage history and / or based on the identification features (20) of the person.

6. The vehicle (12) according to any one of the preceding claims, characterized in that- the client device (14) is configured to receive input data of a user (22) input interface of the vehicle (12) and to change the service release configuration of the user profile (24) based on the input data.

7. The vehicle (12) according to any one of the preceding claims, characterized in that- the client device (14) is configured to connect to a server device (30) external to the vehicle (12) and to synchronize the user profile (24) stored in the memory device (26) of the client device (14) with a respective user profile (24) stored on the server device (30).

8. A server device (30), characterized in that - the server device (30) is configured to store a user profile (24) in a server memory device (32) of the server device (30); wherein the user profile (24) is assigned to a passenger of a vehicle (12) and comprises a release state of a service provided by a vehicle (12); and- the server device (30) is configured to connect to a client device (14) of a vehicle (12) and to synchronize the user profile (24) stored in the server memory device (32) of the server device (30) with a respective user profile (24) stored in the memory device (26) of the client device (14).

9. The server device (30) according to claim 8, characterized in that- the server device (30) comprises an interface device, configured to receive control data related to the user profile (24), and- the server device (30) is configured to change the service release configuration of the selected user profile (24) based on the received control data.19

Images