WO2020063767A1 - Configuration method for uplink dynamic grant-free transmission, and communication device - Google Patents

Abstract

The present application provides a configuration method for uplink dynamic grant-free transmission and a communication device. The method comprises: a network apparatus generating DCI for activating or deactivating a configured grant configuration, the DCI comprising a first indication field and one or more first type fields, the first indication field indicating an index of a configured grant configuration to be activated or deactivated, the number of bits in the first type fields being related to the configured grant configuration to be activated or deactivated, and the first indication field being located before all of the first type fields or at an end position of the DCI; and the network apparatus sending the DCI to a terminal apparatus, such that the terminal apparatus activates or deactivates the configured grant configuration corresponding to the index according to the DCI. The invention places the first indication field before the first type fields or at the end position of the DCI, such that the first indication field has a fixed position in the DCI. The terminal apparatus can parse to obtain the first indication field on the basis of the fixed position, and determine whether the configured grant configuration is to be activated or deactivated.

Description

Configuration method and communication device for uplink free dynamic authorization transmission

This application claims the priority of a Chinese patent application filed on September 28, 2018 with the Chinese Patent Office, application number 201811140993.7, and application name "Configuration Method and Communication Device for Uplink-Free Dynamic Authorization Transmission", the entire contents of which are incorporated by reference In this application.

Technical field

The present application relates to the field of wireless communications, and more particularly, to a configuration method and a communication device for uplink dynamic exemption authorization transmission.

Background technique

Uplink dynamic authorization-free transmission is widely used in, for example, ultra-reliable and low-latency communication (URLLC) and enhanced mobile broadband (enhanced) due to its advantages such as small signaling overhead, low transmission delay, and low terminal power consumption. mobile broadband (eMBB) and mass machine type communication (mMTC).

The uplink dynamic authorization-free transmission may, for example, transmit uplink data through a configured physical uplink shared channel (physical uplink shared channel (PUSCH)). In one implementation manner, the network device may configure some parameters of the PUSCH for the terminal device through a configured authorization configuration. Thereafter, the network device may activate or deactivate the configured grant grant configuration or perform retransmission scheduling, for example, through downlink control information (DCI).

Taking the activated configured grant configuration as an example, the network device can configure multiple configured grant configurations for the terminal device, and it can indicate activation through the hybrid automatic repeat request (HARQ) process number (HPN) field in the DCI. Which one is configured? Granted. Thereafter, the terminal device can send a PUSCH based on the configured grant configuration and the information in the DCI.

However, because the location of the HPN domain in different DCIs is not necessarily the same, because the location of the HPN domain cannot be determined, the terminal device cannot obtain the information in the HPN domain, and it cannot determine which configured grant grant configuration is activated. Therefore, it may affect the normal transmission of PUSCH.

Summary of the Invention

This application provides a configuration method and communication device for uplink dynamic authorization-free transmission, so as to ensure the normal transmission of dynamic authorization-free PUSCH.

In a first aspect, a method for configuring uplink dynamic license-free transmission is provided. The method may be executed by a terminal device, or may be executed by a chip configured in the terminal device.

Specifically, the method includes: receiving DCI, the DCI being used to activate or deactivate a configured grant grant configuration among a plurality of preconfigured configured grant grant configurations, the DCI including a first indication domain and at least one first type domain, the first The number of bits of a type of domain is determined by the activated or deactivated configured configuration. The first indication field indicates an index of the configured configuration. The first indication field is located before the at least one first type field. The field is activated or deactivated. The configured corresponding grant for the index.

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

Specifically, the method includes generating a DCI, which is used to activate or deactivate a configured grant grant configuration among a plurality of preconfigured configured grant grant configurations. The DCI includes a first indication domain and at least one first class domain. The number of bits of a type of domain is determined by the activated or deactivated configured configuration. The first indication field indicates an index of the configured configuration. The first indication field is located before the at least one first type field. The DCI is sent.

Based on the foregoing technical solution, by defining the first indication domain before all the first-type domains, the position of the first indication domain in the DCI may not be affected by the length of the first-type domain. That is, the position of the first indication field in the DCI may be fixed. Therefore, the terminal device can resolve the first indication domain based on the fixed position, so that the activated or deactivated configured grant configuration can be accurately determined. When the configured grant grant configuration is activated, the PUSCH is transmitted based on the parameters therein and the DCI; when the configured grant grant configuration is deactivated, the configured grant configuration is released. Therefore, the dynamic grant-free transmission of PUSCH is not affected, which is beneficial to the use of uplink dynamic grant-free transmission in various scenarios.

With reference to the first aspect or the second aspect, in some possible implementation manners, the DCI further includes a new data indicator (NDI) domain, and the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is located before the at least one first-type domain.

When the NDI domain can be used to determine that the DCI is used to activate or deactivate the configured grant configuration, the NDI domain and the first indication domain can be placed together before all the first-type domains. This application does not limit the relative position relationship between the NDI domain and the first indication domain. The NDI domain may be located before or after the first indication domain. The NDI domain and the first indication domain may be adjacent to each other. It may not be adjacent. The protocol may predefine the positions of the NDI domain and the first indication domain in the DCI, so that the terminal device can resolve the NDI domain and the first indication domain based on the fixed location.

In a third aspect, a method for configuring uplink dynamic license-free transmission is provided. The method may be executed by a terminal device, or may be executed by a chip configured in the terminal device.

Specifically, the method includes: receiving DCI, the DCI being used to activate or deactivate a configured grant grant configuration among a plurality of preconfigured configured grant grant configurations, the DCI including a first indication domain and at least one first type domain, the first The number of bits of a type of domain is determined by the activated or deactivated configured grant configuration. The first indication field indicates an index of the configured grant configuration, and the first indication field is located at the last position of the DCI. The activation or deactivation corresponds to the index. Configured grant configuration.

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

Specifically, the method includes generating a DCI, which is used to activate or deactivate a configured grant grant configuration among a plurality of preconfigured configured grant grant configurations. The DCI includes a first indication domain and at least one first class domain. The number of bits of a type of domain is determined by the activated or deactivated configured configuration. The first indication field indicates an index of the configured configuration. The first indication field is located at the last position of the DCI. The DCI is transmitted.

The first indication field is located at the last position of the DCI, and may include: the first indication field occupies some or all of the bits in the last segment of the DCI. The last segment of bits may be, for example, a plurality of predefined bits. For example, if the DCI does not include padding bits, the first indication field may be the last field of the DCI, or it may not be the last field of the DCI, but it is still located in the last bit. In the 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 inspections, the network device may design multiple DCIs sent to the same terminal device to the same length. At this time, if the first indication field is placed at the last position of the DCI, the position of the first indication field in the DCI can be considered to be fixed.

Based on the above technical solution, by defining the first indication domain at the last position of the DCI, the position of the first indication domain in the DCI may not be affected by the length of the first type domain. That is, the position of the first indication field in the DCI may be fixed. Therefore, the terminal device can resolve the first indication domain based on the fixed position, so that the activated or deactivated configured grant configuration can be accurately determined. When the configured grant grant configuration is activated, the PUSCH is transmitted based on the parameters therein and the DCI; when the configured grant grant configuration is deactivated, the configured grant configuration is released. Therefore, the dynamic grant-free transmission of PUSCH is not affected, which is beneficial to the use of uplink dynamic grant-free transmission in various scenarios.

With reference to the third aspect or the fourth aspect, in some possible implementation manners, the DCI further includes a new data indicator (NDI) domain, and the NDI domain is used to determine whether DCI is used to activate or deactivate a configured grant grant configuration , And the first indication domain and the NDI domain are both located at the last position of the DCI.

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

It should be understood that the relative position relationship between the NDI domain and the first indication domain is not limited in this application, and the NDI domain may be located before the first indication domain or after the first indication domain. The protocol may predefine the positions of the NDI domain and the first indication domain in the DCI, so that the terminal device can resolve the NDI domain and the first indication domain based on the fixed location.

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

Correspondingly, in combination with the second aspect or the fourth aspect, in some possible implementation manners, in a case where the DCI is used to activate a configured grant, the method further includes: receiving a PUSCH based on the DCI and the activated configured grant grant .

That is, the terminal device and the network device can 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 where the DCI is used to deactivate a configured grant, the method further includes: deactivating (or, in other words, releasing) the configured grant grant configuration.

That is, the terminal device deactivates the configured grant configuration, which means that the terminal device no longer sends a PUSCH based on the configured grant configuration, and the network device no longer receives the PUSCH based on the deactivated configured grant configuration.

According to a fifth aspect, a data transmission method is provided. The method may be executed by a terminal device, or may be executed by a chip configured in the terminal device.

Specifically, the method includes: receiving DCI, the DCI is used for retransmission scheduling, the DCI includes a first indication field and at least one first type field, and the number of bits of the first type field is configured by the regranting configured grant grant configuration It is determined that the first indication domain is used to determine the configured grant configuration, the first indication domain is located before the at least one first type domain; the configured grant configuration determined according to the first indication domain and the DCI retransmission transmission block.

According to a sixth aspect, a data transmission method is provided. The method may be executed by a terminal device, or may be executed by a chip configured in the terminal device.

Specifically, the method includes: sending DCI, the DCI is used for retransmission scheduling, the DCI includes a first indication field and at least one first type field, and the number of bits of the first type field is configured by the configured grant for retransmission It is determined that the first indication domain is used to determine the configured grant configuration, and the first indication domain is located before the at least one first-type domain; the configured grant configuration determined according to the first indication domain and the DCI receive retransmission transmission Piece.

Based on the foregoing technical solution, by defining the first indication domain before all the first-type domains, the position of the first indication domain in the DCI may not be affected by the length of the first-type domain. That is, the position of the first indication field in the DCI may be fixed. Therefore, the terminal device can parse the first indication domain based on the fixed location. As a result, the terminal device can accurately determine the configured grant configuration used for retransmission. Therefore, the terminal device can retransmit the transmission block according to some parameters in the DCI and the configured grant configuration, so as to realize the retransmission of data and help improve the overall reliability of data transmission.

With reference to the fifth aspect or the sixth aspect, in some possible implementation manners, the DCI further includes a new data indication NDI domain, the NDI domain indicates that the DCI is used for retransmission scheduling, and the NDI domain is located in the at least one first Before the class domain.

When the NDI domain is available for determining that the DCI is used for retransmission scheduling, the NDI domain and the first indication domain may be placed together before all the first-type domains. This application does not limit the relative position relationship between the NDI domain and the first indication domain. The NDI domain may be located before or after the first indication domain. The NDI domain and the first indication domain may be adjacent to each other. It may not be adjacent. The protocol may predefine the positions of the NDI domain and the first indication domain in the DCI, so that the terminal device can resolve the NDI domain and the first indication domain based on the fixed location.

According to a seventh aspect, a data transmission method is provided. The method may be executed by a terminal device, or may be executed by a chip configured in the terminal device.

Specifically, the method includes: receiving DCI, the DCI is used for retransmission scheduling, the DCI includes a first indication field and at least one first type field, and the number of bits of the first type field is configured by the regranting configured grant grant configuration It is determined that the first indication field is used to determine the configured grant configuration, and the first indication field is located at the last position of the DCI; the configured grant configuration determined according to the first indication field and the DCI retransmission transmission block.

According to an eighth aspect, a data transmission method is provided. The method may be executed by a network device, or may be executed by a chip configured in the network device.

Specifically, the method includes: sending DCI, the DCI is used for retransmission scheduling, the DCI includes a first indication field and at least one first type field, and the number of bits of the first type field is configured by the configured grant for retransmission It is determined that the first indication domain is used to determine the configured grant configuration, and the first indication domain is located at the last position of the DCI; the configured grant configuration determined according to the first indication domain and the DCI receive a retransmitted transmission block.

Based on the above technical solution, by defining the first indication domain at the last position of the DCI, the position of the first indication domain in the DCI may not be affected by the length of the first type domain. That is, the position of the first indication field in the DCI may be fixed. Therefore, the terminal device can parse the first indication domain based on the fixed location. As a result, the terminal device can accurately determine the configured grant configuration used for retransmission. Therefore, the terminal device can retransmit the transmission block according to some parameters in the DCI and the configured grant configuration, so as to realize the retransmission of data and help improve the overall reliability of data transmission.

With reference to the seventh aspect or the eighth aspect, in some possible implementation manners, the DCI further includes a new data indication NDI domain, the NDI domain indicates that the DCI is used for retransmission scheduling, and both the first indication domain and the NDI domain are Located at the end of the DCI.

The first indication field is located at the last position of the DCI, and may include: the first indication field occupies some or all of the bits in the last segment of the DCI. The last segment of bits may be, for example, a plurality of predefined bits. For example, when the DCI does not include a zero-padded bit, the first indication field may be the last field of the DCI, or it may not be the last field of the DCI, but it is still located in the last bit; in the DCI In the case where the zero-padded bits are included, the first indication field may be located after all the zero-padded bits.

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

With reference to any one of the first aspect to the eighth aspect, in some possible implementation manners, the first indication domain is an HPN domain.

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

With reference to any one of the first aspect to the eighth aspect, in some possible implementation manners, 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 grant configuration or used for retransmission scheduling according to the type of the RNTI that scrambles the DCI. Thereafter, the terminal device may further determine whether the DCI is specifically used to activate the configured grant grant configuration, or to deactivate the configured grant grant configuration, or is used for retransmission scheduling according to the NDI domain in the DCI.

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

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

In a ninth aspect, a communication device is provided, including each module or unit for performing the method in any one of the possible implementation manners of the first aspect, the third aspect, the fifth aspect, or the seventh aspect.

In a tenth aspect, a communication device is provided, including a processor. The processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in any one of the possible implementation manners of the first aspect, the third aspect, the fifth aspect, or the seventh aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is 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 manner, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface may be an input / output interface.

Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

According to an eleventh aspect, a communication device is provided, including each module or unit for performing a method in any one of the possible implementation manners of the second aspect, the fourth aspect, the sixth aspect, or the eighth aspect.

According to a twelfth aspect, a communication device is provided, including a processor. The processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in any one of the possible implementation manners of the second aspect, the fourth aspect, the sixth aspect, or the eighth aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is 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 manner, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface may be an input / output interface.

Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

In a thirteenth aspect, a processor is provided, including: an input circuit, an output circuit, and a 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 executes any one of the first aspect to the eighth aspect and any possible implementation manner of the first aspect to the eighth aspect. Method.

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, and various logic circuits. An input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver, and a signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter, and the input circuit and output The circuits may be the same circuit, which are used as input circuits and output circuits respectively at different times. The embodiments of the present application do not limit specific implementations of the processor and various circuits.

In a fourteenth aspect, a processing device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the first aspect to the eighth aspect and any possible implementation manner of the first aspect to the eighth aspect. Methods.

Optionally, there are one or more processors, and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory is separately provided from the processor.

In the specific implementation process, the memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated on the same chip as the processor, or may be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the way of setting the memory and the processor.

It should be understood that the related data interaction process, for example, sending instruction information may be a process of outputting instruction information from a processor, and receiving capability information may be a process of receiving input capability information by a processor. Specifically, the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver. Among them, the transmitter and the receiver may be collectively referred to as a transceiver.

The processing device in the fourteenth aspect may be a chip, and the processor may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented, the processor may be a general-purpose processor, which is implemented by reading software codes stored in a memory. The memory may be integrated in the processor, may be located outside the processor, and exist independently.

According to a fifteenth aspect, a computer program product is provided. The computer program product includes a computer program (also referred to as code or instructions), and when the computer program is executed, causes a computer to execute the first aspect to The eighth aspect and the method in any one of the possible implementation manners of the first to eighth aspects.

According to a sixteenth aspect, a computer-readable medium is provided, where the computer-readable medium stores a computer program (also referred to as code, or instructions) that when executed on a computer, causes the computer to execute the first aspect to The eighth aspect and the method in any one of the possible implementation manners of the first to eighth aspects.

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

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a communication system applicable to a method provided by an embodiment of the present application; FIG.

2 is a schematic flowchart of a method for configuring uplink dynamic exemption authorization transmission according to an embodiment of the present application;

FIG. 3 shows an example of the arrangement order of each domain in DCI;

FIG. 4 shows an example before moving the first indication domain to all domains of the first type;

FIG. 5 shows an example before moving both the first indication domain and the NDI domain to all the first-type domains;

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

FIG. 7 shows an example of moving the first indication field to the last position of the DCI;

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

FIG. 9 shows an example of moving both the HPN domain and the NDI domain to the last position of the DCI;

FIG. 10 is a schematic diagram of an arrangement order of domains in DCI format 0_1 defined in NR;

FIG. 11 to FIG. 14 are schematic diagrams showing the arrangement order of each domain in the DCI format 0_1 obtained after moving the HPN domain and the NDI domain;

15 is a schematic flowchart of a data transmission method according to another embodiment of the present application;

16 is a schematic block diagram of a communication device according to an embodiment of the present application;

17 is a schematic structural diagram of a terminal device according to 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 solutions in this application will be described below with reference to the drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a global mobile communication (GSM) system, a code division multiple access (CDMA) system, and a broadband code division multiple access (wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Global Interoperability for Microwave Access (WiMAX) communication system, 5th generation in the future, 5G) system or new radio (NR).

To facilitate understanding of the embodiments of the present application, a communication system applicable to the method provided by the embodiments of the present application will be described in detail with reference to FIG. 1. FIG. 1 shows a schematic diagram of a communication system 100 applicable to the method provided by an embodiment of the present application. As shown, the communication system 100 may include at least one network device, such as a base station (gNB) in a 5G system shown in FIG. 1; the communication system 100 may further include at least one terminal device, as shown in FIG. 1 User equipment (UE) 1 to UE 6. The network equipment and each terminal equipment 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. Therefore, the gNB and UE1 to UE6 in FIG. 1 may constitute a communication system.

Terminal devices in the communication system 100, such as UE4 to UE6, may also constitute a communication system. For example, UE4 may control UE5 and UE6 to execute corresponding instructions. This application does not limit this.

It should be understood that the network device in the communication system may be any device having a wireless transceiver function. The network equipment includes but is 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 NodeB, or home NodeB, HNB), baseband unit (BBU), wireless fidelity (WiFi) system Access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be 5G, such as, NR, gNB in the system, or transmission point (TRP or TP), one or a group of base stations (including multiple antenna panels) in the 5G system, or an antenna panel, or a network node constituting a gNB or a transmission point , Such as a baseband unit (BBU), or a distributed unit (DU).

In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include a radio frequency unit (radio unit, RU). CU implements some functions of gNB, DU implements some functions of gNB, for example, CU implements radio resource control (RRC), packet data convergence layer protocol (PDCP) layer functions, and DU implements wireless chain Functions of radio control (RLC), media access control (MAC) and physical (PHY) layers. Because the information of the RRC layer will eventually become the information of the PHY layer, or transformed from the information of the PHY layer, under this architecture, higher-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU. , Or, sent by DU + CU. It can 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 can be divided into network equipment in an access network (RAN), or the CU can be divided into network equipment in a core network (CN), which is not limited in this application.

