CN112910613B

CN112910613B - Information processing method, device, user equipment, base station and storage medium

Info

Publication number: CN112910613B
Application number: CN202110221189.7A
Authority: CN
Inventors: 苟伟; 郝鹏; 毕峰
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-02-13
Filing date: 2018-02-13
Publication date: 2022-05-17
Anticipated expiration: 2038-02-13
Also published as: CN112910613A; CN110149172A; CN110149172B

Abstract

An information processing method and apparatus are disclosed. The information processing method comprises the following steps: user Equipment (UE) receives Downlink Control Information (DCI), wherein the DCI carries a parameter S which is used for indicating the formation of a hybrid automatic repeat request acknowledgement information (HARQ-ACK) semi-static codebook; and the UE generates and transmits the HARQ-ACK codebook according to the parameter S. The technical scheme can save the overhead of the HARQ-ACK semi-static codebook.

Description

Information processing method, device, user equipment, base station and storage medium

The application is a divisional application of a patent application with the application date of 2018, 13.02 and the application number of 201810150943.0 and the name of 'an information processing method and device'.

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to an information processing method and apparatus.

Background

In an NR (New Radio ) system, for multiplexing feedback of multiple HARQ-ACKs (Hybrid Automatic Repeat Request Acknowledgement), a UE (User Equipment) may form a dynamic codebook or a semi-static codebook (also referred to as a static codebook).

For the UE supporting a dynamic codebook, when the base station transmits multiple TBs (Transport blocks) for the UE, the Transport blocks may be from one or multiple BWPs (Bandwidth Part) of one carrier or from one or multiple BWPs of multiple aggregated carriers, the number of bits of HARQ-ACK fed back by the UE for multiple Transport blocks may be changed according to the number of Transport blocks scheduled by the base station, that is, the size of the codebook is allowed to change. The HARQ-ACKs of these transport Blocks are required to be multiplexed together for feedback, and a CBG (Code Blocks Group) mechanism is configured in the one or more carriers, allowing 2 sub-codebooks, one at TB level and one at CBG level, to be formed for the HARQ-ACKs of these transport Blocks. The two subcodebooks are generated and then combined together, and the code is sent to a base station. However, there is currently no specific solution for the use of sub-codebooks. For example, HARQ-ACKs of which transport blocks are respectively placed in the two sub-codebooks, how the UE knows its own codebook configuration, and the like.

The method includes that a semi-static codebook is supported for a UE, when a base station schedules one or more transport blocks for the UE, the transport blocks may be from one or more BWPs of one carrier or from one or more BWPs of multiple aggregated carriers, HARQ-ACKs of the transport blocks may be required to be multiplexed together to form the semi-static codebook for transmission through a PUSCH (Physical Uplink Shared Channel) of the UE, the base station schedules the PUSCH of the UE through a DCI (Downlink Control Information), where the DCI is used for Uplink grant and is used for scheduling the PUSCH of the UE, and the UE may transmit the semi-static codebook by puncturing data of the PUSCH Channel or reserving partial resources in the PUSCH Channel.

In the related art, when the UE feeds back the semi-static codebook, the HARQ-ACK is always fed back according to a fixed number of bits, regardless of whether or not the base station schedules a transport block for the UE or how many transport blocks are scheduled. For example, for all possible occasions for scheduling the transport blocks within the scheduling window length corresponding to the semi-static codebook, the UE needs to feed back HARQ-ACK, which has the advantages of simple processing, and avoiding the problem of inconsistent codebook size understanding caused by the change of the number of the scheduled transport blocks or missed detection when the UE detects DCI, thereby avoiding introducing a corresponding solution mechanism, but the HARQ-ACK overhead of the semi-static codebook is relatively high.

In addition, after frequency hopping of a Channel in the frequency domain, for example, for the frequency hopping of a Physical Uplink Control Channel (PUCCH), how to determine a sequence group (also referred to as a group sequence or a base sequence) used for each frequency hopping does not have a corresponding solution.

Disclosure of Invention

The technical problem to be solved by the invention is to provide an information processing method and device, which can save the overhead of a HARQ-ACK semi-static codebook.

The embodiment of the invention provides an information processing method, which comprises the following steps:

user Equipment (UE) receives Downlink Control Information (DCI), wherein the DCI carries a parameter S which is used for indicating the formation of a hybrid automatic repeat request acknowledgement information (HARQ-ACK) semi-static codebook;

and the UE generates and transmits the HARQ-ACK codebook according to the parameter S.

a base station configures and sends downlink control information DCI, wherein the DCI carries a parameter S, and the parameter S is used for indicating the formation of a hybrid automatic repeat request acknowledgement information HARQ-ACK semi-static codebook;

and the base station receives the HARQ-ACK codebook according to the parameter S.

setting numbers for channels and/or each frequency hopping of the channels in a scheduling unit;

and calculating the channels and/or sequence groups corresponding to each frequency hopping of the channels according to the numbers and a preset rule.

An embodiment of the present invention provides an information processing apparatus, which is applied to a user equipment, and includes:

an information receiving module, configured to receive downlink control information DCI, where the DCI carries a parameter S, and the parameter S is used to indicate formation of a HARQ-ACK semi-static codebook of hybrid automatic repeat request acknowledgement information;

and the codebook processing module is used for generating and sending the HARQ-ACK codebook according to the parameter S.

An embodiment of the present invention provides an information processing apparatus, which is applied to a base station, and includes:

an information sending module, configured to configure and send downlink control information DCI, where the DCI carries a parameter S, and the parameter S is used to indicate formation of a hybrid automatic repeat request acknowledgement information HARQ-ACK semi-static codebook;

and the codebook processing module is used for receiving the HARQ-ACK codebook according to the parameter S.

An embodiment of the present invention provides an information processing apparatus, including:

the number processing module is used for setting numbers for the channels and/or each frequency hopping of the channels in one scheduling unit;

and the sequence group determining module is used for calculating the channel and/or the sequence group corresponding to each frequency hopping of the channel according to the serial number and a preset rule.

Compared with the prior art, the information processing method and the device provided by the embodiment of the invention have the advantages that the User Equipment (UE) receives the Downlink Control Information (DCI), wherein the DCI carries the parameter S which is used for indicating the formation of the hybrid automatic repeat request acknowledgement information (HARQ-ACK) semi-static codebook; and the UE generates and transmits the HARQ-ACK codebook according to the parameter S. The embodiment of the invention can save the overhead of the HARQ-ACK semi-static codebook.

Drawings

Fig. 1 is a flowchart of an information processing method according to embodiment 1 of the present invention;

fig. 2 is a flowchart of an information processing method according to embodiment 2 of the present invention;

fig. 3 is a flowchart of an information processing method according to embodiment 3 of the present invention;

FIG. 4 is a structural view of an information processing apparatus according to embodiment 4 of the present invention;

FIG. 5 is a structural view of an information processing apparatus according to embodiment 5 of the present invention;

fig. 6 is a structural diagram of an information processing apparatus according to embodiment 6 of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.

Example 1

As shown in fig. 1, an embodiment of the present invention provides an information processing method, including:

step S110, User Equipment (UE) receives Downlink Control Information (DCI), wherein the DCI carries a parameter S, and the parameter S is used for indicating the formation of a hybrid automatic repeat request acknowledgement information (HARQ-ACK) semi-static codebook;

and step S120, the UE generates and transmits the HARQ-ACK codebook according to the parameter S.

In one embodiment, the UE performs HARQ-ACK codebook generation and transmission according to the parameter S, including:

when the UE is configured with a HARQ-ACK semi-static codebook and is required to transmit the HARQ-ACK semi-static codebook through a Physical Uplink Shared Channel (PUSCH), if the UE receives DCI (Downlink control information) for scheduling the PUSCH and a parameter S contained in the DCI is set to be a first numerical value, the UE generates the semi-static codebook.

and when the UE is configured with the HARQ-ACK semi-static codebook and is required to transmit the HARQ-ACK semi-static codebook through a Physical Uplink Shared Channel (PUSCH), if the UE receives DCI (Downlink control information) for scheduling the PUSCH and a parameter S contained in the DCI is set to be a second numerical value, the UE generates a HARQ-ACK codebook for a Transmission Block (TB) scheduled by the received DCI.

In one embodiment, the UE generates a HARQ-ACK codebook for a transport block, TB, scheduled by the received DCI, including one of:

if the UE is configured with 1 code word CW, one DCI schedules one TB, and the UE generates one HARQ-ACK codebook for the one TB scheduled by the DCI;

if the UE is configured with 2 codewords CW, one DCI schedules two TBs, the UE generates one HARQ-ACK codebook for the two TBs scheduled by the DCI.

when the UE is configured with a HARQ-ACK semi-static codebook and is required to transmit the HARQ-ACK semi-static codebook through a Physical Uplink Shared Channel (PUSCH), if the UE receives DCI for scheduling the PUSCH and a parameter S contained in the DCI is set to be a second numerical value and the UE does not receive any DCI-scheduled TB at a corresponding scheduling opportunity in a scheduling window corresponding to the semi-static codebook, the UE generates a HARQ-ACK codebook according to a fixed 1 TB or a fixed 2 TB or the number of CWs configured for the UE.

In one embodiment, the UE generates one HARQ-ACK codebook according to a fixed 1 TB or according to a fixed 2 TBs or according to the number of CWs configured for the UE, including one of:

if the UE generates one HARQ-ACK codebook according to the number of CWs configured for the UE, if the UE is configured to NCW CWs, the UE generates one HARQ-ACK codebook according to NCW TBs, wherein the NCW is the number of CWs configured for the UE and is a positive integer;

if the UE generates one HARQ-ACK codebook according to the fixed 1 TB, when the UE is configured with one or more CW, the UE generates one HARQ-ACK codebook according to 1 TB;

if the UE generates one HARQ-ACK codebook according to the fixed 2 TBs, the UE generates one HARQ-ACK codebook according to the 2 TBs when the UE is configured with one or more CWs.

In one embodiment, the UE receives downlink control information DCI, which is DCI scheduling a physical uplink shared channel PUSCH of the UE;

the parameter S is 1bit, the first value is 1, and the second value is 0.

Example 2

As shown in fig. 2, an embodiment of the present invention provides an information processing method, including:

step S210, a base station configures and sends downlink control information DCI, wherein the DCI carries a parameter S, and the parameter S is used for indicating the formation of a hybrid automatic repeat request acknowledgement information HARQ-ACK semi-static codebook;

and step S210, the base station receives the HARQ-ACK codebook according to the parameter S.

In one embodiment, the base station receives an HARQ-ACK codebook according to a parameter S, including:

when a base station configures an HARQ-ACK semi-static codebook for User Equipment (UE) and requires to transmit the HARQ-ACK semi-static codebook through a Physical Uplink Shared Channel (PUSCH), if the base station schedules a plurality of Transport Blocks (TBs) or sends a plurality of DCI scheduling TBs for the UE at a scheduling opportunity in a scheduling window corresponding to the semi-static codebook, the base station sets a parameter S as a first numerical value in DCI for scheduling the PUSCH;

wherein the plurality of TBs are more than 1 TB when the base station configures the UE with 1 CW; when the base station configures the UE with 2 CWs, the plurality of TBs are more than 2 TBs; when the base station configures the UE with 2 CWs and allows the base station to dynamically turn off one of the CWs, the plurality of TBs are more than 1 TB; the multiple DCI is more than 1 DCI.

when a base station configures a HARQ-ACK semi-static codebook for user equipment and requires to transmit the HARQ-ACK semi-static codebook through a Physical Uplink Shared Channel (PUSCH), if the base station schedules only 1 TB or transmits only one-time DCI scheduling transmission block TB or does not schedule any TB or does not transmit any one-time DCI scheduling TB for the UE at a scheduling opportunity in a scheduling window corresponding to the semi-static codebook, the base station sets a parameter S in DCI scheduling the PUSCH as a second numerical value;

wherein the scheduling of only 1 TB means that the base station schedules only one TB when the UE is configured with 1 CW.

In one embodiment, the scheduling occasion in the scheduling window corresponding to the semi-static codebook includes at least one of:

scheduling occasions are one or more time domain positions for monitoring DCI configured for the UE by the base station;

the scheduling occasions are distributed in one or more carriers configured for the UE by the base station;

the scheduling occasions are distributed in a fractional bandwidth BWP of one or more carriers configured by the base station for the UE.

In one embodiment, the base station configures and transmits downlink control information DCI, which is DCI scheduling a physical uplink shared channel PUSCH of the UE;

the parameter S is 1bit, the first value is 1, and the second value is 0.

Example 3

As shown in fig. 3, an embodiment of the present invention provides an information processing method, including:

step S310, setting numbers for channels and/or frequency hopping of the channels in a scheduling unit;

and step S320, calculating the channels and/or sequence groups corresponding to each frequency hopping of the channels according to the numbers and a preset rule.

In one embodiment, the setting of the number for the channel and/or each frequency hopping of the channel in one scheduling unit includes at least one of:

in a scheduling unit, when a channel frequency domain hops, a serial number is set for each frequency hopping of the frequency domain;

in one scheduling unit, when a channel does not frequency-domain hop, a number is set for the channel.

configuring one or more channels for one UE in one scheduling unit, and setting continuous numbers for each frequency hopping of the channels when the one or more channels respectively carry out frequency domain frequency hopping;

configuring one or more channels for one UE in a scheduling unit, setting continuous numbers for frequency hopping of each channel when the one or more channels respectively carry out frequency domain frequency hopping, and allowing the numbers of the frequency hopping of the latter channel to repeat the numbers of the frequency hopping of the former channel;

configuring one or more channels for one UE in one scheduling unit, and setting continuous numbers for the channels when the one or more channels are not frequency-hopping in respective frequency domain;

configuring one or more channels for one UE in one scheduling unit, and setting the same number for each channel when the one or more channels are not frequency-hopped in respective frequency domain;

and configuring a plurality of channels for one UE in one scheduling unit, wherein partial channels in the plurality of channels are subjected to frequency domain hopping respectively, and when partial channels are not subjected to frequency domain hopping respectively, continuous numbers are set for each frequency hopping of the frequency domain hopping channels and the frequency domain hopping-free channels.

In one embodiment, the calculating, according to the number and according to a predetermined rule, a sequence group corresponding to a channel and/or each frequency hop of the channel includes:

calculating the index u of the sequence group used by the channel or the sequence group corresponding to each frequency hopping of the channel according to the following formula;

u＝(f_gh+f_ss)mod Q；

wherein Q represents the total number of sequence groups in the system, f_ssIs a value determined by the cell ID, n_sFor the numbering of scheduling units, if the channel frequency domain hops, then l_hopIs the number of the frequency hopping of the channel, if the channel is not frequency domain hopping,/, then_hopFor channel numbering, c (-) is a pseudo-random sequence and N is the total number of times or a constant number of sequence groups need to be determined for the channel and the frequency domain hopping of the channel within one scheduling unit.

u＝(f_gh+f_ss)mod Q；

wherein Q represents the total number of sequence groups in the system, f_ssIs a value determined by the cell ID, n_sFor the numbering of scheduling units, if the channel frequency domain hops, then l_hopIs frequency hopping of channelsNumbering, if the channel does not frequency hop in the frequency domain,/, then_hopFor channel numbering, c (v) is a pseudo-random sequence, and N is the total number of times or a constant number of sequence groups need to be determined for the channel and the frequency domain hopping of the channel within one scheduling unit.

u＝(f_gh+f_ss)mod Q；

wherein Q represents the total number of sequence groups in the system, f_ssIs a value determined by the cell ID, n_sFor the numbering of scheduling units, if the channel frequency domain hops, then l_hopIs the number of the frequency hopping of the channel, if the channel is not frequency domain hopping,/, then_hopFor channel numbering, c (-) is a pseudo-random sequence.

In one embodiment, the scheduling unit comprises: a time slot.

In one embodiment, the channel comprises: and a Physical Uplink Control Channel (PUCCH).

Example 4

As shown in fig. 4, an embodiment of the present invention provides an information processing apparatus, which is applied to a user equipment UE, and includes:

an information receiving module 401, configured to receive downlink control information DCI, where the DCI carries a parameter S, and the parameter S is used to indicate formation of a HARQ-ACK semi-static codebook of hybrid automatic repeat request acknowledgement information;

a codebook processing module 402, configured to generate and transmit a HARQ-ACK codebook according to the parameter S.

In one embodiment, the codebook processing module is configured to perform HARQ-ACK codebook generation and transmission according to the parameter S in the following manner:

and when the UE is configured with the HARQ-ACK semi-static codebook and is required to transmit the HARQ-ACK semi-static codebook through a Physical Uplink Shared Channel (PUSCH), if the UE receives DCI (Downlink control information) for scheduling the PUSCH and a parameter S contained in the DCI is set to be a second numerical value, the UE generates a HARQ-ACK codebook for a transmission block TB scheduled by the received DCI.

In one embodiment, the UE generates one HARQ-ACK codebook according to fixed 1 TB or according to fixed 2 TBs or according to the number of CWs configured for the UE, including one of:

if the UE generates a HARQ-ACK codebook according to the fixed 1 TBs, when the UE is configured with one or more CW, the UE generates a HARQ-ACK codebook according to 1 TB;

if the UE generates one HARQ-ACK codebook according to fixed 2 TBs, the UE generates one HARQ-ACK codebook according to 2 TBs when the UE is configured with one or more CWs.

the parameter S is 1bit, the first value is 1, and the second value is 0.

Example 5

As shown in fig. 5, an embodiment of the present invention provides an information processing apparatus, applied to a base station, including:

an information sending module 501, configured to configure and send DCI, where the DCI carries a parameter S, and the parameter S is used to indicate formation of a HARQ-ACK semi-static codebook of HARQ-ACK;

a codebook processing module 502, configured to receive the HARQ-ACK codebook according to the parameter S.

In one embodiment, the method includes receiving a HARQ-ACK codebook according to a parameter S by using a codebook processing module:

the parameter S is 1bit, the first value is 1, and the second value is 0.

Example 6

As shown in fig. 6, an embodiment of the present invention provides an information processing apparatus including:

a number processing module 601, configured to set a number for a channel and/or each frequency hopping of the channel in a scheduling unit;

a sequence group determining module 602, configured to calculate, according to the serial number and according to a predetermined rule, a sequence group corresponding to a channel and/or each frequency hop of the channel.

In one embodiment, the numbering processing module is configured to set a number for a channel and/or each frequency hop of a channel in one scheduling unit in the following manner:

comprising performing at least one of the following:

In one embodiment, the sequence group determining module is configured to calculate, according to the number and according to a predetermined rule, a sequence group corresponding to a channel and/or each frequency hop of the channel by using the following method:

u＝(f_gh+f_ss)mod Q；

u＝(f_gh+f_ss)mod Q；

In one embodiment, the sequence group determining module is configured to calculate, according to the number and according to a predetermined rule, a sequence group corresponding to a channel and/or each hop frequency of the channel by:

u＝(f_gh+f_ss)mod Q；

In one embodiment, the scheduling unit comprises: a time slot.

Example 7

a memory, a processor, and an information processing program stored on the memory and executable on the processor, the information processing program, when executed by the processor, implementing the steps of the information processing method described in embodiment 1 or embodiment 2 or embodiment 3 above.

Example 8

An embodiment of the present invention provides a computer-readable storage medium, on which an information processing program is stored, and the information processing program, when executed by a processor, implements the steps of the information processing method described in embodiment 1 or embodiment 2 or embodiment 3 above.

The information sending method of the present application is further described below by some examples.

When the UE is configured with a dynamic codebook (the dynamic codebook refers to that the number of bits of HARQ-ACKs fed back by the UE for multiple TBs varies according to the number of TBs scheduled by the base station, or it is understood that the size of the codebook is allowed to vary), and the UE is required to feed back HARQ-ACKs for TBs scheduled from one or more carriers, and multiplex (jointly encode) these HARQ-ACKs together for feedback, and a CBG mechanism is configured in the one or more carriers. When multiple transport blocks TBs are transmitted for a UE (these TBs may be from one or more BWPs (Bandwidth Part, partial Bandwidth) of only one carrier, or one or more BWPs of multiple aggregated carriers), HARQ-ACKs of these TBs are required to be multiplexed together for feedback, allowing 2 sub-codebooks to be formed for HARQ-ACKs of these TBs, one sub-codebook being TB level HARQ-ACKs and one sub-codebook being CBG level HARQ-ACKs. The two subcodebooks are connected in parallel and sent to the base station after being coded. However, there still exist some problems, such as which TBs HARQ-ACK are placed in the two sub-codebooks respectively, how to form HARQ-ACK, how the UE knows its own codebook configuration? The following example X-example XX gives some solutions.

Example 1

In this example, the base station informs the UE of the sub-codebook configuration through explicit signaling, or the base station and the UE agree to implicitly determine the sub-codebook configuration of the UE.

The implicit method specifically includes at least one of the following methods:

1) the base station configures a dynamic codebook for the UE, and at least one of one or more carriers configured for the UE is configured with a CBG mechanism off (meaning that a TB is scheduled from the carrier in the future and a CBG feedback mechanism is not used), and at least one of the one or more carriers configured for the UE is configured with a CBG mechanism on (meaning that a TB is scheduled from the carrier in the future and a CBG feedback mechanism is used), at this time, when the UE (UE and base station) considers that the dynamic codebook is formed, 2 sub-codebooks, one sub-codebook at a TB level and one sub-codebook at a CBG level can be formed.

2) The base station configures a dynamic codebook for the UE, and CBG mechanisms in one or more carriers configured for the UE are all turned off, and at this time, the UE (UE and base station) considers that only a sub-codebook at a TB level (or only a codebook at a TB level) is formed.

3) The base station configures a dynamic codebook for the UE, and the CBG configuration mechanisms in one or more carriers configured for the UE are all opened, and at this time, the UE (the UE and the base station) considers that only the CBG level subcodebooks (or only the CBG level codebooks) are formed. (in this case, further description of CBG codebook formation follows)

4) And when the base station configures only one dynamic codebook for the UE and the CBG mechanism is started for the carrier configured for the UE, the UE forms a CBG-level sub-codebook. (in this case, further description of CBG codebook formation follows)

The explicit signaling method specifically includes at least one of the following methods:

1) the base station configures a dynamic codebook for the UE and uses a parameter a for indicating a specific configuration of the dynamic codebook for the UE, for example, the codebook is 2 sub-codebooks (1 sub-codebook for each of TB level and CBG level), the codebook is only a sub-codebook for TB level, or the codebook is only a sub-codebook for CBG level. The parameter a is sent to the UE through a downlink Control information DCI or an RRC (Radio Resource Control) message.

2) The base station configures a codebook type for the UE, and directly indicates the codebook type configuration through a parameter B, for example, the codebook type includes: the codebook is a static codebook, the codebook is dynamic and includes 2 sub-codebooks (there are 1 sub-codebooks for the TB level and the CBG level respectively), the codebook is a dynamic sub-codebook only for the TB level, or the codebook is a dynamic sub-codebook only for the CBG level. And the parameter B is sent to the UE through downlink control information DCI or RRC message.

After acquiring the configuration information of the codebook, the UE forms the codebook in the following manner.

1) The base station configures a dynamic codebook for the UE, at least one of a plurality of carriers configured for the UE is configured with a CBG mechanism to be closed, at least one of the carriers is configured with a CBG mechanism to be opened, and at the moment, when the UE (the UE and the base station) considers that the dynamic codebook is formed, 2 sub-codebooks can be formed, one is a sub-codebook at a TB level, and the other is a sub-codebook at a CBG level. At this time, the codebook is formed as:

when detecting that the DCI corresponding to the TB is fallback DCI (or the CBG mechanism of the carrier where the TB is located is turned off (further including the unconfigured CBG mechanism of the carrier), or the CBG mechanism of the carrier where the TB is located is turned on, or the UE knows that the TB is to be formed into a TB level HARQ-ACK (for example, the CBG mechanism in the carrier where the TB is located is turned off or the CBG mechanism is not configured, and the UE can know the configuration information through signaling)) among a plurality of TBs scheduled for the UE, the UE forms a 1-bit TB level HARQ-ACK for the TB and places the HARQ-ACK in a TB level sub-codebook.

When the UE schedules a plurality of TBs, the UE detects that DCI corresponding to the TB is non-fallback DCI and a CBG mechanism in a carrier where the TB is located is started, and the UE forms an N-bit CBG level HARQ-ACK (N is the maximum CBG number configured and is the maximum CBG number in all carriers configured for the UE) for the TB and places the N-bit CBG level HARQ-ACK in a CBG level sub-codebook.

For the TBs losing DCI, forming HARQ-ACK at CBG level and placing the HARQ-ACK in CBG sub-codebook (also forming HARQ-ACK at TB level of 1bit, then repeating to N bit, placing the HARQ-ACK in CBG sub-codebook, the HARQ-ACK sent by the two HARQ-ACK is the same finally).

2) The base station configures a dynamic codebook for the UE, and CBG mechanisms in a plurality of carriers configured for the UE are all opened, and at the moment, the UE (the UE and the base station) considers that only CBG subcodebooks (or only CBG-level codebooks) in the dynamic codebook are formed. At this time, the codebook is formed as:

when the DCI corresponding to the TB detected by the UE is fallback DCI in a plurality of TBs scheduled for the UE, the UE forms HARQ-ACK of a 1-bit TB level for the TB and repeats the HARQ-ACK to N bits, and the HARQ-ACK is placed in a CBG sub-codebook.

When the DCI corresponding to the TB detected by the UE is the non-fallback DCI in the plurality of TBs scheduled for the UE, the UE forms HARQ-ACK at the CBG level for the TB and places the HARQ-ACK in the CBG sub-codebook.

3) When the base station configures the dynamic codebook for the UE and only one carrier is configured for the UE, and when the carrier is configured with a CBG mechanism to be started, the UE (the UE and the base station) considers that the dynamic codebook only has a CBG subcodebook. At this time, the codebook is formed as:

Example 2

In the present example, an information processing method is provided for solving the problem of how the UE knows what codebook to form and how a specific codebook is formed.

The UE (UE and base station) always considers that after the UE is configured with the dynamic codebook, 2 sub-codebooks are always configured at the same time (only one of the sub-codebooks (TB sub-codebook or CBG sub-codebook) may be empty, i.e. not transmitted, and does not exist in the process of forming the codebook according to the specific scheduling situation). And then the base station and the UE determine whether the TB sub-codebook or the CBG sub-codebook exists according to the CBG mechanism configuration condition in one or more carriers configured for the UE and the condition that the scheduled TBs have the TBs scheduled by using fallback DCI.

For example, when a carrier exists in one or more carriers configured for the UE and is turned off by the configured CBG mechanism (including that the carrier exists and is not configured with CBG), or when a TB exists in a plurality of TBs (which may be one or more BWPs from one or more carriers) that are scheduled and is scheduled by fallback DCI (even if the one or more carriers are turned on by the configured CBG mechanism), the UE (UE and base station) considers that a TB sub-codebook exists in the dynamic codebook, (otherwise, the TB sub-codebook may be considered as not existing);

for example, when there is a carrier in one or more carriers configured for the UE that is turned on by the CBG configuration mechanism (and there is a TB scheduled by the non-fallback DCI in the carrier where the CBG is turned on, it is generally considered that the TB is scheduled in the carrier by using the non-fallback DCI as long as the carrier is configured with the CBG on, so this "and" restriction may not be present), the UE (UE and base station) considers that the CBG sub-codebook exists (otherwise, the CBG sub-codebook may be considered to not exist).

Some examples are as follows:

if no TBs scheduled by fallback DCI occurs in a plurality of scheduled TBs (one or more BWPs from one or more carriers), and all carriers where the TBs are located are configured with a CBG mechanism on (i.e. none of TBs occurs from carriers not configured with CBG or from carriers configured with CBG mechanism off), at this time, the UE (UE and base station) considers that the sub-codebook at the TB level is empty (i.e. does not exist), and the HARQ-ACKs of the plurality of scheduled TBs all form a HARQ-ACK at the CBG level and are placed in the sub-codebook of CBG. For the TBs losing DCI, forming HARQ-ACK at CBG level and placing the HARQ-ACK in CBG sub-codebook (also forming HARQ-ACK at TB level of 1bit, then repeating to N bit, placing the HARQ-ACK in CBG sub-codebook, the HARQ-ACK sent by the two HARQ-ACK is the same finally).

If the TBs scheduled by the fallback DCI appear in the scheduled multiple TBs (from one or more BWPs of one or more carriers), even if the carriers where the multiple TBs are located are all configured with the CBG mechanism on (i.e. some TBs in the multiple TBs are from the carriers not configured with the CBG or from the carriers configured with the CBG mechanism off), at this time, the UE (UE and the base station) considers that the TB sub-codebook exists, and forms a 1-bit TB level HARQ-ACK for the TBs scheduled by the fallback DCI, and places the HARQ-ACK in the TB sub-codebook. CBG subcodebooks also exist. For TBs with missing DCI (also called missed detection), forming HARQ-ACK at CBG level and placing the HARQ-ACK in CBG subcodebook (also forming HARQ-ACK at TB level of 1bit, then repeating to N bit, placing the HARQ-ACK in CBG subcodebook, the HARQ-ACK sent by both is the same finally).

If in a plurality of scheduled TBs (BWPs from one or more carriers), some of the carriers configured for the UE are configured with CBG mechanism on and some of the carriers are configured with CBG mechanism off (or are not configured with CBG), at this time, the UE (UE and base station) considers that both TB subcodebooks and CBG subcodebooks exist, and forms a 1-bit TB level HARQ-ACK for the TB scheduled by fallback DCI and places it in the TB subcodebook (regardless of whether the CBG mechanism of the carrier from which this TB scheduled by fallback DCI comes is on). For TBs with missing DCI (also called missed detection), forming HARQ-ACK at CBG level and placing the HARQ-ACK in CBG subcodebook (also forming HARQ-ACK at TB level of 1bit, then repeating to N bit, placing the HARQ-ACK in CBG subcodebook, the HARQ-ACK sent by both is the same finally).

If in a plurality of scheduled TBs (one or more BWPs from one or more carriers), all carriers configured for the UE are configured with a CBG mechanism to be turned on, and the base station does not use fallback DCI when scheduling the TB, at this time, the UE (UE and base station) considers that the TB subcodebook does not exist and the CBG subcodebook exists. For TBs with missing DCI (also called missed detection), forming HARQ-ACK at CBG level and placing the HARQ-ACK in CBG subcodebook (also forming HARQ-ACK at TB level of 1bit, then repeating to N bit, placing the HARQ-ACK in CBG subcodebook, the HARQ-ACK sent by both is the same finally).

If in a plurality of scheduled TBs (one or more BWPs from one or more carriers), all carriers configured for the UE are configured with a CBG mechanism to be closed, at this time, the UE (UE and base station) considers that a TB sub-codebook exists and a CBG sub-codebook does not exist. For TBs with missing DCI (also called missed detection), forming HARQ-ACK at CBG level and placing the HARQ-ACK in CBG subcodebook (also forming HARQ-ACK at TB level of 1bit, then repeating to N bit, placing the HARQ-ACK in CBG subcodebook, the HARQ-ACK sent by both is the same finally).

Example 3

In this example, in order to further reduce the complexity of sub-codebook determination and codebook formation, processing from the viewpoint of scheduling may be considered.

If the codebook type is configured for the UE, and when the UE is configured with a dynamic codebook and only a CBG subcodebook (i.e. the UE is configured with a dynamic subcodebook only at CBG level), at this time, each of the multiple TBs scheduled for the UE can only use non-fallback DCI scheduling (i.e. at this time, the base station cannot use fallback DCI to schedule the multiple TBs, or the UE does not expect the multiple TBs to be scheduled by fallback DCI, which is mainly because the counting downlink allocation index (counter dai) and the total downlink allocation index (totalDAI) cannot be carried in the fallback DCI at the same time, which may cause the UE to fail to find the loss of DCI of the TBs), and then the UE forms HARQ-ACKs at CBG level for the multiple TBs respectively and places the HARQ-ACKs in the CBG subcodebook (the TB subcodebook does not exist).

Similarly, if the UE implicitly knows a specific codebook type (for example, the base station configures the codebook for the UE as a semi-static codebook or a dynamic codebook, but when the codebook is a dynamic codebook, which sub-codebook is known implicitly), for example, when one or more carriers are configured for the UE and the dynamic codebook is configured for the UE, and the carriers configured for the UE are all CBG mechanisms turned on: the non-fallback DCI can only be used if the base station schedules multiple TBs for the UE from the one or more carriers. The UE forms HARQ-ACKs of a CBG level for a plurality of TBs respectively and places the HARQ-ACKs in a CBG sub-codebook (a TB sub-codebook does not exist).

This restriction of the DCI format used when scheduling TBs is an easy way to implement.

Example 4

In this example, an information processing mechanism is provided:

when the HARQ-ACKs of multiple TBs scheduled for the UE (these TBs may be from one or more partial Bandwidth (BWP) of only one carrier, or from one or more BWP of multiple aggregated carriers) are fed back using the dynamic codebook, for the TBs scheduled by fallback DCI in the carriers configured with CBG mechanism turned on, the UE (UE and base station) agrees to generate HARQ-ACK at TB level, and then repeats to N bits (N is the configured maximum CBG number, which is the maximum CBG number in all carriers configured for the UE), and places the N bits in the CBG subcodebook for feedback.

Wherein, the UE is configured with one or more carriers, and the CBG mechanism configuration in these carriers may be: part of carriers are configured with a CBG mechanism to be started, and the rest carriers are configured with a CBG mechanism to be closed or not; or all carriers are configured with CBG mechanism starting; or all carriers are configured with CBG mechanism off or not configured with CBG mechanism.

In this example, an information processing mechanism is further provided:

the UE is configured with one or more carriers, and the CBG mechanism configuration in these carriers may be:

1) part of carriers are configured with a CBG mechanism to be started, and the rest carriers are configured with a CBG mechanism to be closed or not;

2) all carriers are configured with CBG mechanism opening;

3) all carriers are configured with a CBG mechanism to be closed or not configured with the CBG mechanism;

(the above CBG mechanism configuration has virtually no effect on the following approach, i.e. it is possible to configure regardless of the CBG mechanism)

When HARQ-ACKs of multiple TBs scheduled for a UE (these TBs may be from one or more partial Bandwidths (BWPs) of only one carrier, or from one or more BWPs of multiple aggregated carriers) are fed back using a dynamic codebook, if the base station uses fallback DCI scheduling for the TB, the base station asks the UE to place HARQ-ACKs of the TB in a TB subcodebook or a CBG subcodebook through the counted downlink allocation index DAI and/or the total downlink allocation index DAI. And the UE receives fallback DCI corresponding to the TB, and determines that the HARQ-ACK of the TB is placed in a TB sub-codebook or a CBG sub-codebook according to the counted downlink allocation indexes DAI and the total downlink allocation indexes DAI. And the UE and the base station agree, if the HARQ-ACK of the TB is placed in the CBG sub-codebook, the UE firstly forms the HARQ-ACK of the TB level, and then repeats to N bits and places the HARQ-ACK of the TB level in the CBG sub-codebook. If the HARQ-ACK of the TB is placed in the TB sub-codebook, the UE forms the HARQ-ACK of the TB level, which is placed in the TB sub-codebook.

