Supplemental uplink transmission in wireless systems

Abstract

Systems, methods, and instrumentalities are disclosed for uplink (UL) transmissions in wireless systems. The systems, methods, and instrumentalities can include a wireless transmit / receive unit (WTRU) having a receiver configured to receive one or more uplink (UL) grants that can include an assignment associated with a regular UL (RUL) carrier and a supplemental UL (SUL) carrier. The RUL and SUL carriers can be associated with a common downlink (DL) carrier of a serving cell. The WTRU can include a processor configured to select data for transmission from one or more logical channels in accordance with the assignment. The WTRU can include a transmitter configured to transmit data from one logical channel on the RUL carrier and data from another logical channel on the SUL carrier in accordance with the assignment.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on November 13, 2018, with application number 201880084912.8 and title "Supplemental Uplink Transmission in a Wireless System".

[0002] Cross-references to related applications

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 586,095, filed November 14, 2017, entitled Supplemental Uplink Transmission in a Wireless System, and U.S. Provisional Application No. 62 / 615,404, filed January 9, 2018, the entire contents of which are incorporated herein by reference. Background Technology

[0004] Mobile devices in wireless communication systems can be configured to operate using uplink (UL) carriers within a given cell. UL carriers can be associated with downlink (DL) carriers within the same cell. To some extent, a mobile device can be configured with more than one UL carrier, each UL carrier associated with a different DL carrier from a different cell. That is, there can be a one-to-one correspondence between UL carriers and DL carriers configured in a mobile device. Increasing the number of available UL carriers for a given DL carrier can improve wireless performance, such as the reliability of UL transmissions from the mobile device. For example, if one of the available UL carriers operates at a higher frequency than the other, the mobile device can extend its transmission range by selecting the lower-frequency UL carrier. However, adding such additional UL carriers presents new technical challenges, including configuring the mobile device to manage these additional UL carriers when processing data for UL transmissions. Summary of the Invention

[0005] Systems, methods, and means for uplink (UL) transmission in a wireless system are disclosed. These systems, methods, and means may include a wireless transmit / receive unit (WTRU) having a receiver configured to receive one or more UL grants. The one or more UL grants may be received via a common downlink (DL) carrier of the serving cell. The uplink grants may include allocations associated with a regular UL (RUL) carrier and allocations associated with a supplementary UL (SUL) carrier. The RUL and SUL carriers may be associated with a common DL carrier of the serving cell. The frequency of the RUL carrier may be greater than the frequency of the SUL carrier. The coverage area of ​​the SUL carrier may be greater than the coverage area of ​​the RUL carrier.

[0006] The WTRU may include a processor configured to select data for transmission from one or more logical channels based on allocations in one or more UL licenses. For example, a logical channel may be selected based at least on an allocation associated with a RUL carrier, and another logical channel may be selected based at least on another allocation associated with a SUL carrier. The WTRU may include a transmitter configured to transmit data on one logical channel on the RUL carrier and from another logical channel on the SUL carrier, according to the corresponding allocations. Data transmission on the RUL carrier and data transmission on the SUL carrier may at least partially overlap in time and / or may occur during different time intervals.

[0007] Data from at least one logical channel can be restricted to transmission on a RUL carrier, while data from at least another logical channel can be restricted to transmission on a SUL carrier. According to another allocation, data from at least another logical channel can be selected for transmission on both RUL and SUL carriers. According to yet another allocation, if the quality of the serving cell is above a threshold, data from at least another logical channel can be selected for transmission on a RUL carrier, and if the quality of the serving cell is below a threshold, it can be used for transmission on a SUL carrier. According to another allocation, the processor can be configured to select the RUL carrier or the SUL carrier for transmission of data from one or more logical channels based on one or more of the following: timing requirements of the data, transmission type of the data, subcarrier spacing (SCS) requirements of the data, radio service type of the data, total size of data available for transmission, explicit indications in one or more UL licenses, redundancy version (RV) of the data transmission, mobility or speed of the WTRU, or quality of service (QoS) requirements of the data. Attached Figure Description

[0008] The same reference numerals in the figure indicate the same elements.

[0009] Figure 1A This is a system diagram illustrating an example communication system in which one or more examples can be implemented.

[0010] Figure 1B It shows that it can be used Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0011] Figure 1C It shows that it can be done Figure 1A The diagram shows a system diagram of an example radio access network (RAN) and an example core network (CN) used in the communication system.

[0012] Figure 1DIt shows that it can be done Figure 1A The system diagram shows another example RAN and another example CN used in the communication system shown.

[0013] Figure 2 This is a system diagram showing an example wireless cell with a coverage area for a downlink (DL) carrier and two or more corresponding uplink (UL) carriers.

[0014] Figure 3 An example Logical Channel Priority (LCP) procedure is shown for prioritizing data from one or more logical channels (LCHs) and / or for assigning such LCHs to one or more UL carriers associated with a cell.

[0015] Figure 4 An example series of transmission time intervals (TTIs) is shown, during which data can be generated based on... Figure 3 The LCP process sequentially transmits data from one or more LCHs on multiple UL carriers.

[0016] Figure 5 An example TTI series is shown, during which time it can be based on Figure 3 The LCP process transmits data from one or more LCHs simultaneously on multiple UL carriers. Detailed Implementation

[0017] A detailed description of illustrative embodiments will now be described with reference to the accompanying drawings. While such description provides detailed examples of possible implementations, it should be noted that these details are intended to be illustrative and in no way intended to limit the scope of this application.

[0018] Figure 1A This diagram illustrates an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word DFT Extended OFDM (ZT-UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0019] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that any number of WTRUs, base stations, networks, and / or network elements are contemplated in the disclosed embodiments. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or MiFi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any WTRU 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0020] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be base transceiver stations (BTS), node B, e-node B, home node B, home e-node B, gNB, NR node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0021] Base station 114a may be part of RAN 104 / 113, and may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0022] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).

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

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

[0025] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use new radio (NR) to establish air interface 116.

[0026] In the embodiments, base station 114a and WTRUs 102a, 102b, and 102c can implement various radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for example, use a dual connectivity (DC) principle to implement both LTE radio access and NR radio access. Therefore, the air interface utilized by WTRUs 102a, 102b, and 102c can be characterized by various types of radio access technologies and / or transmissions sent to or from various types of base stations (e.g., eNBs and gNBs).

[0027] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0028] Figure 1ABase station 114b can be, for example, a wireless router, home node B, home e node B, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business premises, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can have a direct connection to the Internet 110. Therefore, base station 114b does not need to access the Internet 110 via CN 106 / 115.

[0029] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. Data may have varying Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs using the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113, which can utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0030] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

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

[0032] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It is understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0033] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other function that enables WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmitting / receiving element 122. Although Figure 1B While the processor 118 and transceiver 120 are depicted as separate components, it will be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0034] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

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

[0036] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers for enabling WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

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

[0038] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium, nickel-zinc, nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0039] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or alternatively to, the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 116, and / or determine its location based on the timing of signals received from two or more neighboring base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0040] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, etc. Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor; geolocation sensor; altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and / or humidity sensor.

[0041] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for uplink (UL) (e.g., for transmission) and downlink (DL) (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing (e.g., a separate processor (not shown) or via processor 118). In an embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0042] Figure 1C This diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 may employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 may also communicate with CN 106.

[0043] RAN 104 may include eNodeBs 160a, 160b, and 160c, but it should be understood that RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. eNodeBs 160a, 160b, and 160c may each include one or more transceivers to communicate with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNodeBs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNodeB 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

[0044] Each of eNodeB 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, nodes B160a, 160b, and 160C can communicate with each other via the X2 interface.

[0045] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is depicted as part of CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0046] The MME 162 can connect to each of the eNodeBs 162a, 162b, and 162c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies (such as GSM and / or WCDMA).

[0047] The SGW 164 can connect to each of the eNodeBs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during handover between eNodeBs, triggering paging when DL data is available for WTRUs 102a, 102B, and 102c, managing and storing the context of WTRUs 102a, 102B, and 102c, etc.

[0048] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as the Internet 110, to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0049] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRU 102a, 102b, 102c and traditional landline communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), or can communicate with an IP gateway that serves as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0050] Although WTRU is Figure 1A-1D While described as a wireless terminal, it is anticipated that in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

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

[0052] In an Infrastructure Basic Services Set (BSS) mode, a WLAN may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic entering and / or leaving the BSS. Traffic originating from a STA outside the BSS can reach and be delivered to the STA via the AP. Traffic originating from a STA to a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be transmitted via the AP; for example, a source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be transmitted between a source STA and a destination STA (e.g., directly between the source and destination STAs) using Direct Link Establishment (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to here as an "ad-hoc" communication mode.

[0053] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a 20 MHz bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA, including the AP, can sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0054] High-throughput (HT) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels to form a 40MHz wide channel.

[0055] Very High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining adjacent 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels or by combining two non-consecutive 80MHz channels; this is known as an 80+80 configuration. In the 80+80 configuration, after channel coding, the data can pass through a segmented parser that divides the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. The streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0056] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support instrument-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities including support for certain and / or limited bandwidths (e.g., only support). MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0057] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as the primary channel. The primary channel can have a bandwidth 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 one of the STAs operating in the BSS that supports the minimum bandwidth operating mode. In the 802.11ah example, for a STA that supports (e.g., only supports) a 1MHz mode (e.g., an MTC-type device), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1MHz operating mode) is transmitting to the AP, the entire available band can be considered busy even if most of the band remains idle and available.

[0058] In the United States, the available frequency band for 802.11ah is from 902MHz to 928MHz. In South Korea, the available frequency band is from 917.5MHz to 923.5MHz. In Japan, the available frequency band is from 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is from 6MHz to 26MHz.

[0059] Figure 1DThis diagram illustrates a system diagram of RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0060] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, and 180c includes one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In an embodiment, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c may implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0061] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable parameter configurations (numerology). For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) with various or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).

