Patent ID: 12213124

DETAILED DESCRIPTION

FIG.1Ais a diagram illustrating an example communications system100in which one or more disclosed embodiments may be implemented. The communications system100may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system100may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems100may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

As shown inFIG.1A, the communications system100may include wireless transmit/receive units (WTRUs)102a,102b,102c,102d, a radio access network (RAN)104, a core network (CN)106, a public switched telephone network (PSTN)108, the Internet110, and other networks112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs102a,102b,102c,102dmay be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs102a,102b,102c,102d, any of which may be referred to as a station (STA), may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs102a,102b,102cand102dmay be interchangeably referred to as a UE.

The communications systems100may also include a base station114aand/or a base station114b. Each of the base stations114a,114bmay be any type of device configured to wirelessly interface with at least one of the WTRUs102a,102b,102c,102dto facilitate access to one or more communication networks, such as the CN106, the Internet110, and/or the other networks112. By way of example, the base stations114a,114bmay be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations114a,114bare each depicted as a single element, it will be appreciated that the base stations114a,114bmay include any number of interconnected base stations and/or network elements.

The base station114amay be part of the RAN104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like. The base station114aand/or the base station114bmay be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station114amay be divided into three sectors. Thus, in one embodiment, the base station114amay include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station114amay employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

The base stations114a,114bmay communicate with one or more of the WTRUs102a,102b,102c,102dover an air interface116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface116may be established using any suitable radio access technology (RAT).

More specifically, as noted above, the communications system100may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station114ain the RAN104and the WTRUs102a,102b,102cmay implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface116using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).

In an embodiment, the base station114aand the WTRUs102a,102b,102cmay implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface116using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).

In an embodiment, the base station114aand the WTRUs102a,102b,102cmay implement a radio technology such as NR Radio Access, which may establish the air interface116using NR.

In an embodiment, the base station114aand the WTRUs102a,102b,102cmay implement multiple radio access technologies. For example, the base station114aand the WTRUs102a,102b,102cmay implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs102a,102b,102cmay be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).

In other embodiments, the base station114aand the WTRUs102a,102b,102cmay implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

The base station114binFIG.1Amay be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station114band the WTRUs102c,102dmay implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station114band the WTRUs102c,102dmay implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station114band the WTRUs102c,102dmay utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown inFIG.1A, the base station114bmay have a direct connection to the Internet110. Thus, the base station114bmay not be required to access the Internet110via the CN106.

The RAN104may be in communication with the CN106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs102a,102b,102c,102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN106may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown inFIG.1A, it will be appreciated that the RAN104and/or the CN106may be in direct or indirect communication with other RANs that employ the same RAT as the RAN104or a different RAT. For example, in addition to being connected to the RAN104, which may be utilizing a NR radio technology, the CN106may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN106may also serve as a gateway for the WTRUs102a,102b,102c,102dto access the PSTN108, the Internet110, and/or the other networks112. The PSTN108may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet110may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks112may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks112may include another CN connected to one or more RANs, which may employ the same RAT as the RAN104or a different RAT.

Some or all of the WTRUs102a,102b,102c,102din the communications system100may include multi-mode capabilities (e.g., the WTRUs102a,102b,102c,102dmay include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU102cshown inFIG.1Amay be configured to communicate with the base station114a, which may employ a cellular-based radio technology, and with the base station114b, which may employ an IEEE 802 radio technology.

FIG.1Bis a system diagram illustrating an example WTRU102. As shown inFIG.1B, the WTRU102may include a processor118, a transceiver120, a transmit/receive element122, a speaker/microphone124, a keypad126, a display/touchpad128, non-removable memory130, removable memory132, a power source134, a global positioning system (GPS) chipset136, and/or other peripherals138, among others. It will be appreciated that the WTRU102may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

The processor118may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor118may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU102to operate in a wireless environment. The processor118may be coupled to the transceiver120, which may be coupled to the transmit/receive element122. WhileFIG.1Bdepicts the processor118and the transceiver120as separate components, it will be appreciated that the processor118and the transceiver120may be integrated together in an electronic package or chip.

The transmit/receive element122may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station114a) over the air interface116. For example, in one embodiment, the transmit/receive element122may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element122may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element122may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element122may be configured to transmit and/or receive any combination of wireless signals.

Although the transmit/receive element122is depicted inFIG.1Bas a single element, the WTRU102may include any number of transmit/receive elements122. More specifically, the WTRU102may employ MIMO technology. Thus, in one embodiment, the WTRU102may include two or more transmit/receive elements122(e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface116.

The transceiver120may be configured to modulate the signals that are to be transmitted by the transmit/receive element122and to demodulate the signals that are received by the transmit/receive element122. As noted above, the WTRU102may have multi-mode capabilities. Thus, the transceiver120may include multiple transceivers for enabling the WTRU102to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

The processor118of the WTRU102may be coupled to, and may receive user input data from, the speaker/microphone124, the keypad126, and/or the display/touchpad128(e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor118may also output user data to the speaker/microphone124, the keypad126, and/or the display/touchpad128. In addition, the processor118may access information from, and store data in, any type of suitable memory, such as the non-removable memory130and/or the removable memory132. The non-removable memory130may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory132may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor118may access information from, and store data in, memory that is not physically located on the WTRU102, such as on a server or a home computer (not shown).

The processor118may receive power from the power source134, and may be configured to distribute and/or control the power to the other components in the WTRU102. The power source134may be any suitable device for powering the WTRU102. For example, the power source134may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

The processor118may also be coupled to the GPS chipset136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU102. In addition to, or in lieu of, the information from the GPS chipset136, the WTRU102may receive location information over the air interface116from a base station (e.g., base stations114a,114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU102may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

The processor118may further be coupled to other peripherals138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals138may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals138may include one or more sensors. The sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.

The WTRU102may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor118). In an embodiment, the WTRU102may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).

FIG.10is a system diagram illustrating the RAN104and the CN106according to an embodiment. As noted above, the RAN104may employ an E-UTRA radio technology to communicate with the WTRUs102a,102b,102cover the air interface116. The RAN104may also be in communication with the CN106.

The RAN104may include eNode-Bs160a,160b,160c, though it will be appreciated that the RAN104may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs160a,160b,160cmay each include one or more transceivers for communicating with the WTRUs102a,102b,102cover the air interface116. In one embodiment, the eNode-Bs160a,160b,160cmay implement MIMO technology. Thus, the eNode-B160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU102a.

Each of the eNode-Bs160a,160b,160cmay be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown inFIG.10, the eNode-Bs160a,160b,160cmay communicate with one another over an X2 interface.

The CN106shown inFIG.10may include a mobility management entity (MME)162, a serving gateway (SGW)164, and a packet data network (PDN) gateway (PGW)166. While the foregoing elements are depicted as part of the CN106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

The MME162may be connected to each of the eNode-Bs162a,162b,162cin the RAN104via an S1 interface and may serve as a control node. For example, the MME162may be responsible for authenticating users of the WTRUs102a,102b,102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs102a,102b,102c, and the like. The MME162may provide a control plane function for switching between the RAN104and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.

The SGW164may be connected to each of the eNode Bs160a,160b,160cin the RAN104via the S1 interface. The SGW164may generally route and forward user data packets to/from the WTRUs102a,102b,102c. The SGW164may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs102a,102b,102c, managing and storing contexts of the WTRUs102a,102b,102c, and the like.

The SGW164may be connected to the PGW166, which may provide the WTRUs102a,102b,102cwith access to packet-switched networks, such as the Internet110, to facilitate communications between the WTRUs102a,102b,102cand IP-enabled devices.

The CN106may facilitate communications with other networks. For example, the CN106may provide the WTRUs102a,102b,102cwith access to circuit-switched networks, such as the PSTN108, to facilitate communications between the WTRUs102a,102b,102cand traditional land-line communications devices. For example, the CN106may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN106and the PSTN108. In addition, the CN106may provide the WTRUs102a,102b,102cwith access to the other networks112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.

Although the WTRU is described inFIGS.1A-1Das a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

In representative embodiments, the other network112may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control/Machine-Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.

FIG.1Dis a system diagram illustrating the RAN104and the CN106according to an embodiment. As noted above, the RAN104may employ an NR radio technology to communicate with the WTRUs102a,102b,102cover the air interface116. The RAN104may also be in communication with the CN106.

The RAN104may include gNBs180a,180b,180c, though it will be appreciated that the RAN104may include any number of gNBs while remaining consistent with an embodiment. The gNBs180a,180b,180cmay each include one or more transceivers for communicating with the WTRUs102a,102b,102cover the air interface116. In one embodiment, the gNBs180a,180b,180cmay implement MIMO technology. For example, gNBs180a,108bmay utilize beamforming to transmit signals to and/or receive signals from the gNBs180a,180b,180c. Thus, the gNB180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU102a. In an embodiment, the gNBs180a,180b,180cmay implement carrier aggregation technology. For example, the gNB180amay transmit multiple component carriers to the WTRU102a(not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs180a,180b,180cmay implement Coordinated Multi-Point (CoMP) technology. For example, WTRU102amay receive coordinated transmissions from gNB180aand gNB180b(and/or gNB180c).

The WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cusing transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cusing subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

The gNBs180a,180b,180cmay be configured to communicate with the WTRUs102a,102b,102cin a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cwithout also accessing other RANs (e.g., such as eNode-Bs160a,160b,160c). In the standalone configuration, WTRUs102a,102b,102cmay utilize one or more of gNBs180a,180b,180cas a mobility anchor point. In the standalone configuration, WTRUs102a,102b,102cmay communicate with gNBs180a,180b,180cusing signals in an unlicensed band. In a non-standalone configuration WTRUs102a,102b,102cmay communicate with/connect to gNBs180a,180b,180cwhile also communicating with/connecting to another RAN such as eNode-Bs160a,160b,160c. For example, WTRUs102a,102b,102cmay implement DC principles to communicate with one or more gNBs180a,180b,180cand one or more eNode-Bs160a,160b,160csubstantially simultaneously. In the non-standalone configuration, eNode-Bs160a,160b,160cmay serve as a mobility anchor for WTRUs102a,102b,102cand gNBs180a,180b,180cmay provide additional coverage and/or throughput for servicing WTRUs102a,102b,102c.

Each of the gNBs180a,180b,180cmay be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF)184a,184b, routing of control plane information towards Access and Mobility Management Function (AMF)182a,182band the like. As shown inFIG.1D, the gNBs180a,180b,180cmay communicate with one another over an Xn interface.

The CN106shown inFIG.1Dmay include at least one AMF182a,182b, at least one UPF184a,184b, at least one Session Management Function (SMF)183a,183b, and possibly a Data Network (DN)185a,185b. While the foregoing elements are depicted as part of the CN106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

The AMF182a,182bmay be connected to one or more of the gNBs180a,180b,180cin the RAN104via an N2 interface and may serve as a control node. For example, the AMF182a,182bmay be responsible for authenticating users of the WTRUs102a,102b,102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF183a,183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF182a,182bin order to customize CN support for WTRUs102a,102b,102cbased on the types of services being utilized WTRUs102a,102b,102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like. The AMF182a,182bmay provide a control plane function for switching between the RAN104and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

The SMF183a,183bmay be connected to an AMF182a,182bin the CN106via an N11 interface. The SMF183a,183bmay also be connected to a UPF184a,184bin the CN106via an N4 interface. The SMF183a,183bmay select and control the UPF184a,184band configure the routing of traffic through the UPF184a,184b. The SMF183a,183bmay perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

The UPF184a,184bmay be connected to one or more of the gNBs180a,180b,180cin the RAN104via an N3 interface, which may provide the WTRUs102a,102b,102cwith access to packet-switched networks, such as the Internet110, to facilitate communications between the WTRUs102a,102b,102cand IP-enabled devices. The UPF184,184bmay perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.

The CN106may facilitate communications with other networks. For example, the CN106may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN106and the PSTN108. In addition, the CN106may provide the WTRUs102a,102b,102cwith access to the other networks112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs102a,102b,102cmay be connected to a local DN185a,185bthrough the UPF184a,184bvia the N3 interface to the UPF184a,184band an N6 interface between the UPF184a,184band the DN185a,185b.

In view ofFIGS.1A-1D, and the corresponding description ofFIGS.1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU102a-d, Base Station114a-b, eNode-B160a-c, MME162, SGW164, PGW166, gNB180a-c, AMF182a-b, UPF184a-b, SMF183a-b, DN185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.

The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

Below is a list of definitions and abbreviations which may be used in the description provided herein.3GPP Third Generation Partnership Project5G 5thGenerationAOA Angle of ArrivalCSI Channel State InformationCSI-RS Channel State Information Reference SignalDCI Downlink Control InformationFR1 Frequency Range 1gNB NR NodeBMAC Medium Access ControlMAC-CE MAC Control ElementMCS Modulation and Coding SchemeNR New RadioOAM Operation, Administration and MaintenancePDCCH Physical Downlink Control ChannelPDSCH Physical Downlink Shared ChannelPUSCH Physical uplink Shared ChannelPHY Physical LayerRADAR Radio Detection and RangingPRB Physical Resource BlockRRC Radio Resource ControlSINR Signal to Interference plus Noise RatioSSB SS/PBCH blockTPC Transmit Power ControlUE User Equipment

A salient feature of 5G NR is its intrinsic beam-based design and massive MIMO. Examples include the introduction of the SSB (Synchronization Signal Block) beam for initial access and the use of CSI-RS for beam refinement. The beam-based design allows more focused transmission and reception of the signal while reducing the resulting interference in other directions. In this regard, the focused beam emanated from the gNB may result in significant interference to radar when it is pointing in the radar antenna direction, as well as receiving significant interference from the radar when the radar is pointing at the gNB.

In addition, the interference from airborne radar is also highly directional and highly dynamic since the radar beam can sweep in both azimuth direction and elevation direction. A coexistence strategy needs to efficiently manage the dynamic interaction between the beam-based NR system and highly directional high power radar interference to ensure that the interference level from NR to radar is kept at an acceptably low level to meet the mandate from the radar operator, while managing the interference from the radar to the NR system to maintain robust and efficient NR operation.

When a 5G NR system coexists with an incumbent radar operator, it is imperative to ensure that the interference level from NR to radar is kept at an acceptably low level, while managing the interference from the radar to the NR system to maintain the NR operation. The level of interference from radar to a gNB (and its associated UEs) depends on the distance (among other factors such as terrain) between the radar and the gNB.

Since the effective radiated power of the radar is much larger than that of the gNB and the UE, it is expected that when an airborne radar is approaching the NR system from far away, there will be a period when the radar interference to gNB is significant enough to affect NR system operation but the aggregate NR interference to the radar is still below an acceptable threshold. During this period, the main coexistence strategy is to mitigate the interference from the radar.

As the airborne radar further approaches the gNB, the interference from the gNB and/or UE to the radar can become unacceptably high. In this situation, coexistence strategy also needs to ensure the NR system does not create harmful interference to the radar while continuing to operate at a degraded capacity.

An effective way to mitigate the interference from the radar is to perform beam nulling toward the radar direction while pointing the main beam to the targeted UEs. Example beam nulling approaches include null steering or zero-forcing. As a result, the radar interference to the NR system can be mitigated for the NR uplink operation.

In embodiments, beam nulling can be performed in the azimuth direction when the azimuth direction of the UE (relative to its serving gNB) is not very close to the azimuth direction of the radar (relative to the same gNB), or in the elevation direction when the elevation direction of the UE is not very close to the elevation direction of the radar. Otherwise, the desired signal strength will also be significantly reduced when attempting to null out the radar interference.

When the airborne radar is far away, it is expected that the elevation angle of the radar (as measured from the ground) is very close zero. In the NR system, UEs near the cell edge will have a much smaller elevation angle (relative to its serving gNB) than those close to the cell center. In this regard, only UEs in the inner cell region may be subject to effective beam nulling in the elevation direction. Therefore, for UEs in the outer cell region, only azimuth beam nulling should be performed, while for UEs in the inner cell region, beaming nulling can be performed in either azimuth, elevation or simultaneously in both azimuth and elevation direction to achieve the best nulling results. In this regard, it would be beneficial for gNB to automatically identify whether a UE is in the inner cell region or outer cell region to facilitate the most efficient beam nulling strategy.

As the airborne radar further approaches the gNB, the interference from the gNB to the radar becomes unacceptable without additional mitigation measures, and the interference from the radar to the NR system becomes even stronger. In certain embodiments, one strategy is to avoid the mutual interference between NR system and radar via restricted scheduling (a.k.a. PRB blanking) over the detected radar sweeping bandwidth.

However, the interference from radar to the NR system can be so strong that not only the radar signal within the radar sweeping bandwidth can interfere with the NR system, but the radar signal outside of the radar sweeping bandwidth can also introduce significant interference to the NR system. In this case, PRB blanking on the radar sweeping bandwidth is not sufficient to support NR coexistence with radar. Additional mitigation steps need to be taken to alleviate the interference from the radar to the NR system.

In embodiments the afore-mentioned beam nulling strategy can also be applied on the PRBs with detected radar interference outside of the radar sweeping bandwidth. On the uplink, beam nulling can be applied to reduce the interference from the radar on any affected PRBs (outside of the blanked PRBs). In addition, beam nulling can also be used to reduce the interference from gNB to the radar, as needed. Note that the interference from the UE to radar outside of the detected radar sweeping bandwidth is assumed to be of secondary concern, due to its presumably less transmission power.

In embodiments, a tired SSB approach can help facilitate efficient beam nulling and restricted scheduling/PRB blanking by differentiating the inner cell UEs versus outer cell UEs, and the proximity of azimuth direction of any UE to the azimuth angle of arrival direction of the radar.

In addition to beam nulling and restricted scheduling/PRB blanking, several other radio resource management procedures can also benefit from the tiered SSB architecture.

Due to the much smaller path loss, UEs in the inner tier SSB are more likely to have extra power headroom that can be used to overcome radar interference. The additional power transmitted from the UEs in the inner SSB tier should not create significant additional inter-cell interference, due to the relative long distance from inner tier UEs to other gNBs. gNBs can utilize this property to employ a tiered uplink power control strategy. On the other hand, for UEs in the outer SSB tier, radio resource management features such as PUSCH aggregation can be employed to mitigate radar interference. In addition, a more conservative MCS can be selected during link adaption to further improve the robustness of the wireless radio link.

Similarly, on the downlink, the corresponding radio resource management strategy such as lower MCS, PDSCH aggregation, and more conservative PDCCH aggregation level can be used to combat radar interference. Due to the much smaller pathloss, UEs in the inner SSB tier will receive higher power on all downlink channels than those in the outer SSB tier. As a result, the amount of overhead required to exercise the above radio resource management strategy for link robustness can be reduced for the UEs in the inner SSB UEs to achieve higher throughput.

Tiered SSB Framework

In embodiments, a tiered-SSB framework for radar coexistence is provided wherein the NR SSB beams are structured into multiple tiers to facilitate efficient radio resource management during radar coexistence. In embodiments, a tier corresponds with a particular elevation angle which in turn corresponds to a different coverage radius in a cell. In embodiments, the azimuth beamwidth of different tiers is set independently whereas the azimuth beamwidth within each tier is nominally the same. In embodiments, SSB beams in the inner tier(s) are constructed with a null in the (near) horizontal direction for radar coexistence. UEs in the inner SSB tier that uses a wider SSB beamwidth further applies NR beam management procedure 2 (P2) to provide refined azimuth resolution of the UE direction (via CSI-RS beams) to facilitate efficient radio resource management during radar coexistence.

In NR, SSB based beam sweeping is used during initial access by the UE to choose the best beam. A UE measures the beam strength by measuring received signal power. The best SSB beam identified by the UE is informed to the gNB. In principle, in embodiments different SSB beams point to different azimuth and/or elevation directions over the full coverage areas of the cell. Four different tiered-SSB beam design examples are illustrated inFIG.2(assuming a total of 8 SSB beams for FR1), wherein each tier corresponds to a different SSB beam elevation angle, and a different elevation angle corresponds to a different coverage radius within a cell.

The first quadrant210is an example of 2-tier SSBs.a. SSB-Tier 1 (Inner SSB tier): SSB0, SSB1b. SSB-Tier 2 (Outer SSB tier): SSB2, SSB3, SSB4, SSB5, SSB6, SSB7

The second quadrant240is an example of 3-tier SSBs.a. SSB-Tier 1 (Inner SSB tier 1): SSB0b. SSB-Tier 2 (Inner SSB tier 2): SSB1, SSB2c. SSB-Tier 3 (Outer SSB tier): SSB3, SSB4, SSB5, SSB6, SSB7

The third quadrant230is a second example of 2-tier SSBs.a. SSB-Tier 1 (Inner SSB tier): SSB0, SSB1, SSB2, SSB3b. SSB-Tier 2 (Outer SSB tier): SSB4, SSB5, SSB6, SSB7

The fourth quadrant220is a third example of 2-tier SSBs.a. SSB-Tier 1 (Inner SSB tier): SSB0b. SSB-Tier 2 (Outer SSB tier): SSB1, SSB2, SSB3, SSB4, SSB5, SSB6, SSB7

In embodiments, the azimuth beamwidth in different tiers is configured differently. The azimuth beamwidth within each tier is nominally the same. Based on the best SSB beam reported by the UE, the gNB can identify whether the UE is the inner or outer cell region.

The azimuth direction of the UE within each SSB tier can be identified either directly via the SSB index (as exemplified in the second quadrant240ofFIG.2) or rely on NR CSI-RS based beam management procedure 2 (P2). For example, the beam refinement procedure P2 can be triggered for UEs in the inner SSB tier(s) that contain wide SSB beamwidth (as illustrated in the first, second and forth quadrant ofFIG.2) to help provide refined azimuth resolution to facilitate efficient radio resource management during radar coexistence.

Moreover, since airborne radar can be very far away from the gNB, with elevation angle almost equal to zero relative to the gNB, the SSB beams in the inner tier(s) can be constructed with a null in the (near) horizontal direction to alleviate the interference to the radar, irrespective of the azimuth direction of the radar.

Tiered SSB Based Uplink Radio Resource Management

In embodiments, a tiered SSB framework is used to facilitate efficient uplink radio resource measurement for radar coexistence. Below are several examples.

In a first example, a gNB employs different beam nulling methods to different UEs based on the associated SSB beam index/SSB tier. In embodiments this process is refined by the CSI-RS beam index. Example beam nulling approaches include null steering or zero-forcing.

In a further example, a gNB employs different scheduling policies to different UEs based on the associated SSB beam index/SSB tier. In embodiments this process is refined by the CSI-RS beam index.

In a further example, a gNB employs different uplink link adaptation policies to different UEs based on the associated SSB beam index/SSB tier. In embodiments this process is by the CSI-RS beam index. In embodiments, a more aggressive MCS downgrade is used for UEs in the outer SSB tier than those in the inner SSB tier(s) to enhance link robustness during radar coexistence.

In a further example, the gNB employs different uplink power control policies to different UEs based on the associated SSB beam index/SSB tier. In embodiments this process is refined by the CSI-RS beam index. In embodiments a more aggressive uplink power control policy is used for UEs in the inner SSB tier(s) than those in the outer SSB tier to improve uplink throughput during radar coexistence.

In a further example, the gNB employs different PUSCH aggregation policies to different UEs based on the associated SSB beam index/SSB tier. In embodiments this process is refined by the CSI-RS beam index. In embodiments, a more aggressive PUSCH aggregation is used for UEs in the outer SSB tier than those in the inner SSB tier(s) to enhance link robustness during radar coexistence. Examples include wherein multiple PUSCH aggregation levels are configured to the UE via RRC signaling, and wherein the active PUSCH aggregation level may be selected via either MAC-CE or DCI signaling.

A schematic diagram that utilizes the tiered SSB framework to facilitate uplink radio resource management for radar coexistence is illustrated inFIG.3.

The conditions that determine which tier and which SSB a UE will use are shown illustrated inFIG.3.

At a first step310it is determined whether the UE is in the outer SSB tier.

At a next step, either322or324, depending on the outcome of step310, it is determined whether the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) exceeds a predetermined threshold. In embodiments, the angle of arrival (AoA) of the radar signal is estimated by either the gNB or by external sensors. In embodiments, the predetermined azimuth offset threshold is OAM configurable.

