Method and apparatus for UL multiplexing and prioritization in NR communication

Abstract

The present invention relates to a method and apparatus for UL multiplexing and prioritization in NR communications. A wireless transmit / receive unit (WTRU) may receive a first higher layer configuration for a cancel indication (CI). Further, the first higher layer configuration may include a set of reference frequency resources. In addition, the WTRU may receive an authorization indicating a frequency allocation and a time allocation for scheduled transmissions. Further, in the case where the CI is received, the WTRU may interrupt the scheduled transmission. In addition, the CI may indicate, for each time symbol in a set of time symbols, a subset of frequency resources of the set of reference frequency resources. Further, the WTRU may cancel the scheduled transmission if the subset of frequency resources of the set of time symbols overlaps the frequency allocation and the time allocation for the scheduled transmission. In further examples, the first higher layer configuration may include an applicable maximum priority, and the authorization may include a priority index.

Description

This application is a divisional application of Chinese patent application No. 202080032479.0, whose filing date is April 30, 2020, and entitled “Method and Apparatus for Uplink (UL) Multiplexing and Prioritization in New Radio (NR) Communications”. The contents of the parent application are incorporated herein by reference. CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application Serial No. 62 / 841,021, filed April 30, 2019, and U.S. Provisional Application Serial No. 62 / 886,173, filed August 13, 2019, the contents of which are incorporated herein by reference. Background Art

[0002] In the New Radio (NR) for the fifth generation (5G) wireless system, a new structure and design are adopted for the physical uplink control channel (PUCCH) used to transmit uplink data and the scheduling of the PUCCH through the physical downlink control channel (PDCCH). In NR, for data transmission, a transport block (TB) is a data transmission unit consisting of one or more code blocks (CBs).

[0003] A CB is a portion of data associated with an error correction code block and a cyclic redundancy check (CRC). A code block group (CBG) is a group of CBs associated with a single bit for ACK-NACK. A TB can consist of multiple CBGs. The maximum number of CBGs per TB can be configured by higher layer signaling.

[0004] Furthermore, the wireless system may include different use cases, such as services that rely on Ultra Reliable Low Latency (URLLC) access. Furthermore, the use cases may include services that rely on Enhanced Massive Mobile Broadband (eMBB) access. Summary of the invention

[0005] Method and apparatus for uplink (UL) multiplexing and prioritization involving cancellation, interruption, or preemption. In an example, a wireless transmit / receive unit (WTRU) may receive a first higher layer configuration for a cancellation indication (CI). Further, the first higher layer configuration may include a reference frequency resource set. In addition, the WTRU may receive a grant indicating a frequency allocation and a time allocation for a scheduled transmission. In addition, in the event that the CI is received, the WTRU may interrupt the scheduled transmission. In an example, the CI may indicate a frequency resource subset of the reference frequency resource set for each time symbol in a time symbol set. In addition, in the event that a frequency resource subset of the time-conforming set overlaps with a frequency allocation and a time allocation for a scheduled transmission, the WTRU may cancel the scheduled transmission.

[0006] In an example, the grant may include at least one of downlink control information (DCI), a dynamic grant, a configuration grant, a radio point resource control (RRC) signaling, or a second higher layer configuration. Further, the grant may include a priority index and a priority indication for the scheduled transmission, and in a further case where it is determined that the priority index for the scheduled transmission is lower than an applicable maximum priority, the scheduled transmission may be interrupted. Furthermore, the first higher layer configuration may include an applicable maximum priority. Furthermore, the first higher layer configuration may include a first indication. Furthermore, based on the first indication, it is determined that the priority index of the transmission is lower than the applicable maximum priority.

[0007] Furthermore, the first higher layer configuration may include a second indication. Furthermore, the scheduled transmission may be interrupted based on the second indication. Furthermore, the CI may include an applicable maximum priority.

[0008] Additionally, in the event that the priority index indicates a priority level lower than or equal to the applicable maximum priority level, the WTRU may begin transmitting the scheduled transmission as a low priority transmission. Additionally, in the event that the priority index indicates a priority level lower than or equal to the applicable maximum priority level, the WTRU may monitor the CI. Additionally, in the event that the priority index indicates a priority level higher than the applicable maximum priority level, the WTRU may begin transmitting the scheduled transmission as a high priority transmission.

[0009] In another example, the scheduled transmission may be a transmission on a physical uplink control channel (PUCCH). In another example, the scheduled transmission may be a transmission on a physical uplink shared channel (PUSCH). Furthermore, the scheduled transmission may be an ultra-reliable low latency (URLLC) transmission. Furthermore, the scheduled transmission may be an enhanced massive mobile broadband (eMBB) transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The present invention may be understood in more detail from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals denote like elements, and in which:

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

[0012] Figure 1B is a diagram showing that according to an embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) used within a communication system is shown;

[0013] Figure 1Cis a diagram showing that according to an embodiment, Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) used within the communication system shown;

[0014] Figure 1D is a diagram showing that according to an embodiment, Figure 1A A system diagram of another example RAN and another example CN used within the communication system shown;

[0015] Figure 2 is a diagram illustrating an example physical uplink control channel (PUCCH) resource identification based on an uplink (UL) cancellation indication;

[0016] Figure 3 is a flow chart illustrating an example of a WTRU procedure for adaptation of PUCCH format and PUCCH resources based on UL cancellation indication;

[0017] Figure 4 is a diagram showing an example of an enhanced massive mobile broadband (eMBB) frame structure and an ultra-reliable low latency (URLLC) WTRU frame structure;

[0018] Figure 5 is a flow chart illustrating an example process for an eMBB WTRU and a URLLC WTRU;

[0019] Figure 6 is a flow chart illustrating an example of an adaptive eMBB WTRU procedure for UL transmission with a configured grant in the presence of an explicit indication of cancelled UL resources by Group Common Downlink Control Information (GC-DCI);

[0020] Figure 7 is a flow chart illustrating an example of an adaptive eMBB WTRU procedure for UL transmission with dynamic grant in the presence of an explicit indication of cancelled UL resources by GC-DCI;

[0021] Figure 8 is a flow chart illustrating an example of a WTRU procedure for determining a set of cancelled resources based on a combination of semi-static configuration and dynamic indication through GC-DCI;

[0022] Fig. 9 is a diagram showing an example of a WTRU cancelling an uplink transmission based on a cancel indication (CI);

[0023] Fig.10 is a diagram showing an example of URLLC WTRU cancellation monitoring;

[0024] Fig.11is a diagram showing an example of effective cancellation monitoring;

[0025] Fig.12 is a diagram showing an example of an eMBB CG WTRU and a URLLC CG WTRU with monitoring cancelled;

[0026] Fig.13 is a diagram illustrating an example of an eMBB DG WTRU and a URLLC CG WTRU with configuration time based cancellation;

[0027] Fig.14 is a diagram showing an eMBB CG WTRU and a URLLC DG WTRU with cancellation and with a WTRU specific configuration using allowed resources and prohibited resources;

[0028] Fig.15 is a diagram showing an eMBB CG WTRU and a URLLC DG WTRU with cancellation and with grouped WTRU configuration using allowed resources and prohibited resources;

[0029] Fig.16 is a flow chart illustrating an example of a URLLC WTRU procedure for selecting a transmission mode in an ungranted UL transmission;

[0030] Fig.17 is a diagram illustrating an example of ungranted UL transmission by a URLLC WTRU in congested and non-congested transmission modes based on the presence of a UL cancellation indication;

[0031] Fig.18 is a flow chart illustrating an example of a WTRU procedure for physical random access channel (PRACH) format and resource adaptation based on dynamic UL cancellation indication;

[0032] Fig.19 is a diagram showing no interruption and the eMBB WTRU transmits for the entire scheduled duration;

[0033] Fig. 20 is a diagram showing an example of an interruption and an eMBB WTRU skipping transmission in resources occupied by a URLLC WTRU; and

[0034] Fig.21 is a diagram showing an example of an eMBB transmission with interruption, where the eMBB WTRU transmits a preemptive demodulation reference symbol (DMRS) orthogonal to the URLLC transmission. DETAILED DESCRIPTION

[0035] 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 discrete Fourier transform spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC), etc.

[0036] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network 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 (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 subscription 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.

[0037] The communication system 100 may also include a base station 114a and / or a base station 114b. Each base station 114a, 114b may be any type of device configured to facilitate access to one or more communication networks (e.g., the CN 106, the Internet 110, and / or other networks 112) by wirelessly interfacing with at least one of the WTRUs 102a, 102b, 102c, 102d. For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation Node B such as a gNode B (gNB), a New Radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. Although each 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.

[0038] The base station 114a may be part of the RAN 104, 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.

[0039] 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).

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

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

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

[0043] 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).

[0044] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, 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.

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

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

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

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

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

[0050] 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 together in one electronic package or chip.

[0051] 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 / or 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.

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

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

[0054] 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 any suitable memory such as a non-removable memory 130 and / or a removable memory 132, and store data in these memories. 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 subscription identity module (SIM) card, a memory stick, and a secure digital (SD) memory card, etc. 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).

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

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

[0057] 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 / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, frequency modulation (FM) radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, posture sensors, biometric sensors, and humidity sensors, etc.

[0058] The WTRU 102 may include a full-duplex radio for which 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 or simultaneous, etc. A full-duplex radio may include an interference management unit that reduces and / or substantially cancels 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)).

[0059] Figure 1C 1 is a system diagram illustrating 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.

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

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

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

[0063] 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 procedure for 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.

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

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

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

[0067] Although in Figures 1A-1D Although the WTRU is described as a wireless terminal, it should be appreciated that in certain typical embodiments, such a terminal may use (eg, temporarily or permanently) a wired communication interface with a communication network.

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

[0069] 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 may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. Here, the IBSS communication mode may also be referred to as an "ad-hoc" communication mode.

[0070] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit a beacon on a fixed channel (e.g., a primary channel). The primary channel may have a fixed width (e.g., a bandwidth of 20 MHz) or a dynamically set width set via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain 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, one STA (e.g., only one station) may transmit at any given time.

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

[0072] 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 media access control (MAC).

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

[0074] 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 frequency band remains idle and available for use, the entire available frequency band can be considered busy.

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

[0076] Figure 1D 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ NR 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.

[0077] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. 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 and / or 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).

[0078] 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 (SCS) may be different for different communications, 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., including different numbers of OFDM symbols and / or lasting different absolute time lengths).

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

[0080] Each gNB 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support network slicing, DC, implement interworking between NR and E-UTRA, route user plane data to user plane functions (UPFs) 184a, 184b, and route control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. Figure 1D As shown, gNB180a, 180b, and 180c can communicate with each other through the Xn interface.

[0081] Figure 1DThe illustrated CN 106 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 106, it should be understood that any of these elements may be owned and / or operated by entities other than the CN operator.

[0082] The AMF 182a, 182b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the 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 communications (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, and services for MTC access, etc. The AMF 182a / 182b may provide control plane functionality for switching between the RAN 104 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.

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

[0084] The UPF 184a, 184b can be connected to one or more gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which can provide the WTRUs 102a, 102b, 102c with access to packet-switched networks (e.g., the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multi-host PDU sessions, processing user plane QoS, buffering DL packets, and providing mobility anchor processing, etc.

[0085] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108 or may communicate therewith. 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. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the local data network (DN) 185a, 185b via the N3 interface connected to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b through the UPF 184a, 184b.

[0086] 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 emulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or one or more other devices described herein. An emulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device may be used to test other devices and / or emulate network and / or WTRU functions.

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

[0088] 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).

[0089] In NR, for data transmission, a transport block (TB) is a data transmission unit consisting of one or more code blocks (CBs). A CB is a portion of data associated with an error correction code block and a cyclic redundancy check (CRC). A code block group (CBG) is a group of CBs associated with a single bit for acknowledgement (ACK)-negative acknowledgement (NACK). A transport block can consist of multiple CBGs. The maximum number of CBGs per TB can be configured by higher layer signaling.

[0090] In NR and LTE, data transmission is usually dynamically scheduled by the gNB using downlink control information (DCI), which is sent over the physical downlink control channel (PDCCH). The time domain allocation for the physical uplink shared channel (PUSCH) can be scheduled by the following DCI.

[0091] The starting symbol S relative to the start of the slot and the number of consecutive symbols L counted from symbol S allocated to the PUSCH are determined from the start of the index line and the length indicator SLIV: If (L-1)≤7 then Equation 1 SLIV = 14·(L-1)+S Equation 2 otherwise SLIV = 14·(14-L+1)+(14-1-S) Equation 3 where 0 < L ≤ 14 - S Equation 4

[0092] In 5G NR, the downlink preemption procedure is specified as follows. If the WTRU is provided with the higher layer parameter DownlinkPreemption, the WTRU is configured with an interrupt radio network temporary identifier (INT-RNTI) provided by the higher layer parameter int-RNTI for monitoring the PDCCH that carries DCI format 2_1.

[0093] The WTRU may also be configured with a set of serving cells provided by the higher layer parameter INT-ConfigurationPerServingCell and a set of positions corresponding to fields in DCI format 2_1 provided by the higher layer parameter positionInDCI, where the higher layer parameter INT-ConfigurationPerServingCell includes a set of serving cell indices provided by the corresponding higher layer parameter servingCellId. In addition, the information payload size of DCI format 2_1 may be multiplied by the higher layer parameter dci-PayloadSize. Further, the WTRU may be additionally configured with an indication granularity for time-frequency resources provided by the higher layer parameter timeFrequencySet.

[0094] The content of the DCI carrying the "downlink preemption indication" indicates the frequency and time of the preempted resources, including the corresponding symbols.

[0095] In R15 power control, the PUSCH received power can be estimated as shown in Table 1. Table 1

[0096] In the fifth generation (5G) NR, new enhancements are needed to improve the reliability of URLLC UL transmissions. One of these enhancements is the option to cancel eMBB UL data transmissions when the URLLC WTRU needs resources.

[0097] The new enhancements and modifications described herein address these issues. These enhancements and modifications may be used alone or in any combination with each other.

[0098] In one problem, in NR, the Physical Uplink Control Channel (PUCCH) is used by the WTRU to transmit critical feedback information such as Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK), and Scheduling Request (SR) to a base station such as a gNB. In case the eMBB WTRU is configured with UL cancellation, the eMBB WTRU may need to cancel the UL transmission including PUCCH on time-frequency resources that overlap with the UL transmission from the URLLC WTRU. If the PUCCH is cancelled, the eMBB WTRU may not be able to send an SR to request an UL grant from the gNB or send an HARQ-ACK corresponding to the received PDSCH. In the latter case, the gNB cannot assume that the eMBB WTRU has correctly detected the DL packet sent in the corresponding PDSCH, so the gNB may need to retransmit the DL packet, which results in a loss of system throughput. Therefore, a mechanism is needed to ensure that the eMBB WTRU configured with UL cancellation is able to send basic feedback in the UL.

[0099] In another issue, in inter-UE eMBB and URLLC multiplexing, the gNB may send a cancellation indication (e.g., an indication sent in the PDCCH) to the eMBB WTRU to cancel its transmission for a duration, and send an end scheduling indication (e.g., a DCI transmitted in a WTRU-specific DCI) to the URLLC WTRU to use the canceled resources. For example, the indication may be sent in the GC-PDDCH. In another example, an indication for DCI format 2_4 with a CRC scrambled by the CI-RNTI may be sent in the PDCCH. The success or failure of the WTRU to decode the cancellation indication or the scheduling indication may affect the performance of the URLLC transmission. In the event of a failure to decode one or more indications, a method is needed to enable the URLLC WTRU transmission to resume, especially in cases where the delay requirements are very strict. The failure to decode one or more indications may be a failure to decode the cancellation indication, such as by the eMBB WTRU, or a failure to decode the scheduling indication, such as by the URLLC WTRU.