[0062] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without needing to access other RANs (e.g., eNodeBs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, and also with another RAN such as eNodeBs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, and one or more eNodeBs 160a, 160b, and 160c. In a non-standalone configuration, eNodeBs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0063] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0064] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0065] AMF 182a and 182b can connect to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service type used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services that rely on Ultra Reliable Low Latency (URLLC) access, services that rely on Enhanced Massive Mobile Broadband (eMBB) access, and services for Machine-Type Communication (MTC) access. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies (e.g., LTE, LTE-A Pro, and / or non-3GPP access technologies such as WiFi).

[0066] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0067] UPF 184a and 184b can be connected via the N3 interface to one or more of the gNBs 180a, 180b, and 180c in RAN 113. This provides WTRU 102a, 102b, and 102c with access to packet-switched networks such as the Internet 110, facilitating communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and so on.

[0068] CN 115 can facilitate communication with other networks. For example, CN 115 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) or may communicate with an IP gateway that serves as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c may be connected to local data networks (DNs) 185a and 185b via the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0069] Given Figure 1A-1D and Figure 1A-1D As described herein, one or more of the functions described herein with respect to one or more of the following can 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 any (one or more) other devices described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0070] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device for testing purposes and / or can perform tests using over-the-air wireless communication.

[0071] One or more emulation devices may perform one or more functions, including all functions, without being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in test scenarios within test laboratories and / or non-deployed (e.g., testing) wired and / or wireless communication networks to perform testing of one or more components. One or more emulation devices may be test rigs. Emulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0072] The examples provided in this article are not limited to other wireless technologies, for example, using the same or different principles as applicable wireless technologies.

[0073] "Network" can refer to one or more gNBs, which can (for example, in turn) be associated with one or more transmit / receive points (TRPs) or other nodes in a radio access network (RAN).

[0074] Mobile communications are in a continuous evolution. The fifth generation of this evolution is called 5G.

[0075] 5G systems, for example, can at least partially correspond to new radio (NR) access technologies.

[0076] The 5G air interface can support or enable, for example, improved broadband performance (IBB), industrial control and communication (ICC), vehicle-to-everything communication (V2X), massive machine-type communication (mMTC), ultra-low latency (LLC) transmission, ultra-reliable transmission (URC), and / or MTC operation, which may include narrowband operation.

[0077] In examples that support LLC, the air interface latency can be, for example, a round-trip time (RTT) of 1 ms. The TTI can be, for example, between 100us and 250us.

[0078] The WTRU can be configured to support ultra-low access latency (e.g., the time from initial system access to the completion of transmission of the first user plane data unit). For example, communications (e.g., ICs and / or vehicle-to-everything (V2X)) can have end-to-end (e2e) latency, for example, less than 10 ms.

[0079] In examples that support URC, transport reliability can be, for example, approximately 99.999% transport success rate and service availability.

[0080] It can provide support for mobility. The range of movement speed can be, for example, from 0 to 500 km / h.

[0081] It can provide less than 10e for communication (e.g., IC and V2X). -6 Support for Packet Loss Rate (PLR).

[0082] In examples that support MTC operation, the air interface may support narrowband operation (e.g., using less than 200 kHz), extended battery life (e.g., autonomy up to 15 years), and / or minimal communication overhead for small and infrequent data transmissions (e.g., low data rates in the range of 1-100 kbps with access latency of a few seconds to a few hours).

[0083] Orthogonal Frequency Division Multiplexing (OFDM) can be used as a signal format for data transmission, such as for LTE and / or IEEE 802.11. OFDM can be used to divide the spectrum into multiple parallel orthogonal subbands. A rectangular window in the time domain can be used to shape (e.g., each) the subcarriers, resulting in sinusoidal subcarriers in the frequency domain. OFDM access (OFDMA) can be achieved using uplink timing alignment (e.g., perfect) frequency synchronization and (e.g., tight) management over the duration of the cyclic prefix, for example, to maintain orthogonality between signals and minimize inter-carrier interference. For example, tight synchronization can be a challenge in systems where WTRUs can connect to multiple access points simultaneously. Additional power reduction can be applied to uplink transmissions, for example, to meet spectrum transmission requirements in adjacent frequency bands, which may occur where there is aggregation of segmented spectrum for WTRU transmissions.

[0084] OFDM (e.g., Cyclic Prefix (CP)-OFDM) can be implemented with, for example, more stringent RF requirements, such as when operating with large continuous spectrum without the need for aggregation. CP-based OFDM transmission schemes can lead to downlink physical layers in 5G similar to previous generations, such as modifications to pilot signal density and location.

[0085] 5gFLEX can use waveforms other than OFDM for 5G systems.

[0086] The characteristics of 5g FLEX radio access include, for example, very high spectrum flexibility, which allows deployment in different frequency bands with different characteristics, such as different duplex arrangements, different and / or variable sizes of available spectrum (e.g., continuous and / or discontinuous spectrum allocation in the same or different frequency bands). 5g FLEX radio access can support variable timing aspects, such as multiple TTI lengths and / or asynchronous transmissions.

[0087] Time-division duplex (TDD) and frequency-division duplex (FDD) schemes can be supported, for example, in duplex arrangements. For instance, spectrum aggregation can be used to support supplemental DL operations (e.g., for FDD operations). FDD operations can support both full-duplex and half-duplex FDD operations. DL / UL allocation (e.g., for TDD operations) can be dynamic (e.g., it can be based on or not based on a fixed DL / UL frame configuration). The length of the DL transmission or the UL transmission interval can be set, for example, for each transmission opportunity.

[0088] Carrier aggregation (CA) can be used in wireless communication networks, such as LTE-A, and can be used for both FDD and TDD. Each carrier in the aggregated carriers can be called a component carrier (CC), and the aggregated CCs can have the same bandwidth or different bandwidths. Aggregating multiple CCs can increase the wireless bandwidth available to the WTRU. For example, if each CC has a bandwidth of 20 MHz and the wireless network is configured to aggregate up to five CCs, the wireless network can achieve a maximum aggregated bandwidth of 100 MHz when transmitting or receiving data from the WTRU.

[0089] In a CA-based wireless network, each serving cell can have one UL CC and one corresponding DL CC. For example, the aggregation of five UL CCs can involve five serving cells, where each aggregated UL CC is associated with the corresponding DL CC of the respective serving cell. Therefore, in a CA, the number of aggregated UL CCs can not exceed the number of corresponding DL CCs. One of the serving cells can be called the primary serving cell, which manages the primary UL CC. Other UL CCs aggregated with the primary UL CC can be called secondary UL CCs. Secondary UL CCs can be managed by their respective secondary serving cells. Therefore, the primary UL CC and secondary UL CCs can each utilize reference signals and / or control channels from the corresponding DL CC. The primary UL CC and secondary UL CCs can each have different Physical Cell IDs (PCIs). In some cases, such as during handover, secondary UL CCs can be added and removed as needed, while the primary UL CC can be changed.

[0090] Figure 2An example cell 200 (e.g., in NR) including a base station 202 (e.g., a gNB) is shown, where a WTRU (not shown) can be configured with a DL carrier and one or more UL carriers. Cell 200 can have the entire radio coverage area 204, which can include areas 206, 208, and 210. Area 206 can extend radially outward from base station 202 and can represent a portion of coverage area 204. Area 208 can extend radially outward from base station 202 beyond area 206 and can also represent a portion of coverage area 204. Area 210 can extend radially outward from base station 202 beyond areas 206 and 208 and can be the same as (or substantially the same as) coverage area 204. Therefore, area 210 can surround areas 206 and 208, and area 208 can surround area 206.

[0091] The WTRU operating within cell 200 can be configured to have a UL carrier associated with a DL carrier of cell 200. This carrier can be referred to as a regular UL (RUL) carrier and can include a bandwidth portion (BWP)x. The WTRU can also be configured with one or more additional uplink carriers, which can be referred to as supplementary UL (SUL) carriers. The SUL carrier can include BWP y, and the RUL and SUL carriers can each be associated with a DL carrier of cell 200. Thus, both the RUL and SUL carriers can be associated with the same DL carrier or inherently linked to the same DL carrier (e.g., each DL carrier has more than one UL carrier). For example, a reference signal on the DL carrier can be used for channel estimation on the RUL and SUL carriers. One or more control channels on the DL carrier can be used to control the RUL and SUL carriers. The RUL and SUL carriers can utilize the same PCI.

[0092] The individual frequencies (or bands) of the DL, RUL, and / or SUL carriers can be the same or different. For example, the frequency (or band) of the SUL carrier can be higher or lower than the frequency (or band) of the DL carrier and / or RUL carrier. The RUL and SUL carriers can include corresponding configurations for power control settings. For example, the RUL and SUL carriers can each have separate (e.g., different) maximum power settings (e.g., PCMAX) and / or other related power parameters. Cell 200 can consider the SUL carrier for enhanced coverage, for example, in scenarios where the RUL carrier is beamformed and channel conditions (e.g., RSRP) are unfavorable. For example, as determined by cell 200, in some scenarios, the SUL carrier can be used to offload capacity from the RUL carrier. Cell 200 can choose to semi-statically configure the Physical Uplink Control Channel (PUCCH) on the SUL for better reliability while using the RUL carrier for capacity enhancement of data transmission. If the channel conditions (e.g., measured RSRP) are below a configured threshold, a resource allocation procedure can be initiated on the SUL carrier.

[0093] like Figure 2 As shown, the DL, RUL, and SUL carriers can cover area 206. At a given transmit power level, a lower frequency transmission can propagate a longer distance compared to a higher frequency transmission. Therefore, if the SUL carrier's frequency is lower than the RUL carrier's, the DL and SUL carriers can cover area 208, which can extend beyond area 206. If the SUL carrier's frequency is lower than the DL carrier's, the SUL carrier can cover area 210, which can extend beyond areas 206 and 208, thus capturing (or substantially capturing) the entire coverage area 204. Thus, the SUL carrier can be utilized, for example, when the WTRU moves towards the coverage edge of the RUL carrier in cell 200. It should be understood that the SUL carrier can be used to support one or more services (e.g., URLLC, eMBB, MTC, etc.), which may require higher throughput, improved transmission reliability, and / or lower latency.

