CN110971355B

CN110971355B - Configuration method of uplink dynamic-authorization-free transmission and communication device

Info

Publication number: CN110971355B
Application number: CN201811140993.7A
Authority: CN
Inventors: 徐修强; 陈雁; 王轶; 吕永霞
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-09-28
Filing date: 2018-09-28
Publication date: 2021-10-22
Anticipated expiration: 2038-09-28
Also published as: WO2020063767A1; CN110971355A

Abstract

The application provides a configuration method and a communication device for uplink dynamic-authorization-free transmission. The method comprises the following steps: the network device generates DCI, which is used to activate or deactivate the configured authorization configuration. The DCI includes a first indication field and at least one first class field. The first indication field indicates an index of authorized configurations of activated or deactivated configurations. The number of bits of the first type field is related to the authorization configuration of the activated or deactivated configuration. The first indication field is located before all the first-type fields or at the last position of the DCI. The network device sends the DCI to the terminal device, so that the terminal device activates or deactivates an authorized configuration of the configuration corresponding to the index based on the DCI. The position of the first indication field in the DCI is fixed by defining the first indication field before the first-type field or at the last position of the DCI. The terminal device may resolve the first indication field based on the fixed location, determining an authorized configuration of the activated or deactivated configurations.

Description

Configuration method of uplink dynamic-authorization-free transmission and communication device

Technical Field

The present application relates to the field of wireless communications, and in particular, to a configuration method for uplink dynamic grant-free transmission and a communication apparatus.

Background

Due to the advantages of small signaling overhead, low transmission delay, low terminal power consumption, and the like, the uplink dynamic-authorization-free transmission is widely applied to scenarios such as ultra-reliable and low-latency communication (URLLC), enhanced mobile broadband (eMBB), and massive machine type communication (mtc).

The uplink dynamic grant transmission may transmit uplink data through a Physical Uplink Shared Channel (PUSCH) of a configured grant (configured grant), for example. In one implementation, the network device may configure the terminal device with the partial parameters of the PUSCH through a configured grant configuration (configured grant configuration). Thereafter, the network device may activate or deactivate configured grant configuration through Downlink Control Information (DCI), for example, or perform retransmission scheduling.

Taking the activated configured grant configuration as an example, the network device may configure a plurality of configured grant configurations for the terminal device, and may indicate which configured grant configuration is activated through a hybrid automatic repeat request (HARQ) process number (HPN) field in the DCI. Thereafter, the terminal apparatus may transmit the PUSCH based on the configured grant configuration and the information in the DCI.

However, since the positions of the HPN domains in different DCIs are not necessarily the same, the terminal device cannot acquire information in the HPN domain, that is, cannot determine which configured grant configuration is activated, since the positions of the HPN domains cannot be determined. Thus, normal transmission of PUSCH may be affected.

Disclosure of Invention

The application provides a configuration method of uplink dynamic-authorization-free transmission and a communication device, which are used for ensuring normal transmission of a dynamic-authorization-free PUSCH.

In a first aspect, a method for configuring uplink dynamic-grant-free transmission is provided, where the method may be performed by a terminal device, or may also be performed by a chip configured in the terminal device.

Specifically, the method comprises the following steps: receiving DCI for activating or deactivating one configured grant configuration of a plurality of configured grant configurations, the DCI including a first indication field and at least one first type field, a bit number of the first type field being determined by the activated or deactivated configured grant configuration, the first indication field indicating an index of one configured grant configuration, the first indication field being located before the at least one first type field; activate or deactivate the configured grant configuration corresponding to the index.

In a second aspect, a method for configuring an uplink dynamic-grant-free transmission is provided, where the method may be performed by a network device, or may also be performed by a chip configured in the network device.

Specifically, the method comprises the following steps: generating DCI for activating or deactivating one configured grant configuration of a plurality of configured grant configurations, the DCI including a first indication field and at least one first type field, a bit number of the first type field being determined by the activated or deactivated configured grant configuration, the first indication field indicating an index of one configured grant configuration, the first indication field being located before the at least one first type field; the DCI is transmitted.

Based on the above technical solution, by defining the first indication field before all the first-type fields, the position of the first indication field in the DCI may not be affected by the length of the first-type field. That is, the position of the first indication field in the DCI may be fixed. Therefore, the terminal device can resolve the first indication field based on the fixed location, so that the activated or deactivated configured grant configuration can be accurately determined. Transmitting a PUSCH based on the parameter and DCI therein in case of activating the configured grant configuration; in the case of deactivation of the configured grant configuration, the configured grant configuration is released. Therefore, the dynamic authorization-free transmission of the PUSCH is not influenced, and the use of the uplink dynamic authorization-free transmission in various scenes is facilitated.

With reference to the first aspect or the second aspect, in some possible implementations, the DCI further includes a New Data Indicator (NDI) field, where the NDI field is used to determine that the DCI is used to activate or deactivate a configured grant configuration, and the NDI field is located before the at least one first-type field.

When the NDI field is available to determine that the DCI is used to activate or deactivate a configured grant configuration, the NDI field and the first indication field may be placed together before all the first-type fields. The application does not limit the relative position relationship between the NDI field and the first indication field, the NDI field may be located before the first indication field, or may be located after the first indication field, and the NDI field and the first indication field may be adjacent or may not be adjacent. The protocol may predefine the locations of the NDI field and the first indication field in the DCI so that the terminal device resolves the NDI field and the first indication field based on the fixed locations.

In a third aspect, a method for configuring uplink dynamic-grant-free transmission is provided, where the method may be performed by a terminal device, or may also be performed by a chip configured in the terminal device.

Specifically, the method comprises the following steps: receiving a DCI for activating or deactivating one configured grant configuration of a plurality of configured grant configurations, the DCI including a first indication field and at least one first class field, a bit number of the first class field being determined by the activated or deactivated configured grant configuration, the first indication field indicating an index of one configured grant configuration, the first indication field being located at a last position of the DCI; activate or deactivate the configured grant configuration corresponding to the index.

In a fourth aspect, a method for configuring an uplink dynamic-grant-free transmission is provided, where the method may be performed by a network device, or may also be performed by a chip configured in the network device.

Specifically, the method comprises the following steps: generating a DCI, where the DCI is used to activate or deactivate a configured grant configuration of a plurality of configured grant configurations, and the DCI includes a first indication field and at least one first class field, a bit number of the first class field is determined by the activated or deactivated configured grant configuration, the first indication field indicates an index of a configured grant configuration, and the first indication field is located at a last position of the DCI; the DCI is transmitted.

Wherein, the first indication field is located at the last position of the DCI, and may include: the first indication field occupies part or all of the bits in the last segment of the DCI. The last segment of bits may be, for example, a predefined number of bits. For example, in the case that the DCI does not include a zero padding (padding) bit, the first indication field may be the last field of the DCI, or may not be the last field of the DCI but still be located in the last segment of bits; in case that the DCI includes zero padding bits, the first indication field may be located after all the zero padding bits.

In order to reduce the number of blind detections, the network device may design multiple DCIs sent to the same terminal device to have the same length. In this case, if the first indication field is placed at the last position of the DCI, the position of the first indication field in the DCI may be considered to be fixed.

Based on the above technical solution, by defining the first indication field at the last position of the DCI, the position of the first indication field in the DCI may not be affected by the length of the first-type field. That is, the position of the first indication field in the DCI may be fixed. Therefore, the terminal device can resolve the first indication field based on the fixed location, so that the activated or deactivated configured grant configuration can be accurately determined. Transmitting a PUSCH based on the parameter and DCI therein in case of activating the configured grant configuration; in the case of deactivation of the configured grant configuration, the configured grant configuration is released. Therefore, the dynamic authorization-free transmission of the PUSCH is not influenced, and the use of the uplink dynamic authorization-free transmission in various scenes is facilitated.

With reference to the third aspect or the fourth aspect, in some possible implementations, the DCI further includes a New Data Indicator (NDI) field, where the NDI field is used to determine that the DCI is used to activate or deactivate a configured grant configuration, and both the first indication field and the NDI field are located at a last position of the DCI.

When the NDI field is available to determine that the DCI is used to activate or deactivate a configured grant configuration, the NDI field and the first indication field may be placed together at the last position of the DCI. The first indication field and the NDI field are both located at the last position of the DCI, and may include: the first indication field and the NDI field are the last two fields of the DCI in the case that the DCI does not contain the zero padding bit, or both the first indication field and the NDI field are located after the zero padding bit in the case that the DCI contains the zero padding bit. In order to reduce the number of blind detections, the network device may design multiple DCIs sent to the same terminal device to have the same length, and at this time, the first indication field and the NDI field are placed at the last position of the DCI, and the positions of the first indication field and the NDI field in the DCI may be considered to be fixed.

It should be understood that the application is not limited to the relative position relationship between the NDI field and the first indication field, and the NDI field may be located before the first indication field or after the first indication field. The protocol may predefine the locations of the NDI field and the first indication field in the DCI so that the terminal device resolves the NDI field and the first indication field based on the fixed locations.

With reference to the first aspect or the third aspect, in some possible implementations, in a case that the DCI is used to activate configured grant configuration, the method further includes: and transmitting the PUSCH based on the DCI and the activated configured grant configuration.

Accordingly, with reference to the second aspect or the fourth aspect, in some possible implementations, in case that the DCI is used to activate configured grant configuration, the method further includes: receiving a PUSCH based on the DCI and the activated configured grant configuration.

That is, the terminal device and the network device may transmit the PUSCH based on the same transmission resources and transmission parameters.

With reference to the first aspect or the third aspect, in some possible implementation manners, in a case that the DCI is used to deactivate configured grant configuration, the method further includes: deactivating (or, in other words, releasing) the configured grant configuration.

That is, the terminal device deactivates the configured grant configuration, that is, it may be considered that the terminal device no longer transmits the PUSCH based on the configured grant configuration, and the network device no longer receives the PUSCH based on the deactivated configured grant configuration.

In a fifth aspect, a method for data transmission is provided, where the method may be performed by a terminal device, or may be performed by a chip configured in the terminal device.

Specifically, the method comprises the following steps: receiving DCI, the DCI being used for retransmission scheduling, the DCI comprising a first indication field and at least one first class field, the number of bits of the first class field being determined by configured grant configuration used for retransmission, the first indication field being used for determining the configured grant configuration, the first indication field being located before the at least one first class field; and retransmitting the transport block according to the configured grant configuration determined by the first indication field and the DCI.

In a sixth aspect, a method for data transmission is provided, where the method may be performed by a terminal device, or may be performed by a chip configured in the terminal device.

Specifically, the method comprises the following steps: transmitting DCI, the DCI being for retransmission scheduling, the DCI including a first indication field and at least one first-class field, the number of bits of the first-class field being determined by configured grant configuration used for retransmission, the first indication field being used for determining the configured grant configuration, the first indication field being located before the at least one first-class field; and receiving the retransmitted transport block by the DCI according to the configured grant configuration determined by the first indication field.

Based on the above technical solution, by defining the first indication field before all the first-type fields, the position of the first indication field in the DCI may not be affected by the length of the first-type field. That is, the position of the first indication field in the DCI may be fixed. Thus, the terminal device may resolve the first indication field based on the fixed location. Thus, the terminal device can accurately determine the configured grant configuration used for retransmission. Therefore, the terminal device may retransmit the transport block according to the DCI and the configured grant configuration, thereby implementing retransmission of data and facilitating improvement of overall reliability of data transmission.

With reference to the fifth aspect or the sixth aspect, in some possible implementations, the DCI further includes a New Data Indication (NDI) field, the NDI field indicates that the DCI is used for retransmission scheduling, and the NDI field is located before the at least one first-type field.

When the NDI field is available to determine that the DCI is for retransmission scheduling, the NDI field and the first indication field may be placed together before all the first type fields. The application does not limit the relative position relationship between the NDI field and the first indication field, the NDI field may be located before the first indication field, or may be located after the first indication field, and the NDI field and the first indication field may be adjacent or may not be adjacent. The protocol may predefine the locations of the NDI field and the first indication field in the DCI so that the terminal device resolves the NDI field and the first indication field based on the fixed locations.

In a seventh aspect, a method for data transmission is provided, where the method may be performed by a terminal device, or may also be performed by a chip configured in the terminal device.

Specifically, the method comprises the following steps: receiving DCI, wherein the DCI is used for retransmission scheduling, the DCI comprises a first indication domain and at least one first class domain, the bit number of the first class domain is determined by configured grant configuration used for retransmission, the first indication domain is used for determining the configured grant configuration, and the first indication domain is located at the last position of the DCI; and retransmitting the transport block according to the configured grant configuration determined by the first indication field and the DCI.

In an eighth aspect, a method for data transmission is provided, where the method may be performed by a network device, or may be performed by a chip configured in the network device.

Specifically, the method comprises the following steps: transmitting DCI, the DCI being used for retransmission scheduling, the DCI including a first indication field and at least one first class field, the bit number of the first class field being determined by configured grant configuration used for retransmission, the first indication field being used for determining the configured grant configuration, the first indication field being located at the last position of the DCI; and receiving the retransmitted transport block by the DCI according to the configured grant configuration determined by the first indication field.

Based on the above technical solution, by defining the first indication field at the last position of the DCI, the position of the first indication field in the DCI may not be affected by the length of the first-type field. That is, the position of the first indication field in the DCI may be fixed. Thus, the terminal device may resolve the first indication field based on the fixed location. Thus, the terminal device can accurately determine the configured grant configuration used for retransmission. Therefore, the terminal device may retransmit the transport block according to the DCI and the configured grant configuration, thereby implementing retransmission of data and facilitating improvement of overall reliability of data transmission.

With reference to the seventh aspect or the eighth aspect, in some possible implementations, the DCI further includes a New Data Indication (NDI) field, the NDI field indicates that the DCI is used for retransmission scheduling, and the first indication field and the NDI field are both located at the last position of the DCI.

Wherein, the first indication field is located at the last position of the DCI, and may include: the first indication field occupies part or all of the bits in the last segment of the DCI. The last segment of bits may be, for example, a predefined number of bits. For example, in the case that the DCI does not include zero padding bits, the first indication field may be the last field of the DCI, or may not be the last field of the DCI but still be located in the last segment of bits; in case that the DCI includes zero padding bits, the first indication field may be located after all the zero padding bits.

With reference to any one of the first aspect to the eighth aspect, in some possible implementations, the first indication field is an HPN field.

It should be understood that the first indication field may be an HPN field, a newly defined field in the DCI, or another field in the DCI, which is not limited in this application.

With reference to any one of the first aspect to the eighth aspect, in some possible implementations, the DCI is scrambled by a Configured Scheduling (CS) -Radio Network Temporary Identity (RNTI).

The terminal device may determine whether the DCI is used to activate or deactivate the configured grant configuration or to be used for retransmission scheduling according to the type of RNTI that scrambles the DCI. Thereafter, the terminal device may further determine, according to the NDI field in the DCI, whether the DCI is specifically used for activating a configured grant configuration, deactivating a configured grant configuration, or for performing retransmission scheduling.

With reference to any one of the first aspect to the eighth aspect, in some possible implementations, the first class domain includes a frequency domain resource assignment domain and a frequency hopping identification domain.

It should be understood that the frequency domain resource assignment field and the frequency hopping identification field may be two first-class fields in DCI format (format)0_1, but should not constitute any limitation in this application. The present application does not exclude the possibility that DCI of other formats is newly defined in future protocols for activating or deactivating configured grant configuration or for retransmission scheduling. At this time, the newly defined DCI format may also include other first-type fields.

In a ninth aspect, there is provided a communication device comprising means for performing the method of any one of the possible implementations of the first, third, fifth or seventh aspect.

In a tenth aspect, a communication device is provided that includes a processor. The processor is coupled to the memory and is operable to execute the instructions in the memory to implement the method of any one of the possible implementations of the first, third, fifth or seventh aspects. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip configured in the terminal equipment. When the communication device is a chip configured in a terminal device, the communication interface may be an input/output interface.

Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.

In an eleventh aspect, a communication device is provided, which includes various means or units for performing the method in any possible implementation manner of the second, fourth, sixth, or eighth aspect.

In a twelfth aspect, a communications apparatus is provided that includes a processor. The processor is coupled to the memory and is operable to execute the instructions in the memory to implement the method of any of the possible implementations of the second, fourth, sixth or eighth aspects. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

In one implementation, the communication device is a network device. When the communication device is a network device, the communication interface may be a transceiver, or an input/output interface.

In another implementation, the communication device is a chip configured in the network device. When the communication device is a chip configured in a network device, the communication interface may be an input/output interface.

In a thirteenth aspect, a processor is provided, including: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method in any one of the possible implementations of the first to eighth aspects and the first to eighth aspects.

In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the signal output by the output circuit may be output to and transmitted by a transmitter, for example and without limitation, and the input circuit and the output circuit may be the same circuit that functions as the input circuit and the output circuit, respectively, at different times. The embodiment of the present application does not limit the specific implementation manner of the processor and various circuits.

In a fourteenth aspect, a processing apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory, and may receive a signal through the receiver and transmit a signal through the transmitter to perform the method of any one of the possible implementations of the first to eighth aspects and the first to eighth aspects.

Optionally, the number of the processors is one or more, and the number of the memories is one or more.

Alternatively, the memory may be integral to the processor or provided separately from the processor.

In a specific implementation process, the memory may be a non-transient memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

It will be appreciated that the associated data interaction process, for example, sending the indication information, may be a process of outputting the indication information from the processor, and receiving the capability information may be a process of receiving the input capability information from the processor. In particular, the data output by the processor may be output to a transmitter and the input data received by the processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver, among others.

The processing device in the above fourteenth aspect may be a chip, the processor may be implemented by hardware or may be implemented by software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.

In a fifteenth aspect, a computer program product is provided, the computer program product comprising: a computer program (which may also be referred to as code, or instructions), which when executed, causes a computer to perform the method of any one of the possible implementations of the first to eighth aspects and of the first to eighth aspects described above.

In a sixteenth aspect, a computer-readable medium is provided, which stores a computer program (which may also be referred to as code or instructions) that, when executed on a computer, causes the computer to perform the method of any one of the possible implementations of the first to eighth aspects and the first to eighth aspects.

In a seventeenth aspect, a communication system is provided, which includes the foregoing network device and terminal device.

Drawings

Fig. 1 is a schematic diagram of a communication system suitable for use with the method provided by an embodiment of the present application;

fig. 2 is a schematic flowchart of a configuration method for uplink dynamic-grant-free transmission according to an embodiment of the present application;

fig. 3 shows an example of the arrangement order of the respective fields in the DCI;

FIG. 4 illustrates an example of moving a first indicated domain to all first-class domains;

FIG. 5 illustrates an example of moving both the first indication field and the NDI field to all of the first class fields;

FIG. 6 shows an example after moving the first indication field to all zero-padding bits;

fig. 7 illustrates an example of moving the first indication field to the last position of DCI;

FIG. 8 shows an example after moving both the HPN and NDI fields to all zero-padding bits;

fig. 9 illustrates an example of moving both the HPN field and the NDI field to the last position of DCI;

fig. 10 is a schematic diagram of the arrangement order of the respective fields in the DCI format 0_1 defined in NR;

fig. 11 to 14 are schematic diagrams illustrating an arrangement order of each field in DCI format 0_1 obtained after moving the HPN field and the NDI field;

FIG. 15 is a schematic flow chart diagram of a method of data transmission provided by another embodiment of the present application;

fig. 16 is a schematic block diagram of a communication device provided by an embodiment of the present application;

fig. 17 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

fig. 18 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (GSM) systems, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), universal mobile telecommunications system (universal mobile telecommunications system, UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, future fifth generation (5G) or new radio NR systems, etc.

For the understanding of the embodiments of the present application, a communication system suitable for the method provided by the embodiments of the present application will be first described in detail with reference to fig. 1. Fig. 1 shows a schematic diagram of a communication system 100 suitable for use in the method provided by the embodiments of the present application. As shown, the communication system 100 may include at least one network device, such as a base station (gNB) in the 5G system shown in fig. 1; the communication system 100 may further include at least one terminal device, such as User Equipments (UEs) 1 to 6 shown in fig. 1. The network device and each terminal device can communicate through a wireless link. For example, the network device may send configuration information to the terminal device, and the terminal device may send uplink data to the network device based on the configuration information; for another example, the network device may send downlink data to the terminal device. Thus, the gNB and UE 1 to UE6 in fig. 1 may constitute one communication system.

The terminal devices in the communication system 100, e.g., UE4 through UE6, may also form a communication system. For example, the UE4 may control the UE5 and the UE6 to perform corresponding instructions. This is not a limitation of the present application.

It should be understood that the network device in the communication system may be any device having a wireless transceiving function. The network devices include, but are not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (e.g., home evolved NodeB or home Node B, HNB), baseband Unit (BBU), Access Point (AP) in wireless fidelity (WiFi) system, wireless relay Node, wireless backhaul Node, Transmission Point (TP) or Transmission and Reception Point (TRP), etc., and may also be 5G, such as NR, gbb in the system, or transmission point (TRP or TP), one or a group of base stations in the 5G system may also include multiple antennas, or panels, and may also be configured as network panels or NB, such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may also include a Radio Unit (RU). The CU implements part of the function of the gNB, and the DU implements part of the function of the gNB, for example, the CU implements Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) layers, and the DU implements Radio Link Control (RLC), Medium Access Control (MAC) and Physical (PHY) layers. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as the RRC layer signaling, may also be considered to be transmitted by the DU or the DU + CU under this architecture. It is to be understood that the network device may be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU may be divided into network devices in a Radio Access Network (RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this application.

It should also be understood that terminal equipment in the wireless communication system may also be referred to as User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and the like. The embodiments of the present application do not limit the application scenarios.

It should also be understood that fig. 1 is a simplified schematic diagram that is merely illustrated for ease of understanding, and that other network devices or other terminal devices, which are not shown in fig. 1, may also be included in the communication system 100.

To facilitate understanding of the embodiments of the present application, a brief description will first be made of several concepts referred to hereinafter.

1. DCI format (format)0_ 1: the second type of configuration may be used to activate or deactivate a configured grant configuration (configured grant configuration) so that the terminal device performs PUSCH transmission without dynamic grant, and may also be used for retransmission scheduling. The DCI format 0_1 may include a DCI format indication (DCI format) field, a carrier indication (carrier indicator) field, a bandwidth part indication (BWP indicator), a frequency domain resource assignment (frequency domain resource assignment) field, a time domain resource assignment (time domain resource assignment) field, a frequency hopping flag (frequency hopping flag), a Modulation and Coding Scheme (MCS), a New Data Indication (NDI) field, a Redundancy Version (RV) field, a hybrid automatic repeat request (HARQ) process number (HARQ process number, HPN) field, and the like, which are not listed herein for simplicity.

It should be understood that the fields included in the DCI format 0_1 listed above are merely examples, and the specific content and format in the DCI format 0_1 may refer to the NR protocol (e.g., third generation partnership project (3))^rdgeneration partnership project, 3GPP) TS 38.212). Of course, the present application also does not exclude the possibility of making changes to DCI format 0_1 in future protocols.

