Channel transmission method, terminal equipment and network equipment

Abstract

The embodiment of the invention provides a channel transmission method, terminal equipment and network equipment, which enhance HARQ (Hybrid Automatic Repeat reQuest) scheduling limitation under the condition that an HARQ process is de-enabled, and ensure that the processing time sequence of the terminal equipment is not out of order. The channel transmission method comprises: a terminal device transmitting a PUSCH using a first uplink HARQ process, the first uplink HARQ process corresponding to a first state, and a time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process being greater than or equal to a first duration.

Description

[0001] This application is a divisional application of an application with an application date of September 29, 2020, application number 202080103271.3, and invention name “Channel transmission method, terminal device and network device”. Technical Field

[0002] Embodiments of the present application relate to the field of communications, and more specifically, to a channel transmission method, a terminal device, and a network device. Background Art

[0003] The fifth generation mobile communication technology new radio (5G NR) system defines the deployment scenario of non-terrestrial networks (NTN) systems including satellite networks. With the wide-area coverage capability of satellites, NTN systems can achieve the continuity of 5G NR services. In addition, in the NTN system, in order to increase data transmission throughput and reduce the impact of the round trip time (RTT) of signal transmission, the hybrid automatic repeat request (HARQ) process is introduced to enable. In this case, how to design the scheduling restrictions for downlink and uplink transmission to enhance the HARQ scheduling restrictions in the NTN system and ensure that the processing timing of the terminal equipment will not be out of order. Summary of the invention

[0004] The embodiments of the present application provide a channel transmission method, a terminal device, and a network device. When the HARQ process is disabled, the HARQ scheduling restrictions are enhanced to ensure that the processing timing of the terminal device will not be out of order.

[0005] In a first aspect, a channel transmission method is provided, the method comprising:

[0006] The terminal device uses a first uplink HARQ process to transmit a PUSCH, wherein the first uplink HARQ process corresponds to a first state, and a time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration.

[0007] Optionally, the first uplink HARQ process corresponds to a first state, including:

[0008] The first uplink HARQ process is a disabled HARQ process; or,

[0009] The first uplink HARQ process is configured with a disabling parameter.

[0010] In a second aspect, a channel transmission method is provided, the method comprising:

[0011] The network device schedules the terminal device to use a first uplink HARQ process to transmit PUSCH, wherein the first uplink HARQ process corresponds to a first state, and a time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration.

[0012] Optionally, the first uplink HARQ process corresponds to a first state, including:

[0013] The first uplink HARQ process is a disabled HARQ process; or,

[0014] The first uplink HARQ process is configured with a disabling parameter.

[0015] In a third aspect, a channel transmission method is provided, the method comprising:

[0016] The terminal device receives the PDSCH sent by the network device using the first downlink HARQ process, wherein the first downlink HARQ process corresponds to a first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

[0017] Optionally, the first downlink HARQ process corresponds to a first state, including:

[0018] The first downlink HARQ process is a disabled HARQ process; or,

[0019] The first downlink HARQ process is configured with a disabling parameter; or,

[0020] The first downlink HARQ process does not correspond to uplink hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback.

[0021] In a fourth aspect, a channel transmission method is provided, the method comprising:

[0022] The network device uses a first downlink HARQ process to send a PDSCH to a terminal device, wherein the first downlink HARQ process corresponds to a first state, and a time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

[0023] Optionally, the first downlink HARQ process corresponds to a first state, including:

[0024] The first downlink HARQ process is a disabled HARQ process; or,

[0025] The first downlink HARQ process is configured with a disabling parameter; or,

[0026] The first downlink HARQ process does not correspond to uplink HARQ-ACK feedback.

[0027] In a fifth aspect, a terminal device is provided for executing the method in the first aspect.

[0028] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect.

[0029] In a sixth aspect, a network device is provided for executing the method in the second aspect.

[0030] Specifically, the network device includes a functional module for executing the method in the above second aspect.

[0031] In a seventh aspect, a terminal device is provided for executing the method in the third aspect.

[0032] Specifically, the terminal device includes a functional module for executing the method in the third aspect above.

[0033] In an eighth aspect, a network device is provided for executing the method in the fourth aspect.

[0034] Specifically, the network device includes a functional module for executing the method in the fourth aspect above.

[0035] In a ninth aspect, a terminal device is provided, comprising a processor and a memory, wherein 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 first aspect.

[0036] In a tenth aspect, a network device is provided, comprising a processor and a memory, wherein 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 second aspect.

[0037] In an eleventh aspect, a terminal device is provided, comprising a processor and a memory, wherein 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 third aspect.

[0038] In a twelfth aspect, a network device is provided, comprising a processor and a memory, wherein 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 fourth aspect.

[0039] In the thirteenth aspect, a device is provided for implementing the method in any one of the first to fourth aspects above.

[0040] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to fourth aspects described above.

[0041] In a fourteenth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to fourth aspects above.

[0042] In a fifteenth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to fourth aspects above.

[0043] In the sixteenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to fourth aspects above.

[0044] Through the technical solutions of the first and second aspects, when the first uplink HARQ process corresponds to the first state, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to the first duration, thereby enhancing the uplink HARQ scheduling restrictions and ensuring that the processing timing of the terminal device will not be out of order.

[0045] Through the technical solutions of the third and fourth aspects, when the first downlink HARQ process corresponds to the first state, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to the third duration, thereby enhancing the downlink HARQ scheduling restrictions and ensuring that the processing timing of the terminal device will not be out of order. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1A-Figure 1C It is a schematic diagram of an application scenario provided by an embodiment of the present application.

[0047] Figure 2 This is a schematic diagram provided by the present application showing that a certain time interval needs to be met between two PDSCH transmissions.

[0048] Figure 3 This is another schematic diagram provided by the present application showing that a certain time interval needs to be met between two PDSCH transmissions.

[0049] Figure 4 This is a schematic diagram provided by the present application showing that a certain time interval needs to be met between two PUSCH transmissions.

[0050] Figure 5 It is a schematic flowchart of a channel transmission method provided according to an embodiment of the present application.

[0051] Figure 6 This is a schematic diagram provided in an embodiment of the present application showing that the interval between two PUSCH transmissions needs to satisfy a first duration.

[0052] Figure 7 It is a schematic diagram of a first timer and a second timer provided in an embodiment of the present application.

[0053] Figure 8 This is a schematic diagram provided in an embodiment of the present application showing that the interval between two PUSCH transmissions needs to satisfy a second duration.

[0054] Fig. 9 It is a schematic flowchart of another channel transmission method provided according to an embodiment of the present application.

[0055] Fig.10 It is a schematic flowchart of another channel transmission method provided according to an embodiment of the present application.

[0056] Fig.11 This is a schematic diagram provided by an embodiment of the present application showing that the interval between two PDSCH transmissions needs to satisfy a third duration.

[0057] Fig.12 This is another schematic diagram provided by an embodiment of the present application, in which the interval between two PDSCH transmissions needs to satisfy a third duration.

[0058] Fig.13 It is a schematic diagram of the third timer and the fourth timer provided in the embodiment of the present application.

[0059] Fig.14 It is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0060] Fig.15 It is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0061] Fig.16 It is a schematic block diagram of another terminal device provided according to an embodiment of the present application.

[0062] Fig.17 It is a schematic block diagram of another network device provided according to an embodiment of the present application.

[0063] Fig.18 It is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0064] Fig.19 It is a schematic block diagram of a device provided according to an embodiment of the present application.

[0065] Fig. 20 It is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0066] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

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

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

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

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

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

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

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

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

[0075] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

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

[0077] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

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

[0079] Exemplarily, a communication system 100 used in an embodiment of the present application is shown in FIG1. ​​The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or referred to as 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.

[0080] For example, Figure 1AThe following is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. Figure 1A As shown, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or 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.

[0081] Figure 1A One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0082] For example, Figure 1B This is a schematic diagram of another communication system architecture provided in an embodiment of the present application. Figure 1B , including a terminal device 1101 and a satellite 1102, the terminal device 1101 and the satellite 1102 can communicate wirelessly. The network formed between the terminal device 1101 and the satellite 1102 can also be called NTN. Figure 1B In the architecture of the communication system shown, the satellite 1102 may have the function of a base station, and the terminal device 1101 and the satellite 1102 may communicate directly. In the system architecture, the satellite 1102 may be referred to as a network device. Optionally, the communication system may include multiple network devices 1102, and each network device 1102 may include other number of terminal devices within its coverage area, which is not limited in the embodiment of the present application.

[0083] For example, Figure 1C This is a schematic diagram of another communication system architecture provided in an embodiment of the present application. Figure 1C , including terminal equipment 1201, satellite 1202 and base station 1203, terminal equipment 1201 and satellite 1202 can communicate wirelessly, and satellite 1202 and base station 1203 can communicate. The network formed by terminal equipment 1201, satellite 1202 and base station 1203 can also be called NTN. Figure 1C In the architecture of the communication system shown, the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be transferred through the satellite 1202. In this system architecture, the base station 1203 can be called a network device. Optionally, the communication system may include multiple network devices 1203, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiment of the present application.

[0084] It should be noted that Figure 1A-Figure 1CThe system to which the present application is applicable is only illustrated in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems, such as 5G communication system, LTE communication system, etc., and the embodiment of the present application does not make specific limitations on this.

[0085] Optionally, Figure 1A-Figure 1C The wireless communication system shown may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this is not limited in the embodiments of the present application.

[0086] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1A Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

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

[0088] The terms used in the implementation mode of this application are only used to explain the specific embodiments of this application, and are not intended to limit this application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

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

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

[0091] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0092] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0093] In order to better understand the embodiments of the present application, the NTN system related to the present application is described.

[0094] NTN generally uses satellite communications to provide communication services to ground users. Compared with ground cellular network communications, satellite communications have many unique advantages. First, satellite communications are not restricted by user regions. For example, general land communications cannot cover areas such as oceans, mountains, deserts, etc. where communication equipment cannot be set up or where there is no communication coverage due to sparse population. For satellite communications, since one satellite can cover a large area of ​​land, and satellites can orbit the earth, in theory every corner of the earth can be covered by satellite communications. Secondly, satellite communications have great social value. Satellite communications can be covered at a low cost in remote mountainous areas, poor and backward countries or regions, so that people in these areas can enjoy advanced voice communications and mobile Internet technologies, which is conducive to narrowing the digital divide with developed areas and promoting the development of these areas. Thirdly, satellite communications have long distances, and the cost of communications does not increase significantly as the communication distance increases; finally, satellite communications are highly stable and are not restricted by natural disasters.

[0095] According to the different orbital altitudes, communication satellites are divided into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, High Elliptical Orbit (HEO) satellites, etc. At the current stage, the main research is on LEO and GEO.

[0096] Among them, the altitude range of low-orbit satellites is 500km~1500km, and the corresponding orbital period is about 1.5 hours~2 hours. The signal propagation delay of single-hop communication between users is generally less than 20ms. The maximum satellite visibility time is 20 minutes. The signal propagation distance is short, the link loss is small, and the transmission power requirement of the terminal equipment is not high.

[0097] Among them, the geosynchronous orbit satellite has an orbit altitude of 35786km and a rotation period around the earth of 24 hours. The signal propagation delay of single-hop communication between users is generally 250ms.

[0098] In order to ensure satellite coverage and improve 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 a ground area with a diameter of tens to hundreds of kilometers.

[0099] In order to facilitate a better understanding of the embodiments of the present application, the timing relationship of the NR system related to the present application and the timing relationship enhancement of the NTN system are explained.

[0100] Transmission timing of HARQ-ACK on the physical uplink control channel (PUCCH): For the time slot of PUCCH transmission, if the end position of a physical downlink shared channel (PDSCH) reception is in time slot n or the end position of a physical downlink control channel (PDCCH) reception indicating the release of semi-persistent scheduling (SPS) PDSCH is in time slot n, the terminal device should transmit HARQ-ACK on time slot n+K. 1 The corresponding HARQ-ACK information is transmitted on the PUCCH resources within K 1 It is the number of time slots and is indicated by the PDSCH-to-HARQ-timing-indicator information field in the downlink control information (DCI) format, or provided by the HARQ feedback timing set (e.g., dl-DataToUL-ACK field parameter). 1 =0 corresponds to the last time slot of PUCCH transmission overlapping with the time slot of PDSCH reception or PDCCH reception indicating SPS PDSCH release.

[0101] In order to work properly in the NTN system, or to overcome the large transmission delay in the NTN system, the above timing relationship needs to be enhanced. A simple solution is to introduce an offset parameter K in the system. offset , and apply the parameter to the relevant timing relationship.

[0102] Transmission timing of HARQ-ACK on PUCCH: For the time slot of PUCCH transmission, the terminal device should transmit HARQ-ACK in time slot n+K. 1 +K offset The corresponding HARQ-ACK information is transmitted on the PUCCH resources within the HARQ-ACK channel.

[0103] In order to better understand the embodiments of the present application, the NR HARQ scheduling restrictions related to the present application are explained.

[0104] Based on the provisions of the NR protocol, the terminal device has its own HARQ entity for each service cell. Each HARQ entity maintains a set of parallel downlink HARQ processes and a set of parallel uplink HARQ processes. Currently, each uplink and downlink carrier supports a maximum of 16 HARQ processes. The base station can indicate the maximum number of HARQ processes to the terminal device through the semi-static configuration of the radio resource control (Radio Resource Control, RRC) signaling according to the deployment of the network equipment. If the network equipment does not provide the corresponding configuration parameters, the default number of HARQ processes for the downlink is 8, and the maximum number of HARQ processes supported by each uplink carrier is 16. Each HARQ process corresponds to a HARQ process identifier (Identity, ID). For the downlink, the broadcast control channel (Broadcast Control Channel, BCCH) uses a dedicated broadcast HARQ process. For the uplink, the third message (Message 3, Msg 3) in the four-step random process is transmitted using HARQ ID 0.

[0105] For downlink transmission: the terminal device detects DCI according to the configured DCI format 1_0, DCI format 1_1 or DCI format 1_2 and performs PDSCH decoding according to the DCI scheduling.

[0106] If the terminal device receives the first PDSCH of the network device scheduling HARQ x transmission, before the terminal device sends the HARQ-ACK feedback information corresponding to the first PDSCH to the network device, the terminal device does not expect to receive the second PDSCH of the network device scheduling the HARQ x transmission again, such as Figure 2The transmission timing (denoted by K1) of the terminal device sending the HARQ-ACK feedback information corresponding to the first PDSCH to the network device is determined according to the HARQ feedback timing set, and the HARQ feedback timing set can be preset or configured by the network device.

[0107] In a designated scheduling cell, if a terminal device receives a first PDSCH corresponding to a System Information Radio Network Temporary Identity (SI-RNTI) sent by a network device, the terminal device does not expect to decode a retransmission of the first PDSCH by the network device within N symbols after the last symbol of the first PDSCH transmission, such as Figure 3 As shown, the value of N is related to the subcarrier spacing configuration μ of the first PDSCH, when μ=0, N=13, when μ=1, N=13, when μ=2, N=20, and when μ=3, N=24.

[0108] The above two scheduling restrictions indicate that a certain time interval must be satisfied between two PDSCH transmissions in the same HARQ process.

[0109] For uplink transmission: the terminal device detects DCI according to the configured DCI format 0_0, DCI format 0_1 ​​or DCI format 0_2 and sends PUSCH according to the DCI scheduling.

[0110] If a terminal device receives a first PUSCH that is scheduled by a network device through a first DCI for HARQ x transmission, before the terminal device finishes transmitting the first PUSCH to the network device, the terminal device does not expect to receive a second DCI that is sent by the network device for scheduling the HARQ x transmission of a second PUSCH, such as Figure 4 As shown, the second DCI corresponds to DCI format 0_0 or DCI format 0_1 ​​scrambled by a cell radio network temporary identifier (C-RNTI) or a modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI).

[0111] In order to better understand the embodiments of the present application, the PUSCH transmission and PUCCH transmission in the NR system related to the present application are explained.

[0112] In the NR system, PUSCH transmission is determined according to the N2 processing capability.

[0113] If the UE receives uplink authorization information from the base station, the uplink authorization information schedules the UE to send a target PUSCH carrying a target transport block and a demodulation reference signal (DMRS). If the UE determines the starting position of the first uplink symbol of the target PUSCH after considering the influence of the timing advance based on the uplink authorization information, for example, based on the start length indicator value (Start and length indicator value, SLIV) in the uplink authorization information, if the starting position of the first uplink symbol is not earlier than symbol L2, then the UE should transmit the target transport block; otherwise, the UE ignores the scheduling DCI.

[0114] The symbol L2 is defined as the next uplink symbol after the end position of the last symbol of the PDCCH carrying the uplink grant information, wherein the starting position of the cyclic prefix (CP) of the next uplink symbol is later than T proc,2 Processing time, where T proc,2 It is determined according to the value of the physical uplink shared channel (PUSCH) preparation time N2 (for example, in symbols). proc,2 Determined according to the following formula 1.

[0115] T proc,2 =max((N 2 +d 2,1 +d 2 )(2048+144)·κ2 -μ ·T C +T ext +T switch ,d 2,2 ) Formula 1

[0116] It should be noted that the meaning of each parameter in Formula 1 can refer to the definition in Section 6.4 of the communication protocol standard TS38.214, and for the sake of brevity, it will not be discussed here. In addition, different communication protocol standards may revise or update the meaning of each parameter in Formula 1, and this application can be adjusted according to the corresponding communication protocol.

[0117] The processing capability 1 and the processing capability 2 of the UE correspond to different processing capabilities respectively, or in other words, the N2 value corresponding to the processing capability 1 of the UE is different from the N2 value corresponding to the processing capability 2 of the UE.

[0118] Among them, the value of N2 is different under different subcarrier spacings.

[0119] In the NR system, the transmission of PUCCH is determined according to the N1 processing capability, or in other words, the transmission of PUCCH is determined according to the PDSCH processing time of the UE.

[0120] If the UE receives downlink authorization information from the base station, which schedules the UE to receive the PDSCH carrying the target transport block, the UE determines that the HARQ-ACK information corresponding to the scheduled PDSCH is transmitted through the target PUCCH based on the allocated HARQ-ACK timing information K1 and PUCCH resource indication information, and the starting position of the first uplink symbol of the target PUCCH is not earlier than symbol L1 after considering the influence of timing advance, then the UE should provide valid HARQ-ACK information of the scheduled PDSCH; otherwise, the UE may not provide valid HARQ-ACK information of the scheduled PDSCH.

[0121] The symbol L1 is defined as the next uplink symbol after the end position of the last symbol of the PDSCH carrying the target transport block, wherein the starting position of the CP of the next uplink symbol is later than T proc,1 Processing time, where T proc,1 It is determined according to the PDSCH decoding time N1 value (for example, in symbols). proc,1 Determined according to the following formula 2.

[0122] T proc,1 =(N 1 +d 1,1 +d 2 )(2048+144)·κ2 -μ ·T C +T ext Formula 2

[0123] It should be noted that the meaning of each parameter in Formula 2 can refer to the definition in Section 5.3 of the communication protocol standard TS38.214, and for the sake of brevity, it will not be discussed here. In addition, different communication protocol standards may revise or update the meaning of each parameter in Formula 2, and this application can be adjusted according to the corresponding communication protocol.

[0124] The processing capability 1 and the processing capability 2 of the UE correspond to different processing capabilities, respectively. In other words, the N1 value corresponding to the processing capability 1 of the UE is different from the N1 value corresponding to the processing capability 2 of the UE.

[0125] The value of N1 is different under different subcarrier spacings.

[0126] In order to better understand the embodiments of the present application, the NTN HARQ enhancement related to the present application is described.

[0127] In the NTN system, since the communication distance between the terminal device and the satellite (or network device) is very long, the RTT of signal transmission is very large. In the GEO system, the RTT of signal transmission can be in the order of hundreds of milliseconds, for example, the maximum RTT of signal transmission can be about 600ms. In the LEO system, the RTT of signal transmission can be in the order of tens of milliseconds. Since the RTT of the NTN system is much larger than the RTT of the terrestrial communication system, the HARQ mechanism in the existing NR system is no longer applicable to the NTN system.

[0128] Currently, the HARQ enhancement discussed in the NTN system includes: HARQ process disabling.

[0129] The network device can configure to disable one or some downlink HARQ processes of the terminal device. For the downlink HARQ process that is configured to be disabled, the network device does not need to receive the HARQ-ACK information corresponding to the transport block (TransportBlock, TB) transmitted in the HARQ process, and can reuse the HARQ process for data transmission. Therefore, the network device can use the disabled downlink HARQ process to schedule multiple downlink data packets for the terminal device, thereby increasing the data transmission throughput and reducing the impact of RTT. For the downlink HARQ process that is not configured to be disabled, the downlink transmission between the network device and the terminal device uses the same HARQ retransmission mechanism as the NR system.

[0130] The network device can also disable one or some uplink HARQ processes of the terminal device. For the uplink HARQ process that is configured to be disabled, the network device does not need to receive the PUSCH transmitted by the terminal device through the HARQ process, and can reuse the HARQ process to schedule the transmission of other PUSCHs. Therefore, the network device can use the disabled uplink HARQ process to schedule multiple uplink data packets for the terminal device, thereby increasing the data transmission throughput and reducing the impact of RTT. For the uplink HARQ process that is not configured to be disabled, the uplink transmission between the network device and the terminal device uses the same HARQ retransmission mechanism as the NR system.

[0131] That is to say, in the NTN system, the HARQ process may correspond to two states, such as an enabled state and a disabled state (also called a disabled state), where if the HARQ process corresponds to the enabled state, it can be considered that the function of the HARQ process is consistent with the NR system.

[0132] In the NTN system, a HARQ process corresponding to the disabled state is introduced. In this case, how to redesign the scheduling restrictions of downlink transmission and uplink transmission to enhance the HARQ scheduling restrictions in the NTN system and ensure that the processing timing of the terminal device will not be out of order is an urgent problem to be solved in this application.

[0133] Based on the above problems, the present application proposes a channel transmission solution. In the NTN system, when the HARQ process is disabled, the HARQ scheduling restriction is enhanced to ensure that the processing timing of the terminal device will not be out of order.

[0134] The technical solution of the present application is described in detail below through specific embodiments.

[0135] Figure 5 is a schematic flow chart of a channel transmission method 200 according to an embodiment of the present application, such as Figure 5 As shown, the method 200 may include at least part of the following contents:

[0136] S210, the terminal device uses a first uplink HARQ process to transmit a PUSCH, wherein the first uplink HARQ process corresponds to a first state, and a time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration.

[0137] That is, the time interval between the nth PUSCH transmission and the (n-1)th PUSCH transmission corresponding to the first uplink HARQ process is greater than or equal to the first duration, n is a positive integer, and n≥2.

[0138] Optionally, the first uplink HARQ process corresponds to a first state, including:

[0139] The first uplink HARQ process is a disabled HARQ process; or,

[0140] The first uplink HARQ process is configured with a disabling parameter.

[0141] It should be noted that, for the first uplink HARQ process corresponding to the disabled state, the network device does not need to receive PUSCH 1 carrying TB 1 transmitted in the first uplink HARQ process, and can reuse the first uplink HARQ process to schedule the transmission of PUSCH 2 carrying TB 2. Among them, TB 1 and TB 2 can be the same TB or different TBs. However, when the network device reuses the first uplink HARQ process to transmit TB 2, it is necessary to ensure that the time interval between the transmission of PUSCH 1 of TB 1 and the transmission of PUSCH 2 of TB 2 is greater than or equal to the first duration, so as to ensure that the terminal device has enough time to process and prepare for the transmission of PUSCH 2 after sending PUSCH 1 when sending PUSCH 2. In addition, the DCI for scheduling PUSCH 2 may be received before the transmission of PUSCH 1, may be received after the transmission of PUSCH 1, or may be received during the transmission of PUSCH 1.

[0142] Optionally, in some embodiments, in S210, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration, which may specifically include at least one of the following Examples 1 to 3.

[0143] Example 1: The terminal device receives a first PDCCH, which is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and the terminal device does not expect to be scheduled to transmit a second PUSCH using the first uplink HARQ process within the first time length after the last symbol of the target PUSCH transmission in the first PUSCH.

[0144] Example 2: The terminal device receives a first PDCCH, which is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and when the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process within the first time length after the last symbol of the target PUSCH transmission in the first PUSCH, the terminal device does not transmit the second PUSCH.

[0145] Example 3: The terminal device receives a first PDCCH, which is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and when the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process after the first time length after the last symbol of the target PUSCH transmission in the first PUSCH, the terminal device transmits the second PUSCH.

[0146] Optionally, at least one PUSCH included in the first PUSCH may be used to transmit the first TB. That is, each PUSCH in the at least one PUSCH included in the first PUSCH is used to transmit the first TB. For example, the first PUSCH includes PUSCH 1 and PUSCH 2, PUSCH 1 is used to transmit the first TB, and PUSCH 2 is also used to transmit the first TB.

[0147] Optionally, the first PUSCH corresponds to the kth PUSCH transmission, and the second PUSCH corresponds to the k+1th PUSCH transmission.

[0148] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or,

[0149] The target PUSCH is the last PUSCH in the first PUSCH.

[0150] Optionally, the first PUSCH is scheduled by a PDCCH, or the first PUSCH corresponds to a PDCCH.

[0151] Optionally, the first PUSCH is a PUSCH scheduled by a PDCCH, or the first PUSCH is a Semi-Persistent Scheduling (SPS) PUSCH, or the first PUSCH is a Configured Grant (CG) PUSCH.

[0152] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are continuous in the time domain, or the at least two PUSCHs occupy at least two continuous time slots in the time domain.

[0153] For example, the terminal device receives a first PDCCH, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using HARQ x, such as Figure 6In case 1, the earliest time when HARQ x can be rescheduled is the first time after the last symbol of the first PUSCH transmission. That is, when the terminal device is scheduled to transmit the second PUSCH using the HARQ x after the first time after the last symbol of the first PUSCH transmission, the terminal device transmits the second PUSCH.

[0154] For another example, a terminal device receives a first PDCCH, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using HARQ x, where the first PUSCH includes PUSCH 1 and PUSCH 2, such as Figure 6 In case 2, the earliest time that HARQ x can be rescheduled is the first time after the last symbol transmitted by PUSCH 2 in the first PUSCH (the last PUSCH in the first PUSCH). That is to say, when the terminal device is scheduled to transmit the second PUSCH using the HARQ x after the first time after the last symbol transmitted by PUSCH 2 in the first PUSCH, the terminal device transmits the second PUSCH.

[0155] For another example, a terminal device receives a first PDCCH, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using HARQ x, where the first PUSCH includes PUSCH 1 and PUSCH 2, such as Figure 6 In case 3, the earliest time when HARQ x can be rescheduled is the first time after the last symbol transmitted by PUSCH 1 in the first PUSCH (the first PUSCH in the first PUSCH). That is to say, when the terminal device is scheduled to transmit the second PUSCH using the HARQ x after the first time after the last symbol transmitted by PUSCH 1 in the first PUSCH, the terminal device transmits the second PUSCH.

[0156] Optionally, in some embodiments, when the terminal device is configured for discontinuous reception (DRX), the terminal device starts the first timer after the last symbol of the target PUSCH transmission in the first PUSCH, or the terminal device starts the first timer after the last symbol of the first PDCCH transmission.

[0157] The first timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, and the second PDCCH is used to schedule the terminal device to transmit a second PUSCH using the first uplink HARQ process.

[0158] For example, the first timer is used to indicate the minimum duration during which the terminal device does not expect to receive the second PDCCH.

[0159] Alternatively, the first timer is used to indicate that the terminal device does not expect to use the first uplink HARQ process to transmit a time window for the second PUSCH.

[0160] For example, the first timer is used to indicate the minimum duration for which the terminal device does not expect to use the first uplink HARQ process to transmit the second PUSCH.

[0161] Optionally, the first timer is a DRX uplink HARQ RTT timer (drx-HARQ-RTT-TimerUL).

[0162] Optionally, the first timer corresponds to the first duration. For example, the duration of the first timer is less than or equal to the first duration.

[0163] Optionally, the terminal device starts a second timer after the first timer times out, and the second timer is used to indicate a time window in which the terminal device may receive the second PDCCH.

[0164] For example, the second timer is used to indicate the maximum duration that the terminal device may receive the second PDCCH.

[0165] Alternatively, the second timer is used to indicate a time window in which the terminal device may use the first uplink HARQ process to transmit a second PUSCH.

[0166] For example, the second timer is used to indicate the maximum duration that the terminal device may use the first uplink HARQ process to transmit the second PUSCH.

[0167] Optionally, the second timer is a DRX uplink retransmission timer (drx-RetransmissionTimerUL).

[0168] For example, when the terminal device is configured with DRX, the terminal device receives a first PDCCH, and the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using HARQ x, such as Figure 7 In case 1, the terminal device starts the first timer after the last symbol of the first PUSCH transmission, and starts the second timer after the first timer times out. In addition, during the operation of the second timer, the terminal device transmits the second PUSCH using HARQ x.

[0169] For another example, when the terminal device is configured with DRX, the terminal device receives a first PDCCH, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using HARQ x, where the first PUSCH includes PUSCH 1 and PUSCH 2. Figure 7 In case 2, the terminal device starts the first timer after the last symbol transmitted by PUSCH 2 in the first PUSCH (the last PUSCH in the first PUSCH), and starts the second timer after the first timer times out. In addition, during the operation of the second timer, the terminal device transmits the second PUSCH using HARQ x.

[0170] For another example, when the terminal device is configured with DRX, the terminal device receives a first PDCCH, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using HARQ x, where the first PUSCH includes PUSCH 1 and PUSCH 2. Figure 7 In case 3, the terminal device starts the first timer after the last symbol transmitted by PUSCH 1 in the first PUSCH (the first PUSCH in the first PUSCH), and starts the second timer after the first timer times out. In addition, during the operation of the second timer, the terminal device transmits the second PUSCH using HARQ x.

[0171] For another example, when the terminal device is configured with DRX, the terminal device receives a first PDCCH, the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using HARQ x, the terminal device starts the first timer after the last symbol transmitted by the first PDCCH, and starts the second timer after the first timer times out. In addition, during the operation of the second timer, the terminal device receives a second PDCCH for scheduling the terminal device to transmit a second PUSCH using the HARQ x, or the terminal device transmits a second PUSCH using the HARQ x.

[0172] Optionally, in some other embodiments, in S210, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration, which may specifically include at least one of the following Examples 4 to 5.

[0173] Example 4: The terminal device receives a first PDCCH, wherein the uplink authorization information carried in the first PDCCH schedules the terminal device to use the first uplink HARQ process to transmit a first PUSCH carrying a first TB; and when the interval between the end position of the target symbol and the starting position of the first uplink symbol of the first PUSCH after considering the influence of timing advance is less than a second duration, the terminal device ignores the first PDCCH, or the terminal device does not transmit the first PUSCH.

[0174] Example 5, the terminal device receives a first PDCCH, wherein the uplink authorization information carried in the first PDCCH schedules the terminal device to use the first uplink HARQ process to transmit a first PUSCH carrying a first TB; and when the interval between the end position of the target symbol and the starting position of the first uplink symbol of the first PUSCH after considering the influence of timing advance is greater than or equal to the second duration, the terminal device transmits the first PUSCH.

[0175] Among them, the last PUSCH transmitted using the first uplink HARQ process is the third PUSCH, and the third PUSCH includes at least one PUSCH; the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering the timing advance, or the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering the timing advance.

[0176] Optionally, in Example 4 and Example 5, the second duration is determined according to a processing time Tproc,2, where Tproc,2 is determined according to a PUSCH preparation time value N2.

[0177] For example, a terminal device receives a first PDCCH, wherein a first DCI carried in the first PDCCH schedules the terminal device to use HARQ x to transmit a first PUSCH carrying a first TB; the last PUSCH transmitted using the HARQ x is a third PUSCH, the third PUSCH includes PUSCH 1 and PUSCH 2, and the third PUSCH is scheduled for transmission by a third DCI carried in a third PDCCH; Figure 8 In case 1, the later of the last symbol of the first PDCCH and the last uplink symbol of PUSCH 2 after timing advance (the last PUSCH in the third PUSCH) is the last uplink symbol of PUSCH 2 (i.e., the target symbol). Then, the earliest time that the first PUSCH can be sent is the second time duration after the last symbol transmitted by PUSCH 2.

[0178] For another example, a terminal device receives a first PDCCH, wherein the first DCI carried in the first PDCCH schedules the terminal device to use HARQ x to transmit a first PUSCH carrying a first TB; the last PUSCH transmitted using the HARQ x is a third PUSCH, the third PUSCH includes PUSCH 1 and PUSCH 2, and the third PUSCH is scheduled for transmission by a third DCI carried in a third PDCCH; Figure 8 In case 2, the later of the last symbol of the first PDCCH and the last uplink symbol of PUSCH 1 (the first PUSCH in the third PUSCH) after timing advance is the last symbol of the first PDCCH (i.e., the target symbol). Then, the earliest time that the first PUSCH can be sent is the second time duration after the last symbol transmitted by the first PDCCH.

[0179] It should be noted that the above HARQ x is a specific example of the first uplink HARQ process and does not constitute a limitation to the present application.

[0180] Optionally, in the embodiment of the present application, the first duration may be determined according to at least one of the following:

[0181] PUSCH preparation time value;

[0182] T proc,2 Processing time, where T proc,2 It is determined based on the PUSCH preparation time value;

[0183] The processing time value of the network device receiving the PUSCH;

[0184] The larger value between the PUSCH preparation time value and the processing time value of the network device receiving the PUSCH;

[0185] The smaller value between the PUSCH preparation time value and the processing time value of the network device receiving PUSCH.

[0186] It should be noted that the PUSCH preparation time value, for example, N2, may be a PUSCH preparation time value of a terminal device. In addition, the N2 value corresponding to the processing capability 1 of the UE is different from the N2 value corresponding to the processing capability 2 of the UE.

[0187] Optionally, the first duration and the second duration are equal.

[0188] Optionally, the second duration is greater than the first duration.

[0189] Optionally, the PUSCH preparation time value N2 is related to the subcarrier spacing configuration of the PUSCH, or the PUSCH preparation time value N2 is related to the subcarrier spacing configuration of the PDCCH that schedules the PUSCH. For example, the value of N2 is different under different subcarrier spacings.

[0190] For example, if the UE receives uplink authorization information from the base station, the uplink authorization information schedules the UE to send a target PUSCH carrying a target transport block and DMRS and corresponding to the first uplink HARQ process. If the UE determines the starting position of the first uplink symbol of the target PUSCH after considering the influence of timing advance based on the uplink authorization information, for example, based on the SLIV indication in the uplink authorization information, and if the starting position of the first uplink symbol is not earlier than symbol L2, then the UE should transmit the target transport block; otherwise, the UE ignores the scheduling DCI.

[0191] Among them, symbol L2 is defined as: the next uplink symbol after the end position of the later symbol of the last symbol of the PDCCH carrying the uplink authorization information and the last symbol of the previous PUSCH transmission corresponding to the first uplink HARQ process, wherein the starting position of the CP of the next uplink symbol is later than the Tproc,2 processing time.

[0192] Optionally, T proc,2 It can be determined according to the above formula 1.

[0193] It should be noted that the meaning of each parameter in Formula 1 can refer to the definition in Section 6.4 of the communication protocol standard TS38.214, and for the sake of brevity, it will not be discussed here. In addition, different communication protocol standards may revise or update the meaning of each parameter in Formula 1, and this application can be adjusted according to the corresponding communication protocol.

[0194] It should be noted that, in the embodiment of the present application, at least one PUSCH included in the first PUSCH can be used to transmit the first TB. At least one PUSCH included in the second PUSCH can be used to transmit the second TB. At least one PUSCH included in the third PUSCH can be used to transmit the third TB. In addition, in the embodiment of the present application, the first PUSCH corresponds to the kth PUSCH transmission, the second PUSCH corresponds to the k+1th PUSCH transmission, and the third PUSCH corresponds to the k-1th PUSCH transmission.

[0195] Therefore, in the embodiment of the present application, when the first uplink HARQ process corresponds to the first state, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to the first duration, thereby enhancing the uplink HARQ scheduling restriction and ensuring that the processing timing of the terminal device will not be out of order.

[0196] Combination of the above Figures 5 to 8 , describes in detail an embodiment of the channel transmission method 200 of the present application from the terminal side, and the following is combined with Fig. 9 , an embodiment of the channel transmission method 300 of the present application is described in detail from the network side. It should be understood that the embodiment of the channel transmission method 300 corresponds to the embodiment of the channel transmission method 200, and similar descriptions can refer to the embodiment of the channel transmission method 200.

[0197] Fig. 9 is a schematic flow chart of a channel transmission method 300 according to an embodiment of the present application, such as Fig. 9 As shown, the method 300 may include at least part of the following contents:

[0198] S310, the network device schedules the terminal device to use the first uplink HARQ process to transmit PUSCH, wherein the first uplink HARQ process corresponds to a first state, and the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration.

[0199] That is, the time interval between the nth PUSCH transmission and the (n-1)th PUSCH transmission corresponding to the first uplink HARQ process is greater than or equal to the first duration, n is a positive integer, and n≥2.

[0200] Optionally, the first uplink HARQ process corresponds to a first state, including:

[0201] The first uplink HARQ process is a disabled HARQ process; or,

[0202] The first uplink HARQ process is configured with a disabling parameter.

[0203] Optionally, in some embodiments, in S310, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration, which may specifically include at least one of the following Examples 1 to 3.

[0204] Example 1: The network device sends a first PDCCH to the terminal device, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and the network device does not schedule the terminal device to transmit a second PUSCH using the first uplink HARQ process within the first time length after the last symbol of the target PUSCH transmission in the first PUSCH.

[0205] Example 2: The network device sends a first PDCCH to the terminal device, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and when the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process within the first time length after the last symbol of the target PUSCH transmission in the first PUSCH, the network device does not expect to receive the second PUSCH sent by the terminal device.

[0206] Example 3: The network device sends a first PDCCH to the terminal device, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and when the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process after the first time length after the last symbol of the target PUSCH transmission in the first PUSCH, the network device receives the second PUSCH sent by the terminal device.

[0207] Optionally, in some embodiments, the network device sends first configuration information to the terminal device, wherein:

[0208] In a case where the terminal device is configured with discontinuous reception DRX, the first configuration information is used to configure the terminal device to start the first timer after the last symbol of the target PUSCH transmission in the first PUSCH, or the first configuration information is used to configure the terminal device to start the first timer after the last symbol of the first PDCCH transmission;

[0209] The first timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, and the second PDCCH is used to schedule the terminal device to use the first uplink HARQ process to transmit a second PUSCH. Alternatively, the first timer is used to indicate a time window in which the terminal device does not expect to use the first uplink HARQ process to transmit a second PUSCH.

[0210] Optionally, in some embodiments, the network device sends second configuration information to the terminal device, wherein:

[0211] The second configuration information is used to configure the terminal device to start a second timer after the first timer times out, and the second timer is used to indicate a time window in which the terminal device may receive the second PDCCH. Alternatively, the second timer is used to indicate a time window in which the terminal device may use the first uplink HARQ process to transmit the second PUSCH.

[0212] Optionally, the second timer is a DRX uplink retransmission timer (drx-RetransmissionTimerUL).

[0213] Optionally, the second configuration information includes the second timer.

[0214] Optionally, the duration of the first timer is less than or equal to the first duration.

[0215] Optionally, the first timer is a DRX uplink HARQ RTT timer (drx-HARQ-RTT-TimerUL).

[0216] Optionally, the first configuration information includes the first timer.

[0217] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or,

[0218] The target PUSCH is the last PUSCH in the first PUSCH.

[0219] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are continuous in the time domain, or the at least two PUSCHs occupy at least two continuous time slots in the time domain.

[0220] Optionally, the first PUSCH is scheduled by a PDCCH, or the first PUSCH corresponds to a PDCCH.

[0221] Optionally, the first PUSCH is a PUSCH scheduled by a PDCCH, or the first PUSCH is an SPS PUSCH, or the first PUSCH is a CG PUSCH.

[0222] Optionally, in some other embodiments, in S310, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration, which may specifically include at least one of the following Examples 4 to 5.

[0223] Example 4: The network device sends a first PDCCH to the terminal device, wherein the uplink authorization information carried in the first PDCCH schedules the terminal device to use the first uplink HARQ process to transmit a first PUSCH carrying a first transport block TB; and when the interval between the end position of the target symbol and the starting position of the first uplink symbol of the first PUSCH after considering the influence of timing advance is less than a second duration, the network device does not expect the terminal device to transmit the first PUSCH.

[0224] Example 5, the network device sends a first PDCCH to the terminal device, wherein the uplink authorization information carried in the first PDCCH schedules the terminal device to use the first uplink HARQ process to transmit the first PUSCH carrying the first transport block TB; and when the interval between the end position of the target symbol and the starting position of the first uplink symbol of the first PUSCH after considering the influence of timing advance is greater than or equal to the second duration, the network device receives the first PUSCH sent by the terminal device.

[0225] Among them, the last PUSCH transmitted using the first uplink HARQ process is the third PUSCH, the third PUSCH includes at least one PUSCH, the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering the timing advance, or the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering the timing advance.

[0226] Optionally, the second duration is based on T proc,2 The processing time is determined by T proc,2 It is determined according to the PUSCH preparation time value.

[0227] Optionally, in the embodiment of the present application, the first duration may be determined according to at least one of the following:

[0228] PUSCH preparation time value;

[0229] T proc,2 Processing time, where T proc,2 It is determined based on the PUSCH preparation time value;

[0230] The processing time value of the network device receiving the PUSCH;

[0231] The larger value between the PUSCH preparation time value and the processing time value of the network device receiving the PUSCH;

[0232] The smaller value between the PUSCH preparation time value and the processing time value of the network device receiving PUSCH.

[0233] It should be noted that the PUSCH preparation time value N2 may be a PUSCH preparation time value of a terminal device. In addition, the N2 value corresponding to the processing capability 1 of the UE is different from the N2 value corresponding to the processing capability 2 of the UE.

[0234] Optionally, the first duration and the second duration are equal.

[0235] Optionally, the second duration is greater than the first duration.

[0236] Optionally, the PUSCH preparation time value N2 is related to the subcarrier spacing configuration of the PUSCH, or the PUSCH preparation time value N2 is related to the subcarrier spacing configuration of the PDCCH that schedules the PUSCH. For example, the value of N2 is different under different subcarrier spacings.

[0237] For example, if the UE receives uplink authorization information from the base station, the uplink authorization information schedules the UE to send a target PUSCH carrying a target transport block and DMRS and corresponding to the first uplink HARQ process. If the UE determines the starting position of the first uplink symbol of the target PUSCH after considering the influence of timing advance based on the uplink authorization information, for example, based on the SLIV indication in the uplink authorization information, and if the starting position of the first uplink symbol is not earlier than symbol L2, then the UE should transmit the target transport block; otherwise, the UE ignores the scheduling DCI.

[0238] The symbol L2 is defined as the next uplink symbol after the end position of the later symbol of the last symbol of the PDCCH carrying the uplink authorization information and the last symbol of the last PUSCH transmission corresponding to the first uplink HARQ process, wherein the starting position of the CP of the next uplink symbol is later than T proc,2 Processing time.

[0239] Optionally, T proc,2 It can be determined according to the above formula 1.

[0240] It should be noted that the meaning of each parameter in Formula 1 can refer to the definition in Section 6.4 of the communication protocol standard TS38.214, and for the sake of brevity, it will not be discussed here. In addition, different communication protocol standards may revise or update the meaning of each parameter in Formula 1, and this application can be adjusted according to the corresponding communication protocol.

[0241] It should be noted that, in the embodiment of the present application, at least one PUSCH included in the first PUSCH can be used to transmit the first TB. At least one PUSCH included in the second PUSCH can be used to transmit the second TB. At least one PUSCH included in the third PUSCH can be used to transmit the third TB. In addition, in the embodiment of the present application, the first PUSCH corresponds to the kth PUSCH transmission, the second PUSCH corresponds to the k+1th PUSCH transmission, and the third PUSCH corresponds to the k-1th PUSCH transmission.

[0242] Therefore, in the embodiment of the present application, when the first uplink HARQ process corresponds to the first state, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to the first duration, thereby enhancing the uplink HARQ scheduling restriction and ensuring that the processing timing of the terminal device will not be out of order.

[0243] Fig.10 is a schematic flow chart of a channel transmission method 400 according to an embodiment of the present application, such as Fig.10 As shown, the method 400 may include at least part of the following contents:

[0244] S410, the network device sends a PDSCH to the terminal device using a first downlink HARQ process, wherein the first downlink HARQ process corresponds to a first state, and a time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration;

[0245] S420, the terminal device receives the PDSCH sent by the network device using the first downlink HARQ process.