[0100] Another issue is how to design an efficient cancellation procedure and how to signal it to the eMBB user without using too much control resources and with a good tradeoff between signaling overhead and scheduling flexibility. A related issue is how the WTRU can monitor the cancellation indication in a timely manner without consuming a lot of power. In addition, given that a cancellation indication may be indicated on the GC-PDCCH signal, how does the eMBB WTRU determine that the indication applies to it, and how does the URLLC WTRU determine that the cancellation indication does not apply to it.

[0101] Another issue is how to support inter-WTRU uplink multiplexing / prioritization when URLLC WTRUs use ungranted UL transmissions or UL with configured grants. In this case, UL cancellation indication may not be feasible at the beginning because the gNB is not aware of the UL transmission until it detects it from the URLLC WTRU.

[0102] Another issue is how to generalize UL multiplexing / prioritization of UL transmissions using alternatives to PUSCH, such as physical random access channel (PRACH), sounding reference signal (SRS), or both. To apply UL multiplexing / prioritization to other channels, the main issue is how to design an efficient process that provides increased scheduling flexibility without excessive changes to the 5G NR system or specifications.

[0103] In another problem, when a carrier is configured in unmodified time division duplex (TDD) mode, the WTRU can only transmit (uplink) or receive (downlink) on a given time slot. For an eMBB WTRU, it becomes impossible to receive a cancellation indication while sending uplink data on the same carrier. One problem is how to indicate an uplink cancellation indication to the WTRU when the carrier is configured in TDD mode. A related problem includes how a cancellation indication can indicate a cancellation on a carrier different from the carrier used to receive the indication.

[0104] In another issue, it has been shown that enhanced UL power control can provide benefits when used for: inter-ULWTRU transmission prioritization / multiplexing; enhanced dynamic power boosting for URLLC WTRUs, including dynamic changes in power control parameters, such as P0 and α in the absence of a configured scheduling request indicator (SRI); and enhanced transmit power commands (TPC), such as increased TPC range and finer granularity. Note that the need for URLLC WTRU power changes during one transmission instance is not considered, and it is assumed that the eMBB WTRU power control scheme is not changed. Further benefits, such as no loss, have been observed when the gNB uses a successful interference cancellation (SIC) receiver to separate the transmissions. This may require that the channel estimates for both the eMBB WTRU and the URLLC WTRU are clear. In this case, methods are needed to ensure that the demodulation reference symbol (DMRS) or multiple DMRS can be separated with little or no interference.

[0105] In the following, reference symbols may be used to represent symbols such as complex numbers that are fixed, known, and used as pilots. Reference signals may be used to represent time domain signals generated after processing reference symbols. For example, in OFDM, reference symbols are complex numbers fed into an inverse discrete Fourier transform (IDFT) block, and reference signals are outputs of the IDFT block. In NR, a slot may be a unit of 14 OFDM symbols in a time grid. DCI may be a collection of bits transmitted for a user or user group via a PDCCH. A resource element (RE) may be an OFDM symbol on a subcarrier, and a resource element group (REG) may be a group of REs used as building blocks for control channel elements (CCEs) that can assign resource elements to users. REGs that are adjacent in time or frequency and are grouped together and have the same associated precoding are referred to as REG bundling.

[0106] In addition, NR-REG, NR-CCE and NR-PDCCH refer to REG, CCE and PDCCH for NR in 5G. WTRU and user can be used interchangeably, refer to the same thing and still be consistent with the examples provided herein. In addition, base station, g node B and gNB can be used interchangeably, refer to the same thing and still be consistent with the examples provided herein. A control resource set (CORESET) can be a set of resource elements for a downlink control channel, configured by its frequency resources and its time length and the type of its REG bundling. The CORESET time length can be represented by a symbol. A search space or search space set can be a set of PDCCH candidates monitored by a WTRU or a WTRU group during blind detection of a PDCCH. A code block (CB) can be a portion of data associated with one error correction code block and one CRC. A code block group (CBG) is a group of CBs associated with a single bit for ACK-NACK. A transport block (TB) can be a data transmission unit consisting of one or more CBs. In addition, a start and length indicator value (SLIV) can be a parameter for time domain allocation for data transmission.

[0107] The following embodiments, examples and solutions describe methods for PUCCH cancellation, which may be solutions to the above problems. These methods may be used alone or in any combination with each other.

[0108] A method of enhancing reliability, latency, or both of UL transmissions for URLLC users may be that a scheduler provides UL grants or configures PUCCH resources for URLLC WTRUs that overlap with time-frequency resources allocated by eMBB WTRUs for UL transmissions. In an example, the scheduler may be located at a base station or deeper in the network.

[0109] In one example, an eMBB WTRU may receive an indication to cancel uplink control information (UCI) transmission on a configured or dynamically indicated PUCCH resource, wherein the configured or dynamically indicated PUCCH resource fully or partially overlaps with a time-frequency resource configured by a URLLC WTRU for UL transmission. The indication may be sent implicitly or explicitly.

[0110] In another embodiment, an eMBB WTRU subject to UL cancellation may be configured with UCI information bit 0. UCI Two or more PUCCH resource sets for each range of payload. In an example, the range may include: UCI ≤2, 2 <O UCI ≤N2, N2 <O UCI ≤N3, N3 <O UCI ≤ 1706 bits, where N2 and N3 are provided by higher layers. In addition, during normal operation without UL cancellation, the WTRU may use the primary PUCCH resource set for UCI transmission. In addition, the WTRU may use the secondary PUCCH resource set for UCI.

[0111] In one exemplary method, if an eMBB WTRU detects an indication that a transmission from the WTRU on a particular physical resource block (PRB) and in a symbol should be cancelled, the WTRU may determine whether the indicated UL resources subject to cancellation overlap with the primary PUCCH resource set. The indication may be sent implicitly or explicitly.

[0112] If the resources overlap, the WTRU may block the transmission of UCI on the PUCCH resources belonging to the primary PUCCH resource set. In an example, such blocking of UCI transmission may be a PUCCH cancellation. The WTRU may then transmit the UCI on the PUCCH resources belonging to the secondary PUCCH resource set. Additionally or alternatively, the WTRU may multiplex the UCI with the data and transmit it on the grant-based PUSCH resources. Alternatively, in the case where the WTRU does not have an UL grant, the WTRU may transmit both data and UCI using configured PUSCH resources that do not overlap with the UL resources indicated to be subject to cancellation. In one example, the configured PUSCH resources may be grant-free UL resources.

[0113] In another example of an embodiment, an eMBB WTRU configured for UL cancellation may determine the PUCCH format based on an overlapping pattern between the PUCCH resources and the indicated PRBs and the symbols on which the WTRU cancels the UL transmission. According to the method, the WTRU may perform any of the following three operations, including any combination of these operations.

[0114] First, the WTRU may determine whether the indicated UL resources subject to cancellation overlap with a primary PUCCH format from a first set of PUCCH resources. Second, the WTRU may determine a secondary PUCCH format from a second set of PUCCH resources that do not overlap with the indicated UL resources subject to cancellation. Third, the WTRU may transmit UCI on a secondary PUCCH format according to the second set of PUCCH resources.

[0115] Figure 2 is a diagram showing an example PUCCH resource identification based on a UL cancellation indication. Figure 2 As shown in the example of 200 in FIG. 1 , the UL resources may include 14 symbols in a time slot in the time domain and up to 4 subcarriers in the system bandwidth (BW) in the frequency domain. Figure 2 As shown, the first 10 symbols may be allocated to PUSCH 210. The next two symbols may be allocated to a short PUCCH format, or primary PUCCH format 220, which may overlap with UL resources (e.g., resources used for a portion of PUSCH 210). The last two symbols may also be short PUCCH formats, where both of the last two symbols are allocated for primary PUCCH format 220. The last symbol may also be allocated to secondary PUCCH format 230.

[0116] exist Figure 2 In one example shown, a WTRU transmitting 1-2 UCI information bits may perform any of the following three actions. First, the WTRU may determine that the primary PUCCH format 220 is PUCCH format 1 on 4 symbols. For example, these 4 symbols may be allocated for a long PUCCH format. Second, the WTRU may determine that one or more symbols of the determined PUCCH format 1 220 overlap with the indicated UL resources subject to cancellation, e.g. Figure 2 The last 2 symbols shown in ; third, the WTRU may use PUCCH format 0 on 1 symbol, such as the short PUCCH format of the auxiliary PUCCH format 230 for UCI transmission of 1-2 bits.

[0117] In another example, a WTRU transmitting 1-2 UCI information bits may perform any of the following four actions. First, the WTRU may determine that the primary PUCCH format is PUCCH format 1, and the first symbol for PUCCH transmission provided by a higher layer. For example, the first symbol for PUCCH transmission may be provided by a parameter, such as startingSymbolIndex. Second, the WTRU may determine that one or more symbols of the determined PUCCH format 1 overlap with the indicated UL resource that is subject to cancellation. Third, the WTRU may use a shortened PUCCH format 1 with a different first symbol than that used for PUCCH transmission as a secondary PUCCH format. Fourth, the WTRU may determine that the first symbol of the secondary PUCCH format is greater than the first symbol of the primary PUCCH format.

[0118] A WTRU configured with multiple PUCCH resource sets may perform any of the following five actions. First, the WTRU may determine whether the indicated UL resources subject to cancellation overlap with the primary PUCCH format for a given PUCCH resource set. Second, the WTRU may sequentially check each PUCCH resource set by incrementing the PUCCH resource set index. For example, the WTRU may increment using pucch-ResourceSetId+1, where the pucch-ResourceSetId is provided by a higher layer. Also in the second action, additionally or alternatively, the WTRU may check a pre-specified list of PUCCH resource sets. Third, the WTRU may determine a secondary PUCCH format in each PUCCH resource set that does not overlap with the indicated UL resources subject to cancellation. Fourth, the WTRU may transmit UCI on a secondary PUCCH format from a secondary PUCCH resource set. Fifth, the WTRU may determine that the pucch-ResourceSetId of the secondary PUCCH format is greater than the pucch-ResourceSetId of the primary PUCCH format.

[0119] A WTRU configured with a single PUCCH resource set including a list of PUCCH resource indices (e.g., pucch-ResourceId) may perform any of five actions. First, the WTRU may determine whether the indicated UL resource subject to cancellation overlaps with the primary PUCCH format of the configured PUCCH resource set. Second, the WTRU may sequentially check each PUCCH resource in the configured PUCCH resource set by incrementing the PUCCH resource index. For example, the WTRU may increment using pucch-ResourceId+1, where pucch-ResourceId is provided by a higher layer. Also with respect to the second action, additionally or alternatively, the WTRU may check a pre-specified list of PUCCH resources. Third, the WTRU may determine a secondary PUCCH format in the configured PUCCH resource set that does not overlap with the indicated UL resource subject to cancellation. Fourth, the WTRU may transmit UCI on a secondary PUCCH format from the configured PUCCH resource set. Fifth, the WTRU may determine that the pucch-Resourceld of the secondary PUCCH format is greater than the pucch-Resourceld of the primary PUCCH format.

[0120] In one example of an embodiment, if a WTRU configured with dedicated PUCCH resources determines that the PUCCH resources overlap with the indicated UL resources subject to cancellation, the WTRU may use the configured PUCCH resources for transmitting HARQ-ACK information on the PUCCH in an initial UL bandwidth part (BWP).

[0121] In another embodiment, if the WTRU is configured with UL cancellation and supplemental (SUL), then the WTRU may transmit UCI on PUCCH resources configured on SUL even if the WTRU is configured by higher layers to transmit UCI on PUCCH resources on the primary / paired UL cell / carrier. The WTRU may be configured using implicit indication, explicit indication, or both.

[0122] In another embodiment, if the WTRU is configured with UL cancellation and multiple UL carriers / components, UCI may be transmitted on the PUCCH resources of the secondary UL cell / carrier, which may not be paired with the DL primary cell / carrier. The WTRU may be configured with implicit indication, explicit indication, or both.

[0123] Figure 3is a flow chart illustrating an example of a WTRU procedure for adaptation of PUCCH formats and PUCCH resources based on UL cancellation indication.As shown in the example of flow chart 300, an eMBB WTRU may receive a higher layer configuration 320 including a set of PUCCH formats and a corresponding set of UL control resources.

[0124] The eMBB WTRU may then receive a group common DCI (GC-DCI) indicating the cancelled time-frequency UL resources 330. In an example, the GC-DCI may indicate the cancelled time-frequency UL resources explicitly, implicitly, or both.

[0125] Thereafter, the eMBB WTRU may check or determine if there is an overlap with the resource set of the configured primary PUCCH format 350. If there is no overlap, the eMBB WTRU may transmit UCI using the configured primary PUCCH format on the corresponding UL control resource set 360. In an example, the process may end here.

[0126] If there is an overlap, the eMBB BWTRU may determine the secondary PUCCH format and the corresponding UL control resource set 370. The eMBB WTRU may then transmit the UCI 390 using the determined PUCCH format on the corresponding UL control resource set. In an example, the process would then end here. As can be seen, Figure 3 An example procedure is shown for an eMBB WTRU configured with multiple PUCCH formats and different corresponding UL resource sets.

[0127] The following example is an overlay method for eMBB WTRU cancellation and URLLC WTRU preemption where the cancellation / scheduling indication decoding fails. Multiple scenarios and examples are provided and can be used individually or in any combination with each other.

[0128] Four scenarios will be considered. The first scenario is that the cancellation indication decoding fails and the scheduling indication decoding succeeds. The second scenario is that the cancellation indication decoding succeeds and the scheduling indication decoding fails. The third scenario is that the cancellation indication decoding fails and the scheduling indication decoding fails. The fourth scenario is that the cancellation indication decoding succeeds and the scheduling indication decoding succeeds.

[0129] The first case where the decoding of the cancellation indication fails but the decoding of the scheduling indication succeeds is covered below. In this case, the eMBB WTRU continues to transmit and the URLLC WTRU also transmits in the resource assuming that the resource is unblocked. This may result in the failure of both the eMBB transmission and the URLLC transmission.

[0130] To ensure that the UL transmission from the URLLC WTRU is reliably received at the base station or gNB, the URLLC WTRU and / or the eMBB WTRU may assist the base station or gNB in ​​recognizing that the cancellation indication has failed to decode and that the eMBB WTRU is still continuing to transmit in the URLLC transmission resources; the UL cancellation was not successful. The base station or gNB may then take steps to correct the situation.

[0131] In one example of an embodiment, for a URLLC WTRU that assists in the identification of a successful cancellation, the URLLC WTRU may be configured with interference measurement resources (IMR) or zero power channel state information reference symbol (ZP CSI-RS) resources, where the URLLC WTRU is not transmitting on these resources and data is rate matched around them. This allows the base station or gNB to measure the energy / interference on these resources. The base station or gNB may compare the power level in the IMR resources with the power level in the eMBB-only resources and estimate that if the eMBB WTRU successfully stops transmitting, for example, there is a drop in power between the two resources, or if it fails to stop transmitting, for example, there is no change in power between the two resources.

[0132] In addition, in another example of an embodiment, the eMBB WTRU and the URLLC WTRU may jointly assist the base station or gNB in ​​identifying a successful cancellation. The URLLC may be configured with IMR resources or ZP CSI-RS resources, where the URLLC WTRU is not transmitting on these resources and the data is rate matched around them. The eMBB WTRU may be configured with a specific sequence, such as DMRS or CSI-RS. Whenever the eMBB WTRU detects a cancellation indication from the base station or gNB, the eMBB WTRU may send the sequence on the same IMR resources as the URLLC WTRU. This allows the base station or gNB to detect the sequence and verify that the cancellation has been successful, for example, if the eMBB WTRU successfully stops sending, for example, the sequence is detected, or if it fails to stop sending, for example, the sequence is not detected.

[0133] The transmission of a sequence by the eMBB WTRU in the IMR resources of the URLLC WTRU can serve two functions. The first function is to serve as a positive acknowledgement to the base station or gNB when a cancellation indication is received. The base station or gNB is able to recognize the sequence and knows that the eMBB WTRU has canceled its transmission.

[0134] The second feature allows the eMBB WTRU to resume transmission after a cancellation with no phase discontinuity between the original transmission and the resumed transmission. The sequence sent by the eMBB WTRU can help the base station or gNB to interpolate the channel estimate before and after the cancellation.

[0135] It should be noted that a dual solution would be the case where the eMBB WTRU is configured with an IMR resource or ZP CSI-RS and the URLLC WTRU sends a sequence in that resource. When the eMBB WTRU is cancelled and the URLLC WTRU reference signal (RS) is known at the base station or gNB, successful reception / detection of the URLLC WTRU reference signal (RS) may confirm that the URLLC WTRU has successfully received its scheduling indication. In an example, the scheduling indication may be an uplink grant.

[0136] Figure 4 is a diagram showing an example of an eMBB WTRU frame structure and a URLLC WTRU frame structure. Figure 4 As shown in the example of 400 in FIG. 4 , the eMBB WTRU frame structure and the URLLC WTRU frame structure may be used with IMR and sequences utilizing preemption. Figure 4 As shown, the eMBB WTRU may utilize the cancel indication (CI) to know whether the eMBB WTRU should stop sending eMBB data indicated by the stop resources procedure 420. The resume resources procedure may then enable the eMBB WTRU to resume data transmission, such as eMBB data 440, through any available resources (S1, S2, S3, or S4).

[0137] In addition, the URLLC WTRU may monitor using the system indicator (SI) 460 and the URLLC RS 470 and determine whether any available IMR resources the URLLC WTRU has require termination of data transmission or boosting of power on interrupted resources during the URLLC WTRU's preemptive transmission.

[0138] The eMBB WTRU may use the following exemplary process. The process may be divided into six steps. Any one or all of the six steps may be used. In addition, these steps may be used in any combination with each other.

[0139] In a first step, the WTRU may receive a higher layer configuration regarding an identification sequence to transmit during cancellation. This may be a WTRU specific sequence or a sequence common to all WTRUs.

[0140] In a second step, the WTRU may monitor and receive a CI, such as CI 410 .

[0141] In a third step, the WTRU may receive Embb WTRU sequence / resource specific information. This information may be separate from the CI. For example, the information may be received on a dedicated DCI. Additionally or alternatively, the information may be transmitted with the CI. For example, the information may be jointly encoded and received in the same DCI as the CI.

[0142] In addition, in the third step, the eMBB WTRU sequence configuration and / or resources may be explicitly signaled in the CI. The signal may be a configuration for a sequence, such as SCI-RS, and DMRS, etc., which may match the time-frequency pattern of one or more URLLC IMR resources for one or more URLLC WTRUs. The signal may be an index to a predefined table or an index to a radio resource control (RRC) configuration table.

[0143] Also in the third step, the eMBB WTRU sequence configuration may be implicitly signaled. For example, the configuration may be implicitly signaled by CI, DCI, and Radio Network Temporary Identifier (RNTI), etc. The signal may also include URLLC IMR resources to the eMBB WTRU for URLLC WTRU.

[0144] In a fourth step, the eMBB WTRU may stop data transmission during the cancelled resources. In an example, the data may be saved or buffered for later transmission.

[0145] In a fifth step, the eMBB WTRU may send an identification sequence in the resources corresponding to the IMR resources of the URLLC WTRU. In the case where the IMR resource length is shorter than the length of the identification sequence, the eMBB WTRU may send a subset of the identification sequence to the gNB, such as a truncated or sampled value of the sequence. In addition, in the case where the IMR resource length is longer than the length of the identification sequence, the eMBB WTRU may send a sequence of appropriate length derived from the identification sequence, such as a cyclic extension, to the gNB.

[0146] In the sixth step, the eMBB WTRU may stop transmission of its data, or may resume transmission of its data after the URLLC WTRU has stopped sending. If the eMBB WTRU resumes transmission, it should be noted. It may puncture the original transmission, or it may shift the original transmission to avoid the outgoing resources. The eMBB WTRU may continuously monitor for new CIs and ignore the current CI if a new CI arrives.

[0147] Still focusing on the situation where the cancellation indication decoding fails but the scheduling indication decoding succeeds, the URLLC WTRU can use the following process divided into four steps. Any one or all of the four steps can be used. In addition, these steps can be used in any combination with each other.

[0148] In a first step, the WTRU may receive a higher layer configuration to be used on the IMR resources during preemption transmission. The configuration may be received directly or indirectly. Additionally, the configuration may be received as an indication. The indication may be received implicitly, explicitly, or both.

[0149] In the second step, the WTRU may receive scheduling and transmission information, such as an uplink grant. This information may be separate from the CI and may be sent on a dedicated DCI. Alternatively or additionally, this information may be sent in a manner jointly encoded with the CI and sent in the same DCI.

[0150] In the third step, the WTRU may start URLLC transmission in the assigned resources. The WTRU may rate match its data around the IMR resources during the cancellation period.

[0151] In the fourth step, the WTRU may continue to monitor the CI, the scheduling indicator or both. This may be necessary in the case where the gNB recognizes the failure of the CI and wishes to terminate the transmission or, for example, increase the transmission power on the blackout resources.

[0152] Figure 5 is a flow chart illustrating an example process for an eMBB WTRU and a URLLC WTRU. The example process for an eMBB WTRU and a URLLC WTRU described above is Figure 5 As shown in the example of 500 in . For example, the eMBB WTRU may receive a higher layer configuration 510 for an identification sequence. The configuration may be received directly or indirectly. In addition, the configuration may be received as an indication. The indication may be received implicitly, explicitly, or both.

[0153] Next, the eMBB WTRU may monitor and receive the CI 530. Then, the eMBB WTRU may receive information specific to the eMBB WTRU sequence or resource 550. Next, the eMBB WTRU may stop normal transmission 555. Therefore, the eMBB WTRU may transmit an identification sequence in the resource corresponding to the URLLC IMR 570. In addition, the eMBB WTRU may continue to monitor during transmission in the event of a CI failure 575. Figure 5 As shown, the arrow indicates that the process may return to the receiving step 550 depending on whether the CI fails. Finally, the eMBB WTRU may resume transmission 590.

[0154] In addition, the URLLC WTRU may receive a higher layer configuration 520 for IMR resources. The configuration may be received directly or indirectly. In addition, the configuration may be received as an indication. The indication may be received implicitly, explicitly, or both.

[0155] Next, the URLLC WTRU may receive scheduling information and transmission information 540. Thereafter, the URLLC WTRU may start the URLLC transmission 560. Next, during the transmission, the URLLC WTRU may continue to monitor during the transmission in case of a CI failure 565. Finally, the URLLC WTRU may end the URLLC transmission 580.

[0156] In an example of an embodiment, a URLLC WTRU may assume a higher probability of failure of an eMBB cancellation indication and modify its transmission to adapt to the possibility of interference, for example by boosting its power or by transmitting at a lower MCS. The URLLC WTRU may be configured with multiple transmission parameter configurations, such as power level, and MCS, etc., and the scheduling DCI may indicate the appropriate configuration to use, for example based on the capabilities of the interfering eMBB WTRU or based on the aggregation level or reliability used to send the eMBB cancellation indication. This solution combines the WTRU cancellation and power methods in one solution.

[0157] In one example of an embodiment, the eMBB WTRU cancellation indication is sent with the same high reliability level as the URLLC scheduling indication. This ensures that the probability of failure of either indication is roughly the same. This is not possible if the two WTRUs have different capabilities.

[0158] The following solves the situation where the cancellation indication decoding is successful but the scheduling indication decoding fails. In the case where the cancellation indication decoding is successful but the scheduling indication decoding fails, the eMBB WTRU can stop its transmission, while the URLLC WTRU does not transmit in the unblocked resources. This leads to a waste of transmission resources.

[0159] In one example of an embodiment, the gNB can identify this situation by silence in the channel. Additionally or alternatively, the gNB can identify this scenario by identifying a sequence, such as RS, in a configured resource sent by the eMBB WTRU that overlaps with the IMR resources of the URLLC WTRU.

[0160] In this example, the gNB may restart the entire process, for example, sending a new cancellation and scheduling indicator to the WTRU. Additionally or alternatively, the gNB may send a new scheduling indicator to the URLLC WTRU if there are still sufficient resources for the URLLC WTRU to receive the indicator, decode the indicator, and send the URLLC WTRU data to the gNB.

[0161] The following example addresses the situation where the cancellation indication decoding fails and the scheduling indication decoding fails. In the case where the cancellation indication decoding fails and the scheduling indication decoding fails, the eMBB WTRU can continue its transmission while the URLLC WTRU does not transmit in unblocked resources. This is the result of a preemption failure.

[0162] Note that in the case where the eMBB WTRU is configured to send an identification sequence in the configured resources that overlap with the IMR resources of the URLLC WTRU, the gNB can identify this situation by the fact that there is no identifiable sequence from either the eMBB WTRU or the URLLC WTRU.

[0163] The following example addresses the case where the cancellation indication is decoded successfully and the scheduling indication is decoded successfully. In the case where the cancellation indication is decoded successfully and the scheduling indication is decoded successfully, the eMBB WTRU may be able to successfully decode the cancellation indication and the URLLC WTRU may be able to successfully decode the scheduling indication, the eMBB WTRU stops transmitting, and allows the URLLC WTRU to transmit in that resource. The eMBB WTRU may or may not resume transmission upon completion of the URLLC WTRU transmission. Note that these two indications may be sent separately or as one signal.

[0164] The following addresses behavior regarding successful reception of a CI. In an embodiment of behavior regarding successful reception of a CI, the eMBB WTRU may continue to monitor the scheduling indication resource even if it is scheduled to allow it to stop a cancellation period and restart another cancellation period in the event that the gNB assigns new resources, for example based on a preemption failure. This enables the gNB to recover from a failure scenario where it recognizes that there was a failure in the preemption process. Any information received by a successfully received CI overrides the information received by a previously received CI, even if the information from the previously received CI is still current. Upon recognition of a failure, the gNB may immediately restart the preemption process.

[0165] In another example of an embodiment, the URLLC WTRU may continue to monitor the scheduling indication resources even though it has been scheduled to allow it to terminate transmission and possibly restart another transmission if the gNB assigns new resources, for example based on a preemption failure. This enables the gNB to recover from a failure scenario where it recognizes that there was a failure in the preemption process. Any information received by a successfully received SI may overwrite information received by a previously received SI, even though the information from the previously received SI is still current. Upon recognition of a failure, the gNB may immediately restart the preemption process.

[0166] In another example of an embodiment, the eMBB WTRU may monitor multiple CIs from the gNB. The multiple CIs may all point to the same cancelled resources to reduce the probability of eMBB CI decoding failure.

[0167] In another example of an embodiment, the eMBB WTRU may monitor multiple CIs from the gNB. Each CI may point to a separate cancelled resource. The cancelled resources may be completely orthogonal or may overlap to reduce the latency of the URLLC WTRU transmission when identifying a failed preemption process.

[0168] An embodiment of a method for PUSCH cancellation indication via GC-DCI and corresponding PUSCH adaptation is covered below. In an embodiment, an example of indicating PUSCH cancellation via group common DCI is to explicitly indicate the cancelled / interrupted resources via GC-DCI and have a process for the eMBB WTRU to determine the cancellation of its PUSCH or its adaptation based on the modified set of resources.

[0169] As an example, for the case of UL transmission with configured authorization, the eMBB WTRU may determine the active set of UL resources for the UL configured authorization based on a combination of UL configured resource pools configured by higher layer signaling. The eMBB WTRU may also determine that the resource set for the dynamic indication cancellation may be explicitly indicated by the GC-PDCCH carrying the GC-DCI. For example, the cancellation indication may indicate a configured authorization index or a configured authorization group index. Upon receiving a cancellation indication indicating a certain configured authorization, the WTRU may cancel an ongoing transmission or an upcoming transmission on the indicated configured authorization. Finally, the eMBB WTRU may also determine a timer indicating the validity / expiration of the UL cancellation time period. In addition, the timer may be triggered by a MAC CE or DCI carrying the cancellation indication. A component carrier applicable to the cancellation may also be used.

[0170] Figure 6600 is a flow chart illustrating an example of an adaptive eMBB WTRU process for UL transmission with a configured grant in the presence of an explicit indication of a cancelled UL resource by a GC-DCI. As shown in the example in the flow chart 600, the eMBB WTRU may receive a higher layer configuration 620 including a set of resources for a UL configured grant. Next, the eMBB WTRU may receive a GC-DCI indicating the cancelled UL resources 630. Thus, the eMBB WTRU may determine or may check to see if there is an overlap with the set of resources for the UL configured grant 650. If there is no overlap, the eMBB WTRU may transmit a PUSCH with a configured grant on the configured set of resources 660. In an example, the WTRU may transmit based on a process in the NR. In other examples, the WTRU may transmit based on other processes. In an instance, the process may end here.

[0171] If there is an overlap, the eMBB WTRU may determine an active resource set for PUSCH transmission with a configured grant based on the configured resource set and the cancelled UL resources indicated by the GC-DCI 670. Additionally, if there is an overlap, the eMBB WTRU may transmit a PUSCH with a configured grant by using the determined active resource set instead of the configured resource set 690. In an example, the process may end here.

[0172] Figure 7 is a flow chart showing an example of an adaptive eMBB WTRU process for UL transmission with dynamic grant in the presence of an explicit indication of cancelled UL resources by GC-DCI. As an example, for the case of UL transmission with dynamic grant, the eMBB UE may determine an active set of UL resources based on a DCI indicating the resources in which the eMBB UE should transmit. A pool of UL dynamically indicated resources may be sent by a DCI. A cancelled set of resources may also be indicated dynamically. For example, the cancelled resources may be represented by a GC-PDCCH carrying a GC-DCI. For example, a dynamic grant may be sent with an identification index. The cancellation indication may indicate a specific dynamic grant based on the identification index. Upon receiving a cancellation indication indicating a certain dynamic grant or a set of dynamic grants, the WTRU may cancel an ongoing transmission or an upcoming transmission on the indicated dynamic grant.

[0173] A timer indicating the validity / expiration of the UL cancellation period may also be utilized. The timer may be triggered by a MAC CE or DCI carrying the cancellation indication. A component carrier applicable for cancellation may also be used.

[0174] like Figure 7As shown in the example of 700 in FIG. 1 , the eMBB WTRU may receive a DCI 720 including a resource set for a UL dynamic grant. Next, the eMBB WTRU may receive a GC-DCI 730 indicating the cancelled UL resources. Thus, the eMBB WTRU may determine or may check to see if there is an overlap with the resource set for the UL dynamic grant 750. If there is no overlap, the eMBB WTRU may transmit a PUSCH with a dynamic grant on the indicated resource set 760. In an example, the WTRU may transmit based on a process in the NR. In other examples, the WTRU may transmit based on other processes. In an example, the process may end here.

[0175] If there is an overlap, the eMBB WTRU may determine an active resource set for PUSCH transmission with dynamic grant based on the dynamic resource set and the cancelled UL resources indicated by the GC-DCI 770. In an example, the resource set may be a predetermined or pre-signaled resource set. Additionally, if there is an overlap, the eMBB WTRU may transmit PUSCH with dynamic grant by using the determined active resource set instead of the original resource set 790. In an example, the process may end here.