2. New Data Indication (NDI) field: typically, the NDI field may be used to indicate whether the resource scheduled by this DCI is for initial transmission or retransmission. In this embodiment of the present application, the DCI may be used to activate or deactivate the authorization configuration of the second type of configuration, so that the terminal device performs PUSCH transmission without dynamic authorization, and may also be used for retransmission scheduling. The NDI field may be used to determine whether the DCI is used to activate or deactivate a second-type configured grant configuration or to retransmit scheduling.

Specifically, the NDI field may include 1 indication bit. When the indication bit is "1", the DCI may be considered for retransmission scheduling; when the indication bit is "0", it may be further determined whether the DCI is used to activate or deactivate the second-type configured grant configuration in combination with other fields in the DCI. For example, when Most Significant Bits (MSB) in the HPN domain are 0 and the RV domains are all 0, or when the HPN domains are all 0 and the RV domains are all 0, the DCI is used to activate the grant configuration of the second type of configuration; and when the MSB of the HPN domain is 0, the RV domain is all 0, the MCS domain is all 1, and the frequency domain resource assignment domain is all 1, or when the HPN domain is all 0, the RV domain is all 0, the MCS domain is all 1, and the frequency domain resource assignment domain is all 1, the DCI is used for deactivating the authorization configuration of the second type of configuration.

The protocol may predefine how to determine whether the DCI is for activating or deactivating the second-type configured grant configuration or for retransmission scheduling according to each domain in the DCI.

3. HARQ Process Number (HPN) field: typically, the HPN field may be used to indicate the HARQ process number of the retransmitted transport block. In the embodiment of the present application, the DCI may be used to activate or deactivate configured grant configuration, and may also be used to perform retransmission scheduling. When the indication bit in the NDI field is "1", it may indicate that the DCI is used for retransmission scheduling, and the HPN field is used to indicate the HARQ process number of the retransmitted transport block.

As described above, when the indication bit in the NDI field is "0", the terminal device may further determine, in combination with other fields in the DCI, whether the DCI field is used to activate or deactivate the configured grant configuration. When only MSB in the HPN domain is used to determine whether the DCI is an authorized configuration for activation or deactivation configuration, the other 3 bits of the HPN domain may also be used to determine an index (index) of a configured grant configuration activated or deactivated by the DCI.

4. And (3) dynamic authorization-free transmission: the uplink transmission of the terminal device does not need to be completed by scheduling of the network device. Specifically, when the uplink data arrives, the terminal device does not need to send a Scheduling Request (SR) to the network device and wait for a dynamic grant (dynamic grant) of the network device, but may directly send the uplink data to the network device using a transmission resource pre-allocated by the network device and a specified transmission parameter.

In NR, uplink dynamic grant-free transmission can be divided into two categories. Namely, a PUSCH transmission based on a first Type of configuration grant (Type 1 PUSCH transmission with a configured grant, or Type 1 configured grant configuration, or Type 1 configured grant PUSCH transmission) and a PUSCH transmission based on a second Type of configuration grant (Type 2 PUSCH transmission with a configured grant, or Type 2 configured grant configuration, or Type 2 configured grant PUSCH transmission).

The network device may configure the configured grant configuration through higher layer signaling, such as a configured grant configuration control element (configured grant configuration information element, configured IE) carried in a Radio Resource Control (RRC) message. The terminal device may determine whether the configured grant configuration configured by the configurable grant configuration IE is the first-type configured grant configuration or the second-type configured grant configuration according to the parameter configured in the configurable grant configuration IE.

These two types of uplink dynamic-grant-free transmissions are described in detail below.

In the PUSCH transmission based on the first-type configuration grant, the parameters configured in the configured grant configuration may include, for example, a period of a time-frequency resource, an open-loop power control related parameter, a waveform, a redundancy version sequence, a repetition number, a frequency hopping pattern, a resource allocation type, a number of HARQ processes, a demodulation reference signal (DMRS) related parameter, a Modulation Coding Scheme (MCS) table, a Resource Block Group (RBG) size, all transmission resources including a time-domain resource, a frequency-domain resource, an MCS, and the like, and a transmission parameter. After receiving the high-level parameters, the terminal device may directly use the configured transmission parameters to transmit the PUSCH on the configured time-frequency resources. Therefore, this transmission scheme may also be referred to as a full RRC-configured uplink grant (full RRC-configured UL grant).

In the PUSCH transmission based on the second type configuration grant, the parameters configured in the configured grant configuration may include transmission resources and transmission parameters including, for example, a period of time-frequency resources, an open-loop power control related parameter, a waveform, a redundancy version sequence, a repetition number, a frequency hopping pattern, a resource allocation type, a number of HARQ processes, a DMRS related parameter, an MCS table, an RBG group size, and the like. In a specific example, the parameters configured in the configured grant configuration may specifically refer to, for example, specific specifications in NR protocol 3GPP TS 38.331. Thereafter, the network device may activate one configured grant configuration through the DCI for the PUSCH transmission. The DCI may carry an index of the activated configured grant configuration. The DCI may further configure other transmission resources and transmission parameters including time domain resources, frequency domain resources, port numbers of DMRSs, MCSs, and the like. Therefore, after receiving the configured grant configuration, the terminal device cannot immediately perform PUSCH transmission, and needs to determine the activated configured grant configuration after receiving DCI, and transmit PUSCH on the configured time-frequency resources based on the configured transmission parameters in combination with the transmission resources and the transmission parameters indicated in the DCI.

In other words, the terminal device activates a configured grant configuration, i.e. validates the parameters in the configured grant configuration. The terminal device may determine the transmission resource and the transmission parameter for transmitting the PUSCH in combination with the parameter in the configured grant configuration and the parameter in the DCI activating the configured grant configuration, so that the PUSCH transmission may be performed. Thus, when a DCI activates a configured grant configuration, the DCI may be considered to activate a dynamic grant-free transmission based on the configured grant configuration.

In addition, the network device may also deactivate the configured grant configuration through the DCI. Specifically, the DCI may carry an index of a deactivated configured grant configuration. The terminal device may determine the deactivated configured grant configuration according to the index.

In other words, the terminal device deactivates a certain configured grant configuration, i.e. disables the parameter in this configured grant configuration. While the terminal device may deactivate (or otherwise release) the configured grant configuration. Thus, when a DCI deactivates a configured grant configuration, the DCI may be considered to deactivate a dynamic grant-free transmission based on the configured grant configuration.

Hereinafter, for convenience of explanation, the second type of configured grant configuration described above is simply referred to as configured grant configuration, unless otherwise specified.

In an embodiment of the present application, the DCI for activating the configured grant configuration may be DCI scrambled by a specific type of RNTI. When the terminal device receives the DCI, it may be determined whether the DCI is a DCI for activating or deactivating a configured grant configuration, or in other words, whether the DCI is for activating a dynamic grant free transmission, according to the type of RNTI that scrambles the DCI. The specific type of RNTI may be, for example, a CS-RNTI, or another RNTI that is not transmitted by a dynamic grant, or an RNTI dedicated to transmission configured by a higher layer. This is not a limitation of the present application.

It should be noted that the network device may scramble the DCI with a certain RNTI, which specifically means that the network device scrambles Cyclic Redundancy Check (CRC) bits in the DCI with a certain RNTI. If the terminal equipment descrambles the CRC successfully based on a certain RNTI, the information in the DCI can be acquired; if the terminal equipment fails to descramble the CRC based on a certain RNTI, the DCI is not scrambled based on the RNTI or is not sent to the terminal equipment.

5. HARQ process number: HARQ uses stop-and-wait protocol (stop-and-wait protocol) to transmit data. Taking uplink transmission as an example, after sending a Transport Block (TB), the terminal device stops to wait for the acknowledgement information. The network device may use 1 bit of information to Acknowledge (ACK) or Negative (NACK) the transport block. But the terminal device stops waiting for an acknowledgement after each transmission, resulting in a low throughput. The terminal device may use multiple parallel HARQ processes. While one HARQ process is waiting for acknowledgement information, the terminal device may continue to transmit data using another HARQ process.

The HARQ process number is also called HARQ process Identification (ID). One HARQ process number may be used to uniquely specify one HARQ process. After the terminal device performs channel coding on the transport block, the data obtained by the channel coding may be registered in a buffer (buffer) for transmission. The transport blocks in the buffer may have a one-to-one correspondence with HARQ processes, and each transport block may correspond to one HARQ process. The correspondence between the transport block and the HARQ process may be embodied by the correspondence between the transport block and the HARQ process number. Therefore, the terminal device can determine the correspondence between the transport block and the HARQ process number in advance.

Because the network device carries the HARQ process number in the DCI, the HARQ process number has a corresponding relationship with the time-frequency resource indicated in the DCI. That is to say, when a transport block is transmitted based on the time-frequency resource indicated in the DCI, the HARQ process number corresponding to the transport block is the HARQ process number carried in the DCI. Therefore, both the network device and the terminal device can determine the corresponding relationship between the time-frequency resource and the HARQ process number.

When the data received by the network device on a certain time-frequency resource is not successfully decoded or the data is not received on a certain time-frequency resource, the HARQ process number corresponding to the time-frequency resource can be notified to the terminal device through DCI. The terminal device may determine the transport block to be retransmitted according to the corresponding relationship between the HARQ process number and the transport block.

In this embodiment, the network device may perform retransmission scheduling for the terminal device. Specifically, the network device may configure the terminal device with parameters for retransmission through configured grant configuration, where the parameters may include one or more of a waveform, a resource allocation type, a frequency hopping pattern, DMRS related parameters, an MCS table, and an RBG size, for example. Since the network device may configure multiple configured grant configurations for the terminal device, the multiple configured grant configurations may have a corresponding relationship with the HARQ process number, so that the terminal device determines the configured grant configuration used for retransmission based on the HARQ process number indicated in the DCI, and further determines the parameter used for retransmission.

6. Transport Block (TB): the transport block may be a data block from a higher layer. A transport block may include, for example, a data block of a Media Access Control (MAC) Protocol Data Unit (PDU), and the data block may be transmitted over a time unit or may be a unit of HARQ retransmission. In existing LTE and NR, a maximum of two transport blocks can be transmitted per time unit for each terminal device. By way of example and not limitation, the time unit is a Transmission Time Interval (TTI).

As described above, in the wireless communication system, as shown in fig. 1, the network device may configure a plurality of second-type configured grant configurations for the terminal device through higher-layer signaling, and may activate or deactivate one of them through DCI. The terminal device may determine the configured grant configuration to be activated or deactivated according to the HPN domain in the DCI.

However, since the length of some fields in DCI is not fixed, the location of the HPN field in different DCIs is not necessarily the same, or fixed. The terminal device cannot resolve information in the HPN domain based on the fixed location, and cannot determine the activated configured grant configuration.

In view of the above, the present application provides a configuration method, so that a terminal device determines an activated configured grant configuration, and performs PUSCH transmission based on resources and parameters configured in the configured grant configuration.

To facilitate understanding of the embodiments of the present application, the following description is made before describing the embodiments of the present application.

First, in the embodiments of the present application, there are several references to moving a certain domain. For example, "move the first indication field" or "move the first indication field to" a location. It should be understood that this is not to say that the network device would have the action of "moving" the first indication field, but rather that the first indication field appears to be moved in its position in the DCI as used in the embodiments of the present application, as compared to its position in the existing DCI. In this embodiment, the network device generates DCI required to be used in this embodiment according to a DCI format (e.g., a format described in any one of fig. 4 to 9 and fig. 11 to 14) after the first indication field position is moved. Correspondingly, the terminal equipment also analyzes each domain in the DCI according to the corresponding DCI format after receiving the DCI.

Second, in the embodiments of the present application, there are multiple places where higher layer parameters are involved. The higher layer parameters may be carried by higher layer signaling. The higher layer signaling may be, for example, an RRC message, or other higher layer signaling, which is not limited in this application.

Third, in the embodiments of the present application, "indication" may include a direct indication and an indirect indication, and may also include an explicit indication and an implicit indication. If the information indicated by a certain piece of information (such as configuration information described below) is referred to as information to be indicated, in a specific implementation process, there are many ways to indicate the information to be indicated, for example, but not limited to, the information to be indicated may be directly indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein an association relationship exists between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other part of the information to be indicated is known or predetermined. For example, the indication of the specific information may be implemented by means of a predetermined arrangement order of the respective information (e.g., protocol specification), thereby reducing the indication overhead to some extent.

Fourth, the first, second and various numerical numbers in the embodiments shown below are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application. For example, different indication information is distinguished.

Fifth, in the embodiments shown below, "pre-acquisition" may include signaling by the network device or pre-defined, e.g., protocol definition. The "predefined" may be implemented by saving a corresponding code, table, or other means that can be used to indicate the relevant information in advance in the device (for example, including the terminal device and the network device), and the present application is not limited to a specific implementation manner thereof.

Sixth, the term "store" in the embodiments of the present application may refer to a store in one or more memories. The one or more memories may be provided separately or integrated in the encoder or decoder, the processor, or the communication device. The one or more memories may also be provided separately, with a portion of the one or more memories being integrated into the decoder, the processor, or the communication device. The type of memory may be any form of storage medium and is not intended to be limiting of the present application.

Seventh, the "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the communication field, and may include, for example, an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in the present application.

Eighth, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, and c, may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, wherein a, b and c can be single or multiple.

The method provided by the embodiment of the application will be described in detail below with reference to the accompanying drawings.

It should be understood that the methods provided herein may be applicable to a wireless communication system, such as the wireless communication system 100 shown in fig. 1. Two communication devices in a wireless communication system have a wireless communication connection therebetween, and one of the two communication devices may correspond to any one of UE 1 to UE6 shown in fig. 1, for example, may be any one of UE 1 to UE6 in fig. 1, or may be a chip configured in any one of UE 1 to UE 6; the other of the two communication devices may correspond to the gNB shown in fig. 1, and may be, for example, the gNB shown in fig. 1, or may be a chip disposed in the gNB.

Hereinafter, the embodiments of the present application will be described in detail by taking the interaction between the terminal device and the network device as an example without loss of generality. It will be appreciated that any one terminal device in a wireless communication system may communicate with one or more network devices having wireless communication connections based on the same method. This is not limited in this application.

Fig. 2 is a schematic flow chart of a configuration method 200 for uplink dynamic-grant-free transmission according to an embodiment of the present application, which is shown from the perspective of device interaction. As shown, the method 200 may include steps 210 through 240. The various steps in method 200 are described in detail below.

In step 210, the network device sends configuration information, which is used to configure a plurality of configured grant configurations. Accordingly, the terminal device receives the configuration information.

As described above, the network device may configure a plurality of configured grant configurations for the terminal device, for example, through higher layer signaling (i.e., an example of configuration information). In this embodiment, the configured grant configuration may be the second type of configured grant configuration described above. Each configured grant configuration may include transmission resources and transmission parameters including a period of time-frequency resources, an open-loop power control related parameter, a waveform, a redundancy version sequence, a repetition number, a frequency hopping pattern, a resource allocation type, a number of HARQ processes, a DMRS related parameter, an MCS table, an RBG group size, and the like.

It should be understood that the network device may configure multiple configured grant configurations through one higher layer signaling, and may also configure multiple configured grant configurations through multiple higher layer signaling, which is not limited in this application. In addition, the network device may also configure the first-type configured grant configuration through high-level signaling, which is not limited in this application.

The network device may determine that the terminal device may need to use the dynamic authorization-free transmission, for example, based on the capability information reported by the terminal device, or according to the service type of the terminal device. The network device may activate configured grant configuration through DCI, for example, so that the terminal device may perform dynamic grant-free PUSCH transmission.

In step 220, the network device generates DCI including a first indication field indicating an index of an activated or deactivated configured grant configuration.

In this embodiment, the DCI may be used to activate or deactivate a configured grant configuration. The activated or deactivated configured grant configurations may be one of a plurality of configured grant configurations pre-configured by the terminal device in step 210.

As previously described, the DCI may be DCI scrambled by a specific type of RNTI. When receiving the DCI, the terminal device may determine whether the DCI is used to activate or deactivate configured grant configuration or to perform retransmission scheduling according to the type of the RNTI that scrambles the DCI. In other words, the network device may implicitly indicate that the DCI is for activating or deactivating configured grant configuration or for retransmission scheduling by scrambling the DCI through the CS-RNTI.

It should be understood that CS-RNTI is only one example of the specific type of RNTI described above and should not be construed as limiting the application in any way. The special type of RNTI may also include other dynamic grant free transmissions or higher layer configured transmission specific RNTIs. The protocol may pre-define the functions of different types of RNTI-scrambled DCIs, for example, a certain type of RNTI-scrambled DCI may be defined for activating or deactivating configured grant configuration, or another type of RNTI-scrambled DCI may be defined for retransmission scheduling. The network device may generate DCI based on the predefined RNTI type and the DCI function, and the terminal device may also parse DCI based on the predefined RNTI type and the DCI function.

For convenience of explaining the present embodiment, the fields in the DCI may be divided into a first-class field and a second-class field.

Wherein the number of bits of the first type field may be related to a higher layer parameter. Alternatively, the number of bits in the first-type field may vary depending on the higher-level parameters. That is, when DCI is used to activate or deactivate different configured grant configurations, the number of bits included in the first-type field may vary. That is, the length of the first-type field may be different in different DCIs. Specifically, the number of bits of the first-type field is related to parameters configured in the activated or deactivated configured grant configuration. For example, the parameter may specifically include one or more of a period of a time domain resource, an open loop power control related parameter, a waveform, a redundancy version sequence, a number of repetitions, a frequency hopping pattern, a resource allocation type, a number of HARQ processes, a demodulation reference signal related parameter, an MCS table, and an RBG size.

For example, when the format of the DCI is DCI format 0_1, the frequency hopping identity field and the frequency domain resource assignment field in the DCI belong to the first class field. Specifically, the number of bits of the hopping identity field depends on the hopping pattern in the higher layer parameters. If the high layer is configured with the frequency hopping mode parameter, the frequency hopping identification domain can be 1 bit; if the higher layer is not configured with the hopping pattern parameter, the hopping identification field may be 0 bit. The number of bits of the frequency domain resource assignment field may depend on parameters such as waveform, RGB size, frequency hopping pattern, resource allocation type, and the like.

The number of bits in the second type field may be independent of the upper layer parameters, or the number of bits in the second type field may not vary depending on the upper layer parameters. That is, when DCI is used to activate or deactivate different configured grant configurations, the number of bits included in the second-type field does not change. That is, the length of the second-type field may be fixed in different DCIs. Specifically, the number of bits of the second-type field is independent of the parameters configured in the activated or deactivated configured grant configuration.

For example, when the format of the DCI is DCI format 0_1, a format indication field, a carrier indication field, an UL/SUL indication field, a BWP indication field, a time domain resource assignment field, an MCS field, an RV field, an HPN field, an NDI field, etc. in the DCI may all belong to the second class field.

However, it should be understood that each field in the DCI format 0_1 listed above and the category to which the field belongs are only examples, and should not limit the present application in any way. The present application does not exclude the possibility of defining one or more second type fields as first type fields in future protocols, nor of defining one or more first type fields as second type fields.

In this embodiment, the first class of domain may include the frequency hopping identity domain and the frequency domain resource assignment domain.

In this embodiment, the second type field may include a first indication field, and the first indication field may be used to indicate an index of the configured grant configuration that is activated or deactivated. By way of example and not limitation, the first indication field is an HPN field. Of course, the first indication field may be other fields that can be used to indicate the index of the configured grant configuration for activation or deactivation. For example, a newly defined field in DCI or other fields may be multiplexed. This is not a limitation of the present application. Optionally, the second class of domain further comprises an NDI domain.

As an alternative embodiment, the DCI may follow a DCI format defined in an existing protocol. For convenience of differentiation and explanation, the arrangement of the first indication field in the DCI when the DCI format defined in the existing protocol is used will be referred to as case one. A. the

In case one, the network device may generate DCI based on the predefined format. The predefined DCI format may be used to activate or deactivate configured grant configuration, may be used to perform retransmission scheduling, and may be used to perform dynamic scheduling on a PUSCH. This is not a limitation of the present application.

In the predefined DCI format, the first indication field may be preceded by at least one first-class field, and the first indication field may be followed by one or more first-class fields, one or more second-class fields, or one or more zero-padding bits.

The zero padding bits are added in the DCI to ensure that a plurality of DCIs sent to the same terminal device by the network device have the same length, so as to reduce the number of blind tests of the terminal device. In one implementation, the protocol may predefine the length of the DCI, and the network device may determine whether zero padding is needed based on the predefined length. In another implementation, the network device may determine whether zero padding is required for each generated DCI according to the length of the longest DCI.

Fig. 3 shows an example of the arrangement order of the respective fields in DCI. As shown, the DCI may include at least one first-type field and at least one second-type field. Note that the zero padding bits in the figure are merely illustrative, and do not mean that all DCI include zero padding bits.

It can be seen that if the first indication field is located after at least one first type field, the location of the first indication field may change due to different high-level parameters. For example, when the first indication field is located after the hopping pattern identification field and the hopping pattern parameter is allocated to the higher layer or when the hopping pattern parameter is not allocated to the higher layer, the positions of the first indication fields obtained by the respective operations are shifted by 1 bit. If there are more first-type fields before the first indication field, the bit number of the first indication field staggered in different DCIs may be larger. The terminal device cannot determine the location of the first indication field, that is, cannot resolve the information in the first indication field, and thus cannot determine the configured grant configuration for activation or deactivation.

In this embodiment, the network device may move the first indication field in the DCI based on any one of the following two ways:

the first method is as follows: moving the first indication domain to be before all the first-class domains; or

The second method comprises the following steps: the first indication field is moved to the last position of the DCI.

The above two modes are explained in detail below.

In a first way,

The first indication domain is moved to the front of all the first-class domains, or the first indication domain is moved to the front of the first-class domain. Moving the first indication domain to the first class domain may include: the first domain is moved to an arbitrary position before the first domain. Fig. 4 illustrates an example before moving the first indication field in the DCI illustrated in fig. 3 to all the first-type fields. It should be understood that the illustration in the figures is merely an example, and the network device may move the first indicated domain to any position before all the first-type domains. The protocol may predefine to which position before the first indication field is moved to the first type field. For example, the first indication domain is moved to the last domain before the first domain, or the first indication domain is moved to the first domain before the first domain, or the first indication domain is moved to a specific position before the first domain, which is not limited in this application. When the protocol defines that the first indication field is moved to a position before the first type field, the network device may generate DCI based on the definition, and the terminal device may also parse the first indication field in the DCI based on the definition.

