WO2022041002A1

WO2022041002A1 - Transmission method and terminal device

Info

Publication number: WO2022041002A1
Application number: PCT/CN2020/111511
Authority: WO
Inventors: 付喆
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-08-26
Filing date: 2020-08-26
Publication date: 2022-03-03
Also published as: CN115943582A

Abstract

The present application relates to a transmission method and a terminal device. The transmission method comprises: a terminal device receives a configured grant (CG) resource; the terminal device uses the CG resource to automatically transmit a first type of object by means of a second type of mechanism. According to the embodiments of the present application, the use of a CG resource to automatically transmit a first type of object by means of a second type of mechanism can reduce data loss.

Description

Transmission method and terminal equipment

technical field

The present application relates to the field of communications, and more particularly, to a transmission method and terminal device.

Background technique

5G (5th-Generation, next-generation communication) RAN (Radio Access Network, wireless access network) 2URLLC (Ultra-Reliable and Low Latency Communication, ultra-reliable and low-latency communication) needs to support industrial automation (Factory automation), The transmission of services such as Transport Industry and Electrical Power Distribution in the 5G system. In order to support the transmission of URLLC services, the CG (Configured Grant, configuration authorization) has been enhanced, that is, multiple CG configurations are introduced, as well as the specific configuration and use of CG (such as supporting slot-level (slot level) period, Support for automatic transfer of CG, etc.) has been enhanced.

The goal of NRU is to make NR work in unlicensed frequency bands, including the following working scenarios:

Carrier aggregation scenario: PCell is licensed spectrum, and SCells working on unlicensed spectrum are aggregated through carrier aggregation;

Dual-connection working scenario: PCell is LTE licensed spectrum, PScell is NR unlicensed spectrum;

Independent working scenario: NR works as an independent cell in unlicensed spectrum.

In a scenario where NRU (New Radio Unlicensed, New Radio Unlicensed) interference is controlled, how to use CG resources for automatic transmission or retransmission has not yet been determined.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a transmission method and terminal device, which can use CG resources to perform automatic transmission or retransmission to reduce data loss.

The embodiment of the present application provides a transmission method, including:

The terminal device receives and configures authorized CG resources;

The terminal device uses the CG resource to automatically transmit the object of the first type using the mechanism of the second type.

An embodiment of the present application provides a terminal device, including:

a receiving unit, configured to receive configuration authorization CG resources;

A transmission unit, configured to use the CG resource to automatically transmit the object of the first type using the mechanism of the second type.

An embodiment of the present application provides a terminal device, including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so that the terminal device executes the above-mentioned transmission method.

An embodiment of the present application provides a network device including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so that the network device executes the above-mentioned transmission method.

An embodiment of the present application provides a chip for implementing the above-mentioned transmission method.

Specifically, the chip includes: a processor for calling and running a computer program from the memory, so that the device on which the chip is installed executes the above-mentioned transmission method.

Embodiments of the present application provide a computer-readable storage medium for storing a computer program, and when the computer program is run by a device, the device enables the device to execute the above-mentioned transmission method.

An embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned transmission method.

The embodiments of the present application provide a computer program, which, when running on a computer, causes the computer to execute the above-mentioned transmission method.

In this embodiment of the present application, the CG resource is used for automatic transmission or retransmission, which can reduce data loss.

Description of drawings

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

FIG. 2 is a schematic flowchart of a transmission method according to an embodiment of the present application.

FIG. 3 is a schematic flowchart of Example 1 of a transmission method according to an embodiment of the present application.

FIG. 4 is a schematic flowchart of Example 2 of a transmission method according to an embodiment of the present application.

FIG. 5 is a schematic block diagram of a terminal device according to an embodiment of the present application.

FIG. 6 is a schematic block diagram of a communication device according to an embodiment of the present application.

FIG. 7 is a schematic block diagram of a chip according to an embodiment of the present application.

FIG. 8 is a schematic block diagram of a communication system according to an embodiment of the present application.

detailed description

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

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a wideband Code Division Multiple Access (CDMA) system (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) system, Advanced Long Term Evolution (Advanced long term evolution, LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present application can also be applied to these communication systems.

Optionally, the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.

Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In this embodiment of the present application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).

In this embodiment of the present application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks The network equipment (gNB) in the PLMN network in the future evolution or the network equipment in the NTN network, etc.

As an example and not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc. Optionally, the network device may also be a base station set in a location such as land or water.

In this embodiment of the present application, a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). Pico cell), Femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

FIG. 1 exemplarily shows a communication system 100 . The communication system includes one network device 110 and two terminal devices 120 . Optionally, the communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers of terminal devices 120, which are not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF) and other network entities, to which the embodiments of the present application Not limited.

Wherein, the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system further includes a plurality of core networks for communicating with the access network equipment. The access network equipment may be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system, or an authorized auxiliary access long-term evolution (authorized auxiliary access long-term evolution, LAA- The evolved base station (evolutional node B, may be referred to as eNB or e-NodeB for short) in the LTE) system is a macro base station, a micro base station (also called a "small base station"), a pico base station, an access point (AP), Transmission site (transmission point, TP) or new generation base station (new generation Node B, gNodeB), etc.

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system may be referred to as a communication device. Taking the communication system shown in FIG. 1 as an example, the communication device may include a network device and a terminal device with a communication function, and the network device and the terminal device may be specific devices in this embodiment of the application, which will not be repeated here; It may include other devices in the communication system, for example, other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

It should be understood that the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship. For example, if A indicates B, it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, which all belong to the embodiments of the present application. protected range.

The CG enhancements in URLLC are described below:

In the embodiment of the present application, it needs to consider supporting the URLLC service in the interference-controlled NRU scenario. Specifically, it can be considered to consider the use of NRU CG and ULRRC CG enhancement in the NRU scenario, for example: introducing coordinated UL CG enhancement in NRU and URLLC to apply to unlicensed spectrum.

To support the high latency requirements of URLLC services, URLLC enhances the CG cycle to support any slot-level service cycle.

In order to support multiple URLLC services and high latency requirements of URLLC services, URLLC introduces multiple (multiple) CGs. The HARQ (Hybrid Automatic Repeat Request) processes configured by different CGs are different, and the processes of different CGs are guaranteed to be different through HARQ-ProcID-Offset2 (HARQ process identifier-offset 2).

Due to the conflict between CG resources and other resources, in order to ensure that the MAC (Medium Access Control, Medium Access Control) PDU (Protocol Data Unit, Protocol Data Unit) (such as Deprioritized (low priority) MAC PDUs) that have been packaged in the CG resources ) is not discarded/transmitted as soon as possible, automatic transmission for CG is introduced. For the CG of the group of MAC PDUs that cannot be transmitted due to resource conflict, the subsequent CG resources of the same HARQ process and the same CG configuration can be used for new transmission. The use of automatic transfer is determined by the automatic transfer parameter (eg autonomousTx).

The following describes the CG enhancement in NRU:

Generally speaking, the working frequency band (Band) of NRU is 5GHz unlicensed spectrum and 6GHz unlicensed spectrum, (e.g., US 5925–7125MHz, or European 5925–6425MHz, or parts thereof). On the unlicensed spectrum, the design of the NRU should ensure fairness with other systems already working on the unlicensed spectrum, such as WiFi (Wireless Fidelity, wireless fidelity). The principles of fairness include that the NRU's impact on systems already deployed on unlicensed spectrum (eg, WiFi) cannot exceed the impact between those systems.

To ensure fair coexistence among systems on unlicensed spectrum, energy detection has been agreed as a basic coexistence mechanism. The general energy detection mechanism is the LBT (Listen Before Talk) mechanism. The basic principle of this mechanism is that, before the base station or terminal (transmitter) transmits data on the unlicensed spectrum, it needs to listen for a period of time according to regulations. If the result of listening indicates that the channel is in an idle state, the transmitting end can transmit data to the receiving end. If the listening result indicates that the channel is in an occupied state, the transmitting end needs to roll back a certain period of time and continue to monitor the channel until the channel listening result is in an idle state, and can transmit data to the receiving end.

For flexible resource selection, the HARQ process of the NRU CG is not calculated according to the formula, but selected by the UE itself. For one CG resource, RRC configures one HARQ process set, and the UE can select one HARQ process from the set for this CG transmission. The specifically configured HARQ process interval is determined by harq-ProcID-Offset and nrofHARQ-Processes.

In order to support back-to-back resource configuration, NRU introduces multiple CGs. Multiple CG configurations can share the HARQ process.

A CG retransmission timer (cg-RetransmissionTimer, CG retx Timer for short) is introduced to support automatic retransmission of resources when CG resources cannot be transmitted due to LBT failure. After the cg-RetransmissionTimer times out, if the CG timer (configured GrantTimer, CG timer for short) does not time out, the corresponding HARQ process can be retransmitted.

CG transmission can be interrupted by dynamic scheduling DCI (Downlink Control Information, downlink control information) and DFI (Downlink Feedback Information, downlink feedback information). For example, as shown in Table 1 below, the CG timer (CG timer) stops (stop) when DFI is ACK, and is not affected (No impact) when DFI is NACK, and DCI is new transmission (new tx) or retransmission (retx) ) to start or restart. When the CG timer expires, stop the CG retransmission timer (CG retx timer). The CG retransmission timer (CG retx timer) stops when the DFI is ACK, NACK, new transmission or retransmission.