[0176] In an example of a method for indicating UL cancellation via GC-DCI, the WTRU may be provided by a higher layer parameter "UplinkCancellation" and configured with a specific RNTI, which may be referred to as "CAN-RNTI", for monitoring the GC-PDCCH delivering a GC-DCI indicating UL cancellation. The GC-DCI may have a specific format (e.g., DCI format 2_4) dedicated to UL cancellation indication. The DCI format 2_4 may be used to inform the WTRU of the PRB(s) and OFDM symbol(s) for which it may assume that no transmission is expected from the WTRU.

[0177] Additionally or alternatively, the WTRU may use the INT-RNTI used to monitor downlink preemption in order to also monitor UL cancellation. In this case, the DCI may be used to deliver downlink preemption and uplink cancellation indications. In the example, the DCI may be in DCI format 2_1 defined in the NR. In addition, the WTRU may determine which part of the DCI format 2_1 is indicating a downlink preemption indication or a UL cancellation indication, explicitly based on some higher layer configuration (e.g., when the WTRU is configured with UL cancellation and DL preemption at the same time, and / or implicitly based on other parameters, such as the DCI payload size, or based on additional fields in the DCI itself). In the above scenario, the following information may be transmitted by DCI format 2_1 using a CRC scrambled by the INT-RNTI: [Preemption indication 1,…, Preemption indication N, UL cancellation indication].

[0178] In case of being configured to monitor for UL cancellation, the WTRU may also be configured with a set of serving cells via a higher layer parameter CAN-ConfigurationPerServingCell, including a set of serving cell indices provided by a corresponding higher layer parameter servingCellId and a corresponding set of positions of fields in DCI format 2_3 provided by a higher layer parameter positionInDCI. In addition, the payload size of the GC-DCI delivering the UL cancellation indication may be semi-statically configured for the WTRU.

[0179] The GC-DCI for UL cancellation indication may carry a bit field or a bit string that may be mapped to the UL canceled resources that explicitly indicate the frequency and time of the canceled resources in the RB and OFDM symbols. The granularity of the time-frequency resources may be semi-statically configured by a higher layer. The configuration may be the same or different from the configuration of the parameter granularity of the time-frequency resources for downlink preemption indication. In one example, the granularity of the time-frequency resources may be configured by a higher layer parameter timeFrequencySet, which is also used as a downlink preemption indication. In one example, the bits of the UL cancellation indication may be grouped into several groups of the same size, and each group of bits corresponds to a subset of the frequency bandwidth, for example, a PRB subset of a bandwidth portion, or a symbol or a subset of symbols in a monitoring time period, or a combination of frequency and time subsets. In this case, the bits of each group may indicate a cancellation in the time-frequency resource subset.

[0180] Figure 8800 is a flow chart illustrating an example of a WTRU process for determining a set of cancelled resources based on a combination of semi-static configuration and dynamic indication through GC-DCI. As shown in the example of flow chart 800, another method for indicating cancelled resources through GC-DCI is to deliver information about the cancelled resources in the GC-DCI so that along with the configuration, the WTRU can determine the set of cancelled UL resources. As an example, a bit field in the GC-DCI may indicate a subset of frequency resources in the configured resources that corresponds to the cancellation. In this method, the frequency resources of the cancelled UL transmission are indicated relative to the configured set / pool of resources for the configured UL grant, rather than an explicit indication or an indication relative to the corresponding bandwidth portion.

[0181] Another issue in the example using a PUSCH cancellation indication is how to support resumption of PUSCH transmission after cancellation. One solution to support PUSCH cancellation with the possibility of automatic resumption by the WTRU is to indicate the resources used for the resumed UL transmission by signaling a time offset to be applied to the original grant. In the example, the time offset may be indicated based on one or more of slot / mini-slot / symbol / monitoring period. The time offset may be included in the cancellation indication as part of the DCI or may be implicitly obtained from other parts of the cancellation indication (e.g., the time resource corresponding to the cancellation).

[0182] As shown in the example of flow diagram 800, the WTRU may receive a higher layer configuration including a set of resources for a UL configured grant 820. Thereafter, the WTRU may receive a GC-DCI indicating additional information about the cancelled UL resources 830. Next, the WTRU may determine the cancelled UL resources based on the configured set of resources and the additional information about the cancelled UL resources 840. Thereafter, the WTRU may determine an active set of resources for PUSCH transmission with the configured grant by removing the cancelled UL resources 850. Additionally, the WTRU may transmit a PUSCH with the configured grant by using the determined active set of resources instead of the configured set of resources 890.

[0183] In some example solutions, the WTRU may be configured to monitor a continuation indication or CoI on at least one search space of the PDCCH. The WTRU may initiate or continue a transmission that overlaps with a particular time-frequency resource only if a continuation indication is received for that resource. Otherwise, the WTRU may not initiate a transmission or interrupt a transmission at least for the portion that overlaps with the resource, and possibly for any portion that occurs during or after the resource. The time-frequency resource may be signaled using one or more solutions or examples for canceling or preempting indications, such as those described herein. This approach has the benefit of enhancing protection of high priority transmissions, since failure of other WTRUs to decode the indication does not cause them to continue transmitting and interfering.

[0184] The confirmation indication may also be used to instruct the WTRU to perform the transmission using a non-reduced transmission power, or more generally to perform the transmission according to a first set of transmission power parameters. Otherwise, the WTRU may perform the transmission using a reduced transmission or according to a second set of transmission power parameters at least for the portion that overlaps on the resources or possibly for the entire duration of the transmission.

[0185] For example, the WTRU may be scheduled to perform a PUSCH, PRACH, PUCCH, or SRS transmission and determine that the transmission overlaps with at least one resource to which an acknowledgment indication relates. This determination may be based on a higher layer configuration indicating a set of resources that may recur in time and frequency and possibly in the time domain, together with a search space configuration for the corresponding acknowledgment indication. For example, the higher layer configuration may indicate a subset of time symbols and resource blocks within a timeslot, an identification of the search space including periodicity and offset, and possibly a parameter indicating a time offset between a decoded CoI and a corresponding set of resources. The acknowledgment indication may also indicate, for example using a bitmap, a subset of resources for which transmissions may be made in a corresponding set of resources, for example, resources within a timeslot and bandwidth portion. The WTRU may make a transmission that overlaps with a resource subject to an acknowledgment indication only upon receipt of such an acknowledgment indication for the resource.

[0186] This determination may be based on layer 1 signaling, RRC configuration, MAC-CE signaling, or a combination of all three signaling types. Layer 1 signaling may include, for example, a corresponding PDCCH or DCI, such as a WTRU-specific PDCCH or GC-PDCCH. The signaling may indicate a set of resources in the time domain and frequency domain and may be repeated in the time domain. The signaling may also contain a search space configuration for a corresponding confirmation indication, or may point to information configured at a higher layer, such as a search space table, to signal the information. For example, the signaling may indicate one or more of a subset of time symbols and resource blocks within a time slot, an identifier of a search space including periodicity and offset, and a parameter indicating a time offset between a decoded CoI and a corresponding set of resources. The confirmation indication may also indicate, for example, a subset of resources using a bitmap, for which transmissions may be performed in a set of corresponding resources (e.g., resources within a time slot and bandwidth portion). The WTRU may only perform transmissions overlapping with resources subject to the confirmation indication when a confirmation indication for the resource is received.

[0187] For any of the solutions described herein, such solutions may be applicable to situations where, instead of receiving a cancellation indication for a given resource or transmission, the WTRU fails to receive a confirmation indication for such resource or transmission when subject to confirmation.

[0188] Prioritization aspects are described herein. For example, the use of de- / confirmation of priority levels in inter-WTRU multiplexing is described below.

[0189] A priority level or transmission profile corresponding to, for example, eMBB or URLLC may be assigned for the transmission. The priority level may be obtained from the corresponding PDCCH or DCI, from the RRC configuration and / or from MAC signaling (e.g., MAC CE signaling). For example, in the case of HARQ-ACK, dynamic grant, or configuration grant type 2 for PUSCH, non-periodic SRS, the priority level may be obtained from the corresponding PDCCH or DCI. In another example, in the case of grant type 1 configured for PUSCH, scheduling request, the priority level may be obtained from the RRC configuration. In another example, in the case of a scheduling request or PUSCH, the priority may be obtained from MAC signaling (e.g., MAC CE signaling).

[0190] A cancellation indication (CI) or confirmation indication (CoI) may be assigned a priority level set indicating the applicability of transmission for a given priority level or priority index. For example, a cancellation indication may only apply to priority levels equal to or lower than a certain level. In an example, the priority level or priority index may be zero ("0") or one ("1"). In a further example, the priority level or priority index may correspond only to eMBB. Additionally or alternatively, another priority level or priority index may correspond to URLLC. The applicable priority level set may be configured by signaling to the WTRU together with a resource set that is subject to the cancellation or confirmation indication. In an example, the signaling may be MAC CE signaling. Additionally or alternatively, the signaling may be configured by RRC. For example, the RRC configuration may indicate whether the CI is applicable to all priority index values ​​or only to the lowest priority index, such as zero ("0"). Additionally or alternatively, the applicable priority level may be included as part of the CI itself or the CoI itself. For example, such an indication may be located in a field of the DCI or used by the C-RNTI to decode the PDCCH. In the case where only two priority levels are defined, the CI or CoI may implicitly apply only to transmissions of the lowest priority level. In this case, the WTRU may only monitor for indications for the lowest priority transmission.

[0191] In another example method, the WTRU may monitor the CI in a multi-step process to determine the resource allocation being canceled and / or whether it is applicable to the WTRU. For example, the WTRU may first monitor the GC-DCI in a first step, possibly on a pre-configured subset of CORESETs or search spaces. After receiving the first indication in the first step, the WTRU will then monitor the PDCCH on a second set of PDCCH resources, CORESET(s), search space(s) and / or DCI or RNTI formats to determine the resources applicable for cancellation, possibly at a finer granularity. In one example, the CI in the first step may further indicate the applicability of a WTRU subset, where the applicability is indicated according to a particular priority level, transmission profile, WTRU capabilities and / or RNTI value.

[0192] In one example, the WTRU may be configured with a number of transmission profiles or priority levels by a higher layer, such as an RRC configuration. The priority level may correspond to a priority index. The WTRU may determine the transmission profile or priority level for a given transmission based on priority level signaling, which indicates to the WTRU a portion of an RRC message or a portion of a DCI and is applicable to the transmission, such as a PUSCH transmission or a PUCCH transmission. The WTRU may alternatively determine the transmission profile or priority level based on the highest priority channel (LCH) mapped to the transmission or the LCH associated with the transmission or triggered the transmission. The WTRU may alternatively determine the transmission profile or priority level based on a semi-statically configured mapping between the LCH and the transmission profile, whereby the WTRU associates the transmission profile for the transmission according to the highest priority LCH mapped to the transmission, the highest priority LCH associated with the transmission, or the highest priority LCH that has triggered the transmission. The WTRU may also receive a CI with an associated priority or an associated transmission profile, which may be used by the WTRU to determine whether it is applicable to the WTRU.

[0193] In an example solution, the WTRU may be configured to monitor the CI before a transmission starts and / or between an instance of resource allocation DCI reception and the start of the PUSCH. The WTRU may also determine that resources applicable for cancellation have passed or have begun. The WTRU may monitor the CI based on the WTRU capabilities and / or the priority level of its scheduled transmissions, or the transmission profile of its scheduled transmissions. For example, the WTRU may monitor the CI only when the priority level associated with the transmission or the transmission profile associated with the transmission is below a certain threshold and / or the WTRU has certain capabilities. For example, in a case where the priority index of a transmission may be one of two possible values ​​such as 0 or 1, the CI may apply only to transmissions with priority index 0.

[0194] After receiving the CI, the WTRU may cancel the transmission if at least one of the following conditions is met: For example, if the WTRU determines that the CI is applicable to the WTRU, the WTRU may cancel the transmission.

[0195] In another example, if the WTRU determines that a transmission to be potentially cancelled overlaps with resources indicated in part of the CI, the WTRU may cancel the transmission.

[0196] In a further example, if the transmission profile of the potentially canceled transmission is lower than the transmission profile indicated by the cancel indication, the WTRU may cancel the transmission. In yet another example, if the transmission profile of the potentially canceled transmission is equal to or higher than the transmission profile indicated by the cancel indication, the WTRU may cancel the transmission.

[0197] In yet another example, the WTRU may cancel a transmission that is potentially to be canceled if the priority level of the transmission is lower than the priority level indicated by the CI.

[0198] In yet another example, the WTRU may cancel a transmission if it determines that the overlap in both the frequency and time domains is greater than a certain threshold, where the threshold is configured by a higher layer, depends on the size of the resources of the ongoing transmission, or is determined by both.

[0199] In yet another embodiment, the WTRU may cancel a transmission if the WTRU receives the CI at least a minimum processing time before the start time applicable for cancellation. The WTRU may be specified or configured with multiple cancellation points, whereby the WTRU may apply the next cancellation point that is at least the minimum processing time away from the time instance at which it received the CI. For example, the WTRU may be specified to cancel the PUSCH transmission for a number of symbols from the instance at which the WTRU receives the CI. In an example, the number of symbols may be 3 symbols.

[0200] If the WTRU receives a CI before starting a PUSCH transmission or PUCCH transmission to be cancelled, the WTRU may perform at least one of the following procedures. In addition, if the WTRU receives a CI before a certain minimum processing time from the start of the transmission, the WTRU may perform at least one of the following procedures.

[0201] The WTRU may generate a CBG-based PUSCH transmission for a CBG that does not overlap with the resources indicated by the CI. In addition, if the PUSCH cannot be partially sent, the WTRU may not generate a MAC PDU for the PUSCH grant.

[0202] In addition, if the transmission has not yet started, the WTRU may determine alternative, additional or overflow resources for transmitting the PDU or UCI. For example, after determining that the CI refers to a certain configured grant index, the WTRU may select another configured grant with the same transport block size (TBS) if the selected configured grant satisfies the configured channel prioritization (LCP) constraints for the LCH included in the PDU.

[0203] In an example, upon receiving a CI with a lower priority level than the priority level of a transmission that is potentially to be cancelled, the WTRU may adjust its transmit power or apply a different set of power control parameters to the transmission. In another example, upon receiving a CI with a lower priority level than the priority level of a transmission that is potentially to be cancelled, the WTRU may adjust its transmit power or apply a different set of power control parameters to the transmission. Such adjustment applied may be further conditioned on receiving the CI before the start of the PUSCH transmission or PUCCH transmission to be cancelled, or before a certain minimum processing time from the start of the transmission.

[0204] Fig. 9 is a diagram showing an example of a WTRU canceling an uplink transmission based on a CI. As shown in example 900 of the diagram, the WTRU may receive a higher layer configuration for the CI. Specifically, the WTRU may receive a first higher layer configuration for the CI, the first higher layer configuration including a reference frequency resource set. In a further example, the first higher layer configuration may include an applicable maximum priority. In addition, in a case where the priority index of a transmission may be one of two possible values, the higher layer configuration may indicate whether the CI applies only to low priority transmissions or to transmissions that are not related to their priority level. In the example, the low priority may apply to priority index 0.

[0205] In addition, the WTRU may receive a grant indicating a frequency allocation and a time allocation for a scheduled transmission. In addition, the grant may include a priority indication or a priority index. In an example, the grant may include at least one of downlink control information (DCI), a dynamic grant, a configuration grant, a radio point resource control (RRC) signaling, or a second higher layer configuration.

