Transmission method and terminal device

Abstract

The present application relates to a transmission method and a terminal device. The transmission method includes: the terminal device receives a configuration authorization CG resource; the terminal device uses the CG resource to automatically transmit the first type of object using the second type of mechanism. In an embodiment of the present application, the CG resource is used to automatically transmit the first type of object using the second type of mechanism, which can reduce data loss.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a transmission method and terminal equipment. Background Art

[0002] 5G (5th-Generation) RAN (Radio Access Network) 2URLLC (Ultra-Reliable and Low Latency Communication) requires support for the transmission of services such as industrial automation (Factory automation), transmission automation (Transport Industry), and intelligent power distribution (Electrical Power Distribution) in the 5G system. In order to support the transmission of URLLC services, the CG (Configured Grant) has been enhanced, that is, multiple CG configurations have been introduced, as well as the specific configuration and use of CG (such as supporting slot-level cycles, supporting automatic transmission of CG, etc.).

[0003] The goal of NRU is to enable NR to operate in unlicensed frequency bands, including the following working scenarios:

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

[0005] Dual-connectivity working scenario: PCell is LTE licensed spectrum, PScell ​​is NR unlicensed spectrum;

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

[0007] In NRU (New Radio Unlicensed) interference controlled scenarios, how to use CG resources for automatic transmission or retransmission has not yet been determined. Summary of the invention

[0008] An embodiment of the present application provides a transmission method and a terminal device, which can use CG resources for automatic transmission or retransmission to reduce data loss.

[0009] The present application provides a transmission method, including:

[0010] The terminal device receives the configuration authorization CG resource;

[0011] The terminal device utilizes the CG resource to automatically transmit the first type of object using the second type of mechanism.

[0012] The present application provides a terminal device, including:

[0013] A receiving unit, used for receiving a configuration authorization CG resource;

[0014] The transmission unit is used to utilize the CG resource to automatically transmit the first type of object using the second type of mechanism.

[0015] The embodiment of the present application provides a terminal device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above-mentioned transmission method.

[0016] The embodiment of the present application provides a network device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the above-mentioned transmission method.

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

[0018] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned transmission method.

[0019] An embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes the above-mentioned transmission method.

[0020] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned transmission method.

[0021] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned transmission method.

[0022] In the embodiment of the present application, the CG resources are used for automatic transmission or retransmission, which can reduce data loss. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0024] Figure 2 It is a schematic flow chart of a transmission method according to an embodiment of the present application.

[0025] Figure 3 It is a schematic flowchart of Example 1 of a transmission method according to an embodiment of the present application.

[0026] Figure 4 It is a schematic flowchart of Example 2 of a transmission method according to an embodiment of the present application.

[0027] Figure 5 It is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0028] Figure 6 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0029] Figure 7 is a schematic block diagram of a chip according to an embodiment of the present application.

[0030] Figure 8 It is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0031] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

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

[0033] 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 communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type 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.

[0034] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0035] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

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

[0037] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0038] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

[0039] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0040] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, 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 clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0041] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0042] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, 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 up in a location such as land or water.

[0043] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0044] Figure 1 A communication system 100 is exemplarily shown. The communication system includes a network device 110 and two terminal devices 120. Optionally, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in the present embodiment.

[0045] Optionally, the communication system 100 may also include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), etc., which is not limited in the embodiments of the present application.

[0046] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional nodeB, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro-micro base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0047] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system shown as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiments of the present application and will not be repeated here. The communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited to the embodiments of the present application.

[0048] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0049] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0050] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0051] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant 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, and they all belong to the protection scope of the embodiments of the present application.

[0052] The following introduces the CG enhancement in URLLC:

[0053] In the embodiment of the present application, it is necessary to consider supporting URLLC services in the interference controlled NRU scenario. Specifically, the use of NRU CG and ULRRC CG enhancements can be considered in the NRU scenario, for example: introducing coordinated UL CG enhancements in NRU and URLLC to apply to unlicensed spectrum.

[0054] To support the high latency requirements of URLLC services, URLLC enhances the CG cycle and supports any slot-level service cycle.

[0055] In order to support multiple URLLC services and high latency requirements of URLLC services, URLLC introduces multiple CGs. Different CGs have different HARQ (Hybrid Automatic Repeat Request) processes, and HARQ-ProcID-Offset2 (HARQ process identifier-offset 2) is used to ensure that the processes of different CGs are different.

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

[0057] The following introduces the CG enhancement in NRU:

[0058] Generally speaking, the operating frequency band of NRU is 5GHz unlicensed spectrum and 6GHz unlicensed spectrum (eg, US5925-7125MHz, or European 5925-6425MHz, or parts thereof). In the unlicensed spectrum, the design of NRU should ensure fairness with other systems that have already worked in these unlicensed spectrums, such as WiFi (Wireless Fidelity). The principle of fairness includes that the impact of NRU on the systems that have been deployed in the unlicensed spectrum (such as WiFi) cannot exceed the impact between these systems.

[0059] In order to ensure fair coexistence between systems on the unlicensed spectrum, energy detection has been agreed upon 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 a base station or terminal (transmitter) transmits data on the unlicensed spectrum, it needs to listen for a period of time as specified. If the listening result indicates that the channel is idle, the transmitter can transmit data to the receiver. If the listening result indicates that the channel is occupied, the transmitter needs to back off for a period of time as specified and continue to listen to the channel until the channel listening result shows that it is idle before transmitting data to the receiver.

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

[0061] To support back-to-back resource configuration, NRU introduces multiple CG. Multiple CG configurations can share the HARQ process.

[0062] The CG retransmission timer (cg-RetransmissionTimer, referred to as CG retx Timer) 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 (configuredGrantTimer, referred to as CG timer) has not timed out, the corresponding HARQ process can be retransmitted.

[0063] CG transmission can be interrupted by dynamically scheduled DCI (Downlink Control Information) and DFI (Downlink Feedback Information). For example, as shown in Table 1 below, the CG timer (CG timer) stops (stop) when DFI is ACK, is not affected (No impact) when DFI is NACK, and starts (start) or restarts (restart) when DCI is a new transmission (newtx) or a retransmission (retx). When the CG timer times out, the CG retransmission timer (CG retx timer) is stopped (stop). The CG retransmission timer (CG retx timer) stops (stop) when DFI is ACK, NACK, a new transmission or a retransmission.

[0064] Table 1

[0065]

[0066] In an embodiment of the present application, in an NRU interference controlled scenario, it is possible to determine the specific method of using CG resources for automatic transmission or retransmission, as well as how to perform automatic transmission or retransmission.

[0067] Figure 2 is a schematic flow chart of a transmission method 200 according to an embodiment of the present application. The method may optionally be applied to Figure 1 The system shown in the figure is not limited thereto. The method includes at least part of the following contents.

[0068] S210. The terminal device receives a configuration grant (CG) resource.

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

[0070] Optionally, the conventional transmission 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 an embodiment of the present application, after the terminal device receives the CG resource, the second type of mechanism is used to automatically transmit the first type of object, so that the transmission object and the transmission mechanism are not bound, and a specific transmission mechanism can be applied to a variety of transmission objects. 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 a second communication scenario, and these two communication scenarios are different.

[0071] Optionally, in an embodiment of the present application, the terminal device uses the CG resource to automatically transmit the first type of object using the second type of mechanism, including: the terminal device uses the CG resource to automatically transmit the object of the first communication scenario using the transmission mechanism of the second communication scenario.

[0072] Exemplarily, if the first communication scenario is an NRU scenario and the second communication scenario is an URLLC scenario, the terminal device can use CG resources to automatically transmit the objects of the NRU scenario using the transmission mechanism of the URLLC scenario. This method can be called method 1. The first communication scenario can also be an unlicensed spectrum access or scenario. The second communication scenario can also be an authorized spectrum access or scenario. Exemplarily, the scenario or object is an R16 scenario or object.

[0073] Exemplarily, if the first communication scenario is a URLLC scenario and the second communication scenario is an NRU scenario, the terminal device can use CG resources to automatically transmit the objects of the URLLC scenario using the transmission mechanism of the NRU scenario. This method can be called method 2. The first communication scenario can also be an authorized spectrum access or scenario. The second communication scenario can also be an unlicensed spectrum access or scenario. Exemplarily, the scenario or object is an R16 scenario or object.

[0074] Optionally, in mode 1 of an embodiment of the present application, the terminal device receives a CG resource, including: the terminal device receives one or more CG resources from a network, each CG resource has a corresponding hybrid automatic repeat request (HARQ) process, and each CG resource includes at least one of the following configurations:

[0075] Configure automatic transmission parameters (autonomousTx) to trigger automatic transmission;

[0076] Configure the CG timer, but do not configure the CG retransmission timer;

[0077] Configure the CG timer and CG retransmission timer, but set the value of the CG retransmission timer to 0.

[0078] Optionally, in method 1 of an embodiment of the present application, the prerequisite for configuring the autonomousTx includes: the terminal device, the MAC entity or CG resource of the terminal device is configured for priority processing based on LCH (Logical Channel).

[0079] Optionally, in the second embodiment of the present application, the terminal device receives the CG resource, including:

[0080] The terminal device receives one or more CG resources from a network, each CG resource having a corresponding hybrid automatic repeat request HARQ process, and each CG resource including at least one of the following configurations:

[0081] Do not configure the automatic transmission parameter autonomousTx.

[0082] Configure the CG retransmission timer to trigger automatic transmission;

[0083] Configure the CG retransmission timer but set the value to 0 to trigger automatic transmission;

[0084] Configure the CG timer.

[0085] Optionally, in an embodiment of the present application, the CG resource is configured in accordance with the new wireless unauthorized NRU CG or ultra-high reliability and low latency communication URLLC CG. In this way, the configuration method and the transmission method may not be bound. For CG resources configured in accordance with the NRU CG method, the URLLC transmission mechanism may be used for automatic transmission. For CG resources configured in accordance with the URLLC CG method, the NRU transmission mechanism may be used for automatic transmission.

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

[0087] A medium access control MAC protocol data unit PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted;

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

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

[0090] The downlink LBT failure results in the corresponding HARQ process or MAC PDU not being received (DFI downlink feedback information) or DCI (downlink control information).

[0091] Exemplarily, LBT failure may be caused by interference between systems, such as WIFI, or by interference within the system, or by false detection. In a controlled scenario, it is mainly caused by interference within the system, or by false detection.

[0092] Optionally, in the first embodiment of the present application, the automatic transmission includes at least one of the following:

[0093] Based on autonomousTx transmission mode, automatic transmission is performed;

[0094] Automatic transmission based on the authorized spectrum automatic transmission mode;

[0095] Automatic transmission based on low priority data or low priority MAC PDU transmission mode;

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

[0097] Automatic transmission of low-priority data or low-priority MAC PDUs due to resource conflicts;

[0098] Automatic transmission is performed based on the transmission method of low-priority resources or low-priority CG caused by resource conflicts.

[0099] Optionally, in method 1 of an embodiment of the present application, the automatic transmission is URLLC automatic transmission.

[0100] Optionally, in method 1 of the embodiment of the present application, automatic transmission is performed, including: for a CG resource, the MAC entity of the terminal device determines that the NDI (New Data Indication) of the HARQ process is flipped when the first condition is met, and / or, the CG resource is delivered to the HARQ entity. The HARQ entity may include multiple HARQ processes.

[0101] Optionally, in the first embodiment of the present application, the first condition includes at least one of the following:

[0102] The CG's PUSCH (Physical Uplink Shared Channel) does not conflict with the PUSCH resources scheduled by the DCI;

[0103] The PUSCH of CG does not conflict with the PUSCH resources scheduled by RAR (Random Access Response) or TC-RNTI (Temporary Cell-Radio Network Temporary Identifier);

[0104] The PUSCH of the CG does not conflict with the PUSCH resources of the two-step random access message A (MSGA) payload;

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

[0106] CG timer is not configured;

[0107] The CG timer is configured but not running;

[0108] The CG retransmission timer is not configured;

[0109] The CG retransmission timer is configured;

[0110] The CG retransmission timer is configured but the value is 0.

[0111] Optionally, in the first embodiment of the present application, the 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 that the MAC PDU is acquired when a second condition is met, and the second condition includes at least one of the following:

[0112] The uplink grant is CG;

[0113] The uplink grant is configured with the automatic transmission parameter autonomousTx;

[0114] The HARQ process is pending;

[0115] The size of the uplink grant is the same as the size of the acquired MAC PDU;

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

[0117] The uplink grant size is the same as the size of the most recent CG before the HARQ process;

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

[0119] The uplink grant is the same as the CG index of the most recent CG before the HARQ process;

[0120] The uplink grant has the same CG index as the CG before the HARQ process and the same configured BWP (Bandwidth Part);

[0121] The uplink grant size is the same CG configuration as the CG before the HARQ process;

[0122] The uplink grant has the same CG index and the same configured BWP as the most recent CG before the HARQ process;

[0123] The uplink grant size is configured as the same CG as the most recent CG before the HARQ process;

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

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

[0126] Optionally, in method 1 of an embodiment of the present application, automatic transmission is performed and also includes: when the MAC entity or HARQ entity of the terminal device obtains the MAC PDU to be transmitted, the MAC PDU is submitted to the HARQ process, and / or, the HARQ process is instructing to perform a new transmission.

[0127] Optionally, in the first embodiment of the present application, the 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:

[0128] When the third condition is met, 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,

[0129] If the fourth condition is met, the HARQ process is not pending, and the fourth condition includes at least one of the following: autonomousTx is configured, the uplink authorization is CG, the transmission of the HARQ process is executed, successful or completed, the uplink authorization is a resource for priority transmission, the uplink authorization is a non-resource-conflicting uplink authorization, the transmission of the uplink authorization or CG or the MAC PDU is executed, successful or completed, the LBT of the uplink authorization or the CG is successful, 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 success indication is received.

[0130] Optionally, in method 1 of the embodiment of the present application, automatic transmission is performed, and also includes determining the status of the HARQ process in the following manner: when the fifth condition is met, the HARQ process corresponding to the CG resource is pending, and the fifth condition includes at least one of the following: autonomousTx is configured, the uplink authorization is CG, the transmission of the HARQ process is not executed, unsuccessful or not completed, the uplink authorization is a low-priority resource, the uplink authorization is an uplink authorization with resource conflict, the transmission of the uplink authorization or the CG or the MAC PDU is not executed, unsuccessful or not completed, the LBT of the uplink authorization or the CG fails, an LBT failure indication is received, a transmission failure indication is received, a retransmission indication is received, an LBT success indication is not received, and a transmission success indication is not received.

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

[0132] Automatically transmit the MAC PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted;

[0133] Automatically transmit the HARQ process or MAC PDU that was not transmitted, not successfully transmitted, or not completely transmitted due to resource conflicts;

[0134] Low priority resources or CGs are automatically transferred;

[0135] Automatic transmission of MAC PDUs or data considered to be low priority.

[0136] Optionally, in the second embodiment of the present application, the automatic transmission includes at least one of the following:

[0137] Automatic transmission or automatic retransmission based on the retransmission mode of unlicensed spectrum;

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

[0139] Automatic transmission or automatic retransmission based on DFI indication;

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

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

[0142] Automatic transmission or automatic retransmission is performed because the HARQ process is not changed due to the LBT failure, or the HARQ process is still in pending transmission mode;

[0143] Based on the failure of downlink LBT resulting in DFI or DCI not receiving the corresponding transmission mode, automatic transmission or automatic retransmission is performed.

[0144] Optionally, in method 2 of the embodiment of the present application, the automatic transmission is NRU automatic transmission.

[0145] Optionally, in method 2 of an embodiment of the present application, automatic transmission is performed, including: for a CG resource, the MAC entity of the terminal device delivers the CG resource to the HARQ entity when the sixth condition is met.

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

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

[0148] The PUSCH of CG does not conflict with the PUSCH resources scheduled by RAR / TC-RNTI;

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

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

[0151] The CG retransmission timer is configured but not running;

[0152] The HARQ process is pending;

[0153] CG timer is not running.

[0154] Optionally, in method 2 of an embodiment of the present application, the MAC entity determines the NDI flip of the HARQ process.

[0155] Optionally, in method 2 of an embodiment of the present application, the MAC entity determines that the NDI of the HARQ process is not flipped.

[0156] Optionally, in the second embodiment of the present application, if the NDI is flipped and automatic transmission is performed, it also includes:

[0157] 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 met, and the seventh condition includes at least one of the following:

[0158] The uplink authorization is CG;

[0159] The uplink grant is configured with a CG retransmission timer;

[0160] The HARQ process is pending;

[0161] The size of the uplink grant is the same as the size of the acquired MAC PDU.

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

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

[0164] The uplink grant has the same CG index as the CG before the HARQ process and the same configured BWP;

[0165] The uplink grant size is the same CG configuration as the CG before the HARQ process;

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

[0167] The most recent CG before the HARQ process is a low-priority CG;

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

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

