CN112671520B - Method, device, apparatus and medium for determining downlink control information - Google Patents
Method, device, apparatus and medium for determining downlink control information Download PDFInfo
- Publication number
- CN112671520B CN112671520B CN201910984942.0A CN201910984942A CN112671520B CN 112671520 B CN112671520 B CN 112671520B CN 201910984942 A CN201910984942 A CN 201910984942A CN 112671520 B CN112671520 B CN 112671520B
- Authority
- CN
- China
- Prior art keywords
- time domain
- domain resource
- resource allocation
- dci
- dci format
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000013468 resource allocation Methods 0.000 claims abstract description 280
- 238000004590 computer program Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 14
- 230000005540 biological transmission Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000011664 signaling Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method, a device and a medium for determining downlink control information, wherein the method comprises the following steps: time domain resource allocation tables of different service types are independently configured; receiving a time domain resource allocation table which is independently configured for different service types by a network side; receiving downlink control information, wherein the downlink control information schedules different service types by using a downlink control information format, and determining the information bit number contained in a time domain resource allocation bit field in the downlink control information according to the maximum line number of time domain resource allocation tables of different service types. The invention can use one descending control information format to dispatch the time domain resource distribution table corresponding to different service types, because the base station and the terminal side have the same understanding to the descending control information, the correct process of dispatching can be ensured.
Description
Technical Field
The present invention relates to the field of wireless communication technologies, and in particular, to a method, an apparatus, a device, and a medium for determining downlink control information.
Background
In a 5G NR (New wireless communication system, 5Generation New RAT), flexible time domain resource allocation is supported, and a base station configures a time domain resource allocation table to a UE (User Equipment) and indicates time domain resource allocation Information by indicating a specific row in the table through a specific Information field in a DCI (Downlink Control Information). And determining the size of the time domain resource allocation indication domain in the DCI according to the row number contained in the time domain resource allocation table.
For PDSCH (Physical Downlink Shared CHannel), the time domain resource allocation indication field in PDCCH (Physical Downlink Control CHannel) carrying its scheduling information indicates that PDSCH resources use a specific row in the time domain resource allocation table. Specifically, the time domain resource allocation table of NR (New radio communication system, new RAT) includes a resource mapping type, a number of slots of PDCCH and PDSCH/PUSCH (Physical Uplink Shared Channel) intervals, a start symbol, and length information. Similarly, the time domain resource allocation indication field in the PDCCH for scheduling the PUSCH may also indicate that the PUSCH resource uses a specific row in the time domain resource allocation table.
In the NR Rel-15 stage, different traffic types are not distinguished in the system, in the NR Rel-16 stage, the traffic types are distinguished in the system, and for a channel scheduled by DCI, the corresponding traffic types can be distinguished through DCI, for example, the traffic types corresponding to DCI are distinguished through DCI format or newly added bits in DCI or through RNTI (Radio Network temporary Identity) scrambling the DCI or through a search space in which the DCI is located.
The prior art is not sufficient in that no scheme is available for scheduling time domain resource allocation tables corresponding to different service types by using one DCI format.
Disclosure of Invention
The invention provides a method, equipment, a device and a medium for determining DCI (Downlink control information), which are used for solving the problem that a time domain resource allocation table corresponding to different service types cannot be scheduled by using one DCI format.
The embodiment of the invention provides a method for determining DCI, which comprises the following steps:
time domain resource allocation tables of different service types are independently configured;
when different service types are scheduled by using one DCI format, the information bit number contained in the time domain resource allocation bit field in the DCI is determined according to the maximum line number of the time domain resource allocation tables of the different service types.
In an implementation, the DCI format comprises one of the following:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
In the implementation, the time domain resource allocation tables of different service types are defined or configured independently, and include:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the newly defined DCI format for data scheduling for NR Rel-16.
In implementation, when a time domain resource allocation table is predefined or configured independently for each service type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the information bit number is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, and includes:
the number of the information bits is
Wherein, a is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
In implementation, determining the number of rows in the time domain resource allocation table for different service types includes:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
In practice, the
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
The embodiment of the invention provides a method for determining DCI, which comprises the following steps:
receiving a time domain resource allocation table which is independently configured for different service types by a network side;
receiving DCI, wherein the DCI uses one DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of different service types.
In an implementation, the DCI format comprises one of:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
In the implementation, the independently defining or configuring the time domain resource allocation tables of different service types includes:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the newly defined DCI format for data scheduling for NR Rel-16.
In implementation, when a time domain resource allocation table is predefined or configured independently for each service type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the information bit number is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, and includes:
the number of the information bits is
Wherein, A is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
In implementation, determining the number of rows in the time domain resource allocation table for different service types includes:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
In practice, the
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
An embodiment of the present invention provides a base station, where the base station includes:
a processor for reading the program in the memory, performing the following processes:
time domain resource allocation tables of different service types are independently configured;
when different service types are scheduled by using a DCI format, determining the information bit number contained in a time domain resource allocation bit field in the DCI according to the maximum line number of a time domain resource allocation table of the different service types;
a transceiver for receiving and transmitting data under the control of the processor.
In an implementation, the DCI format comprises one of the following:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
In the implementation, the time domain resource allocation tables of different service types are defined or configured independently, and include:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the newly defined DCI format for data scheduling for NR Rel-16.
In implementation, when a time domain resource allocation table is predefined or configured independently for each service type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the information bit number is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, and includes:
the number of the information bits is
Wherein, a is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
In implementation, determining the number of rows in the time domain resource allocation table for different service types includes:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
In practice, the
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
The embodiment of the invention provides a UE, and the UE comprises:
the processor is used for reading the program in the memory and processing data according to the requirement of the processor;
a transceiver for receiving and transmitting data under the control of the processor, performing the following processes:
receiving a time domain resource allocation table which is independently configured for different service types by a network side;
receiving DCI, wherein the DCI uses one DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of different service types.
In an implementation, the DCI format comprises one of the following:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
In the implementation, the independently defining or configuring the time domain resource allocation tables of different service types includes:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the newly defined DCI format for data scheduling for NR Rel-16.
In implementation, when a time domain resource allocation table is predefined or configured independently for each service type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the information bit number is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, and includes:
the number of the information bits is
Wherein, A is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
In implementation, determining the number of rows in the time domain resource allocation table for different service types includes:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format to be A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format to be B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
In practice, the
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
The embodiment of the invention provides a device for determining DCI, which comprises:
the configuration module is used for independently configuring time domain resource allocation tables of different service types;
and the determining module is used for determining the information bit number contained in the time domain resource allocation bit field in the DCI according to the maximum row number of the time domain resource allocation tables of different service types when different service types are scheduled by using one DCI format.
The embodiment of the invention provides a device for determining DCI, which comprises:
the table receiving module is used for receiving a time domain resource allocation table which is independently configured for different service types by a network side;
and the DCI receiving module is used for receiving the DCI, wherein the DCI uses one DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of the different service types.
The embodiment of the present invention provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the processor implements the method for determining DCI.
An embodiment of the present invention provides a computer-readable storage medium, which stores a computer program for executing the DCI determination method described above.
The invention has the following beneficial effects:
in the technical solution provided in the embodiment of the present invention, since time domain resource allocation tables of different service types are defined or configured independently, and then the information bit number contained in the time domain resource allocation bit field in the DCI is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, one DCI format may be used to schedule the time domain resource allocation tables corresponding to different service types.
Furthermore, because the base station and the terminal side have consistent understanding of the DCI, the scheduling process can be guaranteed to be performed correctly.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not limit the invention. In the drawings:
fig. 1 is a schematic flow chart illustrating an implementation of a method for determining DCI at a base station side according to an embodiment of the present invention;
fig. 2 is a schematic flow chart illustrating an implementation of a method for determining DCI on a UE side according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a base station structure according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a UE structure according to an embodiment of the present invention.
Detailed Description
The inventor notices in the process of invention that:
in the NR Rel-16 stage, it will be supported that different traffic types are distinguished by DCI, for example, the traffic types are distinguished by DCI format or new added bits in DCI, or by scrambling RNTI of DCI, or by search space where DCI is located, which is not determined specifically, but it is known that the traffic type scheduled by one DCI can be distinguished by using the physical layer method.
In the NR Rel-16 stage, a new DCI format is supported, and when the new DCI format performs time domain resource scheduling, the reference point of the indicated time domain resource starting position is the PDCCH ending position. However, the reference point of the time domain resource starting position indicated by the original DCI format is a time slot boundary, and therefore, for a specific row in the same time domain resource table, time domain resources obtained by using different DCI formats may be different.
However, different service types have different channel transmission requirements, and in order to match the scheduling requirements of different service types, time domain resource allocation tables corresponding to different service types may be configured independently, and at this time, if one DCI format is supported to schedule different service types, there is no specific scheme for how to use one DCI format to schedule the time domain resource allocation tables corresponding to different service types.
Based on this, the embodiment of the present invention provides a DCI determination scheme, which is used to support a DCI format to schedule time domain resource allocation tables corresponding to different service types. The following describes embodiments of the present invention with reference to the drawings.
In the description process, the implementation of the UE and the base station will be described separately, and then an example of the implementation of the UE and the base station in cooperation will be given to better understand the implementation of the scheme given in the embodiment of the present invention. Such an explanation does not mean that the two must be implemented together or separately, and actually, when the UE and the base station are implemented separately, the UE and the base station solve the problems on the UE side and the base station side, respectively, and when the two are used in combination, a better technical effect is obtained.
Fig. 1 is a schematic implementation flow diagram of a method for determining DCI at a base station side, as shown in the figure, the method includes:
Fig. 2 is a schematic implementation flow diagram of a method for determining DCI on a UE side, as shown in the figure, the method may include:
step 202, receiving DCI, where the DCI schedules different service types using one DCI format, and determines an information bit number included in a time domain resource allocation bit field in the DCI according to a maximum row number of a time domain resource allocation table of the different service types.
Specifically, in the scheme, time domain resource allocation tables of different service types are independently defined or configured, and when one DCI format can schedule different service types, the number of information bits included in a time domain resource allocation bit field in DCI is determined based on the maximum number of rows in the time domain resource allocation tables of different service types.
In an implementation, the DCI format comprises one of the following:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
In the implementation, the time domain resource allocation tables for different service types are defined or configured independently, and the method includes:
a time domain resource allocation table is predefined or configured independently for each service type, specifically, different service types are predefined for the predefined time domain resource allocation table in the protocol, for example, the time domain resource allocation table in the existing protocol is used for eMBB (Enhanced Mobile internet), and in addition, a time domain resource table for URLLC (Ultra high reliability and Ultra Low delay) service is newly defined. For the time domain Resource allocation table configured by the proprietary signaling, configuring different service types respectively, that is, the proprietary signaling configures the time domain Resource allocation table for each service type independently, for example, RRC (Radio Resource Control) proprietary signaling configures a time domain Resource allocation table for eMBB service, and configures a time domain Resource allocation table for URLLC service; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the new DCI format for data scheduling defined by NR Rel-16. Specifically, for the time domain resource allocation tables predefined in the protocol, two time domain resource allocation tables are predefined for different service types, for example, the time domain resource allocation table in the existing protocol is used for the conventional DCI format scheduling eMBB service for data scheduling, and in addition, the time domain resource allocation table corresponding to the DCI format scheduling eMBB service newly defined by NR Rel-16 for data scheduling, the time domain resource allocation table corresponding to the conventional DCI format scheduling URLLC service for data scheduling, and the time domain resource allocation table corresponding to the DCI format scheduling URLLC service newly defined by NR Rel-16 for data scheduling are newly defined.
In a specific implementation, the legacy DCI formats include DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1, and the new DCI format is a DCI format newly defined in addition to the above formats for scheduling PDSCH or PUSCH transmission. In the application, for simplicity of description, a legacy DCI format or a legacy DCI format will be used to represent a legacy DCI format for data scheduling, and a newly defined DCI format or a new DCI format, will be used to represent a new DCI format for data scheduling newly defined by NR Rel-16.
In implementation, when a time domain resource allocation table is predefined or configured independently for each service type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the information bit number is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, and includes:
the number of the information bits is
Wherein, A is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
In implementation, determining the number of rows in the time domain resource allocation table for different service types includes:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format to be A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format to be B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
In practice, the
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
The following is an example.
In the following embodiments, only DCI format 1_1 corresponding to downlink PDSCH and new DCI format are described as examples, but it is easily understood that uplink DCI format 0_1 is similar to the scheduling scheme of downlink DCI format 1_1. For DCI format 0_0 and DCI format 1_0, the time domain resource allocation tables used by them are predefined tables in the protocol, and different predefined tables can be defined for different service types, and the determination scheme of the time domain resource allocation bit field in DCI format 0_0 and DCI format 1_0 is similar to the following manner of determining the time domain resource allocation bit field in DCI when the time domain resource allocation table is configured based on a base station, and is not described one by one.
Example 1:
in this example, a time domain resource allocation table is configured independently for each service type.
Taking PDSCH as an example, the base station configures a time domain resource allocation table for two services, for example, as shown in table 1 below for service type 1, and as shown in table 2 below for service type 2:
table 1: time domain resource allocation for traffic type 1
Table 2: time domain resource allocation for traffic type 2
Then, for DCI format 1_1 or new DCI format for scheduling PDSCH, when determining the number of information bits contained in the time domain resource allocation bit field, first determining that the number of rows in the time domain resource allocation table corresponding to service type 1 is a =8, and the number of rows in the time domain resource allocation table corresponding to service type 2 is B =4, then the number of information bits contained in the time domain resource allocation bit field in DCI format 1_1 or new DCI format is:
due to the fact that
Therefore, only N bits of the time domain resource allocation bit field in the DCI
The bits are valid for the 2 nd service type, that is, the DCI includes a 3-bit time domain resource allocation bit field, where only the first two bits are valid for the 2 nd service type, or only the last two bits are valid for the 2 nd service typeWhether the body uses the first two bits or the last 2 bits is predefined in the protocol.
Example 2:
in this example, a time domain resource allocation table is configured independently for each service type. All rows in each time domain resource allocation table are made up of two parts, one part for legacy DCI formats and the other part for new DCI formats.
Taking PDSCH as an example, the base station configures a time domain resource allocation table for two services, for example, the following table 3 for service type 1 and the following table 4 for service type 2:
table 3: time domain resource allocation for traffic type 1
Table 4: time domain resource allocation for traffic type 2
Where rows 0-7 in Table 3 are for legacy DCI formats, rows 8-11 are for new DCI formats, rows 0-1 in Table 4 are for legacy DCI formats, and rows 2-5 are for new DCI formats.
For the conventional DCI format 1_1 for scheduling PDSCH, when determining the number of information bits contained in the time domain resource allocation bit field, first determining that the number of rows corresponding to DCI format 1_1 in the time domain resource table of service type 1 is a =8, and the number of rows corresponding to DCI format 1_1 in the time domain resource allocation table of service type 2 is B =2, then the number of information bits contained in the time domain resource allocation bit field in DCI format 1_1 is:
due to the fact that
Therefore, only N bits of the time domain resource allocation bit field in the DCI format 1_1 are selected
The bits are valid for the 2 nd traffic type, that is, the DCI format 1_1 includes a 3-bit time domain resource allocation bit field, where only the 1 st bit is valid for the 2 nd traffic type, or only the last 1 bit is valid for the 2 nd traffic type.
Similarly, for a new DCI format for scheduling PDSCH, when determining the number of information bits included in the time domain resource allocation bit field, first determining that the number of rows corresponding to the new DCI format in the time domain resource table of service type 1 is a =4, and the number of rows corresponding to the new DCI format in the time domain resource allocation table of service type 2 is B =4, then the number of information bits included in the time domain resource allocation bit field in the new DCI format is N =
Example 3:
in this example, two time domain resource allocation tables are configured for each traffic type, where one table corresponds to the legacy DCI format and the other table corresponds to the new DCI format.
Taking PDSCH as an example, the base station configures two time domain resource allocation tables for two services, for example, the following tables 5 and 6 for service type 1, and the following tables 7 and 8 for service type 2:
table 5: DCI format 1_1 schedules time domain resource allocation for traffic type 1
Table 6: time domain resource allocation of new DCI format scheduling service type 1
Table 7: DCI format 1_1 schedules time domain resource allocation for traffic type 2
Table 8: time domain resource allocation for new DCI format scheduling traffic type 2
Where table 5 is for DCI format 1_1 scheduling traffic type 1, table 6 is for new DCI format scheduling traffic type 1, table 7 is for DCI format 1_1 scheduling traffic type 2, and table 8 is for new DCI format scheduling traffic type 2.
Then, for DCI format 1_1 for scheduling PDSCH, when determining the number of information bits contained in the time domain resource allocation bit field, first determine that the number of time domain resource table rows of service type 1 corresponding to DCI format 1_1 is a =8, and the number of time domain resource allocation table rows of service type 2 corresponding to DCI format 1_1 is B =2, then the number of information bits contained in the time domain resource allocation bit field in DCI format 1_1 is:
due to the fact that
Therefore, only N bits of the time domain resource allocation bit field in the DCI format 1_1 are selected
Bits are valid for the 2 nd traffic type, that is, the DCI format 1_1 includes a 3-bit time domain resource allocation bit field, where only the 1 st bit is for the 2 nd trafficThe type is valid or only the last 1 bit is valid for the 2 nd traffic type.
Similarly, for a new DCI format for scheduling PDSCH, when determining the number of information bits contained in a time domain resource allocation bit field, first determining that the number of rows of a time domain resource table of service type 1 corresponding to the new DCI format is a =4, and the number of rows of a time domain resource allocation table of service type 2 corresponding to the new DCI format is B =4, then the number of information bits contained in the time domain resource allocation bit field in the new DCI format is N =
Based on the same inventive concept, the embodiment of the present invention further provides a base station, a user equipment, and a DCI determining apparatus, and because the principles of solving the problems of these apparatuses are similar to the DCI determining method, the method may be implemented for these apparatuses, and repeated parts are not described again.
When the technical scheme provided by the embodiment of the invention is implemented, the implementation can be carried out as follows.
Fig. 3 is a schematic structural diagram of a base station, as shown in the figure, the base station includes:
a processor 300 for reading the program in the memory 320, and executing the following processes:
time domain resource allocation tables of different service types are independently configured;
when different service types are scheduled by using a DCI format, determining the information bit number contained in a time domain resource allocation bit field in the DCI according to the maximum line number of a time domain resource allocation table of the different service types;
a transceiver 310 for receiving and transmitting data under the control of the processor 300.
In an implementation, the DCI format comprises one of the following:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the time domain resource allocation tables for different service types are defined or configured independently, including:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to a legacy DCI format for data scheduling and the other table corresponding to a newly defined DCI format for NR Rel-16 for data scheduling.
In implementation, when a time domain resource allocation table is predefined or configured independently for each service type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the information bit number is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, and includes:
the number of the information bits is
Wherein, a is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
In implementation, determining the number of rows in the time domain resource allocation table for different service types includes:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
In practice, the
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
Where in fig. 3, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 300 and memory represented by memory 320. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 310 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The processor 300 is responsible for managing the bus architecture and general processing, and the memory 320 may store data used by the processor 300 in performing operations.
Fig. 4 is a schematic structural diagram of a UE, and as shown in the figure, the UE includes:
a processor 400 for reading the program in the memory 420 to perform data processing according to the processor requirement;
a transceiver 410 for receiving and transmitting data under the control of the processor 400, performing the following processes:
receiving a time domain resource allocation table which is independently configured for different service types by a network side;
receiving DCI, wherein the DCI uses one DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of different service types.
In an implementation, the DCI format comprises one of the following:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
In the implementation, the independently defining or configuring the time domain resource allocation tables of different service types includes:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to a legacy DCI format for data scheduling and the other table corresponding to a newly defined DCI format for NR Rel-16 for data scheduling.
In implementation, when a time domain resource allocation table is predefined or configured independently for each service type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
In implementation, the information bit number is determined according to the maximum number of rows occupied by the time domain resource allocation tables of different service types in the DCI, and includes:
the number of the information bits is
Wherein, A is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
In implementation, determining the number of rows in the time domain resource allocation table for different service types includes:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
In practice, the
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
Where in fig. 4, the bus architecture may include any number of interconnected buses and bridges, with various circuits of one or more processors, represented by processor 400, and memory, represented by memory 420, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 410 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 430 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 400 in performing operations.
The embodiment of the present invention further provides a device for determining DCI at a base station side, including:
the configuration module is used for independently configuring time domain resource allocation tables of different service types;
and the determining module is used for determining the information bit number contained in the time domain resource allocation bit field in the DCI according to the maximum row number of the time domain resource allocation tables of different service types when different service types are scheduled by using one DCI format.
Specific implementation may refer to implementation of the DCI determination method at the base station side.
The embodiment of the invention provides a device for determining DCI (downlink control information) on a UE (user equipment) side, which comprises:
the table receiving module is used for receiving a time domain resource allocation table which is independently configured by a network side for different service types;
and the DCI receiving module is used for receiving the DCI, wherein the DCI uses one DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of the different service types.
Specific implementation may refer to implementation of the DCI determination method on the UE side.
For convenience of description, each part of the above-described apparatus is separately described as being functionally divided into various modules or units. Of course, the functionality of the various modules or units may be implemented in the same one or more pieces of software or hardware in practicing the invention.
The embodiment of the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the processor implements the method for determining DCI.
Specific implementation may refer to implementation of the DCI determination method on the base station side and/or the UE side.
An embodiment of the present invention provides a computer-readable storage medium, which stores a computer program for executing the DCI determination method described above.
Specific implementation may refer to implementation of the DCI determination method on the base station side and/or the UE side.
To sum up, in the technical solution provided in the embodiment of the present invention, the time domain resource allocation tables of different service types are defined or configured independently, and when one DCI format can schedule different service types, the number of information bits included in the time domain resource allocation bit field in the DCI is determined based on the largest number of rows in the time domain resource allocation tables of different service types.
Because the number of information bits contained in the time domain resource allocation bit field in the DCI is determined based on the maximum number of rows in the time domain resource allocation tables of different service types, when the UE is independently configured in the different service type tables and schedules different service types in one DCI format, the base station and the terminal side have consistent understanding on the DCI, and the scheduling process is ensured to be correctly carried out.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (28)
1. A method for determining Downlink Control Information (DCI) is characterized by comprising the following steps:
receiving a time domain resource allocation table independently configured by a network side for different service types;
receiving DCI, wherein the DCI uses one DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of different service types;
the information bit number is determined according to the maximum line number occupied by the time domain resource allocation tables of different service types in the DCI, and the method comprises the following steps:
the number of the information bits is
Wherein, a is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI are selected
The bit is valid for the second traffic type.
2. The method of claim 1, wherein the DCI format comprises one of:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
3. The method of claim 1, wherein independently defining or configuring time domain resource allocation tables for different traffic types is independently defined or configured, comprising:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to a legacy DCI format for data scheduling and the other table corresponding to a newly defined DCI format for NR Rel-16 for data scheduling.
4. A method according to claim 3, wherein when a time domain resource allocation table is predefined or configured independently for each traffic type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
5. The method of claim 1, wherein determining a number of rows in a time domain resource allocation table for different traffic types comprises:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
6. The method of claim 1, wherein the method comprises
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
7. A method for determining DCI (Downlink control information), comprising:
time domain resource allocation tables of different service types are independently configured;
when different service types are scheduled by using a DCI format, determining the information bit number contained in a time domain resource allocation bit field in the DCI according to the maximum row number of time domain resource allocation tables of the different service types;
the information bit number is determined according to the maximum line number occupied by the time domain resource allocation tables of different service types in the DCI, and the method comprises the following steps:
the number of the information bits is
Wherein, A is the maximum line number occupied by the time domain resource allocation table of the first service type in DCI, and B is the second serviceThe maximum line number occupied by the type time domain resource allocation table in the DCI;
if it is used
Only N bits of the time domain resource allocation bit field in the DCI are used
Bit scheduling a first service type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
8. The method of claim 7, wherein the DCI format comprises one of:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
9. The method of claim 7, wherein independently defining or configuring time domain resource allocation tables for different traffic types comprises:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the newly defined DCI format for data scheduling for NR Rel-16.
10. The method of claim 9, wherein when one time domain resource allocation table is predefined or configured independently for each traffic type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
11. The method of claim 7, wherein determining the number of rows in the time domain resource allocation table for different traffic types comprises:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
12. The method of claim 7, wherein the method is as set forth in claim 7
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
13. A user equipment, the user equipment comprising:
the processor is used for reading the program in the memory and processing data according to the requirement of the processor;
a transceiver for receiving and transmitting data under the control of the processor, performing the following processes:
receiving a time domain resource allocation table independently configured by a network side for different service types;
receiving DCI, wherein the DCI uses a DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of different service types;
the information bit number is determined according to the maximum line number occupied by the time domain resource allocation tables of different service types in the DCI, and the method comprises the following steps:
the number of the information bits is
Wherein, A is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the first traffic type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
14. The apparatus of claim 13, wherein the DCI format comprises one of:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
15. The apparatus of claim 13, wherein the time domain resource allocation tables that independently define or configure different traffic types are independently defined or configured, comprising:
predefining or configuring a time domain resource allocation table independently for each service type; or the like, or a combination thereof,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the newly defined DCI format for data scheduling for NR Rel-16.
16. The apparatus of claim 15, wherein when one time domain resource allocation table is predefined or configured independently for each traffic type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one part for the legacy DCI format for data scheduling and the other part for the NR Rel-16 newly defined DCI format for data scheduling.
17. The apparatus of claim 13, wherein determining the number of rows in the time domain resource allocation table for different traffic types comprises:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
18. The apparatus of claim 13, wherein the apparatus is characterized by
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
19. A base station, comprising:
a processor for reading the program in the memory, performing the following processes:
time domain resource allocation tables of different service types are independently configured;
when different service types are scheduled by using a DCI format, determining the information bit number contained in a time domain resource allocation bit field in the DCI according to the maximum row number of time domain resource allocation tables of the different service types;
a transceiver for receiving and transmitting data under the control of the processor;
the information bit number is determined according to the maximum line number occupied by the time domain resource allocation tables of different service types in the DCI, and the method comprises the following steps:
the number of the information bits is
Wherein, a is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI are used
Bit scheduling a first service type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
20. The base station of claim 19, wherein the DCI format comprises one of:
DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, NR Rel-16 newly defined DCI format for data scheduling.
21. The base station of claim 19, wherein independently defining or configuring time domain resource allocation tables for different traffic types comprises:
predefining or configuring a time domain resource allocation table independently for each service type; or,
two time domain resource allocation tables are predefined or configured for each traffic type, one table corresponding to the legacy DCI format for data scheduling and the other table corresponding to the newly defined DCI format for data scheduling for NR Rel-16.
22. The base station of claim 21, wherein when one time domain resource allocation table is predefined or configured independently for each traffic type:
each row in the time domain resource allocation table can be used by a different DCI format; or,
all rows in the time domain resource allocation table are made up of two parts, one for the legacy DCI format for data scheduling and the other for the NR Rel-16 newly defined DCI format for data scheduling.
23. The base station of claim 19, wherein determining the number of rows in the time domain resource allocation table for different traffic types comprises:
determining the number of rows of a time domain resource table corresponding to the first service type as A, and the number of rows of the time domain resource table corresponding to the second service type as B; or,
determining the number of rows of a time domain resource table of a first service type corresponding to the DCI format as A, and the number of rows of a time domain resource table of a second service type corresponding to the DCI format as B; or,
and determining the number of rows corresponding to the DCI format in the time domain resource table of the first service type as A, and determining the number of rows corresponding to the DCI format in the time domain resource table of the second service type as B.
24. The base station of claim 19, wherein said base station is further configured to transmit a signal to said base station
Bit or
The bits are the number of bits that are consecutive from the highest bit among the N bits, or the number of bits that are consecutive from the lowest bit among the N bits.
25. An apparatus for determining DCI, comprising:
the table receiving module is used for receiving a time domain resource allocation table which is independently configured for different service types by a network side;
the DCI receiving module is used for receiving DCI, wherein the DCI uses a DCI format to schedule different service types, and the information bit number contained in a time domain resource allocation bit field in the DCI is determined according to the maximum row number of time domain resource allocation tables of different service types;
the information bit number is determined according to the maximum line number occupied by the time domain resource allocation tables of different service types in the DCI, and the method comprises the following steps:
the number of the information bits is
Wherein, a is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI are used
Bit scheduling a first service type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI are selected
The bit is valid for the second traffic type.
26. An apparatus for determining DCI, comprising:
the configuration module is used for independently configuring time domain resource allocation tables of different service types;
a determining module, configured to determine, when different service types are scheduled in one DCI format, an information bit number included in a time domain resource allocation bit field in the DCI according to the maximum number of rows of the time domain resource allocation tables of the different service types;
the information bit number is determined according to the maximum line number occupied by the time domain resource allocation tables of different service types in the DCI, and the method comprises the following steps:
the number of the information bits is
Wherein, A is the maximum line number occupied by the time domain resource allocation table of the first service type in the DCI, and B is the maximum line number occupied by the time domain resource allocation table of the second service type in the DCI;
if it is not
Only N bits of the time domain resource allocation bit field in the DCI are used
Bit scheduling a first service type; if it is not
Only N bits of the time domain resource allocation bit field in the DCI
The bit is valid for the second traffic type.
27. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 12 when executing the computer program.
28. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910984942.0A CN112671520B (en) | 2019-10-16 | 2019-10-16 | Method, device, apparatus and medium for determining downlink control information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910984942.0A CN112671520B (en) | 2019-10-16 | 2019-10-16 | Method, device, apparatus and medium for determining downlink control information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671520A CN112671520A (en) | 2021-04-16 |
| CN112671520B true CN112671520B (en) | 2023-02-17 |
Family
ID=75400439
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910984942.0A Active CN112671520B (en) | 2019-10-16 | 2019-10-16 | Method, device, apparatus and medium for determining downlink control information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671520B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115298984A (en) * | 2022-06-30 | 2022-11-04 | 北京小米移动软件有限公司 | Method and device for identifying and configuring downlink control information |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017133479A1 (en) * | 2016-02-02 | 2017-08-10 | 电信科学技术研究院 | Method and apparatus for transmitting downlink control information |
| CN108702281A (en) * | 2018-04-04 | 2018-10-23 | 北京小米移动软件有限公司 | The determination method and device of descending control information format size |
| WO2019154185A1 (en) * | 2018-02-12 | 2019-08-15 | 维沃移动通信有限公司 | Downlink control information (dci) transmission method and device, and network device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10912071B2 (en) * | 2018-02-16 | 2021-02-02 | Apple Inc. | Reliability mechanisms for physical downlink control channel (PDCCH) transmissions in new radio (NR) systems |
-
2019
- 2019-10-16 CN CN201910984942.0A patent/CN112671520B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017133479A1 (en) * | 2016-02-02 | 2017-08-10 | 电信科学技术研究院 | Method and apparatus for transmitting downlink control information |
| WO2019154185A1 (en) * | 2018-02-12 | 2019-08-15 | 维沃移动通信有限公司 | Downlink control information (dci) transmission method and device, and network device |
| CN108702281A (en) * | 2018-04-04 | 2018-10-23 | 北京小米移动软件有限公司 | The determination method and device of descending control information format size |
Non-Patent Citations (1)
| Title |
|---|
| "R1-1811810 Summary of 7.1.3.3 (resource allocation)";3GPP;《3GPP tsg_ran\wg1_rl1》;20181009;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671520A (en) | 2021-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109587809B (en) | Method and device for aperiodic SRS | |
| CN109194456B (en) | Method and device in wireless communication | |
| CN110278062A (en) | Resource instruction determines method and device | |
| CN108605340B (en) | Wireless communication method, base station and terminal | |
| US11388049B2 (en) | Resource configuration method and apparatus, and computer storage medium | |
| US11882518B2 (en) | Control information transmission method, base station, and terminal | |
| CN108282293B (en) | Data transmission method, terminal and base station | |
| CN110972275A (en) | Indication information transmission method and device | |
| CN112118627B (en) | Communication method, device, system, base station and computer readable storage medium | |
| CN113543318A (en) | Carrier wave determining and indicating method, equipment, device and medium | |
| CN110225589B (en) | Data transmission method, device and equipment | |
| CN107872883B (en) | Method and device for indicating and determining downlink control information format | |
| CN110324898A (en) | Physical Downlink Shared Channel receives and its time-domain resource indicating means, device, storage medium, base station, terminal | |
| CN110932827A (en) | Transmission method of collateral information, communication equipment and network equipment | |
| CN113660730A (en) | Collision processing and indicating method, equipment, device and medium | |
| CN107453852B (en) | Subframe type notification and determination method and device | |
| CN112671520B (en) | Method, device, apparatus and medium for determining downlink control information | |
| CN109152024B (en) | Indication method, processing method and device | |
| CN109150455B (en) | Indication method, processing method and device | |
| CN112398590B (en) | Method, equipment and device for hybrid automatic repeat request response feedback and reception | |
| CN107295656B (en) | Information transmission method, terminal and base station | |
| CN104469950B (en) | A kind of method, system and equipment sending and receiving data | |
| CN108370558B (en) | Information source determining method, resource allocation method and device | |
| CN111836389B (en) | Uplink resource scheduling method, terminal and network side equipment | |
| CN110708144B (en) | Resource indication method, device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |