WO2021088656A1

WO2021088656A1 - Method and apparatus for determining number of retransmissions, method and apparatus for indicating number of retransmissions, communication node, and medium

Info

Publication number: WO2021088656A1
Application number: PCT/CN2020/122932
Authority: WO
Inventors: 任敏; 石靖; 梁春丽; 苟伟; 韩祥辉; 郝鹏; 李儒岳
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-11-05
Filing date: 2020-10-22
Publication date: 2021-05-14
Also published as: TW202118340A; CN111092695A; CN111092695B

Abstract

Disclosed are a method and apparatus for determining the number of retransmissions, a method and apparatus for indicating the number of retransmissions, a communication node, and a medium. The method for determining the number of retransmissions comprises: receiving configuration information; and determining, according to the configuration information, the number of repeated transmissions of information to be transmitted. The method for indicating the number of retransmissions comprises: determining configuration information, the configuration information being used for indicating the number of repeated transmissions of information to be transmitted; and sending the configuration information.

Description

Method and device for determining the number of retransmissions, method and device for indicating the number of retransmissions, communication node, and medium

This application claims the priority of the Chinese patent application filed with the Chinese Patent Office with application number 201911073155.7 on November 05, 2019, and the entire content of this application is incorporated into this application by reference.

Technical field

This application relates to a wireless communication network, such as a method and device for determining the number of retransmissions, a method and device for indicating the number of retransmissions, communication nodes, and media.

Background technique

In the 5th Generation Mobile Communication Technology (5G), in order to ensure coverage and transmit low-latency and high-reliability services within a short transmission time, the communication node can use one or more time slots to repeatedly send the same For a Transport Block (TB), the number of repeated transmissions in the Release 15 (Release 15, R15) standard is notified by Radio Resource Control (RRC) signaling, and is formulated in the Release 16 (R16) standard In the process, the number of allowed repeated transmissions is indicated by high-layer signaling RRC, or indicated by Downlink Control Information (DCI). However, for different indication methods, there is no effective indication mechanism between the serving node and the communication node, so that the number of repeated transmissions cannot be determined efficiently, resulting in low reliability of repeated transmissions.

Summary of the invention

This application provides a method and device for determining the number of retransmissions, a method and device for indicating the number of retransmissions, a communication node, and a medium to improve the reliability of repeated transmission.

The embodiment of the present application provides a method for determining the number of retransmissions, including:

Receive configuration information;

The number of repeated transmissions of the information to be transmitted is determined according to the configuration information.

The embodiment of the present application also provides a method for indicating the number of retransmissions, including:

Determining configuration information, where the configuration information is used to indicate the number of repeated transmissions of the information to be transmitted;

Send the configuration information.

An embodiment of the present application also provides a device for determining the number of retransmissions, including:

The receiving module is set to receive configuration information;

The first determining module is configured to determine the number of repeated transmissions of the information to be transmitted according to the configuration information.

The embodiment of the present application also provides a device for indicating the number of retransmissions, including:

The second determining module is configured to determine configuration information, where the configuration information is used to indicate the number of repeated transmissions of the information to be transmitted;

The sending module is set to send the configuration information.

The embodiment of the present application also provides a communication node, including:

One or more processors;

Storage device for storing one or more programs;

When the one or more programs are executed by the one or more processors, the one or more processors implement the method for determining the number of retransmissions or the method for indicating the number of retransmissions.

The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method for determining the number of retransmissions or the method for indicating the number of retransmissions described above is implemented.

Description of the drawings

FIG. 1 is a flowchart of a method for determining the number of retransmissions according to an embodiment;

2 is a flowchart of a method for indicating the number of retransmissions according to an embodiment;

FIG. 3 is a schematic diagram of determining the priority of PDSCH based on processing capability 2 and implementation form 1 provided by an embodiment;

4 is a schematic diagram of determining the priority of PDSCH based on processing capability 1 and implementation form 1 according to an embodiment;

FIG. 5 is a schematic diagram of determining the priority of PDSCH based on processing capability 2, implementation form 1, and indication method 1 according to an embodiment;

FIG. 6 is another schematic diagram of determining the priority of PDSCH based on processing capability 2, implementation form 1, and indication method 1 according to an embodiment;

FIG. 7 is another schematic diagram of determining the priority of PDSCH based on processing capability 2, implementation form 1, and indication method 1, provided by an embodiment;

FIG. 8 is a schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2 and indication method 1 according to an embodiment;

FIG. 9 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 1 according to an embodiment;

FIG. 10 is a schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2 and indication method 1 according to an embodiment;

FIG. 11 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication method 1 provided by an embodiment;

FIG. 12 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 1, provided by an embodiment;

FIG. 13 is a schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 2 according to an embodiment;

FIG. 14 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 2 according to an embodiment;

15 is a schematic structural diagram of an apparatus for determining the number of retransmissions provided by an embodiment;

FIG. 16 is a schematic structural diagram of a device for indicating the number of retransmissions according to an embodiment;

Fig. 17 is a schematic structural diagram of a communication node provided by an embodiment.

Detailed ways

The application will be described below with reference to the drawings and embodiments.

In 5G technology, in order to ensure coverage and transmit low-latency and high-reliability services in a short transmission time, the introduction of aggregate transmission based on dynamic scheduling (Aggregate transmission scheduled by DCI) and scheduling-free repeated transmission (Transport Block Repetition for Uplink Transmission) With a Configured Grant), that is, the terminal can use one or more time slots to repeatedly send the same transport block (Transport Block, TB). The 5G Release 15 standard stipulates that the number of repeated transmissions is notified through separate RRC signaling. During the formulation of the Release 16 standard, the number of repeated transmissions is allowed to be combined with the Time Domain Resource Assignment (TDRA) information configured by the higher layers. After encoding, it is indicated by high-layer signaling RRC or DCI. However, for different indication methods, there is no effective indication mechanism between the service node and the communication node, and it is impossible to specify which way to indicate and realize the repeated transmission of the terminal, and the reliability of the repeated transmission is low.

In an embodiment of the present application, a method for determining the number of repeated transmissions is provided, which improves the reliability of repeated transmission by receiving configuration information and determining the number of repeated transmissions according to the configuration information. The communication nodes in the following embodiments are divided into two types: terminal and service node, where the terminal refers to the user equipment (User Equipment), and the number of repeated transmissions can be determined according to the configuration information; the service node refers to the network side, such as the base station, through Sending configuration information to the terminal can indicate the determination method and configuration of the number of repeated transmissions, so that the terminal can efficiently determine the number of repeated transmissions.

Fig. 1 is a flowchart of a method for determining the number of retransmissions according to an embodiment. The method provided in this embodiment can be applied to a terminal. As shown in FIG. 1, the method provided in this embodiment includes step 110 and step 120.

In step 110, configuration information is received.

In step 120, the number of repeated transmissions of the information to be transmitted is determined according to the configuration information.

In this embodiment, the configuration information is used to indicate the number of repeated transmissions. The information to be transmitted is carried on the physical transmission channel. For example, the serving node sends the information to be transmitted to the terminal through a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH).

In an embodiment, the information to be transmitted corresponds to the first transmission type, and the configuration information corresponds to the first mode or the second mode; the first mode includes: the first indication field of the radio resource control RRC signaling is used to indicate the number of repeated transmissions If the first indication field is not configured in the RRC signaling, the number of repeated transmissions is 1; the second method includes: the setting item in the TDRA information is used to indicate the number of repeated transmissions.

In this embodiment, the first transmission type refers to a situation in which repeated transmission of the physical transmission channel corresponds to the dispatching of scheduling information of the physical transmission channel through DCI.

In an embodiment, when the first indication field is configured in the RRC signaling, the value indicated by the first indication field is an integer greater than 1.

In an embodiment, for the second mode, the number of repeated transmissions is an integer greater than or equal to 1.

In an embodiment, the determining the number of repeated transmissions of the information to be transmitted according to the configuration information includes at least one of the following:

In the case that the setting item for each time domain resource in the TDRA information of the second mode is 1, the number of repeated transmissions is determined in the first mode; and there is at least one time in the TDRA information of the second mode. When the setting item corresponding to the domain resource is greater than 1, the second method is used to determine the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is equal to 1, it is passed The first method determines the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is greater than 1, the second method determines the number of repeated transmissions; in the second method If the setting item is not configured in the TDRA information, the number of repeated transmissions is determined by the first method.

When the TDRA information of the second method including the setting item is configured, the number of repeated transmissions is determined by the second method; when the TDRA information of the second method including the setting item is not configured, the TDRA information of the second method including the setting item is not configured. The first method determines the number of repeated transmissions.

In the case where the first indication field is configured in the RRC signaling in the first manner, the number of repeated transmissions is determined in the first manner; in the first manner, the RRC signaling does not configure the first indication field. If the setting item is configured in the TDRA information of the second mode, the number of repeated transmissions is determined by the second mode; in the first mode, the RRC signaling does not configure the first indication field In the case where the setting item is not configured in the TDRA information of the second mode, the number of repeated transmissions is equal to 1; in the first mode, the RRC signaling is not configured with a first indication If the TDRA information of the second mode including the setting item is not configured, the number of repeated transmissions is equal to 1.

In an embodiment, the determining the number of repeated transmissions of the information to be transmitted according to the configuration information includes:

In the case where the RRC signaling indicates the first logical value, the number of repeated transmissions is determined by the first method; in the case where the RRC signaling indicates the second logical value, the number of repeated transmissions is determined by the second method.

In the case of repeated transmission of the Physical Uplink Shared Channel (PUSCH) for dispatching scheduling information through DCI, the network side can configure the number of repeated transmissions in two ways.

In an embodiment, the PUSCH for which scheduling information is delivered through the DCI may include a dynamically scheduled PUSCH, or may include that the first transmission is an uplink transmission with configured grant, but the retransmission uses a dynamically scheduled PUSCH.

In an embodiment, the first way to configure the number of repeated transmissions is an indication field in the RRC signaling, such as pusch-AggregationFactor signaling; the second way to configure the number of repeated transmissions is to communicate with TDRA. (Time domain resource assignment) joint coding.

In an embodiment, the first mode means that when the indicator field of the first mode is not configured, it means that the number of repeated transmissions is equal to 1. When the indicator field of the first mode is configured, according to the value indicated by the indicator field, Get the number of repeated transmissions. Wherein, when the indicator field exists, the value indicated by the indicator field is an integer greater than one.

In an embodiment, the second method refers to adding a setting item to the TDRA information, for example, adding a column to the TDRA information table, the column indicating the number of repeated transmissions.

Table 1 TDRA information table

Table 1 is a TDRA information table. As shown in Table 1, the content of the TDRA information table may include time domain resource index, mapping type (Mapping type), K2, SLIV, and number of repetitions. The content of TDRA information is configured by RRC, and the time domain resources of a row are indicated by high-level signaling or dynamic control information. Among them, K2 refers to the time domain offset (slot offset), which is the scheduling delay between the terminal receiving the DCI and sending the PUSCH. SLIV refers to the Start and Length Indicator Value (SLIV) of the start symbol and the number of time domain duration symbols. The number of repeated transmissions can be an integer greater than or equal to 1.

For the number of repeated transmissions configured in these two ways, the terminal can determine the number of repeated transmissions (number of repetitions) through at least one of the following methods (methods 1-16):

Method 1: In the case that all rows in the column where the number of repetitions are indicated in the TDRA information of the second mode are 1, the number of repetitions is determined according to the first mode.

Method 2: In the case where at least one row in the column of the number of repetitions in the TDRA information of the second mode indicates greater than 1, the number of repetitions is obtained according to the second method.

Method 3: In the case where the number of repetitions is indicated as 1 in the TDRA information of the second method for scheduling the DCI notification of the PUSCH, the number of repetitions is obtained according to the first method.

Method 4: In the case where the number of repetitions indicates that the number of repetitions is greater than 1, in the TDRA information of the second method for scheduling the DCI notification of the PUSCH, the number of repetitions is obtained according to the second method.

Method 5: In the case that the column of the number of repetitions in the TDRA information of the second method is not configured, the number of repetitions is obtained according to the first method.

Method 6: In a case where the TDRA information of the second manner including the number of repetitions is configured, the number of repetitions is obtained according to the second manner.

Method 7: In a case where the TDRA information of the second manner including the number of repetitions is not configured, the number of repetitions is obtained according to the first manner.

Method 8: In the case that the column of the number of repetitions is configured in the TDRA information of the second mode, the number of repetitions is obtained according to the second method.

In the case that the column of the number of repetitions is not configured in the TDRA information of the second way, the number of repetitions is obtained according to the first way.

Method 9: In the case of TDRA information configuration including the number of repetitions, the number of repetitions is determined according to the number of repetitions in the table.

In the case that the TDRA information including the number of repetitions is not configured, the number of repetitions is determined according to an indication field of the RRC signaling.

In an embodiment, when the indication field is not configured, it means that the number of repetitions is equal to one.

Method 10: In the case where the indication field of the first manner exists, the number of repetitions is obtained according to the indication field.

Method 11: In the case that the indication field of the first method does not exist, and the column of the number of repetitions is configured in the TDRA information of the second method, the number of repetitions is obtained according to the second method.

Method 12: In the case that the indication field of the first mode does not exist, and the column of the number of repetitions is not configured in the TDRA information of the second mode, the number of repetitions is 1.

Method 13: In the case that the indication field of the first manner does not exist and the TDRA information including the number of repetitions is not configured, the number of repetitions is 1.

Method 14: Introduce RRC 1-bit (bit) signaling to indicate. For example, 1 bit represents two logical values, the first logical value represents that the number of repetitions is obtained according to the first way; the second logical value represents that the number of repetitions is obtained according to the second way.

Method 15: When the PUSCH mapping type is indicated as the first transmission type in the TDRA information, it means that the number of repetitions is obtained according to the first method; when the PUSCH mapping type is indicated as the second transmission type in the TDRA information, it means repetition The number of times is obtained according to the second method. The first transmission type refers to type A (PUSCH mapping type A), and the second transmission type refers to type B (PUSCH mapping type B), and vice versa. Among them, the main difference between typeA and typeB is that the initial symbol position and time domain duration have different requirements.

Method 16: In the case where K2 is indicated as K2=0 in the TDRA information, the number of repetitions is obtained according to the second method. In the case where K2 is an integer greater than 0, the number of repetitions is obtained according to the first method. The opposite is also possible.

In an embodiment, K2 refers to a time domain offset (slot offset), which is the length of time between the terminal receiving DCI and sending PUSCH.

The PUSCH mentioned in the above embodiment is only an example. The actual information transmission can also be carried on the PDSCH, or carried on the physical random access channel (Physical Random-Access Channel, PRACH), physical uplink control channel (Physical Uplink Control Channel). , PUCCH) and other physical channels.

In an embodiment, the information to be transmitted corresponds to the second transmission type, and the configuration information corresponds to the second mode or the third mode;

The second method includes: indicating the number of repeated transmissions according to a setting item in the TDRA information; the third method includes: indicating the number of repeated transmissions according to a second indication field of RRC signaling.

In this embodiment, the second transmission type refers to the situation that the repeated transmission of the physical transmission channel corresponds to the physical transmission channel for dispatching scheduling information through RRC, and it may also be the physical transmission channel for dispatching scheduling information through activating DCI.

In an embodiment, for the second mode or the third mode, the number of repeated transmissions is an integer greater than or equal to 1.

In the case where the setting item for each time domain resource in the TDRA information of the second mode is 1, the number of repeated transmissions is determined by the third mode; there is at least one time in the TDRA information of the second mode When the setting item corresponding to the domain resource is greater than 1, the second method is used to determine the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is equal to 1, it is passed The third method determines the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is greater than 1, the second method determines the number of repeated transmissions; in the second method When the setting item is not configured in the TDRA information, the number of repeated transmissions is determined by the third method; in the case of the second indication field configured in the RRC signaling in the third method, the third method is used Determine the number of repeated transmissions.

In an embodiment, the determining the number of repeated transmissions of the information to be transmitted according to the configuration information includes one of the following:

When the TDRA information of the second method including the setting item is configured, the number of repeated transmissions is determined by the second method; when the TDRA information of the second method including the setting item is not configured, the TDRA information of the second method including the setting item is not configured. The third method determines the number of repeated transmissions.

In the case where the RRC signaling indicates the third logical value, the number of repeated transmissions is determined by the third method; in the case where the RRC signaling indicates the fourth logical value, the number of repeated transmissions is determined by the second method.

In an embodiment, the information to be transmitted is carried on a physical transmission channel; the physical transmission channel includes at least one of PDSCH and PUSCH.

When the PUSCH for sending scheduling information through RRC is repeatedly sent, the network side can configure the number of repeated transmissions in two ways, namely the second way and the third way.

The PUSCH for dispatching scheduling information through RRC can include type 1 PUSCH without scheduling (Type 1 PUSCH tranmission with a configured grant), and the PUSCH sending scheduling information by activating DCI can include type 2 PUSCH (Type 2 PUSCH tranmission with a configured grant). grant).

The third way to configure the number of repeated transmissions is an indication field in the RRC signaling, such as repK signaling; the second way to configure the number of repeated transmissions is to combine with TDRA (Time domain resource assignment) coding.

The indication field of the third mode always exists, and the number of repeated transmissions is obtained according to the value indicated by the indication field. Wherein, the value indicated by the indicator field is an integer greater than or equal to 1.

The second method is the second method described in the first embodiment. I won't repeat it here.

For the number of repeated transmissions configured in these two ways, the terminal can determine the number of repeated transmissions by at least one of the following methods:

Method 1: In the case that all rows in the column where the number of repetitions are indicated in the TDRA information of the second mode are 1, the number of repetitions is obtained according to the third mode.

Method 3: In the case where the number of repetitions indicated in the TDRA information of the second mode notified in the scheduling information of the PUSCH is 1, the number of repetitions is obtained according to the third mode.

Method 4: In the case where the number of repetitions indicated in the TDRA information of the second mode notified in the scheduling information of the PUSCH is greater than 1, the number of repetitions is obtained according to the second mode.

Method 5: In the case that the column of the number of repetitions in the TDRA information of the second method is not configured, the number of repetitions is obtained according to the third method.

Method 6: In the case where the third method is configured in the RRC signaling, the third method is used to determine the number of repeated transmissions.

Method 7: In a case where the TDRA information of the second manner including the number of repetitions is configured, the number of repetitions is obtained according to the second manner.

Method 8: In a case where the TDRA information of the second manner including the number of repetitions is not configured, the number of repetitions is obtained according to the third manner.

Method 9: Introduce RRC 1bit signaling to indicate. For example, 1 bit represents two logical values, the third logical value represents that the number of repetitions is obtained according to the third method; and the fourth logical value represents that the number of repetitions is obtained according to the second method.

Method 10: When the PUSCH mapping type is indicated as the first transmission type in the TDRA information, it means that the number of repetitions is obtained according to the third method; when the PUSCH mapping type is indicated as the second transmission type in the TDRA information, it means repetition The number of times is obtained according to the second method. The first transmission type refers to type A (PUSCH mapping type A), and the second transmission type refers to type B (PUSCH mapping type B), and vice versa. Among them, the main difference between typeA and typeB is that the initial symbol position and time domain duration have different requirements.

Method 11: In the case where K2 is indicated as K2=0 in the TDRA information, the number of repetitions is obtained according to the second method. In the case where K2 is an integer greater than 0, the number of repetitions is obtained according to the third method. The opposite is also possible. K2 refers to the time domain offset (slot offset), which is the length of time between the terminal receiving the DCI and sending the PUSCH.

The PUSCH (Physical Uplink Shared Channel) mentioned in the above embodiments is only an example, and the actual information transmission may also be carried on the PDSCH (Physical Downlink Shared Channel, physical downlink shared channel). Or carried on other physical channels such as PRACH (Physical Random-Access Channel) and PUCCH (Physical Uplink Control Channel).

