CN118104174A - Dynamic slot format indication and WTRU behavior associated with XDD - Google Patents
Dynamic slot format indication and WTRU behavior associated with XDD Download PDFInfo
- Publication number
- CN118104174A CN118104174A CN202280068491.6A CN202280068491A CN118104174A CN 118104174 A CN118104174 A CN 118104174A CN 202280068491 A CN202280068491 A CN 202280068491A CN 118104174 A CN118104174 A CN 118104174A
- Authority
- CN
- China
- Prior art keywords
- wtru
- resources
- symbols
- slot
- dci
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000000737 periodic effect Effects 0.000 claims abstract description 78
- 238000000034 method Methods 0.000 claims abstract description 24
- 230000005540 biological transmission Effects 0.000 claims description 148
- 238000004891 communication Methods 0.000 claims description 61
- 230000011664 signaling Effects 0.000 description 35
- 238000012544 monitoring process Methods 0.000 description 28
- 238000005516 engineering process Methods 0.000 description 24
- 238000005259 measurement Methods 0.000 description 24
- 230000006870 function Effects 0.000 description 19
- 230000006399 behavior Effects 0.000 description 14
- 238000013468 resource allocation Methods 0.000 description 11
- 238000012360 testing method Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 9
- 238000013507 mapping Methods 0.000 description 9
- 238000001228 spectrum Methods 0.000 description 9
- 241000760358 Enodes Species 0.000 description 8
- 238000013475 authorization Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 8
- 230000004044 response Effects 0.000 description 7
- 230000009471 action Effects 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 229910052770 Uranium Inorganic materials 0.000 description 4
- 230000002776 aggregation Effects 0.000 description 4
- 238000004220 aggregation Methods 0.000 description 4
- 239000000969 carrier Substances 0.000 description 4
- 125000004122 cyclic group Chemical group 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- MJSPPDCIDJQLRE-YUMQZZPRSA-N S-methionyl-L-thiocitrulline Chemical compound CSCC[C@@H](C(S/C(\N)=N/CCC[C@@H](C(O)=O)N)=O)N MJSPPDCIDJQLRE-YUMQZZPRSA-N 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000004088 simulation Methods 0.000 description 3
- 101100172132 Mus musculus Eif3a gene Proteins 0.000 description 2
- 238000004873 anchoring Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 229910001416 lithium ion Inorganic materials 0.000 description 2
- 239000011159 matrix material Substances 0.000 description 2
- QELJHCBNGDEXLD-UHFFFAOYSA-N nickel zinc Chemical compound [Ni].[Zn] QELJHCBNGDEXLD-UHFFFAOYSA-N 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000005355 Hall effect Effects 0.000 description 1
- 101100020598 Homo sapiens LAPTM4A gene Proteins 0.000 description 1
- HBBGRARXTFLTSG-UHFFFAOYSA-N Lithium ion Chemical compound [Li+] HBBGRARXTFLTSG-UHFFFAOYSA-N 0.000 description 1
- 102100034728 Lysosomal-associated transmembrane protein 4A Human genes 0.000 description 1
- 101150071746 Pbsn gene Proteins 0.000 description 1
- 241000700159 Rattus Species 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- OJIJEKBXJYRIBZ-UHFFFAOYSA-N cadmium nickel Chemical compound [Ni].[Cd] OJIJEKBXJYRIBZ-UHFFFAOYSA-N 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000000873 masking effect Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 229910052987 metal hydride Inorganic materials 0.000 description 1
- 230000000116 mitigating effect Effects 0.000 description 1
- 229910052759 nickel Inorganic materials 0.000 description 1
- PXHVJJICTQNCMI-UHFFFAOYSA-N nickel Substances [Ni] PXHVJJICTQNCMI-UHFFFAOYSA-N 0.000 description 1
- -1 nickel metal hydride Chemical class 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000007727 signaling mechanism Effects 0.000 description 1
- 230000000153 supplemental effect Effects 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
- 238000000411 transmission spectrum Methods 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
Systems, methods, and instrumentalities associated with supporting flexible (e.g., sub-band by sub-band) slot format indications that may include a slot type (e.g., new slot type) "M n" as a "hybrid" DL/UL are disclosed herein. Tx/Rx rules for periodic/semi-persistent configuration according to sub-band slot type for XDD may be provided. The search space may be associated with a plurality CORESET. In an example, the WTRU may determine which CORESET to use to monitor the search space based on the slot type (e.g., XDD slot or non-XDD slot). The WTRU may determine to monitor the search space in the XDD slot based on the "M n" type and/or the amount of search space resources reallocated for uplink in the slot. One or more sets of search spaces may be configured and which set of search spaces to monitor may be determined based on the slot type.
Description
Cross Reference to Related Applications
The present application claims priority from U.S. provisional patent application No. 63/244,471, filed on 9, 15, 2021, and U.S. provisional patent application No. 63/395,969, filed on 8, 2022, which provisional patent applications are incorporated herein by reference in their entirety.
Background
Mobile communications using wireless communications continue to evolve. The fifth generation mobile communication Radio Access Technology (RAT) may be referred to as 5G New Radio (NR). The previous generation (legacy) mobile communication RAT may be, for example, fourth generation (4G) Long Term Evolution (LTE). The wireless communication device may establish communication with other devices and data networks, for example, via an access network such as a Radio Access Network (RAN).
Disclosure of Invention
Systems, methods, and instrumentalities associated with supporting flexible (e.g., sub-band by sub-band) slot format indications that may include a slot type (e.g., new slot type) "M n" as a "hybrid" DL/UL are disclosed herein. The WTRU may receive a slot/symbol format indication that includes an "M n" type. In one or more cases, the M n type may be associated with a first set of RBs (e.g., for UL) and a second set of RBs (e.g., for DL).
Tx/Rx rules for periodic/semi-persistent configuration according to sub-band slot type for XDD may be provided. In one or more cases, the WTRU may transmit an uplink channel/signal on one or more symbols (e.g., a first set of symbols). For example, the WTRU may transmit an uplink channel/signal on the first set of symbols when the first set of symbols is indicated by an "M n" type (e.g., n=1 or 2 …) and the first set of RBs of the "M n" type include one or more RBs allocated for the uplink channel/signal. In one or more cases, the WTRU may receive the downlink channel/signal on one or more symbols (e.g., a second set of symbols). For example, the WTRU may receive a downlink channel/signal on the second set of symbols when the second set of symbols is indicated by an "M n" type (n=1 or 2 …) and the second set of RBs of the "M n" type includes one or more RBs allocated for the downlink channel/signal.
The search space may be associated with a plurality CORESET. In an example, the WTRU may determine which CORESET to use to monitor the search space based on the slot type (e.g., XDD slot or non-XDD slot). The WTRU may determine to monitor the search space in the XDD slot based on the "M n" type and/or the amount of search space resources reallocated for uplink in the slot. One or more sets of search spaces may be configured and the set of search spaces to monitor may be determined based on the slot type.
In one or more cases, the WTRU may be configured by higher layers or (e.g., dynamically) scheduled to transmit UL signals (e.g., PUSCH, PUCCH, PRACH, UL RS, etc.) in the resources. The WTRU may transmit an UL signal if the resources are valid for UL transmission based on at least one UL SB (e.g., included therein) indicated by at least one sub-band non-overlapping full duplex (SBFD) (e.g., or XDD) signaling. In one or more cases, the WTRU may skip (e.g., discard, stop, skip as an abnormal situation/operation, not proceed, not perform) monitoring/receiving control channels (e.g., PDCCH, DCI) under the condition that the WTRU determines that resources are available for UL transmission based on at least one UL SB in the symbol/slot. Thus, if this condition is met, skipping monitoring of a control channel (e.g., DCI) in a symbol/slot via a control channel based on CORESET may reduce WTRU complexity and improve efficiency of communication with SBFD.
In one or more cases, the WTRU may be configured to implement NR duplex operation based on sub-band non-overlapping full duplex (SBFD).
In one or more cases, the WTRU may be configured to receive information (e.g., via DCI or MAC CE) indicating that a first subset of Resource Blocks (RBs) of the plurality of Resource Blocks (RBs) associated with one or more symbols is an RB for Downlink (DL) reception. Additionally and/or alternatively, the WTRU may be configured to receive information (e.g., via DCI or MAC CE) indicating that a second subset of RBs of the plurality of RBs associated with one or more symbols are RBs for Uplink (UL) transmission.
In one or more cases, the WTRU may be configured to receive a DL transmission associated with periodic DL resources in one or more symbols if the periodic DL resources (e.g., PDCCH/CG-PDSCH) are included in a first subset of RBs indicated by the information as RBs for DL reception. In one or more cases, the WTRU may be configured to send UL transmissions associated with periodic UL resources (e.g., PUCCH/CG-PUSCH) in one or more symbols. For example, in some cases, the WTRU may be configured to send UL transmissions associated with periodic UL resources in one or more symbols on the condition that the periodic UL resources (e.g., PUCCH/CG-PUSCH) are included in a second subset of RBs indicated by the information as RBs for UL reception.
In one or more cases, the WTRU may be configured to receive configuration information (e.g., via RRC) indicating a plurality of UL/DL RB configurations. In one or more cases, this information (e.g., received via DCI and/or MAC-CE) may indicate which of a plurality of UL/DL RB configurations applies to one or more symbols. In one or more cases, the WTRU may be configured to discard at least one other UL transmission associated with a periodic UL resource (e.g., PUCCH/CG-PUSCH). In one or more cases, the WTRU may be configured to discard at least one other UL transmission associated with periodic UL resources in one or more symbols if the periodic UL resources (e.g., PUCCH/CG-PUSCH) are included in a first set of RBs indicated by the information as RBs for DL reception.
The WTRU may receive an indication that each of the one or more symbols includes both a first subset of resource blocks associated with Downlink (DL) reception and a second subset of resource blocks associated with Uplink (UL) transmission. The WTRU may receive DL transmissions associated with one or more periodic DL resources in the one or more symbols on condition that the one or more periodic DL resources are included in a first subset of resource blocks associated with DL reception of the one or more symbols. For example, one or more periodic DL resources may be used for one or more of a Physical Downlink Control Channel (PDCCH) or a configuration grant physical downlink shared channel (CG-PDSCH). The WTRU may transmit a first UL transmission associated with one or more periodic UL resources in the one or more symbols on condition that the one or more periodic UL resources are included in a second subset of resource blocks associated with UL transmission of the one or more symbols. For example, periodic UL resources may be used for one or more of Physical Uplink Control Channel (PUCCH) or configuration grant physical uplink shared channel (CG-PUSCH).
The WTRU may receive configuration information (e.g., in a Radio Resource Control (RRC) message) indicating a plurality of UL/DL resource block patterns for one or more symbols. For example, a bitmap may be used to indicate multiple UL/DL resource block patterns. The indication may be received via Downlink Control Information (DCI) or a Medium Access Control (MAC) Control Element (CE) and may indicate which one of a plurality of UL/DL resource block patterns indicated in the configuration information is to be applied to one or more symbols. The indication may indicate that a first UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a first symbol of the one or more symbols and a second UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a second symbol of the one or more symbols.
The WTRU may discard the second UL transmission associated with the one or more second periodic UL resources in the one or more symbols on condition that the one or more second periodic UL resources are included in the first resource block subset associated with DL reception of the one or more symbols. The WTRU may not receive the second DL transmission associated with the one or more second periodic DL resources in the one or more symbols if the one or more second periodic DL resources are included in the second subset of resource blocks associated with UL reception of the one or more symbols.
Drawings
Fig. 1A is a system diagram illustrating an exemplary communication system.
Fig. 1B is a system diagram illustrating an exemplary wireless transmit/receive unit (WTRU) that may be used within the communication system shown in fig. 1A.
Fig. 1C is a system diagram illustrating an exemplary Radio Access Network (RAN) and an exemplary Core Network (CN) that may be used within the communication system shown in fig. 1A.
Fig. 1D is a system diagram illustrating another exemplary RAN and another exemplary CN that may be used in the communication system shown in fig. 1A.
Fig. 2 shows an example of FD-gNB and HD-WTRU in a cell.
Fig. 3 shows an example of the "M 1" type.
Fig. 4 shows an example of the "M 2" type.
Fig. 5 shows an exemplary sub-band non-overlapping full duplex (SBFD).
Fig. 6 shows an example of SBFD operation based on a hybrid UL/DL type (M n).
Fig. 7 shows an example of sub-band-by-sub-band BWP dynamic muting for XDD.
Detailed Description
Fig. 1A is a schematic diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. Communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messages, broadcasts, etc., to a plurality of wireless users. Communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, 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 Multicarrier (FBMC), and the like.
As shown in fig. 1A, the communication system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, rans 104/113, cns 106/115, public Switched Telephone Networks (PSTN) 108, the internet 110, and other networks 112, although it will be understood 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. As an example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a "station" and/or a "STA") may be configured to transmit and/or receive wireless signals and may include User Equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular telephones, personal Digital Assistants (PDAs), smartphones, laptop computers, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, internet of things (IoT) devices, watches or other wearable devices, head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in an industrial and/or automated processing chain environment), consumer electronics devices, devices operating on a commercial and/or industrial wireless network, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
Communication system 100 may also include base station 114a and/or 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 to facilitate access to one or more communication networks, such as the CN 106/115, the internet 110, and/or the other network 112. By way of example, the base stations 114a, 114B may be Base Transceiver Stations (BTSs), node bs, evolved node bs, home evolved node bs, gnbs, NR node bs, site controllers, access Points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
Base station 114a may be part of RAN 104/113, which may also include other base stations and/or network elements (not shown), such as Base Station Controllers (BSCs), radio Network Controllers (RNCs), relay nodes, and the like. Base station 114a and/or 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 cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of wireless services to a particular geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of a cell. In one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of a cell. For example, beamforming may be used to transmit and/or receive signals in a desired spatial direction.
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, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable Radio Access Technology (RAT).
More specifically, as noted above, 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, or the like. For example, a 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 interfaces 115/116/117.WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or evolved HSPA (hspa+). HSPA may include high speed Downlink (DL) packet access (HSDPA) and/or High Speed UL Packet Access (HSUPA).
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 use Long Term Evolution (LTE) and/or LTE-advanced (LTE-a) and/or LTE-advanced Pro (LTE-a Pro) to establish the air interface 116.
In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may use a New Radio (NR) to establish the air interface 116.
In embodiments, 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 implement LTE radio access and NR radio access together, e.g., using a Dual Connectivity (DC) principle. 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).
In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., wireless fidelity (WiFi)), IEEE 802.16 (i.e., worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000 1X, CDMA EV-DO, tentative standard 2000 (IS-2000), tentative standard 95 (IS-95), tentative standard 856 (IS-856), global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE (GERAN), and the like.
The base station 114B in fig. 1A may be, for example, a wireless router, home node B, home evolved node B, or access point, and may utilize any suitable RAT to facilitate wireless connections in local areas such as business, home, vehicle, campus, industrial facility, air corridor (e.g., for use by drones), road, etc. In one 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 another 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 a pico cell base station or femto cell base station. As shown in fig. 1A, the base station 114b may have a direct connection with the internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106/115.
The RANs 104/113 may communicate with the CNs 106/115, which may be any type of network configured to provide voice, data, application, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102 d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location based services, prepaid calls, internet connections, video distribution, etc., and/or perform advanced security functions such as user authentication. Although not shown in fig. 1A, it should be appreciated that the RANs 104/113 and/or CNs 106/115 may communicate directly or indirectly with other RANs that employ the same RAT as the RANs 104/113 or a different RAT. For example, in addition to being connected to a RAN 104/113 that may utilize NR radio technology, the CN 106/115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA 2000, wiMAX, E-UTRA, or WiFi radio technology.
The CN 106/115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112.PSTN 108 may include circuit-switched telephone networks that provide Plain Old Telephone Services (POTS). The internet 110 may include a global system for interconnecting computer networks and devices using common communication protocols, such as Transmission Control Protocol (TCP), user Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP internet protocol suite. Network 112 may include wired and/or wireless communication networks owned and/or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RANs 104/113 or a different RAT.
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 over different wireless links). For example, the WTRU 102c shown in fig. 1A may be configured to communicate with a base station 114a, which may employ a cellular-based radio technology, and with a base station 114b, which may employ an IEEE 802 radio technology.
Fig. 1B is a system diagram illustrating an exemplary WTRU 102. As shown in fig. 1B, the WTRU 102 may include 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 peripheral devices 138, etc. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
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 in association 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, or the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which may be coupled to a transmit/receive element 122. Although fig. 1B depicts the processor 118 and the transceiver 120 as separate components, it should be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
The transmit/receive element 122 may be configured to transmit signals to and receive signals from a base station (e.g., base station 114 a) over the air interface 116. For example, in one 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 an emitter/detector configured to emit and/or receive, for example, IR, UV, or visible light signals. In another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF signals and optical signals. It should be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
Although the transmit/receive element 122 is depicted as a single element in fig. 1B, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one 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.
The transceiver 120 may be configured to modulate signals to be transmitted by the transmit/receive element 122 and demodulate signals received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (such as NR and IEEE 802.11).
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, such as 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. Further, the processor 118 may access information from and store data in any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include Random Access Memory (RAM), read Only Memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a Subscriber Identity Module (SIM) card, a memory stick, a Secure Digital (SD) memory card, and the like. In other embodiments, the processor 118 may never physically locate memory access information on the WTRU 102, such as on a server or home computer (not shown), and store the data in that memory.
The processor 118 may receive power from the power source 134 and may be configured to distribute 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 battery packs (e.g., nickel cadmium (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), solar cells, fuel cells, and the like.
The processor 118 may also be coupled to a 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 information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114 b) over the air interface 116 and/or determine its location based on the timing of signals received from two or more nearby base stations. It should be appreciated that the WTRU 102 may obtain location information by any suitable location determination method while remaining consistent with an embodiment.
The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software modules and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, the number of the cells to be processed, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photographs and/or video), universal Serial Bus (USB) ports, vibrating devices, television transceivers, hands-free headsets, wireless communications devices, and the like,Modules, frequency Modulation (FM) radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and/or augmented reality (VR/AR) devices, activity trackers, and the like. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; a geographic position sensor; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and/or humidity sensors.
WTRU 102 may include a full duplex radio for which transmission and reception of some or all signals (e.g., associated with a particular subframe for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and/or simultaneous. The full duplex radio station may include an interference management unit for reducing and/or substantially eliminating self-interference via hardware (e.g., choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with a particular subframe for UL (e.g., for transmission) or downlink (e.g., for reception)).
Fig. 1C is a system diagram illustrating a RAN 104 and a CN 106 according to one embodiment. As noted above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using an E-UTRA radio technology. RAN 104 may also communicate with CN 106.
RAN 104 may include enode bs 160a, 160B, 160c, but it should be understood that 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 to communicate with the WTRUs 102a, 102B, 102c over the air interface 116. In one embodiment, the evolved node bs 160a, 160B, 160c may implement MIMO technology. Thus, the enode B160 a may use multiple antennas to transmit wireless signals to and/or receive wireless signals from the WTRU 102a, for example.
Each of the evolved node bs 160a, 160B, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and/or DL, and the like. As shown in fig. 1C, the enode bs 160a, 160B, 160C may communicate with each other over an X2 interface.
The CN 106 shown in fig. 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and/or operated by entities other than the CN operator.
The MME 162 may be connected to each of the evolved node bs 162a, 162B, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating the user of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, and the like. MME 162 may provide control plane functionality for switching between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and/or WCDMA.
SGW 164 may be connected to each of the evolved node bs 160a, 160B, 160c in RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102 c. The SGW 164 may perform other functions such as anchoring user planes during inter-enode B handover, triggering paging when DL data is available to the WTRUs 102a, 102B, 102c, managing and storing the contexts of the WTRUs 102a, 102B, 102c, etc.
The SGW 164 may be connected to a PGW 166 that may provide the WTRUs 102a, 102b, 102c with access to a packet switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network (such as the PSTN 108) to facilitate communications between the WTRUs 102a, 102b, 102c and legacy landline communication devices. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves 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.
Although the WTRU is depicted in fig. 1A-1D as a wireless terminal, it is contemplated that in some representative embodiments such a terminal may use a wired communication interface with a communication network (e.g., temporarily or permanently).
In representative embodiments, the other network 112 may be a WLAN.
A WLAN in an infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic to and/or from the BSS. Traffic originating outside the BSS and directed to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be sent to the AP to be delivered to the respective destination. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may pass the traffic to the destination STA. Traffic between STAs within a BSS may be considered and/or referred to as point-to-point traffic. Point-to-point traffic may be sent between (e.g., directly between) the source and destination STAs using Direct Link Setup (DLS). 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 (e.g., 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.
When using the 802.11ac infrastructure mode of operation or similar modes of operation, the AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access/collision avoidance (CSMA/CA) may be implemented, for example, in an 802.11 system. For CSMA/CA, STAs (e.g., each STA), including the AP, may listen to the primary channel. If the primary channel is listened to/detected by a particular STA and/or determined to be busy, the particular STA may backoff. One STA (e.g., only one station) may transmit at any given time in a given BSS.
High Throughput (HT) STAs may communicate using 40MHz wide channels, for example, via a combination of a primary 20MHz channel with an adjacent or non-adjacent 20MHz channel to form a 40MHz wide channel.
Very High Throughput (VHT) STAs may support channels that are 20MHz, 40MHz, 80MHz, and/or 160MHz wide. 40MHz and/or 80MHz channels may be formed by combining consecutive 20MHz channels. The 160MHz channel may be formed by combining 8 consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels (this may be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data may pass through a segment parser that may split the data into two streams. An Inverse Fast Fourier Transform (IFFT) process and a time domain process may be performed on each stream separately. These streams may be mapped to two 80MHz channels and data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed and the combined data may be sent to a Medium Access Control (MAC).
The 802.11af and 802.11ah support modes of operation below 1 GHz. Channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11 ac. The 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the television white space (TVWS) spectrum, and the 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter type control/machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including supporting (e.g., supporting only) certain bandwidths and/or limited bandwidths. MTC devices may include batteries with battery lives above a threshold (e.g., to maintain very long battery lives).
WLAN systems that can support multiple channels, and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as primary channels. 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 STAs from all STAs operating in the BSS (which support a minimum bandwidth mode of operation). In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only) 1MHz mode, the primary channel may be 1MHz wide, even though the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and/or other channel bandwidth modes of operation. The carrier sense and/or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because the STA (supporting only 1MHz mode of operation) is transmitting to the AP, the entire available frequency band may be considered busy even though most of the frequency band remains idle and possibly available.
The available frequency band for 802.11ah in the united states is 902MHz to 928MHz. In 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.
Fig. 1D is a system diagram illustrating RAN 113 and CN 115 according to one embodiment. As noted above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, 102c over an air interface 116. RAN 113 may also communicate with CN 115.
RAN 113 may include gnbs 180a, 180b, 180c, although it will be appreciated that RAN 113 may include any number of gnbs while remaining consistent with an embodiment. Each of the gnbs 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, gnbs 180a, 180b, 180c may implement MIMO technology. For example, gnbs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from gnbs 180a, 180b, 180 c. Thus, the gNB 180a may use multiple antennas to transmit wireless signals to and/or receive wireless signals from the WTRU 102a, for example. In an embodiment, the gnbs 180a, 180b, 180c may implement carrier aggregation techniques. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on the unlicensed spectrum while the remaining component carriers may be on the licensed spectrum. In embodiments, the gnbs 180a, 180b, 180c may implement coordinated multipoint (CoMP) techniques. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180 c).
The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using transmissions associated with the scalable parameter sets. For example, the OFDM symbol interval and/or OFDM subcarrier interval may vary from one transmission to another, from one cell to another, and/or from one portion of the wireless transmission spectrum to another. The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using various or scalable length subframes or Transmission Time Intervals (TTIs) (e.g., containing different numbers of OFDM symbols and/or varying absolute time lengths).
The gnbs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in an independent configuration and/or in a non-independent configuration. In a standalone configuration, the WTRUs 102a, 102B, 102c may communicate with the gnbs 180a, 180B, 180c while also not accessing other RANs (e.g., such as the enode bs 160a, 160B, 160 c). In an independent configuration, the WTRUs 102a, 102b, 102c may use one or more of the gnbs 180a, 180b, 180c as mobility anchor points. In an independent configuration, the WTRUs 102a, 102b, 102c may use signals in unlicensed frequency bands to communicate with the gnbs 180a, 180b, 180 c. In a non-standalone configuration, the WTRUs 102a, 102B, 102c may communicate or connect with the gnbs 180a, 180B, 180c, while also communicating or connecting with other RANs (such as the enode bs 160a, 160B, 160 c). For example, the WTRUs 102a, 102B, 102c may implement DC principles to communicate with one or more gnbs 180a, 180B, 180c and one or more enodebs 160a, 160B, 160c substantially simultaneously. In a non-standalone configuration, the enode bs 160a, 160B, 160c may serve as mobility anchors for the WTRUs 102a, 102B, 102c, and the gnbs 180a, 180B, 180c may provide additional coverage and/or throughput for serving the WTRUs 102a, 102B, 102 c.
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, scheduling of users in UL and/or DL, support of network slices, interworking between dual connectivity, NR and E-UTRA, routing of user plane data towards User Plane Functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and so on. As shown in fig. 1D, gnbs 180a, 180b, 180c may communicate with each other through an Xn interface.
The CN 115 shown in fig. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it should be understood that any of these elements may be owned and/or operated by entities other than the CN operator.
AMFs 182a, 182b may be connected to one or more of gNB 180a, 180b, 180c in RAN 113 via an N2 interface and may function as a control node. For example, the AMFs 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slices (e.g., handling of different PDU sessions with different requirements), selection of a particular SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMFs 182a, 182b may use network slices to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102 c. For example, different network slices may be established for different use cases, such as services relying on ultra-high reliability low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for Machine Type Communication (MTC) access, and so on. AMF 162 may provide control plane functionality for switching between RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-a Pro, and/or non-3 GPP access technologies such as WiFi.
The SMFs 183a, 183b may be connected to AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to UPFs 184a, 184b in the CN 115 via an N4 interface. SMFs 183a, 183b may select and control UPFs 184a, 184b and configure traffic routing through UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, etc. The PDU session type may be IP-based, non-IP-based, ethernet-based, etc.
UPFs 184a, 184b may be connected to one or more of the gnbs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to a packet-switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. UPFs 184, 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-host PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
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) that serves 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 one embodiment, the WTRUs 102a, 102b, 102c may connect to the local Data Networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.
In view of fig. 1A-1D and the corresponding descriptions of fig. 1A-1D, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more emulation devices (not shown): the WTRUs 102a-102d, the base stations 114a-114b, the evolved node B160a-160c、MME 162、SGW 164、PGW 166、gNB 180a-180c、AMF 182a-182b、UPF 184a-184b、SMF 183a-183b、DN 185a-185b, and/or any other devices described herein. The emulated device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation device may be used to test other devices and/or analog network and/or WTRU functions.
The simulation device may be designed to enable one or more tests of other devices in a laboratory environment and/or an operator network environment. For example, the one or more emulation devices can perform one or more or all of the functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices can perform one or more functions or all functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for testing purposes and/or may perform testing using over-the-air wireless communications.
The one or more emulation devices can perform one or more (including all) functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the simulation device may be used in a test laboratory and/or a test scenario in a non-deployed (e.g., test) wired and/or wireless communication network in order to enable testing of one or more components. The one or more simulation devices may be test equipment. Direct RF coupling and/or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation device to transmit and/or receive data.
The following abbreviations and abbreviations are used herein inter alia: configuration authorization (CG); dynamic authorization (DG); a MAC control element (MAC CE); acknowledgement (ACK); block error rate (BLER); bandwidth part (BWP); cyclic Prefix (CP); conventional OFDM (cyclic prefix dependent) (CP-OFDM); channel Quality Indicator (CQI); cyclic Redundancy Check (CRC); channel State Information (CSI); downlink Assignment Index (DAI); downlink Control Information (DCI); a Downlink (DL); demodulation reference signal (DM-RS); data Radio Bearers (DRBs); hybrid automatic repeat request (HARQ); long Term Evolution (LTE), e.g., from 3gpp LTE R8 and higher; negative ACK (NACK); modulation and Coding Scheme (MCS); multiple Input Multiple Output (MIMO); new Radio (NR); orthogonal Frequency Division Multiplexing (OFDM); physical layer (PHY); physical Random Access Channel (PRACH); a Primary Synchronization Signal (PSS); random access channel (or procedure) (RACH); random Access Response (RAR); a radio front end (RF); radio Link Failure (RLF); radio Link Monitoring (RLM); a radio network identifier (RNTI); radio Resource Control (RRC); radio Resource Management (RRM); a Reference Signal (RS); reference Signal Received Power (RSRP); a Received Signal Strength Indicator (RSSI); service Data Units (SDUs); sounding Reference Signals (SRS); a Synchronization Signal (SS); secondary Synchronization Signals (SSS); semi-persistent scheduling (SPS); simultaneous transmissions (STxMP) from multiple panels; supplemental Uplink (SUL); a Transport Block (TB); transport Block Size (TBS); a transmission/reception point (TRP); uplink (UL); ultra-reliable low-delay communications (URLLC); wireless local area networks and related technologies (IEEE 802.Xx domain) (WLANs); time Division Duplexing (TDD); cross-division duplexing (XDD); full Duplex (FD); half Duplex (HD); integrated Access and Backhaul (IAB); self-interference (SI); cross Link Interference (CLI); physical Downlink Shared Channel (PDSCH); physical Uplink Shared Channel (PUSCH); a Physical Downlink Control Channel (PDCCH); a Physical Uplink Control Channel (PUCCH); a control resource set (CORESET); sounding Reference Signals (SRS); user Equipment (UE); power Control (PC); resource Blocks (RBs); layer 1-RSRP (L1-RSRP); CSI-RS resource indicator-RSRP (cri-RSRP); a Synchronization Signal Block (SSB); signal to interference plus noise ratio (SINR); a Transmission Configuration Indicator (TCI); open Loop Power Control (OLPC); closed Loop Power Control (CLPC); path Loss (PL); power management-maximum power reduction (P-MPR); power Headroom (PH); power Headroom Report (PHR); uplink Control Information (UCI); SRS Resource Indicator (SRI); a Side Link (SL); SL Control Information (SCI); large-scale machine type communication (mMTC); and non-terrestrial networks (NTNs).
The New Radio (NR) may support dynamic Time Division Duplexing (TDD) by a Group Common (GC) DCI indicating a TDD-UL-DL-config-common/decoded slot format and/or a semi-static configuration (e.g., format 2_0 as shown in table 1), where (e.g., each) slot/symbol may include one or more of a "DL", "UL" and/or "flexible" configuration. For example, TDD-UL-DL-config-common (e.g., TDD-UL-DL-ConfigCommon) may be RRC parameters for cell-specific UL/DL TDD configuration, and TDD-UL-DL-config-dedicated (e.g., TDD-UL-DL-ConfigDedicated) may be RRC parameters for WTRU-specific UL/DL TDD configuration.
In an example, the duplexing may include half-duplexing (HD) for the gNB and the WTRU. Enhancements may be provided to support Full Duplex (FD) for the gNB and/or for WTRUs including Integrated Access and Backhaul (IAB) devices. Cross-division duplexing (XDD) (e.g., sub-band level FD as shown in fig. 2) may be used, and may provide reduced FD implementation complexity in terms of cancelling self-interference (SI) and mitigating cross-link interference (CLI), for example, at least at the transmitter (e.g., at the gNB).
Table 1: time slot format for normal cyclic prefix
Fig. 2 shows an example of FD-gNB and HD-WTRU in a cell. From the perspective of resource muting, the NR may support interrupt transmission (INT) (e.g., downlink preemption) over DCI (e.g., format 2_1) to dynamically indicate that there is no transmission to the WTRU in the active DL BWP of one or more cells and/or use the resource for other purposes (e.g., URLLC). The NR may support a Cancel Indication (CI) over DCI (e.g., format 2_4) to dynamically cancel PUSCH and/or SRS scheduled in the configuration timeFrequencyRegion of one or more cells. The NR may support (e.g., for PDSCH) semi-static resource muting patterns (e.g., rateMatchPatternGroup and rateMatchPatternGroup, such as reserved resources for RB-level) and/or semi-static/dynamic rate matching commands (e.g., for RE-level) through ZP-CSI-RS.
In deployments employing dynamic TDD, component Carriers (CCs) and/or bandwidth parts (BWP) may include one type of downlink ("D"), uplink ("U") and flexible ("F") in a symbol/slot, e.g., depending on GC-DCI (e.g., format 2_0) including a Slot Format Indicator (SFI) and/or a TDD-UL-DL-config-common/decoded configuration. For XDD operation, if other WTRUs have different communication directions (e.g., "D"), the communication directions of the WTRUs (e.g., "U") may have a mismatch. For example, if a mismatch occurs on a subband, the subband may be exposed to WTRU-to-WTRU Cross Link Interference (CLI). In an example, the WTRU may be configured with various types of periodic/semi-persistent DL reception (e.g., SPS-PDSCH) and/or UL transmissions (e.g., configuration Grant (CG) PUSCH). The periodic/semi-persistent configuration of DL/UL and exposed WTRU-to-WTRU CLI issues with respect to dynamic XDD operation may be handled.
The term "subband" may be used to refer to frequency domain resources and may be characterized by at least one of the following: a set of Resource Blocks (RBs), a set of RBs (e.g., if the carrier comprises an intra-cell guard band), a set of interleaved resource blocks, a bandwidth portion (e.g., or portion thereof), or a carrier (e.g., or portion thereof).
The sub-band may be characterized by a starting RB and a plurality of RBs of a set of consecutive RBs within the bandwidth portion. The subbands may be defined by values of a frequency domain resource allocation field and/or a bandwidth part index.
The term "XDD" may be used to refer to sub-band-by-sub-band duplexing (e.g., using UL or DL per sub-band), and/or may be characterized by at least one of: cross-division duplexing (e.g., sub-band FDD within the TDD band), sub-band based full duplexing (e.g., full duplexing when UL and DL are used/mixed on symbols/time slots and UL or DL are used per sub-band on symbols/time slots), frequency Domain Multiplexing (FDM) of DL/UL transmissions within the TDD spectrum, sub-band non-overlapping full duplexing (e.g., non-overlapping sub-band full duplexing), full duplexing other than the same frequency full duplexing (e.g., spectrum sharing, sub-band overlapping full duplexing), or advanced duplexing methods (e.g., other than pure TDD or FDD).
The term "dynamic (/ flexible) TDD" may be used to refer to a TDD system/cell that may dynamically (e.g., and/or flexibly) change/adjust/switch communication directions (e.g., downlink, uplink, or side link, etc.) for a time instance (e.g., slot, symbol, subframe, etc.). For example, in a system employing dynamic/flexible TDD, a Component Carrier (CC) or a bandwidth part (BWP) may have a single type of "D", "U", and "F" on a symbol/slot. In some cases, the CC or BWP may be of a single type on a symbol/slot based on an indication of a Group Common (GC) -DCI (e.g., format 2_0) including a Slot Format Indicator (SFI) and based on a tdd-UL-DL-config-common/decoded configuration. In some cases, the CC or BWP may be of a single type on a symbol/slot based on an indication of a Group Common (GC) -DCI (e.g., format 2_0) including a Slot Format Indicator (SFI). In some cases, the CC or BWP may have a single type on a symbol/slot based on the tdd-UL-DL-config-common/decoded configuration. For a given time instance/slot/symbol, a first gNB (e.g., cell, TRP) employing dynamic/flexible TDD may transmit downlink signals to a first WTRU in communication with/associated with the first gNB based on a first SFI and/or TDD-UL-DL-config configured/indicated by the first gNB. For a given time instance/slot/symbol, a second gNB (e.g., cell, TRP) employing dynamic/flexible TDD may receive uplink signals transmitted from a second WTRU in communication/association with the second gNB based on a second SFI and/or TDD-UL-DL-config configured/indicated by the second gNB. In one or more cases, a first WTRU may determine that an uplink signal interferes with reception of a downlink signal, where the interference caused by the uplink signal may be referred to as WTRU-to-WTRU cross-layer interference (CLI).
In one or more cases, the WTRU may transmit or receive a physical channel or a reference signal in accordance with at least one spatial domain filter. The term "beam" may refer to a spatial domain filter.
In one or more cases, the WTRU may transmit the physical channel or signal using the same spatial domain filter as that used to receive the RS (such as CSI-RS) or SS blocks. In one or more cases, the WTRU transmissions may be referred to as "targets. In one or more cases, the received RS or SS block may be referred to as a "reference" or "source. In this case, the WTRU may be used to transmit the target physical channel or signal. In some cases, the WTRU may be configured to transmit a target physical channel or signal based on the spatial relationship of the reference RS or SS blocks.
In one or more cases, the WTRU may transmit the first physical channel or signal according to the same spatial domain filter as that used to transmit the second physical channel or signal. The first transmission and the second transmission may be referred to as a "target" and a "reference" (or "source"), respectively. In this case, the WTRU may transmit the first (e.g., target) physical channel or signal according to a spatial relationship referencing the second (e.g., reference) physical channel or signal.
In one or more cases, the spatial relationship may be implicit. In one or more cases, the spatial relationship may be configured by RRC. In one or more cases, the spatial relationship may be signaled by a MAC CE or DCI. For example, the WTRU may implicitly transmit PUSCH and DM-RS for PUSCH based on the same spatial domain filter as the SRS indicated by the SRI indicated in the DCI or configured by RRC. In another example, the spatial relationship may be configured by RRC for SRS Resource Indicator (SRI) or signaled by MAC CE for PUCCH. Such spatial relationships may be referred to as "beam pointing".
In one or more cases, the WTRU may receive the first (e.g., target) downlink channel or signal based on the same spatial domain filter or spatial reception parameters as the second (e.g., reference) downlink channel or signal. For example, such an association may exist between a physical channel such as a PDCCH or PDSCH and its corresponding DM-RS. In one or more cases, when the first signal and the second signal are reference signals, such an association may exist when the WTRU is configured with a quasi-parity (QCL) hypothesis type D between the corresponding antenna ports. In one or more cases, such association may be configured to a TCI (transmission configuration indicator) state when the first signal and the second signal are reference signals. The WTRU may indicate the association between CSI-RS or SS blocks and DM-RS by an index to a set of TCI states signaled by RRC configuration and/or by MAC CE. The indication of the association may be referred to as a "beam indication".
In one or more cases, the term "TRP" (e.g., transmission reception point) may be used interchangeably with one or more of the terms TP (transmission point), RP (reception point), RRH (radio remote head), DA (distributed antenna), BS (base station), sector(s) of BS, and cell (e.g., geographic cell area served by BS). In one or more cases, the term "multi-TRP" may be used interchangeably with one or more of the terms MTRP, M-TRP, and multiple TRPs.
In one or more cases, the WTRU may report a subset of Channel State Information (CSI) components. In one or more cases, the CSI component may correspond to one or more of: CSI-RS resource indicator (CRI), SSB resource indicator (SSBRI), an indication of a faceplate (e.g., a faceplate identification or group identification) for receipt at the WTRU, measurements such as L1-RSRP, L1-SINR (e.g., CRI-RSRP, CRI-SINR, SSB-Index-RSRP, SSB-Index-SINR) taken from SSB or CSI-RS, and other channel state information such as Rank Indicator (RI), channel Quality Indicator (CQI), precoding Matrix Indicator (PMI), layer Index (LI), and the like.
In one or more cases, the WTRU may be configured to receive and/or provide one or both of channel measurements and interference measurements. In one or more cases, with respect to a Synchronization Signal Block (SSB), a WTRU may receive a synchronization signal/physical broadcast channel (SS/PBCH) block. The SS/PBCH block (SSB) may include a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSs), and/or a Physical Broadcast Channel (PBCH). The WTRU may monitor, receive, or attempt to decode the SSB during initial access, initial synchronization, radio Link Monitoring (RLM), cell search, cell handover, etc.
Regarding CSI-RS, the WTRU may measure and report Channel State Information (CSI). In one or more cases, CSI for (e.g., each) connection mode may include or be configured with one or more of CSI reporting configuration, CSI-RS resource set, and/or NZP CSI-RS resources. In one or more cases, the CSI reporting configuration may include one or more of the following: CSI reporting amounts (e.g., channel Quality Indicator (CQI), rank Indicator (RI), precoding Matrix Indicator (PMI), CSI-RS resource indicator (CRI), layer Indicator (LI), and other similar indicators); CSI reporting types (e.g., aperiodic, semi-persistent, periodic, and other reporting periods); CSI reporting codebook configuration (e.g., type I, type II port selection, etc.); and/or CSI reporting frequency. For example, the CSI reporting amount may be a parameter reportquality that may be used to indicate one or more of cri-RI-PMI-CQI, cri-RI-CQI, cri-RSRP, and/or ssb-Index-RSRP. As part of CSI reporting, the CSI reporting amount may indicate what value to report. For example, if the parameter reportquality is set to cri-RI-PMI-CQI, the WTRU may report CRI, RI, PMI and/or one or more of the CQIs as a CSI reporting procedure according to a CSI reporting related configuration. In one or more cases, the CSI-RS resource set may include one or more of the following CSI resource settings: NZP-CSI-RS resources for channel measurement, NZP-CSI-RS resources for interference measurement; and/or CSI-IM resources for interference measurements. In one or more cases, the NZP CSI-RS resources may include one or more of the following: NZP CSI-RS resource ID, periodicity and offset, QCL information, and TCI status and/or resource mapping (e.g., port number, density, CDM type, and other resource mapping information).
In one or more cases, the WTRU may indicate, determine, and/or be configured with one or more reference signals. The WTRU may monitor, receive, and/or measure one or more parameters based on the respective reference signals. These parameters may include, for example, but are not limited to, SS reference signal received power (SS-RSRP), CSI-RSRP, SS signal to noise plus interference ratio (SS-SINR), received Signal Strength Indicator (RSSI), cross-layer interference received signal strength indicator (CLI-RSSI), sounding reference signal RSRP (SRS-RSRP). In one or more cases, one or more parameters may be included in the reference signal measurement.
In one or more cases, SS-RSRP may be measured based on a synchronization signal, e.g., a demodulation reference signal (DMRS) in PBCH or SSS. In one or more cases, the SS-RSRP may be a linear average of the power contributions of the Resource Elements (REs) carrying the respective synchronization signals. The power of the reference signal may be scaled when measuring RSRP. In the case that SS-RSRP is used for L1-RSRP, the measurement result may be determined based on CSI reference signals (e.g., in addition to synchronization signals).
In one or more cases, the CSI-RSRP may be measured based on a linear average of power contributions of Resource Elements (REs) carrying the respective CSI-RS. The CSI-RSRP measurements may be configured within measurement resources of configured CSI-RS occasions.
In one or more cases, SS-SINR may be measured based on a synchronization signal (e.g., DMRS in PBCH or SSS). In one or more cases, the SS-SINR may be a linear average of power contributions of Resource Elements (REs) carrying respective synchronization signals divided by a linear average of noise and interference power contributions. In the case that SS-SINR is used for L1-SINR, noise and interference power measurements may be determined based on resources configured by higher layers.
In one or more cases, the CSI-SINR may be measured based on a linear average of power contributions to Resource Elements (REs) carrying the respective CSI-RS divided by a linear average of noise and interference power contributions. In the case where CSI-SINR is used for L1-SINR, noise and interference power measurements may be determined based on resources configured by higher layers. In one or more other cases, noise and interference power may be measured based on the resources carrying the respective CSI-RS.
In one or more cases, the RSSI may be measured based on an average of the total power contributions in the configured OFDM symbols and bandwidth. In one or more cases, power contributions may be received from different resources (e.g., co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).
In one or more cases, CLI-RSSI may be measured based on an average of total power contributions in configured OFDM symbols of the configured time and frequency resources. In one or more cases, power contributions may be received from different resources (e.g., cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).
In one or more cases, SRS-RSRP may be measured based on a linear average of power contributions of Resource Elements (REs) carrying the respective SRS.
In one or more cases, the characteristics of the authorization or assignment may include one or more of the following: frequency allocation; aspects of time allocation, such as duration; a priority; modulation and coding scheme; transmission block size; the number of spatial layers; the number of transport blocks; TCI status, such as CRI or SRI; repeating the times; determining whether the repetition scheme is type a or type B; determining whether the authorization is a configuration authorization type 1, a configuration authorization type 2 or a dynamic authorization; determining whether the assignment is a dynamic assignment or a semi-persistent scheduling (e.g., configuration) assignment; configuring an authorization index or a semi-persistent assignment index; configuring periodicity of grants or assignments; a Channel Access Priority Class (CAPC); and/or any parameters provided in the DCI by the MAC or by the RRC for scheduling grants or assignments. In one or more cases, the indication by the DCI may include one or more of: explicit indication by DCI field or RNTI for masking CRC of PDCCH; and/or implicit indication by a characteristic of a first resource element (e.g., an index of a first control channel element) such as a DCI format, DCI size, coreset or search space, aggregation level, or received DCI, wherein a mapping between the characteristic and the value may be signaled by RRC or MAC. Note that the term "RS" may be used interchangeably with one or more of the terms RS resource, RS resource set, RS port, and RS port set, as described herein. Further, it is noted that the term "RS" may be used interchangeably with one or more of the terms SSB, CSI-RS, SRS, and DM-RS.
Flexible (e.g., subband-by-subband) slot format indication may be provided. In an example, for one or more subbands, a WTRU may receive an indication of a set of frequency resources corresponding to the subband. The indication may consist of, for example, at least one of a start RB, an end RB, or a plurality of RBs. The WTRU may receive an indication of each subband applicable to one or more (e.g., all) slots or time symbols. In an example, for at least one such subset, the WTRU may receive an indication of each subband applicable to the subset of slots or time symbols.
A subband specific slot format indication may be provided. In an example, a WTRU may receive an indication of a slot format for a plurality of subbands (e.g., each of the plurality of subbands). For a subband (e.g., each subband), the slot format may include an indication of whether each symbol is downlink, uplink, or flexible. The indication may be received via DCI (e.g., a group common DCI such as DCI format 2_0), for example, from a certain location of the DCI (e.g., a start bit location configured for WTRU reading). The WTRU may receive an indication of a slot format for the sub-band using at least one of the following features described herein.
In an example, for one or more subbands (e.g., each of the one or more subbands), the WTRU may receive configuration information, such as higher layer configuration information for a slot format combination applicable to the subband. The configuration information may include the same information as a slot format combination Information Element (IE) of the existing system, e.g., including a location in DCI (e.g., a group common DCI such as DCI format 2_0). The WTRU may determine a first slot format combination and a second slot format combination applicable to the first and second subbands, respectively, for example, by decoding DCI in the first and second locations of DCI configured for the first and second subbands, respectively, e.g., where both the first and second locations are configurable (e.g., as parameters or values) according to the WTRU.
In an example, the WTRU may receive (e.g., first receive) higher layer configuration information for a slot format combination of one or more (e.g., all) subbands, including a starting position in the DCI. The WTRU may receive at least one slot format combination sequentially from a starting location, e.g., where the slot format combination (e.g., each slot format combination) is applicable to a subband.
In an example, a WTRU may receive configuration information for one or more multi-subband slot format combinations, where the multi-subband slot format combinations (e.g., each multi-subband slot format combination) include a set of slot formats for at least one subband. In an example, the first multi-subband slot format combination may include a first slot format and a second slot format for a first subband and a first slot format and a second slot format for a second subband. The WTRU may receive configuration information for an index of configured multi-subband slot format combinations (e.g., multi-subband slot format combinations of each configuration). The WTRU may receive the multi-subband slot format combination index from the DCI at the configured subband location and may determine an applicable slot format for the subband (e.g., each subband).
Sub-band specific UL-DL configuration information may be provided. For at least one subband (e.g., each of the at least one subband), the WTRU may receive UL-DL configuration information from a higher layer. For example, if a slot format indication is not received from the DCI or if the slot format indication has a special value (e.g., 255), higher layer configuration information may be applicable to the sub-band.
An applicability of a transmission or reception rule with a subband specific slot format indication may be provided. The WTRU may be configured by higher layers to receive or transmit signals or channels in resources and/or in slots where subband-specific slot format indications are received. The WTRU may determine whether to receive or transmit in the resource based on the received subband-specific slot format indication, according to one or more of the following.
In an example, a WTRU configured by a higher layer to send a PUSCH transmission in a resource may transmit PUSCH if (e.g., only when) the slot format indicates "uplink" for each symbol (e.g., or for a group of symbols) of PUSCH for each sub-band that overlaps PUSCH.
In an example, if (e.g., only when) for more than S (e.g., S > 1) subbands overlapping PUSCH, the slot format indication is "uplink" for each symbol (e.g., or for a group of symbols) of PUSCH, then a WTRU configured by a higher layer to send PUSCH transmissions in the resource may transmit PUSCH. S (e.g., S > 1) may be predefined, configured, and/or indicated.
The suitability of PDCCH monitoring behavior may be provided. In one or more cases, the WTRU may be configured or (dynamically) scheduled by higher layers to transmit UL signals (e.g., PUSCH, PUCCH, PRACH, UL RS, etc.) in the resources. In one or more cases, the WTRU may transmit an UL signal if resources are valid for UL transmission based on (e.g., included in) at least one UL SB indicated by at least one SBFD (or XDD) signaling, as discussed herein. In some cases, where the WTRU determines that resources are available for UL transmission based on at least one UL SB in the symbol/slot, the WTRU may skip (e.g., discard, stop, skip as abnormal situation/operation, not go, not perform) monitoring/receiving a control channel (PDCCH) in the symbol/slot (e.g., monitor DCI via the control channel based on CORESET). Thus, by skipping monitoring or reception of the control channel, the complexity of the WTRU may be reduced and thus the efficiency of communication with SBFD may be improved.
In one or more cases, the WTRU may be configured to monitor a control channel (PDCCH) in the symbol/slot in response to the WTRU determining that resources are not available for UL transmissions in the symbol/slot (e.g., not included in UL SB, etc.). For example, if the WTRU determines that the resources are not available for UL transmission in the symbol/slot, the WTRU may be configured to monitor DCI via a control channel in the symbol/slot based on CORESET.
In one or more cases, in response to the WTRU determining that resources are not available for UL transmissions in the symbol/slot (e.g., not included in UL SB, etc.), the WTRU may be configured to skip (e.g., discard, stop, skip as abnormal conditions/operations, not proceed, not perform) monitoring/receiving a control channel (PDCCH) in the symbol/slot (e.g., monitor DCI via the control channel based on CORESET). Thus, by skipping monitoring or reception of the control channel, the complexity of the WTRU may be reduced and thus the efficiency of communication with SBFD may be improved.
In an example, if (e.g., only when) for each sub-band overlapping the PDSCH, the slot format indicates that it is "downlink" for each symbol (e.g., or for a group of symbols) of the PDSCH, a WTRU configured by a higher layer to receive the PDSCH in the resources may receive the PDSCH and may provide HARQ-ACK feedback.
In an example, if (e.g., only when) for more than S (e.g., S > 1) subbands overlapping the PDSCH, the slot format indication is "downlink" for each symbol (e.g., or for a group of symbols) of the PDSCH, a WTRU configured by a higher layer to receive the PDSCH in the resources may receive the PDSCH and may provide HARQ-ACK feedback. S (e.g., S > 1) may be predefined, configured, and/or indicated.
The slot type of the "hybrid" DL/UL (e.g., denoted by "M n") may be provided. In an example, the slot type of the "hybrid" DL/UL (e.g., denoted by "M n" where n=1 or n=1, 2, …) may be defined or configured (e.g., from the gNB) by the WTRU. The M n type (e.g., defined or configured by the WTRU) may be used to indicate that a time instance (e.g., slot and/or symbol) may be used for at least one of: the method may include transmitting (UL) from the WTRU over a first set of RBs, receiving (DL) at the WTRU over a second set of RBs, or both transmitting (UL) from the WTRU over the first set of RBs and receiving (DL) at the WTRU over the second set of RBs. The first set of RBs and/or the second set of RBs may be configured to be associated with an M n type, for example, where the communication direction (e.g., DL or UL) may be configured/determined to be associated with the first set of RBs or the second set of RBs, for example, in contrast to a set of RBs for which the slot type "F" is not associated with a communication direction in advance.
The M n type may be used and/or included in a parameter of the tdd-UL-DL-config, which parameter may include one or more time instances, for example, each time instance indicating and/or including at least one of "D", "U", "F" or "M n". the parameters of tdd-UL-DL-config may be cell specific (e.g., or cell common) parameters (e.g., tdd-UL-DL-ConfigurationCommon) or WTRU-specific parameters (e.g., tdd-UL-DL-ConfigurationDedicated).
In an example, the M n type (e.g., defined or configured according to the WTRU) may indicate (e.g., include or be associated with) at least one of the following frequency domain resource information contents (e.g., explicitly or implicitly): a first set of RBs for UL use (e.g., or DL use), a second set of RBs for DL use (e.g., or UL use), or a third set of RBs for "flexible" use between DL/UL. In an example, a first set of RBs for UL use (e.g., or DL use) may be configured by an RB-level bitmap, or by which of the regions (e.g., evenly divided regions) divided within a BWP (e.g., currently active BWP and/or CC), for example, this may include an explicit indicator to indicate which region is applicable for a given use (e.g., for DL or for UL). The WTRU may receive an indication of the RB-level bitmap via a Radio Resource Control (RRC) message indicating a plurality of UL/DL resource block patterns for one or more symbols. The WTRU may receive an indication via Downlink Control Information (DCI) or a Medium Access Control (MAC) Control Element (CE), which may indicate which of a plurality of UL/DL resource block patterns indicated in the configuration information is to be applied to one or more symbols. For example, the indication may indicate that a first UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a first symbol of the one or more symbols and a second UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a second symbol of the one or more symbols.
In an example, the second set of RBs for DL use (e.g., or UL use) may be configured by an RB-level bitmap, or by which of the regions (e.g., evenly divided regions) divided within a BWP (e.g., currently active BWP and/or CC), for example, this may include an explicit indicator to indicate which region is applicable for a given use (e.g., for DL or for UL). As described above, the WTRU may receive an indication of the RB-level bitmap via a Radio Resource Control (RRC) message indicating a plurality of UL/DL resource block patterns for one or more symbols. The WTRU may receive an indication via Downlink Control Information (DCI) or a Medium Access Control (MAC) Control Element (CE), which may indicate which of a plurality of UL/DL resource block patterns indicated in the configuration information is to be applied to one or more symbols. For example, the indication may indicate that a first UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a first symbol of the one or more symbols and a second UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a second symbol of the one or more symbols.
The second set of RBs for DL use (e.g., or UL use) may be defined by remaining RBs within the BWP (e.g., currently active BWP and/or CC) that are not included in the first set of RBs. The gNB may first configure a first set of RBs for UL use (e.g., somewhere in the middle and not in the edge region within the BWP, which may result in effectively avoiding inter-operator interference of XDD by the gNB implementations), and the remaining RBs (e.g., including non-contiguous RBs) may be used for DL use.
In an example, a third set of RBs for "flexibility" between DL/UL may be defined by remaining RBs within the BWP (e.g., currently active BWP and/or CC) that are not included in the first and second sets of RBs. The gNB may configure the third set of RBs for "flexibility" between DL/UL where DL Rx or UL Tx may be active (e.g., both may be active), which may provide scheduling flexibility for the gNB (e.g., and reduce gNB implementation complexity).
Fig. 3 shows an example of the "M 1" type (e.g., such as for n=1, as one of the "M n" types). In an example, the WTRU may be configured (e.g., from the gNB) to have one or more of the following types: an "M 1" type, an "M 2" type, an "M 3" type (e.g., depending on the gNB configuration), an "M 4" type (e.g., depending on the gNB configuration), and so forth. The "M 1" type may include a first set of RBs (e.g., for UL) corresponding to the second region 312 of the BWP 302 and/or a second set of RBs (e.g., for DL) corresponding to the first region 310 and the third region 314 of the BWP 302. Fig. 4 shows an example of the "M 2" type (e.g., such as for n=2, as one of the "M n" types). The "M 2" type may include a first set of RBs (e.g., for UL) corresponding to a first RB level bitmap (e.g., 0000011111100000000000) of BWP, a second set of RBs (e.g., for DL) corresponding to a second RB level bitmap (e.g., 1111100000000000111111) of BWP, and/or a third set of RBs (e.g., for "flexible") corresponding to the remaining RBs (e.g., 0000000000011111000000) of BWP other than the first and second sets of RBs. In an example, the number of "M n" types that may be configured according to a WTRU may be based on the related WTRU capabilities (e.g., capability signaling).
In an example, the WTRU may report on how many "M n" types are configurable and/or supported capabilities. The gNB may configure one or more "M n" types based on the reported WTRU capabilities.
The use of "Mn" type tdd-UL-DL-config may be provided. The WTRU may receive configuration information regarding a first parameter (e.g., tdd-UL-DL-ConfigurationCommonXDD) and/or a second parameter (e.g., tdd-UL-DL-ConfigurationDedicatedXDD), for example, through RRC signaling. In an example, the second parameter may indicate (e.g., include and/or be associated with) at least one of one or more "M n" types, "D" types, "U" types, or "F" types, while the first parameter may indicate (e.g., include and/or be associated with) at least one of "D" types, "U" types, or "F" types. The first parameter may be the same as the legacy parameters of tdd-UL-DL-ConfigurationCommon. Having the same legacy parameters as the first parameters may provide compatibility in terms of tdd-UL-DL-configuration with legacy WTRUs (e.g., for implementing XDD). Reuse of the parameters of tdd-UL-DL-ConfigurationCommon as legacy parameters may protect the allocated time domain resources for DL and the allocated time domain resources for UL, e.g., without the potential ambiguity of XDD related signaling having its potential ambiguity period (e.g., during RRC signaling).
In an example, the first parameter may indicate (e.g., include and/or be associated with) at least one of one or more "M n" types, "D" types, "U" types, or "F" types (e.g., in a sub-parameter of the first parameter such as pattern1 and/or pattern 2). In an example, if the "M n" type of the one or more "M n" types is configured, information about the starting symbol position for applying the "M n" type may be indicated (e.g., and/or configured), which may be explicitly configured, or predefined/predetermined (e.g., defined by the next symbol of the last symbol position assigned by a third parameter (e.g., nrofDownlinkSymbols, nrofDownlinkSlots) for the (e.g., downlink) symbol/slot number.
In an example, the second parameter (e.g., tdd-UL-DL-ConfigurationDedicatedXDD) can indicate (e.g., include and/or be associated with) at least one of one or more "M n" types, "D" types, "U" types, or "F" types. In an example, for an indicated slot (e.g., having at least one symbol corresponding to "F" or "M n" according to a first parameter), the gNB may assign a selective "M n" type for an entire remaining symbol configuration and/or indication corresponding to "F" (e.g., or "M n") covered by a selective "M n" type (e.g., n=1 or 2 … selected by the gNB) within the indicated slot by an indicator of "allM1symbols", "allM symbols", or the like.
In an example, for an indicated slot (e.g., having at least one symbol corresponding to "F" or "M n" according to a first parameter), the gNB may configure and/or indicate an explicit symbol position to assign a selective "M n" type (e.g., n=1 or 2 … selected by the gNB) by an indicator of "nrofM1symbols", "nrofM2symbols", etc., where a starting symbol position for applying the selective "Mn" type may be explicitly configured, or predefined/predetermined (e.g., as the next symbol of nrofDownlinkSymbols). If more than one "M n" type is configured, the second starting symbol position of the "M2" type may be the next symbol (e.g., the immediately next symbol) to the symbol position assigned for the "M1" type, and so on. For example, the WTRU may receive an indication that a first UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a first symbol of the one or more symbols and a second UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a second symbol of the one or more symbols.
A dynamic SFI based on DCI signaling using a "Mn" type may be provided. In an example, the WTRU may receive DCI including an SFI, where the SFI may be predetermined (e.g., predefined or preconfigured) based on at least one of one or more "M n" types, "D" types, "U" types, or "F" types. For example, the WTRU may receive an indication that each of the one or more symbols includes both a first subset of resource blocks associated with Downlink (DL) reception and a second subset of resource blocks associated with Uplink (UL) transmission. In an example, the slot format combination parameters (e.g., slotFormatCombination) may include a slot/symbol level pattern based on at least one of one or more "M n" types, "D" types, "U" types, or "F" types of code points of the SFI that may be mapped to the DCI. The DCI may be received by (e.g., only received by) the WTRU (e.g., as WTRU-specific DCI). The DCI may be received by more than one WTRU in a cell (e.g., as a group common DCI, such as DCI format 2_0).
In an example, at least one of the following may be applied (e.g., or configured and/or indicated to be applied): introducing an indicator (e.g., a new RRC parameter) of the "M n" type informing of symbols marked with "F" (e.g., each symbol) in a slot format combination parameter (e.g., slotFormatCombination), wherein the slot format combination parameter includes a mapping to a code point of the SFI (e.g., in DCI); and/or the introduction may include at least one new slot format index of the "M n" type (e.g., using reserved slot format indexes such as 56-254 or adding new candidates, etc.). For example, introducing a new slot format index may include a new index containing D, D, D, F, F, F, M 1、M1、M1、M2、M2、M2, U, and U. For example, introducing a new slot format index may include a new index containing D、M3、M3、M3、F、F、M1、M1、M1、M2、M2、M2、U and U.
An indicator (e.g., a new RRC parameter) of the "M n" type for informing of symbols (e.g., each symbol) marked with "F" may be introduced in a slot format combination parameter (e.g., slotFormatCombination) including a mapping (e.g., in DCI) to a code point of the SFI. The entire symbol position marked with "F" in the slot format combination parameter may inform (e.g., typically inform) the WTRU of the selective "M n" type (e.g., n=1, 2, … selected by the gNB), for example, by introducing an indicator of "allM1forF", "allM2forF", etc. For example, the selective "M n" type may be limited to one slot (e.g., including 14 symbols) because "F" in the slot format combination parameter may be marked at each slot. In an example, a special (e.g., or default) value/parameter may be introduced to indicate "no change" in symbol position for "F" (e.g., the "M n" type is not applied). In an example, parameters may be introduced for a symbol-by-symbol "M n" type pattern of symbol positions marked with an "F" in the cross-slot format combination parameters. For example, the pattern may be an alternating pattern of "M 1"、"M2" … across symbol positions. For example, the pattern may be one in which a first number (e.g., the first half) of symbols follow the "M 1" type and the remaining number of symbols follow the "M 2" type, etc. For example, one or more modes/rules may be predefined and/or preconfigured and may indicate a selector (e.g., for a slot format combination parameter) of the one or more modes/rules.
The applicability of NR duplex operation may be provided. In one or more cases, new Radio (NR) duplexing operations (e.g., NR duplexing, XDD, etc.) may be used to improve conventional TDD operation by enhancing UL coverage, increasing capacity, reducing delay, etc. In one or more cases, conventional TDD operation may be based on dividing the time domain between uplink and downlink. The study was conducted considering the feasibility of allowing full duplex or more specifically sub-band non-overlapping full duplex (SBFD) (e.g., at the gNB) within a conventional TDD band, e.g., as shown in fig. 5. Fig. 5 shows a "SBFD slot" that includes frequency resource allocation based on a combination of "DL SB" and "UL SB". In some cases, conventional TDD as shown in fig. 5 may be an example of one or more "M n" types as described herein. In one or more cases, the gNB may schedule UL and DL resources to the WTRUs within the UL and DL non-overlapping subbands, respectively.
In one or more cases, operations based on "SBFD slots" may reduce implementation complexity in the FD at least at the gNB. To accommodate changing traffic conditions, it may be desirable/beneficial to have the flexibility to dynamically change the direction of the sub-bands (e.g., at least in terms of scheduling flexibility of the gNB, etc.). However, when periodic/semi-persistent resources configured to the WTRU (e.g., for CSI-RS, PDCCH, CG PUSCH, etc.) overlap with subbands that are handed off to the opposite direction, this may result in cross-link interference (CLI). The embodiments provided herein enable dynamic sub-band DL/UL switching without causing CLI for configured resources.
Fig. 6 shows an example of SBFD operation based on a hybrid UL/DL type (M n). As shown in fig. 6, for example, the WTRU may receive one or more configurations, including (or indicating) one or more (N) hybrid UL/DL types (M n), e.g., via RRC signaling. In one or more cases, the one or more (N) hybrid UL/DL types (M n) may (e.g., each) include one or more RB subsets for UL and one or more RB subsets for DL. For example, the WTRU may receive an indication that each of the one or more symbols includes both a first subset of resource blocks associated with Downlink (DL) reception and a second subset of resource blocks associated with Uplink (UL) transmission. Examples of configurations may include, but are not limited to, "region-based" or "bitmap-based" based on fig. 3,4, and/or 6, etc. (where type M 1, type M 2, type M 3, type M 4 are shown as examples).
In one or more cases, the WTRU may be configured to receive an indication (e.g., via MAC-CE and/or DCI) for one or more symbol/slot selection types (among N types). For example, the WTRU may receive an indication that indicates a first UL/DL resource block pattern (e.g., M n type) of the plurality of UL/DL resource block patterns is to be applied to a first symbol of the one or more symbols. For example, as shown in fig. 6, the WTRU may receive an indication of the selection type M 2, where a first frequency region is set to "UL" (SB) (e.g., frequency regions 614, 616, 618 shown in fig. 6), a second frequency region (e.g., adjacent to the first frequency region) is set to "DL" (SB) (e.g., frequency regions 608, 610, 612 shown in fig. 6), and a third frequency region (e.g., adjacent to the second frequency region) is set to "DL" (SB) (e.g., frequency regions 602, 604, 606 shown in fig. 6). The WTRU may be configured with (periodic) UL resources (e.g., PUCCH or Configuration Grant (CG) PUSCH, etc.), on which UL signals and/or UL data packets are scheduled for (periodic) transmission.
In response to receiving the indication of the selection type M 2, the WTRU may determine whether (periodic) UL resources (e.g., periodic UL resources 620, 622, 624 shown in fig. 8) are included in a "UL" (SB) such as a first frequency region (e.g., frequency regions 614, 616, 618, respectively). In one or more cases, the WTRU may determine that (periodic) UL resources 620, 622, and/or 624 are not included in "UL" (SB) frequency regions 614, 616, and/or 618, respectively, indicated by type M 2. In one or more cases, the WTRU may determine that the allocation of (periodic) UL resources 620, 622, and/or 624 falls within "DL" (SB or RB) frequency regions 608, 610, and/or 612, respectively, as shown in fig. 6. In response to determining that the allocation of UL resources 620, 622, and/or 624 falls within "DL" frequency regions 608, 610, and/or 612, respectively, the WTRU may not transmit (e.g., may skip transmission, may stop transmission, may discard transmission, may not be able to perform transmission) UL resources 620, 622, and/or 624. For example, if periodic UL resources 620, 622, 624 are included in the frequency region 602, 604, 606 and/or the frequency region 608, 61, 612 associated with DL reception of one or more symbols, the WTRU may discard UL transmissions associated with the periodic UL resources 620, 622, 624 in the one or more symbols. In some cases, in response to determining that the allocation of UL resources falls in "DL," the WTRU may not transmit until further determined to be valid for transmission.
In one or more cases, the WTRU may receive a second indication (e.g., via MAC-CE and/or DCI) to select a second type (of N types) for one or more symbols/slots. For example, the WTRU may receive an indication that a second UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a second symbol of the one or more symbols. For example, the WTRU may receive a second indication of the selection type M 3, where the first half region (e.g., the first half region 630 and/or 632 shown in fig. 6) is set to "UL" (SB) (e.g., for the case where the first half region 630 and/or 632 includes more RBs than the first frequency region 614, 616 and/or 618, respectively (based on type M 2)), and the second half region (e.g., the second half region 626 and/or 628 shown in fig. 6) is set to "DL" (SB). In one or more cases, the WTRU may determine that (periodic) UL resources (e.g., periodic UL resources 634 and/or 636 shown in fig. 6) are included in "UL" (SB) first half regions 630 and/or 632, respectively, indicated by type M 3 (e.g., for the case where the allocation of UL resources 634 and/or 636 is now in "UL" (SB or RB) first half regions 630 and/or 632, respectively. In one or more cases, the WTRU may determine that the allocation of (periodic) UL resources 634 and/or 636 does not fall into the "DL" (SB or RB) second half region 626 and/or 628, as shown in fig. 6. In response to determining that UL resources 634 and/or 636 are included in "UL" (SB) first half regions 630 and/or 632 and/or UL resources do not fall in "DL" second half regions 626 and/or 628, the WTRU may transmit (e.g., may continue transmitting, may resume transmitting, etc.) UL resources 634 and/or 636. For example, if periodic UL resources 634 and/or 636 are included in an area associated with UL transmission of one or more symbols (e.g., first half area 630 and/or 632), the WTRU may transmit UL transmissions associated with periodic UL resources 634 and/or 636 in the one or more symbols.
Note that these examples are based on (periodic) UL resources according to WTRU configuration/indication, however, it should be understood that similar examples are applicable as well, e.g. those based on (periodic) DL resources according to WTRU configuration/indication. For example, if one or more periodic DL resources are included in an area associated with DL reception of one or more symbols, the WTRU may receive DL transmissions associated with one or more periodic DL resources in the one or more symbols. For example, one or more periodic DL resources may be used for one or more of a Physical Downlink Control Channel (PDCCH) or a configuration grant physical downlink shared channel (CG-PDSCH). The WTRU may not receive the second DL transmission associated with the one or more second periodic DL resources in the one or more symbols if the one or more second periodic DL resources are included in an area of a resource block associated with UL reception of the one or more symbols.
In one or more cases, the WTRU may be configured to receive information (e.g., via DCI or MAC CE) indicating that a first subset of Resource Blocks (RBs) of the plurality of RBs associated with one or more symbols is an RB for Downlink (DL) reception and a second subset of RBs of the plurality of RBs associated with one or more symbols is an RB for Uplink (UL) transmission. In one or more cases, the WTRU may receive a DL transmission associated with a periodic DL resource (e.g., PDCCH/CG-PDSCH) in one or more symbols on condition that the periodic DL resource is included in a first RB subset indicated by the information as RBs for DL reception. In one or more cases, the WTRU may send a UL transmission associated with periodic UL resources (e.g., PUCCH/CG-PUSCH) in one or more symbols on condition that the periodic UL resources are included in a second subset of RBs indicated by the information as RBs for UL reception.
In one or more cases, the WTRU may be further configured to receive configuration information (e.g., via RRC) indicating a plurality of UL/DL RB configurations. In one or more cases, this information (e.g., received via DCI and/or MAC-CE) may indicate which of a plurality of UL/DL RB configurations applies to one or more symbols. In one or more cases, the WTRU may be configured to discard at least one other UL transmission associated with periodic UL resources (e.g., PUCCH/CG-PUSCH) in one or more symbols, if the periodic UL resources are included in a first set of RBs indicated by the information as RBs for DL reception.
Fig. 7 illustrates an example of sub-band-by-sub-band (e.g., BWP-by-BWP) dynamic muting for XDD. An indication sub-band level dynamic silence may be provided. In an example where the granularity of the sub-bands for XDD may be BWP, BWP class XDD may be considered as a design for implementing XDD. For CCs, the gNB may consider one or more configurable BWP with one or more planned and/or aligned BWP sizes for multiple WTRUs in the cell (e.g., which may support XDD). Based on the examples described herein, the gNB can dynamically indicate a sub-band (e.g., BWP-by-BWP) muting command for a WTRU operating on a relatively large RB as its currently active BWP (e.g., BWP0 for WTRU1 as shown in FIG. 7 as DL), e.g., to manage cross-link interference (CLI) in a cell (e.g., WTRU transparently). Based on the examples described herein, similar features (e.g., the gNB is able to dynamically indicate sub-band-by-sub-band such as BWP muting commands, etc. for WTRUs operating on relatively large UL RBs as their currently active UL BWPs) may be applied to uplink implementations.
The introduction of a "BWP Mute Indicator (BMI)" may be provided as an on/off flag. In an example, an indicator to re-interpret a "BWP Indicator (BI)" to indicate an RB to mute for XDD (e.g., rather than indicating BWP handover/selection as an initial purpose of BI) may be defined and/or configured for use in DCI. The indicator (e.g., a "BWP Mute Indicator (BMI)") may include 1 bit to inform the WTRU of the on or off of the re-interpretation of the application for the BI.
In an example, WTRU behavior when receiving data scheduling DCI (e.g., for DL-DCI format 1_1/1_2) may be defined and/or configured as follows. If the BMI field value is set to a first value (e.g., "0" or BWP mute off), the WTRU may interpret the DL-DCI as the same as legacy behavior, meaning that the BI field operates as a "BWP switch command" for its initial purpose. If the BMI field value is set to a second value (e.g., "1" or BWP mute on), the WTRU may reinterpretate (e.g., newly reinterpretate) the value of the BI field as a mute DL RB indicating a match with the BWP corresponding to a value within the currently active DL BWP, and/or may not perform BWP handoff (e.g., even if the value is toggled). If the BMI field value is set to a second value, the Frequency Domain Resource Allocation (FDRA) field in the same DCI may be interpreted as at least one of: existing PDSCH frequency domain resource allocation (e.g., as is conventional, and DCI may schedule PDSCH according to current (e.g., unchanged) active DL-BWP) and/or further reduced muting RB indication. For example, the WTRU may receive/detect DCI (e.g., DL-DCI, which may be DCI format 1_1) including FDRA fields. The DCI may generally be used for DL data (PDSCH) scheduling, where the value indicated by the FDRA field may indicate a frequency domain resource allocation (e.g., one or more RBs) on which the scheduling data (PDSCH) is transmitted for reception by the WTRU. For existing PDSCH frequency domain resource allocations, if the scheduled RBs for the PDSCH belong to and/or overlap with the muted DL RBs, the overlapping RBs may be considered rate matched or the WTRU may not expect overlap. For a further reduced silence RB indication, the WTRU may determine a silence DL RB by intersecting a first RB matching the silence BWP (e.g., a value corresponding to the BI field) with a second RB corresponding to the FDRA field value. In this case, PDSCH may not be scheduled using current DL DCI and the unused DCI field in the DCI may be reused to deliver other relevant information, which may be applicable to reuse of bit width as described herein, for example.
In an example, WTRU behavior when receiving data scheduling DCI (e.g., for DL-DCI format 1_1/1_2) may be defined and/or configured as follows. If the BMI field value is set to a second value, a Time Domain Resource Allocation (TDRA) field in the same DCI may indicate a PDSCH reception time interval and a duration for applying silent DL RBs (e.g., to other DL in addition to or including PDSCH). For example, the WTRU may receive/detect DCI (e.g., DL-DCI, which may be DCI format 1_1) including TDRA fields. The DCI may generally be used for DL data (PDSCH) scheduling, where the value indicated by the TDRA field may indicate a time-domain resource allocation (e.g., one or more RBs) on which the scheduling data (PDSCH) is transmitted for reception by the WTRU. In an example, there may be a new and/or separate field indicating a duration for applying the muting DL RB. In this case, there may be a code point (e.g., default code point) indicating that the same PDSCH reception time interval as in the same DCI is applied. Other code points may be explicitly described by RRC and/or MAC-CE. In an example, if PDSCH is not scheduled with DCI (e.g., FDRA field is re-interpreted as other information content as a further reduced silence RB indication, etc.), TDRA field may indicate a duration for applying silence DL RBs. If the BMI field value is set to a second value, when and for how long the silence DL RB is applied may be determined and/or configured according to at least one of: the muting DL RB may be applied to apply BWP muting for the duration of the indicated TDRA field, or for a duration that is predefined (e.g., the entire current slot), preconfigured, or separately indicated (e.g., when BWP muting is applied may be predefined, preconfigured, and/or separately indicated based on WTRU capabilities), and/or the duration may be associated with the ACK transmission timing of the WTRU (e.g., upon receiving DCI).
In an example, WTRU behavior when receiving data scheduling DCI (e.g., for UL-DCI format 0_1/0_2) may be defined and/or configured as follows. If the BMI field value is set to a first value (e.g., "0" or BWP silence off), the WTRU may interpret the UL-DCI as the same as legacy behavior, meaning that the BI field may operate as a "BWP switch command" for its initial purpose. If the BMI field value is set to a second value (e.g., "1" or BWP silence on), the WTRU may reinterpretate (e.g., newly reinterpretate) the value of the BI field as a silence UL RB indicating a match with BWP corresponding to a value within the currently active UL BWP, and/or may not perform BWP handoff (e.g., even if the value is switched). If the BMI field value is set to a second value, then FDRA fields in the same DCI may be interpreted as at least one of: existing PUSCH frequency domain resource allocation (e.g., as is conventional), and DCI may schedule PUSCH according to current (e.g., unchanged) active UL-BWP and/or further reduced silence RB indication. For existing PUSCH frequency domain resource allocations, overlapping RBs may be considered rate matched or the WTRU may not expect overlap if the RBs for the PUSCH scheduling belong to and/or overlap with the silent UL RBs. For a further reduced silence RB indication, the WTRU may determine a silence UL RB by intersecting a first RB matching the silence BWP (e.g., a value corresponding to the BI field) with a second RB corresponding to the FDRA field value. In this case, PUSCH may not be scheduled using the current UL DCI, and the unused DCI field in the DCI may be reused to deliver other relevant information, which may be applicable to reuse of bit width as described herein, for example.
In an example, WTRU behavior when receiving data scheduling DCI (e.g., for UL-DCI format 0_1/0_2) may be defined and/or configured as follows. If the BMI field value is set to a second value, the TDRA field in the same DCI may indicate a PUSCH transmission time interval and/or a duration for applying silence UL RBs (e.g., to (other) UL in addition to (e.g., or including) PUSCH). In an example, there may be a new and/or separate field indicating a duration for applying the muting UL RB. In this case, there may be a code point (e.g., default code point) indicating that the same PUSCH transmission time interval as in the same DCI is applied. Other code points may be explicitly described by RRC and/or MAC-CE. In an example, if PUSCH is not scheduled with DCI (e.g., FDRA field is re-interpreted as other information content as a further reduced silence RB indication, etc.), TDRA field may indicate a duration for applying silence UL RBs. If the BMI field value is set to a second value, when and for how long to apply the muting UL RB may be determined and/or configured according to at least one of: the muting UL RB may be applied to apply BWP muting within the duration of the indicated TDRA field, or within a predefined (e.g., entire current slot), preconfigured, or separately indicated duration (e.g., when BWP muting is applied may be predefined, preconfigured, and/or separately indicated based on WTRU capabilities), and/or the duration may be associated with UL transmission timing of the WTRU (e.g., upon receipt of DCI), e.g., where UL transmission timing may be PUSCH transmission timing, which may be considered to deliver an ACK upon receipt of DCI.
Support for implicit BMI indication may be provided. In an example, an indicator (e.g., BMI) to reinterpretate an existing BI field to indicate an RB to be muted for XDD may be implicitly signaled to the WTRU based on at least one of: depending on whether the indication value of the "BWP indicator" (BI) is switched (e.g., in combination with applying a combination of "hard-coded" bit fields, by a combination of "hard-coded" bit fields (e.g., informing the WTRU that DCI is not scheduling data such as PDSCH and/or PUSCH), or by a new predefined/preconfigured RNTI for BWP muting purposes (e.g., muting RNTI (M-RNTI) may be used to detect DCI). In an example, the "hard-coded" bit field may be a FDRA field set to all first values (e.g., 0) or second values (e.g., 1). For example, the field may be set to all "0" in the FDRA type 0 configuration case, set to all "1" in the FDRA type 1 configuration case, or set to all "0" in the DYNAMICSWITCH configuration case, the Redundancy Version (RV) may be set to all "1", the Modulation and Coding Scheme (MCS) may be set to all "1", and/or the New Data Indicator (NDI) may be set to 0, etc.
In an example, an indicator (e.g., BMI) to re-interpret an existing BI field to indicate an RB to be muted for XDD may be implicitly signaled to the WTRU based on whether the indicated value of the "BWP indicator" (BI) is switched (e.g., in combination with applying a combination of "hard-coded" bit fields). If the value of BI is not switched (e.g., indicated with the same value as the current BWP index), the WTRU may consider the DCI not to be used for the dynamic BWP muting command (e.g., instead, the DCI is used for other purposes such as the existing SCell sleep indication, or for other purposes of the DCI indication). If the value of BI is switched (e.g., indicated with a different value than the current BWP index), the WTRU may consider the DCI as for the dynamic BWP muting command (e.g., for XDD operation), and the WTRU may apply BWP muting on RBs corresponding to the "switch value of BI field" for the duration of indicated TDRA field or for a predefined, preconfigured or separately indicated duration to apply BWP muting. When BWP muting is applied may be predefined, preconfigured, or indicated separately (e.g., based on WTRU capabilities). The duration may be associated with an ACK transmission timing of the WTRU (e.g., based on receiving DCI). The operation of the dynamic BWP mute command may maintain (e.g., not switch) the currently active BWP and indicate (e.g., indicate only) another BWP frequency region to mute for XDD operations (e.g., as shown in fig. 7). Applying dynamic BWP muting only when BI is switched can provide an efficient control signaling mechanism without increasing signaling overhead.
Support may be provided for reinterpreting other fields in the DCI. In an example, other fields in the DCI may be reinterpreted (e.g., reused) to deliver more information content for other purposes (e.g., related to XDD operations) based on satisfying at least one condition described herein (e.g., if the DCI is not scheduling data due to reinterpretation and/or determined from "hard-coded" bit fields, etc.). At least one of the following may be applied. For DL-DCI, by reusing the bit width of at least one of MCS, NDI, RV, HARQ process numbers, antenna ports, DMRS sequence initialization, TCI, identifiers for DCI formats, carrier indicators, TDRA, DAI, TPC, PRB bundling, PRI, PDSCH to HARQ feedback timing indicators (e.g., if present), more information content (e.g., related to XDD operations) may be provided with at least one of: the applicable time instance of the mute command, the applicable duration of the mute command, any particular anomaly of muting, and/or any multi-CC simultaneous indication (e.g., BWP index with the same indication and/or switch, or separately enumerated BWP index that is muted for each CC). Any particular anomaly of muting may include SSB (e.g., which may default to anomaly), SS (e.g., CSS alone, or some SSs listed by RRC and/or MAC-CE), CORESET (e.g., CORESET #0 alone, or some SSs listed by RRC and/or MAC-CE), CSI-RS (e.g., CSI-RS for mobility alone, or some CSI-RS listed by RRC and/or MAC-CE), and/or some periodic/semi-persistent CSI-RS, and/or an indication for UL power control adjustment configurable by the gNB, e.g., as to whether UL PC adjustment behavior is applied (due to XDD operation), etc.
In an example, other fields in the DCI may be reinterpreted (e.g., reused) to deliver more information content for other purposes (e.g., related to XDD operations) based on satisfying at least one condition described herein (e.g., if the DCI is not scheduling data due to reinterpretation and/or determined from "hard-coded" bit fields, etc.). At least one of the following may be applied. For UL-DCI, by reusing MCS, NDI, RV, HARQ process numbers, antenna ports, DMRS sequence initialization, SRI, precoding information and layer numbers, PTRS-DMRS association, identifiers for DCI formats, carrier indicators, TDRA, bit widths of DAI, more information (e.g., related to XDD operation) of at least one of the following may be provided. The information may be an applicable time instance of the mute command, an applicable duration of the mute command, or any particular exception to the mute. In an example, the particular anomaly of muting may include RACH (e.g., which may default to anomaly), PUCCH (e.g., PUCCH resources listed by RRC and/or MAC-CE), SRS (e.g., SRS listed by RRC and/or MAC-CE), and/or some periodic/semi-persistent SRS, an indication of UL power control adjustment, e.g., as to whether UL PC adjustment behavior is applied (e.g., due to XDD operation), etc. (e.g., configurable by the gNB). The information may be any multi-CC simultaneous indication (e.g., BWP index with the same indication/switch, or separately enumerated BWP index that is muted for each CC). In an example, other fields may remain useless (e.g., ignore field values).
Enhancements to DCI indicating INT may be provided.
DCI format 2_1 may be used to inform PRBs and OFDM symbols, for example, where a WTRU may assume that no transmission is intended for the WTRU. The following information may be transmitted through DCI format 2_1 with CRC scrambled by INT-RNTI: preemption indication 1, preemption indications 2, …, preemption indication N. The size of DCI format 2_1 may be configured by higher layer signaling (e.g., up to 126 bits). The preemption indication (e.g., each preemption indication) may be C bits (e.g., c=14).
DCI (e.g., format 2_1) indicating an interrupt transmission Indication (INT) may be enhanced to deliver RBs to be muted for XDD operation. One or more of the following may be applied. The WTRU may be configured with RRC parameters to implement XDD. The DCI, e.g., existing DCI indicating INT (e.g., DCI format 2_1) may include a field (e.g., a new field) of "silent BWP indication" (MBI). A time domain indication (e.g., based on a legacy INT operation over DCI format 2_1) may be provided/interpreted for when to apply the muting DL RB for XDD and/or how long to apply.
For DCI including MBI field, e.g., existing DCI indicating INT (e.g., DCI format 2_1), one or more of the following may be applied. The MBI field may have the same field value as the BI field (e.g., value "00" for BWP0, value "01" for BWP1, value "10" for BWP2, value "11" for BWP3, and may indicate that BWP is muted, such as not switched/selected). The MBI field (e.g., 2 bits) may have a function independent of the BMI field (e.g., 1 bit) as an on/off flag for reinterpretation as described herein. A single MBI field may be inserted in DCI 2_1. Multiple MBI fields can be inserted in DCI 2_1, for example by one-to-one mapping with existing parameters of "preemption indication N (for 1, …, N)".
In the case where a single MBI field can be inserted in DCI field 2_1, one or more of the following may be applied. The BWP-level dynamic silence indication may be applied (e.g., only applied) to the same CC that receives DCI 2_1. The value of the MBI field may indicate a silence DL RB (e.g., for XDD) that matches a BWP corresponding to the value of the same CC (e.g., without changing the current active DL BWP). This may have the following limitations: the dynamic silence indication for XDD applies to (e.g., only to) one CC (e.g., and the one CC does not apply the same legacy INT indication in the frequency domain). In an example, a single value of the MBI field may apply to CCs (e.g., all CCs that may be indicated by a corresponding "preemption indication N (for 1, …, N)"). The operation mode may be preconfigured by RRC (e.g., as a mode selection for XDD). Other CCs, e.g., indicated by "preemption indication N (for 1, …, N)", may operate as the same legacy INT indication (e.g., to interrupt the entire RB of the active DL BWP of each CC).
In case multiple MBI fields can be inserted in DCI 2_1, for example by utilizing a one-to-one mapping of existing parameters of "preemption indication N (for 1, …, N)", one or more of the following can be applied. In an example, MBI 1, MBI 2, …, MBI N may be provided. MBI 1 may correspond to "preemption indication 1", MBI 2 may correspond to "preemption indication 2", … MBI N may correspond to "preemption indication N". A BWP-level dynamic silence indication (e.g., each BWP-level dynamic silence indication) may be applied to each CC (e.g., indicated by a corresponding "preemption indication n"). The value of the MBI field for a CC may indicate a silence DL RB (e.g., for XDD) that matches the BWP corresponding to the value of the CC (e.g., without changing the current active DL BWP). There may be a limit to the operation in which the value may be switched (e.g., different from the current active BWP of the CC). The dynamic silence indication for XDD may be applicable to multiple CCs simultaneously. Other CCs, e.g., indicated by "preemption indication N (for 1, …, N)" (e.g., and the value of MBI N is not switched) may operate as the same legacy INT indication (e.g., to interrupt the entire RB of the active DL BWP of each CC).
In case when the muting DL RB for XDD is applied and/or a time domain indication of how long is applied, one or more of the following may be applied. For CCs in which the muting DL RBs for XDD are applied, when and for how long the muting DL RBs are valid may follow the legacy INT indication in the same DCI format 2_1 in the time domain. For other CCs (e.g., no silence DL RBs are applied for XDD) indicated by, for example, a "preemption indication N (for 1, …, N)", when and for how long DL preemption is valid may follow the legacy INT indication in the same DCI format 2_1 in the time domain.
A DCI format (e.g., new DCI format (e.g., format 2_1a)) having a function (e.g., purpose) independent of existing DCI (e.g., format 2_1) indicating INT may be introduced to deliver RBs to be silenced, e.g., for XDD operation. One or more of the following may be applied. The WTRU may be configured with RRC parameters to implement XDD. The WTRU may be configured with RNTI, such as a new RNTI (e.g., M-RNTI) for operation. A DCI format, for example, a new DCI format (e.g., 2_1a) may have a field (e.g., a new field) of "silent BWP indication" (MBI). A time domain indication of the time and duration of the mute DL RB for XDD may be applied (e.g., based on the legacy INT operation over DCI format 2_1).
In the case where a DCI format (e.g., a new DCI format (e.g., 2_1a)) may have a "silent BWP indication" (MBI) field, one or more of the following may be applied. A single MBI field may be inserted in DCI 2_1a. Multiple MBI fields can be inserted in DCI 2_1a, for example by a one-to-one mapping with parameters of "preemption indication N (for 1, …, N)".
In the case where a single MBI field is inserted in DCI2_1a, one or more of the following may be applied. The BWP-level dynamic silence indication may be applied (e.g., only applied) to the same CC that received DCI 2_1a. The value of the MBI field may indicate a silence DL RB (e.g., for XDD) that matches a BWP corresponding to the value of the same CC (e.g., without changing the current active DL BWP). In an example, the BWP-level dynamic silence indication may be applied (e.g., only applied) to CCs indicated by the corresponding "preemption indication n". The value of the MBI field may indicate a silence DL RB (e.g., for XDD) that matches a BWP corresponding to a value within the current active DL BWP of the CC. In an example, a single value of the MBI field may apply to CCs (e.g., all CCs indicated by the corresponding "preemption indication N (for 1, …, N)"). The operation mode may be preconfigured by RRC (e.g., as a mode selection for XDD).
In case multiple MBI fields are inserted in DCI 2_1a, for example by utilizing a one-to-one mapping of parameters of "preemption indication N (for 1, …, N)", one or more of the following may be applied. MBI 1, MBI 2, …, MBI N may be provided. MBI 1 may correspond to "preemption indication 1", MBI 2 may correspond to "preemption indication 2", … MBI N may correspond to "preemption indication N". A BWP-level dynamic silence indication (e.g., each BWP-level dynamic silence indication) may be applied to each CC (e.g., indicated by a corresponding "preemption indication n"). The value of the MBI field for a CC may indicate a silence DL RB (e.g., for XDD) that matches the BWP corresponding to the value of the CC (e.g., without changing the current active DL BWP). There may be a limit to the operation in which the value may be switched (e.g., different from the current active BWP of the CC). The dynamic silence indication for XDD may be applicable to multiple CCs simultaneously.
In case there is a time domain indication of when to apply the muting DL RB for XDD and/or how long to apply, one or more of the following may be applied. For CCs in which the muting DL RB for XDD is applied, when the muting DL RB is valid and the validity duration may follow the legacy INT indication in the same DCI format 2_1a in terms of time domain.
Explicit signaling/indication of silence BWP for XDD may be provided (e.g., via MAC-CE and/or DCI). In an example, separate explicit signaling/indication of silence BWP for XDD (e.g., via MAC-CE and/or DCI) (e.g., independently for DL or UL, or for both DL/UL, or for different pairing information for DL/UL in the same MAC-CE, etc.) may be applied and signalled to the WTRU. One or more of the following may be applied. One or more silence BWP indications (MBI) may be included in the MAC-CE and/or DCI message. A time domain indication of when DL (e.g., or UL) RBs for XDD muting are applied and how long to apply may be included. The WTRU's ACK message may be sent, for example, after successful decoding of the MAC-CE. The WTRU may receive an explicit indication MAC CE with a specific Logical Channel ID (LCID) for explicit signaling. The WTRU may receive explicit indication DCI scrambled by a specific RNTI for explicit signaling.
In the case that one or more silent BWP indications (MBIs) are included in the MAC-CE and/or DCI message, one or more of the following may be applied. The one or more indications (e.g., each of the one or more indications) may be associated with/indicated together with a corresponding CC index (e.g., in the same MAC-CE and/or the same DCI message). MBI (e.g., each MBI) can be applied to each CC (e.g., indicated by a corresponding CC index). The value of MBI for a CC may indicate a silence DL RB (e.g., for XDD) that matches the BWP corresponding to the value, e.g., within (e.g., without change to) the currently active DL (e.g., or UL) BWP of the CC. In an example, there may be a limit to the operation that the value may be a different value than the current active BWP of the CC. The WTRU may receive the DCI message by receiving a WTRU-specific DCI format. The WTRU may receive the DCI message by receiving a group DCI format. For example, the WTRU may receive one or more MBI in the DCI message. The WTRU may identify an MBI of the one or more MBIs based on the group ID of the WTRU. The WTRU may receive the group ID based on one or more of RRC, MAC CE, and DCI.
In the case where the WTRU's ACK message is sent after decoding (e.g., successful decoding) of the MAC-CE, the "time domain indication" may be interpreted, for example, according to the ACK transmission timing.
In the case where the WTRU receives an explicit indication MAC CE with a specific Logical Channel ID (LCID) for explicit signaling, the WTRU may receive using a predefined LCID. In an example, the WTRU may receive a particular LCID based on one or more of RRC and MAC CE.
In the case where the WTRU receives explicit indication DCI scrambled by a specific RNTI for explicit signaling, the WTRU may use the predefined RNTI for reception. In an example, the WTRU may receive the specific RNTI based on one or more of RRC and MAC CEs.
A dynamic RB level silence indication may be provided (RBMI). In an example, a dynamic RB level muting indication (RBMI), e.g., within BWP, may be applied and inform the WTRU, e.g., for XDD operation. One or more of the following may be applied. In an example, the gNB may configure a different number of RBs mapped to RBMI values (e.g., each value of RBMI). In an example, the indication of RBMI may be interpreted by reusing existing FDRA fields (e.g., when applicable). In an example, at least one code point of the RBMI field may be linked to an existing "reserved resource" indication (e.g., rateMatchPatternGroup1 and/or rateMatchPatternGroup 2). In an example, RBMI fields may share the same existing field "rate matching indicator" (e.g., and the gNB may configure the RRC enabler (e.g., for XDD) to re-interpret that "rate matching indicator" applies to PDSCH and to other DL (e.g., except SSB)). In an example, the indication RBMI may be given separately/explicitly.
In the case that RBMI fields share the same existing field "rate matching indicator" (e.g., and the gNB may configure the RRC enabler (e.g., for XDD) to re-interpret that "rate matching indicator" applies to PDSCH and to other DL (e.g., except SSB)), one or more of the following may be applied. This may be applied to DL DCI because UL-DCI may not include a "rate matching indicator".
Conflict handling between silent BWP and active BWP may be provided. In an example, the WTRU may receive one or more indications for one or more silent BWP and one or more active BWP. The indication may be based on one or more of BI, BMI, MBI and/or RBMI. Based on the indication, the time and/or frequency resources of the one or more silent BWP may overlap (e.g., collide) with the time and/or frequency resources of the one or more active BWP. Based on the overlap, the WTRU may perform one or more of the following: the overlapping time/frequency resources are assumed to be silent BWP, the overlapping time/frequency resources are assumed to be active BWP, and/or determined based on one or more conditions.
The WTRU may assume overlapping time/frequency resources as silent BWP. For example, if one or more silent BWP overlaps fully/partially with one or more active BWP, the WTRU may assume the overlapping time/frequency resources as silent BWP.
The WTRU may assume overlapping time/frequency resources as silent BWP. For example, if one or more silent BWP overlaps fully/partially with one or more active BWP, the WTRU may assume the overlapping time/frequency resources as active BWP.
The WTRU may determine whether to determine overlapping time/frequency resources as silent BWP or active BWP based on one or more conditions. For example, the WTRU may determine overlapping time/frequency resources as silent BWP if one or more conditions are met. The WTRU may determine overlapping time/frequency resources as active BWP if one or more conditions are not met. The one or more conditions may be one or more of the following: priority indicator, DCI format, size of time/frequency resources, number of subbands, and/or SMTC window.
The WTRU may determine whether to determine overlapping time/frequency resources as silent BWP or active BWP based on the priority indicator. For example, if the WTRU receives a silent BWP with a higher priority (e.g., based on a priority indicator in the DCI), the WTRU may assume overlapping time/frequency resources as the silent BWP. If the WTRU receives an active BWP with a higher priority (e.g., based on a priority indicator in the DCI), the WTRU may assume overlapping time/frequency resources as the active BWP. For example, if the WTRU receives PDSCH/PUSCH scheduling with higher priority in overlapping time/frequency resources, the WTRU may assume the overlapping time/frequency resources as active BWP. If the WTRU receives a PDSCH/PUSCH schedule with a lower priority (e.g., based on a priority indicator in the DCI), the WTRU may assume overlapping time/frequency resources as silent BWP.
The WTRU may determine whether to determine overlapping time/frequency resources as silent BWP or active BWP based on the indicated DCI format (e.g., WTRU-specific DCI such as DCI format 0_1, 0_2, 1_1 or 1_2; or group DCI such as DCI format 2_x). For example, if the WTRU receives silent BWP via a first DCI format (e.g., DCI format 2_x), the WTRU may assume overlapping time/frequency resources as silent BWP. If the WTRU receives active BWP via a second DCI format (e.g., DCI format 0_1, 0_2, 1_1 or 1_2), the WTRU may assume overlapping time/frequency resources as active BWP.
The WTRU may determine whether to determine overlapping time/frequency resources as silent BWP or active BWP based on one or more SMTC windows. For example, if the overlapping time/frequency resources include one or more SMTC windows, the WTRU may assume the overlapping time/frequency resources as active BWP. Otherwise, the UE may assume overlapping time/frequency resources as silent BWP.
Behavior based on the "M n" type and/or muting RBs may be provided. In an example, based on meeting at least one condition described herein (e.g., for a symbol/slot, such as if the symbol/slot corresponds to, belongs to, is associated with, or is configured/indicated by a "M n" type), one or more of the following may be applied (e.g., for a WTRU supporting Full Duplex (FD)). If the WTRU determines that the symbol (e.g., slot) corresponds to an "M n" type that includes a first set of RBs for UL and a second set of RBs for DL (e.g., and if the WTRU reports its capability to support Full Duplex (FD) operation at the WTRU and/or the UE receives a message/signaling/indication (e.g., from the gNB) to confirm/configure FD operation at the WTRU), one or more of the following may be applied. If the WTRU determines that the symbol (e.g., slot) corresponds to an "M n" type that includes a first set of RBs for UL and a second set of RBs for DL, the WTRU may determine that the first set of RBs is valid as UL for scheduled/configured UL transmissions (e.g., PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.), and the WTRU may perform UL Tx on the first set of RBs. If the WTRU determines that the symbol (e.g., slot) corresponds to an "M n" type that includes a first set of RBs for UL and a second set of RBs for DL, the WTRU may determine that the second set of RBs are valid as DL for scheduled/configured DL reception (e.g., PDSCH, PDCCH, RS measurement), and the WTRU may perform DL Rx on the second set of RBs (e.g., simultaneously with UL Tx on the same symbol such as FD operation at the WTRU).
In the event that the WTRU determines that the first set of RBs is valid as UL for scheduled/configured UL transmissions (e.g., PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.) and the WTRU may perform UL Tx on the first set of RBs, one or more of the following may be applied. If not fully allocated on the first set of RBs (e.g., if less than X 1 RBs are allocated), a transmission (e.g., any transmission) of UL resources (e.g., scheduled, configured, or indicated as a transmission such as PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.) may be canceled/skipped on the symbol (e.g., along with other associated symbols of UL resources). The cancel/skip condition may be predefined/preconfigured/indicated. The cancel/skip condition may be predefined/preconfigured/indicated per a particular channel/signal (e.g., per at least one of PUCCH, PUSCH, SRS and/or PRACH, etc.). In an example, the cancel/skip condition may be based on determining a ratio R 1 of a first number of RBs of UL resources that fully overlap with the first set of RBs to a second number of RBs of UL resources that do not overlap with the first set of RBs. If the ratio R 1 is less than the threshold (e.g., R UL), transmission of the UL resource may be canceled/skipped on that symbol (e.g., as well as other associated symbols of the UL resource).
In an example, the cancel/skip condition may be based on checking whether one or more (e.g., all) symbols (e.g., or D 1 symbols) for transmitting UL resources (e.g., for a slot/symbol) satisfy at least one condition described herein. If so, UL resources may be transmitted. If not all symbols (e.g., or D 1 symbols) are satisfied, transmission of the UL may be canceled/skipped for the corresponding transmission opportunity (e.g., for the slot/symbol). In an example, the cancel/skip condition may be determined/defined/configured (e.g., independently determined/defined/configured) based on whether UL resources are scheduled by DCI (e.g., dynamic scheduling and/or grant cases) or higher layer signaling (e.g., semi-static scheduling cases, configuration grant cases, etc.). Cancelling/skipping may mean that transmission of UL resources may be performed by the WTRU among other transmission occasions of UL resources (e.g., depending on the conditions of each transmission occasion and/or whether UL resources are periodic or semi-persistent). If at least X 2 RBs in the first set of RBs (e.g., at least one RB or) are determined/identified as overlapping with DL resources (e.g., scheduled, configured or indicated as measuring/monitoring such as PDCCH, PDSCH, SPS-PDSCH, DL-RS, etc.), reception of DL resources may be canceled/skipped at least on that symbol (e.g., as well as other associated symbols of DL resources). Cancellation/skipping may mean that among other reception occasions of DL resources, reception of DL resources may be performed by the WTRU (e.g., depending on the conditions of each reception occasion and/or whether DL resources are periodic or semi-persistent). X 1、RUL、D1 and/or X 2 may be configured, predefined, or indicated.
In the case where the WTRU determines that the second set of RBs is valid as DL for DL reception (e.g., PDSCH, PDCCH, RS measurements) for scheduling/configuration and the WTRU may perform DL Rx on the second set of RBs (e.g., simultaneously with UL Tx on the same symbol as FD operated at the WTRU), one or more of the following may be applied. If not fully allocated on the second set of RBs (e.g., if less than Y 1 RBs are allocated), reception (e.g., any reception) of DL resources (e.g., scheduled, configured, or indicated as measuring/monitoring such as PDCCH, PDSCH, SPS-PDSCH, DL-RS, etc.) may be canceled/skipped on that symbol (e.g., along with other associated symbols of DL resources). The cancel/skip condition may be predefined/preconfigured/indicated. The cancel/skip condition may be predefined/preconfigured/indicated by a particular channel/signal (e.g., by at least one of PDCCH such as CORESET and/or search space, PDSCH and/or CSI-RS, etc.). In an example, the cancel/skip condition may be based on determining a ratio R 2 of a first number of RBs of DL resources that completely overlap with the second set of RBs to a second number of RBs of DL resources that do not overlap with the second set of RBs. If the ratio R 2 is less than the threshold R DL, the reception of the DL resource may be canceled/skipped on that symbol (e.g., as well as other associated symbols of the DL resource). In an example, the cancel/skip condition may be based on checking whether all symbols (e.g., or D 2 symbols) for receiving DL resources (e.g., for a slot/symbol) satisfy at least one condition described herein. If so, DL resources may be received. If not all symbols (e.g., or D 2 symbols) are satisfied, the reception of the DL may be canceled/skipped for the corresponding reception opportunity (e.g., for the slot/symbol). In an example, the cancel/skip condition may be determined/defined/configured (e.g., independently determined/defined/configured) based on whether DL resources are scheduled by DCI (e.g., dynamic scheduling and/or grant cases) or higher layer signaling (e.g., semi-static scheduling cases, configuration grant cases, etc.). Cancellation/skipping may mean that among other reception occasions of DL resources, reception of DL resources may be performed by the WTRU (e.g., depending on the conditions of each reception occasion and/or whether DL resources are periodic or semi-persistent). If at least Y 2 RBs in the second set of RBs (e.g., at least one RB or) are determined/identified as overlapping UL resources (e.g., scheduled, configured, or indicated as transmission), transmission of UL resources may be canceled/skipped at least on that symbol (e.g., as well as other associated symbols of UL resources). Cancellation/skipping may mean that transmission of UL resources may be performed by the WTRU among other reception occasions of UL resources (e.g., depending on the conditions of each transmission occasion and/or whether UL resources are periodic or semi-persistent). Y 1、RDL、D2 and/or Y 2 may be configured, predefined, or indicated.
In an example, based on satisfying at least one condition described herein (e.g., for a symbol/slot, such as if the symbol/slot corresponds to, belongs to, is associated with, and/or is configured/indicated by a "M n" type), one or more of the following may be applied (e.g., for a WTRU supporting half-duplex (HD)). If the WTRU determines that the symbol (e.g., slot) corresponds to an "M n" type that includes a first set of RBs for UL and a second set of RBs for DL (e.g., and if the WTRU reports its capability to support half-duplex (HD) operation at the WTRU and/or the WTRU receives a message/signaling/indication from the gNB to confirm/configure HD operation at the WTRU), one or more of the following may be applied. If the WTRU determines that the symbol (e.g., slot) corresponds to an "M n" type that includes a first set of RBs for UL and a second set of RBs for DL, the WTRU may determine that the first set of RBs are valid as UL for scheduled/configured UL transmissions (e.g., PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.), and the WTRU may perform UL Tx on the first set of RBs, e.g., if the WTRU identifies/determines that the symbol (e.g., slot) is for "UL" (e.g., rather than for "DL", UL and DL are not mixed in the same symbol/slot). Otherwise (e.g., if the WTRU identifies/determines that the symbol/slot is for "DL"), UL transmissions (e.g., transmission of UL resources) may be canceled/skipped on the symbol (e.g., slot). If the WTRU determines that the symbol (e.g., slot) corresponds to an "M n" type that includes a first set of RBs for UL and a second set of RBs for DL, the WTRU may determine that the second set of RBs are valid as DL for scheduled/configured DL reception (e.g., PDCCH, PDSCH, SPS-PDSCH and/or RS measurements), and, for example, if the UE identifies/determines that the symbol (e.g., slot) is for "DL" (e.g., rather than for "UL," UL and DL are not mixed in the same symbol/slot), the WTRU may perform DL Rx on the first set of RBs. Otherwise (e.g., if the WTRU identifies/determines that the symbol/slot is for "UL"), DL reception (e.g., reception of DL resources) may be canceled/skipped on the symbol (e.g., slot).
In the case where the WTRU determines that the first set of RBs is valid as UL for scheduled/configured UL transmissions (e.g., PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.), and for example, if the WTRU identifies/determines that a symbol (e.g., slot) is used for "UL" (e.g., rather than for "DL," UL and DL are not mixed in the same symbol (/ slot)), the WTRU may perform UL Tx on the first set of RBs, otherwise (e.g., if the WTRU identifies/determines that a symbol (e.g., slot) is used for "DL"), may cancel/skip UL transmissions (e.g., transmission of UL resources) on the symbol (/ slot), one or more of the following may apply. Cancelling/skipping may mean that transmission of UL resources may be performed by the WTRU among other transmission occasions of UL resources (e.g., depending on the conditions of each transmission occasion and/or whether UL resources are periodic or semi-persistent).
The WTRU may identify/determine a symbol (e.g., slot) for "UL". If not fully allocated on the first set of RBs (e.g., if less than X 1 RBs are allocated), a transmission (e.g., any transmission) of UL resources (e.g., scheduled, configured, or indicated as a transmission such as PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.) may be canceled/skipped on the symbol (e.g., along with other associated symbols of UL resources). Reception (e.g., any reception) of DL resources (e.g., scheduled, configured, or indicated as measurement/monitoring such as PDCCH, PDSCH, SPS-PDSCH, DL-RS, etc.) may be canceled/skipped on symbols (e.g., and other associated symbols for DL resources due to HD-WTRU operation). Cancellation/skipping may mean that among other reception occasions of DL resources, reception of DL resources may be performed by the WTRU (e.g., depending on the conditions of each reception occasion and/or whether DL resources are periodic or semi-persistent). X 1、RUL and/or D 1 may be configured, predefined, or indicated.
The WTRU may identify/determine a symbol (e.g., slot) for "UL" based on an implicit determination and/or an explicit indication. In an example, by implicit determination, the WTRU may identify/determine a symbol (e.g., slot) for "UL" if there is at least one UL Tx (e.g., scheduled/configured/indicated) on at least U1 RB of the first set of RBs (e.g., and/or if there is no scheduled/configured/indicated DL Rx on at least U2 RB of the first set of RBs). U1 and/or U2 may be configured, predefined, or indicated (e.g., they may be the same). In an example, the WTRU may identify/determine a symbol (e.g., slot) for "UL" based on a legacy configuration (e.g., tdd-UL-DL-config-common/decoded), e.g., a symbol/slot marked with "U" (e.g., and/or "F") according to the indication. This may mean that the UL symbol/slot (e.g., indicated as the actual communication direction of the UL on the UL symbol/slot) will be indicated by the legacy configuration (e.g., legacy DCI format 2_0, (e.g., for supporting HD-WTRUs)), and a new tdd-UL-DL-config (e.g., for XDD) including one or more "M n" types may be signaled to the WTRU individually/independently, where the new tdd-UL-DL-config may have an overlapping indication of the selective "M n" type on the same symbol marked with "D" or "U" in the legacy configuration. Allowing this overlap may result in a new tdd-UL-DL-config (e.g., for XDD) having the purpose of checking resource validity in the RB level with at least one cancel/skip condition (e.g., for XDD operations such as for HD-WTRUs), but the actual communication direction/link for UL or DL may be indicated by a legacy configuration (e.g., via DCI format 2_0).
One or more of the following may be applied in the case that UL resources (e.g., scheduled, configured, or indicated as transmission (e.g., any transmission) such as PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.) may be canceled/skipped on symbols (e.g., and other associated symbols of UL resources) if not fully allocated on the first set of RBs (e.g., if less than X 1 RBs are allocated). The cancel/skip condition may be predefined/preconfigured/indicated. The cancel/skip condition may be predefined/preconfigured/indicated by a particular channel/signal (e.g., by at least one of PUCCH, PUSCH, SRS, PRACH, etc.). In an example, the cancel/skip condition may be based on determining a ratio R 1 of a first number of RBs of UL resources that fully overlap with the first set of RBs to a second number of RBs of UL resources that do not overlap with the first set of RBs. If the ratio R 1 is less than the threshold R UL, transmission of the UL resource may be canceled/skipped on that symbol (e.g., as well as other associated symbols of the UL resource). In an example, the cancel/skip condition may be based on checking whether all symbols (e.g., or D 1 symbols) used to transmit UL resources meet at least one condition described herein. If so, UL resources may be transmitted. If not all symbols (e.g., or D 1 symbols) are satisfied, transmission of the UL may be canceled/skipped for the corresponding transmission opportunity (e.g., for the slot). In an example, the cancel/skip condition may be determined/defined/configured (e.g., independently determined/defined/configured) based on whether UL resources are scheduled by DCI (e.g., dynamic scheduling/grant cases) or higher layer signaling (e.g., semi-static scheduling cases, configuration grant cases, etc.). Cancelling/skipping may mean that transmission of UL resources may be performed by the WTRU among other transmission occasions of UL resources (e.g., depending on the conditions of each transmission occasion and/or whether UL resources are periodic or semi-persistent).
In the case where the WTRU may determine that the second set of RBs is valid as DL for scheduled/configured DL reception (e.g., PDCCH, PDSCH, SPS-PDSCH and/or RS measurements), and, for example, if the WTRU identifies/determines that the symbol (e.g., slot) is for "DL" (e.g., rather than for "UL", UL and DL are not mixed in the same symbol/slot), the WTRU may perform DL Rx on the second set of RBs, or else (e.g., if the WTRU identifies/determines that the symbol/slot is for "UL") may cancel/skip DL reception (e.g., reception of DL resources) on the symbol (/ slot), one or more of the following may be applied. Cancellation/skipping may mean that among other reception occasions of DL resources, reception of DL resources may be performed by the WTRU (e.g., depending on the conditions of each reception occasion and/or whether DL resources are periodic or semi-persistent).
In the case where the WTRU determines that the second set of RBs is valid as DL for scheduled/configured DL reception (e.g., PDCCH, PDSCH, SPS-PDSCH and/or RS measurements), and, for example, if the WTRU identifies/determines that the symbol (e.g., slot) is for "DL" (e.g., rather than for "UL", UL and DL are not mixed in the same symbol (/ slot)), the WTRU may perform DL Rx on the first set of RBs, or else (e.g., if the WTRU identifies/determines that the symbol/slot is for "UL") may cancel/skip DL reception (e.g., reception of DL resources) on the symbol (e.g., slot), one or more of the following may apply. The WTRU may identify/determine a symbol (e.g., slot) for "DL". If not fully allocated on the second set of RBs (e.g., if less than Y 1 RBs are allocated), reception (e.g., any reception) of DL resources (e.g., scheduled, configured, or indicated as measuring/monitoring such as PDCCH, PDSCH, SPS-PDSCH, DL-RS, etc.) may be canceled/skipped on that symbol (e.g., along with other associated symbols of DL resources). A transmission (e.g., any transmission) of UL resources (e.g., scheduled, configured, or indicated as a transmission such as PUCCH, PUSCH, CG-PUSCH, UL-RS, etc.) may be canceled on a symbol (e.g., as well as other associated symbols for UL resources due to HD-WTRU operation). Cancellation/skipping may mean that transmission of UL resources may be performed by the WTRU among other reception occasions of UL resources (e.g., depending on the conditions of each transmission occasion and/or whether UL resources are periodic or semi-persistent). Y 1、RDL and/or D 2 may be configured, predefined, or indicated.
The WTRU may identify/determine a symbol (e.g., slot) for "DL" based on an implicit determination and/or an explicit indication. In an example, by implicit determination, the WTRU may identify/determine a symbol (e.g., slot) for "DL" if there is at least one DL Rx (e.g., scheduled/configured/indicated) on at least D1 RB of the second set of RBs (e.g., and/or if there is no scheduled/configured/indicated UL Tx on at least D2 RB of the second set of RBs). D1 and/or D2 may be configured, predefined, or indicated (e.g., they may be the same). In an example, the WTRU may identify/determine a symbol (e.g., slot) for "DL" based on a legacy configuration (e.g., tdd-UL-DL-config-common/decoded), e.g., according to the indicated symbol/slot marked with "D" (e.g., and/or "F"). This may mean that DL symbols/slots (e.g., indicated as actual communication direction as DL on DL symbols/slots) will be indicated by legacy configurations (e.g., legacy DCI format 2_0, (e.g., for supporting HD-WTRUs)), and a new tdd-UL-DL-config (e.g., for XDD) including one or more "M n" types may be signaled to the WTRU individually/independently, where the new tdd-UL-DL-config may have an overlapping indication of the selective "M n" type on the same symbol marked with "D" or "U" in the legacy configuration. Allowing this overlap may result in a new tdd-UL-DL-config (e.g., for XDD) having the purpose of checking resource validity in the RB level with at least one cancel/skip condition (e.g., for XDD operations such as for HD-WTRUs), but the actual communication direction/link for UL or DL may be indicated by a legacy configuration (e.g., via DCI format 2_0).
One or more of the following may be applied in the case where the reception (e.g., any reception) of DL resources (e.g., scheduled, configured or indicated to measure/monitor such as PDCCH, PDSCH, SPS-PDSCH, DL-RS, etc.) is canceled/skipped on that symbol (e.g., along with other associated symbols of DL resources) if not fully allocated on the second set of RBs (e.g., if less than Y 1 RBs are allocated). The cancel/skip condition may be predefined/preconfigured/indicated. The cancel/skip condition may be predefined/preconfigured/indicated by a particular channel/signal (e.g., by PDCCH such as CORESET and/or at least one of search space, PDSCH, CSI-RS, etc.). In an example, the cancel/skip condition may be based on determining a ratio R 2 of a first number of RBs of DL resources that completely overlap with the second set of RBs to a second number of RBs of DL resources that do not overlap with the second set of RBs. If the ratio R 2 is less than the threshold R DL, the reception of the DL resource may be canceled/skipped on that symbol (e.g., as well as other associated symbols of the DL resource). In an example, the cancel/skip condition may be based on checking whether all symbols (e.g., or D 2 symbols) for receiving DL resources (e.g., for a slot) satisfy at least one condition described herein. If so, DL resources may be received. If not all symbols (e.g., or D 2 symbols) are satisfied, the reception of the DL may be cancelled/skipped for the corresponding reception occasion (e.g., for the slot). In an example, the cancel/skip condition may be determined/defined/configured (e.g., independently determined/defined/configured) based on whether DL resources are scheduled by DCI (e.g., dynamic scheduling/grant cases) or higher layer signaling (e.g., semi-static scheduling cases, configuration grant cases, etc.). Cancellation/skipping may mean that among other reception occasions of DL resources, reception of DL resources may be performed by the WTRU (e.g., depending on the conditions of each reception occasion and/or whether DL resources are periodic or semi-persistent).
Priority rules for resource validity checking based on the "M n" type may be provided. For at least one condition as to how the WTRU identifies/determines symbols for "UL" (e.g., or "DL") as described herein to check resource validity (e.g., in terms of XDD operation, such as for HD-WTRUs in RB level, if both "DL" and "UL" are identified/determined to be valid on symbol/slot) (e.g., if "F" is indicated on symbol/slot via tdd-UL-DL-config-common/decoded of DCI format 2_0 and/or legacy signaling based on DCI SFI signaling), one or more of the following may be applied. The priority rule may be applied according to at least one priority rule of a plurality of priority rules as described below. The priority may be set differently for each different DL/UL channel/signal.
In the case where the priority rule is applied according to at least one priority rule of the plurality of priority rules, one or more of the following may be applied. The "DL" may have a higher priority than the "UL". For example, if the priority is set to "DL," the WTRU may identify/determine that the symbol/slot is for "DL" and may apply at least one action described herein as corresponding to DL. Alternatively, "UL" may have a higher priority than "DL". For example, if the priority is set to "UL", the WTRU may identify/determine that the symbol/slot is for "UL" and may apply at least one action described herein that corresponds to UL.
Where the priority is set differently for each different DL/UL channel/signal, one or more of the following may be applied. For example, DL/UL control channels (e.g., PDCCH/PUCCH) may have higher priority than DL/UL data channels (e.g., PDSCH/PUSCH). For example, if the WTRU identifies/determines that both PDCCH (e.g., as DL control channel) and PUSCH (e.g., as UL data/shared channel) are valid on a symbol/slot, the WTRU may identify/determine that the symbol/slot is for "DL" based on priority, and may apply at least one of the actions described herein as corresponding to DL. For example, if the WTRU identifies/determines that both PUCCH (e.g., as a UL control channel) and PDSCH (e.g., as a DL data/shared channel) are valid on a symbol/slot, the WTRU may identify/determine that the symbol/slot is for "UL" based on priority and may apply at least one of the actions described herein as corresponding to UL. The control/data channel (e.g., at least one of PDCCH/PUCCH/PDSCH/PUSCH) may have a higher priority than the RS (e.g., at least one of CSI-RS and/or SRS). For example, if the WTRU identifies/determines that PDSCH (e.g., as DL data/shared channel) and SRS (e.g., as UL RS) are both valid on symbols/slots, the WTRU may identify/determine that the symbols/slots are for "DL" based on priority, and may apply at least one of the actions described herein as corresponding to DL. For example, if the WTRU identifies/determines that PUSCH (e.g., as UL data/shared channel) and CSI-RS (e.g., as DL RS) are both valid on a symbol/slot, the WTRU may identify/determine that the symbol/slot is for "UL" based on priority, and may apply at least one of the actions described herein as corresponding to UL. Among the control channels, a first control channel associated with at least one common search space may have a higher priority than a second control channel not associated with the common search space (e.g., associated with only WTRU-specific search spaces).
Behavior (e.g., and/or "M n" type) of the muting RB based on the indication may be provided. In an example, based on satisfying at least one condition described herein (e.g., if a symbol/slot corresponds to, belongs to, is associated with, and/or is configured/indicated by a "M n" type for a symbol/slot) and/or if at least one indication of a muting RB described herein is given to a WTRU, one or more of the following may be applied (e.g., based on WTRU behavior of "M n" type, such as for FD-WTRU and/or HD-WTRU). For active DL BWP (e.g., to receive DL on slots/symbols), one or more of the following may be applied if the WTRU receives a muting command on a DL RB according to at least one example described herein on the corresponding symbol on which the muting DL RB is applied. For active UL BWP (e.g., for transmitting UL on slots/symbols), one or more of the following may be applied if the WTRU receives a muting command on the UL RB according to at least one example described herein on the corresponding symbol on which the muting UL RB is applied.
In the event that the WTRU receives a mute command on a DL RB according to at least one example described herein on a corresponding symbol on which to apply the mute DL RB, one or more of the following may be applied. Reception (e.g., any reception) of DL resources (e.g., scheduled, configured, or indicated to measure/monitor such as PDCCH, PDSCH, SPS-PDSCH, CSI-RS, etc.) may be performed on symbols (e.g., and other associated symbols of DL resources) by WTRUs if they do not overlap completely with silent DL RBs (or do not exceed X RBs) and/or if a resource validity check for DL based on the "M n" type is successful/satisfactory (e.g., determined to be valid at least for DL, etc.). By applying muting (e.g., or rate matching or RB level frequency resource skipping or RB level puncturing, etc.) on DL RBs corresponding to the muting command within a second DL RB allocated for DL resources (e.g., scheduled, configured, or indicated as measurement/monitoring), the execution of the reception of DL resources may be applicable (e.g., configured to do so). The receiving RB for the DL resource may be a third RB that is part of the second RB, wherein the third RB may have (e.g., result in) discontinuous RB allocation due to the muting command on the DL RB. If overlapping with a silent DL RB (e.g., all, part, or more than X RBs) and/or if a resource validity check for DL based on the "M n" type fails (e.g., is determined to be invalid for DL, etc.), reception (e.g., any reception) of DL resources (e.g., is scheduled, configured, or indicated to measure/monitor such as PDCCH, PDSCH, SPS-PDSCH, CSI-RS, etc.) may be canceled/skipped on the symbols (e.g., as well as other associated symbols of DL resources). Cancellation/skipping may mean that among other reception occasions of DL resources, reception of DL resources may be performed by the WTRU (e.g., depending on the conditions of each reception occasion and/or whether DL resources are periodic or semi-persistent). X may be predefined, preconfigured or indicated (e.g., indicated separately). If DL resources (e.g., CSI-RS resources and/or SSB indexes) are used as CSI (e.g., associated CSI or BM) for UL Tx reporting, if DL resources overlap with silent DL RBs (e.g., full, partial, or more than X RBs) and/or if resource validity checks for DL based on "M n" type fail (e.g., are determined to be invalid for DL, etc.), measurement-based DL resources may be cancelled/skipped on a second symbol/slot of a scheduling/configuration/indication CSI (e.g., associated CSI or BM) report (e.g., CSI-RS resources and/or SSB indexes) as CSI for UL Tx (e.g., associated CSI or BM). This may apply at least to wideband reporting for CSI (e.g., or BM) reporting. If the WTRU is configured/indicated to perform subband reporting (e.g., in addition to wideband reporting) as UL Tx based on measured DL resources (e.g., CSI-RS resources and/or SSB indexes), the WTRU may skip reporting for subbands (e.g., subbands only) that overlap with silent DL RBs (e.g., full, partial, or more than Z RBs), and/or overlap with RBs not indicated as "DL" according to the selective "M n" type indicated on the symbol. Z may be predefined, preconfigured or indicated (e.g., indicated separately). For example, if the WTRU is configured/indicated to report subband reports on 4 subbands (e.g., including a first subband, a second subband, a third subband, and a fourth subband), and the first and third subbands overlap more than Z RBs within a muted DL RB (e.g., and/or within an RB portion not indicated as "DL" according to the selective "M n" type indicated on the symbol), the WTRU may report a subband report including a second subband CSI (e.g., derived on the second subband) and a fourth subband CSI (e.g., derived on the fourth subband), and may skip the first subband CSI (e.g., corresponding to the first subband) and first subband CSI (e.g., corresponding to the first subband) and third subband CSI (e.g., corresponding to the third subband) (e.g., not reported as part of a subband report). The parameter Z may be given independently/individually per subband. For example, Z 1、Z2, etc. may be preconfigured or indicated (e.g., individually indicated), where Z 1 is used as Z for the first subband described above, Z 2 is used as Z for the second subband described above, etc., depending on the configuration/indication from the gNB (e.g., Z k parameters for each subband, for a group of subbands, or for a group of RBs, etc.).
In the event that the WTRU receives a muting command on the UL RB according to at least one example described herein on the corresponding symbol on which the muting UL RB is applied, one or more of the following may be applied. If not fully overlapping with the silent UL RBs (or no more than Y RBs) and/or if the resource validity check for UL based on the "M n" type is successful/satisfactory (e.g., determined to be valid at least for UL, etc.), then the transmission (e.g., any transmission) of UL resources (e.g., scheduled, configured, or indicated as a transmission such as PUCCH, PUSCH, CG-PUSCH, SRS, etc.) may be performed by the WTRU on the symbols (e.g., and other associated symbols of UL resources). By applying muting (e.g., or rate matching or RB level frequency resource skipping, etc.) on UL RBs corresponding to the muting command within a second UL RB allocated for UL resources (e.g., scheduled, configured, or indicated as transmission), execution of transmission of UL resources may be applicable (e.g., configured to do so). This may mean that the transmission RB for the UL resource may be a third RB that is part of the second RB, wherein the third RB may have (e.g., result in) a discontinuous RB allocation due to the muting command on the UL RB. If overlapping with a silent UL RB (e.g., all, part, or more than Y RBs) and/or if a resource validity check for UL based on the "M n" type fails (e.g., is determined to be invalid for UL, etc.), transmissions (e.g., any transmissions) of UL resources (e.g., scheduled, configured, or indicated as being transmitted such as PUCCH, PUSCH, CG-PUSCH, SRS, etc.) may be canceled/skipped on symbols (e.g., and other associated symbols of UL resources). Cancelling/skipping may mean that transmission of UL resources may be performed by the WTRU among other transmission occasions of UL resources (e.g., depending on the conditions of each transmission occasion and/or whether UL resources are periodic or semi-persistent). Y may be predefined, preconfigured or indicated (e.g., indicated separately).
PDCCH monitoring behavior based on the "M n" type and/or muting RBs may be provided. XDD mode may refer to one or more of the following: an operation mode in which a new type of slot format indicator (e.g., an XDD slot format indicator) may be used, wherein the new type of slot format indicator may indicate a first resource portion that may be associated with a first direction (e.g., downlink), a second resource portion that may be associated with a second direction (e.g., uplink), and a third resource portion that may be associated with a third direction (e.g., side link); wherein the gNB may indicate an operating mode for a transmission direction (e.g., uplink or downlink) of a portion of resources (e.g., time/frequency resources), wherein the transmission direction indication may be based on semi-static signaling (e.g., RRC or MAC-CE) or dynamic signaling (L1 signaling, DCI, SCI, etc.); an operating mode in which a first resource portion and a second resource portion within a slot (e.g., or symbol) may be associated with different transmission directions (e.g., a first resource portion in a slot may be associated with a downlink and a second resource portion in a slot may be associated with an uplink); and/or an operation mode in which the first resource portion may be used for one transmission direction at a time and the second resource portion may be used for multiple transmission directions (e.g., downlink and uplink) at the same time.
The term "XDD" may be used interchangeably with Subband Full Duplex (SFD), full Duplex (FD), and/or cross-division duplex (CDD). The non-XDD mode may be referred to as one or more of the following: wherein an operating mode of one or more slot format indicators may be used and the one or more slot format indicators may determine a transmission direction (e.g., downlink, uplink, or side link) of a slot or symbol; and/or an operation mode in which a single transmission direction is used for a slot or symbol.
An XDD slot may refer to one or more of the following: a time slot may include a first resource portion that may be associated with a first transmission direction (e.g., downlink) and a second resource portion that may be associated with a second transmission direction (e.g., uplink); a time slot that may include a set of resources, the transmission direction of which may include multiple transmission directions (e.g., downlink and uplink); and/or slots that may be associated with a new slot format indicator (e.g., M n). For example, the XDD slot format may be indicated with a new slot format indicator. The XDD slot format indicator may be referred to as a slot format indicator, which may indicate one of the XDD slot formats. The XDD slot format may include at least one of DL resources, UL resources, or flexible resources.
The term "XDD slot" may be used interchangeably with XDD symbol, XDD bandwidth part, XDD time/frequency resource, XDD time window and/or XDD time resource. The term "non-XDD slot/symbol" may refer to a slot/symbol comprising time/frequency resources for a single transmission direction (e.g., downlink, uplink or side link).
An association between XDD mode/slot and search space/CORESET may be provided. In an example, the WTRU may be configured with one or more CORESETs and/or one or more search spaces, where CORESET and/or the search spaces may be associated with an operating mode (e.g., XDD mode/slot or non-XDD mode/slot). The WTRU may receive CORESET and/or configuration information for the search space, where the configuration (e.g., configuration information) may include its associated mode of operation (e.g., XDD mode or non-XDD mode). CORESET associated with a first mode of operation (e.g., XDD mode) may be provided. A search space associated with a first mode of operation (e.g., XDD mode) may be provided.
In the case where the WTRU receives CORESET and/or configuration information for the search space, which may include its associated mode of operation (e.g., XDD mode or non-XDD mode), one or more of the following may be applied. The WTRU may determine a monitored set of control information (e.g., DCI format, SFI type, and/or bit field interpretation) in the search space based on its associated mode of operation. For example, the WTRU may monitor for an indication of a new SFI type (e.g., an XDD slot format indication) in a search space configured with a first mode of operation (e.g., XDD mode). The WTRU may monitor for an indication of an existing SFI type (e.g., a non-XDD slot format indication) in a search space configured with a second mode of operation (e.g., a non-XDD mode). The WTRU may determine a slot type of a slot including the search space based on an operation mode associated with the search space. For example, if the search space monitored in a slot is associated with a first mode of operation (e.g., XDD mode), the WTRU may determine the slot as a first slot type (e.g., XDD slot). If the monitored search space in the slot is associated with a second mode of operation (e.g., a non-XDD mode), the WTRU may determine the slot as a second slot type (e.g., a non-XDD slot). If the search space is associated with a single CORESET, the mode of operation associated with the search space may be determined based on the mode of operation configured for CORESET associated with the search space.
CORESET associated with a first mode of operation (e.g., XDD mode) may be provided. The subset of RBs within BWP may not be used for CORESET configurations. For example, a set of RBs in the middle of BWP may be considered as unavailable resources for CORESET, and the WTRU may desire that the set of RBs configured for CORESET associated with the first mode of operation not include the set of RBs. The subset of resources configured for CORESET may be indicated as a disabled state, where the disabled state may be used interchangeably with unavailable, dropped, flipped to uplink resources, quiesced, or punctured state. If the subset of resources for CORESET is disabled, one or more of the following may be applied. The WTRU may skip monitoring one or more PDCCH candidates associated with CORESET. The WTRU may monitor a subset of PDCCH candidates that do not have forbidden resources (e.g., CCEs, REGs, and/or REG bundles) within the PDCCH candidate resources. The WTRU may determine to monitor for PDCCH candidates based on whether one or more resources for the PDCCH candidates are disabled.
A search space associated with a first mode of operation (e.g., XDD mode) may be provided. A set of time resources configured for the search space may be allowed and/or configured for a first mode of operation (e.g., XDD mode), wherein one or more of the following time resources may not be allowed or used for the first mode of operation: time resources (e.g., slots or symbols) including synchronization signals (e.g., SS/PBCH blocks); time resources available for measurements (e.g., RRM measurements, neighbor cell measurements, positioning measurements, etc.); a time source configurable for some purpose (e.g., URLLC, mctc, side link operation, and/or NTN); and/or may be configured as a time resource indicating a mode of operation. For example, a set of time resources (e.g., slots) may be configured for WTRU monitoring indications (e.g., SFI, XDD slot configuration), and may be used as a non-XDD mode. For example, if the WTRU is instructed to operate in a first mode of operation, the WTRU may monitor a search space associated with the first mode of operation (e.g., XDD mode). Otherwise, the WTRU may skip monitoring the search space associated with the first mode of operation.
The term "search space" may be used interchangeably with PDCCH search space, monitoring search space, control channel search space, and PSCCH search space.
Search space configurations for XDD and non-XDD modes may be provided. In an example, a WTRU may be configured with one or more sets of search spaces, where a first set of search spaces may be associated with a first mode of operation (e.g., XDD mode) and a second set of search spaces may be associated with a second mode of operation (e.g., non-XDD mode). The time resources for the first set of search spaces may not overlap with the time resources for the second set of search spaces. The XDD slot format indicator may be used for slots associated with the first set of search spaces. There may be an overlap (e.g., or conflict) between time resources configured for the first set of search spaces and the second set of search spaces. The content of the DCI format may differ based on monitoring the set of search spaces.
In the case where an XDD slot format indicator is used for a slot associated with a first set of search spaces, one or more of the following may be applied. For example, the WTRU may determine an XDD slot format of a slot associated with the first set of search spaces, where the XDD slot format may be indicated via higher layer signaling (e.g., RRC or MAC-CE) and/or L1 signaling (e.g., DCI). The WTRU may determine a non-XDD slot format (e.g., indicated or configured) of the slots associated with the second set of search spaces.
In the event that there is an overlap (e.g., or conflict) between time resources configured for the first set of search spaces and the second set of search spaces, one or more of the following may be applied. The WTRU may determine that time resources are used for a first set of search spaces (e.g., or a second set of search spaces). The WTRU may skip monitoring the time resources. For example, if the frequency resources do not overlap (e.g., and the frequency resources for the second set of search spaces are still indicated as downlink resources in the XDD slot format indicator), the WTRU may monitor both the first set of search spaces and the second set of search spaces.
In the case where the content of the DCI format is different based on the monitored set of search spaces, one or more of the following may be applied. In an example, the WTRU may determine a first set of DCI contents for the DCI format when the WTRU monitors the DCI format in a first set of search spaces and may determine a second set of DCI contents for the DCI format when the WTRU monitors the DCI format in a second set of search spaces. The first DCI content (e.g., XDD slot format indicator) may be included in the first set of DCI content and not in the second set of DCI content. The second DCI content (e.g., frequency resource allocation field) may have a first size in the first set of DCI content and a second size in the second set of DCI content. For example, the first size may be larger than the second size based on the assumption that the non-XDD slots may have a larger amount of resources for the downlink or uplink than the XDD slots.
In an example, a first search space type (e.g., a common search space) may be associated with a first mode of operation (e.g., a non-XDD mode) and a second search space type (e.g., a WTRU-specific search space) may be associated with one of the modes of operation (e.g., an XDD mode or a non-XDD mode). The WTRU may determine a time slot including a search space having a first search space type (e.g., a common search space) as a non-XDD time slot. The WTRU may determine a set of resources (e.g., RBs) configured for a search space having a first search space type (e.g., a common search space) as downlink resources. The WTRU may assume that the XDD slot format indicator is not applied to or used for a slot that includes a search space having a first search space type (e.g., a common search space). The first search space type may be a search space associated with a default CORESET (e.g., CORESET # 0).
In an example, the WTRU may determine the search space in the monitoring slot based on the amount of resources reallocated for uplink search space. In an example, in an XDD slot, the WTRU may skip monitoring the search space if at least one resource for the search space is reallocated for uplink. In an example, the WTRU may skip monitoring the search space if the amount of resources reallocated for uplink search space is greater than a threshold, where the threshold may be predetermined, configured, or indicated by the gNB.
The resources for CORESET may be time/frequency resources determined based on CORESET configuration information and its associated search space configuration information. For example, CORESET configuration information may determine the frequency resources and the number of symbols within a slot, and search space configuration information may determine the time resources (e.g., the slot and the starting symbols within the slot).
The resources used for the search space may be used interchangeably with the resources used for CORESET.
The WTRU may monitor search spaces associated with the plurality CORESET. In an example, the search space may be associated with one or more CORESET (e.g., CORESET identification and/or CORESET-id), and the WTRU may determine which CORESET (e.g., CORESET-id) to use to monitor the search space based on the slot type determined for the time slots in which the WTRU monitors the search space. In an example, the WTRU may be configured with a search space that may be associated with a first CORESET (e.g., CORESET-id=1) and a second CORESET (e.g., CORESET-id=2). The WTRU may monitor the search space with the first CORESET in the slot determined to be the XDD slot. The WTRU may monitor the search space with the second CORESET in the time slot determined to be a non-XDD time slot, where the first CORESET and the second CORESET may have different sets of RBs within the BWP. If more than one CORESET is associated with the search space, the WTRU may determine CORESET to monitor the search space (e.g., CORESET within CORESET associated with the search space), the first CORESET associated with the search space may be referred to as a default CORESET, and the second CORESET associated with the search space may be referred to as an auxiliary CORESET.
In the case where the WTRU determines CORESET for monitoring the search space (e.g., CORESET within CORESET associated with the search space), one or more of the following may be applied. The WTRU may determine CORESET (e.g., within CORESET associated with the search space) based on the mode of operation (e.g., indicated). For example, an operation mode (e.g., XDD mode or non-XDD mode) may be indicated to the WTRU via higher layer signaling or L1 (e.g., layer 1 and/or physical layer) signaling. The WTRU may determine CORESET (e.g., within CORESET associated with the search space) based on a Slot Format Indicator (SFI) value (e.g., indicated/provided). For example, if the time slot for which the WTRU monitors the search space indicates a first SFI value, the WTRU may determine to use the first CORESET. For example, if the time slot for which the WTRU monitors the search space indicates a second SFI value, the WTRU may determine to use a second CORESET. The WTRU may determine CORESET (e.g., within CORESET associated with the search space) based on one or more system parameters including slot index, subcarrier spacing, bandwidth, and/or frequency band (e.g., provided/indicated).
In the case where more than one CORESET is associated with a search space, the first CORESET associated with the search space may be referred to as a default CORESET and the second CORESET associated with the search space may be referred to as an auxiliary CORESET, one or more of the following may be applied. The WTRU may determine to use the default CORESET to monitor the associated search space regardless of the slot type, e.g., if the configuration resources for default CORESET are still downlink resources, e.g., based on the indicated "M n" type. For example, if one or more resources for default CORESET are indicated for another transmission direction (e.g., uplink), the WTRU may determine to use assistance CORESET to monitor the associated search space. The resources for CORESET that are indicated for another transmission direction may be referred to as rollover resources, interruption resources, discard resources, muting resources, reallocation resources (e.g., for uplink), and/or handover resources. If the number of rollover resources is greater than the threshold, assist CORESET may be used. If more than one auxiliary CORESET is configured, an auxiliary CORESET that satisfies one or more of the following conditions may be used: the number of flipped resources in a slot is less than CORESET of the threshold, CORESET with no flipped resources in a slot, CORESET configured with a first mode of operation (e.g., XDD mode), and/or CORESET with the lowest CORESET-id within the configured auxiliary CORESET. The WTRU may determine to use a default CORESET to monitor an associated search space in a slot determined to be a non-XDD slot; otherwise, the WTRU may determine to use the assist CORESET to monitor the associated search space. Which CORESET the WTRU uses to monitor the associated search space may be indicated via higher layer signaling (e.g., RRC and/or MAC-CE) or L1 signaling (e.g., DCI). The WTRU may be indicated at slot #n-K which CORESET (e.g., CORESET-id) to use for slot #n, where K may be a positive integer.
In an example, the WTRU may be configured with a search space having one or more associated CORESET, and the WTRU may monitor the search space with one or more (e.g., all) associated CORESET. The WTRU may skip monitoring the PDCCH candidates if there are any rollover resources for the PDCCH candidates. If the total number of PDCCH candidates is greater than the threshold, the WTRU may skip monitoring one or more PDCCH candidates based on the priority. The WTRU may monitor the search space with all associated CORESET in a first slot type (e.g., non-XDD slots) and the WTRU may monitor the search space with an associated CORESET subset in a second slot type (e.g., XDD slots).
In the event that the total number of PDCCH candidates is greater than a threshold, the WTRU may skip monitoring one or more PDCCH candidates based on a priority, where the priority may be determined based on one or more of the following. The priority may be determined based on CORESET-ids. For example, PDCCH candidates associated with lower CORESET-ids may be considered to have higher priority (e.g., or lower priority). The priority may be determined based on CCE aggregation levels. For example, PDCCH candidates with lower aggregation levels may be considered to have higher priorities (e.g., or lower priorities). The priority may be determined based on the REG bundling size. For example, PDCCH candidates with larger REG bundling sizes may be considered to have higher priority (e.g., or lower priority).
In the case where the WTRU monitors the search space with one or more (e.g., all) of the associated CORESET in a first slot type (e.g., non-XDD slots) and the WTRU monitors the search space with a subset of the associated CORESET in a second slot type (e.g., XDD slots), the subset of CORESET may be determined based on whether there are any flipped resources for CORESET and/or whether CORESET are configured for at least one of the modes of operation (e.g., XDD modes).
BWP configuration information may be provided. The WTRU may be configured with one or more BWP, wherein a first BWP (e.g., a default BWP or bwp#0) may be associated with a first mode of operation (e.g., a non-XDD mode) and a second BWP may be associated with a second mode of operation (e.g., an XDD mode). The BWP configuration information may include an operation mode (e.g., an XDD mode or a non-XDD mode). The first BWP (e.g., default BWP or bwp#0) may be the same (e.g., shared) as the third BWP (e.g., the "default" BWP), e.g., the third BWP may be activated based on expiration of the BWP inactivity timer. The first BWP (e.g., default BWP or bwp#0) may be the same (e.g., shared) as the fourth BWP (e.g., an "initial" BWP), e.g., the fourth BWP may be used for initial access (e.g., until the WTRU receives a dedicated configuration parameter such as RRC connection).
In the case where the BWP configuration information includes an operation mode (e.g., an XDD mode or a non-XDD mode), one or more of the following may be applied. If the WTRU is configured with BWP and a first mode of operation (e.g., XDD mode), the WTRU may desire to monitor DCI that may include an XDD slot format indicator. The WTRU may not expect to receive the XDD slot format indicator in BWP configured for non-XDD mode.
Although the above features and elements are described in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements.
While the implementations described herein may consider 3GPP specific protocols, it should be appreciated that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, while the solutions described herein consider LTE, LTE-a, new Radio (NR), or 5G specific protocols, it should be understood that the solutions described herein are not limited to this scenario, and are applicable to other wireless systems as well.
The processes described above may be implemented in computer programs, software and/or firmware incorporated in a computer readable medium for execution by a computer and/or processor. Examples of computer readable media include, but are not limited to, electronic signals (transmitted over a wired or wireless connection) and/or computer readable storage media. Examples of 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, but not limited to, internal hard disks and removable disks), magneto-optical media, and optical media (such as Compact Disks (CD) -ROM disks, and/or Digital Versatile Disks (DVD)). A processor associated with the software may be used to implement a radio frequency transceiver for the WTRU, the terminal, the base station, the RNC, and/or any host computer.
Claims (15)
1. A method implemented in a wireless transmit/receive unit (WTRU), the method comprising:
Receiving an indication that each of the one or more symbols includes both a first subset of resource blocks associated with Downlink (DL) reception and a second subset of resource blocks associated with Uplink (UL) transmission;
Receiving DL transmissions associated with the one or more periodic DL resources in the one or more symbols on condition that the one or more periodic DL resources are included in the first subset of resource blocks associated with DL reception of the one or more symbols; and
A first UL transmission associated with the one or more periodic UL resources in the one or more symbols is transmitted on condition that the one or more periodic UL resources are included in the second subset of resource blocks associated with UL transmission of the one or more symbols.
2. The method of claim 1, further comprising receiving configuration information in a Radio Resource Control (RRC) message, the configuration information indicating a plurality of UL/DL resource block patterns for the one or more symbols.
3. The method of claim 2, wherein the plurality of UL/DL resource block patterns are indicated in the RRC message using a bitmap.
4. The method of claim 2, wherein the indication is received via Downlink Control Information (DCI) or a Medium Access Control (MAC) Control Element (CE) and indicates which one of the plurality of UL/DL resource block patterns indicated in the configuration information is to be applied to the one or more symbols.
5. The method of claim 4, wherein the indication indicates that a first UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a first symbol of the one or more symbols, and the indication indicates that a second UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a second symbol of the one or more symbols.
6. The method of claim 1, the method further comprising:
Discarding a second UL transmission associated with the one or more second periodic UL resources in the one or more symbols, provided that the one or more second periodic UL resources are included in the first subset of resource blocks associated with DL reception of the one or more symbols.
7. The method of claim 1, wherein the periodic UL resources are used for one or more of a Physical Uplink Control Channel (PUCCH) or a configuration grant physical uplink shared channel (CG-PUSCH).
8. A WTRU, the WTRU comprising:
a communication circuit; and
A processor configured to:
Receiving, via the communication circuitry, an indication that each of the one or more symbols includes both a first subset of resource blocks associated with Downlink (DL) reception and a second subset of resource blocks associated with Uplink (UL) transmission;
Receiving, via the communication circuitry, a first DL transmission associated with one or more periodic DL resources in the one or more symbols, provided that the one or more periodic DL resources are included in the first subset of resource blocks associated with DL reception of the one or more symbols; and
UL transmissions associated with the one or more periodic UL resources in the one or more symbols are transmitted via the communication circuitry on condition that the one or more periodic UL resources are included in the second subset of resource blocks associated with UL transmissions of the one or more symbols.
9. The WTRU of claim 8, wherein the processor is further configured to receive configuration information via the communication circuitry, the configuration information indicating a plurality of UL/DL resource block patterns for the one or more symbols.
10. The WTRU of claim 9, wherein the plurality of UL/DL resource block patterns are indicated using a bitmap.
11. The WTRU of claim 9, wherein the indication is received via Downlink Control Information (DCI) or a Medium Access Control (MAC) Control Element (CE) and indicates which one of the plurality of UL/DL resource block patterns indicated in the configuration information is to be applied to the one or more symbols.
12. The WTRU of claim 11, wherein the indication indicates that a first UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a first symbol of the one or more symbols and the indication indicates that a second UL/DL resource block pattern of the plurality of UL/DL resource block patterns is to be applied to a second symbol of the one or more symbols.
13. The WTRU of claim 9, wherein an RRC message includes the configuration information.
14. The WTRU of claim 8, wherein the processor is further configured to fail to receive a second DL transmission associated with one or more second periodic DL resources in the one or more symbols on a condition that the one or more second periodic DL resources are included in the second subset of resource blocks associated with UL reception of the one or more symbols.
15. The WTRU of claim 8, wherein the periodic DL resources are used for one or more of a Physical Downlink Control Channel (PDCCH) or a configuration grant physical downlink shared channel (CG-PDSCH).
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US63/244,471 | 2021-09-15 | ||
| US202263395969P | 2022-08-08 | 2022-08-08 | |
| US63/395,969 | 2022-08-08 | ||
| PCT/US2022/043119 WO2023043683A1 (en) | 2021-09-15 | 2022-09-09 | Dynamic slot format indications and wtru behaviors associated with xdd |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118104174A true CN118104174A (en) | 2024-05-28 |
Family
ID=91149490
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202280068491.6A Pending CN118104174A (en) | 2021-09-15 | 2022-09-09 | Dynamic slot format indication and WTRU behavior associated with XDD |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118104174A (en) |
-
2022
- 2022-09-09 CN CN202280068491.6A patent/CN118104174A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113544989B (en) | Side link feedback channel | |
| CN111034097B (en) | Reliable control signaling | |
| CN113508547A (en) | Method for NR SL multi-subchannel PSCCH transmission | |
| CN118764144A (en) | Wireless transmitting and receiving unit and method thereof | |
| CN116325547A (en) | Beam indication based on TCI state groups | |
| WO2020033513A1 (en) | Control information transmission and sensing in wireless systems | |
| CN115486001A (en) | Enhancement of physical channels in multiple TRPs | |
| CN116158018A (en) | Method, architecture, apparatus and system for dynamically determining processing time | |
| WO2022081722A1 (en) | Methods, apparatuses directed to enabling tone reservations in wireless systems | |
| TWI815157B (en) | Time and code domain coverage enhancements | |
| CN112753194A (en) | CSI feedback in NR-U | |
| CN116963288A (en) | Method and apparatus for flexible aperiodic SRS transmission | |
| CN115606127A (en) | Method and apparatus for improving voice coverage | |
| JP2023536878A (en) | Method and apparatus for dynamic spectrum sharing | |
| TW202316830A (en) | Dynamic slot format indications and wtru behaviors associated with xdd | |
| CN116097594A (en) | PDCCH coverage enhancement | |
| CN118104174A (en) | Dynamic slot format indication and WTRU behavior associated with XDD | |
| US20240372661A1 (en) | Dynamic Slot Format Indications and WTRU Behaviors Associated with XDD | |
| CN112823488B (en) | Method and apparatus for multiple transmit/receive point transmission | |
| CN118104326A (en) | Power control and link adaptation associated with cross-division duplexing (XDD) | |
| TW202415028A (en) | Latency and coverage enhancement for subband non-overlapping full duplex | |
| CN116530150A (en) | Method and apparatus for enabling tone reservation in a wireless system | |
| CN117223358A (en) | Method for implementing carrier switching for uplink control information | |
| WO2023086445A1 (en) | Methods on enhancing reliability and supporting mixed priority traffic in high frequency communications | |
| CN116918283A (en) | Method for ultra-reliable low-delay communication multiplexing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |