Systems and methods for managing fleet digital access credentials

By managing digital key credentials in the fleet system, utilizing the controller of the lead vehicle and the remote backend to verify the key credential data of following vehicles, and selecting the appropriate access mode, the security risks of fleet data transmission and verification are resolved, enabling more efficient traffic management and security control.

CN123075426APending Publication Date: 2026-11-10GM GLOBAL TECHNOLOGY OPERATIONS LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510845145.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2025-06-23
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In existing fleet systems, data transmission and verification between fleets are not effectively carried out, leading to security risks and management inconveniences.

Method used

The controller in the lead vehicle receives digital key credential data from the following vehicles, stores it in the lead-follower key matrix, and manages key sharing based on validity time and shareable attributes. It selects centralized or decentralized access modes, transmits credentials remotely or directly to the following vehicles, and coordinates access transactions and negotiations for the fleet.

Benefits of technology

It improved fleet safety and management efficiency, reduced safety risks, and optimized traffic flow and fuel efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075426A_ABST
    Figure CN123075426A_ABST
Patent Text Reader

Abstract

A method for managing digital access credentials for a fleet of vehicles includes a controller in a lead vehicle receiving digital key credential data transmitted when one or more following vehicles join the fleet. The digital key credential data includes a valid key value and is stored in a lead-follower key matrix. The method further includes the lead vehicle selecting a centralized or decentralized access mode for an upcoming access transaction. The lead vehicle transmits the digital key credential data to a remote backend to receive credentials. In centralized access mode, the lead vehicle uses the received credentials to perform the access transaction with a local device. In decentralized access mode, the lead vehicle forwards the received credentials to the appropriate following vehicle, and the one or more following vehicles perform the access transaction. The method also includes disabling access to the digital key credential data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to a system and method for managing digital access credentials. More specifically, this disclosure relates to a system and method for managing digital access credentials for a fleet of vehicles. Background Technology

[0002] A convoy consists of a lead vehicle and one or more follower vehicles. The lead vehicle receives data from the one or more follower vehicles and coordinates the driving responses of each vehicle in the convoy based on the received data. However, the received data may not be verifiable, leading to safety risks.

[0003] Therefore, while the current fleet has achieved its intended purpose, a new and improved approach is still needed to manage the fleet's digital access credentials. Summary of the Invention

[0004] According to several aspects, a method for managing digital access credentials for a fleet is provided. The fleet includes a lead vehicle and one or more following vehicles. The method includes receiving digital key credential data transmitted by one or more following vehicles when they join the fleet via a controller in the lead vehicle. The method also includes storing the digital key credential data in a lead-follower key matrix, which records at least one key-sharing parameter for each following vehicle. The key-sharing parameter includes a valid key value with a start time and an end time. The start time and end time verify the validity of the digital key credential data. The method further includes selecting a centralized access mode or a decentralized access mode for an upcoming access transaction via the lead vehicle. This selection is based on the current route segment and trajectory of the fleet and the number of available key slots in the lead vehicle. The method also includes transmitting the digital key credential data to a remote backend via the lead vehicle. The method further includes: for centralized access mode, performing an access transaction with a local device via the lead vehicle using credentials received from the remote backend. The method further includes: for decentralized access mode, forwarding credentials received from the remote backend via the lead vehicle to the appropriate following vehicle. The method also includes, for a decentralized access mode, performing access transactions with the local device using credentials received from a remote backend through one or more following vehicles. The method also includes disabling the lead vehicle's access to the digital key credential data and removing the one or more following vehicles from the fleet.

[0005] In another aspect of this disclosure, the method further includes merging digital key credential data from the one or more following vehicles into a leader-follower key matrix.

[0006] In another aspect of this disclosure, the method also includes transmitting instructions from the lead vehicle to the one or more following vehicles in the convoy via a controller in the lead vehicle.

[0007] In another aspect of this disclosure, instructions from the lead vehicle determine the speed of the one or more following vehicles and the range of spacing between consecutive vehicles.

[0008] In another aspect of this disclosure, the digital key credential data includes a shareable attribute. This shareable attribute determines when the lead vehicle leaves the convoy. The lead vehicle shares the digital key credential data with one of the following vehicles.

