Vehicle Administration Order and Vehicle Administration Procedure

Abstract

The present invention relates to a vehicle management arrangement (100) comprising a vehicle manufacturer backend device (110) configured for generating, managing and distributing encrypted immobilizer tokens (112) and unlock PINs (114), wherein each immobilizer token (112) is configured to release an immobilizer (150) of a vehicle (140) when the corresponding unlock PIN (114) is entered, and a vehicle manager backend device (124) configured for communicating with the vehicle manufacturer backend device (110) for receiving and forwarding the encrypted immobilizer tokens (112) and the unlock PINs (114) to a vehicle manager terminal device (130).A vehicle (140) equipped with a control unit (142) for receiving the encrypted immobilizer tokens (112) from the vehicle manufacturer's backend unit (110) and / or the vehicle management backend unit (124), and for decrypting the immobilizer tokens (112) after entering the unlock PIN (114) to release the immobilizer (150). The present invention also relates to a vehicle management method.

Description

[0001] The present invention relates to a vehicle management arrangement and a vehicle management method.

[0002] The manual handover of physical vehicle keys presents a significant operational challenge, particularly in the context of the modern car rental industry. This traditional method has several drawbacks that negatively impact both the efficiency and security of the rental process.

[0003] One problem arises, for example, with the physical handover of keys to numerous service employees responsible for various services such as cleaning, refueling, maintenance, and / or inspections. Each of these employees requires access to the vehicle, necessitating a constant exchange of keys. This practice leads to further delays, increased coordination efforts, and a higher probability of lost keys or misunderstandings.

[0004] Furthermore, the use of physical keys poses significant security risks. The loss or theft of keys can have serious consequences, including the need to replace locks, which entails additional costs and logistical challenges. Moreover, physical key management is prone to human error, which can compromise the security of the entire system.

[0005] Another problem is the lack of flexibility in the operational process, as physical key handover requires a continuous staff presence. In times of digital technologies and increasing customer demand for self-service options, this approach is not only outdated but also a competitive disadvantage.

[0006] These problems highlight the need for an improved procedure for managing rental car access that both increases operational efficiency and minimizes security risks by reducing reliance on physical keys while offering greater ease of use.

[0007] One object of the present invention can be seen as providing an improved vehicle management arrangement and an improved vehicle management method.

[0008] This problem is solved by a vehicle management arrangement having the features of claim 1, and by a vehicle management method having the features of claim 10. Accordingly, the following is planned:

[0009] A vehicle management arrangement comprising a vehicle manufacturer backend device configured to generate, manage, and distribute encrypted immobilizer tokens and unlock PINs, each immobilizer token configured to release a vehicle's immobilizer when the corresponding unlock PIN is entered; a vehicle manager backend device configured to communicate with the vehicle manufacturer backend device for receiving and forwarding the encrypted immobilizer tokens and unlock PINs to a vehicle manager terminal; a vehicle equipped with a control device for receiving the encrypted immobilizer tokens from the vehicle manufacturer backend device and / or the vehicle manager backend device and for decrypting the immobilizer tokens after the unlock PIN is entered to release the immobilizer.

[0010] Furthermore, a vehicle management procedure is provided, comprising the following steps: generation of encrypted immobilizer tokens and unlocking PLNs by a vehicle manufacturer's backend facility, each immobilizer token being configured to release the vehicle's immobilizer when the corresponding unlocking PIN is entered; management and distribution of the encrypted immobilizer tokens and unlocking PLNs by the vehicle manufacturer's backend facility to a vehicle manager's backend facility; forwarding of the encrypted immobilizer tokens and unlocking PINs from the vehicle manager's backend facility to a vehicle manager's terminal; receipt of the encrypted immobilizer tokens by a vehicle control unit from the vehicle manufacturer's backend facility and / or the vehicle manager's backend facility; and entry of the unlocking PIN by a vehicle user.Decryption of the immobilizer token by the control unit after entry of the corresponding unlock PIN; release of the vehicle's immobilizer by the control unit after successful decryption of the immobilizer token.

[0011] The vehicle management system comprises several components that work closely together to provide an efficient and secure system for managing vehicle access and usage. One component of this system is the vehicle manufacturer's backend facility. This facility is specifically designed to generate, manage, and distribute encrypted immobilizer tokens and unlock PINs. An immobilizer token is a digital security mechanism that serves as a key to release a vehicle's immobilizer. This token is encrypted to ensure system security and prevent unauthorized access. The unlock PIN is a personal identification code required to decrypt the immobilizer token and disable the vehicle's immobilizer.The vehicle manufacturer's backend facility ensures that these tokens and PINs are securely created and managed before being forwarded to other system components.

[0012] Another important component of the vehicle management system is the vehicle manager backend. This system communicates directly with the vehicle manufacturer's backend to receive the encrypted immobilizer tokens and unlock PINs. Upon receipt, the vehicle manager backend securely forwards these to a vehicle manager terminal. The vehicle manager terminal serves as an interface for the vehicle manager to access the necessary immobilizer tokens and unlock PINs and, if required, distribute them to the vehicles. This communication between the backends ensures that the tokens and PINs are always up-to-date and synchronized, guaranteeing the security and integrity of the vehicle management system.

[0013] The vehicle itself is another component of this vehicle management system. The vehicle is equipped with a control unit capable of receiving encrypted immobilizer tokens from the vehicle manufacturer's backend and / or the vehicle manager's backend. This control unit is designed to decrypt the immobilizer tokens after the correct unlock PIN has been entered. Once the immobilizer token is successfully decrypted, the vehicle's immobilizer is deactivated, allowing the vehicle to be started and used. This process ensures that only authorized individuals can use the vehicle, as the combination of the immobilizer token and the unlock PIN is required to bypass the security lock.

[0014] The invention's functionality is based on a secure, multi-stage authentication process. First, the vehicle manufacturer's backend generates the necessary immobilizer tokens and unlock PINs and securely distributes them to the vehicle management backend. From there, the data is transmitted to the vehicle, where it is stored and processed in the control unit. When an authorized user enters the unlock PIN via a suitable user interface, the control unit decrypts the immobilizer token. This decrypted immobilizer token then releases the vehicle's immobilizer, allowing the engine to be started. This process ensures that the vehicle can only be used by individuals who possess and correctly use both the immobilizer token and the corresponding unlock PIN.

[0015] The vehicle manufacturer backend facility is a component of the vehicle management arrangement, which is trained to generate, manage, and distribute basic safety data for the vehicles.

[0016] This facility is specifically designed to generate encrypted immobilizer tokens and unlock PINs used to control vehicle access and usage. The vehicle manufacturer's backend facility ensures that this security data is securely generated and stored before being transmitted to other systems or facilities. It plays a crucial role in the security architecture of the vehicle management system by ensuring that only authorized data is transmitted to the vehicles and other systems.

[0017] The vehicle manager backend is another component within the vehicle management system. It acts as a communication interface between the vehicle manufacturer backend and the vehicles themselves. This system is designed to receive the immobilizer tokens and unlock PINs generated and managed by the vehicle manufacturer backend and securely forward them to the appropriate vehicles. Furthermore, the vehicle manager backend can manage and control vehicles within a fleet by monitoring and controlling vehicle access and usage. It allows vehicle managers to maintain a centralized overview of all vehicles and their security status, which is particularly beneficial in fleet management scenarios.

