Method for operating a fleet, and system, vehicle fleet, mobility provider, service location and backend device for carrying out the method

WO2026180335A1PCT designated stage Publication Date: 2026-09-03VOLKSWAGEN AG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/054464
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-02-25
Filing Date
2026-02-18
Publication Date
2026-09-03

Smart Images

  • Figure EP2026054464_03092026_PF_FP_ABST
    Figure EP2026054464_03092026_PF_FP_ABST
Patent Text Reader

Abstract

The invention relates to a method for operating a fleet (100) having a plurality of vehicles (101), in particular automated and / or autonomously driving vehicles, in order to provide a mobility and / or transport service (MaaS / TaaS), by means of a system (S) having a mobility provider (200) for providing the fleet (100), a central service location (300) for parking, charging, filling, servicing and / or cleaning vehicles (101) and / or uploading data collected by the vehicles (101), and a back-end device (400) for supporting optimal use of the central service location (300).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Description

[0002] Method for operating a fleet and system, vehicle fleet, mobility provider, service location and backend device for carrying out the method

[0003] The invention relates to a method for operating a fleet of multiple vehicles, in particular automated and / or autonomous vehicles, to provide a mobility and / or transport service (MaaS / TaaS). The invention further relates to a corresponding fleet of multiple vehicles, a corresponding mobility provider, a corresponding service location, and a corresponding backend device for carrying out the corresponding method.

[0004] Automated and / or autonomous vehicles (AVs) can be used to provide mobility and / or transport services (MaaS / TaaS). A mobility provider can make a fleet of vehicles available. At a specific time, for example in the evening, the vehicles can return to a central service location, a so-called hub, to refuel, recharge, upload collected data, and, if necessary, be cleaned and / or serviced. The processes at the hub are very complex and require consideration of various factors:

[0005] - Staff deployment planning (How many and which employees perform which task when?),

[0006] - Selection and allocation of parking spaces,

[0007] - Selection and allocation of charging stations,

[0008] - Selection and assignment of upload stations for downloading and uploading data (wired or wireless),

[0009] - Carrying out cleaning processes,

[0010] - Carrying out charging processes, etc.

[0011] The problem can be that the hub does not have enough infrastructure (charging stations, data upload stations, etc.) and / or resources (personnel, equipment, etc.) to charge all vehicles in a fleet and download data simultaneously.

[0012] Therefore, the hub would need to plan the use of infrastructure (e.g., parking spaces, charging stations, upload stations, etc.) and / or resources (personnel, equipment, etc.). To do this, the hub would need access to a range of information from all vehicles in the fleet. This would have to happen simultaneously, as the required vehicle information can be interdependent, such as estimated time of arrival (ETA), battery state of charge (SoC), staffing requirements for cleaning, and / or the volume of data collected. This can be problematic, as the hub may not receive the necessary information from the vehicles, or not in a timely manner. This leads to service delivery issues, which often cannot be provided efficiently and / or promptly. It also results in undesirable waiting times for vehicles.

[0013] An exemplary document on the general state of the art, US2021 / 0110323 A1, shows a base station that takes into account private and public parking spaces for the fleet vehicles.

[0014] It is therefore an object of the present invention to overcome at least one of the disadvantages described above, at least partially. In particular, it is an object of the invention to provide an improved method for operating a fleet of multiple vehicles, especially automated and / or autonomous vehicles, in order to provide a mobility and / or transport service (MaaS / TaaS) that improves service delivery, is efficient and reliable, optimizes the use of the service location or hub, avoids waiting times and / or downtime of the vehicles, and enables improved, safe, and reliable provision of mobility and / or transport services (MaaS / TaaS).Furthermore, the object of the invention is to provide a corresponding fleet with several vehicles, a corresponding mobility provider, a corresponding service location and a corresponding backend device for carrying out a corresponding method.