It should also be understood that the terminal equipment in the wireless communication system may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, User terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may be a mobile phone, a tablet, a computer with a wireless transmitting and receiving function, a virtual reality (VR) terminal device, or an augmented reality (AR) terminal. Equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation security ( wireless terminals in transportation, wireless terminals in smart cities, wireless terminals in smart homes, and so on. The embodiment of the present application does not limit the application scenario.

It should also be understood that FIG. 1 is only a simplified schematic diagram for ease of understanding. The communication system 100 may further include other network devices or other terminal devices, which are not shown in FIG. 1.

In order to facilitate understanding of the embodiments of the present application, a few concepts involved in the following are briefly explained first.

1. DCI format 0_1: can be used to activate or deactivate the authorized configuration of the second type of configuration (configured grant configuration), so that the terminal device can perform PUSCH transmission without dynamic authorization, and can also be used for retransmission scheduling. The DCI format 0_1 may include a DCI format indicator (DCI format) domain, a carrier indicator (carrier) indicator, a bandwidth part indicator (BWP) indicator, and a frequency domain resource assignment domain (frequency resource domain). ), Time domain resource assignment domain (time domain resource assignment), frequency hopping flag (frequency hopping flag), modulation and coding scheme (modulation and coding scheme (MCS)), new data indicator (NDI) domain, redundancy The version (redundancy version) field, the hybrid automatic repeat request (HARQ) process number (HARQ process number, HPN) field, etc. are not listed here for brevity.

It should be understood, the above-mentioned fields included in DCI format 0_1 merely exemplary, DCI format 0_1 the specific format and content reference NR protocol (e.g., Third Generation Partnership Project ^{(3 rd generation partnership project, 3GPP} ) TS 38.212). Of course, this application does not exclude the possibility of making changes to DCI format 0_1 in future agreements.

2. New data indication (NDI) domain: In general, the NDI domain can be used to indicate that the resources scheduled by the DCI this time are used for initial transmission or retransmission. In the embodiment of the present application, the DCI can be used to activate or deactivate the authorization configuration of the second type configuration, so that the terminal device can perform PUSCH transmission without dynamic authorization, and can also be used for retransmission scheduling. The NDI domain can be used to determine whether the DCI is used for activating or deactivating the second type of configured grant configuration or for retransmission scheduling.

Specifically, the NDI field may include 1 indication bit. When the indication bit is "1", the DCI can be considered for retransmission scheduling; when the indication bit is "0", it can be further combined with other fields in the DCI to determine whether the DCI is used to activate or deactivate the second Class configured grant configuration. For example, when the most significant bit (MSB) in the HPN domain is 0 and the RV domain is all 0s, or when the HPN domain is all 0s and the RV domains are all 0s, the DCI is used to activate the second Authorization configuration of class configuration; 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 and the RV domain is all When the MCS domain is all 0 and the frequency domain resource assignment domain is all 1, the DCI is used to deactivate the authorization configuration of the second type configuration.

The protocol can pre-define how to determine whether the DCI is used to activate or deactivate the second-type configured grant configuration or retransmission scheduling according to each domain in the DCI.

3. HARQ process number (HPN) field: Generally, the HPN field can 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 a configured grant configuration, and may also be used for 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 domain is "0", the terminal device may further determine whether the DCI domain is used to activate or deactivate the configured grant configuration in conjunction with other domains in the DCI. When only the MSB in the HPN domain is used to determine whether the DCI is used to activate or deactivate the configured authorization configuration, the other 3 bits in the HPN domain can also be used to determine the index of the configured grant grant configuration that is activated or deactivated by the DCI (index).

4. Dynamic authorization-free transmission: The uplink transmission of the terminal equipment does not need to be completed through the scheduling of the network equipment. Specifically, when the uplink data arrives, the terminal device does not need to send a scheduling request (SR) to the network device and waits for a dynamic grant of the network device. Instead, it can directly use the transmission resources and The specified transmission parameters send uplink data to the network device.

In NR, uplink dynamic grant-free transmission can be divided into two categories. That is, PUSCH transmission based on the first type of configuration authorization (Type1PUSCH transmission with a configured or grant, or Type1configured grant configuration, or Type1configured grant, PUSCH transmission) and PUSCH transmission based on the second type configuration authorization (Type2PUSCH transmission withwith a configured) grant, or Type 2configured grant configuration, or Type 2configured grant PUSCH transmission).

The network device may configure configured grant grant configuration through high-level signaling, such as the configured authorized configuration control element (ConfiguredGrantConfiginformation element, ConfiguredGrantConfigIE) carried in a radio resource control (RRC) message. The terminal device may determine whether the configured grant configuration configured by the ConfiguredGrantConfigIE is the first type configured or the second type configured according to the parameters configured in the ConfiguredGrantConfigIE.

The two types of uplink-free dynamic authorization transmission are described in detail below.

In PUSCH transmission based on the first type of configuration authorization, the parameters configured in the configured grant configuration may include, for example, the period of time-frequency resources, open-loop power control related parameters, waveforms, redundant version sequences, repetition times, frequency hopping modes, Resource allocation type, number of HARQ processes, demodulation reference signal (DMRS) related parameters, modulation coding scheme (MCS) table, resource block group (RBG) size, time domain resources, All transmission resources and transmission parameters including frequency domain resources, MCS, etc. 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 can also be called fully RRC-configured UL grant.

In PUSCH transmission based on the second type of configuration authorization, the parameters configured in the configured grant configuration may include, for example, the period of time-frequency resources, open-loop power control related parameters, waveforms, redundant version sequences, repetition times, frequency hopping modes, Transmission resources and transmission parameters including resource allocation type, number of HARQ processes, DMRS related parameters, MCS table, RBG group size, etc. In a specific example, the parameters configured in configured grant configuration can be specifically referred to, for example, specific provisions in the NR protocol 3GPP TS 38.331. Thereafter, the network device can activate a configured grant configuration via DCI for PUSCH transmission. The DCI can carry an index of the configured configured grant. The DCI may further configure other transmission resources and transmission parameters including time domain resources, frequency domain resources, DMRS port numbers, MCS, and the like. Therefore, after receiving the configured grant configuration described above, the terminal device cannot immediately perform PUSCH transmission. After receiving the DCI, it can determine the activated configured grant configuration and combine the transmission resources and transmission parameters indicated in the DCI. , Transmitting the PUSCH on the configured time-frequency resource based on the configured transmission parameters.

In other words, the terminal device activates a configured grant configuration, which means that the parameters in this configured grant configuration are valid. The terminal device may combine the parameters in the configured grant configuration and the parameters in the DCI that activates the configured grant configuration to determine transmission resources and transmission parameters for transmitting the PUSCH, so that PUSCH transmission can be performed. Therefore, when DCI activates a configured grant configuration, it can be considered that the DCI is used to activate a dynamic authorization-free transmission based on the configured grant configuration.

In addition, network devices can also use DCI to deactivate the configured grant. Specifically, the DCI may carry a deactivated configured grant grant configuration index. The terminal device can determine the deactivated configured grant configuration based on the index.

In other words, the terminal device deactivates a configured grant configuration, which means that the parameters in the configured grant configuration are invalidated. At the same time, the terminal device can deactivate (or release) the configured grant configuration. Therefore, when DCI deactivates a configured grant configuration, it can be considered that the DCI is used to deactivate the dynamic authorization-free transmission based on the configured grant configuration.

For the convenience of description below, the second type of configured grant grant configuration mentioned above is referred to simply as “configured grant configuration” without special instructions.

In the embodiment of the present application, the DCI used to activate the configured grant may be a DCI scrambled by a specific type of RNTI. When the terminal device receives the DCI, it can determine whether the DCI is a DCI configured to activate or deactivate a configured grant based on the type of the RNTI that scrambles the DCI, or whether it is used to activate dynamic authorization-free transmission. The specific type of RNTI may be, for example, a CS-RNTI, or another RNTI that is exempt from dynamic authorization transmission, or a RNTI dedicated for transmission configured by a higher layer. This application does not limit this.

It should be noted that the network device may scramble the DCI through a certain RNTI, which specifically may mean that the network device scrambles a cyclic redundancy check (CRC) bit in the DCI through a certain RNTI. If the terminal device successfully descrambles the CRC based on an RNTI, the information in the DCI can be obtained; if the terminal device fails to descramble the CRC based on an RNTI, it indicates that the DCI is not scrambled based on the RNTI, or the DCI is not Sent to this terminal device.

5. HARQ process number: HARQ uses a stop-and-wait protocol to send data. The above line transmission is taken as an example. After the terminal device sends a transport block (TB), it stops and waits for confirmation information. The network device can use 1-bit information to confirm (acknowledgement, ACK) or negative (negative acknowledgement, NACK) the transport block. However, the terminal device stops and waits for confirmation after each transmission, which will result in very low throughput. Therefore, the terminal device can use multiple parallel HARQ processes. When one HARQ process is waiting for confirmation information, the terminal device can continue to send data using another HARQ process.

The HARQ process number is also called a HARQ process identifier (ID). A HARQ process number can be used to uniquely specify a HARQ process. After the terminal device performs channel coding on the transmission block, the data obtained by the channel coding may be registered in a buffer and waited for transmission. There can be a one-to-one correspondence between the transport blocks in the cache and the HARQ process, and each transport block can correspond to one HARQ process. The correspondence between the transport block and the HARQ process can be reflected 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, when a transmission block is transmitted based on the time-frequency resource indicated in the DCI, the HARQ process number corresponding to the transmission block is the HARQ process number carried in the DCI. Therefore, both the network device and the terminal device can determine the correspondence between the time-frequency resource and the HARQ process number.

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

In the embodiment of the present application, the network device may perform retransmission scheduling for the terminal device. Specifically, the network device may configure parameters for retransmission for the terminal device through configured grant. The parameters may include, for example, one of waveform, resource allocation type, frequency hopping mode, DMRS-related parameters, MCS table, and RBG size. Multiple. Because the network device can configure multiple configured grant configurations for the terminal device, the multiple configured grant configurations can have a corresponding relationship with the HARQ process number, so that the terminal device can determine the configured grant grant configuration for retransmission based on the HARQ process number indicated in the DCI To determine the parameters used for retransmission.

6. Transport block (TB): A transport block can be a data block from a higher layer. A transmission block may include, for example, a data block of a media access control (MAC) protocol data unit (PDU). This data block may be transmitted on a time unit or may be retransmitted by HARQ. unit. In the existing LTE and NR, for each terminal device, a maximum of two transport blocks can be sent in each time unit. By way of example and not limitation, the time unit is a transmission time interval (TTI).

As mentioned earlier, in a wireless communication system, as shown in Figure 1, network devices can configure multiple second-class configured grants for terminal devices through high-level signaling, and can be activated or deactivated through DCI. one of. The terminal device can determine the activated or deactivated configured grant configuration according to the HPN domain in the DCI.

However, because the length of some domains in DCI is not fixed, the positions of HPN domains in different DCIs are not necessarily the same, or in other words, not fixed. The terminal device cannot resolve the information in the HPN domain based on a fixed location, and it cannot determine the activated configured grant configuration.

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

In order to facilitate understanding of the embodiments of the present application, before introducing the embodiments of the present application, the following points are described.

First, in the embodiments of the present application, there are multiple references to moving a certain domain. For example, "move the first indication field" or "move the first indication field to" a certain position. It should be understood that this does not mean that the network device will "move" the first indication field, but rather that the position of the first indication field in the DCI used in the embodiment of the present application is compared to its existing position The position in the DCI looks like it has been moved. In the embodiment of the present application, the network device generates the required information according to the DCI format (for example, the format described in any one of FIGS. 4-9 and 11-14) after moving the first indication domain position. DCI. Correspondingly, after receiving the DCI, the terminal device also analyzes each domain in the DCI according to the corresponding DCI format.

Secondly, in the embodiment of the present application, multiple places are related to high-level parameters. This high-level parameter can be carried through high-level signaling. The high-level signaling may be, for example, an RRC message or other high-level signaling, which is not limited in this application.

Third, in the embodiments of the present application, the "indication" may include a direct instruction and an indirect instruction, and may also include an explicit instruction and an implicit instruction. The information indicated by certain information (such as the configuration information described below) is referred to as to-be-instructed information. In the specific implementation process, there are many ways to instruct the instruction information. For example, but not limited to, the to-be-instructed instruction can be directly indicated Information, such as the information to be indicated or an index of the information to be indicated. The information to be indicated may also be indicated indirectly by indicating other information, where there is an association relationship 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 other parts of the information to be indicated are known or agreed in advance. For example, an indication of specific information may also be implemented by means of an arrangement order of each piece of information agreed in advance (such as stipulated in a protocol), thereby reducing the indication overhead to a certain extent.

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

Fifth, in the embodiments shown below, "pre-acquisition" may include indication or pre-definition by network device signaling, for example, protocol definition. Among them, "pre-defined" can be achieved by pre-saving corresponding codes, forms, or other methods that can be used to indicate related information in devices (for example, terminal devices and network devices), and this application does not make specific implementations thereof. limited.

Sixth, "saving" involved in the embodiments of the present application may refer to saving in one or more memories. The one or more memories may be provided separately or integrated in an encoder or a decoder, a processor, or a communication device. The one or more memories may also be partly provided separately and partly integrated in a decoder, a processor, or a communication device. The type of the memory may be any form of storage medium, which is not limited in this application.

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

Eighth, "at least one" means one or more, and "multiple" means two or more. "And / or" describes the association relationship of related objects, and indicates that there can be three kinds of relationships, for example, A and / or B can represent: the case where A exists alone, A and B exist simultaneously, and B alone exists, where A, B can be singular or plural. The character "/" generally indicates that the related objects are an "or" relationship. "At least one or more of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one (a), a, b, or 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, where a, b, and c may be single or multiple.

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

It should be understood that the method provided in this application may be applicable to a wireless communication system, for example, the wireless communication system 100 shown in FIG. 1. There is a wireless communication connection between two communication devices in the wireless communication system. One of the two communication devices may correspond to any one of UE1 to UE6 shown in FIG. 1. Any one of UE1 to UE6 in 1 may also be a chip configured in any one of UE1 to UE6; the other communication device of the two communication devices may correspond to that shown in FIG. 1 The gNB shown may be, for example, the gNB in FIG. 1 or a chip configured in the gNB.

In the following, without loss of generality, the embodiment of the present application will be described in detail by taking the interaction between a terminal device and a network device as an example. It can be understood that any terminal device in the wireless communication system can communicate with one or more network devices having a wireless communication connection based on the same method. This application does not limit this.

FIG. 2 is a schematic flowchart of a configuration method 200 for uplink dynamic exemption authorization transmission provided by an embodiment of the present application from the perspective of device interaction. As shown, the method 200 may include steps 210 to 240. Each step in the method 200 is described in detail below.

Step 210: The network device sends configuration information, and the configuration information is used to configure multiple 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 through high-level signaling (that is, an example of configuration information), for example. In this embodiment, the configured grant configuration may be the second type of configured grant configuration described above. Each configured grant configuration can include the time-frequency resource period, open-loop power control related parameters, waveforms, redundant version sequences, repetition times, frequency hopping modes, resource allocation types, HARQ processes, DMRS related parameters, MCS tables, Transmission resources and transmission parameters including RBG group size.

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

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

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

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

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

It should be understood that the CS-RNTI is only an example of the above-mentioned specific type of RNTI, and should not be construed as limiting this application in any way. This particular type of RNTI may also include other RNTIs dedicated to dynamic authorization-free transmission or high-level configuration transmission. The protocol can predefine the functions of different types of RNTI scrambled DCIs. For example, one type of RNTI scrambled DCI can be defined to activate or deactivate the configured grant grant configuration, or another type of RNTI scrambled DCI can be defined For retransmission scheduling. The network device may generate DCI based on the predefined RNTI type and the function of the DCI, and the terminal device may also analyze the DCI based on the predefined RNTI type and the function of the DCI.

To facilitate the description of this embodiment, the domains in the DCI may be divided into a first-type domain and a second-type domain.

The number of bits of the first type of domain may be related to high-level parameters. In other words, the number of bits in the first type of domain may change due to different high-level parameters. In other words, when DCI is used to activate or deactivate different configured grant configurations, the number of bits contained in the first type of domain may change. That is, the length of the first type domain may be different in different DCIs. Specifically, the number of bits of the first-type domain is related to the parameters configured in the activated or deactivated configured grant configuration. For example, the parameters may specifically include the period of time domain resources, open-loop power control related parameters, waveforms, redundant version sequences, repetition times, frequency hopping modes, resource allocation types, number of HARQ processes, parameters related to dereferencing reference signals, One or more of the MCS table and RBG size.

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

The number of bits of the second type of domain may be independent of high-level parameters, or the number of bits of the second type of domain does not change due to different high-level parameters. That is, when DCI is used to activate or deactivate different configured grant configurations, the number of bits contained in the second type of domain will not change. That is, the length of the second-type domain in different DCIs may be fixed. Specifically, the number of bits of this second type of domain is independent of the parameters configured in the activated or deactivated configured grant configuration.

For example, when the format of DCI is DCI format 0_1, the format indication domain, carrier indication domain, UL / SUL indication domain, BWP indication domain, time domain resource assignment domain, MCS domain, RV domain, HPN domain, NDI domains and the like can all belong to the second type of domain.

However, it should be understood that the domains and categories in the DCI format 0_1 listed above are just examples, and should not be construed as limiting this application. This application does not exclude the possibility of defining one or more second-type domains as first-type domains in future agreements, nor does it exclude the possibility of defining one or more first-type domains as second-type domains .

In this embodiment, the first type of domain may include the foregoing frequency hopping identification domain and frequency domain resource assignment domain.

In this embodiment, the second type of domain may include a first indication domain, and the first indication domain may be used to indicate an activated or deactivated configured grant grant configuration index. By way of example and not limitation, the first indication domain is an HPN domain. Of course, the first indication field may also be another field that can be used to indicate the activated or deactivated configured index. For example, it can be a newly defined domain in DCI, or other domains can be reused. This application does not limit this. Optionally, the second type of domain further includes an NDI domain.

As an optional embodiment, the DCI may inherit the DCI format defined in the existing protocol. For the convenience of differentiation and description, the arrangement of the first indication field in the DCI when the DCI format defined in the existing protocol is used is described as the first case.

In case one, the network device may generate the DCI based on the predefined format. The pre-defined DCI format can be used to activate or deactivate the configured grant configuration, it can also be used for retransmission scheduling, and it can also be used to dynamically schedule PUSCH. This application does not limit this.

In the predefined DCI format, there is at least one first-type domain before the first indication field, and there may be one or more first-type domains, one or more second-type domains, or one or more after the first indication field. Multiple zero-padded bits.

The zero-padded bits are added to the DCI to ensure that multiple DCIs sent by the network device to the same terminal device have the same length, so as to reduce the number of blind inspections of the terminal device. In one implementation manner, 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 manner, the network device may determine whether the DCI generated each time needs to be zero-added according to the length of the longest DCI.

FIG. 3 shows an example of the arrangement order of the domains in the DCI. As shown, the DCI may include at least one first-type domain and at least one second-type domain. It should be noted that the zero-padded bits in the figure are only for illustration, and do not represent that all DCIs include zero-padded bits.

It can be seen that if the first indicator domain is located behind at least one domain of the first type, the position of the first indicator domain may change due to different high-level parameters. For example, the first indication field is located after the frequency hopping identification field. In the case where the frequency hopping mode parameter is configured and the frequency hopping mode parameter is not configured in the upper layer, the positions of the first indication field respectively obtained are staggered by one bit. If there are more first-type domains before the first indication domain, the number of bits of the first indication domain staggered in different DCIs may be larger. Because the terminal device cannot determine the location of the first indication domain, it cannot parse the information in the first indication domain, and thus cannot determine the activated or deactivated configured grant configuration.

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

Method 1: move the first indication domain before all domains of the first category; or

Method 2: Move the first indication field to the last position of the DCI.

The above two methods are described in detail below.

method one,

The first indication domain is moved before all the first-type domains, or the first indication domain may be moved before the first first-type domain. Moving the first indication domain before the first type domain may include: moving the first type domain to an arbitrary position before the first type domain. FIG. 4 shows an example before moving the first indication domain in the DCI shown in FIG. 3 to all domains of the first type. It should be understood that what is shown in the figure is only an example, and the network device may move the first indication domain to any position before all the first-type domains. The protocol may define in advance which position the first indication domain is moved to before the first type domain. For example, move the first indication domain to the last domain before the domain of the first category, or move the first indication domain to the first domain before the domain of the first category, or move the first indication domain to the first category A specific position before the domain is not limited in this application. When the protocol defines that the first indication domain is moved to a position before the first type domain, the network device may generate DCI based on the definition, and the terminal device may also analyze the first indication domain in the DCI based on the definition.

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

Then, in one implementation manner, the network device may also move the NDI domain before all the first-type domains. FIG. 5 shows an example before moving both the HPN domain and the NDI domain in the DCI shown in FIG. 3 to all the first-type domains. It should be understood that the figures shown are merely examples, and the order in which the NDI domain and the HPN domain are arranged in the DCI is not limited in the embodiment of the present application. For example, the HPN domain can 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 defined in advance by the protocol, and this application does not limit this. In addition, the embodiment of this application does not limit the sequence in which other second-type domains are arranged in the DCI.

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

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

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

Way two,

Moving the first indication field to the last position of the DCI may include: moving the first indication field to the last bit of the DCI, and the first indication field may occupy some or all of the bits in the last segment. The last segment of bits may be, for example, a plurality of predefined bits. For example, in the case that the DCI does not contain zero-padded bits, the first indication field may be moved to the last field of the DCI, and the first indication field may be used as the last field. The last bit of the DCI may not occupy the last bit; or it may not be moved after the last field of the DCI, but it is still located in the last bit. In a case where the DCI includes a zero-padding bit, the first indication field may be moved after all the zero-padding bits, or the first indication field may be moved after the last zero-padding bit. It can be understood that the bits after the zero-padded bits are located in the last bit of the DCI.

When the protocol defines that the first indication field is moved to the last bit of the DCI so that the terminal device can parse the first indication field, it can further define which bits of the first indication field are placed in the last bit. Therefore, the position of the first indication domain in the DCI can be determined. The terminal device may resolve the first indication domain based on the location.

Specifically, if the DCI includes zero-padded bits, it can be considered that the length of the DCI does not reach a predefined length or is not the longest DCI among all DCIs. In this case, if the first indication field is moved after all zero-padded 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 after moving the first indication field in the DCI shown in FIG. 3 to all zero-padded bits.

If the DCI does not include zero-padded bits, the length of the DCI may be considered as a predefined length, or the DCI is the longest DCI among all DCIs. In this case, if the first indication domain is moved after the last domain of the DCI, the first indication domain may become the last domain 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.

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

In one implementation, the network device may move the HPN domain and the NDI domain to the last position of the DCI. In the case that the DCI contains zero-padding bits, the network device can move both the HPN domain and the NDI domain 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-padded bits. It should be understood that the figures shown are merely examples, and the order in which the NDI domain and the HPN domain are arranged in the DCI is not limited in the embodiment of the present application. The NDI domain may be the last domain of DCI. At this time, the last bit of the DCI may be the NDI domain; the HPN domain may also be DCI to the last domain. At this time, the last bit of the DCI may be the HPN domain. The last bit. In other words, the NDI domain can be located before or after the HPN domain. The relative position relationship between the NDI domain and the HPN domain may be defined in advance by the protocol, and the order of the NDI domain and the HPN domain is not limited in this embodiment of the present application. In addition, the embodiment of this application does not limit the sequence in which other second-type domains are arranged in the DCI.

In the case that the DCI does not contain the zero-padded bits, the network device may move the HPN domain and the NDI domain to the last position of the DCI, for example, move both the HPN domain and the NDI domain after the last domain. FIG. 9 shows an example of moving the HPN domain and the NDI domain in the DCI shown in FIG. 3 to the last position of the DCI. It should be understood that the figures shown are merely examples and should not be construed as limiting this application in any way. The order of the NDI domain and the HPN domain is not limited in this embodiment of the present application. For example, the HPN domain may be located before the NDI domain or after the HPN domain. That is, the HPN domain can become the last domain of DCI, or the NDI domain can also become the last domain of DCI. The relative position relationship between the NDI domain and the HPN domain may be defined in advance by the protocol, and this application does not limit this. In addition, the embodiment of this application does not limit the sequence in which other second-type domains are arranged in the DCI.

In another implementation manner, the network device may also move the NDI domain before all the first-type domains. That is, the network device can move the NDI domain to any position before the first first-type domain. The protocol can define in advance where the NDI domain is located before the first first-type domain.

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

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

Based on the methods listed above, the following uses DCI format 0_1 in NR as an example to explain the process of network equipment generating DCI.

FIG. 10 is a schematic diagram of an arrangement order of each domain in the DCI format 0_1 defined in the NR. The figure is only schematic, and only shows the arrangement order of some domains in DCI. The HPN domain is an example of the first indication domain. The frequency domain resource assignment domain and frequency hopping identification domain are examples of the first type domain. The remaining domains are of the second type. "..." in the figure indicates an omitted DCI field.