[0206] In an example, the WTRU may receive a DCI including a priority indication or a priority index. The DCI may indicate that the WTRU is scheduled to perform a transmission. In an example, the priority indication or the priority index may indicate the priority of the scheduled transmission. In addition, the DCI may indicate resources allocated for the scheduled transmission. For example, the DCI may indicate a frequency allocation for the scheduled transmission. In addition, the DCI may indicate a time allocation for the scheduled transmission.

[0207] In an example, the WTRU may determine whether the WTRU is scheduled to perform a high priority transmission or a low priority transmission 910. If the WTRU is scheduled to perform a high priority transmission 930, the WTRU may transmit the high priority transmission based on the DCI 950. Therefore, no configured CI may be applicable to such a high priority transmission. In addition, if a high priority transmission is scheduled, the WTRU may not monitor the CI. In addition, the WTRU may not interrupt its scheduled high priority transmission. In an example, the high priority transmission may be a transmission performed on the PUSCH. In another example, the high priority transmission may be a transmission performed on the PUCCH. In an example, the high priority transmission may be a URLLC transmission.

[0208] If the WTRU is scheduled to perform a low priority transmission 920, the WTRU may detect a CI 960. The WTRU may receive the CI 960 and may decode the CI. In addition, the CI may indicate that the configured resources overlap with the scheduled transmission. In an example, the configured resources may be frequency resources. In another instance, the CI 960 may indicate that a subset of the configured resources overlaps with the scheduled transmission. For example, the CI 960 may indicate a subset of frequency resources in a reference frequency resource set for each time symbol in a time symbol set, wherein the scheduled transmission is canceled on the subset of frequency resources that overlaps with the frequency allocation for the scheduled transmission. In an example, the scheduled transmission may be canceled in the case where the subset of frequency resources in the time symbol set overlaps with the frequency allocation and time allocation for the scheduled transmission. In a specific example, the entire scheduled transmission may be canceled in this way. In yet another example, the CI may include an applicable maximum priority.

[0209] Thus, the WTRU may transmit a portion of a low priority transmission 980 and interrupt or cancel a portion or all of the transmission 990 indicated by the CI as overlapping. In an example, the low priority transmission may be a transmission made on the PUSCH. In another example, the low priority transmission may be a transmission made on the PUCCH. Furthermore, the transmission may be a URLLC transmission. Additionally or alternatively, the transmission may be an eMBB transmission.

[0210] In a further example, the WTRU may start monitoring the CI before receiving the CI 960. For example, the CI 940 and the CI 945 may be sent by the network to other WTRUs, and the WTRUs may determine not to use the CI 940 and the CI 945. In an additional example, the WTRU may start monitoring the CI if the frequency allocation of the WTRU transmission overlaps with the reference frequency resources. In a further example, the WTRU may start monitoring the CI if the priority of the WTRU transmission is less than or equal to the applicable maximum priority.

[0211] In addition, the grant may include a priority index, and under the further condition that the priority index of the transmission is determined to be less than an applicable maximum priority, the scheduled transmission may be interrupted. In addition, the first higher layer configuration may include an applicable maximum priority. In addition, the first higher layer configuration may include a first indication. In addition, it may be determined based on receiving the first indication that the priority index of the transmission is less than the applicable maximum priority. In an example, in a case where the priority of the scheduled transmission is less than or equal to the applicable maximum priority, the WTRU may cancel all or part of the scheduled transmission indicated as overlapping. In a further example, in a case where the priority of the scheduled transmission is less than or equal to the applicable maximum priority, the WTRU may interrupt the scheduled transmission indicated as overlapping.

[0212] Furthermore, the first higher layer configuration may include a second indication, and wherein the scheduled transmission is interrupted based on receipt of the second indication.

[0213] In an example, a lower priority may be indicated by a lower numerical value in the priority indication. For example, a lower priority may be indicated by 1, while a higher priority may be indicated by 0.

[0214] In another example, a higher priority may be indicated by a lower numerical value in the priority indication. For example, a higher priority may be indicated by 1, while a lower priority may be indicated by 0.

[0215] In an example, the WTRU may cancel all or part of a scheduled transmission indicated as overlapping if the priority of the scheduled transmission is less than or equal to the priority of a transmission scheduled by another WTRU. In a further example, a scheduled transmission indicated as overlapping is interrupted if the priority of the scheduled transmission is less than or equal to the priority of a transmission scheduled by another WTRU.

[0216] In certain exemplary cases, for example, when the transmission has not yet started for a configured grant for the eMBB WTRU, the network may not be aware that the WTRU has cancelled the PUSCH transmission. After receiving the CI for the initial transmission for a configured grant, if the WTRU determines that it cannot use such configured grant resource(s), the WTRU may perform at least one of the following procedures.

[0217] The WTRU may trigger, for example, a new buffer status report (BSR) or a new SR for the highest priority LCH mapped to the cancelled PDU. Such a new BSR or new SR may also depend on the pending BSR or SR being cancelled due to the inclusion of a BSR MAC CE in the cancelled PDU. For example, the WTRU may trigger a new BSR instead of a BSR that was cancelled due to the inclusion of a BSR MAC on a PDU that was discarded due to an inter-WTRU cancellation.

[0218] The WTRU may generate an autonomous retransmission for the cancelled PDU at the next CG occasion of the CG with the same TBS. If the WTRU has stored the PDU in a certain HARQ process identification (PID) buffer, the WTRU may generate an autonomous retransmission at the next CG occasion applicable to the HARQ PID. If the WTRU does not have the PDU stored in a certain HARQ PID buffer, the WTRU may select an applicable upcoming CG occasion with the same or different HARQ process.

[0219] The WTRU may start a timer. After stopping the timer or after the timer expires, the WTRU may perform any of the above actions. The WTRU may stop the timer upon receiving a dynamic grant applicable to the cancelled PDU (e.g., indicating the same HARQ PID).

[0220] Additionally, the WTRU may start a configured grant timer applicable to the configured grant and corresponding HARQ process ID initially selected for the cancelled transmission. Additionally, the WTRU may maintain the RV number for the cancelled PDU.

[0221] In certain exemplary scenarios, the WTRU may incorrectly decode a resource allocation indicated by a cancellation indication. The WTRU may incorrectly cancel a transmission even though the network is not aware of the cancellation. After receiving a cancellation indication and / or canceling a transmission, the WTRU may perform at least one of the following procedures.

[0222] The WTRU may trigger, for example, a new BSR or a new SR for the highest priority LCH mapped to the cancelled PDU. Such a new BSR or a new SR may further depend on whether a pending BSR or SR is cancelled due to the inclusion of a BSR MAC CE in the cancelled PDU.

[0223] The WTRU may generate an autonomous retransmission of the cancelled PDU at the next CG occasion for the CG with the same TBS. If the WTRU has stored the PDU in a certain HARQ PID buffer, the WTRU may generate an autonomous retransmission at the next CG occasion applicable to that HARQ PID. If the WTRU does not have the PDU stored in a certain HARQ PID buffer, the WTRU may select an applicable upcoming CG occasion with a different HARQ process.

[0224] The WTRU may start a timer. After stopping the timer or after the timer expires, the WTRU may perform any of the above actions. The WTRU may stop the timer upon receiving a dynamic grant applicable to the cancelled PDU (e.g., indicating the same HARQ PID).

[0225] Efficient monitoring details may be configured in the examples provided herein.To reduce monitoring overhead, the network or base station may group transmission types to the WTRU.

[0226] Fig.10 1000, to reduce the monitoring overhead of GC-PDCCH signaling on the eMBB WTRU for UL cancellation, the gNB may signal information about the likelihood of a URLLC transmission occurring. This may be combined with a CI search space configuration to limit the overall CI monitoring of resources where a URLLC WTRU transmission may exist. For example, the gNB may combine information about a URLLC WTRU transmission configuration likelihood or probability 1020 with a URLLC WTRU cancellation monitoring configuration 1040 to create a URLLC WTRU cancellation monitoring message 1060.

[0227] Fig.11 1 is a diagram showing an example of effective cancellation of monitoring. As shown in example 1100 in the figure, the WTRU has only 4 monitoring opportunities (e.g., opportunities 1141 to 1144) instead of 10 monitoring opportunities (e.g., opportunities 1121 to 1130) based on the combination of the URLLC WTRU cancellation monitoring configuration (opportunities 1121 to 1130) and the URLLC WTRU transmission configuration (opportunities 1101 to 1111).

[0228] The URLLC WTRU transmission configuration may be dynamically sent to the eMBB WTRU using a WTRU-specific signal. For example, the WTRU-specific signal may be a WTRU-specific PDCCH. In another example, the WTRU-specific signal may be part of the DCI that schedules the WTRU. The URLLC WTRU transmission configuration may be dynamically sent to the eMBB WTRU using a group signal such as the GC-PDCCH. The URLLC WTRU transmission configuration may be semi-statically or statically sent to the eMBB WTRU using RRC configuration or MAC-CE transmission. The signal may indicate parameters such as the start, stop, periodicity, and / or frequency resources of a CG dynamic grant (DG) URLLC transmission, which may interrupt the transmission of a CG or DG eMBB WTRU.

[0229] The following exemplary scenarios may be used. eMBB WTRU URLLC WTRU Configured Authorization (CG) Configured Authorization (CG) Configured Authorization (CG) Dynamic Grant (DG) Dynamic Grant (DG) Configured Authorization (CG) Dynamic Grant (DG) Dynamic Grant (DG)

[0230] For eMBB CG WTRUs and URLLC CG WTRUs with possible cancellation, the eMBB CG WTRU scheduled in the resources that have been configured for the URLLC CG WTRU may monitor cancellation indications only in resources where there is overlap. The eMBB CG WTRU may require signaling to identify the resources in which the URLLC CG WTRU may transmit. This enables it to monitor cancellation signals when there is overlap and reduce monitoring overhead. The signaling to the eMBB WTRU may include parameters such as frequency resources, time resources or transmission duration, and periodicity of the URLLC WTRU CG resources.

[0231] For grant scheduling of type 1 and type 2 configurations for the eMBB CG WTRU, the information may be signaled as part of the RRC configuration signaling (type 1) or activation signaling (type 2). This is particularly applicable in the case where the eMBB CG WTRU is configured or activated after the URLLC WTRU is configured or activated. For grant scheduling of type 1 and type 2 configurations for the eMBB WTRU, the information may be explicitly signaled to the eMBB CG WTRU as an additional monitoring configuration. This is particularly applicable in the case where the eMBB CG WTRU is configured or activated before the URLLC WTRU is configured or activated. It may also be applicable in the case where the design wishes to keep the cancellation of monitoring configuration / activation separate from the transmission configuration / activation.

[0232] In one example, an eMBB DG WTRU or a set of eMBB DG WTRUs may receive a monitoring activation / deactivation signal at a configured or predefined time, indicating the resources where monitoring cancellation should be activated or deactivated. An eMBB CG WTRU or a set of eMBB CG WTRUs may monitor cancellation when URLLC resources are active.

[0233] Fig.12 1200, an eMBB CG WTRU and a URLLC CG WTRU may receive eMBB cancellation monitoring signaling 1205. The monitoring signaling may identify URLLC CG resources, such as URLLC CG resources 1210, 1220, 1230, 1240, 1250, 1260, on which the URLLC CG WTRU may transmit. The eMBB CG resources, such as eMBB CG resources 1270, 1280, 1290, may overlap with the URLLC CG resources, such as at overlapping resources 1271, 1272, 1283, 1284, 1295, 1296, which enables the eMBB CG WTRU to monitor cancellation or turn on eMBB cancellation monitoring at 1215, 1225, 1235, 1245, 1255, 1265.

[0234] Fig.13 is a diagram showing an example of an eMBB DG WTRU and a URLLC CG WTRU with cancellation based on a configured interval. As shown in the example 1300 in the figure, for an eMBB DG WTRU and a URLLC CG WTRU with cancellation, the eMBB DG WTRU may be scheduled in the resources that have been configured for the URLLC CG WTRU. In addition, the eMBB DG WTRU may monitor the cancellation indication only within their overlapping resources. The eMBB DG WTRU may require signaling to identify the resources in which the URLLC CG WTRU may transmit. This enables monitoring of cancellation signals when there is an overlap and reduces monitoring overhead. The signaling to the eMBB WTRU may include parameters such as frequency resources, time resources or transmission duration, and periodicity of the URLLC WTRU CG resources. Note that the periodicity may be required in the case where the eMBB resources may be transmitted across multiple URLLC CG WTRUs.

[0235] The information may be explicitly signaled to the eMBB DG WTRU as an additional monitoring configuration or as part of the DCI that schedules the DG transmission, such as WTRU-specific signaling. The information may be explicitly sent to all eMBB WTRUs, such as the CG WTRU and the DG WTRU, simultaneously, and the eMBB WTRUs may combine the information with their scheduling information to decide whether de-monitoring may be activated in certain resources. For example, the information may be group signaling such as GC-PDCCH signaling or a group-based sequence. In an example, the information may be grouped eMBB de-monitoring signaling 1305, such as GC-PDCCH signaling.

[0236] In this case, the gNB may send signaling at appropriate intervals to notify all WTRUs of the de-monitoring resources for the subsequent duration. In one example, an eMBB DG WTRU or a set of eMBB DG WTRUs may receive a monitoring activation / deactivation signal at a configured or predefined time, wherein the configured or predefined time indicates the resources at which de-monitoring should be activated or deactivated. For example, a URLLC CG WTRU may be scheduled with URLLC CG resources 1310, 1320, 1330, 1340, 1350, 1360, a first eMBB DG WTRU may be scheduled with eMBB DG resources 1370, and a second eMBB DG WTRU may be scheduled with eMBB DG resources 1380. The first eMBB DG WTRU and the second eMBB DG WTRU may perform de-monitoring at 1335, 1345, 1355.

[0237] In an example, the eMBB CG WTRU uses cancellation of resources based on URLLC DG WTRU resources that are prohibited for the URLLC DG WTRU. In an example, the eMBB CG WTRU that may have URLLC DG WTRUs scheduled in the resources it sends may need to monitor cancellation indications within resources where overlap may exist. The eMBB CG WTRU may require signaling to identify the resources in which the URLLC DG WTRU can transmit. The scheduling may enable the eMBB C G WTRU to monitor cancellation signals when there is overlap and reduce monitoring overhead. The signaling to the eMBB WTRU may include parameters such as frequency resources and time resources within which the URLLC DG WTRU may be scheduled.

[0238] The resources dedicated to the eMBB CG WTRU may be set to be prohibited for the URLLC DG WTRU to prevent the need for the eMBB CG WTRU to have to monitor the cancellation indication. In addition, the resources dedicated to the eMBB CG WTRU may be set to be allowable for the URLLC DG WTRU to ensure that the eMBB CG WTRU can always monitor the cancellation indication. The resources dedicated to the eMBB CG WTRU may be partitioned to have prohibited and allowable resources for the URLLC DG WTRU to ensure that the eMBB CG WTRU always monitors the cancellation indication within the allowable resources.

[0239] In an example, the signaling used to enable identification of allowable resources and prohibited resources may be WTRU-specific. For example, the allowable / prohibited resources may be configured as part of the CG configuration and may be WTRU-specific. In another example, the signaling to enable this may be common to multiple WTRUs, the GC-PDCCH signal.

[0240] Fig.14 1400 is a diagram showing an eMBB CG WTRU and a URLLC DG WTRU with cancellation and with WTRU-specific configuration using allowed resources and prohibited resources. As shown in the example 1400 of the figure, the eMBB CG WTRU may receive a CG configuration 1405 including allowed and prohibited resources. The configuration 1405 may set the eMBB CG resources 1410, 1430, 1450 to be prohibited for URLLC DG WTRU transmissions and may set the eMBB CG resources 1420, 1440, 1460 to be allowed for URLLC DG WTRU transmissions. Therefore, the eMBB DG WTRU may perform cancellation monitoring on 1425, 1445, 1465.

[0241] Fig.15is a diagram showing an eMBB CG WTRU and a URLLC DG WTRU with a WTRU configuration with cancellation and grouping using allowed resources and prohibited resources. As shown in the example 1500 in the figure, the eMBB CG WTRU may receive a configuration including allowed and prohibited resources 1505. In one instance, the configuration 1505 may be signaled via the GC-PDCCH. The configuration 1505 may schedule resources 1530, 1550, 1570 as eMBB CG resources for a first eMBB WTRU, and may schedule resources 1520, 1560 as eMBB CG resources for a second eMBB WTRU. In addition, the configuration 1505 may set the eMBB CG resources 1540 to be allowed for URLLC DG WTRU transmissions. For example, for the first eMBB WTRU, resources 1537 of the eMBB CG resources 1530 and resources 1557 of the eMBB CG resources 1550 may be set to be allowable. In addition, for the second eMBB WTRU, resource 1527 of the eMBB CG resource 1520 may be set as allowable. Therefore, the first eMBB DG WTRU may perform cancellation monitoring at 1535, 1555, and the second eMBB DG WTRU may perform cancellation monitoring at 1510. The above example may also be applied to the eMBB DG WTRU-URLLC DG WTRU scenario.

[0242] For the example of using an eMBB DG WTRU and a URLLC DG WTRU with cancellation, the eMBB DG WTRU in whose resources the URLLC DG WTRU is scheduled may need to monitor for cancellation indications within the resources where they may overlap. The eMBB DG WTRU may require signaling to identify the resources in which the URLLC DG WTRU may transmit. The signaling may enable the eMBB DG WTRU to monitor for cancellation signals when there is overlap and reduce monitoring overhead. The signaling to the eMBB WTRU may include parameters such as frequency resources and time resources within which the URLLC DG WTRU may be scheduled.

[0243] The resources in which the eMBB DG WTRU may transmit may be set to be prohibited to the URLLC DG WTRU to avoid the need for the eMBB DG WTRU to have to monitor for cancellation indications. The resources in which the eMBB DG WTRU may transmit may be set to be allowable to the URLLC DG WTRU to ensure that the eMBB DG WTRU may always monitor for cancellation indications.

[0244] The resources in which the eMBB DG WTRU may transmit may be segmented into resources that are prohibited and allowed for the URLLC DG WTRU to ensure that the eMBB DG WTRU may monitor for cancellation indications only within the allowed resources. In an example, the signaling to enable this operation may be WTRU specific. The allowed / prohibited resources may be sent as part of the DCI that schedules the transmission. The signaling to achieve this may be common to multiple WTRUs (e.g., GC-PDCCH) and may be communicated via e.g. Fig.15 The separate mechanism shown is used for transmission.

[0245] Methods for autonomous hybrid power control and UL cancellation for WTRUs are described herein. For the case of ungranted uplink transmissions by URLLC WTRUs, e.g., with a configured grant, it is not practical to send a cancellation indication from the gNB at the start of the transmission because the gNB must know whether the URLLC WTRU will use the resource. One solution to support inter-WTRU UL multiplexing between URLLC and eMBB WTRUs in this case is to use one or more power controls, different MCSs, and / or transmission modes in UL time periods and / or time slots where an UL cancellation indication is not feasible, such as at an initial transmission. The gNB may send an UL cancellation signal at a later time during the transmission.

[0246] In one example of an embodiment of the method, a URLLC WTRU may be configured with two or more UL transmission modes for unauthorized UL transmission of a PUSCH, for example, a congested mode or a non-congested mode. In one example, each mode may correspond to a set of power control parameters, a modulation and coding scheme (MCS), and / or other transmission-related parameters. The selection of congested mode transmission and non-congested mode transmission by the URLLC WTRU may be completed based on the absence or presence of a UL cancellation indication, respectively. As an example, in the absence of UL cancellation, the URLLC WTRU may start transmission using transmission parameters corresponding to the congested mode. The start of such transmission may include transmission at a higher power level and / or a lower rate. In a continuous time slot / micro time slot and / or UL time period, if the URLLC WTRU receives UL scheduling from the gNB, it may switch to authorization-based UL transmission using parameters based on scheduling information. Otherwise, if the URLLC WTRU does not receive a WTRU-specific DCI for UL transmission, but the URLLC WTRU detects a UL cancellation indication in the GC-DCI, the URLLC WTRU may continue with unauthorized UL transmission but use parameters corresponding to the non-congested transmission mode, as shown in the example below.

[0247] Fig.1616 is a flowchart illustrating an example of a URLLC WTRU process for selecting a transmission mode in an ungranted UL transmission. As shown in the example 1600 of the flowchart, the URLLC WTRU may receive a higher layer configuration including a set of granted resources for the UL configuration and parameters for both congested and non-congested transmission modes 1620. Next, the URLLC WTRU may monitor the GC-DCI for the UL resources indicating the cancellation 1630. Thereafter, the URLLC WTRU may determine whether the UL cancellation may be used for the next timeslot, mini-timeslot, or UL time period 1650. If there is no cancellation, the URLLC WTRU may transmit PUSCH 1660 on the configured resources using transmission parameters corresponding to the congested transmission mode (e.g., power control parameters and MCS). If there is a cancellation, the URLLC WTRU may transmit PUSCH 1670 on the configured resources using transmission parameters corresponding to the non-congested transmission mode (e.g., power control parameters and MCS).

[0248] In one example of the method, the URLLC WTRU may start a new UL ungranted transmission in non-congested mode transmission as long as the previously monitored UL cancellation is still valid. For example, a URLLC WTRU may start an ungranted uplink transmission in time slot 0 and receive an UL cancellation indication in time slot 1 indicating a UL cancellation within 4 time slots and may complete the transmission of the UL data in time slot 1. In this case, the URLLC WTRU may start another ungranted UL transmission with non-congested transmission mode parameters in time slot 2, time slot 3, or time slot 4, as shown in the following example.

[0249] Fig.17 is a diagram showing an example of an unlicensed UL transmission performed by a URLLC WTRU in a congested and non-congested transmission mode based on the presence of an UL cancellation indication. As shown in the example 1700 in the figure, UL transmission (one or more) may be performed on five time slots or portions. In time slot 0 or portion 1710, the URLLC WTRU may begin an unlicensed uplink transmission 1715. In addition, in time slot 1 or portion 1720, an UL cancellation request or cancellation indication 1722 may be sent by the gNB and received by the URLLC WTRU. Time slots 2-4, or portions 1730, 1740, 1750 may be used by the URLLC WTRU to perform unlicensed transmission (one or more) in a non-congested transmission mode. For example, the URLLC WTRU may transmit an unlicensed transmission 1748 in time slot 3 or portion 1740. In addition, the URLLC WTRU may transmit an unlicensed transmission 1758 in time slot 4 or portion 1750. The URLLC WTRU may transmit an unlicensed transmission 1728 in time slot 1 or portion 1720.

[0250] In one method, the URLLC WTRU may switch between congested mode and non-congested mode based on possible eMBB WTRU transmissions. In addition, the URLLC WTRU may switch between congested mode and non-congested mode in predefined time-frequency segments after sending a configured grant to the gNB. In addition, the URLLC WTRU may switch between congested mode and non-congested mode in possible time-frequency shared segments where eMBB and URLLC traffic may be transmitted simultaneously.

[0251] Methods for PRACH cancellation or modification are described herein. One method to enhance the reliability of UL transmissions for URLLC users is to allow those users to transmit on resources allocated to the eMBB WTRU for PRACH transmission. In this case, there should be some procedures to avoid PRACH transmissions by the eMBB WTRU on occupied resources.

[0252] An example of an embodiment includes forming an eMBB WTRU to modify or adjust their PRACH transmissions to avoid conflict with the interrupted URLLC transmission. In the method, the eMBB WTRU may be configured with multiple PRACH formats, the PRACH formats having different corresponding resource sets. As an example, the eMBB WTRU may be configured with two PRACH formats, F1 and F2, where F2 may have a shorter length, and in the event of a resource conflict with a PRACH resource corresponding to format F1 based on a received UL cancel indication, the WTRU may determine that it should use F2, such as Fig.18 As shown. This configuration may be done using a SIB2 message or another higher layer signaling. In another example, if the resources corresponding to the configured format F1 overlap with the cancelled UL resources, the eMBB WTRU may switch to a default PRACH format of format 0 instead of being configured with a PRACH format of F2.

[0253] Fig.181800 is a flow chart illustrating an example of a WTRU process for PRACH format and resource adaptation based on a dynamic UL cancellation indication. As shown in the example 1800 of the flow chart, the WTRU may receive a set of PRACH formats F1 and F2 and a configuration of corresponding PRACH resources in a SIB2 message 1820. Thereafter, the WTRU may receive a GC-DCI indicating the cancelled UL resources 1830. Next, the WTRU may determine at 1850 whether there is an overlap of PRACH resources corresponding to PRACH format F1. If there is no overlap, the WTRU may transmit a PRACH with format F1 on the corresponding PRACH resources 1860. If there is an overlap, the WTRU may transmit a PRACH using format F2 on the corresponding PRACH resources 1870.

[0254] In one example, the PRACH resources for format F2 or default format 0 may be configured as a fixed subset of the PRACH resources assigned to format F1. In another example, the resources for format F2 or default format 0 may be determined by the WTRU based on the PRACH resources configured for format F1 and the canceled uplink resources indicated by the UL cancel indication. For example, the WTRU may be configured with PRACH format 1, which is associated with a time resource of length 3 ms. Within each PRACH resource of length 3 ms, there are 3 possible time resources for PRACH format 0, which have a time resource of length 1 ms. If the WTRU receives an UL cancel indication and observes an overlap with its own configured PRACH resources (associated with format 1), the WTRU may switch to PRACH with default format 0 and may select the first millisecond, the second millisecond, or the third millisecond of its configured PRACH resources as its valid PRACH resource with format 0 based on the first PRACH that does not overlap with the canceled UL resource.

[0255] A method for providing a cross-carrier cancellation indication is provided herein. For an eMBB WTRU sending uplink data or UCI on a TDD carrier, a timely cancellation indication may be received on a different component carrier. In one method, the WTRU may cancel the transmission on a given carrier upon receiving a cross-carrier cancellation indication. The cross-carrier indication may provide any necessary information. For example, the proposed cross-carrier indication may provide the aforementioned content for a cancellation indication for a single carrier. For example, the proposed cross-carrier indication may provide a carrier index applicable for cancellation.

[0256] In another example, the proposed cross-carrier indication may provide a timing offset, which may be explicitly signaled or implicitly determined by the WTRU based on the uplink timing advance and / or downlink reference timing of the two carriers. For example, the WTRU may determine the cancellation timing by considering the timing offset relative to the time when the cross-carrier indication is received. In one example, the two carriers may have two reference rasters or reference start times. The WTRU may add the difference between the two rasters and / or the uplink timing advance before determining the applicable active resources for cancellation on the indicated carrier. In one example, if the WTRU is configured to start a timer when a cancellation indication is received on the same carrier, the WTRU may delay starting the timer by the time offset if the cancellation indication is a cross-carrier indication. In another instance, if the cancellation indication is a cross-carrier indication, the WTRU may subtract the timing offset from the initial timer value before starting the timer. The timing offset may also take into account the minimum processing time of the WTRU on each component carrier. The minimum processing time may be different based on, for example, the parameter configuration of the component carriers or the frequency band in which they are located.

[0257] In another example, the proposed cross-carrier indication may provide an indication for the WTRU to determine whether the cancellation applies to the same carrier on which the cancellation indication was received or a different carrier.

[0258] The WTRU may monitor the cross-carrier indication on the GC-PDCCH or the WTRU-specific PDCCH on the PDCCH.The carrier index applicable for cancellation may be indicated to the WTRU in a number of ways.

[0259] For example, the carrier index applicable for cancellation may be explicitly indicated to the WTRU. The index of the component carrier may be explicitly indicated. In one example, the WTRU may be configured by the RRC to have a subset of component carriers applicable for inter-WTRU cancellation. The UE may receive a DCI indicating one of the carriers configured by the RRC for inter-WTRU cancellation. The WTRU may determine a codebook to map the carriers applicable for inter-WTRU cancellation to the DCI entries. For example, if the RRC configures the WTRU to have 6 carriers applicable for inter-WTRU cancellation, the WTRU may determine a 3-bit codebook to determine the carrier index. Additionally or alternatively, the WTRU may decode the applicable carrier from a bitmap indicated in the DCI indicating which carrier or carriers are applicable for cancellation.

[0260] For example, the carrier index applicable for cancellation may be implicitly indicated to the WTRU based on the attributes of the PDCCH. For example, the WTRU may determine the index of the component carrier applicable for cancellation based on the attributes of the PDCCH on which the cross-carrier cancellation indication is received, including but not limited to: PDCCH resources, CORESET(s), search space(s), PDCCH periodicity, DCI format, and / or RNTI used to decode the PDCCH. In one example, the WTRU may be configured with a subset of component carriers applicable for inter-WTRU cancellation via RRC signaling. The WTRU may also be configured with a mapping table between component carriers and PDCCH attributes (e.g., CORESET or PDCCH resources) via RRC signaling. The WTRU may determine the component carrier index to which the cancellation indication is applicable from the CORESET on which the cross-carrier indication is received.

[0261] For example, the carrier index applicable for cancellation may be implicitly indicated to the WTRU based on a 1-to-1 carrier mapping. For example, the WTRU may determine the index of the component carrier applicable for cancellation from the carrier index on which the cross-carrier indication was received. The WTRU may also monitor for cancellation indications on a given carrier based on the carrier index on which the transmission is scheduled. For example, the WTRU may be configured with a mapping between CC x and CC y through RRC signaling so that any indication received on CC x implies that it is applicable to CC y, possibly with the exception of CC x itself. For an eMBB WTRU scheduled on CC y, the WTRU may monitor the PDCCH for cross-carrier indications on CC x.

[0262] In the example case of supporting cross-carrier cancellation, the WTRU may indicate the minimum processing time required to process the PDCCH, switch carriers, and stop the WTRU transmission. If the architecture is such that the WTRU may monitor the carrier carrying the indication while transmitting, the minimum processing time may be less than if the WTRU may only transmit or receive in the same direction on multiple carriers. The WTRU may explicitly communicate the minimum processing time or may communicate its carrier aggregation capabilities and have the gNB infer its minimum processing time.

[0263] Methods for orthogonal DMRS transmission to achieve minimum mean square estimation (MMSE)-SIC support in power-based multiplexing are disclosed herein. In addition, methods for ensuring DMRS orthogonality in power-based inter-WTRU multiplexing and prioritization are provided.

[0264] For enhanced power control, in the resources where the eMBB WTRU overlaps with the URLLC WTRU, if there is an orthogonal DMRS between the eMBB WTRU and the URLLC WTRU, the performance loss of the eMBB WTRU and the URLLC WTRU can be ignored. In the example provided in this article, a method is proposed to ensure that the DMRS of the eMBB WTRU and the URLLC WTRU are transmitted in an orthogonal manner in the overlapping resources. Therefore, the example in this article provides a beneficial mechanism for ensuring that the DMRS of the eMBB WTRU and the URLLC WTRU are mutually orthogonal.

[0265] In one example solution, the eMBB WTRU may be configured with a possible set of URLLC WTRU DMRS transmission locations, and the eMBB WTRU may skip transmissions in these specific resources. In addition, the eMBB WTRU may send its own orthogonal DMRS in these resources.

