Coexistence of different automotive wireless access technologies

Abstract

Various aspects of the present disclosure generally relate to managing wireless communications in a vehicular communication system. In some aspects, a coexistence manager may receive an interrupt signal from a first component associated with a first automotive radio access technology (RAT) to indicate first timing information associated with an upcoming transmission by the first component associated with the first automotive RAT. The coexistence manager may monitor second timing information associated with a transmission by a second component associated with a second automotive RAT. The coexistence manager may perform actions to manage coexistence between the upcoming transmission by the first component and the transmission by the second component according to the first timing information associated with the upcoming transmission by the first component and the second timing information associated with the transmission by the second component. Numerous other aspects are described.

Description

[Technical Field]

[0001] Aspects of the present disclosure generally relate to wireless communications, and relate to techniques and apparatuses associated with coexistence between different automotive radio access technologies (RATs). [Background Art]

[0002] Vehicle-to-everything (V2X) communication is a generic umbrella term that generally refers to a technology that can be used for communicating information between a vehicle equipped with appropriate communication capabilities and one or more other devices. For example, V2X communication includes vehicle-to-vehicle (V2V) communication technology that enables vehicles to communicate with each other (e.g., to support safety systems with non-line-of-sight and latency-sensitive collision avoidance capabilities), vehicle-to-infrastructure (V2I) communication technology that enables vehicles to communicate with external systems such as street lamps and / or buildings, vehicle-to-pedestrian (V2P) communication technology that enables vehicles to communicate with smartphones and / or connected wearable devices, and / or vehicle-to-network (V2N) communication technology that enables vehicles to communicate with network devices. Generally, V2X communication may be supported using one or more automotive RATs as implementation technologies.

[0003] However, challenges can arise in some cases when different automotive RATs are deployed on different channels within the intelligent transport system (ITS) bandwidth. For example, dedicated short-range communications (DSRC) is an automotive RAT generally based on IEEE 802.11p, an approved modification of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (for example, DSRC is a Wi-Fi solution to support V2X communications, including data exchange between high-speed vehicles, i.e., V2V communications, and data exchange between vehicles and roadside infrastructure, i.e., V2I communications). Cellular V2X (C-V2X), on the other hand, is an automotive RAT based on the 3GPP® standard that uses mobile cellular connectivity based on LTE RAT or NR RAT to exchange messages between vehicles, pedestrians, roadside traffic control devices such as traffic signals, and wireless network infrastructure. In some regions (e.g., Europe and Japan), a large number of DSRC-enabled vehicles have already been deployed. However, because DSRC has not been widely adopted (partly due to its high cost and lack of interoperability with existing cellular networks), C-V2X has emerged as a more promising automotive RAT for enabling V2X applications worldwide.

[0004] However, since many vehicles are already deployed with DSRC support, V2X communication systems (e.g., V2X transceivers) may need to simultaneously support different automotive RATs for both transmission and reception (for example, a V2X communication system on a new vehicle may support DSRC to communicate with older vehicles that only support DSRC, and may support C-V2X to communicate with newer vehicles, pedestrian devices, RSUs, and / or network infrastructure based on the C-V2X standard). However, enabling simultaneous support for DSRC and C-V2X presents various challenges. For example, a V2X communication system typically includes two antennas shared for transmission and reception using different automotive RATs, such as DSRC and C-V2X. This may be due, for example, to the high cost of cables on the vehicle platform and / or insufficient isolation between antennas. In some cases, the half-duplex nature of V2X technology may be due to the limitations of shared antennas for transmission and reception in V2X. For example, if one antenna transmits using one of the automotive RATs, it is possible that none of the antennas receive any reception from that automotive RAT. Furthermore, only one automotive RAT may be active at any given time (e.g., two antennas may both be used for DSRC or both for C-V2X at any given time), and different automotive RATs may be associated with time-unmatched slot structures. Thus, Tx-Tx collisions and / or Rx-Tx collisions may exist between DSRC and C-V2X, which can degrade V2X performance and / or cause safety issues resulting from the collisions, leading to failures in receiving or transmitting V2X messages. Additionally, different vehicles in close proximity to each other may support different automotive RATs (e.g., a car supporting DSRC communication driving in the lane next to another car supporting C-V2X communication), which leads to further Tx-Tx collisions and / or Rx-Tx collisions between the communication systems of these different vehicles. [Overview of the Initiative]

[0005] Some embodiments described herein relate to a coexistence manager for managing wireless communications in a vehicle communication system. The coexistence manager may include a memory and one or more processors coupled to the memory. One or more processors may be configured to receive an interrupt signal transmitted from a first component associated with a first automotive radio access technology (RAT) to a second component associated with a second automotive RAT, indicating a first timing information associated with the next transmission by the first component associated with the first automotive RAT. One or more processors may be configured to monitor a second timing information associated with a transmission by the second component associated with the second automotive RAT. One or more processors may be configured to perform actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, according to first timing information associated with the next transmission by the first component associated with the first automotive RAT and second timing information associated with the transmission by the second component associated with the second automotive RAT.

[0006] Some embodiments described herein relate to a coexistence manager for managing wireless communications in a vehicle communication system. The coexistence manager may include a memory and one or more processors coupled to the memory. One or more processors may be configured to monitor a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT. One or more processors may be configured to monitor a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT. One or more processors may be configured to control power leakage on a hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component, according to the first transmit power level on the first transmit path and the second transmit power level on the second transmit path.

[0007] Some embodiments described herein relate to methods for managing wireless communications in a vehicle communication system, performed by user equipment (UE). The method may include receiving an interrupt signal transmitted from a first component associated with a first automotive RAT to a second component associated with a second automotive RAT, indicating a first timing information associated with the next transmission by the first component associated with the first automotive RAT. The method may also include monitoring a second timing information associated with a transmission by the second component associated with the second automotive RAT. The method may also include taking actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, in accordance with the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with a transmission by the second component associated with the second automotive RAT.

[0008] Some embodiments described herein relate to methods for managing wireless communications in a vehicle communication system, performed by a UE. The method may include monitoring a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT. The method may include monitoring a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT. The method may include controlling power leakage on a hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component, according to the first transmit power level on the first transmit path and the second transmit power level on the second transmit path.

[0009] Some embodiments described herein relate to a non-temporary computer-readable medium for storing a set of instructions for a coexistence manager to manage wireless communications in a vehicle communication system. The set of instructions, when executed by one or more processors of the coexistence manager, can cause the coexistence manager to receive an interrupt signal transmitted from a first component associated with a first automotive RAT to a second component associated with a second automotive RAT, indicating a first timing information associated with the next transmission by the first component associated with the first automotive RAT. The set of instructions, when executed by one or more processors of the coexistence manager, can cause the coexistence manager to monitor a second timing information associated with a transmission by the second component associated with the second automotive RAT. When the set of instructions is executed by one or more processors of the coexistence manager, it may cause the coexistence manager to perform actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, according to first timing information associated with the next transmission by the first component associated with the first automotive RAT and second timing information associated with the transmission by the second component associated with the second automotive RAT.

[0010] Some embodiments described herein relate to a non-temporary computer-readable medium that stores a set of instructions for a coexistence manager to manage wireless communications in a vehicle communication system. The set of instructions, when executed by one or more processors of the coexistence manager, can cause the coexistence manager to monitor a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT. The set of instructions, when executed by one or more processors of the coexistence manager, can cause the coexistence manager to monitor a second transmit power level on a second transmit path associated with a second automotive RAT. The set of instructions, when executed by one or more processors of the coexistence manager, can cause the coexistence manager to control power leakage on a hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component, according to the first transmit power level on the first transmit path and the second transmit power level on the second transmit path.

[0011] Some embodiments described herein relate to devices for managing wireless communications in a vehicle communication system. The device may include means for receiving an interrupt signal transmitted from a first component associated with a first automotive RAT to a second component associated with a second automotive RAT, indicating a first timing information associated with the next transmission by the first component associated with the first automotive RAT. The device may include means for monitoring a second timing information associated with a transmission by the second component associated with the second automotive RAT. The device may include means for performing actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, in accordance with the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with a transmission by the second component associated with the second automotive RAT.

[0012] Some embodiments described herein relate to devices for managing wireless communications in a vehicle communication system. The device may include means for monitoring a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT. The device may include means for monitoring a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT. The device may include means for controlling power leakage on a hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component, according to the first transmit power level on the first transmit path and the second transmit power level on the second transmit path.

[0013] Embodiments are generally substantially described herein with reference to the drawings and this specification and include methods, apparatus, systems, computer program products, non-temporary computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as shown herein.

[0014] The above provides a fairly broad overview of the features and technical advantages of the embodiments described herein in order to better understand the following “Modes for Carrying Out the Invention.” Additional features and advantages are described thereafter. The concepts and specific embodiments disclosed can be readily used as a basis for modifying or designing other structures to accomplish the same objectives of this disclosure. Such equivalent structures will not deviate from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their configuration and method of operation, will be better understood, along with the relevant advantages, by considering the following description in relation to the accompanying figures. Each figure is provided for illustrative and explanatory purposes and is not provided to define limitations on the claims.

[0015] While various embodiments are described in this disclosure by example to several embodiments, those skilled in the art will understand that such embodiments may be implemented in many different configurations and scenarios. The techniques described herein may be implemented using a variety of platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some embodiments may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). The embodiments may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described embodiments and features may include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or analog adders). The embodiments described herein are intended to be applicable to a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and configurations.

[0016] To gain a more detailed understanding of the features of this disclosure listed above, a more detailed description may be obtained by referring to the embodiments partially shown in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical embodiments of this disclosure, and therefore the description may be incorporated into other equally effective embodiments and should not be considered to limit the scope of this disclosure. The same reference numeral in different drawings may identify the same or similar elements. [Brief explanation of the drawing]

[0017] [Figure 1] This figure shows an example of a wireless network that supports different Radio Access Technologies (RATs). [Figure 2] This figure shows an example of at least two user devices (UEs) communicating using side-link communication and vehicle-to-everything (V2X) communication. [Figure 3] This figure shows an example of sidelink communication and accesslink communication. [Figure 4A] This figure shows examples related to the coexistence of different automotive radio access technologies (RATs). Figure 4A shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X communications by using interrupt-based techniques for transferring timing information to intelligently coordinate the coexistence between dedicated short-range communication (DSRC) components and cellular V2X (C-V2X) components. Figure 4B shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4C shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4D shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X by controlling power leakage on hardware leakage paths associated with different RATs. [Figure 4B]This figure shows examples related to the coexistence of different automotive radio access technologies (RATs). Figure 4A shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X communications by using interrupt-based techniques for transferring timing information to intelligently coordinate the coexistence between dedicated short-range communication (DSRC) components and cellular V2X (C-V2X) components. Figure 4B shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4C shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4D shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X by controlling power leakage on hardware leakage paths associated with different RATs. [Figure 4C] This figure shows examples related to the coexistence of different automotive radio access technologies (RATs). Figure 4A shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X communications by using interrupt-based techniques for transferring timing information to intelligently coordinate the coexistence between dedicated short-range communication (DSRC) components and cellular V2X (C-V2X) components. Figure 4B shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4C shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4D shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X by controlling power leakage on hardware leakage paths associated with different RATs. [Figure 4D]This figure shows examples related to the coexistence of different automotive radio access technologies (RATs). Figure 4A shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X communications by using interrupt-based techniques for transferring timing information to intelligently coordinate the coexistence between dedicated short-range communication (DSRC) components and cellular V2X (C-V2X) components. Figure 4B shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4C shows various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4D shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support of DSRC and C-V2X by controlling power leakage on hardware leakage paths associated with different RATs. [Figure 5] This diagram illustrates an exemplary process associated with the coexistence of different automotive RATs. [Figure 6] This diagram illustrates an exemplary process associated with the coexistence of different automotive RATs. [Figure 7] This is a diagram illustrating an exemplary device for managing the coexistence of different automotive RATs. [Modes for carrying out the invention]

[0018] Hereafter, various aspects of the Disclosure will be described more fully with reference to the accompanying drawings. However, the Disclosure may be embodied in many different forms and should not be construed as being limited to any particular structure or function presented throughout the Disclosure. Rather, these aspects are provided to make the Disclosure sufficient and complete and to fully convey the scope of the Disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the Disclosure is intended to encompass all aspects of the Disclosure disclosed herein, whether implemented independently of or in combination with any other aspects of the Disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of aspects described herein. Furthermore, the scope of the Disclosure is intended to encompass such apparatus or method practiced using other structures, functions, or structures and functions in addition to, or other than, the various aspects of the Disclosure described herein. It should be understood that any aspect of the Disclosure disclosed herein may be embodied by one or more elements of the claims.

[0019] Next, several embodiments of telecommunications systems are presented with reference to various devices and techniques. These devices and techniques are described in the following “Modes for Carrying Out the Invention” and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “Elements”). These Elements can be implemented using hardware, software, or a combination thereof. Whether such Elements are implemented as hardware or realized as software depends on the specific application and the design constraints imposed on the overall system.

[0020] Aspects may be described herein using terms generally associated with 5G or New Radio (NR) radio access technology (RAT); however, aspects of the present disclosure may be applied to other RATs, by way of example, such as 3G RAT, 4G RAT, RAT after 5G (e.g., 6G), and / or dedicated short range communication (DSRC) RAT.

[0021] The various embodiments described herein generally relate to coexistence managers capable of managing coexistence in vehicle communication systems supporting different automotive radio access technologies (RATs). For example, some embodiments described herein more specifically relate to interrupt-based techniques that can be implemented in a coexistence manager to resolve transmit-transmit collisions, transmit-receive collisions, and / or other collisions that may potentially occur when a first automotive RAT, such as Dedicated Short-Range Communication (DSRC), and a second automotive RAT, such as Cellular Vehicle-to-Everything (C-V2X), share one or more antennas, but only one automotive RAT can be active at a given time. For example, in some embodiments, the coexistence manager may use interrupt-based techniques to transfer timing information between one or more DSRC components and one or more C-V2X components in order to intelligently coordinate coexistence between DSRC components and C-V2X components. For example, in interrupt-based techniques, a C-V2X component may assert an interrupt to indicate timing information associated with the next C-V2X transmission, and the coexistence manager may send control signals to the DSRC component and / or C-V2X component as needed to avoid or resolve potential conflicts between the next C-V2X transmission and the DSRC transmission. For example, if a DSRC transmission is in progress when an interrupt is asserted from a C-V2X component, the coexistence manager may allow the ongoing DSRC transmission to continue if it can terminate before the next C-V2X transmission begins, send a control signal to drop (e.g., suppress) any portion of the ongoing DSRC transmission that overlaps with the next C-V2X transmission, and / or send a control signal to blank (e.g., suppress) any portion of the next C-V2X transmission that overlaps with the ongoing DSRC transmission.As an addition or alternative, if one or more DSRC components assert an interrupt to initiate DSRC transmission after receiving an interrupt from one or more C-V2X components, the coexistence manager may delay DSRC transmission until the C-V2X transmission is complete, or may initiate DSRC transmission and suppress any portion of the C-V2X transmission that overlaps with the DSRC transmission. As an addition or alternative, the coexistence manager may use power leakage techniques to avoid or resolve potential conflicts between C-V2X transmission and DSRC transmission. For example, a vehicle communication system may include a hardware leakage path from the C-V2X transmission path to the DSRC reception path, and the coexistence manager may be configured to allow transmit power to leak from the C-V2X transmission path to the DSRC reception path while C-V2X transmission is in progress, which may cause one or more DSRC components to detect a channel busy condition and thus delay DSRC transmission until the C-V2X transmission is complete. Furthermore, since the transmit power used in the C-V2X transmit path can vary, the coexistence manager can dynamically adjust the attenuation level on the hardware leakage path to ensure that the power leaking into the DSRC receive path is sufficient to cause one or more DSRC components to detect a channel busy condition that delays DSRC transmission.

[0022] Certain aspects of the subject matter described in the present disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to intelligently resolve transmit-transmit collisions, transmit-receive collisions, and / or other suitable collisions in a vehicle communication system that supports different automotive Radio Access Technologies (RATs) sharing one or more antennas. For example, by using timing information associated with ongoing and / or next transmissions associated with each automotive RAT, the coexistence manager can ensure that only one automotive RAT is active at a given time, minimizing the duration during which transmissions associated with one automotive RAT are suppressed or delayed. Furthermore, by supporting techniques in which transmissions associated with one automotive RAT are delayed or requeued until after potentially conflicting transmissions are completed, the coexistence manager can resolve potential collisions without losing packets that are to be transmitted using the delayed or requeued automotive RAT. Furthermore, by setting the delay duration based on the priority or importance of the packet content to be transmitted, the coexistence manager can ensure that important safety messages or other high-priority messages are transmitted when needed. Furthermore, if the coexistence manager uses a power leakage technique to delay transmissions associated with a particular automotive RAT, adjusting the attenuation level on the hardware leakage path can ensure that components associated with the automotive RAT detect a channel busy condition, thereby delaying any transmissions that might otherwise be initiated while there is an ongoing transmission associated with another automotive RAT. In this manner, as described herein, the coexistence manager can use one or more techniques to intelligently coordinate coexistence between different automotive RATs in a vehicle communication system.

[0023] Figure 1 shows an example of a wireless network 100 that supports different RATs. The wireless network 100 may be, or may include elements thereof, a 5G (e.g., NR) network and / or a 4G (e.g., Long-Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UE120 (shown as UE120a, UE120b, UE120c, UE120d, and UE120e), and / or other entities. A network node 110 is a network node that communicates with the UE120. As shown in the figure, a network node 110 may include one or more network nodes. For example, network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). In another embodiment, network node 110 may be a non-aggregated network node (sometimes referred to as a non-aggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0024] In some embodiments, network node 110 is a network node such as an RU that communicates with UE 120 via a wireless access link, or includes such a network node. In some embodiments, network node 110 is a network node such as a DU that communicates with other network nodes 110 via a fronthaul link or a midhaul link, or includes such a network node. In some embodiments, network node 110 is a network node such as a CU that communicates with other network nodes 110 via a midhaul link or with the core network via a backhaul link, or includes such a network node. In some embodiments, network node 110 (such as an aggregated network node 110 or an unaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network nodes 110 may include, for example, NR base stations, LTE base stations, node B, eNB (e.g., in 4G), gNB (e.g., in 5G), access points, transmission reception points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some embodiments, network nodes 110 may interconnect with each other or with one or more other network nodes 110 within the wireless network 100 using any suitable transport network through various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0025] In some embodiments, network node 110 may provide communication coverage to a specific geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” may refer to the coverage area of ​​network node 110 and / or the network node subsystems serving this coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage with respect to macrocells, picocells, femtocells, and / or other types of cells. Macrocells may cover relatively large geographic areas (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 subscribing to the service. Picocells may cover relatively small geographic areas and may allow unrestricted access by UEs 120 subscribing to the service. Femtocells may cover relatively small geographic areas (e.g., a home) and may allow limited access by UEs 120 associated with that femtocell (e.g., UEs 120 within a closed subscriber group, CSG). A network node 110 relating to a macrocell may be referred to as a macronetwork node. A network node 110 relating to a picocell may be referred to as a piconetwork node. A network node 110 relating to a femtocell may be referred to as a femtonetwork node or home network node. In the embodiment shown in Figure 1, network node 110a may be a macronetwork node relating to a macrocell 102a, network node 110b may be a piconetwork node relating to a picocell 102b, and network node 110c may be a femtonetwork node relating to a femtocell 102c. A network node may support one or more (e.g., three) cells. In some embodiments, cells may not necessarily be fixed, and the geographical area of ​​a cell may move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0026] In some embodiments, the terms “base station” or “network node” may refer to an aggregated base station, a non-aggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some embodiments, “base station” or “network node” may refer to a CU, DU, RU, a near-real-time (near-RT) RAN intelligent controller (RIC), or a non-RT RIC, or a combination thereof. In some embodiments, the terms “base station” or “network node” may refer to a single device configured to perform one or more functions, such as those described herein in relation to network node 110. In some embodiments, the terms “base station” or “network node” may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of several different devices (which may be located in the same or different geographical locations) may be configured to perform at least a portion of a function, or to replicate the performance of at least a portion of a function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some embodiments, the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some embodiments, two or more base station functions may be instantiated on a single device. In some embodiments, the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may contain two or more base stations.

[0027] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit that data to downstream nodes (e.g., UE 120 or network node 110). A relay station may also be a UE 120 that can relay transmissions to other UE 120s. In the embodiment shown in Figure 1, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between them. The network node 110 that relays communications may also be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

[0028] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macronetwork nodes, piconetwork nodes, femtonetwork nodes, and relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference within the wireless network 100. For example, macronetwork nodes may have high transmit power levels (e.g., 5-40 watts), while piconetwork nodes, femtonetwork nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1-2 watts).

[0029] The network controller 130 may be coupled to or communicate with a set of network nodes 110, and may provide coordination and control over these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with each other directly or indirectly via a wireless or wired backhaul communication link. In some embodiments, the network controller 130 may be a CU or core network device, or may include a CU or core network device.

[0030] The UE120 can be distributed across the entire wireless network 100, and each UE120 may be fixed or mobile. The UE120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE120 may be a mobile phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0031] Some UE120s may be considered Machine-Type Communication (MTC) UEs, or evolved or enhanced Machine-Type Communication (eMTC) UEs. Examples of MTC UEs and / or eMTC UEs may include robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with network nodes, other devices (e.g., remote devices), or some other entities. Some UE120s may be considered Internet-of-Things (IoT) devices and / or implemented as NB-IoT (narrowband IoT) devices. Some UE120s may be considered customer premises equipment. A UE120 may be contained within a housing that accommodates its components, such as processor components and / or memory components. In some embodiments, the processor components and memory components may be coupled together. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) may be coupled operationally, communicatively, electronically, and / or electrically.

[0032] In general, any number of wireless networks 100 can be deployed within a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as wireless technology, air interface, etc. Frequencies may be referred to as carriers, frequency channels, etc. To avoid interference between wireless networks of different RATs, each frequency may support a single RAT within a given geographical area. In some cases, NR or 5G RAT networks may be deployed. In some cases, in addition to NR or 5G RAT networks, DSRC RAT networks may be deployed.

[0033] In some embodiments, two or more UE120s (e.g., indicated as UE120a and UE120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE120s may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such embodiments, UE120s may perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by network node 110.

[0034] Devices in wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various classes, bands, channels, etc., depending on frequency or wavelength. For example, devices in wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0035] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. In recent 5G NR research, the operating band for these intermediate band frequencies is identified as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit the characteristics of FR1 and / or FR2, and therefore, in effect, the characteristics of FR1 and / or FR2 may be extended to the intermediate band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0036] With the above examples in mind, please understand that, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that may be below 6GHz, frequencies that may be within the FR1 range, or frequencies that may include intermediate band frequencies. Furthermore, please understand that, unless otherwise specified, terms such as "millimeter wave" may broadly refer to frequencies that may include intermediate band frequencies, frequencies that may be within the FR2, FR4, FR4-a or FR4-1, and / or FR5 ranges, or frequencies that may be within the EHF band. The frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are intended to be applicable to those modified frequency ranges.

[0037] In some embodiments, the UE120 may include a coexistence manager 140. In some embodiments, the coexistence manager 140 may be included in the vehicle communication system of the UE120 and may be used to intelligently control the coexistence of different automotive RATs supported in the vehicle communication system. For example, in some embodiments, the coexistence manager may use one or more techniques, as further described herein, to ensure that only one automotive RAT is active at a given time, and to resolve transmit-transmit collisions, transmit-receive collisions, and / or other potential collisions between different automotive RATs that share one or more antennas.

[0038] For example, as will be described in more detail elsewhere in this specification, the coexistence manager 140 may receive an interrupt signal transmitted from the first component associated with the first automotive RAT to the second component associated with the second automotive RAT, indicating a first timing information associated with the next transmission by the first component associated with the first automotive RAT; may monitor a second timing information associated with a transmission by the second component associated with the second automotive RAT; and may take actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, in accordance with the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with a transmission by the second component associated with the second automotive RAT.

[0039] In addition or alternatively, in some embodiments, the coexistence manager 140 may monitor a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT, monitor a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT, and control power leakage on the hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component according to the first transmit power level on the first transmit path and the second transmit power level on the second transmit path. In addition or alternatively, the coexistence manager 140 may perform one or more other operations described herein.

[0040] For example, UE120a may support a C-V2X-enabled vehicle communication system (e.g., based on LTE RAT and / or NR RAT) on a first vehicle or automobile, and UE120e may support a DSRC-enabled vehicle communication system that may be included on the first vehicle or automobile, or on a second vehicle or automobile different from the first vehicle or automobile. In some embodiments, the coexistence manager 140 may be entirely located on one or more components that support C-V2X communication, entirely located on one or more components that support DSRC, partially located on one or more components that support C-V2X communication, partially located on one or more components that support DSRC, or located on a separate chip or separate device (e.g., on a network node 110). Furthermore, if UE120a is communicating while moving along one or more roads, the coexistence manager 140 may generally operate in a distributed manner across N vehicles or automobiles, where N is an integer with a value of 2 or greater.

[0041] As stated above, Figure 1 is provided as an example. Other examples may differ from those described in relation to Figure 1.

[0042] Figure 2 shows an example of UE200 that communicates using sidelink communication and V2X communication.

[0043] As shown in Figure 2, the first UE205-1 may communicate with the second UE205-2 (and one or more other UE205s) via one or more sidelink channels 210. UE205-1 and 205-2 may communicate using one or more sidelink channels 210 for P2P communication, D2D communication, V2X communication (which may include, for example, V2V communication, V2I communication, and / or V2P communication), and / or mesh networking. In one example, the first UE205-1 may be the first V2X device (for example, the first vehicle, roadside unit (RSU), pedestrian device, or network node), and the second UE205-2 may be the second V2X device (for example, the second vehicle, RSU, pedestrian device, or network node). The first V2X device and the second V2X device may communicate using cellular V2X (C-V2X) communication (e.g., V2X communication using GPP standardized LTE, NR, or other mobile cellular connectivity to exchange messages between vehicles, pedestrians, roadside traffic control devices, and / or other suitable V2X devices). In some embodiments, one or more sidelink channels 210 may use the PC5 interface and / or operate in a high-frequency band (e.g., 5.9 GHz band). Additionally or alternatively, the UE 205 may synchronize the timing of transmission time intervals (TTIs) (e.g., frames, subframes, slots, or symbols) using global navigation satellite system (GNSS) timing.

[0044] As further shown in Figure 2, one or more sidelink channels 210 may include a physical sidelink control channel (PSCCH) 215, a physical sidelink shared channel (PSSCH) 220, and / or a physical sidelink feedback channel (PSFCH) 225. The PSCCH 215 may be used to communicate control information, similar to the physical downlink control channel (PDCCH) and / or physical uplink control channel (PUCCH) used for cellular communication with the network node 110 over an access link or access channel. The PSSCH 220 may be used to communicate data, similar to the physical downlink shared channel (PDSCH) and / or physical uplink shared channel (PUSCH) used for cellular communication with the network node 110 over an access link or access channel. For example, PSCCH215 may carry sidelink control information (SCI)230, which may represent various control information used for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or spatial resources), in which case a transport block (TB)235 may be carried on PSCCH220. TB235 may contain data.The PSFCH225 may be used to communicate sidelink feedback 240 such as hybrid automatic repeat request (HARQ) feedback (e.g., acknowledgment or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), and / or scheduling request (SR).

[0045] In some embodiments, the UE205 may operate using a sidelink transmit mode (e.g., mode 1), in which case resource selection and / or scheduling is performed by the network node 110 (e.g., base station, CU, or DU). For example, the UE205 may receive grants from the network node 110 (e.g., directly or via one or more network nodes) for sidelink channel access and / or scheduling (e.g., for configured grants, in downlink control information (DCI) or in radio resource control (RRC) messages). In some embodiments, the UE205 may operate using a transmit mode (e.g., mode 2), in which case resource selection and / or scheduling is performed by the UE205 (rather than the network node 110). In some embodiments, the UE205 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, the UE205 may measure RSSI parameters associated with various sidelink channels (e.g., sidelink-RSSI (S-RSSI) parameters), RSRP parameters associated with various sidelink channels (e.g., PSSCH-RSRP parameters), and / or RSRQ parameters associated with various sidelink channels (e.g., PSSCH-RSRQ parameters), and may select a channel for transmitting sidelink communications based at least partially on the measurement(s).

[0046] As an addition or alternative, UE205 may perform resource selection and / or scheduling using SCI230 received in PSCCH215, which may indicate occupied resources and / or channel parameters. As an addition or alternative, UE205 may perform resource selection and / or scheduling by determining the channel busy ratio (CBR) associated with various sidelink channels, which may be used for rate control (for example, by indicating the maximum number of resource blocks that UE205 can use for a particular set of subframes).

