Fallback operation selection for vehicle control

Abstract

This disclosure provides systems, methods, and devices for wireless communication that support radio link state-based fallback operation and control. In a first aspect, a network node determines a fallback operation. For example, a network node may be configured to identify an automotive security integrity level (ASIL) rating for a wireless link between the network node and an automotive user equipment (A-UE). The network node may select a fallback operation based on the ASIL rating, and may send a message to the A-UE, the message including a fallback operation for a vehicle associated with the A-UE. Other aspects and features are also claimed and described.

Description

Technical Field

[0001] The aspects of this disclosure generally relate to driver-operated or driver-assisted vehicles, and more specifically to methods and systems suitable for providing driving assistance or for autonomous driving.

[0002] introduction

[0003] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, message sending and receiving, and broadcasting. These wireless networks can be multiple access networks capable of supporting multiple users by sharing available network resources. Such networks can be multiple access networks that support communication for multiple users by sharing available network resources.

[0004] Vehicles come in many shapes and sizes, are propelled by various propulsion technologies, and carry goods, including people, animals, or objects. These machines are capable of moving goods over long distances, at high speeds, and with larger loads than humans can move. Vehicles were initially driven by humans to control the speed and direction of goods to their destination. Human operation of vehicles has led to numerous unfortunate accidents caused by collisions between vehicles, between vehicles and objects, between vehicles and humans, or between vehicles and animals. With advancements in vehicle automation research, various driver assistance systems have been developed and introduced. These include GPS-based navigation guidance, adaptive cruise control, lane change assist, collision avoidance systems, night vision, parking assist, and blind spot detection.

[0005] ISO 26262 standardizes the Safety Integrity Levels (ASILs) for vehicles, outlining the reliability requirements that a system or component must meet to achieve a specific ASIL. The four levels, ASIL A, ASIL B, ASIL C, and ASIL D, are defined with corresponding reliability values. The ISO SOTIF standard extends these standards to cover autonomous driving. Vehicle-to-everything (V2X) communication that meets these ASIL guidelines is expected to play a critical role in vehicle applications such as autonomous driving and remote driving. These applications rely on V2X to interact with roadside units (RSUs), mobile edge computers (MECs), road cameras, and other roadside facilities.

[0006] The Society of Automotive Engineers (SAE) provides standard J3016, which outlines six levels of driving automation for vehicles. At Level 0, there is no automation; all dynamic driving tasks are performed by a human driver, even with the assistance of warning or intervention systems. Level 1 introduces driver assistance, which can control steering or acceleration / deceleration based on environmental information, but all other tasks remain the responsibility of the human driver. Level 2 enhances this by including steering and acceleration / deceleration control performed by driver assistance systems. Level 3 (called conditional automation) allows automated driving systems to perform all aspects of dynamic driving tasks but expects human intervention upon request. At Level 4, or high automation, automated systems perform all dynamic driving tasks regardless of whether a human responds to an intervention request. Finally, Level 5 represents full automation, where automated systems can handle every aspect of dynamic driving tasks under any road and environmental conditions that could be managed by a human driver. Summary of the Invention

[0007] The following summary outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This summary is not an exhaustive overview of all the intended features of this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. The sole purpose of this summary is to present, in a general form, some concepts of one or more aspects of this disclosure as a prelude to the more detailed description that follows.

[0008] One aspect provides a network node including a processing system comprising at least one processor and memory circuitry storing code. The processing system is configured to execute the code to cause the network node to: identify a Vehicle Safety Integrity Level (ASIL) rating for a radio link between the network node and the A-UE based on a first message received from an Automotive User Equipment (A-UE); and send a second message to the A-UE including a fallback operation for a vehicle associated with the A-UE, the fallback operation being selected based on the ASIL rating for the radio link.

[0009] On the other hand, a method for wireless communication by a network node is provided, the method including identifying a Vehicle Safety Integrity Level (ASIL) rating for a wireless link between the network node and the A-UE based on a first message received from a vehicle user equipment (A-UE). The method also includes sending a second message to the A-UE, the second message including a fallback operation for a vehicle associated with the A-UE, the fallback operation being selected based on the ASIL rating for the wireless link.

[0010] An additional aspect provides an apparatus for wireless communication at a vehicle, the apparatus including a processing system comprising at least one processor and memory circuitry storing code. The processing system can be configured to execute the code to cause the apparatus to: identify a Vehicle Safety Integrity Level (ASIL) rating for a wireless link between a network node and an Automotive User Equipment (A-UE) associated with the vehicle, based on a second message received from a network node in response to a first message sent by the A-UE; and select at least one fallback operation for the vehicle based on the ASIL rating for the wireless link.

[0011] Another aspect provides a method for wireless communication by means of a device in a vehicle, the method comprising identifying a Vehicle Safety Integrity Level (ASIL) rating for a wireless link between a network node and an Automotive User Equipment (A-UE) associated with the vehicle, based on a second message received from a network node, the second message being received in response to a first message sent by the A-UE. The method further comprises selecting at least one fallback operation for the vehicle based on the ASIL rating for the wireless link.

[0012] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims.

[0013] In various specific implementations, the technologies and devices can be used in wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) ng networks, LTE networks, GSM networks, fifth-generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems, or devices), and other communication networks. As described herein, the terms "network" and "system" are used interchangeably.

[0014] For example, CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.

[0015] For example, TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standard for the GSM EDGE (Enhanced Data Rate GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network connecting GSM / EDGE base stations (e.g., Ater and Abis interfaces) and base station controllers (A interface, etc.). The radio access network represents a component of the GSM network through which telephone calls and packet data are routed from the Public Switched Telephone Network (PSTN) and the Internet to subscriber handsets (also known as user terminals or user equipment (UEs)) and from subscriber handsets to the PSTN and the Internet. A mobile phone operator's network may include one or more GERANs, which may be coupled with UTRAN in the case of UMTS / GSM networks. Additionally, the operator's network may also include one or more LTE networks, or one or more other networks. Different network types may use different radio access technologies (RATs) and RANs.

[0016] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization called the 3rd Generation Partnership Project (3GPP), and cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). 5G networks include diverse deployments, diverse spectrum, and diverse services and devices that can be achieved using a unified OFDM-based air interface.

[0017] This disclosure may refer to LTE, 4G, or 5G NR technologies to describe certain aspects; however, this description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of this disclosure may relate to shared access to radio spectrum between networks using different radio access technologies or radio air interfaces.

[0018] Devices, networks, and systems can be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency or wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. A similar naming issue sometimes arises for FR2, which in documents and articles is often (interchangeably) referred to as the “millimeter wave” (mmWave) band, although this is different from the extremely high frequency (EHF) band (30GHz-300GHz) designated as “mmWave” by the International Telecommunication Union (ITU).

[0019] In light of the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "mmWave" is used herein, it can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0020] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform characteristics. These characteristics may include scalable parameter sets and transmission time intervals (TTIs); a general, flexible framework for efficiently multiplexing services and features using dynamic, low-latency Time Division Duplex (TDD) or Frequency Division Duplex (FDD) designs; and advanced radio technologies such as massive MIMO, robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets and subcarrier spacing in 5G NR efficiently addresses the operation of various services across different spectrums and deployments. For example, in various outdoor and macro coverage deployments implementing FDD or TDD below 3 GHz, subcarrier spacing may occur at 15 kHz, exceeding bandwidths such as 1 MHz, 5 MHz, 10 MHz, and 20 MHz. For other various outdoor and small cell coverage deployments with TDD above 3 GHz, subcarrier spacing may occur at 30 kHz over an 80 MHz / 100 MHz bandwidth. For various other indoor broadband implementations using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting via mmWave components under 28 GHz TDD, subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.

[0021] For clarity, certain aspects of the apparatus and technology may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in the sections described below; however, this description is not intended to be limited to 5G applications.

[0022] Furthermore, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, apparatuses, and methods described herein can be applied to other communication systems and applications besides the specific examples provided.

[0023] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations or uses may be via integrated chip implementations or other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail or purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations is evident.

[0024] The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that incorporate one or more of the described aspects. In some practical settings, devices combining the described aspects and features may also necessary include additional components and features for implementation and practice that are claimed and described. The innovations described herein are expected to be implemented in a wide variety of implementations of different sizes, shapes, and constructions, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user equipment, etc.

[0025] In the following description, numerous specific details (such as examples of specific components, circuits, and processes) are set forth to provide a thorough understanding of this disclosure. As used herein, the term "coupled" means a direct connection or a connection via one or more intermediate components or circuits. Furthermore, specific terminology is set forth in the following description and for purposes of explanation to provide a thorough understanding of this disclosure. However, it will be apparent to those skilled in the art that these specific details may not be necessary to practice the teachings disclosed herein. In other instances, known circuits and devices are illustrated in block diagram form to avoid obscuring the teachings of this disclosure.

[0026] Certain portions of the following detailed description are presented using other symbolic representations of programs, logic blocks, processes, and data bit operations within computer memory. In this disclosure, programs, logic blocks, processes, etc., are conceived as a self-consistent sequence of steps or instructions that produce a desired result. These steps are those that require physical manipulation of physical quantities. Although not strictly necessary, these physical quantities typically take the form of electrical or magnetic signals that can be stored, transferred, combined, compared, and otherwise manipulated within a computer system.

[0027] In the accompanying drawings, a single block can be described as performing one or more functions. The one or more functions performed by this block can be performed in a single component or across multiple components, and / or can be performed using hardware, software, or a combination of hardware and software. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps are described below in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as causing a departure from the scope of this disclosure. Additionally, the example device may include components other than those shown, including well-known components such as processors, memory, etc.

[0028] Unless otherwise specifically stated, it will be apparent from the following discussion that, throughout this application, the use of terms such as “access,” “receive,” “transmit,” “use,” “select,” “determine,” “normalize,” “multiply,” “average,” “monitor,” “compare,” “apply,” “update,” “measure,” “derive,” “set,” and “generate” refers to the actions and processes of a computer system or similar electronic computing device that manipulate and transform data represented as physical (electronic) quantities in the registers and memories of the computer system into other data similarly represented as physical quantities in the registers, memories, or other such information storage, transmission, or display devices of the computer system.

[0029] The terms "device" and "apparatus" are not limited to one or a specific number of physical objects (such as a smartphone, a camera controller, a processing system, etc.). As used herein, a device can be any electronic device having one or more components that can implement at least some parts of this disclosure. Although the term "device" is used in the following description and examples to describe various aspects of this disclosure, the term "device" is not limited to a particular configuration, type, or number of objects. As used herein, an apparatus can include a device or part of a device for performing the described operations.

[0030] As used herein (including the claims), the term "or" in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing component A, B, or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C.

