Method and device for multi-transmit / receive point transmission
By receiving parameter sets and PDCCH transmissions from multiple TRPs in a multi-TRP environment, decoding the K1 value, determining the PDSCH receiving time slot position, and selecting the farthest PUCCH time slot position, the coordination problem of control information transmission in multi-TRP operation is solved, and the flexibility and reliability of transmission are improved.
Patent Information
- Application Number
- CN201980066429.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-10-09
- Filing Date
- 2019-10-09
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2039-10-09
AI Technical Summary
In multi-TRP operations, existing technologies struggle to effectively coordinate the transmission of control information between multiple TRPs, leading to increased blind search complexity for WTRUs and widespread beam link failures, which in turn affect transmission reliability and flexibility.
By receiving parameter sets and PDCCH transmissions from multiple TRPs, decoding the K1 value of each TRP, determining the PDSCH receiving time slot position, and selecting the farthest PUCCH time slot position for PUCCH transmission based on the comparison of candidate PUCCH time slot positions, the PUCCH time slot positions of multiple TRPs are coordinated to improve transmission efficiency and reliability.
It enables efficient PUCCH slot location determination in a multi-TRP environment, reduces the complexity of blind search, and improves the flexibility and reliability of transmission, especially for ultra-reliable low-latency communication applications.
Smart Images