As shown in the figure, both the HPN domain and the NDI domain are after the frequency domain resource assignment domain (that is, an example of the first type 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 manners listed above. FIG. 11 to FIG. 14 are schematic diagrams showing the arrangement order of each domain in the DCI format 0_1 obtained after moving the HPN domain and the NDI domain. Specifically, FIG. 11 shows an example of moving both the NDI domain and the HPN domain to positions before the frequency domain resource assignment domain. FIG. 12 shows an example of moving the NDI domain and the HPN domain to the last position of the DCI when the DCI does not include the zero-padded bits. FIG. 13 shows positions after moving both the NDI field and the HPN field to all zero-padded 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-padded bits.

It should be understood that the figures shown are merely examples and should not be construed as limiting this application in any way. This application does not limit the order in which the NDI domain and the HPN domain are arranged in the DCI. When the NDI domain and the HPN domain are located before all the first-type domains, the NDI domain and the HPN domain may or may not be adjacent, which is not limited in this application.

The manner of moving the first indication domain and the NDI domain listed above is merely an example, and should not be construed as limiting in this application. Based on the same concept, those skilled in the art can also think of other more possible implementations.

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

Optionally, before moving the first indication domain, the method further includes: the network device determines whether to move the first indication domain according to the function of the DCI. Specifically, when the DCI is configured to activate or deactivate a configured grant, the network device may move the first indication domain in the manner described above.

As an optional embodiment, the network device may separately define a DCI format for the DCI that activates or deactivates the configured grant grant configuration, and the DCI generated based on the DCI format may be specifically used to activate or deactivate the configured grant grant configuration. The DCI format can avoid the problem that the position of the first indication field is not fixed.

In a possible design, the first indication domain may be located before all domains of the first type. For the convenience of distinguishing and explaining, the arrangement of the first indication domain in DCI before all the domains of the first type is referred to as case two.

The DCI format under this design may be similar to the result before moving the first indication field to all the first type fields in the first case in the first case, for example, as shown in FIG. 4. It should be understood that FIG. 4 is merely an example, and the first indication domain may be any position before all domains of the first type. The protocol may pre-define where the first indication domain precedes the first-type domain. For example, the first indication domain may be the first domain of DCI, or may be a domain before all domains of the first category, or may be a domain at a specific location before the domain of the first category, which is not described in this application. limited.

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

In an implementation manner, the NDI domain is also located before all the first-type domains. This NDI domain also precedes all first-type domains. The DCI format under this design can be similar to the result before moving the HPN domain and NDI to all the first type domains in the first case, for example, as shown in FIG. 5. However, it should be understood that FIG. 5 is merely an example, and the order of arrangement of the NDI domain and the HPN domain in the DCI is not limited in the embodiment of the present application. The protocol can predefine the relative position relationship between the HPN domain and the NDI domain. For example, the HPN domain can 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 domain is located at the last position of the DCI. Specifically, the NDI domain may be located in the last segment of the DCI, and the NDI domain may occupy some or all of the bits of the last segment. For example, when the DCI does not include zero-padded bits, the NDI domain may be used as the last domain of the DCI. The NDI domain may occupy the last bit of the DCI or may not occupy the last bit; or The NDI domain may not be used as the last domain of the DCI, but is still located in the last bit. In the 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 domain is the last domain of the DCI. It can be understood that the bits after the zero-padded bits fall into the last bit of the DCI.

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

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

In another possible design, the first indicator field may be located at the last position of the DCI. For the convenience of differentiation and description, the arrangement of the first indication field at the last position of the DCI is recorded as the second case.

Specifically, the first indication field may be located in the last bit of the DCI, and the first indication field may occupy part or all of the bits of the last bit. For example, when the DCI does not include zero-padded bits, the first indication field may be used as the last field of the DCI. The first indication field may occupy the last bit of the DCI or may not occupy the last bit. Or, the first indication field may not be used as the last field of the DCI, but is still located in the last bit. In the 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 domain is the last domain of the DCI. It can be understood that the bits after the zero-padded bits fall into the last bit of the DCI. The DCI format under this design may be similar to the result after the first indication field is moved to the last position of the DCI by using the second method in the first case, for example, as shown in FIG. 6 and FIG. 7.

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

Then, in an implementation manner, the HPN domain and the NDI domain are both located at the last position of the DCI. The HPN domain and the NDI are both located in the last position of the DCI, and may include that the HPN domain and the NDI domain are both located in the last bit 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-padded bits of the DCI, and so on. Specifically, when the DCI does not contain zero-padded bits, the HPN field and the NDI field may be the last two fields of the DCI; when the DCI does not contain zero-padded bits, the HPN field and the NDI field may be located in the zero-padded field. After the bit, it can also be the last two fields of the DCI. The HPN domain can be located before or after the NDI domain. This application does not limit this. The DCI format under this design may be similar to the result after moving the first indication domain and the NDI domain to the last position of the DCI in the second case in the first case, for example, as shown in FIG. 8 and FIG. 9.

In another implementation, the NDI domain is located before all domains of the first type. That is, the NDI domain can be located anywhere before the first-type domain is received. The protocol can define in advance where the NDI domain is located before the first first-type domain.

Optionally, the first indication domain and the HPN domain are different domains. For example, the first indication domain may be a newly added domain in DCI, which is used to indicate an index of configured grant. The configured corresponding grant configuration of this index can be a configured grant configuration activated or deactivated by DCI, or 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 domain may also be a domain other than the HPN domain in the DCI. In this case, the network device may define only the location of the first indication domain and the NDI domain, but not the location of the HPN domain. For example, both the first indication domain and the NDI domain are defined at the last position of the DCI, or the first indication domain is defined at the last position of the DCI, the NDI domain is defined before all the first type domains, and so on.

It should be understood that the positions of the first indication field and the NDI field in the DCI format listed above are merely examples, and should not be construed as any limitation in this application. Based on the same concept, those skilled in the art can also think of other more possible designs.

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

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

The network device can scramble the DCI through the specific RNTI described above, such as CS-RNTI. The network device may send the DCI through a physical downlink control channel (PDCCH), for example. The terminal device can receive DCI through blind detection, and descramble based on CS-RNTI to obtain information in DCI.

For specific methods of sending DCI by a network device and receiving DCI by a terminal device, reference may be made to the prior art. For brevity, detailed descriptions of specific processes are omitted.

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

If the terminal device succeeds in descrambling based on the specific RNTI in step 230, the terminal device may determine whether the DCI is used to activate or deactivate a configured DCI or to retransmit scheduling.

The terminal device may further determine whether the DCI is used to activate or deactivate a configured grant configuration or a retransmission scheduling according to a domain such as an NDI domain in the DCI. The specific method for determining whether the DCI is used for activating or deactivating the configured or granted configuration or retransmission scheduling through the NDI domain and other domains in the DCI has been described in detail above. For brevity, it will not be repeated here.

It should be understood that determining whether DCI is used for activating or deactivating configured grant grant configuration or retransmission scheduling through domains such as the scramble type of DCI and the NDI domain is only one possible implementation, and should not constitute any limitation on this application. . For example, a network device may scramble DCI through different types of RNTIs to distinguish between the DCI used to activate or deactivate the configured DCI and the DCI used for retransmission scheduling; for example, the network device may indicate the DCI through other fields This application does not limit this.

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

It can be understood that the one-to-one correspondence between the configured grant and the configuration may be predetermined by the network device and the terminal device. For example, it may be defined in advance, such as a protocol definition, or a network device may instruct a terminal device through high-level signaling, which is not limited in this application.

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

Specifically, the terminal device may determine part of the transmission resources and transmission parameters according to the configured grant configuration indicated by the first indication field, and send the PUSCH in combination with the transmission resources and transmission parameters 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 includes: 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 domain. The network device no longer receives PUSCH based on the deactivated configured grant configuration.

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

Based on the above technical solution, the position of the first indication domain in the DCI is not affected by the length of the first type of domain, and the terminal device can resolve the first indication domain based on the fixed location. Therefore, the terminal device can accurately determine the activated or deactivated configured grant configuration. When the configured grant grant configuration is activated, the PUSCH is transmitted based on the parameters therein and the DCI; when the configured grant grant configuration is deactivated, the configured grant configuration is released. Therefore, PUSCH transmission without dynamic authorization will not be affected, which is beneficial to the use of uplink dynamic authorization-free transmission in various scenarios.

Conversely, if the position of the first indication domain in the DCI is affected by the length of the first type of domain, its position in the DCI cannot be determined. The terminal device may take a long time to find the first indication domain, or may not find the first indication domain. Therefore, it affects PUSCH transmission without dynamic authorization. For example, it may bring a large delay, which is not conducive to the use of uplink dynamic authorization-free transmission in some scenarios that are sensitive to delay.

The above provides a configuration method that can facilitate the terminal device to determine and parse the first indication domain based on a fixed location, so that it can activate or deactivate the configured corresponding to the index based on the configured grant in the first indication domain grant configuration. However, the DCI is not limited to activating or deactivating the configured grant configuration, but can also be used for retransmission scheduling. In addition, when the DCI is used for retransmission scheduling, scrambling may also be performed through the same type of RNTI, such as CS-RNTI. The terminal device can determine the transmission block that needs to be retransmitted and the configured grant grant configuration for retransmission according to the HPN field in the DCI. The configured grant configuration can be used to indicate the parameters used for retransmission. However, because the location of the HPN domain in different DCIs is not necessarily the same, the terminal device cannot parse the information in the HPN domain based on the fixed location, and it cannot determine the transmission blocks that need to be retransmitted and the configured grant grant used for retransmission. .

This application also provides a method for data transmission, so that the terminal device can analyze the HPN domain based on a fixed location, so that it can determine the transmission block that needs to be retransmitted and the configured grant configuration used for retransmission, and retransmit the data based on the configured grant .

FIG. 15 is a schematic flowchart of a data transmission method 300 according to another embodiment of the present application, which is shown from the perspective of device interaction. As shown, the method 300 may include steps 310 to 350. Each step in the method 300 is described in detail below.

In step 310, the network device sends configuration information, and the configuration information is used to configure 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 the method 200 above. Since step 210 has been described in detail in the method 200 above, for brevity, it will not be repeated here.

In step 320, the network device generates a DCI, where the DCI includes a first indication field, and the first indication field is used to indicate a configured grant configuration used for retransmission.

In this embodiment, the DCI can be used for scheduling retransmission. The parameters used for retransmission may be one of a plurality of configured grants configured in advance 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 mode, a DMRS-related parameter, an MCS table, and an RBG size.

As mentioned earlier, the DCI may be a DCI scrambled by a specific type of RNTI. When the terminal device receives the DCI, it can determine whether the DCI is used for activating or deactivating the configured grant grant configuration or for retransmission scheduling according to the type of the RNTI that scrambles the DCI.

Similar to method 200, the domains in the DCI can also be divided into first-type domains and second-type domains. Since the first-type domain and the second-type domain have been described in detail in the method 200, for the sake of brevity, they are not repeated here.

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

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

It should be noted that when the HPN domain is the first indication domain, the HPN domain carries a HARQ process number. The HARQ process number can be used to determine the retransmitted data. In this embodiment, the network device and the terminal device can determine the correspondence between the HARQ process number and the configured grant configuration in advance. For example, the HARQ process number can be calculated based on the time domain resource index of the configured grant. Therefore, the HARQ process number can be used to indirectly indicate the configured grant configuration used for retransmission. In other words, the HPN domain can be used to determine the configured grant configuration used for retransmissions.

When the HPN domain and the first indication domain are different domains, the first indication domain may directly carry the configured configuration grant index used for retransmission. In this case, the terminal device may determine the configured grant configuration 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. Therefore, the network device may generate the DCI based on the manner provided in the 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 method 1 or the method 2 described in the case 1 of the method 200 when it is determined 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 case 2 or the case 3 in the method 200, so as to avoid that the position of the first indication field is not fixed. The problem.

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

Then, in the DCI generated by the network device based on the method listed above, the NDI domain may also be located before all domains of the first type, or located at the last position of the DCI. Moreover, the relative position relationship between the NDI domain and the first indication domain is not limited in this application.

Optionally, the first indication domain and the HPN domain are different domains. In the DCI generated by the network device based on the method listed above, the first indication domain may be located before all the first type domains or the last position of the DCI, and the position of the NDI domain is not limited.

Since the specific process of generating DCI by the network device in different situations and the arrangement order of the various domains in the DCI have been described in detail in the method 200 above with reference to the accompanying drawings, for the sake of brevity, it will not be repeated here. For the specific process of step 320, refer to the specific process of step 220 above.

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

In step 340, the terminal device retransmits the transmission block according to the DCI and the configured grant configuration indicated by the first indication domain. 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 a retransmitted transmission block according to the HPN domain.

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

When the first indication domain and the HPN domain are different domains, the network device may still generate DCI based on the above method. Since the location of the first indication domain is fixed, the terminal device can parse the first indication domain based on the fixed location, and then can determine the configured grant configuration used for retransmission. At the same time, the terminal device can determine the number of bits of the first type domain according to the configured grant configuration used for retransmission, and then can determine the location of other second type domains, such as the HPN domain.

Alternatively, the network device may also process the HPN domain in a similar manner to the processing of the first indication domain in the process of generating the DCI, so that the HPN domain in the generated DCI precedes all first-type domains, or does not include In the DCI with zero padding bits, it is located after all domains of the first type, or after all zero padding bits with DCI. In addition, this application does not limit the relative positional relationship of the first indication domain, the HPN domain, and the NDI domain.

Either way, the protocol can predefine the position of each domain in the DCI. For example, the first indication field is the last field before all the first-type fields in DCI; for example, the first indication field is the last field of DCI, and the first indication field occupies the last bit of DCI; for 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 example, the first indication field and the NDI field are all zero-padded in the DCI The last two consecutive domains after the bit, and the NDI domain is before the first indicator domain; for example, the first indicator domain, the NDI domain, and the HPN domain are the last three consecutive domains before all the first-type domains in DCI, And the NDI domain is located before the first indication domain, the first indication domain is located before the HPN domain, and so on. For brevity, we will not list them one by one here. Network equipment can generate DCI based on the definition of the protocol, and terminal equipment can analyze DCI based on the definition of the protocol.

After the terminal device determines the transmission block that needs to be retransmitted based on the HARQ process number indicated in the HPN domain, it can transmit the retransmission transmission block through PUSCH according to the configured DCI and the configured grant grant used for the retransmission. The network device can receive the retransmitted transport block on the PUSCH according to the configured grant configuration used by the DCI and the retransmission.

For a specific process of the terminal device sending the retransmission transmission block, reference may be made to the prior art. For brevity, a detailed description of the specific process is omitted here.

Based on the above technical solution, the position of the first indication domain in the DCI is not affected by the length of the first type of domain, and the terminal device can resolve the first indication domain based on the fixed position. As a result, the terminal device can accurately determine the configured grant configuration used for retransmission. Therefore, the terminal device can retransmit the transmission block by configuring the authorized PUSCH according to some parameters in the DCI and the configured grant configuration. In order to achieve data retransmission, it is beneficial to improve the overall reliability of data transmission.

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

It should be understood that, in the above embodiments, the size of the sequence numbers of the processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. .

In the foregoing, the method provided by the embodiment of the present application has been described in detail with reference to FIGS. 2 to 15. Hereinafter, the communication device provided in the embodiment of the present application will be described in detail with reference to FIGS. 16 to 18.

FIG. 16 is a schematic block diagram of a communication apparatus according to an embodiment of the present application. As shown, the communication device 1000 may include a communication unit 1100 and a processing unit 1200.

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

Specifically, the communication device 1000 may correspond to a terminal device in the method 200 and the method 300 according to the embodiment of the present application. The communication device 1000 may include a method for performing the method 300 in FIG. 2 or the method 300 in FIG. 15. A unit of a method performed by a terminal device. In addition, each unit in the communication device 1000 and the other operations and / or functions described above are respectively to implement a corresponding process 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 240 in the method 200.

When the communication device 1000 is used to execute the method 300 in FIG. 15, the communication unit 1100 may be used to execute steps 310, 330, and 340 in the method 300, and the processing unit 1200 may be used to execute step 350 in the method 300.

It should be understood that the specific process for each unit to execute the above corresponding steps has been described in detail in the foregoing method embodiment, and for the sake of brevity, it will not be repeated here.

It should also be understood that when the communication device 1000 is a terminal device, the communication unit 1100 in the communication device 1000 may correspond to the transceiver 2020 in the terminal device 2000 shown in FIG. 17, and the processing unit 1200 in the communication device 1000 may Corresponds to the processor 2010 in the terminal device 2000 shown in FIG. 17.

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

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

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

Specifically, the communication device 1000 may correspond to the method 300 and the network device in the method 300 according to the embodiment of the present application. The communication device 1000 may include a method for performing the method 200 in FIG. 2 or the method 300 in FIG. 15. A unit of a method performed by a network device. In addition, each unit in the communication device 1000 and the other operations and / or functions described above are respectively to implement a corresponding process 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 used to execute the method 300 in FIG. 15, the communication unit 1100 may be used to execute steps 310, 330, and 340 in the method 300, and the processing unit 1200 may be used to execute step 320 in the method 300.

It should also be understood that when the communication device 1000 is a network device, the communication unit in the communication device 1000 is a transceiver 3200 that may correspond to the network device 3000 shown in FIG. 18, and the processing unit 1200 in the communication device 1000 may be Corresponds 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 may be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the foregoing method embodiment.

As shown, the terminal device 2000 includes a processor 2010 and a transceiver 2020. Optionally, the terminal device 2000 further includes a memory 2030. Among them, the processor 2010, the transceiver 2002, and the memory 2030 can communicate with each other through an internal connection path to transfer control and / or data signals. The memory 2030 is used to store a computer program, and the processor 2010 is used to store the computer program from the memory 2030 The computer program is called and run to control the transceiver 2020 to send and receive signals. Optionally, the terminal device 2000 may further include an antenna 2040 for sending uplink data or uplink control signaling output by the transceiver 2020 through 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 program codes stored in the memory 2030 to implement the foregoing functions. In specific implementation, the memory 2030 may also be integrated in the processor 2010 or independent of the processor 2010. The processor 2010 may correspond to the processing unit in FIG. 16.

The above-mentioned 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, or receiving circuit) and a transmitter (or transmitter, or transmitting circuit). The receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that the terminal device 2000 shown in FIG. 17 can implement various processes related to the terminal device in the method embodiments shown in FIG. 2 and FIG. 15. Operations and / or functions of each module in the terminal device 2000 are respectively implemented to implement corresponding processes in the foregoing method embodiments. For details, refer to the description in the foregoing method embodiments. To avoid repetition, detailed descriptions are appropriately omitted here.

