Method and apparatus for downlink frequency hopping communication for reduced capability user equipment

Abstract

Reduced-capability user equipment (UE) uses frequency hopping to improve downlink (DL) coverage. Specifically, the UE can receive a Physical Downlink Shared Channel (PDSCH) using frequency hopping between multiple narrowbands in the wideband portion. The bandwidth of the narrowbands is no greater than the UE's maximum wireless communication bandwidth.

Description

Technical Field

[0001]

[0013] Generally speaking, the technology described below relates to wireless communication systems, and more particularly, the technology described below relates to downlink communication using frequency hopping in wireless communication systems. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. The new telecommunication standard is 5G New Radio (NR). 5G NR is part of the mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (for example, together with the Internet of Things (IoT)) and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvement of 5G NR technology. Such improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] In order to provide a basic understanding of one or more aspects of the present disclosure, a brief summary of such aspects is provided below. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a preface to a more detailed description provided later.

[0005] One aspect of the present disclosure provides an apparatus for wireless communication. The apparatus includes: a processor; a transceiver communicatively coupled to the processor; and a memory communicatively coupled to the processor. The processor is configured to: receive frequency hopping (FH) control information for a physical downlink shared channel (PDSCH) via the transceiver. The processor is also configured to: receive the PDSCH using frequency hopping between multiple narrowbands (NBs) via the transceiver based on the FH control information. The bandwidth of each of the multiple NBs is not greater than the maximum wireless communication bandwidth of the apparatus.

[0006] Another aspect of the present disclosure provides an apparatus for wireless communication. The apparatus includes: a processor; a transceiver communicatively coupled to the processor; and a memory communicatively coupled to the processor. The processor is configured to: send frequency hopping (FH) control information for a physical downlink shared channel (PDSCH) to a user equipment (UE) via the transceiver. The processor is also configured to: send the PDSCH using frequency hopping between multiple narrowbands (NBs) to the UE via the transceiver based on the FH control information. The bandwidth of each of the multiple NBs is not greater than the maximum wireless communication bandwidth of the UE.

[0007] Another aspect of the present disclosure provides a method for wireless communication at a user equipment (UE). The UE receives frequency hopping (FH) control information for a physical downlink shared channel (PDSCH). The UE also receives the PDSCH using frequency hopping between multiple narrowbands (NBs) based on the FH control information. The bandwidth of each NB in ​​the multiple NBs is not greater than the maximum wireless communication bandwidth of the UE.

[0008] Another aspect of the present disclosure provides a method for wireless communication at a scheduling entity. The scheduling entity sends frequency hopping (FH) control information for a physical downlink shared channel (PDSCH) to a user equipment (UE). The scheduling entity also sends the PDSCH using frequency hopping between multiple narrowbands (NBs) to the UE based on the FH control information. The bandwidth of each of the multiple NBs is not greater than the maximum wireless communication bandwidth of the UE.

[0009] After reading the specific embodiments below, these and other aspects of the present invention will become more fully understood. After reading the following description of the specific, exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features and embodiments will become apparent to those skilled in the art. Although features may be discussed below with respect to certain embodiments and the accompanying drawings, all embodiments may include one or more features in the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more features in such features may also be used according to the various embodiments discussed herein. In a similar manner, although exemplary embodiments may be discussed below as equipment, system or method embodiments, it should be understood that such exemplary embodiments may be implemented in various equipment, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a schematic illustration of a wireless communication system in accordance with some aspects of the present disclosure.

[0011] Figure 2 is a conceptual illustration of an example of a wireless access network in accordance with some aspects of the present disclosure.

[0012] Figure 3 is a schematic illustration of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects of the present disclosure.

[0013] Figure 4 is a diagram illustrating a first example of using frequency hopping PDSCH in downlink communications according to some aspects of the present disclosure.

[0014] Figure 5 is a diagram illustrating a second example of using frequency hopping PDSCH in downlink communications according to some aspects of the present disclosure.

[0015] Figure 6 is a diagram illustrating an example signal flow for configuring a PDSCH using frequency hopping according to some aspects of the present disclosure.

[0016] Figure 7 is a diagram illustrating an exemplary PDSCH transmission using narrowband frequency hopping.

[0017] Figure 8 is a diagram showing exemplary narrowband and subband alignment for PDSCH transmission using frequency hopping.

[0018] Fig. 9 is a flow chart illustrating an example method for handling overlap between broadcast PDSCH and narrowband PDSCH according to some aspects of the present disclosure.

[0019] Fig.10 is a flow chart illustrating an example process for transmitting a PDSCH using frequency hopping according to some aspects of the present disclosure.

[0020] Fig.11 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity according to some aspects of the present disclosure.

[0021] Fig.12 is a flow chart illustrating an example process for receiving a PDSCH using frequency hopping according to some aspects of the present disclosure.

[0022] Fig.13 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity according to some aspects of the present disclosure.

[0023] Fig.14 is a diagram showing an example of NB and subband alignment. DETAILED DESCRIPTION

[0024] The specific embodiments described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations, and are not intended to represent the only configuration in which the concepts described herein may be practiced. In order to provide a comprehensive understanding of each concept, the specific embodiments include specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0025] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses can be generated via integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicable scopes for the described innovations. Implementations may have a range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some actual settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for the implementations and practices of the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.) It is expected that the innovations described herein can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations.

[0026] 5G New Radio (NR) networks can provide services to various devices with different capabilities, such as enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), etc. In some applications and use cases, peak capacity is not required. Therefore, 5G NR networks should be scalable and deployable in a more efficient and cost-effective manner to support devices with different capabilities. For example, a user equipment (UE) with reduced capability may have limited bandwidth support and lower peak throughput, latency, and reliability requirements. Some examples of UEs with reduced capabilities are wearable devices, industrial wireless sensor networks, and surveillance cameras.

[0027] Various aspects of the present disclosure provide various apparatuses, methods, and systems for using frequency hopping in downlink communications in a 5G NR network. In some examples, a 5G NR device can use a frequency hopping method when transmitting a physical downlink shared channel (PDSCH) to improve diversity gain and restore downlink coverage for devices with reduced capabilities compared to advanced devices (e.g., smartphones).

[0028] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100, by way of example and not limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be able to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0029] The RAN 104 may implement any one or more suitable wireless communication technologies to provide wireless access to the UE 106. For example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (often referred to as 5G). For another example, the RAN 104 may operate in accordance with a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards (often referred to as LTE). 3GPP refers to this hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0030] As shown, the RAN 104 includes a plurality of base stations 108. Broadly speaking, a base station is a network element in a wireless access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a base station as a base transceiver station (BTS), a wireless base station, a wireless transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an evolved Node B (eNB), a gNodeB (gNB), or some other appropriate terminology.

[0031] The wireless access network 104 is also shown to support wireless communications for multiple mobile devices. In the 3GPP standard, a mobile device may be referred to as a user equipment (UE) 106, but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other appropriate term. A UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0032] In this document, a "mobile" device does not necessarily need to have the ability to move, and it can be stationary. The term mobile device or mobile device refers broadly to a wide variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement are changed to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet devices, personal digital assistants (PDAs), and a variety of embedded systems, for example, corresponding to the "Internet of Things" (IoT). In addition, a mobile device may be a car or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio unit, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor helicopter, a quadcopter, a remote control device, a consumer device such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, and the like, and / or a wearable device. In addition, the mobile device may be a digital home or smart home device, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, and the like. In addition, the mobile device may be a smart energy device, security equipment, solar panels or solar arrays, municipal infrastructure equipment that controls power (e.g., smart grids), lighting, water, and the like; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weapons, and the like. In addition, the mobile device may provide connected medicine or telemedicine support (e.g., telehealth care). Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or priority access relative to other types of information, for example, in terms of priority access for the transmission of critical service data, and / or in terms of the associated QoS for the transmission of critical service data.

