Reliable control signaling

Abstract

Systems, methods and means for reliable control signaling, such as in New Radio (NR) are disclosed. A receiver in a wireless transmit / receive unit (WTRU) may receive one or more physical downlink control channel (PDCCH) transmissions including downlink control information (DCI). The WTRU may determine a transmission profile associated with uplink control information (UCI). Based on the transmission profile, the WTRU may determine one or more transmission characteristics associated with the transmission of the UCI. The WTRU may transmit the UCI on a physical uplink control channel (PUCCH). The UCI may be transmitted using a transmission characteristic determined by the WTRU. The WTRU may transmit the UCI based on at least one of a control resource set (CORESET), a search space, or a radio network temporary identifier (RNTI). The WTRU may determine the transmission profile differently based on what the UCI may include.

Description

[0001] This application is a divisional application of a Chinese invention patent application with a filing date of June 11, 2018, application number 201880050669.8, and title “Reliable Control Signaling”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application Serial No. 62 / 519,585 filed on June 14, 2017, U.S. Provisional Patent Application Serial No. 62 / 585,937 filed on November 14, 2017, U.S. Provisional Patent Application Serial No. 62 / 652,002 filed on April 3, 2018, and U.S. Provisional Patent Application Serial No. 62 / 667,015 filed on May 4, 2018, the contents of which are incorporated herein by reference. Background Art

[0004] Mobile communications using wireless communications continue to develop. The fifth generation or next generation (NG) wireless system may be referred to as 5G or new radio (NR). The previous generation of mobile communications may be, for example, fourth generation (4G) long term evolution (LTE). A set of use cases for NR may generally be classified as one of enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), or massive machine type communications (mMTC). Current processing and transmission mechanisms for such use cases may be inefficient. Summary of the invention

[0005] Systems, methods, and means for reliable control signaling, such as in New Radio (NR) are disclosed. A receiver in a wireless transmit / receive unit (WTRU) may receive one or more physical downlink control channel (PDCCH) transmissions including downlink control information (DCI). The WTRU may determine a transmission profile associated with uplink control information (UCI). The transmission profile may be determined based on one or more of: an identification of a logical channel or logical channel group for data associated with the UCI, and attributes of the at least one PDCCH transmission. The PDCCH transmission may be mapped to one or more resources of a control resource set (CORESET).

[0006] The transmission profile may be determined based on one or more of: one or more DCI fields in the received DCI, or an identification of a bandwidth part (BWP) for transmitting one or more of the DCI or the UCI.

[0007] The DCI may include a first DCI and a second DCI. The DCI field may indicate a hybrid automatic repeat request (HARQ) process index or a logical channel priority. The first DCI may be received using a first control resource set (CORESET), and the second DCI may be received using a second CORESET. The first CORESET or the second CORESET may include one or more of the following: a component carrier, at least one BWP, a subset of resource blocks within each bandwidth part, a set of time symbols within a time slot or mini-time slot, a subcarrier spacing, a subset of time slots within a subframe, or at least one reference signal.

[0008] The UCI may include a first UCI and a second UCI. The first UCI or the second UCI may include one or more of the following: a hybrid automatic repeat request (HARQ), a scheduling request (SR), or a channel quality indicator (CQI). The UCI may be transmitted based on a CORESET, a search space, or an RNTI. The UCI may be associated with a PDSCH transmission or a PDCCH transmission. In an example, the first UCI or the second UCI may include feedback information bits for data transmission allocated by the first DCI or the second DCI. In another example, the second UCI may correspond to a redundant transmission of the first UCI.

[0009] Based on the transmission profile, the WTRU may determine one or more transmission characteristics associated with the UCI transmission. The one or more transmission characteristics may include at least one of: one or more coding parameters, one or more transmission power parameters, one or more resource allocation parameters, or a priority level.

[0010] The WTRU may transmit UCI on a physical uplink control channel (PUCCH). The UCI may be transmitted using a transmission characteristic determined by the WTRU. The WTRU may transmit UCI based on one or more of a CORESET, a search space, or a radio network temporary identifier (RNTI). The PUCCH carrying UCI may be sent on an uplink (UL) carrier and / or a supplementary uplink (SUL) carrier.

[0011] For example, if the UCI includes a hybrid automatic repeat request acknowledgement (HARQ ACK), the WTRU may determine the transmission profile associated with the PDSCH transmission based on one or more of: the duration of the transmission, the bandwidth portion, the parameter configuration, or the modulation and coding scheme (MCS) table for control information.

[0012] For example, if the UCI includes channel state information (CSI), the WTRU may determine the transmission profile based on one or more of: the value of a block error rate (BLER) target associated with the CSI, or the CSI reporting settings.

[0013] For example, if the UCI includes a physical uplink control channel (PUCCH) resource associated with a scheduling request (SR) configured for transmission, the WTRU may determine the transmission profile based on one or more of: subcarrier spacing, duration of the PUCCH resource, a logical channel associated with the SR configuration, and a priority associated with the logical channel. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The present invention can be understood in more detail from the following description given by way of example in conjunction with the accompanying drawings.

[0015] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

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

[0017] Figure 1C It shows that it can be Figure 1A System diagram of an example radio access network (RAN) and an example core network (CN) used within a communication system is shown.

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

[0019] Figure 2 An example of downlink control information (DCI) diversity is shown.

[0020] Figure 3 Examples of DCI and uplink control information (UCI) diversity are shown. DETAILED DESCRIPTION

[0021] A detailed description of illustrative embodiments will now be described with reference to the various drawings. Although this specification provides detailed examples of possible implementations, it should be noted that these details are intended to be exemplary and in no way limit the scope of the present application.

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

[0023] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, however it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, any of the WTRUs 102a, 102b, 102c, 102d may be referred to as a “station” and / or “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 operating in an industrial and / or automated process chain environment), consumer electronic devices, and devices operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

[0024] The communication system 100 may also include a base station 114a and / or a base station 114b. Each base station 114a and / or base station 114b may be any type of device configured to facilitate access to one or more communication networks (e.g., CN 106 / 115, 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 base transceiver stations (BTS), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, and the like. Although each base station 114a, 114b is depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0025] The base station 114a may be part of the RAN 104 / 113, and the RAN may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, 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.

[0026] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0027] More specifically, as described above, the communication system 100 may be a multiple access system and may 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 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

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

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

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access (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).

[0031] 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, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), and GSM EDGE (GERAN), among others.

[0032] Figure 1A The base station 114b in the example can be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and can 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 can 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 can establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In another embodiment, the base station 114b and the WTRUs 102c, 102d can establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). 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 / 115.

[0033] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or may perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113, which may employ NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0034] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. 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 / 113.

[0035] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks 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.

[0036] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a numeric keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other 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.

[0037] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal decoding, 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 into one electronic component or chip.

[0038] The transmit / receive element 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. As an example, in an embodiment, the transmit / receive element 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 element 122 may be configured to transmit and receive RF and light signals. It should be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

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

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

[0041] 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 elements. 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 data 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).

[0042] 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.

[0043] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) 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.

[0044] The processor 118 may be further coupled to other peripherals 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 peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game console module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, and an activity tracker, etc. The peripheral device 138 may include one or more sensors, which 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 posture sensor, a biometric sensor, and / or a humidity sensor.

[0045] The WTRU 102 may include a full-duplex radio in which the reception or transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (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 or receives some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)).

[0046] 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 employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0047] The RAN 104 may include eNode-Bs 160a, 160b, 160c, however it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. Each of the eNode-Bs 160a, 160b, 160c may 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.

[0048] Each eNodeB 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 UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, and 160c may communicate with each other via an X2 interface.

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

[0050] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c 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 also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0051] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during inter-eNode-B handovers, 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.

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

[0053] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or 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 or wireless networks owned and / or operated by other service providers.

[0054] Although in Figures 1A-1D The WTRU is described as a wireless terminal, however 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.

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

[0056] 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 services into and / or out of the BSS. Services originating from outside the BSS and destined for the STA may be reached by the AP and delivered to the STA. Services originating from the STA and destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Services between STAs within the BSS may be sent by the AP, for example, when the source STA may send services to the AP and the AP may deliver services to the destination STA. Services between STAs within the BSS may be considered and / or referred to as point-to-point services. The point-to-point services may be sent using a direct link establishment (DLS) between the source and destination STAs (e.g., directly therebetween). In certain typical embodiments, the DLS may use 802.11eDLS or 802.11z tunneled DLS (TDLS)). 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.

[0057] 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 width that is dynamically set with the aid of signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain typical embodiments, carrier sense multiple access with collision avoidance (CSMA / CA) (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 given BSS, there is one STA (e.g., only one station) transmitting at any given time.

[0058] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, by combining a 20 MHz wide primary channel with an adjacent or non-adjacent 20 MHz wide channel to form the 40 MHz wide channel.

[0059] 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. 160MHz channels can be formed by combining 8 continuous 20MHz channels or by combining two discontinuous 80MHz channels (this combination can be referred to as 80+80 configuration). For the 80+80 configuration, after channel coding, the data can be transmitted and passed through a segment parser, which can divide 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 transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0060] 802.11af and 802.11ah support sub-1 GHz operating modes. The channel operating bandwidths and carriers used in 802.11af and 802.11ah are reduced compared to 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to typical embodiments, 802.11ah may support meter type control / machine type communications (e.g., MTC devices in macro coverage areas). MTC devices may have certain capabilities, such as limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices may include a battery, and the battery life of the battery is above a threshold (e.g., for maintaining a very long battery life).

[0061] 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, wherein the STA originates from all STAs operating in the BSS and 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 state 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 even if most of the band remains idle and available for use, the entire available band can be considered busy.

[0062] 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.

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

[0064] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. Each of the gNBs 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, 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 the WTRU 102a, 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).

[0065] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with the scalable parameter configurations. 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).

[0066] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without 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.

[0067] Each gNB 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, implement dual connectivity, 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, and the like. Figure 1D As shown, gNBs 180a, 180b, and 180c can communicate with each other through the Xn interface.

[0068] Figure 1DThe illustrated CN 115 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 each of the aforementioned elements is described as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by entities other than the CN operator.

[0069] The AMF 182a, 182b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 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 WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, and mobility management, etc. The AMF 182a, 182b may use network slicing processing to customize the CN support provided to the WTRU 102a, 102b, 102c based on the type of service used by the WTRU 102a, 102b, 102c. As an example, different network slices may be established for different use cases, such as services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, and / or services for machine type communication (MTC) access, etc. The AMF 162 may provide control plane functionality for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0070] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and may configure service 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 downlink data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0071] The UPF 184a, 184b can be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 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 downlink packets, and providing mobility anchor processing, etc.

[0072] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the 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.

[0073] 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 185 ab, and / or one or more other devices described herein. A simulation device may be one or more devices configured to simulate one or more or all of the functions described herein. For example, a simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0074] The simulation device can be designed to implement one or more tests 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 a 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 or deployed as a 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.

[0075] One or more simulation devices can perform one or more functions, including all functions, while not being implemented or 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 (as an example, the circuits can include one or more antennas).

[0076] New Radio (NR) can operate with current and future mobile wireless communication systems. NR use cases may include, for example, eMBB, ultra-reliable low latency communications (URLLC), and massive machine type communications (mMTC). NR may support transmission in high frequency bands, such as centimeter wave (cm-wave) and / or millimeter wave (mm-wave) frequencies. Operation within cm-wave and / or mm-wave frequency bands may present challenges related to propagation, for example, in view of higher path loss and shadowing.

[0077] For example, high reliability services may be supported with very low block error rates, e.g., on the order of 0.001%. Lower error rates may be achieved, for example, by utilizing higher reliability of physical layer control information (e.g., hybrid automatic request acknowledgement (HARQ-ACK), uplink grants, and downlink assignments). In an example (e.g., for HARQ-ACK), the probability of misinterpreting a NACK as an ACK is at the level of 0.1%, which may be sufficient for some (e.g., general) mobile broadband services, but may be too large for, e.g., ultra-reliable services (e.g., because the event of a negative acknowledgement (NACK) being misinterpreted as an acknowledgement (ACK) may result in the loss of a transport block).

[0078] The WTRU may be configured for multiple simultaneous transmissions. NR may support WTRU configurations that may include one or more cells for a given MAC entity and / or for multiple MAC entities. The configuration of one unit may provide single unit operation. The configuration of multiple cells may provide carrier aggregation (CA), such as NR CA operation. The configuration of multiple MAC entities may include NR dual connectivity (NRDC). The configuration of multiple MAC entities may provide a combination of LTE and NR (e.g., Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) New Radio Dual Connectivity (EN-DC)). NR may provide a WTRU configuration that includes a cell configured with one downlink carrier, one uplink carrier, and a secondary uplink carrier (SUL). NR may support cells configured with one or more bandwidth parts (BWP). The BWP may be characterized by at least one of a frequency location (e.g., center frequency and / or frequency bandwidth) or a parameter configuration.

[0079] For EN-DC, NR CA, and NR DC in the licensed band, various combinations of carriers (e.g., different combinations) may introduce various timing relationships (e.g., different timing relationships) between transmissions associated with the WTRU (or between transmissions that overlap at least partially in time) in terms of one or more of parameter configuration, transmission start time, or transmission duration. For example, each configured component carrier (downlink (DL) and / or uplink (UL)) and / or bandwidth part (BWP) (DL and / or UL) for the WTRU may have the same or different parameter configurations, and overlapping transmissions between different component carriers / BWPs may have the same or different start times; and the same or different physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission durations.

[0080] For example, timing and / or scheduling aspects may be provided in the case of asynchronous transmissions and / or in the case of partial and / or complete overlap between different uplink transmissions associated with the WTRU. In an example, different transmissions may operate with different HARQ timelines, for example based on dynamic scheduling information. For example, such scheduling information may include a dynamically variable scheduling-related delay component. The dynamically variable scheduling-related delay component may be provided via downlink control information (DCI). The scheduling-related delay component may include one or more of K1, K2, N1, or N2. K1 may be a delay between downlink (DL) data (PDSCH) reception and its corresponding ACK transmission on the uplink (UL). K2 may be a delay between UL grant reception in the DL and UL data transmission (e.g., PUSCH transmission). For example, from the perspective of the WTRU, N1 may be the number of OFDM symbols used for WTRU processing, which is the earliest possible start of the corresponding ACK / NACK transmission from the end of NR-PDSCH reception. For example, from the WTRU perspective, N2 may be the number of OFDM symbols used for WTRU processing from the end of the NR-PDCCH including the UL grant reception to the earliest possible start of the corresponding NR-PUSCH transmission.

[0081] The scheduler may adjust the error probability of the control information, for example, by selecting a transmission power parameter (eg, associated with uplink transmissions) and / or an aggregation level (eg, associated with downlink transmissions).Achieving very low error rates may be problematic.

[0082] In an example, very low error rates may not be achieved by using parameter adjustments of the transmission technology, such as in the presence of bursty interference and / or other channel impairments (eg, severe shadowing at mm-wave frequencies).

[0083] Spectral efficiency and user throughput may be severely degraded, for example, when operating at very low error rates, because when such techniques are applied to one or more types of transmissions, significantly more resources (time, frequency, and / or power) may be consumed than when operating at typical error rates. For example, given that ultra-reliable traffic may be bursty, differentiating between ultra-reliable transmissions and other transmissions (e.g., through resource isolation) may be inefficient.

[0084] Very low error rates may be achieved (eg, for ultra-reliable services). Efficient operation (eg, in a system and / or WTRU) with ultra-reliable and other (eg, non-ultra-reliable) mobile broadband data services may be achieved.

[0085] Uplink control information (UCI) may include, for example, HARQ feedback information (e.g., HARQ-ACK), scheduling request (SR), and / or channel state information (CSI). UCI may be transmitted on an uplink control channel (e.g., physical uplink control channel (PUCCH)) and / or on an uplink data channel (e.g., physical uplink shared channel (PUSCH)). UCI may be transmitted multiplexed or non-multiplexed with uplink data. HARQ feedback information (e.g., HARQ-ACK) may be related to one or more transport blocks, one or more code blocks, and / or one or more code block groups.

[0086] Downlink Control Information (DCI) may refer to physical control signaling (e.g., uplink grants, downlink assignments, power control commands, slot format indicators, HARQ information, etc.) that may be received from the network. The DCI may be transmitted, for example, over a downlink control channel (e.g., PDCCH), for example, in a common search space or a WTRU-specific search space or over a group common control channel (e.g., on the PDCCH). The PDCCH may be mapped to resources of a control resource set (CORESET). The WTRU may attempt to decode a PDCCH, for example, from one or more search spaces within a CORESET. The WTRU may be configured, for example, with at least one CORESET.

[0087] DCI diversity may be provided. In an example, for example, by transmitting multiple DCI instances on resources separated in time, frequency, and / or spatial domains, the transmission reliability of the DCI may be improved. Multiple instances may provide diversity gain against short-term fading, long-term fading, and / or interference.

[0088] DCI (e.g., each DCI instance) may be sent over a downlink physical control channel (e.g., PDCCH, group common PDCCH, PHICH, etc.). Instances may be sent over PDSCH (e.g., when DCI on PDSCH may be supported). PDCCH (e.g., each PDCCH) may be received based on a CORESET configured by a higher layer. The configuration may include one or more parameters. For example, the configuration may include a component carrier or serving cell, one or more bandwidth parts (BWPs), a subset of resource blocks within a BWP (e.g., each BWP), a set of time symbols within a slot or mini-slot, a subcarrier spacing, a subset of slots within a subframe, and / or one or more reference signals (e.g., CSI-RS). Independent configuration of one or more parameters may provide time, frequency, and / or space diversity. In an example, frequency diversity (e.g., by configuring different component carriers or BWPs between CORESETs) may be provided with or without providing space and / or time diversity (e.g., by configuring different sets of time symbols and / or different sets of reference signals).

[0089] DCI diversity is configurable. For example, DCI diversity may be activated or deactivated. The activation or deactivation of DCI diversity may be based on MAC layer signaling or physical layer signaling, for example. In an example, the WTRU may receive an activation command based on a first CORESET to initiate monitoring of a second DCI instance on a second CORESET. The WTRU may receive a deactivation command for monitoring a DCI instance on a specific CORESET.

[0090] DCI diversity may be applied. The content of a DCI instance (e.g., each DCI instance) may be set based on one or more of: (i) the same content transmitted on multiple DCI instances (e.g., repetition); (ii) the same content transmitted via multiple DCI instances (e.g., block coding), or (iii) the nature of the content.

[0091] In an example, each of the multiple DCI instances may include and encode the same information bits for at least one type or format of DCI (e.g., HARQ-ACK for PUSCH, PDSCH assignment, PUSCH grant). The DCI may be decoded (e.g., fully decoded) from receipt of an instance (e.g., a single instance).

[0092] In an example, the DCI may be encoded, for example, by segmenting the DCI into N blocks and encoding the DCI into D blocks. In an example, decoding at least N of the D DCI instances (e.g., at a receiver) may be sufficient to recover the entirety of the DCI. In an example, the encoding may consist of a parity check code.

[0093] In an example, the DCI instance may include one or more of: information associated with at least one DL data transmission on the PDSCH, or information associated with at least one UL data transmission on the PUSCH.

[0094] In an example, the WTRU may be configured to monitor the PDCCH on multiple CORESETs (e.g., two CORESETs). The WTRU may monitor the PDCCH on different carriers or bandwidth portions. The WTRU may receive, for example, multiple DCI instances (e.g., up to two DCI instances). In an example, the DCI instance may include the same information received by the WTRU via the PDCCH in multiple carriers (e.g., in the case of multiple DCIs, each carrier may be received on a carrier). Information about the DCI (e.g., each DCI) may include PDSCH (or PUSCH) allocations / grants for multiple carriers (e.g., two carriers). For example, the WTRU may receive PDSCH or transmit PUSCH on multiple carriers (e.g., two carriers) even in the case where an instance (e.g., one) in the DCI instance may not be successfully decoded. For example, when multiple PSDCH transmissions (e.g., two PDSCH transmissions) or PUSCH transmissions may be encoded into the same transport block, for example, because the DCI and data may be (e.g., be) independently protected by diversity, such as Figure 2 As shown in the example in , very low BLER can be achieved with low latency. Figure 2 As shown, the DCI on downlink component carrier 1 (DL CC1) 202 and the DCI on downlink component carrier 2 (DL CC2) 204 may have the same content. For example, each of the DCIs may include information associated with PDSCH 206 and PSDCH 208.