In this example, an information processing mechanism is further provided:

and configuring a dynamic codebook for the UE, and requiring the dynamic codebook to be transmitted through a PUSCH of the UE. Now, since the dynamic codebook may include 2 sub-codebooks, a total downlink assignment index DAI is indicated for each of the 2 sub-codebooks, and the DCI for scheduling the PUSCH is designed, thereby avoiding the complexity of UE detection. The DCI that can schedule the PUSCH in the existing NR may be fallback DCI or non-fallback DCI, and how parameters in the DCI are agreed is described below.

2) all carriers are configured with CBG mechanism opening;

When the HARQ-ACK of multiple TBs scheduled for the UE (these TBs may be from one or more partial Bandwidth (BWP) of only one carrier, or from one or more BWP of multiple aggregated carriers) is fed back using a dynamic codebook, and the dynamic codebook is required to be transmitted through the PUSCH of the UE, the PUSCH can only use a non-fallback DCI mode (that is, the UE does not expect to receive fallback DCI to schedule the PUSCH), and the DCI always uses 2 DAI fields, and the 2 DAI fields are used as downlink allocation indexes DAI for the CBG sub-codebook and the TB sub-codebook respectively. When the CBG sub-codebook is empty, the DAI field is indicated as 0, and when the TB sub-codebook is empty, the DAI field is indicated as 0.

Example 5

The following example is to solve the problem of how to determine the sequence group for each frequency hopping after the frequency domain frequency hopping of the Channel, for example, when the Channel is the frequency hopping of a Physical Uplink Control Channel (PUCCH), the sequence group (also called group sequence) used for each frequency hopping needs to be determined. When each frequency hopping uses different sequence groups, the robustness of the channel is increased, and the demodulation performance of the channel is improved.

One or more channels are configured for one UE in one scheduling unit (e.g., slot), and the channels are frequency-hopped, where one channel becomes 2 hopping parts (each called a hop).

For example, one channel occupying OFDM (Orthogonal Frequency Division Multiplexing) symbol 3 to OFDM symbol 6 (14 OFDM symbols are included in the scheduling unit, and the numbers are symbol 0 to symbol 13) are configured for the UE in one scheduling unit. At this time, after the frequency domain hopping of the channel, the first hopping of the channel is located at PRBn (only frequency domain resource location is shown, not specific resource size) in symbols 3 to 4, and the second hopping of the channel is located at PRBk in symbols 5 to 6.

Also for example, 2 (possibly multiple) channels are configured for the UE in one scheduling unit. The first channel occupies OFDM symbols 3 to 6 (the scheduling unit includes 14 OFDM symbols, numbered symbol 0 to symbol 13). At this time, after the frequency domain hopping of the channel, the first hopping of the channel is located at PRBn1 (only frequency domain resource location is shown, not specific resource size) in symbols 3 to 4, and the second hopping of the channel is located at PRBk1 in symbols 5 to 6. The second channel occupies OFDM symbol 7 to symbol 10, and after frequency hopping of the channel, the first frequency hopping of the channel is located at PRBn2 (only frequency domain resource location is shown, but not specific resource size) in symbol 7 to symbol 8, and the second frequency hopping of the channel is located at PRBk2 in symbol 9 to symbol 10.

The base station and the UE agree to determine the sequence group used by each frequency hopping of the channel in the following manner:

mode 1

The base station and the UE consider that a number is configured for each frequency hopping of the channel in the scheduling unit, for example, if the UE has only one channel in the scheduling unit and the channel frequency domain hops, the number of the first frequency hopping is marked as 0 and the number of the second frequency hopping is marked as 1. If the UE configures multiple channels in the scheduling unit and the channels frequency-domain hop, the number of each hop of the 1 st channel is used by each hop pair of the subsequent channels. For example, 2 channels are configured in one scheduling unit for the UE, each frequency-domain hopping, and then the number of the first hopping frequency of the first channel is denoted as 0, and the number of the second hopping frequency is denoted as 1. Then the number of the first hop of the second channel is also denoted by 0 and the number of the second hop is denoted by 1 (it is also possible to exchange the two hop numbers of the previous channel with the two hop numbers of the next channel, for example, the number of the first hop of the second channel is denoted by 1 and the number of the second hop is denoted by 0).

Then, the base station and the UE further estimate the sequence group used by each hop using the number of the hop.

Mode 2

Based on the example of mode 1, the numbering rule for each frequency hopping of each channel in the scheduling unit is different for the UE.

When the UE configures a plurality of channels in the scheduling unit and each channel hops, the number of each hopping frequency in the front and back 2 channels is kept continuous. When 2 channels are configured in the scheduling unit for the UE, and each channel is frequency hopped, the number of the first frequency hopping of the first channel is 0, the number of the second frequency hopping is 1, the number of the first frequency hopping of the second channel is continuous with the number of the second frequency hopping of the previous channel, so the number is 3, and the number of the second frequency hopping of the second channel is 4.

It should be noted here that if one UE configures multiple channels in one scheduling unit, and part of the channels perform frequency domain hopping and part of the channels do not perform frequency domain hopping, the channels that do not perform frequency domain hopping and the channels that perform frequency domain hopping (together) are numbered consecutively. For example, 3 channels are configured in one scheduling unit for the UE, the first and third channels are both frequency-domain hopped, and the second channel is not frequency-domain hopped, so the numbering may be: the number of the 2 hops for the first channel is 0 and 1, respectively, the number of the second channel is 2, and the number of the 2 hops for the third channel is 3 and 4. The numbering is now continuous between 3 channels.

Modes 1 and 2 can be summarized as: the base station and the UE think that when the UE has one or more channels to carry out frequency domain frequency hopping in one scheduling unit, each frequency hopping of each channel is provided with a number, and then a sequence group used by the frequency hopping is calculated according to the numbers. The specific numbering rules include: the number of each frequency hop of the latter channel follows the number of each frequency hop of the former channel; or the number of each frequency hopping of the latter channel is correspondingly exchanged with the number of each frequency hopping of the former channel; or the number of the first hop of the following channel and the number of the last hop of the preceding channel are kept continuous (consecutive numbers between hops of a channel), or it can be described that the hop number of the following channel and the hop number of the preceding channel are continuous.

The specific method for estimating the sequence group from the frequency hopping number includes, but is not limited to, one of the following estimation methods, and the frequency hopping number may be used in the estimation process:

estimation 1:

u＝(f_gh+f_ss)mod Q

and (3) calculating:

u＝(f_gh+f_ss)mod Q

and 3, calculating:

u＝(f_gh+f_ss)mod Q

wherein u represents an index of the sequence group, Q represents the total number of the sequence group in the system, e.g., 30, and f_ssThe definition is determined by the cell physical ID, e.g. f_ss＝n_ID mod 30，n_IDIs the cell ID. N is_sFor the numbering of the scheduling units, if the channel does not frequency-domain hop, the l_hopIs the channel number, if the channel frequency domain hops, said/_hopIs the hopping number of a channel, c (-) is a pseudo-random sequence with an initial value

N is_IDIs a cell ID, which may be a cell physical ID, or a virtual cell physical ID configured by a higher layer. N is a constant value, N describes a total number of times that a UE needs to determine a sequence group for a channel and a frequency domain hopping of the channel in a scheduling unit, for example, multiple channels are configured for the UE in the scheduling unit, and each channel is hopped, for example, 1 channel is configured, and each hopping frequency of 2 hopping frequencies (hop) needs to determine the sequence group, so that the number of times of the sequence group needs to be determined in total to be N ═ 2, for example, 2 channels are configured, and each hopping frequency has 4 total hopping frequencies, and each hopping frequency needs to determine the sequence group, so the number of times of the sequence group needs to be determined in total to be N ═ 4; for another example, if 3 channels are configured, and one channel does not hop, and 2 channels hop, 4 hopping sequences are required to determine the sequence group, and another channel also needs to determine the sequence group to use for the entire channel, so that the total number of times that the sequence group needs to be determined is N + 4+ 1. N determines the number of sequence groups according to common or always considering the maximum requirement, and may preferably but not limited to one of the values in the set 2,7, 14.

The present example provides an information processing method including: and setting numbers for the channels and/or the frequency hopping of the channels in one scheduling unit, and calculating sequence groups corresponding to the channels and/or the frequency hopping of the channels according to the numbers and a preset rule.

Wherein, the setting number for the channel and/or each frequency hopping of the channel in one scheduling unit includes at least one of the following:

one or more channels are configured for one UE in one scheduling unit, when the one or more channels respectively carry out frequency domain frequency hopping, continuous numbers are set for the frequency hopping of each channel, and the numbers of the frequency hopping of the latter channel are allowed to repeat the numbers of the frequency hopping of the former channel.

one or more channels are configured for one UE in one scheduling unit, and when the one or more channels are not frequency-hopped respectively, the same number is set for each channel.

The frequency hopping numbering mechanism provided in the technical scheme can not only solve the problem that one channel in one scheduling unit hops in the frequency domain, but also is more suitable for determining the sequence group used by frequency hopping of each channel under the condition that a plurality of channels in one scheduling unit hop in the frequency domain, and is simple to implement. The 3 calculation modes can well realize the randomization of the sequence group, so that the sequences among different cells can be randomized, and the collision is avoided.

Example 6

This example illustrates a method of reducing semi-static codebook overhead.

In NR, currently, the UE supports a semi-static codebook, i.e., the UE is configured with a semi-static codebook, and the UE always feeds back HARQ-ACK according to a fixed number of bits, regardless of whether the base station schedules TBs for the UE or how many TBs are scheduled. For example, for all possible occasions for scheduling TBs within a scheduling window length corresponding to a semi-static codebook, the UE needs to feed back HARQ-ACK, which is mainly for simplicity, and avoids the problem of inconsistent codebook size understanding caused by the change of the number of scheduled TBs or missed detection when the UE detects DCI, thereby avoiding introducing a corresponding solution mechanism, but the HARQ-ACK overhead of the semi-static codebook is relatively high.

In the related art, when a semi-static codebook is configured for a UE and the semi-static codebook of the UE is transmitted through a physical uplink shared channel PUSCH of the UE, the UE transmits the semi-static codebook by puncturing data of the PUSCH channel or by reserving a part of resources from the PUSCH channel. Specifically, for example, a semi-static codebook is configured for the UE, one or more TBs (which may be from one or more partial Bandwidths (BWPs) of only one carrier or one or more BWPs of multiple aggregated carriers) are scheduled for the UE, and HARQ-ACKs of the TBs are required to be multiplexed together to form the semi-static codebook for transmission via the PUSCH of the UE. The UE is then scheduled a PUSCH by downlink control information DCI (this downlink control information is also called an uplink grant, and is used to schedule the PUSCH of the UE), and then transmits the semi-static codebook by puncturing or reserving part of the resources from its PUSCH.

The following is an improvement over the prior art to achieve a reduction in semi-static codebook overhead in some cases. Although the semi-static codebook is configured for the UE, the base station does not always schedule enough TBs (for example, the base station does not schedule a TB to the UE in each scheduling time within a scheduling window corresponding to the semi-static codebook), that is, in some cases, the base station may schedule only one TB, and if the UE still performs codebook feedback according to the agreed semi-static codebook size, it is obvious that the UE actually feeds back a large number of invalid codebooks at this time. For another example, the base station actually has no scheduling for one TB, and if the UE still performs feedback according to the agreed codebook size, it is obvious that the codebook overhead is wasted. In this regard, the following modifications can be made in a number of ways, with specific modifications as follows:

mode A:

if the UE is configured with a semi-static codebook and requires transmission of the semi-static codebook through the PUSCH channel of the UE (regardless of whether the UE actually has uplink data or not): if the base station does not schedule any TB at all scheduling occasions (positions where TBs are allowed to be scheduled for the UE, which are configured by the base station, and may be distributed in one or more carriers configured for the UE, and/or distributed in one or more BWPs configured for the UE) (that is, no TB is scheduled for the UE in a scheduling window corresponding to the semi-static codebook of the current time by the base station, and the TB is sometimes referred to as a physical downlink shared channel PDSCH, or DCI for scheduling the TB is not sent in a scheduling window corresponding to the semi-static codebook of the current time by the base station (except DCI for scheduling semi-static services)), the base station notifies the UE using the parameter X in the DCI for scheduling the PUSCH, no TB is scheduled in the scheduling occasion corresponding to the semi-static codebook of the current time, and accordingly, the UE does not need to transmit the semi-static codebook, and the corresponding puncturing or resource reservation does not need to be implemented for the semi-static codebook; if the base station schedules TB (no matter several TBs are scheduled) at the scheduling opportunity in the scheduling window corresponding to the semi-static codebook, the base station uses the parameter X to notify the UE in the DCI for scheduling the PUSCH, the TB is scheduled at the scheduling opportunity corresponding to the semi-static codebook at this time, and correspondingly, the UE forms a codebook according to the corresponding semi-static codebook and transmits the codebook through the PUSCH (namely, the UE transmits the codebook according to the existing semi-static codebook). For example, the parameter X uses 1bit, when set to 0, it indicates that the base station does not schedule any TB, and when set to 0, it indicates that the base station schedules the TB. And vice versa. For another example, (corresponding to the UE side), the parameter X uses 1bit, and when the parameter X is set to 0, the UE does not form a codebook (i.e., does not transmit a semi-static codebook), and when the parameter X is set to 1, the UE forms a configured semi-static codebook. And vice versa.

In this way, the parameter X can distinguish two states for the UE in the semi-static codebook: the base station does not schedule any TB in the scheduling occasion in the scheduling window corresponding to the semi-static codebook, and the base station schedules the TB in the scheduling occasion in the scheduling window corresponding to the semi-static codebook. And then respectively implementing corresponding semi-static codebook processing modes for the two corresponding states according to convention. This is also the case when the UE fails to detect DCI of all scheduled TBs, for example, when the UE does not detect DCI of any TB in the scheduling occasion corresponding to the semi-static codebook, the UE cannot know whether the base station does not schedule any TB or whether the UE itself fails to detect all DCI.

Mode B

If the UE is configured with a semi-static codebook and requires transmission of the semi-static codebook through the PUSCH channel of the UE (regardless of whether the UE actually has uplink data or not): if the base station transmits only once DCI at a scheduling occasion within a scheduling window corresponding to a semi-static codebook to schedule a TB (sometimes referred to herein as PDSCH, if the UE is configured with a single codeword CW (codeword), when one DCI schedules one TB, if the UE is configured with 2 CWs, when one DCI schedules 2 TBs, or, it can be described herein that if the base station schedules only one TB in a scheduling occasion within a scheduling window corresponding to a semi-static codebook, but it is noted that transmitting only once DCI and only one TB are different, but similar to the following semi-static codebook processing rules in this application, in addition, the TB here may be one or more BWPs from one or more carriers configured for the UE, and when multiple carriers are generally divided into primary and secondary carriers, the TB here may be from only secondary carriers) or no TB is scheduled (i.e. no scheduled DCI is transmitted, except DCI for scheduling semi-static service), the base station uses the parameter S in scheduling the DCI of the PUSCH to notify the UE that only one time of DCI is transmitted to schedule a TB (or only 1 TB is scheduled) or no TB is scheduled in the scheduling occasion corresponding to the semi-static codebook of this time, and accordingly, the UE forms a HARQ-ACK codebook for a TB scheduled by DCI (or the UE does not receive DCI of any scheduled TB, and the UE also forms a HARQ-ACK codebook. The detailed codebook formation is shown below), and correspondingly transmitting the HARQ-ACK codebook corresponding to the TB scheduled by the DCI in the PUSCH of the UE in a punching or resource reservation mode; if the base station sends more than one DCI scheduling TB or schedules more than one TB at the scheduling opportunity corresponding to the semi-static codebook, the base station uses the parameter S in the DCI for scheduling the PUSCH to inform the UE that more than one DCI is sent at the scheduling opportunity corresponding to the semi-static codebook of this time to schedule the TB or schedule more than 1 TBs, and correspondingly, the UE forms a codebook according to the corresponding semi-static codebook and sends the codebook through the PUSCH.

If the base station schedules a TB or only sends DCI once to schedule the TB in the scheduling window, the UE receives the DCI of the TB or the scheduled TB and the parameter S indicates that the base station schedules the TB (or sends the DCI once to schedule the TB) or does not schedule the TB, the UE determines to form ACK or NACK according to the decoding result (if one CW is configured, ACK or NACK information is formed according to 1bit, and if 2 CWs are configured, ACK or NACK information is formed according to 2 bits); if the UE does not receive a TB or does not receive DCI for scheduling the TB within the scheduling window, and the parameter S indicates that the base station schedules a TB (or sends DCI once to schedule the TB) or does not schedule the TB, the UE forms NACK information (NACK information is formed according to 1bit if one CW is configured, and NACK information is formed according to 2 bits if 2 CWs are configured). If the UE receives one TB or no TB and the parameter S indicates that the base station schedules more than one TB, the codebook is formed according to a semi-static codebook. For example, the parameter S uses 1bit, when set to 0, it indicates that the base station does not schedule any TB or only sends DCI once to schedule TB (or only schedules one TB), or it indicates that the UE forms a HARQ-ACK codebook for the received TB (the UE does not receive any TB and also forms a HARQ-ACK codebook, where the number of TBs received by the UE is related to the number of CWs configured by the UE), and when set to 1, it indicates that the base station sends DCI more than one time to schedule TB or schedules more than one TBs. And vice versa. For another example (corresponding to the UE side), the parameter S uses 1bit, when setting 0, it indicates that the UE generates HARQ-ACK for one DCI scheduled TB (S) (where this further includes that if the UE detects this DCI, this DCI schedules 1 TB, the UE generates HARQ-ACK for this TB, this DCI schedules 2 TBs, the UE generates HARQ-ACK for this 2 TBs (HARQ-ACK bundling for 2 TBs is also allowed), or the UE knows whether it is configured with 1 CW (one CW corresponds to one TB) or 2 CWs through high layer signaling, and then the UE generates HARQ-ACK codebook for this scheduled 1 TB or 2 TBs, if the UE does not detect any DCI, the UE generates HARQ-ACK codebook according to 1 CW or 2 CWs configured by high layer signaling, if 1 CW is configured, the UE generates HARQ-ACK codebook for one TB, if 2 CWs are configured, the UE generates HARQ-ACKs for 2 TBs. Here, the HARQ-ACK generation includes three possible ways, 1) HARQ-ACK at TB level, 2) HARQ-ACK at N-bit CBG level, 3) HARQ-ACK at TB level repeated N times (N is defined above), and when the parameter S is set to 1, it indicates that the UE generates the configured semi-static codebook. And vice versa.

Description of the drawings: the parameters X and S in the modes a and B may be 1bit in fallback DCI for scheduling uplink data. With respect to scheduling only one TB or transmitting only one time DCI scheduling TB within a scheduling window corresponding to a semi-static codebook (both the DCI in which no scheduled TB is detected and the DCI in which no scheduled TB is detected are identical), the essence is the same, except that one DCI can schedule only one TB in some cases and multiple TBs can be scheduled in some cases (for example, when 2 CWs are configured) according to the configuration situation. Therefore, in the above-mentioned manner, in case 1, that is, only one TB is scheduled and only one DCI scheduled TB is transmitted (including DCI which does not schedule any TB or transmit any scheduled TB) in the scheduling window corresponding to the semi-static codebook, it may be considered that both the processing manners do not use the semi-static codebook, and 1 or 2 TBs or N are fed back_cwA (N)_cwNumber of CWs configured for the UE); in other cases (except case 1), the codebook needs to be formed according to a semi-static codebook.

In this way, the parameter S is introduced to help the UE reduce the overhead of the semi-static codebook when the above two cases (case 1 and other cases) occur.

Forming a HARQ-ACK codebook for the case that the UE schedules only one DCI (or only one TB), specifically including the following three cases:

the UE is configured with a semi-static codebook, and when at least one carrier in one or more carriers configured for the UE is configured with a CBG mechanism for starting, and the DCI is a fallback DCI (or the TB is scheduled by a fallback DCI), the UE forms a HARQ-ACK at a TB level for the TB corresponding to the DCI (for example, when the DCI schedules a TB, 1-bit TB HARQ-ACK information is formed, when the DCI schedules 2 TBs, 2-bit TB HARQ-ACK information is formed, each TB corresponds to 1 bit; the UE can know that the current DCI schedules 1 or 2 TBs according to the configuration of the base station or from the received DCI, and then repeats to N bits (N is defined in the previous example, and is the number of CBGs, which is the maximum number of CBGs configured in the carriers configured for the UE). And forming HARQ-ACK at a CBG level for the TB corresponding to the lost DCI (also called missed detection) (or forming HARQ-ACK at a TB level, and repeating to N bit, wherein the HARQ-ACK sent in the two modes is the same finally).

The UE is configured with a semi-static codebook, and when at least one carrier in one or more carriers configured for the UE is configured with a CBG mechanism start, and the DCI is a non-fallback DCI (or the TB is scheduled by the non-fallback DCI), the UE forms a HARQ-ACK at a CBG level for the TB corresponding to the DCI (or the UE forms a HARQ-ACK at a CBG level for the TB), and finally is also a HARQ-ACK at a CBG level with N bits, if the number of CBGs configured for the TB where the DCI is scheduled is not the maximum number of CBGs configured in a plurality of carriers configured for the UE, the UE forms a HARQ-ACK at a CBG level according to the number of CBGs configured for the carrier at that time, and then fills NACK bits at the end until the total number of bits is equal to the maximum number of CBGs configured N in all carriers configured with CBGs. The rule is suitable for forming HARQ-ACK of CBG level under the condition that the number of CBGs configured by a plurality of carriers is different, and is suitable for other embodiments. For the TB corresponding to the missing DCI (also called missed detection), a CBG level HARQ-ACK is formed (or a TB level HARQ-ACK is formed and then repeated to N bits, and the HARQ-ACKs sent by the two modes are finally the same).

The UE is configured with a semi-static codebook, and one or more carriers configured for the UE are configured with a CBG mechanism to be closed, or are not configured with the CBG, no matter whether the DCI is fallback DCI or not, the UE forms HARQ-ACK at a TB level for the TB corresponding to the DCI (for example, if the DCI schedules one TB, 1-bit TB HARQ-ACK information is formed, if the DCI schedules 2 TBs, 2-bit TB level HARQ-ACK information is formed, each TB corresponds to 1 bit), and the UE can know that 1 or 2 TBs are scheduled by the current DCI according to the configuration of a base station or from the received DCI). For the TB corresponding to the missing DCI (also called missed detection), a CBG level HARQ-ACK is formed (or a TB level HARQ-ACK is formed and then repeated to N bits, and the HARQ-ACKs sent by the two modes are finally the same).

The following processing scheme can be summarized from scheme B:

if the UE configures a semi-static codebook and requires the UE to transmit the semi-static codebook through the PUSCH channel (the UE and the base station consider that the following processing rules exist, the UE side is the process of encoding and generating the codebook, and the base station side is the inverse process of decoding the codebook):

if the PUSCH is scheduled by a DCI with a parameter S (e.g., 1 bit) set to "1" ("1" is just an example), the UE (and base station) generates a semi-static codebook for one or more TBs that are scheduled (which are from one or more BWPs of one or more carriers and are required to feed back their HARQ-ACKs via the semi-static codebook); and the corresponding base station side schedules more than 1 TB or sends more than one time of DCI to schedule the TB in a scheduling window corresponding to the semi-static codebook, and the base station sets the parameter S to be 1 and sends the parameter S to the UE.

If the PUSCH is scheduled by a DCI, and the parameter S contained in the DCI is set to be 0, the UE (and the base station) generates a HARQ-ACK codebook for the received one or 2 TBs according to the decoding result of the 1 or 2 TBs; and the corresponding base station side schedules 1 TB or transmits DCI once in a scheduling window corresponding to the semi-static codebook to schedule the TB, and the base station sets the parameter S to be 0 and transmits the parameter S to the UE.

If the UE does not receive any TB (in the scheduling window corresponding to the semi-static codebook), the UE (considered by the UE and the base station) generates a HARQ-ACK codebook according to the fixed 1 TB or the fixed 2 TBs or according to the configured number of the CWs. For example, the UE and the base station agree to fixedly generate one HARQ-ACK codebook according to 1 TB or 2 TBs, for example, when it is agreed to generate one HARQ-ACK codebook according to 2 TBs fixedly, 2 TBs are scheduled according to one DCI to generate HARQ-ACK. For example, the UE and the base station agree to determine according to the number of CWs configured for the UE, for example, if the UE is configured with 1 CW, the UE generates a HARQ-ACK codebook according to 1 TB, if the UE is configured with 2 CW, the UE generates a HARQ-ACK codebook according to 2 TB, and so on, for example, the UE is configured with N_cwFor CW, UE is N_cwThe TBs form one HARQ-ACK codebook. And the corresponding base station side schedules 0 TBs or sends 0 DCI to schedule the TBs in a scheduling window corresponding to the semi-static codebook, and the base station sets the parameter S to be 0 and sends the parameter S to the UE.

Mode C