[0018] The immobilizer token is a digital security mechanism specifically designed to control access to and use of a vehicle. This immobilizer token is encrypted to ensure it cannot be decrypted or tampered with by unauthorized individuals. The immobilizer token is programmed to release a vehicle's immobilizer when correctly decrypted using the unlock PIN. The immobilizer token is generated by the vehicle manufacturer's backend system and can be sent to the corresponding vehicle via the vehicle manager's backend system.

[0019] The unlock PIN is a personal identification number required to decrypt the immobilizer token and disable the vehicle's immobilizer. This unlock PIN is generated by the vehicle manufacturer's backend system and used in conjunction with the immobilizer token to ensure that only authorized individuals have access to and can use the vehicle. The unlock PIN can be entered by the user via a user interface on the vehicle. It provides an additional layer of security, as the immobilizer token cannot be decrypted without the correct PIN. The PIN is also preferably transmitted in encrypted form and is designed to further enhance vehicle security.

[0020] The immobilizer is a security-relevant component within the vehicle that, for example, prevents the engine from starting until the immobilizer token has been correctly decrypted. The immobilizer is controlled by the vehicle's control unit, which processes the immobilizer token and the unlock PIN. Only when both elements are correct and authorized is the immobilizer deactivated, allowing the engine to be started. The immobilizer thus forms the physical security barrier that prevents unauthorized use of the vehicle.

[0021] The vehicle manager endpoint is a specialized device or software used by vehicle managers to administer and control vehicles. This endpoint receives immobilizer tokens and unlock PINs forwarded by the vehicle manager backend and makes them available to the vehicles. It serves as an interface through which the vehicle manager can manage vehicle access by monitoring and controlling the distribution of security data. The vehicle manager endpoint enables managers to monitor the status of vehicles in real time and take security measures as needed.

[0022] The vehicle manager is the individual or team responsible for managing and controlling the vehicle fleet. This role includes monitoring vehicle condition, managing security data, and ensuring that only authorized personnel have access to the vehicles. The vehicle manager uses the vehicle manager device and backend systems to coordinate and implement necessary security measures. This role is crucial for the smooth operation of a vehicle fleet, especially in commercial or rental-based scenarios where efficient vehicle management and security are paramount.

[0023] The vehicle's control unit is a component designed to process security data. It receives encrypted immobilizer tokens and unlocking PLNs from the vehicle manufacturer's backend and / or the vehicle administrator's backend. After entering the correct unlocking PLN, the control unit decrypts the immobilizer token and disables the immobilizer, allowing the vehicle to be started or used. The control unit plays a central role in the vehicle administration system, as it is the final authority that authorizes or denies vehicle use. Integrating the control unit into the vehicle ensures that security mechanisms function at the highest level and protects the vehicle from unauthorized access.

[0024] The technical advantages of the vehicle management system according to the invention are manifold. First, the vehicle management system offers a high level of security through the use of encrypted immobilizer tokens and unlocking PLNs, which only release the vehicle's immobilizer when used together. This encryption prevents unauthorized persons from starting the vehicle, even if they have physical access to it. Second, the vehicle management system enables flexible and centralized management of vehicle access via the vehicle management backend, which is particularly advantageous in fleet management scenarios. Third, the digitization and automation of the access process improves efficiency and user-friendliness, as physical keys become at least partially obsolete and vehicle access can be granted quickly and easily via digital means.Finally, the vehicle management system contributes to reduced operating costs because it is less susceptible to loss or theft of physical keys while minimizing administrative overhead. This combination of security, efficiency, and ease of use makes the described vehicle management system a powerful solution for modern vehicle management.

[0025] According to a preferred embodiment, the vehicle manufacturer's backend device can be configured to cyclically rotate the encrypted immobilizer tokens and / or the unlock PINs.

[0026] Cyclical rotation means that immobilizer tokens and / or unlock PINs are renewed according to a set schedule. This process is automatically controlled by the vehicle manufacturer's backend and / or the vehicle management company's backend, generating new immobilizer tokens and / or unlock PINs and invalidating the old ones. The rotation frequency may vary depending on the specific security requirements and policies of the vehicle manufacturer or car rental company.

[0027] This embodiment offers several technical advantages. First, the regular renewal of security features improves the overall security of the vehicle management system by limiting the lifespan of each immobilizer token and / or unlock pln. Even if an attacker were to gain possession of an immobilizer token and / or unlock pln, it would only be valid for a short and defined period. This significantly minimizes the risk and potential impact of a security breach. Second, the rotation protects against so-called replay attacks, in which older, intercepted data could be reused to gain unauthorized access. By invalidating old immobilizer tokens and / or unlock plns after a certain period, such attacks are rendered ineffective.

[0028] Furthermore, the adjustable rotation frequency allows for a flexible response to varying security needs. In higher-risk environments or with higher-value vehicles, the frequency can be increased to adjust the security level accordingly. Finally, the regular renewal of immobilizer tokens and / or unlocking PLNs helps to strengthen user confidence in the security of the vehicle management system.

[0029] Customers and business partners can rely on proactive steps being taken to protect their data and vehicles.

[0030] According to another preferred embodiment, the vehicle's control unit is configured to apply a reset procedure after repeated incorrect entries of the unlock PIN, in which the waiting time for re-entering the unlock PIN is extended after each incorrect entry of an unlock PIN.

[0031] For example, an exponential reset procedure could be implemented, in which the waiting time for re-entering an unlocking PLN is increased exponentially after each incorrect entry. For instance, a waiting time of 30 seconds would be imposed after the first incorrect entry of the unlocking PLN, 60 seconds after the second, and after the third incorrect entry, the input would be blocked for 120 seconds. Additionally, the vehicle's control unit could define a maximum number of permissible incorrect attempts, after which the ability to enter the unlocking PLN is completely blocked, and the vehicle can only be unlocked again by an authorized service technician or through special authorization from the vehicle management backend system. This measure significantly increases the security of the vehicle management system, as it, for example,Effectively prevents brute-force attacks while ensuring that legitimate users are given another chance to enter the correct unlock PIN after a failed attempt.

[0032] According to another preferred embodiment, the vehicle's control unit can be configured to communicate wirelessly with the vehicle manufacturer's backend device and / or the vehicle manager's backend device.

[0033] The wireless communication technology implemented in vehicles can take various forms, such as Wi-Fi, Bluetooth, UWB, cellular networks, or other forms of wireless data transmission. The selection of the specific technology depends on several factors, including the required range, energy efficiency, cost, and / or data transmission security.

[0034] This implementation enables seamless and efficient vehicle access management. For example, when a customer rents a vehicle or a service technician wants to use it, the vehicle manufacturer's backend or the vehicle manager's backend generates an immobilizer token and an associated unlock PIN, which are then wirelessly transmitted to the vehicle. Once the vehicle receives the necessary data, the customer or service technician can enter the unlock PIN via the human-machine interface in or on the vehicle and unlock and / or start the vehicle.

[0035] Wireless communication increases the flexibility and efficiency of vehicle access management. Customers and service personnel benefit from a faster and smoother process, as the need to hand over physical keys is eliminated. This reduces waiting times and improves customer and service employee satisfaction. Furthermore, wireless communication offers enhanced security compared to physical keys, as immobilizer tokens and / or unlock PINs are protected by encryption techniques and can be easily changed or revoked if necessary.

[0036] According to another preferred embodiment, the human-machine interface can be a touchscreen.

[0037] In the described embodiment, the human-machine interface of a vehicle is designed as a touchscreen. This human-machine interface enables interaction between the user and the vehicle system through touches on a screen, which is an intuitive and user-friendly method. The touchscreen serves as the central control element through which users can enter unlock PINs.

[0038] This implementation relies on the use of touchscreen technology, which is already standard in many modern vehicles. The touchscreen responds to the user's touch and allows direct manipulation of the user interface. In this specific context, the touchscreen is used to enter the unlock PIN, which is necessary to decrypt and deactivate the immobilizer token, thus granting access to the vehicle or enabling its start. Once the user enters the unlock PIN via the touchscreen, the vehicle management system processes the input and executes the corresponding action, such as unlocking the vehicle.

[0039] The touchscreen is typically integrated into the dashboard or center console of the vehicle to allow for convenient and intuitive interaction for the driver. Alternatively, the touchscreen can be mounted on an exterior surface of the vehicle, such as next to the driver's door or near the door handle. This positioning allows users to enter the unlock PIN and deactivate the immobilizer token without having to enter the vehicle. The touchscreen is designed, for example, as a robust, weatherproof, high-resolution display that responds to both touch and gestures. The user interface is designed to be user-friendly, offering clear, easy-to-understand menus and input fields for entering the unlock PIN. Additionally, the touchscreen can display the current status of the immobilizer token, ensuring the user is always informed about the vehicle's security status.By integrating modern touch technology, the screen ensures fast and precise input, which is essential for efficient and safe use of the vehicle.

[0040] The human-machine interface could alternatively or additionally use voice control, gesture control, and / or physical buttons and / or rotary controls.

[0041] According to another preferred embodiment, the vehicle manufacturer's backend device can be configured to provide the unlocking PIN only for a predetermined period of time.

[0042] This approach aims to enhance access management security by limiting the validity of the unlock PIN. The unlock PIN is a critical security code used to decrypt and disable the immobilizer token, thus granting access to the vehicle. By ensuring the vehicle manufacturer's backend system provides the unlock PIN only for a defined period, after which it becomes invalid, it is guaranteed that the unlock PIN cannot be permanently compromised.

[0043] This implementation begins with a user requesting an unlock PIN when access to a vehicle is required. The vehicle manufacturer's backend system then generates a time-limited unlock PIN, which is transmitted to the user. This transmission can occur via various secure communication channels, such as an encrypted mobile application or a dedicated device in the vehicle. Once the unlock PIN is used by the user, a timer can start, after which the unlock PIN is automatically deactivated, regardless of whether it has been used or not. Furthermore, a safeguard could be implemented that delays, or even completely prevents, subsequent unlock PIN entries if an incorrect one is entered.

[0044] Limiting the validity period of the unlock PIN provides an additional layer of security, as old or potentially intercepted unlock PINs can no longer be used after their expiration. This minimizes the risk of lost or stolen information leading to unauthorized vehicle access. Furthermore, this implementation increases control over vehicle usage, as access permissions can be closely monitored and controlled, which is particularly advantageous in industries such as car rental. Thirdly, restricting the validity period of the unlock PIN also allows for more efficient monitoring and management of vehicle usage, as each use of the unlock PIN is precisely assigned to a specific time window.

[0045] Furthermore, this implementation contributes to an improved user experience, as users are motivated to conduct their transactions promptly and responsibly by knowing the unlock PIN has a limited validity period. From an operational perspective, the time limit also allows for more efficient resource planning and utilization, since access credentials must be renewed regularly, requiring continuous interaction with the system and thus constantly updating security practices.

[0046] According to another preferred embodiment, the vehicle manager backend facility can be configured to implement additional security measures such as two-factor authentication for accessing the unlocking PINs.

[0047] Two-factor authentication uses two different and independent components to verify a user's identity, which significantly increases security.

[0048] This implementation begins when a user or system requests access to a vehicle and is required to enter an unlock PIN. In addition to entering the unlock PIN, two-factor authentication requires the user to provide a second form of identification. This could be in the form of a physical token, biometric verification such as a fingerprint and / or facial scan, or by using a secure mobile device that generates a unique authentication identifier. Only after successful verification of both factors is access to the unlock PIN granted.

[0049] Two-factor authentication increases security by making it significantly more difficult to gain unauthorized access. Even if an attacker were to decrypt or guess the unlock PIN, they would be denied access unless they could also present the second authentication factor. This considerably reduces the risk of theft or unauthorized use of the vehicle.

[0050] Furthermore, two-factor authentication increases user confidence in the security of the vehicle management system. Customers and operators can be certain that vehicles are only used by authorized individuals, which can be crucial, especially in the car rental industry where vehicles are frequently used by multiple users.

[0051] Furthermore, implementing two-factor authentication can meet or even exceed regulatory requirements, helping car rental companies comply with regulations and minimize potential legal risks. It also reduces fraud by providing a more robust method for verifying identity, ultimately lowering operating costs that could result from fraud and theft.

[0052] In summary, this embodiment, through the integration of two-factor authentication, offers a significant increase in security and reliability in vehicle access management, leading to improved overall security, increased user trust, and more efficient compliance with security standards.

[0053] According to another preferred embodiment, the vehicle can be configured to remain unlocked for a predetermined number of engine starts after the unlocking PLN has been entered.

[0054] The functionality of this embodiment is based on the control unit integrating an engine start counter, which is activated as soon as the correct unlock PIN is entered. The unlock PIN itself is a security code designed to decrypt the immobilizer token, enabling the vehicle to be unlocked and / or the engine to be started. After this unlock PIN is entered and successfully verified by the control unit, the engine start counter is activated. The remaining number of possible engine starts should then be displayed via the human-machine interface (HMI). This counter limits the number of engine starts possible without re-entering the unlock PIN. Once the predetermined number of starts is reached, the vehicle is automatically locked again, and a new unlock PIN must be entered to continue using the vehicle.

[0055] Limiting the number of engine starts after each PIN entry ensures that a potential thief can only start the vehicle a limited number of times, even if they gain access to the correct unlock PIN. This can be particularly useful if a vehicle is stolen unnoticed, as it prevents the thief from using the vehicle for an extended period without reauthorization.

[0056] Furthermore, this feature increases user-friendliness for legitimate users who wish to use the vehicle for short, repeated trips without having to re-enter the unlock PIN each time. This is particularly advantageous in scenarios such as car rental or car-sharing services, where vehicles are frequently used for short periods.

[0057] Furthermore, this implementation allows for more precise control and management of vehicle usage. Vehicle administrators can implement specific policies that target how often a vehicle can be started before re-authentication is required, which can be helpful in monitoring and regulating usage patterns.

[0058] In summary, this embodiment offers a sensible balance between user-friendliness and security by allowing temporary but limited access to the vehicle while ensuring that the vehicle cannot be operated beyond the specified use without further authentication.

[0059] However, it is critical for safety to consider what happens when the maximum number of engine starts is reached and, for example, another engine start is required in a hazardous area. In such cases, an additional safety mechanism could be implemented that allows an emergency start to ensure user safety. One possible approach to implementing an emergency start could be the use of an emergency PIN, issued in addition to the regular unlock PIN. This emergency PIN could be activated only in specific situations, such as when the maximum number of engine starts has been reached and the vehicle is in a hazardous area. After entering the emergency PIN, the vehicle would be unlocked, for example, only for a short, predetermined period during which it could be started and used.This time limit ensures that the vehicle can only be used in an urgent emergency and prevents prolonged, potentially unauthorized use. After this short period, the vehicle automatically locks again, so that it can only be started again after entering a valid unlock PIN.

[0060] According to a further preferred embodiment, the vehicle's control unit can be configured to send the status of the immobilizer, in particular the status of the immobilizer token and the unlock PIN, to the vehicle management backend. In this context, the control unit could, for example, additionally transmit further metadata, such as the number of incorrect unlock PIN entries, the number of remaining attempts to enter the unlock PIN, the number of remaining engine starts, and the duration for which the immobilizer was unlocked, i.e., how long the vehicle was in the "DRIVING" state. This extended information would enable more precise monitoring and management of the vehicles.

[0061] This functionality enables continuous and effective monitoring of the vehicle's safety status by the vehicle manager, which is an essential aspect for fleet management and safety.

[0062] The immobilizer tokens are designed to lock or unlock the vehicle, depending on the correct entry of a corresponding unlock PIN by a user. The vehicle's control unit is responsible for monitoring the current status of these elements. This includes whether an immobilizer token is active—i.e., the immobilizer token has not been decrypted and the vehicle is locked by the immobilizer—or deactivated—i.e., the immobilizer token has been decrypted and the vehicle is unlocked by the immobilizer—as well as the status of the unlock PIN, i.e., whether it has been successfully verified or not.

[0063] This embodiment begins to function by detecting an event, such as the entry of an unlocking PLN or the activation / deactivation of the immobilizer by decrypting the immobilizer token. The control unit captures this information and transmits it to the vehicle management backend via a secure connection. This data transmission occurs in real time or at predefined intervals, depending on the configuration of the vehicle management system.

[0064] The technical advantages of this design are numerous. First, the transmission of the immobilizer status and / or other metadata enables better control and monitoring of the vehicle. Vehicle administrators can thus react quickly to security incidents, such as attempted unauthorized use of the vehicle, and take appropriate measures, for example, relocking the vehicle remotely.

[0065] Secondly, this feature improves the overall security architecture of car rental management by providing continuous feedback on the condition of each vehicle. This allows administrators to obtain more accurate data on the usage patterns and security status of their vehicles, which in turn can help optimize operations and prevent theft or misuse.

[0066] Furthermore, the ability to monitor and communicate the status of security elements such as immobilizer tokens, unlocking PLNs, and other metadata contributes to compliance with insurance and regulatory requirements. This can reduce insurance costs and ensure compliance with legal requirements by demonstrating that effective security and monitoring mechanisms are in place.

[0067] Overall, this design, through the integration of advanced communication technologies, offers a robust solution for vehicle management that not only increases safety and efficiency but also strengthens the trust of customers and business partners in the rental company.

[0068] According to another preferred embodiment, the human-machine interface can be configured to display the current status of the immobilizer token.

[0069] The human-machine interface serves as an information portal for the user, enabling them to view the vehicle's operating status and specific safety functions and / or meta-information.

[0070] The status of this immobilizer token can indicate whether the vehicle is currently locked or unlocked. The ability of the human-machine interface to clearly display this status represents direct communication between the vehicle security system and the user.

[0071] This embodiment typically involves real-time data processing and display. For example, when the user enters the unlock PIN, the control unit processes and verifies this input and updates the status of the immobilizer token and / or immobilizer accordingly. The updated status is then immediately displayed on the human-machine interface, providing the user with direct feedback on the success or failure of their input.

[0072] The technical advantages of this design are considerable. Firstly, the clear and immediate display of the immobilizer token status and / or immobilizer status and / or metadata improves the vehicle's usability and accessibility. Users can see at a glance whether further action is required on their part to start or secure the vehicle, which is particularly advantageous in stressful or urgent situations.

[0073] Secondly, this function increases the security of the vehicle usage process. By keeping users constantly informed about the vehicle's status, they can ensure that the vehicle is not unintentionally left unlocked. This helps to minimize the risks of theft or unauthorized use of the vehicle.

[0074] Furthermore, implementing such an interface fosters user trust in the vehicle and its safety systems. The transparency provided by the system makes users feel safer and more comfortable with the technology, contributing to customer satisfaction and loyalty.

[0075] According to another preferred embodiment, the vehicle manufacturer's backend device can be configured to transmit the encrypted immobilizer tokens and unlock PINs via a secure connection.

[0076] The functionality of this implementation comprises several key components. First, the vehicle manufacturer's backend system generates the encrypted immobilizer token and the unlock PIN, which is specific to a particular vehicle or user. This data is then transmitted over a secure connection based on robust encryption methods such as SSL / TLS (Secure Sockets Layer / Transport Layer Security), VPN (Virtual Private Network), or mTLS (mutual TLS). These technologies ensure that the data cannot be read or altered by third parties during transmission.

[0077] The secure transmission of immobilizer tokens and unlocking PLNs drastically reduces the risk of data leaks or cyberattacks. This not only protects user privacy and security but also strengthens trust in the vehicle management system. Furthermore, this implementation helps ensure compliance with legal data protection regulations, which is crucial for manufacturers in an increasingly regulated environment.

[0078] Furthermore, the use of secure connections improves the reliability of the vehicle management system. Data transmitted correctly and without manipulation ensures that the vehicle access systems function as intended and that no malfunctions occur due to data corruption. This increases overall system stability and reduces the need for technical support and maintenance.

[0079] Overall, this design enables a robust, reliable and trustworthy environment for vehicle management through the secure transmission of critical security data, improving both security and user experience.

[0080] According to another preferred embodiment, the vehicle's control unit can be configured to receive and implement wireless instructions for remote locking and unlocking of the vehicle via the vehicle manufacturer's backend device and / or a vehicle manager's backend device.

[0081] The vehicle's control unit is typically equipped with modern telematics technology, enabling it to securely send and receive signals via cellular networks or other wireless communication methods. The control unit receives specific, encrypted commands from the vehicle manufacturer's backend or the vehicle management company's backend. These commands are then interpreted and executed by the vehicle's control unit to initiate appropriate actions, such as locking or unlocking the doors or activating or deactivating the immobilizer.

[0082] The operation of this embodiment comprises several steps. First, a secure connection is established between the vehicle's control unit and the vehicle manufacturer's backend system and / or the vehicle administrator's backend system, through which commands can be transmitted. This connection preferably uses robust encryption protocols to ensure the security of the transmitted data. Once a remote locking or unlocking command is received, it is processed by the control unit and forwarded to the control unit that activates the physical mechanisms for locking or unlocking, or for activating or deactivating the immobilizer.

[0083] One of the main advantages is the increased flexibility and convenience for both the user and the vehicle management company. For example, users can unlock their vehicle in advance before physically arriving at it, or ensure that the vehicle is locked after they have left, even if they initially forgot to do so. For operators, this functionality offers the ability to respond to emergencies, such as remotely locking the vehicle if it has been stolen.

[0084] Another advantage is improved security. The ability to remotely lock and unlock vehicles or activate or deactivate the immobilizer can help prevent or minimize theft by enabling rapid action. Furthermore, this technology can contribute to more efficient vehicle usage by, for example, dynamically managing vehicle access rights based on actual usage or booking status.

