CN113273240A

CN113273240A - Method for determining DCI (Downlink control information) of cross-carrier scheduling, terminal equipment and network equipment

Info

Publication number: CN113273240A
Application number: CN201980088755.2A
Authority: CN
Inventors: 沈嘉; 赵振山
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-01-11
Filing date: 2019-01-11
Publication date: 2021-08-17
Also published as: WO2020143050A1

Abstract

The application discloses a method for determining DCI (Downlink control information) of cross-carrier scheduling, terminal equipment, network equipment, a chip, a computer readable storage medium, a computer program product and a computer program, wherein the method comprises the following steps: determining the target size of Downlink Control Information (DCI) of cross-carrier scheduling; when DCI scheduling different cells in at least two cells is detected in one cell, the same target size of the DCI is adopted for DCI detection.

Description

Method for determining DCI (Downlink control information) of cross-carrier scheduling, terminal equipment and network equipment

Technical Field

The present application relates to the field of information processing technologies, and in particular, to a method for determining a DCI for cross-carrier scheduling, a terminal device, a network device, a computer storage medium, a chip, a computer-readable storage medium, a computer program product, and a computer program.

Background

According to the NR prior art scheme, when performing cross-Carrier scheduling of a Carrier Aggregation (CA) system, the size of a Frequency Domain Resource Allocation (FDRA) field of Downlink Control Information (DCI) in a scheduling cell is determined by the number N of Resource Block Groups (RBG) of the scheduled cell_RBGAnd number of PRBs

And (4) determining.

And due to the BandWidth Part (BWP) size (in terms of Physical Resource Block (PRB) number N) of different scheduled cells_RBGMeter) may be different, then

May also be different. The size of the FDRA field resulting in scheduling of different cells may be different, and the corresponding DCI size may also be different. Different cells have different

Is caused by two reasons: the absolute size of the active BWPs of the two cells is different, and the SubCarrier Spacing (SCS) of the active BWPs of the two cells is different.

If the two situations occur, the N of the active BWP of different cells can be caused_RBGAnd

in contrast, the DCI sizes of the cells are scheduled to be different, so that when detecting a Physical Downlink Control Channel (PDCCH), the terminal needs to perform blind detection on the DCI with different sizes, and thus the DCI with different sizes is detectedThe blind detection of the DCI with two different sizes can greatly increase the blind detection times of the DCI of the terminal and improve the monitoring complexity of the PDCCH.

Disclosure of Invention

In order to solve the foregoing technical problem, an embodiment of the present application provides a method for determining a DCI for cross-carrier scheduling, a terminal device, a network device, a computer storage medium, a chip, a computer-readable storage medium, a computer program product, and a computer program.

In a first aspect, a method for determining a DCI for cross-carrier scheduling is provided, where the method is applied to a terminal device, and the method includes:

determining the target size of Downlink Control Information (DCI) of cross-carrier scheduling;

when DCI scheduling different cells in at least two cells is detected in one cell, the same target size of the DCI is adopted for DCI detection.

In a second aspect, a method for determining a cross-carrier scheduled DCI is provided, where the method is applied to a network device, and the method includes:

sending DCI for scheduling different cells in at least two cells in one cell to terminal equipment; wherein the target size of the DCI for cross-carrier scheduling of different cells is the same.

In a third aspect, a terminal device is provided, which includes:

the first processing unit is used for determining the target size of the downlink control information DCI of cross-carrier scheduling;

the first communication unit detects DCI scheduling different cells of at least two cells in one cell, and adopts the same target size of the DCI to detect the DCI.

In a fourth aspect, a network device is provided, comprising:

a second communication unit for sending DCI for scheduling different cells of at least two cells in one cell to the terminal device; wherein the target size of the DCI for cross-carrier scheduling of different cells is the same.

In a fifth aspect, a terminal device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method in the first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method of the second aspect or each implementation mode thereof.

In a seventh aspect, a chip is provided for implementing the method in any one of the first and second aspects or its implementation manners.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device on which the chip is installed performs the method in any one of the first aspect and the second aspect or the implementation manners thereof.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method in any one of the first and second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any one of the first and second aspects or implementations thereof.

A tenth aspect provides a computer program which, when run on a computer, causes the computer to perform the method of any one of the first and second aspects or implementations thereof.

By adopting the scheme, the DCI detection can be carried out by adopting the same DCI target size aiming at different cells, so that the DCI blind detection times are reduced, the PDCCH detection complexity is reduced, the control channel receiving time delay is shortened, and the resource scheduling efficiency is improved.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

fig. 2 is a first flowchart illustrating a method for determining DCI for cross-carrier scheduling according to an embodiment of the present application;

fig. 3 is a schematic diagram of a scenario for scheduling DCI;

fig. 4 is a first scenario diagram illustrating a scenario of determining a target size of DCI according to an embodiment of the present disclosure;

fig. 5 is a schematic view of a second scenario for determining a target size of DCI according to an embodiment of the present disclosure;

fig. 6 is a third schematic view of a scenario of determining a target size of DCI according to an embodiment of the present disclosure;

fig. 7 is a fourth schematic view of a scenario of determining a target size of DCI according to an embodiment of the present disclosure;

fig. 8 is a schematic flowchart of a method for determining DCI for cross-carrier scheduling according to an embodiment of the present application;

fig. 9 is a schematic diagram of a scheduling DCI size of a different cell in the prior art;

FIG. 10 is a schematic diagram illustrating a scheduling DCI size of a different cell according to the prior art;

fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

fig. 12 is a schematic diagram of a network device component structure according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 14 is a schematic block diagram of a chip provided by an embodiment of the present application;

fig. 15 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

Detailed Description

So that the manner in which the features and elements of the present embodiments can be understood in detail, a more particular description of the embodiments, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings.

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.

For example, a communication system 100 applied in the embodiment of the present application may be as shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

The first embodiment,

An embodiment of the present application provides a determination method for DCI in cross-carrier scheduling, which is applied to a terminal device, and as shown in fig. 2, the method includes:

step 21: determining a target size of Downlink Control Information (DCI) for cross-carrier scheduling;

step 22: when DCI scheduling different cells in at least two cells is detected in one cell, the same target size of the DCI is adopted for DCI detection.

Here, the present embodiment is applied in a Carrier Aggregation (CA) scenario. The CA system supports self-scheduling (self-scheduling) and cross-carrier scheduling (cross-carrier scheduling). Specifically, the CA may include multiple cells, where different cells correspond to different carriers, and in the scheme provided in this embodiment, the DCI is sent in the scheduling cell, that is, except for the scheduling cell, the DCI of the remaining scheduled cells needs to be acquired from the DCI of the scheduling cell. For example, the CA system shown in fig. 3 includes three carriers, i.e., three cells, which are respectively cells (Cell)0, 1, and 2; wherein, Cell 0 can schedule the resource of the Cell and can schedule the resource of Cell 1 and Cell 2, Cell 0 is called Scheduling Cell (Scheduled Cell), and the resource of Cell 1 and Cell 2 is Scheduled by Cell 0 and is called Scheduled Cell (Scheduled Cell). The downlink and uplink signals within each carrier are limited to an active downlink bandwidth part (DL BWP) and an active downlink bandwidth part (UL BWP), respectively. If the DCI of the Cell 0 schedules the PDSCH or PUSCH of the Cell, the scheduling is called self scheduling (self scheduling); if the DCI of Cell 0 schedules PDSCH or PUSCH of Cell 1 or Cell 2, it is called cross-carrier scheduling (cross-carrier scheduling). In a CA system employing cross-carrier scheduling, the size of a bit field of Frequency Domain Resource Allocation (FDRA) for scheduling DCI for each carrier (cell) is determined according to parameters of the carrier. In some solutions provided in this embodiment, the processing may be performed according to the size of the FDRA or the content size of the DCI, and finally, the scheduling cell adopts the same DCI size regardless of whether the DCI of the scheduling cell or the DCI of the scheduled cell is transmitted.

It should be noted that, in the foregoing step 22, DCI for scheduling different cells of at least two cells is detected in one cell, where one cell refers to a scheduling cell, and at least two cells refer to scheduled cells, and of course, at least two cells may also include the scheduling cell and the scheduled cell; that is, the terminal device detects DCI of different scheduled cells in at least two scheduled cells scheduled in the scheduling cell, and performs DCI detection using the same DCI target size; or, the terminal device detects DCI of the scheduling cell and at least two scheduled cells in the scheduling cell, and performs DCI detection by using the same target size of the DCI.

Specifically, in step 21 of this embodiment, the method for determining the target size of the cross-carrier scheduled DCI may include the following steps:

the method 1,

The determining the target size of the cross-carrier scheduled DCI comprises:

determining a target size of a frequency domain resource allocation bit field in the cross-carrier scheduled DCI based on a size of a BandWidth Part (BWP) of each of the at least two cells;

determining a target size of the cross-carrier scheduled DCI based on a target size of the frequency domain resource allocation bit field.

The processing provided by the present approach may be based on the largest of the multiple cells

Determining a size of a Frequency Domain Resource Allocation (FDRA) domain in the DCI.

Further, in the case of being configured with cross-carrier scheduling, the terminal device determines the sizes of the bandwidth parts of at least two cells, that is, at least two scheduled cells (or a scheduling cell and at least one scheduled cell), and further determines the target size of the frequency domain resource allocation bit domain based on the sizes of the bandwidth parts of the at least two cells.

For example, assume that at least two cells are a first cell and a second cellA second cell; wherein the bandwidth part BWP size of the first cell

And BWP size of second cell

Based on

And

determining a size SFDRA of a frequency domain resource allocation bit field in the DCI scheduling the first cell and the second cell.

Wherein the determining a target size of a frequency domain resource allocation bit field in the cross-carrier scheduled DCI based on a size of a bandwidth part BWP of each of the at least two cells comprises:

determining a size of a Resource Block Group (RBG) of each cell based on a size of a bandwidth part BWP of each cell for the first frequency domain Resource allocation type;

selecting the maximum RBG from the RBGs respectively corresponding to the at least two cells;

determining a target size of a frequency domain resource allocation bit field included in the cross-carrier scheduled DCI based on the size of the largest RBG.

Regarding the frequency domain resource allocation type, in TS 38.212 v15.3.0, the method for determining the FDRA bit field size of DCI is introduced as follows (taking downlink resource allocation as an example, and uplink is similar), and if the resource scheduling mode is fixed to the first frequency domain resource allocation type (such as type 0), the size of the FDRA field is determined by the number N of Resource Block Groups (RBGs) in the active BWP of the cell_RBGIs determined by

The number of Physical Resource Blocks (PRB) in active BWP of the cell

Determining; if the resource scheduling mode is fixed to the second frequency domain resource allocation type (e.g., type 1), the size of the FDRA field is determined by

Determining; if the resource scheduling mode is a mixed mode of type 0 and type 1, the size of the FDRA field is determined by the larger of the two field sizes.

Also taking at least two cells including the first cell and the second cell as an example, for the first frequency domain resource allocation type, the resource allocation method is based on

Determining Resource Block Group (RBG) size P1 of the first cell, and further determining number N of RBGs contained in BWP of the first cell according to P1 _RBG1, based on

Determining the RBG size P2 of the second cell based on

Determining the number N of RBGs contained in the BWP of the second cell _RBG1, based on max (N)_RBG1,N _RBG2) Determining a size of a frequency domain resource allocation bit field, SFDRA, in the DCI.

Alternatively, another way to determine the target size of the frequency-domain resource allocation bit field is that, the determining the target size of the frequency-domain resource allocation bit field in the cross-carrier scheduled DCI based on the size of the bandwidth portion BWP of each of the at least two cells includes:

selecting the largest bandwidth part BWP from BWPs respectively corresponding to the at least two cells aiming at the second frequency domain resource allocation type;

and determining the target size of a frequency domain resource allocation bit field contained in the DCI of the cross-carrier scheduling based on the size of the selected maximum BWP.

The description of the second frequency domain resource allocation type is the same as the foregoing description, and is not repeated.

For example, the at least two cells include a first cell and a second cell; for the second frequency domain resource allocation type, based on