[0094] For example, when the WTRU is configured to operate at a lower frequency (or band), it can perform transmissions on a SUL carrier. The WTRU may include a transmitter configured to change the transmission frequency when switching between RUL and SUL carriers. Therefore, the WTRU can be configured to perform transmissions sequentially or nearly simultaneously (e.g., via TDMA) on both RUL and SUL carriers. In this example, the WTRU may include more than one transmitter (e.g., at a given time or time interval, one is configured to transmit on the RUL carrier frequency, and another is configured to transmit on the SUL carrier frequency). Therefore, the WTRU can be configured to perform transmissions simultaneously on both RUL and SUL carriers.

[0095] The SUL carrier can be configured for any type of cell. Cell 200 can be, for example, part of a standalone radio system or a multi-RAT dual-connectivity radio system. Cell 200 can be a primary cell (PCell), a secondary cell (SCell), and / or a secondary PCell (SPCell), which can be used for dual connectivity.

[0096] For example, a WTRU operating in cell 200 may perform initial access using a RUL carrier and / or a SUL carrier. In this example, for instance, the WTRU may select an SUL carrier for initial access when the attributes of the serving cell's DL carrier are below a threshold, such as a configured threshold. The attributes of the DL carrier can be associated with any suitable threshold, such as the minimum reference received signal power (RSRP). Base station 202 of cell 200 may broadcast the SUL configuration via any suitable signaling, such as in the (e.g., minimum) system information (SI) of cell 200.

[0097] The WTRU can be configured to use SUL carriers in different operating modes, such as Radio Resource Control (RRC) connection mode. In an example of a first mode, the RRC entity can configure the WTRU to have multiple UL carriers, which can include RUL carriers configured via (e.g., typical) UL in cell 200. The multiple UL carriers can also include SUL carriers with a Sounding Reference Signal (SRS) configuration. In the example first mode, the WTRU can transmit (e.g., all) control and user data via the resources of the RUL carriers and can transmit SRS information using the resources of the SUL carriers. RRC configuration (or reconfiguration) can, for example, provide the WTRU with an extended, typical, and / or complete UL configuration to activate one of the UL carriers and / or switch the applicable active UL carrier associated with cell 200 (e.g., for some or all transmissions).

[0098] In the example of the second mode, the RRC entity can configure the WTRU to have multiple UL carriers with extended, typical, and / or complete UL configurations. This configuration may be sufficient for the WTRU to use the resources of the configured UL carriers (e.g., RUL and / or SUL carriers) to perform one or more UL transmissions (e.g., PUCCH, Physical Uplink Shared Channel (PUSCH), and / or Physical Random Access Channel (PRACH)). The WTRU can (e.g., subsequently) receive control signaling (e.g., via MAC Control Element (CE) or via Downlink Control Information (DCI)) that can activate and / or initiate handover between UL carriers, such as between RUL and SUL carriers.

[0099] In the example of the third mode, the RRC entity can configure the WTRU to have multiple UL carriers, which can be activated simultaneously and / or activated in a TDMA manner. This operating mode can restrict the WTRU to perform one or more types of UL transmissions simultaneously. For example, the WTRU may not transmit PUSCH for cell 200 simultaneously on RUL and SUL carriers. For example, this restriction can be configured if the WTRU does not support simultaneous transmission (e.g., for a configured frequency band), such as when the WTRU is equipped with a single transmitter.

[0100] The WTRU can be configured with one or more BWPs and / or associated UL carriers with cell 200. Each BWP can be characterized by subcarrier spacing, cyclic prefix and / or multiple contiguous physical resource blocks (PRBs) (e.g., via configuration aspects). Each BWP may include a frequency location, such as a center frequency.

[0101] The WTRU can be configured to have, for example, an initial BWP. For instance, the WTRU can be configured to have an initial BWP received from the SI, which allows the WTRU to access the system using the initial BWP of cell 200 and / or the associated UL carrier. The WTRU can be configured for initial access, for example, when the WTRU is in idle mode and / or when the WTRU determines it should establish an RRC connection to the system. The initial BWP configuration can include configurations for random access.

[0102] A WTRU can be configured to have a default BWP, such as when the WTRU is in connected mode. The default BWP can be the same as, similar to, or different from the initial BWP. The WTRU can determine to revert to the default BWP based on certain conditions, such as after a timer expires. In one example, the timer can correspond to a period of scheduled activity or inactivity.

[0103] A WTRU can be configured to have additional BWPs. For example, a WTRU can be configured to have one or more BWPs for a specific type of data transfer, such as those that support URLLC services.

[0104] Although the examples described herein are about selecting data and / or logical channels to be transmitted on different uplink carriers (e.g., RUL, SUL, etc.), the examples and criteria used for selection are equally applicable to selecting BWPs for a given transmission. For example, logical channels may be restricted to transmission on certain BWPs, and / or other criteria used herein to select appropriate UL carriers for transmission may be similarly used to select appropriate BWPs for transmission.

[0105] As described above, cell 200 can operate at a DL carrier frequency and (optionally) at a UL carrier frequency (e.g., a RUL carrier). Cell 200 can also operate using additional UL carriers such as SUL carriers. In the case of NR, the WTRU can be configured to operate using zero, one, two, or more uplink carriers (e.g., RUL and SUL carriers) associated with the DL carrier. The two or more UL carriers can be in different frequency bands, which may affect one or more of the WTRU's procedures. These procedures (one or more) can be obtained, for example, based on the path loss of DL transmissions in the same carrier.

[0106] The selection of the UL carrier used for a Layer 2 (L2) process may depend on one or more attributes associated with the radio system (e.g., factors, parameters, standards, conditions, triggering, quality, characteristics, etc.), such as DL and UL carriers, the radio service provided, and / or the data / information transmitted. One or more attributes may be used to determine which configured UL carrier can be used by the WTRU for a given transmission. This attribute may also be used to determine the transition between UL carriers (e.g., between RUL and SUL carriers) and / or any impact on the ongoing process.

[0107] As described above, the WTRU can be configured to have one or more SUL carriers for a given cell, for example... Figure 2 Cell 200 is shown. It should be understood that, in the case of a single SUL carrier described herein, the same considerations can be applied to a WTRU configured with multiple SUL carriers, whether a single SUL carrier or a combination of multiple SUL carriers. For example, the WTRU can select a first subset of applicable / available UL carriers (e.g., based on DL measurements that meet or exceed a specific threshold) and determine the applicable UL carriers (e.g., based on DCI or DCI-scheduled reception). UL carriers can be represented as configured UL BWPs. For example, the WTRU can determine the applicable SUL carriers based solely on the BWP (e.g., UL only) or in combination with other techniques described herein.

[0108] WTRUs can employ packet duplication by transmitting data / information sequentially or simultaneously using multiple UL carriers. Duplicate data can be transmitted on more than one UL carrier via RUL carriers and / or via one or more SUL carriers. Packet duplication can be useful when propagation conditions are degraded in a subset of carriers. Packet duplication can also be used to improve transmission reliability and / or latency.

[0109] The determination of one or more applicable UL carriers (e.g., selection and / or activation of RUL and SUL carriers) can be static, semi-static, and / or dynamic. Static determination of one or more applicable UL carriers can be configured, such as from reception of the SI and / or from a pre-configured source. Semi-static determination of one or more applicable UL carriers can be controlled via Layer 3 (L3) signaling and / or RRC. Dynamic determination of one or more applicable UL carriers can be controlled via Layer 1 (L1) or Layer 2 (L2) signaling, and / or via L1 / MAC signaling.

[0110] A WTRU configured with both RUL and SUL carriers can (for example, also) be configured with an SRS for the SUL carrier. In this way, the WTRU can be configured with thresholds, for example, to determine which UL carrier to select and / or activate.

[0111] The wireless network (e.g., via cell 200) can control the selection and / or activation of RUL and SUL carriers. In a semi-static configuration example, the WTRU can be initially configured (e.g., via an RRC entity) with an RUL carrier and a threshold (e.g., with or without SRS for the SUL carrier). Subsequently, the WTRU can be configured (e.g., via an RRC entity) with an SUL carrier when an event occurs.

[0112] In the example of dynamic configuration / signaling, the WTRU can receive indications of using RUL and / or SUL carriers (e.g., via DCI, DCI indication, and / or MAC CE). For example, reconfiguration of a cell (e.g., cell 200) with a SUL carrier can be transmitted via DCI, such as cross-carrier scheduling for carrier IDs using SUL carriers or BWP control for associated SUL carriers.

[0113] In an example combining semi-static and dynamic configuration / signaling, for instance, a DCI with a specific HARQ process ID can be used to communicate to the WTRU whether a RUL carrier and / or a SUL carrier are to be used. The WTRU can (e.g., initially) be configured with a set of different HARQ processes for the RUL and SUL carriers. Each HARQ process can include a process ID. The WTRU can determine which UL carrier to use, for example, based on the corresponding process ID, which can be indicated in the DCI (e.g., configured or dynamically assigned).

[0114] The WTRU can initiate RUL and / or SUL carrier selection and / or activation. In the example, the WTRU can determine that a corresponding threshold has been reached (or not reached), and once the threshold is reached, the WTRU can initiate a procedure to select RUL and / or SUL carriers and / or perform a handover between RUL and SUL carriers. The network (e.g., cell 200) can determine that a change in the applicable UL carrier has occurred. For example, the network can determine that the change occurred because the WTRU initiated an SRS transmission on the RUL and / or SUL carrier, a WTRU-initiated random access procedure, and / or a WTRU UL control information transmission. The WTRU may determine (and report such selection / handover) between RUL and / or SUL carriers based on one or more of the following: (i) one or more measurement report triggering events (e.g., MAC CE, Status Report (SR) transmission, measurement, RRC signaling, commencement of SRS on the SUL carrier, RACH on the SUL carrier, etc.); (ii) measurement or DL ​​path loss estimates, for example, when the WTRU may be time-aligned in the UL carrier, which have indications made by SRS transmissions (e.g., in the resources of the RUL or SUL carrier); and / or (iii) measurement or DL ​​path loss estimates with indications made by (e.g., in the resources of the RUL or SUL carrier) transmissions utilizing RACH (e.g., using specific preambles and / or PRACH resources). The network (e.g., cell 200) may indicate the handover, such as via MAC CE, DCI, RRC, etc., or may provide UL-SCH resources on the UL carrier.

