WO2021068224A1

WO2021068224A1 - Wireless communication method, terminal device, and network device

Info

Publication number: WO2021068224A1
Application number: PCT/CN2019/110723
Authority: WO
Inventors: 卢前溪
Original assignee: Oppo广东移动通信有限公司; Oppo广东移动通信有限公司深圳分公司
Priority date: 2019-10-12
Filing date: 2019-10-12
Publication date: 2021-04-15
Also published as: CN114258722A

Abstract

The embodiments of the present application relate to a wireless communication method, a terminal device, and a network device, the method comprising: on the basis of configuration information sent by a network device, a terminal device acquires the hybrid automatic repeat request HARQ function state of at least one HARQ process used when transmitting uplink data and acquires timer information of a configured grant timer used for the at least one HARQ process, the HARQ function state comprising an on state or an off state; and, on the basis of the HARQ function state of a first HARQ process corresponding to the uplink data transmission and the timer information of the configured grant timer, the terminal device determines a configured grant timer used for the first HARQ process, the at least one HARQ process comprising the first HARQ process. The wireless communication method, the terminal device, and the network device of the embodiments of the present application can effectively implement usage of the configured grant timer whilst supporting the on or off condition of the HARQ function, further ensuring scheduling performance.

Description

Wireless communication method, terminal equipment and network equipment

Technical field

This application relates to the field of communications, in particular to a wireless communication method, terminal equipment and network equipment.

Background technique

In order to alleviate the problem of transmission delay, the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) introduced the concept of Configured Grant (CG). For each CG resource, 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. In this case, there may be a problem that the data at a certain time has not been transmitted correctly, but the data is deleted (flush) at the same time as the process number at that time. In order to solve this problem, 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.

Due to the transmission delay between the terminal device and the network device, in order to ensure the continuity of data transmission without increasing the number of HARQ processes, a solution to enable or disable the HARQ function is proposed.

Therefore, there is no clear regulation on how to use configuredGrantTimer when the HARQ function is turned on or off. Summary of the invention

The embodiments of the present application provide a wireless communication method, terminal equipment, and network equipment. When 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.

In a first aspect, a wireless communication method is provided, the 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.

In a second aspect, a wireless communication method is provided, the 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.

In a third aspect, a terminal device is provided, which is used to execute the method in the above-mentioned first aspect or its implementation manners.

Specifically, the terminal device includes a functional module for executing the method in the foregoing first aspect or each of its implementation manners.

In a fourth aspect, a network device is provided, which is used to execute the method in the above second aspect or each of its implementation manners.

Specifically, the network device includes a functional module for executing the method in the above-mentioned second aspect or each of its implementation manners.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation manners.

In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each implementation manner thereof.

In a seventh aspect, a device is provided for implementing any one of the above-mentioned first aspect to the second aspect or the method in each of its implementation manners.

Specifically, 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.

Optionally, the device is a chip.

In an eighth aspect, a computer-readable storage medium is provided 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.

In a ninth aspect, a computer program product is provided, 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.

In a tenth aspect, a computer program is provided, 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.

In the above technical solution, when the HARQ function is turned on or off, the terminal device 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. In addition, 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.

Description of the drawings

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.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE ( LTE-based access to unlicensed spectrum, LTE-U system, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, Universal Mobile Telecommunication System (UMTS), global interconnection Microwave access (Worldwide Interoperability for Microwave Access, WiMAX) communication systems, wireless local area networks (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, WiFi), next-generation communication systems or other communication systems, etc.

Exemplarily, 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. Optionally, 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.

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. 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". Examples of 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. 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.

Optionally, direct terminal connection (Device to Device, D2D) communication may be performed between the terminal devices 120.

Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

Figure 1 exemplarily shows one network device and two terminal devices. Optionally, 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.

Optionally, 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.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, 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.

It should also be understood that 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.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article.

In order to facilitate the understanding of the embodiments of the present application, a few terms will be introduced below.

1. Non-Terrestrial Communication Network (Non-Terrestrial Network, NTN)

NTN technology generally uses satellite communication to provide communication services to ground users. Compared with terrestrial cellular network communication, satellite communication has many unique advantages. First of all, satellite communication is not restricted by the user's area. For example, 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. As for 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. Secondly, 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. Third, the satellite communication distance is long, and the communication distance increases and the cost of communication does not increase significantly. Finally, the stability of satellite communication is high, and it is not restricted by natural disasters.

According to different orbital heights, 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.

For example, 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.

For another example, 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.

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.

2. HARQ mechanism

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 . Among them, 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. In 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.

Based on the current NR protocol, 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. Currently, the maximum number of HARQ processes that can be supported by each uplink and downlink carrier is 16. 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. Each HARQ process can correspond to a HARQ process ID. For the downlink, the Broadcast Control Channel (BCCH) can use a dedicated broadcast HARQ process. For the uplink, HARQ ID 0 is used for message 3 (Msg3) transmission in the random process.

For terminals that do not support downlink space division multiplexing, 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.

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.

3. CG

In order to better serve periodic services, NR introduces the concept of pre-configured resources. Among them, the downlink is called Semi-Persistent Scheduling (SPS), and the uplink is called CG.

Currently, NR supports the transmission of the following two types of uplink configuration authorization:

(a) Physical Uplink Control Channel (PUSCH) transmission based on the first type of configuration grant (Configured Grant Type 1)

Through RRC signaling, 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. After receiving the RRC configuration, the terminal device can immediately use the configured transmission parameters to perform PUSCH transmission on the configured time-frequency resources.

(b) PUSCH transmission based on the second type of configuration grant (Configured Grant Type 2)

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. When 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.

Since the maximum number of HARQ processes for terminal equipment is 16, for each CG resource, 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. Assuming that the HARQ process number of the CG resource at time t0 and the HARQ process number of the CG resource at time t1 are both HARQ ID i, at time t0 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.

In order to ensure the correct transmission of data, NR introduces the configured grant timer configuredGrantTimer for each HARQ process. Among them, the maintenance mode of configuredGrantTimer can be:

If the terminal device performs uplink transmission on the resources scheduled by the PDCCH, and the HARQ process used for the uplink transmission can be used to configure authorized transmission, the terminal device can start or restart the configuredGrantTimer corresponding to the HARQ process;

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;

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;

Before the configuredGrantTimer corresponding to a certain HARQ process times out, the MAC PDU stored in the HARQ process cannot be flushed.

Compared with the cellular network used in traditional NR, the signal propagation delay between the terminal equipment and the satellite in NTN has increased significantly. In order to ensure the continuity of data transmission without increasing the number of HARQ processes, it is proposed to enable or disable the HARQ function. Program.

If the HARQ function state is in the off state, 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. In addition, in order to ensure the reliability of data transmission, HARQ retransmission is still supported when the HARQ state is off.

Take the case of PDCCH scheduling PDSCH as an example to illustrate the HARQ function status of the HARQ process. When the HARQ function status of the HARQ process is off, the terminal device does not feed back an Acknowledgment (ACK)/Negative Acknowledgement (NACK) to the network device after demodulating the PDSCH, as shown in HARQ process 1 and HARQ in Figure 2. As shown in process 2. When the HARQ function status of the HARQ process is in the on state, the terminal device needs to feed back ACK/NACK to the network device after demodulating the PDSCH, as shown in the HARQ process x in FIG. 2.

The network device can perform the configuration of enabling or disabling the HARQ function state based on the terminal device or the HARQ process. For the configuration based on the terminal device, 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. For the HARQ process-based configuration method, for multiple HARQ processes of a terminal device, 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.

However, there is no clear regulation on how to use configuredGrantTimer when the HARQ function is enabled or disabled. In view of this, 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, and the network device may be, for example, the network device 110 shown in FIG. 1. As shown in FIG. 2, the method 200 may include at least part of the following content.

In 210, 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.

In 220, 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.

In 230, 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.

Among them, 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. For example, opening can also be expressed as enabling, and closing can also be expressed as disabling or disabling.

In the embodiment of the present application, when the HARQ function is supported on or off, the terminal device 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. In addition, 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.

Optionally, the embodiments of this application can be applied to NTN. Of course, the embodiments of the present application can also be applied to communication scenarios other than NTN. Such as ground cellular network communication, car networking communication, etc.

Optionally, the network device may send configuration information to the terminal device through RRC signaling. Among them, the configuration information can be used to configure the following information:

a) 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.