Determining a size of a frequency-domain resource allocation bit-domain, SFDRA, in the first DCI.

When the target size of the frequency domain resource allocation bit field is determined in this manner, the manner for extracting the frequency domain resource corresponding to each cell from which bits in the DCI is extracted may be:

determining a different number of bits N for indicating frequency domain resources of different cells based on sizes of different cell bandwidth parts BWP in the at least two cells; wherein N is an integer greater than or equal to 1;

and acquiring the frequency domain resources of different cells from the tail N bits in the frequency domain resource allocation bit fields of the DCI of different cells in at least two cells.

For example, the first cell or the second cell of the at least two cells indicates the frequency domain resource of the cell by using the last N bits (N ≦ SFDRA) of the SFDRA bits. N in the first cell or the second cell respectively according to

Or

And (4) determining.

The processing provided by the present invention is described in detail below with reference to fig. 4 and 5, providing the following two examples:

examples 1, 1,

According to the maximum N in a plurality of cells_RBGDetermining the size of the FDRA field in the DCI (both Cell 1 and Cell 2 are configured as a first frequency domain resource allocation type, namely, frequency domain resource allocation type 0).

As shown in fig. 4, it is assumed that the active BWP of Cell 1 and the active BWP of Cell 2 contain 200 PRBs and 150 PRBs, respectively, due to the difference in absolute size and subcarrier spacing between the active BWP of Cell 1 and the active BWP of Cell 2.

According to table 1, it is assumed that both cells adopt Configuration (Configuration)1, and Cell 1 and Cell 2 each have an RBG size (size) of 16, and the respective RBG numbers are N _RBG1 ═ 13 and N _RBG2＝10；

Determining the size of SFDRA as max (N)_RBG1,N _RBG2)＝13；

The 13-bit FDRA field in the DCI of Cell 1 comprises 13-bit FDRA bitmap, and the 13-bit FDRA field in the DCI of Cell 2 comprises 10-bit FDRA bitmap and 3-bit zero padding.

TABLE 1

In a case that a plurality of cells all adopt a first frequency domain resource allocation type (for example, frequency domain resource allocation type 0), the embodiment may be configured according to the maximum N_RBGAnd determining the size of the FDRA domain in the DCI, thereby aligning the sizes of the scheduling DCI of different cells, reducing the DCI blind detection times, reducing the PDCCH monitoring complexity, shortening the control channel receiving time delay and improving the resource scheduling efficiency. Meanwhile, the scheme provided by the example can limit the alignment range to a plurality of cellsUnder the condition of adopting the same frequency domain resource allocation type, the large DCI overhead increase caused by aligning the size of the FDRA domain under the condition that different cells are configured with different frequency domain resource allocation types can be avoided.

Examples 2,

According to the largest of a plurality of cells

And determining the size of the FDRA domain in the DCI (both Cell 1 and Cell 2 are configured to be a second frequency domain resource allocation type, such as frequency domain resource allocation type 1).

As shown in fig. 5, it is assumed that the active BWP size of Cell 1 and the active BWP size of Cell 2 are different due to the difference between the absolute size of the active BWP of Cell 1 and the subcarrier spacing of the active BWP of Cell 2

Determining

According to the formula

FDRA field size SFDRA 15.

The 15-bit FDRA field in the DCI of Cell 1 contains a 15-bit Resource Indication Value (RIV) indicator. According to the formula

The RIV indicator of Cell 2 is calculated to be 14bit, and the 15bit FDRA field in the DCI of Cell 2 contains the RIV indicator of 14bit and zero padding of 1bit, i.e. adding 1bit of "0" before the content of 14 bit.

This example may be based on a maximum in the case where multiple cells all employ the second frequency domain resource allocation type

And determining the size of the FDRA domain in the DCI so as to align the sizes of the scheduling DCI of different cells, thereby reducing the DCI blind detection times, reducing the PDCCH monitoring complexity, shortening the control channel receiving time delay and improving the resource scheduling efficiency. Meanwhile, the alignment range is limited under the condition that the multiple cells adopt the same frequency domain resource allocation type, so that the large DCI overhead increase caused by aligning the size of the FDRA domain under the condition that different cells are configured with different frequency domain resource allocation types can be avoided.

In the existing NR standard, N if BWP is active for different cells_RBGAnd

different, the DCI sizes of the cells are scheduled to be different, so that the terminal needs to perform blind detection on the DCIs with different sizes when detecting the PDCCH, the blind detection on the DCIs with two different sizes can greatly increase the frequency of the blind detection on the DCI of the terminal, and the monitoring complexity of the PDCCH is improved.

In view of the scheme provided by the foregoing mode 1, the maximum frequency resource allocation type can be determined according to the frequency resource allocation type of the multiple cells

Or N_RBGAnd determining the size of the FDRA domain in the DCI so as to align the sizes of the scheduling DCI of different cells, thereby reducing the DCI blind detection times, reducing the PDCCH monitoring complexity, shortening the control channel receiving time delay and improving the resource scheduling efficiency. Meanwhile, the method 1 limits the alignment range to the condition that a plurality of cells adopt the same frequency domain resource allocation type, thereby avoiding the situation that different frequency domain resource allocation types are configured in different cellsIn order to align the size of the FDRA field, a significant DCI overhead increase is incurred.

Mode 2,

The determining the target size of the cross-carrier scheduled DCI comprises:

determining the size of a frequency domain resource allocation bit domain corresponding to each cell in at least two cells;

determining a target size of a frequency domain resource bit domain included in the cross-carrier scheduled DCI based on a size of the frequency domain resource bit domain corresponding to each cell;

determining a target size of the cross-carrier scheduled DCI based on a target size of a frequency domain resource allocation bit field of the cross-carrier scheduling.

Unlike the method 1, in this method, the target size of the frequency domain resource allocation bit field is directly acquired, and the target size of the DCI is determined. That is, the size of the FDRA domain in the final DCI is determined according to the largest FDRA domain size in the plurality of cells.

In the method, under the condition of being configured with cross-carrier scheduling, the terminal equipment respectively calculates the sizes of the frequency domain resource allocation bit domains of at least two cells according to the condition of not being configured with cross-carrier scheduling, and then determines the target size of one frequency domain resource allocation bit domain based on the sizes of the frequency domain resource allocation bit domains of at least two cells. Specifically, the processing may be to select a size of a largest frequency domain resource allocation bit field from sizes of frequency domain resource allocation bit fields of at least two cells as a target size.

For example, at least two cells are a first cell and a second cell, in this manner, the sizes SFDRA1 and SFDRA2 of the frequency domain resource allocation bit regions of the first cell and the second cell are calculated according to the situation that cross-carrier scheduling is not configured, and the size SFDRA of the frequency domain resource allocation bit region in DCI scheduling the first cell and the second cell is determined based on max (SFDRA1, SFDRA 2).

Further, the DCI for different cells may be processed as follows: and acquiring the frequency domain resources of different cells from the tail ends in the frequency domain resource allocation bit fields of DCI (Downlink control information) of different cells in the at least two cells based on the size of the frequency domain resource allocation bit field corresponding to each cell in the at least two cells.

For example, the at least two cells are a first cell and a second cell; for the first cell, 1 bits of the later SFDRA bits are adopted to indicate the frequency domain resources of the cell. For the second cell, 2 bits of the later SFDRA bits are used to indicate the frequency domain resources of the cell. In addition, when there are remaining positions in the frequency domain resource allocation bit domain for a certain cell, zero padding may be performed at the remaining positions.

To explain method 2 with reference to fig. 6, it is assumed that the size of the active BWP of Cell 1 and the size of the active BWP of Cell 2 are respectively equal to each other due to the difference between the absolute size of the active BWP of Cell 1 and the absolute size of the active BWP of Cell 2 and the subcarrier spacing

And Cell 1 is configured to adopt a first frequency domain resource allocation type, namely, frequency domain resource allocation type 0, and Cell 2 is configured to adopt a second frequency domain resource allocation type, namely, frequency domain resource allocation type 1.

According to the situation of not configuring cross-carrier scheduling, assuming that the Cell adopts the first frequency domain resource allocation type, according to table 1, determining the RBG size of Cell 1 (first Cell) to be 16, and the RBG number to be N respectively_RBG1-13, FDRA field size SFDRA 1-13.

According to the condition of not configuring cross-carrier scheduling, according to the formula

The frequency domain resource allocation bit field FDRA field size SFDRA2 of the second Cell (Cell 2) is determined to be 14.

The target size SFDRA max (SFDRA1, SFDRA2) of the final frequency domain resource allocation bit field is determined to be 14.

The 14-bit FDRA field in the DCI of Cell 1 comprises a 13-bit FDRA bit map and a 1-bit zero padding, and the 14-bit FDRA field in the DCI of Cell 2 comprises a 14-bit RIV.

By adopting the method 2 for processing, the scheduling DCI sizes of different cells can be aligned no matter the multiple cells adopt the same or different frequency domain resource allocation types, so that the DCI blind detection times are reduced, the PDCCH monitoring complexity is reduced, the control channel receiving time delay is shortened, and the resource scheduling efficiency is improved. Meanwhile, the method 2 limits the aligned range to the frequency domain resource allocation bit domain, and may cause a large DCI overhead increase in order to align the DCI sizes when the sizes of other domains in the DCI are different.

Compared with the mode 1, the mode 2 can align the sizes of the scheduling DCI of different cells under the condition that the plurality of cells adopt different frequency domain resource allocation types, thereby reducing the blind detection times of the DCI, reducing the monitoring complexity of the PDCCH, shortening the receiving time delay of the control channel and improving the resource scheduling efficiency. Meanwhile, the method 2 limits the alignment range to the frequency domain resource allocation bit field, so as to avoid a large DCI overhead increase caused by aligning the DCI sizes when the sizes of other fields in the DCI are different.

Mode 3,

Respectively determining the size of DCI corresponding to each cell in at least two cells; and determining the target size of the cross-carrier scheduling DCI based on the size of the DCI corresponding to each cell.

Unlike the first two methods, this method does not care about the size of the frequency domain resource allocation bit field or other fields, but rather the size of the finally determined DCI content for each cell, and further determines the target DCI size according to the size of the DCI content for each cell.

For example, assume that the at least two cells include a first cell and a second cell; in the case of configured cross-carrier scheduling, the terminal first calculates DCI sizes SDCI1 and SDCI2 of the first cell and the second cell, respectively, according to the case of not configured cross-carrier scheduling, and determines DCI sizes SDCI for scheduling the first cell and the second cell based on max (SDCI1, SDCI 2).

The method for acquiring the frequency domain resources of the DCI may be: and acquiring the information content of the DCI corresponding to different cells from the tail parts of the DCI of different cells in the at least two cells based on the size of the DCI corresponding to each cell in the at least two cells.

For example, assume that the at least two cells include a first cell and a second cell; under the condition of being configured with cross-carrier scheduling, the terminal respectively calculates DCI (downlink control information) sizes SDCI1 and SDCI2 of a first cell and a second cell according to the condition of not being configured with cross-carrier scheduling; if SDCI1< SDCI, the DCI for the first cell constitutes SDCI bits by SDCI-SDCI1 zero padding (zero padding), and if SDCI2< SDCI, the DCI for the second cell constitutes SDCI bits by SDCI-SDCI2 zero padding (zero padding).

To explain this embodiment in detail by taking fig. 7 as an example, as shown in fig. 7, it is assumed that the DCI size SDCI1 of Cell 1 and the DCI size SDCI2 of Cell 2 are calculated respectively because the FDRA field sizes of Cell 1 and Cell 2 are different from each other and/or the Time Domain Resource Allocation (TDRA) field size is different.

Assuming SDCI1< SDCI2, the final DCI size SDCI ═ max (SDCI1, SDCI2) ═ SDCI2 is determined.

The DCI of Cell 1 comprises DCI payload of SDCI 1bit and zero padding of (SDCI2-SDCI1) bit, and the DCI of Cell 2 comprises DCI payload of SDCI2 bit.

The method can align the DCI size under the condition that the frequency domain resource allocation domains of the plurality of cells are different in size, and can align the DCI size under the condition that the time domain resource allocation domains of the plurality of cells are different in size, so that the DCI blind detection times are reduced, the PDCCH monitoring complexity is reduced, the control channel receiving time delay is shortened, and the resource scheduling efficiency is improved.

