System and method for assigning and using privileges to assist maneuvering and driving of vehicle

Abstract

Techniques are described for enabling a device, such as a user terminal, or an in-vehicle system to receive permissions related to maneuvering and driving of a vehicle associated with the device. The vehicle can support land, water, air or space driving. The privilege grant authorization server may provide a signature document to the device indicating permissions that authorize the vehicle to perform actions related to manipulation and driving of the vehicle, such as exceeding signed driving speed limits, using reserved lanes on a highway, or receiving advantageous traffic processing. The device may wirelessly transmit a message including the signature document to an additional device separate from the vehicle, where the additional device responds upon permission, such as making way for the vehicle. The signature document may include a digital signature and a digital certificate to authenticate the permission.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of Indian Application No. 202241039053, filed on July 7, 2022, entitled “SYSTEMS AND METHODS FOR ASSIGNING AND USING PRIVILEGES TO ASSIST MANEUVERING AND TRAVEL OF VEHICLES,” which application has been assigned to the assignee of this application, the entire contents of which are incorporated herein by reference. Background Art

[0002] A vehicle (e.g., a road, air, sea, or space vehicle) is typically used to move from one location to another and / or through a series of locations (e.g., along a predetermined land or sea route, flight path, or track). There may be obstacles and restrictions to such movement—for example, other vehicles and legal requirements regarding when and how such movement may occur. Summary of the invention

[0003] Embodiments described herein provide for obtaining and granting vehicle privileges using a digitally signed document plus one or more digital certificates (collectively, a "signed document"). The signed document can be sent to a receiving device including a vehicle or another device at the vehicle (e.g., a mobile phone), and can be wirelessly transmitted from the receiving device to other nearby devices to prompt nearby devices of the vehicle's privileges. Depending on the type of privilege being granted, nearby devices can respond accordingly. Requesting and granting privileges in this manner can allow a privilege-granting authority to provide privileges and grant corresponding signed documents in a relatively quick manner (e.g., on an as-needed or as-needed basis), which can be particularly useful in emergencies and other emergency situations.

[0004] According to the present disclosure, an example method for enabling permissions related to the operation of a vehicle at a device may include receiving a signed document indicating the grant of one or more permissions from a privilege granting authority server at the device, wherein the device includes the vehicle or an associated device, the associated device is associated with the vehicle, and the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle. The method may also include, after receiving the signed document, wirelessly transmitting a message including the signed document from the device to one or more additional devices separate from the vehicle, wherein the wireless transmission of the message is configured to invoke a response from the one or more additional devices based on the one or more permissions.

[0005] According to the present disclosure, an example method at a privilege granting authority server for enabling a device to obtain and use permissions related to the operation of a vehicle may include establishing a communication link between the privilege granting authority server and a device, the device including the vehicle or an associated device, the associated device being associated with the vehicle. The method may also include sending a signed document indicating the grant of one or more permissions from the privilege granting authority server to the device, wherein: the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle, and the signed document is configured to, when wirelessly transmitted from the device to one or more additional devices separate from the vehicle, invoke a response from the one or more additional devices based on the one or more permissions.

[0006] According to the present disclosure, an example device for enabling permissions related to the operation of a vehicle may include a transceiver, a memory, and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to receive a signed document indicating the grant of one or more permissions from a privilege granting authority server via the transceiver, wherein: the device includes the vehicle or an associated device, the associated device is associated with the vehicle, and the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle. The one or more processors may also be configured to, after receiving the signed document, wirelessly transmit a message including the signed document from the device to one or more additional devices separate from the vehicle, wherein the wireless transmission of the message is configured to invoke a response from the one or more additional devices based on the one or more permissions.

[0007] According to the present disclosure, an exemplary privilege granting authority server for enabling a device to obtain and use permissions related to the operation of a vehicle may include a transceiver, a memory, and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to establish a communication link between the privilege granting authority server and the device, the device including the vehicle or an associated device, the associated device being associated with the vehicle. The one or more processors may also be configured to send a signed document indicating the grant of one or more permissions to the device via the transceiver, wherein: the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle, and the signed document is configured to invoke a response from the one or more additional devices according to the one or more permissions when wirelessly transmitted from the device to one or more additional devices separate from the vehicle.

[0008] The present summary is neither intended to identify the key or essential features of the claimed subject matter nor is it intended to be used in isolation to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of the present disclosure, any or all of the drawings, and each claim. The foregoing and other features and examples will be described in more detail below in the following specification, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is an illustration depicting a top view of an example road traffic scene.

[0010] Figure 2 is a diagram depicting an example scenario associated with a general aircraft.

[0011] Figure 3 is an illustration of an overhead view of an example scenario depicting a marine vehicle navigating a waterway.

[0012] Figure 4 is a message flow diagram of a process for requesting and granting vehicle permission, according to an embodiment.

[0013] Figure 5 According to the embodiment Figure 4 A version of the flowchart in which all processes can be automatically performed by electronic devices.

[0014] Figure 6 Example data is shown that may be included in a signed document to establish permissions or privileges according to an embodiment.

[0015] Fig. 7A and 7B An example message structure is shown that may be used in some embodiments.

[0016] Figure 8 is a flow chart of a method at a device for enabling permissions related to maneuvering of a vehicle according to an embodiment.

[0017] Fig. 9 is a flow chart of a method at a privilege granting authority server for enabling a device to obtain and use permissions related to the operation of a vehicle according to an embodiment.

[0018] Fig.10 is a block diagram of an embodiment of a device that may be used as part of a vehicle (eg, an electrical system of a vehicle) or as an associated device as described herein (eg, a mobile device, mobile phone, etc.).

[0019] Fig.11 is a block diagram of an embodiment of a computer system.

[0020] According to certain example embodiments, like reference symbols in the various drawings refer to like elements. DETAILED DESCRIPTION

[0021] The following description is directed to certain implementations for the purpose of describing the innovative aspects of various embodiments. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described implementations can be implemented in any device, system, or network capable of sending and receiving radio frequency (RF) signals according to any communication standard, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standard for ultra-wideband (UWB), IEEE 802.11 standards (including those standards identified as Wi-Fi® technology), Bluetooth® standards, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), global system for mobile communications (GSM), GSM / general packet radio service (GPRS), enhanced data GSM environment (EDGE), terrestrial trunked radio (TETRA), wideband CDMA (W-CDMA), evolution data optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B. any of High Speed ​​Packet Data (HRPD), High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolved High Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone System (AMPS), or other known signals for wireless, cellular or Internet of Things (IoT) network communications, such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof. In addition, vehicle-related RF signals may be transmitted using relevant wireless communication technologies and / or standards related to vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), and / or vehicle-to-everything (V2X) communications or similar types of communications. As used herein, V2V, V2I, V2N, and V2P, as well as cellular-based variants (e.g., cellular V2X or CV2X) may be considered different types of V2X communications.

[0022] As used herein, an "RF signal" includes electromagnetic waves that transmit information through space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may send a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multiple channels or paths, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal.

[0023] Furthermore, as used herein, a "privilege" generally refers to a permission granted to a vehicle by an authorized authority that enables the vehicle to perform an action that it might not otherwise be authorized to perform. Thus, the terms "privilege" and "permission" may be used interchangeably. As described in greater detail herein, a digitally signed document plus one or more digital certificates (collectively referred to herein as a "signed document") may be provided to and transmitted by a vehicle as evidence of the privileges granted, which may evoke a response from a receiving device to help enable the vehicle to exercise those privileges.

[0024] As previously discussed, vehicles may be granted certain privileges or permissions to operate in certain ways during ordinary or special travel. These permissions may vary depending on factors such as the type of vehicle, the nature of the intended operation and / or travel, and the relevant privilege-granting authority (referred to herein as the "privilege-granting authority"), and may be permanent or temporary. Permissions may allow the vehicle to reach a destination more quickly, access certain areas or locations that it would not otherwise be able to access, etc. As discussed above, the type of vehicle may vary and may include road vehicles, air vehicles, sea vehicles, and / or space vehicles. Figure 1-4 Examples of different types of transportation and privileges are described.

[0025] Figure 1 is an illustration depicting an overhead view of an example traffic scenario 100 in which a vehicle 105 (in this example, a road vehicle such as a car or truck) may be granted one or more privileges that may affect how it maneuvers while traveling. For example, the vehicle 105 may need to reach its destination urgently but may face delays from obstacles such as traffic intersections, toll booths, speed limits, road works, lane closures or restrictions, traffic jams, etc. Privileges may be granted by a privilege granting authority (not shown) to enable the vehicle 105 to move faster in traffic and reduce or avoid delays from obstacles.

[0026] Road traffic scenes (such as Figure 1 Privileges in the transportation scenario 100) may be granted for any of a variety of reasons. For example, VIPs (e.g., diplomats and government officials), doctors, public servants, etc. may require fast and efficient road access to avoid delays and safeguard the public interest. The transportation of concrete to a construction site may be subject to time constraints to prevent the concrete from setting. The transportation of legal documents may be subject to delivery time constraints. Health and public safety workers may have travel time limits. Participants in important events may need assistance to arrive in time. Airport travelers may need to travel to the airport to catch an upcoming flight.

[0027] The privilege granting authority (also referred to herein as an "authorizing authority") may vary in different situations and environments. Typically, the privilege granting authority may correspond to an organization that controls infrastructure, such as a government, a local government of a town, a city or a state, or a private entity, such as a government or a local government that may have outsourced the management of vehicle-related privileges (such as road privileges) to the private entity. Then, the signed document may only apply to the corresponding control area of ​​the corresponding privilege granting authority. In some instances, the signed document may apply to multiple jurisdictions based on, for example, existing mutual agreements between the corresponding privilege granting authorities for those jurisdictions. Therefore, if a vehicle moves from an area managed by one authority to an area managed by another authority, it may request different privileges (or signed documents) from different authorities, or it may be possible to use signed documents provided by one authority in an area managed by other authorities. For example, if a vehicle moves from one state to another or across multiple states, the vehicle may need to request multiple signed documents (if these states are managed by different authorities), or it may be possible to use one signed document in all states (for example, if the signed document is provided by a national authority). It may be noted that the region or jurisdiction of an authority may not be strictly defined by clear boundaries, as it may be difficult to define exact boundaries. Therefore, there may be overlap between regions where two (or more) authorities may have administrative control, in which case a signed document from either (or any) of the authorities may be considered valid.

[0028] As described above and as used herein, the term "signed document" refers to a document that represents one or more privileges and / or priorities that are temporarily or permanently assigned to a vehicle, a device associated with the vehicle (e.g., a modem or "onboard system" for communications), or a device belonging to a user, operator, or passenger of the vehicle. For example, the document may explicitly list and name each of the one or more privileges and / or priorities, or the document may contain an encoding (e.g., a binary ASN.1 encoding) of each of the one or more privileges and / or priorities. The document may be a text document (e.g., encoded as unformatted text and possibly using Extensible Markup Language (XML)) or a binary document (e.g., encoded using Abstract Syntax Notation 1 (ASN.1)). The document may be signed using a digital signature, for example, the digital signature may be based on a public-private key pair, wherein the digital signature may include encryption using a private key of a hash of the document contents (based on a known or recognized hash algorithm). The recipient of the document may authenticate the document by verifying the digital signature. For example, for a digital signature based on the public key-private key pair just described, the recipient can use the public key to decrypt the digital signature and verify that the decryption result matches the hash of the document, which can be obtained by the recipient using the same known or recognized hash algorithm. In this example, the public key used by the recipient to verify the digital signature can be provided and authenticated by one or more digital certificates, such as digital certificates defined in accordance with ITU X.509 or IETF RFC 5280, which can be provided together with the document and the digital signature. A collection of documents, digital signatures, and one or more digital certificates (if included) indicating one or more privileges and / or priorities associated with a vehicle is referred to herein as a "signed document". A signed document may also be referred to as a certificate, a signature certificate, a privilege certificate, or some other name. It is well known in the art to use a digital signature (e.g., based on a public key-private key pair) to authenticate a document and to use a digital certificate to provide and authenticate a public key. It should be noted that the term "unsigned document" is used herein to refer to a document that represents one or more privileges and / or priorities associated with a vehicle but does not have a digital signature or one or more digital certificates.

[0029] Signed documents may be granted and used in different ways depending on the desired functionality. A vehicle that receives privileges via a signed document may include a permanent onboard user terminal (UE) with vehicle-to-everything (V2X) wireless communication capability. In this case, a signed document that enables privileges may be permanently or temporarily configured in the onboard UE. In addition, a separate UE associated with the vehicle, such as a driver's or passenger's mobile phone, may be used. In the latter case, the separate UE may act as a proxy UE for the vehicle. In either case, the UE (a permanent onboard UE or a separate UE associated with the vehicle) may receive the signed document and use V2X (e.g., using 4G / 5G sidelink signaling) to send (e.g., via unicast or broadcast) to other devices in the area to obtain various driving privileges, and this may apply for the duration defined in the signed document, or until a new signed document with the changed privileges is issued.

