Methods, architectures, devices and systems for sub-band non-overlapping full duplex configuration

Abstract

A program, method, architecture, apparatus, system, apparatus, and computer program product for measurements in a wireless system. A wireless transmit / receive unit (WTRU) for: receiving information indicating an uplink (UL) subband (SB); receiving an indication to perform a measurement on a first set of resource blocks (RBs) and a first set of symbols, wherein the first set of symbols includes a first one or more sub-band non-overlapping full duplex (SBFD) symbols; determining a first measurement value of the RB located in the UL SB in the first group of RBs and at least one additional measurement value of at least one RB located in the UL SB in the first group of RBs under the condition that the first group of RBs comprises the RBs in the UL SB and the RBs except the UL SB; and transmitting a message comprising the first measurement value and the at least one additional measurement value.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application Nos. 63 / 410,723 (filed September 28, 2022), 63 / 421,617 (filed November 2, 2022), and 63 / 464,993 (filed May 9, 2023), which are incorporated herein by reference in their entirety. Background Art

[0003] The present disclosure relates generally to the fields of communications, software, and coding, including, for example, methods, architectures, devices, and systems for measurements in wireless systems. Summary of the invention

[0004] In a first aspect, the present principles relate to a wireless transmit / receive unit (WTRU) configured to: receive information indicating an uplink (UL) subband (SB); receive an indication to perform measurements on a first group of resource blocks (RBs) and a first group of symbols, wherein the first group of symbols includes a first one or more subband non-overlapping full-duplex (SBFD) symbols; determine a first measurement value of RBs in the first group of RBs that are located in the UL SB and at least one additional measurement value of at least one RB in the first group of RBs that are located outside the UL SB, under the condition that the first group of RBs includes RBs in the UL SB and RBs outside the UL SB; and transmit a message including the first measurement value and the at least one additional measurement value.

[0005] In a second aspect, the present invention relates to a method at a wireless transmit / receive unit (WTRU), the method comprising: receiving information indicating an uplink (UL) subband (SB); receiving an indication to perform measurements on a first group of resource blocks (RBs) and a first group of symbols, wherein the first group of symbols comprises a first one or more subband non-overlapping full-duplex (SBFD) symbols; determining a first measurement value of an RB in the first group of RBs located in the UL SB and at least one additional measurement value of at least one RB in the first group of RBs located outside the UL SB, under the condition that the first group of RBs comprises RBs in the UL SB and RBs outside the UL SB; and transmitting a message comprising the first measurement value and the at least one additional measurement value. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the attached drawings. As described in detail, each of the figures in such drawings is an example. Therefore, each of the figures and detailed description should not be regarded as limiting, and other equally effective examples are possible and possible. In addition, the same reference numerals ("labels") in the various figures indicate the same elements, and wherein:

[0007] Figure 1A is a system diagram illustrating an example communication system;

[0008] Figure 1B It shows that it can be Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the communication system is shown;

[0009] Figure 1C It shows that it can be Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system;

[0010] Figure 1D It shows that it can be Figure 1A A system diagram of yet another example RAN and yet another example CN used within the communication system shown;

[0011] Figure 2 The slot format of the normal cyclic prefix according to Table 11.1.1-1 in TS38.213 is shown;

[0012] Figure 3 The NR TDD framework based on FD-gNB and HD-UE in a cell according to NR Rel.18 is shown;

[0013] Figure 4 The sub-bands in the cell are shown to be non-overlapping for FD-gNB and HD-UE;

[0014] Figure 5 An example of a sub-band non-overlapping full-duplex (SBFD) configuration is shown;

[0015] Figure 6 An example of SBFD based on a single bandwidth part (BWP) of a time division duplex (TDD) format DDDSU is shown;

[0016] Figure 7 An example of SBFD based on multiple BWPs is shown;

[0017] Figure 8 and Fig. 9 An example of relative bandwidths of bandwidth pairs is shown; and

[0018] Fig.10An example of CLI measurement performed on a UL sub-band is shown. DETAILED DESCRIPTION

[0019] In the following detailed description, many specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples can be practiced without some or all of the specific details set forth herein. In other cases, well-known methods, programs, components and circuits are not described in detail to avoid blurring the following description. In addition, the embodiments and examples not specifically described herein can replace the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided (collectively referred to as "providing") herein to practice or practice in combination with them. Although various embodiments in which equipment, systems, devices, etc. and / or any of its elements perform operations, processes, algorithms, functions, etc. and / or any part thereof are described and / or claimed herein, it should be understood that any embodiment described and / or claimed herein assumes that any equipment, systems, devices, etc. and / or any of its elements are configured to perform any operations, processes, algorithms, functions, etc. and / or any part thereof.

[0020] Example Communication System

[0021] The methods, devices, and systems provided herein are well suited for communications involving wired and wireless networks. Figures 1A to 1D An overview of various types of wireless devices and infrastructure is provided in which various elements of the network can utilize, perform, be arranged according to, and / or be adapted and / or configured for the methods, devices, and systems provided herein.

[0022] Figure 1A is a system diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources (including wireless broadband). For example, the communication system 100 may 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 (ZT) unique word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0023] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, 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 device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated process chain), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

[0024] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, for example, to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the network 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B (NB), an eNode-B (eNB), a master Node B (HNB), a master eNode-B (HeNB), a gNode-B (gNB), a NR Node B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0025] The base station 114a may be part of the RAN 104 / 113, 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), a relay node, etc. The base station 114a and / or the base station 114b may 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 a licensed spectrum, an unlicensed spectrum, or a combination of a licensed spectrum and an unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area that may be relatively fixed or may vary over time. The cell may also be divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology, and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0026] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, 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 interface 116 may be established using any suitable radio access technology (RAT).

[0027] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0028] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA) which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as New Radio (NR) to establish NR radio access over the air interface 116.

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access, for example using dual connectivity (DC) principles. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, 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), etc.

[0032] Figure 1AThe base station 114b in the example may be, for example, a wireless router, a master Node-B, a master eNode-B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-a, LTE-a Pro, NR, etc.) to establish any of a small cell, a pico cell, or a femto cell. As Figure 1A As shown, base station 114b may be directly connected to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0033] The RAN 104 / 113 may be in communication with the CN 106 / 115, 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 WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although Figure 1A Not shown, but it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing an NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs any of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

[0034] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may use the same RAT as the RAN 104 / 114 or a different RAT.

[0035] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0036] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other elements / peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0037] The processor 118 may 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, such as in an electronic package or chip.

[0038] The transmit / receive element 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via an air interface 116. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In an embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF signals and optical signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0039] Although the transmit / receive element 122 is Figure 1B Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0040] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs (e.g., such as NR and IEEE 802.11).

[0041] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from: a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0042] The processor 118 may receive power from the power source 134 and may be configured to distribute the power to and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may 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, etc.

[0043] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of receiving signals from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0044] The processor 118 may also be coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the components / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (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, etc. Components / peripherals 138 may include one or more sensors, which may be gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0045] The WTRU 102 may include a full-duplex radio in which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) and downlink (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 hardware (e.g., choke) or signal processing via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio in which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0046] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0047] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0048] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0049] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0050] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0051] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0052] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0053] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0054] Although the WTRU Figures 1A to 1D Although depicted as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may (eg, temporarily or permanently) employ a wired communications interface with a communications network.

[0055] In a representative embodiment, other network 112 may be a WLAN.

[0056] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may access a distribution system (DS) or another type of wired / wireless network that loads traffic into and / or out of the BSS or has an interface thereto. Traffic originating from outside the BSS to the STA may be reached by the AP and may be delivered to the STA. Traffic from the STA to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent by 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. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source STA and the destination STA using a direct link setup (DLS) (e.g., directly sent between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0057] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP can send beacons on a fixed channel, such as a primary channel. The primary channel can be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel can be an operating channel of the BSS and can be used by STAs to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access-collision avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. For CSMA / CA, STAs (e.g., each STA) including the AP can sense the primary channel. If the primary signal is sensed / detected by a particular STA and / or is determined to be busy, the particular STA can back off. One STA (e.g., only one station) can transmit in a given BSS at any given time.

[0058] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0059] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two discontinuous 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, the data can be passed through a fragment parser after channel coding, which can divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed on each stream respectively. The stream can be mapped to two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above-mentioned operation of the 80+80 configuration can be reversed, and the combined data can be sent to a media access control (MAC) layer, an entity, etc.

[0060] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah relative to those channel operating channels and carriers used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in TV white space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter type control / machine type communication (MTC), such as MTC devices in macro coverage. MTC devices may have certain capabilities, for example, limited capabilities, including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0061] A WLAN system that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) includes a channel that can be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, due to a STA (which only supports a 1MHz operating mode) transmitting to the AP, the entire available band may be considered busy even if most of the band remains idle and may be available.

[0062] In the United States, the available frequency band that can be used by 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0063] Figure 1D1 is a system diagram showing the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0064] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be located on an unlicensed spectrum, while the remaining component carriers may be located on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0065] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. 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 WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0066] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as the eNode Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may serve as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRU 102a, 102b, 102c.

