CN117835404A

CN117835404A - Communication method, user equipment and base station

Info

Publication number: CN117835404A
Application number: CN202211415695.0A
Authority: CN
Inventors: 吴敏; 孙霏菲
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2022-09-28
Filing date: 2022-11-11
Publication date: 2024-04-05

Abstract

The embodiment of the application provides a communication method, user equipment and a base station, and relates to the technical field of wireless communication. The method comprises the following steps: receiving information about a frequency domain position of a first sub-band within the bandwidth part BWP; receiving frequency domain resource allocation information of a data channel in a first sub-band; and determining the frequency domain resource position of the data channel based on the related information of the frequency domain position of the first sub-band and the frequency domain resource allocation information of the data channel. The scheme can not only enable the bandwidth of the data channel not to exceed the baseband processing bandwidth of the UE, but also dynamically allocate the sub-bands for the data channel in the bandwidth range of BWP, namely, the data channel can be dynamically scheduled in a larger bandwidth range, and the selective hierarchical gain is obtained.

Description

Communication method, user equipment and base station

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a communication method, a user equipment, and a base station.

Background

In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi 5G communication systems. Therefore, a 5G or quasi 5G communication system is also referred to as a "super 4G network" or a "LTE-after-system".

The 5G communication system is implemented in a higher frequency (millimeter wave) band, for example, a 60GHz band, to achieve a higher data rate. In order to reduce propagation loss of radio waves and increase transmission distance, techniques of beamforming, massive Multiple Input Multiple Output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, massive antennas, and the like are discussed in 5G communication systems.

Further, in the 5G communication system, development of system network improvement is being performed based on advanced small cells, cloud Radio Access Networks (RANs), ultra dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), receiving-end interference cancellation, and the like.

In 5G systems, hybrid FSK and QAM modulation (FQAM) and Sliding Window Superposition Coding (SWSC) as Advanced Code Modulation (ACM), and Filter Bank Multicarrier (FBMC), non-orthogonal multiple access (NOMA) and Sparse Code Multiple Access (SCMA) as advanced access technologies have been developed.

In the NR system of Rel-17, a RedCap (Reduced Capability ) UE is proposed, where the RedCap UE technology meets requirements of specific application scenarios, by reducing terminal air interface capability, complexity is reduced, and requirements of reducing cost, power consumption, and the like are met. The Redcap UE is mainly aimed at the internet of things scene, because the internet of things scene has requirements for complexity and cost reduction, size reduction, lower energy consumption and the like of the terminal. In general, the RedCap UE has the following features: the complexity of the terminal is reduced, and compared with the high-end eMBB and URLLC terminals, the complexity and the cost are lower; the size of the equipment is small, and the compact design requirement is met; may be deployed in the 5G full band, including supporting TDD and FDD modes. The transmission bandwidth of the RedCap UE is limited to 20MHz bandwidth, in addition, the number of receiving antennas and the number of layers are reduced, and the scheduling bandwidth of the data channels (PDSCH and PUSCH) is further limited to 5 MHz.

Disclosure of Invention

The purpose of the present application is to at least solve one of the above technical drawbacks, and the technical solutions provided in the embodiments of the present application are as follows:

according to an aspect of an embodiment of the present application, there is provided a method performed by a user equipment UE, including:

receiving information about a frequency domain position of a first sub-band within the bandwidth part BWP;

receiving frequency domain resource allocation information of a data channel in a first sub-band;

and determining the frequency domain resource position of the data channel based on the related information of the frequency domain position of the first sub-band and the frequency domain resource allocation information of the data channel.

Optionally, receiving information about a frequency domain position of the first sub-band within the bandwidth part BWP includes at least one of:

receiving Radio Resource Control (RRC) signaling or Media Access Control (MAC) CE signaling, wherein the RRC signaling or the MAC CE signaling comprises frequency domain position indication information of a first sub-band in BWP;

receiving RRC signaling or MAC CE signaling, wherein the RRC signaling or the MAC CE signaling comprises sub-band index indication information of a first sub-band in BWP;

receiving Downlink Control Information (DCI), wherein the DCI comprises sub-band index indication information of a first sub-band in BWP;

wherein the subband index indicating information is used to indicate one subband from among a plurality of subbands.

Optionally, the frequency domain location indication information of the first sub-band in the BWP included in the RRC signaling or the MAC CE signaling is indicated based on a Type 0 resource allocation method or a Type 1 resource allocation method.

Optionally, the plurality of subbands is partitioned for BWP based on a predefined rule, or the plurality of subbands is configured through RRC signaling.

Optionally, pre-configuring the plurality of subbands by RRC signaling includes:

and respectively configuring a plurality of sub-bands based on a Type 0 resource allocation method or a Type 1 resource allocation method through RRC signaling.

Optionally, dividing the BWP into a plurality of subbands based on predefined rules includes at least one of:

dividing BWP in a first dividing mode to obtain a plurality of sub-bands, wherein Physical Resource Blocks (PRBs) in the plurality of sub-bands are continuous;

the BWP is divided into a plurality of sub-bands by a second division manner, and PRBs in the plurality of sub-bands are discrete.

Optionally, dividing the BWP by the first division manner to obtain a plurality of subbands includes at least one of the following:

dividing BWP from the lowest PRB in the frequency domain, wherein the dividing granularity is N PRBs to obtainA sub-band;

the BWP is divided from the lowest PRB in the frequency domain, the division granularity is 1 PRB, and M-N+1 sub-bands are obtained.

Where M is the number of PRBs that the BWP includes, N is the number of PRBs that the sub-band includes N,represents M divided by N and rounded down.

Optionally, dividing BWP from lowest PRB in frequency domain, where the division granularity is N PRBs, to obtainA subband, comprising:

if M is not divided by N, dividing BWP from the lowest PRB in frequency domainDividing granularity into N PRBs to obtainSub-band, then dividing BWP from the PRB with highest frequency domain, dividing granularity into N PRBs, obtaining additional +.>Sub-bands, in total ∈>A sub-band.

Optionally, dividing the BWP into a plurality of subbands by a second division manner includes:

the PRBs in BWP are allocated to different sub-bands one by one from the PRB with the lowest frequency domain to obtainA sub-band;

Optionally, the DCI and its scheduled data channel satisfy a minimum interval in time, wherein the value of the minimum interval is predefined, or determined by the UE capability; and/or

The earliest schedulable resource of DCI is the first time unit after DCI.

Optionally, receiving the frequency domain resource allocation information of the data channel in the first sub-band includes:

And receiving DCI, wherein the DCI comprises frequency domain resource allocation information of a data channel in a first sub-band, and the frequency domain resource allocation information is indicated based on a Type 0 resource allocation method or a Type 1 resource allocation method.

Optionally, indicating the frequency domain resource allocation information by the Type 0 resource allocation method includes:

indicating one or more Resource Block Groups (RBGs) in a first sub-band to be scheduled in a bitmap mode so as to indicate frequency domain resource allocation information;

wherein the size of the RBG in the first subband is determined by at least one of:

determining an RBG size in a first sub-band based on a bandwidth of the BWP;

the RBG size in the first sub-band is determined based on the bandwidth of the first sub-band.

Optionally, the indicating the frequency domain resource allocation information by the Type 1 resource allocation method includes:

indicating frequency domain resource allocation information by indicating a starting Virtual Resource Block (VRB) and a continuously scheduled VRB in a first sub-band, and mapping the VRB corresponding to the frequency domain resource allocation information to a PRB;

wherein the VRB is mapped to the PRB based on the distributed mapping rule if any of the following conditions is satisfied:

UE capability supports distributed mapping rules;

the DCI is in a different time unit than the data channel it schedules.

Optionally, the method further comprises:

If the data channel is configured into a frequency hopping mode, determining a second sub-band after frequency hopping based on the first sub-band;

a data channel for a frequency hopping transmission is received or transmitted based on the first sub-band and the second sub-band.

Optionally, determining the second sub-band after frequency hopping includes at least one of:

determining a subband index of the second subband based on the subband index of the first subband;

configuring a second sub-band of the first sub-band through RRC signaling;

the second subband of the first subband is indicated by DCI.

Optionally, the method further comprises:

monitoring PDCCH for scheduling the physical downlink shared channel PDSCH through a dedicated search space or a radio network temporary identifier RNTI value dedicated to the UE, wherein the dedicated search space is different from a search space used by the legacy system UE for monitoring the PDCCH, or the dedicated RNTI value is different from an RNTI value used by the legacy system UE for monitoring the PDCCH.

Optionally, the dedicated search space comprises at least one of:

a dedicated search space for listening to scheduled paging messages;

a special search space for monitoring scheduling system information;

dedicated search space for listening for scheduled random access responses.

Optionally, the dedicated RNTI value includes at least one of:

A special paging radio network temporary identity P-RNTI value for monitoring a PDCCH scheduling paging message;

a dedicated system information radio network temporary identity SI-RNTI value for listening to the PDCCH scheduling SIB 1.

Optionally, the method further comprises:

the UE is indicated to the base station as a second reduced capability, redCap, UE by initiating a random access procedure on a dedicated physical random access channel, PRACH, resource.

Optionally, the method further comprises:

if the special PRACH resource is configured, initiating a random access process through the special PRACH resource;

if the special PRACH resource is not configured, but the network is configured with the PRACH resource special for the first RedCAP UE, initiating a random access process through the PRACH resource special for the first RedCAP UE;

if the dedicated PRACH resources are not configured and the network also does not configure the PRACH resources dedicated to the first RedCap UE, initiating a random access procedure through the PRACH resources of the non-RedCap UE.

Optionally, the method further comprises:

the dedicated PRACH resources are configured as part of PRACH resources in the first RedCap UE dedicated PRACH resources, the part of PRACH resources being shared by the second RedCap UE and the first RedCap UE; and/or

The dedicated PRACH resources are configured as part of PRACH resources of the non-RedCap UE, the part of PRACH resources being shared by the second RedCap UE and the non-RedCap UE.

Optionally, the UE is prohibited from accessing the cell corresponding to the base station in any of the following cases:

the base station indicates that the UE is forbidden to access the cell through reserved bits in a Physical Broadcast Channel (PBCH);

the base station indicates that the UE is forbidden to access the cell through reserved bits in DCI for scheduling a system information block SIB1 PDSCH;

PDSCH for carrying SIB1 is allocated a bandwidth exceeding a first preset bandwidth value;

PDSCH for carrying RAR is allocated a bandwidth exceeding a first preset bandwidth value.

Optionally, when receiving the broadcast PDSCH transmitted by the base station exceeding the second preset bandwidth value, the method further includes at least one of the following:

receiving a second preset number of PRBs of the lowest frequency domain in the broadcast PDSCH;

reception of the broadcast PDSCH is achieved based on the UE.

Optionally, the method further comprises:

reporting at least one of the following information to a base station:

whether the UE can simultaneously receive the unicast PDSCH and the PBCH or not, wherein the unicast PDSCH and the PBCH are partially overlapped or fully overlapped on time resources or in a time unit, and the total bandwidth of the bandwidth where the unicast PDSCH is positioned and the bandwidth where the PBCH is positioned does not exceed a third preset bandwidth value or exceeds the third preset bandwidth value;

whether the UE can simultaneously receive the unicast PDSCH and the broadcast PDSCH or not, wherein the unicast PDSCH and the broadcast PDSCH are partially overlapped or completely overlapped on time resources or in a time unit, and the total bandwidth of the bandwidth where the unicast PDSCH is positioned and the bandwidth where the broadcast PDSCH is positioned does not exceed a third preset bandwidth value or exceeds a third preset bandwidth value;

And whether the UE can simultaneously receive at least two unicast PDSCH, wherein the at least two unicast PDSCH are not overlapped on time resources and are in a time unit, and the total bandwidth of the bandwidths of the at least two unicast PDSCH is not more than a third preset bandwidth value or is more than the third preset bandwidth value.

Optionally, the method further comprises:

if the UE cannot receive the unicast PDSCH and the PBCH at the same time, preferentially receiving the unicast PDSCH or determining to preferentially receive one of the unicast PDSCH and the PBCH based on the type of the unicast PDSCH;

if the UE cannot receive the unicast PDSCH and the broadcast PDSCH at the same time, the unicast PDSCH is preferentially received, or one of the unicast PDSCH and the broadcast PDSCH is preferentially received is determined based on the type of the unicast PDSCH.

Optionally, determining to preferentially receive one of the unicast PDSCH and the PBCH based on the type of the unicast PDSCH includes:

if the unicast PDSCH is based on dynamic scheduling, preferentially receiving the unicast PDSCH;

if the unicast PDSCH is a semi-persistent scheduling PDSCH, the PBCH is preferentially received, or one of the unicast PDSCH and the PBCH is determined to be preferentially received based on the UE implementation.

Optionally, determining to preferentially receive one of the unicast PDSCH and the broadcast PDSCH based on the type of the unicast PDSCH includes:

if the unicast PDSCH is a semi-persistent scheduling PDSCH, the broadcast PDSCH is preferentially received, or one of the unicast PDSCH and the broadcast PDSCH is determined to be preferentially received based on the UE implementation.

According to another aspect of an embodiment of the present application, there is provided a method performed by a base station, including:

transmitting information about the frequency domain position of the first sub-band within the bandwidth part BWP to the user equipment UE;

transmitting a Physical Downlink Control Channel (PDCCH) to the UE, wherein the PDCCH comprises frequency domain resource allocation information of a data channel in a first sub-band;

and transmitting the PDCCH scheduled data channel to the UE, wherein the frequency domain resource position of the data channel is determined based on the related information of the frequency domain position of the first sub-band and the frequency domain resource allocation information of the data channel.

Optionally, the sending of the information about the frequency domain position of the first sub-band within the bandwidth part BWP to the user equipment UE comprises at least one of the following:

transmitting Radio Resource Control (RRC) signaling or Media Access Control (MAC) CE signaling containing frequency domain location indication information of a first sub-band in BWP to the UE;

transmitting RRC signaling or MAC CE signaling to the UE, wherein the RRC signaling or the MAC CE signaling comprises sub-band index indication information of a first sub-band in the BWP;

Transmitting Downlink Control Information (DCI) to the UE, wherein the DCI comprises sub-band index indication information of a first sub-band in BWP;

if M is not divided by N, dividing BWP from the lowest PRB in frequency domain, and obtaining N PRBsSub-band, then dividing BWP from the PRB with highest frequency domain, dividing granularity into N PRBs, obtaining additional +.>Sub-bands, in total ∈>A sub-band.

The earliest schedulable resource of DCI is the first time unit after DCI.

Optionally, a physical downlink control channel PDCCH is sent to the UE, the PDCCH including frequency domain resource allocation information of a data channel in a first subband, including:

and sending DCI to the UE, wherein the DCI comprises frequency domain resource allocation information of a data channel in a first sub-band, and the frequency domain resource allocation information is indicated based on a Type 0 resource allocation method or a Type 1 resource allocation method.

determining an RBG size in a first sub-band based on a bandwidth of the BWP;

UE capability supports distributed mapping rules;

the DCI is in a different time unit than the data channel it schedules.

Optionally, the method further comprises:

and transmitting PDCCH for scheduling the broadcast physical downlink shared channel PDSCH to the UE through a special search space or a UE special radio network temporary identifier RNTI value, wherein the special search space is different from a search space used by the legacy system UE for monitoring the PDCCH, or the special RNTI value is different from an RNTI value used by the legacy system UE for monitoring the PDCCH.

Optionally, the dedicated search space comprises at least one of:

a dedicated search space for listening to scheduled paging messages;

a special search space for monitoring scheduling system information;

dedicated search space for listening for scheduled random access responses.

Optionally, the dedicated RNTI value includes at least one of:

Optionally, the method further comprises:

And receiving a random access process initiated by the UE on a special physical random access channel PRACH resource, and determining that the UE is a second reduced capability RedCAP UE.

Optionally, the method further comprises:

if the special PRACH resource is configured, receiving a random access process initiated by the UE on the special PRACH resource;

if the dedicated PRACH resource is not configured, but the network is configured with the PRACH resource dedicated to the first RedCAP UE, receiving a random access process initiated by the UE on the PRACH resource dedicated to the first RedCAP UE;

if the dedicated PRACH resources are not configured and the network also does not configure the PRACH resources dedicated to the first RedCap UE, then receiving a UE-initiated random access procedure on the PRACH resources of the non-RedCap UE.

Optionally, the method further comprises:

the receiving UE reports at least one of the following information:

According to still another aspect of the embodiments of the present application, there is provided a user equipment UE, including:

a transceiver; and

a processor coupled to the transceiver and configured to control to perform the steps of the methods provided herein that are performed by the UE.

According to a further aspect of embodiments of the present application, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method provided by the present application for execution by a UE.

According to still another aspect of the present application, there is provided a base station, including:

a transceiver; and

a processor coupled to the transceiver and configured to control to perform the steps of the methods provided herein that are performed by the base station.

According to a further aspect of embodiments of the present application, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the steps of the method provided by the present application for execution by a UE.

According to the scheme, the sub-bands used for the data channels are configured, so that the bandwidth of the data channels does not exceed the baseband processing bandwidth of the UE, the sub-bands used for the data channels can be dynamically allocated within the bandwidth range of BWP, namely, the data channels can be dynamically scheduled within a larger bandwidth range, and the selective hierarchical gain is obtained.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that are required to be used in the description of the embodiments of the present application will be briefly described below.

Fig. 1 is an example wireless network of various embodiments provided by embodiments of the present application;

FIGS. 2a and 2b are exemplary wireless transmit and receive paths provided by embodiments of the present application;

fig. 3a is an example UE provided by an embodiment of the present application;

FIG. 3b is an example gNB provided by an embodiment of the present application;

fig. 4 is a flowchart of a method performed by a UE according to an embodiment of the present application;

fig. 5 is a division manner of BWP in an example of the embodiment of the present application;

fig. 6 is a block diagram illustrating another BWP partitioning method in an example of the embodiment of the present application;

fig. 7 is a division manner of another BWP in an example of the embodiment of the present application;

fig. 8 is a division manner of another BWP in an example of the embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The following description with reference to the accompanying drawings is provided to facilitate a thorough understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The description includes various specific details to facilitate understanding but should be considered exemplary only. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and phrases used in the following specification and claims are not limited to their dictionary meanings, but are used only by the inventors to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more such surfaces.

The terms "comprises" or "comprising" may refer to the presence of a corresponding disclosed function, operation or component that may be used in various embodiments of the present disclosure, rather than to the presence of one or more additional functions, operations or features. Furthermore, the terms "comprises" or "comprising" may be interpreted as referring to certain features, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be interpreted as excluding the existence of one or more other features, numbers, steps, operations, constituent elements, components, or combinations thereof.

The term "or" as used in the various embodiments of the present disclosure includes any listed term and all combinations thereof. For example, "a or B" may include a, may include B, or both a and B.

Unless defined differently, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by one of ordinary skill in the art to which this disclosure pertains. The general terms as defined in the dictionary are to be construed to have meanings consistent with the context in the relevant technical field, and should not be interpreted in an idealized or overly formal manner unless expressly so defined in the present disclosure.

Fig. 1 illustrates an example wireless network 100 in accordance with various embodiments of the present disclosure. The embodiment of the wireless network 100 shown in fig. 1 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of this disclosure.

The wireless network 100 includes a gndeb (gNB) 101, a gNB102, and a gNB103.gNB 101 communicates with gNB102 and gNB103. The gNB 101 is also in communication with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data network.

Other well-known terms, such as "base station" or "access point", can be used instead of "gnob" or "gNB", depending on the network type. For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to the network infrastructure components that provide wireless access for remote terminals. Also, other well-known terms, such as "mobile station", "subscriber station", "remote terminal", "wireless terminal" or "user equipment", can be used instead of "user equipment" or "UE", depending on the type of network. For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses the gNB, whether the UE is a mobile device (such as a mobile phone or smart phone) or a fixed device (such as a desktop computer or vending machine) as is commonly considered.

The gNB 102 provides wireless broadband access to the network 130 for a plurality of first User Equipment (UEs) within the coverage area 120 of the gNB 102. The plurality of first UEs includes: UE 111, which may be located in a Small Business (SB); UE 112, which may be located in enterprise (E); UE 113, may be located in a WiFi Hotspot (HS); UE 114, which may be located in a first home (R); UE115, which may be located in a second home (R); UE 116 may be a mobile device (M) such as a cellular telephone, wireless laptop, wireless PDA, etc. The gNB 103 provides wireless broadband access to the network 130 for a plurality of second UEs within the coverage area 125 of the gNB 103. The plurality of second UEs includes UE115 and UE 116. In some embodiments, one or more of the gNBs 101-103 are capable of communicating with each other and with UEs 111-116 using 5G, long Term Evolution (LTE), LTE-A, wiMAX, or other advanced wireless communication technology.

The dashed lines illustrate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustration and explanation purposes only. It should be clearly understood that coverage areas associated with the gnbs, such as coverage areas 120 and 125, can have other shapes, including irregular shapes, depending on the configuration of the gnbs and the variations in the radio environment associated with natural and man-made obstructions.

As described in more detail below, one or more of gNB101, gNB 102, and gNB 103 includes a 2D antenna array as described in embodiments of the disclosure. In some embodiments, one or more of gNB101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.

Although fig. 1 shows one example of a wireless network 100, various changes can be made to fig. 1. For example, the wireless network 100 can include any number of gnbs and any number of UEs in any suitable arrangement. Also, the gNB101 is capable of communicating directly with any number of UEs and providing those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 is capable of communicating directly with the network 130 and providing direct wireless broadband access to the network 130 to the UE. Furthermore, the gnbs 101, 102, and/or 103 can provide access to other or additional external networks (such as external telephone networks or other types of data networks).

Fig. 2a and 2b illustrate example wireless transmit and receive paths according to this disclosure. In the following description, transmit path 200 can be described as implemented in a gNB (such as gNB 102), while receive path 250 can be described as implemented in a UE (such as UE 116). However, it should be understood that the receive path 250 can be implemented in the gNB and the transmit path 200 can be implemented in the UE. In some embodiments, receive path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the present disclosure.

The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) block 210, an inverse N-point fast fourier transform (IFFT) block 215, a parallel-to-serial (P-to-S) block 220, an add cyclic prefix block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a remove cyclic prefix block 260, a serial-to-parallel (S-to-P) block 265, an N-point Fast Fourier Transform (FFT) block 270, a parallel-to-serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

In transmit path 200, a channel coding and modulation block 205 receives a set of information bits, applies coding, such as Low Density Parity Check (LDPC) coding, and modulates input bits, such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM), to generate a sequence of frequency domain modulation symbols. A serial-to-parallel (S-to-P) block 210 converts (such as demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the number of IFFT/FFT points used in the gNB 102 and UE 116. The N-point IFFT block 215 performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 220 converts (such as multiplexes) the parallel time-domain output symbols from N-point IFFT block 215 to generate a serial time-domain signal. The add cyclic prefix block 225 inserts a cyclic prefix into the time domain signal. Up-converter 230 modulates (such as up-converts) the output of add cyclic prefix block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at baseband before being converted to RF frequency.

The RF signal transmitted from the gNB 102 reaches the UE 116 after passing through the wireless channel, and an operation inverse to that at the gNB 102 is performed at the UE 116. Down-converter 255 down-converts the received signal to baseband frequency and remove cyclic prefix block 260 removes the cyclic prefix to generate a serial time domain baseband signal. Serial-to-parallel block 265 converts the time-domain baseband signal to a parallel time-domain signal. The N-point FFT block 270 performs an FFT algorithm to generate N parallel frequency domain signals. Parallel-to-serial block 275 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulation symbols to recover the original input data stream.

Each of the gnbs 101-103 may implement a transmit path 200 that is similar to transmitting to UEs 111-116 in the downlink and may implement a receive path 250 that is similar to receiving from UEs 111-116 in the uplink. Similarly, each of the UEs 111-116 may implement a transmit path 200 for transmitting to the gNBs 101-103 in the uplink and may implement a receive path 250 for receiving from the gNBs 101-103 in the downlink.

Each of the components in fig. 2a and 2b can be implemented using hardware alone, or using a combination of hardware and software/firmware. As a specific example, at least some of the components in fig. 2a and 2b may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For example, the FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, wherein the value of the point number N may be modified depending on the implementation.

Further, although described as using an FFT and an IFFT, this is illustrative only and should not be construed as limiting the scope of the present disclosure. Other types of transforms can be used, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It should be appreciated that for DFT and IDFT functions, the value of the variable N may be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of the variable N may be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

Although fig. 2a and 2b show examples of wireless transmission and reception paths, various changes may be made to fig. 2a and 2 b. For example, the various components in fig. 2a and 2b can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. Also, fig. 2a and 2b are intended to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communications in a wireless network.

Fig. 3a shows an example UE 116 according to this disclosure. The embodiment of UE 116 shown in fig. 3a is for illustration only, and UEs 111-115 of fig. 1 can have the same or similar configuration. However, the UE has a variety of configurations, and fig. 3a does not limit the scope of the present disclosure to any particular embodiment of the UE.

UE 116 includes an antenna 305, a Radio Frequency (RF) transceiver 310, transmit (TX) processing circuitry 315, a microphone 320, and Receive (RX) processing circuitry 325.UE 116 also includes speaker 330, processor/controller 340, input/output (I/O) Interface (IF) 345, input device(s) 350, display 355, and memory 360. Memory 360 includes an Operating System (OS) 361 and one or more applications 362.

RF transceiver 310 receives an incoming RF signal from antenna 305 that is transmitted by the gNB of wireless network 100. The RF transceiver 310 down-converts the incoming RF signal to generate an Intermediate Frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuit 325, where RX processing circuit 325 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 325 sends the processed baseband signals to a speaker 330 (such as for voice data) or to a processor/controller 340 (such as for web-browsing data) for further processing.

TX processing circuitry 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (such as network data, email, or interactive video game data) from processor/controller 340. TX processing circuitry 315 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 310 receives outgoing processed baseband or IF signals from TX processing circuitry 315 and up-converts the baseband or IF signals to RF signals for transmission via antenna 305.

Processor/controller 340 can include one or more processors or other processing devices and execute OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor/controller 340 may be capable of controlling the reception of forward channel signals and the transmission of reverse channel signals by RF transceiver 310, RX processing circuit 325, and TX processing circuit 315 in accordance with well-known principles. In some embodiments, processor/controller 340 includes at least one microprocessor or microcontroller.

Processor/controller 340 is also capable of executing other processes and programs resident in memory 360, such as operations for channel quality measurement and reporting for systems having 2D antenna arrays as described in embodiments of the present disclosure. Processor/controller 340 is capable of moving data into and out of memory 360 as needed to perform the process. In some embodiments, the processor/controller 340 is configured to execute the application 362 based on the OS 361 or in response to a signal received from the gNB or operator. The processor/controller 340 is also coupled to an I/O interface 345, where the I/O interface 345 provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I/O interface 345 is the communication path between these accessories and processor/controller 340.

The processor/controller 340 is also coupled to an input device(s) 350 and a display 355. An operator of UE 116 can input data into UE 116 using input device(s) 350. Display 355 may be a liquid crystal display or other display capable of presenting text and/or at least limited graphics (such as from a website). Memory 360 is coupled to processor/controller 340. A portion of memory 360 can include Random Access Memory (RAM) and another portion of memory 360 can include flash memory or other Read Only Memory (ROM).

Although fig. 3a shows one example of UE 116, various changes can be made to fig. 3 a. For example, the various components in FIG. 3a can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. As a particular example, the processor/controller 340 can be divided into multiple processors, such as one or more Central Processing Units (CPUs) and one or more Graphics Processing Units (GPUs). Moreover, although fig. 3a shows the UE 116 configured as a mobile phone or smart phone, the UE can be configured to operate as other types of mobile or stationary devices.

Fig. 3b shows an example gNB 102 in accordance with the present disclosure. The embodiment of the gNB 102 shown in fig. 3b is for illustration only, and other gnbs of fig. 1 can have the same or similar configuration. However, the gNB has a variety of configurations, and fig. 3b does not limit the scope of the disclosure to any particular embodiment of the gNB. Note that gNB 101 and gNB 103 can include the same or similar structures as gNB 102.

As shown in fig. 3b, the gNB102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, transmit (TX) processing circuitry 374, and Receive (RX) processing circuitry 376. In certain embodiments, one or more of the plurality of antennas 370a-370n comprises a 2D antenna array. The gNB102 also includes a controller/processor 378, a memory 380, and a backhaul or network interface 382.

The RF transceivers 372a-372n receive incoming RF signals, such as signals transmitted by UEs or other gnbs, from antennas 370a-370 n. The RF transceivers 372a-372n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signal is sent to RX processing circuit 376, where RX processing circuit 376 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 376 sends the processed baseband signals to a controller/processor 378 for further processing.

TX processing circuitry 374 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller/processor 378. TX processing circuitry 374 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceivers 372a-372n receive the outgoing processed baseband or IF signals from the TX processing circuitry 374 and up-convert the baseband or IF signals to RF signals for transmission via the antennas 370a-370 n.

The controller/processor 378 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, controller/processor 378 may be capable of controlling the reception of forward channel signals and the transmission of backward channel signals via RF transceivers 372a-372n, RX processing circuit 376, and TX processing circuit 374 in accordance with well-known principles. The controller/processor 378 is also capable of supporting additional functions, such as higher-level wireless communication functions. For example, the controller/processor 378 can perform a Blind Interference Sensing (BIS) process such as that performed by a BIS algorithm and decode the received signal from which the interference signal is subtracted. Controller/processor 378 may support any of a variety of other functions in gNB 102. In some embodiments, controller/processor 378 includes at least one microprocessor or microcontroller.

Controller/processor 378 is also capable of executing programs and other processes residing in memory 380, such as a basic OS. Controller/processor 378 is also capable of supporting channel quality measurements and reporting for systems having 2D antenna arrays as described in embodiments of the present disclosure. In some embodiments, the controller/processor 378 supports communication between entities such as web RTCs. Controller/processor 378 is capable of moving data into and out of memory 380 as needed to perform the process.

The controller/processor 378 is also coupled to a backhaul or network interface 382. The backhaul or network interface 382 allows the gNB 102 to communicate with other devices or systems through a backhaul connection or through a network. The backhaul or network interface 382 can support communication through any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as one supporting 5G or new radio access technologies or NR, LTE, or LTE-a), the backhaul or network interface 382 can allow the gNB 102 to communicate with other gnbs over wired or wireless backhaul connections. When the gNB 102 is implemented as an access point, the backhaul or network interface 382 can allow the gNB 102 to communicate with a larger network (such as the internet) through a wired or wireless local area network or through a wired or wireless connection. The backhaul or network interface 382 includes any suitable structure, such as an ethernet or RF transceiver, that supports communication over a wired or wireless connection.

A memory 380 is coupled to the controller/processor 378. A portion of memory 380 can include RAM and another portion of memory 380 can include flash memory or other ROM. In some embodiments, a plurality of instructions, such as BIS algorithms, are stored in memory. The plurality of instructions are configured to cause the controller/processor 378 to perform a BIS process and decode the received signal after subtracting the at least one interfering signal determined by the BIS algorithm.

As described in more detail below, the transmit and receive paths of the gNB 102 (implemented using the RF transceivers 372a-372n, TX processing circuitry 374, and/or RX processing circuitry 376) support aggregated communications with FDD and TDD cells.

Although fig. 3b shows one example of the gNB 102, various changes may be made to fig. 3 b. For example, the gNB 102 can include any number of each of the components shown in FIG. 3 a. As a particular example, the access point can include a number of backhaul or network interfaces 382, and the controller/processor 378 can support routing functions to route data between different network addresses. As another particular example, while shown as including a single instance of TX processing circuitry 374 and a single instance of RX processing circuitry 376, the gNB 102 can include multiple instances of each (such as one for each RF transceiver).

The present application is directed to a Redcap UE, which is enhanced from several aspects, such as frequency domain resource allocation of PDSCH/PUSCH, reception of broadcast PDSCH, random access, and UE capability of simultaneously receiving multiple channels, respectively, which will be described in detail below.

It should be noted that, in the present application, the first Redcap UE may be a Rel-17 Redcap UE (or referred to as Rel-17 version Redcap UE), and the second Redcap UE may be a Rel-18 Redcap UE (or referred to as Rel-18 version Redcap UE), but it is understood that the present application is not limited to this.

In addition, subbands may also be referred to herein as narrowband, scheduled bandwidth, redCap bandwidth, and the like.

Example 1

In the existing NR (New Radio) system, frequency domain resources of PDSCH (Physical Downlink Shared Channel ) and PUSCH (Physical Uplink Shared Channel, physical uplink shared channel) are allocated based on BWP (Bandwidth Part), UE is configured with at most 4 BWP through RRC signaling, at one time, only one BWP is activated, and frequency domain resources of PDSCH/PUSCH may be dynamically allocated within the Bandwidth of the activated BWP. Whereas for a Rel-18 Redcap UE, the baseband processing bandwidth of the data channel (PDSCH/PUSCH) of the UE is only 5MHz in order to reduce hardware cost. Correspondingly, the number of scheduled physical resource blocks (Physical Resource Block, PRBs) of PDSCH and PUSCH is no more than 25 PRBs at maximum in case of 15kHz subcarrier spacing, and no more than 11 (or 12) PRBs at maximum in case of 30kHz subcarrier spacing, but the radio frequency RF (Radio Frequency) bandwidth of the UE can support up to 20MHz. Thus, to support flexibility of scheduling, BWP may be configured to 20MHz, and scheduling of PDSCH and PUSCH may be limited to sub-bands within 20MHz bandwidth up to 5MHz, which has the advantage of being able to dynamically schedule PDSCH and PUSCH of Rel-18 Redcap UEs within one larger bandwidth (20 MHz) in order to obtain selective diversity gain through dynamic scheduling within a larger bandwidth.

Fig. 4 is a flowchart of a method performed by a UE according to an embodiment of the present application, as shown in fig. 4, where the method may include: step S101, receiving the related information of the frequency domain position of the first sub-band in the bandwidth part BWP; step S102, receiving frequency domain resource allocation information of a data channel in a first sub-band; step S103, the frequency domain resource position of the data channel is determined based on the related information of the frequency domain position of the first sub-band and the frequency domain resource allocation information of the data channel.

Specifically, the UE acquires frequency domain location information of a subband (i.e., a first subband) within a Bandwidth Part (BWP), and jointly determines a frequency domain resource location of a PDSCH/PUSCH based on the frequency domain location information of the subband and frequency domain resource allocation information of a data channel (PDSCH/PUSCH). Here, the so-called PDSCH/PUSCH frequency domain resource allocation information is indicated on a subband basis, in other words, the PDSCH/PUSCH frequency domain resource is allocated on a subband basis, i.e., the maximum Bandwidth of the PDSCH/PUSCH does not exceed the Bandwidth of the subband, and the frequency domain location of the subband is indicated on a Bandwidth Part (BWP) basis, i.e., the Bandwidth of the subband is only a portion of the BWP Bandwidth.

In an alternative embodiment of the present application, the receiving the information about the frequency domain position of the first sub-band within the bandwidth part BWP comprises at least one of the following:

Further, the frequency domain location indication information of the first sub-band in the BWP included in the RRC signaling or the MAC CE signaling is indicated based on the Type 0 resource allocation method or the Type 1 resource allocation method.

Further, the plurality of subbands are partitioned for BWP based on a predefined rule, or the plurality of subbands are configured through RRC signaling.

Wherein the pre-configuring the plurality of sub-bands through the RRC signaling includes: and respectively configuring a plurality of sub-bands based on a Type 0 resource allocation method or a Type 1 resource allocation method through RRC signaling.

Wherein, the data channel comprises a PDSCH and a PUSCH.

Specifically, in an alternative, the frequency domain position of the subband within the BWP is configured semi-statically, for example, indicated by RRC (Radio Resource Control, radio resource Control protocol) signaling or MAC (Medium Access Control, media access Control) CE (Control Element) signaling, and the frequency domain position of the subband within the BWP may be configured by reusing the existing method of PDSCH/PUSCH resource allocation Type0 or Type 1. The method has the advantages that the UE can know the frequency domain position of the sub-band in advance before receiving the PDCCH (Physical Downlink Control Channel ), so that the signals of the corresponding frequency band can be cached in advance without waiting for the decoding result of the PDCCH, thereby supporting scheduling in time units (or time slots) (the PDCCH and the PDSCH scheduled by the PDCCH are in the same time unit (or time slot)), and reducing the scheduling delay. It should be noted that, in the embodiments of the present application, the time unit may be one time slot, and a description of a scheme will be made by using the time slot.

In another alternative, the frequency domain position of the sub-band within the BWP is dynamically indicated, for example, by downlink control information (Downlink Control Information, DCI), the frequency domain position information of the sub-band within the BWP may be indicated within scheduling DCI of PDSCH/PUSCH, the scheduling DCI contains a dedicated field for indicating the frequency domain position of the sub-band within the BWP, or the frequency domain position information of the sub-band within the BWP and the resource allocation of PDSCH/PUSCH within the sub-band are jointly indicated by one DCI field. Here, the DCI may indicate one of a plurality of subbands, and the frequency-domain positions of the plurality of subbands within the BWP may be predefined or preconfigured, for example, the BWP is divided into a plurality of subbands by a predefined rule, or the frequency-domain positions of the plurality of subbands within the BWP are indicated by RRC signaling, for example, using a method of allocating Type0 or Type 1 of resources of the existing PDSCH/PUSCH. The method has the advantages that the frequency domain position of the sub-band can be dynamically adjusted, and the selective fading gain of the wireless channel is obtained, namely, the base station can always schedule the UE in the frequency band with better channel condition according to the actual state of the wireless channel.

It should be noted that the DCI and its scheduled data channel satisfy a minimum interval in time, where the value of the minimum interval is predefined or determined by the UE capability; and/or the earliest schedulable resource of the DCI is the first time unit after the DCI.

In the method for dynamically indicating the frequency domain position of the sub-band in the BWP through DCI, the intra-slot scheduling is not supported, namely the DCI and the PDSCH scheduled by the DCI cannot be in the same time slot, in other words, the earliest PDSCH resource which can be scheduled by the DCI is the first time slot after the DCI, because in the inter-slot scheduling, the UE has enough time to decode the PDCCH before receiving the PDSCH, so the base band data signal of the PDSCH can be cached based on the PDSCH frequency domain position information obtained by the PDCCH decoding, and in the intra-slot scheduling, the UE does not have enough time to decode the PDCCH before receiving the PDSCH, so the frequency domain resource position information of the PDSCH cannot be known, the frequency domain position information of the 5MHz sub-band cannot be known, and only the base band data signal of the whole 20MHz BWP can be cached, but the baseband capability of the Rel-18 RedCAP UE cannot be supported; alternatively, the DCI and the PDSCH scheduled by the DCI should satisfy a minimum interval in time, that is, the PDSCH scheduled by the DCI should be at a position after the DCI that satisfies the minimum interval, where the purpose of satisfying the minimum interval is to reserve enough PDCCH decoding time for the UE, so that the UE caches the baseband data signal of the PDSCH based on the PDSCH frequency domain position information obtained by PDCCH decoding, where the value of the minimum interval may be predefined or determined by the UE capability, for example, the UE may report to the base station the minimum interval between the DCI that can be supported and the PDSCH scheduled by the UE, and the base station performs corresponding scheduling according to the UE capability.

In a method of semi-statically configuring (e.g., configured through RRC signaling or MAC CE signaling) the frequency domain location of the sub-band within the BWP, intra-slot scheduling and inter-slot scheduling may be simultaneously supported, and in intra-slot scheduling, although the UE does not have enough time to decode the PDCCH before receiving the PDSCH and thus cannot know the frequency domain resource location information of the PDSCH, the UE can know the frequency domain location information of the 5MHz sub-band, and can buffer the baseband data signal of the 5MHz sub-band first, which is supported by the Rel-18RedCap UE baseband capability.

In an alternative embodiment of the present application, the dividing the BWP into the plurality of sub-bands based on predefined rules comprises at least one of:

dividing the BWP in a first division manner to obtain a plurality of sub-bands, wherein Physical Resource Blocks (PRBs) in the plurality of sub-bands are continuous;

dividing the BWP into the plurality of sub-bands by a second division manner, wherein PRBs in the plurality of sub-bands are discrete.

The first division mode may be referred to as a centralized division mode, and the second division mode may be referred to as a distributed division mode.

Specifically, in a method of indicating a frequency domain position of a subband within a BWP through DCI, the BWP may be divided into a plurality of subbands according to a predefined rule, and the scheduling DCI of the PDSCH/PUSCH indicates a certain one of the plurality of subbands. Specifically, BWP may be divided into a plurality of sub-bands using at least one of the following methods:

1. Starting from the frequency domain lowest PRB of BWP, the whole BWP is divided intoSub-bands, numbering of the sub-bands starting from low frequencies, wherein +.>For the number of PRBs contained in BWP, +.>The number of PRBs included for the sub-band. As shown in fig. 5, assuming that the BWP contains 100 PRBs and the sub-band contains 25 PRBs, the BWP may be divided into 4 sub-bands, and the DCI may indicate one of them using 2 bits. Here, there is no overlap between any two sub-bands, i.e. there is no common PRB. Furthermore, when->Can not be->When dividing, due to->Is rounded down, some PRBs may be left on top of BWP without belonging to any sub-band.

2. In order to associate each PRB within a BWP to one subband, whenCan not be->When dividing, two divisions of the legacy low frequency PRB and the high frequency PRB are supported at the same time, the DCI indicates which division is used, or all sub-bands under both divisions are numbered. As shown in fig. 6, assuming that the BWP contains 64 PRBs and the sub-band contains 25 PRBs, the two divisions have a total of 4 sub-bands, and the DCI may indicate one of them using 2 bits. Wherein 14 PRBs are left under both divisions, i.e. the first preset number is 14 at this time.

3. Starting from the frequency-domain lowest PRB of BWP, each PRB may be the starting PRB of one subband, i.e., the subband may slide PRB by PRB within BWP. As shown in fig. 7, assuming that the BWP includes 100 PRBs and the sub-band includes 25 PRBs, the BWP may be divided into 76 sub-bands.

4. The above methods 1, 2, 3 can be regarded as centrally allocated subbands (i.e. PRBs within a subband are contiguous), and in order to support a distributed allocation of subbands within BWP (i.e. PRBs within a subband are discrete), the subbands may be divided as shown in fig. 8, for example, allocated to different scheduled subbands one PRB by one PRB, assuming that a BWP contains 100 PRBs, a subband contains 25 PRBs, a subband #0 contains an index set of {0,4,8,12, …,96} of PRBs, a subband #1 contains an index set of {1,5,9,13, …,97} of PRBs, a subband #2 contains an index set of {2,6,10,14, …,98} of PRBs, and a subband #3 contains an index set of {3,7,11,115, …,99}.

It should be noted that, the subbands in BWP may support both a centralized partition manner (e.g., methods 1, 2, and 3 described above) and a distributed partition manner (e.g., method 4 described above), and in particular, which partition manner is used may be preconfigured.

In the above embodiment, the UE acquires the frequency domain location information of the first sub-band in the BWP, and the UE needs to acquire the frequency domain resource allocation information of the PDSCH/PUSCH in the sub-band by scheduling DCI in addition to the frequency domain location information of the sub-band in the BWP, and the frequency domain resource allocation method of Type 0 and Type 1 may still be used for the frequency domain resource allocation of the PDSCH/PUSCH in the sub-band.

In an optional embodiment of the present application, indicating the frequency domain resource allocation information by a Type 0 resource allocation method includes:

determining an RBG size in a first sub-band based on a bandwidth of the BWP;

Specifically, in the Type 0 resource allocation method, one or more resource block groups (Resource Block Group, RBG) within a subband are indicated to be scheduled by means of a bitmap (bit map). Alternatively, the RBG size (number of PRBs contained in RBGs) within the sub-band is determined according to the bandwidth of the sub-band, i.e., the RBG size within the sub-band may be different from the RBG size within the BWP.

In the existing NR system, the RBG size (number of included PRBs) is related to the BWP size (number of included PRBs), and table 1 shows RBG sizes at different BWP sizes:

BWP size (number of PRBs)	Configuration 1	Configuration 2
			1～36	2	4
37～72	4	8
			73～144	8	16
145～275	16	16

For example, assuming that the BWP contains 100 PRBs and the sub-band contains 25 PRBs, if the RBG size uses configuration 2 in table 1, the RBG size within the BWP is 16 PRBs and the RBG size within the sub-band is 4 PRBs. In addition, the RBG partitioning of the sub-bands should ensure that there is as common edge as possible with RBGs within BWP, e.g., the first RBG of the sub-band is of a size that satisfies The remaining PRBs are then divided according to RBG size, where P is RBG size (i.e., division granularity), and>the number of the starting system Resource Block (Carrier Resource Block, CRB) of the subband, i.e. the RB (Resource Block) number of the starting PRB of the subband within the system bandwidth.

Alternatively, the RBG size in the first sub-band is determined based on the size of RGB in the BWP. The RBG size of the sub-band is determined according to the size of the underlying BWP, i.e., the RBG size within the sub-band is the same as the RBG size within the BWP, and furthermore, the RBG partition within the sub-band should be identical to the RBG partition within the BWP.

In an optional embodiment of the present application, indicating the frequency domain resource allocation information by a Type 1 resource allocation method includes:

UE capability supports distributed mapping rules;

the DCI is in a different time unit than the data channel it schedules.

Specifically, in the Type 1 resource allocation method based on the sub-band, the frequency domain resource allocation is indicated by indicating the number of the starting VRBs (Virtual Resource Block, virtual resource blocks) and the continuously scheduled VRBs in the sub-band, and then the corresponding PRB positions are determined according to the mapping of the VRBs to the PRBs. Wherein, the VRB-to-PRB mapping can support both centralized mapping and distributed mapping, and the VRB-to-PRB mapping manner and mapping rule should be the same as the VRB-to-PRB mapping in BWP.

The mapping manner from VRB to PRB in the Type 1 resource allocation of Rel-18 Redcap UE is related to the following conditions:

1. determining a mapping mode from VRB to PRB based on UE capability, namely whether the distributed mapping from VRB to PRB is supported or not is related to the UE capability, and reporting whether the distributed mapping can be supported or not to a base station by Rel-18 Redcap UE;

2. in simultaneous slot scheduling (PDCCH and its scheduled data channel are in the same time slot), the VRB to PRB centralized mapping is used by default, and in cross-slot scheduling (PDCCH and its scheduled data channel are in different time slots), the VRB to PRB distributed mapping is used by default.

In an alternative embodiment of the present application, the method may further include:

the data channel of a frequency hopping transmission is received or transmitted based on the first sub-band and the second sub-band.

Further, the determining the second sub-band after frequency hopping includes at least one of the following:

configuring the second sub-band of the first sub-band through RRC signaling;

the second subband of the first subband is indicated by the DCI.