[0031] Additionally, as used herein (including the claims), the word “or” in a list of items beginning with “at least one of” indicates a separate list such that a list such as “at least one of A, B or C” refers to A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these items.

[0032] Additionally, as used herein, the term “substantially” is defined as being largely but not necessarily entirely what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any specific implementation of the disclosure, the term “substantially” may be used in place of the specified content within “[percentage]”, where percentage includes 0.1%, 1%, 5%, or 10%.

[0033] Additionally, as used herein, relative terms, unless otherwise specified, can be understood as a quantity relative to a reference. For example, terms such as “higher” or “lower” or “more” or “less” can be understood as a threshold amount higher, lower, more, or less than a reference value. Attached Figure Description

[0034] A further understanding of the nature and advantages of this disclosure can be achieved by referring to the following figures. In the figures, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0035] Figure 1 This is a perspective view of a motor vehicle with a driver monitoring system according to an embodiment of this disclosure.

[0036] Figure 2 A block diagram of an example system for a vehicle according to one or more aspects of this disclosure is shown.

[0037] Figure 3 It is a block diagram illustrating details of an example wireless communication system based on one or more aspects.

[0038] Figure 4 This is a block diagram illustrating an example wireless communication system that supports fallback operation and control based on wireless link state according to one or more aspects.

[0039] Figure 5 This is a flowchart illustrating an example process for fallback operation and control based on wireless link state, supported by one or more aspects.

[0040] Figure 6 This is a flowchart illustrating an example process for fallback operation and control based on wireless link state, supported by one or more aspects.

[0041] Figure 7 It is a block diagram of an example UE that supports fallback operations and control based on radio link state, according to one or more aspects.

[0042] Figure 8 This is a flowchart illustrating an example process for fallback operation and control based on wireless link state, supported by one or more aspects.

[0043] The same reference numerals and names in various figures indicate the same elements. Detailed Implementation

[0044] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of this disclosure. Rather, the detailed description includes specific details for providing a thorough understanding of the subject matter of the invention. It will be apparent to those skilled in the art that these specific details are not necessary in every situation, and in some cases, well-known structures and components are shown in block diagram form for clarity of presentation.

[0045] This disclosure provides systems, apparatus, methods, and computer-readable media that support fallback operation selection and control for navigation applications, such as vehicle-based wireless link quality. The reliability of wireless communication links within a vehicle and between a vehicle and external entities, such as another vehicle, network nodes, MECs, RSUs, etc., can fluctuate due to variable environmental conditions, network coverage variability, and network congestion.

[0046] Autonomous driving may require a reliable connection between the vehicle and the network for effective operation. For higher levels of automation, such as Level 4 or Level 5 automation levels as defined by the International SAE Standards for Driving Automation of Road Vehicles, fallback mechanisms are designed for safety assurance. These mechanisms can be activated when different systems on the vehicle degrade below the level required for the vehicle's automation level.

[0047] Accurately and responsively determining the ASIL rating of wireless communication links for vehicles requires coordination between network entities and the vehicles. Different networked devices can cover all or part of the road, including base stations, RSUs, and MECs. Resources may be limited under different operating conditions and configurations (such as when a single device serves multiple vehicles). Additionally, it remains uncertain whether future traffic management centers or other servers will control autonomous vehicles; therefore, the techniques used to determine ASIL ratings may need to consider both possibilities.

[0048] One potential solution involves a network node identifying the ASIL rating of the radio link between the node and the A-UE based on a message received from the vehicle user equipment (A-UE). This message may include vehicle information or environmental information, such as vehicle identification, the current ASIL rating for the system, road configuration, and traffic density. The network node can then select a fallback operation for the vehicle based on this data and the ASIL rating, particularly if the ASIL rating drops below a predetermined threshold. The selected fallback operation can then be sent to the A-UE. The selection may also be influenced by traffic information determined by the network node and / or by other network nodes, or by mapping information for associated roads. Details of the selected fallback operation can be sent via an Operation Design Domain (ODD) message. If too many devices are connected, the network node can reject additional requests or send a message indicating a reduced operating mode.

[0049] Another potential solution involves a computing device associated with a vehicle identifying the ASIL rating of the radio link between the network node and the A-UE based on a second message received from a network node in response to a first message sent by the A-UE of the vehicle. Based on the ASIL rating, at least one fallback operation can be selected for the vehicle, where the fallback operation corresponds to a pre-configured operation within a mapping for different ASIL ratings. The second message may include an indication of the fallback operation and can be received as an ODD message via another link to a separate device. The first message from the A-UE may contain route or environmental information, vehicle details, or a combination thereof.

[0050] Specific embodiments of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages or benefits. In some aspects, this disclosure provides techniques to improve the ability of networks and vehicles to respond to changes in the quality of wireless links in the operation of automated and semi-automated vehicles. This results in safer vehicle operation, thereby generating benefits such as reduced vehicle accidents, improved traffic management, and enhanced passenger comfort.

[0051] In some implementations, vehicles may be permitted to determine their own backoff operations, thus providing flexibility in managing varying network conditions and vehicle capabilities. Such implementations can be beneficial when vehicles are more aware of the current operational status than network nodes, or when they are aware of one or more critical operational failures or considerations that make network nodes unavailable.

[0052] Other implementations allow for centralized control of rollback operations by network nodes, manufacturers, etc., which enhances security and coordination across multiple modes of transportation. Such implementations enable coordination across multiple modes of transportation, which can improve the safety and efficiency of vehicle operations under degraded conditions.

[0053] Another specific implementation could be to consider mapping information when determining the rollback operation, which could improve the understanding and prediction of link quality or degradation (such as due to congestion, obstacles, etc.) at different points along the route of the vehicle.

[0054] Some implementations can communicate the rollback operation to the vehicle via a manufacturer's wireless link. Such implementations allow for manufacturer control over the selection of the rollback operation, which can be more knowledgeable about the vehicle's condition and capabilities than network nodes, and also achieve a level of coordination that is impossible when individual vehicles select a rollback operation. Furthermore, such systems are better able to rely on preset operating modes or automation levels based on the quality of the wireless link, as these are more familiar with the specific preset operations for each vehicle.

[0055] Another improvement is the ability to control device connections to network nodes. This functionality not only improves link quality for all users but also allows for adjustments to vehicle operation in cases where a new connection is anticipated to degrade the connection quality of other devices. These preemptive adjustments significantly contribute to enhanced overall security. Furthermore, if any network node denies access, the vehicle is equipped with the ability to seamlessly reroute its connection, ensuring uninterrupted operation.

[0056] Figure 1 This is a perspective view of a motor vehicle with a driver monitoring system according to an embodiment of the present disclosure. The vehicle 100 may include a forward-facing camera 112 mounted in the driver's cab and viewed through a windshield 102. The vehicle may also include a driver's cab-facing camera 114 mounted in the driver's cab facing the occupants of the vehicle 100, and particularly the driver of the vehicle 100. Although a set of mounting locations for cameras 112 and 114 is shown for the vehicle 100, other mounting locations may also be used for cameras 112 and 114. For example, one or more cameras may be mounted on one of the driver or passenger B-pillars 126 or one of the driver or passenger C-pillars 128, such as near the top of pillars 126 or 128. As another example, one or more cameras may be mounted at the front of the vehicle 100, such as behind the radiator grille 130 or integrated with the bumper 132. As a further example, one or more cameras may be mounted as part of a driver or passenger side mirror assembly 134.

[0057] Camera 112 may be oriented such that its field of view captures the scene in front of vehicle 100 in the direction in which vehicle 100 is moving when it is in drive mode or in the forward direction. In some embodiments, an additional camera may be located at the rear of vehicle 100 and oriented such that its field of view captures the scene behind vehicle 100 in the direction in which vehicle 100 is moving when it is in reverse mode or in the reverse direction. Camera 114 may be oriented such that its field of view captures the scene in the driver's cab of vehicle and includes the user operator of vehicle, and in particular the face of the user operator of vehicle, with sufficient detail to distinguish the direction of the user operator's gaze. Each of cameras 112 and 114 may include one, two or more image sensors, such as including a first image sensor.

[0058] Figure 2 A block diagram of an example system for a vehicle according to one or more aspects of this disclosure is shown. Vehicle 100 may include a processing system comprising at least one processor and memory circuitry storing code configured to execute the code to cause vehicle 100 to perform various functions as discussed herein. For example, vehicle 100 may include or otherwise coupled to an image signal processor 212 for processing image frames from one or more image sensors, such as a first image sensor 201, a second image sensor 202, and a depth sensor 240. In some specific embodiments, vehicle 100 may also include or be coupled to a processor (e.g., CPU) 204 and a memory 206 storing instructions 208. Vehicle 100 may also include or be coupled to a display 214 and an input / output (I / O) component 216. I / O component 216 may be used for user interaction, such as a touchscreen interface and / or physical buttons. I / O component 216 may also include a network interface for communicating with other devices such as other vehicles, operator mobile devices, and / or remote monitoring systems. The network interface may include one or more of a wide area network (WAN) adapter 252, a local area network (LAN) adapter 253, and / or a personal area network (PAN) adapter 254. Example WAN adapter 252 is a 4G LTE or 5G NR wireless network adapter. Another example WAN adapter 252 is a V2X wireless network adapter. Example LAN adapter 253 is an IEEE 802.11 WiFi wireless network adapter. Example PAN adapter 254 is a Bluetooth wireless network adapter. Each of adapters 252, 253, and / or 254 may be coupled to an antenna comprising multiple antennas configured for main and diversity reception and / or configured to receive a specific frequency band. Vehicle 100 may also include or be coupled to a power source 218, such as a battery or alternator. Vehicle 100 may also include or be coupled to... Figure 2 Additional features or components not shown. In one example, a wireless interface that may include one or more transceivers and an associated baseband processor may be coupled to or included in a WAN adapter 252 for a wireless communication device. In another example, an analog front end (AFE) for converting analog image frame data into digital image frame data may be coupled between image sensors 201 and 202 and image signal processor 212.

[0059] Vehicle 100 may include a sensor hub 250 for interfacing with sensors to receive data on the movement of vehicle 100, data on the environment surrounding vehicle 100, and / or other non-camera sensor data. One example non-camera sensor is a gyroscope, a device configured to measure rotation, orientation, and / or angular velocity to generate motion data. Another example non-camera sensor is an accelerometer, a device configured to measure acceleration, which can also be used to determine velocity and distance traveled by appropriately integrating the measured acceleration, and one or more of acceleration, velocity, and / or distance may be included in the generated motion data. In other examples, the non-camera sensor may be a Global Positioning System (GPS) receiver, a LiDAR system, a RADAR system, or another ranging system. For example, sensor hub 250 may be connected to a vehicle bus for transmitting configuration commands and / or receiving information from vehicle sensors 272, such as distance (e.g., ranging) sensors or vehicle-to-vehicle (V2V) sensors (e.g., sensors for receiving information from nearby vehicles).