[0266] These predefined locations may be one of the following. The predefined locations may be statically configured and signaled to either or both of the eMBB WTRU and the URLLC WTRU. The predefined locations may be statically configured and dynamically signaled to either or both of the eMBB WTRU and the URLLC WTRU. The predefined locations may be dynamically configured and signaled to either or both of the eMBB WTRU and the URLLC WTRU.

[0267] Fig.19 1900 is a diagram illustrating an example where there is no interruption and the eMBB WTRU transmits throughout the scheduled duration. In the example 1900 shown in the diagram, the eMBB WTRU may transmit DMRS 1910. In addition, the eMBB WTRU may transmit data during the entire scheduled duration 1960 without interruption.

[0268] Fig. 20 2000, the eMBB WTRU may transmit DMRS 2010. Further, the eMBB WTRU may transmit data 2020 and then dynamically suspend its own transmission 2030 while the URLLC WTRU transmits its DMRS 2070. Further, the eMBB WTRU may continue to interrupt its transmission 2040 while the URLLC WTRU transmits its data 2080. The eMBB WTRU may then resume transmitting data 2060.

[0269] The power level of the URLLC WTRU's DMRS may be boosted to improve the URLLC WTRU's channel estimation in the presence of interference sources. In an example, the eMBB WTRU may dynamically suspend its own transmission when the URLLC WTRU is only sending its DMRS, and then the eMBB WTRU may resume transmission of its own data. Further, the eMBB WTRU may interrupt its transmission to transmit an additional DMRS in the same resource and at the same time as the URLLC transmits its DMRS, and then the eMBB WTRU may resume transmission of its own data. In both cases, the gNB may be able to estimate a clear channel for an advanced interference cancellation receiver (e.g., a continuous interference cancellation receiver). The DMRS transmitted by the two WTRUs may be configured to occupy the same time-frequency resources, but be orthogonal in the code domain, for example, by orthogonal cover codes. Since the URLLC WTRU can typically use front-end loaded DMRS, the new DMRS transmitted by the eMBB WTRU may be the first resource allocated to the URLLC. The eMBB WTRU may then resume transmission of its data to prevent phase discontinuity issues in its transmission.

[0270] In an example, to enable the eMBB WTRU as to when to switch, the eMBB WTRU may receive a cancellation or multiplexing indication indicating the resource to be replaced and possibly the parameters for the DMRS or for the DMRS configuration. The DMRS configuration may be semi-statically configured.

[0271] In an example case where an eMBB WTRU may have a second DMRS configured to be transmitted in overlapping resources, one or more of the following may occur. For example, the eMBB WTRU may transmit its second DMRS. The URLLC may send additional orthogonal DMRS in these resources. In another example, the eMBB WTRU may skip sending its second DMRS because the eMBB WTRU has already sent additional DMRS in the resources used by the URLLC WTRU for its front-loaded DMRS.

[0272] Fig.2121 is a diagram illustrating an example of an eMBB transmission with an interruption, wherein the eMBB WTRU transmits a preempted DMRS orthogonal to the URLLC transmission. As shown in the example 2100 of the figure, the eMBB WTRU may use multiple DMRSs and the URLLC WTRU may use multiple DMRSs. The eMBB WTRU may send DMRS 2110. This eMBB transmission may be orthogonal to the URLLC transmission. The eMBB WTRU may use a second DMRS and the URLLC WTRU may transmit a second DMRS orthogonal to the second eMBB DMRS.

[0273] For example, the eMBB WTRU may transmit data 2120 after transmitting the DMRS 2110. In addition, the eMBB WTRU may transmit a second preemptive DMRS 2130 orthogonal to the URLLC WTRU DMRS 2170. Further, the eMBB WTRU may continue to interrupt its transmission 2140 while the URLLC WTRU transmits its data 2180. Additionally or alternatively, the eMBB WTRU may transmit data 2140 during the URLLC WTRU transmission 2180. In addition, the eMBB WTRU may send another DMRS 2150 orthogonal to the second URLLC WTRU DMRS 2190. Also, the eMBB WTRU may continue to interrupt its transmission 2155 while the URLLC WTRU transmits its data 2195. Additionally or alternatively, the eMBB WTRU may transmit data 2155 during the URLLC WTRU transmission 2195. The eMBB WTRU may then resume transmitting data 2160.

[0274] An embodiment URLLC WTRU process is as follows. A URLLC WTRU may receive a DCI indicating its intended resource transmission. The DCI may include a DMRS configuration that ensures orthogonal transmission with any eMBB WTRU DMRS. The URLLC WTRU may send data and one or more DMRS using the received configuration. Data may be rate matched around all transmitted DMRS(s) and data may be punctured to accommodate any transmitted DMRS. Data may be rate matched around any URLLC DMRS and punctured to accommodate any eMBB DMRS.

[0275] An embodiment eMBB WTRU method is as follows. The eMBB WTRU may be configured to monitor for cancellation or multiplexing indications indicating resources to be replaced and possible parameters for DMRS or DMRS configuration. This may be configured to occur when the WTRU is scheduled. This may be configured to occur on resources where the WTRU may be interrupted by the URLLC WTRU, such as preconfigured resources for dynamic URLLC transmissions, and preconfigured resources (one or more) for configured authorized URLLC transmissions, and the like. Upon receiving a valid multiplexing indication, the eMBB WTRU may modify its current transmission to accommodate the DMRS of the URLLC WTRU. The eMBB WTRU may interrupt its transmission to send a DMRS that is orthogonal to the DMRS that the URLLC WTRU is capable of sending. The eMBB WTRU may interrupt its transmission and not send any information in the DMRS resources of the URLLC WTRU. The eMBB WTRU may then resume transmission of its data.

[0276] The examples provided herein also disclose methods for effective monitoring in URLLC / eMBB multiplexing. GC-PDCCH signaling is based on a WTRU set that decodes the PDCCH using an RNTI type (e.g., x-RNTI). This enables the WTRU to receive signaling related to a determined WTRU set. In the example, the signaling may be group common signaling. In the case where both URLLC and eMBB WTRUs have inter-WTRU multiplexing, it may be necessary to define a method that enables the WTRU to receive signaling (e.g., group common signaling) related to a portion of a resource grid, such as a time / frequency resource in a given bandwidth / BWP / cell. In one example, a URLLC WTRU that transmits using a configured grant may have predefined resources in which it needs to transmit. In this way, any WTRU transmitting in this part of the grid may need to monitor the cancellation of signaling, power control, or a combination thereof when resources are allocated in this part of the resource grid.

[0277] In an exemplary solution, the gNB may pre-define monitoring configurations for resource sets for a specific WTRU. In the case of dynamically scheduled eMBB WTRUs, the gNB may include an activation signal for one or more configurations that need to be monitored in the scheduled DCI. In the case of configured authorized eMBB WTRUs, the gNB may use activation / deactivation based on WTRU-specific PDCCH signaling. For Type 2CGs, this may be part of the activation / deactivation signaling used to start / stop CG transmissions, or a separate activation / deactivation signaling to allow flexibility. For Type 1CGs, this may be a new activation / deactivation signaling to enable it to be aware of the resources in which it modifies its behavior.

[0278] The example methods provided herein enable the WTRU to autonomously determine whether signaling, such as group common signaling, is applicable to one or more transmissions for a given time period, rather than blindly following the received signaling. In a possible scheduler strategy for large bandwidths, the network may partition the PRB grid into multiple parts, which may be based on target transmission rates of different WTRUs, etc. The network can then schedule eMBB transmissions to maximize capacity while ensuring that conflicts between URLLC transmissions do not occur. In this case, signaling may be issued to all WTRUs in the cell, which will be applied to each partition so that the scheduler can control conflicts between eMBB WTRUs (one or more) and URLLC WTRUs (one or more), but may also control conflicts between power / interference levels, etc. This will take into account the unpredictable timing aspects of URLLC scheduling for eMBB. For example, when the network schedules URLLC transmissions, the network may issue a public DCI preemption indication for the spectrum portion corresponding to the URLLC transmission, so that all eMBB WTRUs are adjusted accordingly only when and only when these WTRUs determine that they are scheduled / activated in the transmission of the spectrum partition.

[0279] Further, the network may configure one RNTI per partition for such DCI control information. Such control information may include preemption indication for the partition at least in time and also in frequency, power backoff for the partition at least in time and also in frequency, indication to mute transmissions on specific resources, e.g., DM-RS for URLLC transmissions at least in time and also in frequency. In this way, the gNB does not need to configure or reconfigure the WTRU in terms of packets, since the RNTI is associated with the spectrum partition, and the WTRU will autonomously decode the correct RNTI based on the resources associated with the transmission (which may be a scheduled transmission), and only when the control information may change how the WTRU will perform the transmission, e.g., if preemption may be applied, etc.

[0280] For example, the WTRU may autonomously determine that it should decode for a given RNTI a DCI for a preemption indication based on the portion of the bandwidth in which the WTRU has scheduled transmissions, e.g., a URLLC transmission, during a time period when the WTRU may expect such signaling (e.g., before and / or during a transmission if the transmission is for a low priority).

[0281] A generalized example process is discussed below. A WTRU given action [A] may depend on at least one of the following. The action may depend on whether they have a transmission [TRx] scheduled in time period [x], otherwise the WTRU does not perform [A] in time period [y]. For example, the WTRU may evaluate the condition for [A] if [TRx] at least partially overlaps in time with [x].

[0282] The behavior may depend on the associated priority [e.g., 0-URLLC-high priority / 1-eMBB-low priority] of such transmission [TRx]. For example, if [Po] corresponds to [1-eMBB], the WTRU may evaluate the condition for [A], otherwise the WTRU does not perform [A] for a time period [y], where [TRx] may be characterized by resource allocation in time (start and / or duration) / frequency (e.g., PRBs), type of scheduling information [configured or received from DCI], MCS table, (a set of) one or more MCS values, a given power level, HARQ state (e.g., initial or retransmission), or priority (e.g., priority of data included in a transport block).

[0283] In the embodiments herein, [y] may correspond to at least one of the following: [y] may correspond to a time period (possibly an offset time) before the start of TRx, where the offset in time may be a configuration aspect of the WTRU. [y] may correspond to a time period corresponding to the transmission duration of TRx.

[0284] The WTRU given behavior [A] may be a function where [A] may correspond to at least one of the following. For example, [A] may correspond to the WTRU determining one (or more) blind decoding parameters, including at least one of the following parameters. For example, the WTRU may determine the RNTI(s) to be monitored. For example, if a particular PRB set is a superset of at least some resources scheduled for [TRx], the WTRU may monitor the RNTI corresponding to (e.g., by configuration) the PRB set. In addition, the WTRU may monitor the search space (SS) for monitoring. For example, the use of SS may be similar to the above, except that SS is used instead of RNTI. In addition, the WTRU may monitor the aggregation level (AL) for monitoring. For example, the use of AL may be similar to the above, but AL is used instead of RNTI. In addition, the WTRU may monitor the DCI format (one or more) / size (one or more) for monitoring. For example, the use of DCI format (one or more) may be similar to the above, but DCI format (one or more) / size (one or more) is used instead of RNTI. In addition, the WTRU may monitor the PDCCH monitoring timing. For example, using the PDCCH monitoring occasions may be similar to that described above, but using PDDCH occasions instead of RNTIs.

[0285] In another example, [A] may correspond to the WTRU determining that it should apply received signaling, such as a preemption notification; for example, if the WTRU determines that the indication corresponds to a superset of at least some resources scheduled for [TRx], the WTRU may apply preemption.

[0286] In a further example, [A] may correspond to the WTRU determining that it should apply power compensation, power reduction, or both. For example, using power may be similar to the above, but using power compensation instead of preemption. Alternatively or additionally, using power may be similar to the above, but using power reduction instead of preemption.

[0287] In an additional example, [A] may correspond to the WTRU determining that it should avoid performing transmissions in certain symbols / resources, such as for DM-RS skipping. For example, using DM-RS may be similar to the above, but using DM-RS muting instead of preemption.

[0288] A WTRU given action [A] may depend on one or more characteristics of the WTRU's use of such transmissions to evaluate whether to perform action [A], such as one of the following. The WTRU may use resource allocations for transmissions in frequency and / or time (e.g., a set of PRBs). For example, if during time period [y], if [TRx] may at least partially overlap with time period [x], if Po corresponds to 1-eMBB, then the WTRU may perform [A]. For example, if [TRx] at least partially overlaps with PRBs within a portion of the frequency band, if Po corresponds to 1-eMBB, then the WTRU may perform [A].

[0289] In addition, the WTRU may use the grant type (e.g., dynamically configured) as a characteristic. For example, if during time period [y], if [TRx] is scheduled by a configured grant and may at least partially overlap with time period [x], then the WTRU may perform [A].

[0290] In addition, the WTRU may use whether the transmission is an initial transmission or a retransmission. For example, if during time period [y], if [TRx] may at least partially overlap with time period [x], if Po corresponds to 1-eMBB, then the WTRU may perform [A].

[0291] In addition, the WTRU may use an applicable MCS (set). For example, if during time period [y], if [TRx] may at least partially overlap with time period [x], if Po corresponds to 1-eMBB, then the WTRU may perform [A].

[0292] Example solutions to avoid or reduce uplink interference may be included. The WTRU may follow certain procedures to prevent or reduce uplink interference. For example, the WTRU may follow a procedure including at least one of: applying a power backoff or reduction to a transmission; avoiding performing a previously scheduled transmission in at least a portion of the time resources allocated for the transmission; or, for a particular time symbol or resource (e.g., DM-RS), monitoring the PDCCH for an indication to apply or not apply interference reduction behavior, such as an indication to cancel a transmission, confirm a transmission, or reduce transmission power; and performing a previously scheduled transmission in an alternative resource.

[0293] The WTRU may determine whether or how to apply at least one of the above processes during a first time period based on at least one of the following: whether the WTRU has a transmission scheduled in a second time period or a transmission overlapping with the second time period; and / or at least one transmission characteristic. The transmission characteristic may include one or more priority levels associated with the transmission, such as corresponding to eMBB or URLLC; resource allocation for the transmission in frequency and / or time (e.g., PRB set); grant type (configuration type 1, configuration type 2, or dynamic); type of physical channel (PUSCH, PUCCH, PRACH) or physical signal (SRS, DM-RS); PUCCH format; type of uplink control information (HARQ-ACK, SR, CSI); scheduling type of CSI (non-periodic, periodic, or semi-persistent) or SRS; whether the transmission is an initial transmission or a retransmission (e.g., for PUSCH, SR, or PRACH); an MCS table for scheduling the transmission, or an MCS for the transmission.

[0294] In the examples provided herein, the first time period may correspond to at least one time period before the start of the transmission, where the offset in time may be a configuration aspect of the WTRU, or a time period corresponding to the duration of the transmission. In an example, the time period may be a possible time offset.

[0295] The WTRU may monitor the PDCCH for indications based on at least one of the following. The WTRU may determine one or more parameters for decoding the PDCCH, including at least one of the following: at least one search space configuration, the configuration including a CORESET, a periodicity and offset of monitoring occasions, a type, an aggregation level, a set of DCI formats, etc.; and a set of RNTIs (one or more RNTIs) to be monitored. In addition, at least one of the above aspects may be associated with specific resources defined in time and / or frequency resources for potentially affected transmissions (e.g., cancellation or transmission at reduced power). An indication received in a particular time instance may affect transmissions that overlap in time with a time period defined relative to the time instance (e.g., the same time slot or a subsequent time slot, plus an offset). In addition, the set of time and / or frequency resources may be indicated by a field of the indicated DCI. For example, the DCI may include a bitmap indicating which set of time symbols or which set of time symbols and frequency domain portions the indication relates to.