Specifically, for Rel-18 Redcap UE, in order to obtain the frequency diversity gain, the frequency hopping within 20MHz may be supported, the interval between the frequency domain position before the frequency hopping and the frequency domain position after the frequency hopping may exceed 5MHz, in the frequency domain resource allocation method based on the subband described above, the frequency hopping may be based on the subband, that is, the UE needs to determine the subband after the frequency hopping and the frequency domain resource of the subband, it is assumed that the subband where the frequency hopping is located before the frequency hopping is referred to as a first subband, the subband where the frequency hopping is located is referred to as a second subband, the frequency domain resource allocation within the first subband and the frequency domain resource allocation within the second subband may be identical, when performing the frequency hopping, the UE only needs to determine the second subband, and the UE may determine the second subband according to any one of the following methods:

1. determining the second sub-band based on predefined rules, e.g. according to the formulaDetermining an Index number of the second subband, wherein Index ₁ Index number of the second subband ₂ Is the index number of the first subband, N is the total number of subbands contained in BWP;

2. determining a second sub-band based on information preconfigured through RRC signaling, namely configuring a corresponding frequency hopping sub-band for each sub-band by the base station, for example, indicating an index number of the second sub-band based on a relative offset of the index number of the first sub-band, or configuring two sub-bands in pairs for frequency hopping;

3. The second subband is determined based on the indication information within the scheduling DCI, i.e. the second subband is indicated by the scheduling DCI.

Optionally, for the R-18Redcap UE, the data channel may reuse the frequency domain resource allocation method of the legacy system (the allocation method in the foregoing embodiment may be a subband-based frequency domain resource allocation method), that is, the frequency domain resource allocation is indicated based on BWP, and since the hardware processing capability of the R-18Redcap UE is weak, only the data signal within 5MHz can be buffered, and the frequency domain resource allocation of the PDSCH should be known before the PDSCH is received, the PDSCH does not support co-slot scheduling (PDCCH and PDSCH scheduled by the PDCCH are in the same slot), and only cross-slot scheduling (PDCCH and PDSCH scheduled by the PDCCH are in different slots).

Optionally, for the R-18Redcap UE, the unicast data channel may reuse the frequency domain resource allocation method of the legacy system, that is, based on the BWP indication frequency domain resource allocation, unlike legacy UE (UE in legacy system), the R-18Redcap UE does not expect to receive a PDCCH indicating that the scheduling bandwidth of the data channel exceeds 5MHz, that is, the scheduling bandwidth of the data channel exceeds 25 PRBs at 15kHz subcarrier interval, and exceeds 11 or 12 PRBs at 30kHz subcarrier interval; alternatively, when the UE receives a PDCCH indicating that the scheduling bandwidth of the data channel exceeds 5MHz, the UE performs any one of the following actions:

1. The UE judges that the received scheduling information is invalid and will not perform any corresponding transmission or reception;

2. the UE receives or transmits a partial data signal within 5MHz of the data channel, i.e. 25 PRBs (corresponding to 15kHz subcarrier spacing) or 11 PRBs (corresponding to 30kHz subcarrier spacing) within the scheduling bandwidth, the position of the 25 PRBs or 11 PRBs may be predefined, e.g. the first 25 PRBs or 11 PRBs from the low frequency PRBs within the scheduling bandwidth, or the position of the 25 PRBs or 11 PRBs is determined by the UE implementation at the same time;

3. whether the received scheduling information is erroneous, e.g., whether it is possible to receive or transmit a partial data signal within 5MHz of a data channel having a scheduling bandwidth exceeding 5MHz is a UE capability, which the UE should determine is invalid if the UE does not have, and which the UE receives or transmits a partial data signal within 5MHz of the data channel if the UE does have.

It should be noted that, for Rel-18 Redcap UE, the frequency domain resource allocation method based on subband and the frequency domain resource allocation method for reusing legacy system described above are both supported, and the specific frequency domain resource allocation method to be used may be determined by the following manner:

1. By RRC signaling configuration, or indicated in the scheduling DCI, the benefit is to provide sufficient flexibility for the base station configuration;

2. for the broadcast data channel, the frequency domain resource allocation method of the legacy system is reused, which has the advantages of better coexistence with the UE of the legacy system, and for the unicast data channel, the frequency domain resource allocation method based on the sub-band is used, which has the advantage of saving the downlink control signaling overhead of the Rel-18 Redcap UE;

3. which frequency domain resource allocation method is used depends on the UE capability, e.g., whether the UE reports to the base station a frequency domain resource allocation method of the legacy system is supported or not, and/or whether the UE reports to the base station a frequency domain resource allocation method based on subbands is supported or not, the base station uses an appropriate frequency domain resource allocation method according to the UE capability;

4. when the time slot scheduling is carried out (PDCCH and a data channel scheduled by the PDCCH are in the same time slot), a frequency domain resource allocation method based on a sub-band is used by default, and when the time slot scheduling is carried out (PDCCH and a data channel scheduled by the PDCCH are in different time slots), the frequency domain resource allocation method of a legacy system is reused by default;

5. aiming at PDSCH, a frequency domain resource allocation method based on sub-bands is used, and the advantage is that the cost of downlink control signaling is saved; and for the PUSCH, the frequency domain resource allocation method of the legacy system is reused, and the advantage is that enough scheduling flexibility is supported.

Example two

Since the scheduling bandwidth of PDSCH of Rel-18 Redcap UE cannot exceed 5MHz, which affects coexistence of Rel-18 Redcap UE and legacy UE, for example, if the base station wants the two UEs to receive the same broadcast PDSCH, the scheduling bandwidth of the broadcast PDSCH should be limited to 5MHz, which affects performance of legacy UE, so the base station may transmit respective broadcast PDSCH to the two UEs, i.e., rel-18 Redcap UE and legacy UE receive respective broadcast PDSCH, respectively, e.g., the two UEs monitor PDCCH for scheduling broadcast PDSCH through respective PDCC search space or RNTI value. Here, the broadcast PDSCH may be PDSCH carrying paging message, PDSCH carrying system information, PDSCH carrying random access response (Random Access Response, RAR) (i.e., msg2 of random access procedure).

In an alternative embodiment of the present application, the method further comprises:

Wherein the dedicated search space comprises at least one of:

a dedicated search space for listening to scheduled paging messages;

a special search space for monitoring scheduling system information;

dedicated search space for listening for scheduled random access responses.

Wherein the dedicated RNTI value includes at least one of:

Specifically, the base station configures a search space of a dedicated broadcast PDSCH for the Rel-18Redcap UE, which is different from a search space of the legacy UE, for example, the base station may configure at least one of the following dedicated search spaces for scheduling broadcast PDSCH for the Rel-18Redcap UE:

1. the base station configures a dedicated search space for listening to paging messages for Rel-18Redcap UEs, i.e. a search space for listening to paging messages different from legacy UEs, for example, a new configuration, different from the existing configuration, the tagsetsetspace, is introduced tagsetspace-R18-Redcap;

2. the base station configures a dedicated search space for monitoring system information for the Rel-18 reaccap UE, i.e. a search space for monitoring system information different from legacy UE, for example, introduces a new configuration of searchspace ib1-R18-Redcap different from the existing configuration of searchspace ib1, and/or introduces a new configuration of searchspace information-R18-Redcap different from the existing configuration of searchspace information.

3. The base station configures a dedicated search space for listening to a random access response for the Rel-18Redcap UE, i.e. a search space for listening to a random access response different from the legacy UE, for example, a new configuration ra-SearchSpace-R18-Redcap different from the existing configuration ra-SearchSpace is introduced.

Alternatively, the Rel-18Redcap UE listens to the PDCCH for scheduling paging messages using a different P-RNTI value than the existing one, e.g. in the current NR system the value of the P-RNTI is fixed to "FFFE" (hexadecimal), whereas the P-RNTI value used by the Rel-18Redcap UE may be specified as "FFFD" or other predefined value.

Alternatively, the Rel-18Redcap UE listens to the PDCCH for scheduling SIB1 using a different SI-RNTI value than the existing one, e.g. in the current NR system the SI-RNTI value is fixed to "FFFF" (hexadecimal), whereas the SI-RNTI value used by the Rel-18Redcap UE may be specified as "FFFD" or other predefined value.

Example III

Since Rel-18RedCap UEs cannot receive PDSCH with more than 5MHz bandwidth and/or cannot transmit PUSCH with more than 5MHz bandwidth, which has an effect on the initial access procedure, if the UE cannot tell the base station that it is a Rel-18RedCap UE in the first step of the random access procedure (Msg 1), the base station may schedule PDSCH with more than 5MHz bandwidth in the second step of the random access procedure (Msg 2) and the fourth step of the random access procedure (Msg 4), and likewise, the base station may schedule PUSCH with more than 5MHz bandwidth in the third step of the random access procedure (Msg 3), the UE cannot receive Msg2 and Msg4, nor can transmit Msg3, so that the Rel-18RedCap UE informs the base station that it is a Rel-18RedCap UE in Msg1, which can successfully access the network. A direct method for the Rel-18RedCAP UE to inform the base station at Msg1 that the Rel-18RedCAP UE is a Rel-18RedCAP UE is to configure dedicated PRACH resources, namely, distinguish the Rel-18RedCAP UE from the Legacy UE by grouping the PRACH resource pool.

The first RedCAP UE may be Rel-18 RedCAP UE, the second RedCAP UE may be Rel-17 RedCAP UE, and the non-RedCAP UE may be Legacy UE.

Further, the method may further include:

Specifically, in the Rel-17 NR system, the base station already supports configuring dedicated PRACH resources for the Rel-17 RedCap UE, and likewise, the base station may also configure dedicated PRACH resources for the Rel-18 RedCap UE, which configuration is optional in order to support flexibility of the network. Because the PRACH resource pools respectively configured for the Rel-17 RedCAP UE and the Rel-18 RedCAP UE affect the PRACH capacity of the non-RedCAP UE and affect the access performance of the non-RedCAP UE, the base station can determine whether to configure the PRACH resource pools respectively for the Rel-17 RedCAP UE and the Rel-18 RedCAP UE according to the actual situation of the network, the Rel-18 RedCAP UE can preferentially use the PRACH resources configured for the Rel-18 RedCAP UE, if the base station does not configure the PRACH resources for the Rel-18 RedCAP UE, the Rel-18 RedCAP UE preferentially uses the PRACH resources configured for the Rel-17 RedCAP UE, and if the base station also does not configure the PRACH resources for the Rel-17 RedCAP UE, the Rel-18 RedCAP UE uses the PRACH resources of the non-RedCAP UE.

Optionally, when the Rel-18RedCAP UE initiates a random access process, if the network has PRACH resources dedicated to the Rel-18RedCAP, the UE selects one resource from the PRACH resources dedicated to the Rel-18RedCAP to initiate the random access process; if the network is not configured with PRACH resources special for Rel-18RedCAP, but is configured with PRACH resources special for Rel-17RedCAP, the UE selects one resource from the PRACH resources special for Rel-17RedCAP to initiate a random access process; if the network does not configure the PRACH resources dedicated to Rel-18RedCAP and also configures the PRACH resources dedicated to Rel-17RedCAP, the UE selects one resource from the PRACH resources of the non-RedCAP UE to initiate a random access process.

Further, the method may further include:

Specifically, to avoid the impact of Rel-18RedCAP UE's dedicated PRACH resources on the PRACH capacity of non-RedCAP UE (or Rel-17RedCAP UE), a portion of the PRACH resources of non-RedCAP UE (or Rel-17RedCAP UE) may be configured to be available to Rel-18RedCAP UE, i.e., to be shared by Rel-18RedCAP UE and non-RedCAPUE (or Rel-17RedCAP UE), while other PRACH resources cannot be used by Rel-18RedCAP UE, which has the benefit of not affecting the PRACH capacity of non-RedCAP UE (or Rel-17RedCAP UE) and affecting the random access performance of non-RedCAP UE (or Rel-17RedCAP UE) on only a portion of the shared PRACH resources. The base station may indicate a portion of ROs in PRACH resources of a non-RedCap UE (or a Rel-17RedCap UE) as being sharable by a Rel-18RedCap UE, e.g., one RO out of every N ROs may be sharable by a Rel-18RedCap UE, where N is configurable.