After either step322or342it is determined in steps332,334,335and337whether the aggregate NR interference to the radar is deemed unacceptable. In embodiments, the aggregate NR interference to the radar is estimated either by the gNB or by external sensors. In embodiments, the pathloss between the radar and gNB/Cell (including radar antenna gain) is estimated based on the received radar power on the gNB/Cell and the assumed transmit power of the radar. In embodiments, the interference from each cell of a gNB to radar is then estimated based on the transmit power, antenna pattern, geolocation of the cell, and the pathloss between each cell and the radar. In embodiments, the aggregate NR interference to the radar is estimated by summing up the interference from all the cells in the NR system that are currently “illuminated” by the radar interference. The aggregate UE interference to the radar is assumed to be no more than the aggregate gNB/Cell interference to the radar, as a gNB nominally transmits higher power than a UE. There can be many UEs in a cell, in which case they will share the PRB resources of the cell.

If the outcomes of any of steps332,334,335or337is that the aggregate NR interference to the radar is deemed insignificant, at steps342,344,345and347, respectively, it is determined whether the radar interference is affecting NR system operation. In embodiments, the radar interference (e.g., power spectral density) to NR is measured either by the gNB or by external sensors. In embodiments, the measured radar power spectral density is used to estimate the radar sweeping bandwidth and to determine all the PRBs that are currently impacted by the radar (the latter may occur outside of the estimated radar sweeping bandwidth).

