WO2021068224A1 - Procédé de communication sans fil, dispositif terminal et dispositif de réseau - Google Patents

Procédé de communication sans fil, dispositif terminal et dispositif de réseau Download PDF

Info

Publication number
WO2021068224A1
WO2021068224A1 PCT/CN2019/110723 CN2019110723W WO2021068224A1 WO 2021068224 A1 WO2021068224 A1 WO 2021068224A1 CN 2019110723 W CN2019110723 W CN 2019110723W WO 2021068224 A1 WO2021068224 A1 WO 2021068224A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
timer
harq process
configuration
harq
Prior art date
Application number
PCT/CN2019/110723
Other languages
English (en)
Chinese (zh)
Inventor
卢前溪
Original Assignee
Oppo广东移动通信有限公司
Oppo广东移动通信有限公司深圳分公司
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 Oppo广东移动通信有限公司, Oppo广东移动通信有限公司深圳分公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2019/110723 priority Critical patent/WO2021068224A1/fr
Priority to CN201980099518.6A priority patent/CN114258722A/zh
Publication of WO2021068224A1 publication Critical patent/WO2021068224A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • This application relates to the field of communications, in particular to a wireless communication method, terminal equipment and network equipment.
  • the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) introduced the concept of Configured Grant (CG).
  • the network device can configure a limited number of Hybrid Automatic Repeat Request (HARQ) process numbers for it, and the HARQ process numbers of the CG resources at different times may be the same.
  • HARQ Hybrid Automatic Repeat Request
  • a configured grant timer (configuredGrantTimer) of each HARQ process is introduced. Before the configuredGrantTimer corresponding to a certain HARQ process times out, the data saved in the HARQ process cannot be flushed.
  • the embodiments of the present application provide a wireless communication method, terminal equipment, and network equipment.
  • the HARQ function is supported to be turned on or off, the use of the configured authorization timer can be effectively implemented, and the scheduling performance can be further ensured.
  • a wireless communication method including: according to configuration information sent by a network device, a terminal device obtains at least one HARQ function status of a hybrid automatic repeat request HARQ process for transmitting uplink data, and Acquiring timer information of a configuration authorization timer used for the at least one HARQ process, where the HARQ function state includes an on state or an off state;
  • the terminal device determines the configuration grant timer for the first HARQ process according to the HARQ function status of the first HARQ process corresponding to uplink data transmission and the timer information of the configuration grant timer, and the at least one HARQ The process includes the first HARQ process.
  • a wireless communication method includes: a network device sends configuration information to a terminal device, the configuration information includes at least one HARQ function used for a hybrid automatic repeat request HARQ process when transmitting uplink data State, and timer information used for the configuration authorization timer of the at least one HARQ process, and the HARQ function state includes an on state or an off state.
  • a terminal device which is used to execute the method in the above-mentioned first aspect or its implementation manners.
  • the terminal device includes a functional module for executing the method in the foregoing first aspect or each of its implementation manners.
  • a network device which is used to execute the method in the above second aspect or each of its implementation manners.
  • the network device includes a functional module for executing the method in the above-mentioned second aspect or each of its implementation manners.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation manners.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each implementation manner thereof.
  • a device for implementing any one of the above-mentioned first aspect to the second aspect or the method in each of its implementation manners.
  • the device includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes any one of the above-mentioned first aspect to the second aspect or any of the implementations thereof method.
  • the device is a chip.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute any one of the above-mentioned first to second aspects or the method in each implementation manner thereof.
  • a computer program product including computer program instructions that cause a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • a computer program which when running on a computer, causes the computer to execute any one of the above-mentioned first to second aspects or the method in each of its implementation manners.
  • the terminal device when the HARQ function is turned on or off, can determine the configured authorization timer for the HARQ process according to the HARQ function status of the HARQ process and the timer information of the configured authorization timer, so as to be effective Realize the use of configuration authorization timer.
  • the use of the configuration authorization timer can limit the terminal device not being able to send new data during the operation of the configuration authorization timer, so as to reserve time for the scheduling of the original data, thereby further ensuring the scheduling performance.
  • Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.
  • Fig. 2 is a schematic diagram of the HARQ function state being turned on and off according to an embodiment of the present application.
  • Fig. 3 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.
  • Figures 4 to 6 are schematic diagrams of using configuration authorization timers according to embodiments of the present application.
  • Fig. 7 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • Fig. 8 is a schematic block diagram of a network device according to an embodiment of the present application.
  • Fig. 9 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • Fig. 10 is a schematic block diagram of a device according to an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • UMTS Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or called a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • LTE Long Term Evolutional Node B
  • eNB evolved base station
  • CRAN Cloud Radio Access Network
  • the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches
  • the communication system 100 also includes at least one terminal device 120 located within the coverage area of the network device 110.
  • the "terminal equipment” used here includes but is not limited to connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, and direct cable connection ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN wireless local area networks
  • IoT Internet of Things
  • a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal connection (Device to Device, D2D) communication may be performed between the terminal devices 120.
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • Figure 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 having a communication function and a terminal device 120.
  • the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in the embodiment of the present application.
  • the communication system 100 shown in FIG. 1 may also be an NTN system, that is, the network device 110 in FIG. 1 may be a satellite.
  • Non-Terrestrial Communication Network (Non-Terrestrial Network, NTN)
  • NTN technology generally uses satellite communication to provide communication services to ground users.
  • satellite communication Compared with terrestrial cellular network communication, satellite communication has many unique advantages.
  • satellite communication is not restricted by the user's area.
  • ordinary terrestrial communication cannot cover areas such as oceans, mountains, and deserts. Normal communication cannot be carried out in these areas due to the inability to set up communication equipment or due to sparse population.
  • satellite communications since a satellite can cover a larger ground and the satellite can orbit the earth, theoretically every corner of the earth can be covered by satellite communications.
  • satellite communication has greater social value.
  • Satellite communication can be covered at a lower cost in remote mountainous areas, poor and backward countries or regions, so that people in these areas can enjoy advanced voice communication and mobile Internet technology, which is conducive to narrowing the digital gap with developed areas and promoting The development of these areas.
  • the satellite communication distance is long, and the communication distance increases and the cost of communication does not increase significantly.
  • the stability of satellite communication is high, and it is not restricted by natural disasters.
  • communication satellites can be divided into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, and high High Elliptical Orbit (HEO) satellites, etc.
  • LEO Low-Earth Orbit
  • MEO Medium-Earth Orbit
  • GEO Geostationary Earth Orbit
  • HEO High Elliptical Orbit
  • the altitude range of the LEO satellite is 500km to 1500km, and the corresponding orbital period is about 1.5 hours to 2 hours.
  • the signal propagation delay of single-hop communication between users is generally less than 20ms.
  • the maximum satellite viewing time is 20 minutes.
  • the signal propagation distance is short, the link loss is small, and the requirement for the transmission power of the user terminal is not high.
  • the orbital height of the GEO satellite is 35786km, and the rotation period around the earth is 24 hours.
  • the signal propagation delay of single-hop communication between users is generally 250ms.
  • satellites In order to ensure the coverage of satellites and increase the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground.
  • a satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover tens to hundreds of kilometers in diameter. Ground area.
  • NR has two levels of retransmission mechanisms: HARQ mechanism at the Media Access Control (MAC) layer and Automatic Repeat-reQuest (ARQ) mechanism at the Radio Link Control (RLC) layer .
  • MAC Media Access Control
  • ARQ Automatic Repeat-reQuest
  • RLC Radio Link Control
  • the retransmission of lost or erroneous data is mainly handled by the HARQ mechanism of the MAC layer and supplemented by the retransmission function of the RLC layer.
  • the HARQ mechanism of the MAC layer can provide fast retransmission, and the ARQ mechanism of the RLC layer can provide reliable data transmission.
  • HARQ uses Stop-and-Wait Protocol to send data.
  • the stop-and-wait protocol after the sender sends a TB, it stops and waits for the confirmation message. In this way, the sender will stop and wait for confirmation after each transmission, which will result in very low user throughput. Therefore, NR uses multiple parallel HARQ processes. When one HARQ process is waiting for confirmation information, the sender can use another HARQ process to continue sending data. These HARQ processes together form a HARQ entity, which combines the stop-and-wait protocol to allow continuous data transmission.
  • HARQ is divided into uplink HARQ and downlink HARQ. Among them, uplink HARQ is for uplink data transmission, and downlink HARQ is for downlink data transmission, and the two are independent of each other.
  • each serving cell corresponding to the terminal device has its own HARQ entity.
  • Each HARQ entity maintains a set of parallel downlink HARQ processes and a set of parallel uplink HARQ processes.
  • the network equipment can indicate the maximum number of HARQ processes to the terminal equipment through Radio Resource Control (RRC) signaling according to the network deployment situation. If the network device does not provide corresponding configuration parameters, the default number of HARQ processes in the downlink is 8, and the maximum number of HARQ processes supported by each carrier in the uplink is always 16.
  • RRC Radio Resource Control
  • Each HARQ process can correspond to a HARQ process ID.
  • the Broadcast Control Channel BCCH
  • HARQ ID 0 is used for message 3 (Msg3) transmission in the random process.
  • each downlink HARQ process can only process 1 Transport Block (TB) at the same time; for terminals that support downlink space division multiplexing, each downlink HARQ process can process 1 at the same time Or 2 TB. Each uplink HARQ process of the terminal can handle 1 TB at the same time.
  • Transport Block TB
  • each uplink HARQ process of the terminal can handle 1 TB at the same time.
  • HARQ is divided into two types, synchronous and asynchronous in the time domain, and divided into two types, non-adaptive and adaptive in the frequency domain.
  • Both NR uplink and downlink use asynchronous adaptive HARQ mechanism.
  • Asynchronous HARQ that is, retransmission can occur at any time, and the time interval between the retransmission of the same TB and the previous transmission is not fixed.
  • Adaptive HARQ can change the frequency domain resources and MCS used for retransmission.
  • NR introduces the concept of pre-configured resources.
  • the downlink is called Semi-Persistent Scheduling (SPS), and the uplink is called CG.
  • SPS Semi-Persistent Scheduling
  • NR supports the transmission of the following two types of uplink configuration authorization:
  • network equipment configures all transmission resources including time domain resources, frequency domain resources, period of time domain resources, Modulation and Coding Scheme (MCS), number of repetitions, frequency hopping and HARQ processes, etc. And transmission parameters.
  • MCS Modulation and Coding Scheme
  • the terminal device can immediately use the configured transmission parameters to perform PUSCH transmission on the configured time-frequency resources.
  • Type 2 adopts a two-step resource configuration method: first, the network equipment configures transmission resources and transmission parameters including the period of time domain resources, the number of repetitions, the number of frequency hopping, and the number of HARQ processes through RRC; then the cell scheduled by the configuration Radio Network Temporary Identifier (Configured Scheduling Radio Network Temporary Identifier, CS-RNTI) scrambled Physical Downlink Control Channel (PDCCH) activates the second type of PUSCH transmission based on configuration authorization, and the configuration includes time domain resources at the same time, Frequency domain resources, other transmission resources and transmission parameters such as MCS.
  • the terminal device receives the RRC configuration parameters, it cannot immediately use the resources and parameters configured by the configuration parameters for PUSCH transmission, but must wait for the corresponding PDCCH to be activated and configure other resources and parameters before PUSCH transmission can be performed.
  • Radio Network Temporary Identifier Configured Scheduling Radio Network Temporary Identifier, CS-RNTI
  • PDCCH Physical Downlink Control Channel
  • network equipment can configure a limited number of HARQ process numbers for it, and terminal equipment can use these HARQ process numbers in a polling manner. Uplink transmission is performed on CG resources.
  • the terminal device groups the MAC protocol data unit (Protocol Data Unit, PDU) 1 and is stored in HARQ ID i Later, at time t1, since the HARQ process used at time t1 is the same as that at time t0, MAC PDU1 will be flushed, even if MAC PDU1 has not been transmitted correctly at this time.
  • PDU Protocol Data Unit
  • NR introduces the configured grant timer configuredGrantTimer for each HARQ process.
  • the maintenance mode of configuredGrantTimer can be:
  • the terminal device can start or restart the configuredGrantTimer corresponding to the HARQ process
  • the terminal device If the terminal device performs uplink transmission on the configured authorized resource, the terminal device starts or restarts the configuredGrantTimer corresponding to the HARQ process;
  • the terminal device If the terminal device receives the PDCCH for indicating the activation of Configured Grant Type 2, the terminal device stops the configured GrantTimer that is running;
  • the MAC PDU stored in the HARQ process cannot be flushed.
  • the terminal device does not need to send HARQ feedback for the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) to the network device.
  • PDSCH Physical Downlink Shared Channel
  • HARQ retransmission is still supported when the HARQ state is off.
  • the network device can perform the configuration of enabling or disabling the HARQ function state based on the terminal device or the HARQ process.
  • the network device can configure the HARQ functions of all the HARQ processes of the terminal device to be on or off at the same time.
  • the network device may configure the HARQ function of some of the HARQ processes to be turned on, and the HARQ function of the other part of the HARQ processes to be turned off.
  • an embodiment of the present application proposes a wireless communication method, which can realize the use of configuredGrantTimer when the HARQ function is supported on or off.
  • FIG. 3 is a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application.
  • the method described in FIG. 3 may be executed by a terminal device and a network device.
  • the terminal device may be, for example, the terminal device 120 shown in FIG. 1
  • the network device may be, for example, the network device 110 shown in FIG. 1.
  • the method 200 may include at least part of the following content.
  • the network device sends configuration information to the terminal device, the configuration information includes at least one HARQ function state of the HARQ process used for transmitting uplink data, and timer information of the configuredGrantTimer used for the at least one HARQ process.
  • the terminal device obtains at least one HARQ function state of the HARQ process used for transmitting uplink data and timer information of the configured GrantTimer used for the at least one HARQ process according to the configuration information.
  • the terminal device determines the configuredGrantTimer of the first HARQ process according to the HARQ function status of the first HARQ process corresponding to the uplink data transmission and the timer information of the configuredGrantTimer, and the at least one HARQ process includes the first HARQ process.
  • the HARQ function state may include an on state or an off state.
  • the embodiments of this application do not limit the names of opening or closing, that is, they can also be expressed as other names.
  • opening can also be expressed as enabling
  • closing can also be expressed as disabling or disabling.
  • the terminal device when the HARQ function is supported on or off, can determine the configuredGrantTimer used for the HARQ process according to the HARQ function status of the HARQ process and the timer information of the configuredGrantTimer, so that the configuredGrantTimer can be effectively implemented. use.
  • the use of the configuredGrantTimer can be limited to the terminal device not being able to send new data during the running of the configuredGrantTimer, so as to reserve time for the scheduling of the original data, thereby further ensuring the scheduling performance.
  • the embodiments of this application can be applied to NTN.
  • the embodiments of the present application can also be applied to communication scenarios other than NTN.
  • the network device may send configuration information to the terminal device through RRC signaling.
  • the configuration information can be used to configure the following information:
  • At least one HARQ process configuration parameter used for uplink data transmission For example, the number of HARQ processes and the HARQ function status of each HARQ process.
  • CG configuration parameters For example, CS-RNTI, the number of uplink HARQ processes reserved for CG, CG resource period, and timer information of configuredGrantTimer, etc.
  • the network device may also configure a CG for each UL BWP of the at least one UL BWP.
  • the timer information of the configuredGrantTimer may include, but is not limited to, the number of configuredGrantTimers and/or the length of each configuredGrantTimer.
  • the number of configuredGrantTimer may be 1 or 2.
  • the network device may configure the HARQ function state of the HARQ process based on the terminal device or the HARQ process.
  • the network device can configure the HARQ function status of all HARQ processes of the terminal device to be in an on or off state at the same time.
  • the network device can configure the HARQ function status of some of the HARQ processes to be in the on state, and the HARQ function state of the other part of the HARQ processes to be off.
  • the network device configures two configuredGrantTimers for the terminal device, namely the first configuredGrantTimer and the second configuredGrantTimer. Wherein, the length of the first configuredGrantTimer is greater than the length of the second configuredGrantTimer.
  • the length of the first configuredGrantTimer and the length of the second configuredGrantTimer may be preset on the terminal device.
  • the length of the first configuredGrantTimer and the length of the second configuredGrantTimer may be stipulated by the agreement.
  • the length of the first configuredGrantTimer and the length of the second configuredGrantTimer may be configured by the network device.
  • the configuration information may include the length of the first configuredGrantTimer and the length of the second configuredGrantTimer.
  • the method 200 may further include: the network device determines the length of the first configuredGrantTimer and the length of the second configuredGrantTimer. Specifically, the network device may determine the length of the first configuredGrantTimer according to the round trip time (RTT) of the signal transmission between the network device and the terminal device and the scheduling delay for the network device to schedule uplink data transmission. The network device may determine the length of the second configuredGrantTimer according to the scheduling delay of scheduling uplink data transmission.
  • RTT round trip time
  • the terminal device may determine the first configuredGrantTimer as the configuredGrantTimer for the first HARQ process (referred to as the target configuredGrantTimer for convenience of description).
  • the terminal device may determine the second configuredGrantTimer as the target configuredGrantTimer.
  • the network device configures different configuredGrantTimer lengths, so that the terminal device can select configuredGrantTimers of different lengths when the HARQ function status of the HARQ process is in different states, for example, when the HARQ function status of the HARQ process is off
  • the terminal device determines the configuredGrantTimer with a shorter length as the target configuredGrantTimer. In this way, the terminal device can use the CG resource to transmit data as soon as possible, thereby improving the data transmission efficiency.
  • the terminal device receives the PDCCH for scheduling uplink data transmission sent by the network device, and the first HARQ process can be used for the uplink transmission of CG, the terminal device can judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start or restart the first configuredGrantTimer
  • the terminal device can start or restart the second configuredGrantTimer.
  • the terminal device may judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start or restart the first configuredGrantTimer
  • the terminal device can start or restart the second configuredGrantTimer.
  • the uplink data transmission here may mean the initial transmission of uplink data or the retransmission of uplink data.
  • the terminal device may start the first configuredGrantTimer.
  • Embodiment 1 The technical solution of Embodiment 1 will be exemplarily described below with reference to FIG. 4.
  • Step 1 The terminal device receives the RRC configuration information sent by the network device, and the RRC configuration information is used to configure the following parameters:
  • DRX Discontinuous Reception
  • HARQ ID 0 Two uplink HARQ processes, namely HARQ ID 0 and HARQ ID 1.
  • the HARQ function state of HARQ ID 0 is in the off state
  • the HARQ function state of HARQ ID 1 is in the on state.
  • the CG configuration includes two configuredGrantTimers, namely configuredGrantTimer1 and configuredGrantTimer2, configuredGrantTimer The length of 1 is 4 CG periods, and the length of configuredGrantTimer 2 is 2 CG periods.
  • the configuredGrantTimer corresponding to HARQ ID 0 is a shorter configuredGrantTimer, that is, configuredGrantTimer2.
  • the configuredGrantTimer used for HARQ ID 0 is configuredGrantTimer 2.
  • the configuredGrantTimer corresponding to HARQ ID 1 is configuredGrantTimer with a longer length, that is, configuredGrantTimer1.
  • the configuredGrantTimer used for HARQ ID1 is configuredGrantTimer1.
  • Step 2 The terminal device performs the initial transmission of TB1 on the CG, and the HARQ process used for TB1 transmission is HARQ ID 0. Since the HARQ function status of HARQ ID 0 is off, the terminal device starts configuredGrantTimer 2 when sending PUSCH 1.
  • PUSCH 1 includes data obtained by performing rate matching on TB1.
  • rate matching may include operations such as encoding, modulation, mapping, and precoding.
  • Step 3 When the terminal device receives the PDCCH used to schedule TB1 retransmission, the terminal device sends PUSCH 1 on the resource indicated by the PDCCH, and restarts the configuredGrantTimer 2.
  • Step 4 After the configuredGrantTimer 2 corresponding to HARQ ID 0 expires, the terminal device performs the initial transmission of TB3 on the CG, and the HARQ process used for transmission of TB3 is HARQ ID 0. The terminal device starts configuredGrantTimer2 when sending PUSCH3.
  • PUSCH 3 includes data obtained by performing rate matching on TB3.
  • Step 5 After the configuredGrantTimer 2 corresponding to HARQ ID 0 expires, the terminal device performs the initial transmission of TB4 on the CG, and the HARQ process used for transmission of TB4 is HARQ ID 0. The terminal device starts the configuredGrantTimer2 when sending PUSCH4.
  • Step 6 The terminal device performs the initial transmission of TB2 on the CG, and the HARQ process used for the transmission of TB2 is HARQ ID 1.
  • the terminal device starts configuredGrantTimer1 when sending PUSCH2.
  • Step 7 After the terminal device receives the PDCCH used to schedule TB2 retransmission, the terminal device sends PUSCH 2 on the resource indicated by the PDCCH, and restarts configuredGrantTimer 1.
  • Step 8 After the configuredGrantTimer 1 corresponding to HARQ ID 1 expires, the terminal device performs the initial transmission of TB5 on the CG, and the HARQ process used for transmission of TB5 is HARQ ID 1. The terminal device starts configuredGrantTimer1 when sending PUSCH5.
  • the network device configures two configuredGrantTimers for the terminal device, namely the first configuredGrantTimer and the second configuredGrantTimer. Wherein, the length of the first configuredGrantTimer is greater than the length of the second configuredGrantTimer.
  • the terminal device may determine the first configuredGrantTimer as the target configuredGrantTimer.
  • the terminal device may determine the second configuredGrantTimer as the target configuredGrantTimer.
  • the terminal device receives the PDCCH sent by the network device for scheduling the initial transmission of uplink data, and the first HARQ process can be used for the uplink transmission of CG, then the terminal device can be based on the first HARQ process HARQ function status judgment:
  • the terminal device can start the first configuredGrantTimer
  • the terminal device can start the second configuredGrantTimer.
  • the terminal device can judge according to the HARQ function status of the first HARQ process:
  • the terminal device can restart the first configuredGrantTimer
  • the terminal device can continue to run the second configuredGrantTimer.
  • the terminal device may not use the second configuredGrantTimer.
  • the terminal device may stop the running of the second configuredGrantTimer.
  • Embodiment 2 The technical solution of Embodiment 2 will be exemplarily described below with reference to FIG. 5.
  • Step 1 The terminal device receives the RRC configuration information sent by the network device, and the RRC configuration information is used to configure the following parameters:
  • DRX related parameters including DRX cycle, drx-onDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerUL, etc.
  • HARQ ID 0 Two uplink HARQ processes, namely HARQ ID 0 and HARQ ID 1.
  • the HARQ function state of HARQ ID 0 is in the off state
  • the HARQ function state of HARQ ID 1 is in the on state.
  • the CG configuration includes two configuredGrantTimers, namely configuredGrantTimer1 and configuredGrantTimer2, configuredGrantTimer The length of 1 is 4 CG periods, and the length of configuredGrantTimer 2 is 2 CG periods.
  • HARQ ID 0 corresponds to configuredGrantTimer 2. Since the HARQ function status of HARQ ID 1 is on, therefore, HARQ ID 1 corresponds to configuredGrantTimer 1.
  • Step 2 The terminal device performs the initial transmission of TB1 on the CG, and the HARQ process used for TB1 transmission is HARQ ID 0. Since the HARQ function status of HARQ ID 0 is off, the terminal device starts configuredGrantTimer 2 when sending PUSCH 1.
  • PUSCH 1 includes data obtained by performing rate matching on TB1.
  • rate matching may include operations such as encoding, modulation, mapping, and precoding.
  • Step 3 The terminal device receives the PDCCH used to schedule TB1 retransmission, then the terminal device sends PUSCH 1 on the resource indicated by the PDCCH, and continues to run the configuredGrantTimer2.
  • Step 4 After the configuredGrantTimer 2 corresponding to HARQ ID 0 expires, the terminal device performs the initial transmission of TB3 on the CG, and the HARQ process used for transmission of TB3 is HARQ ID 0. The terminal device starts configuredGrantTimer2 when sending PUSCH3.
  • Step 5 After the configuredGrantTimer 2 corresponding to HARQ ID 0 expires, the terminal device performs the initial transmission of TB4 on the CG, and the HARQ process used for transmission of TB4 is HARQ ID 0. The terminal device starts the configuredGrantTimer2 when sending PUSCH4.
  • Step 6 After the configuredGrantTimer 2 corresponding to HARQ ID 0 expires, the terminal device performs the initial transmission of TB5 on the CG, and the HARQ process used for transmission of TB5 is HARQ ID 1. The terminal device starts configuredGrantTimer1 when sending PUSCH5.
  • Step 7 The terminal device performs the initial transmission of TB2 on the CG, and the HARQ process used for the transmission of TB2 is HARQ ID 1.
  • the terminal device starts configuredGrantTimer1 when sending PUSCH2.
  • Step 8 After the terminal device receives the PDCCH used to schedule TB2 retransmission, the terminal device sends PUSCH 2 on the resource indicated by the PDCCH, and restarts configuredGrantTimer 1.
  • Step 9 After the configuredGrantTimer 1 corresponding to HARQ ID 1 expires, the terminal device performs the initial transmission of TB6 on the CG, and the HARQ process used for transmission of TB6 is HARQ ID 1. The terminal device starts the configuredGrantTimer 1 when sending PUSCH 6.
  • Embodiment 3 The network device configures a configuredGrantTimer for the terminal device
  • the configuredGrantTimer configured by the network device is called the third configuredGrantTimer.
  • the terminal device can use the third configuredGrantTimer, that is, determine the third configuredGrantTimer as the target configuredGrantTimer. If the HARQ function state of the first HARQ process is in the off state, the terminal device does not use the third configuredGrantTimer.
  • the terminal device may stop the third configuredGrantTimer if the HARQ function state of the first HARQ process is in the off state and the third configuredGrantTimer is running.
  • the terminal device receives the PDCCH for scheduling uplink data transmission sent by the network device, and the first HARQ process can be used for the uplink transmission of CG, the terminal device can judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start or restart the third configuredGrantTimer
  • the terminal device does not start or restart the third configuredGrantTimer.
  • the terminal device may judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start or restart the third configuredGrantTimer
  • the terminal device does not start or restart the third configuredGrantTimer.
  • the terminal device can use the third configuredGrantTimer, that is, determine the third configuredGrantTimer as the target configuredGrantTimer. If the HARQ function state of the first HARQ process is in the off state, the terminal device may determine the third configuredGrantTimer as the target configuredGrantTimer.
  • the terminal device may judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start or restart the third configuredGrantTimer
  • the terminal device does not start or restart the third configuredGrantTimer.
  • the terminal device can judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start the third configuredGrantTimer
  • the terminal device may start the third configuredGrantTimer.
  • the terminal device can judge according to the HARQ function status of the first HARQ process:
  • the terminal device can restart the third configuredGrantTimer
  • the terminal device may not restart the third configuredGrantTimer. That is, the terminal device does not use the third configuredGrantTimer.
  • the terminal device can use the third configuredGrantTimer, that is, determine the third configuredGrantTimer as the target configuredGrantTimer. If the HARQ function state of the first HARQ process is in the off state, the terminal device may determine the third configuredGrantTimer as the target configuredGrantTimer.
  • the terminal device receives the PDCCH for scheduling uplink data transmission sent by the network device, and the first HARQ process can be used for the uplink transmission of CG, the terminal device can judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start or restart the third configuredGrantTimer
  • the terminal device can start or restart the third configuredGrantTimer.
  • the terminal device may judge according to the HARQ function status of the first HARQ process:
  • the terminal device can start or restart the third configuredGrantTimer
  • the terminal device can start or restart the third configuredGrantTimer.
  • Embodiment 3 The technical solution of Embodiment 3 will be exemplarily described below with reference to FIG. 6.
  • Step 1 The terminal device receives the RRC configuration information sent by the network device, and the RRC configuration information is used to configure the following parameters:
  • DRX related parameters including DRX cycle, drx-onDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerUL, etc.
  • HARQ ID 0 Two uplink HARQ processes, namely HARQ ID 0 and HARQ ID 1.
  • the HARQ function state of HARQ ID 0 is in the off state
  • the HARQ function state of HARQ ID 1 is in the on state.
  • a UL BWP configured for the serving cell of the terminal device and a CG configured for the UL BWP.
  • the CG uses HARQ ID0 and HARQ ID 1.
  • the CG configuration includes 1 configuredGrantTimer, respectively configuredGrantTimer3, the length of the configuredGrantTimer3 is 4 CG cycles.
  • Step 2 The terminal device performs the initial transmission of TB1 on the CG, and the HARQ process used for TB1 transmission is HARQ ID 0. Since the HARQ function status of HARQ ID 0 is off, the terminal device does not start configuredGrantTimer 3 when sending PUSCH 1.
  • Step 3 When the terminal device receives the PDCCH used to schedule TB1 retransmission, the terminal device sends PUSCH 1 on the resource indicated by the PDCCH.
  • Step 4 The terminal device performs the initial transmission of TB3, TB4, and TB5 in sequence on the CG, and the ARQ process used for transmission of TB3, TB4, and TB5 is all HARQ ID 0. Since the HARQ function status of HARQ ID 0 is off, the terminal device does not start configuredGrantTimer 3 when sending PUSCH 3, PUSCH 4, and PUSCH 5.
  • Step 5 The terminal device performs the initial transmission of TB2 on the CG, and the HARQ process used for the transmission of TB2 is HARQ ID 1.
  • the terminal device starts configuredGrantTimer3 when sending PUSCH2.
  • Step 6 After the terminal device receives the PDCCH used to schedule TB2 retransmission, the terminal device sends PUSCH 2 on the resource indicated by the PDCCH, and restarts the configuredGrantTimer 3.
  • Step 7 After the configuredGrantTimer 3 corresponding to HARQ ID 1 expires, the terminal device performs the initial transmission of TB6 on the CG, and the HARQ process used for transmission of TB6 is HARQ ID 1.
  • the terminal device starts configuredGrantTimer3 when sending PUSCH6.
  • Embodiment 1 to Embodiment 3 are described above separately, this does not mean that Embodiment 1 to Embodiment 3 are independent, and the description of each embodiment may refer to each other. For example, the related description in Embodiment 1 can be applied to Embodiment 2.
  • the size of the sequence number 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 be implemented in this application.
  • the implementation process of the example constitutes any limitation.
  • the communication method according to the embodiment of the present application is described in detail above.
  • the communication device according to the embodiment of the present application will be described below in conjunction with FIG. 7 to FIG. 9.
  • the technical features described in the method embodiment are applicable to the following device embodiments.
  • FIG. 7 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application.
  • the terminal device 300 includes:
  • the processing unit 310 is configured to obtain, according to the configuration information sent by the network device, the HARQ function status of at least one HARQ process used for uplink data transmission, and obtain the timer information of the configuration grant timer used for the at least one HARQ process .
  • the processing unit 310 is further configured to determine a configuration grant timer for the first HARQ process according to the HARQ function status of the first HARQ process corresponding to uplink data transmission and the timer information of the configuration grant timer,
  • the at least one HARQ process includes the first HARQ process.
  • the timer information of the configuration authorization timer includes the number of configuration authorization timers and/or the length of each configuration authorization timer.
  • the processing unit 310 is specifically configured to: if the number of configured authorization timers is 2 and the HARQ function status of the first HARQ process is in the on state, the first configuration is authorized The timer is determined to be the configured authorization timer for the first HARQ process; if the number of configured authorization timers is 2 and the HARQ function status of the first HARQ process is off, set the second configuration authorization timer Determined as a configuration grant timer for the first HARQ process; wherein the length of the first configuration grant timer is greater than the length of the second configuration grant timer.
  • the terminal device 300 further includes: a communication unit 320, configured to receive a physical downlink control channel PDCCH sent by the network device for scheduling initial transmission or retransmission of uplink data, and The first HARQ process can be used to configure authorized uplink transmission.
  • a communication unit 320 configured to receive a physical downlink control channel PDCCH sent by the network device for scheduling initial transmission or retransmission of uplink data, and The first HARQ process can be used to configure authorized uplink transmission.
  • the processing unit 310 is further configured to: if the HARQ function state of the first HARQ process is in the on state, start or restart the first configuration grant timer; if the HARQ function state of the first HARQ process is in the off state , Start or restart the second configuration authorization timer.
  • the uplink data transmission is uplink data retransmission
  • the terminal device 300 further includes: a communication unit 320, configured to receive the uplink data sent by the network device for scheduling the uplink data PDCCH retransmitted, and the first HARQ process can be used to configure authorized uplink transmission;
  • the processing unit 310 is further configured to: if the HARQ function status of the first HARQ process is off and the second configuration authorization timer is running, continue to run the second configuration authorization timer.
  • the processing unit 310 is further configured to: when the terminal device performs the uplink data transmission on the configuration authorization, if the HARQ function status of the first HARQ process is on Status, start or restart the first configuration authorization timer; if the HARQ function status of the first HARQ process is off, start or restart the second configuration authorization timer.
  • the length of the first configuration grant timer is based on the round-trip transmission time RTT of the signal transmission between the terminal device and the network device and the network device scheduling the uplink The scheduling delay of data transmission is determined.
  • the length of the second configuration grant timer is determined according to the scheduling delay for the network device to schedule the uplink data transmission.
  • the processing unit 310 is specifically configured to: if the number of configured authorization timers is 1, and the HARQ function status of the first HARQ process is in the on state, the The third configuration authorization timer configured by the network device is determined to be the configuration authorization timer used for the first HARQ process.
  • the terminal device 300 further includes: a communication unit 320, configured to receive a PDCCH used to schedule the uplink data transmission, and the first HARQ process can be used to configure the authorized uplink transmission;
  • the processing unit 310 is further configured to: start or restart the third configuration authorization timer.
  • the processing unit 310 is further configured to: when the terminal device performs uplink data transmission on the configuration authorization, start or restart the third configuration authorization timer.
  • the processing unit 310 is specifically configured to: if the number of the configured authorization timer is 1, and the HARQ function status of the first HARQ process is off, the The third configuration authorization timer configured by the network device is determined to be the configuration authorization timer used for the first HARQ process.
  • the uplink data transmission is the initial transmission of uplink data
  • the terminal device 300 further includes: a communication unit 320 configured to receive a PDCCH for scheduling the initial transmission of the uplink data, and The first HARQ process can be used to configure authorized uplink transmission;
  • the processing unit 310 is further configured to: start the third configuration authorization timer.
  • the length of the third configuration grant timer is based on the round-trip transmission time RTT of the signal transmission between the terminal device and the network device and the network device scheduling the uplink The scheduling delay of data transmission is determined.
  • the terminal device 300 further includes: a communication unit 320, configured to receive the configuration information sent by the network device through radio resource control RRC signaling.
  • the configuration information is used to configure the following parameters: the at least one configuration parameter used for the HARQ process when uplink data is transmitted, wherein the configuration parameter of the HARQ process includes the HARQ function status of the HARQ process; configuration authorization configuration parameters, wherein the configuration authorization configuration parameters include timer information of the configuration authorization timer of the at least one HARQ process; at least An upstream bandwidth part BWP.
  • terminal device 300 may correspond to the terminal device in the method 200, and can implement the corresponding operations of the terminal device in the method 200. For the sake of brevity, details are not described herein again.
  • FIG. 8 shows a schematic block diagram of a network device 400 according to an embodiment of the present application.
  • the network device 400 includes:
  • the communication unit 410 is configured to send configuration information to the terminal device, the configuration information including at least one HARQ function state of the HARQ process used for transmitting uplink data, and the timing of the configuration grant timer for the at least one HARQ process ⁇ Information.
  • the timer information of the configuration authorization timer includes the number of configuration authorization timers and/or the length of each configuration authorization timer.
  • the number of configuration authorization timers is 2, and the configuration authorization timer includes a first configuration authorization timer and a second configuration authorization timer, and the first configuration authorization timer The length of the device is greater than the length of the second configuration authorization timer.
  • the network device 400 further includes: a processing unit 420, configured to schedule the uplink data according to the round-trip transmission time RTT of the signal transmission with the terminal device and the network device
  • the transmission scheduling delay determines the length of the first configuration grant timer.
  • the network device 400 further includes a processing unit 420, configured to determine the length of the second configuration grant timer according to the scheduling delay for scheduling the uplink data transmission.
  • the number of configuration authorization timers is 1, and the configuration authorization timer is a third configuration authorization timer.
  • the network device 400 further includes: a processing unit 420, configured to schedule the uplink data transmission according to the RTT of the signal transmission with the terminal device and the network device Time delay, determining the length of the third configuration authorization timer.
  • a processing unit 420 configured to schedule the uplink data transmission according to the RTT of the signal transmission with the terminal device and the network device Time delay, determining the length of the third configuration authorization timer.
  • the communication unit 410 is specifically configured to send the configuration information to the terminal device through radio resource control RRC signaling.
  • the network device 400 may correspond to the network device in the method 200, and can implement the corresponding operations of the network device in the method 200. For the sake of brevity, details are not described herein again.
  • FIG. 9 is a schematic structural diagram of a communication device 500 provided by an embodiment of the present application.
  • the communication device 500 shown in FIG. 9 includes a processor 510, and the processor 510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the communication device 500 may further include a memory 520.
  • the processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
  • the memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.
  • the communication device 500 may further include a transceiver 530, and the processor 5710 may control the transceiver 530 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 530 may include a transmitter and a receiver.
  • the transceiver 530 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 500 may specifically be a network device of an embodiment of the present application, and the communication device 500 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here. .
  • the communication device 500 may specifically be a terminal device of an embodiment of the application, and the communication device 500 may implement the corresponding process implemented by the terminal device in each method of the embodiment of the application. For brevity, details are not repeated here. .
  • Fig. 10 is a schematic structural diagram of a device according to an embodiment of the present application.
  • the apparatus 600 shown in FIG. 10 includes a processor 610, and the processor 610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the apparatus 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 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.
  • the device 600 may further include an input interface 630.
  • the processor 610 can control the input interface 630 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the device 600 may further include an output interface 640.
  • the processor 610 can control the output interface 640 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the device can be applied to the terminal device in the embodiment of the present application, and the device can implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the device can implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application.
  • the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application.
  • details are not described herein again.
  • the device 600 may be a chip. It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment 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 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 to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the sake of brevity it is not here. Go into details again.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