[0115] It should be understood that the selection, switching, activation and / or initiation of RUL and / or SUL carriers can be any combination of, for example, static, semi-static, dynamic, pre-configured, network-controlled, WTRU-initiated, etc.

[0116] The activation, selection, and / or switching of RUL and / or SUL carriers can have a variety of (e.g., dynamic) causes or triggers, which can be determined, for example, based on one or more properties of the wireless system. For example, activation, selection, and / or switching can be based on one or more of the following attributes: (i) timing aspects (e.g., some time slots may be assigned UL carriers); (ii) the type of transmission used for transmission (e.g., URLLC, eMBB, mMTC, etc.), signal, and / or UL channel; (iii) the subcarrier spacing (SCS) used for transmission; (iv) logical channel (LCH) configuration; (v) type of service (e.g., URLLC, eMBB, mMTC); (vi) payload, amount of data available for transmission, and / or data size; (vii) indications in UL authorization or DL ​​assignment (e.g., indications of carriers used for HARQ feedback); (viii) redundant version (RV) of transmission (e.g., retransmission may use a different UL carrier than the previous (re)transmission); (ix) WTRU mobility or speed; and / or (x) the QoS (e.g., delay) requirements of the data to be transmitted.

[0117] Timing attributes may include system-dependent timing, such as system frame number (SFN), framing-dependent timing, and / or other timing, such as timing controlled by timers. For example, for framing-dependent timing, symbols, microslots, slots, and / or subframes may be assigned or associated with one or more associated UL carriers.

[0118] For the type of transmission to be transmitted (e.g., UL control information, RRC control plane signaling, user plane data), signal and / or UL channel (e.g., PUCCH, PUSCH, SRS, etc.), the WTRU may use a first carrier (e.g., RUL carrier) to perform the transmission of UL control information (e.g., HARQ feedback, channel quality indication (CQI) etc.), while the WTRU may perform the transmission of data on the resources of a second carrier (e.g., SUL carrier).

[0119] For SCS transmissions, the WTRU can perform a first transmission using the resources of a first UL carrier configured with a first SCS, and it can perform a second transmission using the resources of a second UL carrier configured with a second SCS, depending on configuration aspects, such as the association between bearer types (e.g., Signaling Radio Bearer (SRB) or Dedicated Radio Bearer (DRB) and the applicable SCS).

[0120] As will be combined below Figure 3-5Further discussion, regarding LCH configuration, the WTRU can be configured to have one or more applicable UL carriers associated with an LCH (or a group of LCHs, such as an LCH group (LCG) for transmitting data from the respective LCH). When the WTRU determines that it has (e.g., new) data available for transmission based on the LCH associated with the data, the WTRU can determine the applicable UL carrier. In another example, the QoS or priority configuration of the LCH can be used by the WTRU to determine which (or which) UL carriers will be used.

[0121] Service types can be linked to the access class configured in the network configuration, either in the Non-Access Stratum (NAS) or Access Stratum (AS). Service types can be advertised in the SI and / or provided by WTRU-specific signaling. Service types can also be linked to transport parameters in lower layers, such as parameter configuration and / or transport duration.

[0122] For the payload, the amount of data available for transmission, and / or the data size, the WTRU can be configured to determine the appropriate UL carrier, for example, based on the size of the data to be transmitted. For one or more LCHs, the size of the data to be transmitted may correspond to a transport block (TB), MAC PDU, RLC PDU, or Packet Data Convergence Protocol (PDCP) PDU for a given transmission, and / or the total amount of data available for transmission. For example, if the WTRU determines that the data amount is less than a (possibly configured) threshold, the WTRU can determine to use resources on a first UL carrier (e.g., a SUL carrier), or if the data amount is greater than the threshold, the WTRU can determine to use resources on a second UL carrier. The WTRU can perform UL carrier selection based solely on the threshold attribute or in combination with another attribute (e.g., licensed size or path loss estimation). For example, if the WTRU is configured with an SUL carrier, if the WTRU determines that the data amount is greater than a (possibly configured) threshold, and / or if the estimated path loss is less than the threshold and / or less than the WTRU's total available power minus a value associated with the relevant data size, the WTRU can determine to use resources on another UL carrier (e.g., a RUL carrier). Otherwise, the WTRU can use resources on the SUL carrier.

[0123] For indications in UL or DL ​​assignments, the WTRU may receive DL control signaling indicating the applicable UL carrier for HARQ feedback transmissions used in DL transmissions. For example, the WTRU may receive DL control signaling indicating the applicable UL carrier for TB transmissions in UL transmissions. This indication may be configurational, such as as indicated in a higher-layer (e.g., RRC layer) configuration received by the WTRU (e.g., via configured grants and / or via semi-persistent scheduling).

[0124] For the transmitted RV, HARQ retransmissions may use a different UL carrier than the previous (re)transmission, depending on the applicable RV. Thus, the WTRU can determine the applicable UL carrier, for example, from the sequence of (re)transmissions used in the HARQ process.

[0125] For WTRU mobility or speed, the WTRU may determine one or more applicable UL carriers based on its estimated speed, the frequency or number of switching over a period of time, and / or the frequency of paging or tracking area updates.

[0126] WTRU can adjust UL carrier selection individually or in combination with any of the above criteria when carrier availability and / or certain quality thresholds (e.g., RSRP) are met.

[0127] For example, when a triggering condition is met, the WTRU can (e.g., autonomously) switch from the RUL carrier to the SUL carrier.

[0128] The WTRU can receive licenses for RUL and / or SUL carriers, for example, licenses for the same time resources and / or overlapping time resources. UL licenses for both RUL and SUL carriers can be received in the same DCI or different DCIs. The WTRU can be configured (e.g., with functionality) to convert licenses received for RUL carriers to corresponding licenses in SUL carriers, and / or vice versa. This allows (e.g., fast) autonomous handover between RUL and SUL carriers by the WTRU when triggering conditions are met.

[0129] The WTRU can determine the UL carrier to be transmitted on the PUSCH. The WTRU can select the UL carrier for transmission on the PUSCH based on a priority order (e.g., a priority ordering process), which can be based on one or more of the following attributes of the radio system: (i) the estimated path loss to the RUL carrier and / or SUL carrier (e.g., a handover to the SUL carrier can be triggered when the path loss to the RUL carrier may be below a configured threshold); (ii) the power margin (PH) of the RUL carrier and / or SUL carrier (e.g., an SUL carrier can be used when the PH of the RUL carrier may be below a threshold such as 0 dB); (iii) the payload, the amount of data available for transmission, and / or the data size; and (iv) the size of one or more SUL licenses relative to the size of one or more RUL licenses (e.g., when the MAC is generated by the MAC multiplexing and assembly entity). (v) The PDU may be suitable for either authorization without segmentation; (vi) The LCH has buffered data and associated priorities (e.g., including any channel selection restrictions that can be imposed via the LCH Priority Ordering (LCP) procedure); (vi) The occurrence of one or more triggering events for UL carrier selection during the RACH procedure; and / or (vii) Dynamic RUL / SUL carrier selection criteria or conditions (e.g., indications via L1 / L2 signaling). For example, when simultaneous transmission on more than one UL carrier (e.g., RUL and SUL carriers) is unavailable, unreasonable, or impractical, the WTRU may select a UL carrier for transmission.

[0130] The WTRU can indicate to the network (e.g., cell 200) the selected ULs that the WTRU can use to transmit on the PUSCH. The WTRU can report information to the network by, for example, transmitting example types of uplink control information (UCI) (e.g., via RUL and / or SUL carriers) and / or multiplexing the UCI onto the PUSCH for the selected UL carrier, or multiplexing it onto (e.g., specific) PUCCH resources on RUL and / or SUL carriers.

[0131] The WTRU may (e.g., additionally or alternatively) be transmitted on RUL and / or SUL carriers according to an authorization that may specify the resources used for transmission on the RUL and / or SUL carriers. RUL and SUL transmissions may or may not be simultaneous. For example, the WTRU may be transmitted on a UL carrier with a larger SCS (e.g., first), and may (e.g., subsequently) be transmitted on a UL carrier with a smaller SCS (e.g., with the same or different RV). This may, for example, enable a network (e.g., cell 200) to attempt decoding the WTRU transmission (e.g., with lower latency) after (e.g., only) the first transmission.

[0132] Applicability restrictions can be utilized. In the example, the DCI indication in the authorized HARQ information can (e.g., implicitly or explicitly) provide (e.g., to the MAC entity) information about which UL carrier (e.g., RUL and / or SUL carrier) is used. The LCP procedure can be used to restrict the LCH (e.g., via the MAC entity) from using (or not using) a specific or designated UL carrier. For example, such restrictions can be used to enhance the reliability and / or latency of one or more LCHs within an LCH.

[0133] The LCP procedure may use one or more attributes related to the radio system (e.g., factors, parameters, criteria, conditions, triggers, quality, characteristics, etc.) to assign the LCH to the appropriate UL carrier. Attributes may involve one or more of the following: (i) system-dependent timing; (ii) type of UL transmission (e.g., UCI, control plane signaling, user plane data); (iii) SCS used for UL transmission; (iv) QoS requirements; (v) services supported by the UL transmission (e.g., URLLC, eMBB, mMTC, etc.); (vi) payload, size and / or amount of data to be transmitted; (vii) indications in UL and / or DL ​​assignment; (viii) RV of the transmission; (ix) mobility of the WTRU, such as WTRU speed, frequency of WTRU handover, and / or frequency of paging / tracking area updates; (x) radio coverage of the RUL and SUL carriers (e.g., RSRP measurements above or below a threshold); and / or (xi) priority of the data to be transmitted.