b) 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.

c) At least one uplink (Uplink, UL) bandwidth part (BandWidth Part, BWP) of each serving cell of the terminal device. Optionally, the network device may also configure a CG for each UL BWP of the at least one UL BWP.

Optionally, the timer information of the configuredGrantTimer may include, but is not limited to, the number of configuredGrantTimers and/or the length of each configuredGrantTimer. Exemplarily, the number of configuredGrantTimer may be 1 or 2.

It should be understood that the term "and/or" in this text is only an association relationship describing the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, and both A and B exist. , There are three cases of B alone.

Optionally, in the embodiment of the present application, the network device may configure the HARQ function state of the HARQ process based on the terminal device or the HARQ process. Specifically, for the terminal device-based configuration method, 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. For the HARQ process-based configuration method, that is, for multiple HARQ processes of a terminal device, 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.

Hereinafter, the technical solutions of the embodiments of the present application will be described in detail with reference to three embodiments.

Example 1

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.

As an example, the length of the first configuredGrantTimer and the length of the second configuredGrantTimer may be preset on the terminal device. For example, the length of the first configuredGrantTimer and the length of the second configuredGrantTimer may be stipulated by the agreement.

As another example, the length of the first configuredGrantTimer and the length of the second configuredGrantTimer may be configured by the network device. For example, the configuration information may include the length of the first configuredGrantTimer and the length of the second configuredGrantTimer.

At this time, 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.

If the HARQ function state of the first HARQ process is in the on state, 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).

If the HARQ function state of the first HARQ process is in the off state, the terminal device may determine the second configuredGrantTimer as the target configuredGrantTimer.

In the above technical solution, 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 In this case, 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.

Further, 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:

a) If the HARQ function status of the first HARQ process is on, the terminal device can start or restart the first configuredGrantTimer;

b) If the HARQ function status of the first HARQ process is off, the terminal device can start or restart the second configuredGrantTimer.

Or, when the terminal device performs uplink data transmission on the configuration authorization, the terminal device may judge according to the HARQ function status of the first HARQ process:

It should be understood that the uplink data transmission here may mean the initial transmission of uplink data or the retransmission of uplink data. For example, if the terminal device processes the initial transmission of uplink data on the configuration grant, and the HARQ function status of the first HARQ process is in the on state, the terminal device may start the first configuredGrantTimer.

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:

a) Discontinuous Reception (DRX) related parameters, including DRX cycle, drx-onDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerUL, etc.

b) Two uplink HARQ processes, namely HARQ ID 0 and HARQ ID 1. Among them, the HARQ function state of HARQ ID 0 is in the off state, and the HARQ function state of HARQ ID 1 is in the on state.

c) A UL BWP configured for the serving cell of the terminal device and a CG configured for the UL BWP. The CG uses HARQ ID 0 and HARQ ID 1. At the same time, 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.

It can be seen that since the HARQ function status of HARQ ID 0 is off, the configuredGrantTimer corresponding to HARQ ID 0 is a shorter configuredGrantTimer, that is, configuredGrantTimer2. In other words, the configuredGrantTimer used for HARQ ID 0 is configuredGrantTimer 2.

Since the HARQ function status of HARQ ID 1 is on, the configuredGrantTimer corresponding to HARQ ID 1 is configuredGrantTimer with a longer length, that is, configuredGrantTimer1. In other words, 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.

Among them, PUSCH 1 includes data obtained by performing rate matching on TB1. Exemplarily, 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.

Similar to TB 1, 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.

Example 2

If the HARQ function state of the first HARQ process is in the on state, the terminal device may determine the first configuredGrantTimer as the target configuredGrantTimer.

Further, in an implementation manner, 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:

a) If the HARQ function status of the first HARQ process is on, the terminal device can start the first configuredGrantTimer;

b) If the HARQ function status of the first HARQ process is off, the terminal device can start the second configuredGrantTimer.

If the terminal device receives the PDCCH for scheduling uplink data retransmission 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:

a) If the HARQ function status of the first HARQ process is on, the terminal device can restart the first configuredGrantTimer;

b) If the HARQ function status of the first HARQ process is off, and the second configuredGrantTimer corresponding to the first HARQ process is running, the terminal device can continue to run the second configuredGrantTimer.

