Vehicle with a client device and a server device

Abstract

The invention relates to a vehicle (12) comprising a client device (14) for setting an enable state of a set of services used in the vehicle (12). The vehicle (12) includes sensor devices (16) configured to monitor the interior of the vehicle (12), generate corresponding sensor data (18), and deliver the corresponding sensor data (18) to the client device (14). The client device (14) is configured to recognize 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 storage 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).The client device (14) is configured to set the release state of the set of services provided by the vehicle (12) according to a service release configuration of the selected user profile (24).

Description

AREA OF INVENTION

[0001] The present invention relates to the field of motor vehicles. In particular, the present invention relates to a vehicle comprising a client device for setting an enable state of a set of services used in the vehicle, as well as a corresponding server setup. BACKGROUND INFORMATION

[0002] Certain services offered by a vehicle are disabled by default and can only be used by the driver if the respective service is enabled. Currently, predefined sets of vehicle services are available for activation, containing a pre-configured combination of services. However, the specific combination of services cannot be individually selected by the user. Furthermore, the set of vehicle services must be selected when purchasing or registering the vehicle and cannot be changed later.

[0003] Existing solutions therefore have a low degree of flexibility, as they cannot respond to the individual needs of users and their changes. SUMMARY OF THE INVENTION

[0004] It is an object of the present invention to provide a vehicle and a server facility that enables the smooth provision of services from a vehicle.

[0005] This task is accomplished by a vehicle and a server device according to the independent claims. Advantageous embodiments are described in the dependent claims.

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

[0007] The vehicle can be configured as a car or truck. It can also be a hybrid, electric, or other type of motor vehicle. The vehicle is configured to transport passengers. The client device is configured as a control unit that manages access to the services provided by the vehicle.

[0008] The availability of each service provided by the vehicle depends on the availability status of those services. In other words, the vehicle provides the services. The services provided by the vehicle constitute the set of services provided by the vehicle. The availability status determines which of the services provided by the vehicle are currently enabled. Availability can mean that they are accessible or not locked. The availability status can therefore describe which of the services are currently locked and which of the services are currently unlocked.

[0009] The vehicle includes sensor equipment configured to monitor the vehicle's interior. This sensor equipment may include cameras, microphones, seat leveling devices, or radio equipment. The sensor equipment monitors the vehicle's interior and generates corresponding sensor data. This data may include images of the cabin, videos of the cabin, sounds recorded in the cabin, weight on a seat in the cabin, or radio signals detected in the cabin.

[0010] The client device is configured to recognize identification features in the sensor data. These identification features are characteristics of the sensor data that are suitable for identifying a user. In other words, the client device is configured to scan the sensor data for these identification features. Identification features can be a face in an image, a voice in audio, a weight on a seat, or a detected radio. In other words, the client device is configured to recognize a passenger's face, voice, or weight as an identification feature in the sensor data. The client device is configured to use these identification features to identify the respective user.Identification can be achieved by comparing the recognized identification features with the identification features of stored user profiles. The client device is configured to select the identified user's stored profile from its own storage. In other words, the client device is configured to use the identification features to identify the user in the vehicle cabin and select the corresponding user profile.

[0011] The client device is configured to set the sharing state of the vehicle's services according to the service sharing configuration of the selected user profile. In other words, the user profile is assigned to the identified user and includes the respective service sharing configuration. The service sharing configuration determines which service from the vehicle's set of services is shared with the respective user.

[0012] The client device is configured to enable the services provided by the vehicle according to the service enabling configuration of the selected user profile. The client device can enable and / or disable specific services from the vehicle's set of services, according to the service enabling configuration.

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

[0014] According to a further aspect of the present invention, the client device is configured to recognize request characteristics in the sensor data. These request characteristics relate to a change in the enable state of the set of services used in the vehicle, and the client device is configured to change the service enable configuration of the selected user profile based on the recognized request characteristics.

[0015] According to a further aspect of the present invention, the client device is configured to generate a user profile based on the recognized identification features, which is linked to the vehicle passenger. The client device is configured to generate the service sharing configuration of the created user profile according to a standard service sharing configuration. The client device is configured to store the generated user profile in the client device's storage device.

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

[0017] According to a further aspect of the present invention, the client device is configured to control an output interface of the vehicle in order to transmit a suggestion message to the user. The suggestion message specifies a particular service from the set of services used in the vehicle that is blocked in the service release configuration. The suggested service is selected based on the usage history and / or the identification characteristics of the person.