Optionally, the first indication field is an HPN field. Since it has been explained hereinbefore, whether the DCI is for activating or deactivating the configured grant configuration or for retransmission scheduling may be determined according to the NDI field. In case that the DCI is used to activate or deactivate a configured grant configuration, the last 3 bits of the HPN domain may be used to indicate an index of the activated or deactivated configured grant configuration; and in case the DCI is used for retransmission scheduling, the HPN field may be used to indicate the HARQ process number.

Then, in one implementation, the network device may move the NDI domain to precede all of the first-type domains as well. Fig. 5 shows an example before moving both the HPN field and the NDI field in the DCI shown in fig. 3 to all the first-type fields. It should be understood that the illustration in the drawings is merely an example, and the embodiment of the present application does not limit the order in which the NDI field and the HPN field are arranged in the DCI. For example, the HPN domain may be located before or after the NDI domain. The NDI domain and the HPN domain may be two adjacent domains or two non-adjacent domains. The relative position relationship between the NDI domain and the HPN domain may be predefined by a protocol, which is not limited in this application. In addition, the embodiment of the present application does not limit the order of the other second-type fields arranged in the DCI.

In another implementation, the network device may also move the NDI field to the last position of the DCI. That is, the NDI field is taken as the last field of the DCI, and the NDI field occupies the last bit of the DCI. Specifically, in case the DCI includes zero padding bits, the NDI field may be located after all zero padding bits; in case the DCI does not contain zero padding bits, the NDI field may be located after the last field of the DCI. That is, the NDI field is used as the last field of the DCI.

Optionally, the first indication field and the HPN field are different fields. For example, the first indication field may be a newly added field in the DCI, and is used to indicate an index of the configured grant configuration. The configured grant configuration corresponding to the index may be a configured grant configuration activated or deactivated by DCI, or may be a configured grant configuration used for retransmission. In this case, the network device may move the first indication domain only before all the first-class domains, without moving the HPN domain and the NDI domain.

Optionally, the first indication field may also be a field other than the HPN field in the DCI. In this case, the network device may change only the positions of the first indication field and the NDI field without moving the HPN field. For example, the first indication field and the NDI field are moved to before all the first-type fields, or the first indication field is moved to before all the first-type fields, the NDI field is moved to the last position of the DCI, and so on.

The second way,

Moving the first indication field to the last position of the DCI may include: and moving the first indication field into the last section of bits of the DCI, wherein the first indication field can occupy part or all of the last section of bits. The last segment of bits may be, for example, a predefined number of bits. For example, in a case that the DCI does not include zero padding bits, the first indication field may be moved to a last field of the DCI and then used as the last field, and the first indication field may occupy the last bit of the DCI or may not occupy the last bit; alternatively, the DCI may not be moved to the end of the DCI field, but still within the last segment of bits. In the case that the DCI includes zero padding bits, the first indication field may be moved to be after all zero padding bits, or the first indication field may be moved to be after the last zero padding bit. It is understood that the bits following the zero padding bits are located within the last segment of bits of the DCI.

When the protocol defines moving the first indication field into the last segment of bits of the DCI in order for the terminal device to resolve the first indication field, it may further define which bits within the last segment of bits to place the first indication field. Accordingly, the location of the first indication field in the DCI may be determined. The terminal device may resolve the first indication field based on the location.

Specifically, if the DCI includes zero padding bits, it may be considered that the length of the DCI does not reach the predefined length or is not the longest DCI among all DCIs. In this case, if the first indication field is moved to after all the zero padding bits, the first indication field may be the last field of the DCI, and the last bit of the first indication field may be the last bit of the DCI. The starting position of the first indication field may be determined according to the length of the zero-padded DCI and the length of the first indication field. Fig. 6 shows an example of moving the first indication field in the DCI shown in fig. 3 to after all zero padding bits.

If the DCI does not include the zero padding bits, the length of the DCI may be considered to be a predefined length, or the DCI is the longest DCI among all DCIs. In this case, if the first indication field is moved to the end of the DCI, the first indication field may become the end of the DCI. The starting position of the first indication field may be determined according to the length of the DCI and the length of the first indication field. Fig. 7 shows an example of moving the first indication field in the DCI shown in fig. 3 to the last position of the DCI.

In one implementation, the network device may move the HPN field and the NDI field to the last position of the DCI. In the case where the DCI contains zero padding bits, the network device may move both the HPN field and the NDI field to after all the zero padding bits. Fig. 8 shows an example in which both the HPN field and the NDI field in the DCI shown in fig. 3 are moved to all zero padding bits. It should be understood that the illustration in the drawings is merely an example, and the embodiment of the present application does not limit the order in which the NDI field and the HPN field are arranged in the DCI. The NDI field may be the last field of the DCI, and in this case, the last bit of the DCI may be the NDI field; the HPN field may also be DCI to the last field, and in this case, the last bit of the DCI may be the last bit of the HPN field. Alternatively, the NDI domain may be located before the HPN domain or after the HPN domain. The relative position relationship between the NDI domain and the HPN domain may be predefined by a protocol, and the sequence of the NDI domain and the HPN domain is not limited in this embodiment. In addition, the embodiment of the present application does not limit the order of the other second-type fields arranged in the DCI.

In the case where the DCI does not contain the zero padding bits, the network device may move the HPN field and the NDI field to the last position of the DCI, e.g., move both the HPN field and the NDI field after the last field. Fig. 9 shows an example of moving the HPN field and the NDI field in the DCI shown in fig. 3 to the last position of the DCI. It should be understood that the illustration in the drawings is merely an example and should not be construed as limiting the application in any way. In this embodiment, the order of the NDI domain and the HPN domain is not limited, for example, the HPN domain may be located before the NDI domain or after the HPN domain. That is, the HPN field may become the last field of the DCI, or the NDI field may also become the last field of the DCI. The relative position relationship between the NDI domain and the HPN domain may be predefined by a protocol, which is not limited in this application. In addition, the embodiment of the present application does not limit the order of the other second-type fields arranged in the DCI.

In another implementation, the network device may also move the NDI domain ahead of all the first-class domains. That is, the network device may move the NDI domain to any location before the first-type domain. The protocol may predefine where the NDI field is specifically located before the first-type field.

Optionally, the first indication field and the HPN field are different fields. For example, the first indication field may be a newly added field in the DCI, and is used to indicate an index of the configured grant configuration. The configured grant configuration corresponding to the index may be a configured grant configuration activated or deactivated by DCI, or may be a configured grant configuration used for retransmission. In this case, the network device may move the first indication field only after the last field of the DCI, i.e., the first indication field as the last field of the DCI without moving the HPN field and the NDI field.

Optionally, the first indication field may also be a field other than the HPN field in the DCI. In this case, the network device may change only the positions of the first indication field and the NDI field without moving the HPN field. For example, the first indication field and the NDI field are moved to the last position of the DCI, or the first indication field is moved to the last position of the DCI, and the NDI field is moved to all the first-type fields.

Based on the above-listed methods, the following describes a procedure of generating DCI by a network device, with reference to DCI format 0_1 in NR as an example.

Fig. 10 is a schematic diagram of the arrangement order of the respective fields in the DCI format 0_1 defined in NR. The figure is only schematic, and only the arrangement order of partial domains in the DCI is shown. The HPN field is an example of the first indication field. The frequency domain resource assignment field and the frequency hopping identification field are examples of the first class of fields. The remaining fields are all of the second class. In the figure, "… …" indicates an omitted DCI field.

As shown, the HPN domain and the NDI domain are both behind the frequency domain resource assignment domain (i.e., an instance of the first-class domain). If the DCI format 0_1 is used to activate or deactivate the configured grant configuration, the activated or deactivated configured grant configuration needs to be determined according to the HPN domain.

The network device may move the HPN domain and the NDI domain based on the manner enumerated above. Fig. 11 to 14 are schematic diagrams illustrating an arrangement order of each field in DCI format 0_1 obtained after moving the HPN field and the NDI field. Specifically, fig. 11 shows an example of moving both the NDI domain and the HPN domain to a position before the frequency domain resource assignment domain. Fig. 12 shows an example of moving the NDI field and the HPN field to the last position of DCI when DCI does not include zero padding bits. Fig. 13 shows the position after moving both the NDI field and the HPN field to all zero-padding bits. Fig. 14 shows that the NDI domain is moved to a position before the frequency domain resource assignment domain and the HPN domain is moved to a position after all zero padding bits.

It should be understood that the illustration in the drawings is merely an example and should not be construed as limiting the application in any way. The present application does not limit the order of the NDI and HPN fields arranged in the DCI. When the NDI domain and the HPN domain are both located before all the first-type domains, the NDI domain and the HPN domain may be adjacent or not, and the application does not limit this.

The above-listed manner of moving the first indication field and the NDI field is only an example, and should not constitute any limitation to the present application. Other more possible implementations will occur to those skilled in the art based on the same concept.

Based on the above-listed implementations, the network device may generate the DCI. Since the location of the first indication field in the DCI may be determined, the terminal device may parse the first indication field based on the fixed location to activate or deactivate a configured grant configuration corresponding to the index in the first indication field.

Optionally, before moving the first indication field, the method further comprises: the network device determines whether to move the first indication field according to the function of the DCI. Specifically, when the DCI is for activating or deactivating configured grant configuration, the network device may move the first indication field in the manner described above.

As an optional embodiment, the network device may separately define a DCI format for activating or deactivating the configured grant configuration, and the DCI generated based on the DCI format may be specifically used for activating or deactivating the configured grant configuration. The DCI format may avoid the problem that the location of the first indication field is not fixed.

In one possible design, the first indication field may precede all of the first-type fields. For convenience of distinction and explanation, the arrangement case where the first indication domain is located before all the first-type domains in the DCI is referred to as case two.

The DCI format under this design may be similar to the result before the first indication field is moved to all the first type fields in the manner described above in case one, e.g., as shown in fig. 4. It should be understood that the illustration in fig. 4 is merely an example, and the first indication field may be anywhere before all the first-type fields. The protocol may predefine where the first indication field precedes the first type field. For example, the first indication field may be the first field of the DCI, may be a field before all the first-type fields, or may be a field at a specific position before the first-type field, which is not limited in this application.

Optionally, the first indication field is an HPN field. As described previously, whether the DCI is for activating or deactivating configured grant configuration or retransmission scheduling may be determined according to the NDI field. In case that the DCI is used to activate or deactivate a configured grant configuration, the last 3 bits of the HPN domain may be used to indicate an index of the activated or deactivated configured grant configuration; and in case the DCI is used for retransmission scheduling, the HPN field may be used to indicate the HARQ process number.

Then in one implementation the NDI field is also located before all the first type fields. The NDI domain also precedes all domains of the first type. The DCI format under this design may be similar to that used in case one above in the way-HPN fields and NDI are compared to the result before moving to all first type fields, e.g., as shown in fig. 5. However, it should be understood that fig. 5 is only an example, and the embodiment of the present application does not limit the order of arranging the NDI field and the HPN field in the DCI. The protocol may predefine the relative position of the HPN and NDI domains. For example, the HPN domain may be located before or after the NDI domain. The NDI domain and the HPN domain may be two adjacent domains or two non-adjacent domains.

In another implementation, the NDI field is located at the last position of the DCI. Specifically, the NDI field may be located within a last segment of bits of DCI, and the NDI field may occupy part or all of the last segment of bits. For example, when the DCI does not include the zero padding bit, the NDI field may be used as the last field of the DCI, and the NDI field may occupy the last bit of the DCI or may not occupy the last bit; alternatively, the NDI field may not be the last field of the DCI, but still be located in the last segment of bits. In case that the DCI includes zero padding bits, the first indication field may be defined after all the zero padding bits. At this time, the NDI field is the last field of the DCI. It is understood that the bits following the zero padding bit fall within the last segment of the DCI.

Optionally, the first indication field and the HPN field are different fields. For example, the first indication field may be a newly added field in the DCI, and is used to indicate an index of the configured grant configuration. The configured grant configuration corresponding to the index may be a configured grant configuration activated or deactivated by DCI, or may be a configured grant configuration used for retransmission. In this case, the first indication field may be defined only before all the first-type fields.

Optionally, the first indication field may also be a field other than the HPN field in the DCI. In this case, the network device may define only the locations of the first indication field and the NDI field, and not the location of the HPN field. For example, the first indication field and the NDI field are defined before all the first-type fields, or the first indication field is defined before all the first-type fields, the NDI field is defined at the last position of the DCI, etc.

In another possible design, the first indication field may be located at the last position of the DCI. For convenience of distinction and explanation, the arrangement case where the first indication field is located at the last position of the DCI is referred to as case two.

Specifically, the first indication field may be located in a last segment of bits of the DCI, and the first indication field may occupy some or all of the last segment of bits. For example, in a case that the DCI does not include zero padding bits, the first indication field may be used as a last field of the DCI, and the first indication field may occupy the last bit of the DCI or may not occupy the last bit; alternatively, the first indication field may not be the last field of the DCI, but still be located in the last segment of bits. In case that the DCI includes zero padding bits, the first indication field may be defined after all the zero padding bits. At this time, the first indication field is the last field of the DCI. It is understood that the bits following the zero padding bit fall within the last segment of the DCI. The DCI format under this design may be similar to the result of moving the first indication field to the last position of the DCI in manner two as in case one above, e.g., as shown in fig. 6 and 7.

Then, in one implementation, the HPN field and the NDI field are both located at the last position of the DCI. The HPN field and the NDI field are both located at the last position of the DCI, which may include that the HPN field and the NDI field are both located within the last section of bits of the DCI. For example, the HPN field and the NDI field are the last two fields of the DCI, or the HPN field and the NDI field are both located after the zero padding bit of the DCI, etc. Specifically, in the case that the DCI does not contain zero padding bits, the HPN field and the NDI field may be the last two fields of the DCI; in the case that the DCI does not contain the zero padding bit, the HPN field and the NDI field may be located after the zero padding bit, or may be the last two fields of the DCI. The HPN domain may be located before or after the NDI domain. This is not a limitation of the present application. The DCI format under this design may be similar to the result of moving the first indication field and the NDI field to after the last position of the DCI in manner two in case one above, e.g., as shown in fig. 8 and 9.

In another implementation, the NDI domain precedes all the first-class domains. That is, the NDI field may be located at any position before the first-type field. The protocol may predefine where the NDI field is specifically located before the first-type field.

Optionally, the first indication field and the HPN field are different fields. For example, the first indication field may be a newly added field in the DCI, and is used to indicate an index of the configured grant configuration. The configured grant configuration corresponding to the index may be a configured grant configuration activated or deactivated by DCI, or may be a configured grant configuration used for retransmission. In this case, the first indication field may be defined only at the last position of the DCI. That is, the first indication field is the last field of the DCI, and the first indication field occupies the last bit of the DCI.

Optionally, the first indication field may also be a field other than the HPN field in the DCI. In this case, the network device may define only the first indication field and the NDI field location, without defining the location of the HPN field. For example, the first indication field and the NDI field are both defined at the last position of the DCI, or the first indication field is defined at the last position of the DCI, the NDI field is defined before all the first type fields, etc.

It should be understood that the positions of the first indication field and the NDI field in the DCI format listed above are only examples and should not constitute any limitation to the present application. Other more possible designs will occur to those skilled in the art based on the same concept.

Based on the designs listed above, the network device may generate DCI. Since the location of the first indication field in the DCI may be determined, the terminal device may parse the first indication field based on the fixed location to activate or deactivate a configured grant configuration corresponding to the index in the first indication field.

In step 230, the network device transmits the DCI. Accordingly, the terminal device receives the DCI.

The network device may scramble the DCI with a specific RNTI, such as a CS-RNTI, as described above. The network device may transmit the DCI through a Physical Downlink Control Channel (PDCCH), for example. The terminal equipment can receive the DCI in a blind detection mode and descramble based on the CS-RNTI to acquire information in the DCI.

For the specific methods for the network device to transmit DCI and the terminal device to receive DCI, reference may be made to the prior art, and for the sake of brevity, detailed descriptions of specific procedures thereof are omitted.

In step 240, the terminal device activates or deactivates the configured grant configuration indicated by the first indication field.

If the terminal device succeeds in descrambling based on the specific RNTI in step 230, the terminal device may determine that the DCI is a DCI for activating or deactivating a configured grant configuration, or for retransmission scheduling.

The terminal device may further determine whether the DCI is used for activating or deactivating configured grant configuration or retransmission scheduling according to a field such as the NDI field in the DCI. The specific method for determining whether the DCI is used for activating or deactivating configured grant configuration or for retransmission scheduling through the fields such as the NDI field in the DCI has been described in detail above, and for brevity, is not described here again.

It should be understood that determining whether the DCI is used for activating or deactivating configured grant configuration or retransmission scheduling according to the scrambling type of the DCI and the field such as the NDI field is only one possible implementation manner, and should not constitute any limitation to the present application. For example, the network device may scramble the DCI with different types of RNTIs to distinguish the DCI for activating or deactivating the configured grant configuration from the DCI for retransmission scheduling; for another example, the network device may indicate the function of the DCI through another field, which is not limited in this application.

If the terminal device determines that the received DCI is used to activate or deactivate the configured grant configuration, the terminal device may determine the activated or deactivated configured grant configuration according to the DCI and the index of the configured grant configuration indicated by the first indication field.

It is understood that the one-to-one correspondence relationship between the configured grant configuration and the index may be predetermined by the network device and the terminal device. For example, the terminal device may be predefined, such as a protocol definition, or the network device may indicate the terminal device through a high-layer signaling, which is not limited in this application.

Optionally, the method 200 further comprises: if the DCI is used to activate the configured grant configuration, the terminal device may send the PUSCH based on the configured grant configuration indicated by the first indication field and the DCI. Accordingly, the network device receives the PUSCH.

Specifically, the terminal device may determine a partial transmission resource and a transmission parameter according to the configured grant configuration indicated by the first indication field, and transmit the PUSCH in combination with the transmission resource and the transmission parameter indicated in the DCI. The network device may receive the PUSCH based on the same transmission resources and transmission resources.

Optionally, the method 200 further comprises: if the DCI is used to deactivate the configured grant configuration, the terminal device releases (or deactivates) the configured grant configuration indicated by the first indication field. The network device then no longer receives PUSCH based on the deactivated configured grant configuration.

The specific process of activating or deactivating the configured grant configuration by the terminal device may refer to the prior art, and a detailed description of the specific process is omitted here for brevity.

Based on the above technical solution, the position of the first indication field in the DCI is not affected by the length of the first class field, and the terminal device may resolve the first indication field based on the fixed position. Thus, the terminal device can accurately determine the configured grant configuration to be activated or deactivated. Transmitting a PUSCH based on the parameter and DCI therein in case of activating the configured grant configuration; in the case of deactivation of the configured grant configuration, the configured grant configuration is released. Therefore, the PUSCH transmission without dynamic authorization is not affected, and the use of the uplink transmission without dynamic authorization in various scenes is facilitated.

Conversely, if the position of the first indication field in the DCI is affected by the length of the first type field, its position in the DCI cannot be determined. The terminal device may take a long time to find the first indication field or may not find the first indication field. Therefore, dynamic grant free PUSCH transmission is affected. For example, a large delay may be introduced, which is not favorable for the usage of the uplink dynamic-free grant transmission in some scenarios sensitive to the delay.

The foregoing provides a configuration method, which may facilitate a terminal device to determine and parse a first indication field based on a fixed location, so as to activate or deactivate a configured grant configuration corresponding to an index based on the configured grant configuration in the first indication field. However, the DCI is not limited to activating or deactivating the configured grant configuration, and may also be used for retransmission scheduling. And, when the DCI is used for retransmission scheduling, it may also be scrambled by the same type of RNTI, such as CS-RNTI. The terminal device may determine, according to the HPN field in the DCI, a transport block that needs to be retransmitted and a configured grant configuration used for retransmission, where the configured grant configuration may be used to indicate a parameter used for retransmission. However, since the HPN fields are not necessarily located at the same position in different DCIs, the terminal device cannot resolve the information in the HPN field based on the fixed location, and thus cannot determine the transport block to be retransmitted and the configured grant configuration to be retransmitted.

The present application further provides a data transmission method, so that a terminal device can analyze an HPN domain based on a fixed location, thereby determining a transport block that needs to be retransmitted and a configured grant configuration used for retransmission, and retransmitting data based on the configured grant configuration.

Fig. 15 is a schematic flow chart diagram illustrating a method 300 of data transmission provided by another embodiment of the present application from the perspective of device interaction. As shown, the method 300 may include steps 310 through 350. The various steps in method 300 are described in detail below.

In step 310, the network device sends configuration information for configuring a plurality of configured grant configurations. Accordingly, the terminal device receives the configuration information.

The specific process of step 310 is the same as the specific process of step 210 in method 200 above. Since step 210 has already been described in detail in method 200 above, it is not repeated here for brevity.

In step 320, the network device generates DCI, where the DCI includes a first indication field for indicating a configured grant configuration for retransmission.

In this embodiment, the DCI may be used to schedule retransmission. The parameter used for retransmission may be one of a plurality of configured grant configurations preconfigured in step 310. The parameters used for retransmission may include, for example: one or more of a waveform, a resource allocation type, a frequency hopping pattern, a DMRS related parameter, an MCS table, and an RBG size.

As previously described, the DCI may be DCI scrambled by a specific type of RNTI. When the terminal device receives the DCI, it may determine whether the DCI is used to activate or deactivate the configured grant configuration or used for retransmission scheduling according to the type of RNTI that scrambles the DCI.

Similar to the method 200, the fields in the DCI may also be divided into first-class fields and second-class fields. Since the first-type domain and the second-type domain have already been described in detail in the method 200, they are not described here again for brevity.

In this embodiment, the first class of domain may include a frequency hopping identity domain and a frequency domain resource assignment domain.

In this embodiment, the second type field may include a first indication field, and the first indication field may be used to indicate a configured grant configuration for retransmission. By way of example and not limitation, the first indication field is an HPN field. Of course, the first indication field may also be other fields that can be used to indicate the configured grant configuration for retransmission. In this case, the second type field may also include an HPN field. Optionally, the second class of domain further comprises an NDI domain.