[0134] The RRC entity can use the LCP procedure to assign one or more LCHs from the WTRU's LCHs to corresponding UL carriers. For example, the RRC entity can assign a UL carrier based on one or more of the following: (i) a RUL carrier used only for UL-SCH resources; (ii) a SUL carrier used only for UL-SCH resources; and / or (iii) both RUL and SUL carriers (e.g., without restriction). Based on these properties, the RRC entity can instruct that replication should be performed on both the RUL and SUL carriers. The copied data can be transmitted sequentially or simultaneously on the RUL and SUL carriers.

[0135] The WTRU may include a receiver configured to receive one or more UL grants. The UL grants may include an allocation associated with a RUL carrier and an allocation associated with a SUL carrier. The RUL and SUL carriers may be associated with a common DL carrier of the serving cell. The WTRU may include a processor configured to select data for transmission from one or more logical channels based on an allocation in one or more UL grants. For example, a logical channel may be selected based at least on an allocation associated with a RUL carrier, and another logical channel may be selected based at least on another allocation associated with a SUL carrier. The WTRU may include a transmitter configured to transmit data on one logical channel on the RUL carrier and from another logical channel on the SUL carrier, according to the corresponding allocation.

[0136] Figure 3 Example LCP process 300 is shown. Figure 3 As shown, data to be transmitted by WTRU can be assigned to their respective priorities. For example, data can be associated with one or more LCHs, such as LCH1, LCH2, and LCH3. Data from LCH2 can have a higher priority than data from LCH1 and LCH3. Data from LCH1 can have a higher priority than data from LCH3. Therefore, data from LCH2 can be assigned the highest priority, and data from LCH3 can be assigned the lowest priority.

[0137] In addition to priority ordering data, the LCP procedure 300 may also include UL carrier assignment for data transmission. For example, as Figure 3 As further illustrated, data from LCH1, LCH2, and / or LCH3 can be assigned to one or more UL carriers (e.g., RUL and / or SUL carriers). Data from LCH1 can be assigned to RUL and SUL carriers based on radio coverage. For example, if the attributes of the RUL carrier are above a threshold, the WTRU can transmit data from LCH1 on the RUL carrier. This attribute can include an RSRP measurement associated with the RUL carrier. The RSRP measurement can be above the threshold, for example, when the WTRU is within a certain distance (e.g., within area 206) from a base station (e.g., base station 202). The RSRP measurement can be below the threshold when the WTRU is near the edge of the RUL carrier coverage area, for example, when the WTRU is near... Figure 2 When the boundary of region 206 in cell 200 is shown. If the attribute is below a threshold (e.g., because the WTRU has exceeded region 206 in cell 200), the WTRU can be configured to transmit data from LCH1 on the SUL carrier.

[0138] Data from LCH2 can correspond to specific services with certain transmission requirements, such as high reliability and / or low latency. For example, such as... Figure 3 As shown, data from LCH2 can correspond to URLLC type services. Thus, data from LCH2 can be copied and transmitted via RUL and SUL carriers. Data can be transmitted sequentially or simultaneously via RUL and SUL carriers.

[0139] Data from LCH3 can also correspond to specific services, such as eMBB. Data from LCH3 can be assigned for transmission via RUL carriers.

[0140] It should be understood that, in combination Figure 3 The prioritization process and channel assignment described above are merely exemplary. Other data prioritization processes and / or LCH UL channel assignments can be implemented while maintaining consistency with the disclosed embodiments.

[0141] Figure 4 An example TTI Series 400 is shown, during which WTRU is based on a combination Figure 3 The described LCP process 300 transmits data from one or more logical channels on a UL carrier, such as a RUL or SUL carrier. Figure 4 As shown, the WTRU can receive grant 1 for the RUL carrier and grant 2 for the SUL carrier. The WTRU can utilize the resources of the RUL and SUL carriers sequentially (e.g., in different TTIs) based on its capabilities. For example, the WTRU may not include multiple transmitters. Thus, the WTRU may not be able to transmit simultaneously on different frequencies, such as transmitting on both RUL and SUL carriers during the same TTI. The following will combine... Figure 5 An example of simultaneous transmission on RUL and SUL carriers is further described.

[0142] like Figure 4 As shown, Series 400 may include TTI1, TTI2, TTI3, TTI4, TTI5, and TTI6; however, it should be understood that Series 400 may include any number of TTIs. Data can be buffered from LCH1, LCH2, and LCH3 for UL transmission; however, it should also be understood that data can be buffered from any number of LCHs. During TTI1, TTI2, TTI3, TTI4, TTI5, and / or TTI6, data can be transmitted via a RUL carrier (License 1) and / or a SUL carrier (License 2). The RUL and SUL carriers may have transport block sizes (TBS) of 2k bits and 256 bits, respectively, although... Figure 4 The TBS values ​​for RUL and SUL carriers shown are merely illustrative.

[0143] In TTI1, no data can be buffered from LCH1 or LCH2, while 3k bits can be buffered from LCH3 (e.g., a new buffer). According to LCP procedure 300, the 3k bits buffered from LCH3 (e.g., data related to eMBB) can be transmitted via a RUL carrier. Thus, the WTRU can select a RUL carrier (License 1) to transmit 2k bits of buffered data from LCH3 during TTI1 (according to the example TBS of the RUL carrier).

[0144] In TTI2, no data can be buffered from LCH2, while 600 bits can be buffered from LCH1 (e.g., a new buffer), and 1k bits can remain buffered from LCH3 (e.g., 3k bits minus the 2k bits transmitted during TTI1). The 600 bits buffered from LCH1 can support certain services, such as those requiring URLLC. According to LCP procedure 300, the 600 bits buffered from LCH1 may have a higher priority than the 1k bits buffered from LCH3. Furthermore, if the properties of the RUL carrier (e.g., RSRP) are above a threshold, the 600 bits from LCH1 can be assigned to the RUL carrier. Figure 4 As shown, the RSRP of the RUL carrier can be lower than the configured threshold. Therefore, the WTRU can select the SUL carrier to transmit 256 bits of buffered data from LCH1 during TTI2 (according to the example TBS for the SUL carrier). It is understood that in this example, the RUL carrier may not be able to transmit 1k bits from LCH3 during TTI2 because the WTRU may not be able to transmit on both the RUL and SUL carriers simultaneously (e.g., during the same TTI) and / or because, according to example LCP procedure 300, the 600 bits from LCH1 have a higher priority than the 1k bits from LCH3. Thus, the 1k bits from LCH3 can remain buffered for transmission during one or more subsequent TTIs.

[0145] In TTI3, 344 bits can be retained from LCH1 buffer (e.g., 600 bits minus 256 bits transmitted during TTI2), 200 bits can be buffered from LCH2 (e.g., a new buffer), and 1k bits can be retained from LCH3 buffer (e.g., 3k bits minus 2k bits transmitted during TTI1). During TTI3, the measured RSRP can remain below a pre-configured threshold. According to LCP procedure 300, the 200 bits buffered from LCH2 can have a higher priority than the 344 bits buffered from LCH1 and the 1k bits buffered from LCH3. Furthermore, the 200 bits buffered from LCH2 can support URLLC services and can be copied for transmission on RUL and SUL carriers, which can improve transmission reliability and / or latency. Thus, the WTRU can select a RUL carrier (License 1) to transmit 200 bits buffered from LCH3 during TTI3, and select a SUL carrier (License 2) to transmit the same (e.g., duplicated) 200 bits buffered from LCH3 during TTI4. Alternatively, the WTRU can select a SUL carrier (License 2) for transmission during TTI3, and select a RUL carrier (License 1) for transmission during TTI4.

[0146] In TTI5, 344 bits can be held from the LCH1 buffer (e.g., 600 bits minus the 256 bits transmitted during TTI2), and 1k bits can be held from the LCH3 buffer (e.g., 3k bits minus the 2k bits transmitted during TTI1). After transmission on the RUL and SUL carriers during TTI3 and TTI4, no data can be held from the LCH2 buffer. During TTI5, the measured RSRP can exceed a pre-configured threshold. According to LCP procedure 300, the 344 bits buffered from LCH1 can have a higher priority than the 1k bits buffered from LCH3. Therefore, the WTRU can select the RUL carrier (License 1) to transmit the 344 bits from LCH1 during TTI5, and the 1k bits from LCH3 can be held buffered for transmission in one or more subsequent TTIs. Figure 4 As shown, if the network (e.g., cell 200) fails to successfully receive 344 bits via the RUL carrier, the WTRU can receive a negative acknowledgment (NACK) from the network (e.g., cell 200). The WTRU can also receive an indication (e.g., via DCI) to retransmit the 344 bits buffered from LCH1 via the SUL carrier during a subsequent TTI (e.g., TTI6).

[0147] In TTI6, 344 bits can be held in the buffer from LCH1 (e.g., 600 bits minus the 256 bits transmitted during TTI2), and 1k bits can be held in the buffer from LCH3 (e.g., 3k bits minus the 2k bits transmitted during TTI1). According to LCP procedure 300, the 344 bits buffered from LCH1 can have a higher priority than the 1k bits buffered from LCH3. Furthermore, the WTRU can receive signaling (e.g., via an instruction in the DCI) to retransmit the 344 bits initially transmitted during TTI5 via the SUL carrier. Thus, the WTRU can select the SUL carrier (License 2) to transmit the 256 bits buffered from LCH1 during TTI6 (according to the example TBS of the SUL carrier), and the 1k bits from LCH3 can be held in the buffer for transmission in one or more subsequent TTIs. After TTI6, assuming no new data is buffered from LCH1, LCH2, and / or LCH3, 88 bits can remain buffered from LCH1 (e.g., 344 bits minus the 256 bits transmitted during TTI6), while 1k bits can remain buffered from LCH3 (e.g., 3k bits minus the 2k bits transmitted during TTI1). The WTRU can continue processing the buffered data from LCH1, LCH2, and / or LCH3 after TTI6 according to LCP procedure 300.