Compared with the

modes

1 and 2, the mode 3 can align the DCI size under the condition that the frequency domain resource allocation domains of the plurality of cells are different in size, and can align the DCI size under the condition that the time domain resource allocation domains of the plurality of cells are different in size, so that the DCI blind detection times are reduced, the PDCCH monitoring complexity is reduced, the control channel receiving time delay is shortened, and the resource scheduling efficiency is improved.

Therefore, by adopting the scheme, the DCI detection can be performed by adopting the same DCI target size for different cells, so that the DCI blind detection times are reduced, the PDCCH detection complexity is reduced, the control channel receiving time delay is shortened, and the resource scheduling efficiency is improved.

Example II,

An embodiment of the present application provides a method for determining a DCI for cross-carrier scheduling, which is applied to a network device, and as shown in fig. 8, the method includes:

step 31: sending DCI for cross-carrier scheduling of different cells in at least two cells to a terminal device; wherein the target size of the DCI for cross-carrier scheduling of different cells is the same.

It should be noted that, the foregoing sending DCI for scheduling different cells in at least two cells in one cell to a terminal device may be sending DCI for different cells in at least two cells to a scheduling cell of the terminal device. The at least two cells refer to scheduled cells, but the at least two cells may also include a scheduling cell and a scheduled cell.

Specifically, in this embodiment, the network device needs to determine the target size of the cross-carrier scheduled DCI before sending the DCI, which may include the following several ways:

the method 1,

The cross-carrier scheduled DCI comprises: a frequency domain resource allocation bit field;

wherein the target size of the frequency domain resource allocation bit field of the DCI corresponding to different cells is the same and is determined based on the dimension of the BWP of each of the at least two cells.

For example, assume that at least two cells are a first cell and a second cell; wherein the bandwidth part BWP size of the first cell

And BWP of the second cellSize of

Based on

And

In one process, for a first frequency domain resource allocation type, a size of a resource block group, RBG, of each cell is determined based on a size of a bandwidth part, BWP, of each cell;

Regarding the frequency domain resource allocation type, in TS 38.212 v15.3.0, the method for determining the FDRA bit field size of DCI is introduced as follows (taking downlink resource allocation as an example, and uplink is similar), and if the resource scheduling mode is fixed to the first frequency domain resource allocation type (such as type 0), the size of the FDRA field is determined by the number N of Resource Block Groups (RBGs) in the active BWP of the cell_RBGIs determined in that N_RBGAgain by the number of Physical Resource Blocks (PRBs) in the active BWP of this cell

Determining the RBG size P2 of the second cell based on

Or, in another processing, for a second frequency domain resource allocation type, selecting a maximum bandwidth portion BWP from BWPs corresponding to the at least two cells, respectively;

Under the condition that the target size of the frequency domain resource allocation bit field is determined by adopting the method, the tail N bits in the frequency domain resource allocation bit fields of DCI of different cells in the at least two cells represent the frequency domain resources of the different cells;

wherein the N bits are determined based on sizes of different cell bandwidth parts BWP in at least two cells, and N is an integer greater than or equal to 1.

Or

And (4) determining.

examples 1, 1,

Determining the size of SFDRA as max (N)_RBG1,N _RBG2)＝13；

TABLE 1

In a case that a plurality of cells all adopt a first frequency domain resource allocation type (for example, frequency domain resource allocation type 0), the embodiment may be configured according to the maximum N_RBGAnd determining the size of the FDRA domain in the DCI so as to align the sizes of the scheduling DCI of different cells, thereby reducing the DCI blind detection times, reducing the PDCCH monitoring complexity, shortening the control channel receiving time delay and improving the resource scheduling efficiency. Meanwhile, the scheme provided by this example can limit the alignment range to the case where multiple cells use the same frequency domain resource allocation type, and can avoid a large DCI overhead increase to align the size of the FDRA domain when different cells configure different frequency domain resource allocation types.

Examples 2,

Determining

According to the formula

FDRA field size SFDRA 15.

In the existing NR standard, N if BWP is active for different cells_RBGAnd

different, the DCI sizes of the cells are scheduled to be different, so that the terminal needs to perform blind detection on the DCIs of different sizes respectively when detecting the PDCCH, and thus, performing blind detection on the DCI of two different sizes can greatly increase the number of times of blind detection on the DCI of the terminal, and improveHigh PDCCH monitoring complexity.

Or N_RBGAnd determining the size of the FDRA domain in the DCI so as to align the sizes of the scheduling DCI of different cells, thereby reducing the DCI blind detection times, reducing the PDCCH monitoring complexity, shortening the control channel receiving time delay and improving the resource scheduling efficiency. Meanwhile, the method 1 limits the alignment range to the case that the multiple cells adopt the same frequency domain resource allocation type, so that the DCI overhead is prevented from being greatly increased for aligning the size of the FDRA domain when different cells are configured with different frequency domain resource allocation types.

Mode 2,

the target sizes of the frequency domain resource allocation bit fields of the DCI corresponding to different cells are the same, and are determined based on the size of the frequency domain resource bit field corresponding to each cell in at least two cells.

And then setting the frequency domain resources aiming at different cells at the tail of the corresponding frequency domain resource allocation bit field in the DCI of different cells in at least two cells.

According to the situation of unconfigured cross-carrier scheduling, according to the publicFormula (II)

Mode 3,

The target size of the DCI for cross-carrier scheduling of different cells is determined by the information size of the DCI corresponding to each of the at least two cells.

The information content of the DCI corresponding to the information size of the DCI of each cell is set at the tail bit position of the DCI of different cells in the at least two cells, and the residual bits are filled with zero.

Compared with the

modes

Further, in the related art, the reason why the number of detections for generating DCI increases is explained with reference to fig. 9 and 10, one reason is that the absolute sizes of the active BWPs of at least two cells are different, for example, in fig. 9, the absolute size of the active DL BWP (DL BWP 2) of the second Cell, for example, Cell 2 in the figure, is 2 times that of the active DL BWP (DL BWP 1) of the first Cell, for example, Cell 1 in the figure, and the absolute size of the active DL BWP (DL BWP 2) of the DL BWP 1 is 2 times that of the active DL BWP (DL BWP 1) of the first Cell, for example, Cell 1 in the figure