The measures taken depending on the outcome of the process described above and inFIG.3, that utilize tiered SSB framework to facilitate uplink radio resource management for radar coexistence is described below.

Step U0(350) is taken in all cases where the radar is not impacting the NR network. In this case, Normal uplink operation is performed in the absence of radar interference.

In the case where steps310,322and332are answered Yes, Steps U1(331) is taken and the following actions are performed: A) Restrict scheduling on uplink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of UE interference to the radar (without assuming specific UE beamforming capabilities). B) Allow the scheduling of remaining PRBs for uplink transmission. C) Apply beam nulling in the azimuth direction on the PRBs with detected radar interference to mitigate the interference from radar to the gNB if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable. D) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Step U1(331) can be OAM configurable. E) Apply PUSCH aggregation to further mitigate the impact of radar interference. The PUSCH aggregation factor to be used in Step U1(331) can be OAM configurable.

In the case where steps310and322are answered Yes, but step332is answered no, Step U2(342) is taken and the following actions are performed: A) Allow the scheduling of any PRBs for uplink transmission. If initial transmission on PRBs within detected radar sweeping bandwidth fails, optionally retransmit the data outside of the detected radar sweeping bandwidth. B) Apply beam nulling in the azimuth direction on PRBs with detected radar interference to mitigate the interference from radar to the gNB if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Steps U2can be OAM configurable. D) Apply PUSCH aggregation to further mitigate the impact of radar interference. The PUSCH aggregation factor to be used in Steps U2can be OAM configurable.

