Multiple TRPs and panel transmissions using dynamic bandwidth for NR

Abstract

To provide methods and systems employing multiple transmission points and transmission panels for transmission with dynamic bandwidth.SOLUTION: There is provided an apparatus UE on a network, at least including a non-transitory memory including instructions stored thereon for re-establishing a remote radio control (RRC) connection with a base station gNB. A processor operably coupled to the non-transitory memory executes an instruction determining that a radio link failure has occurred between a first bandwidth portion (BWP) of the apparatus tuned to the base station, executes an instruction of initiating a random access (RA) procedure, executes an instruction of determining whether a configured contention-based physical random access channel (PRACH) resource overlaps with the first BWP, executes an instruction of transmitting a RA preamble including the configured contention-based PRACH resource to the base station, and executes an instruction of receiving a RA response from the base station.SELECTED DRAWING: Figure 25

Description

Technical Field

[0001] <Cross - Reference to Related Applications> This application claims the benefit of priority of U.S. Provisional Application No. 62 / 556,005, filed on September 8, 2017, entitled "Multiple TRPs and Panel Transmissions Using Dynamic Bandwidth of NR"; U.S. Provisional Application No. 62 / 564,897, filed on September 28, 2017, entitled "Multiple TRPs and Panel Transmissions Using Dynamic Bandwidth of NR"; U.S. Provisional Application No. 62 / 587,248, filed on November 16, 2017, entitled "Multiple TRPs and Panel Transmissions Using Dynamic Bandwidth of NR"; and U.S. Provisional Application No. 62 / 616,009, filed on January 11, 2018, entitled "Multiple TRPs and Panel Transmissions Using Dynamic Bandwidth of NR", all of which are hereby incorporated by reference in their entirety as part of this specification.

[0002] <Field> This application relates to a method and system for using multiple transmission points (TRPs) and transmission panels for transmission using the dynamic bandwidth of New Radio (NR).

Background Art

[0003] Existing architectures do not support signaling and configuration methods when an NR user equipment (UE) needs to monitor multiple physical downlink control channels (PDCCHs) or PDCCHs scheduled simultaneously from the main TRP.

[0004] Existing architectures may include a wideband component carrier (Component Carrier: CC) and a bandwidth part (Bandwidth Part: BWP) supported by a user equipment (UE) composed of multiple links. However, there is no protocol to explain how the active band functions using multiple TRPs / panels. Also, there is no protocol for transmitting independent or joint PDCCH from multiple TRPs / panels.

[0005] In the case of Physical Uplink Control Channel (Physical Uplink Control Channel: PUCCH) transmission, the quasi-static PUCCH resource setting can be shared at the TRP via a non-ideal backhaul. However, there is no collision resolution protocol to prevent multiple TRPs from scheduling the Physical Uplink Shared Data Channel (Physical Uplink Shared Data Channel: PUSCH) with the same resources.

[0006] In some cases, zero resources are set for the bandwidth part on the P cell or S cell. However, there is no protocol for the UE to handle zero resources for the BWP. SUMMARY OF THE INVENTION

[0007] This summary is provided to introduce, in a simplified form, a selection of concepts that are further described in the detailed description below. This summary is not intended to limit the scope of the subject matter recited in the claims. The aforementioned needs are substantially met by the present application.

[0008] One aspect of the present application relates to an apparatus on a network that includes a non - transient memory storing instructions for re - establishing a Remote Radio Control (RRC) connection with a base station. The apparatus also includes a processor operably coupled to the non - transient memory and capable of executing instructions to determine that a radio link failure has occurred between a first Bandwidth Part (BWP) of the apparatus tuned to the base station. This processor also executes instructions to initiate a Random Access (RA) procedure. The processor also executes instructions to determine whether a configured contention - based Physical Random Access Channel (PRACH) resource overlaps with the first BWP. The process further executes instructions to transmit an RA preamble including the configured contention - based PRACH resource to the base station. This processor further executes instructions to receive an RA response from the base station.

[0009] Another aspect of the present application relates to an apparatus on a network that includes a non - transient memory storing instructions for performing beam recovery. The apparatus also includes a processor operably coupled to the non - transient memory and capable of executing instructions to determine beam quality associated with an active Bandwidth Part (BWP) being less than a predetermined threshold. The processor also executes instructions to initiate a Random Access (RA) procedure. The processor further executes instructions to transmit a Beam Recovery Request (BRR). The processor also further executes instructions to wait for a Random Access Response (RAR) from the base station.

[0010] Another aspect of the present application relates to a device on a network that includes a non-transitory memory storing instructions for operating the device in zero bandwidth part (BWP) mode. The device also includes a processor operatively coupled to the non-transitory memory that can execute instructions to configure the device to monitor a selection function during non-BWP operation. The device also executes instructions to monitor an active or default BWP for received control signals. The device further executes instructions to evaluate the periodicity of the received control signals. The device further executes instructions to determine that a timer for zero BWP operation has expired. The device further executes instructions to return to an active or default BWP via radio resource control (RRC) after the timer has expired.

[0011] As described above, certain embodiments of the present invention have been outlined quite broadly in order to better understand the detailed description thereof and to better understand the contribution of the present invention to the art.

Brief Description of the Drawings

[0012] To facilitate a stronger understanding of the present application, reference is now made to the accompanying drawings, where like elements are referred to by like numerals. These drawings are not to be construed as limiting the present application and are intended for illustration only.

Figure 1A

Figure 1B

Figure 1C

Figure 1D

Figure 1E

Figure 1F

Figure 2

Figure 3

Figure 4A

Figure 4B

Figure 4C

Figure 5A

Figure 5B

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11A

Figure 11B

Figure 12A

Figure 12B

Figure 13A

Figure 13B

Figure 13C

Figure 14A

Figure 14B

Figure 15A

Figure 15B

Figure 16A

Figure 16B

Figure 17A

Figure 17B

Figure 17C

Figure 18A

Figure 18B

Figure 19A

Figure 19B

Figure 20A

Figure 20B

Figure 21A

Figure 21B

Figure 22A

Figure 22B

Figure 22C

Figure 23A

Figure 23B

Figure 24A

Figure 24B

Figure 25

Figure 26

Figure 27

Figure 28A

Figure 28B

Figure 29

Figure 30A

Figure 30B

Figure 31A

Figure 31B

Figure 32

Figure 33

Figure 34

Figure 35A

Figure 35B

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41A

Figure 41B

Figure 42

DETAILED DESCRIPTION OF THE INVENTION

[0013] A detailed description of exemplary embodiments will be given with reference to the various figures, embodiments, and aspects of this specification. This description provides detailed examples of possible implementations, but it should be understood that these details are intended to be examples and do not limit the scope of this application.

[0014] In general, this application relates to methods and systems for monitoring multiple PDCCHs. This application also relates to methods and systems for configuring BWPs. This application also relates to methods and systems for PUCCH resource allocation.

[0015] <DEFINITIONS / ACRONYMS> Definitions of terms and phrases commonly used in this application are provided in the following table.

[0016]

TABLE 1

[0017] <GENERAL ARCHITECTURE> The 3rd Generation Partnership Project (3GPP) is developing technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities (including work on codecs, security, and quality of service). Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced standards. 3GPP has begun work on standardizing the next generation of cellular technology, known as NR (which is also referred to as "5G"). The development of the 3GPP NR standard is expected to include the definition of a next generation radio access technology (new RAT), which will include the provision of new flexible radio access below 6 GHz and new ultra-high speed and high-capacity mobile radio access above 6 GHz. The flexible radio access will consist of new radio access without backward compatibility in the new spectrum below 6 GHz and is expected to include various operating modes that can be multiplexed in the same spectrum to address a wide set of NR use cases with different requirements. Ultra-high speed and high-capacity mobile communications are expected to include the cm-wave and mm-wave spectra, which will provide opportunities for ultra-high speed and high-capacity mobile communication access, for example, for indoor applications and hotspots. In particular, ultra-high speed and high-capacity mobile communications are expected to share a common design framework with the flexible radio access below 6 GHz, using design optimizations specific to the cm-wave and mm-wave spectra.

[0018] 3GPP has identified various use cases that NR is expected to support, resulting in a wide range of user experience requirements for data speed, latency, and mobility. The use cases include the following general categories: namely, enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high broadband access indoors, broadband access in hotspots, 50+ Mbps anywhere, low-cost broadband access, mobile broadband in vehicles), mission-critical communications, massive machine-type communications, network operations (e.g., network slicing, routing, mobility and interworking, energy savings), and enhanced vehicle-to-everything (eV2X) communications. Specific services and applications within these categories include, for example, monitoring and sensor networks, remote control of devices, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, in-vehicle emergency notification systems, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, and virtual reality. This document assumes all of these use cases and other use cases as well.

[0019] FIG. 1A shows one embodiment of an exemplary communication system 100 in which the methods and apparatuses described and claimed herein can be implemented. As shown, the exemplary communication system 100 can include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, and / or 102d (which can generally or collectively be referred to as WTRU 102), radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e can be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Although each of the WTRUs 102a, 102b, 102c, 102d, 102e is shown as a handheld wireless communication device in FIGS. 1A - 1E, in the various use cases contemplated for 5G wireless communication, each WTRU can comprise, or be embodied as, any type of device or apparatus configured to transmit and / or receive wireless signals, and by way of example only, can include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular telephones, personal digital assistants (PDAs), smartphones, laptops, tablets, netbooks, notebook computers, personal computers, wireless sensors, home appliances, wearable devices such as smartwatches or smartware, medical or eHealth devices, robots, industrial equipment, drones, vehicles such as cars, trucks, trains, or airplanes, etc.

[0020] The communication system 100 can also include base stations 114a and 114b. Base station 114a can be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, and / or other network 112. Base station 114b can be any type of device configured to interface, wired and / or wirelessly, with at least one of remote radio heads (RRHs) 118a, 118b and / or transmission and reception points (TRPs) 119a, 119b to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, and / or other network 112. RRHs 118a, 118b can be any type of device configured to wirelessly interface with at least one of WTRUs 102c to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, and / or other network 112. TRPs 119a, 119b can be any type of device configured to wirelessly interface with at least one of WTRUs 102d to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, and / or other network 112. For example, base stations 114a, 114b can be base transceiver stations (BTSs), Node Bs, eNode Bs, home Node Bs, home eNode Bs, site controllers, access points (APs), and wireless routers, etc. Although base stations 114a, 114b are each shown as a single element, it will be understood that base stations 114a, 114b can include any number of interconnected base stations and / or network elements.

[0021] Base station 114a may be part of RANs 103 / 104 / 105, which may also include other base stations and / or network elements (not shown) such as a Base Station Controller (BSC), a Radio Network Controller (RNC), a relay node, etc. Base station 114b may be part of RANs 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown) such as a Base Station Controller (BSC), a Radio Network Controller (RNC), a relay node, etc. Base station 114a may be configured to transmit and / or receive radio signals within a specific geographical area, which may be referred to as a cell (not shown). Base station 114b may be configured to transmit and / or receive wired and / or radio signals within a specific geographical area, which may be referred to as a cell (not shown). The 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 can include three transceivers, for example, one for each sector of the cell. In one embodiment, base station 114a can employ Multiple-Input Multiple Output (MIMO) technology and thus can utilize multiple transceivers for each sector of the cell.

[0022] Base station 114a can communicate with one or more of WTRUs 102a, 102b, 102c via air interfaces 115 / 116 / 117, which can be any suitable wireless communication link [e.g., Radio Frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.]. The air interfaces 115 / 116 / 117 can be established using any suitable Radio Access Technology (RAT).

[0023] The base station 114b can communicate with one or more of the RRHs 118a, 118b, and / or the TRPs 119a, 119b via a wired interface or an air interface 115b / 116b / 117b that can be a wired (e.g., cable, optical fiber, etc.) or wireless [radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.] communication link. The air interface 115b / 116b / 117b can be established using any suitable radio access technology (RAT).

[0024] The RRHs 118a, 118b, and / or the TRPs 119a, 119b can communicate with one or more of the WTRUs 102c, 102d via an air interface 115c / 116c / 117c that can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115c / 116c / 117c can be established using any suitable radio access technology (RAT).

[0025] More specifically, as described above, the communication system 100 is a multi-connection system and can adopt one or more channel access methods such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in RAN103 / 104 / 105 and WTRU102a, 102b, 102c, or the RRH118a, 118b and WTRU102c, 102d as well as TRP119a, 119b in RAN103b / 104b / 105b can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), and they can each use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c. 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).