Figure CN112823488B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 743,339, filed on October 9, 2018, the contents of which are incorporated herein by reference. Background Art
[0003] In New Radio (NR), Multiple TRP (MTRP) operation may be supported. For downlink (DL) NR MTRP, the NR WTRU may be able to receive and process multiple NR-Physical Downlink Control Channels (PDCCHs) and multiple NR-Physical Downlink Shared Channels (PDSCHs).
[0004] In one scenario, a single NR-PDCCH schedules a single NR-PDSCH, where separate NR-PDSCH data layers are sent from separate TRPs. Despite the transmission of multiple NR-PDSCH data layers, the complexity of the WTRU's blind search for downlink control information (DCI) decoding may be similar to that of legacy systems since the WTRU only has to decode one NR-PDCCH. However, scheduling decisions may be centrally coordinated at one gNB, requiring some coordination between multiple TRPs, which may be optimized by one TRP over a large network area. In addition, a beam link failure at the primary coordinating TRP may affect transmissions at all other TRPs since the WTRU may receive control information for all TRPs in the coordination set from one TRP.
[0005] In another scenario, each of the multiple NR-PDCCHs may schedule a corresponding NR-PDSCH, and each NR-PDSCH is sent from a separate TRP. As currently discussed, NR can support up to two NR-PDSCHs per component carrier for a bandwidth portion, and up to two NR-PDCCHs corresponding to a single time slot. Having multiple NR-PDCCHs can produce more scheduling flexibility at the TRP. Each NR-PDCCH can carry different scheduling instructions for the WTRU without being affected by non-ideal backhaul. Therefore, less information may need to be exchanged between cooperating TRPs on the backhaul. Moreover, distributed scheduling can provide diversity because a beam link failure at one TRP may only affect the resources managed by that TRP. Transmissions at other TRPs can continue without interruption. This may be an important factor for ultra-reliable low latency (URLLC) applications. On the other hand, since the WTRU may need to perform blind detection on multiple received NR-PDCCHs, the effective size of the search space may increase. Coordination remains an important aspect of operation to prevent conflicts of NR-PDCCHs sent from MTRPs. Summary of the invention
[0006] A method for multi-transmit / receive point (multi-TRP) transmission, the method comprising receiving a parameter set and a physical downlink control channel (PDCCH) transmission from each TRP of a plurality of TRPs; decoding each received PDCCH transmission based on each received parameter set to obtain a K1 value for each TRP in the plurality of TRPs; receiving a physical downlink shared channel (PDSCH) transmission from each TRP of the plurality of TRPs; determining a PDSCH reception slot position for each received PDSCH transmission; determining a candidate PUCCH slot position for each TRP in the plurality of TRPs based on each determined PDSCH reception slot position and each obtained K1 value; and determining a selected PUCCH slot position for all TRPs in the plurality of TRPs based on a comparison of all determined candidate PUCCH slot positions, wherein, if all determined candidate PUCCH slot positions are not the same, the selected PUCCH slot position is the farthest candidate PUCCH slot position.
[0007] A wireless transmit / receive unit (WTRU) configured to perform multiple transmit / receive point (multi-TRP) transmissions, the WTRU comprising: a receiver; and a processor, wherein the receiver is configured to receive a parameter set, a physical downlink control channel (PDCCH) transmission, and a physical downlink shared channel (PDSCH) transmission from each of a plurality of TRPs; the processor is configured to decode each received PDCCH transmission based on each received parameter set to obtain a K1 value for each of the plurality of TRPs; determine a PDSCH receive slot position for each received PDSCH transmission; determine a candidate PUCCH slot position for each of the plurality of TRPs based on each determined PDSCH receive slot position and each obtained K1 value; and determine a selected PUCCH slot position for all of the plurality of TRPs based on a comparison of all the determined candidate PUCCH slot positions, wherein, if all the determined candidate PUCCH slot positions are not the same, the selected PUCCH slot position is the farthest candidate PUCCH slot position. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals represent like elements, and in which:
[0009] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented;
[0010] Figure 1Bis a diagram showing that according to an embodiment, Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within a communication system is shown;
[0011] Figure 1C is a diagram showing that according to an embodiment, Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the communication system shown;
[0012] Figure 1D is a diagram showing that according to an embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used within the communication system shown;
[0013] Figure 2 is a schematic diagram of two potential scenarios for downlink (DL) multi-TRP (MTRP) operation;
[0014] Figure 3 is a schematic diagram showing asynchronous hybrid automatic repeat request (HARQ) operation in New Radio (NR), where ACK / NACK transmission occurs after physical downlink control channel (PDSCH) decoding K 1 After time slots;
[0015] Figure 4 is shown with T d Schematic diagram of an example of a WTRU with a given WTRU processing delay;
[0016] Figure 5 is a flowchart showing a method for transmitting multiple TRPs according to an embodiment of the present application;
[0017] Figure 6 is a diagram showing K according to an embodiment of the present application 0 and K 1 A schematic diagram of an example of
[0018] Fig. 7A is a schematic diagram showing the relative time slot positions between PDCCH and PDSCH according to an embodiment of the present application;
[0019] Figure 7B is a schematic diagram showing another relative time slot position between a PDCCH and a PDSCH according to an embodiment of the present application;
[0020] Figure 8 is a schematic diagram showing an example of ACK / NACK transmission according to an embodiment of the present application;
[0021] Fig. 9is a schematic diagram showing another example of ACK / NACK transmission according to an embodiment of the present application; and
[0022] Fig.10 is a schematic diagram showing an example of control resource set (CORESET) configuration, where the number of configured CORESETs is equal to the number of configured TRPs. DETAILED DESCRIPTION
[0023] Figure 1A 1 is a diagram showing an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DTS-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC), etc.
[0024] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, any of the WTRUs 102a, 102b, 102c, 102d may be referred to as a station (STA), which may be configured to transmit and / or receive wireless signals, and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices working in an industrial and / or automated process chain environment), consumer electronic devices, and devices working on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.
[0025] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to facilitate access to one or more communication networks (e.g., the CN 106, the Internet 110, and / or other networks 112) by wirelessly interfacing with at least one of the WTRUs 102a, 102b, 102c, 102d. For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation Node B such as a gNode B (gNB), a New Radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. Although each of the base stations 114a, 114b is depicted as a single component, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network components.
[0026] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network components (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies called 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 wireless service coverage for a specific geographic area that is relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, that is, each transceiver corresponds to a sector of the cell. In an embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, by using beamforming, signals may be transmitted and / or received in a desired spatial direction.
[0027] 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).
[0028] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed Uplink (UL) Packet Access (HSUPA).
[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).
[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology that may use NR to establish the air interface 116, such as NR radio access.
[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access (e.g., using dual connectivity (DC) principles). Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).
[0032] 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 (Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), and GSM EDGE (GERAN), among others.
[0033] Figure 1AThe base station 114b in the example may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may use any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In an embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, and the like). As Figure 1A As shown, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114b does not need to access the Internet 110 via the CN 106.
[0034] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or may perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104. For example, in addition to being connected to the RAN 104 employing NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0035] The CN 106 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. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer network devices that use common communication protocols, such as TCP, User Datagram Protocol (UDP), and / or IP in the Transmission Control Protocol / Internet Protocol (TCP / IP) Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or a different RAT as the RAN 104.
[0036] 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). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0037] Figure 1B is a system diagram showing an exemplary WTRU 102. Figure 1B As shown, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a numeric keypad 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0038] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, however it should be appreciated that the processor 118 and the transceiver 120 may also be integrated together in an electronic package or chip.
[0039] The transmit / receive component 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive component 122 may be an antenna configured to transmit and / or receive RF signals. As an example, in another embodiment, the transmit / receive component 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, the transmit / receive component 122 may be configured to transmit and / or receive RF and light signals. It should be appreciated that the transmit / receive component 122 may be configured to transmit and / or receive any combination of wireless signals.
[0040] Although in Figure 1B 102 as a single component, the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0041] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive component 122 and to demodulate signals received by the transmit / receive component 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers that allow the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0042] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a numeric keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data from these components. The processor 118 may also output user data to the speaker / microphone 124, the numeric keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store information in any suitable memory such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as, for example, on a server or a home computer (not shown).
[0043] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power for use by other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
[0044] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via 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 acquire location information via any suitable positioning method while remaining consistent with an embodiment.
[0045] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, FM radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. The peripherals 138 may include one or more sensors. The sensor may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor, etc.
[0046] The WTRU 102 may include a full-duplex radio in which reception or transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous for the radio. A full-duplex radio may include an interference management unit that reduces and / or substantially eliminates self-interference by means of hardware (e.g., chokes) or by signal processing by a processor (e.g., a separate processor (not shown) or by the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio that transmits and receives some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or DL (e.g., for reception)).
[0047] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c using an E-UTRA radio technology over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0048] The RAN 104 may include eNode-Bs 160a, 160b, 160c, however it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.
[0049] Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in the UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0050] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing components are described as being part of the CN 106, it should be appreciated that any of these components may be owned and / or operated by an entity other than the CN operator.
[0051] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, performing bearer activation / deactivation processing, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.
[0052] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during an inter-eNB handover, triggering paging processing when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.
[0053] The SGW 164 may be connected to the PGW 146, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0054] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or communicate with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, and the IP gateway may serve 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.
[0055] Although in Figures 1A-1D Although the WTRU is described as a wireless terminal, it should be appreciated that in certain typical embodiments, such a terminal may use a (eg, temporary or permanent) wired communication interface with a communication network.
[0056] In a typical embodiment, the other network 112 may be a WLAN.
[0057] A WLAN using 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 access or be connected to a distributed system (DS) or other types of wired / wireless networks that send traffic into and / or out of the BSS. Traffic originating from outside the BSS and destined for the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Traffic between STAs within the BSS may be sent through the AP, for example, when the source STA may send traffic to the AP and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. The point-to-point traffic may be sent between the source and destination STAs (e.g., directly therebetween) using a direct link establishment (DLS). In certain typical embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS)). For example, a WLAN using an independent BSS (IBSS) mode does not have an AP, and STAs (eg, all STAs) within or using the IBSS can communicate directly with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode.
[0058] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit a beacon on a fixed channel (e.g., a primary channel). The primary channel may have a fixed width (e.g., a bandwidth of 20 MHz) or a dynamically set width. The primary channel may be a working channel of the BSS and may be used by STAs to establish a connection with the AP. In certain typical embodiments, carrier sense multiple access (CSMA / CA) with collision avoidance (e.g., in an 802.11 system) may be implemented. For CSMA / CA, STAs (e.g., each STA) including the AP may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. In a specified BSS, one STA (e.g., only one station) may transmit at any given time.
[0059] A high throughput (HT) STA may communicate using a 40 MHz wide channel (eg, by combining a 20 MHz wide primary channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).
[0060] Very high throughput (VHT) STA can support channels with widths of 20MHz, 40MHz, 80MHz and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels or by combining two discontinuous 80MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data can be transmitted and passed through a segment parser, which can separate the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed separately on each stream. The stream can be mapped on two 80MHz channels, and the data can be transmitted by the STA performing the transmission. At the receiver of the STA performing the reception, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).
[0061] 802.11af and 802.11ah support working modes below 1 GHz. Compared with 802.11n and 802.11ac, the channel working bandwidth and carrier used in 802.11af and 802.11ah are reduced. 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to a typical embodiment, 802.11ah can support meter type control / machine type communication (MTC) (e.g., MTC devices in macro coverage areas). MTC devices can have certain capabilities, such as limited capabilities including support (e.g., only support) certain and / or limited bandwidths. MTC devices can include a battery, and the battery life of the battery is higher than a threshold (e.g., for maintaining a very long battery life).
[0062] For WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah), these systems include channels that can be designated as primary channels. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by a certain STA, where the STA originates from all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the width of the primary channel can be 1MHz. Carrier sensing and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy (e.g., because a STA (which only supports the 1MHz operating mode) transmits to the AP), then all available frequency bands can be considered busy even if most of the available frequency bands remain idle and available for use.
[0063] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.
[0064] Figure 1D 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c using NR radio technology over the air interface 116. The RAN 104 may also communicate with the CN 106.
[0065] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b, 180c may use beamforming processing to transmit and / or receive signals to and / or from the gNBs 180a, 180b, 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, the gNB 180a may transmit multiple component carriers (not shown) to the WTRU 102a. A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).
[0066] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable digital configuration. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the radio transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., containing different numbers of OFDM symbols and / or lasting different absolute time lengths).
[0067] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect to the gNB 180a, 180b, 180c while communicating / connecting to another RAN (e.g., the eNode-B 160a, 160b, 160c). For example, the WTRU 102a, 102b, 102c may communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principle. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRU 102a, 102b, 102c.
[0068] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support network slicing, DC, implement interworking between NR and E-UTRA, route user plane data to user plane functions (UPFs) 184a, 184b, and route control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. Figure 1D As shown, gNB180a, 180b, and 180c can communicate with each other through the Xn interface.
[0069] Figure 1DThe CN 106 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although the foregoing components are described as part of the CN 106, it should be understood that any of these components may be owned and / or operated by an entity other than the CN operator.
[0070] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating non-access stratum (NAS) signaling, and mobility management, etc. The AMF 182a, 182b may use network slicing processing to customize the CN support provided to the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. As an example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, and / or services for MTC access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) using other radio technologies (e.g., LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi).
[0071] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 106 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 106 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and may configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing DL data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0072] The UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which can provide the WTRUs 102a, 102b, 102c with access to packet-switched networks (e.g., the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b can perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-host PDU sessions, processing user plane QoS, buffering DL packets, and providing mobility anchor processing, etc.
[0073] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b via an N3 interface connected to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b and through the UPF 184a, 184b.
[0074] In view of Figures 1A-1D and about Figures 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 simulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or one or more other devices described herein. These simulation devices may be one or more devices configured to simulate one or more or all of the functions described herein. For example, these simulation devices may be used to test other devices and / or simulate network and / or WTRU functions.
[0075] The simulation device can be designed to implement one or more tests about other devices in a laboratory environment and / or an operator network environment. For example, the one or more simulation devices can perform one or more or all functions while being implemented and / or deployed as part of a wired and / or wireless communication network in whole or in part to test other devices inside the communication network. The one or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly coupled to other devices to perform the test, and / or can use over-the-air wireless communication to perform the test.
[0076] One or more simulation devices can perform one or more functions, including all functions, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test lab and / or a test scenario of a wired and / or wireless communication network that is not deployed (e.g., testing) to implement tests on one or more components. The one or more simulation devices can be test devices. The simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication with the aid of RF circuits (e.g., which can include one or more antennas).
[0077] In order to ensure the efficiency and reliability of multi-TRP operation, many aspects of NR operation should be considered and addressed. In the embodiments described in the present application, methods and apparatus for multi-transmit / receive point (multi-TRP) transmission are described, which can enable the WTRU to manage its NR-PUCCH transmissions regarding multiple NR-PDSCHs from multiple TRPs. In addition, in the embodiments described in the present application, various methods and apparatus are described, which can enable the WTRU to effectively determine its reception state (e.g., multi-TRP operation mode or non-multi-TRP operation mode) through relevant processes to determine and adapt that it can switch between single TRP transmission mode and multi-TRP transmission mode. In addition, in the embodiments described in the present application, various methods and apparatus are described, which can enable coordination of multi-TRP transmissions for both DL demodulation reference signal (DMRS) transmission and uplink (UL) sounding reference signal (SRS) transmission, for example, to maintain orthogonality and reliability of measurements.
[0078] A control resource set (CORESET) may include a set of REs used for downlink control channels and may be configured by its frequency resource, its time length (in symbols) and the type of its REG bundle. A search space (or search space set) may be a set of PDCCH candidates monitored by a WTRU or a group of WTRUs during blind detection of a PDCCH.
[0079] Figure 2is a schematic diagram showing two potential scenarios for downlink multi-TRP operation. In NR, multi-TRP operation is supported, initially focusing on downlink transmissions. It is expected that the WTRU will be able to receive and process multiple PDCCH and PDSCH transmissions. Figure 2 Two main options for downlink multi-TRP operation are shown, where P-TRP refers to primary TRP and S-TP refers to secondary TRP, respectively. In scenario 1, a single PDCCH is used to schedule a single PDSCH transmission, where separate layers are transmitted from separate TRPs. In scenario 2, each of the multiple PDCCHs is used to schedule a separate PDSCH transmission, where each PDSCH transmission is sent from a separate TRP. Although Figure 2 The example in shows 2 PDSCH transmissions per component carrier in the case of one bandwidth part, and a corresponding maximum number of 2 PDCCHs in a single slot, but other configurations are possible.
[0080] In scenario 1, despite transmitting multiple PDSCH data layers, the complexity of the WTRU blind search for DCI decoding may still be similar to that of legacy systems since the WTRU must decode only one PDCCH. However, scheduling decisions may be centrally coordinated at one gNB, requiring some coordination between multiple TRPs. In addition, a beam link failure at the primary coordinating TRP may affect transmission at all other TRPs since the WTRU may receive control information for all TRPs in the coordination set from one TRP.
[0081] In scenario 2, having multiple PDCCHs can result in more scheduling flexibility at the TRPs. Each PDCCH can carry different scheduling instructions for the WTRU without being affected by non-ideal backhaul. Therefore, less information may need to be exchanged between cooperating TRPs on the backhaul. Moreover, distributed scheduling can be used to provide diversity, since a beam link failure at one TRP may only affect the resources managed by that TRP, and transmissions at other TRPs can continue without interruption. This may be an important factor for ultra-reliable low-latency communication (URLLC) applications. On the other hand, since the WTRU may need to perform blind search / blind decoding on multiple received PDCCHs, the effective size of the search space may increase. Coordination remains an important aspect of operation to prevent conflicts in PDCCH transmissions from multiple TRPs.
[0082] Figure 3 is a diagram showing an asynchronous hybrid automatic repeat request (HARQ) operation in NR, where ACK / NACK transmission is performed after PDSCH decoding. 1Once the WTRU decodes the received DCI, such as DCI format 1_1 or DCI format 1_0, it can determine various downlink scheduling information, including the PDSCH to HARQ timing indicator, i.e., K 1 . K 1 It may be an index to an RRC configuration value that defines the time offset between the reception of a PDSCH transmission and the transmission of a PUCCH (e.g., an ACK / NACK transmission on the PUCCH). Figure 3 As shown, the WTRU may determine that the ACK / NACK transmission will be K after the PDSCH reception. 1 Once the WTRU decodes the PDCCH, the WTRU may determine that the time slot for PDSCH reception is time slot i, and therefore the WTRU may further determine that the time slot for ACK / NACK transmission is time slot (i+K 1 ).
[0083] At the same time, the WTRU can also obtain K after decoding the received DCI. 0 and K 2 . K 0 K is a time domain resource assignment indicator, which indicates the time offset between DCI and PDSCH transmission. 2 is a time domain resource assignment that indicates the time offset between DCI and PUSCH transmissions.
[0084] The following embodiments and examples will describe K in detail. 0 and K 1 possible applications.
[0085] Figure 4 is shown with T d Schematic diagram of an example WTRU processing delay for a given WTRU. In a multi-TRP downlink transmission scenario, for each TRP, the applicable PDSCH to HARQ timing offset (i.e., K 1 ) may be different. For example, TRP may not have the same PDSCH resource allocation within a time slot, so different PDSCH to HARQ timing offsets may be required. Figure 4 As shown, for TRP 1, the PDSCH (i.e., PDSCH reception) is located at the beginning of slot i based on the PDSCH resource allocation from TRP 1. Despite the WTRU processing delay T d, but the WTRU may complete processing of the PDSCH in slot i, and therefore the PUCCH (e.g., ACK / NACK on PUCCH) may be located at the slot immediately after slot i. However, in contrast, the PDSCH for TRP2 (i.e., PDSCH reception) may be located at the end of slot i based on the PDSCH resource allocation from TRP 2, and the WTRU may not receive the PDSCH due to the WTRU processing delay T d The PDSCH is processed at time slot (i+1) in the time domain. Therefore, the PUCCH (e.g., ACK / NACK on the PUCCH) should be located at time slot (i+2). In this case, different PDSCH to HARQ timing offsets (i.e., different K 1 value).
[0086] Figure 5 5 is a flow chart showing a process 500 for multiple TRP transmissions. Figure 5 As shown, the process begins with the WTRU receiving a parameter set and a physical downlink control channel (PDCCH) transmission from each of a plurality of TRPs at 501. Next, at 502, the WTRU decodes each received PDCCH transmission based on each received parameter set to obtain a K1 value for each of the plurality of TRPs. Next, at 503, the WTRU may receive a physical downlink shared channel (PDSCH) transmission from each of the plurality of TRPs. Then, at 504, the WTRU may determine a PDSCH receive slot position for each received PDSCH transmission. At 505, based on each determined PDSCH receive slot position and each obtained K1 value, the WTRU may determine a candidate PUCCH slot position for each of the plurality of TRPs. The WTRU may then determine a selected PUCCH slot position for all multiple TRPs based on a comparison of all determined candidate PUCCH slot positions at 506A, wherein at 506B, if all determined candidate PUCCH slot positions are not the same, the selected PUCCH slot position is the farthest candidate PUCCH slot position; and at 506C, if all determined candidate PUCCH slot positions are the same, the selected PUCCH slot position is any one of the determined candidate PUCCH slot positions. Based on the determination, the WTRU selects a PUCCH resource 507 and transmits on the selected PUCCH resource.
[0087] Corresponds to Figure 5As shown in 501, the WTRU may be configured to receive parameter sets and PDCCH transmissions from each of a plurality of TRPs. In order for the WTRU to decode the PDCCH in order to receive the DCI, it must determine a certain frequency range where the PDCCH may be located. However, this information may not be provided to the WTRU in advance, and the location may change dynamically. The parameter set received from each TRP may contain information about the certain frequency range that may carry the PDCCH. Within this range, the WTRU must attempt to decode the PDCCH by blind decoding or blind search. It will be understood that the PDCCH carries control information for the PDSCH and PUSCH, namely the DCI, and that the DCI is a key part of the PDCCH transmission. Therefore, to some extent, blind decoding the PDCCH means blind decoding the DCI. In order to clearly and unambiguously describe the present application, the terms "PDCCH" and "DCI" may be used interchangeably herein unless otherwise noted.
[0088] In one embodiment, the parameter set received from each TRP of the multiple TRPs may include a control resource set (CORESET). A CORESET is a set of physical resources used to carry a PDCCH (i.e., a specific area on the NR downlink resource grids). In NR, the PDCCH does not span the entire system bandwidth as in LTE, and the starting position of the PDCCH in the time domain is also configurable. The CORESET can be used to locate a specific area in the frequency domain where a PDCCH (e.g., DCI) is located, and can therefore be used to assist in blind decoding.
[0089] There may be multiple sub-parameters within a CORESET, such as frequency domain parameters and time domain parameters. The frequency domain parameters may be used to define the frequency domain width of the CORESET. The time domain parameters may be used to define the time domain length of the CORESET. By using these two sub-parameters, information such as the frequency domain and time domain occupied by the PDCCH (for example, the number of OFDM symbols occupied by the PDCCH) may be configured in the CORESET. Although the frequency domain parameters and the time domain parameters have been described above, they are not exclusive or limiting of the present application. It should be understood that in order to apply the method and apparatus for multi-TRPS transmission disclosed in the present application, different sub-parameters within the CORESET are available.
[0090] In one embodiment, the parameter set received from each TRP of the plurality of TRPs may include a search space. The search space and the CORESET are closely associated with each other. The search space may also refer to an area in a downlink resource grid that may carry a PDCCH. The WTRU may perform blind decoding throughout the search space in order to find PDCCH data (e.g., DCI). Information such as the starting OFDM symbol number and the PDCCH monitoring period may be configured through the search space. Therefore, the WTRU may locate the PDCCH by decoding the information in the search space.
[0091] The above CORESET and search space are two examples of parameter sets that the WTRU can use to locate and blindly decode the PDCCH. However, it will be understood that these examples are not intended to be exclusive or limit the embodiments described herein. Parameter sets other than CORESET and search space are also available as long as the parameter set can be used to locate and / or blindly decode the PDCCH. By using this parameter set, the WTRU can determine a certain frequency range where the PDCCH may be located and enable blind decoding.
[0092] It should be understood that the term "parameter set" here is a collective concept, that is, the parameter set received from each TRP is not limited to only one parameter, such as the above-mentioned CORESET. It can include multiple parameters. For example, the parameter set can include both the CORESET and the search space. .
[0093] The parameter set received from each TRP of the plurality of TRPs may be different. For example, in one embodiment, there are three TRPs, namely a first TRP, a second TRP, and a third TRP. The parameter set received from the first TRP may include a CORESET, the parameter set received from the second TRP may include a search space, and the parameter set received from the third TRP may include both a CORESET and a search space.
[0094] It should be understood that the above-mentioned three different parameter sets from three different TRPs are described only as examples, and they are not intended to exclude or limit the method and apparatus for multi-TRP transmission described in this application.
[0095] In response to Figure 5 As shown in 502, the WTRU is configured to decode each received PDCCH based on each received parameter set to obtain K for each TRP in a plurality of TRPs. 1 value.
[0096] It is understandable that due to K 1 Indicates the time offset between PDSCH reception and ACK / NACK transmission on PUCCH, hence the term “K 1" is meant to be its value. Therefore, for the purpose of clarity and unambiguity of description, the term "K 1 ” and “K 1 "values" have the same or similar meanings and, unless otherwise specified, are interchangeable in this application.
[0097] It should be understood that the slot position is a key aspect of the methods and apparatus for multi-TRPS transmission disclosed in this application, and therefore the term "slot" and other similar terms (e.g., "slot i" and "slot i+2") are used to indicate the position of the slot within a subframe or frame. They are not used to describe those resources or symbols within the slot, such as resource elements or control channel elements within the slot. Therefore, unless otherwise indicated, those terms such as "slot", "slot i" and "slot i+2" mean the slot position corresponding to those slots.
[0098] and Figure 5 Corresponding to 503 shown, the WTRU is configured to receive PDSCH transmissions from each of the multiple TRPs.
[0099] In an embodiment of the present application, there may be more than two TRPs, for example, a primary TRP (P-TRP), a secondary TRP (S-TRP), and a third TRP. Therefore, the WTRU can communicate with the P-TRP, the S-TRP, and the third TRP, and receive PDSCH transmissions from the P-TRP (NR-PDSCH 1), PDSCH transmissions from the S-TRP (NR-PDSCH 2), and PDSCH transmissions from the third TRP (NR-PDSCH 3).
[0100] It should be understood that the above example of the WTRU receiving PDSCH from each of the three TRPs is not exclusive and is not a limitation of the present application. For example, there may be four TRPs with which the WTRU can communicate, so that the WTRU can receive a PDSCH transmission from the first TRP (NR-PDSCH 1), a PDSCH transmission from the second TRP (NR-PDSCH 2), a PDSCH transmission from the third TRP (NR-PDSCH 3), and a PDSCH transmission from the fourth TRP (NR-PDSCH 4).
[0101] Corresponds to Figure 5 As shown at 504, the WTRU is configured to determine a PDSCH reception slot location for each received PDSCH.
[0102] Figure 6 An example of time slots used for DCI and PDSCH transmission is shown. Figure 6As shown, the PDSCH reception time slot position can be determined using the time domain resource allocation for PDSCH (DCI-PDSCH timing) resource allocation in the time domain. For PDSCH, its relative time slot position with DCI is determined by K in DCI. 0 For example, if K 0 =0, PDSCH and PDCCH are in the same time slot; if K 0 =1, the PDSCH follows the PDCCH by one time slot in the time domain; if K0=2, the PDSCH follows the PDCCH by two time slots in the time domain, and so on.
[0103] K 0 Based on the digital configuration of PDSCH. In the downlink, the WTRU is scheduled to receive PDSCH transmissions via DCI, that is, the time domain resource assignment field of the DCI provides a row index of the allocation table, where the row index defines K 0 , start and length indicator SLVIA and PDSCH mapping type. The start symbol (ie, the start of the time slot) and the number of consecutive symbols allocated to the PDSCH, counted from the start symbol, are determined according to the start and length indicator SLIVA. Fig. 7A and 7B As shown, the time slot allocated for PDSCH is defined as [n(2 μPDsCH / 2 μPDCCH )]+K 0 , wherein μPDSCH and μPDCCH are subcarrier spacing configurations for the PDSCH and the PDCCH, respectively.
[0104] Fig. 7A and 7B Two examples of PDSCH reception slot locations are shown. Fig. 7A and 7B As shown, each time slot has 14 symbols (i.e., symbols 0-13). Fig. 7A As shown, K 0 = 0, PDSCH and PDCCH are in the same time slot, i.e., time slot n. Symbols 0 and 1 carry PDCCH, and symbols 2-6 carry PDSCH. Figure 7B As shown, K 0 =1, so PDSCH is in slot n and PDCCH is in slot n+1. Symbols 0 and 1 in slot n carry PDCCH, and symbols 0-4 in slot n+1 carry PDSCH.
[0105] It should be understood that Fig. 7A and 7BThe two examples shown are not exclusive and do not constitute a limitation to the present application. The PDSCH reception time slot position may be based on different K 0 values and other parameters vary.
[0106] It should also be understood that due to K 0 represents the time offset between the reception of PDCCH and PDSCH transmissions, hence the term “K 0 " is meant to be its value. Therefore, for the purpose of clarity and unambiguity of description, the term "K 0 ” and “K 0 "values" may have the same or similar meanings and, unless otherwise specified, are interchangeable herein.
[0107] Although the above embodiments illustrate that the WTRU may first receive a PDCCH transmission and then receive a PDSCH transmission, it should be understood that these embodiments are not exclusive and are not limited to the present application. For example, the TRP may transmit a PDCCH and a PDSCH to the WTRU at the same time, and therefore the WTRU may receive a PDCCH transmission and a PDSCH transmission at the same time. After receiving the PDCCH transmission and the PDSCH transmission, the WTRU will blindly search and decode the PDCCH transmission using a parameter set (e.g., CORESET), and then use the DCI from the decoded PDCCH transmission to decode the PDSCH transmission.
[0108] Corresponds to Figure 5 As shown in 505, the WTRU is configured to receive a PDSCH based on each determined PDSCH reception slot position and each obtained K 1 value, determine the candidate PUCCH time slot position for each TRP of multiple TRPs.
[0109] The WTRU may determine that an ACK / NACK transmission on the PUCCH will be K seconds after receiving the PDSCH transmission. 1 time slots later. For example, if K 1 = 0, then PDSCH transmission and ACK / NACK transmission on PUCCH are in the same time slot; if K 1 =1, then the ACK / NACK transmission on the PUCCH is one time slot later in the time domain after receiving the PDSCH transmission; if K 1 =2, then the ACK / NACK transmission on the PUCCH is two slots later in the time domain after receiving the PDSCH transmission, and so on.
[0110] Figure 8 Two examples of candidate PUCCH transmission slot locations are shown. For these two examples, K 1The value is 2, that is, the ACK / NACK transmission on the PUCCH is two time slots after the reception of the PDSCH transmission. Figure 8 As shown, for TRP 1 (i.e., Figure 2 The main TRP shown) and TRP 2 (i.e., Figure 2 The candidate PUCCH transmission time slot positions of the secondary TRPs shown) are the same, i.e., time slot (i+2), and therefore, the ACK / NACK transmissions for TRP 1 and TRP 2 have the same time slot in the time domain, i.e., time slot (i+2).
[0111] Fig. 9 Two more examples of candidate PUCCH transmission slot locations are shown. As mentioned above, different TRPs can receive different K 1 In both examples, the K values of TRP 1 and TRP 2 are 1 The values are different. Fig. 9 As shown, K for TRP 1 1 The value is 1, which means that the ACK / NACK transmission on the PUCCH for TRP 1 is one slot after the PDSCH, that is, the slot for ACK / NACK transmission is slot (i+1). Therefore, the candidate PUCCH transmission slot position for TRP 1 is slot (i+1). 1 The value is 2, which means that the ACK / NACK transmission on the PUCCH for TRP 2 is two time slots after the received PDSCH transmission, i.e., the time slot for the ACK / NACK transmission is time slot (i+2). Therefore, the candidate PUCCH transmission time slot position for TRP 2 is time slot (i+2). Therefore, in these examples, if the WTRU sends an ACK / NACK transmission for each PDSCH received from TRP 1 and TRP 2, those ACK / NACK transmissions will occur in different time slots in the time domain. The method and apparatus for multi-TRP transmission disclosed in the present application can resolve this time slot difference and use a single time slot (i.e., a single PUCCH resource) for PUCCH transmissions for PDSCH transmissions received from TRP 1 and TRP 2.
[0112] As mentioned above, in some embodiments, there may be more than two TRPs. In those embodiments, the K of each TRP 1 The values can be different from each other. For example, the K of TRP 1 1 The value is 0; K of TRP 2 1 value is 1; and K of TRP 2 1 The value is 2. The following description will refer to Figure 5 , Figure 8 and Fig. 9A more detailed description of the different K values for different TRPs 1 The value and how to determine the desired time slot for PUCCH transmission (e.g., ACK / NACK transmission).
[0113] and Figure 5 Corresponding to 506A shown in FIG, the WTRU is configured to determine the selected PUCCH transmission slot positions for all multiple TRPs based on a comparison of all determined candidate PUCCH slot positions. Figure 5 Corresponding to 506B shown in , if all the determined candidate PUCCH time slot positions are the same, the WTRU may determine that the selected PUCCH time slot position is any one of the determined candidate PUCCH time slot positions. Figure 5 Corresponding to 506C shown in , if all determined candidate PUCCH time slot positions are not the same, the WTRU may determine that the selected PUCCH transmission time slot position is the farthest candidate PUCCH time slot position.
[0114] like Figure 8 As shown, the candidate PUCCH transmission slot position for TRP 1 is slot (i+2), and the candidate PUCCH transmission slot position for TRP 2 is also slot (i+2). Therefore, based on the comparison of these determined candidate PUCCH transmission slot positions (i.e., slot (i+2)), the WTRU may determine that slot (i+2) of TRP 1 or slot (i+2) of TRP 2 is the selected PUCCH slot position. In other words, any one of the determined candidate PUCCH transmission slot positions may be the selected PUCCH transmission slot position.
[0115] Although Figure 8 An example is shown where TRP 1 and TRP 2 share the same candidate PUCCH transmission slot position in the time domain, but this example is not intended to be exclusive or limiting of the present application. For example, in one embodiment, there are three TRPs and all of them may share the same candidate PUCCH transmission slot position in the time domain. In this embodiment, the WTRU may determine any one of the same candidate PUCCH transmission slot positions of those TRPs as the selected PUCCH transmission slot position for all TRPs.
[0116] like Fig. 9As shown, the candidate PUCCH transmission slot position for TRP 1 is slot (i+1), and the candidate PUCCH transmission slot position for TRP 2 is slot (i+2). Slot (i+2) is a slot later than slot (i+1), that is, slot (i+2) is the farthest candidate PUCCH transmission slot position for both TRP 1 and TRP 2. Therefore, the WTRU may determine that slot (i+2) for TRP 2 is the selected PUCCH transmission slot position for PUCCH transmission for both TRP 1 and TRP 2.
[0117] Although Fig. 9 An example is shown where the determined candidate PUCCH transmission slot positions for TRP 1 and TRP 2 are not the same, but this example is not intended to be exclusive or limiting of the present application. For example, in one embodiment, there are three TRPs (i.e., TRP 1, TRP 2, and TRP 3), and the WTRU has determined that the candidate PUCCH transmission slot positions for the three TRPs are not the same. For example, the candidate PUCCH transmission slot position for TRP 1 is slot (i+1), the candidate PUCCH transmission slot position for TRP 2 is slot (i+2), and the candidate PUCCH transmission slot position for TRP 3 is slot (i+3). Then, in this case, the WTRU may determine slot (i+3) for TRP 3 as the selected PUCCH transmission slot position for all three TRPs because slot (i+3) is located at the farthest candidate PUCCH transmission slot position among the three candidate PUCCH transmission slot positions.
[0118] It should be understood that the above-described embodiments of determining the selected PUCCH time slot positions for all three TRPs are not exclusive and do not limit the present method and apparatus disclosed in the present application. It should be understood that the method and apparatus for multi-TRP transmission disclosed herein in the present application can be applied to different scenarios with different numbers of TRPs and / or different candidate PUCCH time slot positions.
[0119] and Figure 5 Corresponding to 507 shown in , the WTRU can be configured to select the PUCCH resources of the TRP in the time slot corresponding to the selected PUCCH transmission time slot position as the selected PUCCH resources for all multiple TRPs.
[0120] In one embodiment, the WTRU may be configured with one or more PUCCH resource sets for multiple TRPs, where each resource set may be associated with one TRP in the multiple TRPs. The WTRU may utilize those resources in the PUCCH resource sets to determine the selected PUCCH resources for multi-TRP PUCCH transmissions. For example, in Fig. 9 In the illustrated embodiment, the WTRU may be configured with two PUCCH resource sets, a first PUCCH resource set for TRP 1 and a second PUCCH resource set for TRP 2, and therefore, in this embodiment, the WTRU may select the PUCCH resources of TRP 2 from the second PUCCH resource set 2 as the selected PUCCH resources for PUCCH transmissions to TRP 1 and TRP 2. In the time domain, the selected PUCCH resources are located within slot (i+2) of TRP 2, which corresponds to the selected PUCCH slot position, i.e., slot (i+2).
[0121] In one embodiment, the WTRU may have a PUCCH resource configuration provided by a higher layer parameter for each of the multiple TRPs. The WTRU may use the PUCCH resource configuration to determine the selected PUCCH resource for the multi-TRP PUCCH transmission. For example, Fig. 9 In the illustrated embodiment, the WTRU may have two PUCCH resource configurations, i.e., a first PUCCH resource configuration for TRP 1 and a second PUCCH resource configuration for TRP 2, and therefore, in this embodiment, the WTRU may select a PUCCH resource based on the second PUCCH resource configuration as the selected PUCCH resource for multi-TRP PUCCH transmission to TRP 1 and TRP 2. In the time domain, the selected PUCCH resource is located in slot (i+2) of TRP 2, which corresponds to the selected PUCCH slot position, i.e., slot (i+2).
[0122] More specifically, to select the selected PUCCH resource, the WTRU may calculate the PUCCH resource index. Fig. 9 In the illustrated embodiment, the WTRU may calculate the PUCCH resource index for TRP 2 in order to select the PUCCH resource for TRP 2 in slot (i+2) as the selected PUCCH resource for PUCCH transmission to TRP 1 and TRP 2. The resource index may be calculated based on the number of CCEs in the CORESET received by TRP 2, the index of the first CCE of the PDCCH received by TRP 2, and the PUCCH resource indicator field in the DCI decoded from the PDCCH.
[0123] It should be understood that the above-mentioned methods of selecting the PUCCH resources of the TRP in the time slot corresponding to the selected PUCCH transmission time slot position as the selected PUCCH resources for multi-TRP PUCCH transmission are described only by way of example. They are not exclusive or limiting to the present application.
[0124] and Figure 5 Corresponding to 508 shown in, the WTRU can be configured to transmit the selected PUCCH transmission to all multiple TRPs by using the selected PUCCH resources.
[0125] A WTRU with multiple PDCCHs scheduling multiple PDSCH transmissions may make PUCCH transmissions for all multiple TRPs in the same time slot. The WTRU may transmit ACK / NACK reports for two PDSCH transmissions to the same TRP. For example, Figure 2 and Fig. 9 In the illustrated embodiment, the WTUR may send ACK / NACK reports for both NR-PDSCH 1 and NR-PDSCH 2, and the ACK / NACK reports will be sent to both the P-TRP (ie, TRP 1) and the S-TRP (ie, TRP 2).
[0126] PUCCH transmission can carry uplink control information (UCI), which includes HARQ-ACK report in response to PDSCH, scheduling request (SR) for requesting resources for uplink data transmission, channel state information (CSI) report for link adaptation and downlink data scheduling. More specifically, the CSI report can include channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), layer indicator (LI) and beam related information.
[0127] like Figure 8 As shown, in the time domain, before selecting the selected PUCCH resource, the WTRU may determine a candidate PUCCH transmission in time slot (i+2) for TRP 1, and the WTRU may determine a candidate PUCCH transmission in time slot (i+2) for TRP 2. The candidate PUCCH transmission in time slot (i+2) for TRP 1 may include a candidate ACK / NACK report for a multi-TRP PUCCH transmission, and the candidate PUCCH transmission in time slot (i+2) for TRP 2 may include another candidate ACK / NACK report for a multi-TRP PUCCH transmission. Figure 8 In the illustrated embodiment, after the WTRU selects the PUCCH resources of TRP 1 in time slot (i+2) as the selected PUCCH resources for all multiple TRPs based on the PUCCH resource set or PUCCH resource configuration of TRP 1, the candidate PUCCH transmission in time slot (i+2) for TRP 1 can become the selected PUCCH transmission for multi-TRP PUCCH transmission, and thus the candidate ACK / NACK in the selected PUCCH becomes the selected ACK / NACK.
[0128] Therefore, if Figure 6 As shown, in the time domain, before selecting the selected PUCCH resource, the PUCCH transmission is a candidate PUCCH transmission and the ACK / NACK is a candidate ACK / NACK, and the K1 value defines the time offset between reception of the PDSCH and the candidate PUCCH transmission (e.g., candidate ACK / NACK).
[0129] In one embodiment, the WTRU is configured to discard candidate ACK / NACK reports in slots that do not correspond to the selected PUCCH slot position.
[0130] exist Figure 8 In the illustrated embodiment, the WTRU has determined that the selected PUCCH transmission time slot position is time slot (i+2) of TRP 1, and therefore, the WTRU can discard the candidate PUCCH transmission (e.g., candidate ACK / NACK) scheduled in time slot (i+2) of TRP 2, and can transmit the selected PUCCH transmission (e.g., selected ACK / NACK) for both TRPs in time slot (i+2) of TRP 1.
[0131] exist Fig. 9 In the illustrated embodiment, the WTRU has determined that the selected PUCCH transmission time slot position is time slot (i+2) of TRP 2, and therefore, the WTRU can discard the candidate PUCCH transmission (e.g., candidate ACK / NACK) scheduled in time slot (i+1) of TRP 1, and can transmit the selected PUCCH transmission (e.g., selected ACK / NACK) for both TRPs in time slot (i+2) of TRP 2.
[0132] In the case where multiple DCIs schedule multiple PDSCH transmissions from multiple TRPs in a serving cell, the WTRU may determine quasi-colocation information for PDCCH reception from multiple TRPs according to one of a number of different methods. For example, the WTRU may implicitly determine the quasi-colocation information using an association between a TRP or a TRP set index and a control resource set index from a set of configured control resource sets and / or a search space index from a set of search spaces configured for PDCCH transmission. Alternatively or additionally, the WTRU may be explicitly provided with an antenna port quasi-colocation mapping from an antenna port quasi-colocation set by a higher layer, the mapping indicating the quasi-colocation information of the DM-RS antenna port for PDCCH reception from the corresponding TRP or TRP set.
[0133] In the case where the WTRU implicitly determines the quasi-colocation information, the WTRU may assume that the lowest indexed TRP or set of TRPs is quasi-colocated with the lowest indexed control resource set (e.g., CORESET-ID) used for PDCCH transmission, and / or may assume that the lowest indexed TRP or set of TRPs is quasi-colocated with the lowest indexed search space (i.e., SearchSpace-ID) used for PDCCH transmission. In the case of multi-beam CORESET operation, the WTRU may assume that the lowest indexed TRP or set of TRPs is quasi-colocated with the lowest indexed OFDM symbol of the control resource set within the timeslot used for PDCCH transmission.
[0134] In the case where the WTRU is explicitly provided with antenna port quasi-co-location mapping, configuration in the radio resource control (RRC) may map the DM-RS antenna ports associated with PDCCH reception from a TRP or a set of TRPs to one or more DL-RS configured by the TCI state. For example, a higher layer parameter TCI-StatesPDCCH may be used, which may contain a single or multiple TCI states for PDCCH reception from multiple TRPs. The WTRU may assume that the DM-RS antenna ports associated with PDCCH reception from the corresponding TRP or a set of TRPs are quasi-co-located (e.g., quasi-co-located in terms of: average gain, quasi-co-location (QCL)-type A attribute, and QCL-type D attribute) with the corresponding synchronization sequence (SS) / physical broadcast channel (PBCH) block identified by the WTRU during the initial access procedure.
[0135] In the case where a single DCI schedules multiple PDSCH transmissions from multiple TRPs in a serving cell, the WTRU may determine quasi-colocation information for PDCCH reception from multiple TRPs according to one of a number of different methods. For example, the WTRU may assume that the DM-RS antenna port associated with the PDCCH reception is quasi-colocated with the lowest indexed TRP or TRP set. For another example, a single DCI may schedule multiple PDSCH transmissions from multiple TRPs in a serving cell, and the DCI may not carry a transmission configuration indication (TCI) field, such as where the PDSCH is scheduled via DCI format 1_0, or where for DCI format 1_1, the WTRU is not configured with a tci-PresentInDCI for the CORESET that schedules the PDSCH. In this scenario, the WTRU may determine quasi-colocation information for PDSCH reception as follows. If the WTRU is scheduled via a codeword, the WTRU may implicitly determine the quasi-colocation information using the association between the TRP or TRP set index and the DM-RS antenna port index among the DM-RS antenna ports assigned for PDSCH transmission. For example, the WTRU may assume that the lowest indexed TRP or TRP set is quasi-colocated with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for PDSCH transmission; or the WTRU may assume that the second lowest indexed TRP or TRP set is quasi-colocated with the second lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for PDSCH transmission. If the WTRU is scheduled with two codewords, the WTRU may implicitly determine the quasi-colocation information using the association between the TRP or TRP set index, the codeword index, the MCS index of the two codewords, and / or the DM-RS antenna port index among the DM-RS antenna ports assigned for each codeword. For example, the WTRU may assume that the lowest indexed TRP or TRP set is quasi-colocated with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for the lowest indexed codeword (e.g., codeword 0). The WTRU may assume that the lowest indexed TRP or TRP set is quasi-co-located with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned to codewords with higher (lower) MCS.
[0136] In an embodiment, the WTRU may be configured to support MTRP reception. The activation of this support may be triggered dynamically, for example by a DCI or MAC CE control element (CE), or it may be triggered semi-statically within a given time period.
[0137] In an embodiment, the WTRU may use a newly defined RNTI (e.g., MTRP-RNTI) for multi-TRP operation to identify multiple DCIs that schedule multiple PDSCHs for transmissions from multiple TRPs. In one example, the MTRP-RNTI may be provided by higher layer signaling and may be scrambled using the cyclic redundancy check (CRC) parity bits of the DCI that schedules multiple PDSCHs for transmissions from multiple TRPs. In another example, the WTRU may implicitly determine operation in MTRP mode by DCI field validation. For example, if the WTRU receives two DCIs with the same format 1_1, the WTRU may use the commonality of certain DCI fields as an indication of MTRP reception, where each received DCI carries scheduling information for the corresponding PDSCH layer. In one example, the WTRU may compare certain fields of multiple DCIs that schedule multiple PDSCHs for transmissions from multiple TRPs. If multi-DCI validation is implemented, the WTRU may regard the information in multiple DCIs as an indication of multi-TRP transmissions. If multiple DCI validation is not implemented, the WTRU may consider the multiple DCIs to be DCIs that have been detected with mismatched CRCs.
[0138] Table 1 below provides an example of how some DCI fields in DCI formats 1_0 and 1_1 can be used as a validation mechanism for multiple TRP transmissions. The WTRU may not expect to receive different TPC commands, PUCCH resource indicators, and PDSCH to HARQ feedback timing indicators for scheduled PUCCHs on multiple PDCCH / DCIs. Therefore, it can be expected that the scheduling of multiple PDSCHs for transmissions from multiple TRPs is the same. However, the WTRU may expect different transmission configuration indications (TCIs) for PDSCH transmissions from multiple TRPs.
[0139] If the WTRU receives multiple PDCCHs scheduling multiple PDSCHs, the WTRU may implicitly determine operation in MTRP mode by the combination of received DCI formats. In an embodiment, the WTRU may determine MTRP operation by detecting reception of DCI formats 1_1 and 1_0, where the first DCI format 1_1 carries all scheduling information for two layers and the second DCI format 1_0 may indicate MTRP transmission. In an embodiment, the WTRU may compare certain fields of the received multiple DCIs to verify operation in MTRP mode.
[0140] Table 1
[0141] DCI Field Verification Standards TPC command for scheduled PUCCH Same for multiple DCIs scheduling multiple TRPs PUCCH resource indicator Same for multiple DCIs scheduling multiple TRPs PDSCH to HARQ feedback timing indicator Same for multiple DCIs scheduling multiple TRPs Transport Configuration Indicator Different for multiple DCIs that schedule multiple TRPs
[0142] For multi-TRP operation, the WTRU may be configured with multiple control resource sets (CORESETs) by higher layers, where each CORESET configuration may include antenna port quasi-colocation from an antenna port quasi-colocation set indicating quasi-colocation information of DM-RS antenna ports used for PDCCH / PDSCH reception from the corresponding TRP. The WTRU may expect that the number of CORESETs configured for multi-TRP operation is less than or equal to the number of configured TRPs.
[0143] When the number of configured CORESETs is equal to the number of configured TRPs, the WTRU may assume that the DM-RS antenna ports associated with PDCCH / PDSCH reception in the CORESETs are quasi-co-located with transmissions from the corresponding TRPs (e.g., quasi-co-located in terms of: average gain, QCL-Type A, and QCL-Type D properties). Fig.10 is a schematic diagram showing an example of CORESET configuration, wherein the number of configured CORESETs is equal to the number of configured TRPs.
[0144] In the case where the number of configured CORESETs is less than the number of configured TRPs, the WTRU may assume that the DM-RS antenna ports associated with PDCCH / PDSCH reception in the CORESETs are quasi-co-located (e.g., quasi-co-located in terms of: average gain, QCL-Type A attributes, and QCL-Type D attributes) with transmissions from multiple TRPs or TRP sets.
[0145] In one embodiment, format 1_0 may be configured with an implicit QCL indication (the QCL of CORSET1 is applied to TRP1, i.e., CORSET1 is applied to TRP1 and CORSET2 is applied to TRP2), and format 1_1 may be configured with an explicit QCL indication (the QCL of each PDSCH indicated in the corresponding TCI).
[0146] One or more transmission configuration indication (TCI) states may be configured or used, where the TCI state may include one or more downlink reference signals (e.g., SS / PBCH blocks, CSI-RS, CSI-RS for tracking) and their associated QCL types (e.g., QCL types A, B, C, D). The TCI state may determine spatial Rx (e.g., QCL type D).
[0147] One or more operating modes may be used based on the number of TRPs associated with a downlink control channel, where the downlink control channel may be a downlink control channel in which the WTRU monitors DCI. Hereinafter, downlink control channel, CORESET, and search space may be used interchangeably.
[0148] In one embodiment, the WTRU may determine the TCI state of the search space based on the operation mode. For example, in a first operation mode, the WTRU may determine the TCI state of the search space based on the TCI state configured for the associated CORESET. In a second operation mode, the WTRU may determine the TCI state for the search space based on the TCI state configured for the search space.
[0149] In one embodiment, if the WTRU is in a first mode of operation, the WTRU may monitor the search space (or attempt to decode one or more PDCCH candidates in the search space) with a first TCI state, and if the WTRU is in a second mode of operation, the WTRU may monitor the search space with a second TCI state. The first TCI state may be a TCI state configured for a CORESET associated with the search space, and the second TCI state may be a TCI state configured for the search space.
[0150] The operating mode can be determined based on the DCI format, where a first DCI format can be used for single TRP operation (e.g., a single TCI state associated with a scheduled PDSCH) and a second DCI format can be used for multi-TRP operation (e.g., more than one TCI state associated with a scheduled PDSCH). Alternatively or additionally, the operating mode can be determined based on the number of DM-RS groups (or DM-RS port groups) used for PDSCH. For example, in a first operating mode, a single DM-RS group (or DM-RS port group) can be used for PDSCH, while in a second operating mode, two DM-RS groups (or DM-RS port groups) can be used for PDSCH. Additionally or alternatively, the operating mode can be determined based on an RNTI scrambled using a CRC of a DCI that can be monitored in a search space.
[0151] The WTRU may monitor the search space (or attempt to decode one or more PDCCH candidates in the search space) with one or more TCI states, where the TCI state may be determined based on the PDCCH candidate index. One or more PDCCH candidates in the same OFDM symbol may be associated with the same TCI state. PDCCH candidates in different OFDM symbols may be associated with different TCI states.
[0152] In another embodiment, the WTRU may be configured with more than one TCI state for search space monitoring. For example, the WTRU may use more than one receive beam simultaneously based on capabilities (e.g., spatial Rx QCL parameters), and one or more TRPs may send PDCCH to the WTRU simultaneously. Which receive beams to use may be indicated to the WTRU. For example, the WTRU may indicate its ability to support simultaneous reception of multiple receive (Rx) beams, where the capability may be indicated as the number of TCI states supported simultaneously. For another example, the WTRU may be configured by the gNB with one or more TCI states for monitoring the search space (e.g., attempting to decode one or more PDCCH candidates in the search space), where the one or more TCI states may be indicated via higher layer signaling (e.g., RRC and / or MAC-CE). In another example, a first TCI state may be used in a first Rx panel at a WTRU receiver to determine the Rx beams in the first panel, and a second TCI state may be used in a second Rx panel at the WTRU receiver to determine the Rx beams in the second panel.
[0153] The number of TCI states used for the search space may be determined based on an operating mode, wherein the operating mode may be based on a traffic type. For example, in a first operating mode (e.g., eMBB), a single TCI state may be used for the search space, while in a second operating mode (e.g., URLLC), multiple TCI states may be used for the search space.
[0154] In an embodiment, beam failure recovery (e.g., link reconfiguration) may be performed, used, or triggered when the beam quality of the associated TCI state is below a threshold, where the threshold may be determined based on the operating mode. The first threshold may be used for a first operating mode (e.g., eMBB), and the second threshold may be used for a second operating mode (e.g., URLLC). Additionally or alternatively, beam failure recovery may be performed, used, or triggered if all TCI states of a search space (or CORESET) fail in a first operating mode (e.g., eMBB), and the beam failure recovery may be performed, used, or triggered if any TCI state of the search space (or CORESET) fails in a second operating mode (e.g., URLCC). A TCI state of a search space may be considered failed if the associated beam quality of that TCI state is below a threshold.
[0155] In one embodiment, the WTRU may be configured with one or more SRS resource sets, each of which may be associated with a TRP. In one embodiment, the association between an SRS resource set and a TRP may be determined by which timing advance group (TAG) is used for the SRS resource set. For example, a first SRS resource set may be associated with a first TAG, and a second SRS resource set may be associated with a second TAG. TA and TAG may be used interchangeably here. When a WTRU is triggered by more than one SRS resource set and the triggered SRS resource sets overlap in time, if all triggered SRS resource sets are in the same TAG, the WTRU may send the triggered SRS resource set. Otherwise, the WTRU may send one or more SRS resource sets in the same TAG and discard the remaining SRS resource sets. Simultaneous transmission of SRS resource sets may be based on WTRU capabilities.
[0156] When the WTRU is triggered by more than one SRS resource set and the triggered SRS resource sets overlap in time, the WTRU may send the triggered SRS resource set if the gap between the timing advance values of the triggered SRS resource sets is within a threshold. The threshold may be determined based on a digital configuration (e.g., subcarrier spacing, CP length, etc.). If the WTRU is triggered by more than one SRS resource set and the triggered SRS resource sets overlap in time, the WTRU may determine which SRS resource sets to send based on the associated panel. For example, if the triggered SRS resource sets are in different panels (e.g., Tx panels at the WTRU), the WTRU may send the triggered SRS resource sets. Otherwise, the WTRU may determine a single SRS resource in each panel.
[0157] Although the features and elements are described above in specific combinations, it will be understood by one of ordinary skill in the art that each feature or element may be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via a wired or wireless connection) and 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, buffer memory, semiconductor memory devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and optical media (e.g., CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, and any host computer.
Claims
1. A method for multi-transmit / receive point (multi-TRP) transmission, include: decoding a first physical downlink control channel (PDCCH) transmission from a first transmit reception point (TRP) to obtain a first parameter set indicating first timing information; decoding a second PDCCH transmission from a second TRP to obtain a second set of parameters indicating second timing information; receiving a first physical downlink shared channel (PDSCH) transmission from the first TRP; receiving a second PDSCH transmission from the second TRP; For each TRP, determining a candidate PUCCH time slot position based on each PDSCH reception time slot position and the first timing information and the second timing information; selecting a PUCCH time slot position for the first and second TRPs based on a comparison of the determined candidate PUCCH time slot positions, wherein the selected PUCCH time slot position is the most recent candidate PUCCH time slot position in time; as well as sending PUCCH transmissions to the first and second TRPs using the selected PUCCH time slot locations, Each of the obtained timing information defines a time offset between each received PDSCH transmission and a corresponding candidate PUCCH time slot position.
2. The method according to claim 1, wherein the selected PUCCH time slot position is any one of the determined candidate PUCCH time slot positions under the condition that all the determined candidate PUCCH time slot positions are the same.
3. The method of claim 1, wherein the PUCCH transmission comprises a selected ACK / NACK report.
4. The method according to claim 1, further comprising: include: Candidate ACK / NACK reports are not sent in slots that do not correspond to the selected PUCCH slot location. 5 . The method according to claim 1 , wherein the first parameter set and the second parameter set each indicate a control resource set (CORESET).
6. The method according to claim 1, further comprising: include: Data other than the ACK / NACK report is sent in a candidate PUCCH slot that does not correspond to the selected PUCCH slot position.
7. A wireless transmit / receive unit (WTRU) configured to perform multiple transmit / receive point (multi-TRP) transmissions, the WTRU include: The receiver is configured as: receiving a first physical downlink shared channel (PDSCH) transmission from a first transmit receive point (TRP); as well as receiving a second PDSCH transmission from a second TRP; A processor configured to: decoding a first physical downlink control channel (PDCCH) transmission from the first TRP to obtain a first set of parameters indicating first timing information; decoding a second PDCCH transmission from the second TRP to obtain a second set of parameters indicating second timing information; For each TRP, determining a candidate PUCCH time slot position based on each PDSCH reception time slot position and the first timing information and the second timing information; as well as selecting a PUCCH time slot position for the first and second TRPs based on a comparison of the determined candidate PUCCH time slot positions, wherein the selected PUCCH time slot position is the most recent candidate PUCCH time slot position in time; as well as a transmitter for sending a PUCCH transmission to the first and second TRPs using the selected PUCCH time slot positions, Each of the obtained timing information defines a time offset between each received PDSCH transmission and a corresponding candidate PUCCH time slot position.
8. The WTRU of claim 7, wherein the selected PUCCH time slot position is any one of the determined candidate PUCCH time slot positions, provided that all determined candidate PUCCH time slot positions are the same.
9. The WTRU of claim 7, wherein the PUCCH transmission includes a selected ACK / NACK report.
10. The WTRU of claim 7, wherein the processor is further configured to not send candidate ACK / NACK reports in slots that do not correspond to the selected PUCCH slot position.
11. The WTRU of claim 7, wherein the first parameter set and the second parameter set each indicate a control resource set (CORESET).
12. The WTRU of claim 7, wherein the processor is further configured to transmit data other than the ACK / NACK report in a candidate PUCCH slot that does not correspond to the selected PUCCH slot position.