Les modes de réalisation de la présente invention concernent un procédé de communication sans fil, un dispositif terminal et un dispositif de réseau. Le procédé comprend les étapes au cours desquelles : sur la base d'informations de configuration envoyées par un dispositif de réseau, un dispositif terminal acquiert l'état d'une fonction HARQ de demande de répétition automatique hybride d'au moins un processus HARQ utilisé lors d'une transmission de données de liaison montante et acquiert des informations d'un temporisateur d'autorisation configuré utilisé pour ledit au moins un processus HARQ, l'état de la fonction HARQ comprenant un état activé ou un état désactivé ; et, sur la base de l'état de la fonction HARQ d'un premier processus HARQ correspondant à la transmission de données de liaison montante et des informations du temporisateur d'autorisation configuré, le dispositif terminal détermine un temporisateur d'autorisation configuré utilisé pour le premier processus HARQ, ledit au moins un processus HARQ comprenant le premier processus HARQ. Le procédé de communication sans fil, le dispositif terminal et le dispositif de réseau d'après les modes de réalisation de la présente invention peuvent utiliser efficacement le temporisateur d'autorisation configuré tout en prenant en charge la condition d'activation ou de désactivation de la fonction HARQ, ce qui garantit en outre des performances de planification.
PCT/CN2019/110723 2019-10-12 2019-10-12 Procédé de communication sans fil, dispositif terminal et dispositif de réseau WO2021068224A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/110723 WO2021068224A1 (fr) 2019-10-12 2019-10-12 Procédé de communication sans fil, dispositif terminal et dispositif de réseau
CN201980099518.6A CN114258722A (zh) 2019-10-12 2019-10-12 无线通信方法、终端设备和网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/110723 WO2021068224A1 (fr) 2019-10-12 2019-10-12 Procédé de communication sans fil, dispositif terminal et dispositif de réseau