In an alternative embodiment of the present application, the UE is prohibited from accessing the cell corresponding to the base station in any of the following situations:

Specifically, serving Rel-18 RedCap UEs may affect the random access performance of non-RedCap UEs, and may further complicate the scheduling algorithm at the base station side, so in some cases, the base station may wish to prohibit Rel-18 RedCap UEs from accessing its serving cells. Specifically, rel-18 RedCap UEs may be prohibited from accessing the cell by any of the following methods:

1. one cell explicitly indicates that the Rel-18 RedCap UE is prohibited from accessing the cell through signaling, for example, the base station indicates whether the Rel-18 RedCap UE is prohibited from accessing the cell through reserved bits in the PBCH, or the base station indicates whether the Rel-18 RedCap UE is prohibited from accessing the cell through reserved bits in DCI for scheduling SIB1 PDSCH;

2. Access to the cell is prohibited by some scheduling implicit indication Rel-18 RedCap UE, e.g. if PDSCH for carrying SIB1 is allocated more than 5MHz bandwidth, then implicit indication Rel-18 RedCap UE is prohibited from accessing the cell, if PDSCH for carrying SIB1 is allocated no more than 5MHz bandwidth, then implicit indication Rel-18 RedCap UE is allowed to access the cell; alternatively, if the PDSCH for carrying the RAR is allocated a bandwidth exceeding 5MHz, the implicit indication Rel-18 RedCap UE is prohibited from accessing the cell, and if the PDSCH for carrying the RAR is allocated a bandwidth not exceeding 5MHz, the implicit indication Rel-18 RedCap UE is permitted to access the cell.

Example IV

In an alternative embodiment of the present application, when receiving the broadcast PDSCH transmitted by the base station exceeding the second preset bandwidth value, the method further includes at least one of:

reception of the broadcast PDSCH is achieved based on the UE.

In particular, the Rel-18 Redcap UE may receive a portion of the data signals within 5MHz of the broadcast PDSCH having a scheduling bandwidth exceeding 5MHz (corresponding to the second preset bandwidth value), e.g., if the scheduling bandwidth of the broadcast PDSCH exceeds 5MHz (exceeding 25 PRBs (corresponding to the second preset number of PRBs) in the case of a 15kHz subcarrier spacing, exceeding 11 or 12 PRBs (corresponding to the second preset number of PRBs) in the case of a 30kHz subcarrier spacing), the UE may still receive the broadcast PDSCH, e.g., at 15kHz, the UE may receive PDSCH signals on only the lowest 25 PRBs of the broadcast PDSCH, and discard PDSCH signals on other PRBs, receive the broadcast PDSCH by attempting to decode the truncated PDSCH signals, or which 25 PRBs within the broadcast PDSCH reception bandwidth by the UE may depend on the UE implementation.

Example five

In the current NR system, the UE may receive multiple physical channels simultaneously, for example, the UE may receive a unicast channel and a broadcast channel simultaneously, and the UE may also receive multiple unicast channels simultaneously, where the capability of receiving multiple physical channels simultaneously is difficult for the Rel-18RedCap UE to achieve, because the baseband module of the Rel-18RedCap UE is simplified, for example, the modules of the post-FFT data buffer, the receiving processing module, the LDPC decoding module, the HARQ buffer, etc. are simplified, so that the Rel-18RedCap UE may not receive multiple physical channels simultaneously, and the UE needs to accept or reject when multiple physical channels are allocated to the same symbol or slot. In addition, the baseband module of the Rel-18RedCap UE may correspond to different receiving capabilities after being simplified to different degrees, and then the UE needs to upload the relevant capabilities in order for the base station to provide proper scheduling according to the UE capabilities.

the UE reports at least one of the following information to the base station:

whether the UE can simultaneously receive the unicast PDSCH and the PBCH or not, wherein the unicast PDSCH and the PBCH are partially overlapped or fully overlapped on time resources or in a time slot, and the total bandwidth of the bandwidth where the unicast PDSCH is positioned and the bandwidth where the PBCH is positioned does not exceed a third preset bandwidth value or exceeds the third preset bandwidth value;

Whether the UE can simultaneously receive the unicast PDSCH and the broadcast PDSCH or not, wherein the unicast PDSCH and the broadcast PDSCH are partially overlapped or fully overlapped on time resources or in a time slot, and the total bandwidth of the bandwidth where the unicast PDSCH is positioned and the bandwidth where the broadcast PDSCH is positioned does not exceed a third preset bandwidth value or exceeds the third preset bandwidth value;

and whether the UE can simultaneously receive at least two unicast PDSCH, wherein the at least two unicast PDSCH are not overlapped on time resources and are in one time slot, and the total bandwidth of the bandwidths of the at least two unicast PDSCH is not more than a third preset bandwidth value or is more than the third preset bandwidth value.

Specifically, in order for the base station to provide better scheduling, to avoid multiple physical channels being allocated in the same slot or symbol, the UE needs to report at least one of the following capabilities to the base station:

the UE reports to the base station whether the unicast PDSCH and the PBCH can be received simultaneously, wherein the unicast PDSCH and the PBCH are partially overlapped or fully overlapped on time resources or in a time slot;

the UE reports to the base station whether the unicast PDSCH and the PBCH can be received simultaneously, wherein the unicast PDSCH and the PBCH are partially overlapped or fully overlapped on time resources or in a time slot, and the total bandwidth of the bandwidth where the PDSCH is positioned and the bandwidth where the PBCH is positioned exceeds 5MHz (corresponding to a third preset bandwidth value);

The UE reports to the base station whether the unicast PDSCH and the PBCH can be received simultaneously, wherein the unicast PDSCH and the PBCH are partially overlapped or fully overlapped on time resources or in a time slot, and the total bandwidth of the bandwidth where the PDSCH is positioned and the bandwidth where the PBCH is positioned is not more than 5MHz (corresponding to a third preset bandwidth value);

the UE reports to the base station whether the unicast PDSCH and the broadcast PDSCH can be received simultaneously, wherein the unicast PDSCH and the broadcast PDSCH are partially overlapped or fully overlapped on time resources or in a time slot;

the UE reports to the base station whether the unicast PDSCH and the broadcast PDSCH can be received simultaneously, wherein the unicast PDSCH and the broadcast PDSCH are partially overlapped or fully overlapped on time resources or in a time slot, and the total bandwidth of the unicast PDSCH and the bandwidth of the broadcast PDSCH exceeds 5MHz (corresponding to a third preset bandwidth value);

the UE reports to the base station whether the unicast PDSCH and the broadcast PDSCH can be received simultaneously, wherein the unicast PDSCH and the broadcast PDSCH are partially overlapped or fully overlapped on time resources or in a time slot, and the total bandwidth of the unicast PDSCH and the bandwidth of the broadcast PDSCH is not more than 5MHz (corresponding to a third preset bandwidth value);

The UE reports to the base station whether two or more unicast PDSCHs can be received simultaneously, wherein the two or more unicast PDSCHs are not overlapped on time resources and are in one time slot;

the UE reports to the base station whether two or more unicast PDSCHs can be received simultaneously, wherein the two or more unicast PDSCHs are not overlapped on time resources and are in one time slot, and the total bandwidth of the bandwidths of the two or more unicast PDSCHs exceeds 5MHz (corresponding to a third preset bandwidth value);

the UE reports to the base station whether two or more unicast PDSCH and PBCH can be received simultaneously, where the two or more unicast PDSCH do not overlap in time resources and are in one slot, and the total bandwidth of the bandwidths where the two or more unicast PDSCH are located does not exceed 5MHz (corresponding to the third preset bandwidth value).

In the above description, the total bandwidth exceeds 5MHz, which means that the total bandwidth exceeds 25 PRBs at 15kHz and exceeds 11 or 12 PRBs at 30 kHz; the total bandwidth is not more than 5MHz, which means that the total bandwidth is not more than 25 PRBs at 15kHz and not more than 11 or 12 PRBs at 30 kHz.

Further, determining to preferentially receive one of the unicast PDSCH and the PBCH based on the type of the unicast PDSCH includes:

Further, determining to preferentially receive one of the unicast PDSCH and the broadcast PDSCH based on the type of the unicast PDSCH includes:

Specifically, optionally, the UE does not have the capability to receive both the unicast PDSCH and the PBCH, and if the unicast PDSCH and the PBCH overlap in part or in whole on time resources, or within one slot, the UE preferentially receives the unicast PDSCH.

Optionally, the UE does not have the capability to receive both the unicast PDSCH and the PBCH, if the unicast PDSCH and the PBCH overlap partially, or completely, on time resources, or within one time slot, the UE decides to receive one of them preferentially according to the type of the unicast PDSCH, e.g., if the unicast PDSCH is based on dynamic scheduling, then the UE receives the unicast PDSCH preferentially; if the unicast PDSCH is a Semi-Persistent scheduling (SPS) PDSCH, then the UE preferentially receives the PBCH, or which of the SPS PDSCH and the PBCH the UE receives depends on the UE implementation.

Alternatively, the UE does not have the capability to receive both unicast PDSCH and broadcast PDSCH, and if the unicast PDSCH and broadcast PDSCH overlap in part or in whole on time resources or within one time slot, the UE preferentially receives unicast PDSCH.

Optionally, the UE does not have the capability to receive both the unicast PDSCH and the broadcast PDSCH, and if the unicast PDSCH and the broadcast PDSCH overlap in part or in whole on time resources or within one time slot, the UE decides to receive one of them preferentially according to the type of the unicast PDSCH, for example, if the unicast PDSCH is based on dynamic scheduling, then the UE receives the unicast PDSCH preferentially; if the unicast PDSCH is a Semi-Persistent scheduling (SPS) PDSCH, then the UE preferentially receives the broadcast PDSCH, or which of the SPS PDSCH and the broadcast PDSCH the UE receives depends on the UE implementation.

In an alternative scheme, for a Redcap UE, the maximum signal bandwidth that can be received by radio frequency is 20MHz, the maximum signal bandwidth that can be processed by baseband is 5MHz, the maximum signal bandwidth that can be buffered by Post-FFT (Post-FFT) buffer at the receiving end can be 5MHz or 20MHz, or the maximum signal bandwidth that can be buffered by Post-FFT buffer is 20MHz only applicable to part of OFDM symbols in a slot, while on other OFDM symbols in a slot, the maximum signal bandwidth that can be buffered by Post-FFT buffer is 5MHz. If the maximum signal bandwidth that the Post-FFT buffer of the UE receiving end can buffer is 5MHz UE, then the base station should use cross-slot scheduling to ensure that the UE can complete PDCCH decoding before receiving PDSCH to know the scheduling information of PDSCH, so as to buffer the corresponding band signals, without buffering all 20MHz signals, i.e. the Post-FFT buffer capability of the UE receiving end affects the scheduling of the base station, so that such a Redcap UE needs to report at least one of the following related Post-FFT buffer capabilities to the base station:

the UE indicates to the base station the maximum bandwidth that its Post-FFT buffer can buffer; the standard specification may predefine one or more values for the maximum bandwidth that can be buffered by the Post-FFT buffer, the UE indicating to the base station that its maximum bandwidth that can be buffered by the Post-FFT buffer meets the predefined values, or that its maximum bandwidth that can be buffered by the Post-FFT buffer is one of a plurality of predefined values. For example, the predefined value of the maximum bandwidth that the Post-FFT buffer can buffer may be 5MHz, 10MHz, or 20MHz.

The UE indicates to the base station the size of its Post-FFT buffer;