The above processor 2010 may be used to perform the actions implemented in the terminal device described in the previous method embodiment, and the transceiver 2020 may be used to execute the terminal device described in the previous method embodiment to send or receive from the network device to the network device. action. For details, refer to the description in the foregoing method embodiment, and details are not described herein again.

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

In addition, in order to make the functions of the terminal device more complete, 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, and a sensor 2100. The audio circuit A speaker 2082, a microphone 2084, and the like may also be included.

FIG. 18 is a schematic structural diagram of a network device according to an embodiment of the present application, and may be, for example, a structural schematic diagram of a base station. The base station 3000 can be applied to the system shown in FIG. 1 and executes the functions of the network device in the foregoing method embodiment.

As shown in the figure, 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 (BBU) (also referred to as a digital unit). , Digital unit, DU) 3200. The RRU 3100 may be referred to as a transceiver unit, and corresponds to the communication unit 1200 in FIG. 16. Optionally, the transceiver unit 3100 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 3101 and a radio frequency unit 3102. Optionally, the transceiver unit 3100 may include a receiving unit and a transmitting unit. The receiving unit may correspond to a receiver (or a receiver or a receiving circuit), and the transmitting unit may correspond to a transmitter (or a transmitter or a transmitting circuit). The RRU 3100 part is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals, for example, for sending instruction information to terminal equipment. The BBU 3200 part is mainly used for baseband processing and controlling base stations. The RRU 3100 and the BBU 3200 may be physically located together, or may be physically separated, that is, a distributed base station.

The BBU 3200 is a control center of a base station, and may also be called a processing unit, which may correspond to the processing unit 1100 in FIG. 16, and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (Processing Unit) may be used to control the base station to execute the operation procedure on the network device in the foregoing method embodiment, for example, to generate the foregoing instruction information and the like.

In one example, the BBU 3200 may be composed of one or more boards, and multiple boards may jointly support a wireless access network (such as an LTE network) of a single access system, or may separately support different access systems. Wireless access network (such as LTE network, 5G network or other networks). The BBU 3200 further includes a memory 3201 and a processor 3202. The memory 3201 is configured to store necessary instructions and data. The processor 3202 is configured to control a base station to perform necessary actions, for example, to control the base station to perform an operation procedure on a network device in the foregoing method embodiment. The memory 3201 and the processor 3202 may serve one or more single boards. That is, the memory and processor can be set separately on each board. It is also possible that multiple boards share the same memory and processor. In addition, the necessary circuits can be set on each board.

It should be understood that the base station 3000 shown in FIG. 18 can implement various processes related to the network device in the method embodiments of FIG. 2 and FIG. 15. The operations and / or functions of each module in the base station 3000 are respectively to implement the corresponding processes in the foregoing method embodiments. For details, refer to the description in the foregoing method embodiments. To avoid repetition, detailed descriptions are appropriately omitted here.

The above BBU 3200 can be used to perform the actions implemented by the network device described in the previous method embodiment, and the RRU 3100 can be used to perform the actions that the network device described in the previous method embodiment sends to or receives from the terminal device. For details, refer to the description in the foregoing method embodiment, and details are not described herein again.

An embodiment of the present application further provides a processing apparatus including a processor and an interface; the processor is configured to execute the method in any one of the foregoing method embodiments.

It should be understood that the processing device may be a chip. For example, the processing device may be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or a system chip (SoC). It is a central processor (CPU), a network processor (NP), a digital signal processor (DSP), or a microcontroller (micro controller). (MCU), can also be a programmable controller (programmable logic device, PLD) or other integrated chips.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software. The steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware. To avoid repetition, it will not be described in detail here.

It should be noted that the processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability. In the implementation process, each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software. The above processors may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components . Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. 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 combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrical memory Erase programmable read-only memory (EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. 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 (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM ) And direct memory bus random access memory (direct RAMbus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not 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 also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer causes the computer to execute the operations shown in FIG. 2 and FIG. 15 The method of any one of the embodiments is shown.

According to the method provided in the embodiment of the present application, the present application further provides a computer-readable medium, where the computer-readable medium stores program code, and when the program code runs on the computer, the computer executes the operations shown in FIG. 2 and FIG. 15. The method of any one of the embodiments is shown.

According to the method provided in 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, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it 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 the computer instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (solid state disk) SSD)) and so on.

The network device in each of the foregoing device embodiments corresponds exactly to the network device or terminal device in the terminal device and method embodiments, and the corresponding module or unit performs the corresponding steps, for example, the communication unit (transceiver) performs the receiving or The step of sending, other than sending and receiving, may be performed by a processing unit (processor). For the function of the specific unit, refer to the corresponding method embodiment. Among them, there may be one or more processors.