[0060] Image signal processor (ISP) 212 can receive image data, such as data used to form image frames. In one embodiment, a local bus connector couples the image signal processor 212 to a local bus that corresponds to... Figure 1 The first camera 203 of camera 112 and the camera that can correspond to Figure 1 The second camera 205 of camera 114 contains image sensors 201 and 202. In another embodiment, a wired interface may couple image signal processor 212 to an external image sensor. In yet another embodiment, a wireless interface may couple image signal processor 212 to image sensors 201 and 202.

[0061] The first camera 203 may include a first image sensor 201 and a corresponding first lens 231. The second camera 205 may include a second image sensor 202 and a corresponding second lens 232. Each of lenses 231 and 232 may be controlled by an associated autofocus (AF) algorithm 233 executed in the ISP 212, which adjusts lenses 231 and 232 to focus on a specific focal plane at a certain scene depth from image sensors 201 and 202. The AF algorithm 233 may be assisted by a depth sensor 240. In some embodiments, lenses 231 and 232 may have a fixed focal length.

[0062] In some embodiments, the image signal processor 212 may execute instructions from memory, such as instructions 208 from memory 206, instructions stored in a separate memory coupled to or included in the image signal processor 212, or instructions provided by processor 204. Additionally or alternatively, the image signal processor 212 may include specific hardware (such as one or more integrated circuits (ICs)) configured to perform one or more operations described in this disclosure. For example, the image signal processor 212 may include one or more image front-ends (IFEs) 235, one or more image post-processing engines (IPEs) 236, and one or more automatic exposure compensation (AEC) engines 234. AF 233, AEC 234, IFE 235, and IPE 236 may each include dedicated circuitry embodied as software code executed by the ISP 212 and / or a combination of hardware within the ISP 212 and software code executed on the ISP.

[0063] In some embodiments, memory 206 may include a non-transitory or non-transitory computer-readable medium storing computer-executable instructions 208 to perform all or part of one or more of the operations described in this disclosure. In some embodiments, instructions 208 include a camera application (or other suitable application) to generate images or videos for execution during operation of vehicle 100. Instructions 208 may also include other applications or programs executable by vehicle 100, such as an operating system, mapping application, or entertainment application. Execution of a camera application, such as by processor 204, may enable vehicle 100 to generate images using image sensors 201 and 202 and image signal processor 212. Memory 206 may also be accessible by image signal processor 212 to store processed frames or may be accessible by processor 204 to obtain processed frames. In some embodiments, vehicle 100 includes a system-on-a-chip (SoC) that integrates image signal processor 212, processor 204, sensor hub 250, memory 206, and input / output components 216 into a single package.

[0064] In some embodiments, at least one of the image signal processor 212 or processor 204 executes instructions to perform various operations described herein, including object detection, risk map generation, driver monitoring, and driver alert operations. For example, the execution of instructions may instruct the image signal processor 212 to begin or end the capture of image frames or sequences of image frames. In some embodiments, processor 204 may include one or more general-purpose processor cores 204A capable of executing scripts or instructions (such as instructions 208 stored in memory 206) of one or more software programs. For example, processor 204 may include one or more application processors configured to execute a camera application (or other suitable application for generating images or videos) stored in memory 206.

[0065] In some embodiments, in addition to the ability to execute software to enable vehicle 100 to perform multiple functions or operations (such as those described herein), processor 204 may also include an IC or other hardware (e.g., an artificial intelligence (AI) engine 224). In some other embodiments, vehicle 100 does not include processor 204, such as when all the described functionalities are configured in image signal processor 212.

[0066] In some embodiments, display 214 may include one or more suitable displays or screens that allow user interaction and / or present items (such as previews of image frames captured by image sensors 201 and 202) to the user. In some embodiments, display 214 is a touch-sensitive display. I / O component 216 may be or include any suitable mechanism, interface, or device to receive input (such as commands) from the user and provide output to the user via display 214. For example, I / O component 216 may include (but is not limited to) a graphical user interface (GUI), keyboard, mouse, microphone, speaker, squeezable bezel, one or more buttons (such as a power button), slider, switch, etc. In some embodiments involving autonomous driving, I / O component 216 may include an interface to a vehicle bus for providing commands and information to and receiving information from a vehicle system 270, which includes propulsion (e.g., commands to increase or decrease speed or apply braking) and steering systems (e.g., commands to turn wheels, change route, or change final destination).

[0067] Although shown as coupled to each other via processor 204, components such as processor 204, memory 206, image signal processor 212, display 214, and I / O components 216 may be coupled to each other in various other arrangements, such as via one or more local buses, which are not shown for simplicity. While image signal processor 212 is illustrated as separate from processor 204, image signal processor 212 may be the core of processor 204, which is an application processor unit (APU) included in a system-on-a-chip (SoC), or otherwise included in processor 204. Although vehicle 100 is mentioned in the examples herein for the purpose of encompassing aspects of this disclosure, some device components may not be included. Figure 2 The details are shown to prevent obscuring aspects of this disclosure. Additionally, other components, the number of components, or combinations of components may be included in a suitable vehicle for performing aspects of this disclosure. Therefore, this disclosure is not limited to the configuration of a particular device or component, but includes vehicle 100.

[0068] Vehicle 100 can communicate as a user equipment (UE) (such as an automotive UE (A-UE)) within wireless network 300, such as via WAN adapter 252, etc. Figure 3 As shown. Figure 3 This is a block diagram illustrating details of an example wireless communication system 300 according to one or more aspects. Wireless network 300 may, for example, include a 5G wireless network. Additionally or alternatively, wireless network 300 may, for example, include one or more V2X networks. As those skilled in the art will recognize, Figure 3 The components appearing in this network are likely to have corresponding components in other network arrangements (including, for example, cellular network arrangements and non-cellular network arrangements (e.g., device-to-device, peer-to-peer, or self-organizing network arrangements)).

[0069] Figure 3The illustrated wireless network 300 includes base station 305 and other network entities. A base station can be a station communicating with a UE and may also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), and an access point, etc. Each base station 305 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving that coverage area, depending on the context in which the term is used. In the specific implementation of the wireless network 300 herein, base station 305 may be associated with the same operator or different operators (e.g., the wireless network 300 may include multiple operator wireless networks). Additionally, in the specific implementation of the wireless network 300 herein, base station 305 may use one or more frequencies (e.g., one or more bands of licensed spectrum, unlicensed spectrum, or combinations thereof) from the same frequencies as neighboring cells to provide wireless communication. In some examples, a single base station 305 or UE 315 may be operated by more than one network operating entity. In some other examples, each base station 305 and UE 315 may be operated by a single network operating entity.

[0070] Base stations can provide communication coverage for macro cells, small cells (such as pico cells or femto cells), or other types of cells. Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as pico cells) typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femto cells) also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, provide restricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, pico base station, femto base station, or home base station. Figure 3 In the example shown, base stations 305d and 305e are conventional macro base stations, while base stations 305a-305c are macro base stations implemented using one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 305a to 305c utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 305f is a small cell base station, which can be a home node or a portable access point. A base station can support one or more (e.g., two, three, and four cells, etc.) cells.

[0071] Base station 305 and other network entities discussed herein may include a processing system comprising at least one processor and memory circuitry storing code, the processing system being configured to execute the code to cause the network entity to perform one or more of the functions discussed herein (such as one or more functions of the network node discussed below).

[0072] Wireless Network 300 can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timings, and transmissions from different base stations can be roughly aligned in time. For asynchronous operation, base stations can have different frame timings, and transmissions from different base stations may not be aligned in time. In some scenarios, the network can be enabled or configured to handle dynamic switching between synchronous and asynchronous operations.

[0073] UE 315 is distributed throughout the wireless network 300, and each UE may be stationary or mobile. It should be understood that although mobile devices are generally referred to as UEs in the standards and specifications issued by 3GPP, such devices may additionally or otherwise be referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, mobile phone, terminal, user agent, mobile client, client, gaming device, augmented reality device, vehicle component, vehicle equipment or vehicle module, or some other suitable term.

[0074] Mobile devices (such as UE 315) can communicate with any type of base station (whether macro base station, pico base station, femto base station, or relay station). Figure 3 In this context, a communication link (represented by a lightning bolt) indicates radio transmission between the UE and a serving base station (which is designated to serve the UE on the downlink or uplink), or expected transmission between base stations and backhaul transmission between base stations. The UE may operate as a base station or other network node in some scenarios. Backhaul communication between base stations of the wireless network 300 can be performed using wired or wireless communication links. The wireless network 300 can also provide additional network efficiency through dynamic, low-latency TDD or low-latency FDD communication, such as in vehicle-to-vehicle (V2V) mesh networks between UEs 315i to 315k communicating with macro base station 305e.

[0075] Figure 4This is a block diagram of an example wireless communication system 400 that supports fallback operation and control based on one or more aspects of wireless link state. In some examples, the wireless communication system 400 may implement aspects of the wireless network 300. The wireless communication system 400 includes a computing device 415 and a network node 405. Although a computing device 415 and a network node 405 are illustrated, in some other specific implementations, the wireless communication system 440 may typically include multiple computing devices 415 and may include more than one network node 405.

[0076] Computing device 415 may include various components (such as structural components, hardware components) for performing one or more functions described herein. Specifically, computing device 415 may include a processing system comprising at least one processor and memory circuitry storing code, the processing system being configured to execute the code to cause computing device 415 to perform one or more of the functions described herein. For example, these components may include one or more processors 402 (hereinafter collectively referred to as “processor 402”), one or more memory devices 404 (hereinafter collectively referred to as “memory 404”), one or more transmitters 416 (hereinafter collectively referred to as “transmitter 416”), and one or more receivers 418 (hereinafter collectively referred to as “receiver 418”). Processor 402 may be configured to execute instructions stored in memory 404 to perform the operations described herein. In some specific embodiments, processor 402 includes or corresponds to one or more of a receiving processor, a transmitting processor, and a controller. Memory 404 includes or is configured to store information 407, ASIL rating 420, one or more rollback operations 422, and vehicle control instructions 424.

[0077] Transmitter 416 is configured to transmit reference signals, control information, and data to one or more other devices, and receiver 418 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitter 416 may transmit signaling, control information, and data to network node base station 405, and receiver 418 may receive signaling, control information, and data from the network node base station. In some implementations, transmitter 416 and receiver 418 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 416 or receiver 418 may include or correspond to a reference signal. Figure 2 One or more components of the described processing system.