Of PRB, DL BWP 2

For FDRA type 1, according to the formula

The calculated FDRA domain length of DL BWP 1 is 13bit, and the FDRA domain length of DL BWP 2 is 15 bit.

For the first frequency domain resource allocation type, i.e. FDRA type 0, according to the RBG size determination method of TS 38.214 (see table 2), the FDRA domain length of DL BWP 1 is 13bit or 7bit, and the FDRA domain length of DL BWP 2 is 13 bit.

TABLE 2

Secondly, the subcarrier spacing (SCS) of the active BWP of the two cells is different, as shown in fig. 10, although the absolute size of the active DL BWP (DL BWP 1) of Cell 1 and the active DL BWP (DL BWP 2) of Cell 2 are differentSame, however, SCS of DL BWP 1 is 30kHz, so

And SCS of DL BWP 2 is 60kHz, so

For the FDRA type 1, the FDRA domain length of the DL BWP 1 is 15 bits, and the FDRA domain length of the DL BWP 2 is 13 bits. For the FDRA type 0, the FDRA domain length of the DL BWP 1 is 13 bits, and the FDRA domain length of the DL BWP 2 is 13 bits or 7 bits.

By adopting the above scheme, the present embodiment can perform DCI detection on different cells using the same DCI target size, thereby reducing DCI blind detection times, reducing PDCCH detection complexity, shortening control channel reception delay, and improving resource scheduling efficiency.

Example III,

An embodiment of the present application provides a terminal device, as shown in fig. 11, including:

a first processing unit 41, configured to determine a target size of DCI for cross-carrier scheduling;

when detecting DCI that schedules different cells in at least two cells in one cell, the first communication unit 42 performs DCI detection using the same target size of the DCI.

Detecting DCI for scheduling different cells of at least two cells in one cell, where one cell refers to a scheduling cell and at least two cells refer to scheduled cells, and certainly, the at least two cells may also include the scheduling cell and the scheduled cell; that is, the terminal device detects DCI of different scheduled cells in at least two scheduled cells scheduled in the scheduling cell, and performs DCI detection using the same DCI target size; or, the terminal device detects DCI of the scheduling cell and at least two scheduled cells in the scheduling cell, and performs DCI detection by using the same target size of the DCI.

Specifically, the methods for determining the target size of the DCI scheduled across carriers may include the following steps:

the method 1,

The first processing unit 41 determines a target size of a frequency domain resource allocation bit field in the cross-carrier scheduled DCI based on a size of a BandWidth Part (BWP) of each of at least two cells;

A first processing unit 41 that determines, for the first frequency domain Resource allocation type, a size of a Resource Block Group (RBG) of each cell based on a size of a bandwidth part BWP of each cell;

Alternatively, another way to determine the target size of the frequency domain resource allocation bit field is that, for the second frequency domain resource allocation type, the first processing unit 41 selects the largest bandwidth portion BWP from the bandwidth portions BWPs respectively corresponding to the at least two cells; and determining the target size of a frequency domain resource allocation bit field contained in the DCI of the cross-carrier scheduling based on the size of the selected maximum BWP.

A first processing unit 41, determining different numbers of bits N for indicating frequency domain resources of different cells based on sizes of different cell bandwidth parts BWP in at least two cells; wherein N is an integer greater than or equal to 1;

Mode 2,

The first processing unit 41 determines a size of a frequency domain resource allocation bit domain corresponding to each of at least two cells; determining a target size of a frequency domain resource bit domain included in the cross-carrier scheduled DCI based on a size of the frequency domain resource bit domain corresponding to each cell; determining a target size of the cross-carrier scheduled DCI based on a target size of a frequency domain resource allocation bit field of the cross-carrier scheduling.

The first processing unit 41 may process DCI of different cells by: and acquiring the frequency domain resources of different cells from the tail ends in the frequency domain resource allocation bit fields of DCI (Downlink control information) of different cells in the at least two cells based on the size of the frequency domain resource allocation bit field corresponding to each cell in the at least two cells.

Mode 3,

A first processing unit 41, configured to determine a DCI size corresponding to each cell of at least two cells respectively; and determining the target size of the cross-carrier scheduling DCI based on the size of the DCI corresponding to each cell.

The first processing unit 41 obtains information content of DCI corresponding to different cells from the end of DCI of different cells in the at least two cells based on the size of DCI corresponding to each cell in the at least two cells.

It should be understood that the specific functions of each module in this embodiment are the same as those in the first embodiment, and therefore, the detailed description thereof is omitted.

Example four,

An embodiment of the present application provides a network device, as shown in fig. 12, including:

a second communication unit 51 configured to send DCI for scheduling different cells of at least two cells in one cell to the terminal device; wherein the target size of the DCI for cross-carrier scheduling of different cells is the same.

The sending of the DCI for scheduling different cells in the at least two cells in one cell to the terminal device may be sending the DCI for different cells in the at least two cells to the scheduling cell of the terminal device. The at least two cells refer to scheduled cells, but the at least two cells may also include a scheduling cell and a scheduled cell.

the method 1,

In one process, the network device further comprises:

a second processing unit 52, for the first frequency domain resource allocation type, determining a size of the resource block group RBG of each cell based on a size of the bandwidth part BWP of each cell; selecting the maximum RBG from the RBGs respectively corresponding to the at least two cells; determining a target size of a frequency domain resource allocation bit field included in the cross-carrier scheduled DCI based on the size of the largest RBG.

Or, in another processing, the second processing unit 52, for the second frequency domain resource allocation type, selects the largest bandwidth portion BWP from the bandwidth portions BWP respectively corresponding to the at least two cells; and determining the target size of a frequency domain resource allocation bit field contained in the DCI of the cross-carrier scheduling based on the size of the selected maximum BWP.

Mode 2,

Mode 3,

It should be further noted that the functions of the units in this embodiment are the same as those described in the second embodiment, and are not described again here.