[0026] In some embodiments, the base station 114a and the RRHs 118a, 118b and the TRPs 119a, 119b of the WTRUs 102a, 102b, 102c, or the RANs 103b / 104b / 105b and the WTRUs 102c, 102d can implement radio technologies. For example, Evolved UMTS Terrestrial Radio Access (E-UTRA) can use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) respectively to establish the air interfaces 115 / 116 / 117 or 115c / 116c / 117c. In the future, the air interfaces 115 / 116 / 117 may implement 3GPP NR technology.

[0027] In some embodiments, the base station 114a in the RANs 103 / 104 / 105 and the RRHs 118a, 118b and the TRPs 119a, 119b of the WTRUs 102a, 102b, 102c, or the RANs 103b / 104b / 105b and the WTRUs 102c, 102d can implement radio technologies such as IEEE 802.16 [e.g., Worldwide Interoperability for Microwave Access (WiMAX)], CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0028] In Figure 1A, the base station 114c may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connection in a local area such as a workplace, home, vehicle, campus, etc. In one embodiment, the base station 114c and the WTRU 102e may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114c and the WTRU 102d may implement a wireless technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or a femtocell. As shown in Figure 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114c may not need to access the Internet 110 via the core network 106 / 107 / 109 in some cases.

[0029] RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b may communicate with the core network 106 / 107 / 109, and the core network may be any type of network that provides voice, data, application, and / or Voice Over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location information services, prepaid calls, Internet connections, video delivery, etc., and / or may perform high-level security functions such as user authentication.

[0030] Although not shown in FIG. 1A, it will be understood that RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b and / or core networks 106 / 107 / 109 may communicate directly or indirectly with other RANs that use the same or a different RAT than RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b. For example, in addition to being connected to RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b that may utilize E-UTRA radio technology, core networks 106 / 107 / 109 may also be in communication with another RAN (not shown) that uses GSM radio technology.

[0031] Core networks 106 / 107 / 109 may also function as gateways for WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 includes a circuit-switched telephone network that provides a conventional Plain Old Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP / IP Internet protocol suite. The network 112 may include a wired or wireless communication network owned and / or operated by another service provider. For example, the network 112 may include another core network connected to one or more RANs that may employ the same or a different RAT than RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b.

[0032] Some or all of the WTRUs 102a, 102b, 102c, 102d of the communication system 100 can include a multi-mode function. For example, the WTRUs 102a, 102b, 102c, 102d, and 102e can include a plurality of transceivers for communicating with different wireless networks via different wireless links. For example, the WTRU 102e shown in FIG. 1A can be configured to communicate with a base station 114a that may employ a cellular-based wireless technology and a base station 114c that may employ an IEEE 802 wireless technology.

[0033] FIG. 1B is a block diagram of an exemplary apparatus or device configured for wireless communication, such as the WTRU 102, according to the embodiments shown herein. As shown in FIG. 1B, the exemplary WTRU 102 can include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / display device 128, a non-removable memory 130, a removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. It will be understood that the WTRU 102 can include sub-combinations of the foregoing elements while maintaining consistency with the embodiments. Also, the embodiments assume that the base stations 114a and 114b, and / or the nodes represented by the base stations 114a and 114b, such as, but not limited to, base transceiver stations (BTSs), Node Bs, site controllers, access points (APs), home Node Bs, evolved home Node Bs (eNodeBs), home evolved Node Bs (HeNBs), home evolved Node B gateways, and proxy nodes, can include some or all of the elements shown in FIG. 1B and described herein.

[0034] Processor 118 may be a general - purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or other functions that enable the WTRU 102 to operate in a wireless environment. Processor 118 is coupled to transceiver 120, and transceiver 120 may be coupled to transmit / receive element 122. Although FIG. 1B shows processor 118 and transceiver 120 as separate components, it will be understood that processor 118 and transceiver 120 may be integrated within an electronic package or chip.

[0035] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via the air interfaces 115 / 116 / 117. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. Although not shown in FIG. 1A, it will be understood that the RANs 103 / 104 / 105 and / or the core network 106 / 107 / 109 can communicate directly or indirectly with other RANs using the same RAT as the RANs 103 / 104 / 105 or a different RAT. For example, in addition to being connected to RANs 103 / 104 / 105 that may utilize E - UTRA radio technology, the core network 106 / 107 / 109 may also be communicating with another RAN (not shown) that uses GSM radio technology.

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

[0037] Some or all of the WTRUs 102a, 102b, 102c, 102d of the communication system 100 can include multimode functionality. For example, the WTRUs 102a, 102b, 102c, and 102d can include multiple transceivers for communicating with different wireless networks via different wireless links. For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with a base station 114a that can employ a cellular-based wireless technology and a base station 114b that can employ IEEE 802 wireless technology.

[0038] Figure 1B is a block diagram of an exemplary apparatus or device configured for wireless communication according to an embodiment shown herein, such as WTRU 102. As shown in Figure 1B, the exemplary WTRU 102 can include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / display 128, a non-removable memory 130, a removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripheral devices 138. It will be understood that the WTRU 102 can include sub-combinations of the foregoing elements while maintaining compliance with the embodiments. The embodiments also contemplate that base stations 114a and 114b, and / or nodes represented by base stations 114a and 114b, such as, but not limited to, inter alia, a base transceiver station (BTS), a Node B, a site controller, an access point (AP), a home Node B, an evolved home Node B (eNodeB), a home evolved Node B (HeNB), a home evolved Node B gateway, and a proxy node can include some or all of the elements shown in Figure 1B and described herein.

[0039] Processor 118 may be, for example, a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, other types of integrated circuit (IC), and a state machine. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or other functions that enable the WTRU 102 to operate in a wireless environment. Processor 118 is coupled to transceiver 120, which may be coupled to transmit / receive element 122. Although FIG. 1B shows processor 118 and transceiver 120 as separate components, it will be appreciated that processor 118 and transceiver 120 may be integrated into an electronic package or chip.

[0040] Transmit / receive element 122 may be configured to transmit signals to and / or receive signals from a base station (e.g., base station 114a) via air interface 115 / 116 / 117. For example, in one embodiment, transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In a further embodiment, transmit / receive element 122 may be configured to transmit and receive both RF signals and optical signals. It will be understood that transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0041] In addition, although the transmit / receive element 122 is shown in FIG. 1B as a single element, the WTRU 102 can include any number of transmit / receive elements 122. More specifically, the WTRU 102 can employ MIMO technology. Thus, in one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interfaces 115 / 116 / 117.

[0042] The transceiver 120 can be configured to modulate the signals to be transmitted by the transmit / receive element 122 and to demodulate the signals received by the transmit / receive element 122. As described above, the WTRU 102 can have a multimode function. Thus, the transceiver 120 can include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs such as, for example, UTRA and IEEE 802.11.

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

[0044] The processor 118 can receive power from a power source 134 and can be configured to distribute and / or control power to other components within the WTRU 102. The power source 134 can be any suitable device for supplying power to the WTRU 102. For example, the power source 134 can include one or more dry cells, solar cells, and fuel cells, among others.

[0045] The processor 118 may also be coupled to a GPS chipset 136 that may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via the air interface 115 / 116 / 117, and / or may determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information by any suitable positioning method while maintaining consistency with the embodiments.

[0046] The processor 118 may further be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connections. For example, the peripheral devices 138 may include various sensors such as an accelerometer, a biometric (e.g., fingerprint) sensor, an electronic compass, a satellite transceiver, a digital camera (for photos or video), a Universal Serial Bus (USB) port or other interconnect interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a Frequency Modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0047] WTRU102 may be embodied in a sensor, a household appliance, a wearable device such as a smart watch or smart clothing, a medical or e-health device, a robot, an industrial device, a drone, a vehicle such as a car, a truck, a train, or another device or apparatus such as an airplane. WTRU102 can be connected to other components, modules, or systems of such a device or apparatus via one or more interconnect interfaces, such as an interconnect interface that may include one of the peripheral devices 138.

[0048] Figure 1C is a system diagram of RAN 103 and core network 106 according to one embodiment. As described above, RAN 103 can communicate with WTRU 102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN 103 can also communicate with core network 106. As shown in Figure 1C, RAN 103 can include Node Bs 140a, 140b, 140c, each including one or more transceivers, for communicating with WTRU 102a, 102b, 102c via air interface 115. Each of Node Bs 140a, 140b, 140c can be associated with a particular cell (not shown) within RAN 103. RAN 103 can also include RNCs 142a, 142b. It will be understood that RAN 103 can include any number of Node Bs and RNCs while maintaining consistency with the embodiments.

[0049] As shown in Figure 1C, nodes B140a, 140b may be in communication with RNC142a. Additionally, node B140c may be in communication with RNC142b. Nodes B140a, 140b, 140c can communicate with their respective RNCs 142a, 142b via the Iub interface. RNCs 142a, 142b may be in communication with each other via the Iur interface. Each of RNCs 142a, 142b may be configured to control the respective nodes B140a, 140b, 140c to which it is connected. Further, each of RNCs 142a, 142b can be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, and data encryption.

[0050] The core network 106 shown in Figure 1C may include a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. Although each of the foregoing elements is shown as part of the core network 106, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0051] RNC 142a within RAN 103 may be connected to MSC 146 within core network 106 via the IuCS interface. MSC 146 may be connected to MGW 144. MSC 146 and MGW 144 can provide access to a circuit-switched network such as PSTN 108 to WTRUs 102a, 102b, 102c to facilitate communication between WTRUs 102a, 102b, 102c and conventional wired communication devices.

[0052] In RAN103, RNC142a may also be connected to SGSN148 in core network 106 via the IuPS interface. SGSN148 may be connected to GGSN150. SGSN148 and GGSN150 can provide access to a packet switched network such as the Internet 110 for WTRU102a, 102b, 102c, facilitating communication between WTRU102a, 102b, 102c and IP-enabled devices.

[0053] As described above, core network 106 may also be connected to network 112, which can include other wired or wireless networks owned and / or operated by other service providers.

[0054] Figure 1D is a system diagram of RAN104 and core network 107 according to one embodiment. As described above, RAN104 can use E-UTRA radio technology to communicate with WTRU102a, 102b, and 102c via air interface 116. RAN104 can also communicate with core network 107.

[0055] RAN104 can include eNodeBs 160a, 160b, 160c, although it will be understood that RAN104 can include any number of eNodeBs while maintaining consistency with the embodiment. Each of eNodeBs 160a, 160b, 160c can include one or more transceivers for communicating with WTRU102a, 102b, 102c via air interface 116. In one embodiment, eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, eNodeB 160a, for example, can transmit wireless signals to and receive wireless signals from WTRU102a using multiple antennas.

[0056] Each of the eNodeBs 160a, 160b, and 160c is associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink and / or downlink, etc. As shown in Figure 1D, the eNodeBs 160a, 160b, 160c can communicate with each other via the X2 interface.

[0057] The core network 107 shown in Figure 1D can include a Mobility Management Gateway (MME) 162, a Serving Gateway 164, and a Packet Data Network (PDN) Gateway 166. Although each of the foregoing elements is shown as part of the core network 107, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0058] The MME 162 may be connected to each of the eNodeBs 160a, 160b, and 160c within the RAN 104 via the S1 interface and can function as a control node. For example, the MME 162 can be responsible for user authentication of the WTRUs 102a, 102b, 102c, activation / deactivation of bearers, and selection of a particular serving gateway during the initial attach of the WTRUs 102a, 102b, 102c. The MME 162 may also provide control plane functions for switching between the RAN 104 and other RANs (not shown) using other radio technologies such as GSM or WCDMA.

[0059] The serving gateway 164 can be connected to each of the eNodeBs 160a, 160b, and 160c within the RAN 104 via the S1 interface. The serving gateway 164 can generally route and transfer user data packets to / from the WTRUs 102a, 102b, and 102c. The serving gateway 164 can also perform other functions, for example, anchor the user plane during handover between eNodeBs, trigger paging when downlink data is available to the WTRUs 102a, 102b, and 102c, and manage and store the context of the WTRUs 102a, 102b, and 102c.

[0060] The serving gateway 164 may also be connected to the PDN gateway 166, which can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, and 102c and facilitate communication between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0061] The core network 107 can facilitate communication with other networks. For example, the core network 107 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, and 102c and facilitate communication between the WTRUs 102a, 102b, and 102c and conventional terrestrial communication devices. For example, the core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between the core network 107 and the PSTN 108. The core network 107 can also provide access to the network 112 to the WTRUs 102a, 102b, and 102c, and the network 112 can include other wired or wireless networks owned and / or operated by other service providers.

[0062] Figure 1E is a system diagram of RAN 105 and core network 109 according to one embodiment. RAN 105 can be an Access Service Network (ASN) that communicates with WTRU 102a, 102b, and 102c via air interface 117 using IEEE 802.16 wireless technology. As will be further described below, communication links between different functional entities WTRU 102a, 102b, 102c, RAN 105, and core network 109 may be defined as reference points.