[0018] According to another aspect of the present invention, the client device is configured to receive input data from 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 another aspect of the present invention, the client device is configured to establish a connection to a server device outside the vehicle and to synchronize the user profile stored in the storage 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, wherein the server device is configured to store a user profile in a server storage device of the server device. The user profile is associated with a user and includes a release state configuration of the set of services provided by the vehicle. The server device is configured to connect to a client device of the vehicle and synchronize the user profile stored in the server storage device of the server device with the corresponding user profile stored in the storage device of the client device. According to a further aspect of the present invention, the server device includes an interface device configured to receive control data relating to the user profile.The server device is configured to adjust the service sharing configuration of the selected user profile based on the received control data.

[0021] A computing unit can be understood, in particular, as a data processing device that includes processing circuits. The computing unit can therefore process data in order to perform arithmetic operations. These can also include operations for performing indexed access to a data structure, such as a lookup table (LUT).

[0022] In particular, the computing unit may comprise one or more computers, one or more microcontrollers, and / or one or more integrated circuits, such as one or more application-specific integrated circuits (ASICs), one or more field-programmable gate arrays (FPGAs), and / or one or more systems-on-a-chip (SoCs). The computing unit may also include one or more processors, such as one or more microprocessors, one or more central processing units (CPUs), one or more graphics processing units (GPUs), and / or one or more signal processors, in particular one or more digital signal processors (DSPs). The computing unit may also comprise a physical or virtual cluster of computers or other units of the aforementioned type.

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

[0024] A storage unit can be a volatile data storage device, e.g., a dynamic random access memory (DRAM) or static random access memory (SRAM), or a non-volatile data storage device, e.g., a read-only memory (ROM), 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 will become apparent from the following description of preferred embodiments and from the drawings. The features and combinations of features mentioned above in the description, as well as those mentioned in the following description of the figures and / or illustrated in the figures alone, can be used not only in the combinations specified, but also in any other combination or on their own, without departing from the scope of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The new features and properties of the disclosure are set forth in the accompanying claims. The accompanying drawings, which form part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the leftmost digit(s) of a reference number indicates the figure in which the reference number first appears. The same numbers are used in the figures to refer to identical features and components. Some embodiments of systems and / or methods in accordance with embodiments of the present subject matter are described below only by way of example and with reference to the accompanying figures.

[0027] The drawings show in: Fig. Figure 1 is a schematic representation of a service system; Fig. 2 a schematic representation of a client device; and Fig. 3 a system with a vehicle equipped with a client device and a server device.

[0028] In the figures, identical elements or elements with the same function are indicated by the same reference symbols. DETAILED DESCRIPTION

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

[0030] While the disclosure is open to various modifications and alternative forms, specific embodiments are illustrated by way of example in the drawing and are described in detail below. It should be understood, however, that the disclosure is not intended to be limited to these particular forms, but rather covers all modifications, equivalents, and alternatives that fall within the scope of the disclosure.

[0031] The terms “includes,” “contains,” or other variations thereof are intended to cover non-exclusive inclusion, so that a system, device, or process that includes a list of components or steps may contain not only those components or steps but may also contain other components or steps not expressly listed or belonging to such system, device, or process. In other words, one or more elements in a system or device preceded by the expression “includes” or “include” do not, without further limitations, preclude the presence of other elements or additional elements in the system or process.

[0032] The following detailed description of the embodiment of the disclosure refers to the accompanying drawing, which forms part of the disclosure and illustrates a specific embodiment in which the disclosure can be implemented. This embodiment is described in sufficient detail to enable the person skilled in the art to apply the disclosure, and it is understood that other embodiments may be used and that modifications may be made without infringing the scope of this disclosure. The following description is therefore not to be understood in a restrictive sense.

[0033] Fig. Figure 1 shows a schematic representation of a service system.

[0034] The service system 10 can include a vehicle 12 with a client device 14. The vehicle 12 can include sensor devices 16 configured to monitor the interior of the vehicle 12 and provide corresponding sensor data 18 to the client device 14. The sensor data 18 can be image data captured by a camera, radio frequency signals captured by an RFID reader, temperature readings from a thermal sensor, or pressure measurements from a load cell. The sensor data 18 can also include sound data recorded by a microphone in the cabin.

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

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

[0037] The client device 14 can be configured to recognize identification features 20 in the sensor data 18. These identification features 20 can include characteristics of the sensor data 18 that enable the identification of a user 22 of the vehicle 12 in the cabin. The identification features 20 that can be recognized in the sensor data 18 by the client device 14 can be user 22 characteristics that can be used to uniquely identify the respective user 22. These identification features 20 can include, among other things, facial recognition markings, barcode or QR code patterns, RFID tags, and unique biometric features such as fingerprints or iris patterns.

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