[0067] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0068] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least two session management functions (SMFs) 183a, 183b, and at least one data network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0069] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing, for example, to customize CN support for the WTRU 102a, 102b, 102c based on the type of service the WTRU 102a, 102b, 102c is utilizing. 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, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies (such as LTE, LTE-A, LTE-APro) and / or non-3GPP access technologies (such as Wi-Fi).

[0070] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0071] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, for example, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0072] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b through the UPF 184a, 184b.

[0073] Given that Figures 1A to 1D and Figures 1A to 1D 102a to 102d, base stations 114a to 114b, eNode-Bs 160a to 160c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a to 180c, AMFs 182a to 182b, UPFs 184a to 184b, SMFs 183a to 183b, DNs 185a to 185b, and / or any other elements / devices described herein. A simulation device may be one or more devices configured to simulate one or more or all of the functions described herein. For example, a simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0074] The simulation device can be designed to implement one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, one or more simulation devices can perform one or more or all functions when fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all functions when temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly coupled to another device for testing purposes, and / or can use over-the-air wireless communication to perform testing.

[0075] One or more simulation devices can perform one or more (including all) functions when not implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used for testing scenarios in a test laboratory and / or a wired and / or wireless communication network that is not deployed (e.g., testing) to implement testing of one or more components. One or more simulation devices can be test equipment. The simulation device can use direct RF coupling and / or wireless communication via RF circuits (e.g., which can include one or more antennas) to transmit and / or receive data.

[0076] The examples provided herein do not limit the applicability of the subject matter to other wireless technologies, eg, using the same or different principles may be applicable.

[0077] As described herein, a wireless transmit / receive unit (WTRU) may be an example of a user equipment (UE). Therefore, the terms UE and WTRU may be used in the same context herein.

[0078] Introduction

[0079] NR supports dynamic / flexible time division duplex (TDD) based on a slot format indicator (SFI), which can be indicated to a group of UEs through the group common (GC) downlink control information (DCI) (format 2_0). In addition, semi-static configuration can be configured through the high-layer parameters of "tdd-UL-DL-config-common" and "tdd-UL-DL-config-dedicated", where the transmission mode of each time slot / symbol can be configured as any of the following: "D" as downlink, "U" as uplink, and "F" as flexible.

[0080] Until NR Rel-17, most practical assumptions for duplexing were half-duplex (HD) for gNB and UE. In Rel-18, enhancements have been proposed to support at least full-duplex (FD) for gNB (e.g. Figure 3 In addition, Figure 4As shown, sub-band non-overlapping full-duplex (SBFD), also known as cross-division duplex (XDD), has been identified as a promising approach to reduce the complexity of FD implementation in terms of self-interference (SI) elimination and cross-link interference (CLI) mitigation, at least at the gNB end.

[0081] The SBFD scenario can serve as a basis for improving traditional TDD operations by enhancing UL coverage, increasing capacity, reducing latency, etc. Figure 5 An example SBFD configuration is shown, where UL subbands (SB) may be allocated in "D" slots (and / or "F" slots). As another example, DL subbands may be allocated in "U" slots (and / or "F" slots).

[0082] However, if semi-static configuration is used for time domain and frequency domain configuration (e.g., RBs and / or subbands of SBFD) in SBFD operation based on a single bandwidth part (BWP) pair (e.g., RB set-based SBFD), this may lead to one or more of the following problems, while there may be advantages in terms of hardware complexity reduction (e.g., preset RF ranges for Tx / Rx) through simplified SBFD configuration:

[0083] - Resource waste, for example, one or more TDD directions (eg, UL or DL) may not have sufficient traffic (eg, due to traffic variations), and configuring semi-static resource allocation may result in inefficient resource utilization.

[0084] - Increased latency, for example, one or more of the TDD directions configured in SBFD (e.g., UL or DL) may have heavy traffic (e.g., high load), in which case the semi-static configuration in the time and frequency domain (e.g., RBs and / or subbands for SBFD) may result in increased latency.

[0085] - Reduced flexibility, e.g., without dynamically enabled configuration, scheduling and resource allocation in SBFD may experience lower flexibility in the face of traffic and demand variations (e.g., due to semi-static configuration in the time and frequency domain (e.g., RBs and / or subbands for SBFD)).

[0086] - Increased complexity, e.g., semi-static configuration of RBs and / or subbands in time and frequency domain (e.g., SBFD) may result in increased scheduling complexity. Therefore, scheduling complexity may increase due to fixed / static configuration of UL and / or DL ​​subbands or PRBs in SBFD.

[0087] In case of dynamic SBFD configuration updates / switching, network-side (including neighboring gNB) coordination may be required to make safe / planned subband allocations for cross-layer interference (CLI) measurements and reporting from one or more UEs for a given time duration.

[0088] Overview

[0089] As used herein, the singular form and similar phrases should be interpreted as "one or more" and "at least one". Similarly, any term ending with the suffix "(s)" should be interpreted as "one or more" and "at least one". The term "may" should be interpreted as "may, for example". Unless otherwise specifically stated, the forward slash " / " sign, symbol or mark should be interpreted as "and / or", where, for example, "A / B" may mean "A and / or B".

[0090] In this document, the term "subband" is used to refer to frequency domain resources and may be characterized by at least one of the following: a group of resource blocks (RBs), a group of resource block sets (RB sets), such as when a carrier has an intra-cell guard band, a group of interleaved resource blocks, a bandwidth portion or a portion thereof, and a carrier or a portion thereof.

[0091] For example, a subband may be characterized by a starting RB and the number of RBs in a set of consecutive RBs within a bandwidth part.A subband may also be defined by the value of a frequency domain resource allocation field and a bandwidth part index.

[0092] In this document, the term "XDD" is used to refer to sub-band duplexing (e.g., each sub-band uses UL or DL), and may have at least one of the following characteristics:

[0093] - Cross-division duplexing (e.g., sub-band FDD within a TDD band);

[0094] - Full duplex based on subband (e.g., full duplex because both UL and DL are used / mixed on a symbol / timeslot, but UL or DL ​​is used per subband on a symbol / timeslot);

[0095] - Frequency domain multiplexing (FDM) of DL / UL transmissions within the TDD spectrum;

[0096] - Sub-Band Non-Overlapping Full-Duplex (SBFD) (e.g., non-overlapping sub-band full-duplex);

[0097] - Full duplex except same-frequency (e.g., spectrum sharing, sub-band overlap) full duplex; and

[0098] - Advanced duplexing methods, e.g. other than (pure) TDD or FDD

[0099] In this document, the term "dynamic ( / flexible) TDD" is used to refer to a TDD system / cell that can dynamically (and / or flexibly) change / adjust / switch a communication direction (e.g., downlink, uplink, or sidelink, etc.) at a time instance (e.g., time slot, symbol, subframe, etc.). In one example, in a system adopting dynamic / flexible TDD, based on an indication of a group common (GC)-DCI (e.g., format 2_0) including a time slot format indicator (SFI) and / or based on a tdd-UL-DL-config-common / dedicated configuration, a component carrier (CC) or a bandwidth part (BWP) can have a single type of 'D', 'U', and 'F' at a symbol / time slot. At a given time instance / time slot / symbol, a first gNB (e.g., cell, TRP) employing dynamic / flexible TDD may transmit a downlink signal to a first UE communicating / associated with the first gNB based on a first SFI and / or tdd-UL-DL-config configured / indicated by the first gNB, and a second gNB (e.g., cell, TRP) employing dynamic / flexible TDD may receive an uplink signal transmitted from a second UE, which is communicating / associated with the second gNB based on a second SFI and / or tdd-UL-DL-config configured / indicated by the second gNB. In one example, the first UE may determine that reception of the downlink signal is interfered by the uplink signal, wherein the interference caused by the uplink signal may refer to UE-to-UE cross-layer interference (CLI).

[0100] Definition of beam

[0101] The UE may transmit or receive a physical channel or a reference signal according to at least one spatial domain filter. The term "beam" may be used to refer to a spatial domain filter.

[0102] The UE may transmit a physical channel or signal using the same spatial domain filter as used to receive an RS (e.g., CSI-RS) or SS block. The UE transmission may be referred to as the "target" and the received RS or SS block may be referred to as the "reference" or "source." In this case, it may be said that the UE transmits the target physical channel or signal based on a spatial relationship to the reference of such RS or SS block.

[0103] The UE may transmit the first physical channel or signal according to the same spatial domain filter as used to transmit the second physical channel or signal. The first transmission and the second transmission may be referred to as "target" and "reference" (or "source"), respectively. In this case, the UE may transmit the first (target) physical channel or signal with reference to the second (reference) physical channel or signal according to a spatial relationship.

[0104] The spatial relationship can be implicit, configured by RRC or signaled by MACCE or DCI. For example, the UE can implicitly transmit the PUSCH and DM-RS of the PUSCH according to the same spatial domain filter as the SRS indicated by the SRS resource indicator (SRI) indicated in the DCI or configured by RRC. In another example, the spatial relationship can be configured by RRC for SRI or signaled by MACCE for PUCCH. This spatial relationship can also be called "beam indication".

[0105] The UE may receive a first (target) downlink channel or signal based on the same spatial domain filter or spatial reception parameters as a second (reference) downlink channel or signal. For example, such an association may exist between a physical channel (e.g., PDCCH or PDSCH) and its respective DM-RS. At least when the first and second signals are reference signals, such an association may exist when the UE is configured with a quasi-co-location (QCL) assumption type D between the corresponding antenna ports. This association may be configured as a transmission configuration indicator (TCI) state. The association between a CSI-RS or SS block and a DM-RS may be indicated to the UE by an index to a set of TCI states configured by RRC and / or signaled by MACCE. This indication may also be referred to as a "beam indication."

[0106] TRP, MTRP, M-TRP

[0107] In this document, the term "TRP" (e.g., transmission and reception point) can be used interchangeably with one or more of TP (transmission point), RP (reception point), RRH (radio remote head), DA (distributed antenna), BS (base station), sector (of a BS), and cell (e.g., a geographic cell area served by a BS). In this document, Multi-TRP can be used interchangeably with one or more of MTRP, M-TRP, and multiple TRPs, while still being consistent with the present invention.

[0108] CSI Components

[0109] The UE may report a subset of channel state information (CSI) components, where the CSI components may correspond to at least one CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI), an indication of a panel received at the UE (e.g., a panel identifier or a group identifier), measurement values ​​such as L1-RSRP, L1-SINR obtained from SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and other channel state information (e.g., at least rank indicator (RI), channel quality indicator (CQI), precoding matrix indicator (PMI), layer index (LI), etc.).

[0110] Channel and / or interference measurements

[0111] The UE may receive synchronization signal / physical broadcast channel (SS / PBCH) blocks. The SS / PBCH block (SSB) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE may monitor, receive, or attempt to decode the SSB during initial access, initial synchronization, radio link monitoring (RLM), cell search, cell handover, etc.

[0112] The UE may measure and report channel state information (CSI), where the CSI for each connection mode may include or be configured with one or more of the following:

[0113] -CSI reporting configuration, including one or more of the following;

[0114] - Number of CSI reports, such as channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), etc.;

[0115] -CSI reporting type, such as aperiodic, semi-persistent, periodic;

[0116] -CSI report codebook configuration, such as Type I, Type II, Type II port selection, etc.;

[0117] -CSI reporting frequency; and

[0118] -CSI-RS (resource set), including one or more of the following CSI resources:

[0119] - NZP-CSI-RS resources for channel measurement, where NZP stands for non-zero power;

[0120] - NZP-CSI-RS resources for interference measurements; and

[0121] - CSI-IM resources for interference measurements; and

[0122] -NZP CSI-RS resources, including one or more of the following:

[0123] -NZP CSI-RS resource ID;

[0124] - Periodicity and offset;

[0125] - QCL information and TCI status; and

[0126] - Resource mapping, such as number of ports, density, CDM type, etc.

[0127] The UE may indicate, determine, or be configured with one or more reference signals. The UE may monitor, receive, and measure one or more parameters based on the corresponding reference signals. For example, one or more of the following may be applied. The following parameters - SS-RSRP, CSI-RSRP, SS-SINR, CSI-SINR, RSSI, CLI-RSSI, and SRS-RSRP - are non-limiting examples of parameters that may be included in the reference signal measurement. One or more of these parameters may be included. Other parameters may be included.

[0128] SS-RSRP, or SS Reference Signal Received Power, can be measured based on synchronization signals, such as the Demodulation Reference Signal (DMRS) in PBCH or SSS. It can be defined as the linear average of the power contributions of the resource elements (REs) carrying the corresponding synchronization signal. When measuring RSRP, power scaling of the reference signal may be required. If SS-RSRP is used for L1-RSRP, the measurement can be done based on the CSI reference signal in addition to the synchronization signal.

[0129] CSI-RSRP may be measured based on the linear average of the power contributions of the resource elements (REs) carrying the corresponding CSI-RS. CSI-RSRP measurements may be configured within the measurement resources of the configured CSI-RS occasions.

[0130] SS-SINR, or SS signal-to-noise-interference ratio, can be measured based on synchronization signals (e.g., DMRS in PBCH or SSS). It can be defined as the linear average of the power contribution of the resource elements (REs) carrying the corresponding synchronization signal divided by the linear average of the noise and interference power contributions. If SS-SINR is used for L1-SINR, the noise and interference power measurement can be done based on the resources configured by higher layers.

[0131] The CSI-SINR may be measured based on the linear average of the power contribution of the resource elements (REs) carrying the corresponding CSI-RS divided by the linear average of the noise and interference power contributions. If the CSI-SINR is used for L1-SINR, the noise and interference power measurement may be done based on the resources configured by the higher layers. Otherwise, the noise and interference power may be measured based on the resources carrying the corresponding CSI-RS.

[0132] RSSI, or received signal strength indicator, can be measured based on the average of total power contributions in the configured OFDM symbols and bandwidth. Power contributions can be received from different resources (e.g., co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0133] CLI-RSSI, Cross-layer Interference Received Signal Strength Indicator, can be measured based on the average of the total power contribution in the configured OFDM symbol for the configured time and frequency resources. Power contributions can be received from different resources (e.g., cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0134] SRS-RSRP, Sounding Reference Signal RSRP, can be measured based on the linear average of the power contributions of the Resource Elements (REs) carrying the corresponding SRS.

[0135] In this context, the authorized or assigned attributes may include at least one of the following:

[0136] - Frequency allocation;

[0137] - aspects of time allocation, such as duration;

[0138] - Priority;

[0139] - Modulation and coding scheme;

[0140] -Transport block size;

[0141] - Number of spatial layers;

[0142] - Number of transport blocks;

[0143] -TCI status, CRI or SRI;

[0144] - Number of repetitions;

[0145] - Whether the repetition scheme is type A or type B;

[0146] - Whether the authorization is a configured authorization type 1, type 2, or dynamic authorization;

[0147] - Whether the allocation is dynamic or semi-persistently scheduled (configured);

[0148] - Whether the configured authorization index is a semi-persistent allocation index;

[0149] - Periodicity of authorization or allocation of configurations;

[0150] - Channel Access Priority Class (CAPC); and

[0151] - Any parameters provided in the DCI, by the MAC or by the RRC for scheduling grants or allocations.

[0152] In this context, the DCI indication may include at least one of the following:

[0153] - An explicit indication of the RNTI used to mask the CRC of the PDCCH, either in the DCI field or in the CRC.

[0154] - Implicit indication of attributes such as DCI format, DCI size, core set or search space, aggregation level, first resource element of received DCI (e.g., index of first control channel element), where the mapping between attributes and values ​​can be signaled via RRC or MAC.

[0155] As used herein, the term "signal" may be used interchangeably with one or more of the following:

[0156] - Sounding Reference Signal (SRS);

[0157] - Channel State Information - Reference Signal (CSI-RS);

[0158] - Demodulation Reference Signal (DM-RS);

[0159] - Phase Tracking Reference Signal (PT-RS); and

[0160] -Synchronization Signal Block (SSB).

[0161] In this document, the term "channel" may be used interchangeably with one or more of the following:

[0162] - Physical Downlink Control Channel (PDCCH);

[0163] - Physical Downlink Shared Channel (PDSCH);

[0164] - Physical Uplink Control Channel (PUCCH);

[0165] - Physical Uplink Shared Channel (PUSCH);

[0166] - Physical Random Access Channel (PRACH);

[0167] -etc.

[0168] In this document, the expression "downlink reception" can be used interchangeably with Rx occasion, PDCCH, PDSCH, SSB reception.

[0169] In this document, the expression "uplink transmission" may be used interchangeably with Tx occasions, PUCCH, PUSCH, PRACH, SRS transmission.

[0170] Herein, the expression "RS" may be used interchangeably with one or more of an RS resource, an RS resource set, an RS port, and an RS port group.

[0171] Herein, the expression “RS” may also be used interchangeably with one or more of SSB, CSI-RS, SRS, and DM-RS.

[0172] In this document, the expression "time instance" may be used interchangeably with time slot, symbol, subframe.

[0173] Herein, the expression "UL only and DL only Tx / Rx occasions" may be used interchangeably with legacy TDD UL or legacy TDD DL, respectively. In one example, the legacy TDD UL / DL Tx / Rx occasions may be a case where SBFD is not configured and / or disabled.

[0174] 1SBFD configuration update for advanced duplex operation

[0175] 1.1SBFD Subband Granularity

[0176] SBFD configuration based on a single BWP (e.g. SBFD based on RB sets)

[0177] For SBFD operation scenarios, a single configured DL and UL BWP pair may be used. The UE may be configured with one or more BWPs for a component carrier (CC) (or cell), where each BWP may be indexed with a BWP-ID, e.g., 0, 1, 2, or 3. The UE may receive (from the gNB) a SBFD configuration including at least the time and / or frequency domain of DL / UL subband location information, where the SBFD configuration may be associated with a BWP-ID X, e.g., X=0, 1, 2, or 3. The SBFD configuration may be indicated / configured at the CC / cell level (e.g., together with the CC / cell configuration) or in a system information block (SIB) and / or a master information block (MIB). In one example, the UE may receive a SBFD configuration for a CC (or cell), and the UE may determine that a BWP (e.g., a DL / UL BWP pair) associated with BWP-ID X is an active BWP, for example, in response to determining that the BWP is a default BWP and / or an initial BWP (e.g., after a RACH procedure), or in response to receiving a DCI indicating which BWP-ID becomes the active BWP (e.g., via a "bandwidth part indicator" field in the DCI, as a BWP switching behavior), etc. The UE may determine that the BWP with BWP-ID X includes at least one subband (e.g., a UL subband and / or a DL subband) within the BWP. In response to the determination, the UE may identify / determine that the SBFD configuration (e.g., including at least one subband) is associated with BWP-ID X.

[0178] A UE (e.g., an SBFD-enabled UE) may receive or be configured with one or more SBFD UL or DL ​​subbands in one or more time instances, where the subband may be associated with a BWP-ID X (e.g., X=0, 1, 2, or 3), for example, and / or a CC / cell. The time instance may be (initially and / or previously) configured with a first TDD direction (e.g., downlink), a second TDD direction (e.g., uplink), or a third TDD direction (e.g., flexible). The configuration as DL, UL, or flexible may be based on one or more TDD UL / DL configurations received by the UE, such as a common TDD UL / DL configuration (e.g., tdd-UL-DL-ConfigurationCommon), a dedicated TDD UL / DL configuration (e.g., tdd-UL-DL-ConfigurationDedicated), and / or a slot format indicator (SFI) (e.g., a dynamically indicated SFI, e.g., via DCI).

[0179] The UE may be configured with one or more resource allocations for a SBFD subband. The SBFD configuration may include a flag signal (e.g., enable / disable), where, for example, one value (e.g., a value of zero (0)) indicates no SBFD configuration (e.g., SBFD is not enabled), and another value (e.g., a value of one (1)) may indicate that the SBFD configuration is enabled. The SBFD configuration may be indicated via a system information block (SIB), semi-statically (e.g., via RRC), dynamically (e.g., via MAC-CE, DCI), etc. The UE may receive an indication of the time resources (e.g., one or more symbols, time slots, etc.) that SBFD is applicable to a serving cell, carrier, or BWP.

[0180] The UE may receive a BWP (eg, BWP-IDX) and / or frequency resources (eg, a subband or one or more groups of PRBs) within a CC / cell configured with SBFD. Figure 6An example of SBFD for a single BWP based on TDD format DDDSU is shown (where each letter corresponds to a time slot starting with time slot n, 'D' stands for downlink, 'S' stands for special or 'flexible' time slot, and 'U' stands for uplink), where the SBFD is configured based on one or more groups of PRBs. It can be seen that time slot n is a DL time slot, time slots n+1 and n+2 are DL time slots including UL subbands, time slot n+3 is a special time slot including UL subbands, and time slot n+4 is a UL time slot. The time instances (e.g., time slots, symbols) configured for SBFD can be indicated based on periodic, semi-persistent, or non-periodic configurations. In one example, the time instances can be indicated by explicit configuration (e.g., bitmap configuration), for example, within a certain period in the time domain, where the period (e.g., time interval, time window, periodicity, etc.) can be predefined (e.g., Tms), preconfigured, or indicated to the UE.

[0181] In one example, the UE may be configured with a DL TDD configuration (e.g., with DL slots / symbols) of a BWP for one or more Rx occasions (e.g., via tdd-UL-DL-config-common / dedicated configuration, SFI, etc.). The UE may receive or be configured with SBFD operation as part of the TDD configuration in the corresponding time instance. Thus, if SBFD is configured, the configured frequency resources (e.g., subbands and / or PRBs) may be configured for UL channels / Tx occasions.

[0182] In another example, the UE may be configured with a UL TDD configuration (e.g., with UL time slots / symbols) for BWP for one or more Tx occasions. The UE may also receive or be configured with SBFD operation as part of the TDD configuration in the corresponding time instance. Thus, if SBFD is configured, the configured frequency resources (e.g., subbands and / or PRBs) may be configured for DL ​​channels / Rx occasions.

[0183] In another example, the UE may be configured with a flexible TDD configuration for BWP for one or more Rx / Tx occasions. The UE may receive or be configured with SBFD operation as part of the TDD configuration in the corresponding time instance. Thus, if SBFD is configured, the configured frequency resources (e.g., subbands and / or PRBs) may be configured for UL transmission or TDD reception based on the configuration.

[0184] The duplex mode of the SBFD configuration (UL / DL) may be indicated by a flag, where, for example, a first value (eg, zero (0)) may indicate a UL duplex mode and a second value (eg, one (1)) may indicate a DL duplex mode.

[0185] The SBFD duplex mode configuration / flag may be configured as part of the SBFD configuration, which may be semi-static (eg, via RRC) or dynamic (eg, via DCI, MAC-CE).

[0186] The SBFD duplex mode configuration / flag can be configured as part of the resource allocation configuration of the Tx / Rx occasion.

[0187] SBFD operations within multiple BWP pairs

[0188] For SBFD operation scenarios, multiple configured DL and ULBWP pairs may be used. The UE may configure one or more BWPs for a CC (or cell), where each BWP may be indexed with a BWP-ID, such as 0, 1, 2, or 3. The UE may receive (from the gNB) an SBFD configuration including at least one or more of the following pairs:

[0189] - the first pair {BWP-ID X, "DL" (as the selected link direction of SBFD SB)}, and / or

[0190] - a second pair {BWP-ID Y, "UL" (as the selected link direction of SBFD SB)}, and / or

[0191] - The third pair {BWP-ID Z, "DL" (as the selected link direction of SBFD SB)}, and so on.

[0192] Figure 7 An example of SBFD based on multiple BWPs is shown, where the SBFD is configured based on the TDD configuration of one or more BWPs. Figure 7 In the example, the BWPs with BWP-IDs (eg, x and x+2) are configured as DDDSU, while the BWPs with BWP-IDs (eg, x+1) are configured as DUUUU.

[0193] In one example, the selected link direction of a SBFDSB may be "DL+UL" associated with a BWP-ID, which may mean that the BWP with the BWP-ID contains both DL SBs and UL SBs in a SBFD slot / symbol.

[0194] In one example, the selected link direction for the SBFD SB may be "at least DL" associated with the BWP-ID, where it may mean that the BWP with the BWP-ID contains at least the DL SB in the SBFD slot / symbol (and the UL SB is initially unknown). The UL SB is initially unknown may mean that the UE may receive a scheduling / configuration grant for UL transmission in the BWP with the BWP ID (associated with "at least DL") and may perform UL transmission if no conflict / overlap with actual DL reception is found / determined in the SBFD slot / symbol.

[0195] In one example, the selected link direction for the SBFD SB may be "at least UL" ​​associated with the BWP-ID, where it may mean that the BWP with the BWP-ID contains at least the UL SB in the SBFD slot / symbol (and the DL SB is initially unknown). The DL SB is initially unknown may mean that the UE may receive a scheduling / configuration grant for DL ​​reception in the BWP with the BWP ID (associated with "at least UL") and may perform DL reception if no conflict / overlap with actual UL transmission is found / determined in the SBFD slot / symbol.

[0196] 1.2 Timeline of SBFD configuration update and BWP switching

[0197] In an embodiment, the UE may be configured with (at least) one (RB set based) SBFD configuration per (DL / UL) BWP pair (associated with a BWP-ID) or CC / cell, and a BWP switching command (received at the UE) for switching from a first BWP pair to a second BWP pair, the UE may determine whether and / or how to change the associated SBFD configuration of the second BWP pair. One or more of the following examples and operations may apply.

[0198] In one example, the UE may be configured with one or more BWPs for a CC (or cell), where each BWP may be indexed / configured with a BWP-ID X, e.g., X=0, 1, 2, or 3. The UE may receive (from a gNB) a first SBFD configuration, the configuration including at least first time and / or frequency domain DL / UL subband location information, e.g., associated with a first (DL / UL) BWP pair with BWP-ID 1 (e.g., X=1 in {0, 1, 2, 3}), and / or associated with a CC / cell, where the first BWP pair with BWP-ID 1 may be a default BWP (and / or an initial BWP). In one example, the first BWP pair may not be directly / explicitly configured / associated with the first SBFD configuration, and the UE may determine that the first SBFD configuration (e.g., configured with / associated with the CC / cell) is applicable to the first BWP pair (with BWP-ID 1), e.g., by default, or as a predetermined condition / rule. The UE may receive (from the gNB) a second SBFD configuration comprising at least second time and / or frequency domain DL / UL subband location information associated with a second (DL / UL) BWP pair with BWP-ID 2 (e.g., X=2 in {0,1,2,3}).

