Bandwidth partial frequency hopping for enhanced lightweight UE

By introducing frequency hopping operations based on bandwidth parts in the new 5G radio network, the spectral efficiency and throughput performance degradation caused by the small bandwidth of enhanced lightweight UEs is solved, and the frequency diversity gain is improved and resource coexistence is achieved.

CN119096471APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095295.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-24
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The enhanced lightweight UE has significantly deteriorated spectrum efficiency and throughput performance due to reduced bandwidth, and lacks frequency diversity gain, making it difficult to effectively perform frequency diversity operations.

Method used

By introducing bandwidth-based frequency hopping operations in the new 5G radio network, the frequency hopping BWP is dynamically activated and deactivated, and the frequency resource block offset and subband size are adjusted to achieve the improvement of frequency diversity gain.

Benefits of technology

Under narrow bandwidth conditions, the frequency diversity gain of eRedcap UE is significantly improved through frequency hopping technology, ensuring efficient spectrum usage and throughput performance, avoiding resource fragmentation and conflict, and supporting efficient coexistence with traditional UEs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096471A_ABST
    Figure CN119096471A_ABST
Patent Text Reader

Abstract

A user equipment (UE) configured to: receive a configuration for parameters from a network, the parameters including time and frequency resource parameters for a first bandwidth portion (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; determining time and frequency resource parameters for the one or more FH BWPs based in part on the information included in the configuration, the time and frequency resource parameters for the FH BWPs including at least a first physical resource block (PRB) offset between the first BWP and a first FH BWP; receiving a scheduled downlink control information (DCI) indicating that the first BWP and a subset of the determined FH BWP are activated for the first channel; and performing uplink (UL) or downlink (DL) communication on the first channel in the first BWP and the one or more FH BWPs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to communications, and more particularly to bandwidth fractional frequency hopping for enhanced lightweight UEs. Background Art

[0002] In a 5G New Radio (NR) network, a bandwidth part (BWP) may be configured and activated for a user equipment (UE) so that the UE may transmit a physical uplink shared channel (PUSCH), receive a physical downlink shared channel (PDSCH), and / or perform other functions within the activated resources. For some existing UEs, the UE bandwidth may be 50 MHz or 100 MHz and include, for example, up to 273 physical resource blocks (PRBs) for the BWP. For some other UEs, such as enhanced lightweight (eRedcap) UEs, the UE bandwidth may be as low as 10 MHz or 5 MHz and include, for example, only up to 11 PRBs. Relative to a UE with a bandwidth of 50 MHz or 100 MHz, a UE with a bandwidth of 5 MHz or 10 MHz will experience significant degradation in spectral efficiency and throughput performance due to the lack of frequency diversity gain caused by the reduced UE bandwidth.

[0003] Summary of the invention - to be completed after the claims are completed

[0004] Some exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations. The operations include: receiving a configuration for parameters from a network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; determining the time and frequency resource parameters for the one or more FH BWPs based in part on information included in the configuration from the network, the time and frequency resource parameters for the FH BWPs including at least a first physical resource block (PRB) offset between the first BWP and a first determined FH BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP and a subset of the determined FH BWPs are activated for a first channel; and performing uplink (UL) or downlink (DL) communications on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0005] Other exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations. The operations include: receiving a configuration for parameters from a network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; receiving an indication that at least one of the one or more FH BWPs is activated; determining time and resource parameters for one or more activated FH BWPs by excluding one or more deactivated FH BWPs based on information included in the configuration from the network and the scheduling DCI; and performing uplink (UL) or downlink (DL) communications on the first channel in the activated first BWP and the determined one or more activated FH BWPs.

[0006] A further exemplary embodiment relates to a processor of a user equipment (UE) configured to perform operations. The operations include: receiving configuration for parameters from a network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; determining time and frequency resource parameters for the one or more FH BWPs based on information included in the network configuration and the scheduling DCI, the determined time and frequency resource parameters including an FH interval value including a number of time slots in which the same RB position of the BWP is maintained; and performing uplink (UL) or downlink (DL) communications on the first channel in the activated first BWP and the determined one or more FH BWPs. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0008] Figure 2 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0009] Figure 3 An exemplary base station according to various exemplary embodiments is shown.

[0010] Figure 4 An example illustrating the reduced bandwidth (5 MHz / 11 PRBs) of an enhanced lightweight (eRedcap) user equipment (UE) relative to the bandwidth (50 MHz / 270 PRBs) of some non-eRedcap UEs is shown.

[0011] Figure 5 A diagram illustrating exemplary bandwidth part (BWP) based frequency hopping (FH) operations for downlink (DL) or uplink (UL) operations of an eRedcap user equipment (UE) according to various exemplary embodiments.

[0012] Figure 6 A diagram illustrating exemplary subband-based bandwidth part (BWP)-based frequency hopping (FH) operation for downlink (DL) or uplink (UL) operation of an eRedcap user equipment (UE) according to various exemplary embodiments.

[0013] Figure 7a An exemplary MAC-CE for C-BWP or subband activation / deactivation is shown according to various exemplary embodiments.

[0014] Figure 7b An exemplary table for a two-bit FHI field description is shown in accordance with various exemplary embodiments.

[0015] Figure 7c The use of various exemplary embodiments is shown Figure 7b An illustration of C-BWP or subband activation / deactivation of the FHI field.

[0016] Figure 8 A diagram illustrating an exemplary BWP-based frequency hopping (FH) operation with FH spacing enabled, according to various exemplary embodiments.

[0017] Fig. 9 Methods for bandwidth part (BWP) based frequency hopping (FH) operation for downlink (DL) or uplink (UL) operation of an eRedcap user equipment (UE) according to various exemplary embodiments are shown. DETAILED DESCRIPTION

[0018] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein similar elements have the same reference numerals. The exemplary embodiments introduce modes and techniques for bandwidth part (BWP) based frequency hopping (FH) operation for enhanced lightweight (eRedcap) user equipment (UE). According to some exemplary embodiments, network configurations for BWP based FH operation are described. In other exemplary embodiments, activation / deactivation of FH operation is described, including activation / deactivation of frequency hopping for specific resource block (RB) regions and / or specific channels.

[0019] The exemplary embodiments are described with respect to UE. Those skilled in the art will appreciate that a UE may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a tablet phone, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. Further described are exemplary embodiments with respect to an enhanced lightweight (eRedcap) UE having a significantly reduced operating bandwidth relative to other conventional UEs. However, the exemplary embodiments may be used with any UE operating under similar or different constraints and are not specifically limited to eRedcap UEs. Therefore, a UE as described herein is used to represent any electronic component that communicates directly with a network.

[0020] The exemplary embodiments are also described with reference to a 5G New Radio (NR) network. However, reference to a 5G NR network is provided for illustrative purposes only. The exemplary embodiments may be used with any network that implements a UDC method similar to that described herein. Thus, a 5G NR network as described herein may represent any type of network that implements UDC functionality similar to that of a 5G NR network.

[0021] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a tablet phone, an embedded device, a wearable device (e.g., HMD, AR glasses, etc.), an Internet of Things (IoT) device, an Industrial IoT (IIot) device, etc. It should also be understood that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with a single UE 110 is provided.

[0022] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, next generation RAN (NG-RAN), long term evolution (LTE) RAN, traditional cellular network, WLAN, etc.), and UE 110 may also communicate with the network via a wired connection. Referring to the exemplary embodiment, UE 110 may establish a connection with 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with NR RAN 120.

[0023] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, cells or base stations (Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive communication traffic from UEs equipped with appropriate cellular chipsets.

[0024] UE 110 may connect to 5G NR-RAN 120 via gNB 120A. Those skilled in the art will appreciate that any relevant procedures may be performed for UE 110 to connect to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 may be associated with a particular cellular provider, where UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 may transmit corresponding credential information in order to associate with 5G NR-RAN 120. More specifically, UE 110 may be associated with a particular base station (e.g., gNB 120A). However, as described above, reference to 5G NR-RAN 120 is for illustrative purposes only, and any suitable type of RAN may be used.

[0025] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0026] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1100 is used to describe the UE 110 with respect to the network arrangement 100 of FIG. UE 110 may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, an audio input device, an audio output device, a power source, a data acquisition device, a port for electrically connecting UE 110 to other electronic devices, and the like.

[0027] The processor 205 may be configured to execute multiple engines of the UE 110. For example, these engines may include a BWP-based frequency hopping engine 235 for performing various operations related to BWP-based frequency hopping. These operations may include receiving parameters for BWP configuration and additional parameters for determining the time and frequency position of the frequency hopping to be used when the BWP is activated. These operations may also include receiving one or more scheduling DCIs, which include parameters for activating the BWP for a downlink (DL) or uplink (UL) channel and additional parameters for performing frequency hopping on the channel indicated in the scheduling DCI. These operations may also include determining the frequency hopping position to be used in DL / UL operation based on the configured / indicated parameters received from the network. These operations will be explained in detail below.

[0028] The engine 235 described above is provided as an application (e.g., a program) executed by the processor 205 for illustrative purposes only. The functions associated with the engine 235 may also be represented as independent combined components of the UE 110, or may be modular components coupled to the UE 110, for example, integrated circuits with or without firmware. For example, the integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing signals and other information. The engine may also be embodied as an application or an independent application. In addition, in some UEs, the functions described for the processor 205 are split between two or more processors such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0029] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables user input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120 and / or any other suitable type of network. Thus, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies).

[0030] Figure 3 An exemplary base station 300 is shown in accordance with various exemplary embodiments. Base station 300 may represent any access node (e.g., gNB 120A, etc.) that UE 110 may use to establish a connection and manage network operations.

[0031] Base station 300 may include processor 305, memory arrangement 310, input / output (I / O) devices 315, transceiver 320, and other components 325. Other components 325 may include, for example, batteries, data acquisition devices, ports for electrically connecting base station 300 to other electronic devices, and the like.

[0032] The processor 305 may be configured to execute multiple engines of the base station 300. For example, these engines may include a BWP-based frequency hopping engine 330 for performing various operations related to BWP-based frequency hopping. These operations may include transmitting parameters for BWP configuration and additional parameters for the UE to determine the time and frequency position of the frequency hopping to be used when the BWP is activated. These operations may also include transmitting one or more scheduling DCIs, which include parameters for activating the BWP for the UE for a downlink (DL) or uplink (UL) channel and additional parameters for frequency hopping on the channel indicated in the scheduling DCI. The network, which knows the frequency hopping position used in the DL / UL operation, can schedule other channels for other UEs on the same component carrier to minimize interference between the signals. These operations will be explained in detail below.

[0033] The engine 330 described above as an application (e.g., a program) executed by the processor 305 is merely exemplary. The functions associated with the engine 330 may also be represented as a separate combined component of the base station 300, or may be a modular component coupled to the base station 300, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuits for receiving signals and processing circuits for processing signals and other information. In addition, in some base stations, the functionality described for the processor 305 is split between multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0034] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that enables a user to interact with the base station 300. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies). Thus, the transceiver 320 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0035] A framework has been established to enable lightweight (Redcap) NR devices suitable for a range of use cases, including, for example, industrial sensors, video surveillance and wearables, with requirements for low UE complexity and, in some scenarios, low UE power consumption. It is expected that further reductions in the complexity and cost of Redcap devices will further expand the market for Redcap use cases, providing relatively low cost, low energy consumption and low data rate requirements for, for example, industrial wireless sensor network use cases.

[0036] For Rel-18, the target peak rate supported by enhanced Redcap (eRedcap) devices is 10 Mbps. To further reduce the complexity of eRedcap UEs, the UE bandwidth can be reduced to 5 MHz in FR1, the UE peak rate in FR1 can be reduced, and the UE processing timeline for PDSCH and / or PUSCH and / or CSI can be relaxed.

[0037] Existing (non-Redcap) UEs typically operate with up to 270 PRBs with 15kHz subcarrier spacing (SCS) (corresponding to 50MHz bandwidth) and up to 273 PRBs with 30kHz SCS (corresponding to 100MHz bandwidth). As illustrated in Table 1, a 5MHz bandwidth consists of 25 PRBs with 15kHz SCS and 11 PRBs with 30kHz SCS.

[0038]

[0039] Table 1

[0040] Compared to non-Redcap UEs operating with significantly higher bandwidths and larger numbers of PRBs, the spectral efficiency and throughput performance of eRedcap UEs operating with a reduced 5 MHz bandwidth (and a smaller number of PRBs) may be significantly degraded due to the lack of frequency diversity gain. Figure 4 An example illustrating the reduced bandwidth (5 MHz / 11 PRBs) of an enhanced lightweight (eRedcap) user equipment (UE) relative to the bandwidth (50 MHz / 270 PRBs) of some non-eRedcap UEs is shown. For channels within this effective bandwidth part (BWP) of 11 PRBs, the lack of frequency diversity across the reduced BWP may result in significant performance degradation.

[0041] A carrier bandwidth part (BWP) refers to a set of contiguous physical resource blocks (PRBs) selected from a contiguous subset of common resource blocks of a given numerology on a given carrier. Up to four BWPs can be configured for downlink (DL) or uplink (UL), where one of the configured BWPs can be active for DL ​​or UL at a given time. The network can activate / deactivate a BWP using scheduling downlink control information (DCI).

[0042] Frequency hopping (FH) refers to a technique for spreading a radio signal across several frequency channels. Within a component carrier (CC), a transmitter can hop between narrowband frequencies several times per second in a pseudo-random sequence known to the transmitter and receiver. FH can provide benefits such as interference mitigation and increased frequency diversity gain. Since Rel-15, NR support is limited to frequency hopping (FH) or frequency scheduling (FS) operation for DL / UL channels within an active BWP. The network can configure frequency hopping in the BWP configuration.

[0043] According to various exemplary embodiments described herein, an eRedcap UE may be configured for DL / UL operation with frequency hopping enabled to obtain meaningful frequency diversity gain in view of narrow bandwidth (e.g., limited to a maximum of 11 RBs in an active BWP in case of a 5 MHz bandwidth and a 30 kHz SCS). The frequency hopping pattern may be designed to ensure efficient coexistence of eRedcap UEs and other UEs (normal UEs and / or Rel-17 Redcap UEs) by avoiding resource fragmentation and collisions. In addition, the BWP switching framework for frequency hopping may be modified. The existing BWP switching architecture for frequency hopping will result in unacceptable delay and throughput loss for eRedcap UEs as described above.

[0044] Several approaches can be considered to support floating BWP for narrowband (NB) eRedcap UEs to exploit frequency diversity gain over wider CC bandwidth.