The embodiment of the present application also provides a method for indicating the number of repeated transmissions to effectively indicate the number of repeated transmissions. Fig. 2 is a flowchart of a method for indicating the number of retransmissions according to an embodiment. The method provided in this embodiment can be applied to a service node. As shown in FIG. 2, the method provided in this embodiment includes step 210 and step 220. For details that are not described in detail in this embodiment, please refer to any of the above embodiments. The configuration information determined by the service node corresponds to the configuration information received by the terminal in any of the above embodiments; the implementation of the service node indicating the number of repeated transmissions is the same as the above embodiment. It corresponds to the way the terminal determines the number of repeated transmissions.

In step 210, configuration information is determined, and the configuration information is used to indicate the number of repeated transmissions of the information to be transmitted.

In step 220, the configuration information is sent.

In an embodiment, the information to be transmitted corresponds to a first transmission type, and the configuration information corresponds to a first mode or a second mode; the first mode includes: a first indication field of radio resource control RRC signaling Used to indicate the number of repeated transmissions. When the first indication field is not configured in the RRC signaling, the number of repeated transmissions is 1; the second method includes: the setting item in the TDRA information is used to indicate the number of repeated transmissions .

In an embodiment, for the first manner, when the first indication field is configured in the RRC signaling, the value indicated by the first indication field is an integer greater than 1.

In an embodiment, the number of repeated transmissions is indicated by at least one of the following:

In the case that the setting item for each time domain resource in the TDRA information in the second mode is 1, the number of repeated transmissions is indicated in the first mode; and there is at least one time in the TDRA information in the second mode. When the setting item corresponding to the domain resource is greater than 1, the second method is used to indicate the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is equal to 1, the The first method indicates the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is greater than 1, the second method indicates the number of repeated transmissions; in the second method If the setting item is not configured in the TDRA information, the number of repeated transmissions is indicated in the first manner.

When the TDRA information of the second method including the setting item is configured, the number of repeated transmissions is indicated by the second method; when the TDRA information of the second method including the setting item is not configured, the TDRA information is passed The first way indicates the number of repeated transmissions. In an embodiment, the number of repeated transmissions is indicated by at least one of the following: in the case where the first indication field is configured in the RRC signaling in the first manner, the number of repeated transmissions is indicated in the first manner; When the first indication field is not configured in the RRC signaling in the first mode, and the setting item is configured in the TDRA information in the second mode, the second mode is used to indicate the number of repeated transmissions; In the case where the first indication field is not configured in the RRC signaling in the first manner, and the setting item is not configured in the TDRA information in the second manner, the number of repeated transmissions is equal to 1; In the case where the first indication field is not configured in the RRC signaling in the first manner, and the TDRA information of the second manner including the setting items is not configured, the number of repeated transmissions is equal to one.

In the case where the RRC signaling indicates the first logical value, the number of repeated transmissions is indicated in the first manner; in the case where the RRC signaling indicates the second logical value, the number of repeated transmissions is indicated in the second manner.

In an embodiment, the information to be transmitted corresponds to the second transmission type, and the configuration information corresponds to the second mode or the third mode; the second mode includes: indicating repeated transmission according to a setting item in the TDRA information The number of times; the third way includes: indicating the number of repeated transmissions according to the second indication field of the RRC signaling.

In an embodiment, for the second mode or the third mode, the number of repeated transmissions is an integer greater than or equal to one.

In the case that the setting item for each time domain resource in the TDRA information of the second mode is 1, the number of repeated transmissions is indicated in the third mode; and there is at least one time in the TDRA information of the second mode. When the setting item corresponding to the domain resource is greater than 1, the second method is used to indicate the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is equal to 1, the The third method indicates the number of repeated transmissions; when the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second method is greater than 1, the second method indicates the number of repeated transmissions; in the second method In the case that the setting item is not configured in the TDRA information, the number of repeated transmissions is indicated by the third method; in the case that the RRC signaling in the third method is configured with the second indication field, the third method is used Indicates the number of repeated transmissions.

When the TDRA information of the second method including the setting item is configured, the number of indicated transmissions is determined by the second method; when the TDRA information of the second method including the setting item is not configured, the The third way is to repeat the number of transmissions.

In the case where the RRC signaling indicates the third logical value, the number of repeated transmissions is indicated in the third manner; in the case where the RRC signaling indicates the fourth logical value, the number of repeated transmissions is indicated in the second manner.

In an embodiment, the serving node can instruct the terminal to send physical channels through two transmission modes. Taking PUSCH as an example, the first transmission mode refers to repeatedly sending PUSCH according to the time slot granularity, thereby realizing time slot aggregation based on dynamic scheduling. (Slot-based Aggregation) or slot-based repetition based on scheduling-free. The first transmission mode means that the terminal uses multiple time slots to repeatedly send TB, and the TB has the same time and frequency in each time slot. Resource allocation: The second transmission mode refers to the repeated transmission of TB once or more than once in the same time slot, or the repeated transmission of the same TB across multiple time slots on consecutively available time slots. In this embodiment, when the TDRA information of the two transmission modes is the same (the two transmission modes correspond to the same TDRA information), the terminal can determine the time domain position corresponding to the time slot for repeated transmission according to different transmission modes .

In an embodiment, when the TDRA information corresponding to the above two transmission modes is the same, for the first transmission mode, the time domain position is based on the start symbol and the indication value of the number of time domain duration symbols (Start and Length Indicator). Value, SLIV) is obtained. Through the analysis of SLIV, the time-domain start symbol (denoted as S) and the number of time-domain duration symbols (denoted as L) for the first repeated transmission of the information to be transmitted can be obtained; for the second transmission Mode, the time domain position is directly obtained according to the time domain start symbol (S) and the time domain duration symbol number (L).

In an embodiment, when the TDRA information corresponding to the above two transmission modes is the same (that is, the two transmission modes use the same structure of the TDRA information table), the terminal determines which way to determine the time domain position according to the following method: When the terminal determines to use the second transmission mode to transmit PUSCH, read the information about S and L in the TDRA information table; when the terminal determines to use the first transmission mode to transmit PUSCH, read the SLIV in the TDRA information table That's it.

Table 2 is the TDRA information table of joint coding. As shown in Table 2, when the terminal determines to use the second transmission mode to send PUSCH, read the columns where S and L in the TDRA information table are located; when the terminal determines to use the first transmission mode to send PUSCH, read Take the column of the SLIV in the TDRA information table to determine the time domain position.

Table 2 Jointly coded TDRA information table

In an embodiment, in a case where the TDRA information corresponding to the above two transmission modes is different (that is, the two transmission modes correspond to different TDRA information tables), the terminal determines the time domain position according to the corresponding TDRA information table.

For example, Table 3 is the first type of TDRA information table, and Table 4 is the second type of TDRA information table. When the terminal determines to use the second transmission mode to transmit PUSCH, obtain the time domain position according to the first type of TDRA information table; when the terminal determines to use the second transmission mode to transmit PUSCH, according to the second type of TDRA information table To get the time domain position.

Table 3 The first TDRA information table

Time domain resources

PUSCH

K2

SLIV

Repeat transmission times

索引index	映射类型Mapping type	To	To	To
11	TypeBTypeB	00	23twenty three	22
......	......	......	......	......

Table 4 The second TDRA information table

In an embodiment, the serving node informs the terminal which transmission mode to use through RRC signaling.

For the case where the terminal is configured to only include the new format (DCI Format 1_2), the S reference starting point in TDRA in the new format introduces a new reference (new reference) when K0=0, that is, it is changed to the PDCCH start symbol ( starting symbol). In this case, according to the SLIV in the TDRA information (where the reference starting point of S is the slot boundary), all possible PDSCH positions can be determined, thereby determining the type1 HARQ-ACK codebook.

In an embodiment, when the terminal is configured to include the first format (such as the new format: DCI Format 1_2) and the traditional format (such as DCI Format 1_1), the semi-static codebook construction method includes one of the following:

Method 1: According to the TDRA information table of Format 1_1 and all actual SLIV PDSCH positions in the TDRA information table of Format 1_2, a unified type 1 hybrid automatic repeat request confirmation codebook (type1 HARQ-ACK codebook) is generated, which is half Static codebook.

Method 2: Generate a semi-static codebook for each format. The PDSCH determined by the TDRA information table of Format 1_1 corresponds to a type 1 HARQ-ACK codebook, and the PDSCH determined by the TDRA information table of Format 1 2 corresponds to a type 1 HARQ-ACK codebook.

Method 3: If there is a column in the TDRA information table that can indicate the priority of the corresponding PDSCH or codebook, in this case, for each item in the TDRA information table of Format 1_1 and the TDRA information table of Format 1_2, different priorities Generate a type1 HARQ-ACK codebook respectively. For example, all first priorities (high priority) correspond to a type1 HARQ-ACK codebook, and all second priorities (low priority) correspond to a type1 HARQ-ACK codebook.

Method 4: Generate a type1 HARQ-ACK codebook for different configurations of Control Resource Set (CORESET) or Search Space (Search Space). For example, if the format of the DCI included in the configuration information of CORESET or search space is different, each format corresponds to a type1 HARQ-ACK codebook.

In the case of introducing a new TDRA information table in the above method, the type1 HARQ-ACK codebook is generated according to the format of the DCI, the priority of each item in the TDRA information table, and the different configurations of CORESET or Search Space, which reduces the type1 HARQ-ACK codebook. Overhead, improve the reliability of uplink transmission.

In the New Radio (NR) system, the bit fields of some downlink control information depend on the configuration of high-level signaling. For multiple-input multiple-output (MIMO) related bit fields, especially the bit fields in the DCI for scheduling PUSCH transmission, it depends on the MIMO transmission mode configured by high-level signaling, for example, based on codebook transmission The bit field corresponding to non-codebook-based transmission may be different. In the case of high-level signaling configuration, the terminal does not need to dynamically support different MIMO transmission modes, for example, it does not need to dynamically support codebook-based transmission and non-codebook-based transmission. With the continuous optimization of the NR system, when the new DCI format is supported, the relevant bit fields of the MIMO function are still configured according to the old high-level signaling, which will cause the terminal to be unable to support different MIMO transmission methods and add a new high-level Signaling configuration, for example, PUSCH scheduled in different DCI formats corresponds to codebook-based transmission and non-codebook-based transmission, which can improve terminal processing capabilities, but also increase terminal complexity, for example, the DCI Format 0_1 sounding reference signal in the NR system The (Sounding Reference Signal, SRS) resource indicator bit field needs to be increased to determine the size of the field using four high-level parameters. This embodiment provides a method for configuring SRS resources or resource sets to reduce terminal complexity.

R16 NR introduces a new DCI format, and it also has an SRS resource indicator field. In this case, if it is also a new DCI format (the following embodiment takes Format 0_2 as an example for illustration, the same applies to other new DCI formats The introduction of new high-level parameter configurations in the SRS resource indication field in) will cause the PUSCH scheduled with Format 0_1 and the PUSCH scheduled with Format 0_2 to use codebook-based transmission and non-codebook-based transmission, respectively, resulting in increased terminal complexity. In this embodiment, new RRC parameters (such as SRS-Resource Set) are used for R16, and SRS resources or resource sets are configured by the following method:

Method 1: The configuration value of the new RRC parameter is a subset of the configuration value set of the corresponding parameter in R15.

Method 2: The sum of the new RRC parameters and the corresponding parameters in R15 does not exceed the terminal (User Equipment, UE) capabilities (such as SRS resources supported by the UE), which can be the rs-ResourceIdList in the SRS-Resource Set (SRS resource set) (Resources in the SRS resource collection) and usage (the use of the SRS resource collection). SRS-ResourceSet in R15 and SRS-Resource Set-For DCI in R16 Format0_2 (the new parameters introduced by R16 to configure the SRS resource set, including rs-ResourceIdList and usage) The sum of the corresponding parameters does not exceed the SRS resources supported by the terminal Quantity capacity.

In one embodiment, the RRC configuration parameters related to data transmission (such as txConfig parameters) of R16 can be directly reused R15 parameters (that is, no new RRC parameters are used); the largest multiple-input and multiple-output layer (maxMIMO-Layers) is used The new RRC parameter or directly reuse the R15 parameter. In the case of using the new RRC parameter, the value of the new RRC parameter configuration is not greater than the value of the R15 parameter.

By configuring the SRS resource or resource set through the above method, the terminal does not need to dynamically support codebook-based and non-codebook-based transmission, thereby reducing UE complexity and reducing the size of the bit field.

In the case of supporting the new DCI format, a new high-level signaling configuration is introduced for the relevant bit fields of the MIMO function. To avoid the increase in terminal complexity, this embodiment also provides a medium access control layer control unit (Medium Access Control Control). Element, MAC CE) activation method. In the bit field of DCI Format 0_1 in the NR system, when tci-PresentInDCI (Transmission configuration indication, TCI, transmission configuration indication) is not enabled, the field is 0bit, and in other cases, the field is 3bit. 3 bits indicate one of at most 8 transmission configuration indication (Transmission Configuration Indication, TCI) states activated by the MAC CE. When R16 NR introduces a new DCI format (using Format 1_2 as an example, it is also applicable to other new DCI formats) and has a TCI indicator field, if the TCI indicator field in DCI Format 1_2 supports 1 or 2 bits, then MAC CE The activation method includes one of the following:

Method 1: Use the same MAC and CE activation for the TCI fields in Format 1_1 and Format 1_2. In this case, Format 1_1 also supports 1 or 2 bits. For example, when the MAC CE activates at most 4 TCI states, the TCI field is 2 bits in both Format 1_1 and Format 1_2.

Method 2: Use an independent MAC CE to activate the TCI status of different NR Release versions (NR R15 and NR R16) or different formats (Format 1_1 and Format 1_2). Add 1 bit before MAC CE to distinguish which NR Release version (NR R15 and NR R16) or which format (Format 1_1 and Format 1_2) the activation TCI states are for the current indication; or send activation of different NRs at the same time Release version (NR R15 and NR R16) or TCI states of different formats (Format 1_1 and Format 1_2), using two independent relative positions to determine (for example, two adjacent positions, the bit position is distinguished between high and low) bit field indication . The total number of TCI states of different NR Release versions (NR R15 and NR R16) or different formats (Format 1_1 and Format 1_2) that are independently activated does not exceed 8.

Method 3: Configure the field size of the TCI field in Format 1_2 (assumed to be m bits) through high-level parameters, and determine the TCI states of different formats (Format 1_1 and Format 1_2) respectively through preset rules. The preset rules include one of the following: 1) The TCI states activated by MAC CE are TCI states in Format 1_1, and the first 2 ^m TCI states are TCI states in Format 1_2; 2) The number of TCI states activated in MAC CE is greater than In ^{the case of 2 m} , it means that the TCI states in Format 1_1 are activated; when the number of TCI states activated by MAC CE is less than or equal to 2 ^m , it means that the TCI states in Format 1_2 are activated. In the case of m=3, it means that the TCI states in Format 1_2 and the TCI states in Format 1_2 are activated at the same time.

Method 4: According to the X value of at most X TCI states activated by the MAC CE, it is determined whether the TCI states used for activation are TCI states in Format 1_1 or the TCI states used for activation are TCI states in Format 1_2. When X is less than or equal to 4, the TCI states used for activation are determined to be the TCI states in Format 1_2; when X is greater than 4 and X is less than or equal to 8, the TCI states used for activation are determined to be the TCI states in Format 1_1. TCI states.

Manner 5: Determine whether the TCI states used for activation are TCI states in Format 1_1 or the TCI states used for activation are TCI states in Format 1_2 according to the distinguishing identifier in the MAC CE. For example, in MAC CE, different LCID (Logical Channel Identifier, logical channel identifier) values or 1-bit identifiers are used to distinguish whether the MAC CE is used for activation TCI states as TCI states in Format 1_1 or TCI states for activation. TCI states in Format 1_2.

Optionally, similar to Format 1_1, for Format 1_2, use RRC signaling (tci-PresentInDCI-ForFormat1_2) to determine whether the TCI field is enabled. When tci-PresentInDCI-ForFormat1_2 is not enabled, this field is 0bit; When tci-PresentInDCI-ForFormat1_2 is enabled, this field is 3bit or 2bit or 1bit.

In the foregoing embodiment, by determining TCI fields for different DCI formats, it is possible to flexibly support different formats with different numbers of TCI states, improve the flexibility of indication, and avoid increasing the complexity of the UE.

In an embodiment, the discussion of the scenario in which the UE processes the PDSCH includes the following scenarios:

Scenario 1: Two PDSCHs overlap in the time domain, and the two PDSCHs correspond to the same minimum processing timeline capability.

Scenario 2: Two PDSCHs correspond to different minimum processing time capabilities.

The UE has two processing capabilities:

Processing capability 1: The UE can process two PDSCHs with overlapping time domains, and/or can process two PDSCHs with different minimum processing times (including two cases of time domain overlap and time domain non-overlap).

Processing capability 2: The UE always processes the PDSCH with high priority, and processes the PDSCH with low priority when certain conditions are met, and skips the processing of the PDSCH with low priority in other cases.

The time domain overlap includes the following two scenarios: time domain overlap, frequency domain does not overlap; time and frequency domains overlap.

When there are more than two PDSCHs, how to utilize the processing capability of the UE to process the PDSCH is a problem to be solved urgently.

One solution mechanism is to introduce a priority mechanism, which instructs the UE to process the PDSCH through the priority.

The implementation form of the priority mechanism includes one of the following:

Implementation form 1: The priority is determined according to the time sequence of the scheduling, and the priority of the PDSCH scheduled later is higher than the priority of the PDSCH scheduled earlier.

Implementation form 2: Introduce explicit signaling instructions.

For implementation form 1, it is necessary to determine one or more post-scheduled PDSCHs with high priority that can be processed according to the capabilities of the UE.

For implementation form 2, 1-bit signaling can be introduced in the downlink control information (DCI) to indicate the priority. Among them, 1 bit indicates two logical values.

In an embodiment, the logical value of the priority indication includes the following two ways:

Logical value indication method 1:

When the logic value of the priority indicator of the DCI corresponding to the current PDSCH is different from the logic value of the priority indicator of the DCI corresponding to the current PDSCH, the terminal is instructed to give priority to processing the current PDSCH, and for the previous PDSCH, it is determined according to the capabilities of the terminal Whether to deal with it.

When the logic value of the priority indicator of the DCI corresponding to the current PDSCH is the same as the logic value of the priority indicator of the DCI corresponding to the current PDSCH, it is stipulated that:

When both are the first logical value, the priority of the two PDSCHs is the same, or the priority of the current scheduled PDSCH is lower than the previous PDSCH; when both are the second logical value, the priority of the two PDSCHs is the same, or the priority of the current scheduling The priority of the PDSCH is higher than the previous PDSCH.

Logic value indication mode 2:

When the priority indication of the DCI corresponding to the previous PDSCH is the first logical value:

The priority of the DCI corresponding to the current PDSCH indicates the first logical value: it indicates that the priority of the currently scheduled PDSCH is the same as the priority of the previous PDSCH or is lower than the priority of the previous PDSCH; the priority of the DCI corresponding to the current PDSCH indicates the second Logical value: indicates that the priority of the currently scheduled PDSCH is higher than the priority of the previous PDSCH; when the priority of the DCI corresponding to the previous PDSCH is indicated as the second logical value: the priority of the DCI corresponding to the current PDSCH indicates the first logical value : Indicates that the priority of the currently scheduled PDSCH is the same as the priority of the previous PDSCH, or is lower than the priority of the previous PDSCH; the status of this bit of the current DCI is the second logical value: Indicates that the priority of the current scheduled PDSCH is the same as the previous DCI The priority of the scheduled PDSCH is the same or higher than the priority of the previous PDSCH.

In an embodiment, the first logical value corresponds to "0" and the second logical value corresponds to "1", or vice versa, as long as it is agreed upon by both the base station and the terminal. For ease of description, the first logical value in the following embodiments corresponds to "0", and the second logical value corresponds to "1".

In an embodiment, for implementation form 2 (including two indication methods), when the priority indicator of the DCI corresponding to the current PDSCH is 0, and when the priority indicator of the current DCI is 0, it indicates the currently scheduled PDSCH The priority of the PDSCH is lower than or the same as that of the previous PDSCH. In this case, for a UE with UE processing capability 2, its processing operation can be:

As the implementation behavior of the UE, no provisions are made; the currently scheduled PDSCH is discarded; the previous and currently scheduled PDSCH are processed to the best of the UE's ability; the UE does not expect this scheduling situation to occur.

In an embodiment, for the indication mode 2 of the realization form 2, when the priority indication of the current DCI is 1, and the priority indication of the current DCI is 0, it means that the priority of the currently scheduled PDSCH is higher than that of the previous schedule. Low, or the same. In this case, for a UE with UE capability 2, its processing operations can be:

As the implementation behavior of the UE, no provisions are made; the currently scheduled PDSCH is discarded; the UE does not expect this scheduling situation to occur.

The explicit signaling of implementation form 2 is configurable. If the signaling is not configured, implementation form 1 is adopted by default. If this signaling is configured, the priority of the PDSCH is determined according to the foregoing implementation form 2.

The following uses specific examples to illustrate the implementation of the two priority levels for UEs with different processing capabilities.

Example 1: [Processing capability 2+implementation form 1]

FIG. 3 is a schematic diagram of determining the priority of PDSCH based on processing capability 2 and implementation form 1 provided by an embodiment. As shown in Figure 3, for a UE with processing capability 2, when the priority adopts implementation form 1, the UE determines that the last scheduled PDSCH has the highest priority according to the scheduling sequence, so the UE can always process the last scheduled PDSCH , And the previous PDSCH that overlaps with the time domain will be discarded.

In Figure 3, since PDSCH1 and PDSCH2 overlap in the time domain, PDSCH1 is scheduled first, and PDSCH2 is scheduled later. According to the priority implementation form 1, the UE will discard PDSCH1, and then PDSCH2 and PDSCH3 also overlap in time domain. According to priority form 1, the UE will discard PDSCH2, and only keep the processing of PDSCH3.

Example 2: [Processing capability 1+implementation form 1]

FIG. 4 is a schematic diagram of determining the priority of PDSCH based on processing capability 1 and implementation form 1 provided by an embodiment. As shown in Figure 4, for a UE with processing capability 1, when the priority adopts implementation form 1, the UE determines that the last scheduled two PDSCHs have the highest priority according to the scheduling sequence, and the previous one has the highest priority. PDSCH will be discarded.

In Figure 4, because the time domains of PDSCH1 and PDSCH2 overlap, and the time domains of PDSCH2 and PDSCH3 overlap, since the UE is a UE with processing capability 1, it can handle two overlapping PDSCHs. Therefore, according to the priority implementation form 1, the UE According to the scheduling sequence, it is determined that the last scheduled two PDSCH2 and PDSCH3 have the highest priority, and the UE processes these two PDSCHs and discards PDSCH1.

Example 3: [Processing capability 2+implementation form 2+instruction method 1]

FIG. 5 is a schematic diagram of determining the priority of PDSCH based on processing capability 2, implementation form 1, and indication method 1, provided by an embodiment. As shown in Figure 5, for a UE with processing capability 2, when the priority is used in the indication mode 1 of implementation form 2, the signaling indication is 0 when PDSCH1 is scheduled, and when PDSCH2 is scheduled later, because it is in the time domain It will conflict with PDSCH1, so the signaling is set to 1, (turned 0->1) instructing the UE to process PDSCH2 when PDSCH1 and PDSCH2 conflict in time domain, and then send PDSCH3 again, and PDSCH3 will also interact with PDSCH2 If there is overlap, then set the signaling to be reversed 1->0, instructing the UE to process PDSCH3 when PDSCH2 and PDSCH3 collide in the time domain.

In an embodiment, in the case of implementing the indication method 1 of the form 2, it is also possible to process the PDSCH scheduled first and the PDSCH scheduled after discarding.

FIG. 6 is another schematic diagram of determining the priority of PDSCH based on processing capability 2, implementation form 1, and indication method 1, provided by an embodiment. As shown in Figure 6, when PDSCH1 is scheduled, the signaling is set to 0, and when PDSCH2 is scheduled, the signaling is set to 0, which means that the priority of PDSCH2 is the same as or lower than that of PDSCH1. When one of the two is to be discarded, the one with the lower priority is discarded; when scheduling PDSCH3, the signaling can be set to 1. Because of the inversion, it means that when the PDSCH3 and the previous PDSCH2 overlap in time domain, The UE will process PDSCH3 and discard PDSCH2. At this time, since PDSCH1 and PDSCH3 have no time-domain conflict, the UE will process PDSCH1 and PDSCH3 at the same time.

For the same scenario, if the priority adopts implementation form 1, regardless of whether there is a conflict between PDSCH1 and PDSCH3, since PDSCH1 is scheduled first, it will always be discarded first. However, implementation form 2 is used to provide a mechanism that can process PDSCH1 and PDSCH3 at the same time (as shown in Figure 6).

FIG. 7 is another schematic diagram of determining the priority of PDSCH based on processing capability 2, implementation form 1, and indication manner 1, provided by an embodiment. If PDSCH1 and PDSCH3 overlap, and the indication of the explicit signaling of PDSCH3 is flipped relative to the indication of PDSCH1, the UE will also only process PDSCH3 and discard PDSCH1 (as shown in FIG. 7).

In an embodiment, in the case of using the indication mode 1 of the implementation form 2, for the UE of capability 2, the UE always expects that the priority indication of the current DCI will always be reversed, thereby simplifying and clarifying the behavior of the UE.

Example 4: [Processing capability 1+implementation form 2+instruction method 1]

FIG. 8 is a schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 1, provided by an embodiment. As shown in Figure 8, for a UE with processing capability 1, when the priority adopts the indication mode 1 of implementation form 2, when PDSCH1 is scheduled, the signaling indication is 1, and when PDSCH2 is scheduled later, although it is in the time domain Conflicts with PDSCH1, but a UE with processing capability 2 can process two PDSCHs at the same time, so the signaling is set to 1, indicating that the priority of PDSCH2 is the same as or higher than the priority of PDSCH1. When one of the two is to be discarded In the case of low priority (that is, PDSCH1); then, PDSCH3 will be sent again, and PDSCH3 will also overlap with PDSCH. Considering that the UE can only handle two overlapping PDSCHs at most, set the signal Let the flip 1->0 occur, instruct the UE to process PDSCH3 when PDSCH2 and PDSCH3 collide in the time domain. When the previous PDSCH is to be discarded, the priority of PDSCH1 of PDSCH2 is high, so PDSCH1 is finally discarded, and the process is PDSCH2 and PDSCH3.

FIG. 9 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 1, provided by an embodiment. As shown in Figure 9, for a UE with a processing capability 1, when the priority adopts the indication mode 1 of the realization form 2, when the PDSCH1 is scheduled, the signaling indication is 0, and when the PDSCH2 is scheduled later, although it is in the time domain Conflicts with PDSCH1, but a UE with processing capability 2 can process two PDSCHs at the same time, so the signaling is set to 0, indicating that the priority of PDSCH2 is the same as or lower than that of PDSCH1. When one of the two is to be discarded In the case of low priority (that is, PDSCH2); then, PDSCH3 will be sent again, and PDSCH3 will also overlap with PDSCH2. Considering that the UE can only handle two overlapping PDSCHs at most, set the signal Let the flip 1->0 occur, instruct the UE to process PDSCH3 when PDSCH2 and PDSCH3 collide in the time domain. When the previous PDSCH is to be discarded, the priority of PDSCH2 of PDSCH1 is high, so PDSCH2 is finally discarded, and the process is PDSCH1 and PDSCH3.

In the above example, implementation form 2 introduces additional signaling overhead compared to implementation form 1, but it can be more flexible, because the priority of the previous scheduling of implementation form 1 is definitely lower than that of the subsequent scheduling, so it cannot always be processed first. Implementation form 2 provides the possibility that the priority of the previous scheduling is higher than the priority of the subsequent scheduling.

Example 5: [Processing capability 2+Realization form 2+Instruction form 2]

FIG. 10 is a schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication method 1, provided by an embodiment. As shown in Figure 10, for a UE with processing capability 2, when the priority is in the indication mode 2 of realization form 2, the signaling indication is 0 when PDSCH1 is scheduled, and when PDSCH2 is scheduled later, because it is in the time domain It will conflict with PDSCH1, so the signaling is set to 1, indicating that the priority of PDSCH2 is higher than that of PDSCH1. When the time domain conflicts between PDSCH1 and PDSCH2, the UE should prioritize PDSCH2. Then, PDSCH3 is to be sent again, and PDSCH3 also overlaps with PDSCH2, so the signaling is set to 1, indicating that the priority of PDSCH3 is higher or the same as that of PDSCH2. For a UE with a processing capability of 2, when a time domain conflict occurs between PDSCH2 and PDSCH3 and the UE can only process one of them, PDSCH3 is processed.

FIG. 11 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 1, provided by an embodiment. In the case of implementing the instruction method 2 of the form 2, it is also possible to process the PDSCH scheduled first and discard the PDSCH scheduled afterwards. As shown in Figure 11, when PDSCH1 is scheduled, the signaling is set to 0, and when PDSCH2 is scheduled, the signaling is set to 0, which means that the priority of PDSCH2 is the same as or lower than that of PDSCH1. When one of the two is to be discarded, the one with the lower priority is discarded; when scheduling PDSCH3, the signaling can be set to 1, which means that when the PDSCH3 overlaps with the previous PDSCH2, the UE will process PDSCH3, and Discard PDSCH2. At this time, since PDSCH1 and PDSCH3 have no time-domain conflict, the UE will process PDSCH1 and PDSCH3 at the same time (as shown in FIG. 11).

FIG. 12 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 1, provided by an embodiment. If PDSCH1 and PDSCH3 overlap, and the explicit signaling of PDSCH3 is 1, and PDSCH1 is 0, the UE will also only process PDSCH3 and discard PDSCH1 (as shown in FIG. 12).

In the above example, in the case of using the indication mode 2 of the realization form 2, for the UE of capability 2, the UE always expects the value of the priority indication of the DCI scheduled later to be 1, so as to simplify and clarify the behavior of the UE.

Example 6: [Processing capability 1+implementation form 2+instruction method 2]

FIG. 13 is a schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 2, provided by an embodiment. As shown in Figure 13, for a UE with processing capability 1, when the priority adopts the indication mode 2 of implementation form 2, the signaling indication is 0 when PDSCH1 is scheduled, and when PDSCH2 is scheduled later, although it is in the time domain Conflicts with PDSCH1, but a UE with processing capability 2 can process two PDSCHs at the same time, so the signaling is set to 1, indicating that the priority of PDSCH2 is the same as or higher than the priority of PDSCH1. When one of the two is to be discarded In the case of low priority (that is, PDSCH1); then, PDSCH3 will be sent again, and PDSCH3 will also overlap with PDSCH. Considering that the UE can only handle two overlapping PDSCHs at most, set the signal Let it be 1, instruct the UE to process PDSCH3 when PDSCH2 and PDSCH3 conflict in time domain. Since the current UE is a UE with processing capability 2, the UE can process PDSCH2 and PDSCH3 at the same time.

FIG. 14 is another schematic diagram of determining the priority of PDSCH based on processing capability 1, implementation form 2, and indication manner 2, provided by an embodiment. As shown in Figure 14, for a UE with a processing capability 1, when the priority adopts the indication mode 2 of implementation form 2, the signaling indication is 0 when PDSCH1 is scheduled, and when PDSCH2 is scheduled later, although it is in the time domain Conflicts with PDSCH1, but a UE with processing capability 2 can process two PDSCHs at the same time, so the signaling is set to 0, indicating that the priority of PDSCH2 is the same as or lower than that of PDSCH1. When one of the two is to be discarded In the case of low priority (that is, PDSCH2); then, PDSCH3 will be sent again, and PDSCH3 will also overlap with PDSCH2. Considering that the UE can only handle two overlapping PDSCHs at most, set the signal Let it be 1, instruct the UE to process PDSCH3 when PDSCH2 and PDSCH3 collide in the time domain. When the previous PDSCH is to be discarded, the priority of PDSCH2 of PDSCH1 is high, so PDSCH2 is finally discarded, and PDSCH1 and PDSCH3 are processed.

The foregoing embodiments are directed to PDSCHs with overlapping time domains, and are also applicable to scenarios where there are conflicts in the time and frequency domains. In addition, when different PDSCHs correspond to different minimum processing time capabilities (Minimum Processing Timeline Capability), the method is also applicable.

In this embodiment, a parameter is added to the high-level configuration parameters of the time domain resource allocation of the PDSCH, so that when different PDSCHs can be processed by the UE with different minimum processing times, it indicates that a PDSCH needs to be processed. The minimum processing time used.

In one embodiment, an indication of the minimum processing time is added to the time domain resource allocation of PDSCH. In this embodiment, taking the case of considering two different minimum processing times as an example, the time domain resource allocation of PDSCH is A parameter is added to the high-level configuration parameters.

In one embodiment, when the serving node configures the PDSCH time-domain resource allocation parameters, it can determine a reasonable processing time for the UE to process the PDSCH through a reasonable configuration. For example, for a shorter PDSCH resource allocation, you can configure a shorter PDSCH resource allocation. Small processing time (Capability2), and for longer PDSCH allocation, you can configure a larger processing time (Capability1). By using parameters to indicate the processing time, the service node can have greater flexibility.

This embodiment also provides a method for determining the priority of data scheduled by DCI. In the NR system, a priority indication field is introduced in the DCI format to indicate the priority corresponding to the data scheduled by the DCI. For the case where the scheduled data is downlink data, it can also indicate the HARQ- corresponding to the downlink data. The priority of ACK. In addition, the priority indication field may be configured by RRC signaling whether the priority indication field exists in the DCI format. Take Fallback DCI as an example. Fallback DCI will schedule data, but the number of bits in the information field in Fallback DCI will not depend on the configuration of RRC signaling, because the number of bits in Fallback DCI is always fixed, so avoid The impact of RRC signaling ambiguity on the blind detection of DCI by the UE. Therefore, the aforementioned priority indication field cannot be added to Fallback DCI, because it is based on whether the RRC configuration has the priority indication field.

This embodiment also provides a method for determining the priority of data scheduled by Fallback DCI, and a method for determining the priority of HARQ-ACK corresponding to the data, where Fallback DCI includes DCI format 1-0 and DCI format 0-0 , The priority of the data scheduled by FallbackDCI in Method 1 and/or Method 2.

Method 1: Add a column to the time domain resource allocation table to indicate the priority of time domain resource allocation. That is, the priority of the data in the time domain resource allocation is obtained from the newly added priority indicator column. The priority indication here can be divided into multiple level indications.

When the serving node configures the time domain resource allocation (TDRA) table for the UE, a new column is added to the table, and this column is used to describe the priority corresponding to the time domain resource allocation of each row. In this case, when Fallback DCI schedules data, a row of time domain resource allocation index is selected, and the priority of data transmission in the row of time domain resource allocation is determined to be used for the priority corresponding to the row.

For example, Table 5 is a time domain resource allocation information table. As shown in Table 5, each row corresponds to a time domain resource allocation. According to the above method, add a column to the table, such as priority indication, using 1 to indicate high priority and 0 to indicate low priority. In this way, when the serving node uses Fallback DCI (such as DCI format 1-0) to schedule a PDSCH, the serving node selects a row from the table, and transmits the row index as time domain resource allocation information to the UE in the DCI format 1-0. After receiving the DCI format 1-0, the UE obtains the row index information therein, and then obtains the corresponding priority of the PDSCH time domain resource allocation of the row according to the PDSCH time domain resource allocation table configured by the serving node, and finally obtains the DCI format 1 -0 Priority of scheduled data (PDSCH). This priority is also applicable to the HARQ-ACK of the PDSCH.

The serving node and the UE agree that for non-Fallback DCI, for example, the priority of the PDSCH scheduled from Table 4 in DCI format 1-1, the following methods can be used for processing:

If non-Fallback DCI, such as DCI format 1-1 or DCI format 1-2, a row of PDSCH is scheduled from the table, and the DCI has a priority indicator field, then the priority indicator field in the DCI is used The priority of is subject to the priority of the PDSCH and is applicable to the HARQ-ACK of the PDSCH; or, for the non-Fallback DCI scheduled a row of PDSCH from the table, always follow the corresponding priority indication of the row in the table , As the priority of the PDSCH, and applicable to the HARQ-ACK of the PDSCH. If there is no priority indication field in the DCI, the priority configured in the table shall prevail as the priority of the PDSCH, and it is applicable to the HARQ-ACK of the PDSCH.

Table 5 Time domain resource allocation information table

For another example, Table 6 is another time domain resource allocation information table. As shown in Table 6, where each row corresponds to a time domain resource allocation. According to the above method, add a column to the table, such as priority indication, using 1 to indicate high priority and 0 to indicate low priority. In this way, when the serving node uses Fallback DCI (such as DCI format 0-0) to schedule a PUSCH, the serving node selects a row from the table, and transmits the row index as time domain resource allocation information to the UE in the DCI format 0-0. After receiving the DCI format 0-0, the UE obtains the row index information therein, and then obtains the corresponding priority of the PUSCH time domain resource allocation of the row according to the PUSCH time domain resource allocation table configured by the serving node, and finally obtains the DCI format 0 -0 Priority of scheduled data (PUSCH).

The serving node and the terminal agree that for non-Fallback DCI, such as DCI format 0-1, the priority of the PUSCH scheduled from this table can be processed in the following way: If non-Fallback DCI, such as DCI format 0-1 or DCI format 0-2, a row of PUSCH is scheduled from the table, and the DCI has a priority indication field, then the priority in the priority indication field in the DCI shall prevail as the priority of the PUSCH; or, for The non-Fallback DCI schedules a row of PUSCH from the table, and always uses the corresponding priority indication of the row in the table as the priority of the PUSCH. If there is no priority indication field in the DCI, the priority configured in the table shall prevail as the priority of the PUSCH.

Table 6 Time domain resource allocation information table

Method 2: The serving node and the UE agree that the data scheduled by Fallback DCI always has a high or low priority, that is, it has a set priority.

In an embodiment, the foregoing method 1 and method 2 may be merged. In this case, the DCI can be Fallback DCI or non-Fallback DCI. For example, in method 1, if the priority indication in the time domain resource allocation table is not configured or only the priority corresponding to part of the row index is not configured, the scheduled time domain resource allocation is not configured in the above table. When the priority is selected, the serving node and the UE determine the priority of the time domain resource allocation according to Method 2, or the serving node and the UE agree that the priority of the time domain resource allocation is low or high.

In an embodiment, the serving node and the UE agree that in the process of constructing a high-priority and/or low-priority semi-static HARQ-ACK codebook by the UE, the priority in the PDSCH time domain resource allocation table may also be used. Indicate, determine the corresponding HARQ-ACK priority for each scheduled PDSCH, so that the HARQ-ACK of each scheduled PDSCH belongs to the corresponding high or low priority semi-static HARQ-ACK codebook in.

In the case that the Redundancy Rersion (RV) field is configured as 0 bit or 1 bit, this embodiment provides a method for determining RV, so as to realize the situation where the PDSCH is used for dynamic scheduling and the repetition factor is configured, or When semi-persistent scheduling (SPS) PDSCH transmission is activated and a repetition factor is configured, the RV is determined for each transmission. This embodiment only uses PDSCH as an example for description. For a dynamically scheduled PUSCH with a repetition factor configured, or a configured grant (CG) PUSCH transmission is activated and a repetition factor is configured, how to use the RV version for each transmission It also needs to be determined that the method is equally applicable. The repetition factor in this embodiment can be understood as the number of repeated transmissions.

In related technologies, the RV field in the DCI format is always 2 bits and does not need to be configured. When semi-static PDSCH transmission is configured and the repetition factor is configured, or when the PDSCH is dynamically scheduled and the repetition factor is configured, according to the RV indication in the DCI (for half The static PDSCH is to activate the RV indication in the DCI). Table 7 shows the RV corresponding to each transmission in the repeated transmission of the PDSCH. As shown in Table 7, the repetition factor is configured as K, and each transmission index n is n=0,1,...,K-1.

Table 7 RV corresponding to each transmission in PDSCH repeated transmission

For the RV field configured as 0 bit, only RV0 is used; for the 1 bit RV field, RV0 and RV3 are dynamically indicated. However, when the repetition factor is configured and the RV field is configured as 0 bit or 1 bit, the RV used for each transmission in the repeated transmission needs to be determined.

In this embodiment, when the RV field is configured as 0 bit and the repetition factor is configured, the method for determining the RV includes one of the following:

Method 1: Use RV0 only, and use RV0 for every transmission. Table 8 shows the RV corresponding to each transmission in the repeated transmission of PDSCH in Method 1.

Table 8 RV corresponding to each transmission in the repeated transmission of PDSCH in Method 1

Method 2: Use a predefined RV cycle. Table 9 shows the RV corresponding to each transmission in the repeated transmission of PDSCH in Method 2. As shown in Table 9, the predefined RV cycle is shown in any row in Table 7.

Table 9 RV corresponding to each transmission in repeated transmission of PDSCH in method 2

When the RV domain is configured as 1 bit and the repetition factor is configured, the method for determining RV includes one of the following:

Method A: Use a predefined RV cycle, and the set of candidate RV values is {0,1,2,3}. Table 10-12 shows the RV corresponding to each transmission in the repeated transmission of PDSCH in Method A. The predefined RV cycle is shown in Table 10-12, or a combination of any two rows in Table 9.

Table 10: RV corresponding to each transmission in repeated transmission of PDSCH in method A

Table 11 RV corresponding to each transmission in repeated transmission of PDSCH in method A

Table 12 RV corresponding to each transmission in repeated transmission of PDSCH in Method A

Method B: Use a predefined RV cycle, and the set of candidate RV values is {0,3}. Table 13-14 shows the RV corresponding to each transmission in the repeated transmission of PDSCH in method B.

Table 13 RV corresponding to each transmission in repeated transmission of PDSCH in method B

Table 14 RV corresponding to each transmission in repeated transmission of PDSCH in method B

For the case where the RV is configured to be 1bit, the RV value indicated by the DCI scheduling the PDSCH of the DCI scheduling PDSCH and the RV value used for the nth time in the repeated transmission is determined according to the RV value in the DCI scheduling the PDSCH. The above examples can also be interchanged. For example: Take Table 12 as an example, after the exchange, it is shown in Table 15. Table 15 shows the RV corresponding to each transmission in the repeated transmission of the PDSCH after the RV value and the RV cycle are exchanged.

Table 15 The RV corresponding to each transmission in the repeated transmission of PDSCH after the RV value and the RV cycle are exchanged

Optionally, in an embodiment, it is determined to use different predefined RV cycles according to different repetition factors (number of repetitions). For example, when the configuration RV is 1bit, when the repetition factor (number of repetitions) is 2, use Table 13; when the repetition factor (number of repetitions) is 4, use Table 8.

Through the above-mentioned embodiment, when the traffic channel transmission with the repetition factor is configured, and the redundancy version bit field in the downlink control information is configured as 0 bit or 1 bit, the predefined and limited RV version set is used to determine the location of each repeated transmission. The redundant version is used to avoid data receiving errors caused by inconsistent understanding between the terminal and the service node.

This embodiment also provides a method for dynamically activating/deactivating scheduling-free transmission type 1 (CG type1). The method includes a serving node (such as a base station) configuring and activating one or more sets of scheduling-free transmission for a terminal (such as a UE) For type 1 (CG type1) resources, DCI signaling can deactivate/reactivate the type1 CGs resources, where the deactivation/reactivation DCI signaling indicates an identifier corresponding to the type1 CGs.

In R-15, each bandwidth part (Band Width Part, BWP) can only be configured with one set of scheduling-free resources, namely type1 CG or type2 CG, and the two types of scheduling-free resources do not exist at the same time. Among them, type1 CG resources The configuration is configured by RRC signaling to configure part of CG parameters and activation, and type2 CG resource configuration is configured by RRC signaling to configure part of CG parameters and DCI activation/deactivation scrambled by Radio Network Temporary Identity (CS-RNTI). The main feature of the two types of CGs configuration is that the type 1 configuration has a lower activation delay, and the type 2 is relatively more dynamic. It can adjust the parameters of the CGs more dynamically to better match the user's service transmission. R-16 supports multiple sets of CG configurations and type1 CG and type2 CG can be configured at the same time. Each set of CG is configured with a serial number as an identifier of the CG. In some scenarios, the base station needs to quickly deactivate type1 CG resources or, as time goes by, the type1 CG resource configuration does not match the current service. It is necessary to adjust the parameters of CG resources, and realize type1 CG deactivation and deactivation through RRC reconfiguration. Adjust the parameters, the delay will be very large. In some embodiments, type 1 CGs are deactivated/reactivated through DCI signaling, that is, type 1 CGs and type 2 CGs are combined.

In an embodiment, the serving node (such as the base station gNB) configures the terminal (such as the UE) with 4 sets of scheduling-free transmission resources, the numbers are #0, #1, #2, and #3, respectively. Among them, #0, #1 are Type1 scheduling-free transmission resources, #2, #3 are Type2 scheduling-free transmission resources. After the UE receives the RRC configuration and activation signaling from the base station to activate #0CGs,#1 CGs resources, when it needs to quickly deactivate/or adjust the type1 CG resource parameters, it sends the CS-RNTI scrambled DCI pair #0CGs, #1 Deactivate or reactivate CGs (quickly deactivate CGs configuration or adjust the configuration parameters of type1 CGs), the CGs index (index) indication field in DCI indicates #0, #1 or the combination of #0 index, #1 index Deactivate states.

The embodiment of the present application also provides a device for determining the number of retransmissions. FIG. 15 is a schematic structural diagram of an apparatus for determining the number of retransmissions according to an embodiment. As shown in FIG. 15, the device for determining the number of retransmissions includes: a receiving module 310 and a first determining module 320.

The receiving module 310 is configured to receive configuration information; the first determining module 320 is configured to determine the number of repeated transmissions of the information to be transmitted according to the configuration information.

The device for determining the number of retransmissions in this embodiment improves the reliability of repeated transmission by receiving configuration information and determining the number of repeated transmissions according to the configuration information.

In an embodiment, the first determining module 320 is set to at least one of the following:

In an embodiment, the first determining module 320 is configured to:

The device for determining the number of retransmissions proposed in this embodiment belongs to the same concept as the method for determining the number of retransmissions proposed in the foregoing embodiment. For technical details that are not described in detail in this embodiment, please refer to any of the foregoing embodiments. The method for determining the number of retransmissions has the same effect.

The embodiment of the present application also provides a device for indicating the number of retransmissions. FIG. 16 is a schematic structural diagram of a device for indicating the number of retransmissions according to an embodiment. As shown in FIG. 16, the device for indicating the number of retransmissions includes: a second determining module 410 and a sending module 420.

The second determining module 410 is configured to determine configuration information, where the configuration information is used to indicate the number of repeated transmissions of the information to be transmitted; the sending module 420 is configured to send the configuration information.

The device for indicating the number of retransmissions in this embodiment improves the reliability of repeated transmission by sending configuration information and indicating the number of repeated transmissions according to the configuration information.

In an embodiment, the second determining module 410 is set to at least one of the following:

When the TDRA information of the second method including the setting item is configured, the number of repeated transmissions is indicated by the second method; when the TDRA information of the second method including the setting item is not configured, the TDRA information is passed The first way indicates the number of repeated transmissions.

In the case where the first indication field is configured in the RRC signaling in the first manner, the number of repeated transmissions is the number of repeated transmissions in the first manner; in the first manner, the RRC signaling does not configure the first indication field. If the setting item is configured in the TDRA information of the second mode, the number of repeated transmissions is indicated in the second mode; in the first mode, the RRC signaling does not configure the first indication field In the case where the setting item is not configured in the TDRA information of the second mode, the number of repeated transmissions is equal to 1; in the first mode, the RRC signaling is not configured with a first indication If the TDRA information of the second mode including the setting item is not configured, the number of repeated transmissions is equal to 1.

When the TDRA information of the second method including the setting item is configured, the number of repeated transmissions is the second method; when the TDRA information of the second method including the setting item is not configured, the second method is passed The third method indicates the number of repeated transmissions.

In an embodiment, the second determining module 410 is configured to:

The device for indicating the number of retransmissions proposed in this embodiment belongs to the same concept as the method for indicating the number of retransmissions proposed in the above embodiment. For technical details not described in this embodiment, please refer to any of the above embodiments, and this embodiment is capable of The number of retransmissions indicates the same effect as the method.

The embodiment of the present application also provides a communication node.

In an embodiment, the method for determining the number of retransmissions may be executed by a device for determining the number of retransmissions, and the device for determining the number of retransmissions may be implemented in software and/or hardware and integrated in the communication node. The communication node is a terminal.

In an embodiment, the method for indicating the number of retransmissions may be executed by a device for indicating the number of retransmissions. The device for indicating the number of retransmissions may be implemented in software and/or hardware and integrated in the communication node. The communication node is a service node (network side, base station, etc.).

Fig. 17 is a schematic structural diagram of a communication node provided by an embodiment. As shown in FIG. 17, a communication node provided in this embodiment includes: a processor 510 and a storage device 520. There may be one or more processors in the communication node. In FIG. 17, one processor 510 is taken as an example. The processor 510 and the storage device 520 in the device may be connected by a bus or other methods. Take bus connection as an example.

The one or more programs are executed by the one or more processors 510, so that the one or more processors implement the method for determining the number of retransmissions or the method for indicating the number of retransmissions described in any of the foregoing embodiments.

The storage device 520 in the communication node, as a computer-readable storage medium, can be used to store one or more programs. The programs can be software programs, computer-executable programs, and modules, as in this embodiment, the number of retransmissions is determined The program instructions/modules corresponding to the method (for example, the modules in the device for determining the number of retransmissions shown in FIG. 7 include: a receiving module 310 and a first determining module 320). The processor 510 executes various functional applications and data processing of the communication node by running the software programs, instructions, and modules stored in the storage device 520, that is, implements the method for determining the number of retransmissions or indicating the number of retransmissions in the foregoing method embodiment method.

The storage device 520 mainly includes a storage program area and a storage data area. The storage program area can store an operating system and an application program required by at least one function; the storage data area can store data created according to the use of the device, etc. (as in the above implementation) Example configuration information, TDRA information, etc.). In addition, the storage device 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the storage device 520 may include memories remotely provided with respect to the processor 510, and these remote memories may be connected to a communication node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

In an embodiment, when one or more programs included in the aforementioned communication node are executed by the one or more processors 510, the following operations are implemented: receiving configuration information; determining the repetition of the information to be transmitted according to the configuration information Number of transfers.

In an embodiment, when one or more programs included in the aforementioned communication node are executed by the one or more processors 510, the following operations may also be implemented: determining configuration information, where the configuration information is used to indicate to be transmitted The number of repeated transmissions of information; sending the configuration information.

The communication node proposed in this embodiment belongs to the same concept as the method for determining the number of retransmissions or the method for indicating the number of retransmissions proposed in the above embodiment. For technical details not described in this embodiment, please refer to any of the above embodiments, and this embodiment It has the same effect as the method for determining the number of retransmissions or the method for indicating the number of retransmissions.

The embodiment of the present application also provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute a method for determining the number of retransmissions or a method for indicating the number of retransmissions when executed by a computer processor.

Based on the above description of the implementation manners, this application can be implemented by software and general-purpose hardware, and can also be implemented by hardware. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), Random Access Memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including multiple instructions to make a computer device (which can be a personal computer, server, or network device, etc.) execute any of this application The method described in the embodiment.

The above are only exemplary embodiments of the present application, and are not used to limit the protection scope of the present application.

The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) (Digital Versatile Disc, DVD) or compact disc (Compact Disc, CD)), etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architecture.

Claims

A method for determining the number of retransmissions includes:

Receive configuration information;

The number of repeated transmissions of the information to be transmitted is determined according to the configuration information.
The method according to claim 1, wherein the information to be transmitted corresponds to a first transmission type, and the configuration information corresponds to a first mode or a second mode;

The first manner includes: the first indication field of the radio resource control RRC signaling is used to indicate the number of repeated transmissions, and when the first indication field is not configured in the RRC signaling, the repeated transmission The number of times is 1;

The second method includes: a setting item in the time domain resource allocation TDRA information is used to indicate the number of repeated transmissions.
The method according to claim 2, wherein, for the first mode, in the case where a first indication field is configured in the RRC signaling, the value indicated by the first indication field is an integer greater than 1.
The method according to claim 2, wherein, for the second mode, the number of repeated transmissions is an integer greater than or equal to 1.
The method according to claim 2, wherein the determining the number of repeated transmissions of the information to be transmitted according to the configuration information comprises at least one of the following:

In the case that the setting item for each time domain resource in the TDRA information of the second manner is 1, the number of repeated transmissions is determined by the first manner;

In the case that at least one setting item corresponding to a time domain resource in the TDRA information of the second manner is greater than 1, the second manner is used to determine the number of repeated transmissions;

In a case where the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second mode is equal to 1, the number of repeated transmissions is determined by the first mode;

In a case where the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second mode is greater than 1, the second mode is used to determine the number of repeated transmissions;

In the case that the setting item is not configured in the TDRA information of the second method, the number of repeated transmissions is determined by the first method.
The method according to claim 2, wherein the determining the number of repeated transmissions of the information to be transmitted according to the configuration information comprises at least one of the following:

In the case where the TDRA information of the second mode including the setting item is configured, the number of repeated transmissions is determined by the second mode;

In a case where the TDRA information of the second method including the setting item is not configured, the number of repeated transmissions is determined by the first method.
The method according to claim 2, wherein the determining the number of repeated transmissions of the information to be transmitted according to the configuration information comprises at least one of the following:

In the case where the RRC signaling in the first manner is configured with a first indication field, determine the number of repeated transmissions in the first manner;

In the case where the first indication field is not configured in the RRC signaling in the first manner, and the setting item is configured in the TDRA information in the second manner, the second manner is used to determine the The number of repeated transmissions;

In the case where the first indication field is not configured in the RRC signaling in the first manner, and the setting item is not configured in the TDRA information in the second manner, the number of repeated transmissions is equal to 1. ；

In the case where the first indication field is not configured in the RRC signaling in the first manner, and the TDRA information of the second manner including the setting items is not configured, the number of repeated transmissions is equal to one.
The method according to claim 2, wherein the determining the number of repeated transmissions of the information to be transmitted according to the configuration information comprises:

In the case where the RRC signaling indicates the first logical value, determine the number of repeated transmissions in the first manner;

In the case where the RRC signaling indicates the second logical value, the number of repeated transmissions is determined in the second manner.
The method according to claim 1, wherein the information to be transmitted corresponds to a second transmission type, and the configuration information corresponds to a second mode or a third mode;

The second manner includes: indicating the number of repeated transmissions according to a setting item in the TDRA information;

The third manner includes: indicating the number of repeated transmissions according to a second indication field of RRC signaling.
The method according to claim 9, wherein, for the second mode or the third mode, the number of repeated transmissions is an integer greater than or equal to 1.
The method according to claim 9, wherein the determining the number of repeated transmissions of the information to be transmitted according to the configuration information comprises at least one of the following:

In the case where the setting item for each time domain resource in the TDRA information of the second mode is 1, the number of repeated transmissions is determined by the third mode;

In the case that at least one setting item corresponding to a time domain resource in the TDRA information of the second manner is greater than 1, the second manner is used to determine the number of repeated transmissions;

In a case where the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second mode is equal to 1, the third mode is used to determine the number of repeated transmissions;

In a case where the scheduling information of the information to be transmitted indicates that the setting item in the TDRA information of the second mode is greater than 1, the second mode is used to determine the number of repeated transmissions;

In the case that the setting item is not configured in the TDRA information of the second manner, determine the number of repeated transmissions through the third manner;

In the case where a second indication field is configured in the RRC signaling in the third manner, the number of repeated transmissions is determined by the third manner.
The method according to claim 9, wherein the determining the number of repeated transmissions of the information to be transmitted according to the configuration information comprises one of the following:

In a case where the TDRA information of the second mode including the setting item is configured, the number of repeated transmissions is determined by the second mode;

In a case where the TDRA information of the second method including the setting item is not configured, the number of repeated transmissions is determined by the third method.
The method according to claim 9, wherein the determining the number of repeated transmissions of the information to be transmitted according to the configuration information comprises:

In a case where the RRC signaling indicates a third logical value, determine the number of repeated transmissions by using the third method;

In a case where the RRC signaling indicates the fourth logical value, the number of repeated transmissions is determined by the second method.
The method according to any one of claims 1-13, wherein the information to be transmitted is carried on a physical transmission channel;

The physical transmission channel includes at least one of a physical downlink shared channel PDSCH and a physical uplink shared channel PUSCH.
A method for indicating the number of retransmissions, including:

Determining configuration information, where the configuration information is used to indicate the number of repeated transmissions of the information to be transmitted;

Send the configuration information.
The method according to claim 15, wherein the information to be transmitted corresponds to a first transmission type, and the configuration information corresponds to a first mode or a second mode;

The first manner includes: the first indication field of the radio resource control RRC signaling is used to indicate the number of repeated transmissions, and when the first indication field is not configured in the RRC signaling, the repeated transmission The number of times is 1;

The second method includes: a setting item in the time domain resource allocation TDRA information is used to indicate the number of repeated transmissions.
The method according to claim 16, wherein, for the first mode, in the case where a first indication field is configured in the RRC signaling, the value indicated by the first indication field is an integer greater than 1.
The method according to claim 16, wherein, for the second mode, the number of repeated transmissions is an integer greater than or equal to 1.
The method according to claim 15, wherein the information to be transmitted corresponds to a second transmission type, and the configuration information corresponds to a second mode or a third mode;

The second manner includes: indicating the number of repeated transmissions according to a setting item in the TDRA information;

The third manner includes: indicating the number of repeated transmissions according to a second indication field of RRC signaling.
The method according to claim 19, wherein, for the second mode or the third mode, the number of repeated transmissions is an integer greater than or equal to 1.
A device for determining the number of retransmissions includes:

The receiving module is set to receive configuration information;

The first determining module is configured to determine the number of repeated transmissions of the information to be transmitted according to the configuration information.
A device for indicating the number of retransmissions, including:

The second determining module is configured to determine configuration information, where the configuration information is used to indicate the number of repeated transmissions of the information to be transmitted;

The sending module is set to send the configuration information.
A communication node, including:

At least one processor;

The storage device is set to store at least one program;

When the at least one program is executed by the at least one processor, the at least one processor implements the method for determining the number of retransmissions according to any one of claims 1-14 or any one of claims 15-20 The method for indicating the number of retransmissions.
A computer-readable storage medium storing a computer program, wherein the program is executed by a processor to implement the method for determining the number of retransmissions according to any one of claims 1-14 or any one of claims 15-20 The method for indicating the number of retransmissions described in the item.