[0078] Network node 405 may include various components (such as structural components, hardware components) for performing one or more of the functions described herein. Specifically, a processing system including at least one processor and memory circuitry storing code is configured to execute the code to cause the network node to perform one or more of the functions described herein. For example, these components may include one or more processors 452 (hereinafter collectively referred to as "processor 452"), one or more memory devices 454 (hereinafter collectively referred to as "memory 454"), one or more transmitters 456 (hereinafter collectively referred to as "transmitter 456"), and one or more receivers 458 (hereinafter collectively referred to as "receiver 458"). Processor 452 may be configured to execute instructions stored in memory 454 to perform the operations described herein. Memory 454 includes or is configured to store information 460 and ASIL rating 462.

[0079] Transmitter 456 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 458 is configured to receive reference signals, control information, and data from one or more other devices. For example, transmitter 456 may transmit signaling, control information, and data to UE 115, and receiver 458 may receive signaling, control information, and data from the UE. In some implementations, transmitter 456 and receiver 458 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 456 or receiver 458 may include or correspond to a reference signal. Figure 2 One or more components of the described base station 105.

[0080] In some implementations, the wireless communication system 400 implements a 5G NR network. For example, the wireless communication system 400 may include multiple 5G-capable computing devices 415 and multiple 5G-capable network nodes 405, such as UEs and base stations configured to operate according to 5G NR network protocols (such as those defined by 3GPP). In some implementations, the wireless communication system 400 implements a V2X (vehicle-to-infrastructure) network. For example, the wireless communication system 400 may implement the network according to V2I (vehicle-to-infrastructure) protocols, V2V (vehicle-to-vehicle) protocols, V2P (vehicle-to-pedestrian) protocols, V2N (vehicle-to-network) protocols, or combinations thereof.