[0063] As shown in Figure 1E, RAN 105 can include base stations 180a, 180b, 180c, and ASN gateway 182, although it will be understood that RAN 105 can include any number of base stations and ASN gateways while maintaining consistency with the embodiment. Base stations 180a, 180b, 180c are each associated with a specific cell within RAN 105 and can include one or more transceivers for communicating with WTRU 102a, 102b, 102c via air interface 117. In one embodiment, base stations 180a, 180b, 180c may implement MIMO technology. Thus, for example, base station 180a can transmit wireless signal(s) to WTRU 102a and receive wireless signal(s) from WTRU 102a using multiple antennas. Base stations 180a, 180b, 180c can also provide mobility management functions such as handoff triggering, tunnel establishment, radio resource management, traffic classification, and enforcement of Quality of Service (QoS) policies. ASN gateway 182 can function as a traffic aggregation point and be responsible for paging, caching of subscriber profiles, routing to core network 109, etc.

[0064] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point implementing the IEEE 802.16 specification. Further, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point that may be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0065] The communication links between each of the base stations 180a, 180b, and 180c may be defined as an R8 reference point that includes a protocol for facilitating WTRU handover and transfer of data between base stations. The communication links between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point. This R6 reference point may include a protocol for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0066] As shown in FIG. 1E, the RAN 105 may be connected to the core network 109. The communication link between the RAN 105 and the core network 109 may be defined as an R3 reference point that includes, for example, a protocol for facilitating data transfer and mobility management functions. The core network 109 may include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. Although each of the foregoing elements is shown as part of the core network 109, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0067] The MIP-HA is responsible for IP address management and may enable the WTRU 102a, 102b, and 102c to roam between different ASNs and / or different core networks. The MIP-HA 184 can provide access to a packet switched network such as the Internet 110 to facilitate communication between the WTRU 102a, 102b, 102c and IP-enabled devices. The AAA server 186 can be responsible for user authentication and support of user services. The gateway 188 can facilitate interaction with other networks. For example, the gateway 188 can provide access to a circuit switched network such as the PSTN 108 to facilitate communication between the WTRU 102a, 102b, 102c and a conventional land communication device. In addition, the gateway 188 can provide access to the network 112 for the WTRU 102a, 102b, 102c, and the network 112 can include other wired or wireless networks owned and / or operated by other service providers.

[0068] Although not shown in FIG. 1E, it will be understood that the RAN 105 may be connected to other ASNs and the core network 109 may be connected to other core networks. The communication link between the RAN 105 and other ASNs can be defined as an R4 reference point and can include a protocol for coordinating the mobility of the WTRU 102a, 102b, 102c between the RAN 105 and other ASNs. The communication link between the core network 109 and other core networks can be defined as an R5 reference and can include a protocol for facilitating interaction between the home core network and the visited core network.

[0069] The core network entities described herein and shown in FIGS. 1A, 1C, 1D, and 1E are identified by the names given to the entities in certain existing 3GPP specifications. However, in the future, these entities and functions may be identified by other names, and it is understood that certain entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Accordingly, the specific network entities and functions described and illustrated in FIGS. 1A, 1B, 1C, 1D, and 1E are provided by way of example only, and the subject matter disclosed and claimed herein is understood to be implementable or realizable in any similar communication system, whether currently defined or to be defined in the future.

[0070] FIG. 1F is a block diagram of an exemplary computing system 90, where one or more devices of the communication network shown in FIGS. 1A, 1C, 1D, and 1E, such as a RAN 103 / 104 / 105, a core network 106 / 107 / 109, a PSTN 108, the Internet 110, or other network 112, can be embodied in a particular node or functional entity. The computing system 90 may include a computer or a server and may be mainly controlled by computer-readable instructions, which can be in the form of software, regardless of where or by what means such software is stored or accessed. Such computer-readable instructions may be executed within a processor 91 to cause the computing system 90 to perform work. The processor 91 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and a state machine, etc. The processor 91 can execute signal encoding, data processing, power control, input / output processing, and / or other functions that enable the computing system 90 to operate in a communication network. The coprocessor 81 is an optional processor separate from the main processor 91 that executes additional functions or assists the processor 91. The processor 91 and / or the coprocessor 81 can receive, generate, and process data related to the methods and apparatuses disclosed herein.

[0071] In operation, the processor 91 fetches, decodes, and executes instructions, and exchanges information with other resources via the system bus 80, which is the main data transfer path of the computing system. Such a system bus connects components in the computing system 90 and defines a medium for data exchange. The system bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and operating the system bus. An example of such a system bus 80 is the Peripheral Component Interconnect (PCI) bus.

[0072] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such a memory includes circuits that can store and retrieve information. The ROM 93 generally contains stored data that cannot be easily changed. The data stored in the RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to the RAM 82 and / or ROM 93 can be controlled by the memory controller 92. The memory controller 92 may provide an address translation function that converts virtual addresses to physical addresses when instructions are executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in the first mode can access only the memory mapped by its own process virtual address space. Unless memory sharing between processes is set up, it cannot access the memory within the virtual address space of another process.

[0073] Furthermore, the computing system 90 can include a peripheral device controller 83 responsible for communicating instructions from the processor 91 to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85.

[0074] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output can include text, graphics, animated graphics, and video. The visual output is provided in the form of a graphical user interface (GUI). The display 86 can be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes the electronic components necessary to generate the video signal transmitted to the display 86.

[0075] Furthermore, the computing system 90 can include a communication circuit such as, for example, the network adapter 97, which can be used to connect the computing system 90 to an external communication network such as the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110, or other networks 112 of FIGS. 1A, 1B, 1C, 1D, and 1E, enabling the computing system 90 to communicate with other nodes or functional entities of these networks. The communication circuit can be used, alone or in combination with the processor 91, to perform the transmission and reception steps of the specific devices, nodes, or functional entities described herein.

[0076] Any or all of the apparatuses, systems, methods, and processes described herein can be implemented in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor such as processor 118 or 91, cause the processor to execute and / or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein can be implemented in the form of computer-executable instructions that are executed on a processor of a device or computing system configured for wireless and / or wired network communication. A computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data, but does not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible or physical media that can be used to store the desired information and that can be accessed by a computing system.

[0077] <Reference Signals in LTE> 3GPP TR38.913 defines the scenarios and requirements of next-generation access technologies. The main characteristic evaluation indicators (KPIs) for eMBB, URLLC, and mMTC devices are summarized in Table 2.

[0078]

Table 2

[0079] <LTE TM10> TM10 is defined in 3GPP Rel-11 and includes the following functions: (i) Enables DL CoMP operation and is configurable per serving cell. (ii) TM10 provides a serving cell that configures the UE to evaluate and report multiple sets of CSI-RS, thereby enabling the evaluation of multiple transmission points of the CoMP measurement set. (iii) TM-10 also supports the use of UE-specific DMRS for DL transmission (two UE DMRS scrambling IDs). (iv) Supports the use of DCI-1A and the new DCI format 2D, which is used for CS / CB or enables PDSCH resource element mapping when using JP.

[0080] <Configuration method for multiple TRPs / panels> According to one aspect of the present application, the UE can monitor multiple PDCCHs or schedule multiple PDSCHs simultaneously. The monitoring is performed when the UE is configured using two (or more) non-zero power NZP-CSI (CSI-RS) processes. The monitoring can also occur when the PDSCH and quasi-collocation indicator (or PQI) fields in the DCI (configured parameter set "n") indicate multiple CORESETs.

[0081] In one embodiment, the CSI process is a time series of subframes, where CSI-RS and IMR correspond to a given transmission hypothesis. The time series of the subframes is where the CSI is fed back. For example, in the subframe of the first CSI process, TRP1 sets and transmits CSI-RS using the initialization parameter Y1. In the subframe of the second process, TRP2 sets and transmits CSI-RS using the initialization parameter Y2. The values of the parameters Y1 and Y2 are set for the UE by RRC or MAC-CE signaling. The NZP-CSI-RS process can be triggered by periodic or aperiodic setting of CSI requests. For multiple TRPs, the CSI trigger can use the M-bit CSI request field. An example of M = 2 bits is shown in Table 3 below.

[0082] [Table 3]

[0083] Here, the CSI process is defined by the CSI-RS resource, the CSI-IM resource, and the reporting mode. The CSI process is the following association, namely, (i) the settings of the numerology, slot, and subframe, (ii) one non-zero power CSI-RS resource from the CoMP measurement set, (iii) one interference measurement resource (IMR), (iv) one CSI reporting mode (PUCCH or PUSCH), and (v) other feedback-related parameters such as codebook subset restrictions, which is the RRC / MAC-CE set for the UE.

[0084] For example, to support 2TRP transmission, unique CSI-RS is transmitted by each cooperative TRP. The UE is set with two CSI-RS resources to provide an estimated value of the channel quality. Each CSI-RS resource is transmitted from one of the transmission points. For example, CSI-RS#0 is transmitted from TRP1, and CSI-RS#1 is transmitted from TRP2. In particular, four transmission hypotheses can be implemented by four CSI processes. Adoption of CSI-RS and CSI-IM resources. The following Table 4 shows this embodiment.

[0085] [Table 4]

[0086] As shown in Table 4 above, the CSI-IM #0 resource is used for both TRP1 and TRP2 to measure interference. There are two options for the CSI report. In the first option, individual TRP reports are executed. Specifically, when individual CSI report settings are set for each TRP, the UE reports the PMI / RI, codebook, and CQI for reporting the TRP. In the second option, a joint TRP report is executed. Specifically, when the UE is set with a single CSI report setting, the UE jointly reports the PMI / RI, codebook, and CQI of each TRP.

[0087] According to an exemplary embodiment in a narrow band (NB), the UE stays in a wideband CC and is triggered in multiple CSI processes based on the following scenarios. For example, one of the options for the CSI report is based on determining whether any of the configured (NZP) CSI-RS and / or CSI-IM resources are not present in the active band even though they are triggered by a CSI request. If so, the UE can ignore the corresponding CSI report and terminate the CSI selection process that is not in the active band. On the other hand, if the CSI of multiple TRPs is reported together and is not in the active band, the CSI report is set to zero. Alternatively, if it is not in the active band, the reported CSI is truncated. If the CSI of multiple TRPs is reported individually, there is no corresponding CSI report activity. Further, if the CSI-RS resource is not present in the active band and is QCLed using a DMRS group, when gap CSI measurement is supported, the associated DMRS group cannot be used for PDSCH demodulation.

[0088] If the CSI-RS resource is not in the active band and is outside the active band (or gap), CSI measurement is permitted. Therefore, one or more of the corresponding CSI processes can be executed. In one CSI process, gap CSI measurement set via upper layer signaling is performed. To support the active band, if upper layer signaling RRC or MAC-CE updates the CSI-RS and / or CSI-IM resource configuration parameters, when a new CSI request is reissued, the UE can reactivate the corresponding CSI process.

[0089] One embodiment is illustratively shown in FIG. 2, according to which the configured CSI-RS resource #1 from TRP2 is not in the active band and gap CSI measurement is not permitted / supported. In that case, CSI processes #0, #1, and #3 shown in Table 3 can be terminated. Here, there are two CSI-RS resources #0 (from TRP1) and #1 (from TRP2) configured for multiple TRPs. The CSI-RS #0 resource is in the active band. The CSI-RS #1 resource is not in the active band. Since the UE does not support or enable gap measurement due to power saving or UE function limitation, gap measurement is not permitted. Therefore, the corresponding CSI process (or hypothesis) related to the CSI-RS resource #1 is process #0, and processes #1 and #3 can be stopped.

[0090] According to yet another embodiment, exemplarily shown in FIG. 3, if the configured CSI-RS resource #1 from TRP2 is not in the active band and gap CSI measurement is supported, CSI processes #0, #1, and #3 can be processed when a CSI request is triggered, as referenced in Table 4 above. Here, there are two CSI-RS resources #0 (from TRP1) and #1 (from TRP2) configured for multiple TRPs. However, only the CSI-RS #0 resource is in the active band. The CSI-RS #1 resource is not in the active band. Since gap measurement is supported, the corresponding CSI process (or hypothesis) related to CSI-RS resource #1 in Table 4 can be reported.

[0091] <PDSCH Rate Matching and Quasi-Co-Location Indicator Setting> According to yet another embodiment, the UE can decode multiple PDSCHs by setting to an "N" parameter set list via RRC and / or MAC-CE signaling and by the detected PDCCH with DCI for the UE and a given serving cell. The UE should use the parameter set list for each value of the PDSCH and quasi-co-location indicator field of the detected PDCCH with DCI (i.e., the mapping defined in Table 5 below) to determine the PDSCH antenna port quasi-co-location. The configured parameter set list can include one or two RS sets. The UE infers that one or two antenna ports of the DM-RS port group of the PDSCH of the serving cell are quasi-co-located with the corresponding one or two RS sets given by the shown parameter set list. Each RS set is set using one or more RSs that are QCLed with the DM-RS ports within the corresponding DM-RS group.