[0199] In one example, the UE may identify / determine the current BWP as BWP-ID 1, where BWP-ID 1 may be indicated by a recent DCI including a "Bandwidth Part Indicator" field indicating a value / code point of "BWP-ID=1", or the UE may obtain / determine that the current BWP is BWP-ID 1 based on a rule-based behavior, for example, through a predefined mechanism based on an "initial BWP" and / or "default BWP" parameter.

[0200] In one example, the UE may receive a BWP switching command (e.g., via DCI, UL-related DCI format 0_1, UL-related DCI format 0_2, DL-related DCI format 1_1, or DL-related DCI format 1_2, etc.) at the first time slot (or symbol), indicating that the BWP-ID is set to 2. The BWP switching command may be a "bandwidth part indicator" field, or a separate / new field, or based on an independent / new indication mechanism. The UE may identify / determine that the current BWP (e.g., with BWP-ID 1) will switch to an indicated BWP with BWP-ID 2 at T (>=0) time slots (or symbols) after the first time slot (or symbol), where the value of T may be determined by a predefined rule, for example, based on a parameter of the subcarrier spacing and / or a UE capability of a BWP switching delay, etc. In one example, the UE may identify / determine that T=5 based on the UE's capability report and a predefined BWP switching delay-related rule. In response to receiving a BWP switching command at a first time slot (or symbol), the UE may perform an active BWP switch at a second time slot (or symbol), switching from the current (DL / UL) BWP pair (with BWP-ID 1) to a new (DL / UT) BWP pair (with indicated BWP-ID 2), which second time slot (or symbol) may be calculated / determined as the first time slot (or symbol) + T time slots (or symbols).

[0201] Based on the active BWP switching, for example, at the second time slot (or symbol), the UE may determine whether and / or how to change the associated SBFD configuration along with the BWP switching based on applying at least one of the following operations:

[0202] Operation 1: Based on which DCI format (or type or field / content, etc.) is received, which conveys the BWP switching command, the UE may determine whether to change / switch the associated SBFD configuration along with the BWP switching.

[0203] In one example, when the UE is operating in a first BWP pair with BWP-ID 1 and is operated based on a first SBFD configuration, in response to receiving an UL-related DCI (e.g., format 0_1, 0_2) including a BWP switching command indicating a switch to a second BWP pair with BWP-ID 2, the UE may determine to (also) change / switch the associated SBFD configuration to a second SBFD configuration, e.g., which is associated with the second BWP pair with BWP-ID 2. If the UE subsequently receives a DL-related DCI (e.g., format 1_1, 1_2, or a format other than UL-DCI, etc.) including a BWP switching command indicating a switch to the second BWP pair with BWP-ID 2, the UE may determine to maintain (e.g., not change, retain, continue to use) the first SBFD configuration (e.g., in terms of UL subband position), but change the BWP pair (from the first BWP pair) to the second BWP pair with BWP-ID 2. This may bring benefits in terms of resource utilization flexibility and efficiency, as the SBFD configuration does not change frequently but selectively based on gNB signaling, which can reduce the complexity of gNB implementation by avoiding frequent RF (e.g., RF filter, filtering, filtering coefficients) switching at the gNB.

[0204] In one example, when the UE is operating in a first BWP pair with BWP-ID 1 and is operated based on a first SBFD configuration, in response to receiving a DL-related DCI (e.g., format 1_1, 1_2) including a BWP switching command indicating a switch to a second BWP pair with BWP-ID 2, the UE may determine to (also) change / switch the associated SBFD configuration to a second SBFD configuration, e.g., which is associated with the second BWP pair with BWP-ID 2. If the UE subsequently receives a UL-related DCI (e.g., format 0_1, 0_2, or a format other than DL-DCI, etc.) including a BWP switching command indicating a switch to the second BWP pair with BWP-ID 2, the UE may determine to maintain (e.g., not change, retain, continue to use) the first SBFD configuration (e.g., in terms of UL subband position), but change the BWP pair (from the first BWP pair) to the second BWP pair with BWP-ID 2. This may bring benefits in terms of resource utilization flexibility and efficiency, as the SBFD configuration does not change frequently but selectively based on gNB signaling, which can reduce the complexity of gNB implementation by avoiding frequent RF (e.g., RF filter, filtering, filtering coefficients) switching at the gNB.

[0205] In one example, when the UE is operating in a first BWP pair with BWP-ID 1 and is operated based on a first SBFD configuration, in response to receiving a DCI based on a first RNTI (or other DCI-related type or field / content, etc.) that includes a BWP switching command indicating a switch to a second BWP pair with BWP-ID 2, the UE may determine to (also) change / switch the associated SBFD configuration to a second SBFD configuration, e.g., which is associated with the second BWP pair with BWP-ID 2. If the UE receives a DCI based on a second RNTI (e.g., in addition to the first RNTI, or other DCI-related type or field / content, etc.) that includes a BWP switching command indicating a switch to a second BWP pair with BWP-ID 2, the UE may determine to maintain (e.g., not change, retain, continue to use) the first SBFD configuration (e.g., in terms of UL subband position), but change the BWP pair (from the first BWP pair) to the second BWP pair with BWP-ID 2. This may bring benefits in terms of resource utilization flexibility and efficiency, as the SBFD configuration does not change frequently but selectively based on gNB signaling, which can reduce the complexity of gNB implementation by avoiding frequent RF (e.g., RF filter, filtering, filtering coefficients) switching at the gNB.

[0206] Operation 1 may be configured for the UE to perform based on operation 1 (e.g., as an operation mode), or operation 1 may be predefined as a default operation mode that the UE may follow / perform unless otherwise configured / instructed. Operation 1 may have one or more prerequisites, and operation 1 will be used, for which at least one of the following two paragraphs may apply:

[0207] like Figure 8 and Fig. 9 As shown, the first bandwidth (e.g., number of PRBs, entire frequency resource region) of the first BWP pair is less than or equal to the second bandwidth (e.g., number of PRBs, entire frequency resource region) of the second BWP pair. This may mean that the second bandwidth (of the second BWP pair) completely includes the first bandwidth (of the first BWP pair), which can ensure that, with respect to the selective change of such SBFD configuration, at least one subband (e.g., UL subband and / or DL ​​subband) of the first SBFD configuration is included (e.g., contained within the frequency region) in the second bandwidth (of the second BWP pair).

[0208] The first group of RBs corresponding to at least one subband (e.g., UL subband and / or DL ​​subband) of the first SBFD configuration of the first BWP pair is less than or equal to the second bandwidth (e.g., number of PRBs, entire frequency resource region) of the second BWP pair. This may mean that the second bandwidth (of the second BWP pair) completely includes the first group of RBs, which may ensure that, with respect to the selective change of such SBFD configuration, at least one subband (e.g., UL subband and / or DL ​​subband) of the first group of the first SBFD configuration is included (e.g., contained within the frequency region) in the second bandwidth (of the second BWP pair).

[0209] The UE may receive (or determine) one or more predefined or preconfigured conditions indicating that the current SBFD configuration (e.g., the first SBFD configuration) cannot be maintained in a new / switched BWP pair (e.g., the second BWP pair with BWP-ID 2) in response to the BWP switch command. The one or more conditions may include at least one of the following: a case where the UL subband is not (completely) included in the switched BWP with BWP-ID 2; and a case where it is determined that at least one of the one or more preconditions is not satisfied.

[0210] If the UE determines that one or more predefined or preconfigured conditions are met indicating that the current (first) SBFD configuration cannot be maintained (e.g., if the UL subband is not (fully) contained within the switching BWP with BWP-ID 2), the UE may apply a fallback behavior, which may be predefined or preconfigured based on at least one of: following / applying (legacy) "tdd-UL-DL-config-common" and / or "tdd-UL-DL-config-dedicated" for "D", "U" and / or "F" modes), and applying UL subband truncation (e.g., to adapt) within the switching second BWP with BWP-ID 2 (based on predefined or preconfigured rules).

[0211] Operation 2: Based on the active BWP switching, for example at the second time slot (or symbol), the UE may determine to change the related SBFD configuration along with the BWP switching at the same second time slot (or symbol), for example following the same timeline of the active BWP switching.

[0212] In one example, when the UE is operating in a first BWP pair with BWP-ID 1 and is operated based on a first SBFD configuration, in response to receiving a BWP switching command (e.g., via DCI) indicating a switch to a second BWP pair with BWP-ID 2 (e.g., occurring at a second time slot (or symbol)), the UE may determine to (also) change / switch the associated SBFD configuration to the second SBFD configuration at the same second time slot (or symbol), e.g., which is associated with the second BWP pair with BWP-ID 2. The BWP switching command may be received via at least one of a UL-related DCI (e.g., format 0_1, 0_2) and a DL-related DCI (e.g., format 1_1, 1_2). This may provide benefits in terms of low complexity and simplified operational behavior implemented by the UE.