[0033] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 108). Another way to describe the scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).

[0034] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and apparatuses within its service area or cell. In the present disclosure, as further discussed below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, UE 106 (which may be a scheduled entity) may use resources allocated by scheduling entity 108.

[0035] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs).

[0036] like Figure 1 As shown, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic (including downlink traffic 112, and in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108) in the wireless communication network. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network (e.g., the scheduling entity 108). In some examples, the scheduled entity 106 can use frequency hopping to send the uplink traffic 116. In some examples, the scheduling entity can use frequency hopping to send the downlink traffic 112.

[0037] Typically, base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of a wireless communication system. Backhaul 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or a backhaul interface using any suitable transport network.

[0038] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0039] Figure 2 is a conceptual illustration of an example of a radio access network (RAN) 200 according to some aspects. In some examples, the RAN 200 can be similar to the RAN 200 described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular regions (cells) that a user equipment (UE) may uniquely identify based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cells 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors in a cell are served by the same base station. A wireless link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0040] exist Figure 2In the example shown, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown as being used to control a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH via a feeder cable. In the example shown, cells 202, 204, and 126 may be referred to as macro cells, because base stations 210, 212, and 214 support cells with larger sizes. In addition, a base station 218 is shown in a small cell 208 (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home evolved node B, etc.), where the small cell 208 may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell, because base station 218 supports a cell with a relatively small size. Cell size changes may be made according to system design and component constraints.

[0041] It is to be understood that the wireless access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The base station / scheduling entity 108 shown in FIG.

[0042] Figure 2 Also included is a quadcopter or drone 220 that can be configured to act as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile base station (e.g., quadcopter 220).

[0043] In the RAN 200, a cell may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide all UEs in the corresponding cell with a route to the core network 102 (see Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 by way of RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the mobile stations described above and in Figure 1The UE / scheduled entity 106 shown in FIG. 1 is the same as the UE / scheduled entity 106 shown in FIG. 1 . The UE may use frequency hopping to communicate with a base station or cell.

[0044] In some examples, a mobile network node (eg, quadcopter 220 ) may be configured to function as a UE. For example, quadcopter 220 may operate in cell 202 by communicating with base station 210 .

[0045] In another aspect of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UE 226 and UE 228) can use peer-to-peer (P2P) or sidelink signals 227 to communicate with each other without relaying the communication through a base station (e.g., base station 212). In another example, UE 238 is shown as communicating with UEs 240 and 242. Here, UE 238 can be used as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can be used as scheduled entities or non-primary (e.g., auxiliary) sidelink devices. In another example, UE can be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P) or vehicle-to-vehicle (V2V) network and / or a mesh network. In the mesh network example, UEs 240 and 242 can optionally communicate directly with each other in addition to communicating with the scheduling entity 238. Thus, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate using the scheduled resources.

[0046] In various implementations, the air interface in the wireless access network 200 can utilize a licensed spectrum, an unlicensed spectrum, or a shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-approved license. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, in general, any operator or device can obtain access. Shared spectrum can fall between licensed spectrum and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of a licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0047] The air interface in the wireless access network 200 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link, in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. In a wireless link, a full-duplex channel usually relies on physical isolation of the transmitter and the receiver and appropriate interference elimination techniques. Full-duplex simulation for a wireless link is often achieved by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly (e.g., several times per time slot).

[0048] The air interface in the wireless access network 200 may also utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also referred to as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other appropriate multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0049] Reference will be made to Figure 3 Various aspects of the present disclosure are described using the OFDM waveform schematically shown in FIG. It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to DFT-s-OFDMA waveforms in substantially the same manner as described below herein. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to DFT-s-OFDMA waveforms.

[0050] In this disclosure, a frame refers to a duration of 10 ms used for wireless transmission, where each frame consists of 10 subframes of 1 ms each. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. Now referring to Figure 3 , shows an expanded view of an exemplary DL subframe 302, which displays an OFDM resource grid 304. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction, in units of OFDM symbols; and frequency is in the vertical direction, in units of subcarriers or tones.

[0051] Resource grid 304 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a MIMO implementation with multiple available antenna ports, corresponding multiple resource grids 304 can be available for communication. Resource grid 304 is divided into multiple resource elements (RE) 306. RE (which is 1 carrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RF can represent one or more bits of information. In some examples, a block of REs can be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any appropriate number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, regardless of the number scheme used. In some examples, depending on the number scheme, an RB can include any appropriate number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to a single direction of communication (for a given device, a sending or receiving direction).

[0052] The UE typically utilizes only a subset of the resource grid 304. An RB may be the smallest unit of resources that may be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The UE may use a first set of RBs for downlink communications and a second set of RBs for uplink communications.

[0053] In this diagram, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this diagram, while RB 308 is shown as occupying less than the entire duration of subframe 302, this is only one possible example.

[0054] Each subframe 302 (eg, a 1 ms subframe) may be composed of one or more adjacent time slots. Figure 3 In the example shown in , a subframe 302 includes four time slots 310 as an illustrative example. In some examples, the time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples may include mini-slots with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). In some cases, these mini-slots may be sent occupying resources scheduled for ongoing time slot transmissions for the same or different UEs.

[0055] An expanded view of one of the time slots 310 shows that the time slot 310 includes a control region 312 and a data region 314. In general, the control region 312 may carry a control channel (e.g., a PDCCH), and the data region 314 may carry a data channel (e.g., a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH)). In various examples, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The simple structure shown in is merely exemplary in nature, and different slot structures may be utilized, and different slot structures may include one or more regions in each of the control region and the data region.

[0056] Despite Figure 3 Although not shown in the figure, each RE 306 within the RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide a receiving device to perform channel estimation of the corresponding channel, which can achieve coherent demodulation / detection of the control and / or data channels within the RB 308.

[0057] In a DL transmission, a transmitting device (e.g., a scheduling entity 108) may allocate one or more REs 306 (e.g., within a control region 312) to one or more scheduled entities 106 to carry DL control information 114, including one or more DL control channels (such as a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc.) that typically carry information originating from a higher layer. In addition, DL REs may be allocated to carry DL physical signals that typically do not carry information originating from a higher layer. These DL physical signals may include: a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a demodulation reference signal (DM-RS); a phase tracking reference signal (PT-RS); a channel state information reference signal (CSI-RS); etc. The PDCCH may carry downlink control information (DCI) for one or more UEs in a cell. This may include, but is not limited to, power control commands, scheduling information, grants, and / or assignments of REs for DL ​​and UL transmissions. In some examples, the PDCCH may carry frequency hopping control information for the PDSCH.

[0058] In an UL transmission, a transmitting device (e.g., a scheduled entity 106) may utilize one or more REs 306 to carry UL control information 118 (UCI). The UCI may originate from higher layers via one or more UL control channels (such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc.) to the scheduling entity 108. Further, the UL REs may carry UL physical signals that typically do not carry information originating from higher layers, such as a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a sounding reference signal (SRS), etc. In some examples, the control information 118 may include a scheduling request (SR), i.e., a request for the scheduling entity 108 to schedule an uplink transmission. Here, in response to the SR sent on the control channel 118, the scheduling entity 108 may send downlink control information 114 that may schedule resources for uplink packet transmission.

[0059] The UL control information may also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgement (ACK) or a negative acknowledgement (NACK), channel state information (CSI), or any other suitable UL control information. HARQ is a technology well known to those skilled in the art, in which the accuracy of the integrity of the packet transmission can be checked on the receiving side, for example, using any suitable integrity check mechanism such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may implement append merging, incremental redundancy, etc.

[0060] In addition to control information, one or more REs 306 (e.g., within the data region 414) may also be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels (such as, for DL ​​transmission, the physical downlink shared channel (PDSCH); or for UL transmission, the physical uplink shared channel (PUSCH)).