[0148] Figure 5 An example TTI Series 500 is shown, during which WTRU is based on a combination Figure 3 The described LCP process 300 transmits data from one or more LCHs on a UL carrier, such as a RUL or SUL carrier. Figure 5 As shown, a WTRU can utilize the resources of both RUL and SUL carriers simultaneously (e.g., during the same TTI). For example, a WTRU may include two or more transmitters and may be able to transmit simultaneously on different frequencies, such as on RUL and SUL carriers during the same TTI.

[0149] like Figure 5 As shown, Series 500 may include TTI7, TTI8, TTI9, TTI10, TTI11, and TTI12, but it should be understood that Series 500 may include any number of TTIs. Data can be buffered from LCH1, LCH2, and LCH3 for UL transmission, but it should also be understood that data can be buffered from any number of LCHs. During TTI7, TTI8, TTI9, TTI10, TTI11, and / or TTI12, data can be transmitted via a RUL carrier (License 1) and / or a SUL carrier (License 2). The RUL and SUL carriers may have 2k bits and 256 bits of TBS, respectively, although... Figure 5The TBS values ​​for RUL and SUL carriers shown are merely illustrative.

[0150] In TTI7, no data can be buffered from LCH1 or LCH2, but 3k bits can be buffered from LCH3 (e.g., a new buffer). According to LCP procedure 300, the 3k bits buffered from LCH3 (e.g., data related to eMBB) can be transmitted via a RUL carrier. Thus, the WTRU can select a RUL carrier (License 1) to transmit 2k bits of buffered data from LCH3 during TTI7 (according to the example TBS of the RUL carrier).

[0151] In TTI8, no data can be buffered from LCH2, while 600 bits can be buffered from LCH1 (e.g., a new buffer), and 1k bits can remain buffered from LCH3 (e.g., 3k bits minus the 2k bits transmitted during TTI1). According to LCP procedure 300, the 600 bits buffered from LCH1 may have a higher priority than the 1k bits buffered from LCH3. Furthermore, if the properties of the RUL carrier (e.g., RSRP) are above a threshold, the 600 bits from LCH1 can be assigned to the RUL carrier. Figure 4 As shown, the RSRP of the RUL carrier can be lower than the configured threshold. Therefore, the WTRU can select the SUL carrier to transmit 256 bits of buffered data from LCH1 during TTI8 (based on the example TBS for the SUL carrier). In this example, the RUL carrier can transmit 1k bits from LCH3 during TTI8 because the WTRU can be able to transmit simultaneously on both the RUL and SUL carriers (e.g., during the same TTI). Therefore, the WTRU can also select the RUL carrier (License 1) to transmit 1k bits from LCH3 in TTI8.

[0152] In TTI9, 344 bits can remain buffered from LCH1 (e.g., 600 bits minus the 256 bits transmitted during TTI8), and 200 bits can be re-buffered from LCH2. After transmission on the RUL carrier during TTI8, no data can remain buffered from LCH3. During TTI9, the measured RSRP can be below a pre-configured threshold. According to LCP procedure 300, the 200 bits buffered from LCH2 can have a higher priority than the 344 bits buffered from LCH1. Furthermore, the 200 bits buffered from LCH2 can support URLLC services and can be copied for transmission on both RUL and SUL carriers, which can improve transmission reliability and / or latency. Thus, the WTRU can select RUL and SUL carriers (License 1 and 2) to each transmit the 200 bits buffered from LCH3 during TTI9.

[0153] In TTI10, 344 bits can be retained from the LCH1 buffer (e.g., 600 bits minus the 256 bits transmitted during TTI8). After transmissions during TTI7, TTI8, and / or TTI9, no data can be retained from the LCH2 or LCH3 buffer. During TTI10, the measured RSRP may exceed a pre-configured threshold. Therefore, the WTRU can select a RUL carrier (License 1) to transmit 344 bits from LCH1 during TTI10. Figure 5 As shown, if the network (e.g., cell 200) fails to successfully receive 344 bits via the RUL carrier, the WTRU can receive a NACK from the network (e.g., cell 200). The WTRU can also receive an indication (e.g., via DCI) to retransmit the 344 bits buffered from LCH1 via the SUL carrier during a subsequent TTI (e.g., TTI11).

[0154] In TTI11, 344 bits can remain buffered from LCH1 (e.g., 600 bits minus the 256 bits transmitted during TTI2). The WTRU may have received signaling (e.g., via an instruction in the DCI) to retransmit the 344 bits originally transmitted during TTI10 via the SUL carrier. Thus, the WTRU can select the SUL carrier (License 2) to transmit the 256 bits buffered from LCH1 during TTI11 (based on the example TBS for the SUL carrier).

[0155] During TTI12, 88 bits can be retained from the LCH1 buffer (e.g., 344 bits minus the 256 bits transmitted during TTI11). During TTI12, the measured RSRP may exceed a pre-configured threshold. Therefore, the WTRU can select a RUL carrier (License 1) to transmit the remaining 88 bits from the LCH1 buffer during TTI12.

[0156] The WTRU can receive control signaling (e.g., control plane signaling such as RRC signaling, or via MAC CE) that configures one or more (e.g., similar) restrictions for MAC CE or for a subset of MAC CE. For example, a subset of MAC CE may involve higher priority and / or reliability transmission types (e.g., URLLC) and / or may involve beam-managed MAC CE. Higher priority MAC CE may be restricted to certain types of UL access, such as RUL and / or SUL carriers.

