Communication method, network device, user equipment, electronic device, and storage medium

Abstract

Embodiments of the present application provide a communication method, network device, user equipment, electronic device and storage medium, and relate to the technical field of communication. The method comprises: indicating, to a user equipment (UE), a range of physical uplink shared channels (PUSCHs) to which a downlink assignment index (UL DAI) in a downlink control information (DCI) is applied when one DCI schedules multiple PUSCHs; and transmitting, to the UE, at least one DCI for scheduling the PUSCHs. The embodiments of the present application can avoid HARQ-ACK feedback on each PUSCH or transmission errors of the PUSCHs caused by missing detection of a downlink DCI, and improve the efficiency of HARQ-ACK feedback.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method, network device, user equipment, electronic device, and storage medium. Background Technology

[0002] In New Radio (NR) R17 high-frequency technology, for certain channel parameters (e.g., SCS = 480kHz / 960kHz), a scheduling method for multiple Physical Downlink Shared Channels (PDSCH) / Physical Uplink Shared Channels (PUSCH) is introduced. That is, one Downlink Control Information (DCI) can schedule multiple PDSCHs, and one DCI can schedule multiple PUSCHs.

[0003] Multiple PUSCH scheduling signaling DCIs include a Downlink Assignment Index (UL DAI) indication information. This information is used to calculate the codebook length of the Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) signal multiplexed onto the PUSCH. When a DCI schedules a PUSCH, the UL DAI is applied to that PUSCH. It should be noted that the Downlink Assignment Index DAI included in the uplink PUSCH scheduling DCI is abbreviated as UL DAI.

[0004] When the relevant technology fails to detect DCI, it can lead to errors in the PUSCH received signal. Summary of the Invention

[0005] The present invention provides a communication method, network device, electronic device, and storage medium that overcomes or at least partially solves the above-mentioned problems.

[0006] Firstly, a communication method is provided, the method comprising:

[0007] Indicate to the User Equipment (UE) the range of PUSCHs covered by the UL DAI when a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes a Downlink Allocation Index (UL DAI).

[0008] Send at least one DCI for scheduling PUSCH to the UE.

[0009] In one possible implementation, the user equipment (UE) is instructed to specify the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI:

[0010] The UE is informed via higher-level signaling configuration that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI is specified.

[0011] In one possible implementation, the UE is instructed via higher-level signaling configuration that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI includes:

[0012] Determine the target state value in a predefined state indication table;

[0013] The target state value is sent to the UE as a parameter for higher-layer signaling configuration;

[0014] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0015] In one possible implementation, the state indicator table includes at least one of a first state value, a second state value, a third state value, and a fourth state;

[0016] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0017] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0018] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0019] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0020] In one possible implementation, the UE is instructed via higher-level signaling configuration that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI includes:

[0021] Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI.

[0022] The bitmap is sent to the UE as a parameter for higher-layer signaling configuration;

[0023] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0024] In one possible implementation, each bit in a predefined bitmap indicates whether the corresponding PUSCH falls within the PUSCH range defined by UL DAI, including:

[0025] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0026] In one possible implementation, the user equipment (UE) is instructed to specify the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI:

[0027] The interface specification protocol with the UE indicates the range of PUSCHs that the UL DAI operates on when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI.

[0028] In one possible implementation, the interface specification protocol with the UE indicates the scope of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including at least one of the following:

[0029] The first interface specification protocol information is defined in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0030] The second interface specification protocol information is defined in the interface specification protocol. The second interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI is applied to the last PUSCH.

[0031] The third interface specification protocol information is defined in the interface specification protocol. The third interface specification protocol information is used to indicate that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0032] The fourth interface specification protocol information is defined in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0033] Secondly, a communication method is provided, including:

[0034] If it is determined that the DCI to be sent is used to schedule multiple PUSCHs and the DCI includes UL DAI, then information indicating the range of PUSCHs in which UL DAI operates is set in the DCI.

[0035] Send DCI to UE.

[0036] In one possible implementation, information indicating the PUSCH range of the UL DAI operation is set in the DCI, including:

[0037] Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI.

[0038] The bitmap is set in the DCI to be transmitted as information indicating the range of PUSCH for the UL DAI to function;

[0039] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0040] In one possible implementation, each bit in a predefined bitmap indicates whether the corresponding PUSCH falls within the PUSCH range defined by UL DAI, including:

[0041] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0042] In one possible implementation, information indicating the PUSCH range of the UL DAI operation is set in the DCI, including:

[0043] Determine at least one target bit number combination from a predefined bit number combination table;

[0044] At least one target bit array is combined into information indicating the PUSCH range of the UL DAI operation and set in the DCI to be transmitted;

[0045] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0046] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0047] In one possible implementation, information indicating the PUSCH range of the UL DAI operation is set in the DCI, including:

[0048] If it is determined that the number of PUSCHs scheduled for the DCI to be sent is less than the maximum number of PUSCHs, then the range indication information is recorded according to the target bit bits of the RV and / or NDI in the DCI to be sent.

[0049] The target bit is the bit in RV and / or NDI that does not indicate PUSCH.

[0050] Thirdly, a communication method is provided, including:

[0051] When a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), the range of PUSCHs that the UL DAI applies to is indicated by the receiving network device.

[0052] The receiver receives at least one DCI for scheduling PUSCH from the network device. When the DAI includes UL DAI, it feeds back a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) signal within the PUSCH range covered by the UL DAI.

[0053] In one possible implementation, when the receiving network device indicates that a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), the range of PUSCHs covered by the UL DAI includes:

[0054] The PUSCH range of the UL DAI indicated by the network device is obtained through high-level signaling configuration.

[0055] In one possible implementation, the PUSCH range of the UL DAI action indicated by the network device is obtained through higher-level signaling configuration, including:

[0056] When the higher-layer signaling configuration indicates the range of PUSCHs in which UL DAI operates with a target status value, the range of PUSCHs in which UL DAI operates corresponding to the target status value is searched in the predefined status indication table.

[0057] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0058] In one possible implementation, the state indicator table includes at least one of a first state value, a second state value, a third state value, and a fourth state;

[0059] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0060] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0061] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0062] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0063] In one possible implementation, the PUSCH range of the UL DAI action indicated by the network device is obtained through higher-level signaling configuration, including:

[0064] When the higher-layer signaling configuration uses a bitmap to indicate the range of PUSCHs covered by UL DAI, it determines whether the corresponding PUSCH belongs to the range of PUSCHs covered by UL DAI based on each bit in the bitmap.

[0065] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0066] In one possible implementation, determining whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap includes:

[0067] For any given bit, if the bit value is a first preset value, it indicates that the corresponding PUSCH belongs to the PUSCH range operated by UL DAI; if the bit value is a second preset value, it indicates that the corresponding PUSCH does not belong to the PUSCH range operated by UL DAI.

[0068] In one possible implementation, when the receiving network device indicates that a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), the range of PUSCHs covered by the UL DAI includes:

[0069] By using the interface specification protocol with network devices, the range of PUSCHs that UL DAI operates on is determined when a DCI schedules multiple PUSCHs and the DCI includes UL DAI.

[0070] In one possible implementation, the scope of PUSCHs covered by the UL DAI is determined through the interface specification protocol with the network device, when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0071] When the interface specification protocol defines the first interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0072] When the interface specification protocol defines the second interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the last PUSCH.

[0073] When the third interface specification protocol information is defined in the interface specification protocol, it is determined that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0074] When the fourth interface specification protocol information is defined in the interface specification protocol, it is determined that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0075] Fourthly, a communication method is provided, including:

[0076] Receive DCI sent by network devices;

[0077] Parse the DCI to obtain information about the range of PUSCHs that the UL DAI is active in when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI.

[0078] When the received DAI includes the UL DAI, a hybrid automatic repeat request acknowledgment signal (HARQ-ACK) is fed back within the PUSCH range of the UL DAI.

[0079] In one possible implementation, obtaining information about the range of PUSCHs covered by the UL DAI, as indicated by the network device when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, includes:

[0080] Obtain information in the form of a bitmap;

[0081] Determine whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bit diagram.

[0082] In one possible implementation, determining whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap includes:

[0083] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0084] In one possible implementation, obtaining information about the range of PUSCHs covered by the UL DAI, as indicated by the network device when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, includes:

[0085] Obtain information in the form of a target number of bits;

[0086] Search within the predefined bit combination packets for the PUSCH range of UL DAI action corresponding to the target bit combination;

[0087] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0088] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0089] In one possible implementation, obtaining information about the range of PUSCHs covered by the UL DAI, as indicated by the network device when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, includes:

[0090] Obtain information in the form of the target bits of RV and / or NDI in the DCI;

[0091] Search the preset DCI information field table for the PUSCH range of UL DAI action corresponding to the number of bits on the target bit.

[0092] The bit number combination table includes at least one bit number and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit number.

[0093] Fifthly, a network device is provided, comprising:

[0094] The indication module is used to indicate to the user equipment (UE) the range of PUSCHs in which the UL DAI is applied when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI).

[0095] The first DCI sending module is used to send at least one DCI for scheduling PUSCH to the UE.

[0096] In one possible implementation, the instruction module includes:

[0097] The higher-layer signaling configuration module is used to indicate to the UE the range of PUSCHs covered by UL DAI when a DCI schedules multiple PUSCHs and the DCI includes UL DAI.

[0098] The high-level signaling configuration module includes:

[0099] A state value determination unit is used to determine the target state value from a predefined state indication table;

[0100] The first configuration parameter unit is used to send the target state value as a parameter for higher-layer signaling configuration to the UE;

[0101] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0102] In one possible implementation, the state indicator table includes at least one of a first state value, a second state value, a third state value, and a fourth state;

[0103] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0104] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0105] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0106] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0107] In one possible implementation, the high-level signaling configuration module includes:

[0108] The bitmap indicator unit is used to indicate whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the predefined bitmap.

[0109] The second configuration parameter unit is used to send the bit map as a parameter for higher-layer signaling configuration to the UE;

[0110] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0111] In one possible implementation, the bitmap indicator unit is used for:

[0112] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0113] In one possible implementation, the instruction module includes:

[0114] The interface protocol module is used to indicate the range of PUSCHs that UL DAI operates on when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, through the interface specification protocol with the UE.

[0115] In one possible implementation, the interface protocol module includes at least one of the following:

[0116] The first protocol information unit is used to define the first interface specification protocol information in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0117] The second protocol information unit is used to define the second interface specification protocol information in the interface specification protocol. The second interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI is applied to the last PUSCH.

[0118] The third protocol information unit is used to define the third interface specification protocol information in the interface specification protocol. The third interface specification protocol information is used to indicate that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0119] The fourth protocol information unit is used to define the fourth interface specification protocol information in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0120] Sixthly, a network device is provided, comprising:

[0121] The DCI setting module is used to set information in the DCI indicating the range of PUSCHs in which the UL DAI operates if it is determined that the DCI to be sent is used to schedule multiple PUSCHs and the DCI includes UL DAI.

[0122] The second DCI transmission module is used to send DCI to the UE.

[0123] In one possible implementation, the DCI setup module includes:

[0124] The bit indication module is used to indicate whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the predefined bit diagram.

[0125] The information addition module is used to set the bit map as information indicating the PUSCH range of UL DAI in the DCI to be sent;

[0126] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0127] In one possible implementation, the bit indication module is specifically used for:

[0128] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0129] In one possible implementation, the DCI setup module includes:

[0130] A bit combination definition module is used to determine at least one target bit combination from a predefined bit combination table;

[0131] A bit addition module is used to combine at least one target bit array into information indicating the range of PUSCH indicating the action of UL DAI, set in the DCI to be transmitted;

[0132] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0133] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0134] In one possible implementation, the DCI setup module includes:

[0135] The scheduling record module is used to record information indicating the range of PUSCHs that the UL DAI operates on, based on the target bits of the RV and / or NDI in the DCI to be sent, if it is determined that the number of PUSCHs scheduled for the DCI to be sent is less than the maximum number of PUSCHs scheduled.

[0136] The target bit is the bit in RV and / or NDI that does not indicate PUSCH.

[0137] Fifthly, a user equipment is provided, comprising:

[0138] The instruction receiving module is used to receive the range of PUSCHs that the UL DAI applies to when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI).

[0139] The feedback module is used to receive at least one DCI for scheduling PUSCH sent by the network device. When the DAI includes UL DAI, it feeds back a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) signal within the PUSCH range where the UL DAI is active.

[0140] As an optional implementation, the instruction receiving module includes:

[0141] The higher-layer signaling configuration receiving module is used to obtain the PUSCH range of the ULDAI action indicated by the network device through higher-layer signaling configuration.

[0142] As an optional implementation, the higher-layer signaling configuration receiving module includes:

[0143] The status value parsing unit is used to search in a predefined status indication table for the PUSCH range of the UL DAI that corresponds to the target status value when the higher-layer signaling configuration indicates the PUSCH range of the UL DAI.

[0144] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0145] As an optional implementation, the status indicator table includes at least one of a first status value, a second status value, a third status value, and a fourth status;

[0146] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0147] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0148] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0149] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0150] As an optional implementation, the higher-layer signaling configuration receiving module includes:

[0151] The bitmap parsing unit is used to determine whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap when the higher layer signaling configuration indicates the PUSCH range of UL DAI using a bitmap.

[0152] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0153] As an optional implementation, the bitmap parsing unit includes:

[0154] For any given bit, if the bit value is a first preset value, it indicates that the corresponding PUSCH belongs to the PUSCH range operated by UL DAI; if the bit value is a second preset value, it indicates that the corresponding PUSCH does not belong to the PUSCH range operated by UL DAI.

[0155] As an optional implementation, the instruction receiving module includes:

[0156] The interface protocol receiving module is used to determine the range of PUSCHs covered by UL DAI when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, by means of the interface specification protocol with the network device.

[0157] As an optional implementation, the interface protocol receiving module includes:

[0158] The first interface information parsing unit is used to determine, when the interface specification protocol defines the first interface specification protocol information, that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0159] The second interface information parsing unit is used to determine, when the interface specification protocol defines the second interface specification protocol information, that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI is applied to the last PUSCH.

[0160] The third interface information parsing unit is used to determine, when the third interface specification protocol information is defined in the interface specification protocol, that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0161] The fourth interface information parsing unit is used to determine, when the fourth interface specification protocol information is defined in the interface specification protocol, that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0162] Sixthly, a user equipment is provided, comprising:

[0163] The DCI receiver module is used to receive DCI signals sent by network devices.

[0164] The parsing module is used to parse the DCI and obtain information about the range of PUSCHs that the UL DAI is active in when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, as indicated by the network device.

[0165] The second feedback module is used to feed back a hybrid automatic repeat request acknowledgment signal (HARQ-ACK) within the PUSCH range of the UL DAI when the received DAI includes the UL DAI.

[0166] As an optional implementation, the parsing module includes:

[0167] Bitmap acquisition unit, used to obtain information in the form of a bitmap;

[0168] The bit resolution unit is used to determine whether the corresponding PUSCH belongs to the PUSCH range of ULDAI based on each bit in the bit map.

[0169] As an optional implementation, the bit parsing unit is specifically used for:

[0170] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0171] As an optional implementation, the parsing module includes:

[0172] The bit combination acquisition unit is used to obtain information in the form of a target bit combination;

[0173] The combination search unit is used to search for the range of PUSCH that corresponds to the ULDAI action in a predetermined number of bit combinations;

[0174] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0175] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0176] As an optional implementation, the parsing module includes:

[0177] Bit identification unit, used to obtain information in the form of target bit bits in DCI and / or NDI;

[0178] The bit number search unit is used to search the PUSCH range of UL DAI corresponding to the number of bits on the target bit in the preset DCI information field table;

[0179] The bit number combination table includes at least one bit number and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit number.

[0180] In a seventh aspect, a network device is provided, including a memory, a transceiver, and a processor:

[0181] A memory for storing computer programs; a transceiver for sending and receiving data under the control of a processor; and a processor for reading the computer program from the memory and executing the steps of the method provided in either the first or second aspect.

[0182] Eighthly, a user equipment is provided, including a memory, a transceiver, and a processor:

[0183] A memory is used to store computer programs; a transceiver is used to send and receive data under the control of a processor; and a processor is used to read the computer programs from the memory and execute the steps of the method provided in either the third or fourth aspect.

[0184] In a ninth aspect, embodiments of the present invention provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method provided in any one of the first to fourth aspects.

[0185] In a tenth aspect, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the methods provided in the first to fourth aspects.

[0186] Eleventhly, embodiments of the present invention provide a computer program including computer instructions stored in a computer-readable storage medium. When a processor of a computer device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, causing the computer device to perform steps implementing the methods provided in any of the first to fourth aspects.

[0187] The communication method, network device, electronic device, and storage medium provided in this invention instruct the User Equipment (UE) on the range of PUSCHs covered by the UL DAI when a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes a Downlink Allocation Index (UL DAI); and send at least one DCI for scheduling PUSCHs to the UE. This embodiment of the application avoids HARQ-ACK feedback for each PUSCH or PUSCH transmission errors due to missed downlink DCI detection, thus improving HARQ-ACK feedback efficiency. Attached Figure Description

[0188] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0189] Figure 1 This is a schematic diagram illustrating the PDCCH detection capability in units of time slot groups according to an embodiment of this application;

[0190] Figure 2 This is a schematic diagram of a dynamic codebook according to an embodiment of this application;

[0191] Figure 3 This is a schematic diagram illustrating the problem to be solved in the embodiments of this application;

[0192] Figure 4A schematic diagram of the existing R15 / R16 UL DAI time slot application;

[0193] Figure 5 A diagram illustrating the problems existing in the current technology;

[0194] Figure 6 This is a schematic architecture diagram of a system according to an embodiment of this application;

[0195] Figure 7 This is a flowchart illustrating the communication method according to an embodiment of this application;

[0196] Figure 8 This is a schematic diagram illustrating an application scenario in which the PUSCH range of the UL DAI is determined by high-level signaling status indication according to an embodiment of this application.

[0197] Figure 9 This is a schematic diagram illustrating the application scenario of PUSCH determining the role of UL DAI through a high-layer signaling bit map in an embodiment of this application.

[0198] Figure 10 This is a flowchart illustrating a communication method according to another embodiment of this application;

[0199] Figure 11 This is a schematic diagram of the network device according to an embodiment of this application;

[0200] Figure 12 This is a schematic diagram of the structure of a network device according to another embodiment of this application;

[0201] Figure 13 This is a schematic diagram of the structure of a network device according to another embodiment of this application;

[0202] Figure 14 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0203] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting the invention.

[0204] Those skilled in the art will understand that, unless explicitly stated otherwise, the singular forms “a,” “an,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in the specification of this application means the presence of features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

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

[0206] First, let's introduce and explain several terms used in this application:

[0207] 1. Definition of PDCCH detection capability based on multiple time slots (time slot groups)

[0208] In high-frequency operation, for channels with SCS = 480 / 960kHz, the detection capability of the Physical Downlink Control Channel (PDCCH) is defined in units of time slot groups; that is, the terminal's detection capability is defined in units of time slot groups. For example:

[0209] Table 1. UE PDCCH Detection Capability Definition (by time slot group)

[0210]

[0211] The PDCCH detection capability values ​​in Table 1 are hypothetical values ​​and can be other numbers, which are not restricted here. The number of time slots M is an integer, and 4 / 8 / 16 are examples, which can be other numbers, which are not restricted here.

[0212] Here, we take SCS=960 as an example, where all PDCCH detection opportunities are distributed in one time slot of a time slot group, to illustrate the PDCCH detection capability at the time slot group level (M=8, that is, one time slot group contains 8 time slots).

[0213] Please see Figure 1The figure illustrates a schematic diagram of the PDCCH detection capability in a time slot group according to an embodiment of this application. As shown in the figure, in a time slot group of 8 time slots, only the first time slot is configured with a PDCCH detection opportunity, and there is no PDCCH detection opportunity on other time slots. That is, the base station will only send scheduling information DCI on the first time slot. The DCI includes scheduling downlink PDSCH and scheduling uplink PUSCH.

[0214] Based on the above definition of PDCCH detection capability using multiple time slots as units, the standard discussion supports one DCI scheduling multiple PUSCH / PDSCH, and the multiple PUSCH / PDSCH can be discontinuously distributed in the time domain.

[0215] 2. HARQ-ACK dynamic codebook (type-2) mechanism