[0047] In transmit modes where resource selection and / or scheduling are performed by UE205, UE205 may generate sidelink grants and transmit those grants within SCI230. A sidelink grant may indicate one or more resource blocks to be used for the next sidelink transmit on PSSCH220 (e.g., for TB235), one or more subframes to be used for the next sidelink transmit, and / or one or more parameters to be used for the next sidelink transmit (e.g., transmit parameters), such as one or more resource blocks to be used for the next sidelink transmit on PSSCH220, one or more subframes to be used for the next sidelink transmit, and / or MCS to be used for the next sidelink transmit. In some embodiments, UE205 may generate a sidelink grant indicating one or more parameters for semi-persistent scheduling (SPS), such as the periodicity of sidelink transmits. As an addition or alternative, UE205 may generate a sidelink grant for event-driven scheduling, such as for on-demand sidelink messages.

[0048] As stated above, Figure 2 is provided as an example. Other examples may differ from those described in relation to Figure 2.

[0049] Figure 3 shows an example 300 of side-link communication and access-link communication according to this disclosure.

[0050] As shown in Figure 3, the transmitter (Tx) / receiver (Rx) UE305 and the Rx / Tx UE310 can communicate with each other via sidelinks, as described above with respect to Figure 2. In some cases, the Tx / Rx UE305 may be a first V2X device (such as the first V2X device 205-1), and the Tx / Rx UE310 may be a second V2X device (such as the second V2X device 205-2). As further shown, in some sidelink modes, network node 110 may communicate with the Tx / Rx UE305 (e.g., directly or via one or more network nodes), such as via the first access link. As an addition or alternative, in some sidelink modes, network node 110 may communicate with the Rx / Tx UE310 (e.g., directly or via one or more network nodes), such as via the first access link. The Tx / Rx UE305 and / or Rx / Tx UE310 may correspond to one or more UEs as described elsewhere in this specification, such as UE120 in Figure 1. Therefore, direct links between UE120s (e.g., via the PC5 interface) may be referred to as sidelinks, and direct links between network 110 and UE120 (e.g., via the Uu interface) may be referred to as access links. Sidelink communications may be transmitted via sidelinks, and access link communications may be transmitted via access links. Access link communications may be either downlink communications (from network node 110 to UE120) or uplink communications (from UE120 to network node 110).

[0051] As stated above, Figure 3 is provided as an example. Other examples may differ from those described in relation to Figure 3.

[0052] Figures 4A to 4D illustrate Example 400 related to coexistence between different automotive RATs. Figure 4A shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support for DSRC and C-V2X communications by using interrupt-based techniques for transferring timing information to intelligently coordinate the coexistence between DSRC and C-V2X components. Figures 4B and 4C illustrate various scenarios in which a coexistence manager resolves potential conflicts between DSRC and C-V2X transmissions. Figure 4D shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support for DSRC and C-V2X by controlling power leakage on hardware leakage paths associated with different RATs.

[0053] In some cases, different automotive RATs, such as DSRC and C-V2X, can be deployed on different channels within the Intelligent Transportation Systems (ITS) band. For example, DSRC is generally based on IEEE 802.11p, an approved modification of the IEEE 802.11 standard (for instance, DSRC is a Wi-Fi solution to support V2X communications, including data exchange between high-speed vehicles, i.e., V2V communications, and data exchange between vehicles and roadside infrastructure, i.e., V2I communications). C-V2X, on the other hand, is a 3GPP-based automotive RAT that uses mobile cellular connectivity based on LTE RAT or NR RAT to exchange messages between vehicles, pedestrians, roadside traffic control devices such as traffic signals, and wireless network infrastructure (e.g., one or more CUs, DUs, or RUs). In some regions (e.g., Europe and Japan), a large number of DSRC-enabled vehicles have already been deployed. However, because DSRC has not been widely adopted (partly due to its high cost and lack of interoperability with existing cellular networks), C-V2X has emerged as a more promising automotive RAT for enabling V2X applications worldwide.

[0054] However, since many vehicles are already deployed with DSRC support, V2X communication systems (e.g., V2X transceivers) may need to simultaneously support different automotive RATs for both transmission and reception (for example, a V2X communication system on a new vehicle may support DSRC to communicate with older vehicles that only support DSRC, and may support C-V2X to communicate with newer vehicles, pedestrian devices, RSUs, and / or network infrastructure based on the C-V2X standard). However, enabling simultaneous support for DSRC and C-V2X presents various challenges. For example, a V2X communication system typically includes two antennas shared for transmission and reception using different automotive RATs, such as DSRC and C-V2X. This may be due, for example, to the high cost of cables on the vehicle platform and / or insufficient isolation between antennas. In some cases, the half-duplex nature of V2X technology may be due to the limitations of shared antennas for transmission and reception in V2X. For example, if a transmission using one of the automotive RATs occurs from any one antenna, it is possible that none of the antennas receive any of the automotive RATs. Furthermore, only one automotive RAT may be active at any given time (for example, two antennas may both be used for DSRC or both for C-V2X at any given time), and different automotive RATs may be associated with slot structures that are not time-matched.Furthermore, different automotive RATs may use different communication technologies (e.g., OFDM with carrier-sense multiple access (CSMA) for DSRC 802.11p versus single-carrier frequency division multiplexing (SC-FDM) with semi-persistent sensing for C-V2X), have different transmission times (e.g., typically 0.4 milliseconds (ms) for DSRC versus 1 ms for C-V2X), and / or have different symbol durations (e.g., 8 microseconds (μs) for DSRC versus 71 μs for C-V2X). Therefore, since Tx-Tx collisions and / or Rx-Tx collisions can occur between DSRC and C-V2X, a V2X communication system that simultaneously supports both DSRC and C-V2X may need to employ coexistence algorithms to resolve potential collisions.

[0055] For example, Figure 4A shows an exemplary communication system that may be used in a vehicle UE to enable simultaneous support for DSRC and C-V2X. As shown in Figure 4A, the communication system may support DSRC and C-V2X on different modems, which necessitates managing the coexistence of different chips supporting different automotive RATs. For example, as shown in Figure 4A, the communication system may include a cellular modem 410, a C-V2X software-defined radio (SDR) 412 (e.g., a C-V2X radio frequency (RF) transceiver), and a C-V2X RF front-end (RF front-end, RFFE), which may be located on a first chip. As further shown, the communication system may include a DSRC modem 420 and a DSRC RFFE 422, which may be located on a second chip. Thus, the communication system may include a switching subsystem 430 for passing transmit and / or receive signals between two shared antennas and C-V2X and DSRC components. For example, since DSRC and C-V2X are supported on different, independent modems, the switching subsystem 430 may include various switches controlled by control signals sent from the C-V2X and DSRC components (for example, when there is an ongoing C-V2X transmission, the C-V2X Tx_On signal may be asserted or high; when there is an ongoing DSRC transmission, the DSRC Tx_On signal may be asserted or high; the front-end switching logic within the switching subsystem 430 may be derived from the C-V2X Tx_On signal and the DSRC Tx_On signal). However, in some cases, there may be conflicts between two automotive RATs with different timing structures. For example, DSRC and C-V2X have different transmission timings and different Rx timings, which can potentially lead to Tx-Tx and / or Rx-Rx collisions.

[0056] Accordingly, in some embodiments, the communication system may include a coexistence manager 440 (e.g., coexistence manager 140) that can enable coexistence between DSRC components and C-V2X components sharing one or more antennas. In some embodiments, the coexistence manager 440 may be partially located on a first chip including a cellular modem 410, a C-V2X SDR 412, and a C-V2X RFFE 414, and partially located on a second chip including a DSRC modem 420 and a DSRC RFFE 422. However, it will be understood that other preferred configurations for the coexistence manager 440 are possible. For example, in some embodiments, the coexistence manager 440 may be located only on a first chip including a cellular modem 410, a C-V2X SDR 412, and a C-V2X RFFE 414, or only on a second chip including a DSRC modem 420 and a DSRC RFFE 422, or on separate chips.

[0057] As shown in Figures 4A to 4C and described in further detail herein, the coexistence manager 440 may be configured to monitor interrupts from the C-V2X SDR 412 and DSRC modem 420 indicating the respective timings for C-V2X transmission and DSRC transmission. For example, the coexistence manager 440 may be configured to monitor a C-V2X interrupt indicating timing information associated with the C-V2X Tx_On signal, and a DSRC interrupt indicating timing information associated with the DSRC Tx_On signal. Thus, if there is a potential Tx-Tx collision (e.g., DSRC transmission at least partially overlaps with C-V2X transmission) or a potential Rx-Tx collision (e.g., DSRC transmission at least partially overlaps with C-V2X reception, or vice versa), the coexistence manager 440 can intelligently resolve the collision based on the DSRC and C-V2X timing information.

[0058] For example, as shown in Figure 4A, the coexistence manager 440 may generally include interfaces for receiving DSRC interrupts from the DSRC modem 420 and C-V2X interrupts from the C-V2X SDR 412, where the DSRC interrupt may indicate timing information associated with DSRC transmission and the C-V2X interrupt may indicate timing information associated with C-V2X transmission. Therefore, the coexistence manager 440 may generally use the timing information transmitted by the DSRC interrupt to forward DSRC timing information to the C-V2X components (e.g., the cellular modem 410 and the C-V2X SDR 412) and may use the timing information transmitted by the C-V2X interrupt to forward C-V2X timing information to the DSRC components (e.g., the DSRC modem 420). For example, in some embodiments, the interface may include general-purpose input / output (GPIO) lines or general radio frequency connection (GRFC) lines provided between the DSRC and C-V2X components to transmit timing information between the DSRC and C-V2X components at runtime. Alternatively, in some embodiments, the coexistence manager 440 may share timing information between the DSRC and C-V2X components using a two-wire interface, and the coexistence manager 440 may make centralized decisions to select or schedule DSRC and / or C-V2X transmissions to prevent temporal collisions.