[0213] The conditions mentioned for operation 1 are also applicable to operation 2.

[0214] The UE may be configured (e.g., indicated or predefined / determined) to use operation 1 and operation 2, which means that the application timeline may be shared (the same) for active BWP switching and associated SBFD configuration change / update (e.g., based on operation 2), but whether to change / switch the associated SBFD configuration (e.g., switch to a second SBFD configuration) may vary / determined based on operation 1.

[0215] Operation 3: Based on the active BWP switch, for example, at the second time slot (or symbol), the UE may determine to change the associated SBFD configuration along with the BWP switch at the same second time slot (or symbol) plus a time offset parameter L (e.g., following the timeline of the active BWP switch, but applying the time offset L on top of the timeline). The UE may receive a configuration (or indication) of the L value, which may be the SBFD application time (SAT), where L (e.g., the value of SAT) may be a positive value in time or a negative value in time (or zero, for example, by default). The UE may perform UE capability reporting on the SAT (e.g., supported SAT values), and the L value (SAT) may be UE-specifically configured / indicated to the UE (from the gNB).

[0216] In one example, when the UE is operating in a first BWP pair with BWP-ID 1 and is operated based on a first SBFD configuration, in response to receiving a BWP switching command (e.g., via DCI) indicating a switch to a second BWP pair with BWP-ID 2 (e.g., to occur at a second time slot (or symbol)), the UE may determine to (also) change / switch the associated SBFD configuration to the second SBFD configuration, e.g., associated with the second BWP pair with BWP-ID 2, at the same second time slot (or symbol) plus a time offset parameter L. The BWP switching command may be received via at least one of a UL-related DCI (e.g., format 0_1, 0_2) and a DL-related DCI (e.g., format 1_1, 1_2). The UE shall maintain the current (first) SBFD configuration (e.g., if the UL subband is included in the switching BWP with BWP-ID 2) until the SAT reaches the apply time. If the UE determines that one or more predefined or preconfigured conditions are met, which indicate that the current (first) SBFD configuration cannot be maintained (e.g., if the UL subband is not (fully) contained in the switching BWP with BWP-ID 2), the UE may apply a fallback behavior, such as following / applying the (legacy) "tdd-UL-DL-config-common" and / or applying "tdd-UL-DL-config-dedicated" to "D", "U" and / or "F" modes, or applying UL subband truncation (e.g., to adapt) in the switching second BWP with BWP-ID 2 (based on predefined or preconfigured rules). This may provide benefits in terms of low complexity and simplified operational behavior of the UE implementation, and provide flexibility to adjust the actual application time instance of applying / changing / switching the associated SBFD configuration.

[0217] The conditions mentioned for operation 1 also apply to operation 3.

[0218] The UE may be configured (e.g., indicated or predefined / determined) to use operation 1, operation 2, and / or operation 3. In one example, if the UE is configured (e.g., indicated or predefined / determined) to use all three operations, the application timeline for changing the associated SBFD configuration may be determined based on the timeline of the active BWP switching plus the time offset parameter of L (e.g., based on operation 2 and / or operation 3), but whether to change / switch the associated SBFD configuration (e.g., to the second SBFD configuration) may be varied / determined based on operation 1.

[0219] 2 Configurable CLI measurement types and windows

[0220] Configurable CLI measurement types

[0221] Cross-link interference (CLI) may refer to a signal in one direction (e.g., DL or UL) being interfered with by a signal in another direction (e.g., UL or DL), wherein a first CLI type may be CLI interference occurring due to different TDD DL-UL configurations in adjacent cells, and a second CLI type may be CLI interference occurring due to signal leakage in adjacent frequency sub-bands.

[0222] In an embodiment, one or more CLI measurement types may be defined, determined, or used.

[0223] The first CLI measurement type (CLImeasType1) may refer to (e.g., be defined as) a CLI measurement performed on resources in a legacy downlink slot / symbol, where a legacy downlink slot / symbol may be a downlink (or uplink) slot / symbol in which all resources in the slot / symbol are used, determined, or configured for downlink (or uplink) transmission. Herein, legacy downlink slot / symbol may be used interchangeably with DL-only slot / symbol, non-SBFD slot / symbol, and unidirectional slot / symbol.

[0224] A second CLI measurement type (CLImeasType2) may refer to CLI measurements performed on resources in a SBFD slot / symbol, where the SBFD slot / symbol may be a downlink (or uplink) slot / symbol, where a first subset of resources in the frequency may be used, determined, or configured for transmission in one direction (e.g., downlink or uplink), and a second subset of resources in the frequency may be used, determined, or configured for transmission in another direction (e.g., uplink or downlink).

[0225] CLI measurements in CLImeasType2 may be performed on resources in the downlink direction (eg, a subset of resources for the downlink), which may be referred to as CLImeasType2A.

[0226] CLI measurements in CLImeasType2 may be performed on resources in the uplink direction (eg, a subset of resources of the uplink), which may be referred to as CLImeasType2B.

[0227] CLI measurements in CLImeasType2 may be performed on resources in both downlink and uplink directions, which may be referred to as CLImeasType2C.

[0228] CLI measurements in CLImeasType2 may be performed on resources that may be used to mitigate CLI (eg, gap resources that may be configured, determined, or used between DL and UL resources). CLI measurements performed on gap resources may be referred to as CLImeasType2D.

[0229] The resources measured by CLI can be non-contiguous. For example, CLI measurement resources based on CLImeasType2A can be configured as non-contiguous RB allocations, for example, across Fig.10 Thus, for such non-contiguous CLI measurement resources, the UE may report (or transmit) a single CLI-RSSI (or other metric) report based on measurements of two non-contiguous RBs, or the UE may report (or transmit) separate CLI-RSSI reports, each based on measurements of each contiguous portion of the non-contiguous CLI measurement resources, e.g., based on configuration or instructions from the gNB.

[0230] The third CLI measurement type (CLImeasType3) may refer to CLI measurements performed on resources in both legacy downlink slots / symbols and SBFD slots / symbols, where the CLI measurements in SBFD slots / symbols may be at least one of CLImeasType2A, CLImeasType2B, and CLImeasType2C.

[0231] The fourth CLI measurement type (CLImeasType4) may refer to CLI measurements performed on resources among one or more resources (e.g., DL, UL, or SL resources) configured by the gNB.

[0232] The one or more resources configured by the gNB for CLI measurement may be one or more frequency resources near the frequency resources in another direction (e.g., edge RBs). CLI measurements performed on edge RBs may be referred to as CLImeasType4A.

[0233] One or more resources configured by the gNB for CLI measurement may be zero-power resources (e.g., zero-power CSI-RS, zero-power CLI-RS). CLI measurements performed on zero-power resources may be referred to as CLImeasType4B.

[0234] The UE may perform CLI measurements in one or more resources based on a configured, determined or indicated CLI measurement type (e.g., based on at least one of CLImeasType1, CLImeasType2, CLImeasType2A, CLImeasType2B, CLImeasType2C, CLImeasType2D, CLImeasType3, CLImeasType4, CLImeasType4A, CLImeasType4B).

[0235] In one example, if Fig.10As shown, the UE may receive configuration information indicating a first set of RBs (eg, UL subbands) within a bandwidth portion or carrier that are applicable for uplink transmission in a first set of symbols (eg, SBFD symbols). Fig.10 An example of CLI measurements (CLImeasType2B and / or 2D) for UL subbands is depicted. The configuration information may also include one or more frequency locations on the RB for DL ​​reception (DL subbands), or the UE may identify that the DL subbands are at least outside the UL subbands. The configuration information may also include one or more frequency locations on the RB that are not applicable for DL ​​reception or UL transmission (e.g., "guard bands"), for example, between the UL subband and the DL subband, or the UE may identify that the guard bands are between the UL subband and the DL subband.

[0236] The UE may receive information (e.g., via DCI, MAC-CE, and / or RRC) indicating transmission of an UL channel or signal (e.g., PUSCH, PUCCH, SRS, PRACH, etc.) on a second set of RBs within the first set of RBs and in a second set of symbols including at least one symbol in the first set. The UE may transmit the UL channel or signal on the second set of RBs, e.g., if the UE determines that any CLI measurement resources, types, and / or windows do not overlap with a planned or indicated transmission of the UL channel or signal.

[0237] The UE may receive information (e.g., via DCI, MAC-CE, and / or RRC) indicating that CLI measurements (e.g., based on at least one of CLImeasType1, CLImeasType2, CLImeasType2A, CLImeasType2B, CLImeasType2C, CLImeasType2D, CLImeasType3, CLImeasType4, CLImeasType4A, CLImeasType4B discussed throughout this disclosure) are performed on a third RB set in a third symbol set.