[0045] In one aspect of these exemplary embodiments, configuration of frequency hopping operation based on a BWP is described. Hereinafter, a BWP directly configured by RRC signaling (including, for example, time domain and frequency domain resource allocation) may be referred to as a parent BWP (P-BWP), and a BWP created from a P-BWP using frequency hopping may be referred to as a child BWP (C-BWP). A C-BWP may also be referred to as a FHBWP. The time and frequency resources for one or more P-BWPs may be configured by the network, and the UE may determine the location of a C-BWP based on one or more parameters as described below.

[0046] In some exemplary embodiments, C-BWP may be defined based on one or more RB offset values ​​newly introduced for DL ​​or UL BWP configuration. In other exemplary embodiments, C-BWP may be defined by a subband-based approach, where a component carrier (CC) is divided into a set of subbands, and each subband may potentially include a C-BWP therein.

[0047] According to the first exemplary embodiment for configuring BWP-based FH operation described above, the network can configure a P-BWP occupying a specific frequency range (RB range), wherein the C-BWP is defined based on the RB offset. In one option, the RB offset of each C-BWP with a frequency hopping index i is defined relative to the P-BWP with a frequency hopping index i=0. In another option, the RB offset of a C-BWP with a frequency hopping index i is defined relative to a BWP with a frequency hopping index i-1, which can be a P-BWP or a C-BWP.

[0048] Figure 5 A diagram 500 is shown of an exemplary bandwidth part (BWP) based frequency hopping (FH) operation for downlink (DL) or uplink (UL) operation of an eRedcap user equipment (UE) according to various exemplary embodiments. Diagram 500 includes a P-BWP 505 configured by the network and a P-BWP 506 configured using an RB offset value RB 偏移,i 500, which will be described in detail below. Although three C-BWPs 510-520 are shown in diagram 500, those skilled in the art will appreciate that more or fewer frequency hopping may be configured / used in DL / UL operations depending on factors such as the total bandwidth of component carriers (CCs), the bandwidth of each BWP, coexistence with other channels used by other UEs, etc. In addition, the BWPs 505-520 shown in exemplary diagram 500 have an interval of one time slot, however, an interval including a larger number of time slots may be used. These aspects will be described in more detail below.

[0049] According to the first option, the RB offset of the C-BWP with frequency hopping index i is RB 偏移,i It can be defined according to the RB index of the P-BWP with hopping index i=0. In one example, the offset value RB of the C-BWP with hopping index i, i>1 偏移,i It can be determined as follows, where i=0 for P-BWP: RB 偏移,i =(i*Δ),Δ>N P-BWP , where Δ is configured by RRC signaling, and N P-BWP is the number of RBs configured for P-BWP. RB offset of C-BWP i偏移,i It may be defined according to, for example, the minimum or maximum RB index of a P-BWP.One skilled in the art will recognize that the RB offset may be defined relative to any RB index occupied by a P-BWP.

[0050] In the second option, the RB offset of the C-BWP with frequency hopping index i is RB 偏移,i It can be defined relative to the immediately preceding BWP with frequency hopping index i-1. BWPi-1 can be a C-BWP or a P-BWP. In one example, the offset value RB of a C-BWP with frequency hopping index i, i>1 is 偏移,i Can be a single value RB 偏移,i =RB 偏移 , which can be configured by RRC signaling and applied to each C-BWP. In some designs, i=1, i.e., limiting the operation to two hopping frequencies for BWP, or i=0, e.g., no hopping frequencies for BWP. Similar to the first option, the RB of C-BWP i 偏移,i It can be defined according to any RB index of BWPi-1, for example, the minimum or maximum RB index of BWPi-1.

[0051] exist Figure 5 In the exemplary diagram 500 of FIG. 5 , P-BWP 505 has a hopping index i=0, C-BWP 510 has a hopping index i=1, C-BWP 515 has a hopping index i=2, and C-BWP 520 has a hopping index i=3. For the first option described above, the RB offset of the C-BWP is defined relative to the P-BWP. In this example, the RB offset is defined according to the minimum RB index of the P-BWP, such as the RB offset for the C-BWP 510 with hopping index i=1. 偏移,1 521. RB of C-BWP 515 with frequency hopping index i=2 偏移,2 522 and RB of C-BWP 520 with frequency hopping index i=3 偏移,3 523. For the second option described above, the RB offset i of the C-BWP is defined relative to BWPi-1. In this example, the RB offset is defined according to the minimum RB index of the P-BWP, such as the RB offset of the C-BWP 510 with frequency hopping index i=1. 偏移,1 524. RB of C-BWP 515 with frequency hopping index i=2 偏移,2 525 and RB of C-BWP 520 with frequency hopping index i=3 偏移,3 As shown in 526.

[0052] According to the above-mentioned exemplary implementation of the second type for configuring BWP-based FH operation, the network may configure a P-BWP occupying a first subband having a configurable or determinable size (expressed in units of RBs), wherein the entire bandwidth of a component carrier (CC) is divided into a set of subbands. A C-BWP is defined for a specific one of the set of subbands that is different from the P-BWP.

[0053] The number of subbands in the set N 子带 Can be defined as in represents the CC bandwidth configuration in RB units, and represents the number of RBs in each subband. Figure 6 For an example described in further detail, a 20MHz CC with a 30kHz SCS has a CC bandwidth of PRBs; the number of RBs per subband PRBs; and A sub-band.

[0054] There are several ways to determine the size of the subband. In the first option, the value It may be hard-coded according to a specification (e.g., a 3GPP specification). For example, in one design, It can be equal to the maximum supported bandwidth μ of the UE (e.g., Rel-18e RedCap UE) based on the subcarrier spacing. For 30kHz SCS, can be 10 or 11 PRBs, and for 15kHz SCS, It can be 24 or 25 PRBs. In the second option, The value of can be a function of the downlink CC bandwidth Depending on the trade-off between frequency diversity gain (which can be beneficially increased for larger subband sizes and thus larger frequency offsets between frequency hops) and switching gap overhead (which can be beneficially reduced for smaller subband sizes and smaller frequency offsets between frequency hops), The value of may vary across DL CC BW sizes. In a third option, a set of candidate values ​​may be hard-coded in the specification, and one value from the set may be signaled by the network in a system information block (SIB) (eg, SIB1).

[0055] In one aspect, the starting RB may be configured by the network to ensure coexistence with legacy UEs operating at wider bandwidths. The starting PRB of the lowest subband may be configured by the gNB to, for example, avoid conflict with the PUCCH resource region reserved for the initial access procedure of legacy UEs (including, for example, Rel-17 Redcap UEs), as will be described below. Figure 6 As shown in the example.

[0056] Figure 6 A diagram 600 is shown of an exemplary subband-based bandwidth part (BWP)-based frequency hopping (FH) operation for downlink (DL) or uplink (UL) operation of an eRedcap user equipment (UE) according to various exemplary embodiments. Figure 5 Similarly, diagram 600 includes a P-BWP 605 configured by the network and three frequency hopping including C-BWPs (e.g., C-BWP 610, C-BWP 615, and C-BWP 620). In exemplary diagram 600, BWPs 605-620 are defined using a subband-based approach in accordance with the second embodiment discussed above for configuring BWP-based FH operation.