[0039] The identification features 20 can include a barcode or a QR code for identifying the user 22. These barcodes or QR codes can be scanned with a barcode reader or the camera 12 installed inside the vehicle, and the unique barcode or QR code can be used to identify the user 22. The user 22 can hold the screen of a smartphone or an identity card displaying the barcode or QR code up to the camera for identification.

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

[0041] Unique biometric characteristics such as fingerprints or iris patterns are unique to each individual user and cannot be easily copied or altered. The client device 14 can receive sensor data 18 from a sensor unit 16, which is installed as a biometric scanner in the vehicle 12, in order to recognize these identification characteristics 20 and identify the user 22.

[0042] In addition to the features mentioned above, the client device 14 can also use other features for user identification based on the acquired sensor data 18. For example, the system can use speech recognition algorithms to identify a user 22 based on their speech pattern. The client device 14 can also use other sensor devices 16 installed in the vehicle 12, such as temperature or pressure sensors, to detect unique identification features 20 of the user 22, such as their preferred seat temperature or weight distribution. The client device 14 can 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, with each of the user profiles 24 being associated with the respective user 22.Each of the user profiles 24 can include a service sharing configuration that defines the respective sharing state of services within a set of services deployed in the vehicle 12. The client device 14 can be configured to set the sharing state of the set of services deployed in the vehicle 12 according to the service sharing configuration of the selected user profile 24. In other words, some of the services may be blocked for user 22, while others may be enabled for user 22.

[0043] If user profile 24 has not yet been created for the respective user 22, client device 14 is configured to create a new user profile 24 for that user 22. Client device 14 can be configured to generate the service share configuration of the created user profile 24 according to a standard service share configuration. Client device 14 can also be configured to store the created user profile 24 in the storage facility 26 of client device 14.

[0044] User 22 can use the shared services of vehicle 12. Client device 14 can be configured to record a usage history of the services used by the user in user profile 24.

[0045] User 22 may wish to activate a service of vehicle 12. Therefore, client device 14 can be configured to receive input data from a user input interface of vehicle 12 in order to modify the service sharing configuration of user profile 24 based on that input data. For example, user 22 can use the user input interface, such as a touchscreen, to select the specific service from the set of services provided by the vehicle that they wish to activate.

[0046] Client device 14 can be configured to detect request characteristics 28 in the sensor data 18, where the request characteristics 28 are associated with a change in the enable state of the set of services used in the vehicle 12. For example, user 22 can speak about a service to be enabled. Client device 14 can be configured to identify user 22's voice and detect the request characteristic 28, which describes a service to be enabled from the group of services used in the vehicle. Client device 14 can identify the service to be enabled and change the service enable configuration to enable the service according to the request characteristic 28.

[0047] Client device 14 can be configured to analyze user 22's usage history and / or user 22's identification attributes 20 in order to send a suggestion message to user 22 via an output interface of vehicle 12. The suggestion message indicates a specific service from the set of services used by the vehicle that is currently blocked in user 22's service release configuration. In other words, client device 14 can suggest the service to user 22. The suggested service can depend on user 22's usage history and / or identification attribute 20. Client device 14 may suggest a service similar to other services used by user 22. Client device 14 can also suggest the service based on user 22's identification attribute 20.It may be possible to suggest specific services to user 22 that are popular with users of the same age. Client device 14 can be configured to synchronize user profile 24 in the storage device 26 of client device 14 with a server storage device 32 of an external server device 30. Therefore, it is possible to make user profile 24 available to another vehicle 12 via the server device 30 of client device 14.

[0048] A policy for user 22 can be deployed on client device 14. This policy can be a configurable file that controls the behavior of client device 14 in various situations. The policy can be managed either by user 22 or by server device 30. This policy allows client device 14 to suggest services based on specific criteria, such as user 22's behavior, the current time and date, company or owner promotions, or explicit actions by user 22. The suggested service can be permanently activated, activated for the duration of vehicle ownership, situationally, on demand, by subscription, or on a trial basis.

[0049] For example, if user 22 frequently accelerates vehicle 12 sharply at green lights, client device 14 can suggest an additional horsepower service. Alternatively, if it is currently dark outside vehicle 12, client device 14 could suggest a "glare-reducing" package that increases headlight brightness. Client device 14 can also use out-of-band notifications, such as email or SMS, to inform user 22 about new services, such as a recently activated "chicken detection service."