[0059] For example, Figures 4B and 4C illustrate various scenarios in which the coexistence manager 440 may take one or more actions to resolve potential conflicts between DSRC transmissions and C-V2X transmissions. For example, in some embodiments, timing information associated with a C-V2X transmission may be available to the cellular modem 410 and the C-V2X SDR 412 a certain amount of time (e.g., X microseconds (μs)) before the time when the actual C-V2X transmission is scheduled to begin. Thus, in some embodiments, the C-V2X SDR 412 may send an interrupt to the coexistence manager 440 indicating timing information associated with the next C-V2X transmission X μs before the time when the C-V2X transmission is scheduled to begin. For example, referring to Figures 4B and 4C, reference number 450 shows a waveform associated with an interrupt received by the coexistence manager 440 from the C-V2X SDR 412 (e.g., a C-V2X interrupt to DSRC, sometimes called a DSRC interrupt from C-V2X) indicating timing information associated with the next C-V2X transmission, and reference number 452 shows a waveform associated with the C-V2X Tx_On signal asserted during C-V2X transmission. As illustrated, the C-V2X interrupt indicating timing information for the next C-V2X transmission is asserted Xμs before the scheduled time for the C-V2X transmission to begin, and the C-V2X interrupt is deasserted (e.g., goes low) when the C-V2X transmission is complete. Therefore, the coexistence manager 440 may perform one or more actions to manage the coexistence between the DSRC component and the C-V2X component if there is an ongoing DSRC transmission when the coexistence manager 440 receives an interrupt indicating timing information for the next C-V2X transmission, and / or if the coexistence manager 440 needs to start a DSRC transmission after receiving an interrupt indicating timing information for the next C-V2X transmission.

[0060] For example, Figure 4B illustrates various scenarios in which there is an ongoing DSRC transmission when the coexistence manager 440 receives a C-V2X interrupt indicating timing information for the next C-V2X transmission. For example, references 454, 456-1, and 456-2 each illustrate exemplary states of the DSRC Tx_On signal asserted when a C-V2X interrupt is received to indicate timing information for the next C-V2X transmission, indicating that there is an ongoing DSRC transmission when the C-V2X interrupt is received. In general, timing information associated with an ongoing DSRC transmission may be available to the coexistence manager 440 (for example, by monitoring the timing of the DSRC transmission and / or by monitoring any interrupts that the DSRC modem 420 sends to the C-V2X components via the coexistence manager 440). Thus, the coexistence manager 440 can use the timing information associated with the ongoing DSRC transmission and the timing information associated with the next C-V2X transmission to resolve any potential conflicts. For example, reference number 454 illustrates an example where an ongoing DSRC transmission is scheduled to complete before the start time of the next C-V2X transmission. In this case, the action taken by the coexistence manager 440 may be to allow the ongoing DSRC transmission to continue based on the determination that the ongoing DSRC transmission will complete before the start time of the next C-V2X transmission (for example, if the remaining time for the ongoing DSRC transmission is less than Xμs, the DSRC transmission will not conflict with the C-V2X slot structure associated with the next C-V2X transmission, so the DSRC transmission may complete, and the next C-V2X transmission may proceed as scheduled after the completion of the DSRC transmission).

[0061] However, if the remaining time of an ongoing DSRC transmission is Xμs or more, the ongoing DSRC transmission will at least partially overlap with and therefore conflict with the next C-V2X transmission. In such cases, the coexistence manager 440 may need to take one or more actions to manage the coexistence between the conflicting DSRC transmission and the C-V2X transmission. For example, in some cases, the coexistence manager 440 may drop the DSRC transmission (for example, by signaling or controlling the DSRC modem 420 to abort, delay, or requeue the DSRC transmission for a given duration) in response to a determination that the DSRC transmission has a later completion time than the start time of the next C-V2X transmission (for example, the DSRC transmission enters the slot structure associated with the next C-V2X transmission). Alternatively, in some embodiments, the coexistence manager 440 may allow the ongoing DSRC transmission to continue and suppress the C-V2X transmission during the period in which the ongoing DSRC transmission overlaps with the C-V2X transmission. For example, reference number 456-1 illustrates a first scenario in which an ongoing DSRC transmission partially overlaps with the next C-V2X transmission (e.g., the ongoing DSRC transmission completes after the start time of the next C-V2X transmission, but before the completion time of the next C-V2X transmission). In such a case, as shown by reference number 458-1, the coexistence manager 440 may suppress (e.g., blank) the C-V2X transmission only during the period in which the ongoing DSRC transmission overlaps with the C-V2X transmission, and the C-V2X transmission may be allowed to start after the completion of the DSRC transmission. In another example, reference number 456-2 illustrates a second scenario in which an ongoing DSRC transmission completely overlaps with the next C-V2X transmission (e.g., the ongoing DSRC transmission completes after the scheduled completion time of the next C-V2X transmission). In such a case, as shown by reference number 458-2, the coexistence manager 440 may suppress the entire C-V2X transmission.In some embodiments, to suppress any portion of the C-V2X transmission, the coexistence manager 440 may use a digital-to-analog converter (DAC) blanking circuit to blank all DAC inputs in the C-V2X SDR412 during periods when an ongoing DSRC transmission overlaps with the C-V2X transmission. For example, the coexistence manager 440 may suppress the C-V2X transmission (e.g., by blanking the DAC inputs of the C-V2X SDR412) while a DSRC interrupt sent by the DSRC modem 420 to the C-V2X components is asserted.

[0062] As an addition or alternative, Figure 4C illustrates various scenarios in which the coexistence manager 440 needs to initiate a DSRC transmission after receiving a C-V2X interrupt indicating timing information for the next C-V2X transmission. As described herein, the coexistence manager 440 may take actions to manage the coexistence between the DSRC transmission and the next C-V2X transmission based on the duration of the DSRC transmission and / or the priority associated with the DSRC transmission. For example, if the DSRC transmission can be completed before the scheduled start time of the next C-V2X transmission, the coexistence manager 440 may allow the DSRC transmission to complete. However, if the DSRC transmission does not complete until after the scheduled start time of the next C-V2X transmission, the coexistence manager 440 may need to delay or suppress one of the conflicting transmissions. For example, referring to Figure 4C, reference no. 460 illustrates a scenario in which the DSRC transmission does not complete until after the scheduled start time of the next C-V2X transmission. Therefore, as indicated by reference number 462, DSRC transmission may be delayed until after the C-V2X transmission is completed. Furthermore, reference number 464 indicates the state of the DSRC interrupt that the DSRC modem 420 sends to the C-V2X components via the coexistence manager 440 when a DSRC transmission is being performed. For example, the DSRC transmission may be requeued at a time after the C-V2X transmission is completed, and while the DSRC transmission is delayed, the DSRC receive operation may continue, and therefore the DSRC modem 420 may continue to acquire clear channel assessment (CCA) measurements while the DSRC transmission is delayed. Thus, the DSRC modem 420 may then determine whether to perform the DSRC transmission when the DSRC transmission is requeued, based on the CCA measurements acquired while the DSRC transmission was delayed.

[0063] Generally, when a DSRC transmission is delayed, the coexistence manager 440 may determine the duration for which the DSRC transmission should be delayed based on the packet content of the DSRC transmission, which may be useful when a C-V2X component needs to transmit across multiple consecutive slots. For example, to enable C-V2X transmissions across multiple consecutive slots, a DSRC transmission with a lower priority may be delayed for a longer duration. Additionally or alternatively, if a DSRC transmission has a higher priority (e.g., the DSRC transmission carries an acknowledgment or other message that must be sent immediately), the coexistence manager 440 may execute the DSRC transmission and suppress the C-V2X transmission (e.g., by blanking the DAC input of the C-V2X SDR412) during any period in which the DSRC transmission overlaps with the C-V2X transmission. In such a case, both the C-V2X interrupt to the DSRC modem 420 and the DSRC interrupt to the C-V2X component will be high, and C-V2X transmission may be suppressed while both the C-V2X interrupt to the DSRC modem 420 and the DSRC interrupt to the C-V2X component are high (for example, for overlapping durations).

[0064] In some embodiments, in addition to, or instead of, managing coexistence based on interrupts indicating timing information for DSRC and C-V2X transmissions, the coexistence manager 440 may suppress or delay DSRC transmissions by leaking transmission power from the C-V2X transmission path to the DSRC reception path. For example, referring to Figure 4D, a communication system supporting DSRC and C-V2X may include a hardware leakage path 470 from the C-V2X transmission path to the DSRC reception path. In this case, the coexistence manager 440 may monitor the respective transmission power levels on the DSRC transmission path and the C-V2X transmission path and control power leakage on the hardware leakage path 470 from the C-V2X transmission path to the DSRC reception path according to the respective transmission power levels. For example, when the respective transmit power levels indicate that a C-V2X component is transmitting and a DSRC component is in receive mode, the coexistence manager 440 may leak transmit power from the C-V2X transmit path to the DSRC receive path to delay or suppress any DSRC transmit that may need to be initiated while a C-V2X transmit is in progress. Additionally or alternatively, as shown in Figure 4D, the coexistence manager 440 may monitor the DSRC Tx_On signal, the DSRC Rx_On signal, the C-V2X Tx_On signal, and / or the C-V2X Rx_On signal to determine the current state of the C-V2X and DSRC components at any given time. In either case, as shown by reference numbers 472 and 474, the coexistence manager 440 may determine when a C-V2X transmission is in progress and may leak transmit power from the C-V2X transmission path to the DSRC reception path until the transmit power level and / or the C-V2X Tx_On signal or C-V2X Rx_On signal indicates that the C-V2X component is not transmitting. For example, the coexistence manager 440 may leak sufficient transmit power from the C-V2X transmission path to the DSRC reception path to satisfy (e.g., exceed) a threshold associated with the busy state of the DSRC wireless channel (e.g., to ensure that the CCA measurement indicates a busy state, and as a result, the DSRC modem 420 delays any DSRC transmissions that occur while a C-V2X transmission is in progress).Furthermore, in some embodiments, the coexistence manager 440 may dynamically adjust the attenuation level on the hardware leakage path 470 to ensure that the transmitted power leaked into the DSRC receiving path is sufficient to satisfy a threshold associated with the busy state of the DSRC wireless channel. For example, in some cases (e.g., low-power C-V2X transmission), the transmitted power leaked from the C-V2X transmission path to the DSRC receiving path may be lower than a threshold, thereby allowing the coexistence manager 440 to adjust the attenuation level on the hardware leakage path 470 based on the transmitted power level on the C-V2X transmission path.