Publications (1)

Publication Number Publication Date
WO2021068224A1 true WO2021068224A1 (fr) 2021-04-15

Family

ID=75437615

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/110723 WO2021068224A1 (fr) 2019-10-12 2019-10-12 Procédé de communication sans fil, dispositif terminal et dispositif de réseau

Country Status (2)

Country Link
CN (1) CN114258722A (fr)
WO (1) WO2021068224A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117676617A (zh) * 2022-08-10 2024-03-08 华为技术有限公司 通信方法、装置以及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108270527A (zh) * 2017-01-04 2018-07-10 电信科学技术研究院 一种混合自动重传请求harq传输方法及相关设备
CN110022608A (zh) * 2018-01-09 2019-07-16 电信科学技术研究院 一种信息处理方法、装置及设备
CN110035502A (zh) * 2018-01-11 2019-07-19 华为技术有限公司 通信方法、通信设备和网络设备
US20190260518A1 (en) * 2016-11-04 2019-08-22 Huawei Technologies Co., Ltd. Information transmission method, network device, and terminal device

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5866420B1 (ja) * 2014-09-25 2016-02-17 株式会社Ｎｔｔドコモ ユーザ装置、基地局、及び上り送信電力報告方法
EP3499767A4 (fr) * 2016-08-10 2019-08-28 Huawei Technologies Co., Ltd. Procédé de requête automatique de répétition hybride, et dispositif terminal
DK3711220T3 (da) * 2017-11-16 2022-05-30 Ericsson Telefon Ab L M Datatransmission og gentransmission til semi-persistent planlægning
WO2019127138A1 (fr) * 2017-12-27 2019-07-04 Oppo广东移动通信有限公司 Procédé de gestion de temporisateur et dispositif terminal
CN110278616B (zh) * 2018-03-13 2021-04-06 华硕电脑股份有限公司 无线通信系统中随机接入过程期间处置传送的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190260518A1 (en) * 2016-11-04 2019-08-22 Huawei Technologies Co., Ltd. Information transmission method, network device, and terminal device
CN108270527A (zh) * 2017-01-04 2018-07-10 电信科学技术研究院 一种混合自动重传请求harq传输方法及相关设备
CN110022608A (zh) * 2018-01-09 2019-07-16 电信科学技术研究院 一种信息处理方法、装置及设备
CN110035502A (zh) * 2018-01-11 2019-07-19 华为技术有限公司 通信方法、通信设备和网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Configured scheduling for NTN", 3GPP DRAFT; R2-1907299 CONFIGURED SCHEDULING FOR NTN, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, Nevada, US; 20190513 - 20190517, 2 May 2019 (2019-05-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051711584 *