[0057] exist Figure 6 In the example of FIG. 1 , the UE is configured with a 20 MHz CC with a 30 kHz SCS, which corresponds to a CC bandwidth of PRBs, for example, RB 0-50. The UE is also configured with or determines the number of RBs per subband based on the specification. PRBs. Using these parameters, Can be calculated as N 子带 =4 subbands. Therefore, the BWP can be located in any of the four hop frequencies within the first subband 625 (subband 0), the second subband 630 (subband 1), the third subband 635 (subband 2), or the fourth subband 640 (subband 3), where subbands 0-3 are located in frequency in ascending order of RBs. Figure 6 In the example of , the P-BWP 605 is configured in the fourth subband 640 (subband 3) with the highest RB range, where the C-BWPs 610-625 are located in the first, second and third subbands 625-635 (subbands 0-2). In other words, frequency hopping is performed in time in descending order of frequency. However, those skilled in the art will appreciate that frequency hopping can be performed in time in ascending order of frequency, where the P-BWP is configured in the subband with the lowest RB range relative to the other subbands in the set. In some further embodiments, the P-BWP may be configured in a subband with an RB range somewhere in the middle of the set.

[0058] In this example, the CC includes resources for legacy UEs at the edge of the CC bandwidth. RBs 0-2 are reserved for a first PUCCH region 645 for legacy UEs, and RBs 47-50 are reserved for a second PUCCH region 650 for legacy UEs. The network (e.g., gNB) can configure the starting PRB of the lowest subband so that the frequency hopping of the eRedcap UE will not conflict with the PUCCH regions 645, 650 of the legacy UEs. In this example, the starting PRB is configured as RB 3. Thus, subband 0 625 includes RBs 3-13, subband 1 630 includes RBs 14-24, subband 2 635 includes RBs 25-35, and subband 3 640 includes RBs 36-46.

[0059] P-BWP 605 is configured to span 8 RBs (RB 37-44) in subband 3 640. Frequency hopping extends across subbands 0-2 625-635 and each spans 8 RBs. C-BWP 1 610 is configured in RB 26-33 in subband 2 635. C-BWP 2 615 is configured in RB 15-22 in subband 1 630. C-BWP 3 620 is configured in RB 4-11 in subband 0 625. BWPs 605-620 are offset by 11 RBs, corresponding to the length of each subband 625-640, and as described above, each spans 8 RBs. Therefore, there is a region of 3 RBs between two consecutive BWPs with frequency hopping. These areas, such as available resources 655 between C-BWP 2 615 and C-BWP 3 620 (RB 12-14), available resources 660 between C-BWP 1 610 and C-BWP 2 615 (RB 13-15), and available resources 665 between P-BWP 605 and C-BWP 1 610 (RB 34-36), can be used by the network for other purposes, including as PUCCH resources for legacy UEs or for other channels. The lowest RB used for C-BWP 3 620 is RB 4, and the highest RB used for P-BWP 605 is RB 45, so RB 3 and RB 46-47 can also be used by the network for other purposes. The available RBs that are not used for eRedcap frequency hopping can be used by the network to semi-statically allocate PUCCH resources for legacy devices and thus avoid being affected by BWP frequency hopping of eRedcap UEs.

[0060] According to certain aspects of the invention, various options may be considered to determine which BWPs (configured according to the first embodiment) or which subbands (configured according to the second embodiment) in the set of available BWPs / subbands to use for BWP hopping.

[0061] In the first option, BWP hopping is performed in ascending order of C-BWP index or subband index across all RRC configured C-BWPs (first implementation) or subbands (second implementation). For the second implementation (subband-based), the frequency offset in RBs between two hops for a given BWP may be equal to like Figure 6 As shown. From a specification perspective, the first option is simple. However, this significantly increases the gNB scheduler complexity to avoid resource conflicts between narrowband eRedcap UEs with FH and wideband normal UEs in the same serving cell.

[0062] In the second option, a new MAC Control Element (CE) is introduced to activate and deactivate RRC configured C-BWP or subband, for example to avoid BWP overlap with RBs used by legacy UEs. The new MAC CE may have a fixed size of one octet and be identified by a MAC subheader with a dedicated LCID.

[0063] C-BWP or Subband Activation / Deactivation MAC-CE may be defined as follows. Field C i This field can be used to indicate the activation / deactivation status of the i-th C-BWP or subband. This field can be set to 1 to indicate that the corresponding BWP is to be activated, and can be set to 0 to indicate that the corresponding BWP is to be deactivated. Field R is a reserved bit and is set to 0, which can be used for bits not used for C-BWP or subband. i The octet of the field is in the field.

[0064] Figure 7a An exemplary MAC-CE 700 for C-BWP or subband activation / deactivation according to various exemplary embodiments is shown. In this example, three C-BWPs or four subbands are configured via RRC. Therefore, 3 bits of the octet are used for C-BWP or subband activation / deactivation. i Field, used for activation / deactivation, e.g., C1, C2, and C3, and 5 bits of the octet are reserved R. Frequency hopping is performed across all activated C-BWPs or subbands.

[0065] In a third option, the C-BWP (first embodiment) or subband (second embodiment) used for frequency hopping can be indicated by the scheduling DCI. This option can be used to dynamically grant PDSCH / PUSCH. In one variant, for eRedcap UEs, a new bitmap field can be added to the scheduling DCI, where each bit is used to indicate the activation / deactivation status of the corresponding C-BWP or subband. In another variant, a two-step approach can be used. In the first step, a set of C-BWP lists or subband lists is first configured by RRC signaling or hard-coded according to the specification (for example, for transmission / reception in RRC_IDLE mode). The C-BWP list or subband list can include one or more C-BWPs or subbands and is associated with a dedicated list ID. In the second step, the list ID can be provided by a dedicated "frequency hopping indicator" (FHI) field in the scheduling DCI, where the bit width of this field can be determined based on the number of lists for a given signal or channel.

[0066] Figure 7b An exemplary table 710 for a two-bit FHI field description according to various exemplary embodiments is shown. As shown, a code point "00" of the FHI field may indicate list ID 0, a code point "01" of the FHI field may indicate list ID 1, a code point "10" of the FHI field may indicate list ID 2, and a code point "11" of the FHI field may indicate list ID 3. List ID 0 may include all subbands, list ID 1 may include all even subbands, list ID 2 may include all odd subbands, and list ID 3 may include any custom selection of subbands, e.g., subband X, subband Y, subband Z, etc.

[0067] Figure 7c The use of various exemplary embodiments is shown Figure 7b FIG720 is a diagram of C-BWP or subband activation / deactivation of the FHI field of the gNB. In this example, six subbands / BWPs are first determined or configured based on the CC bandwidth. The gNB may indicate the code point "11" of the FHI field in the scheduling DCI to limit the frequency hopping of the eRedcap to the union of subbands X and Y (e.g., subband 1 and subband 4 of the six subbands), so that the legacy UEs can be scheduled in the remaining subbands 0, 2, 3, and 5 without being affected by the eRedcap frequency hopping.

[0068] According to certain aspects of the present disclosure, a BWP frequency hopping interval may be introduced for eRedcap UEs. When FH is enabled for a given BWP, the same RB position of the BWP may be maintained for a certain number N sThe frequency position of the BWP is switched every Ns time slots, referred to herein as the "FH interval", and the frequency position of the BWP is switched every Ns time slots. The FH interval can be increased to enable cross-slot channel estimation. The same precoding can be applied to the scheduled PDSCH or PUSCH associated with the same TCI state or the same QCL assumption.

[0069] In some designs, N s The set of values ​​may be hard-coded in the specification and used for different UEs or for different DL / UL channels for a given UE. s ={1,2,4,8}.