[0216] In existing 5G systems, a dynamic HARQ-ACK codebook generation mechanism is supported. The principle is as follows: when sending scheduling signaling (DCI), a DAI indicator is added. The terminal side calculates the number of DCI and PDSCH actually sent by the base station based on the DAI count, thereby determining the number of PDSCH that need to be fed back in the HARQ-ACK codebook.

[0217] Please see Figure 2 The diagram above illustrates an example of the dynamic codebook of an embodiment of this application. The base station schedules 7 PDSCHs to the terminal. The scheduling information indicates that the PUCCH feedback time slots are located in the same time slot, and it expects to feed back HARQ-ACK information for 7 PDSCHs (if each PDSCH corresponds to one HARQ-ACK bit feedback, then the HARQ-ACK codebook is 7). Due to the uncertainty of the wireless channel, DCI-5 and DCI-6 are missed by the terminal. The terminal receives scheduling signaling DCI-7 with C-DAI = 3 (corresponding to bit information indicating 10), and the previously received DCI-4 had C-DAI = 4. Therefore, the terminal can determine from the DAI value that 2 DCIs were lost between DCI-4 and DCI-7. Thus, the terminal can still calculate the total number of PDSCHs fed back by HARQ-ACK to be 7.

[0218] In the existing technology, it is assumed that the number of DCIs that the terminal misses consecutively will not exceed 3. Therefore, the DAI in the example uses 2-bit information indication, which is called counter downlink assignment indicator (C-DAI).

[0219] Additionally, to support HARQ feedback on multiple carriers, T-DAI (total DAI) is introduced on top of C-DAI. It uses 2-bit information indication. C-DAI and T-DAI are used together to determine the number of PDSCHs that are actually fed back, thereby determining the codebook length of HARQ-ACK.

[0220] 3. Uplink DAI (UL DAI)

[0221] When the DCI schedules a PUSCH, the scheduled PUSCH may transmit HARQ-ACK codebook information. To ensure the terminal accurately calculates the length of the HARQ-ACK codebook multiplexed on the PUSCH, an indication of UL DAI is added to the DCI that schedules the PUSCH. When calculating the HARQ codebook, the terminal uses UL DAI as T-DAI to calculate the length of the HARQ codebook.

[0222] The existing DCI with format 0_1 ​​carries a copy of UL DAI information. When this DCI schedules multiple PUSCHs, it cannot determine the range of PUSCHs to which the UL DAI information domain applies. Please refer to [link to relevant documentation]. Figure 3 The figure illustrates a schematic diagram of the problem to be solved in the embodiment of this application. As shown in the figure, when the uplink PUSCH scheduling signaling DCI includes UL DAI=3, the UE cannot determine which PUSCH(s) to send a total of 3 HARQ-ACKs.

[0223] Current standards do not provide a method for applying UL DAI information when a DCI schedules multiple PUSCHs.

[0224] A scenario similar to the problem scenario: when a DCI schedules a PUSCH and the PUSCH is sent repeatedly, UL DAI is applied to the time slot where the UE is preparing to perform HARQ-ACK for multiplexing.

[0225] If the PUSCH transmission is carried out on multiple time slots, and the DCI is scheduled to include a DCI field, then the DAI field should be used on the time slot where the UE is preparing to perform HARQ-ACK multiplexing.

[0226] It should be noted that the "time slot for preparing HARQ-ACK multiplexing" mentioned above is understood to be determined by the terminal based on the downlink PDSCH scheduling DCI. Specifically, if the terminal receives the PDSCH scheduling DCI, it performs HARQ-ACK multiplexing; if the terminal does not receive the PDSCH scheduling DCI, it does not perform HARQ-ACK multiplexing. (The terminal not receiving the PDSCH scheduling DCI falls into two categories: 1. The base station did not send it; 2. The base station sent it, but the terminal missed detecting it.)

[0227] Please see Figure 4 The diagram illustrates an example of the existing R15 / R16 UL DAI timeslot application. As shown, the base station transmits three DCIs: DCI-1 schedules a PDSCH indicating HARQ-ACK feedback on timeslot n; DCI-1 schedules another PDSCH indicating HARQ-ACK feedback on timeslot n+2; DCI-3 schedules multiple PUSCHs, transmitting on timeslots n / n+1 / n+2 / n+3, with UL DAI = 1. The base station wants 1 bit of HARQ-ACK to be transmitted on the PUSCH of timeslot n and 1 bit of HARQ-ACK to be transmitted on the PUSCH of timeslot n+2. The terminal receives DCI-1 and DCI-3, but misses DCI-2. Therefore, the terminal only feeds back 1 bit of HARQ-ACK on the PUSCH of timeslot n and no HARQ-ACK information on timeslot n+2.

[0228] The problem with the existing technology is that, for dynamic (Type-2) HARQ codebooks, if DCI is missed, it will lead to PUSCH reception errors.

[0229] Please see Figure 5 The diagram above illustrates a problem with the existing technology. Assume the base station is configured with dynamic HARQ codebook feedback. Assume DCI-1 schedules 8 PDSCHs, and k1 in the scheduling signaling is 3, indicating the time slot of the PUCCH used to transmit HARQ-ACK. Assume DCI-2 schedules 4 PUSCHs (PUSCH0 / 1 / 2 / 3), where the time slot of PUSCH0 indicated by DCI-1 is the same as the time slot of PUCCH.

[0230] Terminal side: Assuming the terminal loses the DCI-1 scheduling signaling, according to the existing R15 protocol, the terminal will not send HARQ-ACK on PUSCH-0 (PUSCH is encoded at coding rate 1).

[0231] Problem: In the above scenario, if the terminal receives the PUSCH based on the assumption of multiplexing HARQ-ACK in PUSCH-0, and since the HARQ-ACK feedback information is 8 bits (greater than 2 bits), the base station will recalculate the PUSCH transmission resources and coding rate to receive the PUSCH (e.g., decoding the PUSCH according to coding rate 2). This leads to PUSCH decoding errors.

[0232] Similarly, for static HARQ-ACK codebook generation, DCI miss detection will also lead to PUSCH decoding errors.

[0233] In the above, if PUSCH transmission occurs across multiple time slots, and the DCI scheduling includes a UL DAI field, then this DAI field is determined based on the DCI scheduling status of the UE receiving the PDSCH (e.g., when the UE receives the PDSCH scheduling signaling DCI, and the feedback HARQ-ACK is in the corresponding PUSCH, the UL DAI is applied to that PUSCH; otherwise, it is not applied). PUSCH demodulation will fail when the following DCI scheduling loss scenarios exist:

[0234] 1. On the corresponding PUSCH, a HARQ-ACK response is sent for one DCI-scheduled PDSCH. This DCI schedules three or more PDSCHs, and the terminal misses detecting this DCI.

[0235] 2: On the corresponding PUSCH, HARQ-ACK feedback is provided for two DCI-scheduled PDSCHs. The sum of the number of DCIs in these two DCI-scheduled PDSCHs is greater than or equal to 3, and the terminal misses detecting these two DCIs.

[0236] 3: On the corresponding PUSCH, HARQ-ACK feedback is provided for the PDSCHs scheduled by three DCIs. The sum of the number of DCIs in these three DCI-scheduled PDSCHs is greater than or equal to 3, and the terminal misses all three DCIs.

[0237] The communication methods, network devices, electronic devices, and computer-readable storage media provided in this application are intended to solve the above-mentioned technical problems of the prior art.

[0238] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0239] Figure 6 This is a schematic architecture diagram of a system according to an embodiment of this application.

[0240] The base station provided in this application embodiment can be a base station (Node B, NB) under Universal Mobile Telecommunications System (UMTS), an evolved Node B (eNB) under Long Term Evolution (LTE), or a base station or controller under 5G mobile communication system.

[0241] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0242] Furthermore, the technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems may include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0243] Please see Figure 7 The figure illustrates a flowchart of a communication method according to an embodiment of this application. This communication method is applied to a base station. As shown, the method includes:

[0244] S101. Indicate to the UE the range of PUSCHs that UL DAI operates when a DCI schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes UL DAI.

[0245] S102, Send at least one DCI for scheduling PUSCH to the UE.

[0246] It should be understood that after receiving the DCI used for scheduling PUSCH, the UE sends HARQ-ACK messages on the PUSCHs within the indicated PUSCH range. This embodiment of the application indicates the PUSCH range for UL DAI application in a multi-PUSCH scheduling scenario. For PUSCHs using UL DAI, the terminal needs to generate a HARQ-ACK codebook based on the UL DAI, regardless of whether the UE receives the corresponding downlink PDSCH scheduling DCI. This avoids performing HARQ-ACK feedback on every PUSCH and prevents PUSCH transmission errors caused by missed downlink PDSCH scheduling on the terminal side, thus improving HARQ-ACK feedback efficiency.

[0247] Based on the above embodiments, as an optional embodiment, this application embodiment indicates to the user equipment the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0248] The UE is informed via higher-level signaling configuration that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI is specified.

[0249] This application embodiment can implement higher-level signaling configuration through higher-level signaling state combination indication. Specifically, the higher-level signaling configuration indicates to the UE the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0250] Determine the target state value in a predefined state indication table;

[0251] The target state value is sent to the UE as a parameter for higher-layer signaling configuration;

[0252] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0253] In this embodiment, the base station uses a state combination indication method to determine the range of PUSCHs that UL DAI can operate on when a DCI schedules multiple PUSCHs through higher-layer signaling configuration.

[0254] This indicates the range of the ULDAI's applied pressure. There are N states (N ≥ 1), and each state represents the range of the ULDAI's applied pressure. The following example uses N = 4; please refer to Table 1:

[0255]

[0256]

[0257] Table 1 Status Indicator Table

[0258] In the table above, X represents the number of PUSCHs scheduled by DCI, and M is an integer greater than 1, such as the number of time slots contained in the PDCCH detection time slot group. Alternatively, PUSCHs can be restricted to valid PUSCHs. Valid means that the terminal removes some PUSCHs that cannot be sent, leaving only the PUSCHs that can be sent (e.g., the scheduled PUSCH contains downlink symbols). Furthermore, in the above conditions, X <= M / 2 or X > M / 2 can also be set.

[0259] Assuming that in the above N=4 states, the base station indicates state 1, that is, the target state value is determined to be 0, when the terminal receives multiple PUSCH schedules, if it contains 1 UL DAI, then HARQ-ACK information is transmitted only on the first valid PUSCH, that is, HARQ-ACK is multiplexed onto the PUSCH.