It should be noted that, when the HPN domain is the first indication domain, the HPN domain carries the HARQ process number. The HARQ process number may be used to determine the retransmitted data. In this embodiment, the network device and the terminal device may determine in advance a corresponding relationship between the HARQ process number and the configured grant configuration. For example, the HARQ process number may be calculated according to the time domain resource index of the configured grant configuration. Thus, the HARQ process number may be used to indirectly indicate the configured grant configuration used for the retransmission. Alternatively, the HPN field may be used to determine the configured grant configuration to be used for retransmission.

When the HPN domain and the first indication domain are different domains, the first indication domain may directly carry an index of the configured grant configuration used for retransmission. In this case, the terminal device may determine the configured grant configuration used for retransmission according to the first indication field.

In this embodiment, the arrangement of the domains in the DCI is the same as the arrangement of the domains in the DCI in the embodiment shown in the method 200. The network device may generate DCI based on the approach provided in method 200. For example, if the DCI is generated based on a predefined DCI format, the network device may move the first indication field based on the first manner or the second manner described in the first case of the method 200 when determining that the DCI is used for retransmission scheduling; if the DCI is defined as a DCI specifically used for retransmission scheduling, the network device may generate the DCI according to any one of the second case and the third case in the method 200, so as to avoid the problem that the location of the first indication field is not fixed.

Optionally, the first indication field is an HPN field. Whether the DCI is for activating or deactivating configured grant configuration or for retransmission scheduling may be determined according to the NDI field. In case that the DCI is used to activate or deactivate a configured grant configuration, the last 3 bits of the HPN domain may be used to indicate an index of the activated or deactivated configured grant configuration; and in case the DCI is used for retransmission scheduling, the HPN field may be used to indicate the HARQ process number.

The NDI field may also precede all fields of the first type or be located at the last position of the DCI in the DCI generated by the network device based on the above-listed methods. In addition, the present application does not limit the relative positional relationship between the NDI field and the first indication field.

Optionally, the first indication field and the HPN field are different fields. The network device may generate DCI based on the above-listed methods, where the first indication field may precede all the first-type fields, or the last position of the DCI, and the position of the NDI field is not limited.

Since the specific process of generating DCI by the network device and the arrangement order of each domain in the DCI under different conditions have been described in detail in the method 200 with reference to the drawings, for brevity, no further description is given here. The specific process of step 320 can be seen in the specific process of step 220 above.

In step 330, the network device transmits the DCI. Accordingly, the terminal device receives the DCI.

In step 340, the terminal device retransmits the transport block according to the DCI and the configured grant configuration indicated by the first indication field. Accordingly, the network device receives the retransmitted transport block.

Optionally, before step 340, the method further includes step 350, in which the terminal device determines the retransmitted transport block according to the HPN domain.

When the first indication domain and the HPN domain are the same domain, the network device may determine, according to the HPN domain, a retransmitted transport block and a configured grant configuration used for retransmission.

When the first indication field and the HPN field are different fields, the network device may still generate DCI based on the above-described method. After the location of the first indication field is fixed, the terminal device may parse the first indication field based on the fixed location, and may further determine a configured grant configuration used for the retransmission. Meanwhile, the terminal device may determine the bit number of the first-type domain according to the configured grant configuration used for the retransmission, and may further determine the positions of other second-type domains, for example, the HPN domain.

Or, in the process of generating the DCI, the network device may process the HPN field in a manner similar to the processing manner of the first indication field, so that the HPN field in the generated DCI is located before all the first-type fields, or in the DCI not including the zero padding bits, is located after all the first-type fields, or is located after all the zero padding bits of the DCI. In addition, the application also does not limit the relative position relationship of the first indication domain, the HPN domain and the NDI domain.

Either way, the protocol may predefine the location of the various fields in the DCI. For example, the first indication field is the last field before all the first type fields in the DCI; for another example, the first indication field is the last field of the DCI, and the first indication field occupies the last bit of the DCI; for another example, the first indication field and the NDI field are the last two consecutive fields before all the first type fields in the DCI, and the NDI field is located before the first indication field; for another example, the first indication field and the NDI field are the last two consecutive fields after all zero padding bits in the DCI, and the NDI field is located before the first indication field; for another example, the first indication field, the NDI field, and the HPN field are the last three consecutive fields before all the first-type fields in the DCI, and the NDI field is located before the first indication field, the first indication field is located before the HPN field, and so on. For the sake of brevity, this is not listed here. The network device may generate the DCI based on the definition of the protocol, and the terminal device may parse the DCI based on the definition of the protocol.

After determining a transport block to be retransmitted based on the HARQ process number indicated in the HPN field, the terminal apparatus may transmit a retransmission transport block through the PUSCH according to the DCI and the configured grant configuration used for retransmission. The network device may then receive the retransmitted transport block on the PUSCH according to the DCI and the configured grant configuration used for the retransmission.

The specific process of the terminal device for sending the retransmission transport block may refer to the prior art, and a detailed description of the specific process is omitted here for brevity.

Based on the above technical solution, the position of the first indication field in the DCI is not affected by the length of the first class field, and the terminal device may resolve the first indication field based on the fixed position. Thus, the terminal device can accurately determine the configured grant configuration used for retransmission. Therefore, the terminal device may retransmit the transport block by configuring the granted PUSCH according to the DCI and the partial parameter in the configured grant configuration. Therefore, data retransmission is realized, and the overall reliability of data transmission is improved.

Conversely, if the position of the first indication field in the DCI is affected by the length of the first type field, its position in the DCI cannot be determined. The terminal device may take a long time to find the first indication field or even not. Therefore, dynamic grant-free transmission of the PUSCH is affected, so that the advantage of reducing the delay caused by retransmitting the transport block through configuring the granted PUSCH cannot be fully utilized.

It should be understood that, in the foregoing embodiments, the sequence numbers of the processes do not imply an execution sequence, and the execution sequence of the processes should be determined by functions and internal logic of the processes, and should not constitute any limitation to the implementation process of the embodiments of the present application.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 2 to 15. Hereinafter, the communication device according to the embodiment of the present application will be described in detail with reference to fig. 16 to 18.

Fig. 16 is a schematic block diagram of a communication device provided in an embodiment of the present application. As shown, the communication device 1000 may include a communication unit 1100 and a processing unit 1200.

In one possible design, the communication apparatus 1000 may correspond to the terminal device in the above method embodiment. For example, the terminal device may be the terminal device, or a chip configured in the terminal device.

Specifically, the communication apparatus 1000 may correspond to the terminal device in the method 200 and the method 300 according to the embodiment of the present application, and the communication apparatus 1000 may include a unit for performing the method performed by the terminal device in the method 300 in fig. 2 or the method 300 in fig. 15. Also, the units and other operations and/or functions described above in the communication device 1000 are respectively for implementing the corresponding flows of the method 300 in fig. 2 or the method 300 in fig. 15.

Wherein, when the communication device 1000 is used to execute the method 200 in fig. 2, the communication unit 1100 may be used to execute steps 210 to 230 in the method 200, and the processing unit 1200 may be used to execute step 240 in the method 200.

When the communication device 1000 is configured to perform the method 300 of fig. 15, the communication unit 1100 may be configured to perform the steps 310, 330 and 340 of the method 300, and the processing unit 1200 may be configured to perform the step 350 of the method 300.

It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

It is further understood that when the communication apparatus 1000 is a terminal device, the communication unit 1100 in the communication apparatus 1000 may correspond to the transceiver 2020 in the terminal device 2000 shown in fig. 17, and the processing unit 1200 in the communication apparatus 1000 may correspond to the processor 2010 in the terminal device 2000 shown in fig. 17.

It should also be understood that when the communication apparatus 1000 is a chip configured in a terminal device, the communication unit 1100 in the communication apparatus 1000 may be an input/output interface.

In another possible design, the communication apparatus 1000 may correspond to the network device in the above method embodiment. For example, it may be a network device or a chip configured in a network device.

In another possible design, the communication apparatus 1000 may correspond to the network device in the above method embodiment, and may be, for example, a network device or a chip configured in a network device.

Specifically, the communication apparatus 1000 may correspond to the method 300 and the network device in the method 300 according to the embodiment of the present application, and the communication apparatus 1000 may include a unit for performing the method performed by the network device in the method 200 in fig. 2 or the method 300 in fig. 15. Also, the units and other operations and/or functions described above in the communication device 1000 are respectively for implementing the corresponding flows of the method 300 in fig. 2 or the method 300 in fig. 15.

When the communication device 1000 is used to execute the method 200 in fig. 2, the communication unit 1100 may be used to execute steps 210 to 230 in the method 200, and the processing unit 1200 may be used to execute step 220 in the method 200.

When the communication device 1000 is configured to perform the method 300 in fig. 15, the communication unit 1100 may be configured to perform the steps 310, 330 and 340 in the method 300, and the processing unit 1200 may be configured to perform the step 320 in the method 300.

It should also be understood that when the communication apparatus 1000 is a network device, the communication unit in the communication apparatus 1000 may correspond to the transceiver 3200 in the network device 3000 shown in fig. 18, and the processing unit 1200 in the communication apparatus 1000 may correspond to the processor 3100 in the network device 3000 shown in fig. 18.

It should also be understood that when the communication device 1000 is a chip configured in a network device, the communication unit 1100 in the communication device 1000 may be an input/output interface.

Fig. 17 is a schematic structural diagram of a terminal device 2000 according to an embodiment of the present application. The terminal device 2000 can be applied to the system shown in fig. 1, and performs the functions of the terminal device in the above method embodiment.

As shown, the terminal device 2000 includes a processor 2010 and a transceiver 2020. Optionally, the terminal device 2000 further comprises a memory 2030. The processor 2010, the transceiver 2002 and the memory 2030 may be in communication with each other via the interconnection path to transfer control and/or data signals, the memory 2030 may be used for storing a computer program, and the processor 2010 may be used for retrieving and executing the computer program from the memory 2030 to control the transceiver 2020 to transmit and receive signals. Optionally, the terminal device 2000 may further include an antenna 2040, configured to transmit uplink data or uplink control signaling output by the transceiver 2020 by using a wireless signal.

The processor 2010 and the memory 2030 may be combined into a processing device, and the processor 2010 is configured to execute the program codes stored in the memory 2030 to achieve the above functions. In particular, the memory 2030 may be integrated with the processor 2010 or may be separate from the processor 2010. The processor 2010 may correspond to the processing unit in fig. 16.

The transceiver 2020 may correspond to the communication unit in fig. 16, and may also be referred to as a transceiver unit. The transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Wherein the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that terminal device 2000 shown in fig. 17 is capable of implementing various processes involving the terminal device in the method embodiments shown in fig. 2 and 15. The operations and/or functions of the modules in the terminal device 2000 are respectively to implement the corresponding flows in the above-described method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

The processor 2010 may be configured to perform the actions described in the preceding method embodiments that are implemented within the terminal device, and the transceiver 2020 may be configured to perform the actions described in the preceding method embodiments that the terminal device transmits to or receives from the network device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

Optionally, the terminal device 2000 may further include a power supply 2050 for supplying power to various devices or circuits in the terminal device.

In addition, in order to further improve the functions of the terminal device, the terminal device 2000 may further include one or more of an input unit 2060, a display unit 2070, an audio circuit 2080, a camera 2090, a sensor 2100, and the like, and the audio circuit may further include a speaker 2082, a microphone 2084, and the like.

Fig. 18 is a schematic structural diagram of a network device provided in the embodiment of the present application, which may be a schematic structural diagram of a base station, for example. The base station 3000 can be applied to the system shown in fig. 1, and performs the functions of the network device in the above method embodiment.