[0081] The wireless communication system 400 also includes a computing device 495. The computing device 495 may include various components (such as architectural components, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors, one or more memory devices, one or more transmitters, and one or more receivers. The processor may be configured to execute instructions stored in memory to perform the operations described herein. Some embodiments of system 400 may omit the computing device 495. Additional or alternative embodiments of system 400 may include multiple computing devices 495.

[0082] During operation of the wireless communication system 400, network nodes can be configured to determine ASIL ratings for communications with one or more vehicles (such as one or more computing devices located within or otherwise associated with the vehicles). Backoff operations can then be determined based on these ASIL ratings.

[0083] Specifically, network node 405 may be configured to identify an ASIL rating 462 for the wireless link between network node 405 and computing device 415. Computing device 415 may be associated with a vehicle (such as vehicle 100). Specifically, computing device 415 may be a means for wireless communication at the vehicle and may include one or more computing devices configured to control vehicle operation (such as automatic operation, semi-automatic operation), send and receive messages on behalf of the vehicle, or combinations thereof. In some specific implementations, computing device 415 may be implemented as an automotive user equipment (A-UE), an advanced driver assistance system (ADAS) processor, or a combination thereof.

[0084] Network node 405 may be a device configured to communicate with such devices (such as computing devices) according to one or more protocols. In some embodiments, the network node may be implemented as a base station, such as base station 305. In additional or alternative embodiments, network node 405 may be implemented as a roadside unit (RSU), a mobile edge computer (MEC), or a combination thereof.

[0085] In some implementations, the wireless link between the network node and the vehicle can be any communication link (such as a wireless communication link) between the network node 405 and the vehicle. In some implementations, the wireless link can be implemented according to a V2X protocol (such as one or more of the V2X protocols discussed above). In additional or alternative implementations, the wireless link can be implemented at least in part using a cellular communication protocol (such as 5G NR).

[0086] In some specific implementations, ASIL ratings are used as a risk classification scheme for the functional safety of road vehicles (such as according to ISO 26262). ASIL ratings provide a measure of the reliability and safety of different systems within a vehicle, including the wireless link between network nodes and the vehicle. ASIL ratings can be determined based on the likelihood, severity, exposure, and controllability of potential failures. Ratings range from the lowest safety integrity level, ASIL A, to the highest, ASIL D. Different systems within a vehicle may have separate corresponding ASIL ratings. For example, for a wireless link, an ASIL A rating might indicate that the wireless link could fail in a way that would cause serious safety consequences. As another example, an ASIL D rating might indicate that a wireless link failure is unlikely or unlikely to have significant safety consequences for the vehicle.

[0087] In some embodiments, network node 405 may be configured to determine ASIL rating 462 based on a first message 480 received from a vehicle (such as a first message 480 received from computing device 415). In some embodiments, ASIL rating 462 may be identified based on the signal strength of the first message 480. In some embodiments, network node 405 may store (e.g., using memory 454) a mapping or other process for determining the corresponding ASIL rating 462 based on signal strength measurements of the received message. In some embodiments, ASIL rating 462 may be additionally or alternatively determined based on link quality measurements, service quality measurements, recent channel measurements, historical channel measurements, or combinations thereof.

[0088] In some embodiments, the first message 480 may include the route of the vehicle. In additional or alternative embodiments, the route may be received from another computing device, such as a navigation server or a computing device associated with the vehicle's manufacturer. An ASIL rating 462 may be determined for the wireless link along at least a portion of the route. For example, network node 405 may be configured to determine multiple ASIL ratings for computing device 415 (such as the current ASIL rating based on the first message and one or more predicted ASIL ratings at various locations along the route), and the ASIL rating 462 may be determined based on multiple ASIL ratings. In some embodiments, the ASIL rating 462 for the wireless link may be determined as the current ASIL rating for the wireless link, the minimum predicted ASIL rating along the route, other predicted ASIL ratings along the route, or a combination thereof. In some embodiments, the ASIL rating 462 may identify one or more of the start time, end time, start location, end location, or a combination thereof for the determined rating.

[0089] In some implementations, network node 405 may identify the ASIL rating for the radio link in response to receiving a request from the vehicle to connect to network node 405 (such as a request included in the first message). In additional or alternative implementations, when the vehicle connects to network node 405, network node 405 may identify the ASIL rating 462 for the radio link at regular intervals.

[0090] Network node 405 may be configured to send a second message 470 to a vehicle, the second message including a fallback operation 422 for the vehicle associated with computing device 415. The fallback operation may include specific actions to be performed by the vehicle. For example, the fallback operation may include automatic lane exit, automatic parking, stop-in-path, user-operated fallback, maximum operating speed, etc. In additional or alternative embodiments, the fallback operation may include a specific level of automatic or semi-automatic operation. In some embodiments, the fallback operation 422 is selected based on an ASIL rating 462 for the wireless link. In some embodiments, network node 405 may be configured to select the fallback operation 422 in response to determining that the ASIL rating is below a predetermined threshold (such as a preset threshold). For example, the ASIL rating 462 for the wireless link (such as the current ASIL rating, the predicted minimum ASIL rating) may be compared to a predetermined threshold. In some embodiments, the predetermined threshold may be associated with a mapping (such as a mapping included in information 460). For example, rollback operation 422 may correspond to a pre-configured rollback operation 422 within a mapping for ASIL rating 462 (such as the current value of ASIL rating 462). The mapping may indicate corresponding rollback operations for different ranges of ASIL ratings for the radio link. For example, the mapping may indicate that a level 4 operation is associated with an ASIL rating D for the radio link, and a level 3 operation is associated with an ASIL rating C for the radio link. When the ASIL rating 462 for the radio link is determined to be C, network node 405 may accordingly determine rollback operation 422 as a level 3 operation for the vehicle.

[0091] In some implementations, network node 405 may be configured to determine fallback operation 422 based on additional information such as vehicle information, environmental information, traffic information, mapping information, and combinations thereof. In some implementations, the first message 480 may include vehicle information 407 (such as information determined by the vehicle). Vehicle information 407 may include (i) vehicle identification information, (ii) vehicle capability information, (iii) the current ASIL rating for one or more vehicle systems, or (iv) a combination thereof. In such instances, the method may also include selecting fallback operation 422 based on vehicle information 407. For example, vehicle identification information may determine that the vehicle is capable of Level 3 or lower automation. Therefore, fallback operation 422 can be selected to match the vehicle's capabilities. Specifically, network node 405 may have different mappings for different types of vehicles, including vehicles capable of different levels of automation, different brands / models of vehicles, etc. In some implementations, mappings may be received from manufacturers or safety agencies.

[0092] In some specific implementations, vehicle identification information can refer to unique indications, details, or other identifiers that help to distinguish or identify a particular vehicle. For example, vehicle identification information may include the vehicle identification number (VIN), license plate number, year of manufacture, brand, model, color, engine type, etc.

[0093] In some specific implementations, vehicle capability information can indicate the current capabilities of a vehicle. For example, vehicle capability information may include mechanical capabilities (such as acceleration, braking rate, current speed, maximum speed, etc.). Vehicle capability information may also include computing capabilities (such as available processing power, computing power, communication systems, etc.). Vehicle capability information may also include sensing capabilities (such as available sensors, sensor placement, sensor characteristics, etc.). Vehicle capability information may also include communication capabilities (such as current communication pairings, available communication systems, supported communication protocols, etc.). Vehicle capability information may also include automatic or semi-automatic capability information (such as the level of automation the vehicle can perform, the vehicle's current level of automation, and combinations thereof). In some specific implementations, vehicle capability information may indicate the hardware statistical failure probability (such as RF chain failure probability) of certain vehicle systems, subsystems, or combinations thereof.

[0094] In some specific implementations, the ASIL rating 420 for other systems may include ratings for systems other than wireless links. For example, the current ASIL rating 420 may include ratings for sensing systems, guidance systems, navigation systems, and combinations thereof. The ASIL rating 420 may be determined by computing device 415, vehicles, or combinations thereof.

[0095] In some embodiments, the first message 480 may include environmental information about the road associated with the vehicle. In additional or alternative embodiments, network node 405 may receive the environmental information from another computing device, such as a navigation server, manufacturer server, etc. The environmental information may include (i) the road configuration, (ii) the traffic density of the road, (iii) the following distance of the vehicle on the road, or (iv) a combination thereof. In such instances, network node 405 may be configured to select a fallback operation 422 based on the environmental information. For example, the environmental information may indicate that the following distance of the vehicle is less than a predetermined threshold (such as 20 feet), and the fallback operation 422 may be determined as a reduction in the operating speed of the vehicle (such as until the following distance is greater than or equal to the threshold). In some embodiments, some of the environmental information may be received by network node 405, and some of the environmental information may be determined by network node 405 (such as based on other messages received by network node 405, based on signal measurements between network node 405 and other devices or vehicles on the road, etc.).

[0096] Road configuration information may include the number of lanes on the road, the current lane of the vehicle, and the road speed limit. Traffic density may include the number of vehicles within a threshold distance on the road. Following distance may include the distance between the vehicle and the nearest vehicle in front of it, behind it, etc.

[0097] In some implementations, network node 405 may select rollback operation 422 based on traffic information about the road associated with the vehicle (such as traffic information contained in information 460). In some implementations, traffic information may include information about the vehicle's current location, its position along its route, or a combination thereof, road conditions, etc. In some implementations, traffic information may include traffic density index, vehicle location (such as lane location), vehicle speed, etc. For example, if traffic information indicates a high level of congestion or a low vehicle speed along the vehicle's route, rollback operation 422 may be selected as a lower level of automation (such as level 2 or level 3), a lower maximum operating speed, or a combination thereof.

[0098] In some implementations, at least a portion of traffic information may be determined based on RF sensing by network node 405 of (i) traffic density, (ii) vehicle location, (iii) vehicle speed, or (iv) a combination thereof. For example, RF sensing may be used to determine traffic information by transmitting RF signals and analyzing signal changes caused by objects in its path, such as other vehicles. These signal changes (including time delays and frequency shifts) may be used to identify the speed, direction, and volume of traffic. In some implementations, RF sensing may achieve more accurate location determination than relying on GNSS location determination (such as that received from vehicles on the road). Additionally or alternatively, network node 405 may utilize wireless links between at least a subset of vehicles on the road to determine traffic information (such as location, speed, or other information received from connected vehicles). In some implementations, traffic information may be received at least partially from another network node (such as another network node along the route of the vehicles). In some implementations, traffic information may be received via an end-node controller protocol. In some implementations, one or more other network nodes may use one or more of the techniques discussed above to determine traffic information. In such implementations, network node 405 may receive traffic information from other network nodes, send traffic information to other network nodes, or a combination thereof. In some implementations, network node 405 may receive traffic information from other network nodes at regular intervals. In additional or alternative implementations, network node 405 may request traffic information (such as one or more locations along a route for a vehicle) and may respond to the request to receive traffic information from one or more other network nodes. In some implementations, the terminal node controller protocol may include protocols for communication between one or more network nodes. In some implementations, the terminal node controller protocol may include the X-3 protocol, the 5G NR protocol, etc. As those skilled in the art will understand, the X-3 messaging protocol may be a communication interface facilitating the transmission of intercepted data in the field of lawful interception (LI). This interface forms part of a series of standardized interfaces (i.e., X1, X2, and X3) and may be described in the ETSI TS 103 221 standard.

[0099] In some embodiments, network node 405 may be configured to select fallback operation 422 based on mapping information for roads associated with a vehicle (such as mapping information contained in information 460). In some embodiments, the mapping information may include information about the current location of the vehicle, the road along the vehicle's route, or a combination thereof. For example, the mapping information may include a high-resolution (HD) map of at least one road associated with the vehicle. In some embodiments, the mapping information may be received in response to a request sent by network node 405. For example, the mapping information may be received from a server or other computing device. The request may include (i) an identifier of network node 405, (ii) the location of network node 405 (such as a GNSS location), (iii) at least one identifier of at least one neighboring network node 405, (iv) at least one location of at least one neighboring node, or (v) a combination thereof. In some embodiments, the mapping information may be received at least partially from another network node 405 via an end-node controller protocol (such as the X-3 protocol).

[0100] In some implementations, the second message 470 may be sent via a wireless link between the network node 405 and the computing device 415. For example, the second message 470 may be sent via the same wireless link that received the first message 480.

[0101] In additional or alternative embodiments, the second message 470 may be sent to computing device 415 via another communication link. In some embodiments, the second wireless link may be separate from the first wireless link. For example, the second wireless link may not be between the vehicle and network node 405. Instead, the second wireless link may be between the vehicle and another computing device 495. For example, the vehicle manufacturer may maintain a communication link between the vehicle and a server or other computing device associated with the manufacturer. In such embodiments, the second message may be transmitted as an Operation Design Domain (ODD) message 492 from the manufacturer via the second wireless link between computing device 415 and computing device 495, such as an ODD message 492 transmitted in response to message 490 received from network node 405. The ODD message may indicate, for example, the vehicle's permissible speed range, the vehicle's prohibited speed range, permitted operations (such as lane changes, overtaking), prohibited operations, recommended following distance, etc.

[0102] In some implementations, network node 405 may be configured to send a fallback operation 422 to computing device 495 in response to a request received from computing device 495 (e.g., via message 490). In additional or alternative implementations, computing device 495 may be configured to send fallback operations to computing device 495 at regular intervals (e.g., based on messages received from vehicles, changes to the determined ASIL rating 462 of the radio link, etc.).

[0103] In various embodiments, the second message 470 may be transmitted to the computing device 415 as a push message (e.g., in the event that no request is received from the computing device 415). In additional or alternative embodiments, the second message 470 may be transmitted in response to a request received from the computing device 415.

[0104] In some implementations, computing device 415 may be configured to implement rollback operation 422 selected by network node 405. In additional or alternative implementations, computing device 415 may determine a separate rollback operation and may ignore the rollback operation included in the second message 470.

[0105] In some specific implementations, network node 405 may not determine the fallback operation 422 for the vehicle. For example, the second message 470 may include an ASIL rating 462 for the radio link and may not include the fallback operation 422. In such instances, the vehicle may be configured to determine its own fallback operation 422, as explained further below.

[0106] In a further specific implementation, network node 405 may not determine ASIL rating 462. For example, computing device 415 may alternatively receive a second message 470 from network node 405 and may determine ASIL rating 462 for the wireless link based on the second message 470. In such instances, computing device 415 may use one or more of the techniques discussed above in conjunction with network node 405 determining ASIL rating 462 to determine ASIL rating 462 (such as based on the second message 470 instead of the first message 480).

[0107] In some specific implementations, the vehicle manufacturer may determine rollback operation 422 (such as, but not, network node 405) and may send rollback operation 422 to the vehicle. For example, network node 405 may be configured to send information (such as ASIL ratings, information received from the vehicle) to computing device 495 at regular intervals. In such an instance, computing device 495 may then be configured to determine (such as via ODD message 492, via network node 405) the rollback operation sent to computing device 415.

[0108] In some implementations, network node 405 may be configured to perform load balancing and other types of network management operations. For example, the first message 480 may be a request for vehicles to connect to network node 405. In some implementations, network node 405 may, in response to receiving the first message 480, determine the current number of devices (such as other vehicles) connected to network node 405 and may compare the current number to a predetermined threshold. The predetermined threshold may indicate the number of devices or vehicles that network node 405 can support without degrading the quality of the connected devices (such as lowering the ASIL rating of the wireless link). For example, the predetermined threshold may be determined based on signal quality, current operating conditions, data transfer requirements of the connected devices, the automation level of the connected devices, the capabilities of network node 405, etc.

[0109] In some implementations, if network node 405 determines that the current number is less than a predetermined threshold, it may permit vehicle connection. Permission to connect may be included in a second message 480, may be communicated separately, or a combination thereof. In some implementations, if network node 405 determines that the current number is greater than or equal to a predetermined threshold, it may disallow vehicle connection. For example, network node 405 may be configured to send a third message 482 to computing device 415, which rejects a request for computing device 415 to connect to network node 405. In additional or alternative implementations, if network node 405 determines that the current number is greater than or equal to a predetermined threshold, it may still allow computing device 415 to connect. For example, network node 405 may be configured to send multiple messages instructing a reduced operating mode to computing device 415 and at least a subset of other devices connected to network node 405. A reduced operating mode may indicate a reduced level of automation, reduced operating speed, increased following distance, queuing, or a combination thereof. In some implementations, network node 405 can identify corresponding operating modes (such as during mapping or other processes) for different numbers of connected devices, different levels of network congestion, etc. In some implementations, instead of sending a specific reduced operating mode, network node 405 can send a message containing a lower radio link ASIL rating to at least a subset of devices, which can then determine their own fallback operation. In some implementations, the reduced operating mode can be sent individually to a subset of vehicles (e.g., using a unicast protocol). In additional or alternative implementations, the same message (e.g., using a broadcast protocol) can be used to send the reduced operating mode to multiple vehicles.

[0110] Turning now to computing device 415, during the operation of wireless communication system 400, computing device 415 can be configured to determine and / or receive fallback operations for associated vehicles.

[0111] Specifically, computing device 415 may be configured to identify an ASIL rating 462 for the wireless link between network node 405 and computing device 415 based on a second message 470 received from network node 405. The second message 470 may be received in response to a first message 480 sent by computing device 415. In some embodiments, the first message 480 may include information that network node 405 may use to determine the ASIL rating. In some embodiments, the first message 480 may include a route of a vehicle, and the ASIL rating 462 may be determined for the wireless link along at least a portion of the route. In some embodiments, the second message 470 may include the ASIL rating 462. In additional or alternative embodiments, computing device 415 may determine the ASIL rating 462 based on the second message 470 (such as signal strength based on the second message 470).

[0112] Computing device 415 can be configured to select at least one fallback operation 422 for a vehicle. In some embodiments, computing device 415 can determine fallback operation 422 based on ASIL rating 462. In some embodiments, computing device 415 can be configured to select at least one fallback operation 422 in response to determining that ASIL rating 462 is below a predetermined threshold. In some embodiments, at least one fallback operation 422 corresponds to a pre-configured fallback operation 422 for an ASIL rating within a mapping. The mapping can indicate the corresponding fallback operation for a range of ASIL ratings 462 for a wireless link. In various embodiments, the mapping used by the vehicle can be similar to those discussed above for network node 405. In some embodiments, the mapping can be received from the vehicle manufacturer, vehicle safety agency, etc.

[0113] In some specific implementations, computing device 415 may also be configured to determine a fallback operation based on other ASIL ratings 420 for other systems of the vehicle. ASIL ratings 420 for other systems may include ratings for systems other than the radio link. For example, ASIL ratings 420 may include ratings for sensing systems, guidance systems, navigation systems, and combinations thereof. For example, the vehicle may use a mapping between ASIL ratings of different systems and corresponding operating modes, and may select the lowest operating mode identified in the mapping. For example, the ASIL rating for the radio link may be ASIL D, which may qualify for fully automated operation of the vehicle. However, the ASIL rating for the anti-lock braking system (ABS) may be lower, such as ASIL C, which may correspond to Level 2 operation. In such instances, the fallback operation determined by computing device 415 may be Level 2 operation of the vehicle.

[0114] In some embodiments, network node 405 may selectively or otherwise indicate fallback operation 422. In some embodiments, the second message 470 may include an indication of a first fallback operation 422, which may then be selected as at least one fallback operation 422 for a vehicle. In some embodiments, the second message 470 may be received via a wireless link with network node 405. In additional or alternative embodiments, the second message 470 may be received by a separate wireless link, such as with the manufacturer of the vehicle. In some embodiments, the second message may be received as an ODD message 492 via a second wireless link between computing device 415 and computing device 495 separate from network node 405. In some embodiments, computing device 415 may select fallback operation 422 in response to receiving the second message 470 containing fallback operation 422. In an additional or alternative embodiment, computing device 415 may not select the received rollback operation, but may instead determine a separate rollback operation 422 (such as using one or more of the techniques discussed herein).

[0115] In some embodiments, computing device 415 may send additional information (such as from information 407) to network node 405. Network node 405 may then be configured to select a fallback operation 422, as discussed above, based at least in part on this information. For example, in some embodiments, the first message 480 may include vehicle information. Vehicle information 407 may include (i) vehicle identification information, (ii) vehicle capability information, (iii) the current ASIL rating 420 for one or more vehicle systems, or (iv) a combination thereof. In some embodiments, the first message 480 may include environmental information about the road associated with the vehicle. Environmental information may include (i) road configuration, (ii) road traffic density, (iii) following distance of the vehicle on the road, or (iv) a combination thereof.

[0116] In some specific implementations, computing device 415 may be configured to determine rollback operation 422 based on the above information. For example, computing device 415 may be configured to determine rollback operation 422 based on vehicle information, environmental information, traffic information, or a combination thereof.

[0117] In some embodiments, computing device 415 may be further configured to identify vehicle control instructions 424 for causing the vehicle to perform at least one reversing operation 422. In some embodiments, vehicle control instructions 424 may refer to a set of commands and instructions that directly or indirectly regulate the movement of the vehicle. These instructions may appear in the form of direct vehicle control instructions such as steering, braking, acceleration, or combinations thereof. In additional or alternative embodiments, vehicle control instructions 424 may be supplementary instructions supporting driver assistance programs such as obstacle avoidance, blind spot monitoring, and other driver assistance alerts.

[0118] In some embodiments, a second message 470 or another message 472 received from network node 405 may indicate that computing device 415 is permitted to connect to network node 405. As noted above, computing device 415 may also receive a downgraded operating mode and may switch to a downgraded operating mode upon connection to network node 405 (as in message 472). In additional or alternative embodiments, a second message 470 or another message 472 received from network node 405 may indicate that computing device 415 is not permitted to connect to network node 405. In such instances, computing device 415 may be configured to determine a new network node to connect to and may send a message (such as first message 480 or a later version thereof) to the new network node. In some instances, the new network node may be along the current route of the vehicle. In other instances, there may be no alternative network node along the current route of the vehicle, and computing device 415 may instead be configured to determine a new route (such as a new route with available network nodes). In a further specific implementation, the vehicle can continue along its current route without connecting to network node 405 or another network node 405 (such as at a reduced level of automation).

[0119] For reference Figure 4 As described, this disclosure provides techniques for improving the response of networks and vehicles to changes in the quality of wireless links during automated operation. The results are safer vehicle operation, reduced accidents, improved traffic management, and enhanced passenger comfort. Vehicles can automatically determine fallback operations or have them centrally controlled by network nodes or the manufacturer, providing flexibility under varying network conditions. Additionally, the technique can control device connections to network nodes, thereby improving link quality for all users and allowing preemptive adjustments if a new connection threatens to degrade quality. In the event of a network node rejection, the vehicle can seamlessly reroute its connection for uninterrupted operation.

[0120] Figure 5This is a flowchart illustrating an example process 500 that supports fallback operations and control based on radio link state, according to one or more aspects. The operation of process 500 can be controlled by a base station (such as the one mentioned above). Figure 3 The described base station 305 or as referenced above Figure 7 The described base station) performs the operation. The operation of process 500 can be performed by a network node (such as network node 405). For example, the example operation of process 600 can enable network node 405 to support fallback operations and control based on radio link state.

[0121] Process 500 includes identifying an ASIL rating for the wireless link between the network node and the computing device based on a first message received from the computing device (block 502). For example, network node 405 may identify an ASIL rating 462 for the wireless link between network node 405 and computing device 415 based on a first message 480 received from computing device 415. In some embodiments, the ASIL rating 462 may be identified based on the signal strength of the first message 480. In some embodiments, the first message 480 may include a route of a vehicle, and the ASIL rating for the wireless link may be determined along at least a portion of the route. In some embodiments, the ASIL rating 462 for the wireless link may be determined as the current ASIL rating for the wireless link, the predicted minimum ASIL rating along the route, other predicted ASIL ratings along the route, or a combination thereof. In some embodiments, network node 405 may identify the ASIL rating 462 for the wireless link in response to receiving a request for connection to network node 405 from computing device 415 (such as a request included in the first message 480). In an additional or alternative implementation, when computing device 415 is connected to network node 405, network node 405 may identify ASIL rating 462 for the wireless link at regular intervals.

[0122] Process 500 includes sending a second message to the computing device, which may include a fallback operation for a vehicle associated with the computing device (block 504). For example, network node 405 may send a second message 470 to computing device 415, which includes a fallback operation 422 for a vehicle associated with computing device 415. The fallback operation 422 may be selected based on an ASIL rating 462 for the wireless link.

[0123] In some implementations, process 500 includes selecting a fallback operation 422 in response to determining that the ASIL rating is below a predetermined threshold. In some implementations, fallback operation 422 corresponds to a pre-configured fallback operation 422 for ASIL rating 462 within a mapping, and the mapping may indicate a corresponding fallback operation for a range of ASIL ratings for the radio link.

[0124] In some implementations, the first message 480 may include vehicle information 407 for the vehicle, which includes (i) vehicle identification information, (ii) vehicle capability information, (iii) the current ASIL rating 420 for one or more vehicle systems, or (iv) a combination thereof. In such instances, process 500 may also include selecting a rollback operation 422 based on the vehicle information.

[0125] In some implementations, the first message 480 may include environmental information about the road associated with the computing device 415, including (i) the road configuration, (ii) the traffic density of the road, (iii) the following distance of vehicles on the road, or (iv) a combination thereof. In such instances, process 500 may also include selecting a rollback operation 422 based on the environmental information.

[0126] In some implementations, process 500 further includes selecting a rollback operation 422 based on traffic information for the road associated with computing device 415. In some implementations, at least a portion of the traffic information may be determined based on RF sensing by network node 405 of (i) traffic density, (ii) vehicle location, (iii) vehicle speed, or (iv) a combination thereof. In some implementations, traffic information may be received at least partially from another network node 405 via an end-node controller protocol.

[0127] In some embodiments, process 500 further includes selecting a fallback operation 422 based on mapping information for a road associated with computing device 415. In some embodiments, mapping information can be received in response to a request sent by network node 405, the request including (i) an identifier of network node 405, (ii) the location of network node 405, (iii) at least one identifier of at least one neighboring network node 405, (iv) at least one location of at least one neighboring node, or (v) a combination thereof. In some embodiments, mapping information can be received at least partially from another network node 405 via an end-node controller protocol.

[0128] In some embodiments, the second message 470 may be transmitted via a wireless link between the network node 405 and the vehicle. In additional or alternative embodiments, the second message 470 may be transmitted to the vehicle via other communication links. In some embodiments, the second message may be transmitted as an ODD message via a second wireless link between the computing device 415 and a separate computing device 495 from the network node 405.

[0129] In some implementations, process 500 also includes sending a rollback operation 422 to computing device 415 in response to a request received from computing device 415.

[0130] In some embodiments, the first message 480 may be a request for computing device 415 to connect to network node 405. In some embodiments, network node 405 may, in response to receiving the first message, determine the current number of devices (such as other vehicles) connected to network node 405 and compare the current number to a predetermined threshold. In some embodiments, if network node 405 determines that the current number is less than the predetermined threshold, it may allow computing device 415 to connect. In some embodiments, if network node 405 determines that the current number is greater than or equal to the predetermined threshold, it may disallow computing device 415 to connect. For example, the network node may be configured to send a third message 472 to a vehicle rejecting its request to connect to network node 405, the third message being sent based on the determination that the current number of devices connected to network node 405 exceeds a threshold for network node 405. In some embodiments, and in additional or alternative embodiments, network node 405 may still allow computing device 415 to connect if it determines that the current number is greater than or equal to the predetermined threshold. For example, a network node may be configured to send multiple messages instructing a reduced operating mode to at least a subset of vehicles and other vehicles connected to network node 405.

[0131] Figure 7 This is a block diagram of an example network node 700 that supports fallback operations and control based on one or more aspects of wireless link state. The network node 700 can be configured to perform operations, including referencing... Figures 5 to 6 The process 500 is described in block 5. Network node 700 may include controller 740, which operates to execute logical or computer instructions stored in memory 742, and components that control network node 700 and provide the characteristics and functionality of network node 700. Network node 700 transmits and receives signals via wireless radio components 701a-t and antenna 734a-t under the control of controller 740. Wireless radio components 701a-t may include various components and hardware, including modulators and demodulators, transmit processors, TXMIMO processors, MIMO detectors, receive processors, or combinations thereof. In additional or alternative embodiments, network node 700 may include the structures, hardware, and components shown and described with reference to network node 405.

[0132] As shown in the figure, memory 742 may include information 702, ASIL rating determination logic 703, and fallback operation determination logic 704. Information 702 may correspond to information 407. ASIL rating determination logic 703 may be configured to determine an ASIL rating for a radio link, such as by executing block 502 of process 500. Fallback operation determination logic 704 may be configured to determine a fallback operation for a vehicle, such as by executing block 504 of process 500. Network node 700 can obtain information from one or more UEs (such as...). Figure 3 The network node 700 can receive signals from or send signals to one or more UEs (such as UE 315). Additionally or alternatively, the network node 700 can receive signals from computing devices associated with the vehicle (such as...). Figure 4 Computing device 415 or Figure 8 The computing devices 800 receive signals or send signals to these computing devices.

[0133] Figure 6 This is a flowchart illustrating an example process 600 that supports fallback operation and control based on wireless link state, according to one or more aspects. The operation of process 600 can be performed by a computing device (such as the one mentioned above). Figure 4 The described computing device 415, as referenced Figure 8 The computing device described above, 800 or the reference above. Figure 3 The UE 315 described is executed. For example, the example operation of procedure 600 (also referred to as the “box”) enables computing device 415 to support fallback operations and control based on radio link state.

[0134] Process 600 includes identifying an ASIL rating for the wireless link between the network node and the computing device based on a second message received from network node 405 (block 602). For example, computing device 415 can identify an ASIL rating 462 for the wireless link between network node 405 and computing device 415 based on a second message 470 received from network node 405. The second message 470 can be received in response to a first message 480 sent by computing device 415. In some implementations, the first message may include a route of a vehicle, and the ASIL rating for the wireless link can be determined along at least a portion of the route.

[0135] Process 600 includes selecting at least one fallback operation for a vehicle based on an ASIL rating for the radio link (block 604). For example, computing device 415 may select at least one fallback operation 422 for a vehicle based on an ASIL rating 462 for the radio link. In some embodiments, computing device 415 may determine fallback operation 422 based on ASIL rating 462. In some embodiments, computing device 415 may select at least one fallback operation 422 in response to determining that ASIL rating 462 is below a predetermined threshold. In some embodiments, at least one fallback operation 422 corresponds to a pre-configured fallback operation 422 for an ASIL rating within a mapping that indicates the corresponding fallback operation for a range of ASIL ratings 462 for the radio link.

[0136] In some embodiments, network node 405 may selectively or otherwise indicate rollback operation 422. In some embodiments, the second message 470 may include an indication of the first rollback operation 422, which is selected as at least one rollback operation 422 for a vehicle. In some embodiments, the second message may be received via a wireless link with network node 405. In some embodiments, the second message may be received as an ODD message via a second wireless link between computing device 415 and computing device 495, which is separate from network node 405.

[0137] In some embodiments, the vehicle may execute the rollback operation 422 in response to receiving a second message containing the rollback operation 422. In additional or alternative embodiments, the vehicle may not execute the received rollback operation, but may instead determine a separate rollback operation.

[0138] In some embodiments, the first message may include vehicle information 407, which includes (i) vehicle identification information, (ii) vehicle capability information, (iii) the current ASIL rating for one or more vehicle systems, or (iv) a combination thereof. In some embodiments, the first message may include environmental information about the road associated with the vehicle, including (i) road configuration, (ii) road traffic density, (iii) following distance of the vehicle on the road, or (iv) a combination thereof. In some embodiments, computing device 415 may be configured to determine a rollback operation 422 based on the above information.

[0139] In some specific implementations, process 600 also includes identifying a vehicle control command for causing the vehicle to perform at least one reversal operation 422.

[0140] Figure 8This is a block diagram of an example computing device 800 that supports fallback operations and control based on one or more aspects of wireless link state. The computing device 800 can be configured to perform operations, including reference... Figures 5 to 6 The described process is outlined in a box. Computing device 800 includes a controller 880 that operates to execute logical or computer instructions stored in memory 882, and components that control the computing device 800 and provide the characteristics and functionality of the computing device 800. Under the control of controller 880, computing device 800 transmits and receives signals via wireless radio components 801a-r and antennas 852a-r. Wireless radio components 801a-r may include various components and hardware, including modulators and demodulators, MIMO detectors, receive processors, transmit processors, and TX MIMO processors and combinations thereof. In additional or alternative embodiments, computing device 800 includes references... Figure 4 The computing device 410 is shown and described in terms of its structure, hardware, and components.

[0141] As shown in the figure, memory 882 may include information 802, ASIL rating determination logic 803, and rollback operation determination logic 804. Information 802 may correspond to information 407. ASIL rating determination logic 803 may be configured to determine the ASIL rating, such as by executing block 602 of process 600. Rollback operation determination logic 804 may be configured to determine rollback operation logic, such as by executing block 604 of process 600. Computing device 800 can obtain data from one or more network entities (such as...). Figure 3 Base station 305 or such Figure 4 and Figure 7 The network node (as illustrated in the example) receives signals or sends signals to one or more network entities.

[0142] Note that this is for reference only. Figures 5 to 6 The described one or more boxes (or operations) can be combined with one or more boxes (or operations) described with reference to another figure. For example, Figure 5 One or more boxes (or operations) can be associated with Figure 6 A combination of one or more boxes (or actions). As another example, with... Figures 5 to 6 One or more associated boxes can be linked with and Figures 1 to 4 A combination of one or more related boxes (or operations). Additionally or alternatively, see above for reference. Figures 1 to 4 One or more operations described can be compared with the reference Figure 7 or Figure 8 The described combination of one or more operations.

[0143] In one or more aspects, the technology for supporting fallback operation and control based on wireless link state may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere in this document.

[0144] A first aspect provides a network node including a processing system comprising at least one processor and memory circuitry storing code. The processing system is configured to execute the code to cause the network node to: identify a Vehicle Safety Integrity Level (ASIL) rating for a radio link between the network node and the A-UE based on a first message received from an Automotive User Equipment (A-UE); and send a second message to the A-UE including a fallback operation for a vehicle associated with the A-UE, the fallback operation being selected based on the ASIL rating for the radio link. Additionally, the apparatus can perform or operate according to one or more aspects described below. In some embodiments, the apparatus includes a wireless device, such as a base station. In some embodiments, the apparatus may include at least one processor and memory coupled to the processor. The processor may be configured to perform the operations described herein with reference to the apparatus. In some other embodiments, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the apparatus. In some embodiments, the apparatus may include one or more components configured to perform the operations described herein. In some embodiments, a method of wireless communication may include one or more operations described herein with reference to the apparatus.

[0145] In a second aspect, in conjunction with the second aspect, the processing system is configured to execute the code to further cause the network node to select the fallback operation when the ASIL rating is below a preset threshold.

[0146] In a third aspect, in combination with one or more of the first to second aspects, the fallback operation corresponds to a pre-configured fallback operation for the ASIL rating within a mapping, the mapping indicating a corresponding fallback operation for a range of ASIL ratings for the radio link.

[0147] In a fourth aspect, in combination with one or more of the first to third aspects, the first message includes vehicle information for the vehicle, and the vehicle information may include (i) vehicle identification information, (ii) vehicle capability information, (iii) the current ASIL rating for one or more vehicle systems, or (iv) a combination thereof. The processing system may be configured to execute the code to further enable the network node to select the fallback operation based on the vehicle information.

[0148] In a fifth aspect, in combination with one or more of the first to fourth aspects, the first message includes environmental information about the road associated with the vehicle, and the environmental information may include (i) the road configuration of the road, (ii) the traffic density of the road, (iii) the following distance of the vehicle on the road, or (iv) a combination thereof. The processing system may be configured to execute the code to further enable the network node to select the fallback operation based on the environmental information.

[0149] In a sixth aspect, in combination with one or more of the first to fifth aspects, the processing system is configured to execute the code to further enable the network node to select the rollback operation based on traffic information for the road associated with the vehicle.

[0150] In the seventh aspect, in conjunction with the sixth aspect, the traffic information is received at least in part from another network node via the terminal node controller protocol.

[0151] In the eighth aspect, in combination with one or more of the sixth to seventh aspects, at least a portion of the traffic information is performed based on RF sensing by the network nodes of (i) traffic density, (ii) vehicle location, (iii) vehicle speed, or (iv) a combination thereof.

[0152] In a ninth aspect, in combination with one or more of the first to eighth aspects, the processing system is configured to execute the code to further enable the network node to select a fallback operation based on mapping information for the road associated with the vehicle.

[0153] In the tenth aspect, in conjunction with the ninth aspect, the mapping information is received in response to a request sent by the network node, and the request may include: (i) an identifier of the network node, (ii) the location of the network node, (iii) at least one identifier of at least one neighboring network node, (iv) at least one location of at least one neighboring node, or (v) a combination thereof.

[0154] In the eleventh aspect, in combination with one or more of the ninth to tenth aspects, the mapping information is received at least in part from another network node via the terminal node controller protocol.

[0155] In the twelfth aspect, in combination with one or more of the first to eleventh aspects, the second message is transmitted as an Operation Design Domain (ODD) message via a second wireless link between the vehicle and a computing device separate from the network node.

[0156] In a thirteenth aspect, in conjunction with the twelfth aspect, the processing system is configured to execute the code to further cause the network node to send the rollback operation to the computing device in response to a request received from the computing device.

[0157] In the fourteenth aspect, in combination with one or more of the first to thirteenth aspects, the ASIL rating is identified based on the signal strength of the first message.

[0158] In the fifteenth aspect, in combination with one or more of the first to fourteenth aspects, the first message includes the route of the vehicle, and the ASIL rating is identified for the wireless link along at least a portion of the route.

[0159] In a sixteenth aspect, in combination with one or more of the first to fifteenth aspects, the processing system is configured to execute the code to further cause the network node to send multiple messages indicating a reduced operating mode to the A-UE and at least a subset of other devices wirelessly communicating with the network node.

[0160] In the seventeenth aspect, in combination with the sixteenth aspect, the first message is a request for the A-UE to connect to the network node, and the plurality of messages are sent when the current number of devices wirelessly communicating with the network node exceeds a threshold for the network node.

[0161] In the eighteenth aspect, in combination with one or more of the first to seventeenth aspects, the first message is a request for the A-UE to connect to the network node, and the processing system is configured to execute the code to further cause the network node to send a third message to the A-UE rejecting the request for the A-UE to connect to the network node, the third message being sent when the current number of devices wirelessly communicating with the network node exceeds a threshold for the network node.

[0162] A nineteenth aspect provides a method for wireless communication by a network node, the method comprising identifying a Vehicle Safety Integrity Level (ASIL) rating for a wireless link between the network node and the A-UE based on a first message received from an automotive user equipment (A-UE). The method further comprises sending a second message to the A-UE, the second message including a fallback operation for a vehicle associated with the A-UE, the fallback operation being selected based on the ASIL rating for the wireless link.

[0163] A twentieth aspect provides an apparatus for wireless communication at a vehicle, the apparatus including a processing system comprising at least one processor and memory circuitry storing code. The processing system is configured to execute the code to cause the apparatus to: identify a Vehicle Safety Integrity Level (ASIL) rating for a wireless link between a network node and an Automotive User Equipment (A-UE) associated with the vehicle, based on a second message received from a network node, the second message being received in response to a first message sent by the A-UE; and select at least one fallback operation for the vehicle based on the ASIL rating for the wireless link. Additionally, the apparatus may perform or operate according to one or more aspects described below. In some embodiments, the apparatus includes a wireless device, such as a UE. In some embodiments, the apparatus may include at least one processor and memory coupled to the processor. The processor may be configured to perform the operations described herein with reference to the apparatus. In some other embodiments, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the apparatus. In some embodiments, the apparatus may include one or more components configured to perform the operations described herein. In some embodiments, a method of wireless communication may include one or more operations described herein with reference to the apparatus.

[0164] In the twentieth aspect, in conjunction with the twentieth aspect, the processing system is configured to execute the code to further cause the device to select the at least one rollback operation when the ASIL rating is below a preset threshold.

[0165] In the twenty-second aspect, in combination with one or more of the twenty to twenty-first aspects, the at least one fallback operation corresponds to a pre-configured fallback operation for the ASIL rating within a mapping, the mapping indicating a corresponding fallback operation for a range of ASIL ratings for the radio link.

[0166] In the twenty-third aspect, in combination with one or more of the twenty to twenty-second aspects, the second message includes an instruction for a first rollback operation, which is selected as the at least one rollback operation for the vehicle.

[0167] In the twenty-fourth aspect, in conjunction with the twenty-third aspect, the second message is received as an Operation Design Domain (ODD) message via a second wireless link between the vehicle and a computing device separate from the network node.

[0168] In the twenty-fifth aspect, in combination with one or more of the twenty to twenty-fourth aspects, the second message includes an instruction for a first rollback operation, and the processing system is configured to execute the code to further cause the device to select a second rollback operation, different from the first rollback operation, as the at least one rollback operation for the vehicle based on a plurality of ASIL ratings for the vehicle, including the ASIL rating for the radio link.

[0169] In the twenty-sixth aspect, in combination with one or more of aspects 20 to 25, the first message includes the route of the vehicle, and the ASIL rating is identified for the wireless link along at least a portion of the route.

[0170] In the twenty-seventh aspect, in combination with one or more of aspects 20 to 26, the first message includes vehicle information, and the vehicle information may include (i) vehicle identification information, (ii) vehicle capability information, (iii) the current ASIL rating for one or more vehicle systems, or (iv) a combination thereof.

[0171] In the twentieth aspect, in combination with one or more of aspects twentieth to twenty-seventh, the first message includes environmental information about the road associated with the vehicle, and the environmental information may include (i) the road configuration of the road, (ii) the traffic density of the road, (iii) the following distance of the vehicle on the road, or (iv) a combination thereof.

[0172] In the twenty-ninth aspect, in combination with one or more of aspects 20 to 28, the processing system is configured to execute the code to further enable the device to identify a vehicle control command for causing the vehicle to perform the at least one rollback operation.

[0173] A thirty-point aspect provides a method for wireless communication by means of a device in a vehicle, the method comprising identifying a Vehicle Safety Integrity Level (ASIL) rating for a wireless link between the network node and an Automotive User Equipment (A-UE) associated with the vehicle based on a second message received from a network node, the second message being received in response to a first message sent by the A-UE. The method further comprises selecting at least one fallback operation for the vehicle based on the ASIL rating for the wireless link.

[0174] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0175] This article is about Figures 1 to 4 The components, functional blocks, and modules described include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, and any combination thereof. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, programs, and / or functions, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. Additionally, the features discussed herein may be implemented via dedicated processor circuitry, via executable instructions, or a combination thereof.