[0095] A DCI index may be provided. In an example, a DCI instance (e.g., each DCI instance) may include a field (e.g., a DCI index) that may identify the DCI content. The WTRU may discard DCI instances that may include the same information. Duplicate DCIs may be discarded to reduce processing. In an example, the WTRU may receive a first DCI instance with a first value of a DCI index. The WTRU may receive a subsequent DCI instance that may include the same DCI index value (e.g., within a group of CORESETs on which DCI diversity may be configured within a time period). The WTRU may discard subsequent DCI instances (e.g., upon reception). The WTRU may use the DCI index, for example, to distinguish between diversity DCI and DCI that may include new information.

[0096] UCI diversity may be provided. For example, transmission reliability of UCI may be increased by transmitting multiple instances on resources, where the resources may be separated in one or more of: time domain, frequency domain, or spatial domain. Multiple UCI instances may, for example, provide diversity gain for short-term fading, long-term fading, and / or interference. UCI instances (e.g., each UCI instance) may be transmitted via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). In an example, UCI diversity may be applicable to certain types of UCI (e.g., HARQ-ACK).

[0097] In an example, the UCI instance may be transmitted on multiple carriers and / or bandwidth portions on which the WTRU may be configured to operate. Figure 3 As shown in FIG. 1 , the same HARQ-ACK information related to a downlink assignment (e.g., received in a previous time slot 302) may be transmitted on multiple PUCCH instances (e.g., two PUCCH instances 306 and 308). The two PUCCH instances may include a first UCI instance 306 that may be transmitted on UL component carrier one (CC1) 310 and a second UCI instance 308 that may be transmitted on UL component carrier two (CC2) 312. The UCI may be sent in time slot 2 304. Each of the first UCI instance 306 and the second UCI instance 308 may include similar information (e.g., the same HARQ ACK-NACK information).

[0098] Figure 3 is an example of implementing DCI diversity and UCI diversity. In an example, a UCI instance (e.g., each UCI instance) may include transmissions of OFDM symbols (e.g., a single OFDM symbol) in adjacent symbols (e.g., using a short PUCCH format). Other examples in the time domain may include, for example, transmissions in the same OFDM symbol or transmissions in different time slots. The resources (e.g., RBs, time symbols, time slots, etc.) that may be occupied by a UCI instance (e.g., each UCI instance) may be independently configured.

[0099] In an example, a UCI instance may be sent via multiple beams. For example, multiple beams may be sent using different precoders. The WTRU may be configured for beam determination associated with a UCI instance (e.g., each UCI instance). The WTRU may be configured to include information of one or more of the following: a beam index, a beam processing identifier, an SRS indicator, or a CSI-RS indicator (e.g., when there is a beam correspondence), etc. The information used by the WTRU for beam determination (e.g., for PUCCH) may be configured by a higher layer for a UCI instance (e.g., for each UCI instance), or may be indicated in a DCI that may include an ACK / NACK resource indicator (ARI). The information used by the WTRU for beam determination (e.g., for PUSCH) may be indicated via a DCI that may include a grant associated with the beam.

[0100] The information that the WTRU uses for beam determination may be derived (e.g., implicitly derived) from a PDCCH, which may include an allocation. In an example, the beam associated with a transmission of a PUCCH instance may be derived from a reference signal (e.g., a channel state information reference signal (CSI-RS)) or a beam indicator, where the beam indicator may be associated with a control resource set or a PDCCH transmission that may include an allocation. For example, this method may be used when PDCCH diversity (or DCI diversity) may be used in addition to UCI diversity. The WTRU may transmit a PUCCH instance (e.g., one PUCCH instance) for a received PDCCH instance (e.g., for each received PDCCH instance). The PDCCH instance may include allocations, for example, when and / or how to send UCI over the PUCCH.

[0101] A supplementary uplink (SUL) may be provided. In an example, the WTRU may be configured with a SUL carrier for at least one serving cell. The WTRU may be configured to transmit UCI including, for example, a scheduling request (SR), channel state information (CSI), or HARQ ACK / NACK. The UCI may be transmitted on a regular UL carrier and a SUL carrier associated with a serving cell.

[0102] UCI diversity may be applied. The content of a UCI instance (e.g., each UCI instance) may be set, for example, based on one or more of the following: (i) whether the same content is to be sent on each of the multiple UCI instances (e.g., repetition); (ii) whether the same content is to be sent across the UCI instance (e.g., block coding); or (iii) the nature of the content.

[0103] In an example, a UCI instance (e.g., each UCI instance) may include and encode the same information bits for at least one type of UCI (e.g., HARQ-ACK). The UCI may be decoded from the reception of a single instance. In an example, for example, the UCI may be encoded by segmenting the UCI into N blocks and encoding the segmented N blocks into D blocks. In an example, decoding at least N blocks of the D UCI instances at the receiver may be sufficient to recover the entirety of the UCI. In an example, the encoding may include a parity check code.

[0104] In an example (eg, where DCI diversity may not be applied), the UCI may include a set of HARQ-ACK bits. For example, the association between a specific HARQ-ACK bit and the reception result of a transport block may be determined based on a downlink allocation index.

[0105] In an example (e.g., where DCI diversity may be applied), for example, a set of HARQ-ACK bits may be generated and transmitted for each DCI instance that may be configured to be received in a diversity manner (e.g., based on the same content). This may occur, for example, regardless of whether the DCI instance may be successfully decoded. For example, when the WTRU may be configured to receive multiple DCI instances (e.g., two DCI instances) in a diversity manner but receives less than the configured DCI instances (e.g., the configured two DCI instances), the WTRU may report a NACK for a transport block corresponding to the DCI instance that may not have been received. For example, when the WTRU receives at least one DCI instance, reporting may be performed. The network may be allowed to determine lost allocations from a DCI instance (e.g., each DCI instance). Determining lost allocations is beneficial for link adaptation of the PDCCH.

[0106] In an example, DCI diversity may be applied. For example, when the WTRU receives at least one DCI instance, the WTRU may report a set of HARQ-ACK bits for a set of DCI instances that may be configured to be received in a diversity manner. The WTRU may report an indication of a subset of DCI instances that may be successfully decoded in the set of DCI instances in a diversity manner.

[0107] The WTRU may receive more than one DCI that may indicate DL data for the same HARQ process and one or more transport blocks. The DCI may be encoded using different redundancy versions. The WTRU may report one HARQ-ACK bit per transport block (e.g., regardless of the number of received instances of PDSCH that may include data for the transport block). The WTRU may transmit a HARQ-ACK bit for each transport block and a PDSCH instance that may include data for the transport block (e.g., with the same value).

[0108] Power control with UCI diversity may be provided. For example, when UCI diversity is applied, the transmit power associated with a transmission (e.g., a PUCCH transmission or a PUSCH transmission) may be set independently. For example, separate configurations of one or more reference signals may be used for path loss estimation, and other parameters may be used to determine the transmit power.

[0109] Power control utilizing UCI diversity may be provided to determine transmit power control (TPC). The WTRU may determine a TPC command applicable to a transmission for which UCI diversity is applicable.

[0110] In an exemplary determination of TPC, the WTRU may apply a similar TPC adjustment to each of multiple UCI instance transmissions. For example, the TPC adjustment may be received from a DCI that may be associated with the UCI transmission. For example, the DCI may include a DL allocation or a CSI request.

[0111] In an exemplary determination of TPC, the WTRU may apply a separate TPC adjustment to each of the multiple UCI instance transmissions. For example, the TPC adjustment (e.g., each TPC adjustment) may be received via a DCI that may be associated with the UCI transmission. In an example, for example, when two transmissions may be used to configure UCI diversity, the associated DCI may include two TPC adjustment values.

[0112] In an exemplary determination of TPC, the WTRU may apply a separate TPC adjustment to each of the UCI instance transmissions. For example, a TPC adjustment for each UCI instance may be received via a specific DCI instance that may be associated with the UCI instance.

[0113] Power control with a power control mode, for example, for carrier aggregation (CA) and / or dual connectivity (DC) may be provided. In an example, for example, when UCI diversity is activated, the WTRU may apply a priority level to a transmission that may include UCI. For example, if the WTRU is configured with a power control mode (PCM), the WTRU may apply a priority level. The WTRU may be configured to group one or more transmissions of one or more types. The WTRU may be configured to allocate at least a certain amount (e.g., a fraction) of the total WTRU available power to, for example, a transmission group with a minimum guaranteed power. The WTRU may determine that the transmissions including the UCI are part of the same transmission group. For example, if the UCI is associated with a transmission profile, the WTRU may perform such grouping. For example, such a transmission profile may correspond to an ultra-reliable low latency communication (URLLC) type of transmission. The WTRU may assign a higher priority to this group of transmissions than other data transmissions (e.g., data transmissions associated with a transmission profile corresponding to a non-URLLC transmission type). For example, in a WTRU configured with CA, for a given MAC instance, a transmission including at least some UCI generated when UCI diversity is applied may have the highest priority compared to other transmissions. For a WTRU configured with DC and / or having multiple transmission groups, for example, a transmission group (or cell group) having at least one transmission including at least some UCI (e.g., generated when UCI diversity is applied) may have the highest priority compared to one or more other groups.

