Communication method, user equipment and base station

Abstract

The embodiment of the invention provides a communication method, user equipment and a base station. The method executed by the user equipment comprises: receiving DCI, the DCI comprising scheduling information of a PDSCH or a PUSCH transmitted on at least two BWPs, the scheduling information comprising time domain resource allocation information and frequency domain resource allocation information, and the frequency domain resource allocation information comprising frequency domain resource allocation information on the at least two BWPs; transmission of PDSCH or PUSCH scheduled by DCI is performed on at least two BWPs, making it possible to configure multiple carriers within one serving cell, by aggregating multiple carriers within one serving cell, more flexible, more simplified, and reduced signaling overhead compared to aggregating multiple carriers by aggregating multiple serving cells.

Description

Technical Field

[0001] This application relates to the field of wireless communication technologies. Specifically, this application relates to a communication method, a user equipment (UE), and a base station. Background Art

[0002] 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 pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "ultra 4G networks" or "post-LTE systems".

[0003] The 5G communication system is implemented in a higher frequency (millimeter wave, mmWave) band, such as the 60 GHz band, to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antennas have been discussed in the 5G communication system.

[0004] In addition, in the 5G communication system, developments for improving the system network are underway based on advanced small cells, cloud radio access network (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), receiver interference cancellation, etc.

[0005] In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superimposed coding (SWSC) as advanced coding modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0006] Existing communication systems can only deploy multiple carriers through Carrier Aggregation (CA) or Dual-Connectivity (DC). In CA / DC, each carrier corresponds to a serving cell, and multiple carriers are aggregated by aggregating multiple serving cells. The UE can simultaneously transmit on the carriers of multiple serving cells. However, in this way of deploying multiple carriers, each cell requires its own signaling overhead, resulting in a complex system. Summary of the Invention

[0007] Embodiments of this application aim to improve the flexibility of deploying multiple carriers, so as to achieve purposes such as simplifying the system and saving signaling overhead.

[0008] According to one aspect of the embodiments of the present application, there is provided a method performed by a UE in a communication system, the method including:

[0009] Receiving DCI, where the DCI includes scheduling information of PDSCH or PUSCH transmitted on at least two BWPs, and the scheduling information includes time-domain resource allocation information and frequency-domain resource allocation information, wherein the frequency-domain resource allocation information includes frequency-domain resource allocation information on at least two BWPs;

[0010] On at least two BWPs, performing transmission of PDSCH or PUSCH scheduled by the DCI.

[0011] Optionally, the frequency-domain resources included in at least two BWPs do not overlap.

[0012] Optionally, at least two BWPs are on different carriers respectively.

[0013] Optionally, the carriers where at least two BWPs are located are configured in the same serving cell.

[0014] Optionally, at least two BWPs include a first BWP and at least one second BWP, and at least two BWPs include at least one of the following situations:

[0015] The first BWP and the second BWP share the transmission configuration of PDSCH and / or PUSCH;

[0016] The first BWP and the second BWP share the configuration of the first transmission parameters of PDSCH and / or PUSCH, and the second transmission parameters other than the first transmission parameters are configured for the first BWP and the second BWP respectively;

[0017] Wherein, the first BWP includes at least one of the following:

[0018] The first BWP is a BWP on an anchor carrier;

[0019] The first BWP is a BWP on a carrier with an index number of zero;

[0020] The first BWP is a BWP on a carrier with the smallest index number;

[0021] The first BWP is a BWP on a carrier with the lowest frequency;

[0022] The first BWP is a BWP indicated by higher-layer signaling.

[0023] Optionally, receiving DCI includes at least one of the following:

[0024] Monitoring PDCCH on a first preset BWP among at least two BWPs, where the PDCCH includes scheduling information on at least two BWPs;

[0025] Transmit PUCCH on a second preset BWP among at least two BWPs, where the PUCCH includes uplink control information related to at least two BWPs;

[0026] Wherein, the first preset BWP and / or the second preset BWP is the first BWP, or the first preset BWP and / or the second preset BWP is configured as one of at least two BWPs.

[0027] Optionally, on at least two BWPs, perform the transmission of PDSCH or PUSCH scheduled by DCI, including at least one of the following methods:

[0028] [[ID=!0]]On at least two BWPs, respectively perform the repeated transmission of PDSCH or PUSCH scheduled by DCI;

[0029] On at least two BWPs, respectively perform the segmented transmission of PDSCH or PUSCH scheduled by DCI.

[0030] Optionally, for the case of respectively performing the repeated transmission of PDSCH or PUSCH scheduled by DCI on at least two BWPs, the method further includes:

[0031] Determine the first transport block size TBS of PDSCH or PUSCH transmitted on at least two BWPs based on at least one of the following:

[0032] The average number of resource elements RE determined on at least two BWPs;

[0033] The maximum value among the RE numbers respectively determined on at least two BWPs;

[0034] The minimum value among the RE numbers respectively determined on at least two BWPs;

[0035] The RE number determined on a preset BWP among at least two BWPs;

[0036] The scaling factor corresponding to the first TBS.

[0037] Optionally, for the case of respectively performing the repeated transmission of PDSCH or PUSCH scheduled by DCI on at least two BWPs, the method further includes:

[0038] Determine the redundancy version RV transmitted on at least two BWPs by at least one of the following methods:

[0039] The RVs transmitted on at least two BWPs are the same, and the RV is predefined, configured by higher layer signaling, or indicated by DCI;

[0040] The RVs transmitted on each of at least two BWPs are different, and each RV is predefined, configured separately by higher layer signaling, or indicated separately by DCI;

[0041] The RVs transmitted on each of at least two BWPs are different, and each RV is determined by an RV sequence. Each of the at least two BWPs cyclically corresponds to each RV in the RV sequence in turn;

[0042] The RVs transmitted on each of at least two BWPs are different, and each RV is determined by an RV sequence and a starting RV. Each of the at least two BWPs starts from the starting RV and cyclically corresponds to each RV in the RV sequence in turn;

[0043] Wherein, the RV sequence is predefined or configured by higher layer signaling, and the starting RV is predefined, configured by higher layer signaling, or indicated by DCI.

[0044] Optionally, the RV sequence is {#0, #1, #2, #3} or {#0, #2, #3, #1}.

[0045] Optionally, for the case of performing segmented transmission of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the method further includes:

[0046] Perform the process of mapping the PDSCH or PUSCH scheduled by DCI to physical resources in at least one of the following ways:

[0047] Start from the BWP with the lowest frequency and perform a first mapping in the BWP in the order of frequency domain first and then time domain, and repeat the first mapping in the remaining BWPs;

[0048] Start from the first time unit and perform a second mapping in the time unit in the order of frequency, and repeat the second mapping in the remaining time units;

[0049] Start from the RE with the lowest frequency and perform a third mapping in the order of time, and repeat the third mapping on the remaining REs.

[0050] Optionally, for the case of performing segmented transmission of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the method further includes:

[0051] Determine the second TBS of the PDSCH or PUSCH transmitted on at least two BWPs based on at least one of the following:

[0052] The total number of REs determined on at least two BWPs;

[0053] The scaling factor corresponding to the second TBS.

[0054] Optionally, the time domain resource allocation information of PDSCH or PUSCH transmitted on at least two BWPs included in the DCI includes at least one of the following situations:

[0055] At least two BWPs share the time domain resource allocation information;

[0056] At least two BWPs share the first time domain resource allocation information, and the second time domain resource allocation information other than the first time domain resource allocation information is configured separately for at least two BWPs;

[0057] The time domain resources allocated on each of at least two BWPs are indicated by different domains in the DCI.

[0058] Optionally, the first time domain resource allocation information includes the number of time units allocated on the BWP; and,

[0059] The second time domain resource allocation information includes the position of the time units allocated on the BWP.

[0060] Optionally, the time domain resource allocation information of PDSCH or PUSCH transmitted on at least two BWPs included in the DCI includes:

[0061] The number of time units allocated on at least two BWPs is the same, and the positions of the time units allocated on each of at least two BWPs are staggered from each other.

[0062] Optionally, the positions of the time units allocated on each of at least two BWPs being staggered from each other includes:

[0063] There is the same first preset interval between the positions of the time units of every two adjacent BWPs;

[0064] Wherein, the first preset interval is determined by at least one of the following methods: predefined, reported by the UE, preconfigured by higher layer signaling, indicated by the DCI.

[0065] Optionally, on at least two BWPs, the transmission of PDSCH or PUSCH scheduled by the DCI includes:

[0066] Within the first preset interval, switch from the BWP where the time unit before the first preset interval is located to the BWP where the time unit after the first preset interval is located to continue the transmission of PDSCH or PUSCH scheduled by the DCI.

[0067] Optionally, the frequency domain resource allocation information of at least two BWPs included in the DCI includes at least one of the following situations:

[0068] At least two BWPs share frequency domain resource allocation information;

[0069] At least two BWPs share first frequency domain resource allocation information, and second frequency domain resource allocation information other than the first frequency domain resource allocation information is configured separately for at least two BWPs;

[0070] The frequency domain resources allocated on each of at least two BWPs are indicated by different fields in DCI respectively;

[0071] The frequency domain resources allocated on at least two BWPs are jointly indicated by the same field in DCI;

[0072] The frequency domain resources allocated on a part of at least two BWPs are indicated by DCI, and the frequency domain resources allocated on another part of at least two BWPs are predefined or preconfigured by higher layer signaling.

[0073] Optionally, the frequency domain resources allocated on at least two BWPs are jointly indicated by the same field in DCI, including:

[0074] At least one of the physical resource blocks PRB, virtual resource blocks VRB, and resource block groups RBG on at least two BWPs is numbered uniformly.

[0075] Optionally, the RBG size is determined by at least one of the following methods:

[0076] Each of at least two BWPs divides the RBG based on the same RBG size, and the RBG size is determined according to the bandwidth size of a specific BWP among at least two BWPs, or the RBG size is determined according to the total bandwidth size of at least two BWPs, where the specific BWP is predefined or preconfigured by higher layer signaling;

[0077] Each of at least two BWPs divides the RBG based on different RBG sizes, and the RBG size is determined respectively according to the bandwidth size of each BWP.

[0078] Optionally, the RBG division on each BWP starts from the carrier resource block CRB0 at the lowest frequency point of the reference carrier, where the reference carrier is a predefined carrier in the carrier where each BWP is located.

[0079] Optionally, the mapping method between VRB and PRB includes at least one of the following:

[0080] Within the respective bandwidths of each BWP, VRB and PRB are interleaved and mapped;

[0081] Within the total bandwidth of at least two BWPs, VRB and PRB are interleaved and mapped.

[0082] Optionally, the PDSCH transmitted on at least two BWPs includes a semi-persistent scheduled physical downlink shared channel SPS-PDSCH, and the PUSCH transmitted on at least two BWPs includes a type 1 preconfigured grant physical uplink shared channel CG-PUSCH and a type 2 CG-PUSCH.

[0083] Optionally, for the CG-PUSCH, the corresponding first hybrid automatic repeat request HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs; or,

[0084] the corresponding first HARQ process number is determined based on the first time unit allocated on a preset BWP among at least two BWPs;

[0085] wherein the preset BWP is predefined or preconfigured.

[0086] Optionally, for the SPS-PDSCH, the corresponding second HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs; or,

[0087] the corresponding second HARQ process number is determined based on the first time unit allocated on a preset BWP among at least two BWPs;

[0088] wherein the preset BWP is predefined or preconfigured.

[0089] Optionally, if any one of the at least two BWPs is deactivated, the method further includes at least one of the following:

[0090] Stop the transmission of SPS-PDSCH or CG-PUSCH on at least two BWPs, and perform at least one of clearing the downlink allocation of SPS-PDSCH, clearing the uplink grant of type 2 CG-PUSCH, and aborting the uplink grant of type 1 CG-PUSCH;

[0091] On the non-deactivated BWP among at least two BWPs, perform the transmission of SPS-PDSCH or CG-PUSCH.

[0092] Optionally, on at least two BWPs, perform the transmission of DCI-scheduled PDSCH or PUSCH, including:

[0093] Determine at least one scheduled BWP among at least two BWPs according to the indication of the resource indication field in the DCI;

[0094] On at least one scheduled BWP, perform the transmission of DCI-scheduled PDSCH or PUSCH.

[0095] Optionally, when at least two BWPs satisfy at least one of the following conditions, on the at least two BWPs, perform the transmission of PDSCH or PUSCH scheduled by DCI:

[0096] The frequency-domain interval between two carriers adjacent in the frequency domain in the at least two BWPs does not exceed a first preset bandwidth;

[0097] The bandwidth between the lowest frequency and the highest frequency in the at least two BWPs does not exceed a second preset bandwidth;

[0098] The sum of the bandwidths of the at least two BWPs does not exceed a third preset bandwidth.

[0099] Optionally, the method further includes:

[0100] Monitor the physical downlink control channel PDCCH corresponding to DCI on a specific BWP among the at least two BWPs, where the specific BWP is predefined or preconfigured by higher-layer signaling.

[0101] Optionally, the configurations related to PDSCH or PUSCH transmitted on the at least two BWPs comply with at least one of the following configurations:

[0102] The configurations related to PDSCH or PUSCH on a specific BWP among the at least two BWPs, where the specific BWP is predefined or preconfigured by higher-layer signaling;

[0103] Dedicated configurations related to PDSCH or PUSCH, where the dedicated configurations related to PDSCH or PUSCH are different from the configurations related to PDSCH or PUSCH on each BWP among the at least two BWPs.

[0104] Optionally, the demodulation reference signal DMRS signal sequences transmitted on each BWP are respectively generated based on at least one of the following:

[0105] The index number of the CRB corresponding to the PRB where the DMRS is located, where the index number of the CRB is numbered starting from CRB0 of the carrier where the DMRS is located, or the index number of the CRB is numbered starting from CRB0 of the carrier of the BWP with the lowest frequency among the at least two BWPs;

[0106] The index number of the carrier where the DMRS is located;

[0107] Dedicated parameters corresponding to the BWP where the DMRS is located, and the dedicated parameters are configured based on each BWP respectively.

[0108] Optionally, the specific BWP is predefined and includes at least one of the following:

[0109] The specific BWP is a BWP on an anchor carrier;

[0110] The specific BWP is a BWP on a carrier with an index number of zero;

[0111] The specific BWP is a BWP on a carrier with the smallest index number;

[0112] The specific BWP is a BWP on a carrier with the lowest frequency;

[0113] The specific BWP is a BWP with a bandwidth less than a first preset value;

[0114] The specific BWP is a BWP with a bandwidth greater than a second preset value.

[0115] According to another aspect of the embodiments of the present application, a method executed by a base station in a communication system is provided. The method includes:

[0116] Transmit DCI, where the DCI includes scheduling information of PDSCH or PUSCH transmitted on at least two BWPs. The scheduling information includes time-domain resource allocation information and frequency-domain resource allocation information, and the frequency-domain resource allocation information includes frequency-domain resource allocation information on at least two BWPs;

[0117] On at least two BWPs, perform the transmission of PDSCH or PUSCH scheduled by the DCI.

[0118] Optionally, the frequency-domain resources included in at least two BWPs do not overlap.

[0119] Optionally, at least two BWPs are on different carriers respectively.

[0120] Optionally, the carriers where at least two BWPs are located are configured in the same serving cell.

[0121] Optionally, at least two BWPs include a first BWP and at least one second BWP. At least two BWPs include at least one of the following situations:

[0122] The first BWP and the second BWP share the transmission configuration of PDSCH and / or PUSCH;

[0123] The first BWP and the second BWP share the configuration of the first transmission parameter of PDSCH and / or PUSCH, and the second transmission parameter other than the first transmission parameter is configured for the first BWP and the second BWP respectively;

[0124] Among them, the first BWP includes at least one of the following:

[0125] The first BWP is a BWP on an anchor carrier;

[0126] The first BWP is the BWP on the carrier with the index number zero;

[0127] The first BWP is the BWP on the carrier with the smallest index number;

[0128] The first BWP is the BWP on the carrier with the lowest frequency;

[0129] The first BWP is the BWP indicated by the higher layer signaling.

[0130] Optionally, the transmitted DCI includes at least one of the following:

[0131] Transmit the PDCCH on the first preset BWP among at least two BWPs, and the PDCCH includes scheduling information on at least two BWPs;

[0132] Receive the PUCCH on the second preset BWP among at least two BWPs, and the PUCCH includes uplink control information related to at least two BWPs;

[0133] Wherein, the first preset BWP and / or the second preset BWP is the first BWP, or the first preset BWP and / or the second preset BWP is configured as one of at least two BWPs.

[0134] Optionally, on at least two BWPs, performing the transmission of the PDSCH or PUSCH scheduled by the DCI includes at least one of the following methods:

[0135] On at least two BWPs, respectively perform the repeated transmission of the PDSCH or PUSCH scheduled by the DCI;

[0136] On at least two BWPs, respectively perform the segmented transmission of the PDSCH or PUSCH scheduled by the DCI.

[0137] Optionally, for the case of respectively performing the repeated transmission of the PDSCH or PUSCH scheduled by the DCI on at least two BWPs, the method further includes:

[0138] Determine the first transport block size TBS of the PDSCH or PUSCH transmitted on at least two BWPs based on at least one of the following:

[0139] The average number of resource elements RE determined on at least two BWPs;

[0140] The maximum value among the RE numbers respectively determined on at least two BWPs;

[0141] The minimum value among the RE numbers respectively determined on at least two BWPs;

[0142] The RE number determined on one preset BWP among at least two BWPs;

[0143] Scaling factor corresponding to the first TBS.

[0144] Optionally, for the case of performing repeated transmissions of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the method further includes:

[0145] Determining the redundancy version RV transmitted on at least two BWPs by at least one of the following methods:

[0146] The RVs transmitted on at least two BWPs are the same;

[0147] The RVs transmitted on each of at least two BWPs are different;

[0148] The RVs transmitted on each of at least two BWPs are different, and each RV is determined by the RV sequence, and each of at least two BWPs cyclically corresponds to each RV in the RV sequence in turn;

[0149] The RVs transmitted on each of at least two BWPs are different, and each RV is determined by the RV sequence and the starting RV, and each of at least two BWPs starts from the starting RV and cyclically corresponds to each RV in the RV sequence in turn.

[0150] Optionally, the RV sequence is {#0, #1, #2, #3} or {#0, #2, #3, #1}.

[0151] Optionally, for the case of performing segmented transmissions of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the method further includes:

[0152] Performing the process of mapping PDSCH or PUSCH scheduled by DCI to physical resources by at least one of the following methods:

[0153] Starting from the BWP with the lowest frequency, performing the first mapping in the BWP in the order of frequency domain first and then time domain, and repeating the first mapping in the remaining BWPs;

[0154] Starting from the first time unit, performing the second mapping in the time unit in the order of frequency, and repeating the second mapping in the remaining time units;

[0155] Starting from the RE with the lowest frequency, performing the third mapping in the order of time, and repeating the third mapping on the remaining REs.

[0156] Optionally, for the case of performing segmented transmissions of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the method further includes:

[0157] Determine the second transport block size (TBS) of the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmitted on at least two bandwidth parts (BWPs) based on at least one of the following:

[0158] The total number of resource elements (REs) determined on at least two BWPs;

[0159] The scaling factor corresponding to the second TBS.

[0160] Optionally, the time-domain resource allocation information of the PDSCH or PUSCH transmitted on at least two BWPs included in the downlink control information (DCI) includes at least one of the following cases:

[0161] At least two BWPs share the time-domain resource allocation information;

[0162] At least two BWPs share the first time-domain resource allocation information, and the second time-domain resource allocation information other than the first time-domain resource allocation information is configured separately for at least two BWPs;

[0163] The time-domain resources allocated on each of at least two BWPs are indicated separately by different fields in the DCI.

[0164] Optionally, the first time-domain resource allocation information includes the number of time units allocated on the BWP; and,

[0165] The second time-domain resource allocation information includes the position of the time units allocated on the BWP.

[0166] Optionally, the time-domain resource allocation information of the PDSCH or PUSCH transmitted on at least two BWPs included in the DCI includes:

[0167] The number of time units allocated on at least two BWPs is the same, and the positions of the time units allocated on each of at least two BWPs are staggered from each other.

[0168] Optionally, the positions of the time units allocated on each of at least two BWPs being staggered from each other includes:

[0169] There is the same first preset interval between the positions of the time units of every two adjacent BWPs.

[0170] Optionally, on at least two BWPs, performing the transmission of the PDSCH or PUSCH scheduled by the DCI includes:

[0171] Within the first preset interval, switch from the BWP where the time unit before the first preset interval is located to the BWP where the time unit after the first preset interval is located to continue performing the transmission of the PDSCH or PUSCH scheduled by the DCI.

[0172] Optionally, the frequency-domain resource allocation information on at least two BWPs included in the DCI includes at least one of the following cases:

[0173] At least two BWPs share the frequency-domain resource allocation information;

[0174] At least two BWPs share the first frequency-domain resource allocation information, and the second frequency-domain resource allocation information other than the first frequency-domain resource allocation information is configured separately for at least two BWPs;

[0175] The frequency-domain resources allocated on each of at least two BWPs are indicated separately by different domains in the DCI;

[0176] The frequency-domain resources allocated on at least two BWPs are jointly indicated by the same domain in the DCI;

[0177] The frequency-domain resources allocated on a part of at least two BWPs are indicated by the DCI, and the frequency-domain resources allocated on another part of at least two BWPs are predefined or preconfigured by higher-layer signaling.

[0178] Optionally, the frequency-domain resources allocated on at least two BWPs are jointly indicated by the same domain in the DCI, including:

[0179] At least one of the physical resource blocks (PRBs), virtual resource blocks (VRBs), and resource block groups (RBGs) on at least two BWPs is numbered uniformly.

[0180] Optionally, the RBG size is determined by at least one of the following methods:

[0181] Each of at least two BWPs divides the RBG based on the same RBG size, and the RBG size is determined according to the bandwidth size of a specific BWP among at least two BWPs, or the RBG size is determined according to the total bandwidth size of at least two BWPs, where the specific BWP is predefined or preconfigured by higher-layer signaling;

[0182] Each of at least two BWPs divides the RBG based on different RBG sizes, and the RBG size is determined separately according to the bandwidth size of each BWP.

[0183] Optionally, the division of the RBG on each BWP starts from the carrier resource block CRB0 at the lowest frequency point of the reference carrier, where the reference carrier is a predefined carrier in the carrier where each BWP is located.

[0184] Optionally, the mapping method between the VRB and the PRB includes at least one of the following:

[0185] Within the respective bandwidth of each BWP, VRBs and PRBs are interleaved and mapped;

[0186] Within the total bandwidth of at least two BWPs, VRBs and PRBs are interleaved and mapped.

[0187] Optionally, the PDSCH transmitted on at least two BWPs includes a semi-persistent scheduled physical downlink shared channel SPS-PDSCH, and the PUSCH transmitted on at least two BWPs includes a type 1 preconfigured grant physical uplink shared channel CG-PUSCH and a type 2 CG-PUSCH.

[0188] Optionally, for the CG-PUSCH, the corresponding first hybrid automatic repeat request HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs; or,

[0189] The corresponding first HARQ process number is determined based on the first time unit allocated on a preset BWP among at least two BWPs;

[0190] wherein the preset BWP is predefined or preconfigured.

[0191] Optionally, for the SPS-PDSCH, the corresponding second HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs; or,

[0192] The corresponding second HARQ process number is determined based on the first time unit allocated on a preset BWP among at least two BWPs;

[0193] wherein the preset BWP is predefined or preconfigured.

[0194] Optionally, if any one of at least two BWPs is deactivated, the method further includes at least one of the following:

[0195] Stop the transmission of SPS-PDSCH or CG-PUSCH on at least two BWPs;

[0196] On the non-deactivated BWP among at least two BWPs, perform the transmission of SPS-PDSCH or CG-PUSCH.

[0197] Optionally, on at least two BWPs, perform the transmission of DCI-scheduled PDSCH or PUSCH, including:

[0198] Determine at least one scheduled BWP among at least two BWPs;

[0199] On the at least one scheduled BWP, perform the transmission of DCI-scheduled PDSCH or PUSCH.

[0200] Optionally, when at least two BWPs satisfy at least one of the following conditions, the transmission of PDSCH or PUSCH scheduled by DCI is performed on the at least two BWPs:

[0201] The frequency-domain interval between two carriers adjacent in the frequency domain among the at least two BWPs does not exceed a first preset bandwidth;

[0202] The bandwidth between the lowest frequency and the highest frequency among the at least two BWPs does not exceed a second preset bandwidth;

[0203] The sum of the bandwidths of the at least two BWPs does not exceed a third preset bandwidth.

[0204] Optionally, the method further includes:

[0205] Sending a physical downlink control channel PDCCH corresponding to DCI on a specific BWP among the at least two BWPs, where the specific BWP is predefined or preconfigured by higher-layer signaling.

[0206] Optionally, the configurations related to PDSCH or PUSCH transmitted on the at least two BWPs comply with at least one of the following configurations:

[0207] The configurations related to PDSCH or PUSCH on a specific BWP among the at least two BWPs, where the specific BWP is predefined or preconfigured by higher-layer signaling;

[0208] Dedicated configurations related to PDSCH or PUSCH, where the dedicated configurations related to PDSCH or PUSCH are different from the configurations related to PDSCH or PUSCH on each BWP among the at least two BWPs.

[0209] Optionally, the demodulation reference signal DMRS signal sequences transmitted on each BWP are respectively generated based on at least one of the following:

[0210] The index number of the CRB corresponding to the PRB where the DMRS is located, where the index number of the CRB is numbered starting from CRB0 of the carrier where the DMRS is located, or the index number of the CRB is numbered starting from CRB0 of the carrier of the BWP with the lowest frequency among the at least two BWPs;

[0211] The index number of the carrier where the DMRS is located;

[0212] Dedicated parameters corresponding to the BWP where the DMRS is located, and the dedicated parameters are configured based on each BWP respectively.

[0213] Optionally, the specific BWP is predefined and includes at least one of the following:

[0214] The specific BWP is the BWP on the anchor carrier;

[0215] The specific BWP is the BWP on the carrier with the index number zero;

[0216] The specific BWP is the BWP on the carrier with the smallest index number;

[0217] The specific BWP is the BWP on the carrier with the lowest frequency;

[0218] The specific BWP is the BWP with a bandwidth less than the first preset value;

[0219] The specific BWP is the BWP with a bandwidth greater than the second preset value.

[0220] According to another aspect of the embodiments of the present application, a user equipment is provided, and the user equipment includes:

[0221] A transceiver configured to send and receive signals; and

[0222] A processor coupled to the transceiver and configured to execute the method performed by the UE provided by the embodiments of the present application.

[0223] According to still another aspect of the embodiments of the present application, a base station is provided, and the base station includes:

[0224] A transceiver configured to send and receive signals; and

[0225] A processor coupled to the transceiver and configured to execute the method performed by the base station provided by the embodiments of the present application.

[0226] According to still another aspect of the embodiments of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the method performed by the UE or the base station provided by the embodiments of the present application is implemented.

[0227] According to still another aspect of the embodiments of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the method performed by the UE or the base station provided by the embodiments of the present application is implemented.

[0228] The communication method, user equipment, and base station provided by the embodiments of the present application enable the user equipment to receive DCI. The DCI includes scheduling information of PDSCH or PUSCH transmitted on at least two BWPs. The scheduling information includes time-domain resource allocation information and frequency-domain resource allocation information. Among them, the frequency-domain resource allocation information includes the frequency-domain resource allocation information on at least two BWPs. On at least two BWPs, the transmission of PDSCH or PUSCH scheduled by DCI is performed, making it possible to configure multi-carriers in a serving cell. By aggregating multiple carriers in a serving cell, it is more flexible than aggregating multiple carriers by aggregating multiple serving cells, can simplify the system more, and save signaling overhead. Description of the Drawings

[0229] To more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for description in the embodiments of the present application.

[0230] Figure 1 Schematic diagram of the overall structure of the wireless network provided by the embodiments of the present application;

[0231] Figure 2a Schematic diagram of the transmission path provided by the embodiments of the present application;

[0232] Figure 2b Schematic diagram of the reception path provided by the embodiments of the present application;

[0233] Figure 3a Schematic diagram of the structure of the UE provided by the embodiments of the present application;

[0234] Figure 3b Schematic diagram of the structure of the base station provided by the embodiments of the present application;

[0235] Figure 4 Schematic diagram of the flowchart of a method executed by the UE provided by the embodiments of the present application;

[0236] Figure 5 Schematic diagram of a method for performing resource mapping provided by the embodiments of the present application;

[0237] Figure 6 Schematic diagram of another method for performing resource mapping provided by the embodiments of the present application;

[0238] Figure 7 Schematic diagram of yet another method for performing resource mapping provided by the embodiments of the present application;

[0239] Figure 8 Schematic diagram of a time-domain resource allocation method provided by the embodiments of the present application;

[0240] Figure 9Schematic diagram of another time-domain resource allocation method provided by an embodiment of the present application;

[0241] Figure 10 Flow schematic diagram of a method executed by a base station provided by an embodiment of the present application;

[0242] Figure 11 Schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Detailed implementation manners

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

[0244] The terms and phrases used in the following specification and claims are not limited to their dictionary meanings but are merely used by the inventors to enable a clear and consistent understanding of the present application. Therefore, it should be apparent to those skilled in the art that the following description of the various embodiments of the present application is for illustrative purposes only and not for the purpose of limiting the present application as defined by the appended claims and their equivalents.

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

[0246] The term "comprises" or "may comprise" refers to the presence of the corresponding disclosed function, operation, or component that can be used in various embodiments of the present application, rather than limiting the presence of one or more additional functions, operations, or features. In addition, the term "comprises" or "has" can be interpreted as indicating certain characteristics, numbers, steps, operations, components, components, or combinations thereof, but should not be interpreted as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, components, components, or combinations thereof.

[0247] The term "or" used in various embodiments of the present application includes any of the listed terms and all combinations thereof. For example, "A or B" can include A, can include B, or can include both A and B.

[0248] Unless defined otherwise, all terms (including technical and scientific terms) used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. As used in a dictionary, ordinary terms are to be interpreted as having a meaning consistent with their context in the relevant art and are not to be interpreted in an idealized or overly formal sense unless expressly so defined in this application.

[0249] Figure 1 FIG. 100 illustrates an example wireless network 100 according to various embodiments of the present application. Figure 1 The embodiments of the wireless network 100 shown in FIG. 100 are for illustrative purposes only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present application.

[0250] The wireless network 100 includes gNodeBs (gNBs) 101, 102, and 103. The gNB 101 communicates with the gNB 102 and the gNB 103. The gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a proprietary IP network, or other data networks.

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

[0252] gNB 102 provides wireless broadband access to network 130 for a plurality of first user equipment (UEs) within coverage area 120 of gNB 102. The plurality of first UEs include: UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a plurality of second UEs within coverage area 125 of gNB 103. The plurality of second UEs include UE 115 and UE 116. In some embodiments, one or more of 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 technologies.

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

[0254] As described in more detail below, one or more of gNBs 101, 102, and 103 include a 2D antenna array as described in embodiments of the present application. In some embodiments, one or more of gNBs 101, 102, and 103 support codebook design and structure for systems with 2D antenna arrays.

[0255] Although Figure 1 an example of wireless network 100 is shown, various changes can be made to Figure 1 it. For example, wireless network 100 can include any number of gNBs and any number of UEs arranged in any suitable manner. Also, gNB 101 can communicate directly with any number of UEs and provide wireless broadband access to network 130 for those UEs. Similarly, each of gNBs 102 - 103 can communicate directly with network 130 and provide direct wireless broadband access to network 130 for UEs. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as an external telephone network or other types of data networks.

[0256] Figure 2a and Figure 2bShows an example wireless transmit and receive path according to the present application. In the following description, the transmit path 200 can be described as being implemented in a gNB (such as gNB 102), while the receive path 250 can be described as being implemented in a UE (such as UE 116). However, it should be understood that the receive path 250 can be implemented in a gNB, and the transmit path 200 can be implemented in a UE. In some embodiments, the receive path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the present application.

[0257] The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) block 210, an N-point inverse fast Fourier transform (IFFT) block 215, a parallel-to-serial (P-to-S) block 220, a cyclic prefix addition block 225, and an upconverter (UC) 230. The receive path 250 includes a downconverter (DC) 255, a cyclic prefix removal 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.

[0258] In the transmit path 200, the channel coding and modulation block 205 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The 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 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. The parallel-to-serial block 220 converts (such as multiplexes) the parallel time-domain output symbols from the N-point IFFT block 215 to generate a serial time-domain signal. The cyclic prefix addition block 225 inserts a cyclic prefix into the time-domain signal. The upconverter 230 modulates (such as upconverts) the output of the cyclic prefix addition block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at baseband before being upconverted to the RF frequency.

[0259] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and operations opposite to those at gNB 102 are performed at UE 116. The downconverter 255 downconverts the received signal to baseband frequency, and the cyclic prefix block 260 removes the cyclic prefix to generate a serial time-domain baseband signal. The serial-to-parallel block 265 converts the time-domain baseband signal to a parallel time-domain signal. The N-point FFT block 270 performs the FFT algorithm to generate N parallel frequency-domain signals. The parallel-to-serial block 275 converts the parallel frequency-domain signals to a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

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

[0261] Figure 2a and Figure 2b each of the components in Figure 2a and Figure 2b can be implemented using only hardware, or using a combination of hardware and software / firmware. As a specific example,

[0262] at least some of the components in

[0263] can be implemented in software, while other components can be implemented by configurable hardware or a hybrid of software and configurable hardware. For example, the FFT block 270 and the IFFT block 215 can be implemented as configurable software algorithms, where the value of the number of points N can be modified according to the implementation.

[0262] Furthermore, although described as using FFT and IFFT, this is merely illustrative and should not be construed as limiting the scope of this application. Other types of transforms can be used, such as the discrete Fourier transform (DFT) and the inverse discrete Fourier transform (IDFT) functions. It should be understood that for the DFT and IDFT functions, the value of the variable N can be any integer (such as 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of the variable N can be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

[0263] Although Figure 2a and Figure 2b show examples of wireless transmit and receive paths, various changes can be made to Figure 2a and Figure 2b For example,Figure 2a and Figure 2b The various components in can be combined, further subdivided, or omitted, and additional components can be added according to specific needs. Moreover, Figure 2a and Figure 2b are intended to show examples of types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0264] Figure 3a An example UE 116 according to the present application is shown. Figure 3a The embodiment of UE 116 shown in is for illustration only, and Figure 1 UEs 111 - 115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3a the scope of the present application is not limited to any particular implementation of the UE.

[0265] UE 116 includes antenna 305, radio frequency (RF) transceiver 310, transmit (TX) processing circuitry 315, microphone 320, and receive (RX) processing circuitry 325. UE 116 also includes speaker 330, processor / controller 340, input / output (I / O) interface (IF) 345, (one or more) input devices 350, display 355, and memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0266] RF transceiver 310 receives incoming RF signals transmitted by the gNB of wireless network 100 from antenna 305. RF transceiver 310 downconverts the incoming RF signals to generate intermediate frequency (IF) or baseband signals. The IF or baseband signals are sent to RX processing circuitry 325, where RX processing circuitry 325 generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 325 sends the processed baseband signals to speaker 330 (such as for voice data) or to processor / controller 340 (such as for web browsing data) for further processing.

[0267] 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 processed baseband or IF signals. RF transceiver 310 receives the outgoing processed baseband or IF signals from TX processing circuitry 315 and upconverts the baseband or IF signals to RF signals transmitted via antenna 305.

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

[0269] The processor / controller 340 can also execute other processes and programs residing in the memory 360, such as operations for channel quality measurement and reporting for a system with a 2D antenna array as described in the embodiments of the present application. The processor / controller 340 can move data into or out of the memory 360 as needed for executing processes. In some embodiments, the processor / controller 340 is configured to execute the application 362 based on the OS 361 or in response to signals received from the gNB or the operator. The processor / controller 340 is also coupled to the 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. The I / O interface 345 is the communication path between these accessories and the processor / controller 340.

[0270] The processor / controller 340 is also coupled to the (multiple) input devices 350 and the display 355. The operator of the UE 116 can use the (multiple) input devices 350 to input data into the UE 116. The display 355 can be a liquid crystal display or other display capable of presenting text and / or at least limited graphics (such as from a website). The memory 360 is coupled to the processor / controller 340. A portion of the memory 360 can include random access memory (RAM), while another portion of the memory 360 can include flash memory or other read-only memory (ROM).

[0271] Although Figure 3a an example of the UE 116 is shown, various changes can be made to Figure 3a it. For example, Figure 3a the various components in Figure 3a can be combined, further subdivided, or omitted, and additional components can be added according to specific needs. As a specific 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

[0272] Figure 3bFIG. 0 shows an example gNB 102 according to the present application. Figure 3b The embodiment of the gNB 102 shown in FIG. 1 is for illustration only, and Figure 1 other gNBs can have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 3b do not limit the scope of the present application to any particular implementation of the gNB. It should be noted that gNB 101 and gNB 103 can include structures that are the same as or similar to those of gNB 102.

[0273] As Figure 3b shown in FIG. 1, the gNB 102 includes a plurality of antennas 370a - 370n, a plurality of RF transceivers 372a - 372n, a transmit (TX) processing circuit 374, and a receive (RX) processing circuit 376. In some embodiments, one or more of the plurality of antennas 370a - 370n include a 2D antenna array. The gNB 102 also includes a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0274] The RF transceivers 372a - 372n receive incoming RF signals from the antennas 370a - 370n, such as signals transmitted by a UE or other gNBs. The RF transceivers 372a - 372n down - convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to the RX processing circuit 376, where the 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 signal to the controller / processor 378 for further processing.

[0275] The TX processing circuit 374 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 378. The TX processing circuit 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 signal from the TX processing circuit 374 and up - convert the baseband or IF signal to an RF signal transmitted via the antennas 370a - 370n.

[0276] 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, the controller / processor 378 can control the reception of forward channel signals and the transmission of reverse channel signals via the RF transceivers 372a - 372n, the RX processing circuitry 376, and the TX processing circuitry 374 according to well-known principles. The controller / processor 378 can also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 378 can perform BIS processes such as those executed by the blind interference sensing (BIS) algorithm and decode the received signals from which the interference signals have been subtracted. The controller / processor 378 can support any one of a variety of other functions in the gNB 102. In some embodiments, the controller / processor 378 includes at least one microprocessor or microcontroller.

[0277] The controller / processor 378 can also execute programs and other processes residing in the memory 380, such as the basic OS. The controller / processor 378 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the present application. In some embodiments, the controller / processor 378 supports communication between entities such as web RTC. The controller / processor 378 can move data into or out of the memory 380 as needed for the execution of processes.

[0278] The controller / processor 378 is also coupled to the backhaul or network interface 382. The backhaul or network interface 382 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or via a network. The backhaul or network interface 382 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G or new radio access technology or NR, LTE, or LTE-A), the backhaul or network interface 382 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. 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) via a wired or wireless local area network or via a wired or wireless connection. The backhaul or network interface 382 includes any suitable structure that supports communication via a wired or wireless connection, such as Ethernet or an RF transceiver.

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

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

[0281] Although Figure 3b an example of gNB 102 is shown, various changes can be made to Figure 3b it. For example, gNB 102 can include any number of Figure 3a each of the components shown therein. As a specific example, an access point can include a number of backhaul or network interfaces 382, and controller / processor 378 can support routing functions to route data between different network addresses. As another specific example, although shown as including a single instance of TX processing circuitry 374 and a single instance of RX processing circuitry 376, gNB 102 can include multiple instances of each (such as one for each RF transceiver).

[0282] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below in conjunction with the accompanying drawings.

[0283] Embodiments of this application provide a method performed by a UE in a communication system and a method performed by a base station in a communication system. This method is an enhancement of existing multi - carrier technologies and supports simultaneous transmission by a UE on multiple carriers within a serving cell.

[0284] The technical solutions of the embodiments of this application and the technical effects produced by the technical solutions of this application will be described below through the description of several exemplary embodiments. It should be noted that the following embodiments can refer to, draw on, or combine with each other. For the same terms, similar features, and similar implementation steps in different embodiments, they will not be repeatedly described.

[0285] In the embodiments of this application, a method performed by a UE in a communication system is provided. As Figure 4 shown, the method includes:

[0286] Step S101: Receive DCI (Downlink Control Information), where the DCI includes scheduling information of PDSCH (Physical Downlink Shared Channel) or PUSCH (Physical Uplink Shared Channel) transmitted on at least two BWPs (Bandwidth Parts). The scheduling information includes time-domain resource allocation information and frequency-domain resource allocation information. Among them, the frequency-domain resource allocation information includes the frequency-domain resource allocation information on at least two BWPs;

[0287] Step S102: On at least two BWPs, perform the transmission of the PDSCH or PUSCH scheduled by the DCI;

[0288] Optionally, the frequency-domain resources included in each of the at least two BWPs do not overlap.

[0289] Optionally, each of the at least two BWPs is on a different carrier.

[0290] Optionally, each of the at least two BWPs is in a different frequency band.

[0291] Optionally, the carriers where each of the at least two BWPs is located are configured in the same serving cell.

[0292] If the operator has more spectrum resources, deploying multiple carriers can improve the rate of the terminal.

[0293] The above method of deploying multiple carriers provided by the embodiments of the present application enables multi-carrier configuration in a serving cell. By aggregating at least two BWPs in a serving cell to aggregate multiple carriers, it is more flexible than the method of aggregating multiple carriers by aggregating multiple serving cells, can simplify the system more, and save signaling overhead.

[0294] Specifically, aggregating multiple carriers by aggregating at least two BWPs in a serving cell has at least one of the following advantages compared to the method of aggregating multiple carriers by aggregating multiple serving cells:

[0295] 1. Save broadcast signaling overhead: For example, in a CA system, each carrier corresponds to a serving cell, and broadcast signaling such as the SSB (Synchronization Signal Block) and SIB1 (System Information Block 1) of the corresponding serving cell needs to be transmitted on each carrier; while for the system with multiple carriers configured in a serving cell provided in the embodiments of the present application, it is only necessary to transmit the broadcast signaling of the serving cell on one of the carriers.

[0296] 2. Simplify the signaling for carrier activation: For example, in a CA system, the secondary cell can be activated / deactivated through RRC (Radio Resource Control) or MAC (Medium Access Control) CE (Control Element) signaling. Activating / deactivating the secondary cell can also be understood as activating / deactivating the carrier corresponding to the secondary cell; while for the system with multiple carriers configured in a serving cell provided in the embodiments of the present application, multiple BWPs in a serving cell can be activated / deactivated through physical layer signaling, where the multiple activated BWPs are located on different carriers respectively. Activating / deactivating multiple BWPs can also be understood as activating / deactivating the carriers where the BWPs are located.

[0297] 3. Simplify mobility measurement and management: For example, in a CA system, each carrier corresponds to a serving cell, and mobility measurement and management of the corresponding serving cell need to be performed on each carrier; while for the system with multiple carriers configured in a serving cell provided in the embodiments of the present application, it is only necessary to perform mobility measurement and management of the serving cell on one of the carriers (such as the anchor carrier or pre-configured carrier, etc., but not limited thereto).

[0298] It can be seen from the above analysis that configuring multiple carriers in a serving cell is more flexible than CA / DC, can simplify the system more, and save signaling overhead.

[0299] In addition, in the existing 5G NR (New Radio) communication system, one downlink carrier and at most two uplink carriers can be configured in a serving cell. When two uplink carriers are configured in a serving cell, one of the uplink carriers is called the Normal Uplink (NUL), and the other uplink carrier is called the Supplement Uplink (SUL). The SUL is usually located in a lower frequency band and is used to enhance the coverage of the uplink. The SUL configuration is optional. Although the SUL and the NUL belong to the same serving cell, that is, multiple uplink carriers are configured in a serving cell and the UE can dynamically switch the uplink transmission between the SUL and the NUL, the UE cannot perform uplink transmission on the SUL and the NUL simultaneously. Therefore, the SUL can only improve the coverage of the uplink, but cannot increase the peak rate of the uplink transmission.

[0300] The embodiments of the present application support configuring multiple downlink carriers and more than two uplink carriers in a serving cell. In addition, the biggest difference between the method of deploying multiple carriers in a serving cell provided by the embodiments of the present application and the SUL is that a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH) can be co-transmitted on multiple carriers in a serving cell, that is, a Transport Block (TB) can be transmitted across multiple carriers in a serving cell, so as to obtain frequency diversity gain and / or increase the peak rate.

[0301] In the embodiments of the present application, technical details related to the method of transmitting a transport block across multiple carriers are provided.

[0302] In the embodiments of the present application, a time unit can be an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single-Carrier-FDMA (SC-FDMA) symbol, or a time unit is a time slot.

[0303] In the embodiments of the present application, a Bandwidth Part (BWP) essentially refers to a continuous frequency-domain resource, and the BWP can be replaced by other technical terms with the same meaning. For example, the BWP can be replaced by a subband.

[0304] In the embodiments of the present application, a serving cell can also be simply referred to as a cell.

[0305] In an embodiment of the present application, multiple carriers can be configured within a serving cell, and one of the carriers can be referred to as an anchor carrier, while the other carriers are referred to as non-anchor carriers. For example, the carrier used to transmit cell system information is referred to as the anchor carrier, and the other carriers are referred to as non-anchor carriers. The base station transmits synchronization signals and cell system information on the anchor carrier, such as cell defining SSB (Cell Defining Synchornization Signal Block, CD-SSB), and cell system information, where the cell system information includes the first system information block and other system information blocks. The base station configures the information of other non-anchor carriers through the anchor carrier. When the anchor carrier is a TDD carrier, the anchor downlink carrier and the anchor uplink carrier are the same anchor carrier; when the anchor carrier is an FDD carrier, the anchor carrier includes an anchor downlink carrier and its paired anchor uplink carrier. On the anchor downlink carrier, the initial downlink BWP is configured, and on the anchor uplink carrier, the PRACH resource pool for accessing the network and the initial uplink BWP are configured. Based on the PRACH configuration parameters, the UE can access the network through the anchor carrier. In other words, the anchor carrier is a carrier with cell system information transmission and / or initial access function.

[0306] In an embodiment of the present application, multiple carriers can be configured within a serving cell, and one or more BWPs can be configured on each carrier. The UE can transmit simultaneously on the BWPs of these multiple carriers to obtain a bandwidth gain and significantly improve the peak rate, achieving a similar effect to CA. The corresponding implementation method can be to activate multiple BWPs, and these multiple activated BWPs belong to different carriers respectively; or, the UE can dynamically switch transmissions on these multiple carriers to obtain a diversity gain, and the corresponding implementation method can be to support cross-carrier BWP switching.

[0307] In the case of activating multiple BWPs on different carriers within a serving cell, the UE can perform transmissions simultaneously on these multiple activated BWPs. One of the transmission methods for the multiple activated BWPs is that the UE transmits different TBs on the multiple activated BWPs respectively, that is, transmits different PDSCHs or different PUSCHs on the multiple activated BWPs. For example, N different TBs are transmitted on the N activated BWPs, and the transmission of these N different TBs can be scheduled by one DCI or by N DCIs respectively; the second transmission method for the multiple activated BWPs is that the UE transmits the same TB on the multiple activated BWPs, that is, transmits one PDSCH or one PUSCH on the multiple activated BWPs. For example, the same TB is transmitted on the N activated BWPs, and the TB transmission across N BWPs is scheduled by one DCI, where N is a positive integer greater than 1.

[0308] In the embodiments of the present application, when multiple BWPs are activated, according to the different functions of the activated BWPs, one of the activated BWPs among the multiple activated BWPs is referred to as the first BWP, and the other activated BWPs are referred to as the second BWPs, that is, the activated BWPs on at least two different carriers within a serving cell include one first BWP and at least one second BWP. Among them, the first BWP may also be referred to as the first activated BWP, the primary BWP, or the primary activated BWP, and the second BWP may also be referred to as the second activated BWP, the secondary BWP, or the secondary activated BWP.

[0309] Optionally, the primary activated BWP (i.e., the first BWP) can be defined according to at least one of the following methods:

[0310] (1) The primary activated BWP has a complete BWP configuration. For example, it reuses the existing BWP configuration, so it can be independently scheduled and used. While the secondary activated BWP only has bandwidth-related configurations and does not have any configurations related to physical channel or signal transmission. Therefore, the secondary activated BWP cannot be independently scheduled and used and can only be used depending on the primary activated BWP, serving to expand the bandwidth.

[0311] (2) Control channel transmission can be configured on the primary activated BWP, while control channel transmission cannot be configured on the secondary activated BWP. For example, PDCCH (Physical Downlink Control Channel) and / or PUCCH (Physical Uplink Control Channel) transmission can be configured on the primary activated BWP, while PDCCH and PUCCH transmission cannot be configured on the secondary activated BWP. Since control channel transmission is configured on the primary activated BWP, the primary activated BWP cannot be deactivated, and the secondary activated BWP can be deactivated.

[0312] In other words, the at least two activated BWPs on different carriers within a serving cell include at least one of the following situations:

[0313] The first BWP and the second BWP share the transmission configuration of PDSCH and / or PUSCH;

[0314] The first BWP and the second BWP share the configuration of the first transmission parameters of PDSCH and / or PUSCH, and the second transmission parameters other than the first transmission parameters are configured separately for the first BWP and the second BWP. That is, the first BWP and the second BWP share some of the same transmission configurations of PDSCH and / or PUSCH.

[0315] Optionally, the first BWP includes at least one of the following: the first BWP is a BWP on an anchor carrier; the first BWP is a BWP on a carrier with an index number of zero; the first BWP is a BWP on a carrier with the smallest index number; the first BWP is a BWP on a carrier with the lowest frequency; the first BWP is a BWP indicated by higher layer signaling.

[0316] And optionally, the first BWP is used to transmit physical control channels (including PDCCH and / or PUCCH) and physical shared channels (including PDSCH and / or PUSCH), and the second BWP is used to transmit physical shared channels.

[0317] Optionally, in order to reduce the power consumption of the UE in PDCCH monitoring, the network may configure PDCCH transmission only on one of at least two BWPs, that is, the UE monitors PDCCH only on one of at least two BWPs. Specifically, for step S101, the UE may monitor PDCCH on a first preset BWP among at least two BWPs, and the PDCCH includes scheduling information on at least two BWPs; where the first preset BWP is the first BWP, or the first preset BWP is configured as one of at least two BWPs.

[0318] Optionally, in order to reduce the configured resources of PUCCH, the network may configure PUCCH only on one of at least two BWPs, that is, the UE sends PUCCH only on one of at least two BWPs. Specifically, for step S101, the UE may send PUCCH on a second preset BWP among at least two BWPs, and the PUCCH includes uplink control information related to at least two BWPs; where the second preset BWP is the first BWP, or the second preset BWP is configured as one of at least two BWPs.

[0319] In an embodiment of this application, an optional implementation manner is provided for step S102. Specifically, it may include: performing repeated transmission of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively.

[0320] For an embodiment of this application, multiple carriers are configured in one serving cell, and one TB (that is, one PDSCH or one PUSCH) can be transmitted across multiple carriers in the cell, that is, resources are allocated on multiple carriers to transmit the same TB, and the transmission signals on each carrier can be regarded as different repetitions of the same TB, and each repetition can use the same or different redundancy versions (RV). The specific process (corresponding to step S101 and step S102) can be described as follows:

[0321] Step SA1: The UE detects a DCI that is used to schedule a PDSCH or PUSCH for cross-multiple BWP (i.e., cross-multiple carriers) transmission. The DCI includes time-domain resource allocation information and frequency-domain resource allocation information on multiple BWPs.

[0322] Step SA2: For the PDSCH, the UE receives different repeated transmissions of the same TB on multiple BWPs (i.e., multiple carriers); for the PUSCH, the UE sends different repeated transmissions of the same TB on multiple BWPs (i.e., multiple carriers).

[0323] Taking the PDSCH as an example, the transmission method based on repetition means that the time-frequency domain resources allocated on each carrier are used to transmit one repetition of the PDSCH, that is, corresponding to one RV. N carriers correspond to N repeated transmissions of the PDSCH. Each repetition of the PDSCH can be decoded independently, and the UE can attempt to decode each repetition of the PDSCH separately; alternatively, multiple repetitions of the PDSCH can be soft combined and then decoded, and the multiple repeated transmissions can use the same or different RVs. In this transmission method, the UE performs rate matching on the repeated transmissions on each active BWP respectively.

[0324] In the current communication system, the TBS (Transport Block Size) is determined based on the number of resource elements (REs). For example, the UE first determines the number of REs N RE , and then based on the number of REs N RE determines the unquantified intermediate variable N info , and then determines the quantified intermediate variable N info according to the value range of the unquantified intermediate variable N i ′ nfo , and then finds the TBS value that is not less than and closest to N i ′ nfo from the TBS table as the determined TBS.

[0325] In the embodiments of the present application, for the case of repeated transmissions of the PDSCH or PUSCH scheduled by the DCI on at least two BWPs respectively, the first TBS of the PDSCH or PUSCH transmitted on at least two BWPs can also be determined based on at least one of the following:

[0326] Method 1: The average number of REs determined on at least two BWPs.

[0327] That is, for the first step of the above-mentioned TBS determination process (i.e., determining the number of REs), the average number of REs on multiple BWPs (or multiple carriers) can be used as the number of REs N for determining the first TBS. RE 。

[0328] In one example, the number of Physical Resource Blocks (PRBs) allocated on different BWPs may be different, the number of symbols allocated on different BWPs may be different, the Demodulation Reference Signal (DMRS) patterns used on different BWPs may be different (i.e., the number of DMRS REs per PRB on different BWPs may also be different), and the signaling overhead sizes configured on different BWPs may also be different. Here, the UE needs to determine the number of REs N on each BWP (or each carrier) separately RE,i , and use the total number of REs on all BWPs divided by the number of BWPs as the average number of REs, that is Or where N is the number of active BWPs (or the number of carriers) for transmitting a TB, and N RE,i is the number of REs on the i-th active BWP (or the i-th carrier). Among them, when the UE determines N RE,i , it first determines the number of REs N R ′ E,i in a PRB on the i-th active BWP (or the i-th carrier), for example, determine Then, based on N RE,i = min(156, N R ′ E,i ) * n PRB,i to determine the number of REs on the i-th active BWP (or the i-th carrier), where n PRB,i is the number of PRBs allocated on the i-th active BWP (or the i-th carrier), is the number of REs included in a PRB, such as is the number of PDSCH symbols allocated in a time slot on the i-th active BWP (or the i-th carrier), is the number of REs used for DMRS in each PRB on the i-th active BWP (or the i-th carrier), is the signaling overhead size on the i-th active BWP (or the i-th carrier) configured by higher-layer parameters.

[0329] In another example, the number of PRBs allocated on different BWPs may be different, but the number of symbols allocated on different BWPs is the same, and the DMRS patterns used on different BWPs are also the same (i.e., the number of DMRS REs per PRB on different BWPs is also the same), and the signaling overhead sizes on different BWPs are also the same. Here, the UE first determines the number of REs within a PRB based on and then determines the average number of PRBs allocated on all BWPs. For example, the total number of PRBs allocated on all BWPs is divided by the number of BWPs to obtain the average number of PRBs, that is or After that, based on N RE = min(156, N R ′ E ) * n PRB the number of REs is determined, where N is the number of active BWPs (i.e., the number of carriers) for transmitting a TB, is the number of REs included in a PRB, such as [[ID=2'slot]]is the number of PDSCH symbols allocated within a slot, is the number of REs used for DMRS within each PRB, is the signaling overhead size configured by higher layer parameters, and n PRB,i is the number of PRBs allocated on the i-th active BWP (or the i-th carrier).

[0330] Method 2: The maximum value among the numbers of REs determined on at least two BWPs respectively.

[0331] That is, for the first step of the above TBS determination process (i.e., determining the number of REs), the maximum number of REs determined among multiple BWPs can be used as the number of REs N for determining the first TBS RE .

[0332] In one example, the number of PRBs allocated on different BWPs may be different, the number of symbols allocated on different BWPs may also be different, the DMRS patterns used on different BWPs may also be different (i.e., the number of DMRS REs per PRB on different BWPs may also be different), and the signaling overhead sizes configured on different BWPs may also be different. Here, the UE needs to determine the number of REs N on each BWP (or each carrier) respectively RE,i , and then use the maximum value among them, that is, the maximum number of REs, as the number of REs N for determining the first TBS RE , that is, N RE = max(NR ′ E,i )。

[0333] In another example, the number of PRBs allocated on different BWPs may be different, but the number of symbols allocated on different BWPs is the same, and the DMRS patterns (patterns) used on different BWPs are also the same (i.e., the number of DMRS REs per PRB on different BWPs is also the same), and the signaling overhead sizes on different BWPs are also the same. Here, the UE first determines the number of REs within a PRB based on and then determines the maximum number of PRBs n allocated on all BWPs PRB , that is, n PRB = max(n PRB,i ), where n PRB,i is the number of PRBs allocated on the i-th active BWP (or the i-th carrier), is the number of REs included in a PRB, such as is the number of PDSCH symbols allocated within a time slot, is the number of REs used for DMRS within each PRB, is the signaling overhead size configured by higher-layer parameters. Then, based on N RE = min(156, N R ′ E ) * n PRB the number of REs is determined.

[0334] Method 3: The minimum value among the numbers of REs determined on at least two BWPs respectively.

[0335] That is, for the first step of the above TBS determination process (i.e., determining the number of REs), the minimum number of REs determined among multiple BWPs can be used as the number of REs N for determining the first TBS RE .

[0336] In one example, the number of PRBs allocated on different BWPs may be different, the number of symbols allocated on different BWPs may also be different, the DMRS patterns (patterns) used on different BWPs may also be different (i.e., the number of DMRS REs per PRB on different BWPs may also be different), and the signaling overhead sizes configured on different BWPs may also be different. Here, the UE needs to determine the number of REs N on each BWP (or each carrier) respectively RE,i , and then use the minimum value among them, that is, the minimum number of REs, as the number of REs N for determining the first TBS RE , that is, N RE= min(N RE,i ).

[0337] In another example, the number of PRBs allocated on different BWPs may be different, but the number of symbols allocated on different BWPs is the same, and the DMRS patterns (patterns) used on different BWPs are also the same (i.e., the number of DMRS REs per PRB on different BWPs is also the same), and the signaling overhead sizes on different BWPs are also the same. Here, the UE first determines the number of REs in a PRB based on and then determines the minimum number of PRBs n PRB allocated on all BWPs, that is, n PRB = min(n PRB,i ), where n PRB,i is the number of PRBs allocated on the i-th active BWP (or the i-th carrier), is the number of REs included in a PRB, such as is the number of PDSCH symbols allocated in a time slot, is the number of REs used for DMRS in each PRB, is the signaling overhead size configured by higher-layer parameters. Then, based on N RE = min(156, N R ′ E ) * n PRB the number of REs is determined.

[0338] Method 4: The number of REs determined on a preset BWP among at least two BWPs.

[0339] That is, for the first step of the above-mentioned TBS determination process (i.e., determining the number of REs), the number of REs determined on a specific BWP (or a specific carrier) can be used as the number of REs N RE for determining the first TBS. Among them, the specific BWP can be the primary active BWP (i.e., the first BWP), the active BWP with the smallest index number, the active BWP on the anchored carrier, the active BWP on the carrier with the index number #0, the active BWP on the carrier with the smallest index number among multiple carriers, the active BWP on the carrier with the lowest frequency, or the active BWP indicated by signaling, etc., but not limited thereto. Among them, the active BWP indicated by signaling can be configured by higher-layer signaling, or indicated by DCI scheduling cross-active BWP transmission.

[0340] Method 5: The scaling factor corresponding to the first TBS.

[0341] For the first step of the above-mentioned process of determining the TBS (i.e., determining the number of REs), the UE may multiply the number of REs determined by the above Method 1, Method 2, Method 3, or Method 4 by a scaling factor, and use the obtained value as the number of REs N for determining the first TBS. RE . For example, or wherein, the size of the scaling factor f1 may be configured by higher layer signaling, and N′ RE is the number of REs determined by the above Method 1, Method 2, Method 3, or Method 4. Optionally, different active BWPs may be configured with different scaling factors f1.

[0342] Alternatively, the UE may multiply the TBS determined by the above Method 1, Method 2, Method 3, or Method 4 by a scaling factor, and use the obtained value as the TBS. For example, or wherein, the size of the scaling factor f2 is configured by higher layer signaling, and TBS′ is the TBS value determined by the above Method 1, Method 2, Method 3, or Method 4. Optionally, different active BWPs may be configured with different scaling factors f2.

[0343] In the embodiments of the present application, for the case of performing repeated transmission of the PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the RVs transmitted on at least two BWPs may also be determined by at least one of the following methods:

[0344] Method 1: The RVs transmitted on at least two BWPs are the same. For example, the PDSCH on each active BWP (or each carrier) re-uses the same RV, and this RV may be pre-defined, configured by higher layer signaling, or indicated by scheduling DCI.

[0345] Method 2: The RVs transmitted on each of the at least two BWPs are different. For example, the PDSCH repetition on each active BWP (or each carrier) may use different RVs, and the RVs of the PDSCH repetition on each active BWP (or each carrier) may be pre-defined separately, configured separately by higher layer signaling, or indicated separately by scheduling DCI.

[0346] Method 3: The RVs transmitted on each of at least two BWPs are different, and each RV is determined by an RV sequence. Each of the at least two BWPs cyclically corresponds to each RV in the RV sequence in turn. For example, the RVs for the PDSCH repetitions on each active BWP (or each carrier) are determined based on a preset RV sequence (or called RV rotation sequence). When corresponding each active BWP to the RV sequence, the order of multiple active BWPs can be arranged in ascending order from low frequency to high frequency, or the order of multiple active BWPs can be arranged in ascending order according to the index number of the carrier they are on, or the order of multiple active BWPs can be arranged in ascending order according to the index number of the BWP (assuming that the BWPs on all carriers are uniformly numbered), etc., and other arrangement methods can also be used. Among them, the RV sequence is predefined or configured by high-layer signaling. Optionally, the RV sequence is {#0, #1, #2, #3} or {#0, #2, #3, #1}, but not limited thereto.

[0347] Method 4: The RVs transmitted on each of at least two BWPs are different, and each RV is determined by an RV sequence and a starting RV. Each of the at least two BWPs cyclically corresponds to each RV in the RV sequence in turn starting from the starting RV. For example, the RVs for the PDSCH repetitions on each active BWP (or each carrier) are determined based on a preset RV sequence (or called RV rotation sequence) and a starting RV. Among them, the RV sequence is predefined or configured by high-layer signaling, and the starting RV is predefined, configured by high-layer signaling, or indicated by DCI. The arrangement method when corresponding each active BWP to the RV sequence and the optional RV sequence, etc. can refer to the description of Method 3, and will not be elaborated here. In one example, assume that the RV rotation sequence is {#0, #3, #2, #1}, and there are a total of three active BWPs. Assume that the starting RV is #3, then the RVs corresponding to the PDSCH repetitions on the three active BWPs are #3, #2, and #1 respectively. Here, the starting RV corresponding to the first active BWP can be fixed. For example, the starting RV is predefined or preconfigured by high-layer signaling; or, the starting RV corresponding to the first active BWP can be dynamically changed. For example, the starting RV is indicated by scheduling DCI.

[0348] The description of the above implementation scheme for PDSCH cross-carrier transmission also applies to the case of PUSCH cross-carrier transmission, and similar implementation processes will not be elaborated.

[0349] In the embodiment of this application, another optional implementation manner is provided for step S102. Specifically, segmented transmission of PDSCH or PUSCH scheduled by DCI can be performed on at least two BWPs respectively.

[0350] For the embodiments of this application, multiple carriers are configured within a serving cell, and a single transport block (TB) can be transmitted across multiple carriers within the cell, that is, resources are allocated on multiple carriers for transmitting this TB. The transmission signals on each carrier can be regarded as different segments of the same TB. That is, rate matching is performed based on all the resources allocated across multiple carriers as a whole for mapping, and the coded and modulated signal of a single TB is segmented and mapped to different carriers. The specific process (corresponding to steps S101 and S102) can be described as follows:

[0351] Step SB1: The UE detects a downlink control information (DCI) that is used to schedule a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) transmitted across multiple bandwidth parts (BWPs), i.e., across multiple carriers. The DCI includes time-domain resource allocation information and frequency-domain resource allocation information for multiple BWPs.

[0352] Step SB2: For the PDSCH, the UE receives different segment transmissions of the same TB on multiple BWPs (i.e., multiple carriers) respectively; for the case of the PUSCH, the UE transmits different segment transmissions of the same TB on multiple BWPs (i.e., multiple carriers) respectively.

[0353] Taking the PDSCH as an example, the segmented transmission method means that a part of the PDSCH signal is transmitted on the time-frequency domain resources allocated to each carrier. That is, the PDSCH transmission signal is divided into N segments and mapped to the time-frequency domain resources of N carriers respectively. The transmission signal on each carrier cannot be independently decoded, and only after concatenating the transmission signals on all carriers can decoding be performed. That is, the signal of the transmission block of the PDSCH after coding and modulation is segmented and mapped to different carriers.

[0354] In the embodiments of this application, for the case of segmented transmission of the PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the process of mapping the PDSCH or PUSCH scheduled by DCI to physical resources can be performed by at least one of the following methods:

[0355] Method 1: Start from the BWP with the lowest frequency and perform the first mapping within the BWP in the order of frequency domain first and then time domain, and repeat the first mapping within the remaining BWPs.

[0356] As Figure 5 shown, this method can be understood as mapping per BWP or per carrier, that is, segmented mapping to the time-frequency resource blocks allocated to each BWP (or each carrier). Optionally, start mapping from the BWP (or carrier) with the lowest frequency. After all the resource elements (REs) allocated on this BWP (or carrier) are mapped, then map to the next carrier with the lowest frequency until all BWPs (or carriers) are mapped. On the time-frequency resource blocks allocated to each BWP (or each carrier), mapping can be performed in the order of frequency domain first and then time domain.

[0357] Method 2: Starting from the first time unit, perform the second mapping in the time unit in frequency order, and repeat the second mapping in the remaining time units.

[0358] That is, perform frequency-domain mapping first and then time-domain mapping on multiple BWPs or carriers, as Figure 6 shown. Optionally, the above time unit may refer to a symbol. That is, start mapping from the RE with the lowest frequency in the first symbol until all the REs on all carriers in this symbol are mapped, and then map the next symbol until all symbols are mapped.

[0359] Method 3: Starting from the RE with the lowest frequency, perform the third mapping in time order, and repeat the third mapping on the remaining REs.

[0360] That is, perform time-domain mapping first and then frequency-domain mapping on multiple BWPs or carriers, as Figure 7 shown. Optionally, the above time unit may refer to a symbol. That is, start mapping from the RE with the lowest frequency until all the symbols corresponding to this RE are mapped, and then map the next RE with the lowest frequency until all the REs on all BWPs or carriers are mapped.

[0361] In the embodiments of the present application, for the case of segmented transmission of PDSCH or PUSCH with DCI scheduling respectively performed on at least two BWPs, the second TBS of PDSCH or PUSCH transmitted on at least two BWPs may be determined based on at least one of the following:

[0362] Method 1: The total number of REs determined on at least two BWPs;

[0363] Taking PDSCH as an example, the second TBS may be determined according to the total number of REs allocated on all BWPs (or all carriers).

[0364] [[ID= twenty-seven ]] In one example, the number of PRBs allocated on different BWPs may be different, the number of symbols allocated on different BWPs may also be different, the DMRS patterns (patterns) used on different BWPs may also be different (that is, the number of DMRS REs per PRB on different BWPs may also be different), and the signaling overhead sizes configured on different BWPs may also be different. Here, the UE needs to determine the number of REs N RE,i on each BWP (or each carrier) respectively, and then use the sum of the RE numbers on all BWPs as the RE number N RE for determining the second TBS, that is N is the number of active BWPs (or the number of carriers) for transmitting one TB, N RE,iis the number of REs on the i-th active BWP (or the i-th carrier).

[0365] In another example, the number of PRBs allocated on different BWPs may be different, but the number of symbols allocated on different BWPs is the same, the DMRS pattern used on different BWPs is also the same (i.e., the number of DMRS REs per PRB on different BWPs is also the same), and the signaling overhead sizes are also the same. Here, the UE first determines the number of REs within a PRB based on and then determines the total number n of PRBs allocated on all BWPs PRB , that is where N is the number of active BWPs (or the number of carriers) for transmitting one TB, n PRB,i is the number of PRBs allocated on the i-th active BWP (or the i-th carrier), is the number of REs included in a PRB, such as is the number of PDSCH symbols allocated within a time slot, is the number of REs used for DMRS within each PRB, is the signaling overhead size configured by higher layer parameters. is the signaling overhead size configured by higher layer parameters. Then, based on N RE = min(156, N R ′ E ) * n PRB the number of REs is determined.

[0366] Method 2: Scaling factor corresponding to the second TBS.

[0367] The UE can multiply the total number of REs determined by Method 1 by a scaling factor, and use the obtained value as the number of REs N for determining the second TBS RE . Or multiply the TBS determined by Method 1 by a scaling factor, and use the obtained value as the TBS. Among them, the size of the scaling factor can be configured by higher layer signaling. Optionally, different active BWPs can be configured with different scaling factors.

[0368] In at least one of the above embodiments, the DCI for scheduling cross-carrier transmission may indicate time-frequency domain resource allocation information on multiple active BWPs (i.e., multiple carriers), where the time-domain resource allocation information of PDSCH or PUSCH transmitted on at least two BWPs included in the DCI includes at least one of the following situations:

[0369] (1) At least two BWPs share time-domain resource allocation information, that is, the time-domain resources allocated on multiple active BWPs (or multiple carriers) are exactly the same, such as Figure 8 shown, including but not limited to the number of allocated time slots and the time slot positions, as well as the number of allocated symbols and the symbol positions within each time slot, that is, the time slots or symbols where the resources allocated on multiple active BWPs (or multiple carriers) are located are exactly the same, and the time-domain resource indication field in the existing DCI can be reused.

[0370] (2) At least two BWPs share first time-domain resource allocation information, and the second time-domain resource allocation information other than the first time-domain resource allocation information is configured separately for at least two BWPs, that is, each BWP among at least two BWPs shares some identical time-domain resource allocation information. The time-domain resources allocated on multiple active BWPs (or multiple carriers) can be different, but can share some identical time-domain resource allocation indication information. Optionally, multiple active BWPs (or multiple carriers) can share at least one of the same number of time slots, time slot positions, number of symbols, and symbol positions. For example, the first time-domain resource allocation information includes the number of time units allocated on the BWP; and, the second time-domain resource allocation information includes the positions of the time units allocated on the BWP, that is, the number of time slots or symbols allocated on multiple active BWPs (or multiple carriers) is the same, but the time slot or symbol positions can be different. The scheduling DCI can respectively indicate the position of the starting time slot or starting symbol for each active BWP (or each carrier), such as the scheduling DCI can respectively indicate the corresponding scheduling delay information, and / or, the scheduling DCI can respectively indicate the symbol positions within each allocated time slot for each active BWP (or each carrier), etc.

[0371] (3) The time-domain resources allocated on each of at least two BWPs are respectively indicated by different fields in the DCI, that is, the time-domain resources allocated on multiple active BWPs (or multiple carriers) can be different, and the time-domain resources on each active BWP (or each carrier) are independently allocated. Optionally, the time-domain resource allocation on each active BWP (or each carrier) can be respectively indicated. For example, the DCI includes a time-domain allocation indication field corresponding to different active BWPs.

[0372] In an optional implementation manner, the time-domain resource allocation information of the PDSCH or PUSCH transmitted on at least two BWPs included in the DCI may include: the number of time units allocated on at least two BWPs is the same, and the positions of the time units allocated on each of at least two BWPs are staggered from each other. That is, the time-domain resources allocated on multiple active BWPs (or multiple carriers) are completely staggered in time, such as Figure 9As shown. Optionally, they can be staggered in time in ascending order of frequency. The advantage of this scheme is that the UE does not need to support the ability to transmit or receive simultaneously on multiple carriers. The UE can perform transmission or reception on multiple carriers in sequence through radio frequency retuning, thereby obtaining a better frequency diversity gain. To reserve the processing time required for the UE to perform radio frequency retuning, a certain interval is reserved between the transmission signals of two adjacent carriers, that is, a certain interval is reserved between the time domain resources of two adjacent carriers. Optionally, there is the same first preset interval between the time unit positions of every two adjacent BWPs; wherein, the first preset interval is determined by at least one of the following methods: predefined, reported by the UE, preconfigured by higher layer signaling, indicated by DCI. The UE can switch from the BWP where the time unit before the first preset interval is located to the BWP where the time unit after the first preset interval is located within the first preset interval to continue the transmission of the PDSCH or PUSCH scheduled by DCI, that is, the UE can perform radio frequency retuning within the first preset interval to switch from one BWP to another BWP among at least two BWPs to perform the transmission of the PDSCH or PUSCH scheduled by DCI. Optionally, in this scheme, the scheduling DCI can respectively indicate the position of the first time unit allocated on each BWP (or carrier).

[0373] In at least one of the above embodiments, the DCI for scheduling cross-carrier transmission can indicate the frequency domain resource allocation information on multiple active BWPs (i.e., multiple carriers), wherein, the frequency domain resource allocation information on at least two BWPs included in the DCI includes at least one of the following situations:

[0374] (1) At least two BWPs share the frequency domain resource allocation information, that is, the number of PRBs and / or the PRB positions allocated on multiple active BWPs (or multiple carriers) are exactly the same.

[0375] (2) At least two BWPs share the first frequency domain resource allocation information, and the second frequency domain resource allocation information other than the first frequency domain resource allocation information is configured separately for at least two BWPs, that is, each of at least two BWPs shares some of the same frequency domain resource allocation information, and the number of PRBs or the PRB positions allocated on multiple active BWPs (or multiple carriers) can be different. For example, the number of PRBs allocated on multiple active BWPs (or multiple carriers) is the same, but the PRB positions are different. The scheduling DCI indicates the number of allocated PRBs, that is, this number of PRBs is allocated on each BWP (or each carrier). In addition, the scheduling DCI can also respectively indicate the starting PRB position (assuming the allocated PRBs are continuous) or the specific PRB position (assuming the allocated PRBs can be discontinuous) on each active BWP (or each carrier).

[0376] (3) The frequency-domain resources allocated on each of at least two BWPs are indicated separately by different fields in the DCI, that is, the frequency-domain allocations on multiple active BWPs (or multiple carriers) are separately indicated by different indication fields. For example, the scheduling DCI includes N frequency-domain resource allocation indication fields, corresponding to N active BWPs (or N carriers) respectively, and the number of bits of each frequency-domain resource allocation indication field is determined by the respective BWP bandwidth.

[0377] (4) The frequency-domain resources allocated on at least two BWPs are jointly indicated by the same field in the DCI, that is, the frequency-domain resource allocations on multiple active BWPs (or multiple carriers) are jointly indicated. The so-called joint indication means that the frequency-domain resource allocation is indicated based on the total bandwidth after aggregation of multiple active BWPs, that is, the PRBs within multiple active BWPs are uniformly numbered, and / or the resource block groups (Resource Block Group, RBG) within multiple active BWPs are uniformly numbered. For example, the PRBs (or RBGs) in the first active BWP at a low frequency position are numbered in order from low frequency to high frequency as #0 to #(N1-1), that is, there are a total of N1 PRBs (or RBGs) on this active BWP, and then the RBGs in the next active BWP at a low frequency position are numbered in order from low frequency to high frequency as #N1 to #(N2+N1-1), that is, there are a total of N2 PRBs (or RBGs) on this active BWP, and so on for other active BWPs until all the PRBs or RBGs of all active BWPs are numbered. Here, the number of PRBs or RBGs included in each active BWP can be different. The scheduling DCI can indicate some of the uniformly numbered PRBs or RBGs through the existing frequency-domain resource indication method, and the number of bits used to indicate the frequency-domain resource allocation is determined based on the aggregated total bandwidth. This scheme can also be called the frequency-domain resource allocation based on aggregated bandwidth.

[0378] (5) The frequency-domain resources allocated on a part of at least two BWPs are indicated by DCI, and the frequency-domain resources allocated on another part of at least two BWPs are predefined or preconfigured by higher-layer signaling. That is, among multiple active BWPs (or multiple carriers), all PRBs within some specific active BWPs are allocated for transmission, and the scheduling DCI does not need to indicate the frequency-domain resource allocation on these specific active BWPs, but only needs to indicate the frequency-domain resource allocation information on other active BWPs. These specific active BWPs can be the primary active BWP (i.e., the first BWP), the active BWP with the smallest index number, the active BWP on the anchored carrier, the active BWP on the carrier with index number #0, the active BWP on the carrier with the smallest index number among multiple carriers, or the active BWP on the carrier with the lowest frequency, the secondary active BWP (i.e., the second BWP), the active BWP with a bandwidth less than the first preset value, the active BWP with a bandwidth greater than the second preset value, or the preconfigured active BWP, etc., but not limited thereto.

[0379] In an alternative embodiment, the case where the frequency-domain resources allocated on at least two BWPs are jointly indicated by the same field in DCI may specifically include: at least one of the PRBs, VRBs (Virtual Resource Blocks), and RBGs on at least two BWPs is uniformly numbered.

[0380] As an example, in the frequency-domain resource allocation type (Resource Allocation Type, RA Type) 0, the scheduling DCI indicates the allocated RBG through a bitmap, which can support continuous or discrete RBG resource allocation, and one RBG includes M consecutive PRBs.

[0381] For the frequency-domain resource allocation method based on the aggregated bandwidth, in order to coexist with other scheduled UEs on each active BWP (where these other scheduled UEs may have only one active BWP), the RBG size on each active BWP can be different, and the same RBG cannot span carriers, that is, the RBGs at both ends of an active BWP may not be complete RBGs, that is, the number of PRBs included in the RBGs at both ends may not be M.

[0382] Optionally, the RBG size (i.e., the minimum granularity RBG size for the frequency-domain resource allocation based on the aggregated bandwidth) is determined by at least one of the following methods:

[0383] (1) Each of at least two BWPs divides the RBG based on the same RBG size, that is, all active BWPs use the same RBG size to allocate frequency-domain resources within the BWP. The RBG size is determined according to the bandwidth size of a specific BWP among at least two BWPs. That is, the RBG size can be determined according to the bandwidth size (i.e., the number of PRBs included) of one specific active BWP, or the RBG size is determined according to the total bandwidth size of at least two BWPs. That is, the RBG size can be determined according to the total bandwidth size of all active BWPs (i.e., the sum of the number of PRBs included in all active BWPs). For example, the RBG size is determined based on Table 1 below. Among them, the specific BWP is predefined or preconfigured by higher-layer signaling. The specific BWP can be the primary active BWP (i.e., the first BWP), the active BWP on the anchored carrier, the active BWP on the carrier with the smallest index number, or the preconfigured active BWP, etc., but not limited thereto.

[0384] (2) Each of at least two BWPs divides the RBG based on different RBG sizes. The RBG size is determined separately according to the bandwidth size of each BWP. That is, each active BWP uses a different RBG size to allocate frequency-domain resources within its own BWP. Optionally, each active BWP determines the RBG size according to its own bandwidth size (i.e., the number of PRBs included). For example, the RBG size is determined based on Table 1 below.

[0385] BWP Size Configuration 1 Configuration 2 1–36 2 4 37–72 4 8 73–144 8 16 145–275 16 16

[0386] Table 1: Determining RBG Based on BWP Size

[0387] It can be understood that this Table 1 can be used to determine the RBG size according to the total bandwidth size of all active BWPs, and can also be used to determine the corresponding RBG size according to the bandwidth size of each BWP. Since the bandwidth sizes are different, the determined RBG sizes may also be different.

[0388] In an optional implementation manner, considering compatibility with other UEs transmitting based on one active carrier, the segmentation of the RBG on each active BWP should be aligned with the Carrier Resource Block (CRB) of the carrier where it is located. That is, the starting position of the RBG on each carrier should be aligned with the starting position of the CRB of the carrier where it is located. That is, the RBG division on each BWP starts from the carrier resource block CRB0 at the lowest frequency point of the carrier where it is located.

[0389] In another alternative embodiment, the RBG division on each BWP starts from the carrier resource block CRB0 at the lowest frequency point of the reference carrier, that is, the RBG on each BWP starts division based on the same CRB0, where the reference carrier is a predefined carrier in the carrier where each BWP is located.

[0390] In RA Type1, the scheduling DCI jointly indicates the starting VRB position and the number of consecutive VRBs in the way of the Start and Length Indicator Value (SLIV). There are two mapping methods between VRB and PRB. The first mapping method is non-interleaved mapping, that is, a group of consecutive VRBs corresponds to a group of consecutive PRBs, and resource scheduling only supports the allocation of consecutive PRBs. The second mapping method is interleaved mapping, that is, a group of consecutive VRBs may correspond to a group of discrete PRBs, and resource scheduling can support the allocation of consecutive or discrete PRBs. For the case where the frequency-domain resources allocated on each BWP among the above at least two BWPs are jointly indicated by the same field in the DCI, the mapping method between VRB and PRB includes at least one of the following:

[0391] (1) Non-interleaved mapping, that is, VRB and PRB are mapped one by one in sequence, that is, the VRB numbered #n corresponds to the PRB numbered #n, and the numbers of the VRB and the corresponding PRB are exactly the same;

[0392] (2) Within the respective bandwidths of each BWP, the VRBs and PRBs are interleaved and mapped, that is, the interleaving and mapping are limited within the carrier. The VRBs and PRBs are interleaved and mapped, that is, a set of consecutive VRBs may correspond to a set of discrete PRBs, but this interleaving is limited within the carrier and cannot cross carriers. For example, assume there are 3 active BWPs. The PRBs on the first active BWP are numbered #0 to #(N1 - 1), that is, there are a total of N1 PRBs on the first active BWP. The PRBs on the second active BWP are numbered #N1 to #(N2 + N1 - 1), that is, there are a total of N2 PRBs on the second active BWP. The PRBs on the third active BWP are numbered #(N1 + N2) to #(N3 + N2 + N1 - 1), that is, there are a total of N3 PRBs on the third active BWP. Then the VRBs and PRBs can be mapped in segments, that is, the VRBs numbered within #0 to #(N1 - 1) correspond to the PRBs numbered within #0 to #(N1 - 1), the VRBs numbered within #N1 to #(N2 + N1 - 1) correspond to the PRBs numbered within #N1 to #(N2 + N1 - 1), and the VRBs numbered within #(N1 + N2) to #(N3 + N2 + N1 - 1) correspond to the PRBs numbered within #(N1 + N2) to #(N3 + N2 + N1 - 1). However, the VRB numbered #m does not necessarily correspond to the PRB numbered #m, that is, the VRBs and PRBs are interleaved and mapped in segments, and the segmented interval is within the carrier. Within each carrier, the mapping rule can reuse the mapping rule of the existing system.

[0393] (3) Within the total bandwidth of at least two BWPs, the VRBs and PRBs are interleaved and mapped, that is, the cross - carrier interleaving and mapping. The VRBs and PRBs are interleaved and mapped, that is, a set of consecutive VRBs may correspond to a set of discrete PRBs, and this interleaving can cross carriers. For example, the mapping rule can reuse the mapping rule of the existing system, and the difference is that the aggregated bandwidth of multiple carriers can be treated as a carrier with a larger bandwidth.

[0394] In the embodiments of this application, the PDSCH transmitted on at least two BWPs includes SPS - PDSCH (Semi - Persistent Scheduling Physical Downlink Shared Channel), and the PUSCH transmitted on at least two BWPs includes Type 1 CG - PUSCH (Configured Grant Physical Uplink Shared Channel) and Type 2 CG - PUSCH.

[0395] That is, the TB without dynamic scheduling can be configured to transmit across multiple carriers. For example, CG-PUSCH can be configured to transmit across multiple carriers, and SPS-PDSCH can also be configured to transmit across multiple carriers. For example, CG-PUSCH Type 1 configures resource allocation on multiple BWPs (or multiple carriers) for transmitting the same CG-PUSCH (i.e., the same transport block) through high-layer signaling, CG-PUSCH Type 2 indicates resource allocation on multiple BWPs (or multiple carriers) for transmitting the same CG-PUSCH (i.e., the same transport block) through an activated DCI, and SPS-PDSCH indicates resources on multiple BWPs (or multiple carriers) for transmitting the same SPS-PDSCH (i.e., the same transport block) through an activated DCI.

[0396] For the CG-PUSCH that transmits across multiple carriers, the corresponding first HARQ (Hybrid Automatic Repeat Request) process number (i.e., the ID (Identity document) number of the HARQ process) can be determined by the following formula: HARQ Process ID = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + harq-ProcID-Offset

[0397] Where, modulo represents modulo operation, floor represents rounding down, periodicity is the transmission period of the pre-configured CG-PUSCH, nrofHARQ-Processes is the number of pre-configured HARQ processes for CG-PUSCH transmission, harq-ProcID-Offset is the pre-configured offset for determining the HARQ process ID, CURRENT_symbol = (SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slot number in the frame × numberOfSymbolsPerSlot + symbol number in the slot), where SFN is the system frame number (SystermFrame Number), numberOfSlotsPerFrame is the number of time slots included in a radio frame, numberOfSymbolsPerSlot is the number of OFDM symbols included in a time slot, slot number in the frame is the index number of the time slot where CG-PUSCH transmission is located in the radio frame, and symbol number in the slot is the index number of the starting symbol of CG-PUSCH transmission in the time slot.

[0398] Optionally, if the positions of the first OFDM symbols allocated for transmitting CG-PUSCH on each carrier are not exactly the same (such as the time-domain interleaved resource allocation method introduced above), then for CG-PUSCH, the corresponding first HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs, that is, the above symbolnumber in the slot refers to the index number of the earliest first OFDM symbol allocated on multiple carriers in the time slot, and the above slot number in the frame refers to the index number of the time slot where the earliest first OFDM symbol allocated on multiple carriers is located in the radio frame.

[0399] Optionally, regardless of whether the first OFDM symbol position allocated for transmitting CG-PUSCH on each carrier is the same, for CG-PUSCH, the corresponding first HARQ process number is determined based on the first time unit (such as an OFDM symbol) allocated on a preset BWP among at least two BWPs. That is, the above-mentioned symbol number in the slot refers to the index number of the first OFDM symbol allocated on the preset BWP in the time slot, and the above-mentioned slot number in the frame refers to the index number of the time slot where the first OFDM symbol allocated on the preset BWP is located in the radio frame. Among them, the preset BWP is predefined or preconfigured. For example, the preset BWP can be the first BWP in the previous text, or the preset BWP can be a preconfigured BWP among the above-mentioned at least two BWPs.

[0400] For the SPS-PDSCH transmitted across multiple carriers, its corresponding second HARQ process number can be determined by the following formula:

[0401] HARQ Process ID = [floor(CURRENT_slot × 10 / (numberOfSlotsPerFrame × periodicity))] modulo nrofHARQ-Processes + harq-ProcID-Offset

[0402] Among them, modulo represents the modulo operation, floor represents rounding down, periodicity is the preconfigured transmission period of the SPS-PDSCH, nrofHARQ-Processes is the number of HARQ processes preconfigured for SPS-PDSCH transmission, harq-ProcID-Offset is the preconfigured offset for determining the HARQ process ID, numberOfSlotsPerFrame is the number of time slots included in a radio frame, CURRENT_slot = [(SFN × numberOfSlotsPerFrame) + slot number in the frame], where SFN is the system frame number (Systerm Frame Number), and slot number in the frame is the index number of the time slot where the SPS-PDSCH transmission is located in the radio frame.

[0403] Optionally, if the time slots allocated for transmitting SPS-PDSCH on each carrier are not exactly the same (such as the time-domain interleaved resource allocation method introduced above), then for SPS-PDSCH, the corresponding second HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs. That is, the above-mentioned slot number in the frame refers to the index number of the earliest time slot among the resources allocated on multiple carriers within the radio frame.

[0404] Optionally, regardless of whether the first time slot positions allocated for transmitting SPS-PDSCH on each carrier are the same, for SPS-PDSCH, the corresponding second HARQ process number is determined based on the first time unit allocated on a preset BWP among at least two BWPs. For example, the above-mentioned slot number in the frame refers to the index number of the first time slot allocated on the preset BWP within the radio frame. Herein, the preset BWP is predefined or preconfigured. For example, the preset BWP can be the first BWP in the foregoing text, or the preset BWP can be a preconfigured BWP among at least two BWPs.

[0405] In the embodiments of the present application, if any one of the at least two BWPs is deactivated, the method performed by the UE further includes at least one of the following:

[0406] (1) Stop transmitting SPS-PDSCH or CG-PUSCH on at least two BWPs, and perform at least one of clearing the downlink allocation of SPS-PDSCH, clearing the uplink grant of type 2 CG-PUSCH, and aborting the uplink grant of type 1 CG-PUSCH;

[0407] That is, if SPS-PDSCH or CG-PUSCH is configured to be transmitted on N BWPs, and one of the N BWPs is deactivated, that is, not all of the N BWPs are activated, then SPS-PDSCH or CG-PUSCH cannot be transmitted. The MAC layer of the UE can clear the downlink allocation of SPS-PDSCH, and / or clear the uplink grant of CG-PUSCH Type 2, and / or abort the uplink grant of CG-PUSCH Type 1.

[0408] (2) On the non-deactivated BWPs among at least two BWPs, perform the transmission of SPS-PDSCH or CG-PUSCH.

[0409] That is, if SPS-PDSCH or CG-PUSCH is configured to be transmitted on N BWPs, and one of the N BWPs, or no more than a preset number of BWPs, is deactivated, that is, not all of the N BWPs are activated, then SPS-PDSCH or CG-PUSCH cannot be transmitted on the deactivated BWPs, but SPS-PDSCH or CG-PUSCH can be transmitted on the activated BWPs. This scheme can correspond to the cross-carrier transmission mode based on repeated transmission introduced in the previous text. That is, when some BWPs are deactivated, it does not affect the transmission of SPS-PDSCH or CG-PUSCH on other activated BWPs, and partial repeated transmission may still achieve the effect of correct decoding. For this scheme, after all of the N activated BWPs are deactivated, the MAC layer of the UE clears the downlink allocation of SPS-PDSCH, and / or clears the uplink grant of CG-PUSCH Type 2, and / or aborts the uplink grant of CG-PUSCH Type 1.

[0410] Based on at least one embodiment of the above-mentioned transmission of one TB across multiple activated BWPs (or multiple carriers), an alternative implementation manner is provided for step S102. Specifically, it may include: determining at least one scheduled BWP among at least two BWPs according to the indication of the resource indication field in the DCI; and performing the transmission of the PDSCH or PUSCH scheduled by the DCI on the at least one scheduled BWP.

[0411] The scheduling DCI can schedule one TB (such as one PDSCH or one PUSCH) to be transmitted on X BWPs, where 1 ≤ X ≤ N, and N is the number of activated BWPs. That is, the scheduled BWPs can be one or more of the activated BWPs, and the number of scheduled BWPs cannot exceed the number of activated BWPs.

[0412] Optionally, the DCI includes an indication field for indicating which of the N activated BWPs are scheduled. For example, the scheduling DCI may include indication information related to the scheduled BWPs and / or the carriers where the scheduled BWPs are located. In addition, the DCI further includes X resource indication fields, corresponding to the X scheduled BWPs respectively, and each resource indication field is used to indicate the time domain and / or frequency domain resource allocation on the corresponding BWP.

[0413] For example, assume that there are a total of 4 active BWPs. For the case of scheduling only one active BWP, the scheduling DCI may include a 2-bit indication field for indicating one of the 4 active BWPs to be scheduled; or, for the case of scheduling one or more active BWPs, the scheduling DCI may include a 4-bit indication field for indicating which of the 4 active BWPs are scheduled in the form of a bitmap, that is, each bit corresponds to an active BWP. When the indication value is "1", it means the corresponding active BWP is scheduled, and when the indication value is "0", it means the corresponding active BWP is not scheduled; or, for the case of scheduling one or more active BWPs, the scheduling DCI may include an indication field for indicating the index number of the scheduled BWP set, where the BWP set is pre-configured by higher-layer signaling.

[0414] Optionally, whether an active BWP is scheduled is indicated by its corresponding resource indication field. For example, the DCI includes N resource indication fields, corresponding to N active BWPs respectively. Each resource indication field is used to indicate the time-domain and / or frequency-domain resource allocation on the corresponding BWP. When the value of a resource indication field is a preset status value (for example, assuming the resource indication field includes 7 bits, the preset status value can be "0000000" or "1111111"), it indicates that the corresponding BWP is not scheduled for transmission, that is, the transmission on some of the active BWPs is dynamically scheduled through the preset status value of the resource indication field.

[0415] In an alternative embodiment, for at least one of the above embodiments where one TB is transmitted across multiple active BWPs (or multiple carriers), certain requirements may be imposed on the multiple active BWPs (or multiple carriers) for transmission. For example, in the case of at least one of the following conditions for N active BWPs (or N carriers), the transmission of the same PDSCH or PUSCH scheduled by DCI is supported on N active BWPs (or N carriers):

[0416] (1) The frequency-domain interval between two carriers with adjacent frequency domains among at least two BWPs does not exceed a first preset bandwidth, that is, the frequency-domain interval between two carriers with similar frequency domains among N active BWPs (or N carriers) cannot exceed the first preset bandwidth;

[0417] (2) The bandwidth from the lowest frequency to the highest frequency among at least two BWPs does not exceed a second preset bandwidth, that is, the overall bandwidth of N active BWPs (or N carriers) cannot exceed the second preset bandwidth. The overall bandwidth refers to the bandwidth occupied between the lowest frequency and the highest frequency of N active BWPs (or N carriers);

[0418] (3) The sum of the bandwidths of at least two BWPs does not exceed a third preset bandwidth, that is, the sum of the bandwidths of N active BWPs (or N carriers) cannot exceed the third preset bandwidth.

[0419] In an alternative embodiment, for at least one of the above embodiments in which one TB is transmitted across multiple active BWPs (or multiple carriers), if the scheduling DCI is transmitted on one of the multiple active BWPs, the method performed by the UE further includes: listening for the PDCCH corresponding to the DCI on a specific BWP among at least two BWPs. In other words, the UE listens for the PDCCH on one of the active BWPs, and does not need to listen for the PDCCH on all active BWPs. The specific BWP is predefined or preconfigured by higher layer signaling. Specifically, the active BWP on which the UE listens for the PDCCH may be at least one of the following cases:

[0420] (1) Listening for the PDCCH on a predefined active BWP among the multiple active BWPs. For example, the primary active BWP (i.e., the first BWP), the active BWP with the smallest index number, the active BWP on the anchored carrier, the active BWP on the carrier with index number #0, the active BWP on the carrier with the smallest index number among multiple carriers, or the active BWP on the carrier with the lowest frequency.

[0421] (2) Listening for the PDCCH on a preconfigured active BWP among the multiple active BWPs. For example, it is possible that the PDCCH transmission is configured on any of the active BWPs, depending on the base station configuration. Optionally, PDCCH transmission can be configured on only one of the multiple active BWPs.

[0422] In an alternative embodiment, for at least one of the above embodiments in which one TB is transmitted across multiple active BWPs (or multiple carriers), the UE may be separately configured with PDSCH transmission parameters or PUSCH transmission parameters on each active BWP. When the UE is scheduled for a PDSCH or PUSCH to be transmitted across multiple active BWPs, the configurations related to the PDSCH or PUSCH transmitted on at least two BWPs comply with at least one of the following configurations:

[0423] (1) The configuration related to the PDSCH or PUSCH on a specific BWP among at least two BWPs, where the specific BWP is predefined or preconfigured by higher layer signaling.

[0424] That is, the PDSCH (or PUSCH) transmitted across multiple active BWPs (or multiple carriers) conforms to the PDSCH configuration (or PUSCH configuration) on a predefined active BWP among the multiple active BWPs. For example, the primary active BWP (i.e., the first BWP), the active BWP with the smallest index number, the active BWP on the anchored carrier, the active BWP on the carrier with index number #0, the active BWP on the carrier with the smallest index number among the multiple carriers, or the active BWP on the carrier with the lowest frequency.

[0425] Alternatively, the PDSCH (or PUSCH) transmitted across multiple active BWPs (or multiple carriers) conforms to the PDSCH configuration (or PUSCH configuration) on a preconfigured active BWP among the multiple active BWPs. For example, it is configured through higher layer signaling for one of the multiple active BWPs, or indicated by scheduling DCI for one of the multiple active BWPs.

[0426] (2) Dedicated PDSCH or PUSCH related configuration, where the dedicated PDSCH or PUSCH related configuration is different from the PDSCH or PUSCH related configuration on each of at least two BWPs.

[0427] That is, the PDSCH (or PUSCH) transmitted across multiple active BWPs (or multiple carriers) conforms to the dedicated PDSCH configuration (or PUSCH configuration), and the dedicated PDSCH configuration (or PUSCH configuration) is different from the PDSCH (or PUSCH configuration) of each active BWP.

[0428] In an alternative implementation, for at least one embodiment of the above-mentioned one TB transmitted across multiple active BWPs (or multiple carriers), to consider the compatibility of DMRS with other UEs transmitted based on one active BWP, the DMRS signal sequences of PDSCH or PUSCH on each carrier are generated separately. Optionally, the DMRS signal sequences transmitted on each BWP are generated separately based on at least one of the following:

[0429] (1) The index number (index) of the CRB corresponding to the PRB where the DMRS is located. Here, the CRB index refers to the number of this PRB relative to the first resource block (i.e., CRB#0) of the carrier where it is located. That is, the index number of the CRB starts numbering from CRB0 of the carrier where the DMRS is located, or the index number of the CRB starts numbering from CRB0 of the carrier with the lowest frequency among at least two BWPs.

[0430] (2) The index number of the carrier where the DMRS is located.

[0431] (3) The dedicated parameters corresponding to the BWP where the DMRS is located. The dedicated parameters are configured separately for each BWP, that is, the parameters for generating the DMRS signal sequence are configured separately for each carrier.

[0432] The method executed by the UE provided in the embodiments of the present application enables multi-carrier configuration within a serving cell, which is more flexible than aggregating multiple carriers by aggregating multiple serving cells, can simplify the system, and save signaling overhead.

[0433] In the embodiments of the present application, a method executed by a base station in a communication system is also provided, as Figure 10 shown, the method includes:

[0434] Step S201: Transmit DCI. The DCI includes scheduling information of the PDSCH or PUSCH transmitted on at least two BWPs. The scheduling information includes time-domain resource allocation information and frequency-domain resource allocation information. Among them, the frequency-domain resource allocation information includes the frequency-domain resource allocation information on at least two BWPs;

[0435] Step S202: On at least two BWPs, perform the transmission of the PDSCH or PUSCH scheduled by the DCI;

[0436] Optionally, the frequency-domain resources included in at least two BWPs do not overlap.

[0437] Optionally, at least two BWPs are on different carriers respectively.

[0438] Optionally, the carriers where at least two BWPs are located are configured in the same serving cell.

[0439] Optionally, at least two BWPs include a first BWP and at least one second BWP. At least two BWPs include at least one of the following situations:

[0440] The first BWP and the second BWP share the transmission configuration of the PDSCH and / or PUSCH;

[0441] The first BWP and the second BWP share the configuration of the first transmission parameters of the PDSCH and / or PUSCH, and the second transmission parameters other than the first transmission parameters are configured separately for the first BWP and the second BWP;

[0442] Optionally, the first BWP includes at least one of the following:

[0443] The first BWP is the BWP on the anchor carrier;

[0444] The first BWP is the BWP on the carrier with the index number zero;

[0445] The first BWP is the BWP on the carrier with the smallest index number;

[0446] The first BWP is the BWP on the carrier with the lowest frequency;

[0447] The first BWP is the BWP indicated by higher layer signaling.

[0448] Optionally, the first BWP is used to transmit the physical control channel and the physical shared channel, and the second BWP is used to transmit the physical shared channel.

[0449] Optionally, step S201 includes at least one of the following:

[0450] Transmit the PDCCH on the first preset BWP among at least two BWPs, where the PDCCH includes scheduling information on at least two BWPs;

[0451] Receive the PUCCH on the second preset BWP among at least two BWPs, where the PUCCH includes uplink control information related to at least two BWPs;

[0452] Wherein, the first preset BWP and / or the second preset BWP is the first BWP, or the first preset BWP and / or the second preset BWP is configured as one of at least two BWPs.

[0453] Optionally, on at least two BWPs, performing the transmission of the PDSCH or PUSCH scheduled by DCI includes at least one of the following methods:

[0454] On at least two BWPs, respectively perform repeated transmission of the PDSCH or PUSCH scheduled by DCI;

[0455] On at least two BWPs, respectively perform segmented transmission of the PDSCH or PUSCH scheduled by DCI.

[0456] Optionally, for the case of respectively performing repeated transmission of the PDSCH or PUSCH scheduled by DCI on at least two BWPs, the method further includes:

[0457] Determine the first TBS of the PDSCH or PUSCH transmitted on at least two BWPs based on at least one of the following:

[0458] The average number of REs determined on at least two BWPs;

[0459] The maximum value among the number of REs respectively determined on each of at least two BWPs;

[0460] The minimum value among the number of REs respectively determined on each of at least two BWPs;

[0461] The number of REs determined on a preset BWP among at least two BWPs;

[0462] The scaling factor corresponding to the first TBS.

[0463] Optionally, for the case of performing repeated transmission of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the method further includes:

[0464] Determining the RVs transmitted on each of at least two BWPs by at least one of the following methods:

[0465] The RVs transmitted on at least two BWPs are the same;

[0466] The RVs transmitted on each of at least two BWPs are different;

[0467] The RVs transmitted on each of at least two BWPs are different, and each RV is determined by the RV sequence. Each of at least two BWPs cyclically corresponds to each RV in the RV sequence in turn;

[0468] The RVs transmitted on each of at least two BWPs are different, and each RV is determined by the RV sequence and the starting RV. Each of at least two BWPs starts from the starting RV and cyclically corresponds to each RV in the RV sequence in turn.

[0469] Optionally, the RV sequence is {#0, #1, #2, #3} or {#0, #2, #3, #1}.

[0470] Optionally, for the case of performing segmented transmission of PDSCH or PUSCH scheduled by DCI on at least two BWPs respectively, the method further includes:

[0471] Performing the process of mapping PDSCH or PUSCH scheduled by DCI to physical resources by at least one of the following methods:

[0472] Starting from the BWP with the lowest frequency, performing the first mapping in the BWP in the order of frequency domain first and then time domain, and repeating the first mapping in the remaining BWPs;

[0473] Starting from the first time unit, performing the second mapping in the time unit in the order of frequency, and repeating the second mapping in the remaining time units;

[0474] Starting from the RE with the lowest frequency, performing the third mapping in the order of time, and repeating the third mapping on the remaining REs.

[0475] Optionally, for the case of segmented transmission of PDSCH or PUSCH that is DCI-scheduled on at least two BWPs respectively, the method further includes:

[0476] Determining a second transport block size (TBS) of PDSCH or PUSCH transmitted on at least two BWPs based on at least one of the following:

[0477] The total number of resource elements (REs) determined on at least two BWPs;

[0478] The scaling factor corresponding to the second TBS.

[0479] Optionally, the time-domain resource allocation information of PDSCH or PUSCH transmitted on at least two BWPs included in the DCI includes at least one of the following cases:

[0480] At least two BWPs share the time-domain resource allocation information;

[0481] At least two BWPs share first time-domain resource allocation information, and second time-domain resource allocation information other than the first time-domain resource allocation information is configured separately for at least two BWPs;

[0482] The time-domain resources allocated on each of at least two BWPs are indicated separately through different fields in the DCI.

[0483] Optionally, the first time-domain resource allocation information includes the number of time units allocated on the BWP; and,

[0484] The second time-domain resource allocation information includes the position of the time units allocated on the BWP.

[0485] Optionally, the time-domain resource allocation information of PDSCH or PUSCH transmitted on at least two BWPs included in the DCI includes: the number of time units allocated on each of at least two BWPs is the same, and the positions of the time units allocated on each of at least two BWPs are completely staggered.

[0486] Optionally, the positions of the time units allocated on each of at least two BWPs are staggered from each other, including: there is the same first preset interval between the positions of the time units of every two adjacent BWPs.

[0487] Optionally, for the transmission of PDSCH or PUSCH that is DCI-scheduled on at least two BWPs, it includes: within the first preset interval, switching from the BWP where the time unit before the first preset interval is located to the BWP where the time unit after the first preset interval is located to continue the transmission of PDSCH or PUSCH that is DCI-scheduled.

[0488] Optionally, the frequency-domain resource allocation information on at least two BWPs included in the DCI includes at least one of the following cases:

[0489] At least two BWPs share the frequency-domain resource allocation information;

[0490] At least two BWPs share the first frequency-domain resource allocation information, and the second frequency-domain resource allocation information other than the first frequency-domain resource allocation information is configured separately for at least two BWPs;

[0491] The frequency-domain resources allocated on each of at least two BWPs are indicated separately through different domains in the DCI;

[0492] The frequency-domain resources allocated on at least two BWPs are jointly indicated through the same domain in the DCI;

[0493] The frequency-domain resources allocated on a part of at least two BWPs are indicated by the DCI, and the frequency-domain resources allocated on another part of at least two BWPs are predefined or preconfigured through higher-layer signaling.

[0494] Optionally, at least one of the physical resource blocks (PRBs), virtual resource blocks (VRBs), and resource block groups (RBGs) on at least two BWPs is numbered uniformly.

[0495] Optionally, the RBG size is determined by at least one of the following methods:

[0496] Each of at least two BWPs divides the RBG based on the same RBG size, and the RBG size is determined according to the bandwidth size of a specific BWP among at least two BWPs, or the RBG size is determined according to the total bandwidth size of at least two BWPs, where the specific BWP is predefined or preconfigured through higher-layer signaling;

[0497] Each of at least two BWPs divides the RBG based on a different RBG size, and the RBG size is determined separately according to the bandwidth size of each BWP.

[0498] Optionally, the division of the RBG on each BWP starts from the carrier resource block CRB0 at the lowest frequency point of the reference carrier, where the reference carrier is a predefined carrier in the carrier where each BWP is located.

[0499] Optionally, the mapping method between VRB and PRB includes at least one of the following:

[0500] Within the respective bandwidths of each BWP, the VRB and the PRB are interleaved and mapped;

[0501] Within the total bandwidth of at least two BWPs, VRBs and PRBs are interleaved and mapped.

[0502] Optionally, the PDSCH transmitted on at least two BWPs includes SPS-PDSCH, and the PUSCH transmitted on at least two BWPs includes type 1 CG-PUSCH and type 2 CG-PUSCH.

[0503] Optionally, for CG-PUSCH, the corresponding first HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs; or, the corresponding first HARQ process number is determined based on the first time unit allocated on a preset BWP among at least two BWPs; where the preset BWP is predefined or preconfigured.

[0504] Optionally, for SPS-PDSCH, the corresponding second HARQ process number is determined based on the earliest first time unit allocated on at least two BWPs; or, the corresponding second HARQ process number is determined based on the first time unit allocated on a preset BWP among at least two BWPs; where the preset BWP is predefined or preconfigured.

[0505] Optionally, if any one of at least two BWPs is deactivated, the method further includes at least one of the following:

[0506] Stop the transmission of SPS-PDSCH or CG-PUSCH on at least two BWPs;

[0507] On the non-deactivated BWP among at least two BWPs, perform the transmission of SPS-PDSCH or CG-PUSCH.

[0508] Optionally, when performing the transmission of DCI-scheduled PDSCH or PUSCH on at least two BWPs, it further includes:

[0509] Determine at least one scheduled BWP among at least two BWPs;

[0510] On at least one scheduled BWP, perform the transmission of DCI-scheduled PDSCH or PUSCH.

[0511] Optionally, the method further includes indicating at least one scheduled BWP among at least two BWPs through the resource indication field in DCI.

[0512] Optionally, when at least two BWPs meet at least one of the following conditions, perform the transmission of DCI-scheduled PDSCH or PUSCH on at least two BWPs:

[0513] The frequency domain interval between two carriers adjacent in the frequency domain of at least two BWPs does not exceed a first preset bandwidth;

[0514] The bandwidth between the lowest frequency and the highest frequency among at least two BWPs does not exceed a second preset bandwidth;

[0515] The sum of the bandwidths of at least two BWPs does not exceed a third preset bandwidth.

[0516] Optionally, the method further includes: transmitting a physical downlink control channel PDCCH corresponding to DCI on a specific BWP among at least two BWPs, where the specific BWP is predefined or preconfigured through higher layer signaling.

[0517] Optionally, the configurations related to PDSCH or PUSCH transmitted on at least two BWPs comply with at least one of the following configurations:

[0518] The configuration related to PDSCH or PUSCH on a specific BWP among at least two BWPs, where the specific BWP is predefined or preconfigured through higher layer signaling;

[0519] The dedicated configuration related to PDSCH or PUSCH, where the dedicated configuration related to PDSCH or PUSCH is different from the configuration related to PDSCH or PUSCH on each BWP among at least two BWPs.

[0520] Optionally, the DMRS signal sequence transmitted on each BWP is generated separately based on at least one of the following:

[0521] The index number of the CRB corresponding to the PRB where the DMRS is located, where the index number of the CRB is numbered starting from CRB0 of the carrier where the DMRS is located, or the index number of the CRB is numbered starting from CRB0 of the carrier where the BWP with the lowest frequency among at least two BWPs is located;

[0522] The index number of the carrier where the DMRS is located;

[0523] The dedicated parameter corresponding to the BWP where the DMRS is located, and the dedicated parameter is configured based on each BWP respectively.

[0524] Optionally, the above specific BWP is predefined and includes at least one of the following:

[0525] The specific BWP is the above first BWP;

[0526] The specific BWP is the above second BWP;

[0527] The specific BWP is the BWP on the anchored carrier;

[0528] The specific BWP is the BWP on the carrier with the index number zero;

[0529] The specific BWP is the BWP on the carrier with the smallest index number;

[0530] The specific BWP is the BWP on the carrier with the lowest frequency;

[0531] The specific BWP is the BWP with a bandwidth less than the first preset value;

[0532] The specific BWP is the BWP with a bandwidth greater than the second preset value.

[0533] The method executed by the base station provided in the embodiments of the present application enables multi-carrier configuration within a serving cell by deploying multiple carriers. Aggregating multiple carriers within a serving cell through at least two BWPs with non-overlapping frequency-domain resources is more flexible than aggregating multiple carriers by aggregating multiple serving cells, simplifies the system more, and saves signaling overhead. Additionally, the method executed by the base station provided in the embodiments of the present application supports configuring multiple downlink carriers and more than two uplink carriers within a serving cell. The biggest difference from SUL is that it can use multiple carriers within a serving cell to simultaneously perform the transmission of PDSCH or PUSCH scheduled by DCI, that is, it can transmit a transport block (TB) across multiple carriers within a serving cell, thereby obtaining frequency diversity gain or increasing the peak rate.

[0534] An electronic device is provided in the embodiments of the present application, including a transceiver configured to send and receive signals, and a processor coupled to the transceiver and configured to implement the steps of the foregoing method embodiments. Optionally, the electronic device may refer to a UE, and the processor is configured to implement the steps of the method embodiments executed by the UE. The detailed function description and the beneficial effects produced can be specifically referred to in the descriptions of the method embodiments executed by the UE in the foregoing text, and will not be elaborated here. Optionally, the electronic device may refer to a base station, and the processor is configured to implement the steps of the method embodiments executed by the base station. The detailed function description and the beneficial effects produced can be specifically referred to in the descriptions of the method embodiments executed by the base station in the foregoing text, and will not be elaborated here. In practical applications, a UE or a base station can be understood as different network nodes.

[0535] An electronic device is also provided in the embodiments of the present application. The electronic device includes a processor, and optionally, may further include a transceiver and / or a memory coupled to the processor. The processor is configured to execute the steps of the method provided in any optional embodiment of the present application.

[0536] Figure 11 A schematic structural diagram of an electronic device applicable to the embodiments of the present invention is shown, as Figure 11 shownFigure 11 The electronic device 4000 shown includes a processor 4001 and a memory 4003. Among them, the processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, and the transceiver 4004 can be used for data interaction between this electronic device and other electronic devices, such as data transmission and / or data reception, 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 does not constitute a limitation on the embodiments of the present application. Optionally, this electronic device can be a first network node, a second network node, or a third network node.

[0537] The processor 4001 can be a CPU (Central Processing Unit, central processor), a general-purpose processor, a DSP (Digital Signal Processor, data signal processor), an ASIC (Application Specific Integrated Circuit, application-specific integrated circuit), an FPGA (Field Programmable Gate Array, field programmable gate array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in connection with the disclosure of the present application. The processor 4001 can also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0538] The bus 4002 may include a path for transmitting information between the above components. The bus 4002 can be a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus or an EISA (Extended Industry Standard Architecture, extended industry standard architecture) bus, etc. The bus 4002 can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 11 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0539] The memory 4003 can be a ROM (Read Only Memory), or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory), or other types of dynamic storage devices that can store information and instructions. It can also be an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or other optical disc storage, optical disc 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 can be read by a computer, which is not limited herein.

[0540] The memory 4003 is used to store the computer program for implementing the embodiments of the present application and is controlled by the processor 4001 for execution. The processor 4001 is used to execute the computer program stored in the memory 4003 to implement the steps shown in the foregoing method embodiments.

[0541] The embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps and corresponding contents of the foregoing method embodiments can be implemented.

[0542] The embodiments of the present application also provide a computer program product, including a computer program. When the computer program is executed by a processor, the steps and corresponding contents of the foregoing method embodiments can be implemented.

[0543] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification, claims and the above drawings of the present application are used to distinguish similar objects and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in words.

[0544] It should be understood that although the flowcharts of the embodiments of the present application indicate each operation step by arrows, the execution order of these steps is not limited to the order indicated by the arrows. Unless there is a clear description in this article, in some implementation scenarios of the embodiments of the present application, the implementation steps in each flowchart can be executed in other orders according to requirements. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on the actual implementation scenario. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage among these sub-steps or stages can also be executed at different times respectively. In the scenario where the execution times are different, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and the embodiments of the present application do not limit this.

[0545] The above text and drawings are provided only as examples to assist the reader in understanding the present application. They are not intended and should not be construed as limiting the scope of the present application in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art based on the content disclosed herein that, without departing from the scope of the present application, changes can be made to the illustrated embodiments and examples, and other similar implementation means based on the technical idea of the present application can be adopted, which also fall within the protection scope of the embodiments of the present application.

Claims

1. A method performed by a user equipment UE in a communication system, characterized in that, Comprising: Receiving downlink control information DCI, where the DCI includes scheduling information of a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH transmitted on at least two bandwidth parts BWPs, and the scheduling information includes time-domain resource allocation information and frequency-domain resource allocation information, wherein the frequency-domain resource allocation information includes frequency-domain resource allocation information on the at least two BWPs; On the at least two BWPs, performing transmission of the PDSCH or PUSCH scheduled by the DCI.

2. The method according to claim 1, characterized in that, The at least two BWPs include a first BWP and at least one second BWP, and the at least two BWPs include at least one of the following cases: The first BWP and the second BWP share the transmission configuration of the PDSCH and / or PUSCH; The first BWP and the second BWP share the configuration of the first transmission parameter of the PDSCH and / or PUSCH, and the second transmission parameter other than the first transmission parameter is configured separately for the first BWP and the second BWP; Wherein, the first BWP includes at least one of the following: The first BWP is a BWP on an anchor carrier; The first BWP is a BWP on a carrier with an index number of zero; The first BWP is a BWP on a carrier with the smallest index number; The first BWP is a BWP on a carrier with the lowest frequency; The first BWP is a BWP indicated by higher-layer signaling.

3. The method according to claim 2, wherein Receiving DCI includes at least one of the following: Monitoring the PDCCH on a first preset BWP among the at least two BWPs, where the PDCCH includes scheduling information on the at least two BWPs; Sending a PUCCH on a second preset BWP among the at least two BWPs, where the PUCCH includes uplink control information related to the at least two BWPs; Wherein, the first preset BWP and / or the second preset BWP is the first BWP, or the first preset BWP and / or the second preset BWP is configured as one of the at least two BWPs.

4. The method according to any one of claims 1 to 3, characterized in that, The performing, on the at least two BWPs, of the transmission of the PDSCH or PUSCH scheduled by the DCI includes at least one of the following manners: On the at least two BWPs, respectively performing repeated transmission of the PDSCH or PUSCH scheduled by the DCI; On the at least two BWPs, respectively performing segmented transmission of the PDSCH or PUSCH scheduled by the DCI.

5. The method according to claim 4, wherein For the case of respectively performing repeated transmission of the PDSCH or PUSCH scheduled by the DCI on the at least two BWPs, the method further includes: Determining a first transport block size TBS of the PDSCH or PUSCH transmitted on the at least two BWPs based on at least one of the following: The average number of resource elements REs determined on the at least two BWPs; The maximum value among the RE numbers respectively determined on the at least two BWPs; The minimum value among the RE numbers respectively determined on the at least two BWPs; The RE number determined on a preset BWP among the at least two BWPs; The scaling factor corresponding to the first TBS.

6. The method according to claim 4, wherein For the case of performing repeated transmission of the PDSCH or PUSCH scheduled by the DCI on the at least two BWPs respectively, the method further includes: Determining the redundancy version RV transmitted on the at least two BWPs by at least one of the following methods: The RVs transmitted on the at least two BWPs are the same, and the RV is predefined, configured by higher layer signaling, or indicated by the DCI; The RVs transmitted on each of the at least two BWPs are different, and each RV is predefined, configured by higher layer signaling respectively, or indicated by the DCI respectively; The RVs transmitted on each of the at least two BWPs are different, and each RV is determined by an RV sequence, and each of the at least two BWPs cyclically corresponds to each RV in the RV sequence in turn; The RVs transmitted on each of the at least two BWPs are different, and each RV is determined by an RV sequence and a starting RV, and each of the at least two BWPs starts from the starting RV and cyclically corresponds to each RV in the RV sequence in turn; Wherein, the RV sequence is predefined or configured by higher layer signaling, and the starting RV is predefined, configured by higher layer signaling, or indicated by the DCI.

7. The method according to claim 4, wherein For the case of performing segmented transmission of the PDSCH or PUSCH scheduled by the DCI on the at least two BWPs respectively, the method further includes: Performing the process of mapping the PDSCH or PUSCH scheduled by the DCI to physical resources by at least one of the following methods: Starting from the BWP with the lowest frequency, performing a first mapping in the BWP in the order of frequency domain first and then time domain, and repeating the first mapping in the remaining BWPs; Starting from the first time unit, performing a second mapping in the time unit in the order of frequency, and repeating the second mapping in the remaining time units; Starting from the RE with the lowest frequency, performing a third mapping in the order of time, and repeating the third mapping on the remaining REs.

8. The method according to claim 4, characterized in that, For the case of performing segmented transmission of the PDSCH or PUSCH scheduled by the DCI on the at least two BWPs respectively, the method further includes: Determining the second TBS of the PDSCH or PUSCH transmitted on the at least two BWPs based on at least one of the following: The total number of REs determined on the at least two BWPs; The scaling factor corresponding to the second TBS.

9. The method according to any one of claims 1-8, characterized in that, The time domain resource allocation information of the PDSCH or PUSCH transmitted on the at least two BWPs included in the DCI includes at least one of the following situations: The at least two BWPs share the time domain resource allocation information; The at least two BWPs share the first time domain resource allocation information, and the second time domain resource allocation information other than the first time domain resource allocation information is configured separately for the at least two BWPs; The time domain resources allocated on each of the at least two BWPs are indicated separately by different domains in the DCI.

10. The method according to claim 9, characterized in that, The first time-domain resource allocation information includes the number of time units allocated on the BWP; and, The second time-domain resource allocation information includes the positions of the time units allocated on the BWP.

11. The method according to any one of claims 1 to 10, characterized in that The time-domain resource allocation information of PDSCH or PUSCH on at least two BWPs included in the DCI includes: The number of time units allocated on the at least two BWPs is the same, and the positions of the time units allocated on each BWP among the at least two BWPs are staggered from each other.

12. The method according to claim 11, wherein The positions of the time units allocated on each BWP among the at least two BWPs being staggered from each other includes: There is the same first preset interval between the time unit positions of every two adjacent BWPs; Wherein, the first preset interval is determined by at least one of the following methods: predefined, reported by the UE, pre-configured by high-layer signaling, indicated by the DCI.

13. The method according to claim 12, characterized in that, Performing the transmission of PDSCH or PUSCH scheduled by the DCI on the at least two BWPs includes: Within the first preset interval, switching from the BWP where the time unit before the first preset interval is located to the BWP where the time unit after the first preset interval is located to continue performing the transmission of PDSCH or PUSCH scheduled by the DCI.

14. The method according to any one of claims 1-13, characterized in that, The frequency-domain resource allocation information of at least two BWPs included in the DCI includes at least one of the following situations: The at least two BWPs share the frequency-domain resource allocation information; The at least two BWPs share the first frequency-domain resource allocation information, and the second frequency-domain resource allocation information other than the first frequency-domain resource allocation information is configured separately for the at least two BWPs; The frequency-domain resources allocated on each BWP among the at least two BWPs are indicated by different fields in the DCI respectively; The frequency-domain resources allocated on the at least two BWPs are jointly indicated by the same field in the DCI; The frequency-domain resources allocated on a part of the at least two BWPs are indicated by the DCI, and the frequency-domain resources allocated on another part of the at least two BWPs are predefined or pre-configured by high-layer signaling.

15. The method according to claim 14, wherein The frequency-domain resources allocated on the at least two BWPs being jointly indicated by the same field in the DCI includes: At least one of the physical resource blocks PRB, virtual resource blocks VRB, and resource block groups RBG on the at least two BWPs is uniformly numbered.

16. The method according to claim 15, wherein The RBG size is determined by at least one of the following methods: Each BWP among the at least two BWPs divides the RBG based on the same RBG size, and the RBG size is determined according to the bandwidth size of a specific BWP among the at least two BWPs, or the RBG size is determined according to the total bandwidth size of the at least two BWPs, where the specific BWP is predefined or pre-configured by high-layer signaling; Each BWP among the at least two BWPs divides the RBG based on different RBG sizes, and the RBG sizes are determined respectively according to the bandwidth size of each BWP.

17. The method according to claim 15, characterized in that, The mapping methods of VRB and PRB include at least one of the following: Within the respective bandwidths of each BWP, VRB and PRB are interleaved and mapped; Within the total bandwidth of the at least two BWPs, VRB and PRB are interleaved and mapped.

18. The method according to any one of claims 1 to 17, characterized in that, The configurations related to PDSCH or PUSCH transmitted on the at least two BWPs comply with at least one of the following configurations: The configurations related to PDSCH or PUSCH on a specific BWP among the at least two BWPs, where the specific BWP is predefined or preconfigured by higher layer signaling; Dedicated configurations related to PDSCH or PUSCH, where the dedicated configurations related to PDSCH or PUSCH are different from the configurations related to PDSCH or PUSCH on each BWP among the at least two BWPs.

19. The method according to any one of claims 1 to 18, characterized in that, The demodulation reference signal DMRS signal sequences transmitted on each BWP are respectively generated based on at least one of the following: The index number of the CRB corresponding to the PRB where DMRS is located, where the index number of the CRB is numbered starting from CRB0 of the carrier where DMRS is located, or the index number of the CRB is numbered starting from CRB0 of the carrier of the BWP with the lowest frequency among the at least two BWPs; The index number of the carrier where DMRS is located; Dedicated parameters corresponding to the BWP where DMRS is located, and the dedicated parameters are configured based on each BWP respectively.

20. A method performed by a base station in a communication system, characterized in that, Include: Transmit downlink control information DCI, where the DCI includes scheduling information of physical downlink shared channel PDSCH or physical uplink shared channel PUSCH transmitted on at least two bandwidth parts BWPs, and the scheduling information includes time domain resource allocation information and frequency domain resource allocation information, where the frequency domain resource allocation information includes the frequency domain resource allocation information on the at least two BWPs; On the at least two BWPs, perform the transmission of PDSCH or PUSCH scheduled by the DCI.

Images