[0015] The problem is solved by a method for operating a fleet of multiple vehicles, a corresponding fleet of multiple vehicles, a corresponding mobility provider, a corresponding service location, and a corresponding backend device with the features of the independent claims. Features and details described in connection with the different embodiments and / or aspects of the invention naturally also apply in connection with the other embodiments and / or aspects, and vice versa, so that the disclosure relating to the individual embodiments and / or aspects always includes or allows for reciprocal reference. The invention provides for a method for operating a fleet of multiple vehicles, in particular automated and / or autonomous vehicles, to provide a mobility and / or transport service (MaaS / TaaS).

[0016] The process is carried out by a system that includes:

[0017] - a mobility provider to supply the fleet, e.g. vehicle manufacturer,

[0018] - a central service location (or hub for short) for parking, charging, refueling, servicing and / or cleaning vehicles and / or uploading data collected by the vehicles and

[0019] - a backend device (or cloud for short) to support optimal use of the central service location.

[0020] The procedure includes the following steps:

[0021] (1) Acquisition (e.g. by internal and / or external sensors) of operating parameters by the vehicles,

[0022] (2) Transmission (e.g. by suitable communication devices of the vehicles,

[0023] e.g. via mobile network) of recorded operating parameters from the vehicles to the backend device,

[0024] (3) Processing of obtained operating parameters by the backend device,

[0025] (4) Determining the optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location by the backend device depending on the processing,

[0026] (5) Transmitting (e.g. via mobile network) a schedule for the determined optimal utilization from the backend device to a computing unit at the central service location, (6) Transmitting (e.g. via mobile network) pending missions, in particular planned routes for the vehicles, and / or service appointments from the mobility provider to the computing unit at the central service location,

[0027] (7) Planning the use of infrastructure and / or resources at the central service location by the central service location's computing unit, depending on information received (meaning a schedule for the determined optimal utilization from step 5 and / or upcoming missions and / or service appointments from step 6) from the backend device and / or the mobility provider,

[0028] (8) Transmission of current utilization at the central service location from the computing unit of the central service location to the backend device and

[0029] (9) Provision of infrastructure and / or resources at the central service location for the vehicles depending on the plan (meaning the physical provision of parking spaces, charging stations, data upload stations [wired or wireless], personnel and / or equipment [cleaning materials, maintenance tools, etc.]).

[0030] The process steps can be carried out simultaneously, at least partially overlapping, and / or sequentially.

[0031] The process can advantageously be carried out repeatedly, e.g., periodically. Preferably, the process can be repeated continuously.

[0032] The idea is to use the data collected by the vehicle fleet, which is sent (preferably continuously) to the cloud in order to calculate optimal use of the hub in the cloud (preferably intermittently) and to transmit this information (preferably continuously) to the hub.

[0033] In this way, relevant information from vehicles can be used safely and reliably (preferably continuously) for planning the use of the hub.

[0034] To reduce the calculations on the hub, the cloud can already calculate setups for optimal hub utilization.

[0035] Furthermore, the hub can consolidate information from the cloud (completed setup) and from the mobility provider (desired setup) and plan the use of infrastructure and / or resources accordingly.

[0036] Furthermore, the procedure may provide that in step (1) the vehicles in the fleet collect and / or store the recorded operating parameters. In this way, the completeness and availability of the data can be ensured, even if the transmission network is sometimes unreachable or overloaded.

