WO2022041002A1 - Procédé de transmission et dispositif terminal - Google Patents

Procédé de transmission et dispositif terminal Download PDF

Info

Publication number
WO2022041002A1
WO2022041002A1 PCT/CN2020/111511 CN2020111511W WO2022041002A1 WO 2022041002 A1 WO2022041002 A1 WO 2022041002A1 CN 2020111511 W CN2020111511 W CN 2020111511W WO 2022041002 A1 WO2022041002 A1 WO 2022041002A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq process
resource
uplink grant
transmission
automatic transmission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/111511
Other languages
English (en)
Chinese (zh)
Inventor
付喆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202080102089.6A priority Critical patent/CN115943582B/zh
Priority to PCT/CN2020/111511 priority patent/WO2022041002A1/fr
Publication of WO2022041002A1 publication Critical patent/WO2022041002A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria

Definitions

  • the present application relates to the field of communications, and more particularly, to a transmission method and terminal device.
  • 5G 5th-Generation, next-generation communication
  • RAN Radio Access Network, wireless access network
  • 2URLLC Ultra-Reliable and Low Latency Communication, ultra-reliable and low-latency communication
  • CG Configured Grant, configuration authorization
  • CG supporting slot-level (slot level) period, Support for automatic transfer of CG, etc.
  • the goal of NRU is to make NR work in unlicensed frequency bands, including the following working scenarios:
  • PCell is licensed spectrum
  • SCells working on unlicensed spectrum are aggregated through carrier aggregation
  • PCell is LTE licensed spectrum
  • PScell is NR unlicensed spectrum
  • NR works as an independent cell in unlicensed spectrum.
  • the embodiments of the present application provide a transmission method and terminal device, which can use CG resources to perform automatic transmission or retransmission to reduce data loss.
  • the embodiment of the present application provides a transmission method, including:
  • the terminal device receives and configures authorized CG resources
  • the terminal device uses the CG resource to automatically transmit the object of the first type using the mechanism of the second type.
  • An embodiment of the present application provides a terminal device, including:
  • a receiving unit configured to receive configuration authorization CG resources
  • a transmission unit configured to use the CG resource to automatically transmit the object of the first type using the mechanism of the second type.
  • An embodiment of the present application provides a terminal device, including a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory, so that the terminal device executes the above-mentioned transmission method.
  • An embodiment of the present application provides a network device including a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory, so that the network device executes the above-mentioned transmission method.
  • An embodiment of the present application provides a chip for implementing the above-mentioned transmission method.
  • the chip includes: a processor for calling and running a computer program from the memory, so that the device on which the chip is installed executes the above-mentioned transmission method.
  • Embodiments of the present application provide a computer-readable storage medium for storing a computer program, and when the computer program is run by a device, the device enables the device to execute the above-mentioned transmission method.
  • An embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned transmission method.
  • the embodiments of the present application provide a computer program, which, when running on a computer, causes the computer to execute the above-mentioned transmission method.
  • the CG resource is used for automatic transmission or retransmission, which can reduce data loss.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of Example 1 of a transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of Example 2 of a transmission method according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a chip according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • Wireless Fidelity Wireless Fidelity
  • WiFi fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • STAION, ST in the WLAN
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • a mobile phone Mobile Phone
  • a tablet computer Pad
  • a computer with a wireless transceiver function a virtual reality (Virtual Reality, VR) terminal device
  • augmented reality (Augmented Reality, AR) terminal Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • 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.
  • the network device may also be a base station set in a location such as land or water.
  • a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device (
  • the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
  • Pico cell Femto cell (Femto cell), etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • FIG. 1 exemplarily shows a communication system 100 .
  • the communication system includes one network device 110 and two terminal devices 120 .
  • the communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers of terminal devices 120, which are not limited in this embodiment of the present application.
  • the communication system 100 may further include a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF) and other network entities, to which the embodiments of the present application Not limited.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system further includes a plurality of core networks for communicating with the access network equipment.
  • the access network equipment may be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system, or an authorized auxiliary access long-term evolution (authorized auxiliary access long-term evolution, LAA-
  • the evolved base station (evolutional node B, may be referred to as eNB or e-NodeB for short) in the LTE) system is a macro base station, a micro base station (also called a "small base station"), a pico base station, an access point (AP), Transmission site (transmission point, TP) or new generation base station (new generation Node B, gNodeB), etc.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device and a terminal device with a communication function, and the network device and the terminal device may be specific devices in this embodiment of the application, which will not be repeated here; It may include other devices in the communication system, for example, other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship.
  • a indicates B it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • corresponding may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.
  • NRU CG and ULRRC CG enhancement in the NRU scenario, for example: introducing coordinated UL CG enhancement in NRU and URLLC to apply to unlicensed spectrum.
  • URLLC enhances the CG cycle to support any slot-level service cycle.
  • URLLC introduces multiple (multiple) CGs.
  • the HARQ (Hybrid Automatic Repeat Request) processes configured by different CGs are different, and the processes of different CGs are guaranteed to be different through HARQ-ProcID-Offset2 (HARQ process identifier-offset 2).
  • the working frequency band (Band) of NRU is 5GHz unlicensed spectrum and 6GHz unlicensed spectrum, (e.g., US 5925–7125MHz, or European 5925–6425MHz, or parts thereof).
  • the design of the NRU should ensure fairness with other systems already working on the unlicensed spectrum, such as WiFi (Wireless Fidelity, wireless fidelity).
  • WiFi Wireless Fidelity, wireless fidelity
  • the principles of fairness include that the NRU's impact on systems already deployed on unlicensed spectrum (eg, WiFi) cannot exceed the impact between those systems.
  • the general energy detection mechanism is the LBT (Listen Before Talk) mechanism.
  • the basic principle of this mechanism is that, before the base station or terminal (transmitter) transmits data on the unlicensed spectrum, it needs to listen for a period of time according to regulations. If the result of listening indicates that the channel is in an idle state, the transmitting end can transmit data to the receiving end. If the listening result indicates that the channel is in an occupied state, the transmitting end needs to roll back a certain period of time and continue to monitor the channel until the channel listening result is in an idle state, and can transmit data to the receiving end.
  • the HARQ process of the NRU CG is not calculated according to the formula, but selected by the UE itself.
  • RRC configures one HARQ process set, and the UE can select one HARQ process from the set for this CG transmission.
  • the specifically configured HARQ process interval is determined by harq-ProcID-Offset and nrofHARQ-Processes.
  • NRU introduces multiple CGs. Multiple CG configurations can share the HARQ process.
  • a CG retransmission timer (cg-RetransmissionTimer, CG retx Timer for short) is introduced to support automatic retransmission of resources when CG resources cannot be transmitted due to LBT failure. After the cg-RetransmissionTimer times out, if the CG timer (configured GrantTimer, CG timer for short) does not time out, the corresponding HARQ process can be retransmitted.
  • CG transmission can be interrupted by dynamic scheduling DCI (Downlink Control Information, downlink control information) and DFI (Downlink Feedback Information, downlink feedback information).
  • DCI Downlink Control Information, downlink control information
  • DFI Downlink Feedback Information, downlink feedback information
  • the CG timer stops (stop) when DFI is ACK, and is not affected (No impact) when DFI is NACK, and DCI is new transmission (new tx) or retransmission (retx) ) to start or restart.
  • CG timer stops (stop) when DFI is ACK, and is not affected (No impact) when DFI is NACK, and DCI is new transmission (new tx) or retransmission (retx) ) to start or restart.
  • CG retx timer stop the CG retransmission timer (CG retx timer).
  • the CG retransmission timer stops when the DFI is ACK, NACK, new transmission or retransmission.
  • FIG. 2 is a schematic flowchart of a transmission method 200 according to an embodiment of the present application.
  • the method can optionally be applied to the system shown in Figure 1, but is not limited thereto.
  • the method includes at least some of the following.
  • the terminal device receives a configuration authorization (CG) resource.
  • CG configuration authorization
  • the terminal device uses the CG resource to automatically transmit the first-type object by using the second-type mechanism.
  • the conventional transport mechanism for the first type of object may be the first type of mechanism.
  • the second type of mechanism may be different from the first type of mechanism.
  • the terminal device uses the second type mechanism to automatically transmit the first type object, so that the transmission object and the transmission mechanism are not bound, and the specific transmission mechanism can also be applied to various transmissions.
  • object For example, the first type of object may be an object of a first communication scenario, and the second type of mechanism may be a transmission mechanism of the second communication scenario, and the two communication scenarios are different.
  • the automatic transmission by the terminal device using the CG resource for the first type of objects using the second type mechanism includes: the terminal device using the CG resource to use the second communication for objects in the first communication scenario.
  • the transfer mechanism of the scene is automatically transferred.
  • the terminal device can use the CG resource to automatically transmit the objects of the NRU scenario using the URLLC scenario transmission mechanism.
  • the first communication scenario may again be an unlicensed spectrum access or scenario.
  • the second communication scenario may again be a licensed spectrum access or scenario.
  • the scene or object is an R16 scene or object.
  • the terminal device can use the CG resource to automatically transmit the objects of the URLLC scenario using the NRU scenario transmission mechanism.
  • the first communication scenario may again be a licensed spectrum access or scenario.
  • the second communication scenario may again be an unlicensed spectrum access or scenario.
  • the scene or object is an R16 scene or object.
  • the terminal device receiving the CG resources includes: the terminal device receives one or more CG resources from the network, and each CG resource has a corresponding Hybrid Automatic Repeat Request (HARQ) resource. ) process, each CG resource includes at least one of the following configurations:
  • the premise of configuring the autonomousTx includes: the terminal device, the MAC entity or the CG resource of the terminal device are configured to be prioritized based on LCH (Logical Channel, logical channel).
  • LCH Logical Channel, logical channel
  • the terminal device receives CG resources, including:
  • the terminal device receives one or more CG resources from the network, each CG resource has a corresponding HARQ process of HARQ, and each CG resource includes at least one of the following configurations:
  • the CG resource is configured in the manner of a new wireless unlicensed NRU CG or an ultra-reliable and low-latency communication URLLC CG.
  • the configuration mode and the transmission mode may not be bound.
  • the URLLC transmission mechanism can be used for automatic transmission.
  • the NRU transmission mechanism can be used for automatic transmission.
  • the terminal device uses the CG resource to automatically transmit the first type of objects by using the second type mechanism, including: automatically transmitting at least one of the following objects:
  • the HARQ process is not changed due to LBT failure, or the HARQ process is still a pending HARQ process or MAC PDU;
  • DFI downlink feedback information or DCI (downlink control information) HARQ process or MAC PDU not received due to downlink LBT failure.
  • DCI downlink control information
  • the LBT failure may be caused by inter-system interference, such as WIFI, or by intra-system interference, or by false detection. In controlled scenarios, it is mainly caused by interference within the system, or by false detection.
  • performing automatic transmission includes at least one of the following:
  • Automatic transmission is performed based on the transmission mode of low-priority resources or low-priority CGs caused by resource conflicts.
  • the automatic transmission is URLLC automatic transmission.
  • performing automatic transmission includes: for a CG resource, the MAC entity of the terminal device determines the NDI (New Data Indication, NDI) of the HARQ process when the first condition is satisfied. new data indication) rollover, and/or hand over the CG resource to the HARQ entity.
  • the HARQ entity may include multiple HARQ processes.
  • the first condition includes at least one of the following:
  • the PUSCH (PhysicalUplinkSharedChannel, physical uplink shared channel) of the CG does not conflict with the PUSCH resource scheduled by the DCI;
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by RAR (Random Access Response, random access response) or TC-RNTI (Temporary Cell-Radio Network Temporary Identifier, temporary cell wireless network temporary identifier);
  • RAR Random Access Response, random access response
  • TC-RNTI Temporary Cell-Radio Network Temporary Identifier, temporary cell wireless network temporary identifier
  • the PUSCH of the CG does not conflict with the PUSCH resource of the two-step random access message A (MSGA) payload (Payload);
  • the MAC entity is configured with LCH-based priority processing
  • CG timer is configured but not running
  • the CG retransmission timer is configured but the value is 0.
  • performing automatic transmission further includes: for a HARQ process corresponding to an uplink grant, the MAC entity or the HARQ entity of the terminal device determines the MAC address when the second condition is satisfied.
  • the PDU is acquired, and the second condition includes at least one of the following:
  • the uplink grant is CG
  • the uplink authorization is configured with the automatic transmission parameter autonomousTx;
  • the HARQ process is pending
  • the uplink grant size is the same as the acquired MAC PDU size
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the size of the uplink grant is the same as the size of the last CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the last CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP (Bandwidth Part, bandwidth part) is the same;
  • the uplink grant size and the CG before the HARQ process are the same CG configuration
  • the uplink grant is the same as the CG index of the last CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the latest CG before the HARQ process are configured for the same CG;
  • the uplink grant is on the same BWP as the CG before the HARQ process;
  • the uplink grant is on the same BWP as the last CG before the HARQ process.
  • performing automatic transmission further includes: in the case that the MAC entity or HARQ entity of the terminal device obtains the MAC PDU to be transmitted, submitting the MAC PDU to the HARQ process, and/or, instructs the HARQ process to perform a new transmission.
  • performing automatic transmission further includes: the MAC entity or the HARQ entity of the terminal device determines the state of the HARQ process in the following manner:
  • 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,
  • the fourth condition includes at least one of the following: configuring autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process is executed, successful or completed , the uplink grant is a priority transmission resource, the uplink grant is a non-resource conflict uplink grant, the uplink grant or CG or the transmission of the MAC PDU is executed, successful or completed, the LBT of the uplink grant or the CG is successful, no The LBT failure indication is received, the transmission failure indication is not received, the retransmission indication is not received, the LBT success indication is received, and the transmission successful indication is received.
  • performing automatic transmission further includes determining the state of the HARQ process in the following manner: in the case where the fifth condition is satisfied, the HARQ process corresponding to the CG resource is pending, and the HARQ process corresponding to the CG resource is pending.
  • the fifth condition includes at least one of the following: configuring autonomousTx, the uplink grant is CG, the transmission of the HARQ process is not executed, unsuccessful or incomplete, the uplink grant is a low-priority resource, and the uplink grant is an uplink grant with conflicting resources,
  • the transmission of the uplink grant or the CG or the MAC PDU is not executed, unsuccessful or incomplete, the LBT of the uplink grant or the CG fails, an LBT failure indication is received, a transmission failure indication is received, and a retransmission indication is received, No LBT success indication was received, no transmission success indication was received.
  • the terminal device uses the CG resource to automatically transmit the first-type object by using the second-type mechanism, including at least one of the following:
  • performing automatic transmission includes at least one of the following:
  • Automatic transmission or automatic retransmission is performed based on the DFI or DCI not receiving the corresponding transmission mode caused by the downlink LBT failure.
  • the automatic transmission is NRU automatic transmission.
  • performing automatic transmission includes: for a CG resource, the MAC entity of the terminal device submits the CG resource to the HARQ entity under the condition that the sixth condition is satisfied.
  • the sixth condition includes at least one of the following:
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;
  • the PUSCH of the CG does not conflict with the PUSCH resource scheduled by the RAR/TC-RNTI;
  • the PUSCH of the CG does not conflict with the PUSCH resources of the MSGA payload
  • the MAC entity is configured with LCH-based priority processing
  • CG retransmission timer is configured but not running
  • the HARQ process is pending
  • the MAC entity determines the NDI inversion of the HARQ process.
  • the MAC entity determines that the NDI of the HARQ process is not reversed.
  • the automatic transmission is performed, further including:
  • the MAC entity or HARQ entity of the terminal device determines that the HARQ process corresponding to the CG resource obtains the MAC PDU to be transmitted when the seventh condition is satisfied, and the seventh condition includes at least one of the following:
  • the uplink authorization is CG
  • the uplink grant is configured with a CG retransmission timer
  • the HARQ process is pending
  • the uplink grant size is the same as the acquired MAC PDU size
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the CG before the HARQ process are the same CG configuration
  • the previous CG corresponding to the HARQ process is a low-priority CG
  • the last CG corresponding to the HARQ process is a low-priority CG
  • the automatic transmission is performed, further including:
  • the MAC entity or HARQ entity of the terminal device When the MAC entity or HARQ entity of the terminal device obtains the MAC PDU to be transmitted, it submits the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform new transmission.
  • the automatic transmission is performed, which further includes:
  • the MAC entity or HARQ entity of the terminal device delivers the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform retransmission.
  • the MAC entity or HARQ entity of the terminal device submits the MAC PDU to the HARQ process, and/or instructs the HARQ process to perform retransmission, including:
  • the MAC entity or the HARQ entity delivers the MAC PDU to the HARQ process and/or instructs the HARQ process to perform retransmission under the condition that an eighth condition is satisfied, and the eighth condition includes at least one of the following:
  • the uplink authorization is CG
  • the uplink grant is configured with a CG retransmission timer
  • the HARQ process is pending
  • the uplink grant size is the same as the acquired MAC PDU size
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the size of the uplink grant is the same as the size of the last CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the last CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the CG before the HARQ process are the same CG configuration
  • the uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the latest CG before the HARQ process are configured for the same CG;
  • the uplink grant is on the same BWP as the CG before the HARQ process;
  • the uplink grant is on the same BWP as the most recent CG before the HARQ process;
  • the previous CG corresponding to the HARQ process is a low-priority CG
  • the last CG corresponding to the HARQ process is a low-priority CG
  • performing automatic transmission includes:
  • the MAC entity or the HARQ entity performs at least one of the following steps when the ninth condition is satisfied:
  • the ninth condition includes at least one of the following:
  • CG retransmission timer is configured but not running
  • CG retransmission timer is configured but the value is 0;
  • the CG timer runs.
  • performing automatic transmission further comprising:
  • MAC PDU transmission is executed, successful or completed, and no LBT failure indication is received, the HARQ process is determined as not pending;
  • MAC PDU transmission is executed, successful or completed, and the LBT success indication is received, and the HARQ process is determined as not pending;
  • the resource corresponding to the MAC PDU is a priority resource, and the resource corresponding to the MAC PDU is not a low-priority resource;
  • the uplink grant resource corresponding to the MAC PDU is not a low-priority resource, or it is not transmitted due to a conflict, and the HARQ process is determined as not pending.
  • URLLC automatic transmission can be performed on the objects of the NRU scene, to ensure that the objects of the NRU scene, such as MAC PDUs that have not been transmitted or have not been successfully transmitted due to LBT failure, are not discarded, so as to avoid data loss, or to make the data as soon as possible. transmission.
  • NRU automatic transmission can be performed on the objects of the URLLC scene, to ensure that the objects of the URLLC scene, such as low-priority MAC PDUs, are not discarded, data loss is avoided, or data is transmitted as soon as possible.
  • Example 1 A pending (pending) HARQ process and/or a non-pending (not pending) HARQ process triggers URLLC automatic transmission.
  • the third condition is at least one of the following: configure autonomousTx, the uplink resource (for example, uplink grant) is CG, and the HARQ process obtains the MAC PDU for transmission. And/or, when the fourth condition is satisfied, it is considered that the corresponding HARQ process is not pending.
  • the fourth condition is: configure autonomousTx, the uplink resource is CG, the transmission of the HARQ process is executed, succeeded or completed, the uplink grant is the priority transmission resource, the uplink grant is the uplink grant that does not conflict with the resource, the uplink grant, CG Or the transmission of the MAC PDU is executed, successful or completed, the LBT for the uplink grant or CG is successful, no LBT failure indication from the lower layer or NW is received, no transmission failure indication from the lower layer or NW is received, and no lower layer or NW is received.
  • the retransmission indication is received, the LBT success indication of the lower layer or NW is received, and the transmission success indication of the lower layer or NW is received. or,
  • the fifth condition is: configure autonomousTx, the uplink resource is CG, the transmission of the HARQ process is not executed, unsuccessful or incomplete, the uplink grant is a low-priority transmission resource, the uplink grant is the uplink grant of resource conflict, the uplink grant
  • the transmission of grant, CG or MAC PDU is not executed, unsuccessful or incomplete, the LBT of the uplink grant or CG fails, the LBT failure indication of the lower layer or NW is received, the transmission failure indication of the lower layer or NW is received, and the lower layer is received.
  • the retransmission indication of the NW, the LBT success indication of the lower layer or the NW is not received, and the transmission success indication of the lower layer or the NW is not received.
  • Example 2 Deprioritized MAC PDUs are automatically retransmitted using NRU. Specifically, it includes at least one of the following methods:
  • the sixth condition includes at least one of the following: the CG retransmission timer (cg-RetransmissionTimer) is configured and not running, the HARQ process is pending, and the CG timer (configuredGrantTimer) is not running.
  • the first mode may also include the following cases: Case 1: The NDI is considered to be reversed, and the transmission is performed according to the new transmission;
  • the ninth condition may include at least one of the following: the cg-RetransmissionTimer is configured and not running, the HARQ process is not pending, and the configuredGrantTimer is running.
  • the ninth condition may include at least one of the following: cg-RetransmissionTimer is configured but the configured duration is 0, the HARQ process is not pending, and the configuredGrantTimer is running.
  • Example 1 The following is the specific implementation process of Example 1 and Example 2:
  • Example 1 Set pending or not pending status for HARQ process. For pending HARQ and/or not pending HARQ processes, trigger URLLC automatic transmission.
  • Example 1 As shown in Figure 3, the specific implementation process of Example 1 is as follows:
  • the UE receives the CG resource from the network (NW). specific:
  • the network can configure one or more CG resources for the UE
  • the HARQ process corresponding to each CG resource configuration, the HARQ process corresponding to different CG resources may be different or the same.
  • the premise of configuring autonomousTx is: the network is the UE or the corresponding MAC entity or CG resource, and configures LCH-BasedPrioritization (LCH-BasedPrioritization)
  • the UE uses the CG resources configured by the network for transmission. specific,
  • the MAC entity For each CG resource, the MAC entity considers the NDI to be reversed under at least one of the following conditions (see the first condition in the above-mentioned embodiment), and/or delivers the CG resource to the HARQ entity.
  • the condition is:
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;
  • the PUSCH of the CG does not conflict with the PUSCH resource scheduled by the RAR/TC-RNTI;
  • the PUSCH of the CG does not conflict with the PUSCH resource of the MSGA payload
  • the MAC entity is configured with LCH-basedPrioritization
  • cg-RetransmissionTimer is configured but the value is 0.
  • the uplink grant is CG
  • the uplink grant is configured with autonomousTx
  • the HARQ process is pending
  • the size of the uplink grant is the same as the size of the obtained MAC PDU
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the size of the uplink grant is the same as the size of the last CG before the HARQ process
  • the uplink grant is the same as the CG index (index) of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the last CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;
  • the size of the uplink grant is the same CG configuration as the CG before the HARQ process
  • the uplink grant is the same as the CG index of the last CG before the HARQ process and the configured BWP is the same;
  • the size of the uplink grant is the same CG configuration as the last CG before the HARQ process
  • the uplink grant is on the same BWP as the CG before the HARQ process;
  • the uplink grant is on the same BWP as the most recent CG before the HARQ process.
  • the MAC PDU is acquired for transmission (that is, the MAC PDU to be transmitted is acquired), the MAC PDU is handed over to the HARQ process, and/or, the HARQ process is instructed to perform a new transmission.
  • the third condition is at least one of the following: configure autonomousTx, the uplink resource (uplink grant) is CG, and the HARQ process obtains the MAC PDU for transmission; when the fourth condition is satisfied, it is considered that the corresponding HARQ process is not pending.
  • the fourth condition includes at least one of the following: configuring autonomousTx, the uplink resource is CG, the transmission of the HARQ process is executed/successful/completed, the transmission of the CG/MAC PDU is executed/successful/completed, the LBT of the CG is successful , did not receive the LBT failure indication of the lower layer or NW, did not receive the transmission failure indication of the lower layer or NW, did not receive the retransmission indication of the lower layer or NW, received the LBT success indication of the lower layer or NW, received the lower layer or NW Transmission success indication.
  • the fifth condition includes at least one of the following: configuring autonomousTx, the uplink resource is CG, the transmission of the HARQ process is not executed/unsuccessful/completed, the transmission of the CG or the MAC PDU is not executed, unsuccessful or incomplete, the LBT failure of CG, LBT failure indication of lower layer or NW received, transmission failure indication of lower layer or NW received, retransmission indication of lower layer or NW received, no LBT success indication of lower layer or NW received, no lower layer being received or NW's transmission success indication.
  • a method for URLLC automatic transmission of untransmitted or unsuccessfully transmitted MAC PDUs in the case of LBT failure is presented to ensure that the MAC PDU Not discarded, avoid data loss, or make data transfer as fast as possible.
  • Example 2 Set pending or not pending state for HARQ process of deprioritized CG or low priority MAC PDU. Use NRU automatic retransmission for deprioritized MAC PDUs.
  • Example 2 As shown in Figure 4, the specific implementation process of Example 2 is as follows:
  • the UE receives the CG resource from the network (NW). specific:
  • the network can configure one or more CG resources for the UE
  • the HARQ process corresponding to each CG resource configuration, the HARQ process corresponding to different CG resources may be different or the same.
  • the UE uses the CG resources configured by the network for transmission.
  • NRU automatic retransmission is used for deprioritized MAC PDUs. Specifically, it can be at least one of the following:
  • the MAC entity For a CG resource, the MAC entity, if at least one of the following conditions (see the above-mentioned sixth condition) is satisfied, delivers the CG resource to the HARQ entity, and considers NDI inversion (new transmission).
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by RAR or TC-RNTI;
  • the PUSCH of the CG does not conflict with the PUSCH resource of the MSGA payload
  • the MAC entity is configured with LCH-basedPrioritization
  • cg-RetransmissionTimer is configured but not running
  • the HARQ process is pending
  • the uplink grant is CG
  • the uplink grant is configured with CG retx timer (CG retransmission timer);
  • the HARQ process is pending
  • the size of the uplink grant is the same as the size of the obtained MAC PDU
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the size of the uplink grant is the same as the size of the last CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CGindex of the last CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;
  • the size of the uplink grant is the same CG configuration as the CG before the HARQ process
  • the uplink grant is the same as the CG index of the last CG before the HARQ process and the configured BWP is the same;
  • the size of the uplink grant is the same CG configuration as the last CG before the HARQ process
  • the uplink grant is on the same BWP as the CG before the HARQ process;
  • the uplink grant is on the same BWP as the last CG before the HARQ process;
  • the previous CG corresponding to the HARQ process is the deprioritized CG
  • the last CG corresponding to the HARQ process is a low-priority CG
  • MAC PDU transmission is executed, successful or completed, and the HARQ process is determined as not pending;
  • MAC PDU transmission is executed, successful or completed, and no LBT failure indication from the lower layer or NW is received, and the HARQ process is determined as not pending;
  • MAC PDU transmission is executed, successful or completed, and the LBT success indication from the lower layer or NW is received, and the HARQ process is determined as not pending;
  • the uplink grant resource corresponding to the MAC PDU is a priority resource, and the resource corresponding to the MAC PDU is not a low-priority resource, and the HARQ process or MAC PDU is determined as not pending;
  • the uplink grant resource corresponding to the MAC PDU is not a low-priority resource, or it is not transmitted due to a conflict, and the HARQ process is determined as not pending.
  • a MAC entity For a CG resource, a MAC entity, if at least one of the following conditions (see the sixth condition in the above-mentioned embodiment) is satisfied, deliver the CG resource to the HARQ entity, but do not consider the NDI to be reversed (reset pass).
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by RAR or TC-RNTI;
  • the PUSCH of the CG does not conflict with the PUSCH resource of the MSGA payload
  • the MAC entity is configured with LCH-basedPrioritization
  • cg-RetransmissionTimer is configured but not running
  • the HARQ process is pending
  • (2-2) Correspondingly, deliver the MAC PDU to the HARQ process, and/or instruct the HARQ process to perform retransmission.
  • the MAC PDU is delivered to the HARQ process, and/or the HARQ process is instructed to perform retransmission.
  • the conditions include:
  • the uplink grant is CG
  • the uplink grant is configured with CG retx timer
  • the HARQ process is pending
  • the size of the uplink grant is the same as the size of the obtained MAC PDU
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the size of the uplink grant is the same as the size of the last CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the last CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;
  • the size of the uplink grant is the same CG configuration as the CG before the HARQ process
  • the uplink grant is the same as the CG index of the last CG before the HARQ process and the configured BWP is the same;
  • the size of the uplink grant is the same CG configuration as the last CG before the HARQ process
  • the uplink grant is on the same BWP as the CG before the HARQ process;
  • the uplink grant is on the same BWP as the last CG before the HARQ process;
  • the previous CG corresponding to the HARQ process is the deprioritized CG
  • the last CG corresponding to the HARQ process is a low-priority CG
  • (2-3) Set the state of the HARQ process, or consider the HARQ process as pending or not pending. For details, refer to the relevant description in (1-4) above.
  • the MAC entity does not deliver the uplink grant resource or CG resource to the HARQ process when the following conditions are met (see the ninth condition in the above embodiment), or, Ignore the grant; or, deliver the CG resource to the HARQ process, but ignore the grant.
  • the condition is at least one of the following: cg-RetransmissionTimer is configured and not running, the HARQ process is not pending, and configuredGrantTimer is running.
  • the MAC entity does not deliver the uplink grant resource or CG resource to the HARQ process, or ignores the grant when the following conditions are met (see the ninth condition above). ; Or, deliver the uplink grant resource or CG resource to the HARQ process, but ignore the grant.
  • the condition is at least one of the following: cg-RetransmissionTimer is configured and the configured duration is 0, the HARQ process is not pending, and the configuredGrantTimer is running.
  • a method for automatic NRU transmission of deprioritized resources is given to ensure that the MAC PDU is not discarded to avoid data loss, or to be transmitted as soon as possible.
  • FIG. 5 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
  • the terminal device 400 may include:
  • a receiving unit 410 configured to receive configuration authorization CG resources
  • the transmission unit 420 is configured to use the CG resource to automatically transmit the object of the first type using the mechanism of the second type.
  • the transmitting unit 420 is further configured to use the CG resource to automatically transmit the object of the first communication scene using the transmission mechanism of the second communication scene.
  • the receiving unit 410 is further configured to receive one or more CG resources from the network, each CG resource has a corresponding HARQ process of HARQ, and each CG resource has a corresponding HARQ process.
  • the resource includes at least one of the following configurations:
  • the precondition for configuring the autonomousTx includes: the terminal device, the MAC entity or the CG resource of the terminal device are configured to be preferentially processed based on the logical channel LCH.
  • the receiving unit 410 is further configured to receive one or more CG resources from the network, each CG resource has a corresponding HARQ process of HARQ, and each CG resource has a corresponding HARQ process.
  • the resource includes at least one of the following configurations:
  • the CG resource is configured in the manner of a new wireless unlicensed NRU CG or an ultra-reliable and low-latency communication URLLC CG.
  • the transmission unit 420 is further configured to automatically transmit at least one of the following objects:
  • the HARQ process is not changed due to LBT failure, or the HARQ process is still a pending HARQ process or MAC PDU;
  • the HARQ process or MAC PDU corresponding to downlink feedback information DFI or downlink control information DCI is not received due to downlink LBT failure.
  • the manner in which the transmission unit 420 performs automatic transmission includes at least one of the following:
  • Automatic transmission is performed based on the transmission mode of low-priority resources or low-priority CGs caused by resource conflicts.
  • the automatic transmission is URLLC automatic transmission.
  • the transmission unit 420 is further configured to, for a CG resource, when the first condition is satisfied, determine that the new data of the HARQ process indicates NDI inversion, and/or, convert the The CG resource is delivered to the HARQ entity.
  • the first condition includes at least one of the following:
  • the physical uplink shared channel PUSCH of the CG does not conflict with the PUSCH resource scheduled by the DCI;
  • the PUSCH of the CG does not conflict with the PUSCH resource scheduled by the random access response RAR or the temporary cell radio network temporary identifier TC-RNTI;
  • the PUSCH of the CG does not conflict with the PUSCH resource of the two-step random access message A;
  • the MAC entity is configured with LCH-based priority processing
  • CG timer is configured but not running
  • the CG retransmission timer is configured but the value is 0.
  • the transmission unit 420 is further configured to, for a HARQ process corresponding to an uplink grant, determine that a MAC PDU is acquired when a second condition is satisfied, and the second condition includes: At least one of the following:
  • the uplink authorization is CG
  • the uplink grant is configured with the automatic transmission parameter autonomousTx
  • the HARQ process is pending
  • the uplink grant size is the same as the acquired MAC PDU size
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the size of the uplink grant is the same as the size of the last CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the last CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured bandwidth part BWP is the same;
  • the uplink grant size and the CG before the HARQ process are the same CG configuration
  • the uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the latest CG before the HARQ process are configured for the same CG;
  • the uplink grant is on the same BWP as the CG before the HARQ process;
  • the uplink grant is on the same BWP as the last CG before the HARQ process.
  • the transmission unit 420 is further configured to, in the case of acquiring the MAC PDU to be transmitted, submit the MAC PDU to the HARQ process, and/or indicate the HARQ process The process performs a new pass.
  • the transmission unit 420 is further configured to determine the status of the HARQ process in the following manner:
  • 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,
  • the fourth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, and the transmission of the HARQ process is executed, successful or Completed, the uplink grant is a priority transmission resource, the uplink grant is a non-resource conflict uplink grant, the transmission of the uplink grant or the CG or the MAC PDU is executed, successful or completed, and the LBT of the uplink grant or the CG is successful, No LBT failure indication is received, no transmission failure indication is received, no retransmission indication is received, LBT success indication is received, and transmission successful indication is received.
  • the transmission unit 420 is further configured to determine the status of the HARQ process in the following manner:
  • the HARQ process corresponding to the CG resource is pending, and the fifth condition includes at least one of the following: configuring the automatic transmission parameter autonomousTx, the uplink authorization is CG, the transmission of the HARQ process is not executed, If the uplink grant is unsuccessful or incomplete, the uplink grant is a low-priority resource, the uplink grant is an uplink grant with conflicting resources, the uplink grant or the transmission of the CG or the MAC PDU is not executed, unsuccessful or incomplete, the uplink grant Or the LBT of the CG fails, the LBT failure indication is received, the transmission failure indication is received, the retransmission indication is received, the LBT success indication is not received, and the transmission successful indication is not received.
  • the manner in which the transmission unit 420 performs automatic transmission includes at least one of the following:
  • the manner in which the transmission unit 420 performs automatic transmission includes at least one of the following:
  • Automatic transmission or automatic retransmission is performed based on the DFI or DCI not receiving the corresponding transmission mode caused by the downlink LBT failure.
  • the automatic transmission is NRU automatic transmission.
  • the transmitting unit 420 is further configured to, for a CG resource, deliver the CG resource to the HARQ entity when the MAC entity of the terminal device satisfies the sixth condition.
  • the sixth condition includes at least one of the following:
  • the PUSCH of the CG does not conflict with the PUSCH resources scheduled by the DCI;
  • the PUSCH of the CG does not conflict with the PUSCH resource scheduled by the RAR/TC-RNTI;
  • the PUSCH of the CG does not conflict with the PUSCH resources of the MSGA payload
  • the MAC entity is configured with LCH-based priority processing
  • CG retransmission timer is configured but not running
  • the HARQ process is pending
  • the transmission unit 420 is further configured to determine the NDI inversion of the HARQ process.
  • the transmission unit 420 is further configured to determine that the NDI of the HARQ process is not reversed.
  • the transmission unit 420 is further configured to determine that the HARQ process corresponding to the CG resource obtains the MAC PDU that needs to be transmitted under the condition that the seventh condition is satisfied.
  • the seventh condition includes at least one of the following:
  • the uplink authorization is CG
  • the uplink grant is configured with a CG retransmission timer
  • the HARQ process is pending
  • the uplink grant size is the same as the acquired MAC PDU size
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the CG before the HARQ process are the same CG configuration
  • the previous CG corresponding to the HARQ process is a low-priority CG
  • the last CG corresponding to the HARQ process is a low-priority CG
  • the transmission unit 420 is further configured to submit the MAC PDU to the HARQ process when the MAC PDU to be transmitted is obtained, and/or, Instructs the HARQ process to perform a new transmission.
  • 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.
  • the transmission unit 420 is further configured to deliver the MAC PDU to the HARQ process under the condition that the eighth condition is satisfied, and/or to indicate the HARQ process Perform retransmission, and the eighth condition includes at least one of the following:
  • the uplink authorization is CG
  • the uplink grant is configured with a CG retransmission timer
  • the HARQ process is pending
  • the uplink grant size is the same as the acquired MAC PDU size
  • the size of the uplink grant is the same as the size of the CG before the HARQ process
  • the size of the uplink grant is the same as the size of the last CG before the HARQ process
  • the uplink grant is the same as the CG index of the CG before the HARQ process;
  • the uplink grant is the same as the CG index of the last CG before the HARQ process;
  • the uplink grant is the same as the CG index of the CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the CG before the HARQ process are the same CG configuration
  • the uplink grant is the same as the CG index of the latest CG before the HARQ process and the configured BWP is the same;
  • the uplink grant size and the latest CG before the HARQ process are configured for the same CG;
  • the uplink grant is on the same BWP as the CG before the HARQ process;
  • the uplink grant is on the same BWP as the most recent CG before the HARQ process;
  • the previous CG corresponding to the HARQ process is a low-priority CG
  • the last CG corresponding to the HARQ process is a low-priority CG
  • the transmission unit 420 is further configured to perform at least one of the following steps for an uplink grant resource or CG resource when the ninth condition is satisfied:
  • the ninth condition includes at least one of the following:
  • CG retransmission timer is configured but not running
  • CG retransmission timer is configured but the value is 0;
  • the CG timer runs.
  • the transmission unit 420 is further configured to determine the status of the HARQ process by adopting at least one of the following manners:
  • the HARQ process is determined as not pending
  • MAC PDU transmission is executed, successful or completed, and the LBT success indication is received, and the HARQ process is determined as not pending;
  • the resource corresponding to the MAC PDU is a priority resource, and the resource corresponding to the MAC PDU is not a low-priority resource;
  • the uplink grant resource corresponding to the MAC PDU is not a low-priority resource, or it is not transmitted due to a conflict, and the HARQ process is determined as not pending.
  • the terminal device 400 in this embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing method embodiments.
  • each module (submodule, unit, or component, etc.) in the terminal device 400 reference may be made to the corresponding descriptions in the foregoing method embodiments, which are not repeated here.
  • the functions described by each module (submodule, unit, or component, etc.) in the terminal device 400 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or may be implemented by the same module Module (submodule, unit or component, etc.) implementation.
  • FIG. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
  • the communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so that the communication device 600 implements the methods in the embodiments of the present application.
  • the communication device 600 may also include a memory 620 .
  • the processor 610 may call and run a computer program from the memory 620, so that the communication device 600 implements the methods in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices .
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 600 may be the network device of this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the communication device 600 may be a terminal device in this embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the terminal device in each method in the embodiment of the present application, which is not repeated here for brevity.
  • FIG. 7 is a schematic structural diagram of a chip 700 according to an embodiment of the present application.
  • the chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiments of the present application.
  • the chip 700 may further include a memory 720 .
  • the processor 710 may call and run a computer program from the memory 720 to implement the method executed by the terminal device or the network device in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • the chip 700 may further include an input interface 730 .
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740 .
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • Chips applied to network equipment and terminal equipment can be the same chip or different chips.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.
  • the memory mentioned above may be either volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM).
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • FIG. 8 is a schematic block diagram of a communication system 800 according to an embodiment of the present application.
  • the communication system 800 includes a terminal device 810 and a network device 820 .
  • the terminal device 810 is configured to receive the configuration authorization CG resource; and use the CG resource to automatically transmit the first-type object by using the second-type mechanism.
  • the network device 820 is configured to send the CG resource to the terminal device.
  • the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • 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.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated.
  • the available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)), and the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium eg, a Solid State Disk (SSD)
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande concerne un procédé de transmission et un dispositif terminal. Le procédé de transmission comprend les étapes suivantes : un dispositif terminal reçoit une ressource d'octroi configuré (CG); le dispositif terminal utilise la ressource de CG pour transmettre automatiquement un premier type d'objet au moyen d'un second type de mécanisme. Selon les modes de réalisation de la présente demande, l'utilisation d'une ressource de CG pour transmettre automatiquement un premier type d'objet au moyen d'un second type de mécanisme peut réduire la perte de données.
PCT/CN2020/111511 2020-08-26 2020-08-26 Procédé de transmission et dispositif terminal Ceased WO2022041002A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080102089.6A CN115943582B (zh) 2020-08-26 2020-08-26 传输方法和终端设备
PCT/CN2020/111511 WO2022041002A1 (fr) 2020-08-26 2020-08-26 Procédé de transmission et dispositif terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/111511 WO2022041002A1 (fr) 2020-08-26 2020-08-26 Procédé de transmission et dispositif terminal

Publications (1)

Publication Number Publication Date
WO2022041002A1 true WO2022041002A1 (fr) 2022-03-03

Family

ID=80352319

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/111511 Ceased WO2022041002A1 (fr) 2020-08-26 2020-08-26 Procédé de transmission et dispositif terminal

Country Status (2)

Country Link
CN (1) CN115943582B (fr)
WO (1) WO2022041002A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115316024A (zh) * 2022-06-02 2022-11-08 上海移远通信技术股份有限公司 无线通信的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109451864A (zh) * 2018-02-13 2019-03-08 北京小米移动软件有限公司 传输信息的方法和装置、基站及用户设备
CN110752899A (zh) * 2018-07-23 2020-02-04 维沃移动通信有限公司 用于半静态授权上行传输的方法、终端设备和网络侧设备
CN111181693A (zh) * 2018-11-09 2020-05-19 华为技术有限公司 发送数据的方法、发送数据的装置、以及终端设备
CN111565460A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种上行传输方法及通信装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102271033B (zh) * 2010-06-04 2015-05-13 中兴通讯股份有限公司 实现混合自动重传请求内存动态调度的方法及装置
CN107295663B (zh) * 2016-04-01 2021-06-29 上海诺基亚贝尔股份有限公司 获取混合自动重传请求确认信息反馈的方法和装置
CN111262670B (zh) * 2019-01-11 2023-02-03 维沃移动通信有限公司 一种混合自动重传确认反馈信息传输方法和终端设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109451864A (zh) * 2018-02-13 2019-03-08 北京小米移动软件有限公司 传输信息的方法和装置、基站及用户设备
CN110752899A (zh) * 2018-07-23 2020-02-04 维沃移动通信有限公司 用于半静态授权上行传输的方法、终端设备和网络侧设备
CN111181693A (zh) * 2018-11-09 2020-05-19 华为技术有限公司 发送数据的方法、发送数据的装置、以及终端设备
CN111565460A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种上行传输方法及通信装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CMCC: "Discussion on CG enhancement for URLLC in unlicensed controlled", 3GPP DRAFT; R2-2007417, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051912164 *
OPPO: "Enhancements of configured grant in NR-U", 3GPP DRAFT; R2-1903285 - NR-U UP CONFIGURED UPLINK TRANSMISSION FOR NR-U, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Xi’an, China; 20190406 - 20190412, 28 March 2019 (2019-03-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051692558 *
SPREADTRUM COMMUNICATIONS: "Autonomous Uplink Transmission in NR-U", 3GPP DRAFT; R2-1900939 AUTONOMOUS UPLINK TRANSMISSION IN NR-U, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20190225 - 20190301, 15 February 2019 (2019-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051602309 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115316024A (zh) * 2022-06-02 2022-11-08 上海移远通信技术股份有限公司 无线通信的方法及装置

Also Published As

Publication number Publication date
CN115943582A (zh) 2023-04-07
CN115943582B (zh) 2024-12-31

Similar Documents

Publication Publication Date Title
US12506565B2 (en) Transmission method and terminal device
US20240032028A1 (en) Cg resource processing method, terminal device, and network device
US12557170B2 (en) Sidelink transmission method and terminal
WO2020248259A1 (fr) Procédé d'accès aléatoire, dispositif terminal et dispositif de réseau
WO2022021007A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2022067519A1 (fr) Procédés et terminaux d'accès aléatoire
WO2022120747A1 (fr) Procédé de communication sans fil et dispositif terminal
CN118476289A (zh) 无线通信的方法和终端设备
WO2023130473A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2020024616A1 (fr) Procédé d'accès aléatoire et dispositif associé
US12526087B2 (en) Wireless communication method, terminal device, and network device
WO2022183406A1 (fr) Procédé de transmission de canal de données, dispositif de terminal, et périphérique de réseau
WO2022082783A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif réseau
WO2022027249A1 (fr) Procédé et appareil de transmission d'informations, dispositif, et support de stockage
WO2022056725A1 (fr) Procédé de rétroaction de canal, dispositif terminal et dispositif de réseau
CN116368760B (zh) 无线通信的方法和终端设备
WO2024011396A1 (fr) Procédé de communication sans fil, dispositif de terminal et dispositif de réseau
WO2021026841A1 (fr) Procédé et dispositif permettant de transmettre une demande de planification
CN116321492B (zh) 使用配置授权cg资源的方法、终端设备和网络设备
WO2022246824A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2022041002A1 (fr) Procédé de transmission et dispositif terminal
CN116114197B (zh) 无线通信的方法、终端设备和网络设备
WO2022036696A1 (fr) Procédés de communication sans fil, dispositif terminal et dispositif réseau
CN116326015B (zh) 传输方法和终端设备
WO2022104515A1 (fr) Procédé de retransmission et terminal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20950674

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20950674

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: 202080102089.6

Country of ref document: CN