[0176] Those skilled in the art will further understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein are merely examples, and that components, methods, or interactions of various aspects of this disclosure can be combined or performed in ways other than those illustrated and described herein.

[0177] The various exemplary logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been broadly described in terms of functionality and illustrated in the aforementioned exemplary components, blocks, modules, circuits, and processes. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0178] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. In some embodiments, the processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some embodiments, specific processes and methods may be performed by circuitry specific to a given function.

[0179] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.

[0180] If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted through a computer-readable medium. The processes of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can be implemented to transfer a computer program from one location to another. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and accessible to a computer. Additionally, any connection may be appropriately referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically reproduce data, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside as a set of code and instructions or any combination of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.

[0181] Various modifications to the specific embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other specific embodiments without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the specific embodiments shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features thereof.

[0182] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positions on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0183] Certain features described in this specification in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as operating in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0184] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the indicated specific order or sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be combined with the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any illustrated operation. In some contexts, multitasking and parallel processing are advantageous. Moreover, the separation of the various system components in the embodiments described above should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other embodiments also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

[0185] As used herein (including the claims), the term "or" in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing component A, B, or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Additionally, as used herein (including the claims), "or" in a list of items beginning with "at least one of" indicates a separate list, such that a list such as "at least one of A, B, or C" refers to A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these items. The term "substantially" is defined as substantially but not necessarily entirely what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed specific implementation, the term “substantially” may be used in place of “[percentage]” for the specified content, where the percentage includes 0.1%, 1%, 5% or 10%.