[0238] In one example, the UE may receive information indicating to perform CLI measurement on a third group of RBs in a third group of symbols based on CLImeasType2B (as a resource in the uplink direction) and / or CLImeasType2D (as a gap resource, e.g., between DL and UL resources / subbands). The UE may determine that at least one symbol is included (e.g., overlapped) in the third group of symbols, and at least one RB in the second group of RBs is included in the third group of RBs in at least one symbol. Based on this determination, the UE may transmit an UL channel or signal on the second group of RBs in the second group of symbols, but not including at least one symbol (e.g., due to overlap with the CLI measurement resource). This may provide the benefit of having a higher priority CLI measurement on a UL subband, because the UL subband may generally be used for UL transmission, but the CLI measurement resource may be configured in the UL subband, wherein the UE may prioritize receiving or measuring the CLI measurement resource within the UL subband while abandoning the UL transmission scheduled or indicated at the overlapping time. The UE may transmit (eg, report) one or more measurement values ​​(eg, based on CLI-RSSI, SRS-RSRP, SINR, etc. discussed above herein) by performing CLI measurements on a third group of RBs in a third group of symbols.

[0239] In a case where the UE can determine, for example, based on CLImeasType2D, one or more RBs included in the third group of RBs and excluded in the second group of RBs (e.g., a "guard band"), the UE can transmit (e.g., report) first one or more measurement values ​​by performing a first CLI measurement on one or more RBs in the third group of symbols (e.g., within the guard band), and can transmit (e.g., report) second one or more measurement values ​​by performing a second CLI measurement on the third group of RBs excluding the one or more RBs in the third group of symbols (e.g., within the UL subband).

[0240] based on Fig.10 The examples discussed are non-limiting examples where the UE may (be configured to) determine whether to transmit a scheduled or indicated UL channel or signal based on overlapping resources of CLI measurement resources configured or indicated based on at least one of CLImeasType1, CLImeasType2, CLImeasType2A, CLImeasType2B, CLImeasType2C, CLImeasType2D, CLImeasType3, CLImeasType4, CLImeasType4A, CLImeasType4B. Fig.10The examples discussed are non-limiting examples, wherein the UE may (be configured to) determine whether to receive a scheduled or indicated DL channel or signal based on overlapping resources of configured or indicated CLI measurement resources determined based on at least one of CLImeasType1, CLImeasType2, CLImeasType2A, CLImeasType2B, CLImeasType2C, CLImeasType2D, CLImeasType3, CLImeasType4, CLImeasType4A, CLImeasType4B.

[0241] Configurable CLI measurement window and UE behavior

[0242] In an embodiment, the UE may receive a dynamic indication to change / switch the SBFD configuration (e.g., as the BWP switches, or by an explicit indication from the gNB). In terms of network-wide operation (based on multiple geographically distributed cells and / or gNBs serving multiple different UEs), it may be beneficial to configure / instruct one or more UEs in the network to perform one or more cross-link interference (CLI) measurements within a time (and / or frequency) window, which may be configured (or indicated) based on coordination between cells (and / or gNBs) in the network.

[0243] In an embodiment, a UE (e.g., a UE in one or more UEs) may be configured to perform CLI measurement for at least one type of CLI through at least one timing configuration, for example, based on at least one of CLImeasType1, CLImeasType2, CLImeasType2A, CLImeasType2B, CLImeasType2C, CLImeasType2D, CLImeasType3, CLImeasType4, CLImeasType4A, and CLImeasType4B. Such a timing configuration may be referred to as a "CLI measurement timing configuration" (CMTC) hereinafter.

[0244] The CMTC may be configured by at least one of periodicity, offset relative to a slot or frame boundary, and number of slots. The CMTC may also be configured by a bitmap pattern, where each bit of the bitmap indicates whether the corresponding slot belongs to the CMTC, and the pattern is assumed to repeat indefinitely.

[0245] When performing CLI measurements in CMTC, the UE may lower the priority of transmission or reception of certain channels. For example, the UE may abandon reception of PDSCH or transmission of PUSCH / SRS or PUCCH. Possibly, the UE may abandon reception or transmission of such channels only if the time and / or frequency domain overlaps with the resources used for the configured CLI measurement instance. The UE may lower the priority of other types of radio resource management (RRM) measurements, such as RSRP, RSRQ, RSSI, etc. In some schemes, a priority parameter may be used to explicitly configure the priority between different types of RRM measurements and different types of CLI measurements. Priorities may be configured by measurement object (or frequency), RAT, or type. Different priorities may be configured in different time instances to ensure that the amount of each type of measurement is minimized.

[0246] The UE may be configured to measure at least one CLI measurement instance. Each CLI measurement instance may be configured with at least one CLI measurement type (e.g., defined in the previous section), a frequency domain configuration, and a time domain configuration or CMTC. Applicable frequency domain configurations may include a starting (e.g., lowest) RB index, a number of RBs, and / or a highest RB index, or a bitmap, where each bit position may represent an RB. The frequency domain configuration may be represented as a frequency domain resource allocation (FDRA) field, as defined in a conventional scheme. Applicable time domain configurations may include periodicity, offset, and / or a bitmap, where each bit position may represent a time slot or symbol.

[0247] At least one frequency domain configuration and / or time domain configuration may be implicitly determined from the configuration aspects of SBFD, for example, a set of time slots applicable to a certain type of SBFD, a frequency range of UL or DL ​​operation within a type of SBFD time slot, UL / DL time slot configuration, etc.

[0248] The measured quantities of the CLI instance may include interference level, received signal strength indicator (RSSI), and / or signal-to-interference ratio (SINR). In the latter case, the signal may be derived from the RSRP measured on another measurement resource (e.g., non-zero power (NZP) CSI-RS or SS block). The measurement results may be in linear units or dB units. The interference result and / or RSSI may be normalized by the number of resource blocks configured for the measurement. This may be referred to as a "normalized" interference level or RSSI.

[0249] The UE may be configured with at least one reporting configuration that may include criteria or events for transmitting a measurement report containing CLI measurement results. Such events may include at least the following and may be configured with supporting parameters (e.g., thresholds, offsets): (normalized) interference / RSSI / SINR becomes higher (lower) than a threshold for a CLI instance; and (normalized) interference / RSSI / SINR from a first CLI instance becomes higher (lower) than the interference from a second CLI instance plus an offset.

[0250] The latter event may be useful in helping the network identify sources of interference (eg, cross-link interference from neighboring cells versus adjacent frequency interference from the uplink portion of the SBFD slot / symbol).

[0251] When a measurement report is transmitted, measurement results for each configured CLI instance may be included, where this behavior may be configured or indicated to the UE.

[0252] in conclusion

[0253] Although features and elements are provided above in specific combinations, it will be understood by those skilled in the art that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in the present application, which are intended to be illustrations of various aspects. Without departing from its spirit and scope, many modifications and changes can be made, as will be apparent to those skilled in the art. Any element, action or instruction used in the description of the present application should not be interpreted as being critical or necessary to the present invention unless explicitly provided as such. In addition to those listed herein, functionally equivalent methods and devices within the scope of the present disclosure are apparent to those skilled in the art from the foregoing description. Such modifications and changes are intended to fall within the scope of the appended claims. The present disclosure is limited only by the terms of the appended claims and the full scope of equivalents given by such claims. It should be understood that the present disclosure is not limited to specific methods or systems herein.

[0254] For simplicity, the foregoing embodiments are discussed with respect to terminology and structure of devices with infrared capabilities (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0255] It will also be understood that the terms used herein are used only for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or a plurality of images displayed over a certain time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of many embodiments of a WTRU; (iii) a device with wireless capabilities and / or wired capabilities (e.g., wearable) that is configured with some or all of the structure and functionality of a WTRU; (iii) a device with wireless capabilities and / or wired capabilities that is configured with less than all of the structure and functionality of a WTRU; or (iv) a similar device. References herein to Figures 1A to 1D Details of an example WTRU are provided, which may be representative of any WTRU set forth herein. As another example, various disclosed embodiments herein are described above and below as utilizing a head mounted display. Those skilled in the art will recognize that devices other than a head mounted display may be utilized, and some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0256] In addition, the methods provided herein may be implemented in a computer program, software, or firmware that is incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of non-temporary computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, 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 associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0257] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the embodiments shown are merely examples and should not be considered to limit the scope of the appended claims. For example, the embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery, etc.) that provides any suitable voltage.

[0258] In addition, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices including processors are mentioned. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to actions and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as "execution," "computer execution," or "CPU execution."

[0259] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which may cause the final conversion or reduction of electrical signals and maintain the data bits in memory locations in the storage system, thereby reconfiguring or otherwise changing the operation of the CPU and other processing of signals. The memory locations where the data bits are maintained are physical locations having specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may support the provided methods.

[0260] The data bits may also be maintained on a computer-readable medium, including a magnetic disk, an optical disk, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system readable by a CPU. The computer-readable medium may include cooperating or interconnected computer-readable media that reside only on a processing system or distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may support the provided methods.