As shown, the base station 3000 may include one or more radio frequency units, such as a Remote Radio Unit (RRU) 3100 and one or more baseband units (BBUs) (also referred to as digital units, DUs) 3200. The RRU 3100 may be referred to as a transceiver unit and corresponds to the communication unit 1200 in fig. 16. Alternatively, the transceiving unit 3100 may also be referred to as a transceiver, transceiving circuit, or transceiver, etc., which may comprise at least one antenna 3101 and a radio frequency unit 3102. Alternatively, the transceiving unit 3100 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter, transmitting circuit). The RRU 3100 part is mainly used for transceiving and converting radio frequency signals to baseband signals, for example, for sending indication information to a terminal device. The BBU 3200 section is mainly used for performing baseband processing, controlling a base station, and the like. The RRU 3100 and the BBU 3200 may be physically disposed together or may be physically disposed separately, i.e. distributed base stations.

The BBU 3200, which is a control center of the base station and may also be referred to as a processing unit, may correspond to the processing unit 1100 in fig. 16, and is mainly used for performing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (processing unit) may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiment, for example, to generate the foregoing indication information.

In an example, the BBU 3200 may be formed by one or more boards, and the boards may collectively support a radio access network of a single access system (e.g., an LTE network), or may respectively support radio access networks of different access systems (e.g., an LTE network, a 5G network, or other networks). The BBU 3200 also includes a memory 3201 and a processor 3202. The memory 3201 is used to store necessary instructions and data. The processor 3202 is used for controlling the base station to perform necessary actions, for example, for controlling the base station to execute the operation flow related to the network device in the above method embodiment. The memory 3201 and processor 3202 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be understood that the base station 3000 shown in fig. 18 can implement various processes involving network devices in the method embodiments of fig. 2 and 15. The operations and/or functions of the respective modules in the base station 3000 are respectively for implementing the corresponding flows in the above-described method embodiments. Reference may be made specifically to the description of the above method embodiments, and a detailed description is appropriately omitted herein to avoid redundancy.

BBU 3200 as described above can be used to perform actions described in previous method embodiments as being implemented internally by a network device, while RRU 3100 can be used to perform actions described in previous method embodiments as being sent by or received from a terminal device by a network device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The embodiment of the application also provides a processing device, which comprises a processor and an interface; the processor is configured to perform the method of any of the above method embodiments.

It should be understood that the processing means may be a chip. For example, the processing device may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD), or other integrated chips.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.

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

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program code which, when run on a computer, causes the computer to perform the method of any of the embodiments shown in figures 2 and 15.

According to the method provided by the embodiment of the present application, the present application also provides a computer readable medium storing program code, which when run on a computer, causes the computer to execute the method of any one of the embodiments shown in fig. 2 and 15.

According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

The network device in the foregoing device embodiments completely corresponds to the terminal device and the network device or the terminal device in the method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the communication unit (transceiver) executes the steps of receiving or transmitting in the method embodiments, and other steps besides transmitting and receiving may be executed by the processing unit (processor). The functions of the specific elements may be referred to in the respective method embodiments. The number of the processors may be one or more.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps (step) described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

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

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

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

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

In the above embodiments, the functions of the functional units may be fully or partially implemented by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). The procedures or functions described in accordance with the embodiments of the present application are generated in whole or in part when the computer program instructions (programs) are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for configuring uplink dynamic-grant-free transmission is characterized by comprising the following steps:

receiving Downlink Control Information (DCI), where the DCI is used to activate or deactivate one configured authorization configuration in a plurality of configured authorization configuration configured in advance, the DCI includes a first indication field and at least one first class field, a bit number of the first class field is determined by the activated or deactivated configured authorization configuration, the first indication field indicates an index of one configured authorization configuration, and the first indication field is located before the at least one first class field;

and activating or deactivating the authorization configuration of the configuration corresponding to the index.

2. The method of claim 1, wherein the DCI further comprises a New Data Indication (NDI) field, the NDI field is used to determine an authorized configuration for the DCI for activating or deactivating a configuration, and the NDI field precedes the at least one first-type field.

3. The method according to claim 1 or 2, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

4. The method of claim 1 or 2, wherein the DCI is scrambled by a configured scheduling CS-radio network temporary identity, RNTI.

5. The method of claim 1 or 2, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

6. A method for configuring uplink dynamic-grant-free transmission is characterized by comprising the following steps:

generating Downlink Control Information (DCI), where the DCI is used to activate or deactivate one configured authorization configuration in a plurality of configured authorization configuration configured in advance, the DCI includes a first indication field and at least one first class field, a bit number of the first class field is determined by the activated or deactivated configured authorization configuration, the first indication field indicates an index of one configured authorization configuration, and the first indication field is located before the at least one first class field;

and transmitting the DCI.

7. The method of claim 6, wherein the DCI further comprises a New Data Indication (NDI) field, wherein the NDI field is used to determine an authorized configuration for which the DCI is used to activate or deactivate a configuration, and wherein the NDI field precedes the at least one first type field.

8. The method according to claim 6 or 7, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

9. The method of claim 6 or 7, wherein the DCI is scrambled by a configured scheduling CS-Radio Network Temporary Identity (RNTI).

10. The method of claim 6 or 7, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

11. A method for configuring uplink dynamic-grant-free transmission is characterized by comprising the following steps:

receiving Downlink Control Information (DCI), where the DCI is used to activate or deactivate one configured authorization configuration in a plurality of configured authorization configuration configured in advance, the DCI includes a first indication field and at least one first class field, a bit number of the first class field is determined by the activated or deactivated configured authorization configuration, the first indication field indicates an index of one configured authorization configuration, and the first indication field is located at a last position of the DCI;

12. The method of claim 11, wherein the DCI further comprises a New Data Indication (NDI) field, wherein the NDI field is used to determine an authorized configuration for the DCI for an activated or deactivated configuration, and wherein the NDI field and the first indication field are both located at a last position of the DCI.

13. The method according to claim 11 or 12, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

14. The method of claim 11 or 12, wherein the DCI is scrambled by a configured scheduling CS-radio network temporary identity, RNTI.

15. The method of claim 11 or 12, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

16. A method for configuring uplink dynamic-grant-free transmission is characterized by comprising the following steps:

generating Downlink Control Information (DCI), where the DCI is used to activate or deactivate one configured authorization configuration in a plurality of configured authorization configuration configured in advance, the DCI includes a first indication field and at least one first class field, a bit number of the first class field is determined by the activated or deactivated configured authorization configuration, the first indication field indicates an index of one configured authorization configuration, and the first indication field is located at a last position of the DCI;

and transmitting the DCI.

17. The method of claim 16, wherein the DCI further comprises a New Data Indication (NDI) field, wherein the NDI field is used to determine an authorized configuration for the DCI for an activated or deactivated configuration, and wherein the NDI field and the first indication field are both located at a last position of the DCI.

18. The method according to claim 16 or 17, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

19. The method of claim 16 or 17, wherein the DCI is scrambled by a configured scheduling CS-radio network temporary identity, RNTI.

20. The method of claim 16 or 17, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

21. A communications apparatus, comprising:

a communication unit, configured to receive downlink control information DCI, where the DCI is configured to activate or deactivate an authorization configuration configured in one of a plurality of preconfigured authorization configuration configured grant configurations, where the DCI includes a first indication field and at least one first class field, a bit number of the first class field is determined by an authorization configuration of the activated or deactivated configuration, the first indication field indicates an index of one configured authorization configuration, and the first indication field is located before the at least one first class field;

and the processing unit is used for activating or deactivating the authorization configuration of the configuration corresponding to the index.

22. The communications apparatus of claim 21, wherein the DCI further comprises a New Data Indication (NDI) field, the NDI field is used to determine an authorized configuration for the DCI for an activated or deactivated configuration, and the NDI field precedes the at least one first type field.

23. The communication apparatus according to claim 21 or 22, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

24. The communications apparatus of claim 21 or 22, wherein the DCI is scrambled by a configured scheduling CS-radio network temporary identity, RNTI.

25. The communications apparatus as claimed in claim 21 or 22, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

26. A communications apparatus, comprising:

a processing unit, configured to generate DCI, where the DCI is configured to activate or deactivate an authorization configuration configured in one of a plurality of preconfigured authorization configuration configured grant configurations, where the DCI includes a first indication domain and at least one first class domain, a bit number of the first class domain is determined by an authorization configuration of the activated or deactivated configuration, the first indication domain indicates an index of one configured authorization configuration, and the first indication domain is located before the at least one first class domain;

a communication unit configured to transmit the DCI.

27. The communications apparatus of claim 26, wherein the DCI further comprises a New Data Indication (NDI) field, the NDI field is used to determine an authorized configuration for the DCI for an activated or deactivated configuration, and the NDI field precedes the at least one first type field.

28. The communication apparatus according to claim 26 or 27, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

29. The communications apparatus of claim 26 or 27, wherein the DCI is scrambled by a configured scheduling CS-radio network temporary identity, RNTI.

30. The communications apparatus as claimed in claim 26 or 27, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

31. A communications apparatus, comprising:

a communication unit, configured to receive downlink control information DCI, where the DCI is configured to activate or deactivate an authorization configuration configured in one of a plurality of preconfigured authorization configuration configured grant configurations, where the DCI includes a first indication field and at least one first class field, a bit number of the first class field is determined by an authorization configuration of the activated or deactivated configuration, the first indication field indicates an index of one configured authorization configuration, and the first indication field is located at a last position of the DCI;

and the processing unit is used for activating or deactivating the authorization configuration corresponding to the index.

32. The communications apparatus of claim 31, wherein the DCI further comprises a New Data Indication (NDI) field, the NDI field is used to determine an authorized configuration for the DCI for an activated or deactivated configuration, and the NDI field and the first indication field are both located at a last position of the DCI.

33. The communications apparatus according to claim 31 or 32, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

34. The communications apparatus of claim 31 or 32, wherein the DCI is scrambled by a configured scheduling CS-radio network temporary identity, RNTI.

35. The communications apparatus as claimed in claim 31 or 32, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

36. A communications apparatus, comprising:

a processing unit, configured to generate DCI, where the DCI is configured to activate or deactivate one configured authorization configuration in a plurality of preconfigured configured authorization configuration configured grants, where the DCI includes a first indication domain and at least one first class domain, a bit number of the first class domain is determined by an activated or deactivated configured authorization configuration, the first indication domain indicates an index of one configured authorization configuration, and the first indication domain is located at a last position of the DCI;

a communication unit configured to transmit the DCI.

37. The communications apparatus of claim 36, wherein the DCI further comprises a New Data Indication (NDI) field, the NDI field is used to determine an authorized configuration for the DCI for an activated or deactivated configuration, and the NDI field and the first indication field are both located at a last position of the DCI.

38. The communications apparatus according to claim 36 or 37, wherein the first indication field is a hybrid automatic repeat request process number, HPN, field.

39. The communications apparatus of claim 36 or 37, wherein the DCI is scrambled by a configured scheduling CS-radio network temporary identity, RNTI.

40. The communications apparatus of claim 36 or 37, wherein the first class of domains comprises a frequency domain resource assignment domain and a frequency hopping identification domain.

41. A communications device comprising at least one processor configured to perform the method of any one of claims 1-5, 6-10, 11-15, 16-20.

42. A computer-readable medium, comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 5, 6 to 10, 11 to 15, 16 to 20.