[0092]

Table 5

[0093] The parameter set "n" set by RRC and / or MAC-CE can include the following parameter settings. That is, (i) the TRS position (number of ports and frequency shift) of the cell / TRP, (ii) the cell / TRP number, secrets, slot, and subframe settings, (iii) zero-power CSI-RS (CSI-IM) settings, (iv) the value of the PDSCH start symbol, (v) the CSI-RS resource indicator of the DMRS quasi-collocation, (vi) the SS burst set location of the cell / TRP, and (vii) the CORESET location for monitoring a single PDCCH or multiple PDCCHs.

[0094] For the sake of clarification, the parameter set "n" set by RRC and / or MAC-CE for multiple TRPs / panels can enable the UE to perform the signaling of the capabilities of two NR-PDCCH / PDSCH while setting multiple PDCCHs at different times.

[0095] Assuming that the UE is set to monitor multiple (or two) PDCCHs and the UE receives PDCCH transmissions from both the primary PDCCH (primary TRP) and the secondary PDCCH (secondary TRP), the primary PDCCH and the secondary PDCCH can be received simultaneously. The active band can be dynamically set by the primary cell or TRP. The primary PDCCH and the secondary PDCCH can be received in different time slots.

[0096] The active band can be set individually by the primary PDCCH and the secondary PDCCH, as well as by DCI. When supporting DPS / DCS using BWP, for example, the UE monitors multiple PDCCHs from the primary TRP or the secondary TRP in different or the same time slots, and each TRP can individually and dynamically set the active band. This is illustrated exemplarily in FIGS. 4A to 4C.

[0097] According to another embodiment, assuming that the UE receives PDCCH transmissions from the primary PDCCH, when the UE is configured to monitor a single PDCCH, the primary PDCCH should simultaneously schedule multiple PDSCHs. This is exemplarily shown in FIGS. 5A - B.

[0098] Regarding the DMRS configuration of the PDSCH (any TRP), since the DCI sets the corresponding DMRS resources for DCS / DPS cases, it can be transparent to the TRP. For the NCJT case, since there is only one group of DM - RS ports permitted for each TRP within the adjustment set, in order to minimize the number of DCI formats, at each PQI state within the DCI, two RS sets with the same RS index can be set from the corresponding TRP. This is illustrated in FIG. 6.

[0099] The DMRS group set can be used to indicate the PUCCH resources for HARQ process A / N feedback and CSI reports. The A / N of different HARQ processes can include either multiplexing or bundling. If only the UE is configured, it is the (primary) simultaneously scheduling PDCCH.

[0100] According to one embodiment, a detailed design method for indicating UL PUCCH resource allocation via CSI - RS or DMRS configuration is described. Specifically, the seed value used for initializing the scrambling sequence of the CSI - RS is set as follows.

[0101]

Number

[0102] Here, Y can take any value within the range of all possible cell IDs and does not have to be the cell ID of the serving cell (or other cells within the CoMP measurement set). The PUCCH resource can be set as a function of Y. For example, the PUCCH resource can be expressed as f(Y), where f(Y) is a mapping function of Y, and the PDCCH resource mapping from two CSI-RSs, Y1 and Y2, is equal to f(Y1) and f(Y2) respectively. To ensure that two PDCCH resources do not overlap, f(Y1) ≠ f(Y2) for Y1 ≠ Y2. f(Y1) and f(Y2) are assigned to different non-overlapping OFDM symbols. For example, the PUCCH resources from different TRPs are TDM. Therefore, when Y1 ≠ Y2, the PUCCH resources from different TRPs do not overlap. If multiple (or two) PUCCHs are set up individually, one CSI-RS or DMRS can be used to uniquely determine the PUCCH resource. Note that if multiple (or two) PUCCHs are set up individually, one CSI-RS or DMRS can be used to uniquely determine the PUCCH resource. The number of transmission layers from each TRP can be independently set by the PDCCH DCI or by scheduling each PDCCH DCI simultaneously.

[0103] For a TDD or self-contained subframe system, the UL BWP is set in the same way as the configured DL BWP. Since the UE is not expected to retune the center frequency of the channel BW between the DL and UL of a TDD or self-contained subframe system, no extra upper layer or DCI signaling is required. In the case of an FDD system, the assigned UL BWP can be independently set via the UL grant. In an exemplary embodiment, FIG. 7 shows an example of the BWP configuration of an FDD system. There are two UL BWPs set via the UL grant. The first UL BWP #1 starts with the m-th PRB, and the second UL BWP #2 starts with the n-th PRB.

[0104] <Default BWP> In yet another embodiment of the application, for a gNB or a cell / TRP, at least one DL BWP can be configured as the default BWP, and the default BWP should include the SS burst set within the UE's BW. This SS burst information can be set via system information (SI). In FIG. 8, there are two BWP setups in this example. Since there is an SS burst set (e.g., SSB1 within BWP#1), BWP#1 can be treated as the default BWP.

[0105] When BWP#2 comes from another cell (e.g., BWP#1 is associated with cell#1 and BWP#2 is associated with cell#2), the default BWP setup can use the following options for multiple TRP receptions. When the PDCCHs are jointly scheduled, for example, when there is a single PDCCH scheduled simultaneously for cell#1 and cell#2, BWP#1 and BWP#2 can use the same default BWP (e.g., the primary BWP). When the PDCCHs are individually scheduled, for example, when there are multiple PDCCHs scheduled individually from cell#1 and cell#2, each configured BWP uses its own default BWP associated with the cell.

[0106] According to one embodiment, the default BWPs for multiple TRP receptions are shown in FIGS. 9A and 9B. In FIG. 9A, BWP#1 and BWP#2 are jointly scheduled by BWP#1 CORESET, and BWP#1 is the default BWP. In FIG. 9B, BWP#1 and BWP#2 are individually scheduled by their respective BWP#1 CORESET and BWP#2 CORESET. In this case, the default BWP is set individually by each TRP.

[0107] <BWP operation using DRX> If there is no DL and UL traffic for the X slot or subframe, the gNB can define a timer, e.g., to return to the RRC idle or RRC inactive timer, which triggers the UE to return to the default BWP during the transfer from the RRC connected mode to the RRC idle mode or the inactive mode. Further, the gNB can also set a periodic time pattern, e.g., a DRX pattern, which directs the UE to retune from the default BWP to the UL or DL BWP during the transfer from the RRC idle or RRC inactive mode to the RRC connected mode. For example, in the RRC idle mode, a CORESET can be detected in the common search space (CSS) on the default BWP, or in the RRC connected mode, measurements can be performed and reported on a given BWP. The gNB can configure the UE in either of the following. That is, (i) a timer that triggers the UE to retune to the default DL BWP in the RRC connected mode when no DL allocation or UL grant for the X slot is received on the currently active DL BWP, or (ii) a time pattern, e.g., a periodic pattern, that triggers the UE to retune to the DL BWP.

[0108] When the UE changes from the RRC connected mode to the RRC idle mode or the inactive mode, the UE can return to the default BWP, where synchronization, mobility measurements, etc. can be performed via the SS burst set on the default BWP. If the UE is configured with a DRX timer, after waking up from the DRX sleep cycle, the UE can retune to the default BWP to perform beam recovery (BR), and can transmit a beam recovery request (BRR) via (i) the contention PRACH of the default BWP or the configured BWP, or (ii) the PUCCH in the default BWP or the configured BWP if available.

[0109] <Rate matching or puncturing for multiple BWP operations> According to yet another embodiment, the position of the BWP can be set by upper layer signaling such as RRC, MAC CE, or can be identified by the start offset Rp and bandwidth W dynamically set by DCI. The start offset Rp represents the number of units (such as PRBs) by which the BWP is away from a reference point (such as the reference PRB of the system). The bandwidth W is the number of units occupied by the BWP, where the units can be arranged within PRBs or RBGs. The UE can receive multiple BWPs simultaneously. As an example, two BWPs are used. As shown in FIG. 10, Rp1 and W1 are set for BWP1, and Rp2 and W2 are set for BWP2. There are the following three options for the locations of the two BWPs. That is, (i) BWP1 and BWP2 have the same start offset and different bandwidths, where Rp1 = Rp2 and W1 ≠ W2; (ii) BWP1 and BWP2 have different start offsets and the same bandwidth, where Rp1 ≠ Rp2 and W1 = W2; and (iii) BWP1 and BWP2 have different start offsets and different bandwidths, where Rp1 ≠ Rp2 and W1 ≠ W2.

[0110] When the UE is configured with two active BWPs and both BWPs are used for data reception, the two BWPs cannot overlap. When the UE is configured with one active BWP1 and one non-active BWP2, these two BWPs can be non-overlapping or partially overlapping. In this scenario, the active BWP1 is used for data reception, and the non-active BWP2 can be used to perform one or more of the following functions. That is, (i) CSI-RS for CSI measurement; (ii) CSI-RS / SS block for mobility measurement; and (iii) TRS for time / frequency tracking.

[0111] While the UE is receiving data on the active BWP1 at different times, it can monitor the same or different inactive BWPs. If the UE needs to monitor different BWPs at different times, it can use any of the following options to set the pattern of BWPs to be monitored.

[0112] (i) The BWP frequency hopping pattern can be set for the UE through higher layer signaling, such as RRC signaling and Mac CE. The UE is set using the location of the inactive BWPs with {Rp1…Rpn} and {W1…Wn,}, the frequency hopping pattern of the nBWPs, the monitoring time (e.g., each BWP needs to be monitored in m slots), and the information of the reference signal to be monitored.

[0113] (ii) The inactive BWP to be monitored can be dynamically set by DCI. The DCI carries a field indicating a parameter set including information of the inactive BWP such as the BWP location and the reference signal to be monitored, which is set by higher layer signaling. The UE determines the details of the setting by detecting the corresponding PDCCH through the CORESET of the BWP and monitors the inactive BWP.

[0114] When the UE is set with the active BWP1 and the inactive BWP2, some of the time and frequency resources of these two BWPs may overlap with each other. If the same resource element is scheduled for both BWPs for different purposes, signal collisions will occur and the performance will degrade. To solve this problem, depending on various use cases, any of the following methods can be used.

[0115] In the first method, active BWP1 performs rate matching. For example, there may be collisions on the resources used by BWP1 for PDSCH and on the resources used by BWP2 for transmitting reference signals such as CSI-RS and TRS. In this scenario, the gNB performs the rate match of PDSCH around the resource elements used by BWP2 as reference signal ports. The UE indicates that rate matching is required by the gNB. Using the reference signal configuration, the UE can determine which REs of BWP1 are muted for the reference signal ports and accordingly decode the data on PDSCH.

[0116] In the second method, active BWP1 is punctured. This option may be applicable to scenarios where the overlapping area between the two BWPs is small. If some REs of CSI-RS of BWP2 overlap with the PDSCH of BWP1, the PDSCH can be punctured in the overlapping Res used for the CSR-RS port to ensure the transmission of CSI-RS for BWP2 without causing an obvious performance degradation of the PDSCH for BWP1.

[0117] In the third method, inactive BWP2 is punctured. This option may be applicable to scenarios where BWP2 is performing measurements that require sample collection in multiple slots. For example, when the UE is performing CSI-based measurements for BWP2 within a time window and some CSI-RS are punctured, for example, not transmitted on those ports, the transmission on BWP1, such as the high priority of PDCCH transmission in BWP1, can be guaranteed without affecting the performance, while it will not significantly affect the measurement results.

[0118] According to the present application, CSI-RS is exemplarily used, and it is assumed that any of the methods described above can be used on BWP2 together with control or data transmission on BWP1. Since multiple options can be used when a collision occurs, the UE needs to indicate which method to use. This indication can be performed, for example, for periodic or semi-persistent settings, through upper layer settings such as RRC signaling and / or MAC CE. Alternatively, it can be dynamically indicated by DCI, where the DCI field refers to a parameter set including related parameters set by upper layer signaling.

[0119] <PRACH operation for BWP> According to another aspect of the present application, PRACH operations using BWP can be used in several UE modes, such as, for example, initial access, transition from RRC_INACTIVE to RRC_CONNECTED, re-establishment of RRC connection, DL arrival during RRC_CONNECTED requiring random access, handover, multi-link, and beam recovery.