Table 1

In this embodiment of the present application, in a scenario where NRU interference is controlled, it is possible to determine a specific manner of using CG resources to perform automatic transmission or retransmission, and how to perform automatic transmission or retransmission.

FIG. 2 is a schematic flowchart of a transmission method 200 according to an embodiment of the present application. The method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least some of the following.

S210. The terminal device receives a configuration authorization (CG) resource.

S220. The terminal device uses the CG resource to automatically transmit the first-type object by using the second-type mechanism.

Optionally, the conventional transport mechanism for the first type of object may be the first type of mechanism. The second type of mechanism may be different from the first type of mechanism. In the embodiment of the present application, after receiving the CG resource, the terminal device uses the second type mechanism to automatically transmit the first type object, so that the transmission object and the transmission mechanism are not bound, and the specific transmission mechanism can also be applied to various transmissions. object. For example, the first type of object may be an object of a first communication scenario, and the second type of mechanism may be a transmission mechanism of the second communication scenario, and the two communication scenarios are different.

Optionally, in the embodiment of the present application, the automatic transmission by the terminal device using the CG resource for the first type of objects using the second type mechanism includes: the terminal device using the CG resource to use the second communication for objects in the first communication scenario. The transfer mechanism of the scene is automatically transferred.

Exemplarily, if the first communication scenario is an NRU scenario and the second communication scenario is a URLLC scenario, the terminal device can use the CG resource to automatically transmit the objects of the NRU scenario using the URLLC scenario transmission mechanism. This way can be called way one. The first communication scenario may again be an unlicensed spectrum access or scenario. The second communication scenario may again be a licensed spectrum access or scenario. Exemplarily, the scene or object is an R16 scene or object.

Exemplarily, if the first communication scenario is the URLLC scenario and the second communication scenario is the NRU scenario, the terminal device can use the CG resource to automatically transmit the objects of the URLLC scenario using the NRU scenario transmission mechanism. This way can be called way two. The first communication scenario may again be a licensed spectrum access or scenario. The second communication scenario may again be an unlicensed spectrum access or scenario. Exemplarily, the scene or object is an R16 scene or object.

Optionally, in the first manner of the embodiment of the present application, the terminal device receiving the CG resources includes: the terminal device receives one or more CG resources from the network, and each CG resource has a corresponding Hybrid Automatic Repeat Request (HARQ) resource. ) process, each CG resource includes at least one of the following configurations:

Configure automatic transmission parameters (autonomousTx) to trigger automatic transmission;

Configure the CG timer, but do not configure the CG retransmission timer;

Configure the CG timer and CG retransmission timer, but the value of the CG retransmission timer is 0.

Optionally, in the first mode of the embodiment of the present application, the premise of configuring the autonomousTx includes: the terminal device, the MAC entity or the CG resource of the terminal device are configured to be prioritized based on LCH (Logical Channel, logical channel).

Optionally, in the second manner of this embodiment of the present application, the terminal device receives CG resources, including:

The terminal device receives one or more CG resources from the network, each CG resource has a corresponding HARQ process of HARQ, and each CG resource includes at least one of the following configurations:

Do not configure the automatic transmission parameter autonomousTx,

Configure the CG retransmission timer to trigger automatic transmission;

Configure the CG retransmission timer with a value of 0 to trigger automatic transmission;

Configure the CG timer.

Optionally, in this embodiment of the present application, the CG resource is configured in the manner of a new wireless unlicensed NRU CG or an ultra-reliable and low-latency communication URLLC CG. In this way, the configuration mode and the transmission mode may not be bound. For the CG resources configured in the NRU CG mode, the URLLC transmission mechanism can be used for automatic transmission. For the CG resources configured in the URLLC CG mode, the NRU transmission mechanism can be used for automatic transmission.

Optionally, in the first mode of the embodiment of the present application, the terminal device uses the CG resource to automatically transmit the first type of objects by using the second type mechanism, including: automatically transmitting at least one of the following objects:

Media access control MAC protocol data unit PDUs that have not been transmitted, have not been successfully transmitted, or have not been transmitted;

HARQ processes or MAC PDUs that were not transmitted, were not successfully transmitted, or were not transmitted due to LBT failure;

The HARQ process is not changed due to LBT failure, or the HARQ process is still a pending HARQ process or MAC PDU;

The corresponding (DFI downlink feedback information) or DCI (downlink control information) HARQ process or MAC PDU not received due to downlink LBT failure.

Exemplarily, the LBT failure may be caused by inter-system interference, such as WIFI, or by intra-system interference, or by false detection. In controlled scenarios, it is mainly caused by interference within the system, or by false detection.

Optionally, in Manner 1 of this embodiment of the present application, performing automatic transmission includes at least one of the following:

Automatic transmission based on autonomousTx transmission mode;

Automatic transmission based on the automatic transmission method of licensed spectrum;

Automatic transmission based on low-priority data or low-priority MAC PDU transmission;

Automatic transmission based on low-priority resources or low-priority CG transmission methods;

Automatic transmission based on the transmission mode of low-priority data or low-priority MAC PDU caused by resource conflict;

Automatic transmission is performed based on the transmission mode of low-priority resources or low-priority CGs caused by resource conflicts.

Optionally, in Manner 1 of this embodiment of the present application, the automatic transmission is URLLC automatic transmission.

Optionally, in the first manner of the embodiment of the present application, performing automatic transmission includes: for a CG resource, the MAC entity of the terminal device determines the NDI (New Data Indication, NDI) of the HARQ process when the first condition is satisfied. new data indication) rollover, and/or hand over the CG resource to the HARQ entity. Wherein, the HARQ entity may include multiple HARQ processes.

Optionally, in Manner 1 of this embodiment of the present application, the first condition includes at least one of the following:

The PUSCH (PhysicalUplinkSharedChannel, physical uplink shared channel) of the CG does not conflict with the PUSCH resource scheduled by the DCI;

The PUSCH of the CG does not conflict with the PUSCH resources scheduled by RAR (Random Access Response, random access response) or TC-RNTI (Temporary Cell-Radio Network Temporary Identifier, temporary cell wireless network temporary identifier);

The PUSCH of the CG does not conflict with the PUSCH resource of the two-step random access message A (MSGA) payload (Payload);

The MAC entity is configured with LCH-based priority processing;

CG timer is not configured;

CG timer is configured but not running;

CG retransmission timer is not configured;

CG retransmission timer is configured;

The CG retransmission timer is configured but the value is 0.

Optionally, in the first manner of the embodiment of the present application, performing automatic transmission further includes: for a HARQ process corresponding to an uplink grant, the MAC entity or the HARQ entity of the terminal device determines the MAC address when the second condition is satisfied. The PDU is acquired, and the second condition includes at least one of the following:

The uplink grant is CG;

The uplink authorization is configured with the automatic transmission parameter autonomousTx;

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size;

The size of the uplink grant is the same as the size of the CG before the HARQ process;

The size of the uplink grant is the same as the size of the last CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the last CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP (Bandwidth Part, bandwidth part) is the same;

The uplink grant size and the CG before the HARQ process are the same CG configuration;

The uplink grant is the same as the CG index of the last CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the latest CG before the HARQ process are configured for the same CG;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process.

Optionally, in the first manner of the embodiment of the present application, performing automatic transmission further includes: in the case that the MAC entity or HARQ entity of the terminal device obtains the MAC PDU to be transmitted, submitting the MAC PDU to the HARQ process, and/or, instructs the HARQ process to perform a new transmission.

Optionally, in the first manner of the embodiment of the present application, performing automatic transmission further includes: the MAC entity or the HARQ entity of the terminal device determines the state of the HARQ process in the following manner:

When the third condition is satisfied, the HARQ process is pending, and the third condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the HARQ process obtains the MAC PDU to be transmitted; and/or,

When the fourth condition is met, the HARQ process is not pending, and the fourth condition includes at least one of the following: configuring autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process is executed, successful or completed , the uplink grant is a priority transmission resource, the uplink grant is a non-resource conflict uplink grant, the uplink grant or CG or the transmission of the MAC PDU is executed, successful or completed, the LBT of the uplink grant or the CG is successful, no The LBT failure indication is received, the transmission failure indication is not received, the retransmission indication is not received, the LBT success indication is received, and the transmission successful indication is received.

Optionally, in the first mode of the embodiment of the present application, performing automatic transmission further includes determining the state of the HARQ process in the following manner: in the case where the fifth condition is satisfied, the HARQ process corresponding to the CG resource is pending, and the HARQ process corresponding to the CG resource is pending. The fifth condition includes at least one of the following: configuring autonomousTx, the uplink grant is CG, the transmission of the HARQ process is not executed, unsuccessful or incomplete, the uplink grant is a low-priority resource, and the uplink grant is an uplink grant with conflicting resources, The transmission of the uplink grant or the CG or the MAC PDU is not executed, unsuccessful or incomplete, the LBT of the uplink grant or the CG fails, an LBT failure indication is received, a transmission failure indication is received, and a retransmission indication is received, No LBT success indication was received, no transmission success indication was received.

Optionally, in the second manner of the embodiment of the present application, the terminal device uses the CG resource to automatically transmit the first-type object by using the second-type mechanism, including at least one of the following:

Automatic transmission of MAC PDUs that have not been transmitted, have not been successfully transmitted or have not been transmitted;

Automatic transmission of HARQ processes or MAC PDUs that have not been transmitted, have not been successfully transmitted, or have not been transmitted due to resource conflicts;

Low-priority resources or CGs for automatic transmission;

Automatic transmission of MAC PDUs that are considered low priority or low priority data.

Optionally, in Manner 2 of this embodiment of the present application, performing automatic transmission includes at least one of the following:

Automatic transmission or automatic retransmission based on the retransmission method of unlicensed spectrum;

Automatic transmission or automatic retransmission based on the pending state of the HARQ process;

Automatic transmission or automatic retransmission based on DFI instructions;

Automatic transmission or automatic retransmission based on the transmission mode of the CG retransmission timer;

Automatic transmission or automatic retransmission based on the untransmitted MAC PDU transmission mode caused by LBT failure;

Automatic transmission or automatic retransmission based on the fact that the HARQ process is not changed due to LBT failure, or the HARQ process is still in the pending transmission mode;

Automatic transmission or automatic retransmission is performed based on the DFI or DCI not receiving the corresponding transmission mode caused by the downlink LBT failure.

Optionally, in the second manner of this embodiment of the present application, the automatic transmission is NRU automatic transmission.

Optionally, in Manner 2 of this embodiment of the present application, performing automatic transmission includes: for a CG resource, the MAC entity of the terminal device submits the CG resource to the HARQ entity under the condition that the sixth condition is satisfied.

Optionally, in the second manner of the embodiment of the present application, the sixth condition includes at least one of the following:

The PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;

The PUSCH of the CG does not conflict with the PUSCH resource scheduled by the RAR/TC-RNTI;

The PUSCH of the CG does not conflict with the PUSCH resources of the MSGA payload;

The MAC entity is configured with LCH-based priority processing;

CG retransmission timer is configured but not running;

The HARQ process is pending;

CG timer is not running.

Optionally, in the second manner of this embodiment of the present application, the MAC entity determines the NDI inversion of the HARQ process.

Optionally, in the second manner of this embodiment of the present application, the MAC entity determines that the NDI of the HARQ process is not reversed.

Optionally, in the second manner of the embodiment of the present application, if the NDI is reversed, the automatic transmission is performed, further including:

The MAC entity or HARQ entity of the terminal device determines that the HARQ process corresponding to the CG resource obtains the MAC PDU to be transmitted when the seventh condition is satisfied, and the seventh condition includes at least one of the following:

the uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size

The uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;

The previous CG corresponding to the HARQ process is a low-priority CG;

The last CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

In the HARQ process, there are MAC PDUs that have not been transmitted, have not been successfully transmitted, have not been transmitted or have not been transmitted due to resource conflicts.

When the MAC entity or HARQ entity of the terminal device obtains the MAC PDU to be transmitted, it submits the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform new transmission.

Optionally, in the second manner of the embodiment of the present application, if the NDI is not reversed, the automatic transmission is performed, which further includes:

The MAC entity or HARQ entity of the terminal device delivers the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform retransmission.

Optionally, in the second manner of this embodiment of the present application, if the NDI is not reversed, the MAC entity or HARQ entity of the terminal device submits the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform retransmission, including:

The MAC entity or the HARQ entity delivers the MAC PDU to the HARQ process and/or instructs the HARQ process to perform retransmission under the condition that an eighth condition is satisfied, and the eighth condition includes at least one of the following:

the uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

Get MAC PDU;

The uplink grant size is the same as the acquired MAC PDU size;

The uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the most recent CG before the HARQ process;

The previous CG corresponding to the HARQ process is a low-priority CG;

The last CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

Optionally, in Manner 2 of this embodiment of the present application, performing automatic transmission includes:

For an uplink grant resource or CG resource, the MAC entity or the HARQ entity performs at least one of the following steps when the ninth condition is satisfied:

Do not deliver uplink grant resources or CG resources to the HARQ entity;

ignore the uplink grant resource or CG resource;

Submit the uplink grant resource or CG resource to the HARQ process but ignore the uplink grant resource or CG resource.

Optionally, in the second manner of the embodiment of the present application, the ninth condition includes at least one of the following:

CG retransmission timer is configured but not running;

CG retransmission timer is configured but the value is 0;

is not pending in the HARQ process;

The CG timer runs.

Optionally, in the second manner of the embodiment of the present application, performing automatic transmission, further comprising:

Determine the status of the HARQ process in at least one of the following ways:

Determine the HARQ process corresponding to the low-priority uplink grant resource as pending;

Determine the HARQ process corresponding to the uplink grant resource of the low-priority MAC PDU as pending;

Determine the HARQ process corresponding to the low-priority CG resource as pending;

Determine the HARQ process corresponding to the CG resource of the low-priority MAC PDU as pending;

Determine the conflicting uplink grant resource or CG resource as pending;

Determine the HARQ process when the MAC PDU is obtained as pending;

Determine the HARQ process as pending when the MAC PDU corresponding to the CG resource is obtained;

Determine the conflicting and prioritized uplink grant resource or CG resource as pending;

Determine the unconflicted uplink authorized resource or CG resource as not pending;

Determine the uplink authorized resources or CG resources that do not conflict and LBT fails to be not pending;

MAC PDU transmission execution, success or completion, determine the HARQ process as not pending,

MAC PDU transmission is executed, successful or completed, and no LBT failure indication is received, the HARQ process is determined as not pending;

MAC PDU transmission is executed, successful or completed, and the LBT success indication is received, and the HARQ process is determined as not pending;

The resource corresponding to the MAC PDU is a priority resource, and the resource corresponding to the MAC PDU is not a low-priority resource;

The uplink grant resource corresponding to the MAC PDU is not a low-priority resource, or it is not transmitted due to a conflict, and the HARQ process is determined as not pending.

In the first mode of the embodiment of the present application, URLLC automatic transmission can be performed on the objects of the NRU scene, to ensure that the objects of the NRU scene, such as MAC PDUs that have not been transmitted or have not been successfully transmitted due to LBT failure, are not discarded, so as to avoid data loss, or to make the data as soon as possible. transmission.

In the second method of the embodiment of the present application, NRU automatic transmission can be performed on the objects of the URLLC scene, to ensure that the objects of the URLLC scene, such as low-priority MAC PDUs, are not discarded, data loss is avoided, or data is transmitted as soon as possible.

A specific example of the transmission method in the embodiment of the present application is introduced below:

Example 1: A pending (pending) HARQ process and/or a non-pending (not pending) HARQ process triggers URLLC automatic transmission.

(1) Increase the condition that the MAC PDU is considered to be acquired

(2) Set the HARQ process state, for example, use at least one of the following methods to set the HARQ process state:

(2-1) In the case where the third condition is satisfied, it is considered that the corresponding HARQ process is pending. The third condition is at least one of the following: configure autonomousTx, the uplink resource (for example, uplink grant) is CG, and the HARQ process obtains the MAC PDU for transmission. And/or, when the fourth condition is satisfied, it is considered that the corresponding HARQ process is not pending. The fourth condition is: configure autonomousTx, the uplink resource is CG, the transmission of the HARQ process is executed, succeeded or completed, the uplink grant is the priority transmission resource, the uplink grant is the uplink grant that does not conflict with the resource, the uplink grant, CG Or the transmission of the MAC PDU is executed, successful or completed, the LBT for the uplink grant or CG is successful, no LBT failure indication from the lower layer or NW is received, no transmission failure indication from the lower layer or NW is received, and no lower layer or NW is received. The retransmission indication is received, the LBT success indication of the lower layer or NW is received, and the transmission success indication of the lower layer or NW is received. or,

(2-2) When the fifth condition is satisfied, it is considered that the corresponding HARQ process is pending. The fifth condition is: configure autonomousTx, the uplink resource is CG, the transmission of the HARQ process is not executed, unsuccessful or incomplete, the uplink grant is a low-priority transmission resource, the uplink grant is the uplink grant of resource conflict, the uplink grant The transmission of grant, CG or MAC PDU is not executed, unsuccessful or incomplete, the LBT of the uplink grant or CG fails, the LBT failure indication of the lower layer or NW is received, the transmission failure indication of the lower layer or NW is received, and the lower layer is received. Or the retransmission indication of the NW, the LBT success indication of the lower layer or the NW is not received, and the transmission success indication of the lower layer or the NW is not received.

Example 2: Deprioritized MAC PDUs are automatically retransmitted using NRU. Specifically, it includes at least one of the following methods:

(1-1) If the sixth condition is satisfied, deliver the CG resource to the HARQ entity. The sixth condition includes at least one of the following: the CG retransmission timer (cg-RetransmissionTimer) is configured and not running, the HARQ process is pending, and the CG timer (configuredGrantTimer) is not running. The first mode may also include the following cases: Case 1: The NDI is considered to be reversed, and the transmission is performed according to the new transmission;

(1-2) If the ninth condition is satisfied, the uplink grant resource or the CG resource is not delivered (deliver) to the HARQ entity, or the grant (grant) is ignored. The ninth condition may include at least one of the following: the cg-RetransmissionTimer is configured and not running, the HARQ process is not pending, and the configuredGrantTimer is running.

(1-3) If the ninth condition is satisfied, the uplink grant resource or CG resource is not delivered to the HARQ entity, or the grant is ignored. The ninth condition may include at least one of the following: cg-RetransmissionTimer is configured but the configured duration is 0, the HARQ process is not pending, and the configuredGrantTimer is running.

(2), HARQ process state setting, including at least one of the following methods:

(2-1) Consider that the HARQ process corresponding to the deprioritized CG resource is pending; or, consider the HARQ process corresponding to the CG resource with the deprioritized MAC PDU to be pending.

(2-2) Consider that the HARQ process is pending when the HARQ process acquires the MAC PDU. If the MAC PDU transmission is executed, successful or completed, and no LBT failure indication from the lower layer or NW is received, the HARQ process is considered not pending. Or, consider that the HARQ process is pending when the HARQ process acquires the MAC PDU. The resource corresponding to the MAC PDU is not considered to be a deprioritized resource, or it is not transmitted due to a conflict, and the HARQ process is considered not pending

The following is the specific implementation process of Example 1 and Example 2:

Example 1: Set pending or not pending status for HARQ process. For pending HARQ and/or not pending HARQ processes, trigger URLLC automatic transmission.

As shown in Figure 3, the specific implementation process of Example 1 is as follows:

1. The UE receives the CG resource from the network (NW). specific:

(1) The network can configure one or more CG resources for the UE;

(2) The HARQ process corresponding to each CG resource configuration, the HARQ process corresponding to different CG resources may be different or the same.

(3) Configure CG resources in the way of URLLC CG, such as configuring Type-B PUSCH resources.

(4) Configure autonomousTx to trigger automatic transmission.

(5) Optionally, the premise of configuring autonomousTx is: the network is the UE or the corresponding MAC entity or CG resource, and configures LCH-BasedPrioritization (LCH-BasedPrioritization)

(6) Configure configuredGrantTimer, but not configure cg-RetransmissionTimer; or configure configuredGrantTimer and cg-RetransmissionTimer, but the value of cg-RetransmissionTimer is 0.

2. The UE uses the CG resources configured by the network for transmission. specific,

(1) For each CG resource, the MAC entity considers the NDI to be reversed under at least one of the following conditions (see the first condition in the above-mentioned embodiment), and/or delivers the CG resource to the HARQ entity. The condition is:

The PUSCH of the CG does not conflict with the PUSCH resource of the MSGA payload;

The MAC entity is configured with LCH-basedPrioritization;

configuredGrantTimer is not configured;

configuredGrantTimer is configured but not running;

cg-RetransmissionTimer is not configured;

cg-RetransmissionTimer is configured;

cg-RetransmissionTimer is configured but the value is 0.

(2) For an uplink grant (uplink grant), when at least one of the following conditions (see the second condition in the above-mentioned embodiment) is satisfied for the corresponding HARQ process, it is considered that the MAC PDU is acquired. The condition is:

The uplink grant is CG;

The uplink grant is configured with autonomousTx;

The HARQ process is pending;

The size of the uplink grant is the same as the size of the obtained MAC PDU;

The uplink grant is the same as the CG index (index) of the CG before the HARQ process;

The size of the uplink grant is the same CG configuration as the CG before the HARQ process;

The size of the uplink grant is the same CG configuration as the last CG before the HARQ process;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the most recent CG before the HARQ process.

3. If the MAC PDU is acquired for transmission (that is, the MAC PDU to be transmitted is acquired), the MAC PDU is handed over to the HARQ process, and/or, the HARQ process is instructed to perform a new transmission.

4. Set the state of the HARQ process, or consider the HARQ process to be pending or not pending, which may include at least one of the following methods:

(1) When the third condition is satisfied, the corresponding HARQ process is considered to be pending. The third condition is at least one of the following: configure autonomousTx, the uplink resource (uplink grant) is CG, and the HARQ process obtains the MAC PDU for transmission; when the fourth condition is satisfied, it is considered that the corresponding HARQ process is not pending. The fourth condition includes at least one of the following: configuring autonomousTx, the uplink resource is CG, the transmission of the HARQ process is executed/successful/completed, the transmission of the CG/MAC PDU is executed/successful/completed, the LBT of the CG is successful , did not receive the LBT failure indication of the lower layer or NW, did not receive the transmission failure indication of the lower layer or NW, did not receive the retransmission indication of the lower layer or NW, received the LBT success indication of the lower layer or NW, received the lower layer or NW Transmission success indication.

(2) When the fifth condition is satisfied, it is considered that the corresponding HARQ process is pending. The fifth condition includes at least one of the following: configuring autonomousTx, the uplink resource is CG, the transmission of the HARQ process is not executed/unsuccessful/completed, the transmission of the CG or the MAC PDU is not executed, unsuccessful or incomplete, the LBT failure of CG, LBT failure indication of lower layer or NW received, transmission failure indication of lower layer or NW received, retransmission indication of lower layer or NW received, no LBT success indication of lower layer or NW received, no lower layer being received or NW's transmission success indication.

In this example, a method for URLLC automatic transmission of untransmitted or unsuccessfully transmitted MAC PDUs in the case of LBT failure (such as caused by intra-system interference, or error detection) is presented to ensure that the MAC PDU Not discarded, avoid data loss, or make data transfer as fast as possible.

Example 2: Set pending or not pending state for HARQ process of deprioritized CG or low priority MAC PDU. Use NRU automatic retransmission for deprioritized MAC PDUs.

As shown in Figure 4, the specific implementation process of Example 2 is as follows:

1. The UE receives the CG resource from the network (NW). specific:

(1) The network can configure one or more CG resources for the UE;

(3) Configure CG resources in the manner of NRU CG or URLLC CG, such as configuring cg-nrofSlots or Type-B PUSCH resources.

(4) Do not configure autonomousTx,

(5) Configure cg-RetransmissionTimer, or configure cg-RetransmissionTimer with a value of 0 to trigger automatic transmission.

(6) Configure configuredGrantTimer.

2. The UE uses the CG resources configured by the network for transmission. Exemplarily, NRU automatic retransmission is used for deprioritized MAC PDUs. Specifically, it can be at least one of the following:

(1-1) For a CG resource, the MAC entity, if at least one of the following conditions (see the above-mentioned sixth condition) is satisfied, delivers the CG resource to the HARQ entity, and considers NDI inversion (new transmission).

The PUSCH of the CG does not conflict with the PUSCH resources scheduled by RAR or TC-RNTI;

The MAC entity is configured with LCH-basedPrioritization;

cg-RetransmissionTimer is configured but not running;

The HARQ process is pending;

configuredGrantTimer is not running.

(1-2) Correspondingly, under the condition that at least one of the following conditions (see the seventh condition in the above-mentioned embodiment) is satisfied, it is considered that the HARQ process corresponding to the CG resource has acquired the MAC PDU for transmission, that is, acquired the need for transmission the MAC PDU. The condition is:

The uplink grant is CG;

The uplink grant is configured with CG retx timer (CG retransmission timer);

The HARQ process is pending;

The size of the uplink grant is the same as the size of the obtained MAC PDU;

The uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CGindex of the last CG before the HARQ process;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process;

The previous CG corresponding to the HARQ process is the deprioritized CG;

The last CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

(1-3) If the MAC PDU is acquired for transmission, submit the MAC PDU to the HARQ process, and/or instruct the HARQ process to perform a new transmission.

(1-4) Set the HARQ process status, or consider the HARQ process as pending or not pending, including at least one of the following:

Set the HARQ process corresponding to the low-priority CG resource as pending;

Determine the conflicting uplink grant resource or CG resource as pending;

Determine the HARQ process when the MAC PDU is obtained as pending;

Determine the non-conflicting uplink grant resource or CG resource as not pending;

Determine the uplink grant resource or CG resource that is not conflicting and LBT has not failed as not pending;

MAC PDU transmission is executed, successful or completed, and the HARQ process is determined as not pending;

MAC PDU transmission is executed, successful or completed, and no LBT failure indication from the lower layer or NW is received, and the HARQ process is determined as not pending;

MAC PDU transmission is executed, successful or completed, and the LBT success indication from the lower layer or NW is received, and the HARQ process is determined as not pending;

The uplink grant resource corresponding to the MAC PDU is a priority resource, and the resource corresponding to the MAC PDU is not a low-priority resource, and the HARQ process or MAC PDU is determined as not pending;

(2-1) For a CG resource, a MAC entity, if at least one of the following conditions (see the sixth condition in the above-mentioned embodiment) is satisfied, deliver the CG resource to the HARQ entity, but do not consider the NDI to be reversed (reset pass).

The MAC entity is configured with LCH-basedPrioritization;

cg-RetransmissionTimer is configured but not running;

The HARQ process is pending;

configuredGrantTimer is not running.

(2-2) Correspondingly, deliver the MAC PDU to the HARQ process, and/or instruct the HARQ process to perform retransmission. Alternatively, when at least one of the following conditions (see the eighth condition in the above-mentioned embodiment) is satisfied, the MAC PDU is delivered to the HARQ process, and/or the HARQ process is instructed to perform retransmission. The conditions include:

The uplink grant is CG;

The uplink grant is configured with CG retx timer;

The HARQ process is pending;

Get MAC PDU;

The size of the uplink grant is the same as the size of the obtained MAC PDU;

The uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process;