[0186] The prior description of this disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A network node, the network node comprising: A processing system, comprising at least one processor and memory circuitry storing code, is configured to execute the code to cause the network node to: The vehicle safety integrity level (ASIL) rating for the wireless link between the network node and the A-UE is identified based on the first message received from the vehicle user equipment (A-UE). as well as A second message is sent to the A-UE, the second message including a fallback operation for the vehicle associated with the A-UE, the fallback operation being selected based on the ASIL rating for the radio link.

2. The network node of claim 1, wherein the processing system is configured to execute the code to further cause the network node to select the fallback operation when the ASIL rating is lower than a preset threshold.

3. The network node of claim 1, wherein the fallback operation corresponds to a pre-configured fallback operation for the ASIL rating within a mapping, the mapping indicating a corresponding fallback operation for a range of ASIL ratings for the radio link.

4. The network node of claim 1, wherein the first message includes vehicle information for the vehicle, the vehicle information including (i) vehicle identification information, (ii) vehicle capability information, (iii) the current ASIL rating for one or more vehicle systems, or (iv) a combination thereof, and The processing system is configured to execute the code to further enable the network node to select the rollback operation based on the vehicle information.

5. The network node of claim 1, wherein the first message includes environmental information about the road associated with the vehicle, the environmental information including (i) the road configuration of the road, (ii) the traffic density of the road, (iii) the following distance of the vehicle on the road, or (iv) a combination thereof, and The processing system is configured to execute the code to further enable the network node to select the fallback operation based on the environmental information.