[0120] In this application, the PRACH resource includes two main parts. The first part is the UL PRACH transmission resource (e.g., UL BWP and preamble). The second part is the DL RA response (RAR) resource (e.g., DL BWP). In the case of dynamic TDD flexible subframes, DL RAR and UL PRACH transmission are within the same BWP. The DL BWP for RAR reception and the UL BWP for PRACH transmission can be individually set and allocated within the BWPs supported by the UE. On the other hand, RAR and PRACH are set to individual BWPs for FDD. That is, there are two BWPs. One is for UL PRACH transmission, e.g., UL BWP, and the other is for DL RAR reception, e.g., DL BWP.

[0121] <Initial access or transition from RRC_INACTIVE to RRC_CONNECTED> In the setup of the initial RRC connection, to switch from the RRC_IDLE / RRC_INACTIVE state to the RRC_CONNECTED state, the UE can initiate a random access. If the NR CC broadcast to multiple SSBs (Synchronization Burst Set) is indicated as SSBi, in different SS raster, i = 1, …… S. As shown in FIGS. 11A and 11B, the several cryptographic SSBi is equal to the several cryptographic SSBj for i ≠ j. FIG. 11A shows an example where SSB1 and SSB2 share system information (SI). FIG. 11B shows an example where SI is independently owned by SSB1 and SSB2.

[0122] When the UE performs an initial access from the RRC_IDLE mode, the PRACH resources may be different. For example, if SIi = SIj for i ≠ j, as shown in FIG. 12A1, the PRACH resources can be set as shared PRACH allocation resources. FIG. 12A2 shows an example of a single allocated PRACH frequency resource.

[0123] Alternatively, FIG. 12B1 shows the PRACH resources set as multiple allocated resources. FIG. 12B2 shows an example of multiple allocated PRACH frequency resources when SIi = SIj for i ≠ j for PRACH transmission.

[0124] If SIi ≠ SIj for i ≠ j, the PRACH resources can be set as shared PRACH allocation resources, as shown in FIG. 13A. FIG. 13A shows an example of a single allocated PRACH frequency resource case 1. Alternatively, as shown in FIG. 13B, the PRACH resources can also be set as multiple allocated resources. FIG. 13B shows an example of a single allocated PRACH frequency resource case 2. FIG. 13C shows an example of multiple allocated PRACH frequency resources when SIi ≠ SIj for i ≠ j.

[0125] Here, we define the supported bandwidth of a narrowband UE, for example, referred to as BWUE. If a narrowband UE, for example, BWUE < BWCC, has a plurality of allocated PRACH resources for transmitting PRACH when SIi = SIj for i ≠ j, the UE can randomly select the allocated PRACH resources or select the PRACH resources based on the cell ID and RA-RNTI.

[0126] Figures 14A and 14B show two UEs performing initial access from the RRC_IDLE mode. For each UE, BWUE < BWCC and SI indicate a plurality of allocated PRACH resources. In this case, UE1 and UE2 have two PRACH resources for transmitting (UL) PRACH. In Figure 14A, when SIi = SIj for i ≠ j, the PRACH resources are associated with SI1 and SI2. In Figure 14B, when SIi ≠ SIj for i ≠ j, the PRACH resources are associated with SI1 and SI2.

[0127] In another embodiment, the gNB or cell / TRP can set at least one DL BWP as the default BWP, and this default BWP (s) should include the SS burst set within the UE's BW. The PRACH resources include the allocated frequency resources and the PRACH preamble configuration. The PRACH resources may be associated with the SSB.

[0128] For the default BWP, the UE's PRACH resources (including the allocated frequency resources and the PRACH preamble) can be indicated by the SI information. The PDSCH carrying SI can be indicated by the MIB. As shown in Figures 15A and 15B, the numerology SSBi is not equal to the numerology SSBj for i ≠ j. Figure 15A shows an example where the system information (SI) is shared by SSB1 and SSB2. Figure 15B shows an example where the SI is independently owned by SSB1 and SSB2.

[0129] When the UE performs initial access from the RRC_IDLE mode, the PRACH resource can adopt any of the following options. When SIi = SIj for i≠j, the PRACH resource can be set as a shared PRACH allocation resource as shown in Fig. 16A1. Fig. 16A2 shows an example of a single allocated PRACH frequency resource in the case of PRACH transmission when SIi = SIj for i≠j. Alternatively, the PRACH resource can be set as a plurality of allocated resources as shown in Fig. 16B1. Fig. 16B2 shows an example of a plurality of allocated PRACH frequency resources, where in the case of PRACH transmission, SIi = SIj for i≠j.

[0130] Furthermore, when SIi≠SIj for i≠j, as shown in Fig. 17A, the PRACH resource can be set as a shared PRACH allocation resource. Fig. 17A shows an example of Case 1 of a single allocated PRACH frequency resource when SIi≠SIj for i≠j. Alternatively, the PRACH resource can be set as a plurality of allocated resources as shown in Fig. 17B. Fig. 17B shows an example of Case 2 of a single allocated PRACH frequency resource, where SIi≠SIj for i≠j. Fig. 17C shows an example of a plurality of allocated PRACH frequency resources, where SIi≠SIj for i≠j. Here, we define a narrowband UE, for example, a supported BW denoted as BWUE. If a narrowband UE, for example, BWUE < BWCC, has a plurality of allocated PRACH resources for transmitting PRACH when SIi = SIj for i≠j, the UE can select the PRACH resource based on the cell ID and RA-RNTI, or the UE can randomly select the allocated PRACH resource.

[0131] Figure 18A shows a PRACH resource associated with SI1 and SI2, and SIi≠SIj for i≠j. Figure 18B shows the PRACH resources associated with SI1 and SI2 when SIi≠SIj for i≠j. In both Figure 18A and 18B, two UEs perform an initial access from the RRC_IDLE mode. For each UE, BWUE<BWCC and SI indicate a plurality of allocated PRACH resources. In this case, UE1 and UE2 have two PRACH resources for transmitting PRACH. The gNB or cell / TRP can set at least one DL BWP as the default BWP, and this default BWP can include an SS burst set within the UE's BW, as well as a PRACH resource and a PRACH preamble setting including the allocated frequency resources. The PRACH resource can be associated with the SSB.

[0132] Figure 19A shows an NR CC broadcast to the SSB, where the scrambling of SSB1 is the same as that of SSB2. Figure 19B shows an NR CC broadcast to the SSB where the scrambling of SSB1 is not equal to that of SSB2. The PRACH resources of the UE for the default BWP (including the allocated frequency resources and the PRACH preamble) can be derived from the PRACH resources indicated by the SI information. The PDSCH carrying SI is indicated by the MIB.

[0133] In the case of Case 1 and Case 2, it is assumed that the system information (SI) indicated by the master information block (MIB) of SSBi and SSBj can be shared for i≠j, for example, the resource SIi = SIj of the system information for i≠j is assumed according to this application. Alternatively, the SI may be independently allocated to different frequency resources for i≠j, for example, the system information SIi≠SIj for i≠j. The bandwidth of SIi for i = 1,..., S shall not exceed the minimum bandwidth that the system can support.

[0134] FIG. 20A shows SI(a) shared by SSB1 and SSB2. FIG. 20B shows SI independently owned by SSB1 and SSB2.

[0135] FIG. 21A1 shows an assigned single PRACH frequency resource, where in the case of PRACH transmission, for i≠j, SIi = SIj. There are many options for the PRACH resource for which the UE performs initial access from the RRC_IDLE mode. For example, if for i≠j, SIi = SIj, as shown in FIG. 21A2, the PRACH resource can be set as a shared PRACH allocation resource. FIG. 21B1 shows a plurality of assigned PRACH frequency resources, where in the case of PRACH transmission, for i≠j, SIi = SIj. Here, as shown in FIG. 21B2, the PRACH resource can be set as a plurality of assigned resources.

[0136] FIG. 22A shows Case 1 of a single assigned PRACH frequency resource where for i≠j, SIi≠SIj. If for i≠j, SIi≠SIj, as shown in FIG. 22A, the PRACH resource can be set as a shared PRACH allocation resource. FIG. 22B shows Case 2 of a single assigned PRACH frequency resource when for i≠j, SIi≠SIj. Alternatively, as shown in FIG. 22B, the PRACH resource can be set as a plurality of assigned resources. FIG. 22C shows a plurality of assigned PRACH frequency resources when for i≠j, SIi≠SIj.

[0137] According to this embodiment, the narrowband UE includes the supported BW shown as BWUE. If the narrowband UE (for example, BWUE < BWCC) has a plurality of assigned PRACH resources for transmitting PRACH, when for i≠j, SIi = SIj, the UE can select the PRACH resource based on the cell ID and RA-RNTI, or can randomly select one of the assigned PRACH resources.

[0138] In a further embodiment, FIGS. 23A and 23B illustrate an example where two UEs perform initial access from the RRC_IDLE mode. For each UE, BWUE < BWCC and SI indicate a plurality of allocated PRACH resources. In this case, UE1 and UE2 have two PRACH resources for transmitting the PRACH. FIG. 23A shows an example of PRACH resources associated with SI1 and S12 and where SIi = SIj for i ≠ j. FIG. 23B shows an example of PRACH resources associated with SI1 and S12, where here SIi ≠ SIj for i ≠ j.

[0139] The gNB or cell / TRP can set at least one DL BWP as the default BWP, and the default BWP should include the SS burst set within the UE's BW, as well as the PRACH resources including the allocated frequency resources and PRACH preamble settings. This PRACH resource can be associated with the SSB. The UE's PRACH resources (including the allocated frequency resources and PRACH preamble) for the default BWP can be obtained from the PRACH resources indicated by the SI information. The PDSCH carrying the SI is indicated by the MIB.

[0140] <RRC Connection Re-establishment Procedure> According to yet another aspect of the application, when a radio link failure (RLF) occurs, the UE needs to re-establish the RRC connection. In this scenario, the UE starts a random access. If the configured contention PRACH resources do not exist in the active BWP, the UE can retune its BW to the configured contention-based PRACH resources, for example, to the contention-based PRACH resources defined in the default BWP where it transmits a random access preamble and receives a random access response.

[0141] During the RRC re - establishment procedure, the gNB can configure a new BWP for the UE. When the RRC re - establishment procedure is completed, the UE can tune that BWP to the active BWP. If contention - based PRACH resources exist in the default BWP, the UE can transmit a PRACH using the PRACH resources associated with the SSB. If contention - based PRACH resources do not exist in the default BWP, the UE can transmit a PRACH using the PRACH resources associated with the CSI - RS.

[0142] Figure 24A shows the re - establishment of the RRC connection when the PRACH resources do not exist in the currently active BW. Here, the configured contention - based PRACH is allocated within the default BWP. The current active BWP does not overlap with the PRACH frequency resources. If the RRC connection needs to be re - established, the UE can tune the BW from the current active BWP to the default BWP or to the BWP that includes the PRACH resources. When the RRC re - establishment procedure is completed, if a new active BWP was configured during the RRC re - establishment procedure, the UE can re - tune the BWP to the new active BWP. Otherwise, the UE can re - tune the BWP to the active BWP before the RRC is re - established.

[0143] Figure 24B shows the re - establishment of the RRC connection, where the UE active BW is re - configured during the RRC re - establishment procedure.

[0144] A way to re - establish the RRC connection using BWP configuration is illustratively shown in Figure 25. In one embodiment, a method can be adopted where a UE in the RRC_CONNECTED state transmits uplink data to the gNB and it is necessary to discover that it is outside the uplink synchronization scenario. In another embodiment, this method can be adopted for the arrival of DL data at RRC_CONNECTED that requires a random access procedure, for example, when the UL synchronization state is "asynchronous".

[0145] In one embodiment, when the gNB needs to send downlink data in the RRC_CONNECTED state to the UE and discovers that the UE has gone out of uplink synchronization due to the expiration of the alignment timer, the gNB instructs the UE to initiate contention-free random access. The contention-free PRACH is dynamically triggered via DCI (PDCCH) and the PRACH resource of the BWP operation. If contention-free PRACH resources, such as UL PRACH transmission and DL RAR reception resources, are allocated to the active band, the DL RA response (RAR) and UL PRACH transmission are executed within the same active band, so there is no need to retune the active BWP. On the other hand, if the contention-free PRACH resource is not in the active band, the UE retunes from the active BWP to the BWP where it can receive the DL RAR and transmit the PRACH preamble.

[0146] When synchronization is complete, the UE can retune and return to the active BWP. The allocated contention-free PRACH resource can be indicated by CSI-RS or connected-mode SSB. The timing for transmitting the PRACH preamble can be set after l symbols along with the reception of DCI in a time slot.