[0009] In another aspect of this disclosure, the method further includes, for a non-centralized access mode, performing access negotiation with the local device using credentials received from a remote backend through one or more following vehicles.

[0010] In another aspect of this disclosure, the method further includes, for a non-centralized access mode, performing access negotiation with the local device using credentials received from a remote backend by the lead vehicle.

[0011] In another aspect of this disclosure, the method also includes notifying the one or more following vehicles of an access transaction and access negotiation performed on behalf of the one or more following vehicles by the lead vehicle.

[0012] In another aspect of this disclosure, the lead-follow key matrix has a storage threshold. The storage threshold sets a limit on the lead vehicle and the local device performing access transactions on the one or more following vehicles in centralized access mode.

[0013] In another aspect of this disclosure, when one or more following vehicles exceed a storage threshold, the one or more following vehicles exceeding the storage threshold perform an access transaction with the local device.

[0014] According to several aspects, a system for managing digital access credentials for a fleet is provided. The fleet includes a lead vehicle and one or more following vehicles. The system includes a controller in the lead vehicle for receiving digital key credential data transmitted when the one or more following vehicles join the fleet. The system also includes a lead-follower vehicle key matrix for storing the digital key credential data for each following vehicle. The digital key credential data records at least one key-sharing parameter. The key-sharing parameter includes a valid key value having a start time and an end time. The start time and end time verify the validity of the digital key credential data. The key-sharing parameter also includes a shared key value for sharing at least one key from the digital key credential data of the one or more following vehicles. The key-sharing parameter also includes a shareable key value. The one or more following vehicles determine the shareable key within the digital key credential data. The key-sharing parameter also includes an authorization value. The one or more following vehicles identify the lead vehicle's access to the digital key credential data. The system also includes a lead vehicle that selects an access mode for an upcoming access transaction based on the current route segment and trajectory of the fleet and the number of available key slots in the lead vehicle. The access mode includes a centralized access mode. The lead vehicle transmits the digital key credential data to a remote backend. The lead vehicle uses the credentials received from the remote backend to perform access transactions and negotiations with the local equipment. Access modes also include a decentralized access mode. The lead vehicle transmits the digital key credential data to the remote backend. The lead vehicle forwards the credentials received from the remote backend to the corresponding following vehicles. These one or more following vehicles use the credentials received from the remote backend to perform access transactions and negotiations with the local equipment. The system may also include removing one or more following vehicles from the fleet, thereby disabling the lead vehicle's access to the digital key credential data.

[0015] In another aspect of this disclosure, the system also includes a lead-follow key matrix for the lead vehicle that merges digital key credential data from the one or more following vehicles.

[0016] In another aspect of this disclosure, the controller in the lead vehicle transmits instructions from the lead vehicle to the one or more following vehicles in the convoy.

[0017] In another aspect of this disclosure, instructions from the lead vehicle determine the speed of the one or more following vehicles and the range of spacing between consecutive vehicles.

[0018] In another aspect of this disclosure, the digital key credential data includes a shareable attribute. This shareable attribute determines when the lead vehicle leaves the convoy. The lead vehicle shares the digital key credential data with one of the following vehicles.

[0019] In another aspect of this disclosure, the system also includes a lead vehicle that notifies the one or more following vehicles of access transactions and access negotiations performed on behalf of the one or more following vehicles.

[0020] In another aspect of this disclosure, the lead-follow key matrix has a storage threshold. The storage threshold sets a limit on the lead vehicle and the local device performing access transactions on the one or more following vehicles in centralized access mode.

[0021] In another aspect of this disclosure, when one or more following vehicles exceed a storage threshold, the one or more following vehicles exceeding the storage threshold perform an access transaction with the local device.