The terms “component”, “module”, “system” and the like used in this specification are used to indicate computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, 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 a computing device can be components. 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. A component may, for example, be based on a signal having one or more data packets (e.g., data from two components that interact with another component between a local system, a distributed system, and / or a network, such as the Internet that interacts with other systems through signals) Communicate via local and / or remote processes.

Those of ordinary skill in the art may realize that various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. achieve. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

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

In the above embodiments, the functions of each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it 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). When the computer program instructions (programs) are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

The above is only a specific implementation of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims (64)

1. A method for configuring uplink dynamic exemption authorization transmission, which comprises:

   Receiving downlink control information DCI, the DCI being used to activate or deactivate a pre-configured authorization configuration of one of the configured grant grant configurations, the DCI includes a first indication domain and at least one first class domain, The number of bits of the first-type domain is determined by an 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 before the at least one first-class field. ;

   Activate or deactivate the configured grant configuration corresponding to the index.
2. The method according to claim 1, wherein the DCI further includes new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is located at Before the at least one first-type domain.
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 according to any one of claims 1 to 3, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
5. The method according to any one of claims 1 to 4, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
6. A method for configuring uplink dynamic exemption authorization transmission, which comprises:

   Generating downlink control information DCI, the DCI being used to activate or deactivate a pre-configured authorization configuration of a plurality of pre-configured authorized configurations configured, the DCI includes a first indication domain and at least one first-type domain, The number of bits of the first-type domain is determined by an 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 before the at least one first-class field. ;

   Sending the DCI.
7. The method according to claim 6, wherein the DCI further includes new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is located at Before the at least one first-type domain.
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 according to any one of claims 6 to 8, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
10. The method according to any one of claims 6 to 9, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
11. A method for configuring uplink dynamic exemption authorization transmission, which comprises:

    Receiving downlink control information DCI, the DCI being used to activate or deactivate a pre-configured authorization configuration of one of the configured grant grant configurations, the DCI includes a first indication domain and at least one first class domain, The number of bits of the first type of domain is determined by 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;

    Activate or deactivate the configured grant configuration corresponding to the index.
12. The method according to claim 11, wherein the DCI further includes new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is related to The first indication fields are all located at the 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 according to any one of claims 11 to 13, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
15. The method according to any one of claims 11 to 14, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
16. A method for configuring uplink dynamic exemption authorization transmission, which comprises:

    Generating downlink control information DCI, the DCI being used to activate or deactivate a pre-configured authorization configuration of a plurality of pre-configured authorized configurations configured, the DCI includes a first indication domain and at least one first-type domain, The number of bits of the first type of domain is determined by the activated or deactivated configured grant configuration, the first indication field indicates an index of the configured grant configuration, and the first indication field is located at the last position of the DCI;

    Sending the DCI.
17. The method according to claim 16, wherein the DCI further comprises a new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is related to The first indication fields are all located at the 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 according to any one of claims 16 to 18, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
20. The method according to any one of claims 16 to 19, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
21. A communication device, comprising:

    A communication unit, configured to receive downlink control information DCI, the DCI being used to activate or deactivate one of a plurality of pre-configured authorized configuration configured grant grant configurations, the DCI including a first indication domain and at least one The first type of domain, the number of bits of the first type of domain is determined by the activated or deactivated configured grant configuration, the first indication field indicates an index of the configured grant configuration, and the first indication field is located in the at least one Before the first domain

    A processing unit, configured to activate or deactivate the configured grant configuration corresponding to the index.
22. The apparatus according to claim 21, wherein the DCI further comprises a new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is located at Before the at least one first-type domain.
23. The apparatus according to claim 21 or 22, wherein the first indication field is a hybrid automatic repeat request process number (HPN) field.
24. The apparatus according to any one of claims 21 to 23, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
25. The communication device according to any one of claims 21 to 24, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
26. A communication device, comprising:

    A processing unit, configured to generate downlink control information DCI, the DCI being used to activate or deactivate one of a plurality of pre-configured authorized configuration configured grant grant configurations, the DCI including a first indication domain and at least one The first type of domain, the number of bits of the first type of domain is determined by the activated or deactivated configured grant configuration, the first indication field indicates an index of the configured grant configuration, and the first indication field is located in the at least one Before the first domain

    A communication unit, configured to send the DCI.
27. The communication device according to claim 26, wherein the DCI further comprises a new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant grant configuration, and the NDI domain Located before the at least one first-type domain.
28. The apparatus according to claim 26 or 27, wherein the first indication field is a hybrid automatic repeat request process number (HPN) field.
29. The apparatus according to any one of claims 26 to 28, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
30. The communication device according to any one of claims 26 to 29, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
31. A communication device, comprising:

    A communication unit, configured to receive downlink control information DCI, the DCI being used to activate or deactivate one of a plurality of pre-configured authorized configuration configured grant grant configurations, the DCI including a first indication domain and at least one The first type of domain, the number of bits of the first type of domain 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 in the DCI Last position

    A processing unit, configured to activate or deactivate the configured grant configuration corresponding to the index.
32. The apparatus according to claim 31, wherein the DCI further comprises a new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is related to The first indication fields are all located at the last position of the DCI.
33. The apparatus according to claim 31 or 32, wherein the first indication field is a hybrid automatic repeat request process number (HPN) field.
34. The communication device according to any one of claims 31 to 33, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
35. The communication device according to any one of claims 31 to 34, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
36. A communication device, comprising:

    A processing unit that generates downlink control information DCI, said DCI being used to activate or deactivate a pre-configured authorization configuration of one of a plurality of configured authorized grant configurations, said DCI including a first indication domain and at least one first Class domain, the number of bits of the first category domain is determined by 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 the last position of the DCI ;

    A communication unit, configured to send the DCI.
37. The apparatus according to claim 36, wherein the DCI further comprises a new data indicating an NDI domain, the NDI domain is used to determine whether the DCI is used to activate or deactivate a configured grant configuration, and the NDI domain is related to The first indication fields are all located at the last position of the DCI.
38. The communication device according to claim 36 or 37, wherein the first indication field is a hybrid automatic repeat request process number (HPN) field.
39. The communication device according to any one of claims 36 to 38, wherein the DCI is scrambled by a configuration scheduling CS-wireless network temporary identifier RNTI.
40. The communication device according to any one of claims 36 to 39, wherein the first type of domain comprises a frequency domain resource assignment domain and a frequency hopping identification domain.
41. A communication device, comprising:

    A processor for executing a computer program stored in a memory, so that the apparatus executes the method according to any one of claims 1 to 5.
42. A communication device, comprising:

    A processor for executing a computer program stored in a memory, so that the apparatus executes the method according to any one of claims 6 to 10.
43. A communication device, comprising:

    A processor for executing a computer program stored in a memory, so that the apparatus executes the method according to any one of claims 11 to 15.
44. A communication device, comprising:

    A processor for executing a computer program stored in a memory, so that the apparatus executes the method according to any one of claims 16 to 20.
45. A communication device, characterized in that the device is used to implement the method according to any one of claims 1 to 5.
46. A communication device, characterized in that the device is used to implement the method according to any one of claims 6 to 10.
47. A communication device, wherein the device is used to implement the method according to any one of claims 11 to 15.
48. A communication device, wherein the device is used to implement the method according to any one of claims 16 to 20.
49. A processing device, comprising a processor, the processor is configured to execute a computer program stored in a memory, so that the device implements the method according to any one of claims 1 to 5.
50. A processing device, comprising a processor, the processor is configured to execute a computer program stored in a memory, so that the device implements the method according to any one of claims 6 to 10.
51. A processing device, comprising a processor for executing a computer program stored in a memory, so that the device implements the method according to any one of claims 11 to 15.
52. A processing device, comprising a processor, the processor is configured to execute a computer program stored in a memory, so that the device implements the method according to any one of claims 16 to 20.
53. A processing device, comprising:

    Memory for storing computer programs;

    A processor for calling and running the computer program from the memory, so that the apparatus implements the method according to any one of claims 1 to 5.
54. A processing device, comprising:

    Memory for storing computer programs;

    A processor for calling and running the computer program from the memory, so that the apparatus implements the method according to any one of claims 6 to 10.
55. A processing device, comprising:

    Memory for storing computer programs;

    A processor for calling and running the computer program from the memory, so that the apparatus implements the method according to any one of claims 11 to 15.
56. A processing device, comprising:

    Memory for storing computer programs;

    A processor for calling and running the computer program from the memory, so that the apparatus implements the method according to any one of claims 16 to 20.
57. A computer-readable medium, comprising a computer program, which causes the computer to execute the method according to any one of claims 1 to 5 when the computer program is run on a computer.
58. A computer-readable medium, comprising a computer program, which causes the computer to execute the method according to any one of claims 6 to 10 when the computer program is run on a computer.
59. A computer-readable medium, comprising a computer program, which causes the computer to execute the method according to any one of claims 11 to 15 when the computer program is run on a computer.
60. A computer-readable medium, comprising a computer program, which causes the computer to execute the method according to any one of claims 16 to 20 when the computer program is run on a computer.
61. A computer program product comprising a computer program, which when executed on a computer, causes the computer to perform the method according to any one of claims 1 to 5.
62. A computer program product, the computer program product comprising a computer program that, when the computer program runs on a computer, causes the computer to perform the method according to any one of claims 6 to 10.
63. A computer program product comprising a computer program that, when run on a computer, causes the computer to perform the method according to any one of claims 11 to 15.
64. A computer program product comprising a computer program that, when run on a computer, causes the computer to perform the method according to any one of claims 16 to 20.

Images