[0061] Described above and in Figure 1-3 The channels or carriers shown in are not necessarily all of the channels or carriers that may be used between the scheduling entity 108 and the scheduled entity 106, and one of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be used in addition to the channels or carriers shown.

[0062] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which may correspond to the number of bits of information, may be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs.

[0063] In an exemplary 5G NR network, UL communications (e.g., PUSCH and PUCCH) may frequency hop. Two exemplary frequency hopping modes are intra-slot hopping and inter-slot hopping. In intra-slot hopping, UL communications may hop within the slot of a scheduled PUSCH / PUCCH symbol. In inter-slot hopping, UL communications may hop for each slot of a PUSCH / PUCCH with slot aggregation. In the PUSCH inter-slot hopping example, based on the absolute slot index, the starting RB may be offset by multiple RBs in an odd-numbered slot, where the offset is indicated in the downlink control information (DCI). DCI is a special set of control information for scheduling PDSCH or PUSCH. In the PUCCH inter-slot hopping example, a scheduling entity (e.g., a base station) may use radio resource control (RRC) signaling to configure two starting PRBs, one for odd-numbered slots and the other for even-numbered slots. In some aspects of the present disclosure, frequency hopping may be applied to the PDSCH, as described in more detail below.

[0064] In some aspects of the present disclosure, a 5G NR UE may have reduced capabilities compared to an advanced device or a full capability device (e.g., a smartphone). An NR light UE is an example of a device with reduced capabilities. For example, an NR light UE may have a narrower maximum supported bandwidth than the full bandwidth of a scheduled frequency band (e.g., 50 MHz for 15 kHz and 100 MHz for 30 / 60 kHz for Band N78). An exemplary NR light UE may support only 10 MHz or 20 MHz bandwidth in a scheduled frequency band or bandwidth part (BWP). A BWP is an available time-frequency resource (e.g., Figure 3 304 in the OFDM resource grid 304). The UE may be configured with one or more BWPs in the uplink and one or more BWPs in the downlink. Typically, one BWP in the UL and one BWP in the DL are active at a given time. BWP configuration parameters include digital scheme, frequency location, bandwidth size, and control resource set (CORESET). NR light UEs may have fewer receive (Rx) antennas than advanced UEs (e.g., smart phones). Therefore, NR light UEs may suffer from potential coverage reduction due to reduced bandwidth support and / or fewer antennas for diversity reception. In some aspects of the present disclosure, NR light UEs may use frequency hopping to improve DL coverage. Specifically, the UE may use DL frequency hopping for PDSCH to improve DL diversity gain.

[0065] Figure 4 402. The present disclosure provides an example of a first example of using a frequency-hopped PDSCH in DL communications in accordance with some aspects of the present disclosure. In addition to the active BWP 404 for NR light UEs, a scheduling entity (e.g., a gNB or a base station) may also configure one or more companion BWPs (e.g., companion BWP 402). The companion BWP and the active BWP may be referred to as narrow BWPs having a bandwidth narrower than the maximum communication bandwidth supported by the NR light UE or reduced capability UE. Figure 4 In the example shown in , the PDSCH (indicated by the number 1) hops between the active BWP 404 and the companion BWP 402 to improve the diversity gain. In some examples, the scheduling entity can explicitly configure the BWP, for example using radio resource control (RRC) and / or DCI. In some examples, the UE can implicitly derive the BWP configuration based on some predetermined rules and / or with the help of some RRC configuration previously received from the scheduling entity. In one example, an information element (e.g., "locationAndBandwidth") can be optionally configured to indicate a companion BWP, which can have the same subcarrier spacing as the active BWP, but at a different frequency domain position.