the standard specification may predefine one or more values for the UE's Post-FFT buffer size, the UE indicating to the base station that its Post-FFT buffer size meets the predefined value, or that its Post-FFT buffer size is one of a plurality of predefined values. For example, for 15kHz, buffering a 20MHz signal of one OFDM symbol is buffering 100 PRBs, i.e. buffering a signal on 1200 Resource Elements (REs), and assuming that the Post-FFT buffer is emptied after one slot at the latest, the Post-FFT buffer needs to be able to buffer 14 (for normal CP) OFDM symbols simultaneously, the corresponding Post-FFT buffer size is 14 x 1200 = 16800 REs, the predefined value of the Post-FFT buffer size may be 16800 REs, 8400 REs, or 4200 REs, or the predefined value of the Post-FFT buffer size may be 1400 PRBs, 700 PRBs, or 350 RRBs.

The UE indicates to the base station the relative size of its Post-FFT buffer;

the standard specification may predefine one or more values for the relative size of the Post-FFT buffer, the UE indicating to the base station that its relative size of the Post-FFT buffer meets the predefined value, or that its relative size of the Post-FFT buffer is one of a plurality of predefined values. For example, with a buffer size for buffering a 20MHz bandwidth as a reference value, the predefined relative size may be 1, 0.5, 0.25, etc., with 0.5 referring to the size of the Post-FFT buffer being half the reference value and 0.25 referring to the size of the Post-FFT buffer being one quarter the reference value.

The UE indicates to the base station the maximum number of OFDM symbols whose Post-FFT buffer can buffer the 20MHz signal in one slot;

the standard specification may predefine one or more values for the maximum number of OFDM symbols that the UE's Post-FFT buffer can buffer a 20MHz signal in one slot, the UE indicating to the base station that its Post-FFT buffer can buffer a 20MHz signal in one slot meets a predefined value, or that its Post-FFT buffer can buffer a 20MHz signal in one slot is one of a plurality of predefined values. For example, the Post-FFT buffer may buffer a predefined value of 14, 7, or 3 OFDM symbols for the maximum number of OFDM symbols of a 20MHz signal within one slot.

In an alternative scheme, for a Redcap UE, the maximum signal bandwidth that can be received by radio frequency is 20MHz, and the maximum signal bandwidth that can be processed by baseband is 5MHz, if the scheduling bandwidth of PDSCH is greater than 5MHz, then the baseband of the UE can process different frequency band signals of PDSCH in time periods, for example, if the scheduling bandwidth of PDSCH is 10MHz, the baseband of the UE can process PDSCH in two time periods, the first time period processes 5MHz signal of PDSCH in low frequency position, the second time period processes 5MHz signal of PDSCH in high frequency position, and compared with the receiving processing method of only processing 5MHz signal of PDSCH, the receiving processing method can greatly improve decoding performance of PDSCH. Since processing signals in different frequency bands according to time periods can prolong the reception processing time of PDSCH, UE cannot receive and process other PDSCH in a period of time after PDSCH, and this baseband reception processing method can affect PDSCH reception capability and thus affect scheduling of base station, so this Redcap UE needs to report at least one of the following about PDSCH reception capability to the base station:

The UE indicates to the base station whether the baseband module at its receiving end has the capability of processing PDSCH signals of different frequency bands in time slots;

here, the PDSCH may be a unicast PDSCH and/or a broadcast PDSCH. Furthermore, the UE may also indicate whether this capability is available for different sized subcarrier spacings, e.g., for 15kHz, 30kHz, 60kHz, and/or 120kHz, respectively. If the UE has the capability, the base station can send the PDSCH with the scheduling bandwidth larger than 5MHz to the UE, when the scheduling bandwidth of the PDSCH is 5-10 MHz, the UE baseband can respectively process different frequency band signals of the PDSCH by using two time periods because the maximum baseband processing bandwidth of the UE is 5MHz, when the scheduling bandwidth of the PDSCH is 10-15 MHz, the UE baseband can respectively process different frequency band signals of the PDSCH by using three time periods, and when the scheduling bandwidth of the PDSCH is 15-20 MHz, the UE baseband can respectively process different frequency band signals of the PDSCH by using four time periods.

The UE indicates to the base station the maximum scheduling bandwidth of PDSCH that it can receive the processing;

here, the PDSCH may be a unicast PDSCH and/or a broadcast PDSCH. The standard specification may predefine one or more values for the maximum bandwidth of the PDSCH that the UE may receive the processing, the UE indicating to the base station that the maximum scheduling bandwidth of the PDSCH that it may receive the processing meets the predefined values, or that the maximum scheduling bandwidth of the PDSCH that it may receive the processing is one of a plurality of predefined values. For example, the predefined value of the maximum scheduling bandwidth of the PDSCH that the UE can receive processing may be 5MHz, 10MHz, or 20MHz. In addition, the UE may also indicate the maximum scheduling bandwidths of the corresponding PDSCH for subcarrier intervals of different sizes, respectively, e.g., the UE indicates the maximum scheduling bandwidths of the corresponding PDSCH for 15kHz, 30kHz, 60kHz, and/or 120kHz, respectively. The PDSCH scheduling bandwidth sent by the base station to the UE should not exceed the capability of reporting by the UE.

The UE indicates to the base station the minimum time interval between two PDSCH of the corresponding different transport block it receives in one slot, or in two consecutive slots;

here, two PDSCH refer to two unicast PDSCH, two broadcast PDSCH, or one unicast PDSCH and one broadcast PDSCH, and the time interval between two PDSCH refers to the relative interval of the end (last) OFDM symbol of the first PDSCH and the start (first) OFDM symbol of the second PDSCH. The unit of the interval may be an OFDM symbol, for example, the minimum interval between two PDSCH may be 2, 3, 4, 7, 10, 14 OFDM symbols. Furthermore, the UE may also indicate a minimum interval between the corresponding two PDSCHs for subcarrier intervals of different sizes, respectively, e.g., the UE indicates a minimum interval between the corresponding two PDSCHs for 15kHz, 30kHz, 60kHz, and/or 120kHz, respectively. The interval between two continuous PDSCH transmitted by the base station to the UE should not exceed the capability of reporting by the UE.

The UE indicates to the base station the maximum number of PDSCH for which it can receive processed corresponding different transport blocks within one slot;

here, the PDSCH may be a unicast PDSCH and/or a broadcast PDSCH. The maximum number of PDSCH may be 1, 2, 4, or 7. Furthermore, the UE may also indicate the maximum number of corresponding PDSCH for subcarrier intervals of different sizes, respectively, e.g., the UE indicates the maximum number of corresponding PDSCH for 15kHz, 30kHz, 60kHz, and/or 120kHz, respectively. The number of PDSCH transmitted by the base station to the UE in one slot should not exceed the capability of reporting by the UE.

The UE indicates to the base station the maximum mapped PRB total for PDSCH that it can receive the processing;

here, the PDSCH may be a unicast PDSCH and/or a broadcast PDSCH, and the total number of mapped PRBs refers to the total number of PRBs mapped by the PDSCH (one or more OFDM symbols) within the duration of the time domain. In addition, the UE may also indicate the maximum mapped PRB total of the corresponding PDSCH for subcarrier intervals of different sizes, respectively, e.g., the UE indicates the maximum mapped PRB total of the corresponding PDSCH for 15kHz, 30kHz, 60kHz, and/or 120kHz, respectively. The maximum total number of mapped PRBs of PDSCH transmitted by the base station to the UE should not exceed the capability of reporting by the UE.

In an alternative, for a Redcap UE, its PDCCH receiving capability may be further relaxed on the basis of existing UE capabilities. For example, the minimum time interval between two PDCCHs received by the UE is represented by (X, Y), where X is the number of OFDM symbols that the PDCCHs last in the time domain, Y is the minimum number of OFDM symbols that the interval between the two PDCCHs refers to the relative interval between the starting OFDM symbols of the two PDCCHs, and further, the value of Y should be greater than or equal to X. In the existing standard specification, the existing value of (X, Y) may be (2, 2), (3, 4), (3, 7), and for the Redcap UE, the value of (X, Y) may be further relaxed to (1, 2), (2, 3), (2, 4), etc.

For a Redcap UE, the maximum signal bandwidth that can be received by radio frequency is 20MHz, and the maximum signal bandwidth that can be processed by baseband is 5MHz, if the scheduling bandwidth of PDSCH is greater than 5MHz, the baseband of the UE can process different frequency band signals of PDSCH in time slots, and the method of processing different frequency band signals in time slots can obviously lengthen the processing time of reception of PDSCH, which can affect some time lines of the existing system, for example, for the elongated processing time of reception of PDSCH, HARQ feedback of PDSCH needs to be delayed and fed back, and if the PDSCH is a PDSCH for scheduling new data transmission, a DRX inactivity timer DRX-incapacity timer started after the scheduling PDCCH corresponding to the pdschhd needs to be started in a delayed manner.

In an alternative, to solve the above problem that the PDSCH reception processing time is significantly elongated, the HARQ feedback of the PDSCH is sent after being delayed by a first Offset on the basis of the existing time line, for example, the UE sends the corresponding HARQ feedback after the PDSCH in the first uplink time slot satisfying the k+offset_1 interval, where k is the existing feedback time delay, the unit of k is a time slot, the value of k may be indicated by the HARQ feedback time indication field in the corresponding scheduling DCI of the PDSCH, or the value of k may be configured by higher layer signaling, the offset_1 is the first Offset, and the unit of the first Offset may be a time slot or an OFDM symbol. In addition, for a PDSCH scheduling new data transmission, the UE starts a drx-incarvitytimer for a first OFDM symbol after a second offset is satisfied after a corresponding scheduling PDCCH of the PDSCH, where the unit of the second offset is an OFDM symbol.

The value of the first offset and/or the value of the second offset may be predefined, preconfigured by the base station through higher layer signaling, or reported by the UE; alternatively, the value of the first offset and/or the value of the second offset is determined by the scheduling bandwidth of the PDSCH, for example, when the scheduling bandwidth of the PDSCH is within 5-10 MHz, the value of the first offset or the value of the second offset is v, when the scheduling bandwidth of the PDSCH is within 10-15 MHz, the value of the first offset or the value of the second offset is 2*v, when the scheduling bandwidth of the PDSCH is within 15-20 MHz, the value of the first offset or the value of the second offset is 3*v, wherein the value of the parameter v may be predefined, preconfigured by the base station through higher layer signaling, or reported by the UE; alternatively, the value of the first offset and/or the value of the second offset may be predefined or preconfigured, respectively, under PDSCH scheduling bandwidths of different sizes.

Furthermore, whether the UE applies the first offset and/or the second offset for the above-described timeline may be determined by at least one of the following conditions:

the UE reports to the base station that it is of a predefined type of Redcap UE, i.e. only the redecap UE of the predefined type applies the first offset and/or the second offset;

The UE applies the first offset and/or the second offset when the scheduling bandwidth of the PDSCH is greater than a preset value, e.g., only when the scheduling bandwidth of the PDSCH is greater than 5MHz or 10 MHz;

the UE applying the first offset and/or the second offset is configured by the base station, i.e. the UE applies the first offset and/or the second offset only after receiving the corresponding configuration signaling; for example, the base station configures the UE to apply the first offset and/or the second offset through RRC signaling, or the base station indicates whether the UE applies the first offset and/or the second offset to the PDSCH within the scheduling DCI of the PDSCH.

In an alternative, for a Redcap UE, the maximum signal bandwidth that can be received by radio frequency is 20MHz, while the maximum signal bandwidth that can be processed by baseband is 5MHz, if the scheduling bandwidth of PDSCH is greater than 5MHz, then the baseband of the UE may process different frequency band signals of PDSCH in time periods, the UE may not expect to receive another PDSCH carrying a different transport block for a period of time after the PDSCH, whether another PDSCH is a unicast PDSCH or a broadcast PDSCH, e.g., the UE may not expect to receive another PDSCH for a Gap period of time after the PDSCH, the value of Gap may be predefined, pre-configured by the base station through higher layer signaling, or reported by the UE, similar to the first offset or second offset previously described, or the value of Gap may be related to the scheduling bandwidth of PDSCH, e.g., the corresponding Gap value may be predefined, pre-configured by the base station through higher layer signaling, or reported by the UE under a different range of PDSCH scheduling bandwidths.