[0065] As described above, Figures 4A to 4D are provided as examples. Other examples may differ from those described with respect to Figures 4A to 4D. For example, although not shown in Figure 4A or 4D, the cellular modem 410 may be coupled to a wide area network (WAN) SDR that can provide a cellular RFFE associated with an antenna subsystem separate from the two antennas used by the C-V2X and DSRC components.

[0066] Figure 5 shows an exemplary process 500 associated with the coexistence of different automotive RATs. The exemplary process 500 is an example of an operation performed by a UE (e.g., UE120) or a component of the UE (e.g., coexistence manager 140 and / or coexistence manager 440) that is associated with managing the coexistence of different automotive RATs.

[0067] As shown in Figure 5, in some embodiments, process 500 may include receiving an interrupt signal transmitted from a first component associated with a first automotive RAT (e.g., C-V2X SDR412 shown in Figure 4) to a second component associated with a second automotive RAT (e.g., DSRC modem 420 shown in Figure 4) to indicate a first timing information associated with the next transmission by the first component associated with the first automotive RAT (block 510). For example, a UE (e.g., using coexistence managers 140 / 440 and / or interrupt handler component 708 shown in Figure 7) may receive an interrupt signal transmitted from a first component associated with a first automotive RAT to a second component associated with a second automotive RAT to indicate a first timing information associated with the next transmission by the first component associated with the first automotive RAT, as described above.

[0068] As further shown in Figure 5, in some embodiments, process 500 may include monitoring second timing information associated with transmissions by a second component associated with a second automotive RAT (block 520). For example, the UE (using, for example, coexistence managers 140 / 440 and / or interrupt handler component 708 shown in Figure 7) may monitor second timing information associated with transmissions by a second component associated with a second automotive RAT, as described above.

[0069] As further shown in Figure 5, in some embodiments, process 500 may include performing actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, according to first timing information associated with the next transmission by the first component associated with the first automotive RAT and second timing information associated with the transmission by the second component associated with the second automotive RAT (block 530). For example, the UE (e.g., using coexistence managers 140 / 150 and / or interrupt handler component 708 shown in Figure 7) may perform actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, according to first timing information associated with the next transmission by the first component associated with the first automotive RAT and second timing information associated with the transmission by the second component associated with the second automotive RAT, as described above.

[0070] Process 500 may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below and / or in relation to one or more other processes described elsewhere in this specification.

[0071] In the first embodiment, transmission by the second component is in progress while an interrupt signal is being sent to the second component.

[0072] In the second aspect, either alone or in combination with the first aspect, the action permits the completion of the transmission by the second component in response to a determination that the transmission by the second component has an earlier completion time than the start time of the next transmission by the first component.

[0073] In the third aspect, the action drops the transmission by the second component either alone or in combination with one or more of the first and second aspects, in response to a determination that the transmission by the second component has a completion time later than the start time of the next transmission by the first component.

[0074] In the fourth aspect, the action, either alone or in combination with one or more of the first to third aspects, is to assert an interrupt to allow the second component to complete a transmission and to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component.

[0075] In the fifth embodiment, the transmission by the second component is scheduled either alone or in combination with one or more of the first to fourth embodiments, after an interrupt signal has been received.

[0076] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the action performs a transmission by the second component in response to a determination that the transmission by the second component has an earlier completion time than the start time of the next transmission by the first component.

[0077] In the seventh aspect, the action, either alone or in combination with one or more of the first to sixth aspects, delays the transmission by the second component until the next transmission by the first component is completed.

[0078] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the transmission by the second component is delayed by a duration associated with the packet content included in the transmission by the second component.

[0079] In the ninth aspect, the action, either alone or in combination with one or more of the first to eighth aspects, performs a transmission by the second component and asserts an interrupt to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component, depending on the priority of the transmission by the second component.

[0080] In the tenth embodiment, an interrupt signal is communicated via a GRFC interface between a first component and a second component, either alone or in combination with one or more of the first to ninth embodiments.

[0081] In the eleventh embodiment, an interrupt signal is communicated either alone or in combination with one or more of the first to tenth embodiments via a GPIO interface between the first and second components.

[0082] In the twelfth embodiment, interrupt signals are communicated either alone or in combination with one or more of the first to eleventh embodiments via a two-wire interface between the first and second components.

[0083] In the 13th embodiment, the first component and the second component share one or more antennas, either alone or in combination with one or more of the first to 12th embodiments.

[0084] In the 14th embodiment, either alone or in combination with one or more of the first to 13 embodiments, a first automotive RAT is associated with C-V2X communication, and a second automotive RAT is associated with DSRC.

[0085] Figure 5 shows an exemplary block of process 500, but in some embodiments, process 500 may include additional blocks, fewer blocks, different blocks, or blocks with a configuration different from that shown in Figure 5. Additionally or alternatively, two or more blocks of process 500 may be executed in parallel.

[0086] Figure 6 shows an exemplary process 600 associated with the coexistence of different automotive RATs. The exemplary process 600 is an example in which a UE (e.g., UE120) or a component of the UE (e.g., coexistence manager 140 and / or coexistence manager 440) performs an action associated with the coexistence of different automotive RATs.

[0087] As shown in Figure 6, in some embodiments, process 600 may include monitoring a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT (block 610). For example, a UE (using, for example, coexistence managers 140 / 440 and / or power leakage component 710 shown in Figure 7) may monitor a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT (for example, the C-V2X SDR412 shown in Figure 4), as described above.

[0088] As further shown in Figure 6, in some embodiments, process 600 may include monitoring a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT (block 620). For example, the UE (using, for example, coexistence managers 140 / 440 and / or power leakage component 710 shown in Figure 7) may monitor a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT (for example, a DSRC modem 420 shown in Figure 4), as described above.

[0089] As further shown in Figure 6, in some embodiments, process 600 may include controlling power leakage on the hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component according to a first transmit power level on the first transmit path and a second transmit power level on the second transmit path (block 630). For example, the UE (e.g., using coexistence managers 140 / 440 and / or power leakage component 710 shown in Figure 7) may control power leakage on the hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component according to a first transmit power level on the first transmit path and a second transmit power level on the second transmit path, as described above.

[0090] Process 600 may include additional embodiments, such as any single embodiment or any combination of embodiments, as described below and / or in relation to one or more other processes described elsewhere in this specification.

[0091] In a first embodiment, controlling power leakage on a hardware leakage path includes leaking power from a first transmission path associated with a first component to a receiving path associated with a second component, in response to a first transmit power level indicating that a first component is transmitting and a determination that a second component is in receive mode.

[0092] In a second embodiment, power is leaked from a first transmission path associated with a first component to a receiving path associated with a second component, either alone or in combination with the first embodiment, until the first transmit power level indicates that the first component is not transmitting.

[0093] In the third embodiment, either alone or in combination with one or more of the first and second embodiments, power leakage on a hardware leakage path satisfies a threshold associated with the busy state of the wireless channel associated with the second automotive RAT.

[0094] In the fourth aspect, controlling power leakage on a hardware leakage path, either alone or in combination with one or more of the first to third aspects, includes adjusting the attenuation level on the hardware leakage path according to a first transmit power level to ensure that power leakage on the hardware leakage path meets a threshold.

[0095] In the fifth embodiment, the first component and the second component share one or more antennas, either alone or in combination with one or more of the first to fourth embodiments.

[0096] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, a first automotive RAT is associated with C-V2X communication and a second automotive RAT is associated with DSRC.

[0097] Figure 6 shows an exemplary block of process 600, but in some embodiments, process 600 may include additional blocks, fewer blocks, different blocks, or blocks with a configuration different from that shown in Figure 6. Additionally or alternatively, two or more blocks of process 600 may be executed in parallel.

[0098] Figure 7 shows an exemplary device 700 for managing coexistence between different automotive RATs. The device 700 may be a UE, or a UE may include the device 700. In some embodiments, the device 700 includes a receiving component 702 and a transmitting component 704, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the device 700 may use the receiving component 702 and the transmitting component 704 to communicate with another device 706 (such as a UE, a base station, or another wireless communication device). As further shown, the device 700 may include coexistence managers 140 and / or 440, shown in Figure 7 and described herein as coexistence managers 140 / 440. The communication managers 140 / 440 may include, among other examples, one or more of the interrupt handler component 708 or the power leakage component 710.

[0099] In some embodiments, the device 700 may be configured to perform one or more operations described herein with respect to Figures 4A to 4C and / or Figure 5. Additionally or alternatively, the device 700 may be configured to perform one or more processes described herein, such as process 500 in Figure 5, process 600 in Figure 6, or a combination thereof. In some embodiments, the device 700 and / or one or more components shown in Figure 7 may include one or more components of the UE described with respect to Figures 4A to 4D. Additionally or alternatively, one or more components shown in Figure 7 may be implemented within one or more components described with respect to Figures 4A to 4D. Additionally or alternatively, one or more components of a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-temporary computer-readable medium, which can be executed by a controller or processor to perform the function or operation of that component.

[0100] The receiving component 702 may receive communications from the device 706, such as reference signals, control information, data communications, or a combination thereof. The receiving component 702 may provide the received communications to one or more other components of the device 700. In some embodiments, the receiving component 702 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and provide the processed signals to one or more other components of the device 700. In some embodiments, the receiving component 702 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memory, or a combination thereof, of the UE described in relation to Figure 2.

[0101] The transmitting component 704 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 706. In some embodiments, one or more other components of the device 700 may generate communications and provide these generated communications to the transmitting component 704 for transmission to the device 706. In some embodiments, the transmitting component 704 may perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding) on ​​the generated communications and transmit these processed signals to the device 706. In some embodiments, the transmitting component 704 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memory, or combinations thereof of the UE described in relation to Figure 2. In some embodiments, the transmitting component 704 may be located in the transceiver alongside the receiving component 702.

[0102] The interrupt handler component 708 may receive an interrupt signal from the first component associated with the first automotive RAT to be transmitted to the second component associated with the second automotive RAT, indicating first timing information associated with the next transmission by the first component associated with the first automotive RAT. The interrupt handler component 708 may monitor second timing information associated with the transmission by the second component associated with the second automotive RAT. The interrupt handler component 708 may perform actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, according to the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with the transmission by the second component associated with the second automotive RAT.

[0103] The power leakage component 710 may monitor a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT. The power leakage component 710 may monitor a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT. The power leakage component 710 may control power leakage on the hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component, according to the first transmit power level on the first transmit path and the second transmit power level on the second transmit path.

[0104] The number and configuration of components shown in Figure 7 are provided as an example. In practice, there may be additional components, fewer components, different components, or components with configurations different from those shown in Figure 7. Furthermore, two or more components shown in Figure 7 may be implemented within a single component, or a single component shown in Figure 7 may be implemented as multiple distributed components. Additionally or alternatively, the set of components (one or more) shown in Figure 7 may perform one or more functions that are described as being performed by another set of components shown in Figure 7.

[0105] The following provides an overview of some aspects of this disclosure.

[0106] Embodiment 1: A method for managing wireless communication in a vehicle communication system, performed by a UE, comprising: receiving an interrupt signal transmitted from a first component associated with a first automotive RAT to a second component associated with a second automotive RAT, indicating a first timing information associated with the next transmission by the first component associated with the first automotive RAT; monitoring a second timing information associated with a transmission by the second component associated with the second automotive RAT; and performing actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, in accordance with the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with a transmission by the second component associated with the second automotive RAT. Methods that include...

[0107] Embodiment 2: The method according to Embodiment 1, wherein transmission by the second component is in progress while an interrupt signal is being sent to the second component.

[0108] Embodiment 3: The method according to Embodiment 2, wherein, in response to a determination that a transmission by the second component has an earlier completion time than the start time of the next transmission by the first component, the action is to permit the completion of the transmission by the second component.

[0109] Embodiment 4: The method according to Embodiment 2, wherein the action is to drop the transmission by the second component in response to a determination that the transmission by the second component has a completion time later than the start time of the next transmission by the first component.

[0110] Embodiment 5: The method according to Embodiment 2, wherein the action is to allow the second component to complete a transmission and to assert an interrupt to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component.

[0111] Embodiment 6: The method according to Embodiment 1, wherein the transmission by the second component is scheduled after the interrupt signal has been received.

[0112] Embodiment 7: The method according to Embodiment 6, wherein, in response to a determination that a transmission by the second component has an earlier completion time than the start time of the next transmission by the first component, the action is to perform a transmission by the second component.

[0113] Embodiment 8: The method according to Embodiment 6, wherein the action is to delay the transmission by the second component until the next transmission by the first component is completed.

[0114] Embodiment 9: The method according to Embodiment 8, wherein the transmission by the second component is delayed by a duration associated with the packet content included in the transmission by the second component.

[0115] Embodiment 10: The method according to Embodiment 6, wherein the action is to perform a transmission by a second component and assert an interrupt to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component, depending on the priority of the transmission by the second component.

[0116] Embodiment 11: The method according to any one of embodiments 1 to 10, wherein an interrupt signal is communicated via a GRFC interface between a first component and a second component.

[0117] Embodiment 12: The method according to any one of embodiments 1 to 11, wherein the interrupt signal is communicated via a GPIO interface between the first component and the second component.

[0118] Embodiment 13: The method according to any one of embodiments 1 to 12, wherein the interrupt signal is communicated via a two-wire interface between the first component and the second component.

[0119] Embodiment 14: The method according to any one of Embodiments 1 to 13, wherein the first component and the second component share one or more antennas.

[0120] Embodiment 15: The method according to any one of Embodiments 1 to 14, wherein a first automotive RAT is associated with C-V2X communication and a second automotive RAT is associated with DSRC.

[0121] Embodiment 16: A method for managing wireless communication in a vehicle communication system, performed by a UE, comprising: monitoring a first transmit power level on a first transmit path associated with a first component associated with a first automotive RAT; monitoring a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT; and controlling power leakage on a hardware leakage path from the first transmit path associated with the first component to the receive path associated with the second component, according to the first transmit power level on the first transmit path and the second transmit power level on the second transmit path. Methods that include...

[0122] Embodiment 17: The method of Embodiment 16, wherein controlling power leakage on a hardware leakage path includes leaking power from a first transmission path associated with a first component to a receiving path associated with a second component in response to a first transmit power level indicating that a first component is transmitting and a determination that a second component is in receive mode.

[0123] Embodiment 18: The method of Embodiment 17, wherein power is leaked from a first transmission path associated with a first component to a receiving path associated with a second component until a first transmission power level indicates that the first component is not transmitting.

[0124] Embodiment 19: The method according to Embodiment 17 or 18, wherein power leakage on a hardware leakage path satisfies a threshold associated with the busy state of a wireless channel associated with a second automotive RAT.

[0125] Embodiment 20: The method according to Embodiment 19, wherein controlling power leakage on a hardware leakage path includes adjusting the attenuation level on the hardware leakage path according to a first transmit power level to ensure that power leakage on the hardware leakage path meets a threshold.

[0126] Embodiment 21: The method according to any one of Embodiments 16 to 20, wherein the first component and the second component share one or more antennas.

[0127] Embodiment 22: The method according to any one of Embodiments 16 to 21, wherein a first automotive RAT is associated with C-V2X communication and a second automotive RAT is associated with DSRC.

[0128] Embodiment 23: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor, wherein the instructions cause the device to execute one or more of the methods from Embodiments 1 to 22.

[0129] Embodiment 24: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein one or more processors are configured to perform one or more methods of Embodiments 1 to 22.

[0130] Embodiment 25: An apparatus for wireless communication, comprising at least one means for performing one or more methods of Embodiments 1 to 22.

[0131] Embodiment 26: A non-temporary computer-readable medium storing code for wireless communication, wherein the code includes instructions that can be executed by a processor, and the instructions perform one or more of the methods of Embodiments 1 to 22.

[0132] Embodiment 27: A non-temporary computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions comprises one or more instructions, and when one or more instructions are executed by one or more processors of the device, the device causes the device to execute one or more of the methods of Embodiments 1 to 22.

[0133] The above disclosures are for illustrative and illustrative purposes only, and are not intended to be exhaustive or to limit the forms to those disclosed. Modifications and variations may be made in light of the above disclosures or obtained from the practice of the forms.

[0134] Where used herein, the term “Components” is intended to be interpreted broadly as hardware and / or combinations of hardware and software. “Software” is intended to be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, among many other examples. Where used herein, “Processor” is implemented in hardware and / or combinations of hardware and software. It will become clear that the systems and / or methods described herein can be realized in various forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to these embodiments. Therefore, it will be understood that those skilled in the art can design software and hardware to implement the system and / or method based at least in part on the description herein; thus, the operation and behavior of the system and / or method are described herein without reference to specific software code.

[0135] As used herein, "meets threshold" may mean, depending on the context, that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold.

[0136] Even if certain combinations of features are enumerated in the claims and / or disclosed herein, those combinations are not intended to limit the disclosure of various embodiments. Many of these features may be combined in ways not specifically enumerated in the claims and / or disclosed herein. The disclosure of various embodiments includes each dependent claim in combination with any other claim in the set of claims. Where used herein, the phrase "at least one of" the list of items refers to any combination of those items, including a single member. As an example, “at least one of a, b, or c” is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other sequence of a, b, and c).

[0137] None of the elements, actions, or commands used herein should be construed as essential or mandatory unless expressly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referred to in relation to the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” When only one item is intended, the phrase “only one” or similar words should be used. Also, as used herein, terms such as “has,” “have,” and “having” are open-ended terms that do not limit the elements they modify (for example, an element that “has” A may also have B). Furthermore, unless otherwise specified, the phrase "based on" is intended to mean "at least partially based on." Also, as used herein, the term "or" is intended to be inclusive when used in a series, and may be used interchangeably with "and / or" unless otherwise specified (for example, when used in combination with "either" or "only one of").

Claims

1. A coexistence manager for managing wireless communications in a vehicle communication system, Memory and The memory comprises one or more processors operably coupled to the memory, and the one or more processors An interrupt signal is received from a first component associated with a first automotive radio access technology (RAT) and transmitted to a second component associated with a second automotive RAT, indicating first timing information associated with the next transmission by the first component associated with the first automotive RAT. The second timing information associated with the transmission by the second component associated with the second automotive RAT is monitored. Actions are taken to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, according to the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with the transmission by the second component associated with the second automotive RAT. It is structured in such a way. Coexistence Manager.

2. The coexistence manager according to claim 1, wherein the transmission by the second component is in progress when the interrupt signal is sent to the second component.

3. The coexistence manager according to claim 2, wherein the action permits the completion of the transmission by the second component in response to a determination that the transmission by the second component has an earlier completion time than the start time of the next transmission by the first component.