[0050] Based on the policy, the client device 14 can also suggest promotions, such as free movie viewing for user 22 during a specific week. This offer can be displayed on the user interface device 36 of the vehicle 12, or user 22 can receive an in-band or out-of-band notification when starting the vehicle 12. User 22 can explicitly enable or disable services via the user interface device 36, a website, or an app.

[0051] The service could be activated situationally based on certain conditions, such as during nighttime driving or when the respective user 22 is driving vehicle 22. The service can also be activated on demand in specific situations, such as driving at night in Utah.

[0052] The prices for these services may be fixed or fluctuate depending on activity, circumstances, or current location. For example, the cost of a service might increase due to higher demand in Utah or during rainy weather.

[0053] In summary, the client device can use the policy file to control behavior and suggest services to users based on specific criteria. The client device offers flexible service activation options, including permanent, contextual, on-demand, subscription-based, or trial pricing. This approach allows users to personalize their driving experience and benefit from special offers and new services as they become available.

[0054] Fig. Figure 2 shows a schematic representation of a client device.

[0055] The client device 14 can be configured to receive sensor data 18 from the sensor array 16 of the vehicle 12. The sensor data 18 can include images, voices, or other cabin parameters that can be used to identify a user 22 of the vehicle 12. The client device 14 can receive the sensor data 18 and analyze it for the identification features 20. The client device 14 can be configured to identify a person based on the identification features 20 and select the respective user profile 24 of the user 22. The identification can be performed by the client device 14 itself or by the server device 30.

[0056] Fig. Figure 3 shows a system with a vehicle equipped with a client device and a server device.

[0057] The server device 30 can include a server storage device 32 for storing user profiles 24 of users 22. The user profiles 24 can be synchronized between the server device 30 and the client device 14 of the vehicle 12 via a mobile connection. A user 22 can 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 can relate to a change in the service sharing configuration of user profile 24. Therefore, the server device 30 can change the service sharing configuration of user profile 24.

[0058] Personalization is key for everyone to achieve their perfect luxury driving experience. Customers should be able to easily do all of this at the service or package level. In particular, customers should be able to activate services and offers via an app, in the vehicle, or on their computer, all of which serve as a central hub for service customization.

[0059] Customers should have the option to activate services and offers for a limited time; for example, satellite radio could be activated for a weekend only. It should also be possible to activate / deactivate services depending on the driver / passenger. One user (22) might want to use a satellite radio service, while a second user (22) might want to use advanced maps / weather services but not the satellite radio service, and so on.

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

[0061] Users might want different service levels. Currently, you either have it or you don't. But why can't we have Platinum, Gold, Silver, Brass, or whatever levels of different services you want, all with different prices, offers, etc.?

[0062] This can also offer additional services. You can opt for the premium infotainment system or, alternatively, purchase the basic radio with a single satellite radio channel of particular interest.

[0063] The current implementation comprises three elements: user profiles 24, service IDs, and vehicle information 12. These three elements are linked and enable the determination of which customer is using which service for which vehicle 12. To achieve further differentiation of services, it is necessary to implement different service levels, e.g., autonomous driving for beginners and for advanced users.

[0064] The device can also include a pay-as-you-use model, where services are only billed when used. The customer does not need to sign up or register for any services; they can simply be billed after use.

[0065] Vehicle 12 should be able to recognize the driver and / or passengers through a combination of factors using sensors within the vehicle. These could include video cameras that register each passenger's weight as they take their seat, or microphones that record voices. Vehicle 12 could also measure its combined weight as each passenger enters. Using this data, a profile of each person could be created based on their height, weight, and appearance. If necessary, this process could be carried out entirely within Vehicle 12 itself. However, more accurate predictive models could also be created by sending the sensor data 18 back to the central server, where it is generated, stored, and compared with data from other drivers or online.

[0066] Subscription data is stored both in the vehicle 12 and on the servers. This data is kept synchronized during updates and when the vehicle 12 is used. This includes, for example, registering for new services.

[0067] Communication between the vehicle 12 and the server devices 30 takes place wirelessly via any number of different lines, including WiFi, MNOs, Bluetooth, etc.

[0068] Currently, the services are provided with the Vehicle 12, and the licensing model is perpetual. In the near future, new Vehicle 12s will be available with the subscription model described above. To enable atomic services, a pay-as-you-go model will be necessary; that is, costs will not be based on a day or month, but on actual customer usage.