Or, if the HARQ function state of the first HARQ process is in the off state, the terminal device may not use the second configuredGrantTimer. Exemplarily, if the second configuredGrantTimer is running, the terminal device may stop the running of the second configuredGrantTimer.

The technical solution of Embodiment 2 will be exemplarily described below with reference to FIG. 5.

a) DRX related parameters, including DRX cycle, drx-onDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerUL, etc.

It can be seen that since the HARQ function status of HARQ ID 0 is off, therefore, 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 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 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

For the convenience of description, the configuredGrantTimer configured by the network device is called the third configuredGrantTimer.

In an implementation manner, if the HARQ function state of the first HARQ process is in the on state, 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.

Further, if the HARQ function state of the first HARQ process is in the off state and the third configuredGrantTimer is running, the terminal device may stop the third configuredGrantTimer.

a) If the HARQ function status of the first HARQ process is on, the terminal device can start or restart the third configuredGrantTimer;

b) If the HARQ function state of the first HARQ process is in the off state, the terminal device does not start or restart the third configuredGrantTimer.

In another implementation manner, if the HARQ function state of the first HARQ process is in the on state, 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.

Further, when the terminal device performs uplink data transmission on the configuration authorization, the terminal device may judge according to the HARQ function status of the first HARQ process:

Or, if the terminal device receives the PDCCH for scheduling the initial transmission of uplink data 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:

a) If the HARQ function status of the first HARQ process is on, the terminal device can start the third configuredGrantTimer;

b) If the HARQ function state of the first HARQ process is in the off state, the terminal device may start the third configuredGrantTimer.

a) If the HARQ function status of the first HARQ process is on, the terminal device can restart the third configuredGrantTimer;

b) If the HARQ function status of the first HARQ process is off, the terminal device may not restart the third configuredGrantTimer. That is, the terminal device does not use the third configuredGrantTimer.

b) If the HARQ function state of the first HARQ process is in the off state, the terminal device can start or restart the third configuredGrantTimer.

The technical solution of Embodiment 3 will be exemplarily described below with reference to FIG. 6.

c) 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. At the same time, 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.

It should be understood that in the embodiments of the present application, "first", "second" and "third" are only used to distinguish different objects, but do not limit the scope of the embodiments of the present application.

It should also be understood that although 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 preferred embodiments of the present application are described in detail above with reference to the accompanying drawings. However, the present application is not limited to the specific details in the above-mentioned embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application. These simple variants all belong to the protection scope of this application.

For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, various possible combinations are not described in this application. Explain separately.

For another example, various different implementations of this application can also be combined arbitrarily, as long as they do not violate the idea of this application, they should also be regarded as the content disclosed in this application.

It should be understood that in the various method embodiments of the present application, 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. As shown in FIG. 7, 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.

Optionally, in this embodiment of the present application, the timer information of the configuration authorization timer includes the number of configuration authorization timers and/or the length of each configuration authorization timer.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

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.

Optionally, in this embodiment of the present application, the uplink data transmission is uplink data retransmission, and 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in the embodiment of the present application, the uplink data transmission is the initial transmission of uplink data, and 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in this embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

It should be understood that the 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. As shown in FIG. 8, 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.

Optionally, in this embodiment of the present application, 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.

Optionally, in the embodiment of the present application, 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.

Optionally, in this embodiment of the present application, 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.

Optionally, in this embodiment of the present application, the number of configuration authorization timers is 1, and the configuration authorization timer is a third configuration authorization timer.

Optionally, in this embodiment of the application, 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.

Optionally, in the embodiment of the present application, the communication unit 410 is specifically configured to send the configuration information to the terminal device through radio resource control RRC signaling.

It should be understood that 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.

Optionally, as shown in FIG. 9, 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.

Optionally, as shown in FIG. 9, 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.

Wherein, 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.

Optionally, 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. .

Optionally, 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.

Optionally, as shown in FIG. 10, 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.

Optionally, 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.

Optionally, 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.

Optionally, 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. For brevity, details are not described herein again.

Optionally, 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. For the sake of brevity, details are not described herein again.

Optionally, 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.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, 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. 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.