In an alternative, for a Redcap UE, the maximum signal bandwidth that can be received by radio frequency is 20MHz, and the maximum signal bandwidth that can be processed by baseband is 5MHz, if the scheduling bandwidth of PDSCH is greater than 5MHz, then the baseband of the UE may process different frequency band signals of PDSCH in time, and if the UE receives another PDSCH carrying a different transport block in a time period after the PDSCH, the UE may perform at least one of the following actions:

terminating the subsequent processing of the PDSCH, i.e. receiving only part of the band signals for processing the PDSCH, discarding part of the band signals for the PDSCH to free the baseband processing unit for processing the next PDSCH;

continuing to process other frequency band signals of the PDSCH, discarding or deferring processing of the next PDSCH;

the UE decides whether to terminate the subsequent processing of the previous PDSCH according to the priorities of the two PDSCHs, e.g., if the priority of the previous PDSCH is not lower or higher than the priority of the next PDSCH, the UE continues to receive other frequency band signals processing the previous PDSCH, relinquishes or delays processing the next PDSCH, if the priority of the previous PDSCH is not higher or lower than the next PDSCH, the UE terminates the subsequent processing of the previous PDSCH, starts processing the next PDSCH, wherein the priorities of the PDSCHs may be indicated within the corresponding scheduling DCI, and/or specifies that the unicast PDSCH has a higher priority than the broadcast PDSCH, and/or specifies that the dynamically scheduled PDSCH has a higher priority than the semi-statically scheduled PDSCH.

Example six

The embodiment of the application provides a flow diagram of a method executed by a base station, which may include: step S201, transmitting information about the frequency domain position of the first sub-band in the bandwidth part BWP to the user equipment UE; step S202, a physical downlink control channel PDCCH is sent to the UE, wherein the PDCCH comprises frequency domain resource allocation information of a data channel in the first sub-band; step S203, transmitting the data channel scheduled by the PDCCH to the UE, where the frequency domain resource location of the data channel is determined based on the related information of the frequency domain location of the first subband and the frequency domain resource allocation information of the data channel.

Similarly, the methods of the embodiments of the present application correspond to the methods of the embodiments of the UE side, and detailed description of the functions and the beneficial effects thereof may be specifically referred to the description of the corresponding methods shown in the embodiments of the UE side, which is not repeated herein.

Example seven

The embodiment of the application also provides an electronic device, which comprises a memory, a processor and a computer program stored on the memory, wherein the processor can realize the steps of the method provided by any optional embodiment of the application when executing the computer program.

Fig. 9 shows a schematic structural diagram of an electronic device to which the embodiment of the present invention is applied, where, as shown in fig. 9, an electronic device 4000 shown in fig. 9 includes: a processor 4001 and a memory 4003. Wherein the processor 4001 is coupled to the memory 4003, such as via a bus 4002. Optionally, the electronic device 4000 may further comprise a transceiver 4004, the transceiver 4004 may be used for data interaction between the electronic device and other electronic devices, such as transmission of data and/or reception of data, etc. It should be noted that, in practical applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 is not limited to the embodiment of the present application. Alternatively, the electronic device may be a first network node, a second network node or a third network node.

The processor 4001 may be a CPU (Central Processing Unit ), general purpose processor, DSP (Digital Signal Processor, data signal processor), ASIC (Application Specific Integrated Circuit ), FPGA (Field Programmable Gate Array, field programmable gate array) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor 4001 may also be a combination that implements computing functionality, e.g., comprising one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

Bus 4002 may include a path to transfer information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus or an EISA (Extended Industry Standard Architecture ) bus, or the like. The bus 4002 can be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 9, but not only one bus or one type of bus.

Memory 4003 may be, but is not limited to, ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, RAM (Random Access Memory ) or other type of dynamic storage device that can store information and instructions, EEPROM (Electrically Erasable Programmable Read Only Memory ), CD-ROM (Compact Disc Read Only Memory, compact disc Read Only Memory) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store a computer program and that can be Read by a computer.

The memory 4003 is used for storing a computer program that executes an embodiment of the present application, and is controlled to be executed by the processor 4001. The processor 4001 is configured to execute a computer program stored in the memory 4003 to realize the steps shown in the foregoing method embodiment.

Embodiments of the present application provide a computer readable storage medium having a computer program stored thereon, where the computer program, when executed by a processor, may implement the steps and corresponding content of the foregoing method embodiments.

The embodiments of the present application also provide a computer program product, which includes a computer program, where the computer program can implement the steps of the foregoing method embodiments and corresponding content when executed by a processor.

The terms "first," "second," "third," "fourth," "1," "2," and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the present application described herein may be implemented in other sequences than those illustrated or otherwise described.

It should be understood that, although the flowcharts of the embodiments of the present application indicate the respective operation steps by arrows, the order of implementation of these steps is not limited to the order indicated by the arrows. In some implementations of embodiments of the present application, the implementation steps in the flowcharts may be performed in other orders as desired, unless explicitly stated herein. Furthermore, some or all of the steps in the flowcharts may include multiple sub-steps or multiple stages based on the actual implementation scenario. Some or all of these sub-steps or phases may be performed at the same time, or each of these sub-steps or phases may be performed at different times, respectively. In the case of different execution time, the execution sequence of the sub-steps or stages may be flexibly configured according to the requirement, which is not limited in the embodiment of the present application.

The above text and drawings are provided as examples only to assist the reader in understanding the present disclosure. They are not intended, nor should they be construed, to limit the scope of the present disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those skilled in the art from this disclosure that changes may be made in the embodiments and examples shown without departing from the scope of the disclosure, and that other similar implementations based on the technical ideas of the application are also within the scope of the embodiments of the application.

Claims

1. A method performed by a user equipment, UE, comprising:

receiving frequency domain resource allocation information of a data channel in the first sub-band;

2. The method according to claim 1, wherein the receiving information about the frequency domain position of the first sub-band within the bandwidth part BWP comprises at least one of the following:

receiving Radio Resource Control (RRC) signaling or Media Access Control (MAC) CE signaling, wherein the RRC signaling or the MAC CE signaling comprises frequency domain position indication information of a first sub-band in the BWP;

receiving RRC signaling or MAC CE signaling, wherein the RRC signaling or the MAC CE signaling comprises sub-band index indication information of a first sub-band in the BWP;

receiving Downlink Control Information (DCI), wherein the DCI comprises sub-band index indication information of a first sub-band in the BWP;

wherein the subband index indicating information is used for indicating one subband from a plurality of subbands.

3. The method of claim 2, wherein the RRC signaling or the MAC CE signaling includes frequency domain location indication information of the first sub-band within the BWP, which is indicated based on a Type 0 resource allocation method or a Type 1 resource allocation method.

4. The method of claim 2, wherein the plurality of subbands are partitioned based on predefined rules or are configured through RRC signaling.

5. The method of claim 4, wherein pre-configuring the plurality of subbands by RRC signaling comprises:

and respectively configuring the plurality of sub-bands based on a Type 0 resource allocation method or a Type 1 resource allocation method through the RRC signaling.

6. The method of claim 4, wherein dividing the BWP into the plurality of subbands based on predefined rules comprises at least one of:

7. The method of claim 6, wherein the dividing the BWP into the plurality of subbands by a first division method comprises at least one of:

dividing the BWP from the PRB with the lowest frequency domain, wherein the dividing granularity is N PRBs, and obtaining A sub-band;

dividing the BWP from the PRB with the lowest frequency domain, wherein the division granularity is 1 PRB, and M-N+1 sub-bands are obtained;

where M is the number of PRBs that the BWP includes, N is the number of PRBs that the subband includes N,represents M divided by N and rounded down.

8. The method of claim 7, wherein the dividing the BWP is performed starting from the lowest PRB in the frequency domain with a granularity of N PRBs, resulting inA subband, comprising:

if M is not divided by N, dividing the BWP from the PRB with the lowest frequency domain, wherein the dividing granularity is N PRBs to obtainSub-band, then dividing the BWP from the PRB with highest frequency domain, wherein the dividing granularity is N PRBs, and obtaining the additional +.>Sub-bands, in total ∈>A sub-band.

9. The method of claim 6, wherein the dividing the BWP into the plurality of subbands by a second division method comprises:

allocating PRBs in the BWP to different sub-bands one by one from the PRB with the lowest frequency domain to obtainA sub-band;

10. The method of claim 2, wherein the DCI and the data channel it schedules satisfy a minimum interval in time, wherein a value of the minimum interval is predefined or determined by the UE capability; and/or

The earliest schedulable resource of the DCI is the first time unit after the DCI.

11. The method according to claim 1, wherein the method further comprises:

12. The method of claim 11, wherein the determining the second sub-band after frequency hopping comprises at least one of:

configuring the second sub-band of the first sub-band through RRC signaling;

the second subband of the first subband is indicated by DCI.

13. The method according to claim 1, wherein the method further comprises:

and monitoring a PDCCH for scheduling a Physical Downlink Shared Channel (PDSCH) through a special search space or a Radio Network Temporary Identifier (RNTI) value special for the UE, wherein the special search space is different from a search space used for monitoring the PDCCH by the legacy system UE, or the special RNTI value is different from an RNTI value used for monitoring the PDCCH by the legacy system UE.

14. The method according to claim 1, wherein the method further comprises:

and indicating the UE to be the second reduced capability RedCap UE to the base station by initiating a random access procedure on a dedicated physical random access channel PRACH resource.

15. The method as recited in claim 14, further comprising:

if the dedicated PRACH resource is not configured, and the network does not configure the PRACH resource dedicated to the first RedCap UE, initiating a random access procedure through the PRACH resource of the non-RedCap UE.

16. The method according to claim 14, wherein the UE is barred from accessing the cell to which the base station corresponds in any of the following cases:

the base station indicates that the UE is forbidden to access the cell through reserved bits in DCI (downlink control information) for scheduling a system information block SIB1 PDSCH;

17. The method according to claim 1, wherein the method further comprises:

reporting at least one of the following information to a base station:

whether the UE can receive the unicast PDSCH and the PBCH at the same time or not, wherein the unicast PDSCH and the PBCH are partially overlapped or fully overlapped on time resources or in a time unit, and the total bandwidth of the bandwidth where the unicast PDSCH is positioned and the bandwidth where the PBCH is positioned does not exceed a third preset bandwidth value or exceeds the third preset bandwidth value;

whether the UE can simultaneously receive a unicast PDSCH and a broadcast PDSCH or not, wherein the unicast PDSCH and the broadcast PDSCH are partially overlapped or fully overlapped on time resources or in a time unit, and the total bandwidth of the unicast PDSCH and the bandwidth of the broadcast PDSCH is not more than the third preset bandwidth value or is more than the third preset bandwidth value;

and whether the UE can simultaneously receive at least two unicast PDSCH or not, wherein the at least two unicast PDSCH are not overlapped on time resources and are in a time unit, and the total bandwidth of the bandwidths of the at least two unicast PDSCH is not more than the third preset bandwidth value or is more than the third preset bandwidth value.

18. A method performed by a base station, comprising:

transmitting a Physical Downlink Control Channel (PDCCH) to the UE, wherein the PDCCH comprises frequency domain resource allocation information of a data channel in the first sub-band;

and transmitting the data channel scheduled by the PDCCH to the UE, wherein the frequency domain resource position of the data channel is determined based on the related information of the frequency domain position of the first sub-band and the frequency domain resource allocation information of the data channel.

19. A user equipment, UE, comprising:

a transceiver; and

a processor coupled to the transceiver and configured to control to perform the steps of the method of any one of claims 1-27.

20. A base station, comprising:

a transceiver; and

a processor coupled to the transceiver and configured to control to perform the steps of the method of claim 18.