[0114] PUCCH may be used to provide UCI diversity for resource allocation. For example, according to one or more example procedures, the resources and format of PUCCH transmissions (e.g., when a UCI instance is sent via PUCCH) may be determined. In an example, a WTRU may be configured with one or more combinations of PUCCH resources. A PUCCH resource (e.g., each PUCCH resource) may correspond to a resource over which a UCI instance may be transmitted. In an example (e.g., with two UCI instances), a combination may be defined as PUCCH resource index #24 on a first CC or bandwidth portion and PUCCH resource index #13 on a second CC or bandwidth portion. A combination may be referred to as a PUCCH diversity resource or a PUCCH diversity super resource. A WTRU may be configured (e.g., by a higher layer) with more than one PUCCH diversity resource. A PUCCH diversity resource may be indicated in a field (e.g., an ARI field) of an associated DCI. A WTRU may be configured (e.g., by a higher layer) with a pool. The pool may include normal PUCCH resources and PUCCH diversity resources, which may allow the network to control (e.g., dynamically control) the use of UCI diversity.

[0115] In an example, in addition to UCI diversity, the WTRU may also be configured with DCI diversity. The WTRU may transmit a UCI instance on resources indicated by the associated DCI instance. A DCI instance (e.g., each DCI instance) may include an ARI that may indicate a PUCCH resource. For example, the WTRU may transmit a UCI instance when the WTRU may have received a corresponding DCI instance.

[0116] A transmission of DTX feedback may be provided. In an example, the WTRU may transmit HARQ-ACK information in a specific PUCCH resource. The HARQ-ACK may indicate (e.g., explicitly indicate) that no DL transmission or DL ​​allocation was received from a specific CORESET in a given timeslot or mini-slot (e.g., in the case of discontinuous transmission (DTX)). The timing of the PUCCH resources may be obtained, for example, from the timing of the timeslots or mini-slots for which no DL allocation was received.

[0117] PUCCH interference randomization may be provided. In an example, PUCCH transmissions from two or more WTRUs to two or more transmit / receive points (TRPs) may collide. Interference randomization may be used, for example, to reduce the impact of strong interfering PUCCH transmissions on victim PUCCH transmissions. Interference randomization may be used, for example, by a pair of WTRUs to not use colliding PUCCH resources.

[0118] Interference randomization may be utilized to increase transmit diversity. Interference randomization may include, for example, one or more of the following hopping resources: hopping a transmission beam or beam pair, hopping PUCCH symbols within or across slots, or hopping a replication pattern.

[0119] In the example of frequency hopping resources, frequency hopping may be performed within a BWP or between multiple BWPs. A PUCCH transmission (eg, each PUCCH transmission) may, for example, cycle over a pattern of frequency resources. In an example, frequency hopping may be performed within a PUCCH transmission.

[0120] In examples where frequency hopping is performed on a transmission beam or beam pair, the PUCCH transmission may cycle between a set of beams. In examples, cycling between beams may be performed, for example, using a beam per set of PUCCH symbols within a PUCCH transmission. In examples where frequency hopping is performed on PUCCH symbols within or across slots, for each of multiple PUCCH transmissions, a short PUCCH may occupy a different symbol of the slot.

[0121] In an example where a replication pattern is frequency hopped, a PUCCH transmission (e.g., each PUCCH transmission) may use multiple replications. Each replication may use different resources. Subsequent PUCCH transmissions (e.g., each subsequent PUCCH transmission) may use different resource sets (e.g., distinct sets). Different resource sets may be used to implement multiple replications.

[0122] The use of interference randomization and / or frequency hopping patterns may be indicated to the WTRU. For example, such use of interference randomization and / or frequency hopping patterns may be dynamically indicated to the WTRU. For example, the frequency hopping pattern may be determined based on properties of a PUCCH transmission. In an example, the frequency hopping PUCCH configuration may depend on the frame timing, subframe timing, or time slot timing of the PUCCH. In an example, the PUCCH configuration may depend on the PUCCH configuration used for a previous PUCCH transmission. In an example, the frequency hopping PUCCH configuration may depend on a WTRU parameter (e.g., WTRU ID) or a TRP parameter (e.g., TRP ID).

[0123] Configuration of PUCCH resources may be provided. The WTRU may be configured to use one or more PUCCH formats or format types (e.g., short PUCCH or long PUCCH). The WTRU may be configured with parameters associated with one or more PUCCH formats. Configuration of PUCCH resources may be provided, for example, semi-statically.