[0037] Furthermore, the procedure can provide that the operating parameters include data (e.g.

[0038] This includes maintenance requirements, error messages, etc., which may be relevant for determining optimal utilization of infrastructure, especially parking, charging, and / or upload stations, and / or resources, especially personnel and / or equipment, at the central service location. The vehicles can thus provide relevant data as needed to enable improved hub planning.

[0039] Furthermore, the procedure may stipulate that the operating parameters include at least one or more of the following parameters: - current battery state of health (SoH),

[0040] - predicted battery state of health (SoH),

[0041] - current battery charge level (State of Charge, SoC),

[0042] - predicted battery state of charge (SoC),

[0043] - currently stored data volume,

[0044] - Estimated data volume at the time of arrival at the central service location, - current location,

[0045] - current speed,

[0046] - Navigation route,

[0047] - Appointment calendar,

[0048] - Estimated arrival time at various locations for missions and / or service appointments from the mobility provider,

[0049] - estimated time of arrival at the central service location and / or

[0050] - Recordings from internal and / or external sensors of the vehicles, e.g. images from an interior camera, to assess how dirty a vehicle cabin is and how much time, personnel and / or equipment are required for cleaning.

[0051] This allows for improved, comprehensive planning of hub usage.

[0052] Advantageously, the procedure can provide that in step (2) the recorded operating parameters, in particular battery charge level and / or stored data volume, are continuously transmitted to the backend device during vehicle operation. This enables dynamic planning of hub utilization.

[0053] For example, the procedure may provide that in step (2) the recorded operating parameters are transmitted from the vehicles to the backend device via mobile communications, the internet and / or WLAN.

[0054] Furthermore, the method can provide that in step (2) the recorded operating parameters are transmitted directly to the backend device and / or indirectly via V2V communication, e.g., via Bluetooth, or indirectly via V2L communication to the backend device. In this way, the existing communication technologies on the vehicles can be used advantageously to enable uninterrupted and complete data transmission. In addition, the method can provide that the recorded operating parameters, in particular battery charge status and / or stored data volume, are added as metadata to data that must be transmitted anyway, such as status messages. The metadata can identify the data to be transmitted and facilitate its assignment in the cloud.

[0055] If necessary, or upon request or mission, it can be provided that the recorded operating parameters are transmitted anonymously and / or encrypted.

[0056] Advantageously, the process can provide for the collection and / or storage of operating parameters received from the vehicles and / or the current utilization data received from the central service location in a data pool on the backend device. This enables improved determination of optimal infrastructure and / or resource utilization at the hub in the cloud, taking into account feedback from the real-world situation. The determination can thus be carried out in a control-system-like manner. Furthermore, this allows for the integration of self-learning functions in the determination process. In addition, it enables the creation and advantageous use of a history of hub usage.

[0057] Furthermore, it may be provided that in step (3) the data received from the vehicles and / or from the central service location are preprocessed, in particular to remove outliers, compress the data and / or identify patterns in the data. In this way, relevant data can be filtered out for determination.

[0058] Furthermore, it may be provided that in step (4) an optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location is determined using a machine learning method. This allows the determination to be made with minimal computational effort and with improved functions, which may include self-learning capabilities.

[0059] Furthermore, it may be provided that in step (4) an optimization problem is solved for:

[0060] - optimal use of parking spaces,

[0061] - optimal use of charging stations,

[0062] - optimal use of data upload stations,

[0063] - optimal use of personnel and / or

[0064] - optimal use of equipment. In this way, optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, can be determined at the central service location in a resource-appropriate and needs-based manner.

[0065] For example, the procedure may provide that in step (5) a list for the determined optimal utilization via mobile network, internet and / or WLAN is transmitted from the backend device to the computing unit of the central service location.

[0066] For example, the procedure may provide that in step (6) the pending missions and / or service appointments are transmitted from the mobility provider to the computing unit of the central service location via mobile communications, internet and / or WLAN.

[0067] Advantageously, in step (7), the computing unit of the central service location can perform a plan based on information received from the backend device and / or the mobility provider, for:

[0068] - the use of parking spaces,

[0069] - the use of charging stations,

[0070] - the use of data upload stations,

[0071] - use of staff and / or

[0072] - use of equipment.

[0073] In this way, optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location can be determined in an improved manner, in particular in a resource-oriented and needs-based way.

[0074] Preferably, in step (7) the setup for the specified optimal utilization received from the backend device and a request from the mobility provider can be compared with the current utilization at the central service location to enable resource-efficient and demand-oriented planning.

[0075] Furthermore, it may be provided that in step (7) current and / or forecasted capacities at the central service location are taken into account, e.g., for parking, charging and / or upload stations, personnel and / or equipment at the central service location. In this way, dynamic planning can be enabled. Furthermore, it may be provided that in step (8) the current utilization at the central service location is transmitted from the computing unit of the central service location to the backend device via mobile network, internet and / or WLAN. In this way, feedback to the actual situation in the hub can be enabled on the cloud side.

[0076] Furthermore, it can be provided that in step (9) corresponding planning results are assigned to the relevant vehicles as they approach the central service location. This allows the relevant vehicles to specifically access the required parking spaces, charging stations, data upload stations, cleaning stations, and / or maintenance stations at the hub.

[0077] Furthermore, it may be stipulated that in step (9) corresponding planning results are assigned to selected personnel at the central service location. This will enable improved, planned service delivery at the hub.

[0078] Furthermore, the invention provides for:

[0079] A system for carrying out a process that can proceed as described above, comprising a mobility provider for supplying the fleet, a central service location for parking, charging, refueling, maintaining and / or cleaning vehicles and / or uploading data collected by the vehicles, and a backend device for supporting optimal use of the central service location. The same advantages can be achieved as described above in connection with the process according to the invention.

[0080] Furthermore, the invention provides for:

[0081] a fleet of multiple vehicles, in particular automated and / or autonomous vehicles, to provide a mobility and / or transport service (MaaS / TaaS) according to a process which may be as described above,

[0082] wherein the vehicles are designed to acquire operating parameters and transmit them to the backend device, wherein the vehicles are designed to receive and execute corresponding missions, in particular planned routes, and / or service appointments from the mobility provider, and wherein the vehicles are designed to receive and utilize the results of the planning for the use of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location from the computing unit of the central service location. The same advantages can be achieved as described above in connection with the method according to the invention. Furthermore, the invention provides:

[0083] A mobility provider for supplying a fleet of multiple vehicles, in particular automated and / or autonomous vehicles, to provide a mobility and / or transport service (MaaS / TaaS) according to a method that can proceed as described above, wherein the mobility provider is configured to transmit pending missions, in particular planned routes for the vehicles, and / or service appointments to the corresponding vehicles and / or to the central service location. The same advantages can be achieved as described above in connection with the method according to the invention.

[0084] Furthermore, the invention provides for:

[0085] a central service location for parking, charging, refueling, servicing and / or cleaning vehicles and / or uploading data collected by the vehicles according to a procedure which may proceed as described above, wherein the central service location has a computing unit, wherein the computing unit is configured to obtain a schedule for the specified optimal utilization from the backend device, wherein the computing unit is configured to obtain pending missions, in particular planned routes for the vehicles, and / or service appointments from the mobility provider, wherein the computing unit is configured to plan the use of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location, wherein the computing unit is configured to transmit a current utilization at the central service location to the backend device.The same advantages can be achieved as described above in connection with the method according to the invention.

[0086] Furthermore, the invention provides for:

[0087] A backend device for supporting optimal utilization of the central service location according to a method that can proceed as described above, wherein the backend device is configured to obtain and process operating parameters of the vehicles, and wherein the backend device is configured to determine the optimal utilization of infrastructure, in particular parking, charging, and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location and to transmit this to the computing unit of the central service location. The same advantages can be achieved as described above in connection with the method according to the invention. Further advantages and features of the invention will become apparent from the following description, in which an embodiment of the invention is described in detail with reference to the drawing. The drawing schematically illustrates:

[0088] Figure 1 shows an exemplary system architecture.

[0089] Fig. 1 serves to describe a method according to the invention, which was developed for operating a fleet 100 with several vehicles 101, in particular automated and / or autonomously driving vehicles, in order to achieve a mobility and / or

[0090] To provide a transport service (MaaS / TaaS).

[0091] The process is carried out by a system S, which is shown schematically in Fig. 1 and comprises the following components:

[0092] - a mobility provider 200 to provide the fleet 100, e.g., vehicle manufacturer, - a central service location 300 (or hub for short) for parking, charging, refueling, maintenance and / or cleaning vehicles 101 and / or uploading data collected by the vehicles 101 and

[0093] - a backend device 400 (or simply called Cloud) to support optimal use of the central service location 300.

[0094] The procedure includes the following steps:

[0095] (1) Acquisition (e.g. by internal and / or external sensors) of operating parameters BP by the vehicles 101,

[0096] (2) Transmitting (e.g. by suitable communication devices of the vehicles, e.g. via mobile communication) of recorded operating parameters BP from the vehicles 101 to the backend device 400,

[0097] (3) Processing of obtained operating parameters BP by the backend device 400, (4) Determining an optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location 300 by the backend device 400 depending on the processing,

[0098] (5) Transmitting (e.g. via mobile network) a schedule for the determined optimal utilization from the backend device 400 to a computing unit ECU of the central service location 300,

[0099] (6) Transmitting (e.g. via mobile network) pending missions, in particular planned routes for the vehicles 101, and / or service appointments from the mobility provider 200 to the ECU of the central service location 300; (7) Planning the use of infrastructure and / or resources at the central service location 300 by the ECU of the central service location 300 depending on the information received (meaning a schedule for the specific optimal utilization from step 5 and / or pending missions and / or service appointments from step 6) from the backend device 400 and / or from the mobility provider 200.

[0100] (8) Transmission of current utilization at the central service location 300 from the central service location 300's ECU to the backend device 400 and (9) Provision of infrastructure and / or resources at the central service location 300 for the vehicles 101 depending on the plan (meaning physical provision of parking spaces, charging stations, data upload stations [wired or wireless], personnel and / or equipment [cleaning materials, maintenance tools, etc.]).

[0101] The process steps can be carried out simultaneously, at least partially overlapping, and / or sequentially.

[0102] The process can advantageously be carried out repeatedly, e.g., periodically. Preferably, the process can be repeated continuously.

[0103] The method proposes using operating parameters collected by the vehicle fleet of 100, which are sent (preferably continuously) to the cloud in order to calculate optimal use of the hub in the cloud (preferably repeatedly) and to transmit this information (preferably continuously) to the hub.

[0104] In step (1) the vehicles 101 of the fleet 100 can collect and / or store the recorded operating parameters BP to advantageously ensure the completeness and availability of the data, e.g. despite connection and / or communication problems.

[0105] Advantageously, the operating parameters can include BP data (e.g., maintenance requirements, error messages, etc.) that may be relevant for determining optimal utilization of infrastructure, especially parking, charging and / or upload stations, and / or resources, especially personnel and / or equipment, at the central service location 300, in order to enable improved, individual services in the hub.

[0106] The operating parameters BP can include at least one or more of the following parameters:

[0107] - Current battery health (State of Health, SoH), - Predicted battery health (State of Health, SoH),

[0108] - current battery charge level (State of Charge, SoC),

[0109] - predicted battery state of charge (SoC),

[0110] - currently stored data volume,

[0111] - Estimated data volume at the time of arrival at the central service location: 300

[0112] - current location,

[0113] - current speed,

[0114] - Navigation route,

[0115] - Appointment calendar,

[0116] - Estimated arrival time at various locations for missions and / or service appointments from the mobility provider 200,

[0117] - Estimated time of arrival at the central service location 300 and / or

[0118] - Recordings from internal and / or external sensors of the vehicles 101, e.g. images from an interior camera, e.g. to assess how dirty a vehicle cabin is and how much time, personnel and / or equipment is required for cleaning.

[0119] This allows for improved, comprehensive planning of hub usage.

[0120] Advantageously, the recorded operating parameters BP, in particular the battery charge state SoC and / or the stored data volume, can be continuously transmitted to the backend device 400 in step (2) during the operation of the vehicles 101 in order to enable dynamic planning of hub usage.

[0121] For example, the recorded operating parameters BP in step (2) can be transmitted from the vehicles 101 to the backend device 400 via mobile network, internet and / or WLAN.

[0122] The recorded operating parameters BP can be transmitted directly to the backend device 400 and / or indirectly via V2V communication (e.g. via Bluetooth communication) or indirectly via V2L communication (i.e., via other vehicles and / or infrastructure participants) to the backend device 400 in order to enable uninterrupted and complete data transmission.

[0123] In principle, it is conceivable that the recorded operating parameters BP, in particular battery charge state (SoC) and / or stored data volume, could be added as metadata to data that must be transmitted anyway, such as status messages. Alternatively, it could be provided that the recorded operating parameters BP are transmitted anonymously and / or encrypted.

[0124] Advantageously, the operating parameters BP received from the vehicles 101 and / or the current utilization received from the central service location 300 can be collected and / or stored in a data pool 401 at the backend device 400. This allows feedback to the actual situation in the hub, enabling control-like determination. Furthermore, this allows for self-learning functions in the determination process. In addition, this allows for the creation and advantageous use of a history of hub usage.

[0125] In step (3) the data received from the vehicles 101 and / or from the central service location 300 can first be pre-processed 402 in order to remove outliers, compress the data and / or identify patterns in the data.

[0126] In step (4) an optimal utilization of infrastructure and / or resources in the hub can be determined using a 403 machine learning method KNN.

[0127] In step (4) an optimization problem can be solved for:

[0128] - optimal use of parking spaces,

[0129] - optimal use of charging stations,

[0130] - optimal use of data upload stations,

[0131] - optimal use of personnel and / or

[0132] - optimal use of equipment.

[0133] The configuration for the specific optimal utilization in the hub can be transmitted in step (5) via mobile network, internet and / or WLAN from the backend device 400 to the computing unit ECU of the central service location 300.

[0134] In step (6) the upcoming missions and / or service appointments can be transmitted via mobile network, internet and / or WLAN from the mobility provider 200 to the computing unit ECU of the central service location 300.

[0135] Advantageously, in step (7), the ECU of the central service location 300 can perform a planning process based on information received from the backend device 400 and / or the mobility provider 200, for:

[0136] - the use of parking spaces,

[0137] - use of charging stations, - use of data upload stations,

[0138] - use of staff and / or

[0139] - use of equipment.

[0140] Preferably, in step (7) the setup for the determined optimal utilization received from the backend device 400 and a request from the mobility provider 200 can be compared with the current utilization at the central service location 300 in order to enable improved, in particular resource-oriented and demand-oriented, planning.

[0141] Advantageously, in step (7) current and / or forecasted capacities at the central service location 300 can be taken into account to enable dynamic planning.

[0142] In step (8) the current utilization at the central service location 300 can be transmitted via mobile network, internet and / or WLAN from the computing unit ECU of the central service location 300 to the backend device 400 in order to enable feedback to the real situation in the hub in the cloud.

[0143] Firstly, in step (9), corresponding planning results can be assigned to the relevant vehicles 101 as they approach the central service location 300. This allows the relevant vehicles 101 to specifically target the required parking spaces, charging stations, data upload stations, cleaning stations and / or maintenance stations within the hub.

[0144] Secondly, in step (9), corresponding planning results can be assigned to selected personnel at the central service location 300. This enables improved, scheduled service delivery at the hub. The planning results can designate one or more persons to perform a service. They can also specify the duration of the assignment, the required materials, equipment, and / or tools.

[0145] Furthermore, the invention provides for:

[0146] a corresponding system S for carrying out a procedure which can proceed as described above, with a mobility provider 200 for providing the fleet 100, a central service location 300 for parking, charging, refueling, maintaining and / or cleaning vehicles 101 and / or uploading data collected by the vehicles 101 and a backend device 400 for supporting optimal use of the central service location 300.

[0147] Furthermore, the invention provides for:

[0148] a corresponding fleet 100 with several vehicles 101, a corresponding mobility provider 200 for providing the fleet 100, a corresponding central service location 300 for parking, charging, refueling, maintaining and / or cleaning vehicles 101 and / or uploading data collected by the vehicles 101, and a corresponding backend device 400 to support optimal use of the central service location 300 for carrying out a procedure which may proceed as described above.

[0149] The preceding explanation of the embodiments describes the present invention solely by way of examples. Naturally, individual features of the embodiments can be freely combined with one another, provided this is technically feasible, without departing from the scope of the present invention. Reference numerals

[0150] 100 Fleet

[0151] 101 vehicles

[0152] 200 mobility providers

[0153] 300 service locations

[0154] ECU computing unit

[0155] 400 Back end device

[0156] 401 Data Pool

[0157] 402 Preprocessing

[0158] 403 Machine Learning Methods

[0159] S System

Claims

Patent claims 1. Method for operating a fleet (100) of multiple vehicles (101), in particular automated and / or autonomous vehicles, to provide a mobility and / or transport service (MaaS / TaaS), through a system (S) with a mobility provider (200) to provide the Fleet (100), a central service location (300) for parking, charging, refueling, servicing and / or cleaning vehicles (101) and / or uploading data collected by the vehicles (101) and a backend device (400) to support optimal use of the central service location (300), demonstrating the procedure: (1) Acquisition of operating parameters (BP) by the vehicles (101), (2) Transmitting recorded operating parameters (BP) from the vehicles (101) to the backend device (400), (3) Processing of obtained operating parameters (BP) by the back end device (400), (4) Determining an optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location (300) by the backend device (400) depending on the processing, (5) Transmitting a schedule for the determined optimal utilization from the backend device (400) to a computing unit (ECU) at the central service location (300), (6) Transmitting pending missions, in particular planned routes for the vehicles (101), and / or service appointments from the mobility provider (200) to the computing unit (ECU) of the central service location (300), (7) Planning the use of infrastructure and / or resources at the central service location (300) by the central service location's computing unit (ECU) (300) depending on information received from the backend device (400) and / or the mobility provider (200), (8) Transmission of a current utilization at the central service location (300) from the computing unit (ECU) of the central service location (300) to the backend device (400) and (9) Providing infrastructure and / or resources at the central service location (300) for the vehicles (101) depending on the plan.

2. Method according to claim 1, characterized by that in step (1) the vehicles (101) of the fleet (100) collect and / or store the recorded operating parameters (BP), and / or that the operating parameters (BP) include data that may be relevant for determining optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location (300), and / or that the operating parameters (BP) include at least one or more of the following parameters: - current battery health status (State of Health, SoH), - predicted battery state of health (SoH), - current battery charge level (State of Charge, SoC), - predicted battery state of charge (SoC), - currently stored data volume, - estimated data volume at the time of arrival at the central service location (300), - current location, - current speed, - Navigation route, - Appointment calendar, - Estimated arrival time at various locations for missions and / or service appointments from the mobility provider (200), - estimated time of arrival at the central service location (300) and / or - Recordings from internal and / or external sensors of the vehicles (101), e.g. Images from an interior camera, e.g., to assess how dirty a vehicle cabin is and how much time, personnel and / or equipment are needed for cleaning.

3. Method according to claim 1 or 2, characterized by that in step (2) the recorded operating parameters (BP), in particular battery charge state (SoC) and / or stored data volume, are continuously transmitted to the backend device (400) during the operation of the vehicles (101), and / or that in step (2) the recorded operating parameters (BP) are transmitted from the vehicles (101) to the backend device (400) via mobile network, internet and / or WLAN, and / or that in step (2) the recorded operating parameters (BP) are transmitted directly to the backend device (400) and / or indirectly via V2V communication, e.g. via Bluetooth, or indirectly via V2L communication to the backend device (400), and / or that the recorded operating parameters (BP), in particular battery state of charge (SoC) and / or stored data volume, are added as metadata to data that must be transmitted anyway, e.g. status messages, and / or that the recorded operating parameters (BP) are transmitted anonymously and / or encrypted.

4. Method according to any one of the preceding claims, characterized by that the operating parameters (BP) received from the vehicles (101) and / or the current utilization received from the central service location (300) are collected and / or stored in a data pool (401) at the backend device (400), and / or that in step (3) the data received from the vehicles (101) and / or from the central service location (300) are pre-processed (402) in order in particular to remove outliers, to compress the data and / or to detect patterns in the data.

5. Method according to any one of the preceding claims, characterized by that in step (4) an optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location (300) is determined using a machine learning (ANN) method (403), and / or that in step (4) an optimization problem is solved for: - optimal use of parking spaces, - optimal use of charging stations, - optimal use of data upload stations, - optimal use of personnel and / or - optimal use of equipment.

6. Method according to any one of the preceding claims, characterized in that in step (5) a schedule for the specific optimal utilization via mobile network, internet and / or WLAN is transmitted from the backend device (400) to the computing unit (ECU) of the central service location (300), and / or that in step (6) the pending missions and / or service appointments are transmitted via mobile network, internet and / or WLAN from the mobility provider (200) to the computing unit (ECU) of the central service location (300).

7. Method according to any of the preceding claims, characterized by that in step (7) the computing unit (ECU) of the central service location (300) performs a planning process based on information received from the backend device (400) and / or the mobility provider (200), for: - the use of parking spaces, - the use of charging stations, - the use of data upload stations, - use of staff and / or - use of equipment.

8. Method according to any one of the preceding claims, characterized by that in step (7) a comparison is carried out between the setup for the specified optimal utilization received from the backend device (400) and / or a request from the mobility provider (200) with the current utilization at the central service location (300), and / or that in step (7) current and / or projected capacities at the central service location (300) are taken into account, in particular for parking, charging and / or upload stations, personnel and / or equipment at the central service location (300).

9. Method according to any one of the preceding claims, characterized by that in step (8) the current utilization at the central service location (300) is transmitted via mobile network, internet and / or WLAN from the computing unit (ECU) of the central service location (300) to the backend device (400).

10. Method according to any one of the preceding claims, characterized in that in step (9) corresponding results of the planning are assigned to corresponding vehicles (101) when they approach the central service location (300), and / or that in step (9) corresponding results of the planning are assigned to selected personnel at the central service location (300).

11. System for carrying out a method according to one of the preceding claims, comprising a mobility provider (200) for providing the fleet (100), a central service location (300) for parking, charging, refueling, servicing and / or cleaning vehicles (101) and / or uploading data collected by the vehicles (101) and a backend device (400) for supporting optimal use of the central service location (300).

12. Fleet (100) with multiple vehicles (101), in particular automated and / or autonomous vehicles, to provide mobility and / or to provide a transport service (MaaS / TaaS) according to a method according to any of the preceding claims 1 to 10, wherein the vehicles (101) are designed to acquire operating parameters (BP) and transmit them to the backend device (400), wherein the vehicles (101) are designed to receive and carry out corresponding missions, in particular planned routes, and / or service appointments from the mobility provider (200), and wherein the vehicles (101) are designed to receive and use the results of the planning for the use of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location (300) from the computing unit (ECU) of the central service location (300).

13. Mobility providers (200) to provide the fleet (100) with several vehicles (101), in particular automated and / or autonomous vehicles, to provide a mobility and / or transport service (MaaS / TaaS) according to a method according to any one of the preceding claims 1 to 10, wherein the mobility provider (200) is configured to transmit pending missions, in particular planned routes for the vehicles (101), and / or service appointments to the corresponding vehicles (101) and / or to the central service location (300).

14. Central service location (300) for parking, charging, refueling, servicing and / or cleaning vehicles (101) and / or uploading data collected by the vehicles (101) according to a method according to any one of the preceding claims 1 to 10, wherein the central service location (300) comprises a processing unit (ECU), wherein the computing unit (ECU) is designed to obtain a schedule for the specific optimal utilization from the backend device (400), wherein the computing unit (ECU) is designed to receive pending missions, in particular planned routes for the vehicles (101), and / or service appointments from the mobility provider (200), wherein the computing unit (ECU) is designed to plan the use of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location (300), wherein the computing unit (ECU) is designed to transmit a current utilization at the central service location (300) to the backend device (400).

15. Backend device (400) for supporting optimal use of the central service location (300) according to a method according to any one of the preceding claims 1 to 10, wherein the backend device (400) is designed to obtain and process operating parameters (BP) of the vehicles (101), wherein the backend device (400) is designed to determine the optimal utilization of infrastructure, in particular parking, charging and / or upload stations, and / or resources, in particular personnel and / or equipment, at the central service location (300) and to transmit this information to the computing unit (ECU) of the central service location (300).