In the case where steps310is answered yes, step322is answered no and step334is answered yes, Step U3(333) is taken and the following actions are performed: A) Restrict scheduling on uplink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of UE interference to the radar (without assuming specific UE beamforming capabilities) and radar interference to the gNB. B) Allow the scheduling of remaining PRBs for uplink transmission. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Steps U3can be OAM configurable. D) Apply possibly the highest PUSCH aggregation factor to further mitigate the impact of radar interference via time diversity. The PUSCH aggregation factor to be used in Steps U3can be OAM configurable.

In the case where steps310is answered yes, step322is answered no and step334is answered no and step344is answered yes, step U4(343) is taken and the following actions are performed. A) Restrict scheduling on uplink PRBs within the detected radar sweeping bandwidth to mitigate the impact of radar interference to the gNB. B) Allow the scheduling of remaining PRBs for uplink transmission. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Steps U4can be OAM configurable. D) Apply PUSCH aggregation to mitigate the impact of radar interference via time diversity. The PUSCH aggregation factor to be used in Steps U4can be OAM configurable.

In the case where step310is answered no, step324is answered yes and step335is answered yes, step U5(336) is taken and the following actions are performed: A) Restrict scheduling on uplink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of UE interference to the radar (without assuming specific UE beamforming capabilities). B) Allow the scheduling of remaining PRBs for uplink transmission. C) Apply beam nulling in the azimuth and/or elevation direction on the PRBs with detected radar interference to mitigate the interference from radar to the gNB if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable. D) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Steps U5can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. E) Instruct the UEs to transmit higher power (via TPC command) to compensate for the additional SINR margin included in link adaptation or to further improve uplink throughput. The uplink power control target SINR offset to be used in Steps U5can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. F) Apply PUSCH aggregation to further mitigate the impact of radar interference. The PUSCH aggregation factor to be used in Steps U5can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed.

In the case where step310is answered no, step324is answered yes, step335is answered no and step345is answered yes. step U6(346) is taken and the following actions are performed: A) Allow the scheduling of any PRBs for uplink transmission. If initial transmission on PRBs within detected radar sweeping bandwidth fails, optionally retransmit the data outside of the detected radar sweeping bandwidth. B) Apply beam nulling in the azimuth and/or elevation direction on PRBs with detected radar interference to mitigate the interference from radar to the gNB if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable. C) Optionally apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Steps U6can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. D) Instruct the UEs to transmit higher power (via TPC command) to compensate for the additional SINR margin included in link adaptation or to further improve uplink throughput. The uplink power control target SINR offset to be used in Steps U6can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. E) Optionally apply PUSCH aggregation to further mitigate the impact of radar interference. The PUSCH aggregation factor to be used in Steps U6can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed.

In the case where step310is answered no, step324is answered no and step337is answered yes, step U7(338) is taken and the following actions are performed: A) Restrict scheduling on uplink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of UE interference to the radar (without assuming specific UE beamforming capabilities). B) Allow the scheduling of remaining PRBs for uplink transmission. C) Optionally apply beam nulling in the elevation direction on the PRBs with detected radar interference to mitigate the interference from radar to the gNB if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable. D) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Steps U7can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. E) Instruct the UEs to transmit higher power (via TPC command) to compensate for the additional SINR margin included in link adaptation or to further improve uplink throughput. The uplink power control target SINR offset to be used in Steps U7can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. F) Apply PUSCH aggregation to further mitigate the impact of radar interference. The PUSCH aggregation factor to be used in Steps U7can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed.