[0260] like Figure 8 As shown, this example illustrates an application scenario where the range of PUSCHs affected by UL DAI is determined through higher-layer signaling status indication according to an embodiment of this application. Assuming the base station is configured with dynamic HARQ codebook feedback, DCI-0 schedules 8 PDSCHs, and k1 in the scheduling signaling is 3, indicating the time slot of the PUCCH used for transmitting HARQ-ACK. Assuming DCI-1 schedules 4 PUSCHs (PUSCH0 / 1 / 2 / 3), where the time slot of PUSCH0 indicated by DCI-1 is the same as the time slot of the PUCCH, HARQ-ACK information needs to be transmitted on PUSCH-0, and the length of the HARQ-ACK information is calculated using the UL DAI in DCI-1.

[0261] On the terminal side, the terminal missed detecting DCI-0, but since DCI-1 indicates UL DAI=1 and the scope of UL CAI is known to be the first PUSCH, i.e. PUSCH0, according to the higher-layer signaling configuration, the terminal still transmits 8 bits of HARQ-ACK information on PUSCH-0 according to UL DAI, ensuring that PUSCH-0 is sent and received at the expected code rate.

[0262] When the contents of the table above are configured via higher-level signaling, they indicate the scope of UL DAI's PUSCH. When the higher-level signaling is not configured, it can be represented by another meaning (i.e., the default indication method).

[0263] For example: Suppose that the higher-level signaling state combination is defined in the PUSCH configuration information and is optional, as shown below:

[0264] PUSCH-ConfigCommon::=SEQUENCE{ / / PUSCH configuration information}

[0265] pusch-TimeDomainAllocationList OPTIONAL / / PUSCH's time-domain scheduling parameter table, optional

[0266] ULDAIApplyPUSCHstateindicationOPTIONAL / / State combination indicator, optional

[0267] }

[0268] The state combination indicator (ULDAIApplyPUSCHstateindication) defines only one state and is expressed as "acts on 1 PUSCH and is the last valid PUSCH".

[0269] If configured during actual execution, it means "UL DAI applies to 1 PUSCH, and is the last valid PUSCH". If not configured, it can be interpreted in another way, such as "applies to 1 PUSCH, and is the first valid PUSCH".

[0270] Based on the above embodiments, for PUSCHs outside the scope of USCH application, if a DCI for the corresponding PDSCH is received, indicating that HARQ-ACK information is to be transmitted on these PUSCHs, the terminal can use any of the following methods (configurable by the protocol):

[0271] - Calculate HARQ-ACK feedback information using UL DAI in the DCI of the scheduling PUSCH.

[0272] - Calculate HARQ-ACK feedback information using DAI in the DCI of the scheduled PDSCH.

[0273] Based on the above embodiments, the higher-layer signaling status indication can be sent to the UE via broadcast message, RRC message or MAC-CE message. This application embodiment does not impose specific limitations.

[0274] Based on the above embodiments, as an optional embodiment, the UE is instructed via higher-layer signaling configuration to determine the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI. This range includes:

[0275] Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI.

[0276] The bitmap is sent to the UE as a parameter for higher-layer signaling configuration;

[0277] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0278] Specifically, each bit in the predefined bitmap indicates whether the corresponding PUSCH belongs to the PUSCH range controlled by ULDAI, including:

[0279] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0280] The embodiments of this application indicate the scope of the UL DAI's action on the PUSCH, which can be indicated by a bit map N, where N is equal to the maximum number of PUSCHs that a DCI can schedule (e.g., N = 8). Each bit corresponds to a scheduled PUSCH, with "1" indicating that the PUSCH is acted on, "0" indicating that the PUSCH is not acted on, or vice versa.

[0281] The following example uses N=8. For instance, when the bitmap is 1,0,0,0,0,0,0,0, it indicates that UL DAI operates on 1 PUSCH, specifically the first PUSCH; when the bitmap is 0,0,0,0,0,0,0,1, it indicates that UL DAI operates on 1 PUSCH, specifically the last PUSCH; when the bitmap is 0,1,0,0,0,0,0,0, it indicates that UL DAI operates on 1 PUSCH, specifically the second PUSCH; when the bitmap is 1,0,0,0,1,0,0,0, it indicates that UL DAI operates on 1 or 2 PUSCHs.

[0282] --When X<=M / 2, UL DAI is applied to the first scheduled PUSCH.

[0283] --When X>M / 2, UL DAI applies the effective PUSCH in the 1st and (1+M / 2)th scheduling.

[0284] Where M is an integer greater than 1.

[0285] like Figure 9As shown in the figure, this embodiment of the present application illustrates an application scenario where the PUSCH for determining the role of UL-DAI is determined through a higher-layer signaling bitmap. Assume the base station is configured with dynamic HARQ codebook feedback. Assume DCI-0 schedules 4 PDSCHs, and k1 in the scheduling signaling is 8, indicating the time slot of the PUCCH used for transmitting HARQ-ACK. Assume DCI-1 schedules 4 PDSCHs, and k1 in the scheduling signaling is 7, indicating the time slot of the PUCCH used for transmitting HARQ-ACK. Assume DCI-1 schedules 6 PUSCHs (PUSCH0 / 1 / 2 / 3 / 4 / 5), then the terminal uses UL-DAI on PUSCH0 and PUSCH4.

[0286] Additionally, assuming the terminal misses DCI-1, but because DCI-1 indicates UL DAI=1 and the PUSCH coverage area is known from the bitmap, the terminal will still transmit 4 bits of HARQ-ACK information on PUSCH-4 based on UL DAI. This ensures that PUSCH-4 transmits and receives data at the expected rate.

[0287] Additionally: When the UL DAI is used on two or more PUSCHs, the example assumes that there is only one UL DAI in the DCI. However, in the standard, two or more UL DAIs can also be indicated in the DCI, which can be respectively mapped to the corresponding PUSCHs. No restrictions are imposed here.

[0288] It should be noted that when the above table content is configured through higher-level signaling, it indicates the scope of UL DAI's PUSCH. When the higher-level signaling is not configured, it can be represented by another meaning (i.e., the default indication method).

[0289] For example: Suppose the higher-layer signaling bit map is defined in the PUSCH configuration information and is optional, as shown below:

[0290] PUSCH-ConfigCommon::=SEQUENCE{ / / PUSCH configuration information}

[0291] pusch-TimeDomainAllocationListOPTIONAL / / PUSCH's time-domain scheduling parameter table, optional

[0292] ValidPuschWithinGroupBIT STRING(b0,b1,b2,b3,b4,b5,b6,b7) OPTIONAL / / Bitmap, optional

[0293] }

[0294] If there is no configuration, it can be interpreted in another way, such as UL DAI being invalid, meaning it does not apply to any PUSCH. In this case, UL DAI in DCI can be interpreted in other ways (such as PUSCH channel coding version information, HARQ process information, etc.).

[0295] For PUSCHs other than the specific PUSCHs for which UL DAI is applied as indicated in this embodiment, if a DCI for the corresponding PDSCH is received, indicating that HARQ-ACK information is transmitted on these PUSCHs, the terminal may use any of the following methods (configurable by the protocol):

[0296] - Calculate HARQ-ACK feedback information using UL DAI in the DCI of the scheduling PUSCH.

[0297] - Calculate HARQ-ACK feedback information using DAI in the DCI of the scheduled PDSCH.

[0298] - Discard the PUSCH, or discard the HARQ-ACK message that needs to be transmitted.

[0299] - The terminal considers the simultaneously received PUSCH scheduling information and HARQ-ACK indication information to be invalid (i.e., the terminal does not want to receive this scheduling signaling).

[0300] The aforementioned higher-level signaling can be sent to the UE via broadcast messages, RRC messages, or MAC-CE messages; no specific restrictions are imposed here.

[0301] Based on the above embodiments, as an optional embodiment, the user equipment (UE) is instructed to specify the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0302] The interface specification protocol with the UE indicates the range of PUSCHs that the UL DAI operates on when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI.

[0303] This embodiment explicitly defines the scope of ULDAI when a DCI schedules multiple PUSCHs in the interface specification protocol between the base station and the UE. The protocol may define any of the following methods:

[0304] Specifically, through the interface specification protocol with the UE, it is indicated that when a DCI schedules multiple PUSCHs and the DCI includes ULDAI, the range of PUSCHs covered by UL DAI includes at least one of the following:

[0305] The first interface specification protocol information is defined in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0306] The second interface specification protocol information is defined in the interface specification protocol. The second interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI is applied to the last PUSCH.

[0307] The third interface specification protocol information is defined in the interface specification protocol. The third interface specification protocol information is used to indicate that when the number of PUSCHs scheduled by DCI is greater than the number of time slots M contained in the PDCCH detection time slot group, UL DAI is applied to the 1st and M+1st scheduled PUSCHs.

[0308] The fourth interface specification protocol information is defined in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0309] The third interface specification protocol information can also indicate:

[0310] When a DCI schedules multiple PUSCHs, and the DCI contains DAI information, the DAI value is used for HARQ-ACK information multiplexing in the "first PUSCH".

[0311] If the number of PUSCHs scheduled by the DCI is greater than M, the DAI value is also applied to the (M+1)th PUSCH for HARQ-ACK information reuse.

[0312] The value M is an integer greater than 1, and it can also be related to the PDCCH detection capability.

[0313] For PUSCHs other than those using UL DAI as indicated in the embodiments of this application, if a DCI for the corresponding PDSCH is received, indicating that HARQ-ACK information is transmitted on these PUSCHs, the terminal can use any of the following methods (configurable by the protocol):

[0314] - Calculate HARQ-ACK feedback information using UL DAI in the DCI of the scheduling PUSCH.

[0315] - Calculate HARQ-ACK feedback information using DAI in the DCI of the scheduled PDSCH.

[0316] - Discard the PUSCH, or discard the HARQ-ACK message that needs to be transmitted.

[0317] - The terminal considers the PUSCH scheduling information and HARQ-ACK indication information received at the same time to be invalid (i.e., the terminal does not want to receive the PUSCH and the PUCCH that transmits HARQ-ACK to overlap).

[0318] This application also provides a communication method; please refer to [link to relevant documentation]. Figure 10 ,include:

[0319] S201. If it is determined that the DCI to be sent is used to schedule multiple PUSCHs and the DCI includes UL DAI, then information indicating the range of PUSCHs in which UL DAI operates is set in the DCI.

[0320] S202, Send DCI to UE.

[0321] This application embodiment adds information indicating the range of PUSCHs affected by UL DAI to the scheduling signaling DCI for scheduling PUSCHs, enabling the UE to determine the range of PUSCHs affected by UL DAI in real time based on the received DCI.

[0322] This application embodiment adds information indicating the PUSCH range of the UL DAI function to the DCI, which can be divided into two methods: adding a fixed-length information field and adding a variable-length information field to the DCI.

[0323] For the method of adding a fixed-length information field, the information in the DCI that indicates the PUSCH range of the UL DAI is set, including:

[0324] Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI.

[0325] The bitmap is set in the DCI to be transmitted as information indicating the range of PUSCH for the UL DAI to function;

[0326] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0327] Assuming a DCI can schedule a maximum number of PUSCHs of length max_PUSCH, a new bitmap of length max_PUSCH is added to the DCI, with each bit indicating whether the corresponding scheduled PUSCH applies UL DAI.

[0328] Each bit in the predefined bitmap indicates whether the corresponding PUSCH falls within the PUSCH range defined by UL DAI, including:

[0329] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0330] The following example uses N=8. For example,

[0331] When the bitmap is 1,0,0,0,0,0,0,0, it means that UL DAI acts on 1 PUSCH, and is the first PUSCH;

[0332] When the bitmap is 0,0,0,0,0,0,0,1, it means that UL DAI acts on 1 PUSCH, and it is the last PUSCH.

[0333] When the bitmap is 0,1,0,0,0,0,0,0, it means that UL DAI acts on 1 PUSCH, and it is the second PUSCH;

[0334] When the bitmap is 1,0,0,0,1,0,0,0, it indicates that UL DAI acts on 1 or 2 PUSCH:

[0335] --When X<=M / 2, UL DAI is applied to the first scheduled PUSCH.

[0336] --When X>M / 2, UL DAI applies to the valid PUSCH in the 1st and (1+M / 2)th schedules.

[0337] It should be noted that the length of the newly added information bits can be less than the maximum number of PUSCH bits.

[0338] Based on the above embodiments, information indicating the PUSCH range of UL DAI operation is set in the DCI, including:

[0339] Determine at least one target bit number combination from a predefined bit number combination table;

[0340] At least one target bit array is combined into information indicating the PUSCH range of the UL DAI operation and set in the DCI to be transmitted;

[0341] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0342] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0343] Assuming a DCI can schedule a maximum number of PUSCHs of max_PUSCH, a new information field of length 1 bit is added to the DCI to indicate which PUSCH the UL DAI is applied to.

[0344] Here is an example where max_PUSCH = 8:

[0345] 000 indicates the first PUSCH application UL DAI in the schedule;

[0346] 001 indicates that the second PUSCH application UL DAI is scheduled;

[0347] 010 indicates that the third PUSCH application in the schedule is UL DAI;

[0348] And so on.

[0349] It should be noted that the length of the newly added information bits can be less than [the specified value].

[0350] A new variable length information field has been added, which sets information in the DCI indicating the range of PUSCH that the UL DAI applies to, including:

[0351] If it is determined that the number of PUSCHs scheduled for the DCI to be sent is less than the maximum number of PUSCHs, then the range indication information is recorded according to the target bit bits of the RV and / or NDI in the DCI to be sent.

[0352] The target bit is the bit in RV and / or NDI that does not indicate PUSCH.

[0353] It should be noted that when one DCI schedules two or more PUSCHs, the RV version NDI indicator for each PUSCH uses a 1-bit indicator (RV version; Channel Coding Redundancy Version Number, NDI: New Data Indicator). To maintain the consistent length of the DCI scheduling information for each iteration, the RV bit information for all PUSCHs is fixed to the maximum value of the number of PUSCHs that can be scheduled, max_PUSCH (e.g., max_PUSCH = 8). When the actual number of scheduled PUSCHs M is less than N (e.g., max_PUSCH = 4), only the first M bits are used, and the remaining max_PUSCH - M bits are not used.

[0354] In this embodiment, when the number of dynamically scheduled PUSCHs is less than the maximum number, the unused RV or NDI, RV and NDI are used to indicate the scope of UL DAI's PUSCH application.

[0355] The specific method is as follows:

[0356] Assumptions: The base station is configured to schedule a maximum of max_PUSCHs per DCI. When the terminal receives a DCI scheduling message, the actual number of PUSCHs scheduled is act_PUSCH. The process by which the terminal and base station determine the PUSCHs to apply for the UL DAI value is as follows:

[0357] -If the number of scheduled PUSCHs is equal to max_PUSCH, the application PUSCH range is determined by higher-layer signaling or protocol determination.

[0358] - If the number of scheduled PUSCHs is less than max_PUSCH, then the range of PUSCHs used by UL DAI is indicated using no more than (max_PUSCH - act_PUSCH) * 2 bits. Two examples are given below to illustrate this.

[0359] Taking max_PUSCH=8 and act_PUSCH=7 as an example, from the background content of NDI and RV above, we know that NDI and RV each have 1 bit of information that is not used (e.g., RV[7], NDI[7], that is, a total of 2 bits of information are spared). Then the base station and the terminal use 2 bits of information to indicate the application location of UL DAI, as shown in Table 2:

[0360]

[0361] Table 2 First DCI Information Domain Table

[0362] In other words, when 00 is recorded using 1 bit of information in RV and NDI, it indicates that the first PUSCH in the schedule applies UL DAI; when 01 is recorded using 1 bit of information in RV and NDI, it indicates that the second PUSCH in the schedule applies UL DAI; when 10 is recorded using 1 bit of information in RV and NDI, it indicates that the third PUSCH in the schedule applies UL DAI; and when 11 is recorded using 1 bit of information in RV and NDI, it indicates that the fourth PUSCH in the schedule applies UL DAI.

[0363] Taking max_PUSCH=8 and act_PUSCH=4 as an example, NDI and RV each have 4 bits of information unused, meaning a total of 8 bits of information are available. The base station and terminal can then use the 4 bits of information from RV or NDI to represent the application scope of the UL DAI, as shown in Table 3.

[0364]

[0365] Table 3 Second DCI Information Domain Table

[0366] Taking RV[4] in Table 3 as an example, the fourth bit of RV can indicate whether the first PUSCH applies UL DAI. For example, when the bit is 0, it means that the first PUSCH does not apply UL DAI, and when it is 1, it means that the first PUSCH applies UL DAI.

[0367] This application provides a communication method, including:

[0368] When a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), the range of PUSCHs that the UL DAI applies to is indicated by the receiving network device.

[0369] The receiver receives at least one DCI for scheduling PUSCH from the network device. When the DAI includes UL DAI, it feeds back a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) signal within the PUSCH range covered by the UL DAI.

[0370] In one possible implementation, when the receiving network device indicates that a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), the range of PUSCHs covered by the UL DAI includes:

[0371] The PUSCH range of the UL DAI indicated by the network device is obtained through high-level signaling configuration.

[0372] In one possible implementation, the PUSCH range of the UL DAI action indicated by the network device is obtained through higher-level signaling configuration, including:

[0373] When the higher-layer signaling configuration indicates the range of PUSCHs in which UL DAI operates with a target status value, the range of PUSCHs in which UL DAI operates corresponding to the target status value is searched in the predefined status indication table.

[0374] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0375] In one possible implementation, the state indicator table includes at least one of a first state value, a second state value, a third state value, and a fourth state;

[0376] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0377] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0378] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0379] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0380] In one possible implementation, the PUSCH range of the UL DAI action indicated by the network device is obtained through higher-level signaling configuration, including:

[0381] When the higher-layer signaling configuration uses a bitmap to indicate the range of PUSCHs covered by UL DAI, it determines whether the corresponding PUSCH belongs to the range of PUSCHs covered by UL DAI based on each bit in the bitmap.

[0382] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0383] In one possible implementation, determining whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap includes:

[0384] For any given bit, if the bit value is a first preset value, it indicates that the corresponding PUSCH belongs to the PUSCH range operated by UL DAI; if the bit value is a second preset value, it indicates that the corresponding PUSCH does not belong to the PUSCH range operated by UL DAI.

[0385] In one possible implementation, when the receiving network device indicates that a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), the range of PUSCHs covered by the UL DAI includes:

[0386] By using the interface specification protocol with network devices, the range of PUSCHs that UL DAI operates on is determined when a DCI schedules multiple PUSCHs and the DCI includes UL DAI.

[0387] In one possible implementation, the scope of PUSCHs covered by the UL DAI is determined through the interface specification protocol with the network device, when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0388] When the interface specification protocol defines the first interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0389] When the interface specification protocol defines the second interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the last PUSCH.

[0390] When the third interface specification protocol information is defined in the interface specification protocol, it is determined that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0391] When the fourth interface specification protocol information is defined in the interface specification protocol, it is determined that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0392] This application provides a communication method, including:

[0393] Receive DCI sent by network devices;

[0394] Parse the DCI to obtain information about the range of PUSCHs that the UL DAI is active in when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI.

[0395] When the received DAI includes the UL DAI, a hybrid automatic repeat request acknowledgment signal (HARQ-ACK) is fed back within the PUSCH range of the UL DAI.

[0396] In one possible implementation, obtaining information about the range of PUSCHs covered by the UL DAI, as indicated by the network device when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, includes:

[0397] Obtain information in the form of a bitmap;

[0398] Determine whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bit diagram.

[0399] In one possible implementation, determining whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap includes:

[0400] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0401] In one possible implementation, obtaining information about the range of PUSCHs covered by the UL DAI, as indicated by the network device when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, includes:

[0402] Obtain information in the form of a target number of bits;

[0403] Search within the predefined bit combination packets for the PUSCH range of UL DAI action corresponding to the target bit combination;

[0404] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0405] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0406] In one possible implementation, obtaining information about the range of PUSCHs covered by the UL DAI, as indicated by the network device when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, includes:

[0407] Obtain information in the form of the target bits of RV and / or NDI in the DCI;

[0408] Search the preset DCI information field table for the PUSCH range of UL DAI action corresponding to the number of bits on the target bit.