By adopting the above scheme, the present embodiment can enable DCI detection to be performed on different cells by using the same DCI target size, thereby reducing DCI blind detection times, reducing PDCCH detection complexity, shortening control channel reception delay, and improving resource scheduling efficiency.

Fig. 13 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application, where the communication device may be the terminal device or the network device described in this embodiment. The communication device 600 shown in fig. 13 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 13, the communication device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.

Optionally, as shown in fig. 13, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include one or more antennas.

Optionally, the communication device 600 may specifically be a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 600 may specifically be a terminal device or a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by a mobile terminal/a terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Fig. 14 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 14 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 14, the chip 700 may further include a memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 720 may be a separate device from the processor 710, or may be integrated into the processor 710.

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

Fig. 15 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. As shown in fig. 15, the communication system 800 includes a terminal device 810 and a network device 820.

The terminal device 810 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 820 may be configured to implement the corresponding function implemented by the network device in the foregoing method, which is not described herein again for brevity.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for determining a DCI (Downlink control information) of cross-carrier scheduling is applied to terminal equipment, and the method comprises the following steps:

determining the target size of Downlink Control Information (DCI) of cross-carrier scheduling;

when DCI scheduling different cells in at least two cells is detected in one cell, the same target size of the DCI is adopted for DCI detection.
The method of claim 1, wherein the determining a target size of a cross-carrier scheduled DCI comprises:

determining a target size of a frequency domain resource allocation bit field in the cross-carrier scheduled DCI based on a size of a bandwidth part BWP of each of at least two cells;

determining a target size of the cross-carrier scheduled DCI based on a target size of the frequency domain resource allocation bit field.
The method of claim 2, wherein the determining a target size of a frequency domain resource allocation bit field in the cross-carrier scheduled DCI based on a size of a bandwidth part BWP of each of the at least two cells comprises:

determining a size of a resource block group RBG of each cell based on a size of a bandwidth part BWP of each cell for the first frequency domain resource allocation type;

selecting the maximum RBG from the RBGs respectively corresponding to the at least two cells;

determining a target size of a frequency domain resource allocation bit field included in the cross-carrier scheduled DCI based on the size of the largest RBG.
The method of claim 2, wherein the determining a target size of a frequency domain resource allocation bit field in the cross-carrier scheduled DCI based on a size of a bandwidth part BWP of each of the at least two cells comprises:

selecting the largest bandwidth part BWP from BWPs respectively corresponding to the at least two cells aiming at the second frequency domain resource allocation type;

and determining the target size of a frequency domain resource allocation bit field contained in the DCI of the cross-carrier scheduling based on the size of the selected maximum BWP.
The method according to any one of claims 2-4, wherein the method further comprises:

determining a different number of bits N for indicating frequency domain resources of different cells based on sizes of different cell bandwidth parts BWP in the at least two cells; wherein N is an integer greater than or equal to 1;

and acquiring the frequency domain resources of different cells from the tail N bits in the frequency domain resource allocation bit fields of the DCI of different cells in at least two cells.
The method of claim 1, wherein the determining a target size of a cross-carrier scheduled DCI comprises:

determining the size of a frequency domain resource allocation bit domain corresponding to each cell in at least two cells;

determining a target size of a frequency domain resource bit domain included in the cross-carrier scheduled DCI based on a size of the frequency domain resource bit domain corresponding to each cell;

determining a target size of the cross-carrier scheduled DCI based on a target size of a frequency domain resource allocation bit field of the cross-carrier scheduling.
The method of claim 6, wherein the method further comprises:

and acquiring the frequency domain resources of different cells from the tail ends in the frequency domain resource allocation bit fields of DCI (Downlink control information) of different cells in the at least two cells based on the size of the frequency domain resource allocation bit field corresponding to each cell in the at least two cells.
The method of claim 1, wherein the determining the size of the cross-carrier scheduled DCI comprises:

respectively determining the size of DCI corresponding to each cell in at least two cells;

and determining the target size of the cross-carrier scheduling DCI based on the size of the DCI corresponding to each cell.
The method of claim 8, wherein the method further comprises:

and acquiring the information content of the DCI corresponding to different cells from the tail parts of the DCI of different cells in the at least two cells based on the size of the DCI corresponding to each cell in the at least two cells.
A method for determining a DCI (Downlink control information) of cross-carrier scheduling is applied to a network device, and the method comprises the following steps:

sending DCI for scheduling different cells in at least two cells in one cell to terminal equipment; wherein the target size of the DCI for cross-carrier scheduling of different cells is the same.
The method of claim 10, wherein the cross-carrier scheduled DCI comprises: a frequency domain resource allocation bit domain;

wherein the target size of the frequency domain resource allocation bit field of the DCI corresponding to different cells is the same and is determined based on the dimension of the BWP of each of the at least two cells.
The method of claim 11, wherein the method further comprises:

determining a size of a resource block group RBG of each cell based on a size of a bandwidth part BWP of each cell for the first frequency domain resource allocation type;

selecting the maximum RBG from the RBGs respectively corresponding to the at least two cells;

determining a target size of a frequency domain resource allocation bit field included in the cross-carrier scheduled DCI based on the size of the largest RBG.
The method of claim 11, wherein the method further comprises:

selecting the largest bandwidth part BWP from BWPs respectively corresponding to the at least two cells aiming at the second frequency domain resource allocation type;

and determining the target size of a frequency domain resource allocation bit field contained in the DCI of the cross-carrier scheduling based on the size of the selected maximum BWP.
The method according to any of claims 11-13, wherein the last N bits in the frequency domain resource allocation bit fields of the DCI for different ones of the at least two cells characterize the frequency domain resources of the different cells;

wherein the N bits are determined based on sizes of different cell bandwidth parts BWP in at least two cells, and N is an integer greater than or equal to 1.
The method of claim 10, wherein the cross-carrier scheduled DCI comprises: a frequency domain resource allocation bit field;

the target sizes of the frequency domain resource allocation bit fields of the DCI corresponding to different cells are the same, and are determined based on the size of the frequency domain resource bit field corresponding to each cell in at least two cells.
The method of claim 15, wherein frequency domain resources for different cells are set at an end of a corresponding frequency domain resource allocation bitfield in DCI for different ones of the at least two cells.
The method of claim 10, wherein the target size of the cross-carrier scheduled DCI for different cells is determined by an information size of DCI corresponding to each of at least two cells.
The method of claim 17, wherein at last bits of DCI for different cells of the at least two cells, information content of DCI corresponding to an information size of DCI for each cell is set, and remaining bits are padded with zero.
A terminal device, comprising:

the first processing unit is used for determining the target size of the downlink control information DCI of cross-carrier scheduling;

the first communication unit detects DCI scheduling different cells of at least two cells in one cell, and adopts the same target size of the DCI to detect the DCI.
The terminal device of claim 19, wherein the first processing unit determines a target size of a frequency domain resource allocation bit field in the cross-carrier scheduled DCI based on a size of a bandwidth part BWP of each of the at least two cells; determining a target size of the cross-carrier scheduled DCI based on a target size of the frequency domain resource allocation bit field.
The terminal device of claim 20, wherein the first processing unit determines, for a first frequency-domain resource allocation type, a size of a resource block group, RBG, of each cell based on a size of a bandwidth part, BWP, of each cell; selecting the maximum RBG from the RBGs respectively corresponding to the at least two cells; determining a target size of a frequency domain resource allocation bit field included in the cross-carrier scheduled DCI based on the size of the largest RBG.
The terminal device of claim 20, wherein the first processing unit selects, for a second frequency-domain resource allocation type, a maximum bandwidth portion BWP from BWPs corresponding to the at least two cells, respectively; and determining the target size of a frequency domain resource allocation bit field contained in the DCI of the cross-carrier scheduling based on the size of the selected maximum BWP.
The terminal device according to any of claims 20-22, wherein the first processing unit determines different numbers of bits N indicating frequency domain resources of different cells based on the size of different cell bandwidth parts BWP in at least two cells; wherein N is an integer greater than or equal to 1; and acquiring the frequency domain resources of different cells from the tail N bits in the frequency domain resource allocation bit fields of the DCI of different cells in at least two cells.
The terminal device of claim 19, wherein the first processing unit determines a size of a frequency domain resource allocation bit domain corresponding to each of at least two cells; determining a target size of a frequency domain resource bit domain included in the cross-carrier scheduled DCI based on a size of the frequency domain resource bit domain corresponding to each cell; determining a target size of the cross-carrier scheduled DCI based on a target size of a frequency domain resource allocation bit field of the cross-carrier scheduling.
The terminal device of claim 24, wherein the first processing unit obtains the frequency domain resources of different cells from the end of the frequency domain resource allocation bit field of the DCI of different cells in the at least two cells based on the size of the frequency domain resource allocation bit field corresponding to each cell in the at least two cells.
The terminal device of claim 19, wherein the first processing unit determines a DCI size corresponding to each of at least two cells respectively; and determining the target size of the cross-carrier scheduling DCI based on the size of the DCI corresponding to each cell.
The terminal device of claim 26, wherein the first processing unit obtains information content of DCI corresponding to different cells from ends of DCI corresponding to different cells in the at least two cells based on a size of DCI corresponding to each cell in the at least two cells.
A network device, comprising:

a second communication unit for sending DCI for scheduling different cells of at least two cells in one cell to the terminal device; wherein the target size of the DCI for cross-carrier scheduling of different cells is the same.
The network device of claim 28, wherein the cross-carrier scheduled DCI comprises: a frequency domain resource allocation bit field;

wherein the target size of the frequency domain resource allocation bit field of the DCI corresponding to different cells is the same and is determined based on the dimension of the BWP of each of the at least two cells.
The network device of claim 29, wherein the network device further comprises:

a second processing unit determining a size of a resource block group RBG of each cell based on a size of a bandwidth part BWP of each cell for the first frequency domain resource allocation type; selecting the maximum RBG from the RBGs respectively corresponding to the at least two cells; determining a target size of a frequency domain resource allocation bit field included in the cross-carrier scheduled DCI based on the size of the largest RBG.
The network device of claim 29, wherein the network device further comprises:

a second processing unit, configured to select, for a second frequency-domain resource allocation type, a largest bandwidth portion BWP from BWPs corresponding to the at least two cells, respectively; and determining the target size of a frequency domain resource allocation bit field contained in the DCI of the cross-carrier scheduling based on the size of the selected maximum BWP.
The network equipment of any one of claims 29-31, wherein the last N bits in the frequency domain resource allocation bit fields of DCI for different ones of the at least two cells characterize the frequency domain resources of the different cells;

wherein the N bits are determined based on sizes of different cell bandwidth parts BWP in at least two cells, and N is an integer greater than or equal to 1.
The network device of claim 28, wherein the cross-carrier scheduled DCI comprises: a frequency domain resource allocation bit field;

the target sizes of the frequency domain resource allocation bit fields of the DCI corresponding to different cells are the same, and are determined based on the size of the frequency domain resource bit field corresponding to each cell in at least two cells.
The network device of claim 33, wherein frequency domain resources for different cells are set at an end of a corresponding frequency domain resource allocation bitfield in DCI for different ones of the at least two cells.
The network device of claim 28, wherein the target size of the cross-carrier scheduled DCI for different cells is determined by an information size of DCI corresponding to each of at least two cells.
The network device of claim 35, wherein at last bits of DCI for different cells of the at least two cells, information content of DCI corresponding to an information size of DCI for each cell is set, and remaining bits are padded with zero.
A terminal device, comprising: a processor and a memory for storing a computer program capable of running on the processor,

wherein the memory is adapted to store a computer program and the processor is adapted to call and run the computer program stored in the memory to perform the steps of the method according to any of claims 1-9.
A network device, comprising: a processor and a memory for storing a computer program capable of running on the processor,

wherein the memory is adapted to store a computer program and the processor is adapted to call and run the computer program stored in the memory to perform the steps of the method according to any of claims 10-18.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1-9.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 10-18.
A computer-readable storage medium for storing a computer program for causing a computer to perform the steps of the method according to any one of claims 1 to 18.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 18.
A computer program for causing a computer to perform the method of any one of claims 1-18.