[0085] Overall, this embodiment, through the implementation of advanced wireless communication technologies, offers a significant expansion of the operational and safety capabilities of vehicles, which can increase both customer satisfaction and operational efficiency.

[0086] According to another preferred embodiment, the vehicle manager backend facility can be configured to provide the unlock PIN upon request from a user after the vehicle has been returned without an open booking in order to allow engine starts for maintenance purposes.

[0087] Once a vehicle is returned and marked in the system as "no open booking", a service representative or other authorized user can contact the car rental company's backend facility to obtain a temporary unlock PIN.

[0088] This implementation begins when a vehicle is returned, at which point it is recorded in the car rental company's management system as available without a booking. Service personnel or other authorized individuals can then submit a request to the vehicle management backend to gain access to the vehicle. The vehicle management backend then generates an unlock PIN, specific to the requested purpose, and securely transmits it to the appropriate person. This unlock PIN then allows, for example, starting the engine, which may be necessary for inspections, repairs, or other maintenance work.

[0089] This design enables improved maintenance efficiency, as vehicles can be accessed quickly and easily for necessary inspections and maintenance. This is particularly important in a commercial environment where vehicle downtime must be minimized and availability maximized. Furthermore, this functionality enhances security, as the unlock PIN is only issued upon request and only for specific, documented purposes. This helps prevent unauthorized access and ensures that only authorized personnel have access to the vehicles.

[0090] Furthermore, this approach can improve operational flexibility by enabling the car rental company to respond quickly to unforeseen maintenance needs. By giving service personnel the ability to start vehicles as required, potential problems can be identified and resolved more quickly, increasing the overall reliability of the vehicles. This implementation therefore not only supports direct vehicle maintenance but also contributes to long-term vehicle care and optimization, ultimately boosting customer satisfaction and the car rental company's business success.

[0091] According to another preferred embodiment, the vehicle manager backend facility can further be configured to log and limit the number of engine starts that can be performed after the unlock PIN has been provided.

[0092] This embodiment aims to precisely monitor and control the use of the vehicle, particularly after a user or service employee has gained access to the vehicle.

[0093] This implementation begins with the vehicle management backend generating and providing an unlock PIN, which grants a user or service technician access to the vehicle. Once the unlock PIN is used, the vehicle management system activates a function that counts each engine start. The vehicle management backend can, for example, define how many times the engine may be started before access is re-enabled. The number of remaining engine starts could be displayed, for example, via the human-machine interface (HMI). This is often used in scenarios where a vehicle has been released for maintenance and it is essential to ensure that the vehicle is not used beyond its intended purpose.

[0094] The vehicle management backend system centrally stores and manages this data, making it accessible for later review or analysis of vehicle usage. By logging startup events, the vehicle manager can maintain detailed records of each vehicle's usage. This information is particularly valuable for fleet management, as it helps identify and prevent unauthorized or unexpected use.

[0095] One advantage is the increased security and control over the vehicle fleet. By limiting the number of engine starts, vehicle managers can ensure that vehicles are not used beyond their permitted limits. This is particularly important when vehicles are temporarily released for service or maintenance, as it significantly reduces the possibility of misuse.

[0096] Furthermore, this functionality enables better vehicle management and maintenance. By accurately monitoring how often a vehicle is started, maintenance intervals can be better planned and overall vehicle maintenance optimized. This leads to a longer vehicle lifespan and potentially lower maintenance costs.

[0097] Another advantage is improved operational efficiency. A detailed understanding of vehicle usage allows vehicle managers to make informed decisions about vehicle deployment, contributing to optimized resource utilization and more efficient vehicle management.

[0098] Overall, this design offers enhanced control and monitoring of vehicle usage, which not only improves safety and maintenance but also helps to reduce operating costs and increase end-user satisfaction.

[0099] According to another preferred embodiment, the vehicle can be configured to automatically send feedback to the vehicle manager backend facility once the unlock PIN has been used to confirm the complete and secure return of the vehicle.

[0100] The vehicle is equipped with a control unit capable of transmitting data directly to the vehicle management backend system. Once a service employee enters the unlock PIN at the end of a rental period to unlock the vehicle and prepare it for return, the vehicle's system recognizes this action and initiates the transmission of a confirmation message. This message contains specific data confirming that the vehicle has been returned correctly.

[0101] The vehicle management backend facility receives this data and updates the vehicle's status in its system, triggering administrative and security-related processes.

[0102] Automatic feedback allows the vehicle manager to verify that the vehicle has indeed been returned and is in a secure condition. This minimizes the risk of theft or loss after return. Additionally, this functionality enables faster and more accurate processing of returns, as the return information can be updated directly in the vehicle manager's system without manual input or delays.

[0103] Another advantage is improved customer service. Customers can receive immediate confirmation after returning the vehicle that their rental agreement has been properly concluded, which strengthens trust in the rental process and avoids potential conflicts or ambiguities regarding the vehicle return.

[0104] In summary, this implementation offers an efficient, secure, and user-friendly solution through the automation of the feedback process, providing significant benefits for both the car rental company and the customer. This helps to streamline administrative processes while simultaneously increasing safety and customer satisfaction.

[0105] According to another preferred embodiment, the vehicle manager backend facility can be configured to automatically send an encrypted immobilizer token to the vehicle after the termination of a vehicle rental agreement in order to secure the vehicle until the next rental.

[0106] The process begins when a specific vehicle has been properly returned and the vehicle manager has identified the vehicle as "returned" or "ready." The vehicle manager's backend facility is notified of the end of the rental agreement, either through manual entry by staff or automatically by a vehicle management system. The vehicle manager's backend facility then generates a new encrypted immobilizer token specifically for that vehicle. This immobilizer token is then sent to the vehicle, using advanced encryption methods to ensure the security of the data transmission.

[0107] As soon as the vehicle receives the new immobilizer token, it is activated and the vehicle is automatically locked by the immobilizer. This prevents the vehicle from being started or used without the appropriate authorization. The immobilizer token remains active until it is decrypted and deactivated by an authorized person who knows the corresponding unlock PIN, or until a new rental agreement begins, for which a different immobilizer token is generated and sent.

[0108] Automatically locking vehicles immediately after they are returned by the vehicle manager significantly reduces the risk of unauthorized access. This is particularly important in car rental companies, where vehicles frequently change location and are used by different people. Encrypting the immobilizer token also ensures that it cannot be manipulated or bypassed by unauthorized individuals. Additionally, a security mechanism could be implemented that allows for an emergency start to guarantee user safety. One possible approach to implementing an emergency start could be the use of an emergency PIN, issued in addition to the regular unlock PIN. This emergency PIN could be activated only in specific situations, such as when the maximum number of engine starts has been reached and the vehicle is in a hazardous area.

[0109] Automating the process of sending and activating immobilizer tokens reduces administrative overhead and the need for manual intervention, which can lead to faster processes and lower operating costs. The vehicle management backend setup also enables centralized monitoring and control of vehicle security, simplifying the management of the entire vehicle fleet.

[0110] Overall, this implementation contributes to improving the security and management efficiency of vehicle fleets by providing a reliable, automated solution for securing vehicles between rentals. This not only increases customer confidence in the security of the rental service but also supports the car rental company's risk management and operational performance.

[0111] Further features, advantages and effects of the invention will become apparent from the following description of preferred embodiments of the invention.