[0124] The configuration of PUCCH resources may include, for example, one or more of the following: (i) PUCCH format (e.g., short PUCCH format or long PUCCH format); (ii) PUCCH duration in a symbol (e.g., 1 or 2 symbols for short PUCCH and long PUCCH duration); (iii) waveform used for PUCCH transmission (e.g., cyclic prefix-based orthogonal frequency division multiplexing (CP-OFDM) or discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-s-OFDM)); (iv) parameter configuration for PUCCH (e.g., subcarrier spacing, CP type, etc.); (v) time position (e.g., symbol position within a time slot where PUCCH can be transmitted); (vi) frequency position (e.g., (e.g., subcarrier, PRB, bandwidth part (BWP)); (vii) frequency interleave index (e.g., for FDM of multiple PUCCHs on the same PRB or BWP, where a PUCCH transmission can be assigned to one or more interlaces within a PRB or BWP); (viii) one or more frequency hopping patterns (e.g., for frequency hopping within a PUCCH transmission or frequency hopping between PUCCH transmissions); (ix) beams or beam pairs; (x) replication pattern (e.g., for PUCCH transmissions that can be replicated across multiple resources); (xi) orthogonal cover code (OCC) (e.g., can include whether the OCC is applied over time or over subcarrier elements); (xii) cyclic shift; or (xiii) a transmit diversity scheme.

[0125] The frequency position may include, for example, a frequency allocation at which a PUCCH may be transmitted. The frequency position may be provided, for example, as an offset value. The offset may be applied to, for example, a PDCCH to which a PUCCH may be configured, or a PDCCH to which a PDSCH is allocated, or a frequency position of a PDSCH. The offset may be applied to the frequency position of a concurrent PUSCH. The frequency position may include, for example, a subcarrier set, a PRB, and / or a BWP. A set may be used to indicate (e.g., dynamically indicate) the frequency position of a PUCCH transmission instance (e.g., each PUCCH transmission instance). For example, a set may be used to achieve frequency diversity by repetition. For example, a set may be used to achieve frequency hopping.

[0126] A configuration (eg, including a replication pattern) may include a set of resources on which a PUCCH transmission may be replicated. Different replication patterns may be selected (eg, dynamically selected).

[0127] The semi-static configuration may include one or more tables. A table may include a set of code points and a set of PUCCH configurations that may be bound to each code point in the set of code points. In an example, a first table may include a configuration for short PUCCH transmissions and a second table may include a configuration for long PUCCH transmissions. In an example, a table may be applicable to multiple PUCCH durations and PUCCH formats.

[0128] A dynamic indication of a PUCCH configuration may be provided. In an example, an indication (e.g., a dynamic indication) may be provided (e.g., to a WTRU) indicating a combination of PUCCH configurations for transmitting UCI (e.g., HARQ A / N or CSI). The dynamic indication may include, for example, a table index and a codepoint index to be used in the table. In an example, a dynamic indication may be provided (e.g., implicitly). For example, the dynamic indication may be provided based on a transmission (e.g., based on a parameter of a PDCCH transmission or a PDSCH transmission). In an example, a hybrid process may be used. The WTRU may determine the PUCCH configuration, for example, based on a combination of an explicit index and an implicit relationship. In an example, the WTRU may dynamically determine the PUCCH configuration. In an example, the WTRU may determine a first set of configurations or a PUCCH configuration table, and may determine a codepoint in a second set of configurations or a table. For example, the PUCCH configuration table may be implicitly determined, and the second set of configurations or codepoints may be explicitly determined.

[0129] The implicit indication may include one or more of: slot size, (ii) UL / DL configuration of the slot, (iii) service type, (iv) UCI ​​multiplexing, (v) feedback timing, (vi) feedback type, or (vii) conflict of different feedback types. In the example of slot size, a mini slot may indicate the use of a short PUCCH, or a regular slot may indicate the use of a long PUCCH. In the example of UL / DL configuration of the slot, the WTRU may determine the PUCCH type (e.g., short or long) or the long PUCCH duration, for example, based on the number of symbols allocated for UL transmission. In the example of service type, URLLC may involve a PUCCH format for HARQ, which may achieve higher reliability. In the example, URLLC transmissions may require PUCCH diversity. In the example of UCI multiplexing, transmissions of HARQ bound to multiple TBs (e.g., due to multiple carriers or slot aggregation) may have a higher payload PUCCH format. In the example of feedback timing, feedback timing using an offset less than a threshold may use a first PUCCH table, while feedback timing using an offset greater than the threshold may use a second PUCCH table. In an example, short PUCCH can be used for self-contained time slots, for example, where feedback can be provided in the same time slot as DL data. In an example of feedback type, HARQ feedback can use a first PUCCH configuration, while CSI can use a second PUCCH configuration. In an example, HARQ feedback based on a transport block (TB) can use a first PUCCH configuration (e.g., short PUCCH), and HARQ feedback based on a code block group (CBG) can use a second PUCCH configuration. In an example of a conflict between different feedback types (e.g., associated with different service types), a PUCCH configuration for a service type with a higher priority can be used. In an example, for example, when eMBB HARQ feedback may conflict with URLLC HARQ feedback, feedback multiplexing can be used in the PUCCH configuration for URLLC services.

[0130] Feedback selection based on PUCCH configuration may be provided. In an example, the WTRU may determine the type of feedback based on the PUCCH configuration to be used for feedback. A WTRU allocated with short PUCCH resources may, for example, determine that a PDSCH transmission may require TB-based HARQ feedback. A WTRU allocated with long PUCCH resources may, for example, determine that CBG-based HARQ feedback may be required. In an example, the WTRU may determine the type of CSI feedback based on the PUCCH configuration, for example.

[0131] PUCCH transmissions may be multiplexed. In an example, a WTRU may be configured to multiplex multiple PUCCH transmissions. For example, multiplexing may be achieved by allocating multiple PUCCH transmissions on the same resources. A WTRU may be allocated a different frequency interleave, frequency hopping pattern, and / or orthogonal cover code (OCC) for each of the multiple PUCCH transmissions.

[0132] A WTRU may be allocated resources for multiple PUCCH transmissions. For example, the resources may be conflicting resources. In an example, the WTRU may multiplex multiple UCIs on the same PUCCH resource. In an example, the WTRU may have a priority order associated with the UCI. The WTRU may discard UCI or feedback with a lower priority. In an example, the WTRU may have a priority order associated with the UCI and may use the PUCCH resource for the highest priority UCI and may use another set of PUCCH resources (e.g., a fallback set of PUCCH resources) for another UCI transmission. In an example, the WTRU may use fallback PUCCH resources for multiple UCI transmissions. In an example, different fallback resources may be allocated for each of the multiple UCIs. The fallback resources may enable multiplexing (e.g., efficient multiplexing). In an example, the PUCCH configuration for the UCI may not use interleaving. In an example, the fallback configuration may use an interleaving pattern that may enable multiplexing. In an example, the PUCCH configuration for the UCI may include a BWP offset (e.g., in the event of a conflict with another UCI transmission). In an example, the short PUCCH configuration timing (eg, one or more symbol positions) may depend on whether the UCI transmission may be collision aware. In an example, the PUCCH frequency hopping configuration may depend on whether a collision occurs.

[0133] Differentiated treatment may be provided. Determination of a profile applicable to a transmission may be provided. The WTRU may process and transmit UCI, for example, according to a transmission profile (e.g., a determined transmission profile) that may be associated with the UCI. For example, a transmission profile may be determined such that the amount of resources and priority may meet the reliability target of the UCI. Such determination of the transmission profile may allow for efficient utilization of resources.

[0134] In an example, a transmission profile may be associated with uplink data or sidelink data. For example, a transmission profile associated with uplink data or sidelink data may be used to allow prioritization between uplink data or sidelink data and UCI of different profiles.

[0135] A transmission profile applicable to the DCI, UCI, or data may be determined. In an example, the transmission profile associated with the UCI may be equivalent to or determined from one or more of: (i) a transmission profile for associated downlink data transmission (e.g., for HARQ-ACK or CSI); (ii) a transmission profile for associated uplink data transmission (e.g., for SR); or (iii) a bandwidth portion in which the UCI is transmitted.

[0136] For example, a transmission profile associated with UCI or uplink data may be determined based on one or more of the following: (i) a logical channel or logical channel group from which data may be transmitted based on a higher layer configuration (e.g., a transmission profile may be configured for each logical channel or logical channel group, or the WTRU may determine a transmission profile based on the configuration of a logical channel (LCH) to determine one or more physical layer attributes for a given transmission (e.g., transmission duration or the like); (ii) a logical channel or logical channel group for data that may have triggered an SR; (iii) a value of a field in a DCI that may be associated with the transmission of UCI or uplink data (e.g., an explicit indication of a transmission profile, or an implicit indication of a transmission profile); (iv) attributes of a PDCCH that may be associated with the transmission of UCI or uplink data (e.g., CORESET, monitoring period, determination of whether to monitor the PDCCH at the beginning of a timeslot, search space or aggregation level, or bandwidth portion that may be used for PDCCH decoding), such as where a transmission profile may be configured (e.g., by a higher layer) for a CORESET (e.g., per CORESET) or a PDCCH configuration (e.g., per PDCCH configuration; (v) a field in higher layer signaling (e.g., for CSI) and / or DCI, which may indicate a set of parameters configured, for example, by a higher layer (e.g., a CSI report setting that may be indicated by a periodic CSI field); (vi) attributes of a PDSCH transmission or attributes associated with a PDSCH transmission, such as duration, bandwidth portion, attributes of a parameter configuration (e.g., subcarrier spacing, symbol duration, etc.), transmission configuration indication (TCI) state (e.g., for HARQ-ACK), a modulation and coding scheme (MCS) table configured or indicated for control information associated with a PDSCH transmission (e.g., in a DCI); (vii) a PDSCH configured for transmission of an SR. attributes of UCCH resources or associated with PUCCH resources configured for transmission of SR (such as subcarrier spacing, duration of PUCCH resources, logical channels associated with the SR configuration, or attributes thereof, such as priority, and / or a transmission profile explicitly configured as part of the SR configuration); (viii) attributes of grants or PUSCH transmissions (e.g., for uplink data) or associated with grants or PUSCH transmissions (e.g., for uplink data), for example, attributes used to determine logical channel restrictions for logical channel prioritization (such as duration of PUSCH transmissions, attributes of parameter configuration (e.g., subcarrier spacing, symbol duration), or attributes of the carrier);Or (ix) a portion of the bandwidth over which an associated PDSCH transmission or PUSCH transmission is transmitted. With respect to (iv), the transmission profiles may have a precedence based on a priority order that may be configured. For example, if a PDCCH candidate is part of a search space associated with more than one transmission profile, the transmission profiles may have a precedence based on the configured priority order. With respect to (i), a transmission profile associated with the UCI may be determined based on an attribute (e.g., a QoS metric) associated with a logical channel or logical channel group from which data may be transmitted. With respect to (v), a BLER target value may be configured for a CSI reporting setup. The BLER target value may implicitly indicate a transmission profile. For example, a lower BLER target value may indicate a higher priority transmission profile. In one example, a CQI reporting table may be configured for a CSI reporting setup. ;

[0137] The transmission profile of the DCI or downlink data can be determined, for example, based on one or more of the following: (i) an attribute of the PDCCH from which the DCI can be decoded or an allocation for downlink data can be decoded, for example, as disclosed herein for UCI or uplink data (e.g., search space, explicit configuration, etc.); (ii) a modulation and coding scheme (MCS) table indicated for control information associated with a PDSCH transmission (e.g., in the DCI); such an indication can be configured by a higher layer or can be included in a field of the DCI; (iii) a value of a field in the DCI that can be associated with the transmission of downlink data or an RNTI value that can be used to mask the CRC; or (iv) an attribute of an allocation or PDSCH transmission (e.g., for downlink data) or an attribute associated with an allocation or PDSCH transmission (e.g., for downlink data), such as the duration of the PDSCH transmission, and / or attributes of a parameter configuration (e.g., subcarrier spacing, symbol duration, etc.).

[0138] In an example, a transmission profile may be defined for a physical channel (e.g., PDCCH, PUCCH, PDSCH, or PUSCH). For example, the transmission profile may be determined based on the type of data or control information that may be carried by the physical channel. For example, when the physical channel transmission includes control information and / or data of different profiles (e.g., UCI multiplexed in PUSCH), the transmission profile may be set based on the highest priority level in the profile.

[0139] The determination of the profile may indicate a timing characteristic. In an example, a transmission profile may be associated with a timing characteristic. Such a timing characteristic may correspond to at least one of: (1) a scheduling-related delay component, for example, such a component may correspond to one of N1 or N2; (2) a WTRU processing time, for example, such a processing time may correspond to one of N1 or N2; (3) a starting symbol of a transmission; or (4) a duration of a transmission. N1 and / or N2 may represent the number of OFDM symbols as described herein. In an example, a transmission profile may correspond to a transmission for which one or more such timing characteristics may be provided up to a value. The particular value may represent an aspect of the WTRU configuration. The transmission profile may be associated with at least one priority level or at least one parameter that determines a channel access attribute for operation in an unlicensed band. For example, the at least one parameter may include a maximum contention window size or a deferral duration.

[0140] Processing of transmission characteristics based on a profile (eg, a transmission profile) may be provided. For example, coding aspects, transmission power, and / or resource selection or allocation may be determined based on a transmission profile as described herein.

[0141] In an example, the WTRU may determine one or more aspects related to channel coding for a physical channel (e.g., PDCCH, PDSCH, PUCCH, or PUSCH) based on a transmission profile. The coding aspects that may be determined may include one or more of the following: (i) code type (e.g., polar code, LDPC, Turbo code, repetition); (ii) code rate; (iii) length of a cyclic redundancy check (CRC) that may be appended to a set of information bits for error detection; (iv) mapping between a modulation and coding scheme (MCS) field and a modulation order and code rate; or (v) one or more search spaces for one or more aggregation levels for decoding a PDCCH.

[0142] In an example, for example, when the higher layer configuration for the PDCCH may indicate a first transmission profile, the WTRU may be configured with a 16-bit CRC for the PDCCH. For example, when the configuration may indicate a second transmission profile, the WTRU may be configured with a 24-bit CRC. For example, when the characteristics of the data being transmitted may require a variable CRC size, using a variable CRC size may allow the network to use a more reliable PDCCH transmission.

[0143] In an example, a code rate that can be applied to at least one type of UCI (e.g., HARQ-ACK) can depend on, for example, a transmission profile. In an example, UCIs of multiple transmission profiles can be multiplexed into the same transmission (e.g., PUCCH). UCIs (e.g., each UCI) can be encoded separately (e.g., at a profile-dependent code rate). Such encoding can represent a first encoding stage. The decoded bits from the first encoding stage associated with each UCI can be concatenated and subjected to a second encoding stage.

[0144] The transmission power may be determined based on a transmission profile. In an example, the WTRU may determine and apply a transmission power associated with a transmission. The transmission power may be determined using a formula and / or parameters that depend on the transmission profile. In an example, a parameter that may be used in a power control formula may be configured (e.g., independently configured) for each transmission profile. In an example, the power control setting may be based on an offset value that may be configured by the transmission profile. In an example, the interpretation of the TPC field (e.g., in terms of the number of dB used to increase or decrease) may depend on the transmission profile. Using a transmission profile to determine the transmission power may facilitate using an appropriate power level to achieve a target reliability associated with a transmission (e.g., each transmission).

[0145] In an example, the power control parameters applied to the transmission of a scheduling request (SR) may depend on the SR configuration. The SR configuration may be mapped to the logical channel that may have triggered the SR.

[0146] In an example, the power control parameters applied to the HARQ-ACK transmission may depend on the duration of the corresponding PDSCH transmission. For example, if the PDSCH transmission is below a threshold configured by higher layers, the WTRU may apply a first set of power control parameters. If the PDSCH transmission is above the threshold, the WTRU may apply a second set of power control parameters.

[0147] In an example, the power control parameters applied to the HARQ-ACK transmission may depend on the UL bandwidth part (eg, active bandwidth part) in which the HARQ-ACK is transmitted, or on the DL bandwidth part in which the corresponding PDSCH is transmitted. Each bandwidth part may be configured with a set of power control parameters by higher layers.

[0148] In an example, the power control parameters applied for CSI transmission on the PUCCH (or PUSCH) may depend on the BLER target value configured for the CSI reporting setting. For example, the WTRU may apply a power offset based on the BLER target value. The BLER target value may be configured by higher layers, for example, for each BLER target value. For example, the power offset may be configured for each CSI reporting setting.

[0149] Data or UCI of multiple transmission profiles may be multiplexed in the same transmission.For example, power control parameters for common transmissions may be determined based on the profile (eg, the profile with the highest priority level).

[0150] In an example, the power control parameters may include a specific power control mode (PCM) or a minimum guaranteed power level. For example, the PCM may include PCM1, PCM2, and the like.

[0151] For example, resource selection or allocation may be determined based on a transmission profile. In an example, the resources and / or formats that may be used by a transmission may be a function of the transmission profile. For example, in the case of a PUCCH, the set of resources and / or formats indicated by the ARI may depend on the transmission profile. The network may, for example, configure at least one resource set for a transmission profile (e.g., each transmission profile). A resource set that may be subject to lower interference may be associated with a transmission profile that may be used for more reliable transmission.

[0152] In an example, the use of long or short PUCCH formats and / or the number of symbols may be a function of the transmission profile. In an example, the WTRU may be configured to transmit PUCCH on multiple symbols (e.g., two symbols) for a transmission profile (e.g., a first transmission profile) that may be suitable for ultra-reliable services. The WTRU may be configured to transmit PUCCH on a symbol (e.g., one symbol) for another transmission profile (e.g., a second transmission profile) that may be suitable for other non-ultra-reliable mobile broadband services.

[0153] In an example, a set of bandwidth portions and parameter configurations (e.g., including one or more of subcarrier spacing, length of cyclic prefix, or number of symbols per timeslot or mini-slot) may be used for downlink transmissions or uplink transmissions within a carrier, e.g., may depend on a transmission profile.

[0154] In an example, the waveform may depend on the transmission profile. For example, the waveform may be an orthogonal frequency division multiplexing (OFDM) waveform or a single carrier frequency division multiple access (SC-FDMA) waveform. In an example, the use of frequency hopping may depend on the transmission profile.

[0155] In an example, with respect to at least one type of UCI (e.g., HARQ-ACK), the UCI may be transmitted on the PUCCH or multiplexed with data transmitted on the PUSCH. The selection of whether the UCI is transmitted on the PUCCH or multiplexed with data transmitted on the PUSCH may depend on a transmission profile associated with the UCI and the data. In an example, for example, when the UCI and the data may have the same transmission profile or the same priority associated with the transmission profile, the UCI may be multiplexed with the data on the PUSCH. The UCI may be sent separately on the PUCCH. In an example, at least one type of UCI (e.g., channel state information (CSI)) may be discarded.

[0156] In an example, the number or fraction of resource elements that may be used by at least one type of UCI (e.g., when multiplexed with data in a PUSCH) may be determined, for example, by one or more factors (e.g., β parameters). These factors may be a function of a transmission profile. In an example, for a given type of UCI, the WTRU may be configured with a first set of factors applicable to a first transmission profile and a second set of factors applicable to a second transmission profile. For example, a transmission profile that may be applicable to ultra-reliable services may allow a larger proportion of PUSCH resources to be used.

[0157] In an example, the WTRU may determine whether to apply UCI diversity. For example, the SR configuration may include the configuration of PUCCH resources (or PUCCH diversity resources) applicable for UCI diversity. For example, when the SR is triggered by a logical channel (LCH) mapped to such a SR configuration, the WTRU may transmit the SR on more than one PUCCH resource (or PUCCH diversity resource).

[0158] Prioritization between transmissions can be provided. In an example, a priority level can be defined or configured for a transmission profile (e.g., each transmission profile). For example, the priority level can be used to determine whether one or more transmissions can be dropped or preempted, curtailed, allocated fewer resources, or processed later, such as in the presence of contention. For example, the occurrence of contention can be beneficial (e.g., from a system perspective) by allowing a greater proportion of system resources to be used (e.g., compared to a situation where resources can be reserved).

[0159] Prioritization may be provided for power scaling. In an example, for example, when the configured total maximum power is exceeded during a time period (e.g., during a subframe, time slot, or mini-slot), the WTRU may scale back at least one transmission. The priority order for scaling may depend on the transmission profile (e.g., in addition to other criteria such as UCI or data type). In an example, the transmission profile criteria may take precedence over or supersede other criteria. In an example, if a first transmission profile has a higher priority than a second transmission profile, power may be allocated to a PUSCH that may include data to be transmitted according to a first transmission profile before a PUCCH that may include a HARQ-ACK to be transmitted according to the second transmission profile. Prioritization based on the use of transmission profiles may be applied even when the HARQ-ACK may otherwise take precedence over the data.

[0160] Prioritization may be provided for dropping a transmission or at least a portion of a transmission. In an example, the WTRU may determine, for example, based on a transmission profile associated with overlapping transmissions, that more than one transmission may overlap on a subset of resources and at least a portion of at least one transmission may be dropped or preempted. The WTRU may, for example, determine that a transmission with the highest priority (e.g., based on the transmission profile) may be transmitted on the resource.

[0161] For example, overlap may arise due to scheduling instructions that may be received at different times and have different waiting time requirements. In an example, the WTRU may receive a downlink assignment that may require the transmission of HARQ-ACK on the PUCCH in certain symbols of a time slot. The WTRU may receive an authorization for a PUSCH transmission for the same time slot (e.g., subsequently receive an authorization). For example, when a transmission profile associated with uplink data that may be transmitted via PUSCH has a higher priority than a transmission profile associated with HARQ-ACK that may be transmitted via PUCCH, the WTRU may determine that the PUSCH transmission takes precedence over the PUCCH transmission. Based on such a determination, the WTRU may use overlapping resources for PUSCH transmissions and may discard PUCCH transmissions. In an example, the WTRU may transmit PUCCH on overlapping resources. The WTRU may use the remaining resources that may be indicated for PUSCH, for example, to consider the reduced amount of resources in the rate matching calculation.

[0162] The WTRU may receive a first downlink assignment indicating a HARQ-ACK transmission on a PUCCH in a first resource. The WTRU may receive (e.g., subsequently receive) a second downlink assignment indicating a transmission of a HARQ-ACK on a PUCCH in a second resource. For example, if the first resource and the second resource overlap or are the same, the WTRU may transmit a HARQ-ACK corresponding to a PDSCH (or PDCCH) with a transmission profile having a higher priority. The WTRU may transmit a HARQ-ACK corresponding to a PDSCH (or PDCCH) based on, for example, a CORESET, a search space, and / or an RNTI.

[0163] In an example, the WTRU may receive a grant for a PUSCH on a timeslot. The WTRU may receive (e.g., subsequently receive) a downlink assignment (or trigger a scheduling request) that may require transmission of a PUCCH on one or more resources of the same timeslot (e.g., on the last time symbol for a short PUCCH or on one or more available time symbols (e.g., most or all time symbols) of an uplink for a long PUCCH). For example, when the PUCCH includes UCI associated with a higher transmission profile than the data transmitted over the PUSCH, the WTRU may determine that the PUCCH may be transmitted on overlapping resources. The WTRU may determine that the PUSCH may be dropped or that the PUSCH may be transmitted on non-overlapping resources, such as applying puncturing on overlapping resources. The course of action may depend on the type of preempted transmission (e.g., when preempted by a short PUCCH, the PUSCH may still be transmitted) and / or whether the proportion of preempted resources may be above a threshold.

[0164] The WTRU may multiplex HARQ-ACK and CSI into a single PUCCH transmission or PUSCH transmission and determine one or more subsets of CSI reports (e.g., N 报告的 CSI ) may be selected based on a configurable maximum code rate. The priority order of one or more CSI reports may depend on the transmission profile (or configured BLER target value), such that a CSI report associated with a lower BLER target value may be considered to have a higher priority than a CSI report associated with a higher BLER target value. The priority determined from the BLER target value or the transmission profile may override at least one other priority criterion for selecting a CSI report, such as the CSI type. For example, this may result in the precoding matrix information (PMI) of a CSI report associated with a lower BLER target value having a higher overall priority than the RI (rank information) of a CSI report associated with a higher BLER target value.

[0165] Prioritization may be provided for DL ​​data processing. In an example, a WTRU may be scheduled to receive DL data with different transmission profiles on at least one PDSCH and may report a HARQ-ACK associated with the DL data (e.g., at a specific time). The WTRU may not be able to complete decoding of at least one code block in time to transmit the corresponding HARQ-ACK. The WTRU may prioritize decoding of higher priority DL data, for example, based on the transmission profile associated with the DL data.

[0166] In an example, the HARQ-ACK may be transmitted before the decoding of at least one code block group of the transport block is completed. Depending on the transmission profile associated with the data, the WTRU may set the HARQ-ACK using one of the following methods. For example, when the decoding is completed, the WTRU may set the HARQ-ACK for the code block group that has not yet been decoded to ACK, and may set it to NACK for at least one other code block group of the transport block. The WTRU may set the HARQ-ACK to ACK for one or more code block groups (except for the code block groups that may be set to NACK). This may minimize the amount of resources used by the network for retransmissions, for example, in cases where some code blocks that have not yet been decoded may be successful and do not need to be retransmitted. For example, this example process may be selected for a transmission profile that may have a lower priority.

[0167] In an example, the WTRU may set the HARQ-ACK for a code block group that has not yet been decoded to NACK. This may minimize latency for transport block delivery, for example, when retransmitted data may be available sooner, for example, when the result of decoding may not be successful. For example, this example process may be selected for a transport profile that may have a higher priority.

[0168] Prioritization may be provided for resource sharing. In an example, the WTRU may be configured to multiplex UCI and / or uplink data into (e.g., the same) PUSCH transmission or PUCCH transmission according to different transmission profiles. The proportion of resources (e.g., resource elements (REs)) that may be allocated to UCI or data according to the transmission profile may depend on the relative priority level of the transmission profile. In an example (e.g., for UCI multiplexing in PUSCH), for example, when the priority of the transmission profile associated with UCI is higher than the priority of the transmission profile associated with data, a first value of the β parameter for the UCI type may be applied. For example, when the two transmission profiles have the same priority, a second value of the β parameter may be applied. For example, when the priority of the transmission profile associated with UCI is lower than the priority associated with the transmission profile of data, a third value of the β parameter may be applied.

[0169] The payload / MCS selection may be priority based. In an example, the WTRU may be configured to use a first modulation and coding scheme, transport block size, and / or payload for a transmission, for example, when the transmission may not conflict with a higher priority transmission according to a transmission profile. The WTRU may be configured to use a second modulation and coding scheme, transport block size, or payload for the transmission, for example, when the transmission conflicts with a higher priority transmission according to a transmission profile. The conflict may correspond to a situation, for example, when resources of multiple transmissions may overlap or when a configured maximum total transmit power may be exceeded.

[0170] State-based differential processing may be provided. In an example, the WTRU may apply a set of parameters corresponding to a transmission profile (e.g., based on a transmission profile state). The transmission profile state may be changed by an indication from the network. For example, the transmission profile state may be changed via a MAC control element (MAC CE) or via downlink control information (DCI). The transmission profile state may be changed when an event occurs, such as when a timer (e.g., a timing advance (TA) timer) expires. The set of parameters corresponding to the transmission profile may include a PUCCH resource set for HARQ ACK / NACK, a parameter set for determining a fraction of resource elements used for UCI in a PUSCH, etc.

[0171] In an example, a transmission profile and associated parameters may be configured for a bandwidth part. A WTRU configured with multiple bandwidth parts may apply a transmission profile and associated parameters corresponding to an active bandwidth part. The WTRU may receive a DCI or MAC CE indicating a change in the active bandwidth part. The WTRU may (e.g., upon receiving the indication) apply the transmission profile and associated parameters associated with the received (or indicated) active bandwidth part.

[0172] In an example, the WTRU may receive a DCI indicating a change of an active bandwidth portion (e.g., where the new active bandwidth portion and the existing active bandwidth portion may share the same configuration, except for at least the transmission profile and associated parameters). For example, the WTRU may be configured to have two bandwidth portions, the two bandwidth portions having the same frequency allocation. When the WTRU receives an indication of a change of active bandwidth portion (e.g., which satisfies the condition), the WTRU may receive the PDSCH in the same timeslot as the timeslot in which the DCI was received based on the parameters indicated in the DCI (e.g., as if there was no change in the active bandwidth portion). In an example, if the WTRU receives an indication of an active bandwidth portion, where the new active bandwidth portion does not have the same frequency allocation as the existing active bandwidth portion, the WTRU may apply a gap in the reception of the PDSCH (e.g., to allow retuning and / or perform other actions (e.g., CSI measurements on the new active bandwidth portion)).

[0173] Systems, methods, and means may be provided for handling transmission characteristics having overlap between multiple transmissions. A WTRU may determine that there is an overlap in time between multiple transmissions (e.g., a first transmission and a second transmission). The WTRU may perform at least one of the following: (1) perform a subset (e.g., one) of the transmissions; (2) cancel, discard, or interrupt (e.g., if already in progress) one of the transmissions; (3) suspend and / or delay one of the transmissions; (4) perform both transmissions, e.g., if there is no frequency overlap between the transmissions, and / or apply a power scaling function to at least one of the transmissions; or (5) modify at least one attribute of the first transmission, e.g., to transmit at least a portion of information that may have been transmitted using the second transmission. For example, the WTRU may modify an attribute of a demodulation reference signal (DM-RS) for a first PUSCH transmission to indicate a scheduling request (SR). The modification may include, for example, assigning zero power, changing to a second preconfigured resource, changing phase, etc. The WTRU may perform such an action in conjunction with assigning zero power to a second transmission, e.g., an SR on a PUCCH, which may have overlapped in time.

[0174] In other examples of transmissions described herein, the first transmission may include an SR and the second transmission may include a PUSCH (or PUCCH). An SR associated with a high priority service may be multiplexed with the PUSCH or PUCCH. The WTRU may indicate and / or transmit uplink control information (e.g., an SR) associated with a first transmission profile by modifying at least one attribute of a transmission associated with a second transmission profile, such as a PUSCH transmission or a PUCCH transmission. In an example, the first transmission profile may have a higher priority than the second transmission profile. In an example, the duration of the PUSCH transmission or the PUCCH transmission may be longer than (e.g., significantly longer than) the period of the scheduling request of the first transmission profile. The length of the PUSCH transmission or the PUCCH transmission may have a property that waiting for the end of the PUSCH transmission or the PUCCH transmission before sending the SR may exceed a waiting time value (e.g., an acceptable waiting time value).

[0175] At least one property of the transmission that can be modified can include a property of a reference signal embedded in the transmission, such as a demodulation reference signal (DM-RS). For example, such a property can include a relative phase between two time symbols carrying the DM-RS. For example, if no SR is transmitted, the relative phase can be a first value. If a scheduling request is transmitted, the relative phase can be a second value.

[0176] At least one attribute of the transmission that may be modified may include a transmit power parameter for at least one time symbol (or resource element). For example, when an SR is transmitted, the transmit power of at least one symbol may be reduced compared to the transmit power of the remaining symbols. In an example, the transmit power of the at least one symbol may be reduced to zero and / or the WTRU may not transmit on the at least one symbol. This may allow the network to reliably detect the transmission of the SR and allow successful decoding of the PUSCH.

[0177] At least one time symbol (or resource element) on which a transmission is modified may be limited to a subset of the time symbols of the transmission. For example, if the indication is carried by modifying an attribute of a reference signal, the time symbols may be limited to time symbols carrying such a reference signal. The time symbols affected by the modification may include time symbols (e.g., all time symbols) that carry a reference signal after the SR is triggered. In an example, if the indication is carried by modifying the transmission power of at least one time symbol, the subset may be determined based on the configured periodicity of the scheduling request. At least one affected time symbol may include a single symbol or a time symbol (e.g., all time symbols) immediately after the SR is triggered, which may coincide with the configured timing of the scheduling request. In an example, one or more time symbols including a reference signal may be excluded from the subset.

[0178] In an example, a subset of resource elements (or time symbols) of a PUSCH transmission or a PUCCH transmission may be configured to indicate whether an SR has been triggered since the start of the transmission. The WTRU may be configured to have at least one such subset of resource elements that occurs regularly (e.g., periodically) in the time domain. This configuration may depend on the configured periodicity of the SR, or may coincide with the configured timing of the transmission of the SR. On a given subset, for example, if the SR has not been triggered until an offset before one or more time symbols of the subset, the WTRU may transmit a first predefined sequence of modulation symbols. For example, if the SR has been triggered, the WTRU may transmit a second predefined sequence of modulation symbols. The predefined sequence may overwrite (e.g., using puncturing) modulation symbols of the PUSCH or PUCCH that may have been mapped (e.g., previously mapped) to the subset of resource elements, or the subset of resource elements may have been initially excluded from the set of resource elements to which the modulation symbols of the PUSCH or PUCCH transmission are mapped.

[0179] Systems, methods and means for processing transmission characteristics based on timing may be provided.One or more aspects may be determined based on available WTRU processing (eg, WTRU processing time).

[0180] The WTRU may determine that it may apply at least one prioritization or multiplexing solution. The prioritization or multiplexing solution may be a function of one or more timing aspects, including, for example, at least one of the following: (1) a timing aspect of when data is available for transmission, or when data available for transmission may trigger the transmission of a BSR and / or the transmission of an SR; (2) a timing aspect of when a scheduling request (SR) may be triggered; (3) a timing aspect of when downlink control information indicating an uplink transmission (e.g., a PUSCH transmission or a PUSCH transmission) may be received; (4) a timing aspect of when, for example, at least a configured grant or another periodic or semi-persistent transmission (e.g., CSI, SR S), (5) timing aspects of receiving higher layer signaling according to a configured or dynamic grant, (6) timing aspects of when a PUCCH transmission may start (and / or end), for example, according to a semi-static configuration or an indication from downlink control information, (7) the duration of a PUSCH or PUCCH transmission, or (8) timing aspects when a transmission may be determined to occur in the future due to any other reason, such as the receipt of a paging request, the initiation of a procedure such as an RRC connection re-establishment, etc. In the case of (1), the WTRU may perform such a determination, for example, when new data may become available for transmission of a logical channel (LCH) of a particular priority and / or type, or when data available for transmission may trigger the transmission of a buffer status report (BSR) and / or SR. The WTRU may perform such a determination for data associated with mapping restrictions (e.g., (LCH to transmission mapping restrictions), profiles, and / or LCH / Logical Channel Group (LCG) priorities.

[0181] The WTRU may perform such a determination to apply at least one of a prioritization or multiplexing solution for data and / or for transmissions associated with a particular (LCH to transmission) mapping restriction to a particular profile and / or a particular LCH / LCG priority. For example, the WTRU may determine a prioritization or multiplexing solution that may be applied to at least two or more transmissions (e.g., partially overlapping transmissions). As described herein, the determination may be made based on a difference between a start time of a first transmission and a time at which a second transmission is determined to exist.

[0182] For example, if the WTRU determines that a first event A (Event A) occurs at least x symbols (one or more) before the start of event B (Event B), the WTRU may perform a first action 1 (Action 1) or a second action 2 (Action 2). Event B may be a known event.

[0183] One or more timing cases may be provided to indicate that the SR trigger may be a function of the suitability of the grant. Event A may correspond to a WTRU autonomous trigger associated with the receipt of downlink control signaling and / or may correspond to an event of higher priority than event B (e.g., based on an applicable transmission profile). The autonomous trigger may be one of the timing aspects as described herein, for example, triggering an SR when new data becomes available for transmission. Event B may correspond to a scheduling event (e.g., an uplink transmission).

[0184] In action 1, the WTRU may determine that there is sufficient time available to act on the scheduling information and / or prioritize one of the two events before the lower priority event begins. In action 2, the WTRU may determine that there is insufficient time available to adjust its transmission and / or prioritize one of the two events before the lower priority event begins so that the WTRU may determine to modify the attributes of the corresponding ongoing transmission. The WTRU may be configured, for example, through RRC, with a value of x, where x may be a time value in symbols in framing units (e.g., mini-slots, slots, subframes) or in absolute time (e.g., in milliseconds).

[0185] In an example, event A may correspond to a SR trigger for data associated with a transmission profile, e.g., a transmission profile corresponding to transmission of URLLC data. Event B may correspond to the start of an uplink transmission on a PUSCH for data associated with a transmission profile, e.g., corresponding to transmission of eMBB data.

[0186] Action 1 may correspond to cancellation of an uplink transmission, e.g., corresponding to a PUSCH transmission of eMBB data, and the WTRU performs an SR transmission using resources / methods corresponding to the URLLC data type. Action 2 may correspond to cancellation / dropping / zero power setting of one or more specific symbols and / or DM-RS modification of a PUSCH transmission for eMBB, e.g., to indicate an SR for URLLC, as described herein.

[0187] In an example, one of the transmissions may correspond to a first transmission profile or the like, such as a URLLC service, and the other may correspond to a second transmission profile, such as an eMBB service. In such an example, if the WTRU determines that there is sufficient processing time (e.g., the time between two events is less than x), and if the WTRU makes this determination before any of the at least partially overlapping transmissions begins, the WTRU may perform at least one of the following for different signal combinations: (1) the WTRU may prioritize the SR (for URLLC) and discard the PUSCH (for eMBB); (2) the WTRU may use the SR (for URLLC) to pre-empt and / or puncture the PUSCH (for eMBB), for example using a cascading principle similar to the UCI on the PUSCH used for LTE; (3) the WTRU may embed the transmission, for example, discarding a portion of the PUSCH (for eMBB) and replacing it with sPUSCH (including the BSR (for URLLC)); (4) the WTRU may use a modification to the DM-RS sequence of the PUSCH (for eMBB) to signal the SR; (5) the WTRU may adjust the UL PC, for example, by applying power scaling, for example if the WTRU is power limited.

[0188] In an example, if the WTRU determines that there is insufficient processing time (e.g., the time between two events is less than x), or if the WTRU does not make this determination before any one of the at least partially overlapping transmissions begins, the WTRU may perform at least one of the following for different signal combinations: (1) the WTRU may preempt / interrupt or puncture the ongoing PUSCH (for eMBB), and the WTRU may use associated resources (e.g., on a short PUCCH) to transmit an SR (for URLLC), while, for example, transmitting a BSR (for URLLC) on a short PUSCH (for URLLC), and / or transmitting a URLLC TB, for example, on a short PUSCH (for URLLC); (2) the WTRU may signal an SR using a change in the DM-RS sequence of the ongoing PUSCH (for eMBB); (3) the WTRU may adjust the UL PC accordingly (e.g., for DM-RS enhancement).

[0189] In an example, for example, if the WTRU is configured with simultaneous PUSCH+PUSCH or PUSCH+PUCCH, the WTRU may initiate additional transmissions on the same carrier. For example, if configured and / or activated, the WTRU may send additional transmissions in the same bandwidth portion or in different bandwidth portions. The WTRU may perform such transmissions using disjoint resources and / or joint resources. Disjoint resources may include separate PUSCH and / or PUCCH transmissions that may start with (one or more) other ongoing transmissions. For example, when URLLC is configured, joint resources may be used, and / or any grants for other types of services (e.g., services with lower priority) may include resources for additional transmissions of SR, BSR.

[0190] The WTRU may use one or more power control functions to allocate power. The WTRU may consider transmissions that at least partially overlap in time but the WTRU may not have yet determined whether to transmit such transmissions. The WTRU may include the following factors in determining whether to transmit such transmissions: the power allocation function, method, and / or corresponding priority in the resources that may be used, for example, if a maximum power reduction (MPR) setting is implemented.

[0191] The systems and / or methods described herein may be implemented in a computer program, software, and / or firmware contained in a computer-readable medium so as to be executed by a computer and / or a processor. Examples of computer-readable media may include electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media may include read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as, but not limited to, internal hard disks and removable disks), magneto-optical media and / or optical media (such as CD-ROM disks), and / or digital versatile disks (DVDs). A processor associated with the software may be used to implement a radio frequency transceiver used in a WTRU, a terminal, a base station, an RNC, and / or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), comprising: a receiver configured to receive configuration information indicating a first set of one or more parameters associated with resource allocation for a first uplink control information (UCI) associated with a first priority and a second set of one or more parameters associated with resource allocation for a second UCI associated with a second priority; as well as receiving information indicating that the first UCI associated with the first priority is to be transmitted, wherein the first UCI is to be transmitted in a physical uplink shared channel (PUSCH) transmission; as well as a processor configured at least to: determine, based on the first set of one or more parameters associated with resource allocation for the first UCI associated with the first priority, an amount of resources to be allocated for the PUSCH transmission of the first UCI; as well as A transmitter configured to transmit the first UCI using the amount of resources for the physical uplink shared channel transmission determined based on the first set of one or more parameters associated with resource allocation for the first UCI associated with the first priority.

2. The WTRU of claim 1 , wherein the receiver is further configured to receive information indicating that information of the second UCI associated with the second priority is to be transmitted, wherein The second UCI is to be transmitted in a second physical uplink shared channel transmission; wherein the processor is further configured to determine, based on the second set of one or more parameters associated with resource allocation for UCI associated with the second priority, an amount of resources to be allocated to the second physical uplink shared channel transmission of the second UCI; and The transmitter is further configured to transmit the second UCI using the amount of resources for transmission of the second physical uplink shared channel determined based on the second set of one or more parameters associated with resource allocation of UCI associated with the second priority.

3. The WTRU of claim 1 , wherein the first priority is associated with a first transmission profile and the second priority is associated with a second transmission profile.

4. The WTRU of claim 1 , wherein the first set of one or more parameters associated with resource allocation for the first UCI associated with the first priority comprises a first set of one or more β parameters for multiplexing the first UCI associated with the first priority on a physical uplink shared channel resource, and the second set of one or more parameters associated with resource allocation for the second UCI associated with the second priority comprises a second set of one or more β parameters for multiplexing the second UCI associated with the second priority on a physical uplink shared channel resource.

5. The WTRU of claim 4 , wherein the first set of one or more β parameters is associated with a greater proportion of physical uplink shared channel resources allocated for transmitting the first UCI than the second set of one or more β parameters, and the first priority is a higher priority than the second priority.

6. The WTRU of claim 1 , wherein the information indicating that the first UCI is associated with the first priority comprises downlink control information (DCI) received in a physical downlink control channel transmission, and the DCI comprises a field indicating the first priority.

7. The WTRU of claim 1 , wherein the first UCI is multiplexed with uplink data associated with the first priority in a physical uplink shared channel transmission.

8. The WTRU of claim 1, wherein the first UCI comprises a scheduling request, and the information indicating that the first UCI is associated with the first priority comprises information indicating that a logical channel associated with the scheduling request is associated with the first priority.

9. The WTRU of claim 1 , wherein the amount of resources to be allocated to the physical uplink shared channel transmission of the first UCI comprises a number of resource elements.

10. The WTRU of claim 1, wherein the information indicating that the first UCI is associated with the first priority comprises configuration information received via higher layer signaling.

11. A method for transmitting uplink control information (UCI), comprising: receiving configuration information indicating a first set of one or more parameters associated with resource allocation for first uplink control information (UCI) associated with a first priority and a second set of one or more parameters associated with resource allocation for second UCI associated with a second priority; receiving information indicating that the first UCI associated with the first priority is to be transmitted, wherein the first UCI is to be transmitted in a physical uplink shared channel (PUSCH) transmission; as well as determining, based on the first set of one or more parameters associated with resource allocation for the first UCI associated with the first priority, an amount of resources to be allocated for the PUSCH transmission of the first UCI; as well as The first UCI is transmitted using the amount of resources for the physical uplink shared channel transmission determined based on the first set of one or more parameters associated with resource allocation for the first UCI associated with the first priority.

12. The method of claim 11, wherein the information indicating that the first UCI is associated with the first priority comprises downlink control information (DCI) received in a physical downlink control channel transmission, and the DCI comprises a field indicating the first priority. 13 . The method of claim 11 , wherein the first UCI is multiplexed with uplink data associated with the first priority in a physical uplink shared channel transmission.

14. The method of claim 11, wherein the first priority is associated with a first transmission profile and the second priority is associated with a second transmission profile. 15 . The method of claim 11 , wherein the amount of resources to be allocated to the physical uplink shared channel transmission of the first UCI comprises a number of resource elements. 16 . The method of claim 11 , wherein the first UCI comprises a scheduling request (SR), and the information indicating that the first UCI is associated with the first priority comprises information indicating that a logical channel associated with the SR is associated with the first priority. 17 . The method of claim 11 , wherein the information indicating that the first UCI is associated with the first priority comprises configuration information received via higher layer signaling.

18. The method according to claim 11, further comprising: receiving information indicating that information of the second UCI associated with the second priority is to be transmitted, wherein the second UCI is to be transmitted in a second physical uplink shared channel transmission; determining, based on the second set of one or more parameters associated with resource allocation for the second UCI associated with the second priority level, an amount of resources to be allocated for the second physical uplink shared channel transmission of the second UCI; and The second UCI is transmitted using the amount of resources for the second physical uplink shared channel transmission determined based on the second set of one or more parameters associated with resource allocation for the second UCI associated with the second priority.

19. The method of claim 11, wherein the first set of one or more parameters associated with resource allocation for the first UCI associated with the first priority includes a first set of one or more β parameters for multiplexing the first UCI associated with the first priority on a physical uplink shared channel resource, and the second set of one or more parameters associated with resource allocation for the second UCI associated with the second priority includes a second set of one or more β parameters for multiplexing the second UCI associated with the second priority on a physical uplink shared channel resource.

20. The method of claim 19, wherein the first set of one or more β parameters is associated with a greater proportion of physical uplink shared channel resources allocated for transmitting the first UCI than the second set of one or more β parameters, and the first priority is a higher priority than the second priority.

Images