4. The coexistence manager according to claim 2, wherein, in response to a determination that the transmission by the second component has a completion time later than the start time of the next transmission by the first component, the action is to drop the transmission by the second component.

5. The coexistence manager according to claim 2, wherein the action is to allow the second component to complete the transmission and to assert an interrupt to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component.

6. The coexistence manager according to claim 1, wherein the transmission by the second component is scheduled after the interrupt signal has been received.

7. The coexistence manager according to claim 6, wherein, in response to a determination that the transmission by the second component has an earlier completion time than the start time of the next transmission by the first component, the action is to execute the transmission by the second component.

8. The coexistence manager according to claim 6, wherein the action is to delay the transmission by the second component until the next transmission by the first component is completed.

9. The coexistence manager according to claim 8, wherein the transmission by the second component is delayed by a duration associated with the packet content included in the transmission by the second component.

10. The coexistence manager according to claim 6, wherein the action is to perform the transmission by the second component, and assert an interrupt to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component, depending on the priority of the transmission by the second component.

11. The coexistence manager according to claim 1, wherein the interrupt signal is communicated via a general-purpose radio frequency connection (GRF) interface between the first component and the second component.

12. The coexistence manager according to claim 1, wherein the interrupt signal is communicated via a general-purpose input / output (GPIO) interface between the first component and the second component.

13. The coexistence manager according to claim 1, wherein the interrupt signal is communicated via a two-wire interface between the first component and the second component.

14. The coexistence manager according to claim 1, wherein the first component and the second component share one or more antennas.

15. The coexistence manager according to claim 1, wherein the first automotive RAT is associated with cellular vehicle-to-everything (V2X) communication, and the second automotive RAT is associated with dedicated short-range communication (DSRC).

16. A coexistence manager for managing wireless communications in a vehicle communication system, Memory and The memory comprises one or more processors operably coupled to the memory, and the one or more processors The system monitors the first transmit power level on a first transmit path associated with a first component associated with a first automotive radio access technology (RAT), The second transmit power level on the second transmit path associated with the second component associated with the second automotive RAT is monitored. Controlling power leakage on the hardware leakage path from the first transmission path associated with the first component to the receiving path associated with the second component, according to the first transmission power level on the first transmission path and the second transmission power level on the second transmission path. It is structured in such a way. Coexistence Manager.

17. The coexistence manager according to claim 16, wherein one or more processors are configured to leak power from the first transmit path associated with the first component to the receive path associated with the second component in order to control the power leakage on the hardware leakage path, in response to a first transmit power level indicating that the first component is transmitting and a determination that the second component is in receive mode.

18. The coexistence manager according to claim 17, wherein power is leaked from the first transmission path associated with the first component to the receiving path associated with the second component until the first transmission power level indicates that the first component is not transmitting.

19. The coexistence manager according to claim 17, wherein the power leakage on the hardware leakage path satisfies a threshold associated with the busy state of the wireless channel associated with the second automotive RAT.

20. The coexistence manager according to claim 19, wherein the one or more processors are configured to control the power leakage on the hardware leakage path by adjusting the attenuation level on the hardware leakage path according to the first transmit power level in order to ensure that the power leakage on the hardware leakage path satisfies the threshold.

21. The coexistence manager according to claim 16, wherein the first component and the second component share one or more antennas.

22. The coexistence manager according to claim 16, wherein the first automotive RAT is associated with cellular vehicle-to-everything (V2X) communication, and the second automotive RAT is associated with dedicated short-range communication (DSRC).

23. A method for managing wireless communication in a vehicle communication system, which is performed by user equipment (UE), Receiving an interrupt signal transmitted from a first component associated with a first automotive radio access technology (RAT) to a second component associated with a second automotive RAT, which indicates first timing information associated with the next transmission by the first component associated with the first automotive RAT, Monitoring second timing information associated with transmission by the second component associated with the second automotive RAT, To perform actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, in accordance with the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with the transmission by the second component associated with the second automotive RAT, Methods that include...

24. The method according to claim 23, wherein the transmission by the second component is in progress while the interrupt signal is being sent to the second component.

25. The method according to claim 24, comprising permitting the completion of the transmission by the second component in response to a determination that the transmission by the second component has an earlier completion time than the start time of the next transmission by the first component.

26. The method according to claim 24, comprising dropping the transmission by the second component in response to a determination that the transmission by the second component has a completion time later than the start time of the next transmission by the first component.

27. The method according to claim 24, comprising allowing the second component to complete the transmission and asserting an interrupt to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component.

28. The method according to claim 23, wherein the transmission by the second component is scheduled after the interrupt signal has been received.

29. The method according to claim 28, further comprising executing the transmission by the second component in response to a determination that the transmission by the second component has an earlier completion time than the start time of the next transmission by the first component.

30. The method according to claim 28, comprising delaying the transmission by the second component until the next transmission by the first component is completed.

31. The method according to claim 30, wherein the transmission by the second component is delayed by a duration associated with the packet content included in the transmission by the second component.

32. The method according to claim 28, comprising performing the transmission by the second component, and asserting an interrupt to suppress the next transmission by the first component during the period in which the transmission by the second component conflicts with the next transmission by the first component, depending on the priority of the transmission by the second component.

33. The method according to claim 23, wherein the interrupt signal is communicated via a general-purpose radio frequency connection (GRF) interface between the first component and the second component.

34. The method according to claim 23, wherein the interrupt signal is communicated via a general-purpose input / output (GPIO) interface between the first component and the second component.

35. The method according to claim 23, wherein the interrupt signal is communicated via a two-wire interface between the first component and the second component.

36. The method according to claim 23, wherein the first component and the second component share one or more antennas.

37. The method according to claim 23, wherein the first automotive RAT is associated with cellular vehicle-to-everything (V2X) communication, and the second automotive RAT is associated with dedicated short-range communication (DSRC).

38. A method for managing wireless communication in a vehicle communication system, which is performed by user equipment (UE), Monitoring a first transmit power level on a first transmit path associated with a first component associated with a first automotive radio access technology (RAT), Monitoring the second transmit power level on the second transmit path associated with the second component associated with the second automotive RAT, Controlling power leakage on the hardware leakage path from the first transmission path associated with the first component to the receiving path associated with the second component, according to the first transmission power level on the first transmission path and the second transmission power level on the second transmission path, Methods that include...

39. The method according to claim 38, wherein controlling the power leakage on the hardware leakage path includes leaking power from the first transmission path associated with the first component to the receiving path associated with the second component in response to a first transmission power level indicating that the first component is transmitting and a determination that the second component is in receiving mode.

40. The method according to claim 39, wherein power is leaked from the first transmission path associated with the first component to the receiving path associated with the second component until the first transmission power level indicates that the first component is not transmitting.

41. The method according to claim 39, wherein the power leakage on the hardware leakage path satisfies a threshold associated with the busy state of the wireless channel associated with the second automotive RAT.

42. The method according to claim 41, wherein controlling the power leakage on the hardware leakage path includes adjusting the attenuation level on the hardware leakage path according to the first transmit power level to ensure that the power leakage on the hardware leakage path satisfies the threshold.

43. The method according to claim 38, wherein the first component and the second component share one or more antennas.

44. The method according to claim 38, wherein the first automotive RAT is associated with cellular vehicle-to-everything (V2X) communication, and the second automotive RAT is associated with dedicated short-range communication (DSRC).

45. A non-temporary computer-readable medium for storing a set of instructions for managing wireless communication in a vehicle communication system, wherein the set of instructions is The instruction includes one or more instructions, and when the one or more instructions are executed by one or more processors of the coexistence manager, the coexistence manager, An interrupt signal is transmitted from a first component associated with a first automotive wireless access technology (RAT) to a second component associated with a second automotive RAT, indicating first timing information associated with the next transmission by the first component associated with the first automotive RAT. The second timing information associated with the transmission by the second component associated with the second automotive RAT is monitored. Actions are taken to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, according to the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with the transmission by the second component associated with the second automotive RAT. Non-temporary computer-readable media.

46. A non-temporary computer-readable medium for storing a set of instructions for managing wireless communication in a vehicle communication system, wherein the set of instructions is The instruction includes one or more instructions, and when the one or more instructions are executed by one or more processors of the coexistence manager, the coexistence manager, The system monitors the first transmit power level on a first transmit path associated with a first component associated with a first automotive radio access technology (RAT), The second transmit power level on the second transmit path associated with the second component associated with the second automotive RAT is monitored. The power leakage on the hardware leakage path from the first transmission path associated with the first component to the receiving path associated with the second component is controlled according to the first transmission power level on the first transmission path and the second transmission power level on the second transmission path. Non-temporary computer-readable media.

47. A device for managing wireless communication in a vehicle communication system, Means for receiving an interrupt signal transmitted from a first component associated with a first automotive radio access technology (RAT) to a second component associated with a second automotive RAT, which indicates first timing information associated with the next transmission by the first component associated with the first automotive RAT, means for monitoring second timing information associated with transmission by the second component associated with the second automotive RAT, Means for performing actions to manage the coexistence between the next transmission by the first component associated with the first automotive RAT and the transmission by the second component associated with the second automotive RAT, in accordance with the first timing information associated with the next transmission by the first component associated with the first automotive RAT and the second timing information associated with the transmission by the second component associated with the second automotive RAT, A device equipped with the following features.

48. A device for managing wireless communication in a vehicle communication system, Means for monitoring a first transmit power level on a first transmit path associated with a first component associated with a first automotive radio access technology (RAT), Means for monitoring a second transmit power level on a second transmit path associated with a second component associated with a second automotive RAT, Means for controlling power leakage on a hardware leakage path from the first transmission path associated with the first component to the receiving path associated with the second component, according to the first transmission power level on the first transmission path and the second transmission power level on the second transmission path, A device equipped with the following features.

Images