[0069] The device is capable of creating a dynamic profile based on the physical characteristics of the individuals involved. Vehicle 12 is equipped with cameras, seats that register weight, and microphones. These can be used to create a profile of the people in vehicle 12. The processing of the sensor measurements depends on the chosen model, although theoretically the entire process could be completed on board or at least captured locally. In a further optional step, the sensor or machine learning / engineering models are transmitted to the cloud, where they can be further processed or even used to identify the user in other vehicles 12. For example, if a user 22 rents a car, the system can recognize them based on their previous vehicle 12. Furthermore, metadata can be used to enhance this process.For example, a car rental company can tell the vehicle the driver's name, which can facilitate communication between the two and support the server in identifying the driver.

[0070] The institution's profile would be updated over time to facilitate the identification of user 22.

[0071] Upon first use of vehicle 12, user 22 is offered a range of options. Additional options can be accessed through interaction with vehicle 12 via a mobile phone app, voice control, the available physical controls, etc.

[0072] User 22 is expected to be able to easily request the satellite radio service or a similar service and activate it with minimal delay, or as soon as the software allows. The same principle applies to interrupting or removing a service.

[0073] It is possible that the device creates a fictitious profile, which would serve to clarify the variables that contribute to profile creation, including weight, height, seating position within the vehicle, and so on. It is obvious that this system will need to work with a number of other services to create a profile. These include a facial recognition algorithm, a classification algorithm, and so forth. Additional modules may be required. For example, if the back seat is occupied and the weight and height fall within a certain range, there is an 80 percent probability that the occupant is a child. The second component of the system, providing a list of services, can be implemented through conversational AI. Reference sign 10 Service system 12 vehicles 14 Client devices 16 Sensor device 18 sensor data 20 Identification feature 22 users 24 User profile 26 Storage setup 28 requirement characteristics 30 server devices 32 Server storage setup 34 User device 36 User Interface Setup

Claims

[1] Vehicle (12) with a client device (14) for setting an enabling state of a set of services of the vehicle (12) used in the vehicle, characterized by , that - the vehicle (12) includes sensor devices (16) configured to monitor the interior of the vehicle (12), generate respective sensor data (18) and deliver 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 storage device of the client device (14) based on the captured identification features (20), the stored user profile (24) being 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 services used in the vehicle (12) according to a service release configuration of the selected user profile (24). [2] Vehicle (12) according to claim 1, characterized by , that - the client device (14) is configured to capture request characteristics (28) in the sensor data (18), the request characteristics (28) being related to a change in the enable state of the set of services provided by the vehicle (12); and - the client device (14) is configured to change the service sharing configuration of the selected user profile (24) based on the detected request characteristics (28). [3] Vehicle (12) according to claim 1 or 2, characterized by , 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 captured identification features (20), wherein - the client device (14) is configured to generate the service sharing configuration of the created user profile (24) according to a standard service sharing configuration, and - the client device (14) is configured to store the generated user profile (24) in the storage facility of the client device (14). [4] Vehicle (12) according to any of the preceding claims, characterized by , that - the client device (14) is configured to log a usage history of a service by the person in the user profile (24). [5] Vehicle (12) according to any of the preceding claims, characterized by , that - the client device (14) is configured to control an output interface device of the vehicle (12) to provide a suggestion message to the user (22), the suggestion message indicating a specific service from the set of vehicle-specific services blocked in the service release configuration, selected on the basis of the usage history and / or on the basis of the person's identification features (20). [6] Vehicle (12) according to any of the preceding claims, characterized by , that - the client device (14) is configured to receive input data from a user (22) input interface of the vehicle (12) and to modify the service sharing configuration of the user profile (24) based on the input data. [7] Vehicle (12) according to any of the preceding claims, characterized by , that - the client device (14) is configured to connect to a server device (30) outside the vehicle (12) and synchronize the user profile (24) stored in the storage device (26) of the client device (14) with a corresponding user profile (24) stored on the server device (30). [8] Server setup (30), characterized by , that - the server device (30) is configured to store a user profile (24) in a server storage device (32) of the server device (30), wherein the user profile (24) is associated with a passenger of a vehicle (12) and includes an enabled 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 synchronize the user profile (24) stored in the server storage device (32) of the server device (30) with a corresponding user profile (24) stored in the storage device (26) of the client device (14). [9] Server setup (30) according to claim 8, characterized by , that - the server device (30) includes 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 sharing configuration of the selected user profile (24) based on the received control data.

Images