In the case where step310is answered no, step324is answered no, step337is answered no, and step347is answered yes, step U8(348) is taken and the following actions are performed: A) Allow the scheduling of any PRBs for uplink transmission. If initial transmission on PRBs within detected radar sweeping bandwidth fails, optionally retransmit the data outside of the detected radar sweeping bandwidth. B) Optionally apply beam nulling in the elevation direction on PRBs with detected radar interference to mitigate the interference from radar to the gNB if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing. The additional uplink link adaptation SINR margin to be used in Steps U8can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. D) Instruct the UEs to transmit higher power (via TPC command) to compensate for the additional SINR margin included in link adaptation or to further improve uplink throughput. The uplink power control target SINR offset to be used in Steps U8can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. E) Apply PUSCH aggregation to further mitigate the impact of radar interference. The PUSCH aggregation factor to be used in Steps U8can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed.

Tiered-SSB Based Uplink Beam Nulling

In embodiments, Tiered-SSB based uplink radio resource management is implemented with tiered-SSB to facilitate efficient uplink radio resource management for radar coexistence. Beam nulling is performed toward the radar direction while pointing the main beam to the targeted UEs on any uplink scheduled PRBs that are deemed affected by the radar interference to improve uplink throughput wherein when the offset of the azimuth direction of the UE (relative to its serving gNB based on the index of the associated SSB beam, possibly refined by the CSI-RS beam) and the azimuth direction of the radar (relative to the same gNB) exceeds a predetermined low threshold but is still below a predetermined high threshold for beam nulling. For UEs in the outer SSB tier, apply beam nulling in the azimuth direction to mitigate the impact of radar interference on the gNB. For UEs in the inner SSB tier(s), apply beam nulling in the azimuth and/or elevation direction to mitigate the impact of radar interference on the gNB. When the offset of the azimuth direction of the UE (relative to its serving gNB based on the index the associated SSB beam, possibly refined by the CSI-RS beam) and the azimuth direction of the radar (relative to the same gNB) is below a predetermined low threshold for beam nulling, for UEs in the inner SSB tier(s), apply beam nulling in the elevation direction to mitigate the impact of radar interference on the gNB.

Tiered-SSB Based Uplink Scheduling

If the radar interference is deemed to affect NR system operation but the aggregate NR interference to the radar is deemed insignificant, when the offset between the azimuth direction of the UE (relative to its serving gNB based on the index of the associated SSB beam, possibly refined by the CSI-RS beam) and the azimuth direction of the radar (relative to the same gNB) exceeds a predetermined threshold, allow the scheduling of any PRBs for uplink transmission. If initial transmission on PRBs within detected radar sweeping bandwidth fails, optionally retransmit the data outside of the detected radar sweeping bandwidth. When the offset between the azimuth direction of the UE (relative to its serving gNB based on the index of the associated SSB beam, possibly refined by the CSI-RS beam) and the azimuth direction of the radar (relative to the same gNB) is below a predetermined threshold, for UEs in the inner SSB tier(s), allow the scheduling of any PRBs for uplink transmission. If initial transmission on PRBs within detected radar sweeping bandwidth fails, optionally retransmit the data outside of the detected radar sweeping bandwidth. For UEs in the outer SSB tier, restrict scheduling on uplink PRBs within detected radar sweeping bandwidth to mitigate the impact of radar interference on the gNB and allow the scheduling of remaining PRBs for uplink transmission. If the aggregate NR interference to the radar is deemed unacceptable, restrict scheduling of uplink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of UE interference on the radar (without assuming specific UE beamforming capabilities) and radar interference on the gNB and allow the scheduling of remaining PRBs for uplink transmission.

Tiered-SSB Based Uplink Power Control

In embodiments UEs are instructed to transmit extra power (via the TPC command) based on the index and tier of the SSB beam (possibly refined by the CSI-RS beam) during the period of radar coexistence.

Tiered-SSB Based PUSCH Aggregation

PUSCH aggregation may be employed for UEs based on the index and tier of their associated SSB beams (possibly refined by the CSI-RS beams) during the period of radar coexistence. Multiple PUSCH aggregation factors may be configured to the UE via RRC signaling; the active PUSCH aggregation factor may be selected via either MAC-CE or DCI signaling; and a higher PUSCH aggregation factor may be selected for UEs in the outer SSB tier than those in the inner SSB tier.

Tiered-SSB Based Uplink Link Adaptation

A more robust MCS selection, a.k.a., MCS downgrade (e.g., by including an additional SINR margin during link adaptation) may be employed for UEs based on their associated index and tier of the SSB beams (possibly refined by the CSI-RS beams) during the period of radar coexistence. A higher SINR margin may be employed for the UEs in the outer SSB tier than those in the inner SSB tier to maintain robust connectivity, as UEs in the outer SSB tier suffer much higher pathloss than those in the inner SSB tier and hence have much less power headroom, if any, to transmit extra power to overcome radar interference.

Tiered SSB Based Downlink Radio Resource Management

In embodiments, a tiered SSB framework is used to facilitate efficient downlink radio resource measurement for radar coexistence. Below are several examples.

In embodiments, the gNB employs different beam nulling methods to different UEs based on the associated SSB beam index/SSB tier, possibly refined by the CSI-RS beam index. Example beam nulling approaches may include null steering or zero-forcing.

In embodiments, the gNB employs different scheduling policies to different UEs based on the associated SSB beam index/SSB tier, possibly refined by the CSI-RS beam index.

In embodiments, the gNB employs different downlink link adaptation policies to different UEs based on the associated SSB beam index/SSB tier, possibly refined by the CSI-RS beam index. In embodiments, a more aggressive MCS downgrade is used for UEs in the outer SSB tier than those in the inner SSB tier(s) to enhance link robustness during radar coexistence.