[0022] According to several aspects, a method for managing digital access credentials for a fleet is provided. The fleet includes a lead vehicle and one or more following vehicles. The method includes receiving digital key credential data transmitted by the one or more following vehicles when they join the fleet via a controller in the lead vehicle. The method also includes storing the digital key credential data in a lead-follower key matrix, which records at least one key-sharing parameter for each following vehicle. The key-sharing parameter includes a valid key value having a start time and an end time. The start time and end time verify the validity of the digital key credential data. The key-sharing parameter also includes a shared key value. The shared key value shares at least one key from the digital key credential data of the one or more following vehicles. The key-sharing parameter also includes an authorization value. The one or more following vehicles identify the lead vehicle's access to the digital key credential data. The method also includes selecting a centralized access mode or a decentralized access mode for an upcoming access transaction via the lead vehicle. This selection is based on the current route segment and trajectory of the fleet and the number of available key slots in the lead vehicle. The method also includes transmitting the digital key credential data to a remote backend via the lead vehicle. The method also includes transmitting instructions from the lead vehicle to the one or more following vehicles via a controller in the lead vehicle. These instructions include determining the speed of the one or more following vehicles to coordinate their speed with the lead vehicle. The instructions also include determining the spacing range between each vehicle in the convoy. The method further includes, for centralized access mode, having the lead vehicle perform an access transaction with the local device using credentials received from a remote backend. The method also includes, for centralized access mode, having the lead vehicle perform access negotiation with the local device using credentials received from a remote backend. The method further includes, for decentralized access mode, having the lead vehicle forward credentials received from the remote backend to the appropriate following vehicles. The method also includes, for decentralized access mode, having the one or more following vehicles perform access transactions with the local device using credentials received from a remote backend. The method further includes, for decentralized access mode, having the one or more following vehicles perform access negotiation with the local device using credentials received from a remote backend. The method also includes, for decentralized access mode, having the lead vehicle notify the one or more following vehicles of the access transactions and access negotiations performed on their behalf. The method also includes disabling the lead vehicle's access to the digital key credential data and removing at least one following vehicle from the fleet.

[0023] In another aspect of this disclosure, the lead-follow key matrix has a storage threshold. The storage threshold sets a limit on the lead vehicle that performs access transactions and access negotiations on behalf of one or more following vehicles. When one or more following vehicles exceed the storage threshold, the one or more following vehicles exceeding the storage threshold perform access transactions and access negotiations with the local device.

[0024] Further areas of application will become apparent from the description provided herein. It should be understood that the descriptions and specific examples are for illustrative purposes only and are not intended to limit the scope of this disclosure. Attached Figure Description

[0025] The accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure in any way.

[0026] Figure 1 This is a schematic diagram of a vehicle fleet according to an exemplary embodiment.

[0027] Figure 2 This is a schematic diagram of a fleet in a centralized access mode according to an exemplary embodiment.

[0028] Figure 3 This is a schematic diagram of a fleet in a non-centralized access mode according to an exemplary embodiment.

[0029] Figure 4 This is a flowchart of a method for a fleet under a centralized access mode according to an exemplary embodiment.

[0030] Figure 5 This is a flowchart of a method for a fleet in a non-centralized access mode according to an exemplary embodiment. Detailed Implementation

[0031] The following description is exemplary in nature and is not intended to limit this disclosure, application, or use.

[0032] Reference Figure 1 A schematic diagram of convoy 10 is shown. Convoy 10 includes a lead vehicle 12 and one or more following vehicles 14 traveling closely in the same direction. The lead vehicle 12 communicates with the one or more following vehicles 14 to coordinate their driving responses. During operation, the total number of participating vehicles in convoy 10 may change. Vehicles may request to join convoy 10, and one or more following vehicles 14 may request to leave convoy 10, resulting in the lead vehicle 12 maintaining and updating communication with each of the one or more following vehicles 14. It should be understood that... Figure 1 This is merely an example, and the lead vehicle 12 and the one or more following vehicles 14 in the convoy 10 can be any type of vehicle, such as, but not limited to, cars, trucks, SUVs, vans, or motorhomes.

[0033] The lead vehicle 12 collects data via a first Global Positioning System (GPS) 16 and a first sensor group 18 disposed within the lead vehicle 12. The first sensor group 18 communicates with a controller 20 disposed within the lead vehicle 12. The first GPS 16 provides the position of the lead vehicle 12 to allow the lead vehicle 12 to navigate and to communicate the position of the lead vehicle 12 to the one or more following vehicles 14. The first sensor group 18 is configured to generate signals based on observable conditions of the external environment of the lead vehicle 12. The first sensor group 18 may be, but is not limited to, one or more sensors, including radio detection and ranging (RADAR) sensors, light detection and ranging (LIDAR) sensors, proximity sensors, ground-penetrating radar (GPR) sensors, and / or cameras (e.g., optical cameras and / or infrared cameras). The first sensor group 18 allows the lead vehicle 12 to determine and communicate the distance to the one or more following vehicles 14. It should be understood that the first sensor group 18 is disposed within the lead vehicle 12 and may include any number of sensors without departing from the scope of this disclosure.