[0246] That is, the time interval between the nth PDSCH transmission and the (n-1)th PDSCH transmission corresponding to the first downlink HARQ process is greater than or equal to the third duration, n is a positive integer, and n≥2.

[0247] Optionally, the first downlink HARQ process corresponds to a first state, including:

[0248] The first downlink HARQ process is a disabled HARQ process; or,

[0249] The first downlink HARQ process is configured with a disabling parameter; or,

[0250] The first downlink HARQ process does not correspond to uplink HARQ-ACK feedback.

[0251] It should be noted that, for the first downlink HARQ process corresponding to the disabled state, the network device does not need to receive the HARQ-ACK information corresponding to TB 1 transmitted in the first downlink HARQ process, and can reuse the first downlink HARQ process to transmit TB 2. TB 1 and TB 2 can be the same TB or different TBs. However, when the network device reuses the first downlink HARQ process to transmit TB 2, it is necessary to ensure that the time interval between PDSCH 1 for transmitting TB 1 and PDSCH 2 for transmitting TB 2 is greater than or equal to the third time length, so as to ensure that the terminal device has sufficient time to process the reception of PDSCH 1 when receiving PDSCH 2.

[0252] Optionally, in some embodiments, in S410, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, which may specifically include at least one of the following Examples 1 to 3.

[0253] Example 1, the terminal device receives the first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and the terminal device does not expect to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process within the third time length after the last symbol of the target PDSCH transmission in the first PDSCH. Correspondingly, the network device does not send the second PDSCH using the first downlink HARQ process within the third time length after the last symbol of the target PDSCH transmission in the first PDSCH.

[0254] Example 2, the terminal device receives the first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and in the case where the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process within the third time length after the last symbol of the target PDSCH in the first PDSCH is transmitted, the terminal device does not receive or decode the second PDSCH. Correspondingly, in the case where the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process within the third time length after the last symbol of the target PDSCH in the first PDSCH is transmitted, the network device assumes that the terminal device does not receive or decode the second PDSCH.

[0255] Example 3, the terminal device receives a first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and in a case where the terminal device receives or decodes a second PDSCH sent by the network device using the first downlink HARQ process after the third time period after the last symbol of the target PDSCH in the first PDSCH is scheduled to be transmitted, the terminal device receives or decodes the second PDSCH. Correspondingly, in a case where the terminal device receives or decodes the second PDSCH sent by the network device using the first downlink HARQ process after the third time period after the last symbol of the target PDSCH in the first PDSCH is scheduled to be transmitted, the network device assumes that the terminal device receives or decodes the second PDSCH.

[0256] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or,

[0257] The target PDSCH is the last PDSCH in the first PDSCH.

[0258] For example, the terminal device receives the first PDSCH sent by the network device using HARQ y, such as Fig.11 In case 1, the earliest time when HARQ y can be rescheduled is the third time after the last symbol of the first PDSCH transmission. That is, when the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the HARQ y after the third time after the last symbol of the first PDSCH transmission, the terminal device receives or decodes the second PDSCH.

[0259] For another example, the terminal device receives the first PDSCH sent by the network device using HARQ y, where the first PDSCH includes PDSCH 1 and PDSCH 2. Fig.11 In case 2, the earliest time that HARQ y can be rescheduled is the third time after the last symbol transmitted by PDSCH 2 in the first PDSCH (the last PDSCH in the first PDSCH). That is to say, when the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the HARQ y the third time after the last symbol transmitted by PDSCH 2 in the first PDSCH, the terminal device receives or decodes the second PDSCH.

[0260] For another example, the terminal device receives the first PDSCH sent by the network device using HARQ y, where the first PDSCH includes PDSCH 1 and PDSCH 2. Fig.11 In case 3, the earliest time when HARQ y can be rescheduled is the third time after the last symbol transmitted by PDSCH 1 in the first PDSCH (the first PDSCH in the first PDSCH), that is, when the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the HARQ y the third time after the last symbol transmitted by PDSCH 1 in the first PDSCH, the terminal device receives or decodes the second PDSCH.

[0261] Optionally, in some other embodiments, in S410, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, which may specifically include at least one of the following Examples 4 to 6.

[0262] Example 4, the terminal device receives the first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and the terminal device does not expect to receive the second PDCCH scheduled by the network device to transmit the second PDSCH by the first downlink HARQ process within the third time duration of the last symbol of the target PDSCH transmission in the first PDSCH. Correspondingly, the network device does not send the second PDCCH scheduled to transmit the second PDSCH by the first downlink HARQ process within the third time duration after the last symbol of the target PDSCH transmission in the first PDSCH.

[0263] Example 5, the terminal device receives the first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and in the case where the terminal device receives the second PDCCH scheduling the network device to transmit the second PDSCH by the first downlink HARQ process within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the terminal device does not receive or decode the second PDSCH. Correspondingly, in the case where the terminal device receives the second PDCCH scheduling the network device to transmit the second PDSCH by the first downlink HARQ process within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the network device assumes that the terminal device does not receive or decode the second PDSCH.

[0264] Example 6, the terminal device receives the first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and in the case where the terminal device receives the second PDCCH that schedules the network device to transmit the second PDSCH by the first downlink HARQ process after the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the terminal device receives or decodes the second PDSCH. Correspondingly, in the case where the terminal device receives the second PDCCH that schedules the network device to transmit the second PDSCH by the first downlink HARQ process after the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the network device assumes that the terminal device receives or decodes the second PDSCH.

[0265] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or,

[0266] The target PDSCH is the last PDSCH in the first PDSCH.

[0267] For example, the terminal device receives the first PDSCH sent by the network device using HARQ y, such as Fig.12 In case 1, the earliest time for sending the PDCCH that can reschedule HARQ y is the third time period after the last symbol of the first PDSCH transmission. That is to say, when the terminal device receives the second PDCCH scheduling the HARQ y transmission of the second PDSCH by the network device after the third time period after the last symbol of the first PDSCH transmission, the terminal device receives or decodes the second PDSCH.

[0268] For another example, the terminal device receives the first PDSCH sent by the network device using HARQ y, where the first PDSCH includes PDSCH 1 and PDSCH 2. Fig.12 In case 2, the earliest sending time of the PDCCH that can reschedule HARQ y is the third time period after the last symbol transmitted by PDSCH 2 in the first PDSCH (the last PDSCH in the first PDSCH). That is to say, when the terminal device receives the second PDCCH scheduling the HARQ y to transmit the second PDSCH after the third time period after the last symbol transmitted by PDSCH 2 in the first PDSCH, the terminal device receives or decodes the second PDSCH.

[0269] For another example, the terminal device receives the first PDSCH sent by the network device using HARQ y, where the first PDSCH includes PDSCH 1 and PDSCH 2. Fig.12 In case 3, the earliest sending time of the PDCCH that can reschedule HARQ y is the third time period after the last symbol transmitted by PDSCH 1 in the first PDSCH (the first PDSCH in the first PDSCH). That is to say, when the terminal device receives the second PDCCH scheduling the HARQ y to transmit the second PDSCH after the third time period after the last symbol transmitted by PDSCH 1 in the first PDSCH, the terminal device receives or decodes the second PDSCH.

[0270] Optionally, in some embodiments, when the terminal device is configured with DRX, the terminal device starts a third timer after the last symbol of the target PDSCH transmission in the first PDSCH, wherein the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, or the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDSCH, and the second PDCCH is used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.

[0271] For example, the third timer is used to indicate the minimum duration during which the terminal device does not expect to receive the second PDCCH, or the third timer is used to indicate the minimum duration during which the terminal device does not expect to receive the second PDSCH.

[0272] Optionally, the terminal device starts a fourth timer after the third timer times out, and the fourth timer is used to indicate a time window in which the terminal device may receive the second PDCCH or the second PDSCH.

[0273] For example, the fourth timer is used to indicate the maximum duration that the terminal device may receive the second PDCCH or the second PDSCH.

[0274] Optionally, the network device sends first configuration information to the terminal device, wherein:

[0275] In the case where the terminal device is configured with DRX, the first configuration information is used to configure the terminal device to start a third timer after the last symbol of the target PDSCH transmission in the first PDSCH, wherein the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, or the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDSCH, and the second PDCCH is used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.

[0276] Optionally, the network device sends second configuration information to the terminal device, wherein:

[0277] The second configuration information is used to configure the terminal device to start a fourth timer after the third timer times out, and the fourth timer is used to indicate a time window in which the terminal device may receive the second PDCCH or the second PDSCH.

[0278] Optionally, the fourth timer is a DRX downlink retransmission timer (drx-RetransmissionTimerDL).

[0279] Optionally, the second configuration information includes the fourth timer.

[0280] Optionally, the duration of the third timer is less than or equal to the third duration.

[0281] Optionally, the third timer is a DRX downlink HARQ RTT timer (drx-HARQ-RTT-TimerDL).

[0282] Optionally, the first configuration information includes the third timer.

[0283] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or,

[0284] The target PDSCH is the last PDSCH in the first PDSCH.

[0285] Optionally, the first PDSCH includes at least two PDSCHs, the at least two PDSCHs are continuous in the time domain, or the at least two PDSCHs occupy at least two continuous time slots in the time domain.

[0286] Optionally, the first PDSCH is scheduled by a PDCCH, or the first PDSCH corresponds to a PDCCH.

[0287] Optionally, the first PDSCH is a PDSCH scheduled by a PDCCH, or the first PDSCH is an SPS PDSCH.

[0288] For example, when the terminal device is configured with DRX, the terminal device receives the first PDSCH sent by the network device using HARQ y, such as Fig.13 In case 1, the terminal device starts the third timer after the last symbol of the first PDSCH transmission, and starts the fourth timer after the third timer times out. In addition, during the operation of the fourth timer, the terminal device receives a second PDSCH sent by the network device using HARQ y, or the terminal device receives a second PDCCH sent by the network device for scheduling the HARQ y transmission of the second PDSCH.

[0289] For another example, when the terminal device is configured with DRX, the terminal device receives the first PDSCH sent by the network device using HARQ y, where the first PDSCH includes PDSCH 1 and PDSCH 2, such as Fig.13 In case 2, the terminal device starts the third timer after the last symbol of PDSCH 2 (the last PDSCH in the first PDSCH) in the first PDSCH is transmitted, and starts the fourth timer after the third timer times out. In addition, during the operation of the fourth timer, the terminal device receives a second PDSCH sent by the network device using HARQ y, or the terminal device receives a second PDCCH sent by the network device for scheduling the HARQ y transmission of the second PDSCH.

[0290] For another example, when the terminal device is configured with DRX, the terminal device receives the first PDSCH sent by the network device using HARQ y, where the first PDSCH includes PDSCH 1 and PDSCH 2, such as Fig.13In case 3, the terminal device starts the third timer after the last symbol of PDSCH 1 (the first PDSCH in the first PDSCH) in the first PDSCH is transmitted, and starts the fourth timer after the third timer times out. In addition, during the operation of the fourth timer, the terminal device receives a second PDSCH sent by the network device using HARQ y, or the terminal device receives a second PDCCH sent by the network device for scheduling the HARQ y transmission of the second PDSCH.

[0291] It should be noted that the above HARQ y is a specific example of the first downlink HARQ process and does not constitute a limitation to the present application.

[0292] Optionally, in the embodiment of the present application, the third duration may be determined according to at least one of the following:

[0293] PDSCH decoding time value;

[0294] T proc,1 Processing time, where T proc,1 It is determined based on the PDSCH decoding time value;