The previous CG corresponding to the HARQ process is the deprioritized CG;

The last CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

(2-3) Set the state of the HARQ process, or consider the HARQ process as pending or not pending. For details, refer to the relevant description in (1-4) above.

(3-1) For an uplink grant resource or CG resource, the MAC entity does not deliver the uplink grant resource or CG resource to the HARQ process when the following conditions are met (see the ninth condition in the above embodiment), or, Ignore the grant; or, deliver the CG resource to the HARQ process, but ignore the grant. The condition is at least one of the following: cg-RetransmissionTimer is configured and not running, the HARQ process is not pending, and configuredGrantTimer is running.

(3-2) Correspondingly: Set the state of the HARQ process, or consider the HARQ process as pending or not pending. For details, please refer to the relevant description in (1-4) above.

(4-1) For an uplink grant resource or CG resource, the MAC entity does not deliver the uplink grant resource or CG resource to the HARQ process, or ignores the grant when the following conditions are met (see the ninth condition above). ; Or, deliver the uplink grant resource or CG resource to the HARQ process, but ignore the grant. The condition is at least one of the following: cg-RetransmissionTimer is configured and the configured duration is 0, the HARQ process is not pending, and the configuredGrantTimer is running.

(4-2) Correspondingly: Set the HARQ process status, or consider the HARQ process as pending or not pending, for details, please refer to the relevant description in the above (1-4).

In this example, a method for automatic NRU transmission of deprioritized resources is given to ensure that the MAC PDU is not discarded to avoid data loss, or to be transmitted as soon as possible.

FIG. 5 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application. The terminal device 400 may include:

a receiving unit 410, configured to receive configuration authorization CG resources;

The transmission unit 420 is configured to use the CG resource to automatically transmit the object of the first type using the mechanism of the second type.

Optionally, in this embodiment of the present application, the transmitting unit 420 is further configured to use the CG resource to automatically transmit the object of the first communication scene using the transmission mechanism of the second communication scene.

Optionally, in the first mode of this embodiment of the present application, the receiving unit 410 is further configured to receive one or more CG resources from the network, each CG resource has a corresponding HARQ process of HARQ, and each CG resource has a corresponding HARQ process. The resource includes at least one of the following configurations:

Configure the automatic transmission parameter autonomousTx to trigger automatic transmission;

Configure the CG timer, but do not configure the CG retransmission timer;

Optionally, in the first manner of the embodiment of the present application, the precondition for configuring the autonomousTx includes: the terminal device, the MAC entity or the CG resource of the terminal device are configured to be preferentially processed based on the logical channel LCH.

Optionally, in the second manner of the embodiment of the present application, the receiving unit 410 is further configured to receive one or more CG resources from the network, each CG resource has a corresponding HARQ process of HARQ, and each CG resource has a corresponding HARQ process. The resource includes at least one of the following configurations:

Do not configure the automatic transmission parameter autonomousTx,

Configure the CG retransmission timer to trigger automatic transmission;

Configure the CG timer.

Optionally, in the first manner of the embodiment of the present application, the CG resource is configured in the manner of a new wireless unlicensed NRU CG or an ultra-reliable and low-latency communication URLLC CG.

Optionally, in the first manner of this embodiment of the present application, the transmission unit 420 is further configured to automatically transmit at least one of the following objects:

The HARQ process or MAC PDU corresponding to downlink feedback information DFI or downlink control information DCI is not received due to downlink LBT failure.

Optionally, in the first manner of this embodiment of the present application, the manner in which the transmission unit 420 performs automatic transmission includes at least one of the following:

Automatic transmission based on autonomousTx transmission mode;

Optionally, in Manner 1 of this embodiment of the present application, the transmission unit 420 is further configured to, for a CG resource, when the first condition is satisfied, determine that the new data of the HARQ process indicates NDI inversion, and/or, convert the The CG resource is delivered to the HARQ entity.

The physical uplink shared channel PUSCH of the CG does not conflict with the PUSCH resource scheduled by the DCI;

The PUSCH of the CG does not conflict with the PUSCH resource scheduled by the random access response RAR or the temporary cell radio network temporary identifier TC-RNTI;

The PUSCH of the CG does not conflict with the PUSCH resource of the two-step random access message A;

The MAC entity is configured with LCH-based priority processing;

CG timer is not configured;

CG timer is configured but not running;

CG retransmission timer is not configured;

CG retransmission timer is configured;

The CG retransmission timer is configured but the value is 0.

Optionally, in the first manner of the embodiment of the present application, the transmission unit 420 is further configured to, for a HARQ process corresponding to an uplink grant, determine that a MAC PDU is acquired when a second condition is satisfied, and the second condition includes: At least one of the following:

the uplink authorization is CG;

The uplink grant is configured with the automatic transmission parameter autonomousTx

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size;

The uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured bandwidth part BWP is the same;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process.

Optionally, in the first manner of this embodiment of the present application, the transmission unit 420 is further configured to, in the case of acquiring the MAC PDU to be transmitted, submit the MAC PDU to the HARQ process, and/or indicate the HARQ process The process performs a new pass.

Optionally, in the first manner of the embodiment of the present application, the transmission unit 420 is further configured to determine the status of the HARQ process in the following manner:

When the third condition is satisfied, the HARQ process is pending, and the third condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the HARQ process obtains the MAC PDU to be transmitted; and/ or,

When the fourth condition is met, the HARQ process is not pending, and the fourth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process is executed, successful or Completed, the uplink grant is a priority transmission resource, the uplink grant is a non-resource conflict uplink grant, the transmission of the uplink grant or the CG or the MAC PDU is executed, successful or completed, and the LBT of the uplink grant or the CG is successful, No LBT failure indication is received, no transmission failure indication is received, no retransmission indication is received, LBT success indication is received, and transmission successful indication is received.

Optionally, in the first manner of this embodiment of the present application, the transmission unit 420 is further configured to determine the status of the HARQ process in the following manner:

When the fifth condition is satisfied, the HARQ process corresponding to the CG resource is pending, and the fifth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, the transmission of the HARQ process is not executed, If the uplink grant is unsuccessful or incomplete, the uplink grant is a low-priority resource, the uplink grant is an uplink grant with conflicting resources, the uplink grant or the transmission of the CG or the MAC PDU is not executed, unsuccessful or incomplete, the uplink grant Or the LBT of the CG fails, the LBT failure indication is received, the transmission failure indication is received, the retransmission indication is received, the LBT success indication is not received, and the transmission successful indication is not received.

Optionally, in the second manner of this embodiment of the present application, the manner in which the transmission unit 420 performs automatic transmission includes at least one of the following:

Low-priority resources or CGs for automatic transmission;

Perform automatic transmission or automatic retransmission based on the pending state of the HARQ process;

Automatic transmission or automatic retransmission based on DFI instructions;

Optionally, in the second manner of this embodiment of the present application, the transmitting unit 420 is further configured to, for a CG resource, deliver the CG resource to the HARQ entity when the MAC entity of the terminal device satisfies the sixth condition.

The MAC entity is configured with LCH-based priority processing;

CG retransmission timer is configured but not running;

The HARQ process is pending;

CG timer is not running.

Optionally, in the second manner of this embodiment of the present application, the transmission unit 420 is further configured to determine the NDI inversion of the HARQ process.

Optionally, in the second manner of this embodiment of the present application, the transmission unit 420 is further configured to determine that the NDI of the HARQ process is not reversed.

Optionally, in the second manner of this embodiment of the present application, if the NDI is reversed, the transmission unit 420 is further configured to determine that the HARQ process corresponding to the CG resource obtains the MAC PDU that needs to be transmitted under the condition that the seventh condition is satisfied. The seventh condition includes at least one of the following:

the uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size

The uplink grant is the same as the CG index of the CG before the HARQ process;

The previous CG corresponding to the HARQ process is a low-priority CG;

The last CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

Optionally, in the second manner of the embodiment of the present application, if the NDI is reversed, the transmission unit 420 is further configured to submit the MAC PDU to the HARQ process when the MAC PDU to be transmitted is obtained, and/or, Instructs the HARQ process to perform a new transmission.

Optionally, in the second manner of the embodiment of the present application, if the NDI is not reversed, the transmission unit 420 is further configured to deliver the MAC PDU to the HARQ process, and/or instruct the HARQ process to perform retransmission.

Optionally, in the second manner of the embodiment of the present application, if the NDI is not reversed, the transmission unit 420 is further configured to deliver the MAC PDU to the HARQ process under the condition that the eighth condition is satisfied, and/or to indicate the HARQ process Perform retransmission, and the eighth condition includes at least one of the following:

the uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

Get MAC PDU;

The uplink grant size is the same as the acquired MAC PDU size;

The uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is on the same BWP as the CG before the HARQ process;

The previous CG corresponding to the HARQ process is a low-priority CG;

The last CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

Optionally, in Manner 2 of this embodiment of the present application, the transmission unit 420 is further configured to perform at least one of the following steps for an uplink grant resource or CG resource when the ninth condition is satisfied:

Do not deliver uplink grant resources or CG resources to the HARQ entity;

ignore the uplink grant resource or CG resource;

CG retransmission timer is configured but not running;

CG retransmission timer is configured but the value is 0;

is not pending in the HARQ process;

The CG timer runs.