[0030] Depending on the scenario and privilege, transportation (e.g. Figure 1 The vehicle 105 in the vicinity can send the signed document to any of a variety of nearby vehicles and devices. For example, Figure 1 In the traffic scenario 100 of FIG. 1 , a vehicle 105 receiving a signed document granting various privileges may send the signed document to one or more nearby vehicles 110, 115, roadside units (RSUs) 120, and / or cellular base stations 125. In some instances, the receiving device may send the signed document to other devices. For example, a roadside unit 120 or cellular base station 125 may relay the signed document to a more distant vehicle 130, which may be out of range of direct RF communication with the privileged vehicle 105, but may still be affected by the privileges of the privileged vehicle 105. In some instances, traffic-related devices (such as traffic lights 140 and radars 150) may receive the signed document directly from the privileged vehicle 105, or may receive the signed document and / or another indication that the vehicle 105 has a specific privilege via another device (such as a roadside unit 120) that may manage traffic-related devices.

[0031] The type of permission granted may vary in different business scenarios. Privileges may include, for example, permission to exceed the posted speed limit by a certain limit without being stopped / ticketed, access to a scheduled or reserved parking space, permission to use a toll road and pass through a toll area without delay and / or without payment, access to a reserved driving lane (e.g., a high occupancy vehicle (HOV) lane 160 or some other high priority lane), making the traffic light at a traffic intersection (e.g., traffic light 140) turn green when arriving at the intersection (or just before arriving at the intersection), or allowing the use of detours and shortcuts (other vehicles are not available) to bypass traffic congestion, roadworks, lane closures and / or road closures, or a combination thereof. According to some embodiments, a signed document may have rules that allow all available privileges or a subset of available privileges. In addition, privileges may be limited to one or more specific routes, speed ranges, one or more specific areas, specific dates and / or times, and / or specific time periods after the expiration of the signed document. According to some embodiments, RSUs obtain the location and / or speed and direction of privileged vehicles, and manage traffic-related devices to help enable certain privileges (eg, instruct a traffic light to turn green when a privileged vehicle approaches).

[0032] The decision of the privilege granting authority to grant a privilege to a vehicle can be based on any of a number of factors. For example, some privileges may only be granted to certain types of vehicles. For example, emergency vehicles and / or vehicles escorting VIPs may be the only types of vehicles that obtain privileges, such as turning a traffic light green as they approach an intersection. Some privileges may be granted based on payment (e.g., payment to access HOV lanes, privileged routes, etc.). Other privileges may be based on need, such as health emergencies. Additional details about the process that can be used to request and grant privileges are provided below.

[0033] Depending on the privilege granted, the receiving device (the device that receives the signed document from the privileged vehicle) may respond in accordance with the privilege granted to implement or exercise the privilege. For example, in some embodiments, the privilege may include helping to overtake a non-privileged vehicle. In the traffic scenario 100, this may mean allowing the privileged vehicle 105 to exceed the existing speed limit and instructing the nearby (non-privileged) vehicle 115 to move to another lane. Instructions to the nearby vehicle 115 may be sent from the RSU 120 or from the privileged vehicle 105 itself (e.g., via a V2X message). If the nearby vehicle 115 is an automated (self-driving) vehicle, the nearby vehicle 115 may automatically change lanes. Otherwise, the instructions may reach the driver of the nearby vehicle 115 via voice or text message. If the receiving device does not recognize the privilege (e.g., due to an invalid signature document / mismatch or because the receiving device is not implemented or configured to recognize or support the privilege, etc.) or cannot enable the privileged vehicle to exercise the privilege, the receiving device may send a message to the privileged vehicle (e.g., via V2X) to indicate to the privileged vehicle that the receiving device will not take action to implement / exercise the privilege.

[0034] It may be noted that a signed document may not guarantee elevated privileges. That is, a privilege granted by a privilege granting authority may not necessarily result in a privileged vehicle receiving or exercising the privilege in all circumstances. Receiving a privilege may, for example, depend on the priority status of the privilege or privileged vehicle and the privileges of nearby vehicles. For example, in traffic scenario 100, if nearby vehicle 115 has privileges similar to privileged vehicle 105, privileged vehicle 105 may not be able to exercise the privilege of overtaking vehicle 115. Similarly, if vehicle 130 has the privilege of receiving a green light (e.g., green traffic light 140) at an intersection, privileged vehicle 105 having the same privilege may not be able to exercise the privilege if both approach the intersection at almost the same time. According to some embodiments, priority may be used to determine which vehicle receives the privilege when a conflict similar to this occurs.

[0035] Depending on the desired functionality, the priority may be associated with the status of the vehicle itself (e.g., a vehicle with a VIP status), the status of the owner of the user or UE associated with the vehicle, and / or the status of the privilege / permission (e.g., a privilege with an associated high priority status). According to some embodiments, the priority levels associated with the privileges and / or vehicle status may be explicitly defined in a signed document granted by the privilege granting authority. In addition, multiple priority levels may be established so that if a privilege of a lower priority vehicle would conflict with a privilege of a higher priority vehicle, the vehicle with the higher priority may override the privilege of the lower priority vehicle. Depending on the desired functionality, the priority associated with the privilege may be established on a per-privilege basis (e.g., each privilege a vehicle has may have its own priority), or may be established on a per-vehicle basis (e.g., all privileges of a vehicle or a UE associated with a vehicle may have the same priority). Typically, when there is a conflict in the implementation of privileges for two vehicles, privileges for a higher priority vehicle / privilege may be exercised at the expense of a lower priority vehicle / privilege, and privileges may be granted to a privileged vehicle of any priority (e.g., a vehicle with a signed document granting privileges) for a vehicle without privileges / priorities.

[0036] According to some embodiments, a receiving device receiving a signed document may use rules for determining how to respond to one or more privileges associated with a signed document. These rules may be defined based on privileges and any associated priorities, and implemented by a device receiving a signed document from a privileged vehicle (such as an RSU). For example, an RSU may implement privileges for a privileged vehicle (e.g., indicating that a traffic light turns green when a privileged vehicle approaches, indicating that a toll booth is exempt from tolls and / or lifting control arms, etc.), and may further prioritize implementation of higher priority privileges over lower priority privileges in the presence of a conflict. In addition to or as an alternative to priorities, an RSU (and other receiving devices) may decide to implement privileges based on other factors, such as the consequences of implementing / rejecting privileges, available resources for implementing privileges, historical data about vehicles and / or vehicle users, the time when the RSU receives a request for a privilege (e.g., a timestamp for receiving a signed document from a privileged vehicle), or a combination thereof.

[0037] In some embodiments, a user score (or user rating) or a vehicle score (or vehicle rating) associated with a vehicle driver / user may be established to facilitate the decision. For example, a database of user scores (or ratings) may be established based on a user's traffic violation record. The database may be accessible (e.g., via the Internet or via a dedicated signaling link) to certain devices (such as RSUs) that support vehicle privileges. In the case where such a device (e.g., RSU) may need to decide between implementing conflicting privileges for two vehicles with the same priority, the device may decide which vehicle it will implement the privilege for based on the user score (or rating) and / or other factors. In the case where priority and / or other factors result in a tie or otherwise fail to indicate which vehicle should receive the privilege, the vehicle may be randomly selected. According to some embodiments, a database may be maintained for situations where a vehicle is denied privileges (e.g., where another vehicle is given a higher priority), which may be used as a factor in a subsequent determination of whether to implement the privilege. Using this information, a device (e.g., RSU) can help ensure that a vehicle that is denied privileges in one instance may have a higher probability of exercising privileges in subsequent instances.

[0038] As described above, receiving devices such as RSUs and nearby vehicles can respond to enable the privileged vehicle to exercise one or more of its privileges. To further achieve this, in addition to sending the signed document, the privileged vehicle can communicate information (e.g., via V2X) using one or more messages that can also include the signed document, which can indicate the privileged vehicle's presence, speed, location, instructions / purpose, or a combination thereof. This can allow the receiving device to respond accordingly to grant the privilege. Figure 1 In the traffic scenario 100, for example, the privileged vehicle 105 can communicate its position and speed to the nearby vehicle 115, thereby enabling the nearby vehicle 115 (given its own position) to know how much time it must change lanes in order to allow the privileged vehicle 105 to travel unimpeded in the HOV lane 160.

[0039] As previously described, the privileged vehicle may transmit the signed document to one or more receiving devices by broadcast, groupcast / multicast or unicast. In the case of broadcast, the periodicity of the broadcast may be based on the speed of the vehicle and / or the density of the vehicle in the surrounding environment. For example, the higher the speed and / or the greater the density of the vehicle, the more frequently the privileged vehicle may send the signed document. According to some embodiments, the decision whether to broadcast, groupcast (also referred to as multicast) or unicast the signed document may depend at least in part on the type of privilege granted. For example, a privileged vehicle that has been granted the privilege of receiving a green traffic light when approaching an intersection may not affect the operation of other vehicles. Therefore, the privileged vehicle may unicast the signed document associated with the privilege to the RSU or directly unicast to a traffic light equipped with RSU capabilities, and does not adopt broadcast or multicast. However, if the privileged vehicle has other privileges associated with the signed document that may affect the operation of nearby vehicles, the privileged vehicle may also (or optionally) transmit the signed document to both nearby vehicles and RSUs by unicast, groupcast (or multicast) or broadcast.

[0040] Depending on the desired functionality, embodiments may limit the ability or frequency of a vehicle to request one or more privileges. In some embodiments, for example, a vehicle may be prevented from requesting a signed document granting one or more privileges unless it is necessary to do so to reach a certain destination (e.g., a destination associated with an important national or international level conference or event) or to reach a certain or any destination at a certain time (e.g., if the purpose of the trip satisfies certain priority conditions). Further, in some embodiments, a vehicle may send a request only when traffic is heavy (e.g., above a certain threshold) or only when there are a number of traffic lights (e.g., above a threshold number) that may delay the vehicle from reaching its destination.

[0041] In some embodiments, for example, one or more privileges may be granted to a vehicle in an emergency, thereby effectively enabling the vehicle to become or at least act as a temporary emergency vehicle. The privilege granting authority may determine that such privileges are provided to the vehicle under certain conditions, such as if no ambulance or other emergency vehicle is available to reach a vulnerable person (e.g., experiencing a medical emergency) within a threshold amount of time (e.g., which may vary depending on the type of medical emergency). In this case, the driver of a non-emergency vehicle may be able to transport the vulnerable person to a hospital, and therefore a privilege may be requested to enable the vehicle to become or act as a temporary emergency vehicle. For example, this may occur when a public safety answering point (PSAP) (e.g., an emergency service / 911 dispatcher) receives an emergency call from a driver or vulnerable person and determines that no ambulance is available to take the vulnerable person to an emergency room in time to effectively handle the medical emergency. In this example, the PSAP may act as a privilege granting authority and provide a signed document to a device associated with the driver (e.g., a driver's car or a UE associated with the driver / vulnerable person) via the Internet and / or a wireless network (e.g., a cellular, Bluetooth, and / or Wi-Fi network). To help prevent false positives / fraud, privileges associated with temporary emergency transportation may only grant privileges for a limited amount of time (e.g., approximately the maximum amount of time required to drive a vulnerable person to an emergency room) and within a certain area (e.g., defined by a geo-fence / geo-polygon and covering one or more routes from the vulnerable user's current location to the emergency room). In some embodiments, a device associated with the driver that receives the signed document (e.g., a vehicle or a UE associated with the vehicle) may prompt the driver if the vehicle is approaching the limits of the privilege. For example, the device may warn the driver if the time period associated with the privilege is about to expire and / or if the vehicle is approaching the geographic boundaries of the privilege.

[0042] As previously mentioned, some privileges can be granted based on the user's payment. In some embodiments, the amount of the monetary fee for the privilege can be based on factors such as the number of users (e.g., passengers) utilizing the use of a signed document, the nature of the privilege, the priority of the request in the signed document, the use time period, the use area, etc., and change. For example, the cost of receiving a driving privilege in a dense urban area (e.g., downtown New York City) during rush hour may be significantly higher than the cost of using the same privilege in a small town or during a low traffic period (e.g., at night or very early in the morning). The monetary charge can also depend on the authority. For example, for the same priority / condition, the charge of one authority can be higher than the charge of another authority. This can also depend on factors such as the tax requirements of the authority, the revenue required by the authority, etc.

[0043] According to some embodiments, the receiving device can verify the authenticity of the signed document or unsigned document by interacting in real time with a privilege granting authority that can be indicated in the signed document or unsigned document. For example, the receiving device can interact with a computer server maintained by the privilege granting authority. This interaction is referred to as "real-time document verification" here. For example, the receiving device can send a message to the privilege granting authority (or an associated server) and include a signed document or an unsigned document, or indicate one or more privileges required by the vehicle and the identification of the vehicle and / or the identification of the signed or unsigned document. The privilege granting authority (or an associated server) can then respond to the receiving device and indicate whether the privileges required by the signed or unsigned document or the vehicle are authentic. In this case, the unsigned document can only indicate a set of privileges (and priority), identity (e.g., name or number) of the unsigned document and / or the vehicle, and does not include additional information to authenticate the unsigned document, because the authentication can be performed in real time through the interaction between the receiving device and the privilege granting authority. To facilitate such interaction, the privileged vehicle may include the identity of the authority when transmitting the signed or unsigned document to the receiving device, or the signed or unsigned document may include the identity of the authority as part of the signed or unsigned document. To make such interactive verification secure, the receiving device may be configured with the identity (e.g., an Internet address) of a known and trusted privilege-granting authority, and verification may be performed only if the privilege-granting authority indicated in the signed or unsigned document, or indicated by the vehicle or device providing the signed or unsigned document, is one of the privilege-granting authorities configured in the receiving device.

[0044] According to some embodiments using real-time document verification, the privilege granting authority may maintain a log indicating when a signed or unsigned document is verified for a receiving device (e.g., an RSU) in order to obtain some privileges. In embodiments where a monetary fee is associated with the privilege, the log may be used to determine a corresponding fee (e.g., a fee that may be charged to a privileged vehicle user or owner at a later time).

[0045] In some embodiments, a privilege granting authority may limit the number of times a signed document may be used to prevent overuse and preserve the value of a privilege. For example, a privilege granting authority may have a predefined limit on the number of signed documents for certain privileges that it can or will provide. In some embodiments, the priority associated with different privileges may be adjusted if the limit is approached. For example, if the number of signed documents to be issued exceeds a predefined limit for a particular privilege, a number of lower priority privileges may be reduced, and / or a lower priority privilege may be revoked.

[0046] The type of user / vehicle that is granted privileges can vary depending on the desired functionality. For example, permanent users can include users who can be granted privileges permanently or for an extended period of time. These users can include, for example, VIPs, tourist vehicles, government / authority vehicles, transportation vehicles, and / or others. In some embodiments, other users who are granted privileges for an extended period of time (e.g., a year or more) can be considered "permanent" users in some respects, such as when determining the priority associated with the granted privileges. In some embodiments, permanent users with privileges granted permanently (or for a long time) can be granted temporary privileges with a higher priority where a higher priority may be desired.

[0047] Temporary users may include users who may be temporarily granted privileges within a more limited time period (e.g., a single trip, a day / week / month, etc.). The priority associated with temporary privileges may be based on need, depending on the purpose for which the privilege is sought. For example, a passenger who is late to catch a flight may contact an airline or airport to obtain road privileges (e.g., at a monetary cost) in order to arrive at the airport in a timely manner. In this example, the airline or airport may operate as a privilege granting authority and may be granted such authority by a government or local authority. If the airline / airport receives a privilege payment, the airline / airport may transfer part or all of the payment to the government or local authority. In another example, a university may issue road privileges to their students during an exam. In another example, a user (e.g., a driver) may pay an additional vehicle license or registration fee to obtain limited additional privileges and / or a specific type of vehicle and / or a vehicle owner may receive a set of automatic privileges. For example, motorcycles and electric vehicles may be automatically granted the privilege of accessing HOV lanes.

[0048] According to some embodiments, privileges and / or associated priorities can be updated, removed or abandoned after being granted to a vehicle, device or user. This can be done by the vehicle or device, for example, in the case of an update or abandonment, or by a server of a privilege granting authority. According to some embodiments, the server of the privilege granting authority can use information from, for example, an RSU, the first vehicle itself, or other vehicles to track the first vehicle to which the privilege is assigned. The server can also consider additional information, such as the number of higher priority and / or higher privilege vehicles that may delay the first vehicle on the designated route of the first vehicle and / or near the first vehicle. If the server determines that the first vehicle may fall behind a known set of travel times or targets, the server can upgrade privileges and / or priorities-for example, by providing an updated signed document to the first vehicle or a device associated with the first vehicle. The upgrade of privileges and / or priorities may bring additional costs to the user. The additional cost can be based on several factors, such as the degree of privilege and / or priority upgrade, multiple other vehicles with similar privileges and / or priorities, etc.

[0049] In accordance with some embodiments, granting privileges in the manner described herein may enable privileged vehicles to achieve faster travel speeds on expressways and highways. For example, in the case of an autonomous vehicle, vehicles with appropriate privileges (e.g., "highway" or priority lane access) may move into less crowded lanes, while vehicles without such privileges move outside of those lanes. In the case of a manually operated vehicle with driver prompting capabilities, the driver of a non-privileged vehicle may be warned to leave the lane or not enter the lane if the lane is occupied by one or more vehicles with privileges. On the other hand, for a manually operated vehicle, the driver of a vehicle with appropriate privileges may be given lane change assistance, such as being told which lane to move to on a highway and when to change lanes.

[0050] Although there have been reports on road or ground transport (e.g. Figure 1 The transportation scenario 100 of FIG. 100 describes many of the previously described aspects regarding the granting and use of privileges, but many of these aspects may be applied to non-road and / or non-ground vehicles and other applications. As noted, other applications may involve aircraft, marine vehicles, or space vehicles.

[0051] Figure 2 A scenario related to a general aircraft is shown, which is provided to discuss some aspects that may be unique to aircraft applications. Figure 2An unmanned aerial vehicle (UAV) 210 (e.g., a commercial or private drone) is shown, but aspects described herein with respect to the aircraft may be applied to other types of aircraft, including manned and unmanned aircraft (e.g., helicopters, airplanes, gliders, balloons, etc.).

[0052] Similar to how ground transportation vehicles can be granted privileges / permits related to travel / maneuvering to reduce travel delays (e.g., Figure 1 As described above, embodiments may be extended to aircraft. Specifically, an aircraft may be granted certain flight privileges / permits by a relevant privilege granting authority. In the case of an aircraft, the privilege granting authority may include a government, agency, local government, or other entity with jurisdiction over air travel. Privileges may be granted based on various factors such as priority, requirements, purpose of travel, aircraft type, and the like. For example, different types of aircraft may be given different types of privileges. These types may include, for example, military and government aircraft, commercial aircraft, private aircraft, aircraft related to agriculture, forestry, mining, or public safety, and the like.

[0053] In addition to the many types of privileges previously described with respect to road vehicles (e.g., relaxed speed limits, access to certain lanes / routes, etc.), there may be other privileges that may be unique to air travel. For example, different restrictions may apply to air travel over certain areas, and a privilege may make exceptions to some of these restrictions.

[0054] According to some embodiments, different types of regions may impose different standardized restrictions on air travel over those regions. In an example with eight region types, regions may be defined as:

[0055] Area 0: Airport, landing strip, runway;

[0056] Area 1: Military area / confidential area (Presidential Palace, National Defense Headquarters, etc.);

[0057] Area 2: School / Hospital;

[0058] Region 3: Dense urban areas;

[0059] Area 4: Residential area;

[0060] Area 5: large gathering areas such as parks and theme parks;

[0061] Region 6: Urban areas; and

[0062] Region 7: Others (e.g. rural areas).

[0063] Different restrictions may apply to different types of zones, with some types being more restrictive than others. In this example, zone types 0-3 may be more restrictive to air travel than zone types 4-7.

[0064] Additional factors may determine what types of zones (or more generally, what types of air travel restrictions) may apply. This may include, for example, whether the zone includes private land / public land in a rural, suburban, urban area. Private landowners may enforce minimum altitudes for aircraft to fly over privately owned land, subject to applicable landowner rights. Some restrictions, including such minimum altitude restrictions, may be lifted upon payment of applicable fees (e.g., access fees).

[0065] Return to Figure 2 For example, different area types include dense urban areas 220, hospital areas 230, and rural areas 240. Dense urban areas 220 may include tall buildings and other obstacles that may result in restrictions on any air travel, or at least restrict any area travel below a relatively high minimum altitude 250 (e.g., depending on the building height, such as 300-2000 feet). Hospital areas 230 may be less restrictive, imposing restrictions on air travel below a relatively low minimum altitude 260 (e.g., 100-200 feet). Rural areas 240, which may include unoccupied public or private land, may have even fewer restrictions, imposing restrictions (if any) on air travel below a relatively low minimum altitude 260. When an aircraft 210 passes through a boundary 270 from one area to another, different restrictions may apply, and (in some cases) privileges for air travel may be obtained from different privilege-granting authorities.

[0066] Different privileges may be applied to different areas. For example, in dense urban areas 220, privileges may be granted to fly below a relatively high minimum altitude 250 and even a relatively low minimum altitude 260. This may enable commercial delivery drones, for example, to deliver payloads to targets in dense urban areas 220, or helicopters to land and take off from rooftops of buildings. These privileges may be limited to a certain airspace directly above the target location. With respect to hospital areas 230, which may have air travel associated with medical helicopters arriving at and / or departing from hospitals, aircraft 210 may be granted the privilege to fly over hospital areas (e.g., above a relatively low minimum altitude 260) during time periods when no medical helicopter traffic is expected. With respect to rural areas 240, privileges to fly below a minimum altitude (e.g., a relatively low minimum altitude 260) may be granted at certain times based on payment of fees, etc.

[0067] According to some embodiments, the privilege granting authority may consider different aspects of an aircraft's travel, characteristics, and / or capabilities when determining whether to grant certain permissions to an aircraft. These aspects may include, for example, the weight of the aircraft and / or its payload, the range / distance the aircraft is intended to travel, the speed at which the aircraft will travel, the maximum time the aircraft can spend in the air based on fuel / battery levels and / or thermal capabilities, the maximum altitude the aircraft can travel, conditions that may affect the aircraft, and / or other (e.g., noise generated, durability, etc.), or combinations thereof. When requesting permission from the privilege granting authority, the aircraft may share this information with the privilege granting authority, as well as other details that the privilege granting authority may request (e.g., origin, destination, etc.).

[0068] The following is about Figures 4 to 9 General details of the process that embodiments may employ regarding requesting and granting privileges for vehicle travel (for any vehicle type) are described. However, with respect to an aircraft, an exemplary process may proceed as follows. First, a permission associated with air travel may be requested and obtained by the aircraft or an entity associated therewith (e.g., an aircraft controller). This may be performed prior to and / or during flight. The aircraft may interact with the controller (e.g., using direct and / or indirect wireless RF communications) to provide location and flight details and receive instructions (e.g., to continue or stay at / return to origin). In some embodiments, the controller may interact with a privilege granting authority. In some embodiments, the aircraft may interact directly with the privilege granting authority.

[0069] In some instances, permissions may be modified or revoked during flight, depending on different circumstances. The modification or revocation of permissions may be based on, for example, changes in requirements or dynamic changes in relevant regulations. For example, if an emergency occurs with one or more aircraft in an area, the privileges of certain other UAVs that have been assigned may be revoked by a privilege granting authority or an associated server, such as by sending an updated signed document from the server to each other UAV, or by sending an indication from the server to each other UAV that the assigned signed document has been revoked. If an aircraft has a sudden emergency mid-flight or falls behind on a flight schedule, it may request additional permissions and / or increased priority from a privilege granting authority, for example, in order to respond appropriately to the emergency (e.g., such as landing as quickly as possible) or catch up with the flight schedule.

[0070] As mentioned above, different permissions can be applied to the airspace above different types of areas. In addition, permissions can be received / rejected, revoked or modified before or during flight. The permissions that can be requested and granted can involve flying into certain areas (e.g., latitude / longitude permissions), flying at certain altitudes / above / below (altitude permissions), flying at certain speeds (speed or rate permissions), flying along certain routes, taking off and / or landing from certain locations, carrying (or not carrying) certain cargo, or a combination thereof. In addition, as noted, the granting of such permissions can be based in part on various characteristics related to the type of aircraft, its capabilities, its expected route of travel, aerospace restrictions, etc. For example, a permission based on speed or rate can be granted to allow the aircraft to reach its destination at a certain desired time. Permission to allow an aircraft to travel at a lower altitude and lower speed (e.g., along a route above an uncongested area) can be granted to an aircraft carrying a heavy payload. Permission to allow a relatively noisy aircraft to travel along a route above an uncongested area may be better than permission to travel near a school or hospital. That is, permission to travel in the airspace above a school or other area closed for the holiday can be granted during holidays. Other time-based permits may include requiring higher driving during night or daytime hours (depending on the area) to reduce disruptions.

[0071] As noted, the purpose of the travel may affect which permissions are granted. Aircraft operating in emergency situations (e.g., carrying critical medications, medical supplies, seriously injured persons, etc.) may be given high priority, permitted to operate at any speed at low altitudes. On the other hand, aircraft operating for non-emergency purposes may be given relatively low priority with higher minimum altitude restrictions. In cases where the purpose of the travel is less urgent, other restrictions on speed, altitude, etc. may apply.

[0072] Denial of clearance may also be based on any of a variety of factors. If the privilege granting authority determines that certain requested clearances will result in unsafe travel, then clearance may be denied. This may be based on, for example, aircraft capabilities, current weather conditions (wind, rain, fog, smoke, smog, etc.), current battery / fuel levels, etc. The presence of other air traffic may also play a role in denying clearances in situations where granting clearances may increase the likelihood of collisions between aircraft to unsafe levels.

[0073] Similar to the road traffic example described previously, priorities may come into play. For example, the purpose of travel and aircraft type may play a role in determining priority. Specifically, certain aircraft types (e.g., military and government aircraft) may be given priority over other aircraft types (e.g., private aircraft) when granting certain permissions. Additionally, certain permissions may have an associated priority, which may again be based on aircraft type, purpose, etc. As a result, aircraft with lower priorities may not be able to access the same areas / altitudes as higher priority aircraft, particularly in high traffic scenarios.

[0074] Figure 3 is an illustration depicting an overhead view of an example scenario in which a signed document may be used to grant permissions associated with waterborne (or marine) vehicles traveling in a waterway. Generally, privilege granting authorities (e.g., port authorities, coast guards, etc.) may establish and regulate the travel of waterborne vehicles (e.g., commercial, government, and / or recreational vessels and boats) in various waterways. Various lanes within a waterway may be established for different types of uses, including mixed-use lanes.

[0075] exist Figure 3 In the scenario depicted in FIG, a loaded cargo ship 310 traveling toward a dock 320 and / or an empty cargo ship 330 traveling away from the dock 320 can receive permission to travel to and from the dock 320. Specifically, the central channel 340 in the waterway in which the cargo ship is authorized to travel may not be wide enough to allow the loaded cargo ship 310 to travel past the empty cargo ship 330 and reach the dock 320. Therefore, the privilege granting authority can grant permission to allow the loaded cargo ship 310 and / or the empty cargo ship 330 to temporarily enter the docking channel 350 and / or the non-commercial channel 360, thereby allowing the ships to travel past each other. In order to grant permission in a safe manner, the privilege granting authority can track the location of all water vehicles in the area. This can include knowing the location of the non-cargo water vehicle vehicle 370, and may prompt the non-cargo water vehicle vehicle 370 to grant permission for the loaded cargo ship 310 and / or the empty cargo ship 330 to temporarily enter the non-commercial channel 360.

[0076] Some embodiments may be used in applications other than road vehicles, water vehicles, and aircraft. For example, a low earth orbit (LEO) satellite may be able to change its position or orbit (e.g., to avoid collision with other satellites or space boundary objects). Using the techniques provided herein, embodiments may enable requesting permission to change position and / or orbit or otherwise move by satellite and / or other spacecraft.

[0077] It may also be noted that in such applications, applicable RF communications related to the specific application may be utilized. As shown herein, V2X may be used for road traffic applications. Other RF communication technologies may be used for other applications related to aircraft, water vehicles, and / or space vehicles.

[0078] Figure 4 It is a message flow diagram for a process of requesting and granting vehicle privileges / permits that can be executed in any of a variety of applications, including applications for road vehicles, water (or sea) vehicles, aircraft, and spacecraft, as described herein. Optional operations are shown with dotted / dashed lines. In this example, a vehicle 405 (e.g., a road, water, air, or space vehicle) can communicate with a privilege granting authority 410 via one or more intermediate network devices 415. The network device 415 may include a radio tower, a base station, a server, a repeater, a public and / or private data (and voice) communication network (e.g., including a wide area network (WAN), the Internet, etc.) or a combination thereof. The type of network device 415, network, communication technology, etc. may vary depending on the application. As described above, V2X can be used in some applications, including applications for road vehicles. For example, in maritime and / or aerospace applications, additional wireless communication standards may be utilized. Vehicle 405 may correspond to a device that is part of the vehicle (e.g., a UE) or a device that is otherwise associated with the vehicle (e.g., a device belonging to or carried by an operator or passenger of the vehicle).

[0079] The process may begin with an optional function that detects a triggering event, as shown in block 420. Here, a triggering event may include an event that triggers the vehicle 405 to request a permission associated with the trip from the privilege granting authority 410. According to some embodiments, a triggering event may include a determination by the vehicle 405 that it may not be able to reach its destination at the desired time, or at all, without the necessary permission. This may occur before or during the trip, and may be based on monitoring current trip, traffic conditions, etc. Other triggering conditions may correspond to a change in the state of the vehicle (e.g., low fuel / battery, engine / motor failure, etc.), an emergency (e.g., an emergency of the vehicle or an occupant), a need to travel in a certain manner or along a certain route, or a combination thereof.

[0080] In response to the triggering event, the vehicle 405 may establish a data connection or session (e.g., a TCP / IP connection) with the privilege granting authority 410, as indicated by arrow 425. The establishment of the data connection may be governed by applicable protocols and standards. It may be noted that in some instances, the data connection may have been established between the vehicle 405 and the privilege granting authority 410 before the triggering event is detected at block 420. In such a case, the operation at arrow 425 may not be required.

[0081] In some embodiments, the vehicle 405 may also transmit vehicle characteristics and / or vehicle requirements, indicated by arrows 430 and 435, respectively. As previously discussed, an aircraft may indicate characteristics such as weight, fuel level, noise level, cargo type, etc., which the privilege granting authority 410 may consider when determining whether to grant certain permissions. The vehicle requirements may include certain requirements of the vehicle, such as delivering a payload, traveling along a certain route, or arriving at a destination on time. Again, the privilege granting authority 410 may take this into account when determining whether to grant permissions and which permissions to grant.

[0082] Although previously described with respect to an aircraft, there may be applications or embodiments involving other types of vehicles, where the vehicle 405 sends vehicle characteristics, requirements, and / or other information to the privilege granting authority 410 to determine whether to grant certain permissions. For example, this may be the case in the previously described example, where a private road vehicle may be granted certain permissions, thereby effectively becoming or acting as a temporary emergency vehicle to transport a vulnerable person experiencing a medical emergency to an emergency room. In this case, information about the type of emergency experienced by the vulnerable person may be provided, which may inform the vulnerable person of the urgency of needing to be transported to the emergency room. Some medical emergencies may be more urgent than other emergencies. Therefore, more urgent medical emergencies may receive permissions (e.g., regarding maximum speed, certain routes, etc.) to enable the vehicle 405 to reach the emergency room faster than less urgent medical emergencies.

[0083] The vehicle 405 may then send a request for the privilege to the privilege-granting authority 410, as indicated by arrow 440, which may then use the request (and any related information, such as vehicle characteristics / requirements) to determine whether to grant the privilege, as indicated by block 445. As previously described, some permissions may come at a monetary cost, in which case the privilege-granting authority 410 and vehicle 405 may engage in a financial transaction (not shown), in which the privilege-granting authority 410 may contact a financial institution, or may draw from a previously funded account associated with the vehicle 405.

[0084] According to some embodiments, operations 420-445 may be automatic, manual, or a combination thereof. That is, the detection of the triggering event at box 420, the subsequent communication between the vehicle 405 and the privilege granting authority 410, and the determination of the granting privilege at box 445 may be automatically performed by the vehicle 405 (e.g., a UE integrated into the vehicle or other UE co-located with the vehicle) and a computer server acting on behalf of the privilege granting authority 410, without manual input. However, optionally, some or all of these operations may be performed manually (e.g., with at least some human intervention). Returning to the example of a permission enabling an ordinary private vehicle to effectively become or act as a temporary emergency vehicle, a human user may detect a health emergency (triggering event) of a vulnerable person and call an emergency service dispatcher (privilege granting authority). The caller may also provide information to the emergency service dispatcher to enable the emergency service dispatcher to determine whether to grant permission, such as details about the emergency, the identity of the caller and / or the vulnerable person, details about the vehicle (license plate number / characteristics / requirements), etc. Someone at the emergency services dispatcher may decide to grant a vehicle permission to exceed speed limits, receive green traffic lights, etc., similar to emergency vehicles. (Again, this may be limited to a certain time period and specific route or a set of other routes)

[0085] As indicated by arrow 450, the privilege granting authority 410 may then create a signed document and transmit it (e.g., electronically) to the vehicle 405 (or a device located in the vehicle). Optionally, as indicated by arrow 455, the vehicle 405 may send a confirmation to the privilege granting authority. As described in more detail below, the signed document may appear in a variety of forms, which may vary depending on the type of vehicle, permissions, etc. In general, the form may include information such as the identification of the privilege granting authority 410, the identification of the vehicle 405, any time permissions granted, a description or identification of the permissions and privileges granted at box 445, the expiration time of the permissions and privileges, the priority of the permissions and privileges, and / or the priority of the vehicle 405, or any combination thereof. In some embodiments, information about the route of the vehicle 405 (e.g., a geographic polygon or a series of identified roads) may be included in the signed document.

[0086] Upon receiving the signed document, the vehicle 405 (e.g., optionally) may be configured based on the details and content of the signed document, as shown in block 460. This may include prompting for action (e.g., adjusting route, speed, etc.) and configuring a wireless communication interface to send the signed document to other vehicles / devices 465.

[0087] As shown in box 470, the vehicle 405 also transmits the signed document to other vehicles / devices 465. As previously described, the communication can be unicast, groupcast / multicast or broadcast, and can utilize appropriate RF technologies and associated protocols and standards, such as those supporting V2X, ProSe defined by the Third Generation Partnership Project (3GPP), sidelink RF signaling, etc., and associated protocols and standards. Then, the other vehicles / devices 465 can verify the signed document. For example, each of the other vehicles / devices 465 can use a public key provided and authenticated by one or more digital certificates included in the signed document to verify the digital signature included in the signed document. In addition, if an unsigned document is transmitted instead of a signed document at 450 and box 470, the other vehicles / devices 465 can each adopt real-time document verification, as previously described herein, to verify the unsigned document. Then, the other vehicles / devices 465 can respond accordingly (e.g., change lanes, flight paths, waterways or altitudes, adjust traffic lights, etc.) to enable the vehicle 405 to exercise one or more of its granted privileges.

[0088] Figure 5 yes Figure 4 , wherein all processes may be automatically performed (e.g., without human intervention) by electronic devices such as vehicle 505 (which may correspond to vehicle 405), privilege granting authority 510 (which may correspond to privilege granting authority 410), network device 515 (which may correspond to network device 415), and other vehicles / devices 520 (which may correspond to other vehicles / devices 465). Here, vehicle 505 may request privileges from privilege granting authority 510 using any of a variety of data channels, as shown in block 525. These may include wireless communications, email, text (SMS), session initiation protocol (SIP) calls, dedicated or proprietary channels for privilege requests, and the like. For example, an international delivery service utilizing drones may access privilege granting authority 510 for a specific delivery vehicle 505 using a dedicated communication interface, application programming interface (API) calls (e.g., when interfacing with a computer server of privilege granting authority 510), and the like.

[0089] It may be noted that in some embodiments, there may be a seamless transition between placing a voice call (e.g., from the vehicle 505) to the privilege-granting authority 510 to request a privilege and receiving a signed document indicating and evidencing the privilege from the privilege-granting authority 510 via another medium. In some embodiments, for example, a mobile phone associated with the vehicle 505 may be used to place a request for a privilege, and the privilege-granting authority 510 may then send the signed document to the mobile phone (e.g., via SMS, email, TCP / IP, an application, etc.). The signed document may then be sent to the other vehicle / device 520 using the mobile phone in the vehicle 505. Additionally, the mobile phone may transfer the signed document to the vehicle 505 (e.g., using an application) via a wired or wireless technology (such as Bluetooth, Wi-Fi, USB, etc.).

[0090] As with other examples provided herein, the vehicle 505 may determine the privilege granting authority 510 to which to send the privilege request based on the location and / or expected route of the vehicle 505 and the corresponding authority having jurisdiction over the location / expected route. In the event that the expected route is covered by multiple jurisdictions, the vehicle 505 may send multiple requests for privileges to multiple privilege granting authorities (e.g., the operations shown at block 525 may be repeated).

[0091] The decision to grant the privilege at block 530, the sending of the signed document indicating the privilege as indicated by arrow 535, and the transmission of the signed document to the other vehicle / device at block 540 may each be performed in a manner similar to Figure 4 In some embodiments, the data channel used to send the signed document at arrow 535 can be the same data channel used to request the privilege at box 525. For example, the signed document can be sent using the communication channel established when requesting the privilege. Again, this can include wireless communications, email, text (SMS), SIP, TCP / IP, dedicated or proprietary protocols and / or channels for privilege requests, etc.

[0092] Figure 6Example text data based on XML according to an embodiment is shown, which can be included as part of a signed document to indicate permissions or privileges assigned to a vehicle or to a device associated with the vehicle. Here, the text data includes the identity of the user associated with the vehicle (phone: 0629481198) and the time when the permission was assigned. The data also includes the expiration time and route (indicated by a sequence of latitude / longitude positions) applied to the permission. The permission includes an increased maximum driving speed (120 miles / hour) and an increased priority level (VIP). Of course, different instances can include different data (e.g., reflecting different permissions, different users, etc.), and different embodiments can use different forms / structures to transmit permission data.

[0093] Embodiments that enable a vehicle to effectively become a temporary emergency vehicle may use Figure 6 According to some embodiments, the license and signature documents may be embedded in a single data structure, which, when encoded based on ASN.1, is generally described as follows:

[0094] Emergency signature document sequence () {

[0095] Token string,

[0096] Duration time,

[0097] Destination name string,

[0098] Geological PolygonsGeological Polygons,

[0099] Signature digital signature,

[0100] Certificate Digital Certificate

[0101] }

[0102] Here, the token may include a text, octet, or binary string indicating a privilege provided by a privilege granting authority, the duration may indicate the validity period of the privilege, the destination name may indicate the destination of the vehicle, the geographic polygon may indicate the geographic area for which the privilege is valid, the signature may include a digital signature of the other parameters (e.g., a digital signature including a binary string or octet string of the token, duration, destination name, and geographic polygon), and the certificate may include one or more digital certificates providing and authenticating a public key used for signing.

[0103] According to some embodiments, the above data structure may be included in a message (such as an emergency vehicle alert (EVA) message) sent by a privilege granting authority to a vehicle that is granted permission to become a temporary emergency vehicle and then sent by the vehicle to other vehicles and other devices (such as RSU). EVA can be a wireless message defined in a relevant V2X standard, and an emergency vehicle can use V2X to send the wireless message to other vehicles and devices. Traditionally, private vehicles may not be provided for use as emergency vehicles. However, using the permission request and granting technology provided herein, a privilege granting authority such as an emergency service center (e.g., PSAP / emergency service dispatcher) can authorize non-emergency vehicles to send EVA (and / or equivalent) messages. Similarly, the permission can be associated with a specific time limit and / or a specific geographic polygon / a set of routes. With this permission, the vehicle can send EVA messages directly to other vehicles / devices via V2X, which can enable various privileges for the vehicle, as described herein.

[0104] According to some embodiments, a vehicle may send EVA messages to an intermediate device, which may relay these messages and / or control other devices. Figure 1 In the traffic scenario 100 of FIG. 1 , for example, the privileged vehicle 105 may send an EVA message via the Uu wireless interface to the base station 125. The base station 125 may then wirelessly relay the EVA message to one or more other devices within its coverage area and / or one or more remote devices (e.g., via the Internet).

[0105] Embodiments that enable a vehicle to effectively become a temporary emergency vehicle can modify the EVA message structure to implement this functionality. For example, the EVA message structure can be defined by a standard (eg, SAE J2735), and the standard can be modified to implement the embodiments described herein.

[0106] Fig. 7A An example ASN.1-based EVA message structure that can be used in such an embodiment is shown. Structure 700 shows the content of the modified EVA message. In addition to the data included in the traditional EVA message (e.g., timestamp, ID, details, etc.), the modified EVA message may also include a "basicType" parameter indicating the type of vehicle, as well as a signature parameter and a certificate parameter, as described above. According to an embodiment, when a private vehicle becomes a temporary emergency vehicle, the vehicle type can be set to "private" or a similar type. For emergency vehicles, the vehicle type (if included) can be set to "emergency", "ambulance", "police", etc.

[0107] Figure 7Bshows the ASN.1 Fig. 7A Here, in addition to the parameters previously used (siren usage, lights usage, etc.), the emergency event details may also include vehicle details and route map parameters. These parameters may respectively provide information about a privileged vehicle, and a route map associated with a route or set of routes along which the privileged vehicle may need to travel. Likewise, a route map may be defined using geographic polygons. The vehicle details parameter may include identification information for the vehicle, including a vehicle identification number (VIN) or other ID and / or other identifying characteristics (e.g., whether it is a passenger car / truck / van, color, make, model, etc.).

[0108] Figure 8 8 is a flow chart of a method 800 for enabling permissions associated with the operation of a vehicle at a device according to an embodiment. As described in more detail below, the device may include a vehicle or a device associated with a vehicle, such as a mobile phone of a vehicle passenger or operator or a device attached to the vehicle (e.g., a modem or vehicle system). Figure 8 The operations shown in the figure may correspond to one or more operations performed by the vehicle or associated equipment in the previously described embodiments. Figure 8 The units of functionality shown in one or more blocks shown in the figure may be performed by hardware and / or software components of an electronic device, which may be a stand-alone device or integrated into a larger system or vehicle. Example components of such a device are shown in Fig.10 This is shown in FIG. , which will be described in more detail below.

[0109] The functionality of box 810 includes receiving, at a device, a signed document indicating the grant of one or more permissions from a privilege granting authority server, wherein the device includes a vehicle or an associated device, the associated device is associated with the vehicle, and wherein the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle. As previously described, the vehicle may include a road vehicle, an air vehicle, a sea vehicle, or a space vehicle. As indicated in the previously described embodiments, the privilege granting authority server may be maintained by a privilege granting authority and may be capable of transmitting the signed document to the vehicle and / or other devices (e.g., via one or more network devices). The privilege granting authority may include a government, agency, or other entity having jurisdiction over the operation of the vehicle on at least a portion of a route that has been, is, or will be traveled.

[0110] The device itself may include the vehicle or a subsystem thereof (e.g., a UE incorporated into the vehicle), or a device associated therewith. As indicated in the previously described embodiments, the associated device may include a mobile phone or other device of a passenger or operator of the vehicle. More generally, the associated device may include a mobile device that is co-located with the vehicle (e.g., in or on the vehicle). According to some embodiments, the associated device may become associated with the vehicle based on information obtained from an authority that grants privileges to associate the device with the vehicle. This information may be included in a request for one or more permissions or provided separately, and may identify the vehicle (e.g., using a VIN and / or other identifier), the passenger / operator, and / or the associated device (e.g., using a unique ID, such as a phone number, device ID / serial number, MAC address, etc.).

[0111] The apparatus for performing the functions at block 810 may include a bus 1005, a processor 1010, a DSP 1020, a wireless communication interface 1030, a sensor 1040, a memory 1060, and / or other components of the UE device 1000, such as Fig.10 shown and described below.

[0112] The functionality of box 820 includes, after receiving the signed document, wirelessly transmitting a message including the signed document from the device to one or more additional devices separate from the vehicle, wherein the wireless transmission of the message is configured to invoke a response from the one or more additional devices based on one or more permissions. Here, the one or more additional devices may include a receiving device and / or a vehicle that may be able to respond in a manner that allows the vehicle to exercise the granted permissions. As noted in the previously described embodiments, the receiving vehicle may move out of the path of the privileged vehicle to enable the privileged vehicle to pass faster along the route, access a specific stop or parking space, etc. The receiving device may include RSUs and / or other infrastructure equipment that may be able to change traffic lights, move toll booth arms, move or direct traffic, and / or otherwise change conditions so that the privileged vehicle can exercise its permissions.

[0113] The apparatus for performing the functions at block 820 may include bus 1005, processor 1010, DSP 1020, wireless communication interface 1030, sensor 1040, memory 1060, and / or other components of apparatus 1000, such as Fig.10 shown and described below.

[0114] Depending on the desired functionality, embodiments of method 800 may include one or more additional features. For example, as previously described, a signed document may include one or more permitted indications and a digital signature. The digital signature may be based on a public key-private key pair, wherein the signed document also includes one or more digital certificates, and wherein the one or more digital certificates indicate and authenticate the public key.

[0115] According to some embodiments, method 800 may also include determining a triggering event for requesting one or more permissions, and sending a request for the one or more permissions from the device to a privilege granting authority server, wherein receiving a signed document is responsive to the request. As noted in the above embodiments, the type of triggering event may vary depending on the application. For example, the triggering event may include the presence of an emergency; user input indicating a desire to obtain the one or more permissions; the need to obtain the one or more permissions to travel along a certain route to a certain destination or at a certain time; the need to obtain the one or more permissions to travel in a certain manner; or a combination thereof.

[0116] like Figure 4 As described, the vehicle or device may send information to the privilege granting authority so that the privilege granting authority can determine whether to grant permission. Therefore, some embodiments of method 800 may also include sending vehicle information from the device to the privilege granting authority server before receiving the signed document. In such an embodiment, the vehicle information may indicate one or more characteristics of the operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for manipulating the vehicle, or a combination thereof. The purpose of the trip and / or the state of the operator / passenger may affect the determination of whether to grant the signed document. Therefore, one or more characteristics of the operator or passenger of the vehicle may include VIP status, serving as a doctor, government official, military official or public safety official, having a medical condition and / or using the vehicle to perform important or emergency actions. In addition, one or more characteristics of the vehicle may include the weight of the vehicle (vehicle), the size of the vehicle, the type of vehicle, the brand of the vehicle, the model of the vehicle, the cargo of the vehicle, the maximum mileage of the vehicle, the maximum speed of the vehicle, the maximum height of the vehicle, or the measurement of the noise of the vehicle, or a combination thereof.

[0117] Here, the maneuvering of a vehicle may involve any type of action or movement that a vehicle may take during the course of travel. Thus, according to some embodiments of method 800, one or more actions associated with the maneuvering of a vehicle may include accessing a shipping channel, flight area, road, or lane; accessing a priority travel route; using a parking space, landing location, dock location, or earth orbit; transporting a certain item or item type; moving to an alternate earth orbit; traveling at a certain speed or speed range; traveling at a certain altitude or altitude range; performing one or more maneuvers; or a combination thereof.

[0118] Method 800 may include additional or alternative features described elsewhere herein. For example, one or more permissions may be temporary. The signed document may also indicate a priority level for one or more permissions. As the vehicle travels along a route, the device may wirelessly transmit a message to one or more additional devices separate from the vehicle, wherein the selection of the route, the manner in which the vehicle travels along the route, or both are responsive to responses from the one or more additional devices. According to some embodiments, the method may also include receiving an updated signed document from a privilege granting authority server, wirelessly transmitting the updated signed document from the device to another additional device separate from the vehicle, and in response to receiving the updated signed document or in response to a response from another additional vehicle: adjusting the route, adjusting the manner in which the vehicle travels along the route, or both.

[0119] The message may include one or more V2X messages, one or more near field communication service (ProSe) messages, one or more side link messages, or some combination of these. Depending on the desired functionality, the message or the signed document (or both) may also include information indicating the destination of the vehicle, the duration of one or more permits, the route of the vehicle, or a combination thereof. Wirelessly transmitting the message may include broadcasting the message, multicasting the message (e.g., to multiple receiving devices), or sending the message to a specific receiving device via unicast. Sending the message may include sending the message using ProSe or side link communication. According to some embodiments, method 800 may also include: after sending the message, receiving one or more confirmations of received messages from one or more additional devices.

[0120] Fig. 9 is a flow chart of a method 900 at a privilege granting authority server for enabling a device to obtain and use permissions related to operation of a vehicle according to an embodiment. Likewise, the device may include a vehicle or a device associated with a vehicle. Fig. 9 The operations shown in can correspond to one or more operations performed by a privilege granting authority server, as described in the embodiments provided herein. Fig. 9The functions shown in one or more blocks shown in the figure may be performed by hardware and / or software components of a computer system. Example components of such a computer system are shown in Fig.11 , and will be described in more detail below.

[0121] The functionality of block 910 includes establishing a communication link between a privilege granting authority server and a device, the device including a vehicle or an associated device, the associated device being associated with the vehicle. Likewise, depending on the application, the vehicle may include a road vehicle, an air vehicle, a sea vehicle, or a space vehicle. The application may further affect the communication technology used to establish the communication link. As previously described, different types of communication links may be governed by different types of standards / protocols. The devices used to perform the functionality at block 910 may include a bus 1105, a processor 1110, a DSP input device 1115, a communication subsystem 1130, a memory 1135, and / or other components of the computer system 1100, such as Fig.11 shown and described below.

[0122] The functionality of block 920 includes sending a signed document from the privilege granting authority server to the device indicating a grant of one or more permissions, wherein the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle, and the signed document is configured to, when wirelessly transmitted from the device to one or more additional devices separate from the vehicle, invoke a response from the one or more additional devices in accordance with the one or more permissions. As described above, the response may enable the vehicle to exercise its permissions.

[0123] In some embodiments, the privilege-granting authority server may include an indication of one or more permissions and a digital signature in the signed document. The digital signature may be based on a public-private key pair, and the privilege-granting authority server may include one or more digital certificates in the signed document, wherein the one or more digital certificates indicate and authenticate the public key.

[0124] As described herein, the determination of whether to grant one or more permissions may be based on any of a variety of factors. Thus, according to some embodiments, method 900 may also include: determining, before sending the signed document, whether to grant one or more permissions (e.g., Figure 4 and Figure 5As described above). Wherein, determining to grant the one or more permissions is based at least in part on weather conditions, an emergency condition associated with the vehicle, a destination of the vehicle, a time period during which the vehicle will be traveling with the one or more permissions, one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, or one or more requirements of the vehicle, or a combination thereof. In such an embodiment, method 900 may also include determining a priority level for the one or more permissions; and including the priority level in the signed document. In addition, method 900 may include receiving a request for one or more permissions at a privilege granting authority server, wherein determining to grant the one or more permissions may be responsive to receiving the request for one or more permissions. In addition, method 900 may include receiving vehicle information of the vehicle at the privilege granting authority server, wherein determining to grant the one or more permissions is based at least in part on the vehicle information, and wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof. For example, the one or more characteristics of the operator or passenger of the vehicle may include: VIP status; serving as a doctor, government official, military official, or public safety official; having a health condition; or using the vehicle to perform an important or emergency action. For example, one or more characteristics of a vehicle may include: the weight of the vehicle; the size of the vehicle; the type of vehicle; the brand of the vehicle; the model of the vehicle; the cargo of the vehicle; the maximum range of the vehicle; the maximum speed of the vehicle; the maximum height of the vehicle; a measure of noise of the vehicle; or a combination thereof.

[0125] Means for performing the functions at block 920 may include bus 1105, processor 1110, DSP input device 1115, communication subsystem 1130, memory 1135, and / or other components of computer system 1100, such as Fig.11 shown and described below.

[0126] Depending on the desired functionality, embodiments may also employ one or more additional features. For example, according to some embodiments, one or more actions associated with the operation of a vehicle may include accessing a shipping channel, flight area, road, or lane; accessing a priority travel route; using a parking space, landing location, or dock location or earth orbit; transporting a certain item or item type; moving to an alternative earth orbit; traveling at a certain speed or speed range; traveling at a certain altitude or altitude range; performing one or more operations; or a combination thereof. Some embodiments of method 900 may also include: after sending the signed document, determining to revoke one or more permissions, and sending a message from the privilege granting authority server to the device indicating the revocation of one or more permissions. Here, determining to revoke one or more permissions may be based at least in part on a determination that the vehicle has arrived at a designated destination, a determination that the vehicle has left the designated travel route of the vehicle, an emergency condition affecting the designated travel route of the vehicle, a traffic condition affecting the designated travel route of the vehicle, or a combination thereof.

[0127] Fig.10 is a block diagram of an embodiment of a device 1000 that can be used as part of a vehicle (e.g., an electrical system of a vehicle) or as described herein (e.g., with Figure 1-9 For example, the device 1000 may execute Figure 8 One or more functions of the method shown in and / or more generally functions of the device, vehicle and / or UE as described herein. It should be noted that Fig.10 It is intended only to provide a generalized description of the various components, any or all of which may be utilized as appropriate. It may be noted that in some instances, Fig.10 The components shown may be located in a single physical device and / or distributed among various networked devices, which may be located at different physical locations. In addition, as previously mentioned, the functions of the devices and vehicles discussed in the previously described embodiments may be provided by Fig.10 One or more of the hardware and / or software components shown in FIG.

[0128] Device 1000 is shown as including hardware elements that may be electrically coupled via bus 1005 (or may communicate in other ways as appropriate). The hardware elements may include a processor 1010, which may include, but is not limited to, one or more general-purpose processors (e.g., application processors), one or more special-purpose processors (e.g., digital signal processor (DSP) chips, graphics acceleration processors, application-specific integrated circuits (ASICs), and / or the like), and / or other processing structures or devices. Processor 1010 may include one or more processing units, which may be housed in a single integrated circuit (IC) or multiple ICs. Fig.10 As shown, some embodiments may have a separate DSP 1020, depending on the desired functionality. Position determination and / or other determinations based on wireless communications may be provided in the processor 1010 and / or the wireless communication interface 1030 (described below). The device 1000 may also include one or more input devices 1070, which may include but are not limited to one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, and / or the like; and one or more output devices 1015, which may include but are not limited to one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, and / or the like.

[0129] The device 1000 may also include a wireless communication interface 1030, which may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication device and / or a chipset (e.g., a Bluetooth® device, an IEEE 802.11 device, an IEEE 802.15.4 device, a Wi-Fi device, a WiMAX device, a WAN device, and / or various cellular devices, etc.), etc., which may enable the device 1000 to communicate with other devices described in the above embodiments. The wireless communication interface 1030 may permit the transmission (e.g., transmission and reception) of data and signaling with a wireless node of a network via, for example, an eNB, a gNB, an ng-eNB, an access point, various base stations and / or other access node types and / or other network components, a computer system and / or any other electronic device communicatively coupled to the wireless node, as described herein. Communication may be performed via one or more wireless communication antennas 1032 that send and / or receive wireless signals 1034. According to some embodiments, the wireless communication antenna 1032 may include multiple discrete antennas, an antenna array, or any combination thereof. The antenna 1032 may be capable of using beams (eg, Tx beams and Rx beams) to send and receive wireless signals. Beamforming may be performed using digital and / or analog beamforming techniques and corresponding digital and / or analog circuits. The wireless communication interface 1030 may include such circuits.

[0130] Depending on the desired functionality, the wireless communication interface 1030 may include a separate receiver and transmitter, or any combination of transceivers, transmitters, and / or receivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers (e.g., wireless devices and access points). The device 1000 may communicate with different data networks, which may include various network types. For example, a WWAN may be a CDMA network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, a WiMAX (IEEE 802.16) network, and the like. A CDMA network may implement one or more RATs, such as CDMA2000®, WCDMA, and the like. CDMA2000® includes IS-95, IS-2000, and / or IS-856 standards. A TDMA network may implement GSM, a digital advanced mobile phone system (D-AMPS), or other RATs. An OFDMA network may employ LTE, LTE Advanced, 5G NR, and the like. 5G NR, LTE, Advanced LTE, GSM, and WCDMA are described in documents from 3GPP. CDMA2000® is described in documents from an alliance named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE 802.11x network, and a wireless personal area network (WPAN) may be a Bluetooth network, IEEE 802.15x, or other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN, and / or WPAN.

[0131] Device 1000 may also include sensor 1040. Sensor 1040 may include, but is not limited to, one or more inertial sensors and / or other sensors (e.g., accelerometers, gyroscopes, cameras, magnetometers, altimeters, microphones, proximity sensors, light sensors, barometers, etc.), some of which may be used to obtain location-related measurements and / or other information.

[0132] Embodiments of the device 1000 may also include a global navigation satellite system (GNSS) receiver 1080 that is capable of receiving signals 1084 from one or more GNSS satellites using an antenna 1082 (which may be the same as the antenna 1032). Positioning based on GNSS signal measurements may be used to supplement and / or incorporate the techniques described herein. The GNSS receiver 1080 may use conventional techniques to extract the location of the device 1000 from GNSS satellites of a GNSS system, such as the Global Positioning System (GPS), Galileo, GLONASS, the Quasi-Zenith Satellite System (QZSS) over Japan, the IRNSS over India, the BeiDou Navigation Satellite System (BDS) over China, and the like. In addition, the GNSS receiver 1080 may be used with various augmentation systems, such as a Satellite Based Augmentation System (SBAS), which may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multipurpose Satellite-Based Augmentation System (MSAS), and / or the Geographic Augmentation Navigation System (GAGAN), and / or the like.

[0133] It can be noted that although the GNSS receiver 1080 Fig.10 As used herein, the term "GNSS receiver" may include hardware and / or software components configured to obtain GNSS measurements (measurements from GNSS satellites). Thus, in some embodiments, the GNSS receiver may include a measurement engine executed (as software) by one or more processors (e.g., processor 1010, DSP 1020, and / or a processor in wireless communication interface 1030 (e.g., in a modem). The GNSS receiver may also optionally include a positioning engine that may use the GNSS measurements from the measurement engine to determine the position of the GNSS receiver using an extended Kalman filter (EKF), weighted least squares (WLS), a hatch filter, a particle filter, etc. The positioning engine may also be executed by one or more processors (e.g., processor 1010 or DSP 1020).

[0134] The device 1000 may also include and / or be in communication with a memory 1060. The memory 1060 may include, but is not limited to, local and / or network accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices, such as random access memory (RAM) and / or read-only memory (ROM), which may be programmable, flash-updatable, and / or the like. Such storage devices may be configured to implement any suitable data storage, including, but not limited to, various file systems, database structures, and / or the like.

[0135] The memory 1060 of the device 1000 may also include software elements ( Fig.10 1000), including an operating system, a device driver, an executable library, and / or other code, such as one or more applications, which may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more programs described with respect to the methods discussed above may be implemented as code and / or instructions in memory 1060 that may be executed by device 1000 (and / or processor 1010 or DSP 1020 within device 1000). Then, in some embodiments, such code and / or instructions may be used to configure and / or adapt a general purpose computer (or other device) to perform one or more operations according to the described methods.

[0136] Fig.11 is a block diagram of an embodiment of a computer system 1100 that may be used, in whole or in part, to provide the functionality of one or more network components (eg, servers) as described in the embodiments herein. For example, the computer system 1100 may execute Fig. 9 One or more functions of the method shown and / or the more general functions of the privilege granting authority server as described herein. It should be noted that Fig.11 It is intended only to provide a generalized description of the various components, any or all of which may be utilized as appropriate. Fig.11 It is broadly shown how the various system elements can be implemented in a relatively independent or relatively more integrated manner. In addition, it can be noted that Fig.11 The components shown may be localized to a single device and / or distributed among various networked devices that may be located at different geographical locations.

[0137] The computer system 1100 is shown to include hardware elements that may be electrically coupled via a bus 1105 (or may otherwise communicate as appropriate). The hardware elements may include a processor 1110, which may include, but is not limited to, one or more general-purpose processors, one or more special-purpose processors (e.g., digital signal processing chips, graphics acceleration processors, and / or the like), and / or other processing structures that may be configured to perform one or more of the methods described herein. The computer system 1100 may also include one or more input devices 1115, which may include, but is not limited to, a mouse, a keyboard, a camera, a microphone, and / or the like; and one or more output devices 1120, which may include, but is not limited to, a display device, a printer, and / or the like.

[0138] The computer system 1100 may further include (and / or communicate with) one or more non-transitory storage devices 1125, which may include, but are not limited to, local and / or network accessible storage devices, and / or may include, but are not limited to, disk drives, drive arrays, optical storage devices, solid-state storage devices, such as RAM and / or ROM, which may be programmable, flash-updatable, and / or the like. Such storage devices may be configured to implement any suitable data storage, including, but not limited to, various file systems, database structures, and / or the like. Such data storage may include databases and / or other data structures for storing and managing messages and / or other information to be sent to one or more devices via a hub, as described herein.

[0139] The computer system 1100 may also include a communication subsystem 1130, which may include wireless communication technologies and wired technologies (such as Ethernet, coaxial communication, universal serial bus (USB), etc.) managed and controlled by a wireless communication interface 1133. The wireless communication interface 1133 may include one or more wireless transceivers, which may send and receive wireless signals 1155 (e.g., signals according to 5G NR or LTE) via a wireless antenna 1150. Therefore, the communication subsystem 1130 may include a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device and / or a chipset and / or the like, which may enable the computer system 1100 to communicate with any device (including a user terminal (UE), a base station and / or other TRP and / or any other electronic device described herein) on any or all of the communication networks described herein. Therefore, the communication subsystem 1130 can be used to receive and send data, as described in the embodiments of this document.

[0140] In many embodiments, the computer system 1100 will further include a working memory 1135, which may include a RAM or ROM device, as described above. The software elements shown as being located within the working memory 1135 may include an operating system 1140, device drivers, executable libraries, and / or other code, such as one or more applications 1145, which may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more programs described with respect to the methods discussed above may be implemented as code and / or instructions executable by a computer (and / or a processor within a computer); then, in one aspect, such code and / or instructions may be used to configure and / or adjust a general purpose computer (or other device) to perform one or more operations according to the described methods.

[0141] The set of these instructions and / or codes may be stored on a non-transitory computer-readable storage medium (such as the storage device 1125 described above). In some cases, the storage medium may be incorporated into a computer system (e.g., computer system 1100). In other embodiments, the storage medium may be independent of the computer system (e.g., removable media such as a compact disc), and / or provided in an installation package so that the storage medium can be used to program, configure, and / or adjust a general-purpose computer having the instructions / code stored thereon. These instructions may take the form of executable code that can be executed by the computer system 1100 and / or may take the form of source and / or installable code that, after being compiled and / or installed on the computer system 1100 (e.g., using any of a variety of commonly available compilers, installers, compression / decompression utilities, etc.), then takes the form of executable code.

[0142] It will be apparent to those skilled in the art that substantial variations may be made depending on specific requirements. For example, custom hardware may also be used, and / or specific elements may be implemented in hardware, software (including portable software, such as applets, etc.), or both. In addition, connections to other computer systems such as network input / output devices may be employed.

[0143] With reference to the accompanying drawings, the components that may include memory may include non-temporary machine-readable media. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any storage medium that participates in providing data that enables a machine to operate in a particular manner. In the embodiments provided above, various machine-readable media may involve providing instructions / codes to a processor and / or other devices for execution. In addition, machine-readable media may be used to store and / or carry such instructions / codes. In many embodiments, computer-readable media are physical and / or tangible storage media. Such media may take many forms, including but not limited to non-volatile media and volatile media. Common forms of computer-readable media include, for example, magnetic and / or optical media, any other physical media with hole patterns, RAM, programmable ROM (PROM), erasable PROM (EPROM), flash-EPROM, any other memory chip or box, or any other medium from which a computer can read instructions and / or codes.

[0144] The methods, systems and devices discussed herein are examples. Various embodiments may appropriately omit, replace or add various processes or components. For example, features described with respect to certain embodiments may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. The various components of the accompanying drawings provided herein may be embodied in hardware and / or software. In addition, technology is constantly iterating, so many elements are examples that do not limit the scope of the present disclosure to those specific examples.

[0145] It has proven convenient at times, primarily for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, numerals, and the like. It will be understood, however, that all of these or similar terms are associated with the appropriate physical quantities and are merely convenient labels. Unless otherwise specifically stated, as will be apparent from the above discussion, it will be understood that throughout this specification, discussions utilizing terms such as "processing," "computing," "calculating," "determining," "ascertaining," "identifying," "correlating," "measuring," "performing," and the like refer to the actions or processes of a specific apparatus, such as a special purpose computer or similar special purpose electronic computing device. Thus, in the context of this specification, a special purpose computer or similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as electronic, electrical, or magnetic physical quantities within a memory, register, or other information storage device, transmission device, or display device of the special purpose computer or similar special purpose electronic computing device.

[0146] The terms "and" and "or" as used herein may include multiple meanings, which are also expected to depend at least in part on the context in which the terms are used. Generally, "or", if used in an associative list, such as A, B, or C, is intended to mean A, B, and C (used in an inclusive sense here), as well as A, B, or C (used in an exclusive sense here). In addition, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe a certain combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example and the claimed subject matter is not limited to this example. In addition, if used in an associative list (such as A, B, or C), the term "at least one" may be interpreted to mean any combination of A, B, and / or C, such as A, AB, AA, AAB, AABBCCC, etc.

[0147] Several embodiments have been described, and various modifications, alternative configurations, and equivalents may be used without departing from the scope of the present disclosure. For example, the above elements may be merely components of a larger system, where other rules may take precedence over or otherwise modify the application of the various embodiments. In addition, multiple steps may be performed before, during, or after considering the above elements. Therefore, the above description does not limit the scope of the present disclosure.

[0148] In view of this description, embodiments may include different combinations of features. Implementation examples are described in the following numbered clauses:

[0149] Clause 1. A method for enabling permissions related to the operation of a vehicle at a device, the method comprising: receiving at the device a signed document indicating the grant of one or more permissions from a privilege granting authority server, wherein: the device includes the vehicle or an associated device, the associated device is associated with the vehicle, and the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle; and after receiving the signed document, wirelessly transmitting a message including the signed document from the device to one or more additional devices separate from the vehicle, wherein the wireless transmission of the message is configured to invoke a response from the one or more additional devices based on the one or more permissions.

[0150] Clause 2. The method of clause 1, wherein the signed document comprises an indication of the one or more licenses and a digital signature.

[0151] Clause 3. The method of clause 2, wherein the digital signature is based on a public-private key pair, wherein the signed document further comprises one or more digital certificates indicating and authenticating the public key.

[0152] Clause 4. The method of any one of clauses 1-3, wherein the vehicle comprises: a road vehicle, an air vehicle, a sea vehicle, or a space vehicle.

[0153] Clause 5. The method of any one of clauses 1-4, further comprising determining a triggering event for requesting the one or more permissions; and sending a request for the one or more permissions from the device to the privilege granting authority server, wherein receiving the signed document is in response to the request.

[0154] Clause 6. A method as described in Clause 5, wherein the triggering event includes: the existence of an emergency; user input indicating a desire to obtain the one or more permissions; the need to obtain the one or more permissions to travel along a certain route to a certain destination or at a certain time; the need to obtain the one or more travel permissions in a certain manner; or a combination thereof.

[0155] Clause 7. The method as described in any of Clauses 1-6 further includes sending vehicle information from the device to the privilege granting authority server before receiving the signed document, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

[0156] Clause 8. A method as described in Clause 7, wherein the one or more characteristics of the operator or the passenger of the vehicle include: VIP status, serving as a doctor, a government official, a military official or a public safety official, having a medical condition, using the vehicle to perform important or emergency actions, or a combination thereof.

[0157] Clause 9. A method as described in any of Clauses 7-8, wherein the one or more characteristics of the vehicle include: the weight of the vehicle, the size of the vehicle, the type of the vehicle, the brand of the vehicle, the model of the vehicle, the cargo of the vehicle, the maximum mileage of the vehicle, the maximum speed of the vehicle, the maximum height of the vehicle, a measure of the noise of the vehicle, or a combination thereof.

[0158] Clause 10. A method as described in any of clauses 7-9, wherein one or more actions related to the operation of the vehicle include: accessing a shipping channel, flight area, road, or lane; accessing a priority route; using a parking space, landing location, dock location, or earth orbit; transporting an item or type of item; moving to an alternative earth orbit; traveling at a speed or speed range; traveling at an altitude or altitude range; performing one or more maneuvers; or a combination thereof.

[0159] Clause 11. The method of any of clauses 1-10, wherein the one or more permissions are temporary.

[0160] Clause 12. The method of any of Clauses 1-11, wherein the signed document further indicates a priority level of the one or more permissions.

[0161] Clause 13. A method as described in any of clauses 1-12, wherein when the vehicle is traveling along a route, the device wirelessly transmits the message to one or more additional devices separate from the vehicle, wherein the selection of the route, the manner in which the vehicle travels along the route, or both are responsive to a response from the one or more additional devices.

[0162] Clause 14. The method as described in Clause 13 also includes receiving an updated signed document from the privilege granting authority server; wirelessly transmitting the updated signed document from the device to another additional device separate from the vehicle; and in response to receiving the updated signed document or in response to a response from the other additional vehicle: adjusting the route, adjusting the manner in which the vehicle travels along the route, or both.

[0163] Clause 15. The method of any of clauses 1-14, wherein the message comprises one or more vehicle-to-everything (V2X) messages, one or more near field communication service (ProSe) messages, one or more sidelink messages, or some combination of these.

[0164] Clause 16. The method of any of clauses 1-15, wherein the message or the signed document further comprises information indicating a destination of the vehicle, a duration of the one or more permits, a route of the vehicle, or a combination thereof.

[0165] Clause 17. The method of any of clauses 1-16, wherein the wirelessly transmitted message comprises: broadcasting the message, multicasting the message, or transmitting the message via unicast to specific receiving devices.

[0166] Clause 18. The method of any of clauses 1-17, wherein sending the message comprises sending the message using a near field communication service (ProSe) or a sidelink communication.

[0167] Clause 19. The method of any of clauses 1-18, further comprising: after transmitting the message, receiving one or more confirmations of receipt of the message from the one or more additional devices.

[0168] Clause 20. A method at a privilege granting authority server for enabling a device to obtain and use permissions related to the operation of a vehicle, the method comprising: establishing a communication link between the privilege granting authority server and the device, the device including the vehicle or an associated device, the associated device being associated with the vehicle; and sending a signed document from the privilege granting authority server to the device indicating the grant of one or more permissions, wherein: the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle, and the signed document is configured to invoke a response from one or more additional devices based on the one or more permissions when wirelessly transmitted from the device to one or more additional devices separate from the vehicle.

[0169] Clause 21. The method of Clause 20, further comprising including an indication of the one or more licenses and a digital signature in the signed document.

[0170] Clause 22. The method of clause 21, wherein the digital signature is based on a public-private key pair, and further comprising including one or more digital certificates in the signed document, the one or more digital certificates indicating and authenticating the public key.

[0171] Clause 23. The method of any one of Clauses 20-22, wherein the vehicle comprises: a road vehicle, an air vehicle, a sea vehicle, or a space vehicle.

[0172] Clause 24. The method of any of clauses 20-23, further comprising determining to grant the one or more permissions before sending the signed document, wherein determining to grant the one or more permissions is based at least in part on: weather conditions, an emergency condition associated with the vehicle, a destination of the vehicle, a time period during which the vehicle will travel with the one or more permissions, one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements of the vehicle. Or a combination thereof.

[0173] Clause 25. The method of Clause 24, further comprising determining a priority level for the one or more permissions; and including the priority level in the signed document.

[0174] Clause 26. The method of any of Clauses 24-25, further comprising receiving, at the privilege-granting authority server, a request for the one or more permissions, wherein determining to grant the one or more permissions is responsive to receiving the request for the one or more permissions.

[0175] Clause 27. The method as described in any of Clauses 24-26 further includes receiving vehicle information of the vehicle at the privilege granting authority server, wherein determining to grant the one or more permissions is based at least in part on the vehicle information, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

[0176] Clause 28. A method as described in Clause 27, wherein the one or more characteristics of the operator or the passenger of the vehicle include: VIP status, serving as a doctor, government official, military official or public safety official, having a medical condition, or using the vehicle to perform important or emergency actions, or a combination thereof.

[0177] Clause 29. A method as described in any of Clauses 27-28, wherein the one or more characteristics of the vehicle include: the weight of the vehicle, the size of the vehicle, the type of the vehicle, the brand of the vehicle, the model of the vehicle, the cargo of the vehicle, the maximum mileage of the vehicle, the maximum speed of the vehicle, the maximum height of the vehicle, a measure of the noise of the vehicle, or a combination thereof.

[0178] Clause 30. The method of any of clauses 27-29, wherein one or more actions associated with the maneuvering of the vehicle include: accessing a shipping lane, flight area, road, or lane; accessing a priority route of travel; using a parking space, landing location, dock location, or earth orbit; transporting an item or type of item; moving to an alternative earth orbit; traveling at a speed or speed range; traveling at an altitude or altitude range; performing one or more maneuvers; or a combination thereof.

[0179] Clause 31. The method of any of Clauses 20-30, further comprising, after sending the signed document, determining to revoke the one or more permissions; and sending a message from the privilege-granting authority server to the device indicating the revocation of the one or more permissions.

[0180] Clause 32. A method according to clause 31, wherein determining to revoke the one or more permissions is based at least in part on: determining that the vehicle has arrived at a designated destination, determining that the vehicle has left the designated route of travel of the vehicle, an emergency condition affecting the designated route of travel of the vehicle, traffic conditions affecting the designated route of travel of the vehicle, or a combination thereof.

[0181] Clause 33. A device for enabling permissions associated with the operation of a vehicle, the device comprising: a transceiver; a memory; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: receive a signed document indicating the grant of one or more permissions from a privilege granting authority server via the transceiver, wherein: the device comprises a vehicle or an associated device, the associated device is associated with the vehicle, and the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle; and after receiving the signed document, wirelessly transmit a message including the signed document from the device to one or more additional devices separate from the vehicle, wherein the wireless transmission of the message is configured to invoke a response from the one or more additional devices based on the one or more permissions.

[0182] Clause 34. The apparatus of clause 33, wherein the signed document comprises an indication of the one or more permissions and a digital signature.

[0183] Clause 35. The apparatus of clause 34, wherein the digital signature is based on a public-private key pair, wherein the signed document further comprises one or more digital certificates indicating and authenticating the public key.

[0184] Clause 36. The apparatus of any of clauses 33-35, wherein the vehicle comprises: a road vehicle, an air vehicle, a sea vehicle, or a space vehicle.

[0185] Clause 37. A device as described in any of clauses 33-36, wherein the one or more processors are further configured to: determine a triggering event for requesting the one or more permissions; and send a request for the one or more permissions to the privilege granting authority server via the transceiver, wherein receiving the signed document is in response to the request.

[0186] Clause 38. A device as described in clause 37, wherein the triggering event includes: the existence of an emergency situation; user input indicating a desire to obtain the one or more permissions; the need to obtain the one or more permissions to travel along a certain route to a certain destination or at a certain time; the need to obtain the one or more permissions to travel in a certain manner; or a combination thereof.

[0187] Clause 39. A device as described in any of clauses 33-38, wherein the one or more processors are further configured to send vehicle information from the device to the privilege granting authority server before receiving the signed document, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

[0188] Clause 40. The apparatus of any of clauses 33-39, wherein the one or more permissions are temporary.

[0189] Clause 41. The device of any of clauses 33-40, wherein the signed document further indicates a priority level of the one or more permissions.

[0190] Clause 42. A device as described in any of clauses 33-41, wherein the one or more processors are further configured to wirelessly transmit the message to the one or more additional devices separate from the vehicle while the vehicle is traveling along a route, wherein selection of the route, the manner in which the vehicle travels along the route, or both are responsive to a response from the one or more additional devices.

[0191] Clause 43. A device as described in Clause 42, wherein the one or more processors are further configured to: receive an updated signed document from the privilege granting authority server; wirelessly transmit the updated signed document from the device to another additional device separate from the vehicle; and in response to receiving the updated signed document or in response to a response from another additional vehicle: adjust the route, adjust the manner in which the vehicle travels along the route, or both.

[0192] Clause 44. The apparatus of any of clauses 33-43, wherein the message or the signed document further comprises information indicating a destination of the vehicle, a duration of the one or more permits, a route of the vehicle, or a combination thereof.

[0193] Clause 45. The device of any of clauses 33-44, wherein, to wirelessly transmit the message, the one or more processors are configured to broadcast the message, multicast the message, or send the message via unicast to specific receiving devices.

[0194] Clause 46. The apparatus of any of clauses 33-45, wherein, to transmit the message, the one or more processors are configured to transmit the message using a near field communication service (ProSe) or a sidelink communication.

[0195] Clause 47. The device of any of clauses 33-46, wherein the one or more processors are further configured to receive one or more acknowledgments of receipt of the message from the one or more additional devices after transmitting the message.

[0196] Clause 48. A privilege granting authority server for enabling a device to obtain and use permissions related to the operation of a vehicle, the privilege granting authority server comprising: a transceiver; a memory; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: establish a communication link between the privilege granting authority server and the device, the device including the vehicle or an associated device, the associated device being associated with the vehicle; and send a signed document indicating the grant of one or more permissions to the device via the transceiver, wherein: the one or more permissions authorize the vehicle to perform one or more actions related to the operation of the vehicle, and the signed document is configured to invoke a response from the one or more additional devices based on the one or more permissions when wirelessly transmitted from the device to one or more additional devices separate from the vehicle.

[0197] Clause 49. The privilege-granting authority server of Clause 48, wherein the one or more processors are further configured to include an indication of the one or more permissions and a digital signature in the signed document.

[0198] Clause 50. The privilege-granting authority server of Clause 49, wherein the digital signature is based on a public-private key pair, and the one or more processors are configured to include one or more digital certificates in the signed document, the one or more digital certificates indicating and authenticating the public key.

[0199] Clause 51. A privilege granting authority server as described in any of clauses 48-50, wherein the one or more processors are further configured to, before sending the signed document: determine to grant the one or more permissions, wherein the determination to grant the one or more permissions is based at least in part on: weather conditions, an emergency condition associated with the vehicle, a destination of the vehicle, a time period during which the vehicle will travel with the one or more permissions, one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements of the vehicle, or a combination thereof.

[0200] Clause 52. The privilege-granting authority server of Clause 51, wherein the one or more processors are further configured to: determine a priority level for the one or more permissions; and include the priority level in the signed document.

[0201] Clause 53. A privilege granting authority server as described in any of Clauses 51-52, wherein the one or more processors are further configured to receive a request for the one or more permissions via the transceiver, wherein the one or more processors are further configured to determine to grant the one or more permissions in response to receiving the request for the one or more permissions.

[0202] Clause 54. A privilege granting authority server as described in any of Clauses 51-53, wherein the one or more processors are further configured to receive vehicle information of the vehicle via the transceiver, wherein the one or more processors are configured to determine the granting of the one or more permissions based at least in part on the vehicle information, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

[0203] Clause 55. A privilege granting authority server as described in any of clauses 48-54, wherein the one or more processors are further configured to: determine to revoke the one or more permissions after sending the signed document; and send a message to the device via the transceiver indicating the revocation of the one or more permissions.

[0204] Clause 56. A privilege granting authority server as described in Clause 55, wherein the one or more processors are configured to determine the revocation of the one or more permissions based at least in part on: determining that the vehicle has arrived at a designated destination, determining that the vehicle has left the designated route of travel of the vehicle, an emergency condition affecting the designated route of travel of the vehicle, traffic conditions affecting the designated route of travel of the vehicle, or a combination thereof.

[0205] Clause 57. An apparatus having means for performing the method of any of clauses 1-32.

[0206] Clause 58. A non-transitory computer-readable medium storing instructions comprising code for performing the method of any of clauses 1-32.

Claims

1. A method at a device for enabling a permission associated with the operation of a vehicle, the method comprising: receiving, at the device from a privilege-granting authority server, a signed document indicating a grant of one or more permissions, wherein: The device includes the vehicle or an associated device, the associated device being associated with the vehicle, and The one or more permissions authorize the vehicle to perform one or more actions related to operation of the vehicle; and After receiving the signed document, a message including the signed document is wirelessly transmitted from the device to one or more additional devices separate from the vehicle, wherein the wireless transmission of the message is configured to invoke a response from the one or more additional devices based on the one or more permissions.

2. The method according to claim 1, wherein: The signed document includes an indication of the one or more permissions and a digital signature.

3. The method according to claim 2, wherein: The digital signature is based on a public key-private key pair, wherein the signed document further comprises one or more digital certificates indicating and authenticating the public key.

4. The method according to claim 1, wherein: The transportation means include: Road transport, Air transportation, Marine transportation, or Space transportation.

5. The method according to claim 1, further comprising: determining a triggering event for requesting the one or more permissions; as well as A request for the one or more permissions is sent from the device to the privilege-granting authority server, wherein receiving the signed document is responsive to the request.

6. The method according to claim 5, wherein: The triggering events include: the existence of an emergency; user input indicating a desire to obtain the one or more permissions; the one or more permits required to travel along a certain route to a certain destination or at a certain time; requires one or more of the above permissions to travel in a certain manner; or Its combination.

7. The method according to claim 1, further comprising: Prior to receiving the signed document, vehicle information is sent from the device to the privilege granting authority server, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

8. The method according to claim 7, wherein: The one or more characteristics of the operator or the passenger of the vehicle include: VIP status, Serving as a physician, government official, military officer, or public safety officer, Those with health conditions, Use the vehicle to perform an important or urgent action, or Its combination.

9. The method according to claim 7, wherein: The one or more characteristics of the vehicle include: the weight of the vehicle, the dimensions of the vehicle, the type of transport, the brand of the vehicle, the model of the vehicle, the cargo of the said transport, the maximum mileage of the vehicle, the maximum speed of the vehicle, the maximum height of the vehicle, a measure of the noise level of the vehicle, or Its combination.

10. The method according to claim 1, wherein: The one or more actions associated with the operation of the vehicle include: Entering a shipping lane, flying area, road or carriageway; access priority driving routes; Use a parking space, landing position, docking location, or Earth orbit; Transporting a certain item or type of item; moving to alternative Earth orbits; Travel at a certain speed or speed range; Travel at a certain altitude or altitude range; perform one or more manipulations; or Its combination.

11. The method according to claim 1, wherein: The one or more permissions are temporary.

12. The method according to claim 1, wherein: The signed document also indicates a priority level of the one or more permissions.

13. The method according to claim 1, wherein: The device wirelessly transmits the message to the one or more additional devices separate from the vehicle as the vehicle travels along the route, wherein selection of the route, the manner in which the vehicle travels along the route, or both are responsive to responses from the one or more additional devices.

14. The method according to claim 13, further comprising: receiving an updated signed document from the privilege-granting authority server; wirelessly transmitting the updated signed document from the device to another attached device separate from the vehicle; and In response to receiving the updated signed document or a response from another additional vehicle: Adjusting the route, adjust the manner in which the vehicle travels along the route, or Both.

15. The method according to claim 1, wherein: The message or the signed document also includes information indicating: the destination of the transport, the duration of the one or more permissions, the route of said transport, or Its combination.

16. The method according to claim 1, wherein: Wirelessly transmitting the message comprises: Broadcast messages, Multicast messages, or Send messages to specific receiving devices via unicast.

17. The method according to claim 1, wherein: Transmitting the message includes transmitting the message using a near field communication service (ProSe) or a sidelink communication.

18. The method of claim 1, further comprising: After transmitting the message, one or more acknowledgments of receipt of the message are received from the one or more additional devices.

19. A method at a privilege granting authority server for enabling a device to obtain and use permissions related to the operation of a vehicle, the method comprising: establishing a communication link between the privilege granting authority server and the device, the device comprising the vehicle or an associated device, the associated device being associated with the vehicle; as well as sending a signed document indicating a grant of one or more permissions from the privilege-granting authority server to the device, wherein: The one or more permissions authorize the vehicle to perform one or more actions related to operation of the vehicle, and The signed document is configured to, when wirelessly transmitted from the device to one or more additional devices separate from the vehicle, invoke a response from the one or more additional devices in accordance with the one or more permissions.

20. The method of claim 19, further comprising including an indication of the one or more permissions and a digital signature in the signed document.

21. The method of claim 20, wherein the digital signature is based on a public-private key pair, and further comprising including one or more digital certificates in the signed document, the one or more digital certificates indicating and authenticating the public key.

22. The method according to claim 19, wherein: The transportation means include: Road transport, Air transportation, Marine transportation, or Space transportation.

23. The method of claim 19, further comprising, before sending the signed document: Determining to grant the one or more permissions, wherein determining to grant the one or more permissions is based at least in part on: Weather conditions, an emergency situation related to said means of transport, the destination of the transport, the time period during which the vehicle will travel with the one or more permits, one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements of said means of transport, or Its combination.

24. The method according to claim 23, further comprising: determining a priority level of the one or more permissions; as well as The priority level is included in the signed document.

25. The method of claim 23, further comprising receiving, at the privilege-granting authority server, a request for the one or more permissions, wherein determining to grant the one or more permissions is responsive to receiving the request for the one or more permissions.

26. The method of claim 23, further comprising: Vehicle information of the vehicle is received at the privilege granting authority server, wherein determining to grant the one or more permissions is based at least in part on the vehicle information, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

27. The method according to claim 26, wherein: The one or more characteristics of the operator or the passenger of the vehicle include: VIP status, Serving as a physician, government official, military officer, or public safety officer, have a medical condition, or Use the vehicle to perform an important or urgent action, or Its combination.

28. The method according to claim 26, wherein: The one or more characteristics of the vehicle include: the weight of the vehicle, the dimensions of the vehicle, the type of transport, the brand of the vehicle, the model of the vehicle, the cargo of the said transport, the maximum mileage of the vehicle, the maximum speed of the vehicle, the maximum height of the vehicle, a measure of the noise level of the vehicle, or Its combination.

29. The method according to claim 19, wherein: The one or more actions associated with the operation of the vehicle include: Entering a shipping lane, flying area, road or carriageway; access priority travel routes; Use a parking space, landing position, docking location, or Earth orbit; Transporting a certain item or type of item; moving to alternative Earth orbits; Travel at a certain speed or range of speeds; Travel at a certain altitude or range of altitudes; perform one or more manipulations; or Its combination.

30. The method of claim 19, further comprising: After sending the signed document, determining to revoke the one or more permissions; as well as A message is sent from the privilege-granting authority server to the device indicating revocation of the one or more permissions.

31. The method according to claim 30, wherein: Determining to revoke the one or more permissions is based at least in part on: Determining that the vehicle has arrived at the designated destination, determining that the vehicle has left the designated travel route of the vehicle, an emergency situation affecting the designated route of travel of the vehicle, traffic conditions affecting the designated route of travel of the vehicle, or Its combination.

32. An apparatus for enabling a permission associated with the operation of a vehicle, the apparatus comprising: Transceiver; Memory; as well as one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: receiving, via the transceiver, from a privilege-granting authority server a signed document indicating a grant of one or more permissions, wherein: The device includes the vehicle or an associated device, the associated device being associated with the vehicle, and The one or more permissions authorize the vehicle to perform one or more actions related to operation of the vehicle; and After receiving the signed document, a message including the signed document is wirelessly transmitted from the device to one or more additional devices separate from the vehicle, wherein the wireless transmission of the message is configured to invoke a response from the one or more additional devices based on the one or more permissions.

33. The apparatus of claim 32, wherein: The signed document includes an indication of the one or more permissions and a digital signature.

34. The apparatus of claim 33, wherein: The digital signature is based on a public key-private key pair, wherein the signed document further comprises one or more digital certificates indicating and authenticating the public key.

35. The apparatus of claim 32, wherein: The transportation means include: Road transport, Air transportation, Marine transportation, or Space transportation.

36. The device of claim 32, wherein the one or more processors are further configured to: determining a triggering event for requesting the one or more permissions; and A request for the one or more permissions is sent via the transceiver to the privilege-granting authority server, wherein receiving the signed document is responsive to the request.

37. The apparatus of claim 36, wherein: The triggering events include: the existence of an emergency; user input indicating a desire to obtain the one or more permissions; the one or more permits required to travel along a certain route to a certain destination or at a certain time; requires one or more of the above permissions to travel in a certain manner; or Its combination.

38. The apparatus of claim 32, wherein: The one or more processors are also configured to send vehicle information from the device to the privilege granting authority server before receiving the signed document, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

39. The apparatus of claim 32, wherein: The one or more permissions are temporary.

40. The apparatus of claim 32, wherein: The signed document also indicates a priority level of the one or more permissions.

41. The apparatus of claim 32, wherein: The one or more processors are also configured to wirelessly transmit the message to the one or more additional devices separate from the vehicle as the vehicle travels along the route, wherein selection of the route, the manner in which the vehicle travels along the route, or both are responsive to a response from the one or more additional devices.

42. The apparatus of claim 41 , wherein the one or more processors are further configured to: receiving an updated signed document from the privilege-granting authority server; wirelessly transmitting the updated signed document from the device to another attached device separate from the vehicle; and In response to receiving the updated signed document or a response from another additional vehicle: Adjusting the route, adjust the manner in which the vehicle travels along the route, or Both.

43. The apparatus of claim 32, wherein: The message or the signed document also includes information indicating: the destination of the transport, the duration of the one or more permissions, the route of said transport, or Its combination.

44. The apparatus of claim 32, wherein: To wirelessly transmit the message, the one or more processors are configured to: Broadcast messages, Multicast messages, or Send messages to specific receiving devices via unicast.

45. The apparatus of claim 32, wherein: To transmit the message, the one or more processors are configured to transmit the message using a near field communication service (ProSe) or a sidelink communication.

46. ​​The apparatus of claim 32, wherein: The one or more processors are further configured to, after transmitting the message, receive one or more acknowledgments of receipt of the message from the one or more additional devices.

47. A privilege granting authority server for enabling a device to obtain and use permissions related to the operation of a vehicle, the privilege granting authority server comprising: Transceiver; Memory; as well as one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: establishing a communication link between the privilege granting authority server and the device, the device comprising the vehicle or an associated device associated with the vehicle; and sending, via the transceiver, to the device a signed document indicating the grant of one or more permissions, wherein: The one or more permissions authorize the vehicle to perform one or more actions related to operation of the vehicle, and The signed document is configured to, when wirelessly transmitted from the device to one or more additional devices separate from the vehicle, invoke a response from the one or more additional devices in accordance with the one or more permissions.

48. The privilege granting authority server of claim 47, wherein: The one or more processors are further configured to include an indication of the one or more permissions and a digital signature in the signed document.

49. A privilege granting authority server according to claim 48, wherein: The digital signature is based on a public-private key pair, and the one or more processors are configured to include one or more digital certificates in the signed document, the one or more digital certificates indicating and authenticating the public key.

50. The privilege granting authority server of claim 47, wherein: The one or more processors are further configured to, prior to sending the signed document: Determining to grant the one or more permissions, wherein determining to grant the one or more permissions is based at least in part on: Weather conditions, an emergency situation related to said means of transport, the destination of the transport, the time period during which the vehicle will travel with the one or more permits, one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements of said means of transport, or Its combination.

51. The privilege granting authority server of claim 50, wherein: The one or more processors are further configured to: determining a priority level of the one or more permissions; and The priority level is included in the signed document.

52. The privilege granting authority server of claim 50, wherein the one or more processors are further configured to receive a request for the one or more permissions via the transceiver, wherein the one or more processors are further configured to determine to grant the one or more permissions in response to receiving the request for the one or more permissions.

53. The privilege granting authority server of claim 50, wherein: The one or more processors are also configured to receive vehicle information of the vehicle via the transceiver, wherein the one or more processors are configured to determine to grant the one or more permissions based at least in part on the vehicle information, wherein the vehicle information indicates one or more characteristics of an operator or passenger of the vehicle, one or more characteristics of the vehicle, one or more requirements for operating the vehicle, or a combination thereof.

54. The privilege granting authority server of claim 47, wherein: The one or more processors are further configured to: After sending the signed document, determining to revoke the one or more permissions; as well as A message is sent to the device via the transceiver indicating revocation of the one or more permissions.

55. The privilege granting authority server of claim 54, wherein: The one or more processors are configured to determine to revoke the one or more permissions based at least in part on: Determining that the vehicle has arrived at the designated destination, determining that the vehicle has left the designated travel route of the vehicle, an emergency situation affecting the designated route of travel of the vehicle, traffic conditions affecting the designated route of travel of the vehicle, or Its combination.

Images