[0295] K 1 value, or K 1 The time domain position of the PUCCH resource indicated by the value, where K 1 It is indicated by the HARQ feedback timing indication information field in the DCI format, or K 1 It is provided by the HARQ feedback timing set;

[0296] K offset value, or K offset The time domain position of the PUCCH resource indicated by the value, where K offset The value is indicated by the network device through at least one of a system message, an RRC message, a Media Access Control Control Element (MAC CE) and a DCI;

[0297] K 1 +K offset value, or K 1 +K offset The time domain position of the PUCCH resource indicated by the value, where K 1 +K offset It is indicated by the HARQ feedback timing indication information field in the DCI format, or K 1 +K offset is provided by the HARQ feedback timing set; or, K 1It is indicated by the HARQ feedback timing indication information field in the DCI format, or K 1 is provided by the HARQ feedback timing set, K offset The value is indicated by the network device through at least one of a system message, an RRC message, a MAC CE, and a DCI;

[0298] The processing time of the network equipment to prepare to send PDSCH;

[0299] The larger value between the PDSCH decoding time value and the processing time value of the network device preparing to send the PDSCH;

[0300] The smaller value between the PDSCH decoding time value and the processing time value of the network device to prepare to send PDSCH.

[0301] Optionally, when the HARQ feedback timing set includes multiple values, K 1 It is indicated by the HARQ feedback timing indication information field in the DCI format; when the HARQ feedback timing set includes a value, K 1 It is provided through a HARQ feedback timing set, wherein the DCI format does not include a HARQ feedback timing indication information field.

[0302] Optionally, the third duration is determined according to a time domain position of a PUCCH resource, including:

[0303] The third duration is determined according to the time domain position corresponding to the first symbol of the PUCCH resource; or,

[0304] The third duration is determined according to a time domain position corresponding to the last symbol of the PUCCH resource.

[0305] For example, the end position of the third duration is determined according to the start position of the first symbol of the PUCCH resource.

[0306] For another example, the end position of the third duration is determined according to the end position of the last symbol of the PUCCH resource.

[0307] Optionally, the PDSCH decoding time value is related to the subcarrier spacing configuration of the PDSCH.

[0308] It should be noted that the PDSCH decoding time value such as N or N1 may be a PDSCH decoding time value of a terminal device. In addition, the PDSCH decoding time value corresponding to the UE's processing capability 1 such as N1 and the PDSCH decoding time value corresponding to the UE's processing capability 2 such as N1 may be different.

[0309] Optionally, T proc,1 It can be determined according to the above formula 2.

[0310] It should be noted that the meaning of each parameter in Formula 2 can refer to the definition in Section 5.3 of the communication protocol standard TS38.214, and for the sake of brevity, it will not be discussed here. In addition, different communication protocol standards may revise or update the meaning of each parameter in Formula 2, and this application can be adjusted according to the corresponding communication protocol.

[0311] As an example but not a limitation, the value of the third time length is related to the subcarrier spacing configuration μ of the PDSCH. When μ=0, the third time length is 13 symbols, when μ=1, the third time length is 13 symbols, when μ=2, the third time length is 20 symbols, and when μ=3, the third time length is 24 symbols.

[0312] Therefore, in the embodiment of the present application, when the first downlink HARQ process corresponds to the first state, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to the third duration, thereby enhancing the downlink HARQ scheduling restriction and ensuring that the processing timing of the terminal device will not be out of order.

[0313] Combination of the above Figures 5 to 13 , describes in detail the method embodiment of the present application, and the following is combined with Figures 14 to 20 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.

[0314] Fig.14 FIG. 5 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application. Fig.14 As shown, the terminal device 500 includes:

[0315] The communication unit 510 is used to transmit a physical uplink shared channel PUSCH using a first uplink hybrid automatic repeat request HARQ process, wherein the first uplink HARQ process corresponds to a first state, and the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration.

[0316] Optionally, the terminal device 500 further includes a processing unit 520 .

[0317] The time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to the first duration, including:

[0318] The communication unit 510 is further configured to receive a first physical downlink control channel PDCCH, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH;

[0319] The processing unit 520 is configured to not expect to use the first uplink HARQ process to transmit the second PUSCH within the first duration after the last symbol of the target PUSCH transmission scheduled in the first PUSCH; or,

[0320] In a case where the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process within the first duration after the last symbol of the target PUSCH transmission in the first PUSCH, the communication unit 510 is further configured not to transmit the second PUSCH; or,

[0321] When the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process after the first time length after the last symbol of the target PUSCH transmission in the first PUSCH, the communication unit 510 is also used to transmit the second PUSCH.

[0322] Optionally, when the terminal device is configured with discontinuous reception DRX, the communication unit 510 is further configured to start the first timer after the last symbol of the target PUSCH transmission in the first PUSCH, or the processing unit 520 is further configured to start the first timer after the last symbol of the first PDCCH transmission;

[0323] The first timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, and the second PDCCH is used to schedule the terminal device to transmit a second PUSCH using the first uplink HARQ process.

[0324] Optionally, the processing unit 520 is further used to start a second timer after the first timer times out, and the second timer is used to indicate a time window in which the terminal device may receive the second PDCCH.

[0325] Optionally, the second timer is a DRX uplink retransmission timer.

[0326] Optionally, the duration of the first timer is less than or equal to the first duration.

[0327] Optionally, the first timer is a DRX uplink HARQ round trip transmission time RTT timer.

[0328] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or,

[0329] The target PUSCH is the last PUSCH in the first PUSCH.

[0330] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are continuous in the time domain, or the at least two PUSCHs occupy at least two continuous time slots in the time domain.

[0331] Optionally, the first PUSCH is scheduled by a PDCCH, or the first PUSCH corresponds to a PDCCH.

[0332] Optionally, the first PUSCH is a PUSCH scheduled by PDCCH, or, the first PUSCH is a semi-persistently scheduled SPS PUSCH, or, the first PUSCH is a configured authorized CG PUSCH.

[0333] Optionally, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration, including:

[0334] The communication unit 510 is further configured to receive a first physical downlink control channel PDCCH, wherein the uplink grant information carried in the first PDCCH schedules the terminal device to use the first uplink HARQ process to transmit a first PUSCH carrying a first transport block TB;

[0335] In the case where the interval between the end position of the target symbol and the start position of the first uplink symbol of the first PUSCH after considering the influence of the timing advance is less than the second duration, the processing unit 520 is further configured to ignore the first PDCCH, or the terminal device does not transmit the first PUSCH; or,

[0336] In a case where an interval between an end position of the target symbol and a start position of a first uplink symbol of the first PUSCH after considering the timing advance effect is greater than or equal to the second duration, the communication unit 510 is further configured to transmit the first PUSCH;

[0337] Among them, the last PUSCH transmitted using the first uplink HARQ process is the third PUSCH, the third PUSCH includes at least one PUSCH, the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering the timing advance, or the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering the timing advance.

[0338] Optionally, the second duration is based on T proc,2 The processing time is determined by T proc,2 It is determined according to the PUSCH preparation time value.

[0339] Optionally, the first duration is determined according to a PUSCH preparation time value; or,

[0340] The first duration is based on T proc,2 The processing time is determined by T proc,2 is determined based on the PUSCH preparation time value; or,

[0341] The first duration is determined according to a processing time value of a network device receiving a PUSCH; or,

[0342] The first duration is determined according to a larger value of a PUSCH preparation time value and a processing time value of a network device receiving a PUSCH; or,

[0343] The first duration is determined according to a smaller value between a PUSCH preparation time value and a processing time value of a network device receiving a PUSCH.

[0344] Optionally, the PUSCH preparation time value is related to the subcarrier spacing configuration of the PUSCH, or the PUSCH preparation time value is related to the subcarrier spacing configuration of a physical downlink control channel PDCCH that schedules the PUSCH.

[0345] Optionally, the first uplink HARQ process corresponds to a first state, including:

[0346] The first uplink HARQ process is a disabled HARQ process; or,

[0347] The first uplink HARQ process is configured with a disabling parameter.

[0348] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0349] It should be understood that the terminal device 500 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 500 are respectively to implement Figure 5 For the sake of brevity, the corresponding process of the terminal device in the method 200 is not repeated here.

[0350] Fig.15 FIG. 6 shows a schematic block diagram of a network device 600 according to an embodiment of the present application. Fig.15 As shown, the network device 600 includes:

[0351] The processing unit 610 is used to schedule the terminal device to use the first uplink hybrid automatic repeat request HARQ process to transmit the physical uplink shared channel PUSCH, wherein the first uplink HARQ process corresponds to a first state, and the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration.

[0352] Optionally, the network device 600 further includes a communication unit 620 .

[0353] Optionally, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration, including:

[0354] The communication unit 620 is used to send a first physical downlink control channel PDCCH to the terminal device, where the first PDCCH is used to schedule the terminal device to transmit a first PUSCH using the first uplink HARQ process, where the first PUSCH includes at least one PUSCH;

[0355] The processing unit 610 is further configured to not schedule the terminal device to transmit a second PUSCH using the first uplink HARQ process within the first duration after the last symbol of the target PUSCH transmission in the first PUSCH; or,

[0356] In a case where the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process within the first duration after the last symbol of the target PUSCH transmission in the first PUSCH, the processing unit 610 is further configured not to expect to receive the second PUSCH sent by the terminal device; or,

[0357] When the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process after the first time length after the last symbol of the target PUSCH transmission in the first PUSCH, the communication unit 620 is further used to receive the second PUSCH sent by the terminal device.

[0358] Optionally, the communication unit 620 is further configured to send first configuration information to the terminal device, wherein:

[0359] In a case where the terminal device is configured with discontinuous reception DRX, the first configuration information is used to configure the terminal device to start the first timer after the last symbol of the target PUSCH transmission in the first PUSCH, or the first configuration information is used to configure the terminal device to start the first timer after the last symbol of the first PDCCH transmission;

[0360] The first timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, and the second PDCCH is used to schedule the terminal device to transmit a second PUSCH using the first uplink HARQ process.

[0361] Optionally, the communication unit 620 is further configured to send second configuration information to the terminal device, wherein:

[0362] The second configuration information is used to configure the terminal device to start a second timer after the first timer expires, and the second timer is used to indicate a time window in which the terminal device may receive the second PDCCH.

[0363] Optionally, the second timer is a DRX uplink retransmission timer, and / or the second configuration information includes the second timer.

[0364] Optionally, the duration of the first timer is less than or equal to the first duration.

[0365] Optionally, the first timer is a DRX uplink HARQ round trip transmission time RTT timer, and / or the first configuration information includes the first timer.

[0366] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or,

[0367] The target PUSCH is the last PUSCH in the first PUSCH.

[0368] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are continuous in the time domain, or the at least two PUSCHs occupy at least two continuous time slots in the time domain.

[0369] Optionally, the first PUSCH is scheduled by a PDCCH, or the first PUSCH corresponds to a PDCCH.

[0370] Optionally, the first PUSCH is a PUSCH scheduled by PDCCH, or, the first PUSCH is a semi-persistently scheduled SPS PUSCH, or, the first PUSCH is a configured authorized CG PUSCH.

[0371] Optionally, the time interval between two adjacent PUSCH transmissions corresponding to the first uplink HARQ process is greater than or equal to a first duration, including:

[0372] The communication unit 620 is further configured to send a first PDCCH to the terminal device, wherein the uplink grant information carried in the first PDCCH schedules the terminal device to use the first uplink HARQ process to transmit a first PUSCH carrying a first transport block TB;

[0373] In a case where the interval between the end position of the target symbol and the start position of the first uplink symbol of the first PUSCH after considering the influence of the timing advance is less than the second duration, the processing unit 610 is further configured to not expect the terminal device to transmit the first PUSCH; or,

[0374] In a case where the interval between the end position of the target symbol and the start position of the first uplink symbol of the first PUSCH after considering the influence of the timing advance is greater than or equal to the second duration, the communication unit 620 is further configured to receive the first PUSCH sent by the terminal device;

[0375] Among them, the last PUSCH transmitted using the first uplink HARQ process is the third PUSCH, the third PUSCH includes at least one PUSCH, the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering the timing advance, or the target symbol is the later symbol of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering the timing advance.

[0376] Optionally, the second duration is based on T proc,2 The processing time is determined by T proc,2 It is determined according to the PUSCH preparation time value.

[0377] Optionally, the first duration is determined according to a PUSCH preparation time value; or,

[0378] The first duration is based on T proc,2 The processing time is determined by T proc,2 is determined based on the PUSCH preparation time value; or,

[0379] The first duration is determined according to a processing time value of a network device receiving a PUSCH; or,

[0380] The first duration is determined according to a larger value of a PUSCH preparation time value and a processing time value of a network device receiving a PUSCH; or,

[0381] The first duration is determined according to a smaller value between a PUSCH preparation time value and a processing time value of a network device receiving a PUSCH.

[0382] Optionally, the PUSCH preparation time value is related to the subcarrier spacing configuration of the PUSCH, or the PUSCH preparation time value is related to the subcarrier spacing configuration of a physical downlink control channel PDCCH that schedules the PUSCH.

[0383] Optionally, the first uplink HARQ process corresponds to a first state, including:

[0384] The first uplink HARQ process is a disabled HARQ process; or,

[0385] The first uplink HARQ process is configured with a disabling parameter.

[0386] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0387] It should be understood that the network device 600 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 600 are respectively to implement Fig. 9 For the sake of brevity, the corresponding processes of the network device in the method 300 are not repeated here.

[0388] Fig.16 FIG. 7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application. Fig.16 As shown, the terminal device 700 includes:

[0389] The communication unit 710 is used to receive a physical downlink shared channel PDSCH sent by a network device using a first downlink hybrid automatic repeat request HARQ process, wherein the first downlink HARQ process corresponds to a first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

[0390] Optionally, the terminal device 700 further includes a processing unit 720 .

[0391] Optionally, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including:

[0392] The communication unit 710 is further configured to receive a first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH;

[0393] The processing unit 720 is configured to not expect to receive or decode a second PDSCH sent by the network device using the first downlink HARQ process within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH; or,

[0394] In the case where the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the communication unit 710 is used to not receive or decode the second PDSCH; or,

[0395] When the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission in the first PDSCH, the communication unit 710 is used to receive or decode the second PDSCH.

[0396] Optionally, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including:

[0397] The communication unit 710 is further configured to receive a first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH;

[0398] The processing unit 720 is configured to not expect to receive the second PDCCH for scheduling the first downlink HARQ process to transmit the second PDSCH within the third time period after the last symbol of the target PDSCH in the first PDSCH is transmitted; or,

[0399] In the case where the terminal device receives the second PDCCH that schedules the first downlink HARQ process to transmit the second PDSCH within the third time period after the last symbol of the target PDSCH in the first PDSCH is transmitted, the communication unit is further configured not to receive or decode the second PDSCH; or,

[0400] When the terminal device receives the second PDCCH scheduled by the network device to transmit the second PDSCH through the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission in the first PDSCH, the communication unit is also used to receive or decode the second PDSCH.

[0401] Optionally, when the terminal device is configured for discontinuous reception DRX, the processing unit 720 is further used to start a third timer after the last symbol of the target PDSCH transmission in the first PDSCH, wherein the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, or the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDSCH, and the second PDCCH is used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.

[0402] Optionally, the processing unit 720 is further used to start a fourth timer after the third timer times out, and the fourth timer is used to indicate a time window in which the terminal device may receive the second PDCCH or the second PDSCH.

[0403] Optionally, the fourth timer is a DRX downlink retransmission timer.

[0404] Optionally, the duration of the third timer is less than or equal to the third duration.

[0405] Optionally, the third timer is a DRX downlink HARQ round trip transmission time RTT timer.

[0406] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or,

[0407] The target PDSCH is the last PDSCH in the first PDSCH.

[0408] Optionally, the first PDSCH includes at least two PDSCHs, the at least two PDSCHs are continuous in the time domain, or the at least two PDSCHs occupy at least two continuous time slots in the time domain.

[0409] Optionally, the first PDSCH is scheduled by a PDCCH, or the first PDSCH corresponds to a PDCCH.

[0410] Optionally, the first PDSCH is a PDSCH scheduled by PDCCH, or the first PDSCH is a semi-persistently scheduled SPSPDSCH.

[0411] Optionally, the third duration is determined according to a PDSCH decoding time value; or,

[0412] The third duration is based on T proc,1 The processing time is determined by T proc,1 is determined according to the PDSCH decoding time value; or,

[0413] The third duration is based on K 1value, or the third duration is determined according to K 1 The time domain position of the physical uplink control channel PUCCH resource indicated by the value is determined, where K 1 It is indicated by the HARQ feedback timing indication information field in the DCI format, or K 1 is provided by a HARQ feedback timing set; or,

[0414] The third duration is based on K offset value, or the third duration is determined according to K offset The time domain position of the PUCCH resource indicated by the value is determined, where K offset The value is indicated by the network device through at least one of a system message, a radio resource control RRC message, a media access control element MAC CE, and a DCI; or,

[0415] The third duration is based on K 1 +K offset value, or the third duration is determined according to K 1 +K offset The time domain position of the PUCCH resource indicated by the value is determined, where K 1 or K 1 +K offset It is indicated by the HARQ feedback timing indication information field in the DCI format, or K 1 or K 1 +K offset is provided by the HARQ feedback timing set, or, K offset The value is indicated by the network device through at least one of a system message, an RRC message, a MAC CE, and a DCI; or,

[0416] The third duration is determined according to the processing time of the network device to prepare to send the PDSCH; or,

[0417] The third duration is determined according to a larger value between a PDSCH decoding time value and a processing time value for the network device to prepare to send the PDSCH; or,

[0418] The third duration is determined according to a smaller value between a PDSCH decoding time value and a processing time value for the network device to prepare to send the PDSCH.

[0419] Optionally, the third duration is determined according to a time domain position of a PUCCH resource, including:

[0420] The third duration is determined according to the time domain position corresponding to the first symbol of the PUCCH resource; or,

[0421] The third duration is determined according to a time domain position corresponding to the last symbol of the PUCCH resource.

[0422] Optionally, the PDSCH decoding time value is related to the subcarrier spacing configuration of the PDSCH.

[0423] Optionally, the first downlink HARQ process corresponds to a first state, including:

[0424] The first downlink HARQ process is a disabled HARQ process; or,

[0425] The first downlink HARQ process is configured with a disabling parameter; or,

[0426] The first downlink HARQ process does not correspond to uplink hybrid automatic repeat request-acknowledgement HARQ-ACK feedback.

[0427] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0428] It should be understood that the terminal device 700 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 700 are respectively to implement Fig.10 For the sake of brevity, the corresponding process of the terminal device in the method 400 is not repeated here.

[0429] Fig.17 FIG. 8 is a schematic block diagram of a network device 800 according to an embodiment of the present application. Fig.17 As shown, the network device 800 includes:

[0430] The communication unit 810 is used to use the first downlink hybrid automatic repeat request HARQ process to send a physical downlink shared channel PDSCH to the terminal device, wherein the first downlink HARQ process corresponds to a first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

[0431] Optionally, the network device 800 also includes a processing unit 820 .

[0432] Optionally, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including:

[0433] The communication unit 810 is further configured to send a first PDSCH to the terminal device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH;

[0434] The processing unit 820 is further configured to not use the first downlink HARQ process to send a second PDSCH within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH; or,

[0435] In the case where the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the processing unit 820 is further configured to assume that the terminal device does not receive or decode the second PDSCH; or,

[0436] In the case where the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission in the first PDSCH, the processing unit 820 is also used to assume that the terminal device receives or decodes the second PDSCH.

[0437] Optionally, the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including:

[0438] The communication unit 810 is further configured to send a first PDSCH to the terminal device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH;

[0439] The communication unit 810 is further configured to not send a second PDCCH for scheduling the first downlink HARQ process to transmit a second PDSCH within the third duration after the last symbol of the target PDSCH in the first PDSCH is transmitted; or,

[0440] In the case where the terminal device receives the second PDCCH in which the network device schedules the first downlink HARQ process to transmit the second PDSCH within the third time period after the last symbol of the target PDSCH transmission scheduled in the first PDSCH, the processing unit 820 is further configured to assume that the terminal device does not receive or decode the second PDSCH; or,

[0441] In the case where the terminal device receives the second PDCCH scheduled by the network device to transmit the second PDSCH through the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission scheduled in the first PDSCH, the processing unit 820 is also used to assume that the terminal device receives or decodes the second PDSCH.

[0442] Optionally, the communication unit 810 is further configured to send first configuration information to the terminal device, wherein:

[0443] In the case where the terminal device is configured for discontinuous reception DRX, the first configuration information is used to configure the terminal device to start a third timer after the last symbol of the target PDSCH transmission in the first PDSCH, wherein the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDCCH, or the third timer is used to indicate a time window in which the terminal device does not expect to receive a second PDSCH, and the second PDCCH is used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.

[0444] Optionally, the communication unit 810 is further configured to send second configuration information to the terminal device, wherein:

[0445] The second configuration information is used to configure the terminal device to start a fourth timer after the third timer times out, and the fourth timer is used to indicate a time window in which the terminal device may receive the second PDCCH or the second PDSCH.

[0446] Optionally, the fourth timer is a DRX downlink retransmission timer, and / or the second configuration information includes the fourth timer.

[0447] Optionally, the duration of the third timer is less than or equal to the third duration.

[0448] Optionally, the third timer is a DRX downlink HARQ round trip transmission time RTT timer, and / or the first configuration information includes the third timer.

[0449] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or,

[0450] The target PDSCH is the last PDSCH in the first PDSCH.

[0451] Optionally, the first PDSCH includes at least two PDSCHs, the at least two PDSCHs are continuous in the time domain, or the at least two PDSCHs occupy at least two continuous time slots in the time domain.

[0452] Optionally, the first PDSCH is scheduled by a PDCCH, or the first PDSCH corresponds to a PDCCH.

[0453] Optionally, the first PDSCH is a PDSCH scheduled by PDCCH, or the first PDSCH is a semi-persistently scheduled SPSPDSCH.

[0454] Optionally, the third duration is determined according to a PDSCH decoding time value; or,

[0455] The third duration is based on T proc,1 The processing time is determined by T proc,1 is determined according to the PDSCH decoding time value; or,

[0456] The third duration is based on K 1 value, or the third duration is determined according to K 1 The time domain position of the physical uplink control channel PUCCH resource indicated by the value is determined, where K 1 It is indicated by the HARQ feedback timing indication information field in the DCI format, or K 1 is provided by a HARQ feedback timing set; or,