[0070] Figure 8 A diagram 800 illustrates an exemplary BWP-based frequency hopping (FH) operation with FH spacing enabled according to various exemplary embodiments. In this example, the FH spacing N is configured. s =2 and two sub-bands. BWP 805 on sub-band X includes two time slots, and BWP 810 on sub-band Y includes two time slots.

[0071] The gNB is given flexibility to control the spacing for a specific UE based on various network considerations (such as, for example, the speed at which the UE is traveling). For low mobility UEs, a larger spacing (more slots) may improve performance, while for high mobility UEs, a smaller spacing (fewer slots) may be beneficial. FH spacing N s The time slots can be configured in a variety of ways.

[0072] In a first option, a value may be selected by the network and provided in a cell-specific manner to minimize the signaling overhead required to configure this parameter. In some designs, the selected N s The value may be provided in the SIB.

[0073] In addition, for the first option, the network can override the broadcast N for a specific UE. s Value. For example, N s The value may be configured (eg, enabled / disabled) for a UE-specific BWP or some UE-specific channels via dedicated RRC signaling.

[0074] In the second option, FH is spaced N s timeslots can be configured for UE-specific BWPs on a per-BWP basis. For receiving SIB1 transmissions, N s The value can be provided by the scheduling DCI for PDSCH. For example, two reserved bits can be reused to indicate the FH interval N sOne of the four hard-coded values ​​in the time slot is used to receive the SIB transmission of the eRedcap specific SIB. For other messages in the initial access process, such as Msg2 / Msg3 / Msg4, at least two variants can be considered. In one variant, similar to the above, two reserved bits in the scheduling DCI can be used to provide N s In another variation, SIB1 can carry N time slots. s value.

[0075] In the third option, as a unified solution, FH interval N s The value of the number of time slots can be signaled through a field in the scheduling DCI, for example, by reusing a reserved bit in the scheduling DCI or introducing a new field to achieve this function. s =1, the UE may additionally be provided with enabling / disabling intra-slot FH.

[0076] Frequency hopping operation may be explicitly disabled by higher layers for a cell (e.g., SIB1), for a UE or a UE-specific BWP (e.g., UE-specific RRC signaling), or by a dedicated value (e.g., all zeros or all ones) of the corresponding field in the scheduling DCI for a given signal / channel.

[0077] Fig. 9 A method 900 of bandwidth part (BWP) based frequency hopping (FH) operation for downlink (DL) or uplink (UL) operation of an eRedcap user equipment (UE) is shown in accordance with various exemplary embodiments.

[0078] In 905, the UE receives a BWP and frequency hopping configuration from the network. The BWP configuration may include time and frequency parameters for one or more BWPs that may be activated by the network and used for network operation (UL or DL). In all cases, the BWP configuration includes at least the time and frequency resources for the BWP, the subcarrier spacing (SCS), and other parameters known to those skilled in the art. According to the various embodiments discussed above, various additional parameters may be included in the BWP / FH configuration to support frequency hopping operation based on the BWP. These additional parameters allow the UE to determine the time and frequency resources for the C-BWP created by the P-BWP with frequency hopping.

[0079] For example, according to the above Figure 5 In the first exemplary embodiment discussed for configuring a BWP-based FH, the UE may receive an RB offset RB for determining a C-BWP with a frequency hopping index i, i>1. 偏移,i, (in one option (where C-BWP is defined relative to P-BWP) is the parameter Δ, and in the other option (where C-BWPi is defined relative to BWPi-1) is the parameter RB 偏移 ).

[0080] In another example, according to the above Figure 6 In the second exemplary embodiment discussed for configuring BWP-based FH, the UE may receive a signal for determining a subband size. 905). In other embodiments, the UE may determine the parameter, as shown below in step 905. In addition, the UE may receive a configuration for a starting PRB for the lowest subband in a set of subbands to be used across component carriers. The network may select the starting PRB based on scheduling constraints for other (e.g., legacy) UEs, such as a PUCCH region for legacy UEs at the edge of a CC.

[0081] In yet another example, the UE may receive a configuration of a C-BWP list or subband list including one or more C-BWPs or subbands associated with a list ID. Based on the list ID indicated in the scheduling DCI, the UE may activate / deactivate a specific C-BWP / subband for FH operation. The network may choose to activate / deactivate a specific C-BWP / subband based on scheduling constraints for other (e.g., legacy) UEs.

[0082] In yet another example, the UE may receive a signal for a frequency hopping interval N. s In one embodiment, N s The value may be provided in a system information (SI) broadcast (e.g., SIB1). s The value may be provided in dedicated RRC signaling.

[0083] In yet another example, FH operation may be explicitly disabled via SIB1 or UE-specific RRC signaling.

[0084] In 910, the UE receives a scheduling DCI including activation of a specific one of the configured BWPs and, in some embodiments, additional parameters for performing BWP-based frequency hopping.

[0085] For example, in one embodiment, the scheduling DCI may indicate the activation / deactivation status of the corresponding C-BWP or subband. In a variation, a list ID may be indicated in the scheduling DCI, corresponding to one activation / deactivation pattern from a configured list of activation / deactivation patterns.

[0086] In another example, the UE may receive a signal for the hopping interval N.s In one embodiment, N s The values ​​may be provided as two reserved bits in the scheduling DCI or a new field may be introduced in the scheduling DCI.

[0087] In yet another example, FH operation may be explicitly disabled via a scheduling DCI.

[0088] In 915, the UE determines the frequency hopping position (C-BWP) to use based on parameters received from the network and / or hard-coded parameters.

[0089] For example, according to the above Figure 5 In the first exemplary embodiment discussed for configuring BWP-based FH, as an initial step, the UE may determine the PRBs for the configured P-BWP and the offset value RB of the C-BWP with frequency hopping index i relative to the P-BWP or BWP i-1. 偏移,i The RB 偏移,i The UE may determine the RB offset based on the received parameter (parameter Δ in one option and parameter RB in another option) for determining the RB offset. 偏移 ) to determine the RB offset for each of the C-BWPs.

[0090] In another example, according to the above Figure 6 In the second exemplary embodiment discussed for configuring BWP-based FH, as an initial step, the UE may determine a set of subbands based on the bandwidth of the component carrier (CC). The number of subbands in the set N 子带 It can be determined based on the total number of PRBs in the CC bandwidth and the number of PRBs per subband. The subband size can be hard-coded according to the specification (first option), can be a function of the CC bandwidth, and / or can be indicated by the network, for example in SIB1, and selected from a set of hard-coded values. In another example, the UE can determine the starting PRB of the lowest subband based on the network configuration. The frequency offset in the RB between two hop frequencies can be determined to be equal to the subband size.

[0091] In yet another example, the UE may determine which C-BWPs or subbands to use for (activate / deactivate C-BWPs) FH operation. In one option, all BWPs configured by the network are used by default. In another option, the UE may determine whether to activate / deactivate the corresponding C-BWP or subband based on the received MAC-CE. In yet another option, for example, for dynamically granted PDSCH / PUSCH, the scheduling DCI may indicate the activation / deactivation status of the corresponding C-BWP or subband (in one embodiment, based on the configuration of the C-BWP list or subband list and the list ID indicated in the scheduling DCI).

[0092] In yet another example, the UE may determine the interval to be used for FH. A set of interval values ​​may be hard-coded as per the specification and depend on the type of channel activated for P-BWP. An interval value from the set may be indicated in a SIB broadcast, RRC signaling, or scheduling DCI.

[0093] At 920, UL / DL communication is performed according to the determined FH position.

[0094] Those skilled in the art will appreciate that the configuration step described in 905, the activation step described in 910, the determination step described in 915, and the UL / DL communication step described in 920 may be performed in various operation orders. For example, the UE may perform frequency hopping according to a first BWP and FH configuration and parameters indicated in a first one or more scheduling DCIs, after which the UE may receive different BWP and FH configuration parameters before performing frequency hopping for subsequent UL / DL operations (e.g., UL / DL operations on different channels). In another example, the FH parameters of the BWP for receiving SIB1 may be received in the scheduling DCI and changed for subsequent initial access operations (Msg2 / Msg3 / Msg4) using SIB1 or another scheduling DCI.

[0095] As described above, FH operation may be explicitly disabled via SIB1, UE-specific RRC signaling, or scheduling DCI.

[0096] Example

[0097] In a first embodiment, a processor of a user equipment (UE) is configured to perform operations including: receiving a configuration for parameters from a network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; determining the time and frequency resource parameters for the one or more FH BWPs based in part on information included in the configuration from the network, the time and frequency resource parameters for the FH BWPs including at least a first physical resource block (PRB) offset between the first BWP and a first determined FH BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP and a subset of the determined FH BWPs are activated for a first channel; and performing uplink (UL) or downlink (DL) communications on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0098] In a second embodiment, the processor according to the first embodiment, wherein the first PRB offset is defined relative to a minimum or maximum RB index of the first BWP and is configured via radio resource control (RRC) signaling.

[0099] In a third embodiment, the processor according to the second embodiment, wherein the time and frequency resource parameters for the FH BWP include a set of PRB offset values ​​for each of the one or more FH BWPs.

[0100] In a fourth embodiment, the processor according to the first embodiment, wherein the first BWP is configured in a component carrier, wherein the operations further include dividing the component carrier into a plurality of subbands based on a size of the component carrier and a size of the subband expressed in units of PRBs, wherein the first BWP is carried in the first subband, and each of the one or more FH BWPs is carried in a corresponding additional subband.

[0101] In a fifth embodiment, a processor according to the fourth embodiment, wherein the size of the sub-band is a value hard-coded according to the specification.

[0102] In a sixth embodiment, the processor according to the fifth embodiment, wherein the size of the subband is equal to the total bandwidth of the UE in units of PRBs based on a subcarrier spacing (SCS) of the component carrier.

[0103] In a seventh embodiment, the processor according to the sixth embodiment, wherein for 30KHz SCS, the size of the subband is equal to 11 or 10 PRBs, and for 15KHz SCS, the size of the subband is equal to 24 or 25 PRBs.

[0104] In an eighth embodiment, a processor according to the fifth embodiment, wherein the size of the subband is a function of the size of the component carrier or the bandwidth of the component carrier.

[0105] In a ninth embodiment, the processor according to the fourth embodiment, wherein the network configuration further comprises a set of candidate values ​​for the size of the subband, wherein the operations further comprise receiving an indication of a candidate value in the set of candidate values.

[0106] In a tenth embodiment, the processor according to the fourth embodiment, wherein the network configuration further includes a starting PRB of one of the subbands having a lowest RB index.

[0107] In an eleventh embodiment, a processor according to the tenth embodiment, wherein starting PRBs and frequency resource locations of the first BWP and the one or more FHBWPs are selected for coexistence with channels of other UEs located in the same component carrier.

[0108] In a twelfth embodiment, a processor according to the eleventh embodiment, wherein the channel of the other UE includes a physical uplink control channel (PUCCH) resource region reserved for an initial access procedure.

[0109] In a thirteenth embodiment, a user equipment (UE) includes a transceiver and a processor, the transceiver being configured to communicate with a network, the processor being communicatively coupled to the transceiver and configured to perform operations including: receiving a configuration for parameters from the network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; determining the time and frequency resource parameters for the one or more FH BWPs based in part on information included in the configuration from the network, the time and frequency resource parameters for the FH BWPs including at least a first physical resource block (PRB) offset between the first BWP and a first determined FH BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP and a subset of the determined FH BWPs are activated for a first channel; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0110] In a fourteenth embodiment, a processor of a base station is configured to perform operations including: transmitting a network configuration for parameters including time and resource parameters for a first bandwidth part (BWP) and FH parameters for a user equipment (UE) to determine time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; transmitting these time and resource parameters for the one or more FH BWPs based on information included in the network configuration, the time and frequency resource parameters for the FH BWPs including at least a first physical resource block (PRB) offset between the first BWP and a first determined FH BWP; transmitting scheduling downlink control information (DCI) indicating that the first BWP and a subset of the FH BWPs are activated for a first channel; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0111] In a fifteenth embodiment, a processor according to the fourteenth embodiment, wherein the first PRB offset is defined relative to a minimum or maximum RB index of the first BWP and is configured via radio resource control (RRC) signaling.

[0112] In a sixteenth embodiment, the processor according to the fifteenth embodiment, wherein the second PRB offset is determined between a minimum PRB or maximum RB index of the first BWP and a minimum PRB or maximum RB index of a second determined FH BWP.

[0113] In a seventeenth embodiment, the processor according to the fifteenth embodiment, wherein the second PRB offset is determined between the minimum PRB or maximum RB index of the first determined FH BWP and the minimum PRB or maximum RB index of the second determined FH BWP.

[0114] In an eighteenth embodiment, the processor according to the fifteenth embodiment, wherein the time and frequency resource parameters for the FH BWP include a set of PRB offset values ​​for each of the one or more FH BWPs.

[0115] In a nineteenth embodiment, the processor according to the fourteenth embodiment, wherein the first BWP is configured in a component carrier, wherein the operations further include dividing the component carrier into a plurality of subbands based on a size of the component carrier and a size of the subband expressed in units of PRBs, wherein the first BWP is carried in the first subband, and each FHBWP of the one or more FH BWPs is carried in a corresponding additional subband.

[0116] In a twentieth embodiment, a processor according to the nineteenth embodiment, wherein the size of the sub-band is a value hard-coded according to the specification.

[0117] In a twenty-first embodiment, a processor according to the twentieth embodiment, wherein the size of the subband is equal to the total bandwidth of the UE in units of PRBs based on a subcarrier spacing (SCS) of the component carrier.

[0118] In a twenty-second embodiment, a processor according to the twenty-first embodiment, wherein for 30KHz SCS, the size of the subband is equal to 11 or 10 PRBs, and for 15KHz SCS, the size of the subband is equal to 24 or 25 PRBs.

[0119] In a twenty-third embodiment, a processor according to the twentieth embodiment, wherein the size of the subband is a function of the size of the component carrier or the bandwidth of the component carrier.

[0120] In a twenty-fourth embodiment, a processor according to the nineteenth embodiment, wherein the network configuration further comprises a set of candidate values ​​for the size of the subband, wherein the operation further comprises transmitting an indication of a candidate value in the set of candidate values.

[0121] In a twenty-fifth embodiment, a processor according to the twenty-fourth embodiment, wherein the indication of a candidate value in the set of candidate values ​​is transmitted in a system information block 1 (SIB1).

[0122] In a twenty-sixth embodiment, a processor according to the nineteenth embodiment, wherein the network configuration further comprises a starting PRB of one of the subbands having a lowest RB index.

[0123] In a twenty-seventh embodiment, a processor according to the twenty-sixth embodiment, wherein the starting PRBs and frequency resource locations of the first BWP and the one or more FH BWPs are selected for coexistence with channels of other UEs located in the same component carrier.