If the UE is configured with a semi-static codebook, when the semi-static codebook is required to be transmitted through a PUCCH (Physical Uplink Control CHannel): and if the UE does not detect the DCI of the scheduling TB at all the occasions in the scheduling window corresponding to the semi-static codebook, the UE does not form the semi-static codebook. Correspondingly, at this time, the base station side may not schedule any TB in the scheduling window, or the base station side may schedule a TB in the scheduling window but the UE loses all the corresponding DCI. When the UE detects DCI of the scheduling TB in the scheduling window, all DCI conditions are lost, then according to the processing, the UE does not feed back the semi-static codebook, at the moment, the base station feeds back the semi-static codebook for the UE so as to receive the semi-static codebook, the base station cannot receive the corresponding static codebook, and at the moment, the base station considers that the UE does not correctly receive the scheduled TB, so as to retransmit the TB (obviously, the retransmission is correct, because the UE actually does not correctly receive the semi-static codebook, and the semi-static codebook is transmitted through a PUCCH, the UE does not send the semi-static codebook and cannot influence the PUCCH or PUSCH transmission of other UEs); if the base station does not schedule any TB in the scheduling window, and the UE cannot detect any DCI of the scheduled TB, according to the processing, the UE does not feed back the semi-static codebook, and the base station cannot receive the semi-static codebook when receiving, and at the moment, the base station considers that the UE does not feed back the semi-static codebook and does not schedule the TB actually. And if the UE does not have the DCI missing condition, the UE forms a semi-static codebook according to the TB condition corresponding to the received DCI and sends the semi-static codebook, and the base station receives the fed-back semi-static codebook and determines whether to retransmit the TB according to the receiving condition.

In the related art, if the UE is configured with the semi-static codebook, even if the base station does not schedule any TB for the UE, the UE is required to feed back the semi-static codebook, and the semi-static codebook is prevented from being transmitted under the condition after the method C is adopted, so that codebook overhead is saved.

It should be noted that the present invention can be embodied in other specific forms, and various changes and modifications can be made by those skilled in the art without departing from the spirit and scope of the invention.

Claims

1. An information processing method applied to User Equipment (UE), the method comprising:

receiving Downlink Control Information (DCI), wherein the DCI carries a parameter S, and the parameter S is used for indicating the formation of a hybrid automatic repeat request acknowledgement information (HARQ-ACK) semi-static codebook;

generating and sending an HARQ-ACK codebook according to the parameter S;

the generating and sending of the HARQ-ACK codebook according to the parameter S comprises:

and under the condition that the HARQ-ACK semi-static codebook is configured and the HARQ-ACK semi-static codebook is required to be transmitted through a Physical Uplink Shared Channel (PUSCH), only one Transport Block (TB) or only one DCI (Downlink control information) scheduled TB is received, and a parameter S contained in the received DCI for scheduling the PUSCH is set to be a second numerical value, and then ACK or NACK is determined to be formed only for the received TB according to a decoding result.

2. The method as claimed in claim 1, wherein said HARQ-ACK codebook generation and transmission according to said parameter S comprises:

and under the condition that a HARQ-ACK semi-static codebook is configured and the HARQ-ACK semi-static codebook is required to be transmitted through a Physical Uplink Shared Channel (PUSCH), receiving DCI (Downlink control information) for scheduling the PUSCH and setting a parameter S contained in the DCI to be a first numerical value, and generating the HARQ-ACK semi-static codebook.

3. The method of claim 1, wherein the determining to form an ACK or NACK for only the received TB according to a decoding result comprises one of:

forming ACK or NACK information for one TB scheduled by 1bit under the condition of being configured into 1 code word CW, wherein the DCI schedules the one TB;

configured as 2 codewords CW, the DCI schedules two TBs forming ACK or NACK information in 2 bits for the two TBs.

4. The method as claimed in claim 1, wherein said HARQ-ACK codebook generation and transmission according to said parameter S comprises:

under the condition that a HARQ-ACK semi-static codebook is configured and the HARQ-ACK semi-static codebook is required to be transmitted through a Physical Uplink Shared Channel (PUSCH), receiving DCI (Downlink control information) for scheduling the PUSCH, setting a parameter S contained in the DCI to be a second numerical value, not receiving any DCI-scheduled TB at a corresponding scheduling opportunity in a scheduling window corresponding to the semi-static codebook, and generating a HARQ-ACK codebook according to a fixed number, wherein the fixed number is at least one of 1, 2 and the configured number of CWs.

5. The method of claim 4, wherein generating a HARQ-ACK codebook by a fixed number comprises at least one of:

under the condition that an HARQ-ACK codebook is generated according to the configured number of CWs, when the HARQ-ACK codebook is configured to be NCW CWs, an HARQ-ACK codebook is generated according to NCW TBs, wherein the NCW is the configured number of the CWs, and the value of the NCW is a positive integer;

generating an HARQ-ACK codebook according to 1 TB when being configured with at least one CW under the condition that the HARQ-ACK codebook is generated according to 1 TB;

in case that one HARQ-ACK codebook is generated according to 2 TBs, one HARQ-ACK codebook is generated according to 2 TBs when at least one CW is configured.

6. The method of claim 1, wherein the DCI is a DCI for scheduling a Physical Uplink Shared Channel (PUSCH), and wherein a parameter S carried in the DCI is 1bit, a first value of the parameter S is 1, and a second value of the parameter S is 0.

7. The method as claimed in claim 1, wherein said HARQ-ACK codebook generation and transmission according to said parameter S comprises:

and under the condition that a HARQ-ACK semi-static codebook is configured and the HARQ-ACK semi-static codebook is required to be transmitted through a Physical Uplink Shared Channel (PUSCH), if the parameter S contained in the DCI for scheduling the PUSCH is set to be a second numerical value, the HARQ-ACK semi-static codebook transmitted in the PUSCH is not formed, wherein the second numerical value is 0.

8. An information processing method applied to a base station, the method comprising:

configuring and sending Downlink Control Information (DCI), wherein the DCI carries a parameter S, and the parameter S is used for indicating the formation of a hybrid automatic repeat request acknowledgement information (HARQ-ACK) semi-static codebook;

receiving an HARQ-ACK codebook according to the parameter S;

the receiving of the HARQ-ACK codebook according to the parameter S comprises:

under the condition that a HARQ-ACK semi-static codebook is configured for User Equipment (UE) and the HARQ-ACK semi-static codebook is required to be transmitted through a Physical Uplink Shared Channel (PUSCH), only 1 TB is scheduled for the UE or a transmission block TB is scheduled by DCI for only one time at a scheduling opportunity in a scheduling window corresponding to the semi-static codebook, a parameter S is set to be a second numerical value in the DCI for scheduling the PUSCH, and the UE is required to determine to form ACK or NACK only for the TB according to a decoding result.

9. The method of claim 8, wherein the receiving the HARQ-ACK codebook according to the parameter S comprises:

under the condition that a HARQ-ACK semi-static codebook is configured for User Equipment (UE) and the HARQ-ACK semi-static codebook is required to be transmitted through a Physical Uplink Shared Channel (PUSCH), at least one Transmission Block (TB) is scheduled for the UE or at least two DCI scheduling TBs are transmitted at a scheduling opportunity in a scheduling window corresponding to the semi-static codebook, a parameter S is set to be a first numerical value in DCI for scheduling the PUSCH, and the UE is required to form the HARQ-ACK codebook according to the corresponding semi-static codebook and transmit the HARQ-ACK codebook through the PUSCH.

10. The method according to claim 8 or 9, wherein the scheduling occasion in the scheduling window corresponding to the semi-static codebook comprises at least one of:

the scheduling occasion is at least one time domain position configured for the UE to monitor the DCI;

the scheduling occasions are distributed in at least one carrier configured for the UE;

the scheduling occasions are distributed in a fractional bandwidth BWP of at least one carrier configured for the UE.

11. The method of claim 8, wherein the DCI is a DCI for scheduling a Physical Uplink Shared Channel (PUSCH) of a User Equipment (UE), and wherein a parameter S carried in the DCI is 1bit, wherein a first value of the parameter S is 1, and wherein a second value of the parameter S is 0.

12. The method of claim 8, wherein the receiving the HARQ-ACK codebook according to the parameter S comprises:

under the condition that a HARQ-ACK semi-static codebook is configured for User Equipment (UE) and the HARQ-ACK semi-static codebook is required to be transmitted through a Physical Uplink Shared Channel (PUSCH), if no TB is scheduled or no TB is scheduled for the UE at a scheduling time in a scheduling window corresponding to the semi-static codebook, a parameter S is set to be a second numerical value in DCI for scheduling the PUSCH, and the UE is not required to form the HARQ-ACK semi-static codebook transmitted in the PUSCH.

13. An information processing apparatus, applied to a User Equipment (UE), the apparatus comprising:

a codebook processing module for generating and transmitting HARQ-ACK codebook according to the parameter S;

14. An information processing apparatus, applied to a base station, the apparatus comprising:

a codebook processing module for receiving the HARQ-ACK codebook according to the parameter S;

the receiving of the HARQ-ACK codebook according to the parameter S comprises:

15. A user equipment, the user equipment comprising:

one or more processors;

a memory for storing one or more information processing programs which, when executed by the one or more processors, cause the one or more processors to implement the information processing method of any one of claims 1-7.

16. A base station, characterized in that the base station comprises:

one or more processors;

a memory for storing one or more information processing programs which, when executed by the one or more processors, cause the one or more processors to implement the information processing method of any one of claims 8-12.

17. A computer-readable storage medium on which an information processing program is stored, characterized in that the information processing program realizes the information processing method according to any one of claims 1 to 7 or 8 to 12 when executed by a processor.