[0147] Figure 26 shows an example of a method for DL data arrival in RRC_CONNECTED that requires random access using BWP configuration. Each step is indicated by an Arabic numeral. In particular, the UE determines in step 4 that the time alignment timer has expired. The UE receives DL data from the gNB in the buffer state. The UE retunes the BWP to the PRACH BWP as needed and, in step 7, sends a message containing the RACH preamble to the gNB. The UE receives the RAR timing adjustment (TA) in step 8. Next, the UE synchronizes its UL (step 9). After receiving and confirming the reconfiguration of the RRC connection in steps 10 and 11, the UE retunes the BWP to the active BWP.

[0148] <Handover> According to yet another aspect of the present application regarding handover, the UE starts a random access in the target cell. If a contention-based PRACH is used for handover and the configured contention PRACH resource does not exist in the active BWP, the UE can retune its BW to the defined contention PRACH resource. For example, the contention PRACH resource defined in the default BWP is used for the transmission of the random access preamble and the reception of the response.

[0149] The target gNB can configure new BWP(s) information via handover commands, e.g., the PHY / MAC configuration provided in the RRCConnectionReconfiguration message sent to the UE. When the handover procedure is completed, the UE can tune the BWP to the RRC-configured BWP in the target cell as the new active BWP. The BWP configuration of the target cell is in the radioResourceConfigDedicated list as shown in Table 6.

[0150] [Table 6]

[0151] A new "bandwidthPartInfo" subfield is added to the "physicalConfigDedicated" field. "bandwidthPartInfo" lists the BWP information of the target cell of the UE.

[0152] If the contention PRACH resource is in the default BWP(s), the UE can use the PRACH resource associated with the SSB of the target cell. If the contention PRACH resource is not in the default BWP(s), the UE may use the PRACH resource t associated with the SSB of the target cell.

[0153] When contention-free based PRACH is used for handover, the contention-free PRACH is dynamically triggered via DCI (PDCCH). For example, the PDCCH order and contention-free PRACH resources, such as BWP(s) operation, may be contention-free PRACH frequency resources within the active band. In this case, a PRACH preamble is transmitted, and the RA response (RAR) can be performed in the active band. Alternatively, contention-free PRACH resources can be allocated to contention-free PRACH resources. For example, when the BWP is not in the (current) active band, the UE re-tunes to the contention-free PRACH and receives the RAR in the configured PRACH BWP. When the UE completes the handover, the UE returns to the active BWP. The allocated contention-free PRACH resources can be indicated by CSI-RS or connected mode SSB. The timing for transmitting the PRACH can be the configured l symbols following the reception of DCI.

[0154] Figure 27 shows an example of the call flow of the UE handover procedure using BWP operation. In this procedure, random access according to the BWP configuration is required for contention-free based PRACH operation.

[0155] <Multi-link> According to a further aspect of the present application, it is assumed that one or more PDSCHs can be transmitted in one BWP. In one embodiment, the PDSCH can be split into two BWPs for transmission. For example, the UE is configured with three BWPs and two PDSCH transmissions. In this example, the UE is configured with three BWPs such as BWP#1, BWP#2, and BWP#3. PDSCH#1 may be transmitted in BWP#1 and BWP#3. PDSCH#2 may be transmitted in BWP#2. This can be achieved when the (primary) PDCCH schedules two PDSCHs simultaneously in the (primary) BWP. For example, set BWP#1 as the primary BWP for the simultaneous scheduling of the PDCCH. Alternatively, the two PDSCHs may be scheduled independently by two PDCCHs. Each PDCCH transmits only on the BWP having the configured CORESET. For example, PDCCH#1 may be transmitted on BWP#1, and PDCCH#2 may be transmitted in BWP#3.

[0156] If the primary PDCCH schedules two PDCSHs simultaneously and one of these links (or TRP) requires RRC reconfiguration or DL / UL asynchrony, random access can use the PRACH BWP associated with the default BWP. If the default BWP overlaps partially or entirely with one of the active BWPs, it is necessary to notify the UE of the rate matching information including the allocated PRACH BW.

[0157] If the primary PDCCH schedules two PDCSHs independently and if one of the links (or TRPs) requests RRC reconfiguration or DL / UL out-of-synchronization, the RA can use the PRACH BWP associated with each default BWP. If each default BWP partially or fully overlaps with one of the active BWPs, the rate matching information including the assigned PRACH BW needs to be notified to the UE. If multiple BWPs use only the primary default BWP, the UE can use the PRACH resources (e.g., PRACH on PRBs) in the primary default BWP.

[0158] In the exemplary embodiment shown in FIG. 28A, two PDCCHs are scheduled simultaneously and use the PRACH BW associated with the default BW1. In FIG. 28B, two PDCCHs are scheduled independently and use the PRACH BW associated with each default BWP, e.g., default BWP1 and default BWP2.

[0159] <Beam Recovery Request> According to yet another aspect of the present application, it has been found that when the UE's current beam triggers beam failure recovery, the UE needs to send a beam recovery request (BRR). For example, if the PUCCH cannot be used for BRR transmission, the UE starts the RA, returns to the (primary) default BWP(s) there, and uses the PRACH associated with the primary BWP to send the PRACH together with the BRR. A dedicated PRACH preamble can be used to identify the BRR. Then, the UE can set and start a BWP timer, and if the BWP timer expires and the UE fails to receive the RAR, the UE can stay in the (primary) default BWP(s) and set RRC_CONNECT to RRC_IDLE. If the beam recovers before the BWP timer expires, the UE performs a switch (re-tuning) to the active BWP(s).

[0160] Alternatively, the UE can use the RA resources configured via RRC. The RA resources include two main parts. One of these parts is for UL PRACH transmission. The other part is for DL RAR reception. The configured RA resources may be the same as or different from the current active BWP(s). The UE can use the PRACH associated with the primary BWP to transmit the PRACH together with the BRR. The dedicated PRACH preamble can be used to identify the BRR. The dedicated PRACH preamble can also be used for the setting and starting of the BWP timer. If the BWP timer expires before receiving the RAR, the UE stays in the configured BWP and sets RRC_CONNECT to RRC_IDLE. However, if the beam recovers before the BWP timer expires, the UE can switch (retune) to the active BWP as needed.

[0161] If the PUCCH is available for BRR transmission, the UE can transmit the BRR via the PUCCH from the active BWP and set and start the BWP timer. If the ACK is successfully received before the BWP timer expires, the beam recovers and the UE can resume data transmission and reception. If the BWP timer expires without successfully receiving the ACK for the BRR, the UE can retune from the configured BWP(s) to the (primary) default BWP(s) and set RRC_CONNECT to RRC_IDLE.

[0162] According to a further embodiment exemplarily shown in FIG. 29, an active BWP timer expires, and the timing at which the UE returns to the default BWP is described. The UE can use the configuration, resolution, and operation method of the BWP timer to switch an active DL / UL bandwidth part (BWP) to the default or another active DL / UL BWP. The mechanism for switching from the active BWP to the default BWP described herein can also be applied to scenarios such as switching from one active BWP to another active BWP.

[0163] The BWP inactivity timer can be set by one of the following exemplary methods and signaled to the UE. For example, the bwp-inactivityTimer can identify the number of consecutive slots during which the UE becomes active after successfully decoding the PDCCH, which indicates a new transmission or retransmission in UL or DL. For example, this timer is restarted / reset when a UL grant is received on the DL scheduling PDCCH. When this timer expires, the UE can switch to the default BWP.

[0164] The BWP inactivity timer is set by an RRC message for a serving cell, such as a primary cell (P cell) or a primary S cell (PS cell). The BWP inactivity timer setting can be carried under the bwp-config IE in an RRC message such as RRCConnectionReeconfiguartion, in conjunction with the MAC-MainConfig of the DRX cycle setting.

[0165] For unpaired spectra such as TDD, the non-activity DL and UL BWP timers can be jointly set, or one BWP non-activity timer can be shared for both DL and UL. For example, as shown in Figure 29, the BWP non-activity timer value can be set to 1 ms. In this case, when the BWP non-activity timer expires, the UE returns to the default BWP. On the other hand, for paired spectra such as FDD, the DL and UL BWP non-activity timers, e.g., the DL and UL non-activity timers, can be set individually.

[0166] The BWP non-activity timer value may depend on the BWP set with the same numerology or different numerologies, or the BW of the BWP. RRC signaling can set an individual BWP timer for each set BWP. However, it is not necessary to set a non-activity timer for the default BWP. The UE can refer to the BWP non-activity timer value from the BWP activation DCI. The activation DCI uses a bitmap or BWP index to indicate that the set BWP is valid or activated. The UE can set the BWP non-activity timer according to the activated BWP. The timer value of the BWP can be set via upper layer signaling such as RRC.

[0167] In the RRC message, since the BWP non-activity timer value can be defined from the perspective of time such as ms, it can be adapted to various numerologies or bandwidths. In FDD, the non-activity timer for DL or UL can be continuously counted down slot by slot. In TDD, the BWP non-activity timer decreases only when counting DL subframes and special subframes (SSF), where the SSF is used to facilitate the switch from DL to UL.

[0168] The UE can send a scheduling request (SR) when the UL BWP inactivity timer is on. However, when sending an SR, the UE must continuously monitor the PDCCH until the SR procedure is completed even if the DL BWP inactivity timer expires. Alternatively, when the UE sends an SR on the UL, for FDD, it is necessary to reset the UL, for TDD, it is necessary to reset the UL, or reset the self - contained sub - frame BWP inactivity timer, or pause or hold the BWP inactivity timer when receiving DL DCI for uplink grant. In this method, if the DL BWP inactivity timer is shorter than the corresponding sr - ProhibitTimer, the UE needs to continue monitoring the PDCCH until the sr - ProhibitTimer expires.

[0169] In FDD, when the UE obtains uplink grant DCI (corresponding to SR), it resets the UL BWP inactivity timer, e.g., ulbwp - inactivityTimer. In TDD, it resets the BWP inactivity timer bwp - inactivityTimer. If the UE switches from an active DL (first) BWP to another active DL or default (second) DL BWP and the first and second BWPs use different numerologies, PRACH resources need to be allocated to each (UL) BWP.

[0170] Figure 30A shows an exemplary embodiment of the timing of the HARQ RTT and re - transmission timer. The UE may have a BWP inactivity timer and one HARQ entity for each serving cell with, for example, multiple BWPs. While the BWP inactivity timer is running (e.g., counting down), if there is a re - transmission (NACK), the UE can respond in many ways. For example, the UE can set the BWP inactivity timer according to the re - transmission. Alternatively, the UE can hold the BWP inactivity timer for the re - transmission.

[0171] The UE can release the maintenance of the deactivation timer after the earliest of the following. That is, when the retransmission is ACKed (for example, when the decoding of the retransmitted data is successful), when the retransmission times out, or when the retransmission reaches the maximum number of retransmissions.

[0172] The retransmission timer value can be dynamically signaled via the DCI HARQ message. The UE can set the dynamic DL / UL HARQ timing parameters via the DCI. The dynamic DL / UL HARQ A / N timing parameters are K and N. DL / UL data reception in slot N, and the acknowledgement response in slot +K. Therefore, the retransmission timer value can be set as 2N, for example, as the minimum HARQ round-trip time (RTT). The retransmission timer value can set the HARQ RTT as the maximum value of the number of retransmissions.

[0173] While the BWP inactivity timer is in progress (e.g., counting down, etc.) and a BWP activation DCI is received, the retransmission is scheduled to the target BWP using the scheduling PDCCH carrying the activation DCI. For example, the UE switches to the active BWP for retransmission and also resets or deactivates the BWP inactivity timer.

[0174] When the BWP inactivity timer, e.g., bwp-inactivityTimer, expires and the HARQ buffer is not yet empty, the UE can choose not to flush the HARQ buffer while performing the switch to the default or another active BWP (for example, when the UE does not report being asynchronous or when there are no PUCCH resources allocated to the default (UL) BWP).

[0175] According to FIG. 30B, if the UE requests beam failure recovery (BFR), for example, if the UE transmits the BFR PRACH or PUCCH while both the beam recovery timer and the bwp-inactivityTimer for both DL and UL are running, the UE pauses the inactivity timer of the BWP for both DL and UL. Then it can monitor the DL PDCCH in the current BWP for the gNB's response. If the UE receives the gNB's beam recovery (BR) response before the beam failure recovery timer expires or before the UE reaches the maximum number of transmissions of the beam failure recovery request (BFRR), the UE can resume the BWP inactivity timer. Otherwise, the UE flushes the HARQ buffer, declares that the recovery of the beam failure has failed, and then switches back to the default BWP.

[0176] When detecting a beam failure in the current BWP, if CSI-RS or SSB is not configured to perform identification of new candidate beams for the UE, the UE starts the beam recovery timer and holds the data in the HARQ buffer. The UE can switch to the default BWP, stop the BWP inactivity timers for both DL and UL, perform identification of new candidate beams, and request BFRR. The UE monitors the BFRR response until the beam recovery timer expires or the UE reaches the maximum number of transmissions of BFRR. FIG. 30B shows an exemplary embodiment of the DL BWP inactivity timer with BFR. If the UE starts the beam recovery timer during the running time of the BWP inactivity timer, when the UE performs BFRR, the UE can pause the BWP inactivity timer or reset the BWP inactivity timer until it receives a BFR indication on the DL PDCCH in the current BWP.