[0124] In a twenty-eighth embodiment, a processor according to the twenty-seventh embodiment, wherein the channels of the other UEs include a physical uplink control channel (PUCCH) resource region reserved for an initial access procedure.

[0125] In a twenty-ninth embodiment, a base station includes a transceiver and a processor, the transceiver being configured to communicate with a user equipment (UE), the processor being communicatively coupled to the transceiver and configured to perform operations including: transmitting a network configuration for parameters including time and resource parameters for a first bandwidth part (BWP) and FH parameters for the user equipment (UE) to determine time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; transmitting these time and resource parameters for the one or more FH BWPs based on information included in the network configuration, the time and frequency resource parameters for the FH BWPs including at least a first physical resource block (PRB) offset between the first BWP and a first determined FHBWP; transmitting scheduling downlink control information (DCI) indicating that the first BWP and a subset of the FH BWPs are activated for a first channel; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more FHBWPs.

[0126] In a thirtieth embodiment, a processor of a user equipment (UE) is configured to perform operations including: receiving a configuration for parameters from a network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; receiving an indication that at least one of the one or more FH BWPs is activated; determining time and resource parameters for one or more activated FH BWPs by excluding one or more deactivated FH BWPs based on information included in the configuration from the network and the scheduling DCI; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more activated FH BWPs.

[0127] In a thirty-first embodiment, a processor according to the thirtieth embodiment, wherein the indication is carried in a scheduling DCI.

[0128] In a thirty-second embodiment, a processor according to the thirty-first embodiment, wherein the configuration from the network further includes a set of FH BWPs or subband lists for activation or deactivation, and indicates selection of one entry from the set of FH BWPs or subband lists.

[0129] In a thirty-third embodiment, a processor according to the thirty-second embodiment, wherein the indication is provided by a dedicated frequency hopping indicator (FHI) field in the scheduling DCI.

[0130] In a thirty-fourth embodiment, a processor according to the thirty-third embodiment, wherein the FHI field indicates an index of a FH BWP or subband list mode to be used to activate the one or more FH BWPs for communication with a network.

[0131] In a thirty-fifth embodiment, a processor according to the thirtieth embodiment, wherein the one or more FH BWPs are selected for activation to coexist with channels of other UEs located in the same component carrier.

[0132] In a thirty-sixth embodiment, a user equipment (UE) includes a transceiver and a processor, the transceiver being configured to communicate with a network, the processor being communicatively coupled to the transceiver and configured to perform operations including: receiving a configuration for parameters from the network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; receiving an indication that at least one of the one or more FH BWPs is activated; determining time and resource parameters for one or more activated FH BWPs by excluding one or more deactivated FH BWPs based on information included in the configuration from the network and the scheduling DCI; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more activated FH BWPs.

[0133] In a thirty-seventh embodiment, a processor of a base station is configured to perform operations including the following: transmitting a configuration for parameters to a user equipment (UE), the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for the user equipment (UE) to determine time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; transmitting scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; transmitting an indication that at least one of the one or more FH BWPs is activated, wherein the UE determines time and resource parameters for one or more activated FH BWPs by excluding one or more deactivated FH BWPs based on information included in the configuration from the network and the scheduling DCI; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more activated FH BWPs.

[0134] In a thirty-eighth embodiment, the processor according to the thirty-seventh embodiment, wherein the indication is carried in a medium access control (MAC) control element (MAC-CE).

[0135] In a thirty-ninth embodiment, a processor according to the thirty-eighth embodiment, wherein the MAC-CE is a fixed size of one octet and is identified by a MAC subheader with a dedicated logical channel identifier (LCID).

[0136] In a 40th embodiment, the processor according to the 39th embodiment, wherein C i This field indicates the activation or deactivation status for the iFHBWP or subband.

[0137] In a forty-first embodiment, a processor according to the thirty-seventh embodiment, wherein the indication is carried in a scheduling DCI.

[0138] In a forty-second embodiment, a processor according to the forty-first embodiment, wherein a new bitmap field is added to the scheduling DCI, wherein each bit is used to indicate an activation or deactivation status for the iFH BWP or subband.

[0139] In a forty-third embodiment, the processor according to the forty-first embodiment, wherein the configuration transmitted to the UE further includes a set of FH BWPs or subband lists for activation or deactivation, and indicates selection of one entry from the set.

[0140] In a forty-fourth embodiment, a processor according to the forty-third embodiment, wherein the indication is provided by a dedicated frequency hopping indicator (FHI) field in the scheduling DCI.

[0141] In a forty-fifth embodiment, a processor according to the forty-fourth embodiment, wherein the FHI field indicates an index of a FH BWP or subband list mode to be used to activate the one or more FH BWPs for communication with the UE.

[0142] In a forty-sixth embodiment, a processor according to the thirty-seventh embodiment, wherein the one or more FH BWPs are selected for activation to coexist with channels of other UEs located in the same component carrier.

[0143] In a forty-seventh embodiment, a base station includes a transceiver and a processor, the transceiver being configured to communicate with a user equipment (UE), the processor being communicatively coupled to the transceiver and configured to perform operations including: transmitting a configuration for parameters to the user equipment (UE), the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for the user equipment (UE) to determine time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; transmitting scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; transmitting an indication that at least one of the one or more FH BWPs is activated, wherein the UE determines time and resource parameters for one or more activated FH BWPs by excluding one or more deactivated FH BWPs based on information included in the configuration from the network and the scheduling DCI; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more activated FH BWPs.

[0144] In a forty-eighth embodiment, a processor of a user equipment (UE) is configured to perform operations including: receiving configuration for parameters from a network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; determining time and frequency resource parameters for the one or more FH BWPs based on information included in the network configuration and the scheduling DCI, the determined time and frequency resource parameters including an FH interval value including the number of time slots in which the same RB position of the BWP is maintained; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0145] In a forty-ninth embodiment, a processor according to the forty-eighth embodiment, wherein the set of interval values ​​is hard-coded per specification, and the interval value is determined based on a channel type activated for the first BWP.

[0146] In a fiftieth embodiment, a processor according to the forty-eighth embodiment, wherein the operations further comprise receiving an indication that the FH BWP is activated via a system information block 1 (SIB1) broadcast, UE-specific radio resource control (RRC) signaling, or a new scheduling DCI.

[0147] In a fifty-first embodiment, a user equipment (UE) includes a transceiver and a processor, the transceiver being configured to communicate with a network, the processor being communicatively coupled to the transceiver and configured to perform operations including: receiving configuration for parameters from the network, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; determining time and frequency resource parameters for the one or more FH BWPs based on information included in the network configuration and the scheduling DCI, the determined time and frequency resource parameters including an FH interval value including a number of time slots in which the same RB position of the BWP is maintained; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0148] In a fifty-second embodiment, a processor of a base station is configured to perform operations including the following: transmitting configuration for parameters to a user equipment (UE), the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for the user equipment (UE) to determine time and frequency resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; transmitting scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; wherein the UE determines the time and frequency resource parameters for the one or more FH BWPs based on information included in the network configuration and the scheduling DCI, the determined time and frequency resource parameters including an FH interval value including the number of time slots in which the same RB position of the BWP is maintained; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0149] In a fifty-third embodiment, a processor according to the fifty-second embodiment, wherein the set of interval values ​​is hard-coded per UE specification, and the interval value is determined based on a channel type activated for the first BWP.

[0150] In a fifty-fourth embodiment, a processor according to the fifty-third embodiment, wherein the set of interval values ​​includes {1, 2, 4, 8}.