Optionally, in the second manner of this embodiment of the present application, the transmission unit 420 is further configured to determine the status of the HARQ process by adopting at least one of the following manners:

Determine the conflicting uplink grant resource or CG resource as pending;

Determine the HARQ process when the MAC PDU is obtained as pending;

If the MAC PDU transmission is executed, successful or completed, and no LBT failure indication is received, the HARQ process is determined as not pending;

The terminal device 400 in this embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing method embodiments. For the corresponding processes, functions, implementations, and beneficial effects of each module (submodule, unit, or component, etc.) in the terminal device 400, reference may be made to the corresponding descriptions in the foregoing method embodiments, which are not repeated here. It should be noted that the functions described by each module (submodule, unit, or component, etc.) in the terminal device 400 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or may be implemented by the same module Module (submodule, unit or component, etc.) implementation.

FIG. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so that the communication device 600 implements the methods in the embodiments of the present application.

Optionally, the communication device 600 may also include a memory 620 . The processor 610 may call and run a computer program from the memory 620, so that the communication device 600 implements the methods in the embodiments of the present application. The memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices . Among them, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of the antennas may be one or more.

Optionally, the communication device 600 may be the network device of this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.

Optionally, the communication device 600 may be a terminal device in this embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the terminal device in each method in the embodiment of the present application, which is not repeated here for brevity.

FIG. 7 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiments of the present application.

Optionally, the chip 700 may further include a memory 720 . The processor 710 may call and run a computer program from the memory 720 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

The memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may further include an input interface 730 . The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740 . The processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.

Optionally, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which is not repeated here for brevity.

Chips applied to network equipment and terminal equipment can be the same chip or different chips.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc. Wherein, the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.

The memory mentioned above may be either volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM).

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

FIG. 8 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a terminal device 810 and a network device 820 . The terminal device 810 is configured to receive the configuration authorization CG resource; and use the CG resource to automatically transmit the first-type object by using the second-type mechanism. The network device 820 is configured to send the CG resource to the terminal device. The terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can 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 program instructions are loaded and executed on a computer, the procedures 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 device. The computer instructions may be stored on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)), and the like.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art who is familiar with the technical scope disclosed in the present application can easily think of changes or substitutions. Covered within the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of transmission comprising:

The terminal device receives and configures authorized CG resources;

The terminal device uses the CG resource to automatically transmit the first-type object by using the second-type mechanism.
The method according to claim 1, wherein the terminal device uses the CG resource to automatically transmit the first type of objects by using the second type mechanism, comprising:

The terminal device uses the CG resource to automatically transmit the object of the first communication scene using the transmission mechanism of the second communication scene.
The method according to claim 1 or 2, wherein the terminal device receives CG resources, comprising:

The terminal device receives one or more CG resources from the network, each CG resource has a corresponding HARQ process, and each CG resource includes at least one of the following configurations:

Configure the automatic transmission parameter autonomousTx to trigger automatic transmission;

Configure the CG timer, but do not configure the CG retransmission timer;

Configure the CG timer and CG retransmission timer, but the value of the CG retransmission timer is 0.
The method according to claim 3, wherein the premise of configuring the autonomousTx includes: the terminal device, the MAC entity or the CG resource of the terminal device are configured to be prioritized based on the logical channel LCH.
The method according to claim 1 or 2, wherein the terminal device receives CG resources, comprising:

The terminal device receives one or more CG resources from the network, each CG resource has a corresponding HARQ process, and each CG resource includes at least one of the following configurations:

Do not configure the automatic transmission parameter autonomousTx,

Configure the CG retransmission timer to trigger automatic transmission;

Configure the CG retransmission timer with a value of 0 to trigger automatic transmission;

Configure the CG timer.
The method according to any one of claims 1 to 5, wherein the CG resource is configured in the manner of a new wireless unlicensed NRU CG or an ultra-reliable and low-latency communication URLLC CG.
The method according to any one of claims 1 to 6, wherein the terminal device uses the CG resource to automatically transmit the first type of objects by using the second type mechanism, comprising:

Automatic transfer of at least one of the following objects:

Media access control MAC protocol data unit PDUs that have not been transmitted, have not been successfully transmitted, or have not been transmitted;

HARQ processes or MAC PDUs that were not transmitted, were not successfully transmitted, or were not transmitted due to LBT failure;

The HARQ process is not changed due to LBT failure, or the HARQ process is still a pending HARQ process or MAC PDU;

The HARQ process or MAC PDU corresponding to downlink feedback information DFI or downlink control information DCI is not received due to downlink LBT failure.
The method of claim 7, wherein performing automatic transmission comprises at least one of the following:

Automatic transmission based on autonomousTx transmission mode;

Automatic transmission based on the automatic transmission method of licensed spectrum;

Automatic transmission based on low-priority data or low-priority MAC PDU transmission;

Automatic transmission based on low-priority resources or low-priority CG transmission methods;

Automatic transmission based on the transmission mode of low-priority data or low-priority MAC PDU caused by resource conflict;

Automatic transmission is performed based on the transmission mode of low-priority resources or low-priority CGs caused by resource conflicts.
The method according to claim 7 or 8, wherein the automatic transmission is URLLC automatic transmission.
The method of any one of claims 7 to 9, wherein the automatic transmission comprises:

For one CG resource, when the first condition is satisfied, the MAC entity of the terminal device determines that the new data of the HARQ process indicates NDI inversion, and/or, delivers the CG resource to the HARQ entity.
The method of claim 10, wherein the first condition includes at least one of the following:

The physical uplink shared channel PUSCH of the CG does not conflict with the PUSCH resource scheduled by the DCI;

The PUSCH of the CG does not conflict with the PUSCH resource scheduled by the random access response RAR or the temporary cell radio network temporary identifier TC-RNTI;

The PUSCH of the CG does not conflict with the PUSCH resource of the two-step random access message A;

The MAC entity is configured with LCH-based priority processing;

CG timer is not configured;

CG timer is configured but not running;

CG retransmission timer is not configured;

CG retransmission timer is configured;

The CG retransmission timer is configured but the value is 0.
The method of any one of claims 7 to 11, wherein performing automatic transmission, further comprising:

For a HARQ process corresponding to an uplink grant, the MAC entity or the HARQ entity of the terminal device determines that a MAC PDU is acquired when a second condition is satisfied, and the second condition includes at least one of the following:

The uplink authorization is CG;

The uplink authorization is configured with the automatic transmission parameter autonomousTx

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size;

the size of the uplink grant is the same as the size of the CG before the HARQ process;

The size of the uplink grant is the same as the size of the last CG before the HARQ process;

the uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the latest CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured bandwidth part BWP is the same;

The uplink grant size and the CG before the HARQ process are the same CG configuration;

The uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the latest CG before the HARQ process are the same CG configuration;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process.
The method of any one of claims 7 to 12, wherein performing automatic transmission, further comprising:

When the MAC entity or HARQ entity of the terminal device acquires the MAC PDU to be transmitted, it submits the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform new transmission.
The method according to any one of claims 7 to 13, wherein the automatic transmission further comprises: the MAC entity or the HARQ entity of the terminal device determines the state of the HARQ process in the following manner:

In the case where the third condition is met, the HARQ process is pending, and the third condition includes at least one of the following: configure the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the HARQ process obtains the MAC PDU to be transmitted; and / or,

When the fourth condition is satisfied, the HARQ process is not pending, and the fourth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process is performed , success or completion, the uplink grant is a priority transmission resource, the uplink grant is a non-resource conflict uplink grant, the uplink grant or the transmission of the CG or the MAC PDU is executed, successful or completed, the uplink grant Or the LBT of the CG succeeds, no LBT failure indication is received, no transmission failure indication is received, no retransmission indication is received, an LBT success indication is received, and a transmission successful indication is received.
The method of any one of claims 7 to 14, wherein performing automatic transmission further comprises determining the status of the HARQ process in the following manner:

When the fifth condition is satisfied, the HARQ process corresponding to the CG resource is pending, and the fifth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process Not executed, unsuccessful or incomplete, the uplink grant is a low-priority resource, the uplink grant is an uplink grant of resource conflict, the transmission of the uplink grant or the CG or the MAC PDU is not executed, unsuccessful Or not completed, the LBT of the uplink grant or the CG fails, the LBT failure indication is received, the transmission failure indication is received, the retransmission indication is received, the LBT success indication is not received, and the transmission success indication is not received.
The method according to any one of claims 1 to 6, wherein the terminal device uses the CG resource to automatically transmit the first type of objects by using the second type mechanism, including at least one of the following:

Automatic transmission of MAC PDUs that have not been transmitted, have not been successfully transmitted or have not been transmitted;

Automatic transmission of HARQ processes or MAC PDUs that have not been transmitted, have not been successfully transmitted, or have not been transmitted due to resource conflicts;

Low-priority resources or CGs for automatic transmission;

Automatic transmission of MAC PDUs that are considered low priority or low priority data.
The method of claim 16, wherein performing the automatic transmission comprises at least one of the following:

Automatic transmission or automatic retransmission based on the retransmission method of unlicensed spectrum;

Automatic transmission or automatic retransmission based on the pending state of the HARQ process;

Automatic transmission or automatic retransmission based on DFI instructions;

Automatic transmission or automatic retransmission based on the transmission mode of the CG retransmission timer;