In embodiments, the gNB employs different PDCCH aggregation policies to different UEs based on the associated SSB beam index/SSB tier, possibly refined by the CSI-RS beam index. In embodiments, A higher minimum PDCCH aggregation level is used for UEs in the outer SSB tier than those in the inner SSB tier(s) to enhance link robustness during radar coexistence.

In embodiments, the gNB employs different PDSCH aggregation policies to different UEs based on the associated SSB beam index/SSB tier, possibly refined by the CSI-RS beam index. In embodiments, a more aggressive PDSCH aggregation is used for UEs in the outer SSB tier than those in the inner SSB tier(s) to enhance link robustness during radar coexistence. In embodiments, multiple PDSCH aggregation levels are configured to the UE via RRC signaling. In embodiments, the active PDSCH aggregation level is selected via either MAC-CE or DCI signaling.

A schematic diagram that utilizes the tiered SSB framework to facilitate downlink radio resource management for radar coexistence is illustrated inFIG.4. The conditions that determine which tier and which SSB a UE will use are shown illustrated inFIG.4and are further elaborated as follows:

At step410it is determined whether the UE is in the outer SSB tier.

At steps422or424, depending on the outcome of step410, it is determined whether the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) exceeds a predetermined threshold. In embodiments. the angle of arrival (AoA) of the radar signal is estimated by either the gNB or by external sensors. The predetermined azimuth offset threshold can be OAM configurable.

Depending on the outcome of either steps422or424, at steps432,434,435and437it is determined whether the aggregate NR interference to the radar is deemed unacceptable. In embodiments, the aggregate NR interference to the radar may be estimated either by the gNB or by external sensors. In embodiments, the pathloss between the radar and gNB/Cell (including radar antenna gain) is estimated based on the received radar power on the gNB/Cell and the assumed transmit power of the radar. The interference from each cell of a gNB to radar can then be estimated based on the transmit power, antenna pattern, geolocation of the cell, and the pathloss between each cell and the radar. The aggregate NR interference to the radar can be estimated by the summing up the interference from all the cells in the NR system that are currently “illuminated” by the radar interference. The aggregate UE interference to the radar is assumed to be no more than the aggregate gNB/Cell interference to the radar, as a gNB nominally transmits higher power than a UE. In cases where there are many UEs in a cell, they will share the PRB resources of the cell.

If the aggregate NR interference to the radar is deemed insignificant, as evidenced by a negative result to any of steps431,433,435or437, it is determined in steps442,444,445and447, respectively, whether the radar interference is affecting NR system operation. The radar interference (e.g., power spectral density) to NR may be measured either by the gNB or by external sensors. In embodiments, the measured radar power spectral density is used to estimate the radar sweeping bandwidth and to determine all the PRBs that are currently impacted by the radar (the latter may occur outside of the estimated radar sweeping bandwidth).

A set of example steps, as illustrated inFIG.4, that utilize tiered SSB framework to facilitate downlink radio resource management for radar coexistence is described below.

In the case where radar is not impacting the NR network as shown by negative outcomes to steps442,444,445and447, step DO (450) is performed, which is normal downlink operation.

In the case where step410is answered yes, step422is answered yes and step432is answered yes, step D1is taken and the following actions are performed: A) Restrict scheduling on downlink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of radar interference on the UE and gNB interference to the radar. B) Allow the scheduling of remaining PRBs for downlink transmission. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in Steps D1can be OAM configurable. D) Increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in step D1(431) can be OAM configurable. E) Apply PDSCH aggregation to further mitigate the impact of radar interference via time diversity. The PDSCH aggregation factor to be used in step D1(431) can be OAM configurable. F) Perform beam nulling in the azimuth direction on any PRBs outside of the radar sweeping bandwidth but deemed to impact radar operation to mitigate gNB interference to the radar if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable.

In the case where step410is answered yes, step422is answered yes, step432is answered no and step442is answered yes, step D2(441) is taken and the following actions are performed: A) Restrict scheduling on downlink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of radar interference on the UE. B) Allow the scheduling of PRBs outside of the radar sweeping bandwidth. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in Steps D2can be OAM configurable. D) Increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in Steps D2can be OAM configurable. E) Apply PDSCH aggregation to further mitigate the impact of radar interference via time diversity. The PDSCH aggregation factor to be used in Steps D2can be OAM configurable.

In the case where step410is answered yes, step422is answered no and step434is answered yes, step D3(433) is taken and the following actions are performed: A) Restrict scheduling on downlink PRBs within the detected radar sweeping bandwidth to mitigate the impact of gNB interference on the radar and possible impact of radar interference on the UE (without assuming specific UE beamforming capabilities). B) Allow the scheduling of remaining PRBs for downlink transmission. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in step D3can be OAM configurable. D) Increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in step D3can be OAM configurable. E) Apply possibly the highest PDSCH aggregation factor to further mitigate the impact of radar interference via time diversity. The PDSCH aggregation factor to be used in step D3can be OAM configurable.

In the case where step410is answered yes, step422is answered no, step434is answered no and step444is answered yes, step D4(443) is taken and the following actions are performed: A) Restrict scheduling on downlink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of radar interference on the UE (without assuming specific UE beamforming capabilities). B) Allow the scheduling of any PRBs outside of radar sweeping bandwidth. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in Steps D4can be OAM configurable. D) Increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in step D4can be OAM configurable. E) Apply PDSCH aggregation to further mitigate the impact of radar interference via time diversity. The PDSCH aggregation factor to be used in step D4can be OAM configurable.

In the case where step410is answered no, step424is answered yes and step435is answered yes, step D5(436) is taken and the following actions are performed: A) Restrict scheduling on downlink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of radar interference on the UEs and gNB interference to the radar. B) Allow the scheduling of remaining PRBs for downlink transmission. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in step D5can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. D) Optionally increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in step D5can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. E) Apply PDSCH aggregation to further mitigate the impact of radar interference. The PDSCH aggregation factor to be used in step D5can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. E) Optionally perform beam nulling in the azimuth and/or elevation direction on any downlink PRBs outside of the radar sweeping bandwidth but deemed to impact radar operation to mitigate gNB interference to the radar if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable.