[0151] In a fifty-fifth embodiment, a processor according to the fifty-second embodiment, wherein the operations further comprise transmitting the interval value in a system information block (SIB) broadcast.

[0152] In a fifty-sixth embodiment, a processor according to the fifty-fifth embodiment, wherein the operations further comprise transmitting a new interval value in dedicated radio resource control (RRC) signaling to overwrite the interval value received by the UE in the SIB broadcast.

[0153] In a fifty-seventh embodiment, a processor according to the fifty-second embodiment, wherein the interval value is carried in a scheduling DCI.

[0154] In a fifty-eighth embodiment, a processor according to the fifty-seventh embodiment, wherein two reserved bits in the scheduling DCI are used to indicate an interval value from a plurality of hard-coded interval values.

[0155] In a fifty-ninth embodiment, a processor according to the fifty-seventh embodiment, wherein reception of Msg2, Msg3, or Msg4 indicates an interval value of one in a system information block 1 (SIB1) broadcast.

[0156] In a sixtieth embodiment, the processor according to the fifty-second embodiment, wherein the operations further comprise transmitting an indication that the FH BWP is activated via a system information block 1 (SIB1) broadcast, UE-specific radio resource control (RRC) signaling, or a new scheduling DCI.

[0157] In a sixty-first embodiment, a base station includes a transceiver and a processor, the transceiver being configured to communicate with a user equipment (UE), the processor being communicatively coupled to the transceiver and configured to perform operations including: transmitting a configuration for parameters to the UE, the parameters including time and frequency resource parameters for a first bandwidth part (BWP) and FH parameters for the user equipment (UE) to determine time and frequency resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; transmitting scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; wherein the UE determines the time and frequency resource parameters for the one or more FH BWPs based on information included in the network configuration and the scheduling DCI, the determined time and frequency resource parameters including an FH interval value including the number of time slots in which the same RB position of the BWP is maintained; and performing uplink (UL) or downlink (DL) communication on the first channel in the activated first BWP and the determined one or more FH BWPs.

[0158] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0159] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0160] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0161] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A processor of a user equipment (UE), the processor being configured to perform operations including: receiving, from a network, a configuration for parameters including time and frequency resource parameters for a first bandwidth part (BWP) and frequency hopping (FH) parameters for determining time and frequency resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; determining the time and frequency resource parameters for the one or more FH BWPs based in part on information included in the configuration from the network, the time and frequency resource parameters for the FH BWPs comprising at least a first physical resource block (PRB) offset between the first BWP and a first determined FH BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP and the determined subset of FH BWPs are activated for a first channel; as well as An uplink (UL) or downlink (DL) communication is performed on the first channel in the activated first BWP and the determined one or more FH BWPs.

2. The processor of claim 1, wherein the first PRB offset is defined relative to a minimum or maximum RB index of the first BWP and is configured via radio resource control (RRC) signaling. 3 . The processor of claim 2 , wherein a second PRB offset is determined between a minimum PRB or maximum RB index of the first BWP and a minimum PRB or maximum RB index of a second determined FH BWP. 4 . The processor of claim 2 , wherein a second PRB offset is determined between a minimum PRB or maximum RB index of the first determined FH BWP and a minimum PRB or maximum RB index of a second determined FH BWP.

5. The processor of claim 1 , wherein the first BWP is configured in a component carrier, wherein the operations further comprise: The component carrier is divided into a plurality of subbands based on a size of the component carrier and a size of the subband expressed in units of PRBs, wherein the first BWP is carried in a first subband and each FHBWP of the one or more FH BWPs is carried in a corresponding other subband.

6. The processor of claim 1 , wherein the first BWP is configured in a component carrier, wherein the operations further comprise: dividing the component carrier into a plurality of subbands based on a size of the component carrier and a size of the subband expressed in units of PRBs, wherein the first BWP is carried in a first subband and each of the one or more FH BWPs is carried in a corresponding additional subband, wherein the network configuration further comprises a set of candidate values ​​for the size of the subband; An indication of one of the set of candidate values ​​is received, wherein the indication of one of the set of candidate values ​​is received in a system information block 1 (SIB1).

7. The processor of claim 1 , wherein the first BWP is configured in a component carrier, wherein the operations further comprise: The component carrier is divided into a plurality of subbands based on a size of the component carrier and a size of the subband expressed in units of PRBs, wherein the first BWP is carried in the first subband and each of the one or more FH BWPs is carried in a corresponding additional subband, wherein a network configuration further includes a set of candidate values ​​for the size of the subbands, wherein the network configuration further includes a starting PRB of one of the subbands having a lowest RB index.

8. A processor of a user equipment (UE), the processor being configured to perform operations comprising: receiving, from a network, a configuration for parameters including time and frequency resource parameters for a first bandwidth part (BWP) and frequency hopping (FH) parameters for determining time and resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; receiving an indication that at least one of the one or more FH BWPs is activated; determining the time and resource parameters for one or more activated FH BWPs by excluding one or more deactivated FH BWPs based on information included in the configuration from the network and the scheduling DCI; as well as Uplink (UL) or downlink (DL) communication is performed on the first channel in the activated first BWP and the determined one or more activated FH BWPs.

9. The processor of claim 8, wherein the indication is carried in a Medium Access Control (MAC) Control Element (MAC-CE).

10. The processor of claim 9, wherein the MAC-CE is a fixed size of one octet and is identified by a MAC subheader with a dedicated logical channel identifier (LCID).

11. The processor of claim 10, wherein C i The field indicates the activation or deactivation status for the ith FH BWP or subband.

12. The processor of claim 8, wherein the indication is carried in the scheduling DCI.

13. The processor of claim 12, wherein a new bitmap field is added to the scheduling DCI, wherein each bit is used to indicate an activation or deactivation status for an iFH BWP or subband.

14. A processor of a user equipment (UE), the processor being configured to perform operations comprising: receiving, from a network, a configuration for parameters including time and frequency resource parameters for a first bandwidth part (BWP) and frequency hopping (FH) parameters for determining time and frequency resource parameters for one or more frequency hopping (FH) BWPs from the first BWP; receiving scheduling downlink control information (DCI) indicating that the first BWP is activated for a first channel; determining the time and frequency resource parameters for the one or more FH BWPs based on information included in a network configuration and the scheduling DCI, the determined time and frequency resource parameters comprising an FH interval value, the FH interval value comprising a number of time slots in which the same RB position of the BWP is maintained; as well as An uplink (UL) or downlink (DL) communication is performed on the first channel in the activated first BWP and the determined one or more FH BWPs.

15. The processor of claim 14, wherein a set of interval values ​​is hard-coded in a specification and the interval value is determined based on a channel type activated for the first BWP, wherein the set of interval values ​​includes {1, 2, 4, 8}.

16. The processor of claim 14, wherein the operations further comprise: The interval value is received in a system information block (SIB) broadcast.

17. The processor of claim 16, wherein the operations further comprise: A new interval value is received in dedicated radio resource control (RRC) signaling to overwrite the interval value received in the SIB broadcast.

18. The processor of claim 14, wherein the interval value is carried in the scheduling DCI.

19. The processor of claim 18, wherein two reserved bits in the scheduling DCI are used to indicate an interval value from a plurality of hard-coded interval values.

20. The processor of claim 18, wherein for Msg2, Msg3, or Msg4 reception, an interval value of one is indicated in a system information block 1 (SIB1) broadcast.