[0034] The first sensor group 18 senses observable conditions outside the lead vehicle 12. These observable conditions include road conditions, driving conditions around the lead vehicle 12, and local devices 22 (such as...). Figure 2 (As shown). Road conditions include, but are not limited to, road curvature, traffic patterns, intersection configuration, paved roads, unpaved roads, and precipitation. Local equipment 22 (e.g.) Figure 2 (As shown) may include, but is not limited to, vehicles not included in fleet 10, toll collection systems, parking systems, and charging stations.

[0035] A controller 20 in the lead vehicle 12 coordinates the driving responses between the lead vehicle 12 and one or more following vehicles 14. The coordinated responses may include, but are not limited to, speed and spacing ranges. The controller determines the speed of each of the lead vehicle 12 and each of the one or more following vehicles 14, and causes the lead vehicle 12 and each of the one or more following vehicles 14 to travel at the determined speed. Furthermore, the controller defines the spacing range and maintains each vehicle in the convoy 10 within the defined spacing range between each consecutive vehicle. The coordinated responses improve aerodynamic efficiency and performance, thereby increasing road capacity and providing a more stable traffic flow. The controller 20 is a non-general-purpose electronic control device having a pre-programmed digital computer or processor 26, a memory 28, input and output ports 30, and a transceiver 24.

[0036] Processor 26 may be a custom or commercially available processor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processor among multiple processors associated with controller 20, a semiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, a combination thereof, or generally a device for executing instructions. Memory 28 is used to store and record data from the leader-follower key matrix 42, including digital key credential data described further in detail below. Memory 28 also stores control logic, software applications, instructions, computer code, data, lookup tables, etc. Memory 28 includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and overwrite it later, such as rewritable optical discs or erasable storage devices. Computer code includes any type of program code, including source code, object code, and executable code.

[0037] Input and output port 30 receives input data from the first sensor group 18 and the first GPS 16. The input data is transmitted to processor 26. Input and output port 30 also receives data from the one or more following vehicles 14, which will be described in further detail below. Processor 26 processes the input data and the data received from the one or more following vehicles 14 to determine and convey instructions from the lead vehicle 12 to the one or more following vehicles 14.

[0038] Transceiver 24 is configured to conduct wireless information communication with the lead vehicle 12, such as, but not limited to, vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, remote systems of remote call centers (e.g., General Motors' ON-STAR), and / or personal devices. Communication with remote systems can be conducted via cellular links, Wi-Fi links, satellite links, or other radio frequency (RF) technologies. The lead vehicle 12 may include one or more antennas and / or transceiver 24 for receiving and / or transmitting signals (e.g., cooperative sensing messages (CSM)).

[0039] The lead vehicle 12 wirelessly communicates with one or more following vehicles 14 via V2V communication to request data from them. Each following vehicle 14 includes a second sensor array 32, a second GPS 34, and a follow key matrix 36 to store the requested data. The second sensor array 32, located within each following vehicle 14, senses observable conditions outside the vehicle. The second GPS 34 provides the location of each following vehicle 14. The follow key matrix 36 stores digital key credential data. The digital key credential data includes at least key-sharing parameters.

[0040] The key-sharing parameters include at least the valid key value, the shared key value, the shareable key value, and the authorized value. The valid key value identifies the start and end times used to verify the validity of the digital key credential data. The shared key value identifies the key value shared between the lead vehicle 12 and the one or more following vehicles 14. The shareable key value identifies which keys the one or more following vehicles 14 can share with the lead vehicle 12. The authorized value identifies the lead vehicle 12's access to the key shared by the one or more following vehicles 14. For example, the lead vehicle 12 may have full access, limited access, and / or driving capability.

[0041] To verify the credentials of the digital key credential data for each of the one or more following vehicles 14, the lead vehicle forwards the digital key credential data to a remote backend 38 in the cloud 40. The remote backend 38 verifies the credentials using a server that verifies signatures using the vehicle's public key and cross-checks the data against a secure credential database. The remote backend 38 then transmits the result of the digital key credential data for each of the one or more following vehicles 14 back to the lead vehicle 12. This result may include whether the credentials are unverified or verified. The lead vehicle 12 refuses to allow one or more unverified following vehicles 14 to join the convoy 10, thereby reducing the security risk of the convoy 10.

[0042] Alternatively, the lead vehicle 12 allows one or more following vehicles 14 with verified credentials to join the convoy 10, thereby granting the lead vehicle 12 access to and management of the verified digital key credential data. By accessing and managing the digital key credential data, the lead vehicle 12 can determine one or more operating parameters of the convoy 10. For example, the lead vehicle 12 can determine the speed of each vehicle in the convoy 10, the distance between consecutive vehicles in the convoy 10, and / or allow the lead vehicle 12 to perform some or all access negotiations and / or access transactions with external entities on behalf of all vehicles in the convoy 10. The external entity can be a remote entity or a local device 22, such as, but not limited to, a remote toll collection system, a road use system, a locally controlled access gate, or a remotely controlled access gate.

[0043] Reference Figure 2 and Figure 3 The diagram illustrates a convoy 10. The lead vehicle 12 can select an access mode to control and manage digital key credential data. The access mode can be either centralized access mode 44 or decentralized access mode 46. This selection can be based on a prior configuration in the controller 20 of the lead vehicle 12 to specify centralized access mode 44 or decentralized access mode 46. Furthermore, the selection can be based on the current route segment and trajectory of convoy 10, the number of available key slots in the lead-follower key matrix 42, and the prior configuration in one or more following vehicles 14. The prior configuration in one or more following vehicles 14 specifies the selection of centralized access mode 44, the selection of decentralized access mode 46, and a preference for centralized access mode 44 or decentralized access mode 46.

[0044] For example, when the number of vehicles in fleet 10 exceeds a threshold, the decentralized access mode 46 may overwhelm local device 22 or its remote system. Local device 22's remote system manages access negotiation and / or access transactions. Therefore, a centralized access mode is selected, allowing the lead vehicle 12 to perform access negotiation and access transactions on behalf of all vehicles in fleet 10, thereby improving traffic flow and / or fuel efficiency in fleet 10.

[0045] Alternatively, there might be a road segment with multiple toll lanes available, used simultaneously by multiple vehicles in convoy 10. For example, six vehicles in convoy 10 might pass through a six-lane toll area. Decentralized access mode 46 might have advantages. The lead vehicle 12 negotiates access with local equipment 22, while each of the following vehicles 14 communicates access transactions with local equipment 22. Alternatively, specific access restrictions might exist on certain road segments, prohibiting the gates from opening simultaneously for all vehicles in convoy 10, thus requiring data collection from each vehicle passing through the gates to make decentralized access mode 46 more efficient.

[0046] Alternatively, local device 22 or a backend system supporting local device 22 may preferentially select centralized access mode 44 or decentralized access mode 46. This preference or selection can be sent to lead vehicle 12 via a handshake message or advertisement. Lead vehicle 12 uses this preference to determine whether to use centralized access mode 44 or decentralized access mode 46.

[0047] A mixed access mode may also exist, in which some of the one or more following vehicles 14 use a centralized access mode 44, allowing the lead vehicle 12 to represent some of the one or more following vehicles 14 in access negotiation and / or access transactions. While some of the one or more following vehicles 14 use centralized access mode 44, the other following vehicles of one or more following vehicles 14 use a non-centralized access mode 46. For example, a convoy 10 may consist of twelve cars that need to pass through a three-lane toll area. The lead vehicle 12 provides access negotiation and access transactions on behalf of three of the one or more following vehicles 14. The remaining eight following vehicles 14 use other lanes and conduct access transaction exchanges independently. It should be understood that... Figure 2 and Figure 3 This is merely an example, and local device 22 is not limited to a toll collection system. Local device 22 could also be a vehicle not included in fleet 10, a parking system, or a charging station.

[0048] Figure 2 The diagram illustrates a convoy 10 in centralized access mode 44. In centralized access mode 44, the lead vehicle 12 receives key-sharing parameters from at least each of the one or more following vehicles 14, and merges and stores these parameters in a lead-follower vehicle key matrix 42 stored in the lead vehicle 12. During convoy travel, the lead vehicle 12 can sense a local device 22 within a predetermined distance. This predetermined distance may be, but is not limited to, within 30, 60, or 120 feet of the local device 22. Once the convoy 10 reaches the local device 22 within the predetermined distance, the lead vehicle 12 can perform access transactions and / or access negotiations with the local device 22 using local short-range communication or remote communication. This remote communication uses Internet access and represents each of the one or more following vehicles 14.

[0049] Access negotiation between the lead vehicle 12 and the local device 22 may include the lead vehicle 12 presenting digital information to the local device 22, thereby allowing the lead vehicle 12 to self-identify and authenticate with the local device 22. Furthermore, the digital information allows the lead vehicle 12 to prove its right to access or passage to the local device 22. The digital information may be, but is not limited to, a pre-negotiated certificate stored within the lead vehicle 12. The local device 22 may accept the pre-negotiated certificate, or its backend system may perform a determination of the acceptability of the pre-negotiated certificate. Access transactions between the lead vehicle 12 and the local device 22 include determining the fees payable by the lead vehicle 12 and any one of the following vehicles 14 represented by the lead vehicle 12 when performing the access transaction. For example, the lead vehicle 12 determines the fees payable by the convoy 10 for using a road or passing through a gate or restricted area. The local device 22 may, in turn, use database resources from its local computer and remote backend systems to calculate the transaction fees. The local device 22 communicates the transaction fees to the lead vehicle 12.

[0050] Alternatively, local device 22 may be a virtual local device, enforced via geofencing configured on lead vehicle 12 to implement different access negotiation and access transaction policies as convoy 10 crosses state, national, or county boundaries or enters / leaves any area with specific access policies. The executed access transactions and / or access negotiations are based on digital key credential data stored in lead-follower key matrix 42. Simultaneously executing access transactions and access negotiations for each of the one or more follower vehicles 14 improves the efficiency of each access transaction and access negotiation.

[0051] The lead-follow key matrix 42 is a data structure stored in the lead vehicle 12. For each following vehicle, the lead-follow key matrix 42 stores the digital key credential data of that following vehicle. The digital key credential data of the following vehicles includes the valid window, shared key count, shareable key count, and authorization value. The digital key credential data of the following vehicles is stored in a limited set of key slots in the lead-follow key matrix 42, enabling the lead vehicle 12 to verify these credentials and perform access negotiation and / or access transactions for the entire fleet 10. The lead-follow key matrix 42 has storage limits or storage thresholds for the key slots. The storage limit defines the maximum number of key slots that can be stored in the lead-follow key matrix 42, thereby limiting the access transactions and access negotiations that the lead vehicle 12 can perform. The total number of participating vehicles in the fleet 10 may change. Additional vehicles may be added to the number of one or more following vehicles 14. Digital key credential data from additional vehicles may exceed the storage limit. If the digital key credential data of an additional vehicle exceeds the storage limit, the lead vehicle 12 will not perform access transactions or access negotiations for the additional vehicle. However, the lead vehicle 12 will continue to coordinate driving instructions from other vehicles. For example, the lead vehicle 12 can coordinate driving instructions via short-range V2V communication.

[0052] Figure 3 The diagram illustrates a convoy 10 in decentralized access mode 46. In decentralized access mode 46, the lead vehicle 12 receives verified credentials from a remote backend 38. Once the convoy 10 reaches a predetermined distance, the lead vehicle 12 forwards the verified credentials to the corresponding following vehicles 14 and sends instructions to each of the one or more following vehicles 14 via V2V communication. The one or more following vehicles 14 follow the instructions provided by the lead vehicle 12 and perform access transactions and / or access negotiations with the local device 22 via V2I communication. Instructions on the responses of each of the one or more following vehicles improve the efficiency of access transactions and access negotiations.

[0053] For example, access negotiation between the one or more following vehicles 14 and the local device 22 may include the lead vehicle 12 presenting digital data to the local device 22, thereby allowing the lead vehicle 12 to perform self-identification and verification with the local device 22. Furthermore, the digital data allows the lead vehicle 12 to prove its right to access or passage to the local device 22. The digital data may be, but is not limited to, a pre-negotiated certificate stored in the lead vehicle 12. The local device 22 may accept the pre-negotiated certificate, or its backend system may perform a determination of the acceptability of the pre-negotiated certificate. The access transaction between the one or more following vehicles 14 and the local device 22 includes determining the fees to be paid, and the local device 22 communicating the transaction fees to the lead vehicle 12. Once the fee determination is communicated to the lead vehicle 12, the lead vehicle 12 communicates the fees to the one or more following vehicles 14 and instructs the one or more following vehicles 14 to proceed with the access transaction.

[0054] Reference Figure 4 The diagram illustrates a flowchart of a method 100 for managing fleet digital access credentials under centralized access mode 44. Method 100 begins at step 102. In step 102, the lead vehicle 12 communicates with one or more following vehicles 14 to request data from one or more following vehicles 14. Method 100 then proceeds to step 104.

[0055] In step 104, the one or more following vehicles 14 transmit their respective digital key credential data to the lead vehicle 12, thereby allowing the lead vehicle 12 to access and manage the digital key credential data. The digital key credential data includes at least key-sharing parameters. These parameters include at least a valid key value, a shared key value, a shareable key value, and an authorized value. The valid key value identifies the start and end times for verifying the validity of the digital key credential data. The shared key value identifies the value of the key shared between the lead vehicle 12 and the one or more following vehicles 14. The shareable key value identifies the value that the one or more following vehicles 14 determine which keys can be shared with the lead vehicle 12. The authorized value identifies the lead vehicle 12's access to the keys shared by the one or more following vehicles 14. For example, the lead vehicle 12 may have full access, limited access, and driving capabilities. Full access allows the lead vehicle 12 to perform all access functions of the one or more following vehicles 14 without any restrictions or limitations. Restricted access allows one or more following vehicles 14 to create access restrictions while sharing a key with the lead vehicle 12. Driving capability allows the lead vehicle 12 to perform driving actions while the one or more following vehicles 14 are in motion, and requires other capabilities bound to the digital access system.

[0056] The shared key can have a "shareable" attribute to indicate whether the lead vehicle 12 can share the shared key with any of the following vehicles 14 when the lead vehicle 12 is about to leave convoy 10 or stops being the lead vehicle 12 of convoy 10. For example, the shareable attribute is set for vehicle C so that it can share the shared key with the lead vehicle A. When the lead vehicle A terminates its lead role and / or leaves convoy 10, it can share the shared key with vehicle B. Vehicle B will then become the new lead vehicle, thus eliminating the need to exchange further key-sharing messages with vehicle C. The digital key credential data is received via the controller 20 of the lead vehicle 12. Method 100 proceeds to step 106.

[0057] In step 106, the lead vehicle 12 transmits digital key credential data from each of the one or more following vehicles 14 to the remote backend 38. Method 100 proceeds to step 108. In step 108, the remote backend 38 receives the digital key credential data and verifies the credentials for each digital key credential data. Method 100 proceeds to step 110.

[0058] In step 110, the lead vehicle 12 allows one or more following vehicles 14 with verified credentials to join the fleet 10. Method 100 continues to step 112. In step 112, the lead vehicle 12, based on the received digital key credential data, performs an access transaction and / or access negotiation with the local device 22 on behalf of each of the one or more following vehicles 14. The lead vehicle 12 notifies the one or more following vehicles 14 of the performed access transaction and / or access negotiation. Method 100 continues to step 114. In step 114, the one or more following vehicles 14 may deactivate their access to the digital key credential data, thereby removing the one or more following vehicles 14 from the fleet 10.

[0059] Reference Figure 5 The diagram illustrates a flowchart of a method 200 for managing fleet digital access credentials under a decentralized access mode 46. Method 200 begins at step 202. In step 202, the lead vehicle 12 communicates with one or more following vehicles 14 to request data from them. Method 200 then proceeds to step 204.

[0060] In step 204, the one or more following vehicles 14 transmit their respective digital key credential data to the lead vehicle 12, thereby allowing the lead vehicle 12 to access and manage the digital key credential data. The digital key credential data includes at least key-sharing parameters. These parameters include at least a valid key value, a shared key value, a shareable key value, and an authorized value. The valid key value identifies the start and end times used to verify the validity of the digital key credential data. The shared key value identifies the value of the key shared between the lead vehicle 12 and the one or more following vehicles 14. The shareable key value identifies the value that the one or more following vehicles 14 determine which keys can be shared with the lead vehicle 12. The authorized value identifies the lead vehicle 12's access to the key shared by the one or more following vehicles 14. For example, the lead vehicle 12 may have full access, limited access, and driving capability. The digital key credential data is received via the controller 20 of the lead vehicle 12. Method 200 then proceeds to step 206.

[0061] In step 206, the lead vehicle 12 transmits digital key credential data from each of the one or more following vehicles 14 to the remote backend 38. Method 200 proceeds to step 208. In step 208, the remote backend 38 receives the digital key credential data and verifies the credentials for each digital key credential data. Method 200 proceeds to step 210.

[0062] In step 210, the lead vehicle 12 allows one or more following vehicles 14 to join the convoy 10. Method 200 continues to step 212. In step 212, the lead vehicle 12 sends an instruction to one or more following vehicles 14. The one or more following vehicles 14 receive the instruction and perform an access transaction and / or access negotiation with the local device 22. Method 200 continues to step 214. In step 214, the one or more following vehicles 14 may deactivate access to the digital key credential data, thereby removing one or more following vehicles 14 from the convoy 10.

[0063] The methods 100 and 200 of this disclosure offer several advantages. These advantages include improved aerodynamic efficiency and driving performance, increased road capacity, and more stable traffic flow. Furthermore, verifying the digital key credential data of one or more following vehicles 14 reduces security risks within the convoy 10.

[0064] The description in this disclosure is merely exemplary in nature, and any modifications that do not depart from the spirit of this disclosure are intended to fall within its scope. Such modifications should not be considered as departing from the scheme and scope of this disclosure.

Claims

1. A method for managing digital access credentials for a fleet of vehicles, the fleet comprising a lead vehicle and one or more following vehicles, the method comprising: The controller in the lead vehicle receives digital key credential data transmitted when one or more following vehicles join the convoy; The digital key credential data is stored in a leader-follower key matrix, which records at least one key-sharing parameter for each following vehicle. The at least one key-sharing parameter includes: A valid key value having a start time and an end time, wherein the start time and end time verify the validity of the digital key credential data; The lead vehicle selects a centralized or decentralized access mode for the upcoming access transaction, the selection being based on the current route segment and trajectory of the convoy and the number of available key slots in the lead vehicle. The digital key credential data is transmitted to the remote backend via the lead vehicle. In the centralized access mode, the lead vehicle uses credentials received from the remote backend to perform access transactions with the local device. In the non-centralized access mode, the lead vehicle forwards the credentials received from the remote backend to the corresponding following vehicles. For the decentralized access mode, the access transaction is performed with the local device by one or more following vehicles using credentials received from the remote backend; and Disable the lead vehicle's access to the digital key credential data and remove one or more following vehicles from the convoy.

2. The method of claim 1 further includes merging the digital key credential data from the one or more following vehicles into the leader-follower key matrix.

3. The method of claim 1, further comprising transmitting instructions from the lead vehicle to the one or more following vehicles in the convoy via a controller in the lead vehicle.

4. The method according to claim 3, wherein, The instructions from the lead vehicle determine the speed of the one or more following vehicles and the range of spacing between consecutive vehicles.

5. The method according to claim 1, wherein, The digital key credential data includes a shareable attribute, wherein the shareable attribute determines that the lead vehicle leaves the convoy, and wherein the lead vehicle shares the digital key credential data with one of the following vehicles.

6. The method according to claim 1, further comprising: In the decentralized access mode, one or more following vehicles use credentials received from the remote backend to perform access negotiation with the local device.

7. The method according to claim 1, further comprising: In the decentralized access mode, the lead vehicle uses credentials received from the remote backend to perform access negotiation with the local device.

8. The method of claim 7, further comprising the lead vehicle notifying one or more following vehicles of the access transaction and the access negotiation performed on behalf of the one or more following vehicles.

9. The method according to claim 1, wherein, The lead-follower key matrix has a storage threshold, wherein the storage threshold is the restriction set by the lead vehicle and the local device for the access transaction performed by the local device on one or more following vehicles in the centralized access mode.

10. The method according to claim 9, wherein, When one or more following vehicles exceed the storage threshold, the one or more following vehicles exceeding the storage threshold perform the access transaction with the local device.