[0170] Optionally, in the second embodiment of the present application, if the NDI is flipped and automatic transmission is performed, it also includes:

[0171] When the MAC entity or HARQ entity of the terminal device obtains the MAC PDU that needs to be transmitted, it delivers the MAC PDU to the HARQ process and / or instructs the HARQ process to perform a new transmission.

[0172] Optionally, in the second embodiment of the present application, if the NDI is not flipped, automatic transmission is performed, further comprising:

[0173] 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.

[0174] Optionally, in the second embodiment of the present application, if the NDI is not flipped, 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, including:

[0175] The MAC entity or the HARQ entity delivers the MAC PDU to the HARQ process and / or instructs the HARQ process to perform retransmission when an eighth condition is met, wherein the eighth condition includes at least one of the following:

[0176] The uplink authorization is CG;

[0177] The uplink grant is configured with a CG retransmission timer;

[0178] The HARQ process is pending;

[0179] Get MAC PDU;

[0180] The size of the uplink grant is the same as the size of the acquired MAC PDU;

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

[0182] The uplink grant size is the same as the size of the most recent CG before the HARQ process;

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

[0184] The uplink grant is the same as the CG index of the most recent CG before the HARQ process;

[0185] The uplink grant has the same CG index as the CG before the HARQ process and the same configured BWP;

[0186] The uplink grant size is the same CG configuration as the CG before the HARQ process;

[0187] The uplink grant has the same CG index and the same configured BWP as the most recent CG before the HARQ process;

[0188] The uplink grant size is configured as the same CG as the most recent CG before the HARQ process;

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

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

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

[0192] The most recent CG before the HARQ process is a low-priority CG;

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

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

[0195] Optionally, in the second embodiment of the present application, the automatic transmission includes:

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

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

[0198] Ignore the uplink authorization resource or CG resource;

[0199] The uplink authorization resource or CG resource is delivered to the HARQ process but the uplink authorization resource or CG resource is ignored.

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

[0201] The CG retransmission timer is configured but not running;

[0202] The CG retransmission timer is configured but the value is 0;

[0203] The HARQ process is not pending;

[0204] CG timer running.

[0205] Optionally, in the second embodiment of the present application, the automatic transmission further includes:

[0206] The state of the HARQ process is determined in at least one of the following ways:

[0207] The HARQ process corresponding to the low-priority uplink grant resource is determined as pending;

[0208] The HARQ process corresponding to the uplink grant resource of the low-priority MAC PDU is determined as pending;

[0209] The HARQ process corresponding to the low-priority CG resource is determined as pending;

[0210] The HARQ process corresponding to the CG resource of the low-priority MAC PDU is determined as pending;

[0211] Determine the conflicting uplink grant resources or CG resources as pending;

[0212] The HARQ process when the MAC PDU is obtained is determined as pending;

[0213] The HARQ process when the MAC PDU corresponding to the CG resource is obtained is determined as pending;

[0214] Determine the conflicting and prioritized uplink authorization resources or CG resources as pending;

[0215] Determine the non-conflicting uplink grant resources or CG resources as notpending;

[0216] Determine the uplink authorized resources or CG resources that are not in conflict and have not failed LBT as notpending;

[0217] MAC PDU transmission is executed, successful or completed, and the HARQ process is determined as not pending.

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

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

[0220] 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;

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

[0222] Method 1 of the embodiment of the present application can perform URLLC automatic transmission on objects in the NRU scenario to ensure that the MAC PDU of the NRU scenario that is not transmitted or not successfully transmitted due to LBT failure is not discarded, thereby avoiding data loss or transmitting data as quickly as possible.

[0223] Method 2 of the embodiment of the present application can perform NRU automatic transmission on objects in the URLLC scenario to ensure that objects in the URLLC scenario, such as low-priority MAC PDU, are not discarded, avoid data loss, or enable data to be transmitted as quickly as possible.

[0224] The following is a specific example of the transmission method of the embodiment of the present application:

[0225] Example 1: A pending HARQ process and / or a not pending HARQ process triggers URLLC automatic transmission.

[0226] (1) Add the condition for considering MAC PDU as acquired

[0227] (2) Setting the HARQ process state, for example, using at least one of the following methods to set the HARQ process state:

[0228] (2-1) When the third condition is met, the corresponding HARQ process is considered to be pending. The third condition is at least one of the following: autonomous Tx is configured, the uplink resource (such as uplink grant) is CG, and the HARQ process obtains MAC PDU for transmission. And / or, when the fourth condition is met, the corresponding HARQ process is considered to be not pending. The fourth condition is: autonomous Tx is configured, the uplink resource is CG, the transmission of the HARQ process is executed, successful or completed, the uplink grant is a resource for priority transmission, the uplink grant is a non-resource conflicting uplink grant, the transmission of the uplink grant, CG or MAC PDU is executed, successful or completed, the LBT of the uplink grant or CG is successful, no LBT failure indication is received from the lower layer or NW, no transmission failure indication is received from the lower layer or NW, no retransmission indication is received from the lower layer or NW, an LBT success indication is received from the lower layer or NW, and a transmission success indication is received from the lower layer or NW. Or,

[0229] (2-2) If the fifth condition is met, the corresponding HARQ process is considered to be pending. The fifth condition is: autonomousTx is configured, the uplink resource is CG, the transmission of the HARQ process is not executed, unsuccessful or incomplete, the uplinkgrant is a resource for low-priority transmission, the uplink grant is an uplink grant for resource conflict, the transmission of the uplinkgrant, CG or MAC PDU is not executed, unsuccessful or incomplete, the LBT of the uplink grant or CG fails, an LBT failure indication is received from the lower layer or NW, a transmission failure indication is received from the lower layer or NW, a retransmission indication is received from the lower layer or NW, an LBT success indication is not received from the lower layer or NW, and a transmission success indication is not received from the lower layer or NW.

[0230] Example 2: The deprioritized MAC PDU uses NRU automatic retransmission. Specifically, at least one of the following methods is included:

[0231] (1-1) When the sixth condition is met, the CG resources are delivered 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, and the HARQ process is pending and the CG timer (configuredGrantTimer) is not running. Method 1 may also include the following situations: Situation 1: NDI is considered to be flipped and new transmission is performed; Situation 2: NDI is not considered to be flipped and retransmission is performed.

[0232] (1-2) When the ninth condition is met, the uplink grant resource or the 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 and not running, and when the HARQ process is not pending, configuredGrantTimer is running.

[0233] (1-3) If the ninth condition is met, the uplink grant resource or the 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: the cg-RetransmissionTimer is configured but the configured duration is 0, and the HARQ process is not pending and the configuredGrantTimer runs.

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

[0235] (2-1) The HARQ process corresponding to the deprioritized CG resources is considered to be pending; or, the HARQ process corresponding to the CG resources with deprioritized MAC PDU is considered to be pending.

[0236] (2-2) The HARQ process is considered pending when the HARQ process obtains the MAC PDU. The MAC PDU transmission is executed, successful or completed, and no LBT failure indication is received from the lower layer or NW. The HARQ process is considered not pending. Or, the HARQ process is considered pending when the HARQ process obtains the MAC PDU. The resources corresponding to the MAC PDU are not considered to be deprioritized resources, or they are not transmitted due to conflicts. The HARQ process is considered not pending.

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

[0238] Example 1: Setting the pending or not pending state for the HARQ process. Triggering URLLC automatic transmission for the pending HARQ and / or notpending HARQ processes.

[0239] like Figure 3 As shown, the specific implementation process of Example 1 is as follows:

[0240] 1. UE receives CG resources from the network (NW). Specifically:

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

[0242] (2) Each CG resource configuration corresponds to a HARQ process. The HARQ processes corresponding to different CG resources can be different or the same.

[0243] (3) Configure CG resources according to the URLLC CG method, such as configuring Type-B PUSCH resources.

[0244] (4) Configure autonomousTx to trigger automatic transmission.

[0245] (5) Optional. The premise for configuring autonomousTx is that the network configures LCH-Based Prioritization for the UE or the corresponding MAC entity or CG resources.

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

[0247] 2. The UE uses the CG resources configured by the network for transmission. Specifically,

[0248] (1) For each CG resource, the MAC entity considers that the NDI is flipped and / or passes the CG resource to the HARQ entity under at least one of the following conditions (see the first condition in the above embodiment). The condition is:

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

[0250] The PUSCH of CG does not conflict with the PUSCH resources scheduled by RAR / TC-RNTI;

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

[0252] The MAC entity is configured with LCH-basedPrioritization;

[0253] configuredGrantTimer is not configured;

[0254] configuredGrantTimer is configured but not running;

[0255] cg-RetransmissionTimer is not configured;

[0256] cg-RetransmissionTimer is configured;

[0257] cg-RetransmissionTimer is configured but its value is 0.

[0258] (2) For an uplink grant, the MAC PDU is considered to be acquired for the corresponding HARQ process when at least one of the following conditions (see the second condition in the above embodiment) is met. The condition is:

[0259] The uplinkgrant is CG;

[0260] The uplink grant is configured with autonomousTx;

[0261] The HARQ process is pending;

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

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

[0264] The uplink grant size is the same as the size of the most recent CG before the HARQ process;

[0265] The uplink grant has the same CG index as the CG before the HARQ process;

[0266] The uplink grant is the same as the CG index of the most recent CG before the HARQ process;

[0267] The uplink grant has the same CGindex as the CG before the HARQ process and the same configured BWP;

[0268] The uplink grant size is the same as the CG configuration before the HARQ process;

[0269] The uplink grant has the same CG index and the same configured BWP as the most recent CG before the HARQ process;

[0270] The uplink grant size is configured with the same CG as the most recent CG before the HARQ process;

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

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

[0273] 3. If a MAC PDU is obtained for transmission (i.e., a MAC PDU that needs to be transmitted is obtained), the MAC PDU is delivered to the HARQ process, and / or the HARQ process is instructed to perform a new transmission.

[0274] 4. Setting the HARQ process state, or considering the HARQ process as pending or not pending, may specifically include at least one of the following methods:

[0275] (1) When the third condition is met, the corresponding HARQ process is considered to be pending. The third condition is at least one of the following: autonomousTx is configured, the uplink resource (uplink grant) is CG, and the HARQ process obtains MAC PDU for transmission; When the fourth condition is met, the corresponding HARQ process is considered to be not pending. The fourth condition includes at least one of the following: autonomousTx is configured, the uplink resource is CG, the transmission of the HARQ process is executed / successfully / completed, the transmission of the CG / MAC PDU is executed / successfully / completed, the LBT to the CG is successful, no LBT failure indication is received from the lower layer or NW, no transmission failure indication is received from the lower layer or NW, no retransmission indication is received from the lower layer or NW, an LBT success indication is received from the lower layer or NW, and a transmission success indication is received from the lower layer or NW.

[0276] (2) If the fifth condition is met, the corresponding HARQ process is considered to be pending. The fifth condition includes at least one of the following: autonomousTx is configured, the uplink resource is CG, the transmission of the HARQ process is not executed / unsuccessful / not completed, the transmission of the CG or MAC PDU is not executed, unsuccessful or not completed, the LBT to the CG fails, an LBT failure indication is received from the lower layer or NW, a transmission failure indication is received from the lower layer or NW, a retransmission indication is received from the lower layer or NW, an LBT success indication is not received from the lower layer or NW, and a transmission success indication is not received from the lower layer or NW.

[0277] In this example, a method for automatically performing URLLC transmission on a MAC PDU that has not been transmitted or has not been successfully transmitted is provided in the event of an LBT failure (such as caused by interference within the system or error detection), to ensure that the MAC PDU is not discarded, to avoid data loss, or to enable the data to be transmitted as quickly as possible.

[0278] Example 2: Set the pending or not pending state for the HARQ process of the deprioritized CG or the low-priority MAC PDU. Use NRU automatic retransmission for the deprioritized MAC PDU.

[0279] like Figure 4 As shown, the specific implementation process of Example 2 is as follows:

[0280] 1. UE receives CG resources from the network (NW). Specifically:

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

[0282] (2) Each CG resource configuration corresponds to a HARQ process. The HARQ processes corresponding to different CG resources can be different or the same.

[0283] (3) Configure CG resources according to NRU CG or URLLC CG, such as configuring cg-nrofSlots or Type-BPUSCH resources.

[0284] (4) Do not configure autonomousTx.

[0285] (5) Configure cg-RetransmissionTimer, or configure cg-RetransmissionTimer and set its value to 0 to trigger automatic transmission.

[0286] (6)Configure configuredGrantTimer.

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

[0288] (1-1) For a CG resource, the MAC entity shall deliver the CG resource to the HARQ entity when at least one of the following conditions (see the sixth condition mentioned above) is met, and the NDI is considered to be flipped (new transmission).

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

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

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

[0292] The MAC entity is configured with LCH-basedPrioritization;

[0293] cg-RetransmissionTimer is configured but not running;

[0294] The HARQ process is pending;

[0295] configuredGrantTimer is not running.

[0296] (1-2) Accordingly, when at least one of the following conditions (see the seventh condition in the above embodiment) is met, it is considered that the HARQ process corresponding to the CG resource obtains the MAC PDU to be transmitted, that is, obtains the MAC PDU that needs to be transmitted. The condition is:

[0297] The uplink grant is CG;

[0298] The uplink grant is configured with a CG retx timer.

[0299] The HARQ process is pending;

[0300] The size of the uplinkgrant is the same as the size of the acquired MAC PDU;

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

[0302] The uplink grant size is the same as the size of the most recent CG before the HARQ process;

[0303] The uplinkgrant is the same as the CGindex of the CG before the HARQ process;

[0304] The uplink grant is the same as the CGindex of the most recent CG before the HARQ process;

[0305] The uplinkgrant has the same CG index as the CG before the HARQ process and the same configured BWP;

[0306] The uplinkgrant size is the same as the CG configuration before the HARQ process;

[0307] The uplink grant has the same CG index and the same configured BWP as the most recent CG before the HARQ process;

[0308] The uplink grant size is configured with the same CG as the most recent CG before the HARQ process;

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

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

[0311] The previous CG corresponding to the HARQ process is the deprioritized CG;

[0312] The most recent CG before the HARQ process is a low-priority CG;

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

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

[0315] (1-3) If a MAC PDU is obtained for transmission, the MAC PDU is delivered to the HARQ process, and / or the HARQ process is instructed to perform a new transmission.

[0316] (1-4) Setting the HARQ process state, or considering the HARQ process as pending or not pending, specifically including at least one of the following:

[0317] The HARQ process corresponding to the low-priority uplink grant resource is determined as pending;

[0318] The HARQ process corresponding to the uplinkgrant resource of the low-priority MAC PDU is determined as pending;

[0319] Set the HARQ process corresponding to the low-priority CG resource to pending;

[0320] The HARQ process corresponding to the CG resource of the low-priority MAC PDU is determined as pending;

[0321] Determine the conflicting uplink grant resources or CG resources as pending;

[0322] The HARQ process when the MAC PDU is obtained is determined as pending;

[0323] The HARQ process when the MAC PDU corresponding to the CG resource is obtained is determined as pending;

[0324] Determine the conflicting and prioritized uplink grant resources or CG resources as pending;

[0325] Determine non-conflicting uplink grant resources or CG resources as not pending;

[0326] Determine uplink grant resources or CG resources that are not in conflict and have not failed LBT as not pending;

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

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

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

[0330] 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 the MAC PDU is determined as not pending;

[0331] The uplink grant resource corresponding to the MAC PDU is not a low priority resource, or is not transmitted due to a conflict, so the HARQ process is determined as not pending.

[0332] (2-1) For a CG resource, the MAC entity delivers the CG resource to the HARQ entity when at least one of the following conditions (see the sixth condition in the above embodiment) is met, but does not consider NDI flipping (retransmission).

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

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

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

[0336] The MAC entity is configured with LCH-basedPrioritization;

[0337] cg-Retransmission Timer is configured but not running;

[0338] The HARQ process is pen ding;

[0339] configuredGrantTimer is not running.

[0340] (2-2) Accordingly, the MAC PDU is delivered to the HARQ process, and / or the HARQ process is instructed to perform retransmission. Alternatively, when at least one of the following conditions (see the eighth condition in the above embodiment) is met, the MAC PDU is delivered to the HARQ process, and / or the HARQ process is instructed to perform retransmission. The conditions include:

[0341] The uplinkgrant is CG;

[0342] The uplink grant is configured with a CG retx timer;

[0343] The HARQ process is pending;

[0344] Get MAC PDU;

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

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

[0347] The uplink grant size is the same as the size of the most recent CG before the HARQ process;

[0348] The uplink grant is the same as the CGindex of the CG before the HARQ process;

[0349] The uplink grant is the same as the CG index of the most recent CG before the HARQ process;

[0350] The uplink grant has the same CGindex as the CG before the HARQ process and the same configured BWP;

[0351] The uplink grant size is the same as the CG configuration before the HARQ process;

[0352] The uplink grant has the same CG index and the same configured BWP as the most recent CG before the HARQ process;

[0353] The uplink grant size is configured with the same CG as the most recent CG before the HARQ process;

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

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

[0356] The previous CG corresponding to the HARQ process is the deprioritized CG;

[0357] The most recent CG before the HARQ process is a low-priority CG;

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

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

[0360] (2-3) Setting the HARQ process state, or considering the HARQ process as pending or not pending. For details, refer to the relevant description in the above (1-4).

[0361] (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, or ignores the grant, or delivers the CG resource to the HARQ process but ignores the grant if the following conditions are met (see the ninth condition in the above embodiment). The condition is at least one of the following: cg-RetransmissionTimer is configured and not running, and the HARQ process is not pending and configuredGrantTimer is running.

[0362] (3-2) Correspondingly: setting the HARQ process status, or considering the HARQ process as pending or not pending. For details, please refer to the relevant description in the above (1-4).

[0363] (4-1) For an uplink grant resource or CG resource, the MAC entity shall not deliver the uplink grant resource or CG resource to the HARQ process, or ignore the grant, if 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 configuredGrantTimer is running.

[0364] (4-2) Correspondingly: setting the HARQ process status, or considering the HARQ process as pending or not pending. For details, please refer to the relevant description in the above (1-4).

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

[0366] Figure 5 4 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application. The terminal device 400 may include:

[0367] A receiving unit 410 is used to receive a configuration authorization CG resource;

[0368] The transmission unit 420 is used to utilize the CG resource to automatically transmit the first type of object using the second type of mechanism.

[0369] Optionally, in an embodiment of the present application, the transmission unit 420 is further used to utilize the CG resource to automatically transmit the object of the first communication scenario using the transmission mechanism of the second communication scenario.

[0370] Optionally, in the first 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 having a corresponding hybrid automatic repeat request HARQ process, and each CG resource including at least one of the following configurations:

[0371] Configure the automatic transmission parameter autonomousTx to trigger automatic transmission;

[0372] Configure the CG timer, but do not configure the CG retransmission timer;

[0373] Configure the CG timer and CG retransmission timer, but set the value of the CG retransmission timer to 0.

[0374] Optionally, in method 1 of an embodiment of the present application, the prerequisite for configuring the autonomousTx includes: the terminal device, the MAC entity or CG resources of the terminal device are configured to be processed based on the logical channel LCH priority.

[0375] Optionally, in the second embodiment of the present application, the receiving unit 410 is further used to receive one or more CG resources from the network, each CG resource has a corresponding hybrid automatic repeat request HARQ process, and each CG resource includes at least one of the following configurations:

[0376] Do not configure the automatic transmission parameter autonomousTx.

[0377] Configure the CG retransmission timer to trigger automatic transmission;

[0378] Configure the CG retransmission timer but set the value to 0 to trigger automatic transmission;

[0379] Configure the CG timer.

[0380] Optionally, in method 1 of an embodiment of the present application, the CG resources are configured in accordance with the new wireless unlicensed NRU CG or ultra-high reliability and low latency communication URLLC CG.

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

[0382] A medium access control MAC protocol data unit PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted;

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

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

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

[0386] Optionally, in the first embodiment of the present application, the transmission unit 420 performs automatic transmission in at least one of the following ways:

[0387] Based on autonomousTx transmission mode, automatic transmission is performed;

[0388] Automatic transmission based on the authorized spectrum automatic transmission mode;

[0389] Automatic transmission based on low priority data or low priority MAC PDU transmission mode;

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

[0391] Automatic transmission of low-priority data or low-priority MAC PDUs due to resource conflicts;

[0392] Automatic transmission is performed based on the transmission method of low-priority resources or low-priority CG caused by resource conflicts.

[0393] Optionally, in method 1 of an embodiment of the present application, the automatic transmission is URLLC automatic transmission.

[0394] Optionally, in method 1 of an embodiment of the present application, the transmission unit 420 is also used to determine, for a CG resource, when a first condition is met, that the new data indication NDI of the HARQ process flips, and / or to deliver the CG resource to the HARQ entity.

[0395] Optionally, in the first embodiment of the present application, the first condition includes at least one of the following:

[0396] The CG's physical uplink shared channel PUSCH does not conflict with the PUSCH resources scheduled by DCI;

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

[0398] The PUSCH of the CG does not conflict with the PUSCH resources of the two-step random access message A payload;

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

[0400] CG timer is not configured;

[0401] The CG timer is configured but not running;

[0402] The CG retransmission timer is not configured;

[0403] The CG retransmission timer is configured;

[0404] The CG retransmission timer is configured but the value is 0.

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

[0406] The uplink authorization is CG;

[0407] The uplink grant is configured with the automatic transmission parameter autonomousTx

[0408] The HARQ process is pending;

[0409] The size of the uplink grant is the same as the size of the acquired MAC PDU;

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

[0411] The uplink grant size is the same as the size of the most recent CG before the HARQ process;

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

[0413] The uplink grant is the same as the CG index of the most recent CG before the HARQ process;

[0414] The uplink grant has the same CG index as the CG before the HARQ process and the same configured bandwidth part BWP;

[0415] The uplink grant size is the same CG configuration as the CG before the HARQ process;

[0416] The uplink grant has the same CG index and the same configured BWP as the most recent CG before the HARQ process;

[0417] The uplink grant size is configured as the same CG as the most recent CG before the HARQ process;

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

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

[0420] Optionally, in method 1 of an embodiment of the present application, the transmission unit 420 is further used to deliver the MAC PDU to the HARQ process when a MAC PDU to be transmitted is obtained, and / or to instruct the HARQ process to perform a new transmission.

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

[0422] When the third condition is met, 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,

[0423] If 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, the transmission of the HARQ process is executed, successful or completed, the uplink authorization is a resource for priority transmission, the uplink authorization is a non-resource-conflicting uplink authorization, the transmission of the uplink authorization or CG or the MAC PDU is executed, successful or completed, the LBT of the uplink authorization or the CG is successful, 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 success indication is received.

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

[0425] If the fifth condition is met, 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, unsuccessful or not completed, the uplink authorization is a low priority resource, the uplink authorization is an uplink authorization with resource conflict, the transmission of the uplink authorization or the CG or the MAC PDU is not executed, unsuccessful or not completed, the LBT of the uplink authorization 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.

[0426] Optionally, in the second embodiment of the present application, the transmission unit 420 performs automatic transmission in at least one of the following ways:

[0427] Automatically transmit the MAC PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted;

[0428] Automatically transmit the HARQ process or MAC PDU that was not transmitted, not successfully transmitted, or not completely transmitted due to resource conflicts;

[0429] Low priority resources or CGs are automatically transferred;

[0430] Automatic transmission of MAC PDUs or data considered to be low priority.

[0431] Optionally, in the second embodiment of the present application, the transmission unit 420 performs automatic transmission in at least one of the following ways:

[0432] Automatic transmission or automatic retransmission based on the retransmission mode of unlicensed spectrum;

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

[0434] Automatic transmission or automatic retransmission based on DFI indication;

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

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

[0437] Automatic transmission or automatic retransmission is performed because the HARQ process is not changed due to the LBT failure, or the HARQ process is still in pending transmission mode;

[0438] Based on the failure of downlink LBT resulting in DFI or DCI not receiving the corresponding transmission mode, automatic transmission or automatic retransmission is performed.

[0439] Optionally, in method 2 of the embodiment of the present application, the automatic transmission is NRU automatic transmission.

[0440] Optionally, in mode 2 of an embodiment of the present application, the transmission unit 420 is also used to, for a CG resource, the MAC entity of the terminal device delivers the CG resource to the HARQ entity when a sixth condition is met.

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

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

[0443] The PUSCH of CG does not conflict with the PUSCH resources scheduled by RAR / TC-RNTI;

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

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

[0446] The CG retransmission timer is configured but not running;

[0447] The HARQ process is pending;

[0448] CG timer is not running.

[0449] Optionally, in mode 2 of the embodiment of the present application, the transmission unit 420 is also used to determine the NDI flip of the HARQ process.

[0450] Optionally, in mode 2 of the embodiment of the present application, the transmission unit 420 is further used to determine that the NDI of the HARQ process is not flipped.

[0451] Optionally, in the second embodiment of the present application, if the NDI is flipped, the transmission unit 420 is further used to determine that the HARQ process corresponding to the CG resource obtains the MAC PDU to be transmitted when the seventh condition is met, and the seventh condition includes at least one of the following:

[0452] The uplink authorization is CG;

[0453] The uplink grant is configured with a CG retransmission timer;

[0454] The HARQ process is pending;

[0455] The size of the uplink grant is the same as the size of the acquired MAC PDU.

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

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

[0458] The uplink grant has the same CG index as the CG before the HARQ process and the same configured BWP;

[0459] The uplink grant size is the same CG configuration as the CG before the HARQ process;

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

[0461] The most recent CG before the HARQ process is a low-priority CG;

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

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

[0464] Optionally, in method 2 of an embodiment of the present application, if the NDI is flipped, the transmission unit 420 is also used to deliver the MAC PDU to the HARQ process when the MAC PDU to be transmitted is obtained, and / or instruct the HARQ process to perform a new transmission.

[0465] Optionally, in mode 2 of the embodiment of the present application, if the NDI is not flipped, the transmission unit 420 is further used to deliver the MAC PDU to the HARQ process, and / or instruct the HARQ process to perform retransmission.

[0466] Optionally, in the second embodiment of the present application, if the NDI is not flipped, 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 when the eighth condition is met, and the eighth condition includes at least one of the following:

[0467] The uplink authorization is CG;

[0468] The uplink grant is configured with a CG retransmission timer;

[0469] The HARQ process is pending;

[0470] Get MAC PDU;

[0471] The size of the uplink grant is the same as the size of the acquired MAC PDU;

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

[0473] The uplink grant size is the same as the size of the most recent CG before the HARQ process;

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

[0475] The uplink grant is the same as the CG index of the most recent CG before the HARQ process;

[0476] The uplink grant has the same CG index as the CG before the HARQ process and the same configured BWP;

[0477] The uplink grant size is the same CG configuration as the CG before the HARQ process;

[0478] The uplink grant has the same CG index and the same configured BWP as the most recent CG before the HARQ process;

[0479] The uplink grant size is configured as the same CG as the most recent CG before the HARQ process;

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

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

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

[0483] The most recent CG before the HARQ process is a low-priority CG;

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

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

[0486] Optionally, in the second embodiment of the present application, the transmission unit 420 is further configured to, for an uplink grant resource or a CG resource, perform at least one of the following steps when the ninth condition is met:

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

[0488] Ignore the uplink authorization resource or CG resource;

[0489] The uplink authorization resource or CG resource is delivered to the HARQ process but the uplink authorization resource or CG resource is ignored.

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

[0491] The CG retransmission timer is configured but not running;

[0492] The CG retransmission timer is configured but the value is 0;

[0493] The HARQ process is not pending;

[0494] CG timer running.

[0495] Optionally, in the second embodiment of the present application, the transmission unit 420 is further configured to determine the state of the HARQ process by adopting at least one of the following methods:

[0496] The HARQ process corresponding to the low-priority uplink grant resource is determined as pending;

[0497] The HARQ process corresponding to the uplink grant resource of the low-priority MAC PDU is determined as pending;

[0498] The HARQ process corresponding to the low-priority CG resource is determined as pending;

[0499] The HARQ process corresponding to the CG resource of the low-priority MAC PDU is determined as pending;

[0500] Determine the conflicting uplink grant resources or CG resources as pending;

[0501] The HARQ process when the MAC PDU is obtained is determined as pending;

[0502] The HARQ process when the MAC PDU corresponding to the CG resource is obtained is determined as pending;

[0503] Determine the conflicting and prioritized uplink authorization resources or CG resources as pending;

[0504] Determine the non-conflicting uplink grant resources or CG resources as notpending;

[0505] Determine the uplink authorized resources or CG resources that are not in conflict and have not failed LBT as notpending;

[0506] MAC PDU transmission is executed, successful or completed, and the HARQ process is determined as not pending.

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

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

[0509] 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;

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

[0511] The terminal device 400 of the embodiment of the present application can implement the corresponding functions of the terminal device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the terminal device 400 can be found in the corresponding descriptions in the above method embodiments, which will not be repeated here. It should be noted that the functions described by the various modules (sub-modules, units or components, etc.) in the terminal device 400 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-module, unit or component, etc.).

[0512] Figure 6 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 to enable the communication device 600 to implement the method in the embodiment of the present application.

[0513] Optionally, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to enable the communication device 600 to implement the method in the embodiment 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.

[0514] 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, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of antennas may be one or more.

[0515] Optionally, the communication device 600 may be a network device of an 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 will not be described in detail here for the sake of brevity.

[0516] Optionally, the communication device 600 may be a terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0517] Figure 7 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 to implement the method in the embodiment of the present application.

[0518] 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.

[0519] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0520] 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 obtain information or data sent by other devices or chips.

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

[0522] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0523] Optionally, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0524] The chips used in the network device and the terminal device may be the same chip or different chips.

[0525] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0526] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0527] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM).

[0528] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), 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 link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, 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.

[0529] Figure 8 It 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 used to receive a configuration authorization CG resource; and utilize the CG resource to automatically transmit the first type of object using the second type mechanism. The network device 820 is used to send the CG resource to the terminal device. Among them, 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 the sake of brevity, it will not be repeated here.

[0530] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using 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 process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrations. 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)).

[0531] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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

[0533] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A transmission method, comprising: The terminal device receives the configuration authorization CG resource; The terminal device automatically transmits the first type of object using the second type of mechanism using the CG resource; The terminal device automatically transmits the first type of object using the second type of mechanism by using the CG resource, including: The terminal device automatically transmits the object of the first communication scenario using the transmission mechanism of the second communication scenario by using the CG resource; The terminal device automatically transmits the first type of object using the second type of mechanism by using the CG resource, including: Automatically transfer at least one of the following: A medium access control MAC protocol data unit PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted; HARQ processes or MAC PDUs that were not transmitted, not successfully transmitted, or not completely transmitted due to LBT failure; The HARQ process is not changed due to LBT failure, or the HARQ process is still pending HARQ process or MAC PDU; The HARQ process or MAC PDU corresponding to the downlink feedback information DFI or downlink control information DCI is not received due to downlink LBT failure; The automatic transmission includes at least one of the following: Automatic transmission based on autonomousTx transmission mode; Automatic transmission based on the authorized spectrum automatic transmission mode; Automatic transmission based on low priority data or low priority MAC PDU transmission mode; Automatic transmission based on low-priority resources or low-priority CG transmission methods; Automatic transmission of low-priority data or low-priority MAC PDUs due to resource conflicts; Automatic transmission is performed based on the transmission method of low-priority resources or low-priority CG caused by resource conflicts.

2. The method according to claim 1, wherein: The terminal device receives CG resources, including: The terminal device receives one or more CG resources from the network, each CG resource having a corresponding hybrid automatic repeat request HARQ process, and each CG resource including 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 set the value of the CG retransmission timer to 0.

3. The method according to claim 2, wherein: The prerequisite for configuring the autonomousTx includes: the terminal device, the MAC entity or the CG resource of the terminal device is configured to be processed based on the logical channel LCH priority.

4. The method according to claim 1, wherein: The terminal device receives CG resources, including: The terminal device receives one or more CG resources from the network, each CG resource having a corresponding hybrid automatic repeat request HARQ process, and each CG resource including 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 but set the value to 0 to trigger automatic transmission; Configure the CG timer.

5. The method according to any one of claims 1 to 4, wherein: The CG resources are configured in accordance with the new wireless unlicensed NRUCG or ultra-high reliability and low latency communication URLLC CG.

6. The method according to claim 1, wherein: The automatic transmission is URLLC automatic transmission.

7. The method according to claim 1, wherein: Perform automatic transfers, including: For a CG resource, the MAC entity of the terminal device determines that the new data indication NDI of the HARQ process is flipped when the first condition is met, and / or delivers the CG resource to the HARQ entity.

8. The method according to claim 7, wherein: The first condition includes at least one of the following: The CG's physical uplink shared channel PUSCH does not conflict with the PUSCH resources scheduled by DCI; The PUSCH of the CG does not conflict with the PUSCH resources 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 resources of the two-step random access message A payload; The MAC entity is configured with LCH-based priority processing; CG timer is not configured; The CG timer is configured but not running; The CG retransmission timer is not configured; The CG retransmission timer is configured; The CG retransmission timer is configured but the value is 0.

9. The method according to claim 1, wherein: For automatic transmission, it also includes: For a HARQ process corresponding to an uplink grant, the MAC entity or the HARQ entity of the terminal device determines that the MAC PDU is acquired when a second condition is satisfied, where 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 size is the same as the size of the CG before the HARQ process; The uplink grant size is the same as the size of the most recent 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 most recent CG before the HARQ process; The uplink grant has the same CG index as the CG before the HARQ process and the same configured bandwidth part BWP; The uplink grant size and the CG before the HARQ process are the same CG configuration; The uplink grant has the same CG index as the most recent CG before the HARQ process and has the same configured BWP; The uplink grant size is configured as the same CG as the most recent CG before the HARQ process; The uplink grant and the CG before the HARQ process are on the same BWP; The uplink grant is on the same BWP as the most recent CG before the HARQ process.

10. The method according to claim 1, wherein: For automatic transmission, it also includes: When the MAC entity or HARQ entity of the terminal device obtains the MAC PDU that needs to be transmitted, it submits the MAC PDU to the HARQ process and / or instructs the HARQ process to perform a new transmission.

11. The method according to claim 1, wherein: The automatic transmission also 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 met, 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, If 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, the transmission of the HARQ process is executed, successful or completed, the uplink authorization is a resource for priority transmission, the uplink authorization is a non-resource-conflicting uplink authorization, the transmission of the uplink authorization or CG or the MAC PDU is executed, successful or completed, the LBT of the uplink authorization or the CG is successful, 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 success indication is received.

12. The method according to claim 1, wherein: The automatic transmission also includes determining the state of the HARQ process in the following manner: When the fifth condition is met, 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, unsuccessful or not completed, the uplink authorization is a low priority resource, the uplink authorization is an uplink authorization with resource conflict, the transmission of the uplink authorization or the CG or the MAC PDU is not executed, unsuccessful or not completed, the LBT of the uplink authorization 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.

13. The method according to any one of claims 1 to 4, wherein: The terminal device automatically transmits the first type of object using the second type of mechanism by using the CG resource, including at least one of the following: Automatically transmit the MAC PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted; Automatically transmit the HARQ process or MAC PDU that was not transmitted, not successfully transmitted, or not completely transmitted due to resource conflicts; Low priority resources or CGs are automatically transferred; Automatic transmission of MAC PDUs or data considered to be low priority.

14. The method according to claim 13, wherein: Automatic transmission includes at least one of the following: Automatic transmission or automatic retransmission based on the retransmission mode 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 indication; Automatic transmission or automatic retransmission based on the transmission mode of CG retransmission timer; Automatic transmission or automatic retransmission based on the transmission mode of the untransmitted MAC PDU caused by LBT failure; Automatic transmission or automatic retransmission is performed because the HARQ process is not changed due to the LBT failure, or the HARQ process is still in pending transmission mode; Based on the failure of downlink LBT resulting in DFI or DCI not receiving the corresponding transmission mode, automatic transmission or automatic retransmission is performed.

15. The method according to claim 13, wherein: The automatic transmission is NRU automatic transmission.

16. The method according to claim 13, wherein the automatic transmission comprises: For a CG resource, the MAC entity of the terminal device delivers the CG resource to the HARQ entity if the sixth condition is met.

17. The method according to claim 16, wherein the sixth condition comprises at least one of the following: The PUSCH of CG does not conflict with the PUSCH resources scheduled by DCI; The PUSCH of CG does not conflict with the PUSCH resources scheduled by RAR / TC-RNTI; The PUSCH of CG does not conflict with the PUSCH resources of MSGA payload; The MAC entity is configured with LCH-based priority processing; The CG retransmission timer is configured but not running; The HARQ process is pending; CG timer is not running.

18. The method of claim 16, wherein the MAC entity determines an NDI flip of a HARQ process.

19. The method of claim 16, wherein the MAC entity determines that the NDI of the HARQ process is not flipped.

20. The method according to claim 18, wherein the automatic transmission further comprises: 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 met, 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 size 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 has the same CG index as the CG before the HARQ process and the same configured BWP; 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 most recent CG before the HARQ process is a low-priority CG; There is a low priority MAC PDU in the HARQ process; In the HARQ process, there exists a MAC PDU which is not transmitted, not successfully transmitted, not completely transmitted, or not transmitted due to resource conflict.

21. The method according to claim 18, wherein the automatic transmission further comprises: When the MAC entity or HARQ entity of the terminal device obtains the MAC PDU that needs to be transmitted, it delivers the MAC PDU to the HARQ process and / or instructs the HARQ process to perform a new transmission.

22. The method according to claim 19, wherein the automatic transmission further comprises: 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.

23. The method according to claim 22, wherein 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, comprising: The MAC entity or the HARQ entity delivers the MAC PDU to the HARQ process and / or instructs the HARQ process to perform retransmission when an eighth condition is met, wherein 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 size is the same as the size of the CG before the HARQ process; The uplink grant size is the same as the size of the most recent 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 most recent CG before the HARQ process; The uplink grant has the same CG index as the CG before the HARQ process and the same configured BWP; The uplink grant size and the CG before the HARQ process are the same CG configuration; The uplink grant has the same CG index as the most recent CG before the HARQ process and has the same configured BWP; The uplink grant size is configured as the same CG as the most recent CG before the HARQ process; The uplink grant and the CG before the HARQ process are on the same BWP; 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 most recent CG before the HARQ process is a low-priority CG; There is a low priority MAC PDU in the HARQ process; In the HARQ process, there exists a MAC PDU which is not transmitted, not successfully transmitted, not completely transmitted, or not transmitted due to resource conflict.

24. The method according to claim 13, wherein the automatic transmission comprises: For an uplink grant resource or a CG resource, the MAC entity or the HARQ entity performs at least one of the following steps when the ninth condition is met: Do not deliver uplink grant resources or CG resources to the HARQ entity; Ignore the uplink authorization resource or CG resource; The uplink authorization resources or CG resources are delivered to the HARQ process but the uplink authorization resources or CG resources are ignored.

25. The method according to claim 24, wherein the ninth condition comprises at least one of the following: The CG retransmission timer is configured but not running; The CG retransmission timer is configured but the value is 0; The HARQ process is not pending; CG timer running.

26. The method according to claim 13, wherein the automatic transmission further comprises: The state of the HARQ process is determined in at least one of the following ways: The HARQ process corresponding to the low-priority uplink grant resource is determined as pending; The HARQ process corresponding to the uplink grant resource of the low-priority MAC PDU is determined as pending; The HARQ process corresponding to the low-priority CG resource is determined as pending; The HARQ process corresponding to the CG resource of the low-priority MAC PDU is determined as pending; Determine the conflicting uplink authorization resources or CG resources as pending; The HARQ process when the MAC PDU is obtained is determined as pending; The HARQ process when the MAC PDU corresponding to the CG resource is obtained is determined as pending; Determine the conflicting and prioritized uplink authorization resources or CG resources as pending; Determine the non-conflicting uplink authorization resources or CG resources as not pending; Determine the uplink authorized resources or CG resources that are not in conflict and have not failed LBT 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 is received, and the HARQ process is determined as not pending; MAC PDU transmission is executed, successful or completed, and an 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 is not transmitted due to a conflict, and the HARQ process is determined as not pending.

27. A terminal device, comprising: A receiving unit, used for receiving a configuration authorization CG resource; A transmission unit, used for the terminal device to automatically transmit the first type of object using the second type of mechanism by using the CG resource; The transmission unit is further used to automatically transmit the object of the first communication scenario using the transmission mechanism of the second communication scenario by using the CG resource; The transmission unit is further used to automatically transmit at least one of the following objects: A medium access control MAC protocol data unit PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted; HARQ processes or MAC PDUs that were not transmitted, not successfully transmitted, or not completely transmitted due to LBT failure; The HARQ process is not changed due to LBT failure, or the HARQ process is still pending HARQ process or MAC PDU; The HARQ process or MAC PDU corresponding to the downlink feedback information DFI or downlink control information DCI is not received due to downlink LBT failure; The automatic transmission method of the transmission unit includes at least one of the following: Based on autonomousTx transmission mode, automatic transmission is performed; Automatic transmission based on the authorized spectrum automatic transmission mode; Automatic transmission based on low priority data or low priority MAC PDU transmission mode; Automatic transmission based on low-priority resources or low-priority CG transmission methods; Automatic transmission of low-priority data or low-priority MAC PDUs due to resource conflicts; Automatic transmission is performed based on the transmission method of low-priority resources or low-priority CG caused by resource conflicts.

28. The terminal device according to claim 27, wherein: The receiving unit is further configured to receive one or more CG resources from the network, each CG resource having a corresponding hybrid automatic repeat request HARQ process, and each CG resource including 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 set the value of the CG retransmission timer to 0.

29. The terminal device according to claim 28, wherein: The prerequisite for configuring the autonomousTx includes: the terminal device, the MAC entity or the CG resource of the terminal device is configured to be processed based on the logical channel LCH priority.

30. The terminal device according to claim 27, wherein: The receiving unit is further configured to receive one or more CG resources from the network, each CG resource having a corresponding hybrid automatic repeat request HARQ process, and each CG resource including 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 but set the value to 0 to trigger automatic transmission; Configure the CG timer.