[0157] The WTRU may receive control signaling (e.g., control plane signaling such as RRC signaling, or via MAC CE) that configures one or more (e.g., similar) restrictions for the grant type, such as one or more of the following: (i) grant determined based on the reception of dynamic control signaling (e.g., DCI on the Physical Downlink Control Channel (PDCCH); (ii) grant determined based on WTRU configuration or configuration type (e.g., type 2 UL transport without UL grant, semi-persistent grant); (iii) grant determined based on activation status (e.g., whether scheduling information for ungranted transport is active / available), and / or grant for dedicated transport or for contention-based transport.

[0158] The WTRU can receive control signaling (e.g., control plane signaling such as RRC signaling, or via MAC CE) that configures one or more (e.g., similar) limits for one or more LCHs to apply to one or more parts of an LCP process, such as LCP process 300. For example, the control signaling could indicate that steps 1 and 2 of the LCP process can only apply if resources can be allocated to satisfy the variable Bj for each LCH, where each TTI is set and updated via the priority bit rate (PBR) of the LCH. Authorization for the SUL carrier indication is used to implement different parts of the LCP process, for example, by serving all LCHs (e.g., in step 3). This can be used for, for example, throughput enhancement.

[0159] The WTRU can be configured to select and process data to be transmitted on one or more UL grants. The WTRU can determine that it has multiple received available grants, such as one for a RUL carrier and one for a SUL carrier, for transmissions using at least partially overlapping time resources. For example, when the WTRU is capable of simultaneous PUSCH transmissions on multiple ULs, the WTRU can assemble a MAC PDU for each applicable transmission on the RUL and / or SUL carriers (e.g., using LCP procedure 300). For example, when LCHs can be configured to be prioritized or restricted on a particular UL, the MAC entity can process an LCP procedure (e.g., LCP procedure 300) for granting on the UL suitable for the higher priority (e.g., first) LCH. The MAC entity can (e.g., additionally or alternatively) process one or more grants with the aim of maximizing the total data rate.

[0160] The WTRU can prioritize the available licenses on RUL and / or SUL carriers (e.g., via LCP procedure 300). For example, the WTRU can prioritize a selection when it may or may not be able to perform PUSCH transmissions on both RUL and SUL carriers simultaneously. Prioritization may consider one or more of the following: (i) the estimated path loss to the RUL and / or SUL carriers (e.g., a handover to the SUL carrier may be triggered when the path loss to the RUL carrier may be below a configured threshold); (ii) the PH of the RUL and / or SUL carriers (e.g., the WTRU may use the SUL carrier when the PH of the RUL carrier is below a threshold, such as 0 dB); (iii) the TBS of the SUL carrier relative to the TBS of the RUL carrier; and / or (iv) logical channels with buffered data and associated priorities (e.g., including any possible channel selection constraints based on the LCP procedure (e.g., LCP procedure 300)).

[0161] Examples of prioritizing available licenses based on the TBS of the SUL carrier relative to the TBS of the RUL carrier may include, for example: (i) when a MAC PDU generated by the MAC multiplexing and assembly entity can be adapted to the RUL carrier or the SUL carrier without segmentation, one or more UL licenses on the RUL carrier or the SUL carrier may be selected; (ii) one or more UL licenses on the RUL carrier or the SUL carrier may be selected to maximize the amount of data that the WTRU can transmit in (e.g., the current) TTI; and / or (iii) one or more UL licenses on the RUL carrier or the SUL carrier may be selected to maximize the amount of high-priority data that the WTRU can transmit in (e.g., the current) TTI.

[0162] In an example of LCHs with buffered data and associated priorities, some LCHs can be configured with selection restrictions. A MAC entity can, for example, select one or more UL grants, which can be associated with higher-priority LCHs, or can maximize the amount of data that the WTRU can send in the (e.g., current) TTI.

[0163] The MAC entity may include, for example, a HARQ entity for each serving cell with a configured UL, and may maintain a parallel HARQ process for each serving cell.

[0164] For example, when configuring a SUL carrier in a WTRU, HARQ can be modeled in a variety of (e.g., two) different ways.

[0165] As described above, RUL and / or SUL carriers can be part of the same serving cell. RUL and / or SUL carriers can, for example, share the same HARQ entity. A common set of HARQ procedures within a HARQ entity can be used for both RUL and / or SUL carriers. The gNB can be configured to use a subset of HARQ procedures that can be identified using RUL and / or SUL carriers. Cross-uplink retransmissions can be possible, for example, when a handover occurs between RUL and SUL carriers.

[0166] RUL and SUL carriers can be considered as separate carriers and can have separate HARQ entities. RUL and SUL carriers can (e.g., in either modeling example) have separate HARQ configurations, such as HARQ timeline values ​​(e.g., maxHARQ-Tx, maxHARQ-Msg3Tx).

[0167] For example, for a WTRU capable of (e.g., fast) handover between RUL and SUL carriers, a single or separate HARQ procedure can be used across multiple ULs. In the example, the WTRU can be configured with multiple (e.g., two) configured grants (e.g., SPS resources) on both RUL and SUL carriers. For example, when a handover event can be triggered, the applicable configured grant resources can be used. For example, when (e.g., a single) HARQ procedure can be used for UL transmissions across multiple UL carriers (e.g., RUL and SUL carriers), TB retransmissions between multiple ULs are possible.

[0168] WTRUs configured with multiple ULs having a specific number of HARQ retransmissions may result in different WTRU behaviors. In the example, retransmissions on the SUL carrier may occur, for example, after a specific (e.g., a threshold) number of UL HARQ transmissions using the RUL carrier. In an additional or alternative example, for example, when the WTRU (e.g., without UL-SCH resources on the SUL carrier) can reach the threshold number of UL HARQ transmissions using the RUL carrier, an SR may be triggered to request UL-SCH resources on the SUL carrier.

[0169] The WTRU can use RUL and / or SUL carriers, such as HARQ feedback reports used for DL ​​transmissions. In the example, the WTRU can select RUL and / or SUL carriers based on DL and / or UL measurements. For example, when both RUL and SUL can be active (e.g., available), the SUL carrier can be used (e.g., regardless), or the selection between RUL and SUL carriers can be based on DL path loss measurements. The WTRU can select reports reporting feedback on a specific UL or BWP based on semi-static configuration or dynamic indications from the network (e.g., cell 200).

[0170] For example, due to changes in propagation conditions that might prevent the WTRU from successfully transmitting feedback on the RUL carrier, the WTRU can use the SUL carrier to transmit feedback to the gNB. In this example, the WTRU can (e.g., autonomously) switch to the PUCCH on the SUL carrier, or it can receive an instruction from the gNB to do so. For example, when the gNB might not (e.g., in a timely manner) receive the expected feedback from the WTRU on the RUL carrier, the gNB can send an instruction to the WTRU to switch to the PUCCH on the SUL carrier. Feedback may be aggregated for multiple DL TBs or may not be aggregated.

[0171] In additional or alternative examples, the WTRU can transmit HARQ feedback on the RUL carrier. For example, once a HARQ acknowledgment (ACK) value has been transmitted on the RUL carrier, the WTRU can store that value. The WTRU can be polled to transmit multiple (e.g., previously transmitted) HARQ-ACK values ​​on the SUL carrier. For example, once a timer expires, once a value has been polled on the SUL carrier, and / or once a TB retransmission occurs, the WTRU can remove the stored value.

[0172] The WTRU can use packet replication and routing. The WTRU can be configured to have one or more UL carriers for a given cell, such as RUL and SUL carriers. The WTRU can determine that multiple UL carriers are available for UL transmission, for example, by being configured, activated, or based on scheduling information. The WTRU can determine that multiple UL carriers can be active simultaneously. When the WTRU determines that multiple UL carriers are active simultaneously, the WTRU can be configured to activate packet replication.

[0173] When the WTRU determines that multiple BWPs are activated simultaneously, for example, whether a BWP is configured for packet replication and / or after receiving an activation indication from the network (e.g., cell 200), the WTRU can be configured to activate packet replication.

[0174] The WTRU can activate packet replication for (e.g., robust) handover. For example, the WTRU can be configured to transmit a copy PDU to both the source and destination cells during handover. In the example, the WTRU can use the source cell's SUL carrier and the destination cell's RUL carrier to transmit the copy PDU. Alternatively, the WTRU can use the source cell's RUL carrier and the destination cell's SUL carrier to transmit the copy PDU. Activation of packet replication can depend on the content of the handover command.

[0175] The WTRU can determine whether replication is needed based on one or more attributes of the wireless system, such as radio (e.g., carrier) conditions determined by measurement. For example, when the WTRU is configured with both RUL and SUL carriers in a given cell, the WTRU can (e.g., only) activate replication if the measured cell quality (e.g., RSRP of the RUL and / or SUL carriers) is below a predefined threshold.

[0176] The WTRU can be configured to perform PDCP replication, for example, for one or more PDUs associated with one or more logical channels. The WTRU can activate replication in the PDCP. For example, the WTRU can determine, based on the reception of control signaling, such as via L1 / PDCCH, L2 MAC CE, or RRC entities, that multiple UL carriers (e.g., RUL and SUL carriers) are activated for a given cell (e.g., cell 200). The WTRU can determine replication based on semi-static, dynamic activation signaling, or a combination of both.

[0177] When the WTRU performs packet replication, the WTRU may: (i) replicate PDCP data PDUs for one or more specific radio bearers (e.g., radio bearers may be dynamically indicated by the network, semi-statically configured, or statically configured based on service or QoS requirements); (ii) replicate SRBs; (iii) replicate specific messages (e.g., measurement reports, including those used for beam management purposes); and / or (iv) replicate SDUs, whereby, for SDU replication, the PDCP SDU discards timers less than a specific threshold. The WTRU may determine to perform any of (i)-(iv) based on the configuration and / or reception of a repeat activation indication received by the WTRU via the network (e.g., cell 200) (e.g., through DCI, MAC CE, and / or RRC signaling).

[0178] The WTRU can determine to replicate one or more packets based on the received PDCP SR (e.g., the WTRU can apply replication to a specific PDU based on the received PDCP SR). The WTRU can determine that multiple PDUs can be retransmitted from the PDCP SR, and the WTRU can determine that the WTRU should perform replication for these PDUs. The WTRU can initiate cumulative retransmissions (e.g., where a handover implies a MAC reset) and can apply replication to (e.g., all) the cumulatively retransmitted PDUs.

[0179] A WTRU may not be able to transmit simultaneously on multiple UL carriers (e.g., RUL and SUL carriers) and BWPs. This may be due to one or more of the following attributes: (ii) received configuration signaling; (iii) WTRU capability; and / or (iii) radio conditions and measurements. Thus, the handover between UL carriers and / or BWPs may depend on the aforementioned attributes.

[0180] PDCP routing can depend on the WTRU receiving PDCP Status Reports (SRs). For example, the WTRU can select the UL or BWP for a specific PDU based on the received PDCP SR (e.g., the WTRU can determine that multiple PDUs can be retransmitted from the PDCP SR and select the same or different UL or BWP for these PDUs). The WTRU can initiate cumulative retransmissions (e.g., in the case of a handover implying a MAC reset) and can select the same or different UL or BWP for all cumulatively retransmitted PDUs.

[0181] WTRUs can use HARQ-based replication and routing. Simultaneous activation of RUL and SUL carriers activates HARQ-based replication for a specific HARQ, which can be configured to have replication. HARQ can, for example, transmit copies of the TB on RUL and SUL carriers simultaneously or consecutively. Due to the activation of more than one BWP, HARQ can transmit copies of the TB on RUL and SUL carriers. Replication can be semi-static or dynamically activated signaling, or a combination of both.

[0182] The WTRU can determine the use of simultaneous HARQ-based replication based on the received grant on the SUL carrier and the received grant on the RUL carrier. The grant on the SUL carrier can be pre-configured. The timing of the configured grant can be relative to the timing of the grant used for the RUL carrier.

[0183] WTRU can determine whether to use replication based on the retransmission rate (RV) signaled by the retransmission signal. For example, if the RV is above a certain number, WTRU can activate HARQ-based replication.

[0184] WTRU can determine whether to use replication based on the parameter configuration or physical layer characteristics of different BWP or UL carriers. For example, if the parameter configurations of the BWP or UL carriers are the same, HARQ-based replication can be activated.

[0185] The WTRU can determine the replication of activation on more than one BWP based on a BWP with a different parameter configuration than the BWP used for the initial transmission. For example, for a retransmitted TB, the TB can be retransmitted on the BWP where the initial transmission occurred, and the same TB can be transmitted on a newly activated BWP, for example, as a retransmission with an updated RV on the same HARQ, or as a new transmission on a separate HARQ. The WTRU can determine the replication of activation due to the activation of one or more SUL carriers, which may have different parameter configurations or subcarrier spacings.

[0186] A WTRU can transmit a copy of a given TB by interleaving transmissions in the time domain, such as on symbols in the same time slot, on symbols in different time slots, or on symbols in different TTIs. This is useful when the WTRU may not be able to perform simultaneous transmissions, for example, based on the WTRU's capabilities, one or more configuration aspects, and / or the parameters involved.

[0187] WTRUs can use HARQ routing. WTRUs may not be able to transmit simultaneously on RUL and SUL carriers or on more than one BWP. Switching between UL carriers or BWPs can depend on attributes such as the capabilities of the WTRU.

[0188] For (e.g.) new TB transmissions, the network can provide a portion of scheduling / HARQ information indicating which UL carrier or BWP the authorization belongs to.

[0189] For retransmissions, if the WTRU cannot retransmit on a different parameter configuration, and the SUL carrier or BWP whose parameter configuration differs from that of the initial transmission becomes active before receiving an ACK for the TB, the WTRU may: (i) remain on the UL carrier or BWP used for the initial transmission until an ACK for the TB is received; (ii) remain on the UL carrier or BWP used for the initial transmission until an ACK for the TB is received or the retransmission of the relevant TB is successfully completed, for example when the WTRU has a license on the UL carrier or BWP used for the initial transmission; and / or (iii) switch to the SUL carrier or a new BWP (e.g., if a NACK is received, the WTRU may use an SR configuration that distinguishes the parameter configuration of the initial transmission to send the SR).

[0190] For retransmissions, if the RSRP is less than the configured threshold and the configured number of retransmissions or the configured number of RVs is reached, the WTRU can perform random access using the SUL carrier to obtain authorization for the retransmission. The WTRU can send SRs with appropriate configuration to obtain authorization on the SUL carrier, thereby performing the retransmission, for example, based on the service, the QoS of the retransmitted data, or the priority of the LCH involved.

[0191] A WTRU can be configured to transmit on multiple UL carriers (e.g., RUL and SUL carriers) in a wireless system. Activation, selection, initiation, and / or handover of such UL carriers can be, for example, static, semi-static, dynamic, pre-configured, reconfiguration-based, network-controlled, and / or WTRU-initiated. A WTRU can be configured to perform HARQ processing, for example, when activating a SUL carrier and / or handover between RUL and SUL carriers. A WTRU can be configured with an LCP procedure for UL-SCH authorization on RUL and / or SUL carriers. A WTRU can be configured for PDCP replication and / or routing to RUL and / or SUL carriers, for example, for Signaling Radio Bearers (SRBs), radio bearers, specific messages, and / or SDUs. A WTRU can be configured to have HARQ-based replication and / or multiple authorizations on UL carriers. The timing of authorizations on SUL carriers can, for example, be relative to the timing of authorizations on RUL carriers.

[0192] The processes and methods described herein can be applied in any combination, to other wireless technologies, and for other services.

[0193] WTRU can involve the identifier of a physical device, or the identifier of a user, such as a subscription-related identifier like an MSISDN or SIP URI. WTRU can also involve application-based identifiers, such as usernames that can be used by each application.

[0194] Each computing system described herein may have one or more computer processors with memory configured with executable instructions or hardware to perform the functions described herein, including determining the parameters described herein and sending and receiving messages between entities (e.g., WTRUs and networks) to perform the functions described herein.

[0195] The above processes can be implemented in computer programs, software, and / or firmware, which are incorporated into computer-readable media for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as CD-ROMs and / or digital multifunction discs (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver used in WTRUs, terminals, base stations, RNCs, and / or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU) including a processor and a memory, the processor and memory being configured to: Receive configuration information, the configuration information indicating that data corresponding to a first set of one or more logical channels can be transmitted using a first type of uplink (UL) grant and data corresponding to a second set of one or more logical channels can be transmitted using a second type of UL grant; Receive a first UL grant and a second UL grant, wherein the first UL grant and the second UL grant at least partially overlap in the time domain, the first UL grant corresponding to a first type of UL grant, and the second UL grant corresponding to a second type of UL grant; The first set of one or more logical channels includes a first logical channel having data available for transmission, the first logical channel being associated with a first priority; The second set of one or more logical channels includes a second logical channel having data available for transmission, the second logical channel being associated with a second priority, the first priority being higher than the second priority; Based on the fact that the first priority is higher than the second priority, the first UL authorization is prioritized over the second UL authorization; and Based on prioritizing the first UL grant over the second UL grant, data associated with the first set of one or more logical channels is transmitted according to the first UL grant.

2. The WTRU of claim 1, wherein the processor and memory are configured to prioritize the first UL authorization over the second UL authorization, comprising: The processor and memory are configured to ignore the second UL authorization.

3. The WTRU of claim 1, wherein at least one of the first UL authorization or the second UL authorization is received via Radio Resource Control (RRC) signaling.

4. The WTRU of claim 1, wherein at least one of the first UL authorization or the second UL authorization is received via downlink control information (DCI).

5. The WTRU of claim 1, wherein the first logical channel corresponds to the highest priority logical channel in the first set of one or more logical channels that has data available for transmission, and the second logical channel corresponds to the highest priority logical channel in the second set of one or more logical channels that has data available for transmission.

6. The WTRU of claim 1, wherein the first UL authorization is associated with a first UL transport resource, and the second UL authorization is associated with a second UL transport resource.

7. The WTRU of claim 1, wherein the configuration information is received in a Radio Resource Control (RRC) message.

8. The WTRU of claim 1, wherein at least one of the first UL authorization or the second UL authorization is a configured authorization.

9. A method implemented by a wireless transmit-receive unit (WTRU), the method comprising: Receive configuration information, the configuration information indicating that data corresponding to a first set of one or more logical channels can be transmitted using a first type of uplink (UL) grant and data corresponding to a second set of one or more logical channels can be transmitted using a second type of UL grant; Receive a first UL grant and a second UL grant, wherein the first UL grant and the second UL grant at least partially overlap in the time domain, the first UL grant corresponding to a first type of UL grant, and the second UL grant corresponding to a second type of UL grant; The first set of one or more logical channels includes a first logical channel having data available for transmission, the first logical channel being associated with a first priority; The second set of one or more logical channels includes a second logical channel having data available for transmission, the second logical channel being associated with a second priority, the first priority being higher than the second priority; Based on the fact that the first priority is higher than the second priority, the first UL authorization is prioritized over the second UL authorization; and Based on prioritizing the first UL grant over the second UL grant, data associated with the first set of one or more logical channels is transmitted according to the first UL grant.

10. The method of claim 9, wherein prioritizing the first UL authorization over the second UL authorization comprises: Ignore the second UL authorization.

11. The method of claim 9, wherein at least one of the first UL authorization or the second UL authorization is received via Radio Resource Control (RRC) signaling.

12. The method of claim 9, wherein at least one of the first UL authorization or the second UL authorization is received via downlink control information (DCI).

13. The method of claim 9, wherein the first logical channel corresponds to the highest priority logical channel in the first set of one or more logical channels that is available for data transmission, and the second logical channel corresponds to the highest priority logical channel in the second set of one or more logical channels that is available for data transmission.

14. The method of claim 9, wherein the first UL authorization is associated with a first UL transport resource, and the second UL authorization is associated with a second UL transport resource.

15. The method of claim 9, wherein the configuration information is received in a Radio Resource Control (RRC) message.

16. The method of claim 9, wherein at least one of the first UL authorization or the second UL authorization is a configured authorization.

17. A wireless transmit / receive unit (WTRU) including a processor and a memory, the processor and memory being configured to: The first uplink (UL) transport grant and the second UL transport grant are determined to overlap at least partially in time; Based on Logical Channel Priority (LCP) restriction information received for the first logical channel and the second logical channel, it is determined that the first logical channel is mapped to the first UL transmission grant and the second logical channel is mapped to the second UL transmission grant, wherein the first logical channel is associated with a first priority, which is the highest priority in a first set of one or more logical channels mapped to the first UL transmission grant and having data available for transmission, and the second logical channel is associated with a second priority, which is the highest priority in a second set of one or more logical channels mapped to the second UL transmission grant and having data available for transmission; Based on the fact that the first priority is higher than the second priority, the first UL transmission grant is prioritized over the second UL transmission grant; and Based on the fact that the first priority is higher than the second priority, the second UL transmission authorization is discarded.

18. The WTRU of claim 17, wherein the processor and memory are configured to prioritize the first UL transfer grant over the second UL transfer grant, comprising: The processor and memory are configured to use the first UL transmission grant to perform a transmission associated with the first logical channel during a time interval in which the first UL transmission grant overlaps with the second UL transmission grant.

19. The WTRU of claim 17, wherein at least one of the first UL transmission grant or the second UL transmission grant is received via Radio Resource Control (RRC) signaling.

20. The WTRU of claim 17, wherein at least one of the first UL transmission grant or the second UL transmission grant is received via downlink control information.

21. The WTRU of claim 17, wherein the LCP restriction information is received by the WTRU via Radio Resource Control (RRC) signaling.

22. The WTRU of claim 17, wherein the first UL transport grant is associated with a first UL transport resource, and the second UL transport grant is associated with a second UL transport resource, and wherein the first UL transport resource and the second UL transport resource at least partially overlap in time.

23. The WTRU of claim 22, wherein the first UL transmission resource and the second UL transmission resource are associated with the same transmission time interval.

24. The WTRU of claim 17, wherein at least one of the first UL transfer grant or the second UL transfer grant is a configured grant.

25. The WTRU of claim 17, wherein the LCP constraint maps the first logical channel and the second logical channel to corresponding UL carriers.

26. A method implemented by a wireless transmit-receive unit (WTRU), the method comprising: The first uplink (UL) transport grant and the second UL transport grant are determined to overlap at least partially in time; Based on Logical Channel Priority (LCP) restriction information received for the first logical channel and the second logical channel, it is determined that the first logical channel is mapped to the first UL transmission grant and the second logical channel is mapped to the second UL transmission grant, wherein the first logical channel is associated with a first priority, which is the highest priority in a first set of one or more logical channels mapped to the first UL transmission grant and having data available for transmission, and the second logical channel is associated with a second priority, which is the highest priority in a second set of one or more logical channels mapped to the second UL transmission grant and having data available for transmission; Based on the fact that the first priority is higher than the second priority, the first UL transmission grant is prioritized over the second UL transmission grant; and Based on the fact that the first priority is higher than the second priority, the second UL transmission authorization is discarded.

27. The method of claim 26, wherein prioritizing the first UL transfer grant over the second UL transfer grant comprises: During the time interval in which the first UL transmission grant overlaps with the second UL transmission grant, the first UL transmission grant is used to perform a transmission associated with the first logical channel.

28. The method of claim 26, wherein at least one of the first UL transmission grant or the second UL transmission grant is received via Radio Resource Control (RRC) signaling.

29. The method of claim 26, wherein at least one of the first UL transmission grant or the second UL transmission grant is received via downlink control information.

30. The method of claim 26, wherein the LCP restriction information is received by the WTRU via Radio Resource Control (RRC) signaling.

31. The method of claim 26, wherein the first UL transmission grant is associated with a first UL transmission resource, and the second UL transmission grant is associated with a second UL transmission resource, and wherein the first UL transmission resource and the second UL transmission resource at least partially overlap in time.

32. The method of claim 31, wherein the first UL transmission resource and the second UL transmission resource are associated with the same transmission time interval.

33. The method of claim 26, wherein at least one of the first UL transfer authorization or the second UL transfer authorization is a configured authorization.

34. The method of claim 26, wherein the LCP constraint maps the first logical channel and the second logical channel to corresponding UL carriers.

Images