Also Published As

Publication number Publication date
CN114258722A (zh) 2022-03-29

Similar Documents

Publication Publication Date Title
WO2021031089A1 (fr) Procédé de configuration de ressource, dispositif terminal et dispositif réseau
US20220232596A1 (en) Discontinuous reception method, terminal device and storage medium
WO2021081908A1 (fr) Procédé d'attribution de ressources à un canal logique de liaison montante, et dispositif terminal
WO2021056226A1 (fr) Procédé de communication sans fil et dispositif terminal
WO2020252708A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
US20230224091A1 (en) Wireless communication method and device
US20230015847A1 (en) Method for releasing uplink resource, terminal device, and network device
WO2021184266A1 (fr) Procédé de réassemblage de paquet de données, dispositif électronique et support de stockage
US20230199799A1 (en) Wireless communication method, terminal device and network device
WO2021128318A1 (fr) Procédé et appareil de transmission de mac ce de liaison montante
WO2021022567A1 (fr) Procédé de transmission de données et dispositif de terminal
CN114731238B (zh) 配置授权定时器的使用方法与装置、终端设备和网络设备
CN113330762B (zh) 无线通信的方法及设备
CN116134906A (zh) 一种随机接入方法、电子设备及存储介质
WO2021068224A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2021184317A1 (fr) Procédé de détermination de temps utile, terminal et dispositif réseau
CN116192337A (zh) 无线通信的方法及装置
WO2021227030A1 (fr) Procédé de traitement de réception discontinue, dispositif électronique et support de stockage
WO2022120747A1 (fr) Procédé de communication sans fil et dispositif terminal
WO2022082353A1 (fr) Procédé et appareil de démarrage de temporisateur de retransmission de réception discontinue, dispositif et support
WO2022077174A1 (fr) Dispositif et procédé de communication sans fil
WO2022006724A1 (fr) Procédé de traitement destiné à être utilisé pour désactiver une retransmission harq, équipement terminal et dispositif de réseau
WO2021026847A1 (fr) Procédé et dispositif de communication sans fil
WO2021155597A1 (fr) Procédé de commande de temporisateur, dispositif terminal et dispositif de réseau
WO2022099514A1 (fr) Procédé et dispositif de communication sans fil

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: 19948642

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: 19948642

Country of ref document: EP

Kind code of ref document: A1