[0409] The bit combination table includes at least one bit number and the PUSCH range of the UL DAI function in the corresponding DCI. This application provides a network device, such as... Figure 11 As shown, the device may include: an indication module 101 and a first DCI transmission module 102, specifically:

[0410] Indication module 101 is used to indicate to user equipment UE the range of PUSCHs in which UL DAI is applied when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI).

[0411] The first DCI sending module 102 is used to send at least one DCI for scheduling PUSCH to the UE.

[0412] In one possible implementation, the instruction module includes:

[0413] The higher-layer signaling configuration module is used to indicate to the UE the range of PUSCHs covered by UL DAI when a DCI schedules multiple PUSCHs and the DCI includes UL DAI.

[0414] The high-level signaling configuration module includes:

[0415] A state value determination unit is used to determine the target state value from a predefined state indication table;

[0416] The first configuration parameter unit is used to send the target state value as a parameter for higher-layer signaling configuration to the UE;

[0417] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0418] In one possible implementation, the state indicator table includes at least one of a first state value, a second state value, a third state value, and a fourth state;

[0419] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0420] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0421] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0422] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0423] In one possible implementation, the high-level signaling configuration module includes:

[0424] The bitmap indicator unit is used to indicate whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the predefined bitmap.

[0425] The second configuration parameter unit is used to send the bit map as a parameter for higher-layer signaling configuration to the UE;

[0426] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0427] In one possible implementation, the bitmap indicator unit is used for:

[0428] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0429] In one possible implementation, the instruction module includes:

[0430] The interface protocol module is used to indicate the range of PUSCHs that UL DAI operates on when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, through the interface specification protocol with the UE.

[0431] In one possible implementation, the interface protocol module includes at least one of the following:

[0432] The first protocol information unit is used to define the first interface specification protocol information in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0433] The second protocol information unit is used to define the second interface specification protocol information in the interface specification protocol. The second interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI is applied to the last PUSCH.

[0434] The third protocol information unit is used to define the third interface specification protocol information in the interface specification protocol. The third interface specification protocol information is used to indicate that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0435] The fourth protocol information unit is used to define the fourth interface specification protocol information in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0436] The network device provided in this embodiment of the invention specifically executes the process described in the above method embodiment. For details, please refer to all embodiments of the communication method in the network device; further elaboration will not be repeated here. The network device provided in this embodiment of the invention instructs the User Equipment (UE) to specify the range of PUSCHs covered by the UL DAI when a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes a Downlink Allocation Index (UL DAI); and sends at least one DCI for scheduling PUSCHs to the UE. This embodiment of the application avoids HARQ-ACK feedback for each PUSCH or PUSCH transmission errors due to missed downlink DCI detection, thus improving HARQ-ACK feedback efficiency.

[0437] This application provides a network device, such as... Figure 12 As shown, the device may include: a DCI setting module 201 and a second DCI transmitting module 202, specifically:

[0438] DCI setting module 201 is used to set information in the DCI indicating the range of PUSCHs in which UL DAI is applied if it is determined that the DCI to be sent is used to schedule multiple PUSCHs and the DCI includes UL DAI.

[0439] The second DCI sending module 202 is used to send DCI to the UE.

[0440] In one possible implementation, the DCI setup module includes:

[0441] The bit indication module is used to indicate whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the predefined bit diagram.

[0442] The information addition module is used to set the bit map as information indicating the PUSCH range of UL DAI in the DCI to be sent;

[0443] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0444] In one possible implementation, the bit indication module is specifically used for:

[0445] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0446] In one possible implementation, the DCI setup module includes:

[0447] A bit combination definition module is used to determine at least one target bit combination from a predefined bit combination table;

[0448] A bit addition module is used to combine at least one target bit array into information indicating the range of PUSCH indicating the action of UL DAI, set in the DCI to be transmitted;

[0449] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0450] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0451] In one possible implementation, the DCI setup module includes:

[0452] The scheduling record module is used to record information indicating the range of PUSCHs that the UL DAI operates on, based on the target bits of the RV and / or NDI in the DCI to be sent, if it is determined that the number of PUSCHs scheduled for the DCI to be sent is less than the maximum number of PUSCHs scheduled.

[0453] The target bit is the bit in RV and / or NDI that does not indicate PUSCH.

[0454] The network device provided in this embodiment of the invention specifically executes the process described in the above method embodiment. For details, please refer to the content of all embodiments of the above communication method on the network device side, which will not be repeated here. The network device provided in this embodiment of the invention adds information indicating the PUSCH range in which UL DAI operates to the scheduling signaling DCI for scheduling PUSCH, enabling the UE to determine the PUSCH range in which UL DAI operates in real time based on the received DCI.

[0455] In one alternative embodiment, a network device is provided, such as Figure 13 As shown, it includes a memory 1020, a transceiver 1040, and a processor 1010;

[0456] Memory 1020 is used to store computer programs;

[0457] Transceiver 1040 is used to receive and send data under the control of processor 1010;

[0458] Processor 1010 is used to read computer programs from memory 1020 and perform the following operations:

[0459] Indicate to the User Equipment (UE) the range of PUSCHs covered by the UL DAI when a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes the UL DAI.

[0460] Send at least one DCI for scheduling PUSCH to the UE.

[0461] Based on the above embodiments, as an optional embodiment, the processor indicates to the user equipment (UE) the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0462] The UE is informed via higher-level signaling configuration that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI is specified.

[0463] Based on the above embodiments, as an optional embodiment, the processor, through higher-layer signaling configuration, indicates to the UE the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0464] Determine the target state value in a predefined state indication table;

[0465] The target state value is sent to the UE as a parameter for higher-layer signaling configuration;

[0466] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0467] Based on the above embodiments, as an optional embodiment, the status indicator table includes at least one of a first status value, a second status value, a third status value, and a fourth status;

[0468] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0469] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0470] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0471] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0472] Based on the above embodiments, as an optional embodiment, the processor, through higher-layer signaling configuration, indicates to the UE the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0473] Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI.

[0474] The bitmap is sent to the UE as a parameter for higher-layer signaling configuration;

[0475] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0476] Based on the above embodiments, as an optional embodiment, the processor indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the predefined bitmap, including:

[0477] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0478] Based on the above embodiments, as an optional embodiment, the processor indicates to the user equipment (UE) the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0479] The interface specification protocol with the UE indicates the range of PUSCHs that the UL DAI operates on when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI.

[0480] Based on the above embodiments, as an optional embodiment, the processor, through the interface specification protocol with the UE, indicates the range of PUSCHs covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, including at least one of the following:

[0481] The first interface specification protocol information is defined in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0482] The second interface specification protocol information is defined in the interface specification protocol. The second interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI is applied to the last PUSCH.

[0483] The third interface specification protocol information is defined in the interface specification protocol. The third interface specification protocol information is used to indicate that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0484] The fourth interface specification protocol information is defined in the interface specification protocol. The first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0485] Based on the above embodiments, as an optional embodiment, the processor is also configured to perform the following operations:

[0486] If it is determined that the DCI to be sent is used to schedule multiple PUSCHs and the DCI includes UL DAI, then information indicating the range of PUSCHs in which UL DAI operates is set in the DCI.

[0487] Send DCI to UE.

[0488] Based on the above embodiments, as an optional embodiment, the processor sets information in the DCI indicating the PUSCH range of the UL DAI operation, including:

[0489] Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI.

[0490] The bitmap is set in the DCI to be transmitted as information indicating the range of PUSCH for the UL DAI to function;

[0491] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0492] Based on the above embodiments, as an optional embodiment, the processor indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the predefined bitmap, including:

[0493] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0494] Based on the above embodiments, as an optional embodiment, the processor sets information in the DCI indicating the PUSCH range of the UL DAI operation, including:

[0495] Determine at least one target bit number combination from a predefined bit number combination table;

[0496] At least one target bit array is combined into information indicating the PUSCH range of the UL DAI operation and set in the DCI to be transmitted;

[0497] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0498] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0499] Based on the above embodiments, as an optional embodiment, the processor sets information in the DCI indicating the PUSCH range of the UL DAI operation, including:

[0500] If it is determined that the number of PUSCHs scheduled in the DCI to be sent is less than the maximum number of PUSCHs to be scheduled, then information indicating the range of PUSCHs to be operated by UL DAI is recorded based on the target bits of RV and / or NDI in the DCI to be sent.

[0501] The target bit is the bit in RV and / or NDI that does not indicate PUSCH.

[0502] Among them, Figure 13In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors 1010 represented by processor 1010 and various circuits of memory 1020 represented by memory 1020. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1030 provides an interface. Transceiver 1040 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. Processor 1010 is responsible for managing the bus architecture and general processing, and memory 1020 can store data used by processor 1010 during operation.

[0503] The processor 1010 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 1010 can also adopt a multi-core architecture.

[0504] The processor 1010 executes any of the methods provided in the embodiments of this application by calling a computer program stored in the memory 1020, according to the obtained executable instructions. The processor 1010 and the memory 1020 may also be physically separated.

[0505] The network device provided in this embodiment of the invention specifically executes the process of the above method embodiment. For details, please refer to the content of all embodiments of the above communication method on the network device side, which will not be repeated here.

[0506] This application provides a user equipment, including:

[0507] The instruction receiving module is used to receive the range of PUSCHs that the UL DAI applies to when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI).

[0508] The feedback module is used to receive at least one DCI for scheduling PUSCH sent by the network device. When the DAI includes UL DAI, it feeds back a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) signal within the PUSCH range where the UL DAI is active.

[0509] As an optional implementation, the instruction receiving module includes:

[0510] The higher-layer signaling configuration receiving module is used to obtain the PUSCH range of the ULDAI action indicated by the network device through higher-layer signaling configuration.

[0511] As an optional implementation, the higher-layer signaling configuration receiving module includes:

[0512] The status value parsing unit is used to search in a predefined status indication table for the PUSCH range of the UL DAI that corresponds to the target status value when the higher-layer signaling configuration indicates the PUSCH range of the UL DAI.

[0513] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0514] As an optional implementation, the status indicator table includes at least one of a first status value, a second status value, a third status value, and a fourth status;

[0515] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0516] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0517] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0518] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0519] As an optional implementation, the higher-layer signaling configuration receiving module includes:

[0520] The bitmap parsing unit is used to determine whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap when the higher layer signaling configuration indicates the PUSCH range of UL DAI using a bitmap.

[0521] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0522] As an optional implementation, the bitmap parsing unit includes:

[0523] For any given bit, if the bit value is a first preset value, it indicates that the corresponding PUSCH belongs to the PUSCH range operated by UL DAI; if the bit value is a second preset value, it indicates that the corresponding PUSCH does not belong to the PUSCH range operated by UL DAI.

[0524] As an optional implementation, the instruction receiving module includes:

[0525] The interface protocol receiving module is used to determine the range of PUSCHs covered by UL DAI when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, by means of the interface specification protocol with the network device.

[0526] As an optional implementation, the interface protocol receiving module includes:

[0527] The first interface information parsing unit is used to determine, when the interface specification protocol defines the first interface specification protocol information, that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0528] The second interface information parsing unit is used to determine, when the interface specification protocol defines the second interface specification protocol information, that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI is applied to the last PUSCH.

[0529] The third interface information parsing unit is used to determine, when the third interface specification protocol information is defined in the interface specification protocol, that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0530] The fourth interface information parsing unit is used to determine, when the fourth interface specification protocol information is defined in the interface specification protocol, that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0531] This application provides a user equipment, including:

[0532] The DCI receiver module is used to receive DCI signals sent by network devices.

[0533] The parsing module is used to parse the DCI and obtain information about the range of PUSCHs that the UL DAI is active in when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, as indicated by the network device.

[0534] The second feedback module is used to feed back a hybrid automatic repeat request acknowledgment signal (HARQ-ACK) within the PUSCH range of the UL DAI when the received DAI includes the UL DAI.

[0535] As an optional implementation, the parsing module includes:

[0536] Bitmap acquisition unit, used to obtain information in the form of a bitmap;

[0537] The bit resolution unit is used to determine whether the corresponding PUSCH belongs to the PUSCH range of ULDAI based on each bit in the bit map.

[0538] As an optional implementation, the bit parsing unit is specifically used for:

[0539] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0540] As an optional implementation, the parsing module includes:

[0541] The bit combination acquisition unit is used to obtain information in the form of a target bit combination;

[0542] The combination search unit is used to search for the range of PUSCH that corresponds to the ULDAI action in a predetermined number of bit combinations;

[0543] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0544] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0545] As an optional implementation, the parsing module includes:

[0546] Bit identification unit, used to obtain information in the form of target bit bits in DCI and / or NDI;

[0547] The bit number search unit is used to search the PUSCH range of UL DAI corresponding to the number of bits on the target bit in the preset DCI information field table;

[0548] The bit number combination table includes at least one bit number and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit number.

[0549] The user equipment provided in this embodiment of the invention specifically executes the process of the above method embodiment. For details, please refer to the content of all embodiments of the above communication method on the user equipment side, which will not be repeated here.

[0550] In one alternative embodiment, a user equipment is provided, including a memory, a transceiver, and a processor;

[0551] Memory, used to store computer programs;

[0552] A transceiver is used to receive and send data under the control of a processor;

[0553] A processor is used to read computer programs from memory and perform the following operations:

[0554] When a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), the range of PUSCHs that the UL DAI applies to is indicated by the receiving network device.

[0555] The receiver receives at least one DCI for scheduling PUSCH from the network device. When the DAI includes UL DAI, it feeds back a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) signal within the PUSCH range covered by the UL DAI.

[0556] In one possible implementation, the processor receives an indication from the network device that when a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes a Downlink Allocation Index (UL DAI), the range of PUSCHs covered by the UL DAI includes:

[0557] The PUSCH range of the UL DAI indicated by the network device is obtained through high-level signaling configuration.

[0558] In one possible implementation, the processor obtains the PUSCH range of the UL DAI action indicated by the network device through higher-level signaling configuration, including:

[0559] When the higher-layer signaling configuration indicates the range of PUSCHs in which UL DAI operates with a target status value, the range of PUSCHs in which UL DAI operates corresponding to the target status value is searched in the predefined status indication table.

[0560] The status indication table includes at least one status value and the corresponding UL DAI action PUSCH range indicated by the status value.

[0561] In one possible implementation, the state indicator table includes at least one of a first state value, a second state value, a third state value, and a fourth state;

[0562] Among them, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling;

[0563] The second state value corresponds to the UL DAI indicating the range of PUSCHs that the DCI scheduler operates on, which is the last PUSCH.

[0564] The range of PUSCHs that UL DAI applies to, corresponding to the third state value, is as follows: when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0565] The fourth state value corresponds to the UL DAI's PUSCH range of action: all PUSCHs scheduled by DCI.

[0566] In one possible implementation, the processor obtains the PUSCH range of the UL DAI action indicated by the network device through higher-level signaling configuration, including:

[0567] When the higher-layer signaling configuration uses a bitmap to indicate the range of PUSCHs covered by UL DAI, it determines whether the corresponding PUSCH belongs to the range of PUSCHs covered by UL DAI based on each bit in the bitmap.

[0568] The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

[0569] In one possible implementation, the processor determines whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap, including:

[0570] For any given bit, if the bit value is a first preset value, it indicates that the corresponding PUSCH belongs to the PUSCH range operated by UL DAI; if the bit value is a second preset value, it indicates that the corresponding PUSCH does not belong to the PUSCH range operated by UL DAI.

[0571] In one possible implementation, the processor receives an indication from the network device that when a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes a Downlink Allocation Index (UL DAI), the range of PUSCHs covered by the UL DAI includes:

[0572] By using the interface specification protocol with network devices, the processor determines the range of PUSCHs that UL DAI operates on when a DCI schedules multiple PUSCHs and the DCI includes UL DAI.

[0573] In one possible implementation, the processor determines, through an interface specification protocol with the network device, the range of PUSCHes covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI, including:

[0574] When the interface specification protocol defines the first interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the first PUSCH.

[0575] When the interface specification protocol defines the second interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI acts on the last PUSCH.

[0576] When the third interface specification protocol information is defined in the interface specification protocol, it is determined that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1.

[0577] When the fourth interface specification protocol information is defined in the interface specification protocol, it is determined that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, UL DAI applies to all PUSCHs.

[0578] The processor in this embodiment is also used to perform the following operations:

[0579] Receive DCI sent by network devices;

[0580] Parse the DCI to obtain information about the range of PUSCHs that the UL DAI is active in when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI.

[0581] When the received DAI includes the UL DAI, a hybrid automatic repeat request acknowledgment signal (HARQ-ACK) is fed back within the PUSCH range of the UL DAI.

[0582] In one possible implementation, the processor obtains information from the network device regarding the range of PUSCHs covered by the UL DAI when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, including:

[0583] Obtain information in the form of a bitmap;

[0584] Determine whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bit diagram.

[0585] In one possible implementation, the processor determines whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bitmap, including:

[0586] For any given bit, when the bit value is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the bit value is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

[0587] In one possible implementation, the processor obtains information from the network device regarding the range of PUSCHs covered by the UL DAI when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, including:

[0588] Obtain information in the form of a target number of bits;

[0589] Search within the predefined bit combination packets for the PUSCH range of UL DAI action corresponding to the target bit combination;

[0590] The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit combination;

[0591] The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

[0592] In one possible implementation, the processor obtains information from the network device regarding the range of PUSCHs covered by the UL DAI when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI, including:

[0593] Obtain information in the form of the target bits of RV and / or NDI in the DCI;

[0594] Search the preset DCI information field table for the PUSCH range of UL DAI action corresponding to the number of bits on the target bit.

[0595] The bit number combination table includes at least one bit number and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit number.

[0596] The user equipment provided in this embodiment of the invention specifically executes the process of the above method embodiment. For details, please refer to the content of all embodiments of the above communication method on the user equipment side, which will not be repeated here.

[0597] This application provides an electronic device comprising: a memory and a processor; at least one program stored in the memory, which, when executed by the processor, can, compared to existing technologies, instruct a user equipment (UE) to specify the range of PUSCHs covered by the UL DAI when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI); and send at least one DCI for scheduling PUSCHs to the UE. This application avoids HARQ-ACK feedback for each PUSCH or PUSCH transmission errors due to downlink DCI miss detection, thus improving HARQ-ACK feedback efficiency.

[0598] In one alternative embodiment, an electronic device is provided, such as Figure 14 As shown, Figure 14 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of this electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0599] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0600] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0601] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0602] The memory 4003 stores application code that executes the scheme of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the application code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.

[0603] This application provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments. Compared with the prior art, this application provides a method by instructing the User Equipment (UE) on the range of PUSCHs covered by the UL DAI when a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes a Downlink Allocation Index (UL DAI); and by sending at least one DCI for scheduling PUSCHs to the UE. This application avoids HARQ-ACK feedback for each PUSCH or PUSCH transmission errors due to downlink DCI miss detection, thus improving HARQ-ACK feedback efficiency.

[0604] This application provides a computer program including computer instructions stored in a computer-readable storage medium. When a processor of a computer device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, causing the computer device to perform the content shown in the foregoing method embodiments. Compared with the prior art, by instructing the user equipment (UE) on the range of PUSCHs covered by the UL DAI when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI), and by sending at least one DCI for scheduling PUSCHs to the UE, this application avoids HARQ-ACK feedback for each PUSCH or PUSCH transmission errors due to downlink DCI miss detection, thus improving HARQ-ACK feedback efficiency.

[0605] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0606] The above are only some embodiments of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A communication method, characterized in that, include: By configuring higher-layer signaling, the user equipment (UE) is informed of the range of PUSCHs covered by the UL DAI when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes an uplink allocation index (UL DAI). Sending at least one DCI for scheduling PUSCH to the UE; wherein, indicating the PUSCH range of the UL DAI to the UE through higher-layer signaling configuration includes: Determine the target state value in a predefined state indication table; The target state value is sent to the UE as a parameter for higher-layer signaling configuration; The status indication table includes at least one status value and a PUSCH range for the UL DAI action corresponding to each status value.

2. The communication method according to claim 1, characterized in that, The status indication table includes at least one of the following: a first status value, a second status value, a third status value, and a fourth status value; Wherein, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling. The second state value corresponds to the UL DAI's PUSCH range, which is the last PUSCH scheduled by DCI. The range of PUSCHs for which the third state value indicates the UL DAI is applied is as follows: when the number of PUSCHs scheduled by the DCI is greater than M, the UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1. The fourth state value corresponds to the UL DAI's indication of the range of PUSCHs affected by the DCI: all PUSCHs scheduled by the DCI.

3. The communication method according to claim 1, characterized in that, The method of instructing the UE via higher-layer signaling configuration, when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI also includes: Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI. The bitmap is sent to the UE as a parameter for higher-layer signaling configuration; The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

4. The communication method according to claim 3, characterized in that, The step of indicating whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the predefined bit map also includes: For any given bit, when the value of the bit is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the value of the bit is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

5. The communication method according to claim 1, characterized in that, The instruction to the user equipment (UE) that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI further includes: The interface specification protocol with the UE indicates the range of PUSCHs that the UL DAI operates on when a DCI schedules multiple PUSCHs and the DCI includes the UL DAI.

6. The communication method according to claim 5, characterized in that, The interface specification protocol with the UE indicates that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the range of PUSCHs covered by the UL DAI includes at least one of the following: The interface specification protocol defines a first interface specification protocol information, which is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the UL DAI acts on the first PUSCH. The interface specification protocol defines a second interface specification protocol information, which is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the UL DAI acts on the last PUSCH. The third interface specification protocol information is defined in the interface specification protocol. The third interface specification protocol information is used to indicate that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1. The interface specification protocol defines a fourth interface specification protocol information, and the first interface specification protocol information is used to indicate that when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, the UL DAI applies to all PUSCHs.

7. A communication method, characterized in that, include: If it is determined that the DCI to be sent is used to schedule multiple PUSCHs and the DCI includes UL DAI, then information indicating the range of PUSCHs in which UL DAI operates is set in the DCI. Send the DCI to the UE; The information in the DCI that indicates the range of PUSCH indicating the action of UL DAI includes: Each bit in the predefined bit diagram indicates whether the corresponding PUSCH belongs to the PUSCH range of UL DAI. The bitmap is set in the DCI to be transmitted as information indicating the range of PUSCH for the operation of UL DAI; The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

8. The communication method according to claim 7, characterized in that, The step of indicating whether the corresponding PUSCH according to each bit in the predefined bitmap belongs to the PUSCH range of UL DAI includes: For any given bit, when the value of the bit is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the value of the bit is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

9. The communication method according to claim 7, characterized in that, The information in the DCI that indicates the range of PUSCH for UL DAI operation includes: Determine at least one target bit number combination from a predefined bit number combination table; The at least one target bit array is combined into information indicating the PUSCH range of the UL DAI operation and set in the DCI to be transmitted; The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the bit combination; The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

10. The communication method according to claim 7, characterized in that, The information in the DCI that indicates the range of PUSCH for UL DAI operation includes: If it is determined that the number of PUSCHs scheduled in the DCI to be sent is less than the maximum number of PUSCHs to be scheduled, then the information of the range of PUSCHs indicating the action of UL DAI is recorded according to the target bit of RV and / or NDI in the DCI to be sent. The target bit is the bit in the RV and / or NDI that does not indicate PUSCH.

11. A communication method, characterized in that, include: The range of PUSCHs that the UL DAI applies to, as indicated by the receiving network device through higher-layer signaling configuration, when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes an uplink allocation index (UL DAI). Receive at least one DCI for scheduling PUSCH sent by the network device, and when the DCI includes UL DAI, feed back a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) signal in the PUSCH range where the UL DAI is applied. The step of obtaining the PUSCH range of the UL DAI indicated by the network device through higher-layer signaling configuration includes: When the higher-layer signaling configuration indicates the PUSCH range of the UL DAI with a target status value, the PUSCH range of the UL DAI corresponding to the target status value is searched in a predefined status indication table. The status indication table includes at least one status value and a PUSCH range for the UL DAI action corresponding to each status value.

12. The communication method according to claim 11, characterized in that, The status indication table includes at least one of the following: a first status value, a second status value, a third status value, and a fourth status value; Wherein, the range of PUSCHs indicated by the first state value is the first PUSCH of the DCI scheduling. The second state value corresponds to the UL DAI's PUSCH range, which is the last PUSCH scheduled by DCI. The range of PUSCHs for which the third state value indicates the UL DAI is applied is as follows: when the number of PUSCHs scheduled by the DCI is greater than M, the UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1. The fourth state value corresponds to the UL DAI's indication of the range of PUSCHs affected by the DCI: all PUSCHs scheduled by the DCI.

13. The communication method according to claim 11, characterized in that, The method of obtaining the PUSCH range of the UL DAI indicated by the network device through higher-layer signaling configuration includes: When the higher-layer signaling configuration indicates the range of PUSCHs covered by the UL DAI using a bit map, it determines whether the corresponding PUSCH belongs to the range of PUSCHs covered by the UL DAI based on each bit in the bit map. The number of bits in the bitmap represents the maximum number of PUSCHs in a DCI schedule.

14. The communication method according to claim 13, characterized in that, The step of determining whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bit map includes: For any given bit, when the value of the bit is a first preset value, it is determined that the corresponding PUSCH belongs to the PUSCH range of UL DAI; when the value of the bit is a second preset value, it is determined that the corresponding PUSCH does not belong to the PUSCH range of UL DAI.

15. The communication method according to claim 11, characterized in that, When the receiving network device indicates that a Downlink Control Information (DCI) schedules multiple Physical Uplink Shared Channels (PUSCHs) and the DCI includes a Downlink Allocation Index (ULDAI), the range of PUSCHs covered by the ULDAI includes: By using the interface specification protocol with the network device, the range of PUSCHs covered by the UL DAI is determined when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI.

16. The communication method according to claim 15, characterized in that, The method of determining the range of PUSCHes covered by the UL DAI when a DCI schedules multiple PUSCHs and the DCI includes a UL DAI, through the interface specification protocol with the network device, includes: When the interface specification protocol defines the first interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, the UL DAI acts on the first PUSCH; When the interface specification protocol defines the second interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, the UL DAI acts on the last PUSCH; When the third interface specification protocol information is defined in the interface specification protocol, it is determined that when the number of PUSCHs scheduled by DCI is greater than M, UL DAI is applied to the 1st and M+1st scheduled PUSCHs, where M is an integer greater than 1. When the interface specification protocol defines the fourth interface specification protocol information, it determines that when a DCI schedules multiple PUSCHs and the DCI includes UL DAI, the UL DAI applies to all PUSCHs.

17. A communication method, characterized in that, include: Receive DCI sent by network devices; The DCI is parsed to obtain information on the range of PUSCHs that UL DAI operates on when the DCI is used to schedule multiple PUSCHs and the DCI includes UL DAI, as indicated by the network device. When the received DCI includes UL DAI, a hybrid automatic repeat request acknowledgment signal HARQ-ACK is fed back within the PUSCH range where the UL DAI is active. The information obtained by the network device indicating the range of PUSCHs covered by the UL DAI when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI includes: Obtain the information in the form of the target bits of RV and / or NDI in the DCI; Search the preset DCI information field table for the PUSCH range of UL DAI action corresponding to the number of bits on the target bit; The bit combination table includes at least one bit number and the PUSCH range of the UL DAI action in the DCI corresponding to the corresponding bit number.

18. The communication method according to claim 17, characterized in that, The information obtained by the network device indicating the range of PUSCHs covered by the UL DAI when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI includes: Obtain the information in the form of a bitmap; Determine whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bit diagram.

19. The communication method according to claim 18, characterized in that, The step of determining whether the corresponding PUSCH belongs to the PUSCH range of UL DAI based on each bit in the bit map includes: For any given bit, when the value of the bit is a first preset value, it is used to indicate that the corresponding PUSCH belongs to the PUSCH range under the action of UL DAI; when the value of the bit is a second preset value, it is used to indicate that the corresponding PUSCH does not belong to the PUSCH range under the action of UL DAI.

20. The communication method according to claim 17, characterized in that, The information obtained by the network device indicating the range of PUSCHs covered by the UL DAI when the DCI is used to schedule multiple PUSCHs and the DCI includes the UL DAI includes: Obtain the information in the form of a target number of bits combination; Search within a predetermined set of bit combination packets for the range of UL DAI action corresponding to the target bit combination; The bit combination table includes at least one bit combination and the PUSCH range of the UL DAI action in the DCI corresponding to the bit combination; The bit width of the bit combination is related to the maximum number of PUSCHs in a DCI schedule.

21. A network device, characterized in that, include: The indication module is used to indicate to the user equipment (UE) the range of PUSCHs in which the ULDAI is applied when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI). The first DCI sending module is used to send at least one DCI for scheduling PUSCH to the UE; The step of instructing the UE on the PUSCH range of the UL DAI through higher-layer signaling configuration includes: Determine the target state value in a predefined state indication table; The target state value is sent to the UE as a parameter for higher-layer signaling configuration; The status indication table includes at least one status value and a PUSCH range for the UL DAI action corresponding to each status value.

22. A user equipment, characterized in that... The instruction receiving module is used to receive the range of PUSCHs that the UL DAI applies when a downlink control information (DCI) schedules multiple physical uplink shared channels (PUSCHs) and the DCI includes a downlink allocation index (UL DAI). The first feedback module is used to receive at least one DCI for scheduling PUSCH sent by the network device. When the DCI includes UL DAI, a hybrid automatic repeat request acknowledgment signal HARQ-ACK is fed back to the PUSCH range where the UL DAI is applied. The step of obtaining the PUSCH range of the UL DAI indicated by the network device through higher-layer signaling configuration includes: When the higher-layer signaling configuration indicates the PUSCH range of the UL DAI with a target status value, the PUSCH range of the UL DAI corresponding to the target status value is searched in a predefined status indication table. The status indication table includes at least one status value and a PUSCH range for the UL DAI action corresponding to each status value.

23. A network device, characterized in that, Includes memory, transceiver, and processor: Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; A processor for reading a computer program from the memory and executing the steps of the communication method as described in any one of claims 1 to 10.

24. A user equipment, characterized in that, Includes storage, transceiver, and processor: Memory, used to store computer programs; A transceiver for sending and receiving data under the control of the processor; a processor for reading a computer program from the memory and executing the steps of the communication method as described in any one of claims 11 to 20.

25. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the communication method as described in any one of claims 1 to 20.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause the computer to perform the steps of the communication method as described in any one of claims 1 to 20.

Images