It can be understood that 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. Among them, 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. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, 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.

Optionally, 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. For the sake of brevity, here No longer.

Optionally, 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. For the sake of brevity, here No longer.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, 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. For the sake of brevity, it is not here. Go into details again.

Optionally, 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. For the sake of brevity, it is not here Repeat it again.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the terminal device in the embodiment of the present application. When 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. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When 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. For the sake of brevity , I won’t repeat it here.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

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

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, 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. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, 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.

In addition, 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.

If 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. Based on this understanding, 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. .

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

Claims

A wireless communication method, characterized in that the method includes:

According to the configuration information sent by the network device, the terminal device obtains at least one HARQ function state of the HARQ process for the hybrid automatic repeat request HARQ process when transmitting uplink data, and obtains the timer for the configuration authorization timer of the at least one HARQ process information;

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.
The method according to claim 1, wherein 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 method according to claim 2, wherein the terminal device determines to be used 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 configured authorization timer. The configuration authorization timer of the HARQ process includes:

If the number of configuration authorization timers is 2 and the HARQ function status of the first HARQ process is in the on state, the terminal device determines the first configuration authorization timer as the configuration authorization timing for the first HARQ process Device

If the number of configuration authorization timers is 2, and the HARQ function status of the first HARQ process is off, the terminal device determines the second configuration authorization timer as the configuration authorization timing for the first HARQ process Device

Wherein, the length of the first configuration authorization timer is greater than the length of the second configuration authorization timer.
The method according to claim 3, wherein the method further comprises:

The terminal device receives the 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;

If the HARQ function status of the first HARQ process is in the on state, the terminal device starts or restarts the first configuration authorization timer;

If the HARQ function state of the first HARQ process is in the off state, the terminal device starts or restarts the second configuration authorization timer.
The method according to claim 3, wherein the uplink data transmission is uplink data retransmission, and the method further comprises:

The terminal device receives the PDCCH used to schedule the uplink data retransmission sent by the network device, and the first HARQ process can be used to configure authorized uplink transmission;

If the HARQ function status of the first HARQ process is off and the second configuration authorization timer is running, the terminal device continues to run the second configuration authorization timer.
The method according to claim 3, wherein the method further comprises:

When the terminal device performs the uplink data transmission on the configuration authorization, if the HARQ function status of the first HARQ process is in the on state, the terminal device starts or restarts the first configuration authorization timer;

If the HARQ function state of the first HARQ process is in the off state, the terminal device starts or restarts the second configuration authorization timer.
The method according to any one of claims 3 to 6, wherein the length of the first configuration authorization timer is based on the round-trip transmission time (RTT) of the signal transmission between the terminal device and the network device and The scheduling delay for the network equipment to schedule the uplink data transmission is determined.
The method according to any one of claims 3 to 7, wherein 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 method according to claim 2, wherein the terminal device determines to be used 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 configured authorization timer. The configuration authorization timer of the HARQ process includes:

If the number of the configuration authorization timer is 1, and the HARQ function status of the first HARQ process is in the on state, the terminal device determines that the third configuration authorization timer configured by the network device is used for the Configure the authorization timer for the first HARQ process.
The method according to claim 9, wherein the method further comprises:

The terminal device receives the PDCCH used to schedule the uplink data transmission, and the first HARQ process can be used to configure authorized uplink transmission;

The terminal device starts or restarts the third configuration authorization timer.
The method according to claim 9, wherein the method further comprises:

When the terminal device performs uplink data transmission on the configuration authorization, the terminal device starts or restarts the third configuration authorization timer.
The method according to any one of claims 9 to 11, wherein the terminal device determines according to the HARQ function status of the first HARQ process corresponding to uplink data transmission and the timer information of the configured grant timer The configured authorization timer for the first HARQ process includes:

If the number of the configuration authorization timer is 1, and the HARQ function status of the first HARQ process is off, the terminal device determines the third configuration authorization timer configured by the network device to be used for the Configure the authorization timer for the first HARQ process.
The method according to claim 12, wherein the uplink data transmission is an initial transmission of uplink data, and the method further comprises:

The terminal device receives the PDCCH used to schedule the initial transmission of the uplink data, and the first HARQ process can be used to configure the authorized uplink transmission;

The terminal device starts the third configuration authorization timer.
The method according to any one of claims 9 to 13, wherein the length of the third configuration authorization timer is based on the round-trip transmission time RTT of the signal transmission between the terminal device and the network device and The scheduling delay for the network equipment to schedule the uplink data transmission is determined.
The method according to any one of claims 1 to 14, wherein the method further comprises:

The terminal device receives the configuration information sent by the network device through radio resource control RRC signaling.
The method according to any one of claims 1 to 15, wherein the configuration information is used to configure the following parameters:

The at least one configuration parameter of the HARQ process used for uplink data transmission, where the configuration parameter of the HARQ process includes the HARQ function status of the HARQ process;

Configure authorization configuration parameters, where the configuration authorization configuration parameters include timer information of a configuration authorization timer of the at least one HARQ process;

At least one uplink bandwidth part BWP of each serving cell of the terminal device.
The method according to any one of claims 1 to 16, wherein the method is applied in a non-terrestrial communication network NTN.
A wireless communication method, characterized in that the method includes:

The network device sends configuration information to the terminal device, where the configuration information includes at least one HARQ function status of the HARQ process for hybrid automatic repeat request when transmitting uplink data, and a configuration authorization timer for the at least one HARQ process. Timer information.
The method according to claim 18, wherein 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 method according to claim 19, wherein the number of the configuration authorization timer is 2, 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 authorization timer is greater than the length of the second configuration authorization timer.
The method according to claim 20, wherein the method further comprises:

The network device determines the length of the first configuration grant timer according to the round-trip transmission time RTT of the signal transmission with the terminal device and the scheduling delay for the network device to schedule the uplink data transmission.
The method according to claim 20 or 21, wherein the method further comprises:

The network device determines the length of the second configuration grant timer according to the scheduling delay for scheduling the uplink data transmission.
The method according to claim 19, wherein the number of the configuration authorization timer is 1, and the configuration authorization timer is a third configuration authorization timer.
The method according to claim 23, wherein the method further comprises:

The network device determines the length of the third configuration grant timer according to the RTT of the signal transmission with the terminal device and the scheduling delay for the network device to schedule the uplink data transmission.
The method according to any one of claims 18 to 24, wherein the sending of configuration information by the network device to the terminal device comprises:

The network device sends the configuration information to the terminal device through radio resource control RRC signaling.
The method according to any one of claims 18 to 25, wherein the method is applied to a non-terrestrial communication network NTN.
A terminal device, characterized in that it comprises:

The processing unit is configured to obtain the HARQ function status of at least one HARQ process for the hybrid automatic repeat request HARQ process when transmitting uplink data according to the configuration information sent by the network device, and obtain the configuration authorization timer for the at least one HARQ process Timer information;

The processing unit is further configured to determine the configuration authorization 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 authorization timer, so The at least one HARQ process includes the first HARQ process.
The terminal device according to claim 27, wherein 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 terminal device according to claim 28, wherein the processing unit 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, determine the first configuration authorization timer as the configuration 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, determine the second configuration authorization timer as the configuration authorization timer for the first HARQ process;

Wherein, the length of the first configuration authorization timer is greater than the length of the second configuration authorization timer.
The terminal device according to claim 29, wherein the terminal device further comprises:

A communication unit, configured to receive a physical downlink control channel PDCCH used to schedule initial transmission or retransmission of uplink data sent by the network device, and the first HARQ process can be used to configure authorized uplink transmission;

The processing unit is also used for:

If the HARQ function status of the first HARQ process is in the on state, start or restart the first configuration authorization timer;

If the HARQ function state of the first HARQ process is in the off state, start or restart the second configuration grant timer.
The terminal device according to claim 29, wherein the uplink data transmission is uplink data retransmission, and the terminal device further comprises:

A communication unit, configured to receive the PDCCH used to schedule the uplink data retransmission sent by the network device, and the first HARQ process can be used to configure authorized uplink transmission;

The processing unit is also used for:

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 terminal device according to claim 29, wherein the processing unit is further configured to:

When the terminal device performs the uplink data transmission on the configuration grant, if the HARQ function status 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 grant timer.
The terminal device according to any one of claims 29 to 32, wherein the length of the first configuration authorization timer is based on the round-trip transmission time (RTT) of signal transmission between the terminal device and the network device And the scheduling delay for the network equipment to schedule the uplink data transmission is determined.
The terminal device according to any one of claims 29 to 33, wherein 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 terminal device according to claim 28, wherein the processing unit is specifically configured to:

If the number of the configuration authorization timer is 1, and the HARQ function status of the first HARQ process is in the on state, the third configuration authorization timer configured by the network device is determined to be used for the first HARQ process Configure the authorization timer.
The terminal device according to claim 35, wherein the terminal device further comprises:

A communication unit, configured to receive a PDCCH used to schedule the uplink data transmission, and the first HARQ process can be used to configure authorized uplink transmission;

The processing unit is also used for:

Start or restart the third configuration authorization timer.
The terminal device according to claim 35, wherein the processing unit 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 terminal device according to any one of claims 35 to 37, wherein the processing unit is specifically configured to:

If the number of the configuration authorization timer is 1, and the HARQ function status of the first HARQ process is off, the third configuration authorization timer configured by the network device is determined to be used for the first HARQ process Configure the authorization timer.
The terminal device according to claim 38, wherein the uplink data transmission is an initial transmission of uplink data, and the terminal device further comprises:

A communication unit, configured to receive a PDCCH used to schedule the initial transmission of the uplink data, and the first HARQ process can be used to configure authorized uplink transmission;

The processing unit is also used for:

Start the third configuration authorization timer.
The terminal device according to any one of claims 35 to 39, wherein the length of the third configuration authorization timer is based on the round-trip transmission time (RTT) of signal transmission between the terminal device and the network device And the scheduling delay for the network equipment to schedule the uplink data transmission is determined.
The terminal device according to any one of claims 27 to 40, wherein the terminal device further comprises:

The communication unit is configured to receive the configuration information sent by the network device through radio resource control RRC signaling.
The terminal device according to any one of claims 27 to 41, wherein the configuration information is used to configure the following parameters:

The at least one configuration parameter of the HARQ process used for uplink data transmission, where the configuration parameter of the HARQ process includes the HARQ function status of the HARQ process;

Configure authorization configuration parameters, where the configuration authorization configuration parameters include timer information of a configuration authorization timer of the at least one HARQ process;

At least one uplink bandwidth part BWP of each serving cell of the terminal device.
A network device, characterized in that it comprises:

The communication unit is configured to send configuration information to the terminal device, the configuration information including at least one HARQ function status of the HARQ process used for hybrid automatic repeat request when transmitting uplink data, and the configuration authorization for the at least one HARQ process Timer information of the timer, and the HARQ function state includes an on state or an off state.
The network device according to claim 43, wherein 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 network device according to claim 44, wherein the number of the configuration authorization timer is 2, the configuration authorization timer includes a first configuration authorization timer and a second configuration authorization timer, the first The length of the configuration authorization timer is greater than the length of the second configuration authorization timer.
The network device according to claim 45, wherein the network device further comprises:

The processing unit is configured to determine the length of the first configuration grant timer according to the round-trip transmission time RTT of the signal transmission with the terminal device and the scheduling delay for the network device to schedule the uplink data transmission.
The network device according to claim 45 or 46, wherein the network device further comprises:

The processing unit is configured to determine the length of the second configuration grant timer according to the scheduling delay for scheduling the uplink data transmission.
The network device according to claim 44, wherein the number of the configuration authorization timer is 1, and the configuration authorization timer is a third configuration authorization timer.
The network device according to claim 48, wherein the network device further comprises:

The processing unit is configured to determine the length of the third configuration grant timer according to the RTT of the signal transmission with the terminal device and the scheduling delay for the network device to schedule the uplink data transmission.
The network device according to any one of claims 43 to 49, wherein the communication unit is specifically configured to:

Sending the configuration information to the terminal device through radio resource control RRC signaling.
A terminal device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute as claimed in claims 1 to 17. Any of the methods.
A network device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute the computer program as in claims 18 to 26 Any of the methods.
An apparatus, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 1 to 17.
An apparatus, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 18 to 26.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 1 to 17.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 18 to 26.
A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 1 to 17.
A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 18 to 26.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 17.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 18 to 26.