[0112] This shows: Fig. 1 a schematic block diagram of an embodiment of a vehicle management arrangement according to the invention; Fig. 2 a schematic flowchart of an embodiment of a vehicle management method according to the invention; and Fig. 3 a schematic flowchart of a further embodiment of a vehicle management method according to the invention. Fig. 4 a schematic UML diagram of a section of a further embodiment of a vehicle management method according to the invention. Fig. 5 a schematic UML diagram of a section of a further embodiment of a vehicle management method according to the invention. Fig. 6 a schematic UML diagram of a section of a further embodiment of a vehicle management method according to the invention. Fig. 7 a schematic UML diagram of a section of a further embodiment of a vehicle management method according to the invention.

[0113] Corresponding or identical parts are each provided with the same reference symbols in the figures.

[0114] Where appropriate, the described embodiments and further developments can be combined with one another as desired. Further possible embodiments, further developments, and implementations of the invention also include combinations of features of the invention described previously or subsequently with regard to the exemplary embodiments, even if not explicitly mentioned.

[0115] The accompanying drawings are intended to provide a further understanding of the embodiments of the invention. They illustrate embodiments and, in conjunction with the description, serve to explain the principles and concepts of the invention. Other embodiments and many of the aforementioned advantages become apparent with reference to the drawings. The elements of the drawings are not necessarily shown to scale relative to one another. Identical reference numerals denote identical or similarly functioning components.

[0116] Fig. Figure 1 shows a schematic block diagram of an embodiment of a vehicle management system 100 according to the invention. The vehicle management system 100 comprises a vehicle manufacturer backend unit 110, which is configured to generate, manage, and distribute encrypted immobilizer tokens 112 and unlock PINs 114. Each immobilizer token 112 is configured to release an immobilizer 150 of a vehicle 140 when the corresponding unlock PIN 114 is entered. The vehicle manager backend unit 124 communicates with the vehicle manufacturer backend unit 110 to receive the encrypted immobilizer tokens 112 and unlock PINs 114 and forward them to a vehicle manager terminal 130.The vehicle 140 is equipped with a control unit 142 which receives the encrypted immobilizer tokens 112 from the vehicle manufacturer backend unit 110 and / or the vehicle manager backend unit 124 and decrypts them after the unlock PIN 114 is entered in order to release the immobilizer 150.

[0117] Optionally, the control unit 142 of the vehicle 140 can be configured such that, after the immobilizer 150 is released, the decrypted immobilizer token 112 and the unlock PIN 114 are immediately discarded to prevent reuse of the unlock PIN 114. The vehicle manufacturer's backend unit 110 can further be configured to cyclically rotate the encrypted immobilizer tokens 112 and / or the unlock PINs 114.

[0118] The control unit 142 of the vehicle 140 can also communicate wirelessly with the vehicle manufacturer's backend unit 110 and / or the vehicle manager's backend unit 124. The vehicle 140 can be configured to remain unlocked for a predetermined number of engine starts after the unlock PIN 114 has been entered. The control unit 142 of the vehicle 140 can also send the status of the immobilizer 150, in particular the status of the immobilizer token 112 and the unlock PIN 114, to the vehicle manager's backend unit 124.

[0119] The human-machine interface 148 of the vehicle 140 can display the current status of the immobilizer token 112 or the immobilizer 150, or other metadata. Furthermore, the control unit 142 of the vehicle 140 can receive wireless instructions for remotely locking and unlocking the vehicle 140 and execute them via the vehicle manufacturer backend unit 110 and / or the vehicle manager backend unit 124. Upon termination of a rental agreement, the vehicle manager backend unit 124 can automatically send an encrypted immobilizer token 112 to the vehicle 140 to secure it until the next rental.

[0120] Fig. Figure 2 shows a schematic flowchart of an embodiment of a vehicle management method according to the invention. The vehicle management method comprises steps S100, S200, S300, S400, S500, S600, and S700.

[0121] In step S100, encrypted immobilizer tokens 112 and unlocking PINs 114 are generated by a vehicle manufacturer backend facility 110, each immobilizer token 112 being designed to release an immobilizer 150 of the vehicle 140 when the corresponding unlocking PIN 114 is entered.

[0122] In step S200, the encrypted immobilizer tokens 112 and unlocking PINs 114 are managed by the vehicle manufacturer backend facility 110 and distributed to a vehicle manager backend facility 124.

[0123] Step S300 involves forwarding the encrypted immobilizer tokens 112 and unlock PINs 114 from the vehicle manager backend facility 124 to a vehicle manager terminal 130.

[0124] In step S400, a control unit 142 of the vehicle 140 receives the encrypted immobilizer tokens 112 from the vehicle manufacturer backend unit 110 and / or the vehicle manager backend unit 124.

[0125] Step S500 involves the entry of the unlock PIN 114 by a user of vehicle 140.

[0126] In step S600, the control unit 142 decrypts the immobilizer token 112 after entering the corresponding unlock PIN 114.

[0127] Finally, in step S700, the immobilizer 150 of the vehicle 140 is released by the control unit 142 after successful decryption of the immobilizer token 112.

[0128] Fig. Figure 3 shows a schematic flowchart of another embodiment of a vehicle management method according to the invention. The vehicle management method according to this embodiment comprises five process steps S101, S201, S301, S401, and S501. In step S101, the vehicle manufacturer's backend facility 110 configures specific security settings for a vehicle 140. This includes generating and encrypting immobilizer tokens 112 and creating associated unlocking PLNs 114, which make the vehicle 140 accessible only to authorized users.

[0129] In step S201, the vehicle manufacturer backend facility 110 securely transmits the encrypted immobilizer tokens 112 and unlocking PlNs 114 to the vehicle manager backend facility 124, which is responsible for distributing this security data to the corresponding vehicle 140.

[0130] Upon receiving the data in vehicle 140, the control unit 142 activates the received immobilizer token 112 in step S301. This step ensures that vehicle 140 cannot be started without entering the correct unlocking PLN 114.

[0131] In step S401, the authorized user enters the unlock PIN 114 via a human-machine interface 148 to unlock the vehicle 140 and make it available for use. After correct entry, the immobilizer token 112 is deactivated, allowing the user to start and use the vehicle 140.

[0132] After the vehicle 140 has been used, the control unit 142 collects relevant usage data in step S501, such as the number of engine starts performed, and sends this data back to the vehicle manager backend unit 124. This information can be used to analyze and optimize vehicle usage.

[0133] Fig. Figure 4 shows a schematic UML diagram of a section of a further embodiment of a vehicle management method according to the invention. In particular, it shows Fig. 4. The procedure for renewing an unlock PIN 114. The vehicle management procedure begins when a customer 150 returns the vehicle 140. A service employee 151 receives the vehicle 140 from the customer 150 and performs the necessary tasks with the vehicle 140, which can also be performed by several people. A vehicle management backend facility 153, e.g., a special app for managing vehicles 140, supports the service employee 151 in performing these tasks.

[0134] First, a vehicle management introduction procedure (PIN-REF-001) takes place between vehicle manager backend facility 155 and vehicle manufacturer backend facility 156. Next, a barcode of vehicle 140 is scanned to display the vehicle's details (PIN-REF-002 and PIN-REF-003). Then, the processing of vehicle 140 is completed (PIN-REF-004), followed by a request to complete the processing of vehicle 140 for the Vehicle Identification Number (VIN) (PIN-REF-005). Subsequently, the status of vehicle 140 is updated to "Ready for Booking" (PIN-REF-006), and it is determined that an update of the unlock PIN 114 is pending (PIN-REF-007). An event notification regarding the update of the unlock PIN 114 is sent (PIN-REF-008).