[0177] While any of the DL-UL non-activity timers of the DL, UL, or TDD BWP for FDD, e.g., bwp-inactivityTimer, is in progress (ON) and the HARQ buffer is not yet empty, if the UE detects out-of-synchronization, the UE does not flush out the HARQ buffer. If the UE declares out-of-synchronization, e.g., if the radio link (RL) recovery timer expires, the UE can go to the default BWP and the UE can re-establish a new RL from the default BWP.

[0178] The BWP non-activity timer may interact with the connected-mode DRX timer. For example, if no DL assignment or UL grant is received for X slots on the current active DL BWP, the gNB can configure the UE using a BWP timer that triggers the UE to re-tune to the default DL BWP regardless of the RRC mode. The purpose of the BWP non-activity timer is to switch to the default BWP when there is inactivity on the active BWP.

[0179] Starting from the first slot of the onDuration period, the UE remains in the default BWP until it successfully decodes a PDCCH indicating an initial UL grant or DL transmission for this UE. If the initial BWP is indicated in the PDCCH, the UE switches to the initial BWP. When the UE returns to the DRX sleep mode, the UE returns to the default BWP. If the default BWP is not configured, it migrates to the DRX sleep mode on the initial BWP. This means that the UE wakes up during the onDuration period of this initial BWP. If the BWP inactivity timer expires during the execution of the DL / UL drx_RetransmissionTimer, the UE can maintain the bwp-inactivityTimer and does not switch to the default BWP. If the BWP inactivity timer expires and the default BWP has a different value from the currently active BWP during the execution of the rx_RetransmissionTimer or drx_inactivityTimer, the UE does not flush out the HARQ buffer or

[0180] During the execution of the drx_RetransmissionTimer, if the UE is in the default BWP, the UE waits for the drx_RetransmissionTimer to expire. If the BWP inactivity timer expires during the execution of the drx-InactivityTimer, the UE switches to the default BWP.

[0181] Figure 31A shows an example of the timing of the guard period for BWP switching for UL activation. Figure 31B shows an example of the timing for the guard period for BWP switching for DL activation. Figure 32 shows an example of the timing of the guard period for BWP switching when the UL BWP inactivity timer expires. Figure 33 shows an example of the timing for the guard period for BWP switching when the DL BWP inactivity timer expires.

[0182] For paired spectra such as FDD, the guard period is used for frequency retuning between two consecutive slots. While the UL BWP inactivity timer is running (e.g., counting down) and the UL BWP activation DCI is being received, the guard period is created by the DL scheduling DCI together with the activation DCI. For example, it can reserve the K2 guard OFDM or SC-FDMA symbols that are referenced from the received activation DCI or the PDCCH in the current DL BWP slot (the current DL BWP means the DL BWP where the UE stays). For example, as shown in Figure 32A, the K2 value can be set to three symbols. The UE transmits the PUSCH after the K2 symbols in the target UL BWP, where the target UL BWP means the UL BWP to which the UE is trying to switch.

[0183] While the DL BWP inactivity timer is running (e.g., counting down) and the DL BWP activation DCI is being received, the guard period is created by the DL scheduling DCI using the activation DCI. For example, it can reserve the K1 guard symbols that are referenced from the activation DCI received in the current DL BWP slot or the PDCCH (the current DL BWP means the DL BWP where the UE stays). For example, as shown in Figure 32B, the value of K1 can be set to three symbols. The UE receives the PDSCH after the K1 symbols in the target DL BWP, where the target DL BWP means the DL BWP to which the UE is about to switch.

[0184] FIG. 34 shows an example of the timing of the guard period for BWP switching for TDD. FIG. 35A shows an example of the timing of the guard period created by the UE for BWP switching using the same numerical calculations for the self - contained subframe and BWP activation. FIG. 35B shows an example of the timing of the guard period created by the UE for BWP switching using the same numerical magic for the self - contained subframe and the expiration of the BWP inactivity timer.

[0185] In the case of unpaired spectrum such as TDD, while the BWP inactivity timer is running (counting down, etc.) and the BWP activation DCI is being received, the guard period is created by the DL scheduling DCI. For example, as shown in FIG. 34, it can reserve the K1 guard symbol referenced from the current DL BWP TDD activation DCI or PDCCH. After the BWP inactivity timer expires and the UE switches from the current BWP back to the default BWP, the UE monitors the scheduling DCI in the default BWP PDCCH region if it is a TDD DL slot, or the UE can transmit SRS, PUCCH (long or short format), PRACH in the default BWP if it is a TDD UL slot.

[0186] In the case of a self - contained subframe, while the BWP inactivity timer is running (counting down, etc.) and the BWP activation DCI is being received, the transmission guard symbol K1 for in - slot switching can be implicitly indicated by the activation DCI or explicitly indicated by the scheduling DCI as shown in FIG. 35A. While the BWP inactivity timer expires and the UE switches from the current BWP to the default BWP, as shown in FIG. 35B, the guard period can be reserved by dropping the last K2UL symbol.

[0187] According to yet another embodiment, FIG. 36 shows an example of the timing of default BWP configuration using Carrier Aggregation (CA). The gNB can set one DL BWP as the default BWP for each component carrier (CC), and each default BWP can include an SS burst set within the UE's BW. In the case of a secondary CC, the gNB can set the default BWP. In FIG. 36, CC#1 and CC#2 use different numerologies, and each CC is set with an individual default BWP.

[0188] The SS burst (a set of SS blocks) can be configured within the measurement period (for connected mode only) for the default BWP of each CC. This SS burst information can be configured via system information (SI). If a CC is deactivated, the corresponding configured default BWP is deactivated. The DCI carrier indicator (CIF) and the BWP bitmap can be used to indicate which BWP is active on which CC. For example, if 4 bits of the CIF and 4 bits of the BWP are used for the indication of the BWP on which the CC is active, the binary 0010 0100 indicates the second CC and the third BWP is active.

[0189] For the primary serving cell, if no default BWP is configured, the initial (active) BWP can be used for the default BWP. The initial (active) BWP means the BWP on which the UE performs initial access. Each CC can be configured using a BWP inactivity timer, and the BWP inactivity depends on the numerology. In CA, if BWP#1 is for CC#1 as the default BWP, the UE can respond in several ways. If the PDCCH is jointly scheduled for CA, for example, if there is a single PDCCH jointly scheduled for CC#1 and CC#2, the UE can use BWP#1 as the default BWP (e.g., the primary default BWP) when there is no default BWP configuration for CC#2. If the numerologies of CC#1 and CC#2 are the same, the UE can use BWP#1 as the default for both CC#1 and CC#2; otherwise, CC#1 can use BWP#1 as the default BWP, and CC#2 can use BWP#2 as the default BWP. If the PDCCH is scheduled individually, for example, if there are multiple PDCCHs scheduled independently from CC#1 and CC#2, CC#1 can use BWP#1 as the default BWP, and CC#2 can use BWP#2 as the default BWP.

[0190] In yet another embodiment, FIG. 37 shows an example of the timing of the default BWP when the CCs are co-scheduled. Default BWP operation using CA is shown. CC#1 and CC#2 are co-scheduled, and CC#1 and CC#2 use the same numerology. BWP#1 CORESET and BWP#1 are the default BWPs for both CC#1 and #2.

[0191] In CA, for example, in Figure 36, if BWP#2 is set to CC#2 as the default BWP and BWP#1 is set to CC#1 as the default BWP, the UE can respond in many ways. For FDD, the DL and UL BWP timers can be set independently for each CC. In the case of TDD and self-contained subframes, the BWP timer is set individually for each CC.

[0192] If the PDCCH is scheduled jointly for CA or scheduled individually, for example, if a single PDCCH is scheduled simultaneously for CC#1 and CC#2, if the numerical values of CC#1 and CC#2 are the same, the UE can be set by the RRC using a single BWP timer value; otherwise, the BWP timer value can be set up independently for each CC. If the PDCCH is scheduled jointly during CA, a single DRX timer can be used for all CCs. If the PDCCH is scheduled individually during CA and their numerical values are different from the primary CC, individual DRX timers can be set independently for each CC.

[0193] According to yet another embodiment, FIG. 38 shows an example of the timing of a guard period for a UE to perform SRS gap transmission. FIG. 39 shows an example of the timing of a guard period for a UE to perform CSI-RS gap measurement. If the UE performs a measurement gap or transmits SRS outside the active BWP and an aperiodic SP or periodic SRS is scheduled to be transmitted using the long PUCCH or short PUCCH in the UL slot when the BWP inactivity timer is on (e.g., not expired) for paired spectrum (FDD), the UE can skip the aperiodic SP or periodic SRS transmission. If the PUSCH is scheduled to be transmitted using the aperiodic SP or periodic SRS, a guard period is generated by the UE and PUSCH transmission continues in the next slot. It generates the guard period using k1 OFDM or SC-FDMA symbols, followed by the scheduled SRS transmission, and the first k2 OFDM or SC-FDMA guard symbols are generated in the second PUSCH transmission slot. If the PUCCH is scheduled to be transmitted using the aperiodic SP or periodic SRS, a guard period is generated by the UE and PUSCH transmission continues in the next slot. It generates the guard period using k1 OFDM or SC-FDMA symbols, followed by the scheduled SRS transmission, and the first k2 OFDM or SC-FDMA guard symbols are generated in the second PUCCH transmission slot. If the PUSCH is scheduled to be transmitted using the aperiodic SP or periodic SRS, a guard period is generated by the UE and PUCCH transmission continues in the next slot. This generates the guard period using k1 OFDM or SC-FDMA symbols, followed by the scheduled SRS transmission, and then k2 OFDM or SC-FDMA guard symbols follow at the end of the current transmission slot. If the PDSCH is scheduled to be transmitted using the aperiodic SP or periodic CSI-RS, a guard period is generated by the UE and PDSCH transmission continues in the next slot.As shown in FIG. 39, it generates a guard period using k1 OFDM symbols, followed by the scheduled CSI-RS (outside the active BWP), and then k2 OFDM guard symbols at the end of the current slot.

[0194] For unpaired spectrum (TDD, self-contained subframes), if an aperiodic SP or periodic SRS is scheduled to be transmitted using the long PUCCH or short PUCCH within the UL slot, or the UL symbols in the self-contained subframe, the UE can skip the aperiodic SP or periodic SRS transmission. If the PUSCH is scheduled to be transmitted using an aperiodic SP or periodic SRS, a guard period is generated by the UE. It generates the guard period using k1 OFDM or SC-FDMA symbols, followed by the scheduled SRS transmission, and then k2 OFDM or SC-FDMA guard symbols at the end of the current transmission slot.

[0195] When the bwp-CSI mask restricts the CQI / PMI / PTI / RI and / or QCL reports to the duration of the (DL) bwp timer inactive cycle, the gNB can set the UE's CSI mask. If the CSI mask is set up by RRC, the reports of CQI / PMI / RI / PTI and / or QCL on the PUCCH should not be invalidated when the DL BWP inactivity timer has not expired. Otherwise, the UE should transmit CQI / PMI / RI / PTI reports for aperiodic CSI, SP-CSI, and periodic CSI reports.

[0196] When the bwp-SRS mask restricts SRS transmission to the duration of the inactive cycle of the UL BWP timer, the gNB can configure the UE's SRS mask. If the SRS mask is set up by RRC, the UE should not transmit SRS while the UL BWP inactivity timer has not expired. Otherwise, the UE should transmit SRS for aperiodic SRS, SP-SRS, and periodic SRS.

[0197] Figure 40 shows an exemplary embodiment of the timing of BWP activation DCI error handling. When the BWP activation DCI cannot be decoded successfully, for example, when the UE's BWP activation fails, the UE can respond in many ways. Whether there is DL data allocation or UL grant, if the UE receives the BWP activation DCI, it can stay in the current DL or UL BWP until the DL or UL BWP inactivity timer expires and can also return to the default BWP. Alternatively, if DL data is scheduled or there is a UL DCI grant, it resets the BWP inactivity timer. The UE can continue to monitor the DL DCI until the BWP inactivity timer expires without flushing out the HARQ buffer. If there is an uplink transmission such as scheduled SRS (aperiodic, semi-persistent, or periodic), the UE can continue to transmit the scheduled SRS. If there is any DL measurement such as scheduled CSI-RS (aperiodic, semi-persistent, or periodic) or SSB, the UE can continue to transmit the measurement of the scheduled CSI-RS or SSB.