In the case where step410is answered no, step424is answered yes, step435is answered no and step445is answered yes step D6(446) is taken and the following actions are performed: A) Allow the scheduling of any PRBs for downlink transmission. If initial transmission on PRBs within detected radar sweeping bandwidth fails, optionally retransmit the data outside of the detected radar sweeping bandwidth. B) Optionally apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in step D6can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. C) Increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in step D6can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. D) Apply PDSCH aggregation to further mitigate the impact of radar interference. The PDSCH aggregation factor to be used in Steps D6can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed.

In the case where step410is answered no, step424is answered no and step437is answered yes, step D7(438) is taken and the following actions are performed: A) Restrict scheduling on downlink PRBs within the detected radar sweeping bandwidth to mitigate the possible impact of radar interference to the UE and gNB interference to the radar. B) Allow the scheduling of remaining PRBs for downlink transmission. C) Apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in step D7can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. D) Increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in step D7can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. E) Apply PDSCH aggregation to further mitigate the impact of radar interference. The PDSCH aggregation factor to be used in step D7can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. F) Optionally perform beam nulling in the elevation direction on any downlink PRBs outside of the radar sweeping bandwidth but deemed to impact radar operation to mitigate gNB interference to the radar if the offset between the azimuth direction of the SSB/CSI-RS beam associated with the UE (relative to its serving gNB) and the azimuth direction of the radar (relative to the same gNB) is below a second predetermined threshold. The second predetermined azimuth offset threshold can be OAM configurable.

In the case where step410is answered no, step424is answered no, step437is answered no and step447is answered yes, step D8(448) is taken and the following actions are performed: A) Allow the scheduling of any PRBs for downlink transmission. If initial transmission on PRBs within detected radar sweeping bandwidth fails, optionally retransmit the data outside of the detected radar sweeping bandwidth. B) Optionally apply MCS downgrade (e.g., by adding an additional SINR margin in link adaptation) to mitigate the uncertainty of radar interference timing on the CSI report. The additional downlink link adaptation SINR margin to be used in steps D8can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. C) Optionally increase PDCCH aggregation level (or enforce a minimum PDCCH aggregation level) to mitigate the uncertainty of radar interference timing on the CSI report. The minimum PDCCH aggregation level to be used in steps D8can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. D) Optionally apply PDSCH aggregation to further mitigate the impact of radar interference. The PDSCH aggregation factor to be used in steps D8can be OAM configurable. A separate OAM parameter can be provided for each inner SSB tier when multiple inner SSB tiers are constructed. Tiered-SSB Based Downlink Beam Nulling

In embodiments, beam nulling toward the radar direction is performed while pointing the main beam to the targeted UEs on any downlink scheduled PRBs that are deemed to impact radar operation. When the offset of the azimuth direction of the UE (relative to its serving gNB based on the index of the associated SSB beam, possibly refined by the CSI-RS beam) and the azimuth direction of the radar (relative to the same gNB) exceeds a predetermined low threshold, but is still below a predetermined high threshold for beam nulling, for UEs in the outer SSB tier, apply beam nulling in the azimuth direction to alleviate the gNB interference to the radar. For UEs in the inner SSB tier(s), apply beam nulling in the azimuth and/or elevation direction to alleviate the gNB interference to the radar. When the offset between the azimuth direction of the UE (relative to its serving gNB based on the index of the associated SSB beam, possibly refined by the CSI-RS beam) and the azimuth direction of the radar (relative to the same gNB) is below a predetermined low threshold for beam nulling, for UEs in the inner SSB tier(s), apply beam nulling in the elevation direction to alleviate the gNB interference to the radar.

Tiered-SSB Based Downlink Scheduling

If the radar interference is deemed to affect NR system operation but the aggregate NR interference to the radar is deemed insignificant, for UEs in the inner SSB tier, allow the scheduling of any PRBs for downlink transmission. If initial transmission on PRBs within a detected radar sweeping bandwidth fails, in embodiments the system is configured to optionally retransmit the data outside of the detected radar sweeping bandwidth. For UEs in the outer SSB tier, in embodiments, the system is configured to restrict scheduling on downlink PRBs within detected radar sweeping bandwidth to mitigate the possible impact of radar interference on the UE (without assuming specific UE beamforming capabilities) and allow the scheduling of any PRBs outside of radar sweeping bandwidth. If the aggregate NR interference to the radar is deemed unacceptable, the system can be configured to restrict scheduling on downlink PRBs within the detected radar sweeping bandwidth to mitigate the impact of gNB interference on the radar and possible impact of radar interference on the UE (without assuming specific UE beamforming capabilities), irrespective of the tier of the SSB and allow the scheduling of remaining PRBs for downlink transmission.

Tiered-SSB Based PDCCH Aggregation

In embodiments, a PDCCH aggregation level for UEs is selected based on their associated index and tier of the SSB beams (possibly refined by the CSI-RS beams) during the period of radar coexistence. By way of example, a higher PDCCH aggregation level may be employed for the UEs in the outer SSB tier than those in the inner SSB tier and a minimum PDCCH aggregation level may be employed based on the tier of the SSB. In embodiments, a higher minimum PDCCH aggregation level is employed for the UEs in the outer SSB tier than those in the inner SSB tier.

Tiered-SSB Based PDSCH Aggregation

In embodiments, PDSCH aggregation is employed for UEs based on their associated index and tier of the SSB beams (possibly refined by the CSI-RS beams) during the period of radar coexistence wherein: multiple PDSCH aggregation factors are configured to the UE via RRC signaling; in embodiments the active PDSCH aggregation factor is selected via either MAC-CE or DCI signaling; and in embodiments a higher PDSCH aggregation factor is selected for UEs in the outer SSB tier than those in the inner SSB tier.

Tiered-SSB Based Downlink Link Adaptation

In an embodiment, a more robust MCS selection, a.k.a., MCS downgrade (e.g., by including an additional SINR margin during link adaptation) may be employed for UEs based on their associated index and tier of the SSB beams (possibly refined by the CSI-RS beams) during the period of radar coexistence wherein a higher SINR margin is employed for the UEs in the outer SSB tier than those in the inner SSB tier(s) to maintain robust connectivity, as UEs in the outer SSB tier suffer much higher pathloss than those in the inner SSB tier.

Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.