[0135] During the return process, vehicle 140 is returned to the vehicle manager backend facility 153 (PIN-REF-009). A verification check confirms that vehicle 140 is in rental mode (PIN-REF-010). A new immobilizer token 112 and a new unlock PIN 114 are generated (PIN-REF-011), stored (PIN-REF-012), and sent to vehicle 140 (PIN-REF-013). Another verification check confirms that vehicle 140 remains in rental mode (PIN-REF-014), and the stored immobilizer token 112 is used for the new unlock PIN 114 (PIN-REF-015). After successful update, a confirmation is sent (PIN-REF-016), the status of the update of the Immobilizer Token 112 is set (PIN-REF-017), and a notification about the new unlock PIN 114 for the specific VIN is sent (PIN-REF-018).The unlock PIN 114 is stored in the vehicle management order 100 for the corresponding VIN (PIN-REF-019), and the status is set to "Unlock PIN 114 updated" (PIN-REF-020).

[0136] Fig. Figure 5 shows a schematic UML diagram of a section of a further embodiment of a vehicle management method according to the invention. In particular, it shows Fig. 5. A procedure for returning a vehicle 140. After the vehicle 140 has been fully processed and a rental agreement terminated (VEH-RET-001), the vehicle 140's QR / barcode is scanned again (VEH-RET-002), and the proper return of the vehicle 140 is confirmed (VEH-RET-005). The vehicle 140's status is set to "Returned" (VEH-RET-006), and the corresponding update is requested (VEH-RET-007). Upon completion of this process, a new unlock PIN 114 can be requested (VEH-RET-010), with the vehicle management order 100 ensuring that the vehicle 140 has indeed been marked as returned (VEH-RET-011). The unlock PIN 114 is finally entered via the human-machine interface 148 (VEH-RET-014), verified (VEH-RET-015), and an engine start can be performed (VEH-RET-016).Then the unlock PIN 114 is written on the windscreen or on a slip of paper (VEH-RET-017).

[0137] Additionally, the procedure includes steps for the safe unlocking and use of the vehicle 140. The procedure, which is described in Fig. As shown in Figure 6, the process begins with unlocking vehicle 140 (PIN-GET-001 and PIN-GET-002), either directly or by requesting remote unlocking via remote services (PIN-GET-003). After unlocking vehicle 140 (PIN-GET-004), the doors are unlocked (PIN-GET-005) to allow access to the interior of vehicle 140. Next, the windshield or any note is checked (PIN-GET-006) to capture relevant information. The barcode of vehicle 140 is scanned (PIN-GET-007) to display specific details of vehicle 140 (PIN-GET-008).

[0138] The next step in the process is requesting the unlock PIN 114 (PIN-GET-009) based on the specific vehicle identification number (VIN) (PIN-GET-010). The system then checks if the vehicle's status is "Returned" (PIN-GET-011) to ensure that vehicle 140 is ready for use. Once unlock PIN 114 is received (PIN-GET-012), it is displayed on the human-machine interface 148 (PIN-GET-013) to allow vehicle 140 to be started.

[0139] Fig. Figure 7 shows a schematic UML diagram of a section of a further embodiment of a vehicle management method according to the invention. In particular, it shows Fig.7. A procedure for managing the return of a vehicle 140. As part of the processing of the vehicle 140, the vehicle 140 can be unlocked (VEH-HDL-001 and VEH-HDL-002), which can also be requested via remote services (VEH-HDL-003). After unlocking the vehicle 140 (VEH-HDL-004) and the doors (VEH-HDL-005), the user enters the unlock PIN 114 via the human-machine interface 148 (VEH-HDL-006) in order to decrypt the immobilizer token 112 with the unlock PIN 114 (VEH-HDL-007).

[0140] If the entered unlock PIN 114 is incorrect, there is a limited number of attempts before entry of the unlock PIN 114 is blocked (VEH-HDL-008). With each incorrect entry of the unlock PIN 114, the blocking time for re-entry increases (VEH-HDL-009), e.g., exponentially, to maximize security. If the unlock PIN 114 is entered correctly, the immobilizer token 112 is decrypted, and the engine of vehicle 140 can be started (VEH-HDL-010), allowing vehicle 140 to be used.