31. The terminal device according to any one of claims 27 to 30, wherein: The CG resources are configured in accordance with the new wireless unlicensed NRU CG or ultra-high reliability and low latency communication URLLC CG.

32. The terminal device according to claim 27, wherein: The automatic transmission is URLLC automatic transmission.

33. The terminal device according to claim 27, wherein: The transmission unit is also used to determine, for a CG resource, that the new data indication NDI of the HARQ process flips when the first condition is met, and / or to deliver the CG resource to the HARQ entity.

34. The terminal device according to claim 33, wherein: The first condition includes at least one of the following: The CG's physical uplink shared channel PUSCH does not conflict with the PUSCH resources scheduled by DCI; The PUSCH of the CG does not conflict with the PUSCH resources 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 resources of the two-step random access message A payload; The MAC entity is configured with LCH-based priority processing; CG timer is not configured; The CG timer is configured but not running; The CG retransmission timer is not configured; The CG retransmission timer is configured; The CG retransmission timer is configured but the value is 0.

35. The terminal device according to claim 27, wherein: The transmission unit is further configured to determine, for a HARQ process corresponding to an uplink grant, that a MAC PDU is acquired when a second condition is satisfied, wherein 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 size is the same as the size of the CG before the HARQ process; The uplink grant size is the same as the size of the most recent 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 most recent CG before the HARQ process; The uplink grant has the same CG index as the CG before the HARQ process and the same configured bandwidth part BWP; The uplink grant size and the CG before the HARQ process are the same CG configuration; The uplink grant has the same CG index as the most recent CG before the HARQ process and has the same configured BWP; The uplink grant size is configured as the same CG as the most recent CG before the HARQ process; The uplink grant and the CG before the HARQ process are on the same BWP; The uplink grant is on the same BWP as the most recent CG before the HARQ process.

36. The terminal device according to claim 27, wherein: The transmission unit is further configured to, when a MAC PDU to be transmitted is acquired, deliver the MAC PDU to the HARQ process, and / or instruct the HARQ process to perform a new transmission.

37. The terminal device according to claim 27, wherein: The transmission unit is further configured to determine the state of the HARQ process in the following manner: When the third condition is met, 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, If 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, the transmission of the HARQ process is executed, successful or completed, the uplink authorization is a resource for priority transmission, the uplink authorization is a non-resource-conflicting uplink authorization, the transmission of the uplink authorization or CG or the MAC PDU is executed, successful or completed, the LBT of the uplink authorization or the CG is successful, 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 success indication is received.

38. The terminal device according to claim 27, wherein: The transmission unit is further configured to determine the state of the HARQ process in the following manner: When the fifth condition is met, 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, unsuccessful or not completed, the uplink authorization is a low priority resource, the uplink authorization is an uplink authorization with resource conflict, the transmission of the uplink authorization or the CG or the MAC PDU is not executed, unsuccessful or not completed, the LBT of the uplink authorization 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.

39. The terminal device according to any one of claims 27 to 30, wherein: The automatic transmission method of the transmission unit includes at least one of the following: Automatically transmit the MAC PDU that has not been transmitted, has not been successfully transmitted, or has not been completely transmitted; Automatically transmit the HARQ process or MAC PDU that was not transmitted, not successfully transmitted, or not completely transmitted due to resource conflicts; Low priority resources or CGs are automatically transferred; Automatic transmission of MAC PDUs or data considered to be low priority.

40. The terminal device according to claim 39, wherein: The automatic transmission method of the transmission unit includes at least one of the following: Automatic transmission or automatic retransmission based on the retransmission mode 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 indication; Automatic transmission or automatic retransmission based on the transmission mode of CG retransmission timer; Automatic transmission or automatic retransmission based on the transmission mode of the untransmitted MAC PDU caused by LBT failure; Automatic transmission or automatic retransmission is performed because the HARQ process is not changed due to the LBT failure, or the HARQ process is still in pending transmission mode; Based on the failure of downlink LBT resulting in DFI or DCI not receiving the corresponding transmission mode, automatic transmission or automatic retransmission is performed.

41. The terminal device according to claim 39, wherein: The automatic transmission is NRU automatic transmission.

42. According to the terminal device according to claim 39, the transmission unit is also used for, for a CG resource, the MAC entity of the terminal device delivers the CG resource to the HARQ entity when a sixth condition is met.

43. The terminal device according to claim 42, wherein the sixth condition comprises at least one of the following: The PUSCH of CG does not conflict with the PUSCH resources scheduled by DCI; The PUSCH of CG does not conflict with the PUSCH resources scheduled by RAR / TC-RNTI; The PUSCH of CG does not conflict with the PUSCH resources of MSGA payload; The MAC entity is configured with LCH-based priority processing; The CG retransmission timer is configured but not running; The HARQ process is pending; CG timer is not running.

44. According to the terminal device according to claim 42, the transmission unit is also used to determine the NDI flip of the HARQ process.

45. According to the terminal device according to claim 42, the transmission unit is also used to determine that the NDI of the HARQ process is not flipped.

46. ​​The terminal device according to claim 44, 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 met, 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 size 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 has the same CG index as the CG before the HARQ process and the same configured BWP; 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 most recent CG before the HARQ process is a low-priority CG; There is a low priority MAC PDU in the HARQ process; In the HARQ process, there exists a MAC PDU which is not transmitted, not successfully transmitted, not completely transmitted, or not transmitted due to resource conflict.

47. According to the terminal device according to claim 44, the transmission unit is also used to submit the MAC PDU to the HARQ process when the MAC PDU to be transmitted is obtained, and / or instruct the HARQ process to perform a new transmission.

48. According to the terminal device according to claim 45, the transmission unit is further used to deliver the MAC PDU to the HARQ process, and / or instruct the HARQ process to perform retransmission.

49. The terminal device according to claim 48, wherein the transmission unit is further configured to deliver the MAC PDU to the HARQ process and / or instruct the HARQ process to perform retransmission when an eighth condition is met, wherein 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 size is the same as the size of the CG before the HARQ process; The uplink grant size is the same as the size of the most recent 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 most recent CG before the HARQ process; The uplink grant has the same CG index as the CG before the HARQ process and the same configured BWP; The uplink grant size and the CG before the HARQ process are the same CG configuration; The uplink grant has the same CG index as the most recent CG before the HARQ process and has the same configured BWP; The uplink grant size is configured as the same CG as the most recent CG before the HARQ process; The uplink grant and the CG before the HARQ process are on the same BWP; 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 most recent CG before the HARQ process is a low-priority CG; There is a low priority MAC PDU in the HARQ process; In the HARQ process, there exists a MAC PDU which is not transmitted, not successfully transmitted, not completely transmitted, or not transmitted due to resource conflict.

50. The terminal device according to claim 39, wherein the transmission unit is further configured to, for an uplink grant resource or a CG resource, perform at least one of the following steps when a ninth condition is met: Do not deliver uplink grant resources or CG resources to the HARQ entity; Ignore the uplink authorization resource or CG resource; The uplink authorization resources or CG resources are delivered to the HARQ process but the uplink authorization resources or CG resources are ignored.

51. The terminal device according to claim 50, wherein the ninth condition comprises at least one of the following: The CG retransmission timer is configured but not running; The CG retransmission timer is configured but the value is 0; The HARQ process is not pending; CG timer running.

52. The terminal device according to claim 39, wherein the transmission unit is further configured to determine the state of the HARQ process in at least one of the following ways: The HARQ process corresponding to the low-priority uplink grant resource is determined as pending; The HARQ process corresponding to the uplink grant resource of the low-priority MAC PDU is determined as pending; The HARQ process corresponding to the low-priority CG resource is determined as pending; The HARQ process corresponding to the CG resource of the low-priority MAC PDU is determined as pending; Determine the conflicting uplink authorization resources or CG resources as pending; The HARQ process when the MAC PDU is obtained is determined as pending; The HARQ process when the MAC PDU corresponding to the CG resource is obtained is determined as pending; Determine the conflicting and prioritized uplink authorization resources or CG resources as pending; Determine the non-conflicting uplink authorization resources or CG resources as not pending; Determine the uplink authorized resources or CG resources that are not in conflict and have not failed LBT 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 is received, and the HARQ process is determined as not pending; MAC PDU transmission is executed, successful or completed, and an 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 is not transmitted due to a conflict, and the HARQ process is determined as not pending.

53. A terminal device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the terminal device executes the method as claimed in any one of claims 1 to 26.

54. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 26.

55. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 26.

56. A computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method of any one of claims 1 to 26.

Images