6. The network node of claim 1, wherein the processing system is configured to execute the code to further cause the network node to select the rollback operation based on traffic information for the road associated with the vehicle.

7. The network node of claim 6, wherein the traffic information is received at least in part from another network node via an end-node controller protocol.

8. The network node of claim 6, wherein at least a portion of the traffic information is performed by the network node based on RF sensing of (i) traffic density, (ii) vehicle location, (iii) vehicle speed, or (iv) a combination thereof.

9. The network node of claim 1, wherein the processing system is configured to execute the code to further cause the network node to select a rollback operation based on mapping information for the road associated with the vehicle.

10. The network node of claim 9, wherein the mapping information is received in response to a request sent by the network node, the request comprising: (i) the identifier of the network node, (ii) the location of the network node, (iii) at least one identifier of at least one neighboring network node, (iv) at least one location of at least one neighboring node, or (v) a combination thereof.

11. The network node of claim 9, wherein the mapping information is received at least in part from another network node via an end-node controller protocol.

12. The network node of claim 1, wherein the second message is transmitted as an Operation Design Domain (ODD) message via a second wireless link between the vehicle and a computing device separate from the network node.

13. The network node of claim 12, wherein the processing system is configured to execute the code to further cause the network node to send the rollback operation to the computing device in response to a request received from the computing device.

14. The network node of claim 1, wherein the ASIL rating is identified based on the signal strength of the first message.

15. The network node of claim 1, wherein the first message includes the route of the vehicle, and the ASIL rating is identified for the wireless link along at least a portion of the route.

16. The network node of claim 1, wherein the processing system is configured to execute the code to further cause the network node to send a plurality of messages indicating a reduced operating mode to at least a subset of the A-UE and other devices wirelessly communicating with the network node.

17. The network node of claim 16, wherein the first message is a request for the A-UE to connect to the network node, and wherein the plurality of messages are sent when the current number of devices wirelessly communicating with the network node exceeds a threshold for the network node.

18. The network node of claim 1, wherein the first message is a request for the A-UE to connect to the network node, and the processing system is configured to execute the code to further enable the network node to: A third message is sent to the A-UE rejecting the request for the A-UE to connect to the network node, the third message being sent when the current number of devices wirelessly communicating with the network node exceeds a threshold for the network node.

19. A method for wireless communication by a network node, the method comprising: The vehicle safety integrity level (ASIL) rating for the wireless link between the network node and the A-UE is identified based on the first message received from the vehicle user equipment (A-UE). as well as A second message is sent to the A-UE, the second message including a fallback operation for the vehicle associated with the A-UE, the fallback operation being selected based on the ASIL rating for the radio link.

20. An apparatus for wireless communication in a vehicle, the apparatus comprising: A processing system, comprising at least one processor and memory circuitry storing code, the processing system being configured to execute the code to cause the apparatus to: The second message is received in response to a first message sent by the A-UE to identify the vehicle safety integrity level (ASIL) rating for the wireless link between the network node and the vehicle user equipment (A-UE) associated with the vehicle. as well as Select at least one fallback operation for the vehicle based on the ASIL rating for the wireless link.

21. The apparatus of claim 20, wherein the processing system is configured to execute the code to further cause the apparatus to select the at least one rollback operation when the ASIL rating is below a preset threshold.

22. The apparatus of claim 20, wherein the at least one fallback operation corresponds to a pre-configured fallback operation for the ASIL rating within a mapping, the mapping indicating a corresponding fallback operation for a range of ASIL ratings for the radio link.

23. The apparatus of claim 20, wherein the second message includes an instruction for a first rollback operation, the first rollback operation being selected as the at least one rollback operation for the vehicle.

24. The apparatus of claim 23, wherein the second message is received as an Operation Design Domain (ODD) message via a second wireless link between the vehicle and a computing device separate from the network node.

25. The apparatus of claim 20, wherein the second message includes an instruction for a first rollback operation, and wherein the processing system is configured to execute the code to further cause the apparatus to select a second rollback operation, different from the first rollback operation, as the at least one rollback operation for the vehicle based on a plurality of ASIL ratings for the vehicle, including the ASIL rating for the radio link.

26. The apparatus of claim 20, wherein the first message includes the route of the vehicle, and the ASIL rating is identified for the wireless link along at least a portion of the route.

27. The apparatus of claim 20, wherein the first message includes vehicle information, the vehicle information including (i) vehicle identification information, (ii) vehicle capability information, (iii) current ASIL rating for one or more vehicle systems, or (iv) a combination thereof.

28. The apparatus of claim 20, wherein the first message includes environmental information about a road associated with the vehicle, the environmental information including (i) the road configuration of the road, (ii) the traffic density of the road, (iii) the following distance of the vehicle on the road, or (iv) a combination thereof.

29. The apparatus of claim 20, wherein the processing system is configured to execute the code to further enable the apparatus to identify a vehicle control command for causing the vehicle to perform the at least one rollback operation.

30. A method for wireless communication from a device at a vehicle, the method comprising: The second message received from the network node identifies the vehicle safety integrity level (ASIL) rating for the wireless link between the network node and the vehicle user equipment (A-UE) associated with the vehicle, the second message being received in response to a first message sent by the A-UE; as well as Select at least one fallback operation for the vehicle based on the ASIL rating for the wireless link.

Images