[0141] These comprehensive safety measures and procedures ensure that the vehicle 140 is only used by authorized persons, while at the same time guaranteeing smooth and efficient management of the use of the vehicle 140. Reference list 100 Vehicle Management Order 110 Vehicle manufacturer backend setup 112 Immobilizer Tokens 114 Unlock PIN 124 Vehicle Management Backend Setup 130 vehicle management terminals 140 vehicles 142 Control unit in the vehicle 148 Human-Machine Interface 150 Customer 151 Vehicle Handler (Intro) - Receiving the vehicle from the customer 152 Vehicle Handler (Doing) - Performing tasks with the vehicle (could also be performed by 10 or more different people) 153 Intro Handler App - Vehicle Manager Backend Setup (App for managing vehicles) 154 Vehicle - Vehicle 155 Rental Backend - Vehicle Management Backend Setup 156 Vehicle OEM Backend - Vehicle Manufacturer Backend Setup PIN-REF-001 Vehicle Infleeting Process - Vehicle Management Induction Procedure PIN-REF-002 Scan vehicle barcode - Scan the vehicle barcode PIN-REF-003 Show vehicle details - Show vehicle details PIN-REF-004 Perform "Vehicle Handling Complete" - Complete vehicle handling PIN-REF-005 Request: Vehicle Handling Complete for VIN - Request: Complete vehicle processing for the Vehicle Identification Number (VIN) PIN-REF-006 Update vehicle status: “READY FOR BOOKING” - Update vehicle status: “Ready for booking” PIN-REF-007 Set status: 'PIN UPDATE PENDING' - Set status: "Unlock PIN update pending" PIN-REF-008 Event Notification: Refresh Engine Start PIN - Event notification: Update unlock PIN PIN-REF-009 Return - Return PIN-REF-010 Check: Vehicle in RENTAL Mode - Verification: Vehicle in rental mode PIN-REF-011 Generate Engine Start Immobilizer Token + PIN - Generate immobilizer token and unlock PIN PIN-REF-012 Persist Immotoken+PIN - Store immobilizer token and unlock PIN PIN-REF-013 Push Immotoken - Send immobilizer token PIN-REF-014 Check: Vehicle in RENTAL Mode - Verification: Vehicle in rental mode PIN-REF-015 Persist Immobilizer Token for PIN - Store immobilizer token for unlock PIN PIN-REF-016 Push Confirmation - Send confirmation PIN-REF-017 Set: Immotoken Update Confirmed - Set status: "Update Immobilizer Token Confirmed" PIN-REF-018 Event Notification: Vehicle PIN for VIN - Event notification: Unlock PIN for VIN PIN-REF-019 Persist PIN for VIN - Save unlock PIN for VIN PIN-REF-020 Set status: 'PIN UPDATED' - Set status: "Unlock PIN updated" VEH-RET-001 Turn over vehicle - Terminate booking in rental app - Hand over vehicle - Terminate booking of the vehicle in the vehicle manager backend setup (rental app) VEH-RET-002 Scan Vehicle QR / Barcode - Scan the vehicle's QR / barcode VEH-RET-003 Scan QR / Barcode - Scan QR / Barcode VEH-RET-004 Open Vehicle Screen VEH-RET-005 Confirm Return - Confirm return of vehicle VEH-RET-006 Set vehicle status 'RETURNED' - Set vehicle status to "Returned" VEH-RET-007 Request: Update vehicle status VEH-RET-008 Update vehicle status: 'RETURNED' - Update vehicle status: "Returned" VEH-RET-009 Return - Return VEH-RET -010 Request: Request Engine start PIN - Request: Request unlock PIN VEH-RET-011 Check if vehicle status is 'RETURNED' - Check if the vehicle status is 'Returned' VEH-RET-012 Return: Engine start PIN - Return: Unlock PIN VEH-RET-013 Show Engine Start PIN - Display unlock PIN VEH-RET-014 Enter PIN via HMI - Enter unlock PIN via human-machine interface (HMI) VEH-RET -015 Verify PIN - Verify unlock PIN VEH-RET -016 Perform Engine Start - Perform engine start VEH-RET-017 Write PIN to windscreen / paper note / ... - Write unlock PIN on windscreen / paper note PIN-GET-001 Unlock vehicle - Unlock vehicle PIN-GET-002 Unlock vehicle - Unlock vehicle PIN-GET-003 Request vehicle unlock (remote services) - Request vehicle unlocking (remote services) PIN-GET-004 Unlock vehicle - Unlock vehicle PIN-GET-005 Unlock doors PIN-GET-006 Check windscreen / paper note / ... - Check windscreen / paper note PIN-GET-007 Scan vehicle barcode - Scan the vehicle's barcode PIN-GET-008 Show vehicle details - Show vehicle details PIN-GET-009 Perform 'Request Engine Start PIN' - 'Request unlock PIN' PIN-GET-010 Request: Engine Start PIN for VIN - Request: Unlock PIN for VIN PIN-GET-011 Check if vehicle status is 'RETURNED' - Check if the vehicle status is 'Returned' PIN-GET-012 Return: Engine start PIN - Return: Unlock PIN PIN-GET-013 Show Engine Start PIN - Show unlock PIN VEH-HDL-001 Unlock vehicle - Unlock vehicle VEH-HDL-002 Unlock vehicle - Unlock vehicle VEH-HDL-003 Request vehicle unlock (remote services) - Request vehicle unlocking (remote services) VEH-HDL-004 Unlock vehicle - Unlock vehicle VEH-HDL-005 Unlock doors VEH-HDL-006 Enter PIN via HMI - Enter unlock PIN via human-machine interface (HMI) VEH-HDL-007 Decrypt Immobilizer Token with PIN - Decrypt immobilizer token with unlocking PIN VEH-HDL-008 Decrement Attempt Counter - Reset on successful PIN input or condition - Reduce attempt counter - Reset upon successful unlock PIN entry or condition VEH-HDL-009 Block PIN Input for x Seconds - Blocked time duration increases for each incorrect attempt, e.g., exponentially - Block unlock PIN input for x seconds - Blocked time increases with each incorrect attempt, e.g., exponentially VEH-HDL-010 Perform Engine Start - Perform engine start S100 process step S200 process step S300 process step S400 process step S500 process step S600 process step S700 process step S101 Procedure step S201 Procedure step S301 Procedure step S401 Procedure step S501 Procedure step

Claims

Vehicle management arrangement (100), comprising: a vehicle manufacturer backend device (110) configured to generate, manage and distribute encrypted immobilizer tokens (112) and unlocking PlNs (114), each immobilizer token (112) being configured to release an immobilizer (150) of a vehicle (140) when the corresponding unlocking PIN (114) is entered; a vehicle manager backend device (124) configured to communicate with the vehicle manufacturer backend device (110) for receiving and forwarding the encrypted immobilizer tokens (112) and unlocking PlNs (114) to a vehicle manager terminal device (130);a vehicle (140) equipped with a control unit (142) for receiving the encrypted immobilizer tokens (112) from the vehicle manufacturer backend unit (110) and / or the vehicle manager backend unit (124), and for decrypting the immobilizer tokens (112) after entering the unlock PIN (114) to release the immobilizer (150). Vehicle management arrangement (100) according to claim 1, characterized in that the control unit (142) of the vehicle (140) is configured to immediately discard the decrypted immobilizer token (112) and the unlocking PIN (114) after the release of the immobilizer (150) in order to prevent reuse of the unlocking PIN (114). Vehicle management arrangement (100) according to claim 1 or 2, characterized in that the vehicle manufacturer backend device (110) is configured to cyclically rotate the encrypted immobilizer tokens (112) and / or the unlocking PINs (114). Vehicle management arrangement (100) according to one of the preceding claims, characterized in that the control unit (142) of the vehicle (140) is configured to communicate wirelessly with the vehicle manufacturer backend unit (110) and / or the vehicle manager backend unit (124). Vehicle management arrangement (100) according to one of the preceding claims, characterized in that the vehicle (140) remains unlocked for a predetermined number of engine starts after entry of the unlock PIN (114). Vehicle management arrangement (100) according to one of the preceding claims, characterized in that the control unit (142) of the vehicle (140) is configured to send the status of the immobilizer (150), in particular the status of the immobilizer token (112) and the unlocking PIN (114), to the vehicle management backend unit (124). Vehicle management arrangement (100) according to one of the preceding claims, characterized in that the human-machine interface (148) is configured to display the current status of the immobilizer token (112). Vehicle management arrangement (100) according to one of the preceding claims, characterized in that the control unit (142) of the vehicle (140) is configured to receive and implement wireless instructions for remote locking and unlocking of the vehicle (140) via the vehicle manufacturer backend unit (110) and / or a vehicle manager backend unit (124). Vehicle management arrangement (100) according to one of the preceding claims, characterized in that the vehicle manager backend device (124) is configured to automatically send an encrypted immobilizer token (112) to the vehicle (140) after termination of a rental agreement of the vehicle (140) in order to secure the vehicle (140) until the next rental. Vehicle management procedure for managing a vehicle (140), comprising the following steps: (S100) Generating encrypted immobilizer tokens (112) and unlocking PlNs (114) by a vehicle manufacturer backend facility (110), each immobilizer token (112) being configured to release an immobilizer (150) of the vehicle (140) when the corresponding unlocking PIN (114) is entered; (S200) Managing and distributing the encrypted immobilizer tokens (112) and unlocking PlNs (114) by the vehicle manufacturer backend facility (110) to a vehicle manager backend facility (124); (S300) Forwarding the encrypted immobilizer tokens (112) and unlocking PlNs (114) from the vehicle manager backend facility (124) to a vehicle management terminal (130);(S400) Receipt of the encrypted immobilizer token (112) by a control unit (142) of the vehicle (140) from the vehicle manufacturer backend unit (110) and / or the vehicle manager backend unit (124); (S500) Entry of the unlock PIN (114) by a user of the vehicle (140); (S600) Decryption of the immobilizer token (112) by the control unit (142) after entry of the corresponding unlock PIN (114); (S700) Release of the immobilizer (150) of the vehicle (140) by the control unit (142) after successful decryption of the immobilizer token (112).;

Images