Automatic transmission or automatic retransmission based on the untransmitted MAC PDU transmission mode caused by LBT failure;

Automatic transmission or automatic retransmission based on the fact that the HARQ process is not changed due to LBT failure, or the HARQ process is still in the pending transmission mode;

Automatic transmission or automatic retransmission is performed based on the DFI or DCI not receiving the corresponding transmission mode caused by the downlink LBT failure.
The method of claim 16 or 17, wherein the automatic transmission is an NRU automatic transmission.
The method of any one of claims 16 to 18, performing automatic transmission, comprising:

For one CG resource, the MAC entity of the terminal device submits the CG resource to the HARQ entity under the condition that the sixth condition is satisfied.
The method of claim 19, the sixth condition comprising at least one of the following:

The PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;

The PUSCH of the CG does not conflict with the PUSCH resource scheduled by the RAR/TC-RNTI;

The PUSCH of the CG does not conflict with the PUSCH resources of the MSGA payload;

The MAC entity is configured with LCH-based priority processing;

CG retransmission timer is configured but not running;

The HARQ process is pending;

CG timer is not running.
The method of claim 19 or 20, the MAC entity determines NDI rollover of the HARQ process.
The method of claim 19 or 20, the MAC entity determines that the NDI of the HARQ process is not flipped.
The method of claim 21, performing automatic transmission, further comprising:

The MAC entity or the HARQ entity of the terminal device determines that the HARQ process corresponding to the CG resource obtains the MAC PDU that needs to be transmitted when a seventh condition is satisfied, and the seventh condition includes at least one of the following:

Uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size

the size of the uplink grant is the same as the size of the CG before the HARQ process;

the uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the CG before the HARQ process are the same CG configuration;

The previous CG corresponding to the HARQ process is a low-priority CG;

The previous most recent CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

In the HARQ process, there are MAC PDUs that have not been transmitted, have not been successfully transmitted, have not been transmitted or have not been transmitted due to resource conflict.
The method of claim 21, performing automatic transmission, further comprising:

When the MAC entity or HARQ entity of the terminal device obtains the MAC PDU to be transmitted, it submits the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform a new transmission.
The method of claim 22, performing automatic transmission, further comprising:

The MAC entity or HARQ entity of the terminal device delivers the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform retransmission.
The method according to claim 25, wherein the MAC entity or the HARQ entity of the terminal device delivers the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform retransmission, comprising:

The MAC entity or the HARQ entity submits the MAC PDU to the HARQ process and/or instructs the HARQ process to perform retransmission under the condition that the eighth condition is satisfied, and the eighth condition includes at least one of the following:

Uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

Get MAC PDU;

The uplink grant size is the same as the acquired MAC PDU size;

the size of the uplink grant is the same as the size of the CG before the HARQ process;

The size of the uplink grant is the same as the size of the last CG before the HARQ process;

the uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the latest CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the CG before the HARQ process are the same CG configuration;

The uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the latest CG before the HARQ process are the same CG configuration;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process;

The previous CG corresponding to the HARQ process is a low-priority CG;

The previous most recent CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

In the HARQ process, there are MAC PDUs that have not been transmitted, have not been successfully transmitted, have not been transmitted or have not been transmitted due to resource conflict.
The method of any one of claims 16 to 26, performing automatic transmission, comprising:

For an uplink grant resource or CG resource, the MAC entity or the HARQ entity performs at least one of the following steps when the ninth condition is satisfied:

Do not deliver uplink grant resources or CG resources to the HARQ entity;

ignore the uplink grant resource or CG resource;

The uplink grant resources or CG resources are submitted to the HARQ process but the uplink grant resources or CG resources are ignored.
The method of claim 27, the ninth condition comprising at least one of the following:

CG retransmission timer is configured but not running;

CG retransmission timer is configured but the value is 0;

is not pending in the HARQ process;

The CG timer runs.
The method of any one of claims 16 to 28, performing automatic transmission, further comprising:

Determine the status of the HARQ process in at least one of the following ways:

Determine the HARQ process corresponding to the low-priority uplink grant resource as pending;

Determine the HARQ process corresponding to the uplink grant resource of the low-priority MAC PDU as pending;

Determine the HARQ process corresponding to the low-priority CG resource as pending;

Determine the HARQ process corresponding to the CG resource of the low-priority MAC PDU as pending;

Determine the conflicting uplink grant resource or CG resource as pending;

Determine the HARQ process when the MAC PDU is obtained as pending;

Determine the HARQ process when the MAC PDU corresponding to the CG resource is obtained as pending;

Determine the conflicting and prioritized uplink authorized resources or CG resources as pending;

Determine the unconflicted uplink authorized resource or CG resource as not pending;

Determine the uplink authorized resources or CG resources that are not conflicting and LBT has not failed as not pending;

MAC PDU transmission execution, success or completion, determine the HARQ process as not pending,

MAC PDU transmission is executed, successful or completed, and no LBT failure indication is received, and the HARQ process is determined as not pending;

MAC PDU transmission is executed, successful or completed, and the LBT success indication is received, and the HARQ process is determined as not pending;

The uplink authorization resource corresponding to the MAC PDU is a priority resource, and the resource corresponding to the MAC PDU is not a low-priority resource, and the HARQ process or the MAC PDU is determined as not pending;

The uplink grant resource corresponding to the MAC PDU is not a low-priority resource, or it is not transmitted due to a conflict, and the HARQ process is determined as not pending.
A terminal device including:

a receiving unit, configured to receive configuration authorization CG resources;

A transmission unit, used for the terminal device to automatically transmit the first-type object by using the second-type mechanism by using the CG resource.
The terminal device according to claim 30, wherein the transmission unit is further configured to use the CG resource to automatically transmit the object of the first communication scene using the transmission mechanism of the second communication scene.
The terminal device according to claim 30 or 31, wherein the receiving unit is further configured to receive one or more CG resources from the network, each CG resource has a corresponding HARQ process, and each CG resource has a corresponding HARQ process. The resource includes at least one of the following configurations:

Configure the automatic transmission parameter autonomousTx to trigger automatic transmission;

Configure the CG timer, but do not configure the CG retransmission timer;

Configure the CG timer and CG retransmission timer, but the value of the CG retransmission timer is 0.
The terminal device according to claim 32, wherein the premise of configuring the autonomousTx comprises: the terminal device, the MAC entity or the CG resource of the terminal device are configured to be preferentially processed based on the logical channel LCH.
The terminal device according to claim 30 or 31, wherein the receiving unit is further configured to receive one or more CG resources from the network, each CG resource has a corresponding HARQ process, and each CG resource has a corresponding HARQ process. The resource includes at least one of the following configurations:

Do not configure the automatic transmission parameter autonomousTx,

Configure the CG retransmission timer to trigger automatic transmission;

Configure the CG retransmission timer with a value of 0 to trigger automatic transmission;

Configure the CG timer.
The terminal device according to any one of claims 30 to 34, wherein the CG resources are configured in the manner of a new wireless unlicensed NRU CG or an ultra-reliable and low-latency communication URLLC CG.
The terminal device according to any one of claims 30 to 35, wherein the transmission unit is further configured to automatically transmit at least one of the following objects:

Media access control MAC protocol data unit PDUs that have not been transmitted, have not been successfully transmitted, or have not been transmitted;

HARQ processes or MAC PDUs that were not transmitted, were not successfully transmitted, or were not transmitted due to LBT failure;

The HARQ process is not changed due to LBT failure, or the HARQ process is still a pending HARQ process or MAC PDU;

The HARQ process or MAC PDU corresponding to downlink feedback information DFI or downlink control information DCI is not received due to downlink LBT failure.
The terminal device according to claim 36, wherein the manner in which the transmission unit performs automatic transmission comprises at least one of the following:

Automatic transmission based on autonomousTx transmission mode;

Automatic transmission based on the automatic transmission method of licensed spectrum;

Automatic transmission based on low-priority data or low-priority MAC PDU transmission;

Automatic transmission based on low-priority resources or low-priority CG transmission methods;

Automatic transmission based on the transmission mode of low-priority data or low-priority MAC PDU caused by resource conflict;

Automatic transmission is performed based on the transmission mode of low-priority resources or low-priority CGs caused by resource conflicts.
The terminal device according to claim 36 or 37, wherein the automatic transmission is URLLC automatic transmission.
The terminal device according to any one of claims 36 to 38, wherein the transmission unit is further configured to, for one CG resource, in the case that the first condition is satisfied, determine that the new data of the HARQ process indicates NDI inversion, and /or, delivering the CG resource to the HARQ entity.
The terminal device according to claim 39, wherein the first condition includes at least one of the following:

The physical uplink shared channel PUSCH of the CG does not conflict with the PUSCH resource scheduled by the DCI;

The PUSCH of the CG does not conflict with the PUSCH resource scheduled by the random access response RAR or the temporary cell radio network temporary identifier TC-RNTI;

The PUSCH of the CG does not conflict with the PUSCH resource of the two-step random access message A;

The MAC entity is configured with LCH-based priority processing;

CG timer is not configured;

CG timer is configured but not running;

CG retransmission timer is not configured;

CG retransmission timer is configured;