[0261] In an illustrative embodiment, any operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0262] There is little difference between hardware and software implementations of various aspects of the system. The use of hardware or software is usually (but not always, as in some cases, the choice of hardware or software may become important) a design choice that represents a cost-efficiency trade-off. There may be various vehicles (e.g., hardware, software, and / or firmware) with which the processes and / or systems and / or other technologies described herein can be implemented, and the preferred vehicle may change with the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are most important, then the implementer may select a primary hardware and / or firmware vehicle. If flexibility is most important, then the implementer may select a primary software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0263] The foregoing detailed description has been described various embodiments of the apparatus and / or process by using block diagrams, flow charts and / or examples. Insofar as such block diagrams, flow charts and / or examples include one or more functions and / or operations, it will be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or indeed any combination thereof. In an embodiment, several parts of the subject matter described herein may be implemented via an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP) and / or other integrated formats. However, those skilled in the art will recognize that all or part of some aspects of the embodiments disclosed herein may be equivalently implemented in an integrated circuit, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware or almost as any combination thereof, and according to the present disclosure, designing circuit systems and / or writing codes for software and / or firmware will be completely within the skill range of those skilled in the art. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a program product in a variety of forms, and that the illustrative examples of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually carry out the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.; and transmission media such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0264] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system by a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system can typically include a system unit housing, a video display device, a memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, a computing entity such as an operating system, a driver, a graphical user interface, and an application, one or more interactive devices such as a touch pad or screen, and / or a control system including a feedback loop and a control motor (e.g., feedback for sensing position and / or velocity; a control motor for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as components typically found in data computing / communication and / or network computing / communication systems.

[0265] The subject matter described herein sometimes illustrates different parts that are included in different other parts or connected with different other parts.It should be understood that the architecture of such description is only an example, and many other architectures that realize the same function can actually be implemented.In a conceptual sense, any arrangement of parts for realizing the same function is effectively "associated" so that the desired function can be realized.Therefore, any two parts that are combined to realize a specific function in this article can be regarded as "associated" with each other so that no matter how the architecture or intermediate parts realize the desired function.Similarly, any two parts that are associated in this way can also be regarded as "operably connected" or "operably coupled" to realize the desired function, and any two parts that can be associated in this way can also be regarded as "operably coupled" to realize the desired function.The specific example of operable coupling includes (but is not limited to) parts that can be matched physically and / or physically interact, and / or parts that can be wirelessly interacted and / or wirelessly interacted, and / or parts that can be logically interacted and / or parts that can be logically interacted.

[0266] With respect to the use of substantially any plural and / or singular terms herein, those skilled in the art can translate from the plural to the singular and / or from the singular to the plural where appropriate to the context and / or application. For clarity, the various singular / plural arrangements may be expressly set forth herein.

[0267] Those skilled in the art will understand that, in general, the terms used herein and particularly in the appended claims (e.g., the bodies of the appended claims) are generally intended to be "open" terms (e.g., the term "comprising" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "including" should be interpreted as "including but not limited to," etc.). Those skilled in the art will further understand that if a specific number of an introduced claim statement is intended, such intent will be expressly stated in the claim, and in the absence of such a statement, no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce multiple claim statements. However, the use of such phrases should not be interpreted as implying that a claim recitation introduced by the indefinite article "a" or "an" will limit any particular claim including such introduced claim recitation to embodiments including only one such recitation, even if the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same is true for the use of definite articles to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, one skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited number (e.g., merely reciting "two recitations" without other modifiers means at least two recitations or two or more recitations). Furthermore, in those cases where a convention similar to “at least one of A, B, and C, etc.” is used, generally, such construction is intended to represent the convention that one skilled in the art would understand (e.g., “a system having at least one of A, B, and C” would include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C, etc.). In those cases where a convention similar to “at least one of A, B, or C, etc.” is used, generally, such meaning is intended in the sense that one skilled in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C, etc.). One skilled in the art would further understand that any transitional word and / or phrase (whether in the specification, claims, or drawings) that actually gives two or more alternatives should be understood to contemplate the possibility of including one of the items, either of the items, or both of the items. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B."Furthermore, as used herein, the term "any" followed by a plurality of items and / or a listing of items in a plurality of categories is intended to include "any," "any combination," "any plurality," and / or "any combination of plurality," either alone or in combination with other items and / or items in other categories. Furthermore, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And as used herein, the term "plurality" is intended to be synonymous with "plurality."

[0268] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0269] As will be understood by those skilled in the art, for any and all purposes, such as in providing a written description, all ranges disclosed herein also encompass any and all possible sub-ranges and combinations of sub-ranges thereof. Any listed range can be easily identified as fully describing and capable of decomposing the same range into at least equal halves, one-third, one-quarter, one-fifth, one-tenth, etc. As a non-limiting example, each range discussed herein can be easily decomposed into a lower third, a middle third, and an upper third, etc. As will be understood by those skilled in the art, all languages ​​such as "at most", "at least", "greater than", "less than", etc. include the enumerated numbers, and refer to the ranges that can be subsequently subdivided into sub-ranges as discussed above. Finally, as will be understood by those skilled in the art, the range includes each individual member. Therefore, for example, a group with 1 to 3 units refers to a group with 1, 2 or 3 units. Similarly, a group with 1 to 5 units refers to a group with 1, 2, 3, 4 or 5 units, and so on.

[0270] Furthermore, the claims should not be read as limited to the order or elements provided unless otherwise stated. In addition, the use of the term "means for..." in any claim is intended to invoke 35 U.S.C. § 112, or means-plus-function claim format, and any claim without the term "means for..." is not intended to be so.

Claims

1. A wireless transmit / receive unit (WTRU), the WTRU being configured to: receiving information indicating an uplink (UL) subband (SB); receiving an indication to perform measurements on a first set of resource blocks (RBs) and a first set of symbols, wherein the first set of symbols includes first one or more sub-band non-overlapping full-duplex (SBFD) symbols; Determine a first measurement value of at least one first RB in the first group of RBs that is outside the UL SB and a second measurement value of at least one second RB in the first group of RBs that is outside the UL SB, wherein the at least one first RB and the at least one second RB are non-contiguous; as well as A message based on the first measurement and the second measurement is transmitted.

2. The WTRU of claim 1 , wherein: The first measurement value, the second measurement value, or the first measurement value and the second measurement value are cross-link interference (CLI) measurements.

3. The WTRU of claim 2, wherein: The second measurement value includes a CLI measurement value of a second group of RBs, the second group of RBs including one or more RBs in the first group of RBs, the second group of RBs corresponding to a DL region, a guard band, an edge of the UL SB, or an edge of a DL region in the first one or more SBFD symbols.

4. The WTRU of claim 3, wherein: The WTRU is also configured to: The second set of RBs is determined based on the received measurement type indication.

5. The WTRU of any one of claims 1 to 4, wherein: The WTRU is also configured to: An indication is received to transmit on a UL channel in a third group of RBs and a third group of symbols, wherein the third group of RBs is located in the UL SB and the third group of symbols includes one or more third SBFD symbols.

6. The WTRU of claim 5, wherein: The WTRU is also configured to: Under the condition that at least one symbol in the third group of SBFD symbols overlaps with a symbol in the first group of SBFD symbols, the UL channel is transmitted using the third group of RBs and a subset of the third group of symbols, wherein the subset includes the following symbols in the third group of symbols: a) symbols that are not SBFD symbols; or b) SBFD symbols that do not overlap with symbols in the first group of SBFD symbols.

7. A method at a wireless transmit / receive unit (WTRU), the method comprising: receiving information indicating an uplink (UL) subband (SB); receiving an indication to perform measurements on a first set of resource blocks (RBs) and a first set of symbols, wherein the first set of symbols includes first one or more sub-band non-overlapping full-duplex (SBFD) symbols; Determine a first measurement value of at least one first RB in the first group of RBs that is outside the UL SB and a second measurement value of at least one second RB in the first group of RBs that is outside the UL SB, wherein the at least one first RB and the at least one second RB are non-contiguous; as well as A message based on the first measurement and the second measurement is transmitted.

8. The method according to claim 7, wherein: The first measurement value, the second measurement value, or the first measurement value and the second measurement value are cross-link interference (CLI) measurements.

9. The method according to claim 8, wherein: The second measurement value includes a CLI measurement value of a second group of RBs, the second group of RBs including one or more RBs in the first group of RBs, the second group of RBs corresponding to a DL region, a guard band, an edge of the UL SB, or an edge of a DL region in the first one or more SBFD symbols.

10. The method according to claim 9, further comprising: A second set of RBs is determined based on the received measurement type indication.

11. The method according to any one of claims 7 to 10, further comprising: An indication is received to transmit on a UL channel in a third group of RBs and a third group of symbols, wherein the third group of RBs is located in the UL SB and the third group of symbols includes one or more third SBFD symbols.

12. The method according to claim 11, further comprising: Under the condition that at least one symbol in the third group of SBFD symbols overlaps with a symbol in the first group of SBFD symbols, the UL channel is transmitted using the third group of RBs and a subset of the third group of symbols, wherein the subset includes the following symbols in the third group of symbols: a) symbols that are not SBFD symbols; or b) SBFD symbols that do not overlap with symbols in the first group of SBFD symbols.

Images