[0066] Figure 5 5 is a diagram illustrating a second example of using frequency hopping PDSCH in DL communications according to some aspects of the present disclosure. A scheduling entity (e.g., a gNB or a base station) may configure one or more narrowband (NB) in an active wide BWP 510 (e.g., in Figure 5 502, NB 504, NB 506, and NB 508 are shown in FIG. 1 ). Each NB has a bandwidth narrower than the maximum bandwidth supported by an NR light UE or a UE with reduced capability. The active wide BWP has a bandwidth greater than the maximum bandwidth supported by an NR light UE or the like. During transmission, the PDSCH may hop between NBs. For example, the first PDSCH (supported by Figure 5 1) hops between NB 502 and NB 506. Similarly, a second PDSCH (indicated by number #2) hops between NB 504 and NB 508. In some examples, the scheduling entity may explicitly configure the NB, for example, using RRC and / or DCI. In some examples, the UE may implicitly derive the narrowband configuration based on some predetermined rules and / or with the aid of some RRC configuration previously received from the scheduling entity. Each NB may be defined as a set of contiguous subbands or resource block groups (RBGs) having a total frequency span not greater than the maximum bandwidth supported by the UE. In 5G NR, RBs may be defined only for the frequency domain. Each RBG is a set of contiguous resource blocks (RBs) having a configurable size depending on the total number of PRBs in the bandwidth part. Similarly, a subband is defined as a set of contiguous PRBs having a configurable size depending on the total number of PRBs in the bandwidth part. The configuration of the NB may be common to all UEs sharing the same wide BWP having a bandwidth greater than the maximum bandwidth supported by the UE. In this example, BWP 510 includes four non-overlapping NBs (e.g., NBs 502, 504, 506, and 508), and each NB has a fixed size in the number of RBGs or subbands. In one example, depending on the size of the BWP, a subband may include 4, 8, 16, or 32 PRBs. The NBs may be functionally similar to those described with respect to Figure 4 In some aspects, a network may use a wide BWP to support coexistence of advanced UEs and reduced capability UEs, as the wide BWP may also support the bandwidth of advanced UEs (which have a wider supported bandwidth than reduced capability UEs).

[0067] Figure 6 is a diagram illustrating an exemplary signal flow for configuring a PDSCH using frequency hopping according to some aspects of the present disclosure. A wireless communication system may include Figure 1-36 and a base station (BS) 604. The base station 604 may use RRC and / or DCI signaling 606 to configure the UE 602 to use frequency hopping for PDSCH. The base station 604 may send the DCI in the PDCCH. In one example, the base station 604 may configure the UE 602 to use one or more companion BWPs for PDSCH frequency hopping, as described above with respect to Figure 4 In another example, the base station 604 can configure the UE 602 to use multiple narrowbands (NBs) within the wide BWP for PDSCH frequency hopping, as described above with respect to Figure 5 For example, RRC and / or DCI signaling 606 may provide information for configuring PDSCH frequency hopping using a companion BWP or NB. Then, UE 602 may receive PDSCH using frequency hopping from base station 604 using a companion / wide BWP or NB.

[0068] For PDSCH frequency hopping configuration, the frequency domain resource allocation (FDRA) may include a starting NB index and resource assignments within the NB. In one example, the configuration information may include an X-bit NB index, where X is determined by the number of NBs within the wide BWP. The NB index identifies the corresponding NB within the wide BWP. The configuration information may also include a resource assignment for the NB identified by the NB index. number of bits, where is the size of the NB (eg, bandwidth). For example, the resource allocation bits may indicate the RBs allocated for PDSCH. In some cases, if the starting NB is the same as the active NB or anchor NB which may be the NB for PDCCH, X may be a zero bit.

[0069] In some examples, when the same search space is used to send broadcast PDCCH to advanced UEs (e.g., UEs supporting wide carrier bandwidth or full carrier bandwidth) in addition to reduced capability UEs, FDRA size alignment may be required for DCI formats (e.g., DCI format 1_0) used for common search space (CSS) to reduce the required PDCCH overhead and / or the number of blind decodes. For FDRA alignment, one or more zero padding bits may be added as the MSB (most significant bit) of the FDRA field, and the bit size of the FDRA field may be increased to It is determined by the size of the wide BWP and has the same size of the FDRA field for resource allocation for advanced UEs. For reduced capability UEs, resource allocation for NB hopping may be determined by the size of the FDRA field. For DCI formats used for UE-specific search space (USS) (e.g., DCI format 1_1), the size of the FDRA field is bits, i.e., no zero padding bits are added to the FDRA field.

[0070] In some aspects of the present disclosure, NB hopping for PDSCH may be semi-statically configured by RRC (with or without dynamic activation / deactivation via DCI). In one example, when DCI activation is used, since interleaved mapping of virtual resource blocks (VRBs) to physical resource blocks (PRBs) is not applied to bandwidth-constrained UEs (e.g., NR light UEs, etc.) configured with wide BWP, the reduced-capability UE may reinterpret or repurpose the VRB to PRB mapping field in the DCI as a frequency hopping (FH) flag, e.g., as described above with respect to Figure 5 as described.

[0071] In one aspect of the present disclosure, the PDSCH-NB hopping configuration may include a hopping time interval t hop and the hopping frequency offset f hop Or the maximum number of jumps N hop For the benefit of inter-cell interference coordination, these parameters may be common to all UEs sharing the same BWP. Based on the above configuration, the NB used for frequency hopping PDSCH transmission may be determined by:

[0072] in, is the narrowband indicated by the DCI, and i is the time slot index, and is the number of narrowbands in the BWP.

[0073] In some aspects of the present disclosure, PDSCH frequency hopping between two NBs may have a time gap between consecutive hops, and the time gap may depend on the UE capability and the NB position in the BWP. In some cases, the time gap may be BWP-specific if desired. For example, the time gap may depend on the RF return time of the UE and the supported maximum communication bandwidth of the UE.

[0074] Figure 7 is a diagram showing an exemplary two PDSCH transmissions using NB frequency hopping. The first PDSCH transmission with NB hopping may be from an active or default NB 702 ( Figure 71). The UE may monitor the PDCCH / DCI in the active or default NB. In this case, the time domain scheduling parameter K0, which defines the time slot level PDSCH scheduling delay, does not change due to NB hopping. For example, when K0 is 0, PDSCH 704 starts from the symbol of PDSCH-based time domain resource allocation (TDRA) in the same time slot as PDCCH (DCI). TDRA may be implemented as a lookup table including multiple entries. TDRA indicates the starting symbol and length of the PDSCH in the time slot. When the second PDSCH transmission 706 is scheduled to be from a NB 708 (other than the activated or default NB 702), the UE may monitor the PDCCH / DCI in the active or default NB. In this case, the time domain scheduling parameter K0, which defines the time slot level PDSCH scheduling delay, does not change due to NB hopping. For example, when K0 is 0, PDSCH 704 starts from the symbol of PDSCH-based time domain resource allocation (TDRA) in the same time slot as PDCCH (DCI). TDRA may be implemented as a lookup table including multiple entries. TDRA indicates the starting symbol and length of the PDSCH in the time slot. Figure 7 When the NB#3 in 706 starts, an additional symbol-level delay can be introduced above K0. For example, the second PDSCH transmission 706 can be postponed for several symbols based on the additional delay. In this case, the configuration of the TDRA table does not have to take into account NB hopping. There is no restriction on the TDRA table, and for non-hopping cases, full scheduling flexibility can be achieved. In one example, the additional delay value can be fixed based on the UE RF return time. Alternatively, the delay value can be a value that ensures that the delayed PDSCH does not start earlier than the time when the UE has completed reconfiguring its RF chain to use a different NB. For example, the delay value can vary based on the difference between the indicated PDCCH to PDSCH time offset and the UE's RF return time. As another example, the delay value can be a value that ensures that the delayed PDSCH still remains within the time slot defined by parameter K0.

[0075] In some aspects of the present disclosure, the use of additional delays may also depend on the PDCCH to PDSCH time offset determined by the PDSCH parameter K0, the TDRA of the PDSCH, and the PDSCH mapping type. PDSCH has two different types of mapping, referred to as type A and type B. These types are characterized by DMRS positions and PDSCH start symbols. For PDSCH mapping type A, the PDSCH start symbol is limited to the first few symbols of the time slot (e.g., symbols 0-3). Therefore, it is not always possible to postpone PDSCH transmission by additional symbol delays. For PDSCH mapping type B, the PDSCH start symbol is more flexible than type A. For example, in the case of a normal CP length, the PDSCH start symbol may be within symbols 0-12, or in the case of an extended CP length, the PDSCH start symbol may be within symbols 0-10. For example, for PDSCH mapping type B, if the PDCCH to PDSCH time offset is less than a threshold, an additional symbol level delay may be used if necessary. The threshold may be a value based on the RF return time of the UE, etc.

[0076] In some aspects of the present disclosure, if the UE does not support additional symbol level delay, the starting NB may be determined based on the PDCCH to PDSCH time offset. For example, if the PDCCH to PDSCH time offset is less than a threshold such that the PDCCH to PDSCH time offset may not provide sufficient delay for the UE to reconfigure its RF chain (e.g., RF return) to use a different NB, the active or default NB for PDCCH monitoring may be used as the starting NB, regardless of the starting NB indicated in the DCI. However, if the PDCCH to PDSCH time offset is not less than the threshold, the UE may use the starting NB indicated by the PDCCH / DCI. In this case, the PDCCH to PDSCH time offset provides sufficient time for the UE to reconfigure its RF chain for the new NB.

[0077] Figure 8 8 is a diagram showing an exemplary narrowband (NB) and subband alignment for PDSCH transmission using frequency hopping (FH). In one aspect of the present disclosure, BWP 802 includes four NBs (in Figure 8 802). In some examples, the start or end of a BWP may not be aligned with a subband. As a result, the size of an edge NB 804 (e.g., NB 0) may be different from other NBs (e.g., NB 1, 2, and 3) in the same BWP 802. In another example, the total number of subbands in a BWP may not be an integer multiple of the total number of subbands in a narrowband. Fig.14 is a diagram showing an example of NB and subband alignment. Fig.14 , the start of the wide BWP 1402 is not aligned with the RBG boundary. When the wide BWP 1402 is divided into multiple NBs (e.g., Fig.14 In some aspects of the present disclosure, the BWP may be divided into NBs by grouping adjacent RBGs into a narrow band.

[0078] Therefore, the first or last NB in ​​a BWP may have a different size than other NBs. Since the resource allocation within a NB is based on the maximum NB size, the PDSCH transmission in the outlying RB 806 of the edge NB (e.g., NB 0) may be punctured. Outlying RBs are RBs that are not included in a BWP.

[0079] In some aspects of the present disclosure, NB frequency hopping is used for UE-specific PDSCH, but not for broadcast PDSCH. For example, UE-specific PDSCH can be scheduled by PDCCH with CRC scrambled by C-RNTI (cell radio network temporary identifier), MCS-C-RNTI (modulation coding scheme cell RNTI), CS-RNTI (configured scheduling RNTI). Broadcast PDSCH does not use frequency hopping.

[0080] When there is overlap in the time domain between PDSCH using NB frequency hopping (FH) and broadcast PDSCH not using NB frequency hopping, certain priority rules may be used to handle the overlap situation. Fig. 9 is a flow chart illustrating an exemplary method 900 for handling overlap between a broadcast PDSCH and a NB-FHPDSCH. In some examples, the method 900 may be Figure 1-3 and operates at any UE in the UEs shown in 6.

[0081] At box 902, the UE determines whether a time domain overlap occurs between a PDSCH using NB frequency hopping (FH) and a broadcast PDSCH that does not utilize FH. At box 904, if the UE determines that there is no overlap, the UE may take no action regarding the overlap. At box 906, if there is an overlap between the broadcast PDSCH and the PDSCH using FH, the UE determines whether the broadcast PDSCH carries at least one of a dedicated system information block (SIB) or on-demand system information requested by the UE. At box 908, if the broadcast PDSCH carries the SIB requested by the UE, the UE may prioritize the broadcast PDSCH over the PDSCH using NB FH. At box 910, if the broadcast PDSCH does not carry the SIB requested by the UE, the UE may use rules to handle the overlap situation based on a specific UE implementation.

[0082] Fig.10 1 is a flow chart illustrating an exemplary process 1000 for transmitting a PDSCH using frequency hopping according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, process 1000 may be performed by Fig.11 In some examples, process 1000 may be performed by any suitable device or unit for performing the functions or algorithms described below.

[0083] At block 1002, a scheduling entity (e.g., a base station or gNB) sends frequency hopping (FH) control information for a PDSCH. The PDSCH may be similar to the above description of Figure 4-8 At block 1004, the scheduling entity transmits a PDSCH using frequency hopping between multiple NBs based on the FH control information. The bandwidth of each NB is not greater than the maximum wireless communication bandwidth supported by the UE receiving the PDSCH.

[0084] In some examples, multiple NBs may be included in the wide bandwidth portion (e.g., in Figure 7 The FH control information may include a wide BWP as shown in FIG, and the BWP has a bandwidth greater than the maximum wireless communication bandwidth of the UE. In some examples, the FH control information may include frequency domain resource allocation (FDRA) information, which includes an NB index and resource assignment for PDSCH. The NB index indicates a starting narrowband selected for PDSCH using frequency hopping between multiple NBs, and the resource assignment allocates frequency resources within the selected narrowband.

[0085] In some examples, the FH control information may include a FDRA field having a first plurality of bits based on a size of a BWP having a bandwidth greater than a maximum wireless communication bandwidth of the UE. The least significant bit of the first plurality of bits may be configured to indicate a starting NB and a resource assignment within the selected narrowband.

[0086] In some examples, the scheduling entity may send a PDSCH using frequency hopping between a first narrowband and a second narrowband among multiple NBs. The first narrowband and the second narrowband may not be adjacent to each other in the frequency domain. When there are one or more RBs between the narrowbands in the frequency domain, the two narrowbands are not adjacent. In some examples, the FH control information may include a hopping time interval, a hopping frequency offset, and a maximum hopping number. In some examples, the scheduling entity may select a narrowband based on the hopping time interval, the hopping frequency offset, and the maximum hopping number.

[0087] In some examples, the scheduling entity may send downlink control information (DCI) for controlling the PDSCH in a first narrowband. The scheduling entity may then send the PDSCH starting in a second narrowband configured based on the DCI. The PDSCH scheduling delay may depend on at least one of the RF return capabilities of the UE.

[0088] In some examples, the scheduling entity may transmit a PDSCH that uses frequency hopping between a first narrowband and a second narrowband. One or more resource blocks in the first narrowband that are not aligned with a subband may be punctured relative to the PDSCH, and the punctured resource blocks are located outside the bandwidth portion that includes the narrowband (e.g., see Figure 8 remote RB in the middle).

[0089] Fig.111 is a block diagram illustrating an example of a hardware implementation for a scheduling entity 1100 employing a processing system 1114. For example, the scheduling entity 1100 may be as described in Figure 1 , 2 , 3 and / or 6, or any one or more of the base stations shown in the figures.

[0090] The scheduling entity 1100 may be implemented using a processing system 1114 including one or more processors 1104. Examples of processors 1104 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, the scheduling entity 1100 may be configured to perform any one or more of the functions described herein. That is, the processor 1104 as utilized in the scheduling entity 1100 may be used to implement the various functions described herein. Figure 4-10 Any one or more of the procedures and processes shown and described.

[0091] In this example, the processing system 1114 may be implemented using a bus architecture, which is generally represented by bus 1102. Depending on the specific application of the processing system 1114 and the overall design constraints, the bus 1102 may include any number of interconnecting buses and bridges. The bus 1102 communicatively couples various circuits including one or more processors (generally represented by processor 1104), memory 1105, and computer readable media (generally represented by computer readable media 1106). The bus 1102 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described any further. The bus 1102 may be implemented as a serial bus or a parallel bus. The bus interface 1108 provides an interface between the bus 1102 and the transceiver 1110. The transceiver 1110 provides a communication interface or unit for communicating with various other devices over a transmission medium. Depending on the nature of the device, a user interface 1112 (e.g., keypad, display, speaker, microphone, joystick, touch screen) may also be provided. Of course, such a user interface 1112 is optional and may be omitted in some examples (such as a base station).

[0092] In some aspects of the present disclosure, processor 1104 may include circuits configured for various functions, including, for example, downlink communications (eg, PDSCH) using frequency hopping. For example, the circuits may be configured to implement Figure 4-10 One or more of the described features.

[0093] For example, the processor 1104 may include a processing circuit 1140, an uplink (UL) communication circuit 1142, and a downlink (DL) communication circuit 1144. The processing circuit 1140 may be configured to perform various data processing, communication, and logic functions in cooperation or without cooperation with one or more other components of the scheduling entity 1100. In one example, the scheduling entity 1100 may use the processing circuit 1140 to schedule and allocate communication resources for UL and DL communications, such as a PDSCH using frequency hopping, such as with respect to Figure 4-10 Described. The scheduling entity 1100 may use the UL communication circuit 1142 to perform various UL communication functions with one or more other devices (e.g., UE). The scheduling entity may use the DL communication circuit 1144 to perform various DL communication functions with one or more other devices (e.g., UE). In one example, the scheduling entity may use the DL communication circuit 1144 to send frequency hopping control information for the PDSCH via the transceiver 1110. In one example, the scheduling entity may use the DL communication circuit 1144 to send a PDSCH using frequency hopping between multiple narrowbands (NBs) based on the frequency hopping control information. The bandwidth of each NB in ​​the multiple NBs is not greater than the maximum wireless communication bandwidth of the UE.

[0094] The processing circuit 1104 is responsible for managing the bus 1102 and general processing, including executing software stored on the computer-readable medium 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described below for any particular device. The computer-readable medium 1106 and the memory 1105 may also be used to store data manipulated by the processor 1104 when executing the software.

[0095] One or more processors 1104 in the processing system can execute software. Software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc., whether it is called software, firmware, middleware, microcode, hardware description language or other terms. Software can reside on computer-readable media 1106. Computer-readable media 1006 can be non-temporary computer-readable media. For example, non-temporary computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable media for storing software and / or instructions that can be accessed and read by a computer. The computer readable medium 1106 may reside in the processing system 1114, external to the processing system 1114, or distributed across multiple entities including the processing system 1114. The computer readable medium 1106 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the specific application and the overall design constraints imposed on the entire system.

[0096] In one or more examples, the computer-readable storage medium 1106 may include software configured for various functions, including, for example, downlink communications (e.g., PDSCH) using frequency hopping. For example, the software may be configured to implement the above-described Figure 4-10 One or more of the described features.

[0097] For example, the software may include processing instructions 1152, UL communication instructions 1154, and DL communication instructions 1156. When executed by the processor 1104, the processing instructions may perform various data processing, communication, and logic functions in cooperation or without cooperation with one or more other components of the scheduling entity 1100. When executed by the processor 1104, the UL communication instructions 1154 may perform various UL communication functions with one or more other devices (e.g., UEs). When executed by the processor 1104, the DL communication instructions 1156 may perform various DL communication functions with one or more other devices (e.g., UEs), such as PDSCH transmissions using frequency hopping.

[0098] In one configuration, a scheduling entity 1100 for wireless communication includes: a unit for sending frequency hopping control information for a PDSCH to a UE; and a unit for sending a PDSCH using frequency hopping between multiple NBs based on the frequency hopping control information. The bandwidth of each NB in ​​the multiple NBs is not greater than the maximum wireless communication bandwidth of the UE. In one aspect, the aforementioned unit may be in Fig.11 The processor 1104 shown in FIG. 1 is configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0099] Of course, in the above examples, the circuits included in the processor 1004 are provided only as examples, and other units for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1106, or in Figure 1 , 2 , 3 and / or 6 and using, for example, the present invention Figure 4-10 Any other suitable means or elements of the described processes and / or algorithms.

[0100] Fig.12 1 is a flow chart illustrating an exemplary process 1200 for receiving a PDSCH using frequency hopping according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementations of all embodiments. In some examples, the process 1200 may be performed by Fig.13 In some examples, process 1200 may be performed by any suitable apparatus (eg, UE) or unit for performing the functions or algorithms described below.

[0101] At block 1202, a scheduled entity (eg, a UE) receives frequency hopping (FH) control information for a PDSCH. The PDSCH may be similar to that described above with respect to Figure 4-8 At block 1204, the scheduled entity receives a PDSCH using frequency hopping between multiple NBs based on the FH control information. The bandwidth of each NB in ​​the multiple NBs is not greater than the maximum wireless communication bandwidth of the scheduled entity.

[0102] In some examples, multiple NBs may be included in the wide bandwidth portion (e.g., in Figure 7In some examples, the FH control information may include frequency domain resource allocation (FDRA) information, which includes an NB index and a resource assignment. The NB index indicates a starting narrowband selected for a PDSCH using frequency hopping between multiple NBs, and the resource assignment allocates resources within the selected narrowband for the PDSCH.

[0103] In some examples, the FH control information may include a FDRA field having a first plurality of bits having a size based on a wide BWP having a bandwidth greater than a maximum wireless communication bandwidth of a scheduled entity. The least significant bit of the first plurality of bits may be configured to indicate a resource assignment for the PDSCH within the selected narrowband.

[0104] In some examples, the scheduled entity may receive a PDSCH that uses frequency hopping between a first narrowband and a second narrowband. The first narrowband and the second narrowband may not be adjacent to each other in the frequency domain. In some examples, the FH control information may include a hopping time interval, a hopping frequency offset, and a maximum number of hoppings. In some examples, the scheduled entity may select a narrowband between multiple NBs based on the hopping time interval, the hopping frequency offset, and the maximum number of hoppings.

[0105] In some examples, the scheduled entity may receive downlink control information (DCI) for controlling the PDSCH in a first narrowband. The scheduled entity may then receive the PDSCH starting in a second narrowband. The delay between the DCI and the PDSCH may depend on at least one of the RF return capability of the scheduled entity or the slot level PDSCH scheduling delay.

[0106] In some examples, the scheduled entity may receive a PDSCH that uses frequency hopping between a first narrowband and a second narrowband. One or more resource blocks in the first narrowband that are not aligned with a subband are punctured relative to the PDSCH, and the punctured resource blocks are located outside of a bandwidth portion that includes multiple NBs (e.g., see Figure 8 remote RB in the middle).

[0107] In some examples, when the broadcast PDSCH partially overlaps with the UE-specific PDSCH, the scheduled entity may prioritize the broadcast PDSCH over the UE-specific PDSCH utilizing frequency hopping. For example, if the broadcast PDSCH carries SIBs requested by the scheduled entity, the scheduled entity may prioritize the broadcast PDSCH over the UE-specific PDSCH.

[0108] Fig.131304. The 1304-1406 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary scheduled entity 1300 employing a processing system 1314. According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1314 including one or more processors 1304. For example, the scheduled entity 1300 may be as in Figure 1 , 2 , 3 and / or 6, or any one or more of the user equipment (UE) shown in FIG.

[0109] The processing system 1314 may be substantially the same as in Fig.11 The processing system 1114 shown in FIG. 1 is the same as that shown in FIG. 1 , including a bus interface 1308, a bus 1302, a memory 1305, a processor 1304, and a computer-readable medium 1306. In addition, the scheduling entity 1300 may include a user interface 1312 and a transceiver 1310, which are substantially similar to those described above in FIG. Fig.11 That is, the processor 1304 as utilized in the scheduled entity 1300 may be used to implement Figure 4-9 and any one or more of the processes shown in 12.

[0110] In some aspects of the present disclosure, processor 1304 may include circuits configured for various functions, including, for example, downlink communications (eg, PDSCH) using frequency hopping. For example, the circuits may be configured to implement the following description of Figure 4-9 and Fig.12 One or more of the described features.

[0111] For example, the processor 1304 may include a processing circuit 1340, an uplink (UL) communication circuit 1342, and a downlink (DL) communication circuit 1344. The processing circuit 1340 may be configured to perform various data processing, communication, and logic functions in cooperation or without cooperation with one or more other components of the scheduled entity 1300. In one example, the scheduled entity 1300 may use the processing circuit 1340 to schedule and allocate communication resources for UL and DL communications, such as, for example, Figure 4-9and 12 as described in connection with the PDSCH using frequency hopping. The UL communication circuit 1342 may be configured to perform various UL communication functions with one or more other devices (e.g., a scheduling entity). The DL communication circuit 1344 may be configured to perform various DL communication functions with one or more other devices (e.g., a scheduling entity). In one example, the scheduled entity may use the DL communication circuit 1344 to receive frequency hopping (FH) control information for the PDSCH via the transceiver 1310. In one example, the scheduling entity may use the DL communication circuit 1344 to receive a PDSCH using frequency hopping between multiple NBs based on the frequency hopping control information. The bandwidth of each of the multiple NBs is not greater than the maximum wireless communication bandwidth of the scheduled entity.

[0112] In one configuration, a scheduling entity 1300 for wireless communication includes: a unit for receiving frequency hopping control information for a PDSCH; and a unit for receiving a PDSCH using frequency hopping between multiple NBs based on the frequency hopping control information. The bandwidth of each NB in ​​the multiple NBs is not greater than the maximum wireless communication bandwidth of the scheduled entity. In one aspect, the aforementioned unit may be in Fig.13 The processor 1304 shown in FIG. 1 is configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any device configured to perform the functions recited by the aforementioned means.

[0113] Of course, in the above example, the circuits included in the processor 1304 are provided only as examples, and other units for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1306, or in the computer-readable storage medium 1306. Figure 1 , 2 , 3 and / or 6 and using, for example, the present invention Figure 4-9 and any other suitable means or units for the processes and / or algorithms described in 12.

[0114] Several aspects of wireless communication networks are presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0115] For example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed depends on the specific application and the overall design constraints imposed on the system.

[0116] In the present disclosure, the word "exemplary" is used to mean "serving as an example, instance or illustration". Any implementation or aspect described herein as "exemplary" should not be interpreted as being preferred or having advantages over other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the features, advantages or modes of operation discussed. The term "coupling" is used herein to refer to a direct coupling or an indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object can be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "electronic circuit" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (wherein these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuit) and software implementations of information and instructions (wherein these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).

[0117] Can Figure 1-14 One or more of the components, steps, features and / or functions shown in the present invention may be rearranged and / or combined into a single component, step, feature or function, or may be embodied in several components, steps or functions. In addition, additional elements, components, steps and / or functions may be added without departing from the novel features disclosed herein. Figure 1-14 The devices, apparatuses and / or components shown in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0118] It is to be understood that the specific order or hierarchy of steps in the methods disclosed herein is an illustration of an exemplary process. It is to be understood that the specific order or hierarchy of steps in these methods may be rearranged based on design preferences. The attached method claims present elements of the various steps in an example order, but are not intended to be limited to the specific order or hierarchy presented unless expressly recorded herein.

[0119] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise explicitly stated, the term "some" refers to one or more. A phrase referring to "at least one" in a list of items refers to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described in this disclosure, which are known or will be known to those skilled in the art, are expressly incorporated herein by reference, and are intended to be included by the claims. In addition, no disclosure herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. An apparatus for wireless communication at a user equipment (UE) configured with reduced capabilities, the apparatus comprising: processor; as well as a memory configured to be communicatively coupled to the processor and to store instructions that, when executed by the processor, cause the apparatus to: receiving frequency hopping FH control information from a scheduling entity to enable reception of transmissions via a physical downlink shared channel PDSCH; and receiving the transmission via the PDSCH using frequency hopping between a plurality of narrowband NBs based on the received FH control information, wherein the plurality of NBs are configured by the scheduling entity, and receiving the transmission comprises: frequency hopping between at least two different NBs in the plurality of NBs to receive the transmission via the PDSCH; The FH control information includes frequency domain resource allocation FDRA information, and the FDRA information includes: an index configured to indicate a narrowband selected for starting the reception of the PDSCH using frequency hopping between the plurality of NBs; and resource assignment of resource blocks allocated to the PDSCH within the selected narrowband; and The bandwidth of each NB among the multiple NBs is narrower than the maximum wireless communication bandwidth of the device.

2. The device according to claim 1, wherein: The plurality of NBs are included in a bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the apparatus.

3. The device according to claim 2, wherein: When executed by the processor, the instructions further cause the apparatus to perform the following operations: determine the configuration of the plurality of NBs based on at least one of a radio resource control (RRC) configuration or a predetermined rule.

4. The device according to claim 3, wherein: The RRC configuration or the predetermined rule defines a plurality of contiguous subbands allocated to each of the plurality of NBs, wherein a size of the subbands is configurable based at least on a bandwidth of the bandwidth portion.

5. The device according to claim 3, wherein: The RRC configuration or the predetermined rule defines a plurality of contiguous resource block groups allocated to each of the plurality of NBs, wherein a size of the resource block groups is configurable based at least on a bandwidth of the bandwidth part.

6. The device according to claim 1, wherein: The FH control information includes a FDRA field including a plurality of bits based on a size of the narrowband and a number of the plurality of NBs in a bandwidth part.

7. The device according to claim 1, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: receiving downlink control information DCI mapped to a common search space, wherein the FH control information includes a FDRA field included in the DCI, wherein the FDRA field comprises a first plurality of bits based on a size of a bandwidth portion, the bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the device, and The least significant bit of the first plurality of bits is configured to indicate the narrowband selected for starting the reception of the PDSCH and the resource assignment within the selected narrowband.

8. The device according to claim 1, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: The PDSCH using frequency hopping between a first narrowband and a second narrowband among the plurality of NBs is received, the first narrowband and the second narrowband being not adjacent to each other in the frequency domain.

9. The device according to claim 1, wherein: The FH control information includes a hopping time interval, a hopping frequency offset and a maximum hopping number.

10. The device according to claim 9, wherein: The instructions, when executed by the processor, further cause the apparatus to perform the following operations: select a narrowband among the plurality of NBs based on the hopping time interval, the hopping frequency offset, and the maximum hopping number.

11. The device according to claim 1, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: receiving downlink control information DCI in a first narrowband among the plurality of NBs, the DCI being configured to control the PDSCH; and The PDSCH is received starting in a second narrowband among the plurality of NBs, wherein a start time of the PDSCH depends on at least one of an RF return time of the device or a PDSCH scheduling delay indicated in the DCI.

12. The device according to claim 11, wherein The PDSCH scheduling delay indicated in the DCI is less than the RF return time, the start of the PDSCH in the second narrowband is postponed by an additional delay of multiple symbols.

13. The device according to claim 1, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: receiving downlink control information DCI in a first narrowband among the plurality of NBs, the DCI being configured to indicate a PDSCH scheduling delay and a narrowband index for starting the reception of the PDSCH, When the PDSCH scheduling delay is less than an RF return time of the device, the PDSCH starting in the first narrowband according to the PDSCH scheduling delay and covering the narrowband index is received.

14. The device according to claim 1, wherein: The processor is further configured to: The PDSCH is received using frequency hopping between a first narrowband and a second narrowband as edge narrowbands among the multiple NBs, wherein one or more resource blocks of the first narrowband that are not aligned with the subband are punctured relative to the PDSCH, and the punctured resource blocks are located outside the bandwidth portion including the multiple NBs.

15. The device according to claim 1, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: Prioritizing reception of a broadcast PDSCH without frequency hopping over the PDSCH with frequency hopping, the PDSCH with frequency hopping having at least one symbol overlapping with the reception of the broadcast PDSCH without frequency hopping, wherein the broadcast PDSCH includes on-demand system information.

16. An apparatus for wireless communication at a scheduling entity, the apparatus comprising: processor; as well as a memory configured to be communicatively coupled to the processor and to store instructions that, when executed by the processor, cause the apparatus to: sending frequency hopping FH control information to a user equipment UE configured with reduced capability to enable reception of transmissions via a physical downlink shared channel PDSCH by the UE; as well as sending the transmission to the UE via the PDSCH using frequency hopping between a plurality of narrowband NBs based on the transmitted FH control information, wherein the plurality of NBs are configured by the scheduling entity, and sending the transmission comprises: frequency hopping between at least two different NBs in the plurality of NBs to send the transmission via the PDSCH; The FH control information includes frequency domain resource allocation FDRA information, and the FDRA information includes: an index configured to indicate a narrowband selected for starting reception of the PDSCH using frequency hopping between the plurality of NBs; and resource assignment of resource blocks allocated to the PDSCH within the selected narrowband; and The bandwidth of each NB among the multiple NBs is narrower than the maximum wireless communication bandwidth of the UE.

17. The device according to claim 16, wherein: The plurality of NBs are included in a bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the UE.

18. The device according to claim 16, wherein: The FH control information includes a FDRA field including a plurality of bits based on a size of the narrowband and a number of the plurality of NBs in a bandwidth part.

19. The device according to claim 16, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: Sending downlink control information DCI mapped to the common search space, wherein the FH control information includes a FDRA field included in the DCI, wherein the FDRA field comprises a first plurality of bits based on a size of a bandwidth portion, the bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the UE, and The least significant bit of the first plurality of bits is configured to indicate the narrowband selected for starting the reception of the PDSCH and the resource assignment within the selected narrowband.

20. The device according to claim 16, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: The PDSCH using frequency hopping between a first narrowband and a second narrowband among the plurality of NBs is transmitted, the first narrowband and the second narrowband being not adjacent to each other in a frequency domain.

21. The device according to claim 16, wherein: The FH control information includes a hopping time interval, a hopping frequency offset and a maximum hopping number.

22. The device according to claim 21, wherein The instructions, when executed by the processor, further cause the apparatus to select a narrowband from the plurality of NBs based on the hopping time interval, the hopping frequency offset, and the maximum hopping number.

23. The device according to claim 16, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: Sending downlink control information DCI in a first narrowband among the plurality of NBs, the DCI being configured to control the PDSCH; and The PDSCH starting in a second narrowband among the plurality of NBs is transmitted, wherein a start time of the PDSCH depends on at least one of an RF return time of the UE or a PDSCH scheduling delay indicated in the DCI.

24. The device according to claim 23, wherein: The PDSCH scheduling delay indicated in the DCI is less than the RF return time, the start of the PDSCH in the second narrowband is postponed by an additional delay of multiple symbols.

25. The device according to claim 16, wherein: When executed by the processor, the instructions further cause the device to perform the following operations: transmitting downlink control information DCI in a first narrowband among the plurality of NBs, the DCI being configured to indicate a PDSCH scheduling delay and a narrowband index for starting reception of the PDSCH, When the PDSCH scheduling delay is less than the RF return time of the UE, the PDSCH starting in the first narrowband according to the PDSCH scheduling delay and covering the narrowband index is transmitted.

26. The device according to claim 16, wherein: The processor is further configured to: The PDSCH using frequency hopping is transmitted between a first narrowband and a second narrowband as edge narrowbands among the multiple NBs, wherein one or more resource blocks of the first narrowband that are not aligned with the subband are punctured relative to the PDSCH, and the punctured resource blocks are located outside the bandwidth portion including the multiple NBs.

27. A method for wireless communication performed by a user equipment (UE) configured with reduced capabilities, the method comprising: receiving frequency hopping FH control information from a scheduling entity to enable reception of transmissions via a physical downlink shared channel PDSCH; as well as receiving the transmission via the PDSCH using frequency hopping between a plurality of narrowband NBs based on the received FH control information, wherein the plurality of NBs are configured by the scheduling entity, and receiving the transmission comprises: frequency hopping between at least two different NBs in the plurality of NBs to receive the transmission via the PDSCH; The FH control information includes frequency domain resource allocation FDRA information, and the FDRA information includes: an index configured to indicate a narrowband selected for starting the reception of the PDSCH using frequency hopping between the plurality of NBs; and resource assignment of resource blocks allocated to the PDSCH within the selected narrowband; and The bandwidth of each NB among the multiple NBs is narrower than the maximum wireless communication bandwidth of the UE.

28. The method according to claim 27, wherein: The plurality of NBs are included in a bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the UE.

29. The method according to claim 28, further comprising: The configuration of the plurality of NBs is determined based on at least one of a radio resource control (RRC) configuration or a predetermined rule.

30. The method of claim 29, wherein: The RRC configuration or the predetermined rule defines a plurality of consecutive subbands allocated to each of the plurality of NBs and a bandwidth of the bandwidth portion.

31. The method of claim 29, wherein: The RRC configuration or the predetermined rule defines a plurality of consecutive resource block groups allocated to each of the plurality of NBs and a bandwidth of the bandwidth portion.

32. The method of claim 27, wherein: The FH control information includes a FDRA field including a plurality of bits based on a size of the narrowband and a number of the plurality of NBs in a bandwidth part.

33. The method of claim 27, further comprising: receiving downlink control information DCI mapped to a common search space, wherein the FH control information includes a FDRA field included in the DCI, wherein the FDRA field comprises a first plurality of bits based on a size of a bandwidth portion, the bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the UE, and The least significant bit of the first plurality of bits is configured to indicate the narrowband selected for starting the reception of the PDSCH and the resource assignment within the selected narrowband.

34. The method of claim 27, further comprising: The PDSCH using frequency hopping between a first narrowband and a second narrowband among the plurality of NBs is received, the first narrowband and the second narrowband being not adjacent to each other in the frequency domain.

35. The method of claim 27, wherein: The FH control information includes a hopping time interval, a hopping frequency offset and a maximum hopping number.

36. The method of claim 35, further comprising: A narrowband is selected among the plurality of NBs based on the hopping time interval, the hopping frequency offset, and the maximum hopping number.

37. The method of claim 27, further comprising: Receiving downlink control information DCI in a first narrowband among the plurality of NBs, the DCI being configured to control the PDSCH; as well as The PDSCH is received starting in a second narrowband among the plurality of NBs, wherein a start time of the PDSCH depends on at least one of an RF return time of the UE or a PDSCH scheduling delay indicated in the DCI.

38. The method of claim 37, wherein: The PDSCH scheduling delay indicated in the DCI is less than the RF return time, the start of the PDSCH in the second narrowband is postponed by an additional delay of multiple symbols.

39. The method of claim 27, further comprising: receiving downlink control information DCI in a first narrowband among the plurality of NBs, the DCI being configured to indicate a PDSCH scheduling delay and a narrowband index for starting the reception of the PDSCH, When the PDSCH scheduling delay is less than the RF return time of the UE, the PDSCH starting in the first narrowband according to the PDSCH scheduling delay and covering the narrowband index is received.

40. The method of claim 27, further comprising: The PDSCH is received using frequency hopping between a first narrowband and a second narrowband as edge narrowbands among the multiple NBs, wherein one or more resource blocks of the first narrowband that are not aligned with the subband are punctured relative to the PDSCH, and the punctured resource blocks are located outside the bandwidth portion including the multiple NBs.

41. The method of claim 27, further comprising: Prioritizing reception of a broadcast PDSCH without frequency hopping over the PDSCH with frequency hopping, the PDSCH with frequency hopping having at least one symbol overlapping with the reception of the broadcast PDSCH without frequency hopping, wherein the broadcast PDSCH includes on-demand system information.

42. A method for wireless communication performed by a scheduling entity, the method comprising: sending frequency hopping FH control information to a user equipment UE configured with reduced capability to enable reception of transmissions via a physical downlink shared channel PDSCH by the UE; as well as sending the transmission to the UE via the PDSCH using frequency hopping between a plurality of narrowband NBs based on the transmitted FH control information, wherein the plurality of NBs are configured by the scheduling entity, and sending the transmission comprises: frequency hopping between at least two different NBs in the plurality of NBs to send the transmission via the PDSCH; The FH control information includes frequency domain resource allocation FDRA information, and the FDRA information includes: an index configured to indicate a narrowband selected for starting reception of the PDSCH using frequency hopping between the plurality of NBs; and resource assignment of resource blocks allocated to the PDSCH within the selected narrowband; and The bandwidth of each NB among the multiple NBs is narrower than the maximum wireless communication bandwidth of the UE.

43. The method of claim 42, wherein: The plurality of NBs are included in a bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the UE.

44. The method of claim 42, wherein: The FH control information includes a FDRA field including a plurality of bits based on a size of the narrowband and a number of the plurality of NBs in a bandwidth part.

45. The method of claim 42, further comprising: Sending downlink control information DCI mapped to the common search space, wherein the FH control information includes a FDRA field included in the DCI, wherein the FDRA field comprises a first plurality of bits based on a size of a bandwidth portion, the bandwidth portion having a bandwidth greater than the maximum wireless communication bandwidth of the UE, and The least significant bit of the first plurality of bits is configured to indicate the narrowband selected for starting the reception of the PDSCH and the resource assignment within the selected narrowband.

46. ​​The method of claim 42, further comprising: The PDSCH using frequency hopping between a first narrowband and a second narrowband among the plurality of NBs is transmitted, the first narrowband and the second narrowband being not adjacent to each other in a frequency domain.

47. The method of claim 42, wherein: The FH control information includes a hopping time interval, a hopping frequency offset and a maximum hopping number.

48. The method of claim 47, further comprising: A narrowband is selected among the plurality of NBs based on the hopping time interval, the hopping frequency offset, and the maximum hopping number.

49. The method of claim 42, further comprising: Sending downlink control information DCI in a first narrowband among the plurality of NBs, wherein the DCI is configured to control the PDSCH; as well as The PDSCH starting in a second narrowband among the plurality of NBs is transmitted, wherein a start time of the PDSCH depends on at least one of an RF return time of the UE or a PDSCH scheduling delay indicated in the DCI.

50. The method of claim 49, wherein: The PDSCH scheduling delay indicated in the DCI is less than the RF return time, the start of the PDSCH in the second narrowband is postponed by an additional delay of multiple symbols.

51. The method of claim 42, further comprising: transmitting downlink control information DCI in a first narrowband among the plurality of NBs, the DCI being configured to indicate a PDSCH scheduling delay and a narrowband index for starting reception of the PDSCH, When the PDSCH scheduling delay is less than the RF return time of the UE, the PDSCH starting in the first narrowband according to the PDSCH scheduling delay and covering the narrowband index is transmitted.

52. The method of claim 42, further comprising: transmitting the PDSCH using frequency hopping between a first narrowband and a second narrowband as edge narrowbands among the plurality of NBs, One or more resource blocks of the first narrowband that are not aligned with the subband are punctured relative to the PDSCH, and the punctured resource blocks are located outside the bandwidth part including the multiple NBs.

Images