The CG retransmission timer is configured but the value is 0.
The terminal device according to any one of claims 36 to 40, wherein the transmission unit is further configured to, for a HARQ process corresponding to an uplink grant, determine that a MAC PDU is acquired when the second condition is satisfied, and the The second condition includes at least one of the following:

The uplink authorization is CG;

The uplink authorization is configured with the automatic transmission parameter autonomousTx

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size;

the size of the uplink grant is the same as the size of the CG before the HARQ process;

The size of the uplink grant is the same as the size of the last CG before the HARQ process;

the uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the latest CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured bandwidth part BWP is the same;

The uplink grant size and the CG before the HARQ process are the same CG configuration;

The uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the latest CG before the HARQ process are the same CG configuration;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process.
The terminal device according to any one of claims 36 to 41, wherein the transmission unit is further configured to deliver the MAC PDU to the HARQ process, and/or, instructing the HARQ process to perform a new transmission.
The terminal device according to any one of claims 36 to 42, wherein the transmission unit is further configured to determine the status of the HARQ process in the following manner:

In the case where the third condition is met, the HARQ process is pending, and the third condition includes at least one of the following: configure the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the HARQ process obtains the MAC PDU to be transmitted; and / or,

When the fourth condition is satisfied, the HARQ process is not pending, and the fourth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process is performed , success or completion, the uplink grant is a priority transmission resource, the uplink grant is a non-resource conflict uplink grant, the uplink grant or the transmission of the CG or the MAC PDU is executed, successful or completed, the uplink grant Or the LBT of the CG succeeds, no LBT failure indication is received, no transmission failure indication is received, no retransmission indication is received, an LBT success indication is received, and a transmission successful indication is received.
The terminal device according to any one of claims 36 to 43, wherein the transmission unit is further configured to determine the status of the HARQ process in the following manner:

When the fifth condition is satisfied, the HARQ process corresponding to the CG resource is pending, and the fifth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process Unexecuted, unsuccessful or incomplete, the uplink grant is a low-priority resource, the uplink grant is an uplink grant with conflicting resources, the transmission of the uplink grant or the CG or the MAC PDU is not executed or unsuccessful Or not completed, the LBT of the uplink grant or the CG fails, the LBT failure indication is received, the transmission failure indication is received, the retransmission indication is received, the LBT success indication is not received, and the transmission success indication is not received.
The terminal device according to any one of claims 30 to 35, wherein the manner in which the transmission unit performs automatic transmission includes at least one of the following:

Automatic transmission of MAC PDUs that have not been transmitted, have not been successfully transmitted or have not been transmitted;

Automatic transmission of HARQ processes or MAC PDUs that have not been transmitted, have not been successfully transmitted, or have not been transmitted due to resource conflicts;

Low-priority resources or CGs for automatic transmission;

Automatic transmission of MAC PDUs that are considered low priority or low priority data.
The terminal device according to claim 45, wherein the manner in which the transmission unit performs automatic transmission comprises at least one of the following:

Automatic transmission or automatic retransmission based on the retransmission method of unlicensed spectrum;

Perform automatic transmission or automatic retransmission based on the pending state of the HARQ process;

Automatic transmission or automatic retransmission based on DFI instructions;

Automatic transmission or automatic retransmission based on the transmission mode of the CG retransmission timer;

Automatic transmission or automatic retransmission based on the untransmitted MAC PDU transmission mode caused by LBT failure;

Based on the HARQ process that is not changed due to LBT failure, or the HARQ process is still in the pending transmission mode, automatic transmission or automatic retransmission is performed;

Automatic transmission or automatic retransmission is performed based on the DFI or DCI not receiving the corresponding transmission mode caused by the downlink LBT failure.
The terminal device according to claim 45 or 46, wherein the automatic transmission is an NRU automatic transmission.
The terminal device according to any one of claims 45 to 47, wherein the transmission unit is further configured to, for one CG resource, the MAC entity of the terminal device submits the CG resource under the condition that the sixth condition is satisfied to the HARQ entity.
The terminal device according to claim 48, the sixth condition comprises at least one of the following:

The PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;

The PUSCH of the CG does not conflict with the PUSCH resource scheduled by the RAR/TC-RNTI;

The PUSCH of the CG does not conflict with the PUSCH resources of the MSGA payload;

The MAC entity is configured with LCH-based priority processing;

CG retransmission timer is configured but not running;

The HARQ process is pending;

CG timer is not running.
The terminal device according to claim 48 or 49, wherein the transmission unit is further configured to determine the NDI inversion of the HARQ process.
The terminal device according to claim 48 or 49, wherein the transmission unit is further configured to determine that the NDI of the HARQ process is not inverted.
The terminal device according to claim 50, wherein the transmission unit is further configured to determine that the HARQ process corresponding to the CG resource obtains the MAC PDU to be transmitted when a seventh condition is satisfied, and the seventh condition includes the following at least one of:

Uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

The uplink grant size is the same as the acquired MAC PDU size

the size of the uplink grant is the same as the size of the CG before the HARQ process;

the uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the CG before the HARQ process are the same CG configuration;

The previous CG corresponding to the HARQ process is a low-priority CG;

The previous most recent CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

In the HARQ process, there are MAC PDUs that have not been transmitted, have not been successfully transmitted, have not been transmitted or have not been transmitted due to resource conflict.
The terminal device according to claim 50, wherein the transmission unit is further configured to deliver the MAC PDU to the HARQ process when the MAC PDU to be transmitted is acquired, and/or instruct the HARQ process to execute a new pass.
The terminal device according to claim 51, wherein the transmission unit is further configured to deliver a MAC PDU to the HARQ process, and/or instruct the HARQ process to perform retransmission.
The terminal device according to claim 54, wherein the transmission unit is further configured to deliver the MAC PDU to the HARQ process when an eighth condition is satisfied, and/or instruct the HARQ process to perform retransmission, the eighth condition Include at least one of the following:

Uplink authorization is CG;

The uplink grant is configured with a CG retransmission timer;

The HARQ process is pending;

Get MAC PDU;

The uplink grant size is the same as the acquired MAC PDU size;

the size of the uplink grant is the same as the size of the CG before the HARQ process;

The size of the uplink grant is the same as the size of the last CG before the HARQ process;

the uplink grant is the same as the CG index of the CG before the HARQ process;

The uplink grant is the same as the CG index of the latest CG before the HARQ process;

The uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the CG before the HARQ process are the same CG configuration;

The uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;

The uplink grant size and the latest CG before the HARQ process are the same CG configuration;

The uplink grant is on the same BWP as the CG before the HARQ process;

The uplink grant is on the same BWP as the last CG before the HARQ process;

The previous CG corresponding to the HARQ process is a low-priority CG;

The previous most recent CG corresponding to the HARQ process is a low-priority CG;

There is a low-priority MAC PDU in the HARQ process;

In the HARQ process, there are MAC PDUs that have not been transmitted, have not been successfully transmitted, have not been transmitted or have not been transmitted due to resource conflict.
The terminal device according to any one of claims 45 to 55, wherein the transmission unit is further configured to perform at least one of the following steps for one uplink grant resource or CG resource when the ninth condition is satisfied:

Do not deliver uplink grant resources or CG resources to the HARQ entity;

ignore the uplink grant resource or CG resource;

The uplink grant resources or CG resources are submitted to the HARQ process but the uplink grant resources or CG resources are ignored.
The terminal device according to claim 56, the ninth condition comprises at least one of the following:

CG retransmission timer is configured but not running;

CG retransmission timer is configured but the value is 0;

is not pending in the HARQ process;

The CG timer runs.
The terminal device according to any one of claims 45 to 57, wherein the transmission unit is further configured to determine the status of the HARQ process in at least one of the following manners:

Determine the HARQ process corresponding to the low-priority uplink grant resource as pending;

Determine the HARQ process corresponding to the uplink grant resource of the low-priority MAC PDU as pending;

Determine the HARQ process corresponding to the low-priority CG resource as pending;

Determine the HARQ process corresponding to the CG resource of the low-priority MAC PDU as pending;

Determine the conflicting uplink grant resource or CG resource as pending;

Determine the HARQ process when the MAC PDU is obtained as pending;

Determine the HARQ process when the MAC PDU corresponding to the CG resource is obtained as pending;

Determine the conflicting and prioritized uplink authorized resources or CG resources as pending;

Determine the unconflicted uplink authorized resource or CG resource as not pending;

Determine the uplink authorized resources or CG resources that are not conflicting and LBT has not failed as not pending;

MAC PDU transmission execution, success or completion, determine the HARQ process as not pending,

MAC PDU transmission is executed, successful or completed, and no LBT failure indication is received, and the HARQ process is determined as not pending;

MAC PDU transmission is executed, successful or completed, and the LBT success indication is received, and the HARQ process is determined as not pending;

The resource corresponding to the MAC PDU is a priority resource, and the resource corresponding to the MAC PDU is not a low-priority resource, and the HARQ process or the MAC PDU is determined as not pending;

The uplink grant resource corresponding to the MAC PDU is not a low-priority resource, or it is not transmitted due to a conflict, and the HARQ process is determined as not pending.
A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the performance as claimed in claims 1 to 29 The method of any of the above.
A chip, comprising: a processor for calling and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 1 to 29.
A computer-readable storage medium for storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1 to 29.
A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 29.
A computer program that causes a computer to perform the method of any one of claims 1 to 29.