[0457] The third duration is based on K offset value, or the third duration is determined according to K offset The time domain position of the PUCCH resource indicated by the value is determined, where K offset The value is indicated by the network device through at least one of a system message, a radio resource control RRC message, a media access control element MAC CE, and a DCI; or,

[0458] The third duration is based on K 1 +K offset value, or the third duration is determined according to K 1 +K offset The time domain position of the PUCCH resource indicated by the value is determined, where K 1 or K 1 +K offset It is indicated by the HARQ feedback timing indication information field in the DCI format, or K 1 or K 1 +K offset is provided by the HARQ feedback timing set, or, K offset The value is indicated by the network device through at least one of a system message, an RRC message, a MAC CE, and a DCI; or,

[0459] The third duration is determined according to the processing time of the network device to prepare to send the PDSCH; or,

[0460] The third duration is determined according to a larger value between a PDSCH decoding time value and a processing time value for the network device to prepare to send the PDSCH; or,

[0461] The third duration is determined according to a smaller value between a PDSCH decoding time value and a processing time value for the network device to prepare to send the PDSCH.

[0462] Optionally, the third duration is determined according to a time domain position of a PUCCH resource, including:

[0463] The third duration is determined according to the time domain position corresponding to the first symbol of the PUCCH resource; or,

[0464] The third duration is determined according to a time domain position corresponding to the last symbol of the PUCCH resource.

[0465] Optionally, the PDSCH decoding time value is related to the subcarrier spacing configuration of the PDSCH.

[0466] Optionally, the first downlink HARQ process corresponds to a first state, including:

[0467] The first downlink HARQ process is a disabled HARQ process; or,

[0468] The first downlink HARQ process is configured with a disabling parameter; or,

[0469] The first downlink HARQ process does not correspond to uplink hybrid automatic repeat request-acknowledgement HARQ-ACK feedback.

[0470] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0471] It should be understood that the network device 800 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 800 are respectively to implement Fig.10 For the sake of brevity, the corresponding processes of the network device in the method 400 are not repeated here.

[0472] Fig.18 It is a schematic structural diagram of a communication device 900 provided in an embodiment of the present application. Fig.18 The communication device 900 shown includes a processor 910, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0473] Alternatively, if Fig.18 As shown, the communication device 900 may further include a memory 920. The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0474] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0475] Alternatively, if Fig.18 As shown, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0476] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna, and the number of antennas may be one or more.

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

[0478] Optionally, the communication device 900 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0479] Fig.19 It is a schematic structural diagram of the device of an embodiment of the present application. Fig.19 The device 1000 shown includes a processor 1010, and the processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0480] Alternatively, if Fig.19 As shown, the apparatus 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0481] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0482] Optionally, the apparatus 1000 may further include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0483] Optionally, the apparatus 1000 may further include an output interface 1040. The processor 1010 may control the output interface 1040 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0484] 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 in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0485] Optionally, the apparatus may be applied to a mobile terminal / terminal device in an embodiment of the present application, and the apparatus may implement corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0486] Optionally, the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0487] Fig. 20 1 is a schematic block diagram of a communication system 1100 provided in an embodiment of the present application. Fig. 20 As shown, the communication system 1100 includes a terminal device 1110 and a network device 1120 .

[0488] Among them, the terminal device 1110 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0489] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. 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.

[0490] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0491] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0492] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0493] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0494] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0495] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0496] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0497] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

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

[0499] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0500] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0501] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

[0503] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0504] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0505] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0506] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

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

Claims

1. A channel transmission method, characterized in that: include: The terminal device receives a physical downlink shared channel PDSCH sent by a network device using a first downlink hybrid automatic repeat request HARQ process, wherein the first downlink HARQ process corresponds to a first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

2. The method according to claim 1, characterized in that The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including: The terminal device receives a first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; The terminal device does not expect to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH; or, In a case where the terminal device is scheduled to receive or decode a second PDSCH sent by the network device using the first downlink HARQ process within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the terminal device does not receive or decode the second PDSCH; or, When the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission in the first PDSCH, the terminal device receives or decodes the second PDSCH.

3. The method according to claim 1, characterized in that The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including: The terminal device receives a first PDSCH sent by the network device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; The terminal device does not expect to receive the second PDCCH for scheduling the first downlink HARQ process to transmit the second PDSCH within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH; or, In the case where the terminal device receives the second PDCCH for scheduling the first downlink HARQ process to transmit the second PDSCH within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the terminal device does not receive or decode the second PDSCH; or, When the terminal device receives the second PDCCH scheduled by the network device to transmit the second PDSCH by the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission in the first PDSCH, the terminal device receives or decodes the second PDSCH.

4. The method according to any one of claims 2 to 3, characterized in that The target PDSCH is the first PDSCH in the first PDSCH; or, The target PDSCH is the last PDSCH in the first PDSCH.

5. The method according to any one of claims 2 to 4, characterized in that The first PDSCH includes at least two PDSCHs, and the at least two PDSCHs are continuous in the time domain, or the at least two PDSCHs occupy at least two continuous time slots in the time domain.

6. The method according to any one of claims 1 to 5, characterized in that The third duration is determined according to the PDSCH decoding time value; or, The third duration is based on T proc,1 The processing time is determined by T proc,1 is determined according to the PDSCH decoding time value; or, The third duration is determined according to the K1 value, or the third duration is determined according to the time domain position of the physical uplink control channel PUCCH resource indicated by the K1 value, wherein K1 is indicated by the HARQ feedback timing indication information field in the DCI format, or K1 is provided by the HARQ feedback timing set; or, The third duration is based on K offset value, or the third duration is determined according to K offset The time domain position of the PUCCH resource indicated by the value is determined, where K offset The value is indicated by the network device through at least one of a system message, a radio resource control RRC message, a media access control element MAC CE, and a DCI; or, The third duration is based on K1+K offset value, or the third duration is determined according to K1+K offset The time domain position of the PUCCH resource indicated by the value is determined, where K1 or K1+K offset It is indicated by the HARQ feedback timing indication information field in the DCI format, or K1 or K1+K offset is provided by the HARQ feedback timing set, or, K offset The value is indicated by the network device through at least one of a system message, an RRC message, a MAC CE, and a DCI; or, The third duration is determined according to the processing time of the network device to prepare to send the PDSCH; or, The third duration is determined according to the larger value of the PDSCH decoding time value and the processing time value of the network device preparing to send the PDSCH; or, The third duration is determined according to a smaller value between a PDSCH decoding time value and a processing time value for the network device to prepare to send the PDSCH.

7. The method according to claim 6, characterized in that The PDSCH decoding time value is related to the subcarrier spacing configuration of the PDSCH.

8. The method according to any one of claims 1 to 7, characterized in that The first downlink HARQ process corresponds to a first state, including: The first downlink HARQ process is a disabled HARQ process; or, The first downlink HARQ process is configured with a disabling parameter; or, The first downlink HARQ process does not correspond to uplink hybrid automatic repeat request-acknowledgement HARQ-ACK feedback.

9. A channel transmission method, characterized in that: include: The network device uses the first downlink hybrid automatic repeat request HARQ process to send a physical downlink shared channel PDSCH to the terminal device, wherein the first downlink HARQ process corresponds to a first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

10. The method according to claim 9, characterized in that The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including: The network device sends a first PDSCH to the terminal device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; The network device does not use the first downlink HARQ process to send the second PDSCH within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH; or, In a case where the terminal device is scheduled to receive or decode a second PDSCH sent by the network device using the first downlink HARQ process within the third duration after the last symbol of the target PDSCH transmission in the first PDSCH, the network device assumes that the terminal device does not receive or decode the second PDSCH; or, When the terminal device is scheduled to receive or decode the second PDSCH sent by the network device using the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission in the first PDSCH, the network device assumes that the terminal device receives or decodes the second PDSCH.

11. The method according to claim 9, characterized in that The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration, including: The network device sends a first PDSCH to the terminal device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; The network device does not send a second PDCCH for scheduling the first downlink HARQ process to transmit a second PDSCH within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH; or, In the case where the terminal device receives the second PDCCH for scheduling the first downlink HARQ process to transmit the second PDSCH within the third time period after the last symbol of the target PDSCH transmission in the first PDSCH, the network device assumes that the terminal device does not receive or decode the second PDSCH; or, When the terminal device receives the second PDCCH scheduled by the network device to transmit the second PDSCH by the first downlink HARQ process after the third time length after the last symbol of the target PDSCH transmission in the first PDSCH, the network device assumes that the terminal device receives or decodes the second PDSCH.

12. The method according to any one of claims 10 to 11, characterized in that The target PDSCH is the first PDSCH in the first PDSCH; or, The target PDSCH is the last PDSCH in the first PDSCH.

13. The method according to any one of claims 10 to 12, characterized in that The first PDSCH includes at least two PDSCHs, and the at least two PDSCHs are continuous in the time domain, or the at least two PDSCHs occupy at least two continuous time slots in the time domain.

14. The method according to any one of claims 9 to 13, characterized in that The third duration is determined according to the PDSCH decoding time value; or, The third duration is based on T proc,1 The processing time is determined by T proc,1 is determined according to the PDSCH decoding time value; or, The third duration is determined according to the K1 value, or the third duration is determined according to the time domain position of the physical uplink control channel PUCCH resource indicated by the K1 value, wherein K1 is indicated by the HARQ feedback timing indication information field in the DCI format, or K1 is provided by the HARQ feedback timing set; or, The third duration is based on K offset value, or the third duration is determined according to K offset The time domain position of the PUCCH resource indicated by the value is determined, where K offset The value is indicated by the network device through at least one of a system message, a radio resource control RRC message, a media access control element MAC CE, and a DCI; or, The third duration is based on K1+K offset value, or the third duration is determined according to K1+K offset The time domain position of the PUCCH resource indicated by the value is determined, where K1 or K1+K offset It is indicated by the HARQ feedback timing indication information field in the DCI format, or K1 or K1+K offset is provided by the HARQ feedback timing set, or, K offset The value is indicated by the network device through at least one of a system message, an RRC message, a MAC CE, and a DCI; or, The third duration is determined according to the processing time of the network device to prepare to send the PDSCH; or, The third duration is determined according to the larger value of the PDSCH decoding time value and the processing time value of the network device preparing to send the PDSCH; or, The third duration is determined according to a smaller value between a PDSCH decoding time value and a processing time value for the network device to prepare to send the PDSCH.

15. The method according to claim 14, characterized in that The PDSCH decoding time value is related to the subcarrier spacing configuration of the PDSCH.

16. The method according to any one of claims 9 to 15, characterized in that The first downlink HARQ process corresponds to a first state, including: The first downlink HARQ process is a disabled HARQ process; or, The first downlink HARQ process is configured with a disabling parameter; or, The first downlink HARQ process does not correspond to uplink hybrid automatic repeat request-acknowledgement HARQ-ACK feedback.

17. A terminal device, characterized in that: include: A communication unit is used to receive a physical downlink shared channel PDSCH sent by a network device using a first downlink hybrid automatic repeat request HARQ process, wherein the first downlink HARQ process corresponds to a first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

18. A network device, characterized in that: include: A communication unit is used to use a first downlink hybrid automatic repeat request HARQ process to send a physical downlink shared channel PDSCH to a terminal device, wherein the first downlink HARQ process corresponds to a first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to a third duration.

19. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 8.

20. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 9 to 16.

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

22. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 9 to 16.

23. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 8.

24. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 9 to 16.

25. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 1 to 8.

26. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 9 to 16.

27. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 8.

28. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 9 to 16.

Images