[0198] As shown in Fig. 41A, for unauthorized operations using a BWP, the UE can use the GF resources that are semi-statically scheduled or dynamically activated by the PDCCH and set by the RRC for unauthorized transmissions. As shown in Fig. 41B, if the GF resources are not allocated to the UL BWP where the GF resources are activated, the UE cannot perform unauthorized transmissions. Regarding BWP switching, if it is explicitly indicated by the RRC configuration, semi-statically indicated by the MAC CE, or dynamically indicated by the PDCCH, the UE can set the BWP inactivity timer that is set by the RRC, semi-statically indicated by the MAC CE, or uses the BWP inactivity timer value. When the BWP inactivity timer expires, the UE can switch to another active BWP or its default BWP indicated by the RRC, MAC CE, or PDCCH. The UE can pause or reset the BWP inactivity timer for retransmission, and when the retransmission is confirmed (such as ACK), or when the retransmission times out, or when the maximum number of retransmissions is reached, (if the timer is paused) resume the timer. For unauthorized resources indicated or activated by L1 signaling, such as the PDCCH, the BWP activation / deactivation DCI can be combined with the unauthorized resource activation / deactivation DCI for the UE to switch between active BWP(s) or between the active BWP and the default BWP. If the currently active BWP is deactivated, the GF resources allocated to this BWP are also deactivated by the BWP inactivity timer or the MAC CE or the deactivation DCI.

[0199] <No PRB allocation for BWP> According to yet another aspect of the present application, a zero BWP can be defined as a zero resource assignment (RA) for DL- or UL-BWP. When a DL or UL zero BWP is configured or signaled, the operation of the UE depends on the following scenarios described below.

[0200] In a first embodiment of unpaired spectrum, there is a zero PRB configuration. The S cell BWP is deactivated. For unpaired spectrum, i.e., a TDD or self-contained subframe system, the DL and UL-BWPs are configured together. If the DL-BWP is configured with zero resources (plural) for one or a group of secondary cells (S cells), when it is P cell - S cell co-scheduling or is directly configured via an S cell, the UE is deactivated from the corresponding S cell BWP. The zero deactivated BWP does not support DL reception or UL transmission if there are retransmissions, i.e., if the HARQ buffer does not become empty, so the UE can switch from the DL- and UL-BWPs of the deactivated S cell to the following. That is, (i) the default BWP of the S cell, (ii) the active DL of the P cell and the UL-BWP with a non-zero resource assignment, (iii) the default DL and UL-BWPs of the P cell, or (iv) the P cell initial access DL and UL-BWPs. This is based on an indication from the gNB via RRC configuration or DCI signaling (e.g., the flag where the BWP DCI is zero). If there is no indication from the gNB, the default selection order can be as follows. That is, (i) the default BWP of the S cell if configured, (ii) if there is no default BWP of the S cell, the active DL of the P cell and the UL-BWP, (iii) if there is no active DL and UL-BWPs of the P cell, the default DL and UL-BWPs of the P cell, (iv) if the default DL and UL-BWPs of the P cell are not configured, the P cell initial access DL and UL-BWPs.

[0201] If the DL- and UL-BWP of the S cell are configured with a BWP timer that is activated, i.e., if the BWP-InactivityTimer has not expired, the UE can switch to the default BWP of the S cell, the active BWP of the P cell, or the default BWP of the P cell to stop the BWP timer. In this case, the zero BWP deactivates the active BWP of the S cell and invalidates the associated BWP timer.

[0202] A second embodiment of this aspect describes unpaired spectrum where the BWP of the P cell is deactivated. If the DL-BWP of the P cell is configured with zero resources other than the default DL-BWP of the P cell, the UE can deactivate the DL- and UL-BWP and switch to the default DL and UL-BWP. This is either the initial active DL and UL-BWP if it occurs during configuration or if no default BWP is configured in the P cell. The UE can monitor the scheduling CORESET (e.g., common search space or group common DCI or DCI in fallback DCI) on its default DL BWP or initial access DL BWP. Alternatively, it can transmit a PRACH on the default UL BWP or initial access UL BWP in the P cell. If the DL- and UL-BWP of the P cell are configured using an activated BWP timer, i.e., if the BWP-InactivityTimer and BWP-InactivityTimer have not expired, the UE can switch to the default PWB of the P cell or, if no default BWP is configured, switch to the initial active BWP to stop the BWP timer.

[0203] The third embodiment of this aspect describes a zero BWP that is inactive and derived from the serving cell. If a zero BWP is configured or signaled from the serving cell, the zero_BWP_timer can be configured for the UE's inactive duration. For example, the UE is in an "inactive mode" or "micro-sleep mode" and does not monitor or detect PDCCH in a common or UE-specific search space. When the zero BWP timer expires, the UE can return to the default or active BWP. This depends on the configuration via RRC or DCI signaling using zero BWP DCI to monitor a common or UE-specific search space. If no active BWP or default BWP is configured, the UE can use the initial access BWP after the zero_BWP_timer expires. If the BWP is activated during the monitoring DCI period, the UE can switch to the reactivated BWP. The monitoring DCI period can be configured via RRC signaling. To ensure synchronization between the UE wake-up timing and the network transmission timing, the TRS can be transmitted during the monitoring DCI period. The zero BWP processing of unpaired spectrum in the first, second, and third embodiments is shown in FIG. 42.

[0204] The fourth embodiment of this aspect describes paired spectra, where the DL / UL BWP of the S cell is deactivated. In the case of paired spectra (i.e., an FDD system with separately configured DL BWP and UL BWP), the DL-BWP(s) and UL-BWP(s) are set with zero resources for one or a group of secondary cells (S cells). When the BWP(s) are simultaneously scheduled via the P cell, or are directly configured via the S cell and no BWP timer is set, the BWP of the DL / UL S cell is deactivated. The UE can continue to monitor, if possible, the DCI of the BWP of the activated P cell. Since a zero DL / UL BWP cannot support DL / UL data reception, DL / UL (re)transmission can be switched to the DL / UL BWP of the P cell. If a BWP timer is set up for the DL / UL BWP and the BWP timer has not expired, this deactivation ignores the BWP timer.

[0205] The fifth embodiment of this aspect describes paired spectra where the DL / UL BWP of the P cell is deactivated without using the BWP of the S cell. In the case of paired spectra, if the DL / UL BWP is set with zero resources of the BWP of the P cell instead of the default BWP, the UE can be switched to the default DL / UL BWP of the P cell if it is set. If a BWP timer is set for the DL / UL BWP and the BWP timer has not expired, the BWP timer can be ignored by the deactivation. The UE monitors the DCI in the group common DCI or the common search space, or falls back the DCI to its DL default BWP if it is set. Alternatively, it can monitor the PRACH on its UL default BWP if it is set, or on its UL initial access BWP (if set) if no default is set for the P cell.

[0206] <DCI Monitoring during Zero BWP Period> According to a further aspect of the present application, when the UE is configured with a zero BWP, it can operate in one of the following ways for monitoring. That is

[0207] (i) No monitoring during the zero BWP setup period

[0208] (ii) The UE stops monitoring the PHY channel until the timer for the zero BWP configuration expires. Thereby, the UE can save power over the duration of the zero BWP timer.

[0209] (iii) When the zero BWP timer expires, the UE returns to the default or active BWP according to the configuration. The configuration for returning to the default or active BWP can be performed via RRC in a UE-specific way or a cell-specific way.

[0210] In one embodiment, monitoring is restricted during the zero BWP setup period. When configured for the zero BWP, the UE stops monitoring the data channel and certain control channels. However, the UE can continue to monitor the active BWP (the latest BWP being monitored and the latest BWP receiving the configuration of that BWP) or the default BWP for certain control signals, e.g., a configured CORESET (where it receives group-common DCI or DCI of the common search space). Thus, in the zero BWP, the UE can continue to receive certain control information such as SFI, control information related to SI-RNTI, but does not receive DL and UL grants. The purpose is to keep the monitoring period for the monitored control signaling low enough so that the UE can save power in this mode. This state can continue until the timer for the zero BWP configuration expires.

[0211] Alternatively, even when the zero BWP timer is still running, the UE can receive BWP reconfiguration via monitored DCI such as group common PDCCH, and the UE can switch according to the reconfiguration. When the zero BWP timer expires, the UE returns to the default or active BWP according to the setting. The setting to return to the default or active BWP can be performed via RRC in a UE-specific or cell-specific manner.

[0212] <DCI Format for Zero BWP Configuration> According to yet another aspect, the DCI for supporting zero BWP depends on the RRC configuration. If the bandwidth path indicator field is set in DCI format 1_1, the bandwidth path indicator field value indicates the active DL BWP from the DL BWP set configured for DL reception. If the bandwidth path indicator field is configured in DCI format 0_1, the value of the bandwidth path indicator field indicates the active UL BWP from the UL BWP set configured for UL transmission. Table 7 below shows the DCI formats for both DL and UL grants for supporting zero BWP configuration.

[0213]

Table 7

[0214] Table 8 below shows another DCI format for both DL grant and UL grant for supporting zero BWP configuration.

[0215]

Table 8

[0216] According to the present application, any or all of the systems, methods, and processes described herein can be embodied in the form of computer-executable instructions stored on a computer-readable storage medium, such as program code, which, when executed by a machine such as a computer, server, M2M terminal device, M2M gateway device, transit device, etc., execute and / or implement the systems, methods, and processes described herein. Specifically, any of the above steps, operations, or functions can be implemented in the form of such computer-executable instructions. The computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information, but such computer-readable storage medium does not include signals. The computer-readable storage medium includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD ROM, digital versatile disk (DVD) or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices, or other physical media that can be used to store the information of interest and can be accessed by a computer.

[0217] The systems and methods have been described with respect to what are presently considered to be particular embodiments, but the present application need not be limited to these disclosed embodiments. It is intended to cover various modifications and similar configurations that are within the spirit and scope of the claims, and the scope should be given the broadest interpretation so as to encompass all such modifications and similar structures. The present disclosure includes any and all aspects of the claims.

Claims

1. A non - transitory memory storing commands, and a processor operably coupled to the non - transitory memory, wherein the processor is configured to: transmit, via an active downlink bandwidth part (DL BWP) of the wireless transmit - receive unit (WTRU), one or more reference signals transmitted for at least one of beam measurement or radio link impairment measurement by the WTRU, to the WTRU via the active DL BWP; perform, by the WTRU in a default uplink bandwidth part (UL BWP), a random access channel (RACH) procedure using the default UL BWP during at least one of beam impairment or radio link impairment associated with the active DL BWP, wherein the RACH procedure comprises: receiving a random access (RA) preamble from the WTRU using RACH resources configured in the default UL BWP; transmitting an RA response to the WTRU; and switching the WTRU from the default UL BWP to an active UL BWP. The network node is capable of executing a command to perform the above operations.

2. The processor further executes a command to transmit a request to start RA to the WTRU based on the expiration of an alignment timer, according to the network node of Claim 1.

3. The processor executes a command to switch from the default UL BWP to an active UL BWP after the expiration of a non - activity timer, according to the network node of Claim 1.

4. The RA preamble occurs 1 symbol after the transmission of downlink control information (DCI), according to the network node of Claim 1.

5. The RA preamble is associated with a secondary synchronization broadcast (SSB), according to the network node of Claim 1.

6. The RACH procedure is initiated from the perspective of radio link impairment in an active downlink bandwidth part (DL BWP) with the WTRU, according to the network node of Claim 1. ​ Transmit one or more reference signals transmitted via the active downlink bandwidth part (DL BWP) of the wireless transmit / receive unit (WTRU) for at least one of beam measurement or radio link impairment measurement by the WTRU to the WTRU via the active DL BWP, perform a random access channel (RACH) procedure using the default uplink bandwidth part (UL BWP) by the WTRU during at least one of beam impairment or radio link impairment associated with the active DL BWP, the RACH procedure comprising: receive a random access (RA) preamble from the WTRU using RACH resources configured in the default UL BWP, transmit an RA response to the WTRU, including that, switch the WTRU from the default UL BWP to an active UL BWP, A method performed by a network node, including that.

8. The method according to claim 7, further comprising transmitting a request to the WTRU to initiate RA based on expiration of an alignment timer.

9. The method according to claim 7, switching from the default UL BWP to an active UL BWP after expiration of an inactivity timer.

10. The method according to claim 7, wherein the RA preamble occurs 1 symbol after transmission of downlink control information (DCI).

11. The method according to claim 7, wherein the RA preamble is associated with a secondary synchronization broadcast (SSB).

12. The method according to claim 7, wherein the RACH procedure is initiated from the perspective of radio link impairment in the active downlink bandwidth part (DL BWP) with the WTRU.

Images