[0296] For example, during a time period when the WTRU may expect such signaling (if the transmission is for a low priority (e.g., not URLLC)), the WTRU may autonomously determine that it should decode a given RNTI for a DCI for a cancellation indication based on the portion of the bandwidth in which the WTRU has scheduled transmissions.

[0297] Although the features and elements are described above in specific combinations, it will be understood by those skilled in the art that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein can be implemented in a computer program, software, or firmware that is incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor associated with the software can be used to implement a radio frequency transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method for use in a wireless transmit / receive unit (WTRU), the method comprising: receiving first higher layer configuration information; receiving a grant indicating information associated with an uplink transmission; Receiving a cancel instruction (CI) message; as well as Based on the CI information and the first higher layer configuration information, at least a portion of the uplink transmission is cancelled.

2. The method according to claim 1, wherein: The grant indicating information associated with the uplink transmission is at least one of: first downlink control information (DCI), a dynamic grant, a configured grant, first radio resource control (RRC) signaling, or second higher layer configuration information.

3. The method according to claim 1, wherein: The uplink transmission is one of the following: For transmission on a physical uplink control channel (PUCCH), for transmission on a physical uplink shared channel (PUSCH), ultra-reliable low latency (URLLC) transmission, or enhanced massive mobile broadband (eMBB) transmission.

4. The method according to claim 1, wherein: The CI information is received via at least one of second RRC signaling or second DCI.

5. The method according to claim 1, wherein: Canceling at least a portion of the uplink transmission based on the CI information and the first higher layer configuration information includes: canceling at least a portion of the uplink transmission under the conditions that the CI information is received, at least one frequency resource in a frequency resource subset overlaps with a frequency allocation for the uplink transmission, at least one time symbol in a time symbol set overlaps with a time allocation for the uplink transmission, and a priority index for the uplink transmission is determined to be a priority suitable for cancellation.

6. The method according to claim 5, wherein: The first higher layer configuration information indicates a maximum priority level applicable for cancellation.

7. The method according to claim 6, wherein: Based on the maximum priority applicable for cancellation, the priority index for the uplink transmission is determined as a priority applicable for cancellation.

8. The method according to claim 6, wherein: The CI information indicates the maximum priority applicable for cancellation.

9. The method according to claim 1, further comprising: receiving a second grant indicating information associated with a second uplink transmission; as well as The second uplink transmission is sent.

10. The method according to claim 1, wherein: The first higher layer configuration information includes first radio resource control (RRC) configuration information.

11. A wireless transmit / receive unit (WTRU), the WTRU comprising a processor, the processor configured to: receiving first higher layer configuration information; receiving a grant indicating information associated with an uplink transmission; receiving a cancellation indication (CI) message; and Based on the CI information and the first higher layer configuration information, at least a portion of the uplink transmission is cancelled.

12. The WTRU of claim 11, wherein the grant indicating information associated with the uplink transmission is at least one of: first downlink control information (DCI), a dynamic grant, a configured grant, a first radio resource control (RRC) signaling, or a second higher layer configuration information.

13. The WTRU of claim 11 , wherein the uplink transmission is one of: For transmission on a physical uplink control channel (PUCCH), for transmission on a physical uplink shared channel (PUSCH), ultra-reliable low latency (URLLC) transmission, or enhanced massive mobile broadband (eMBB) transmission.

14. The WTRU of claim 11, wherein the CI information is received via at least one of second RRC signaling or second DCI.

15. The WTRU of claim 11 , wherein the processor being configured to cancel at least a portion of the uplink transmission based on the CI information and the first higher layer configuration information comprises: The processor is configured to cancel at least a portion of the uplink transmission upon receiving the CI information, at least one frequency resource in a frequency resource subset overlaps with a frequency allocation for the uplink transmission, at least one time symbol in a time symbol set overlaps with a time allocation for the uplink transmission, and a priority index for the uplink transmission is determined to be a priority suitable for cancellation.

16. The WTRU of claim 15, wherein the first higher layer configuration information indicates a maximum priority applicable for cancellation.

17. The WTRU of claim 16, wherein the priority index for the uplink transmission is determined as a priority applicable for cancellation based on the maximum priority applicable for cancellation.

18. The WTRU of claim 16, wherein the CI information indicates the maximum priority applicable for cancellation.

19. The WTRU of claim 11 wherein the processor is further configured to: receiving a second grant indicating information associated with a second uplink transmission; and The second uplink transmission is sent.

20. The WTRU of claim 11, wherein the first higher layer configuration information comprises first radio resource control (RRC) configuration information.

21. A wireless transmit / receive unit (WTRU), the WTRU comprising a processor configured to: receiving, via radio resource control (RRC) signaling, an indication of a set of reference frequency resources for which uplink cancellation may occur and an allocation for a configured grant; receiving a physical downlink control channel (PDCCH) transmission, the PDCCH including downlink control information (DCI), the DCI including cancel indication (CI) information; and Based on the CI information and the RRC signaling, at least a portion of uplink transmission associated with the configured grant is cancelled.

22. The WTRU of claim 21 , wherein the processor being configured to cancel at least a portion of uplink transmissions associated with the configured grant based on the CI information and the RRC signaling comprises: The processor is configured to: Upon receiving the CI information, at least one frequency resource in the subset of the reference frequency resource set overlaps with the frequency allocation for the configured authorization, at least one time symbol of one or more time symbols overlaps with the time allocation for the configured authorization, and the priority index for the configured authorization is determined to be a priority suitable for cancellation, at least a portion of the uplink transmission associated with the configured authorization is canceled.

23. The WTRU of claim 22, wherein the processor is configured to, upon receiving the CI information, at least one frequency resource in the subset of the set of reference frequency resources overlaps with a frequency allocation for a configured grant, at least one time symbol of one or more time symbols overlaps with a time allocation for the configured grant, and a priority index for the configured grant is determined to be a priority suitable for cancellation, canceling at least a portion of the uplink transmission associated with the configured grant comprises: The processor is configured to: determining a first portion of the uplink transmission associated with the configured grant and a second portion of the uplink transmission associated with the configured grant; canceling the first portion of the uplink transmission associated with the configured grant; as well as The second portion of the uplink transmission is sent in association with the configured grant.

24. The WTRU of claim 22, wherein the processor is configured to, conditional upon receiving the CI information, at least one frequency resource in the subset of the set of reference frequency resources overlapping with a frequency allocation for a configured grant, at least one time symbol of one or more time symbols overlapping with a time allocation for the configured grant, and a priority index for the configured grant being determined to be a priority suitable for cancellation, canceling at least a portion of the uplink transmission associated with the configured grant comprises: The processor is configured to: The entire uplink transmission associated with the configured grant is canceled.

25. A WTRU according to claim 22, wherein the priority index for the configured grant is determined as a priority applicable for cancellation based on an indication of the at least one priority applicable for uplink cancellation received in the RRC signaling and a value of the priority index.

26. A WTRU according to claim 25, wherein the priority index for the configured authorization is determined as a priority applicable for cancellation under the condition that the priority index for the configured authorization is lower than or equal to the at least one priority applicable for uplink cancellation indicated in the RRC signaling.

27. The WTRU of claim 21 wherein the RRC signaling includes an applicable maximum priority.

28. The WTRU of claim 21, wherein the processor is further configured to transmit the uplink transmission.

29. The method according to claim 21, wherein: The uplink transmission is one of: transmission on a physical uplink control channel (PUCCH), transmission on a physical uplink shared channel (PUSCH), an ultra-reliable low latency (URLLC) transmission, or an enhanced massive mobile broadband (eMBB) transmission.

30. The WTRU of claim 21 , wherein the processor is further configured to: receiving a second PDCCH transmission, the second PDCCH comprising a second DCI, the second DCI comprising second CI information; and The second uplink transmission is sent.

31. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving, via radio resource control (RRC) signaling, an indication of a set of reference frequency resources for which uplink cancellation may occur and an allocation for a configured grant; receiving a physical downlink control channel (PDCCH) transmission, the PDCCH including downlink control information (DCI), the DCI including cancel indication (CI) information; as well as Based on the CI information and the RRC signaling, at least a portion of uplink transmission associated with the configured grant is cancelled.

32. The method according to claim 31, wherein: The canceling at least a portion of uplink transmission associated with the configured grant based on the CI information and the RRC signaling comprises: Upon receiving the CI information, at least one frequency resource in the subset of the reference frequency resource set overlaps with the frequency allocation for the configured authorization, at least one time symbol of one or more time symbols overlaps with the time allocation for the configured authorization, and the priority index for the configured authorization is determined to be a priority suitable for cancellation, at least a portion of the uplink transmission associated with the configured authorization is canceled.

33. The method of claim 32, wherein: Canceling at least a portion of the uplink transmission associated with the configured grant under the condition that the CI information is received, at least one frequency resource in the subset of the reference frequency resource set overlaps with the frequency allocation for the configured grant, at least one time symbol of the one or more time symbols overlaps with the time allocation for the configured grant, and a priority index for the configured grant is determined to be a priority applicable for cancellation comprises: determining a first portion of the uplink transmission associated with the configured grant and a second portion of the uplink transmission associated with the configured grant; cancelling the first portion of the uplink transmission associated with the configured grant; and The second portion of the uplink transmission is sent in association with the configured grant.

34. The method of claim 32, wherein: Canceling at least a portion of the uplink transmission associated with the configured grant under the condition that the CI information is received, at least one frequency resource in the subset of the reference frequency resource set overlaps with the frequency allocation for the configured grant, at least one time symbol of the one or more time symbols overlaps with the time allocation for the configured grant, and a priority index for the configured grant is determined to be a priority applicable for cancellation comprises: The entire uplink transmission associated with the configured grant is canceled.

35. The method of claim 32, wherein: Based on the indication received in the RRC signaling of the at least one priority for which uplink cancellation is applicable and the value of the priority index, the priority index for the configured grant is determined to be the priority applicable for cancellation.

36. The method of claim 35, wherein: Under the condition that the priority index for the configured grant is lower than or equal to the at least one priority indicated in the RRC signaling for which uplink cancellation is applicable, the priority index for the configured grant is determined to be a priority applicable for cancellation.

37. The method of claim 31, wherein: The RRC signaling includes the applicable maximum priority level.

38. The method of claim 31 further comprising: The uplink transmission is transmitted.

39. The method of claim 31, wherein: The uplink transmission is one of: transmission on a physical uplink control channel (PUCCH), transmission on a physical uplink shared channel (PUSCH), an ultra-reliable low latency (URLLC) transmission, or an enhanced massive mobile broadband (eMBB) transmission.

40. The method of claim 31 , further comprising: receiving a second PDCCH transmission, the second PDCCH comprising a second DCI, the second DCI comprising second CI information; as well as The second uplink transmission is sent.

41. A method for use in a wireless transmit / receive unit (WTRU), the method comprising: receiving first higher layer configuration information, wherein the first higher layer configuration information indicates a reference frequency resource set for cancelling indication CI information; receiving a grant indicating information associated with an uplink transmission, wherein the information associated with the uplink transmission includes a priority level for the uplink transmission; receiving the CI information; determining a priority level for the uplink transmission indicating that the uplink transmission is a low priority transmission; Based on determining that the priority level for the uplink transmission indicates that the uplink transmission is a low priority transmission, at least a portion of the uplink transmission is cancelled.

42. The method according to claim 41, wherein: The authorization indicating information associated with the uplink transmission includes at least one of: first downlink control information DCI, a dynamic authorization, a configured authorization, a first radio resource control RRC signaling, or a second higher layer configuration information, and wherein the uplink transmission is one of: for transmission on a physical uplink control channel PUCCH, for transmission on a physical uplink shared channel PUSCH, an ultra-reliable low latency URLLC transmission, or an enhanced massive mobile broadband eMBB transmission.

43. The method of claim 41, further comprising: The portion of the uplink transmission that was not cancelled is transmitted.

44. The method of claim 41, wherein: Determining that the priority level for the uplink transmission indicates that the uplink transmission is a low priority transmission includes determining that the priority level for the uplink transmission is below a maximum priority applicable for cancellation.

45. The method of claim 44, wherein: The CI information indicates the maximum priority applicable for cancellation.

46. ​​The method of claim 41, further comprising: receiving a second grant indicating information associated with a second uplink transmission, wherein the information associated with the second uplink transmission includes a priority level for the second uplink transmission; determining that the priority level for the second uplink transmission indicates that the second uplink transmission is a high priority transmission; as well as Based on determining that the priority level for the second uplink transmission indicates that the second uplink transmission is a high priority transmission, transmitting the second uplink transmission.

47. The method of claim 41, wherein: The first higher layer configuration information includes first radio resource control RRC configuration information.

48. A wireless transmit / receive unit WTRU, the WTRU comprising: transceiver; as well as a processor operably coupled to the transceiver; wherein: The transceiver is configured to receive first higher layer configuration information, wherein the first higher layer configuration information indicates a reference frequency resource set for cancelling indication CI information; The transceiver is configured to receive a grant indicating information associated with an uplink transmission, wherein the information associated with the uplink transmission includes a priority level for the uplink transmission; The transceiver is used to receive the CI information; The processor is configured to determine that the priority level for the uplink transmission indicates that the uplink transmission is a low priority transmission; and The transceiver and the processor are configured to cancel at least a portion of the uplink transmission based on determining that the priority level for the uplink transmission indicates that the uplink transmission is a low priority transmission.

49. A WTRU according to claim 48, wherein the authorization indicating information associated with the uplink transmission includes at least one of: first downlink control information DCI, a dynamic authorization, a configured authorization, a first radio resource control RRC signaling or a second higher layer configuration information, and wherein the uplink transmission is one of: for transmission on a physical uplink control channel PUCCH, for transmission on a physical uplink shared channel PUSCH, an ultra-reliable low latency URLLC transmission or an enhanced massive mobile broadband eMBB transmission.

50. The WTRU of claim 48, wherein the transceiver and the processor are further configured to transmit the portion of the uplink transmission that was not cancelled.

51. The WTRU of claim 48, wherein the processor is configured to determine that the priority level for the uplink transmission indicates that the uplink transmission is a low priority transmission comprises: The processor is configured to determine that the priority level for the uplink transmission is lower than a maximum priority level applicable for cancellation.

52. The WTRU of claim 51, wherein the CI information indicates the maximum priority applicable for cancellation.

53. The WTRU of claim 48 wherein: the transceiver being configured to receive a second grant indicating information associated with a second uplink transmission, wherein the information associated with the second uplink transmission includes a priority level for the second uplink transmission; The processor is configured to determine that the priority level for the second uplink transmission indicates that the second uplink transmission is a high priority transmission; and The transceiver and the processor are further configured to transmit the second uplink transmission based on determining that the priority level for the second uplink transmission indicates that the second uplink transmission is a high priority transmission.

54. The WTRU of claim 48, wherein the first higher layer configuration information comprises first radio resource control (RRC) configuration information.

55. An enhanced massive mobile broadband (eMBB) wireless transmit / receive unit (WTRU), the WTRU comprising a processor configured to: receiving a higher layer configuration for one or more identification sequences from a network; Monitor cancel indication (CI) information; receiving the CI; receiving information specific to one or more of an eMBB sequence or an eMBB resource; Stop normal transmission; transmitting an identification sequence in one or more resources corresponding to ultra-reliable low latency (URLLC) interference measurement resources (IMRs); and Resume the transfer.

56. An ultra-reliable low latency (URLLC) wireless transmit / receive unit (WTRU), the WTRU comprising a processor configured to: receiving a higher layer configuration for one or more interference measurement resource (IMR) resources; receiving scheduling information and transmission information; Start URLLC transmission; monitoring cancel indication (CI) information; and End URLLC transmission.

Images