Channel transmission methods, terminal equipment, and network equipment
By setting time interval limits for HARQ processes in non-terrestrial network systems, the problem of out-of-order processing by terminal devices is solved, enabling more reliable and efficient data transmission.
Patent Information
- Application Number
- CN202411539840.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-29
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2040-09-29
AI Technical Summary
In non-terrestrial network systems, how should the scheduling constraints for downlink and uplink transmissions be designed when the Hybrid Automatic Repeat Request (HARQ) process is disabled to avoid out-of-order processing by terminal devices?
By setting the time interval between two adjacent PUSCH or PDSCH transmissions to be greater than or equal to a specific duration when the HARQ process is disabled, the terminal device is ensured to have enough time to process the signal and avoid out-of-order transmission.
The HARQ scheduling constraints have been enhanced, ensuring the orderly processing sequence of terminal devices and improving the reliability and efficiency of data transmission.
Smart Images

Figure CN119421258B_ABST
Abstract
Description
[0001] This application is a divisional application of the application filed on September 29, 2020, with application number 202080103271.3 and entitled "Method for Channel Transmission, Terminal Equipment and Network Equipment". Technical Field
[0002] This application relates to the field of communications, and more specifically, to a method for channel transmission, a terminal device, and a network device. Background Technology
[0003] The 5G New Radio (5G NR) system defines deployment scenarios for non-terrestrial networks (NTN), including satellite networks. Leveraging the wide-area coverage of satellites, NTN systems can ensure the continuity of 5G NR services. Furthermore, to increase data transmission throughput and reduce the impact of round-trip time (RTT) in NTN systems, a Hybrid Automatic Repeat Request (HARQ) process is introduced. In this context, how to design downlink and uplink scheduling constraints to enhance HARQ scheduling constraints in NTN systems and ensure that the processing timing of terminal devices does not become out of order is a key challenge. Summary of the Invention
[0004] This application provides a channel transmission method, a terminal device, and a network device. When the HARQ process is disabled, the HARQ scheduling constraints are enhanced to ensure that the processing timing of the terminal device will not be out of order.
[0005] Firstly, a method for channel transmission is provided, the method comprising: The terminal device uses a 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.
[0006] Optionally, the first uplink HARQ process corresponds to a first state, including: The first uplink HARQ process is a disabled HARQ process; or, The first uplink HARQ process is configured to disable parameters.
[0007] Secondly, a method for channel transmission is provided, the method comprising: 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.
[0008] Optionally, the first uplink HARQ process corresponds to a first state, including: The first uplink HARQ process is a disabled HARQ process; or, The first uplink HARQ process is configured to disable parameters.
[0009] Thirdly, a method for channel transmission is provided, the method comprising: The terminal device receives a PDSCH sent by the network device using a 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.
[0010] Optionally, 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 to disable parameters; or, The first downlink HARQ process does not correspond to an uplink Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) response.
[0011] Fourthly, a method for channel transmission is provided, the method comprising: The network device sends PDSCH to the terminal device using a 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.
[0012] Optionally, 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 to disable parameters; or, The first downlink HARQ process does not correspond to uplink HARQ-ACK feedback.
[0013] Fifthly, a terminal device is provided for performing the method described in the first aspect above.
[0014] Specifically, the terminal device includes a functional module for performing the method described in the first aspect above.
[0015] In a sixth aspect, a network device is provided for performing the method described in the second aspect above.
[0016] Specifically, the network device includes a functional module for performing the method described in the second aspect above.
[0017] In a seventh aspect, a terminal device is provided for performing the method described in the third aspect above.
[0018] Specifically, the terminal device includes a functional module for performing the method described in the third aspect above.
[0019] Eighthly, a network device is provided for performing the method described in the fourth aspect above.
[0020] Specifically, the network device includes a functional module for performing the method described in the fourth aspect above.
[0021] A ninth aspect provides a terminal device including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method described in the first aspect.
[0022] In a tenth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to perform the method described in the second aspect above.
[0023] Eleventhly, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method described in the third aspect above.
[0024] In a twelfth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to perform the method described in the fourth aspect above.
[0025] In a thirteenth aspect, an apparatus is provided for implementing the method in any one of the first to fourth aspects described above.
[0026] Specifically, the device includes a processor for retrieving and running a computer program from a memory, causing a device equipped with the device to perform the method described in any of the first to fourth aspects above.
[0027] In a fourteenth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the methods of any one of the first to fourth aspects described above.
[0028] In a fifteenth aspect, a computer program product is provided, comprising computer program instructions that cause a computer to perform the methods of any one of the first to fourth aspects described above.
[0029] In a sixteenth aspect, a computer program is provided that, when run on a computer, causes the computer to perform the methods of any one of the first to fourth aspects described above.
[0030] Through the technical solutions described in the first and second aspects above, 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. This enhances the uplink HARQ scheduling constraint and ensures that the processing timing of the terminal device will not be out of order.
[0031] Through the technical solutions described in the third and fourth aspects above, 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. This enhances the downlink HARQ scheduling constraint and ensures that the processing timing of the terminal device will not be out of order. Attached Figure Description
[0032] Figures 1A-1C This is a schematic diagram illustrating an application scenario provided in an embodiment of this application.
[0033] Figure 2 This is a schematic diagram illustrating that a certain time interval needs to be met between two PDSCH transmissions, as provided in this application.
[0034] Figure 3 This is a schematic diagram illustrating another requirement for a certain time interval between two PDSCH transmissions, as provided in this application.
[0035] Figure 4 This is a schematic diagram illustrating that a certain time interval needs to be met between two PUSCH transmissions, as provided in this application.
[0036] Figure 5 This is a schematic flowchart of a channel transmission method provided according to an embodiment of this application.
[0037] Figure 6 This is a schematic diagram illustrating that the interval between two PUSCH transmissions needs to meet a first duration, as provided in an embodiment of this application.
[0038] Figure 7 This is a schematic diagram of the first timer and the second timer provided in the embodiments of this application.
[0039] Figure 8 This is a schematic diagram illustrating that the interval between two PUSCH transmissions needs to meet a second duration, as provided in an embodiment of this application.
[0040] Figure 9 This is a schematic flowchart of another channel transmission method provided according to an embodiment of this application.
[0041] Figure 10 This is a schematic flowchart of another channel transmission method provided according to an embodiment of this application.
[0042] Figure 11 This is a schematic diagram illustrating that the interval between two PDSCH transmissions needs to meet a third duration, as provided in an embodiment of this application.
[0043] Figure 12 This is a schematic diagram illustrating another requirement for the interval between two PDSCH transmissions to meet a third duration, as provided in an embodiment of this application.
[0044] Figure 13 This is a schematic diagram of the third and fourth timers provided in the embodiments of this application.
[0045] Figure 14 This is a schematic block diagram of a terminal device provided according to an embodiment of this application.
[0046] Figure 15 This is a schematic block diagram of a network device provided according to an embodiment of this application.
[0047] Figure 16 This is a schematic block diagram of another terminal device provided according to an embodiment of this application.
[0048] Figure 17 This is a schematic block diagram of another network device provided according to an embodiment of this application.
[0049] Figure 18 This is a schematic block diagram of a communication device provided according to an embodiment of this application.
[0050] Figure 19 This is a schematic block diagram of an apparatus provided according to an embodiment of this application.
[0051] Figure 20 This is a schematic block diagram of a communication system provided according to an embodiment of this application. Detailed Implementation
[0052] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.
[0053] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for 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, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-Generation (5G) communication systems, or other communication systems.
[0054] Traditional communication systems typically 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 communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.
[0055] Optionally, the communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, or standalone (SA) network deployment scenarios.
[0056] Optionally, the communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be considered as non-shared spectrum.
[0057] This application describes various embodiments in conjunction with network devices and terminal devices. 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.
[0058] Terminal devices can be stations (STs) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in next-generation communication systems such as NR networks, or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc.
[0059] In the embodiments of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites).
[0060] In the embodiments of this application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, 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 care, 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.
[0061] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0062] In the embodiments of this application, the network device can be a device for communicating with mobile devices. The network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, a relay station or access point, or a network device or base station (gNB) in an in-vehicle device, wearable device, or NR network, or a network device in a future evolved PLMN network or NTN network, etc.
[0063] By way of example and not limitation, in this embodiment, the network device may have mobility characteristics; 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 located on land, water, or other similar locations.
[0064] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.
[0065] For example, the communication system 100 used in the embodiments of this application is as follows: 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, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area.
[0066] For example, Figure 1AThis is a schematic diagram of the architecture of a communication system provided in an embodiment of this 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, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area.
[0067] Figure 1A An exemplary embodiment shows a network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.
[0068] For example, Figure 1B This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application. Please refer to... Figure 1B This includes terminal device 1101 and satellite 1102, which can communicate wirelessly. The network formed between terminal device 1101 and satellite 1102 can also be called an NTN. Figure 1B In the architecture of the communication system shown, satellite 1102 can function as a base station, and terminal device 1101 and satellite 1102 can communicate directly. In this system architecture, satellite 1102 can be referred to as a network device. Optionally, the communication system may include multiple network devices 1102, and the coverage area of each network device 1102 may include other numbers of terminal devices; this embodiment does not limit this.
[0069] For example, Figure 1C This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application. Please refer to... Figure 1C The network includes terminal device 1201, satellite 1202, and base station 1203. Terminal device 1201 and satellite 1202 can communicate wirelessly, and satellite 1202 can communicate with base station 1203. The network formed by terminal device 1201, satellite 1202, and base station 1203 can also be called an NTN. Figure 1C In the architecture of the communication system shown, satellite 1202 may not function as a base station, and communication between terminal device 1201 and base station 1203 requires relay through satellite 1202. In this system architecture, base station 1203 can be referred to as a network device. Optionally, the communication system may include multiple network devices 1203, and the coverage area of each network device 1203 may include other numbers of terminal devices; this embodiment does not limit this.
[0070] It should be noted that, Figures 1A-1CThis application is merely an example illustrating the system to which this application applies. Of course, the methods shown in the embodiments of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc. This application does not specifically limit these systems.
[0071] Optionally, Figures 1A-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 application does not limit this.
[0072] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. 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, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities. This application embodiment does not limit this.
[0073] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0074] The terminology used in the embodiments section of this application is for the purpose of explaining specific embodiments of this application only, and is not intended to limit this application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.
[0075] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0076] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.
[0077] In this embodiment of the application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.
[0078] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.
[0079] To facilitate a better understanding of the embodiments of this application, the NTN system related to this application will be described.
[0080] NTN typically uses satellite communication to provide communication services to terrestrial users. Compared to terrestrial cellular communication, satellite communication has many unique advantages. First, satellite communication is not limited by the user's geographical location. For example, conventional terrestrial communication cannot cover areas such as oceans, mountains, and deserts where communication equipment cannot be installed, or areas with sparse populations where communication coverage is not available. However, with satellite communication, a single satellite can cover a large area, and since satellites orbit the Earth, theoretically every corner of the Earth can be covered by satellite communication. Second, satellite communication has significant social value. Satellite communication can provide coverage in remote mountainous areas and impoverished countries or regions at a relatively low cost, enabling people in these areas to enjoy advanced voice communication and mobile internet technologies, helping to narrow the digital divide with developed regions and promoting development in these areas. Third, satellite communication has a long range, and the cost does not increase significantly with increasing communication distance. Finally, satellite communication is highly stable and is not affected by natural disasters.
[0081] Communication satellites are classified according to their orbital altitude into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, Highly Elliptical Orbit (HEO) satellites, and so on. Currently, research primarily focuses on LEO and GEO.
[0082] Low Earth orbit (LEO) satellites range in altitude from 500km to 1500km, with corresponding orbital periods of approximately 1.5 to 2 hours. The signal propagation delay for single-hop communication between users is generally less than 20ms. The maximum satellite visibility time is 20 minutes. The short signal propagation distance results in low link loss and low requirements for the transmission power of terminal equipment.
[0083] Among them, the geostationary orbit satellite has an orbital altitude of 35,786 km and an orbital period of 24 hours around the Earth. The signal propagation delay for single-hop communication between users is generally 250 ms.
[0084] To ensure satellite coverage and improve the overall capacity of the satellite communication system, satellites use multi-beam coverage to cover the ground. A single satellite can generate dozens or even hundreds of beams to cover the ground; a single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.
[0085] To facilitate a better understanding of the embodiments of this application, the timing relationships of the NR system and the timing relationship enhancement of the NTN system related to this application will be explained.
[0086] Transmission timing of HARQ-ACK on the Physical Uplink Control Channel (PUCCH): For a PUCCH transmission slot, if the end position of a Physical Downlink Shared Channel (PDSCH) reception is in slot n, or the end position of a Physical Downlink Control Channel (PDCCH) reception indicating semi-persistent scheduling (SPS) PDSCH release is in slot n, the terminal device should transmit HARQ-ACK in slot n+ K The corresponding HARQ-ACK information is transmitted on the PUCCH resource within 1, where K 1 represents 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 by the HARQ feedback timing set (e.g., dl-DataToUL-ACK Provided by the field parameters. K 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.
[0087] To function properly in an NTN system, or rather, to overcome the large transmission delays in NTN systems, the aforementioned timing relationships need to be enhanced. A simple solution is to introduce an offset parameter into the system. K offset And apply this parameter to the relevant timing relationships.
[0088] Transmission timing of HARQ-ACK on PUCCH: For the PUCCH transmission time slot, 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 resource within the system.
[0089] To facilitate a better understanding of the embodiments of this application, the NR HARQ scheduling restrictions related to this application are explained.
[0090] Based on the NR protocol, each terminal device has its own HARQ entity for each serving 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 semi-static configuration of Radio Resource Control (RRC) signaling, based on the network equipment deployment. If the network equipment does not provide corresponding configuration parameters, the default number of downlink HARQ processes is 8, and the maximum number of uplink HARQ processes supported per carrier is 16. Each HARQ process corresponds to a HARQ process identifier (ID). For downlink, the Broadcast Control Channel (BCCH) uses a dedicated broadcast HARQ process. For uplink, the third message (Message 3, Msg 3) in the four-step random process uses HARQ ID 0.
[0091] 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 schedule.
[0092] If the terminal device receives a network device scheduling HARQ x Before the transmission of the first PDSCH by the terminal device to the network device ends, the terminal device does not expect to receive the HARQ scheduled by the network device again. x The second PDSCH transmitted, such as Figure 2As shown. The 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, which can be preset or configured by the network device.
[0093] In a designated scheduling cell, if a terminal device receives a first PDSCH containing a System Information Radio Network Temporary Identity (SI-RNTI) from a network device, the terminal device does not expect the network device to decode the retransmission of the first PDSCH within N symbols following the last symbol of the first PDSCH transmission. Figure 3 As shown, the value of N is related to the subcarrier spacing configuration of the first PDSCH. Related, When = 0, N = 13. When =1, N=13. When =2, N=20. When the value is 3, N = 24.
[0094] The two scheduling constraints mentioned above indicate that a certain time interval must be met between two PDSCH transmissions within the same HARQ process.
[0095] For uplink transmission: The terminal device detects the 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 schedule.
[0096] If the terminal device receives a HARQ from the network device via the first DCI scheduling... x Before the transmission of the first PUSCH from the terminal device to the network device ends, the terminal device does not expect to receive another HARQ scheduled by the network device. x Transmit the second DCI of the second PUSCH, such as Figure 4 As shown, the second DCI corresponds to the DCI format 0_0 or DCI format 0_1 of the scrambling code of the Cell Radio Network Temporary Identity (C-RNTI) or the Modulation and Coding Scheme Cell Radio Network Temporary Identity (MCS-C-RNTI).
[0097] To facilitate a better understanding of the embodiments of this application, the PUSCH transmission and PUCCH transmission in the NR system related to this application will be described.
[0098] In the NR system, the transmission of PUSCH is determined based on the N2 processing capacity.
[0099] If the UE receives uplink grant information from the base station, the uplink grant 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 timing advance effect based on the uplink grant information, for example, based on the start and length indicator value (SLIV) in the uplink grant 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 scheduled DCI.
[0100] Here, symbol L2 is defined as: the next uplink symbol after the end position of the last symbol of the PDCCH carrying the uplink authorization information, wherein the starting position of the cyclic prefix (CP) of the next uplink symbol is later than... T proc,2 Processing time, of which, T proc,2 It is determined based on the Physical Uplink Shared Channel (PUSCH) preparation time N2 value (e.g., in symbols). For example, T proc,2 Determined according to Formula 1 below.
[0101] Formula 1 It should be noted that the meanings of the parameters in Formula 1 can be found in Section 6.4 of the communication protocol standard TS38.214, and will not be discussed further here for the sake of brevity. Furthermore, different communication protocol standards may revise or update the meanings of the parameters in Formula 1, and this application may be adjusted accordingly based on the relevant communication protocol.
[0102] In this context, UE's processing capability 1 and processing capability 2 correspond to different processing capabilities, or in other words, the N2 value corresponding to UE's processing capability 1 is different from the N2 value corresponding to UE's processing capability 2.
[0103] The value of N2 varies depending on the subcarrier spacing.
[0104] In the NR system, the transmission of PUCCH is determined based on the N1 processing capability, or in other words, the transmission of PUCCH is determined based on the UE's PDSCH processing time.
[0105] If the UE receives downlink grant information from the base station, the downlink grant information schedules the UE to receive a PDSCH carrying the target transport block. The UE determines, based on the allocated HARQ-ACK timing information K1 and PUCCH resource indication information, that the HARQ-ACK information corresponding to the scheduled PDSCH is transmitted through the target PUCCH. If the starting position of the first uplink symbol of the target PUCCH, after considering the timing advance effect, is not earlier than symbol L1, then the UE should provide valid HARQ-ACK information for the scheduled PDSCH; otherwise, the UE may not provide valid HARQ-ACK information for the scheduled PDSCH.
[0106] Wherein, 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 start position of the CP of the next uplink symbol is later than... T proc,1 Processing time, of which, T proc,1 It is determined based on the PDSCH decoding time N1 value (e.g., in symbols). For example, T proc,1 Determined according to Formula 2 below.
[0107] Formula 2 It should be noted that the meanings of the parameters in Formula 2 can be found in Section 5.3 of the communication protocol standard TS38.214, and will not be discussed further here for the sake of brevity. Furthermore, different communication protocol standards may revise or update the meanings of the parameters in Formula 2, and this application may be adjusted accordingly based on the relevant communication protocol.
[0108] In this context, UE's processing capability 1 and processing capability 2 correspond to different processing capabilities, or in other words, the N1 value corresponding to UE's processing capability 1 is different from the N1 value corresponding to UE's processing capability 2.
[0109] The value of N1 varies depending on the subcarrier spacing.
[0110] To facilitate a better understanding of the embodiments of this application, the NTN HARQ enhancements related to this application will be described.
[0111] In NTN systems, the communication distance between terminal devices and satellites (or network devices) is very long, resulting in a large RTT (Round-Trip Time). In GEO systems, the RTT can be on the order of hundreds of milliseconds, for example, a maximum RTT of approximately 600 ms. In LEO systems, the RTT can be on the order of tens of milliseconds. Because the RTT of NTN systems is much larger than that of terrestrial communication systems, the HARQ mechanism in existing NR systems is no longer suitable for NTN systems.
[0112] Currently, the HARQ enhancements discussed in the NTN system include: disabling the HARQ process.
[0113] Network devices can configure one or more downlink HARQ processes on terminal devices to be disabled. For downlink HARQ processes configured to be disabled, the network device does not need to receive the HARQ-ACK information corresponding to the Transport Block (TB) transmitted in that HARQ process to reuse the HARQ process for data transmission. Therefore, the network device can use disabled downlink HARQ processes to schedule multiple downlink data packets for the terminal device, thereby increasing data transmission throughput and reducing the impact of RTT. For downlink HARQ processes that are not configured to be disabled, downlink transmission between the network device and the terminal device uses the same HARQ retransmission mechanism as the NR system.
[0114] Network devices can also configure to disable one or more uplink HARQ processes for terminal devices. For a disabled uplink HARQ process, the network device does not need to receive PUSCHs transmitted by the terminal device through that HARQ process to reuse that HARQ process for scheduling other PUSCH transmissions. Therefore, the network device can use a disabled uplink HARQ process to schedule multiple uplink packets for the terminal device, thereby increasing data transmission throughput and reducing the impact of RTT. For uplink HARQ processes that are not configured to be disabled, uplink transmission between the network device and the terminal device uses the same HARQ retransmission mechanism as the NR system.
[0115] In other words, in the NTN system, the HARQ process may correspond to two states, such as the enabled state and the disabled state (also known as the deenabled state). If the HARQ process corresponds to the enabled state, then the function of the HARQ process can be considered to be consistent with that of the NR system.
[0116] In the NTN system, a corresponding HARQ process in the disabled state is introduced. In this case, how to redesign the scheduling constraints of downlink and uplink transmission to enhance the HARQ scheduling constraints in the NTN system and ensure that the processing timing of the terminal device does not have out-of-order problems is an urgent problem to be solved in this application.
[0117] Based on the above problems, this application proposes a channel transmission scheme. In the NTN system, when the HARQ process is disabled, the HARQ scheduling constraint is enhanced to ensure that the processing timing of the terminal device will not be out of order.
[0118] The technical solution of this application is described in detail below through specific embodiments.
[0119] Figure 5 This is a schematic flowchart of a channel transmission method 200 according to an embodiment of this application, such as... Figure 5 As shown, the method 200 may include at least some of the following: S210, the terminal device uses a 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.
[0120] That is, the time interval between the nth PUSCH transmission and the (n-1th PUSCH transmission in the first uplink HARQ process is greater than or equal to the first duration, where n is a positive integer and n≥2.
[0121] Optionally, the first uplink HARQ process corresponds to a first state, including: The first uplink HARQ process is a disabled HARQ process; or, The first uplink HARQ process is configured to disable parameters.
[0122] It should be noted that for the first uplink HARQ process in the disabled state, the network device does not need to receive PUSCH 1 carrying TB 1 transmitted in the first uplink HARQ process, but can reuse the first uplink HARQ process to schedule the transmission of PUSCH 2 carrying TB 2. Here, TB 1 and TB 2 can be the same TB or different TBs. However, when reusing the first uplink HARQ process to transmit TB 2, the network device needs to ensure that the time interval between transmitting PUSCH 1 of TB 1 and transmitting PUSCH 2 of TB 2 is greater than or equal to a first duration, so that the terminal device has sufficient time to process and prepare for the transmission of PUSCH 2 after transmitting PUSCH 1. Furthermore, the DCI for scheduling PUSCH 2 may be received before, after, or during the transmission of PUSCH 1.
[0123] 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.
[0124] Example 1: The terminal device receives a first PDCCH, which is used to schedule the terminal device to transmit a first PUSCH using a first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and the terminal device does not expect to transmit a second PUSCH using the first uplink HARQ process within a first duration after the last symbol of the target PUSCH scheduled to be transmitted in the first PUSCH.
[0125] Example 2: The terminal device receives a first PDCCH, which is used to schedule the terminal device to transmit a first PUSCH using a first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and if the terminal device transmits a second PUSCH using the first uplink HARQ process within a first duration after the last symbol of the target PUSCH in the first PUSCH is scheduled to be transmitted, the terminal device does not transmit the second PUSCH.
[0126] Example 3: The terminal device receives a first PDCCH, which is used to schedule the terminal device to transmit a first PUSCH using a first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and the terminal device transmits the second PUSCH after a first duration following the last symbol of the target PUSCH in the first PUSCH that is scheduled to be transmitted, using the first uplink HARQ process.
[0127] Optionally, at least one PUSCH included in the first PUSCH can 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, where PUSCH 1 is used to transmit the first TB and PUSCH 2 is also used to transmit the first TB.
[0128] Optionally, the first PUSCH corresponds to the k-th PUSCH transmission, and the second PUSCH corresponds to the (k+1)-th PUSCH transmission.
[0129] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or, The target PUSCH is the last PUSCH in this first PUSCH.
[0130] Optionally, the first PUSCH is scheduled via a PDCCH, or the first PUSCH corresponds to a PDCCH.
[0131] Optionally, the first PUSCH is a PDCCH scheduled PUSCH, or the first PUSCH is a semi-persistent scheduling (SPS) PUSCH, or the first PUSCH is a configured grant (CG) PUSCH.
[0132] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are consecutive in the time domain, or the at least two PUSCHs occupy at least two consecutive time slots in the time domain.
[0133] For example, the terminal device receives a first PDCCH, which is used to schedule the terminal device to use HARQ. x Transmit the first PUSCH, such as Figure 6 In case 1, the earliest reschedulable HARQ occurs one time after the last symbol of the first PUSCH transmission. xThe time, that is, the HARQ is used after the terminal device is scheduled to use it a certain duration after the last symbol of the first PUSCH transmission. x In the case of transmitting a second PUSCH, the terminal device transmits the second PUSCH.
[0134] For example, the terminal device receives a first PDCCH, which is used to schedule the terminal device to use HARQ. x Transmit the first PUSCH, which includes PUSCH 1 and PUSCH 2, such as Figure 6 In scenario 2, the earliest reschedulable HARQ occurs one time after the last symbol transmitted in PUSCH 2 (the last PUSCH in the first PUSCH). x The time, that is, the HARQ is used after the first duration following the last symbol of the PUSCH 2 transmission scheduled in the first PUSCH. x In the case of transmitting a second PUSCH, the terminal device transmits the second PUSCH.
[0135] For example, the terminal device receives a first PDCCH, which is used to schedule the terminal device to use HARQ. x Transmit the first PUSCH, which includes PUSCH 1 and PUSCH 2, such as Figure 6 In case 3, the earliest reschedulable HARQ is the first duration after the last symbol transmitted in PUSCH 1 (the first PUSCH in the first PUSCH). x The time, that is, the HARQ is used after the first duration following the last symbol of the PUSCH 1 transmission scheduled in the first PUSCH by the terminal device. x In the case of transmitting a second PUSCH, the terminal device transmits the second PUSCH.
[0136] Optionally, in some embodiments, when the terminal device is configured for Discontinuous Reception (DRX), the terminal device starts a first timer after the last symbol of the target PUSCH transmission in the first PUSCH, or the terminal device starts a first timer after the last symbol of the first PDCCH transmission.
[0137] The first timer is used to indicate the time window during which the terminal device does not expect to receive the second PDCCH, and the second PDCCH is used to schedule the terminal device to use the first uplink HARQ process to transmit the second PUSCH.
[0138] For example, the first timer is used to indicate the minimum duration for which the terminal device does not expect to receive the second PDCCH.
[0139] Alternatively, the first timer can be used to indicate a time window in which the terminal device does not expect to use the first uplink HARQ process to transmit the second PUSCH.
[0140] 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.
[0141] Optionally, the first timer is a DRX uplink HARQ RTT timer ( drx-HARQ-RTT-TimerUL ).
[0142] 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.
[0143] Optionally, the terminal device starts a second timer after the first timer expires. The second timer is used to indicate the time window in which the terminal device may receive the second PDCCH.
[0144] For example, the second timer is used to indicate the maximum duration for which the terminal device may receive the second PDCCH.
[0145] Alternatively, the second timer can be used to indicate a time window in which the terminal device may use the first uplink HARQ process to transmit the second PUSCH.
[0146] For example, the second timer is used to indicate the maximum duration for which the terminal device may use the first uplink HARQ process to transmit the second PUSCH.
[0147] Optionally, the second timer is a DRX uplink retransmission timer. drx-RetransmissionTimerUL ).
[0148] For example, when a terminal device is configured with DRX, the terminal device receives a first PDCCH, which is used to schedule the terminal device to use HARQ. x Transmit the first PUSCH, such as Figure 7 In scenario 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. Furthermore, during the operation of the second timer, the terminal device uses HARQ. x Transmit the second PUSCH.
[0149] For example, when a terminal device is configured with DRX, the terminal device receives a first PDCCH, which is used to schedule the terminal device to use HARQ. x Transmit the first PUSCH, which includes PUSCH 1 and PUSCH 2, such as Figure 7 In scenario 2, the terminal device starts the first timer after the last symbol transmitted in PUSCH 2 (the last PUSCH in the first PUSCH), and starts the second timer after the first timer times out. Furthermore, during the operation of the second timer, the terminal device uses HARQ. x Transmit the second PUSCH.
[0150] For example, when a terminal device is configured with DRX, the terminal device receives a first PDCCH, which is used to schedule the terminal device to use HARQ. x Transmit the first PUSCH, which includes PUSCH 1 and PUSCH 2, such as Figure 7 In scenario 3, the terminal device starts the first timer after the last symbol transmitted in PUSCH 1 (the first PUSCH in the first PUSCH), and starts the second timer after the first timer times out. Furthermore, during the operation of the second timer, the terminal device uses HARQ. x Transmit the second PUSCH.
[0151] For example, when a terminal device is configured with DRX, the terminal device receives a first PDCCH, which is used to schedule the terminal device to use HARQ. x The terminal device transmits a first PUSCH, starts a first timer after the last symbol of the first PDCCH transmission, and starts a second timer after the first timer times out. Furthermore, during the execution of the second timer, the terminal device receives information for scheduling the use of the HARQ. x The second PDCCH transmits the second PUSCH, or the terminal device uses the HARQ. x Transmit the second PUSCH.
[0152] Optionally, in 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 Examples 4 to 5 below.
[0153] Example 4: The terminal device receives a first 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 TB; and if 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 timing advance effect is less than a second duration, the terminal device ignores the first PDCCH, or the terminal device does not transmit the first PUSCH.
[0154] Example 5: The terminal device receives a first 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 TB; and the terminal device transmits the first PUSCH if 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 timing advance effect is greater than or equal to the second duration.
[0155] Wherein, the PUSCH last transmitted using the first uplink HARQ process is the third PUSCH, which includes at least one PUSCH; the target symbol is the later of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering timing advance, or the target symbol is the later of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering timing advance.
[0156] Alternatively, in Examples 4 and 5, the second duration is based on Tproc,2 The processing time is fixed, among which Tproc,2 It is based on the PUSCH preparation time value N2 It's confirmed.
[0157] For 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 The first PUSCH carrying the first TB; the last time the HARQ was used x The transmitted PUSCH is a third PUSCH, which includes PUSCH 1 and PUSCH 2. This third PUSCH is scheduled for transmission by the third DCI carried in the third PDCCH; such as Figure 8In case 1, if the later of the last symbol of the first PDCCH and the last uplink symbol of PUSCH 2 (the last PUSCH in the third PUSCH) after considering the timing advance 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 duration after the last symbol transmitted by PUSCH 2.
[0158] For 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 The first PUSCH carrying the first TB; the last time the HARQ was used x The transmitted PUSCH is a third PUSCH, which includes PUSCH 1 and PUSCH 2. This third PUSCH is scheduled for transmission by the third DCI carried in the third PDCCH; such as Figure 8 In case 2, if 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 considering the timing advance is the last symbol of the first PDCCH (i.e. the target symbol), then the earliest time when the first PUSCH can be sent is the second duration after the last symbol of the first PDCCH transmission.
[0159] It should be noted that the above HARQ x This is a specific example of the first uplink HARQ process and does not constitute a limitation on this application.
[0160] Optionally, in embodiments of this application, the first duration can be determined based on at least one of the following: PUSCH preparation time value; T proc,2 Processing time, of which T proc,2 It is determined based on the PUSCH preparation time value; The processing time value for PUSCH received by the network device; The larger of the PUSCH preparation time value and the processing time value of the network device receiving the PUSCH; The smaller of the PUSCH preparation time value and the processing time value for the network device to receive the PUSCH.
[0161] It should be noted that this PUSCH preparation time value is, for example... N2 This could be the PUSCH preparation time value of the terminal device. Furthermore, the N2 value corresponding to UE's processing capability 1 is different from the N2 value corresponding to UE's processing capability 2.
[0162] Optionally, the first duration and the second duration are equal.
[0163] Optionally, the second duration is longer than the first duration.
[0164] Optionally, the PUSCH preparation time value N2 Related to the subcarrier spacing configuration of the PUSCH, or the PUSCH preparation time value. N2 This is related to the subcarrier spacing configuration of the PDCCH that schedules the PUSCH. For example, the value of N2 differs under different subcarrier spacings.
[0165] For example, if the UE receives uplink grant information from the base station, and this uplink grant 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 timing advance effect based on the uplink grant information, for example, based on the SLIV indication in the uplink grant 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 scheduled DCI.
[0166] Here, symbol L2 is defined as: the next uplink symbol following the end position of the later 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 start position of the CP of the next uplink symbol is later than... Tproc,2 Processing time.
[0167] Optionally, T proc,2 It can be determined according to Formula 1 above.
[0168] It should be noted that the meanings of the parameters in Formula 1 can be found in Section 6.4 of the communication protocol standard TS38.214, and will not be discussed further here for the sake of brevity. Furthermore, different communication protocol standards may revise or update the meanings of the parameters in Formula 1, and this application may be adjusted accordingly based on the relevant communication protocol.
[0169] It should be noted that, in this embodiment, 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. Furthermore, in this embodiment, the first PUSCH corresponds to the k-th PUSCH transmission, the second PUSCH corresponds to the (k+1)-th PUSCH transmission, and the third PUSCH corresponds to the (k-1)-th PUSCH transmission.
[0170] Therefore, in this embodiment, 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. This enhances the uplink HARQ scheduling constraint and ensures that the processing timing of the terminal device will not be out of order.
[0171] The above text combined Figures 5 to 8 The embodiments of the channel transmission method 200 of this application are described in detail from the terminal side, and the following is in conjunction with Figure 9 The embodiments of the channel transmission method 300 of this application are described in detail from the network side. It should be understood that the embodiments of the channel transmission method 300 correspond to the embodiments of the channel transmission method 200, and similar descriptions can be referred to the embodiments of the channel transmission method 200.
[0172] Figure 9 This is a schematic flowchart of a channel transmission method 300 according to an embodiment of this application, such as... Figure 9 As shown, the method 300 may include at least some of the following: 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.
[0173] That is, the time interval between the nth PUSCH transmission and the (n-1th PUSCH transmission in the first uplink HARQ process is greater than or equal to the first duration, where n is a positive integer and n≥2.
[0174] Optionally, the first uplink HARQ process corresponds to a first state, including: The first uplink HARQ process is a disabled HARQ process; or, The first uplink HARQ process is configured to disable parameters.
[0175] 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.
[0176] Example 1: The network device sends a first PDCCH to the terminal device, the first PDCCH being used to schedule the terminal device to transmit a first PUSCH using a 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 a first duration after the last symbol of the transmission of the target PUSCH in the first PUSCH.
[0177] Example 2: The network device sends a first PDCCH to the terminal device, the first PDCCH being used to schedule the terminal device to transmit a first PUSCH using a first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and if the terminal device transmits a second PUSCH using the first uplink HARQ process within a first duration after the last symbol of the target PUSCH in the first PUSCH being scheduled for transmission, the network device does not expect to receive the second PUSCH sent by the terminal device.
[0178] Example 3: The network device sends a first PDCCH to the terminal device, the first PDCCH being used to schedule the terminal device to transmit a first PUSCH using a first uplink HARQ process, wherein the first PUSCH includes at least one PUSCH; and if the terminal device transmits a second PUSCH using the first uplink HARQ process after the last symbol of the target PUSCH in the first PUSCH is scheduled to be transmitted, the network device receives the second PUSCH sent by the terminal device.
[0179] Optionally, in some embodiments, the network device sends first configuration information to the terminal device, wherein... When the terminal device is configured to receive DRX discontinuously, the first configuration information is used to configure the terminal device to start a 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 a first timer after the last symbol of the first PDCCH transmission. Wherein, the first timer is used to indicate a time window in which the terminal device does not expect to receive the second PDCCH, and the second PDCCH is used to schedule the terminal device to use the first uplink HARQ process to transmit the 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 the second PUSCH.
[0180] Optionally, in some embodiments, the network device sends second configuration information to the terminal device, wherein... The second configuration information is used to configure the terminal device to start a second timer after the first timer expires. 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.
[0181] Optionally, the second timer is a DRX uplink retransmission timer. drx-RetransmissionTimerUL ).
[0182] Optionally, the second configuration information includes the second timer.
[0183] Optionally, the duration of the first timer is less than or equal to the first duration.
[0184] Optionally, the first timer is a DRX uplink HARQ RTT timer ( drx-HARQ-RTT-TimerUL ).
[0185] Optionally, the first configuration information includes the first timer.
[0186] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or, The target PUSCH is the last PUSCH in this first PUSCH.
[0187] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are consecutive in the time domain, or the at least two PUSCHs occupy at least two consecutive time slots in the time domain.
[0188] Optionally, the first PUSCH is scheduled via a PDCCH, or the first PUSCH corresponds to a PDCCH.
[0189] Optionally, the first PUSCH is a PUSCH scheduled by PDCCH, or the first PUSCH is an SPS PUSCH, or the first PUSCH is a CG PUSCH.
[0190] Optionally, in 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 Examples 4 to 5 below.
[0191] Example 4: The network device sends 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; and if 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 timing advance effect is less than a second duration, the network device does not expect the terminal device to transmit the first PUSCH.
[0192] Example 5: The network device sends 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; and the network device receives the first PUSCH sent by the terminal device if 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 timing advance effect is greater than or equal to the second duration.
[0193] The PUSCH that was last 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 of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering timing advance, or the target symbol is the later of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering timing advance.
[0194] Optionally, the second duration is based on T proc,2 The processing time is fixed, among which T proc,2 It is determined based on the PUSCH preparation time value.
[0195] Optionally, in embodiments of this application, the first duration can be determined based on at least one of the following: PUSCH preparation time value; T proc,2 Processing time, of which T proc,2 It is determined based on the PUSCH preparation time value; The processing time value for PUSCH received by the network device; The larger of the PUSCH preparation time value and the processing time value of the network device receiving the PUSCH; The smaller of the PUSCH preparation time value and the processing time value for the network device to receive the PUSCH.
[0196] It should be noted that this PUSCH preparation time value N2 This could be the PUSCH preparation time value of the terminal device. Furthermore, the N2 value corresponding to UE's processing capability 1 is different from the N2 value corresponding to UE's processing capability 2.
[0197] Optionally, the first duration and the second duration are equal.
[0198] Optionally, the second duration is longer than the first duration.
[0199] Optionally, the PUSCH preparation time value N2 Related to the subcarrier spacing configuration of the PUSCH, or the PUSCH preparation time value. N2 This is related to the subcarrier spacing configuration of the PDCCH that schedules the PUSCH. For example, the value of N2 differs under different subcarrier spacings.
[0200] For example, if the UE receives uplink grant information from the base station, and this uplink grant 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 timing advance effect based on the uplink grant information, for example, based on the SLIV indication in the uplink grant 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 scheduled DCI.
[0201] Here, symbol L2 is defined as: the next uplink symbol following the end position of the later 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 start position of the CP of the next uplink symbol is later than... T proc,2 Processing time.
[0202] Optionally, T proc,2 It can be determined according to Formula 1 above.
[0203] It should be noted that the meanings of the parameters in Formula 1 can be found in Section 6.4 of the communication protocol standard TS38.214, and will not be discussed further here for the sake of brevity. Furthermore, different communication protocol standards may revise or update the meanings of the parameters in Formula 1, and this application may be adjusted accordingly based on the relevant communication protocol.
[0204] It should be noted that, in this embodiment, 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. Furthermore, in this embodiment, the first PUSCH corresponds to the k-th PUSCH transmission, the second PUSCH corresponds to the (k+1)-th PUSCH transmission, and the third PUSCH corresponds to the (k-1)-th PUSCH transmission.
[0205] Therefore, in this embodiment, 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. This enhances the uplink HARQ scheduling constraint and ensures that the processing timing of the terminal device will not be out of order.
[0206] Figure 10 This is a schematic flowchart of a channel transmission method 400 according to an embodiment of this application, such as... Figure 10 As shown, the method 400 may include at least some of the following: S410, the network device sends PDSCH to the terminal device using the first downlink HARQ process, wherein the first downlink HARQ process corresponds to the first state, and the time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process is greater than or equal to the third duration. S420, the terminal device receives the PDSCH sent by the network device using the first downlink HARQ process.
[0207] That is, the time interval between the nth PDSCH transmission and the (n-1th PDSCH transmission in the first downlink HARQ process is greater than or equal to the third duration, where n is a positive integer and n≥2.
[0208] Optionally, 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 to disable parameters; or, The first downlink HARQ process does not correspond to uplink HARQ-ACK feedback.
[0209] It should be noted that for the first downlink HARQ process in 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 to reuse the first downlink HARQ process for the transmission of TB 2. TB 1 and TB 2 can be the same TB or different TBs. However, when reusing the first downlink HARQ process for the transmission of TB 2, the network device needs to ensure that the time interval between transmitting PDSCH 1 for TB 1 and transmitting PDSCH 2 for TB 2 is greater than or equal to a third duration, so that the terminal device has sufficient time to process the reception of PDSCH 1 when receiving PDSCH 2.
[0210] 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 Examples 1 to 3 below.
[0211] Example 1: The terminal device receives a first PDSCH sent by the network device using a first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and the terminal device does not expect to receive or decode a second PDSCH sent by the network device using the first downlink HARQ process within a third duration following 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 duration following the last symbol of the target PDSCH transmission in the first PDSCH.
[0212] Example 2: The terminal device receives a first PDSCH sent by the network device using a first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and if the terminal device receives or decodes a second PDSCH sent by the network device using the first downlink HARQ process within a third duration 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, if the terminal device receives or decodes 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.
[0213] Example 3: In the case that 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 the case that the terminal device receives or decodes a second PDSCH sent by the network device using the first downlink HARQ process after a third duration following 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 that the terminal device receives or decodes a second PDSCH sent by the network device using the first downlink HARQ process after the third duration following 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.
[0214] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or, The target PDSCH is the last PDSCH in this first PDSCH.
[0215] For example, the terminal device receives HARQ from the network device. y The first PDSCH sent, such as Figure 11 In case 1, the earliest reschedulable HARQ occurs three time intervals after the last symbol of the first PDSCH transmission. y The time, that is, the time after which the terminal device is scheduled to receive or decode the network device using HARQ, is three time intervals after the last symbol of the first PDSCH transmission. y In the case of a second PDSCH being sent, the terminal device receives or decodes the second PDSCH.
[0216] For example, terminal devices receive HARQ data from network devices. y The first PDSCH sent, which includes PDSCH 1 and PDSCH 2, such as Figure 11 In scenario 2, the earliest reschedulable HARQ occurs three time intervals after the last symbol transmitted in PDSCH 2 (the last PDSCH in the first PDSCH). y The time, that is, the time after which the terminal device receives or decodes the network device using HARQ, is three time intervals after the last symbol of the PDSCH 2 transmission scheduled in the first PDSCH. y In the case of a second PDSCH being sent, the terminal device receives or decodes the second PDSCH.
[0217] For example, the terminal device receives HARQ from the network device.y The first PDSCH sent, which includes PDSCH 1 and PDSCH 2, such as Figure 11 In case 3, the earliest reschedulable HARQ occurs three time intervals after the last symbol transmitted in PDSCH 1 (the first PDSCH in the first PDSCH). y The time, that is, the time after which the terminal device receives or decodes the network device using HARQ, is three time intervals after the last symbol of the PDSCH 1 transmission scheduled in the first PDSCH. y In the case of a second PDSCH being sent, the terminal device receives or decodes the second PDSCH.
[0218] 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 Examples 4 to 6 below.
[0219] Example 4: The terminal device receives a first PDSCH sent by the network device using a first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and the terminal device does not expect to receive a second PDCCH for the network device to schedule the transmission of a second PDSCH by the first downlink HARQ process within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH. Accordingly, the network device does not send the second PDCCH for scheduling the transmission of a second PDSCH by the first downlink HARQ process within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH.
[0220] Example 5: The terminal device receives a first PDSCH sent by the network device using a first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and if the terminal device receives a second PDCCH for transmitting a second PDSCH using the first downlink HARQ process within a third duration following the last symbol of the target PDSCH transmission in the first PDSCH, the terminal device does not receive or decode the second PDSCH. Correspondingly, if the terminal device receives a second PDCCH for transmitting a second PDSCH using the first downlink HARQ process within the third duration following 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.
[0221] Example 6: In the case that the terminal device receives a first PDSCH sent by the network device using a first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; and in the case that the terminal device receives a second PDCCH for transmitting a second PDSCH using the first downlink HARQ process after a third duration following 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 that the terminal device receives a second PDCCH for transmitting a second PDSCH using the first downlink HARQ process after the third duration following 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.
[0222] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or, The target PDSCH is the last PDSCH in this first PDSCH.
[0223] For example, the terminal device receives HARQ from the network device. y The first PDSCH sent, such as Figure 12 In case 1, the earliest reschedulable HARQ occurs three time intervals after the last symbol of the first PDSCH transmission. y The PDCCH transmission time, that is, the time after which the terminal device receives the HARQ scheduled by the network device three times after the last symbol of the first PDCCH transmission. y In the case of transmitting a second PDSCH and a second PDCCH, the terminal device receives or decodes the second PDSCH.
[0224] For example, terminal devices receive HARQ data from network devices. y The first PDSCH sent, which includes PDSCH 1 and PDSCH 2, such as Figure 12 In scenario 2, the earliest reschedulable HARQ occurs three time intervals after the last symbol transmitted in PDSCH 2 (the last PDSCH in the first PDSCH). y The PDCCH transmission time, that is, the third time interval after the terminal device receives the HARQ scheduled by the network device after the last symbol of PDSCH 2 transmission in the first PDSCH. y In the case of transmitting a second PDSCH and a second PDCCH, the terminal device receives or decodes the second PDSCH.
[0225] For example, the terminal device receives HARQ from the network device. y The first PDSCH sent, which includes PDSCH 1 and PDSCH 2, such as Figure 12 In case 3, the earliest reschedulable HARQ occurs three time intervals after the last symbol transmitted in PDSCH 1 (the first PDSCH in the first PDSCH). y The transmission time of the PDCCH, that is, the third time interval after the terminal device receives the HARQ scheduled by the network device after the last symbol of PDSCH 1 transmission in the first PDSCH. y In the case of transmitting a second PDSCH and a second PDCCH, the terminal device receives or decodes the second PDSCH.
[0226] 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 the second PDCCH, or the third timer is used to indicate a time window in which the terminal device does not expect to receive the second PDSCH, the second PDCCH being used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.
[0227] For example, the third timer is used to indicate the minimum duration for which the terminal device does not expect to receive the second PDCCH, or the third timer is used to indicate the minimum duration for which the terminal device does not expect to receive the second PDSCH.
[0228] Optionally, the terminal device starts a fourth timer after the third timer expires. The fourth timer is used to indicate the time window in which the terminal device may receive the second PDCCH or the second PDSCH.
[0229] For example, the fourth timer is used to indicate the maximum duration for which the terminal device may receive the second PDCCH or the second PDSCH.
[0230] Optionally, the network device sends first configuration information to the terminal device, wherein, When 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. The third timer is used to indicate a time window in which the terminal device does not expect to receive the second PDCCH, or the third timer is used to indicate a time window in which the terminal device does not expect to receive the second PDSCH. The second PDCCH is used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.
[0231] Optionally, the network device sends second configuration information to the terminal device, wherein, The second configuration information is used to configure the terminal device to start a fourth timer after the third timer expires. The fourth timer is used to indicate the time window in which the terminal device may receive the second PDCCH or the second PDSCH.
[0232] Optionally, the fourth timer is a DRX downlink retransmission timer ( drx-RetransmissionTimerDL ).
[0233] Optionally, the second configuration information includes the fourth timer.
[0234] Optionally, the duration of the third timer is less than or equal to the third duration.
[0235] Optionally, the third timer is a DRX downlink HARQ RTT timer ( drx-HARQ-RTT-TimerDL ).
[0236] Optionally, the first configuration information includes the third timer.
[0237] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or, The target PDSCH is the last PDSCH in this first PDSCH.
[0238] Optionally, the first PDSCH includes at least two PDSCHs that are consecutive in the time domain, or the at least two PDSCHs occupy at least two consecutive time slots in the time domain.
[0239] Optionally, the first PDSCH is scheduled via a PDCCH, or the first PDSCH corresponds to a PDCCH.
[0240] Optionally, the first PDSCH is a PDSCH scheduled by PDCCH, or the first PDSCH is an SPS PDSCH.
[0241] For example, when a terminal device is configured with DRX, the terminal device receives HARQ data from the network device. y The first PDSCH sent, such as Figure 13 In scenario 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. Furthermore, during the operation of the fourth timer, the terminal device receives HARQ data from the network device. y The second PDSCH is sent, or the terminal device receives a HARQ from the network device for scheduling the HARQ. y The second PDCCH transmits the second PDSCH.
[0242] For example, when a terminal device is configured with DRX, the terminal device receives HARQ data from the network device. y The first PDSCH sent, which includes PDSCH 1 and PDSCH 2, such as Figure 13 In scenario 2, the terminal device starts the third timer after the last symbol transmitted in PDSCH 2 (the last PDSCH in the first PDSCH), and starts the fourth timer after the third timer expires. Furthermore, during the operation of the fourth timer, the terminal device receives HARQ data from the network device. y The second PDSCH is sent, or the terminal device receives a HARQ from the network device for scheduling the HARQ. y The second PDCCH transmits the second PDSCH.
[0243] For example, when a terminal device is configured with DRX, the terminal device receives HARQ data from the network device. y The first PDSCH sent, which includes PDSCH 1 and PDSCH 2, such as Figure 13 In scenario 3, the terminal device starts the third timer after the last symbol transmitted in PDSCH 1 (the first PDSCH in the first PDSCH), and starts the fourth timer after the third timer expires. Furthermore, during the operation of the fourth timer, the terminal device receives HARQ data from the network device. y The second PDSCH is sent, or the terminal device receives a HARQ from the network device for scheduling the HARQ. y The second PDCCH transmits the second PDSCH.
[0244] It should be noted that the above HARQ y This is a specific example of the first downlink HARQ process and does not constitute a limitation on this application.
[0245] Optionally, in embodiments of this application, the third duration can be determined based on at least one of the following: PDSCH decoding time value; T proc,1 Processing time, of which T proc,1 It is determined based on the PDSCH decoding time value; The K1 value, or the time-domain location of the 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. K offset Value, or K offset The value indicates the temporal location of the PUCCH resource, where K offset The value is indicated by the network device through at least one of system messages, RRC messages, Media Access Control Control Element (MAC CE), and DCI; K1+K offset Value, or, K1+K offset The value indicates the time-domain location of the PUCCH resource, where K1+K offset It is indicated through the HARQ feedback timing indication information field in the DCI format, or, K1+K offset K1 is provided through the HARQ feedback timing set; or, K1 is indicated through the HARQ feedback timing indication information field in the DCI format; or, K1 is provided through the HARQ feedback timing set. offset The value is indicated by the network device through at least one of system messages, RRC messages, MAC CE, and DCI; The processing time for network devices to prepare to send PDSCH; The larger of the PDSCH decoding time value and the processing time value of the network device preparing to send the PDSCH; The smaller of the PDSCH decoding time value and the processing time value when the network device prepares to send the PDSCH.
[0246] Optionally, when the HARQ feedback timing set includes multiple values, K1 is indicated by the HARQ feedback timing indication information field in the DCI format; when the HARQ feedback timing set includes one value, K1 is provided by the HARQ feedback timing set, wherein the DCI format does not include the HARQ feedback timing indication information field.
[0247] Optionally, the third duration is determined based on the time-domain location of the PUCCH resource, including: This third duration is determined based on the time-domain position corresponding to the first symbol of the PUCCH resource; or, This third duration is determined based on the time-domain position corresponding to the last symbol of the PUCCH resource.
[0248] For example, the end position of the third duration is determined based on the start position of the first symbol of the PUCCH resource.
[0249] For example, the end position of the third duration is determined based on the end position of the last symbol of the PUCCH resource.
[0250] Optionally, the PDSCH decoding time value is related to the PDSCH subcarrier spacing configuration.
[0251] It should be noted that the PDSCH decoding time value is, for example... N or N1 This can be the PDSCH decoding time value of the terminal device. Furthermore, the PDSCH decoding time value, such as the N1 value, corresponding to UE processing capability 1 can be different from the PDSCH decoding time value, such as the N1 value, corresponding to UE processing capability 2.
[0252] Optionally, T proc,1 It can be determined according to Formula 2 above.
[0253] It should be noted that the meanings of the parameters in Formula 2 can be found in Section 5.3 of the communication protocol standard TS38.214, and will not be discussed further here for the sake of brevity. Furthermore, different communication protocol standards may revise or update the meanings of the parameters in Formula 2, and this application may be adjusted accordingly based on the relevant communication protocol.
[0254] As an example, and not a limitation, the value of the third duration is related to the subcarrier spacing configuration of the PDSCH. Related, When =0, the third duration is 13 symbols. When =1, the third duration is 13 symbols. When the duration is 2, the third duration is 20 symbols. =3, the third duration is 24 symbols.
[0255] Therefore, in this embodiment, 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. This enhances the downlink HARQ scheduling constraint and ensures that the processing timing of the terminal device will not be out of order.
[0256] The above text combined Figures 5 to 13 The method embodiments of this application are described in detail below, in conjunction with... Figures 14 to 20 The present application describes the device embodiments in detail. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be referred to the method embodiments.
[0257] Figure 14 A schematic block diagram of a terminal device 500 according to an embodiment of this application is shown. Figure 14 As shown, the terminal device 500 includes: The communication unit 510 is used to transmit the 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.
[0258] Optionally, the terminal device 500 also includes a processing unit 520.
[0259] This corresponds to a first uplink HARQ process where the time interval between two adjacent PUSCH transmissions is greater than or equal to a first duration, including: The communication unit 510 is also used to receive a first physical downlink control channel (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. The processing unit 520 is used to transmit a second PUSCH using the first uplink HARQ process within the first duration after the last symbol of the target PUSCH transmission scheduled in the first PUSCH; or... If, during the first duration following the last symbol of the target PUSCH transmission scheduled in the first PUSCH, the communication unit 510 is configured not to transmit the second PUSCH, the communication unit 510 may also be configured not to transmit the second PUSCH; or, In the case where the terminal device is scheduled to transmit a second PUSCH using the first uplink HARQ process 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.
[0260] Optionally, if the terminal device is configured to receive DRX discontinuously, the communication unit 510 is further configured to start a 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 a first timer after the last symbol of the first PDCCH transmission. The first timer is used to indicate the time window during which the terminal device does not expect to receive the second PDCCH, and the second PDCCH is used to schedule the terminal device to use the first uplink HARQ process to transmit the second PUSCH.
[0261] Optionally, the processing unit 520 is further configured to start a second timer after the first timer expires, the second timer being configured to indicate a time window in which the terminal device may receive the second PDCCH.
[0262] Optionally, the second timer is a DRX uplink retransmission timer.
[0263] Optionally, the duration of the first timer is less than or equal to the first duration.
[0264] Optionally, the first timer is a DRX uplink HARQ round-trip time (RTT) timer.
[0265] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or, The target PUSCH is the last PUSCH in this first PUSCH.
[0266] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are consecutive in the time domain, or the at least two PUSCHs occupy at least two consecutive time slots in the time domain.
[0267] Optionally, the first PUSCH is scheduled via a PDCCH, or the first PUSCH corresponds to a PDCCH.
[0268] Optionally, the first PUSCH is a PUSCH scheduled by PDCCH, or the first PUSCH is a semi-persistent scheduling SPSPUSCH, or the first PUSCH is a configuration-authorized CG PUSCH.
[0269] 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: The communication unit 510 is also used 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. If 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 timing advance effect) 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... If 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 timing advance effect is greater than or equal to the second duration, the communication unit 510 is also used to transmit the first PUSCH. The PUSCH last 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 of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering timing advance, or the target symbol is the later of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering timing advance.
[0270] Optionally, the second duration is based on T proc,2 The processing time is fixed, among which T proc,2 It is determined based on the PUSCH preparation time value.
[0271] Optionally, this first duration is determined based on the PUSCH preparation time value; or, The first duration is based on T proc,2 The processing time is fixed, among which T proc,2 It is determined based on the PUSCH preparation time value; or, This first duration is determined based on the processing time value of the PUSCH received by the network device; or, This first duration is determined based on the larger of the PUSCH preparation time and the processing time of the network device receiving the PUSCH; or, The first duration is determined based on the smaller of the PUSCH preparation time value and the processing time value of the network device receiving the PUSCH.
[0272] 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 the physical downlink control channel (PDCCH) that schedules the PUSCH.
[0273] Optionally, the first uplink HARQ process corresponds to a first state, including: The first uplink HARQ process is a disabled HARQ process; or, The first uplink HARQ process is configured to disable parameters.
[0274] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.
[0275] It should be understood that the terminal device 500 according to the embodiments of this application may correspond to the terminal device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the terminal device 500 are respectively for implementing Figure 5 The corresponding process of the terminal device in method 200 shown will not be described in detail here for the sake of brevity.
[0276] Figure 15 A schematic block diagram of a network device 600 according to an embodiment of this application is shown. Figure 15 As shown, the network device 600 includes: 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.
[0277] Optionally, the network device 600 also includes a communication unit 620.
[0278] 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: The communication unit 620 is used to send a first physical downlink control channel (PDCCH) to the terminal device. The first PDCCH is used to schedule the terminal device to use the first uplink HARQ process to transmit a first PUSCH. The first PUSCH includes at least one PUSCH. The processing unit 610 is also configured to, without scheduling the terminal device to transmit the 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, If, during the first duration following the last symbol of the target PUSCH transmission scheduled in the first PUSCH, the processing unit 610 transmits a second PUSCH using the first uplink HARQ process, the processing unit 610 is further configured not to expect to receive the second PUSCH sent by the terminal device; or, In the case where the terminal device transmits a second PUSCH using the first uplink HARQ process after the first duration following the last symbol of the target PUSCH transmission in the first PUSCH, the communication unit 620 is also used to receive the second PUSCH sent by the terminal device.
[0279] Optionally, the communication unit 620 is further configured to send first configuration information to the terminal device, wherein, When the terminal device is configured to receive DRX discontinuously, the first configuration information is used to configure the terminal device to start a 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 a first timer after the last symbol of the first PDCCH transmission. The first timer is used to indicate the time window during which the terminal device does not expect to receive the second PDCCH, and the second PDCCH is used to schedule the terminal device to use the first uplink HARQ process to transmit the second PUSCH.
[0280] Optionally, the communication unit 620 is further configured to send second configuration information to the terminal device, wherein, The second configuration information is used to configure the terminal device to start a second timer after the first timer expires. The second timer is used to indicate the time window in which the terminal device may receive the second PDCCH.
[0281] Optionally, the second timer is a DRX uplink retransmission timer, and / or the second configuration information includes the second timer.
[0282] Optionally, the duration of the first timer is less than or equal to the first duration.
[0283] Optionally, the first timer is a DRX uplink HARQ round-trip time (RTT) timer, and / or the first configuration information includes the first timer.
[0284] Optionally, the target PUSCH is the first PUSCH in the first PUSCH; or, The target PUSCH is the last PUSCH in this first PUSCH.
[0285] Optionally, the first PUSCH includes at least two PUSCHs, wherein the at least two PUSCHs are consecutive in the time domain, or the at least two PUSCHs occupy at least two consecutive time slots in the time domain.
[0286] Optionally, the first PUSCH is scheduled via a PDCCH, or the first PUSCH corresponds to a PDCCH.
[0287] Optionally, the first PUSCH is a PUSCH scheduled by PDCCH, or the first PUSCH is a semi-persistent scheduling SPSPUSCH, or the first PUSCH is a configuration-authorized CG PUSCH.
[0288] 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: The communication unit 620 is also used to send 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. If 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 timing advance effect) 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, If 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 timing advance effect is greater than or equal to the second duration, the communication unit 620 is also used to receive the first PUSCH sent by the terminal device. The PUSCH last 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 of the last symbol of the first PDCCH and the last uplink symbol of the last PUSCH in the third PUSCH after considering timing advance, or the target symbol is the later of the last symbol of the first PDCCH and the last uplink symbol of the first PUSCH in the third PUSCH after considering timing advance.
[0289] Optionally, the second duration is based on T proc,2 The processing time is fixed, among which T proc,2 It is determined based on the PUSCH preparation time value.
[0290] Optionally, this first duration is determined based on the PUSCH preparation time value; or, The first duration is based on T proc,2 The processing time is fixed, among which T proc,2 It is determined based on the PUSCH preparation time value; or, This first duration is determined based on the processing time value of the PUSCH received by the network device; or, This first duration is determined based on the larger of the PUSCH preparation time and the processing time of the network device receiving the PUSCH; or, The first duration is determined based on the smaller of the PUSCH preparation time value and the processing time value of the network device receiving the PUSCH.
[0291] 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 the physical downlink control channel (PDCCH) that schedules the PUSCH.
[0292] Optionally, the first uplink HARQ process corresponds to a first state, including: The first uplink HARQ process is a disabled HARQ process; or, The first uplink HARQ process is configured to disable parameters.
[0293] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.
[0294] It should be understood that the network device 600 according to the embodiments of this application may correspond to the network device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the network device 600 are respectively for implementing Figure 9 The corresponding procedures for network devices in method 300 shown are not described in detail here for the sake of brevity.
[0295] Figure 16 A schematic block diagram of a terminal device 700 according to an embodiment of this application is shown. Figure 16 As shown, the terminal device 700 includes: The communication unit 710 is used to receive the Physical Downlink Shared Channel (PDSCH) sent by the network device using the 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.
[0296] Optionally, the terminal device 700 also includes a processing unit 720.
[0297] 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: The communication unit 710 is also 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. The processing unit 720 is configured to receive or decode the 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, where it is not expected; or, If the terminal device receives or decodes 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 scheduled in the first PDSCH, the communication unit 710 is configured not to receive or decode the second PDSCH; or, In the 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 duration following 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.
[0298] 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: The communication unit 710 is also 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. The processing unit 720 is configured to receive a second PDCCH for transmitting the second PDCCH within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH, which is not expected by the network device to schedule the first downlink HARQ process to transmit the second PDSCH; or, If the terminal device receives a second PDCCH from the network device within the third time period following the last symbol of the target PDSCH transmission in the first PDSCH, and the network device schedules the first downlink HARQ process to transmit the second PDSCH, the communication unit is further configured not to receive or decode the second PDSCH; or, In the case where the terminal device receives the second PDCCH that the network device schedules the first downlink HARQ process to transmit the second PDCCH after the third duration following the last symbol of the target PDCCH transmission in the first PDCCH, the communication unit is also used to receive or decode the second PDCCH.
[0299] Optionally, when the terminal device is configured to receive DRX discontinuously, the processing unit 720 is further configured to start a third timer after the last symbol of the target PDSCH transmission in the first PDSCH, wherein the third timer is configured to indicate a time window in which the terminal device does not expect to receive the second PDCCH, or the third timer is configured to indicate a time window in which the terminal device does not expect to receive the second PDSCH, the second PDCCH being used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.
[0300] Optionally, the processing unit 720 is further configured to start a fourth timer after the third timer expires, the fourth timer being configured to indicate a time window in which the terminal device may receive the second PDCCH or the second PDSCH.
[0301] Optionally, the fourth timer is a DRX downlink retransmission timer.
[0302] Optionally, the duration of the third timer is less than or equal to the third duration.
[0303] Optionally, the third timer is a DRX downlink HARQ round-trip time (RTT) timer.
[0304] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or, The target PDSCH is the last PDSCH in this first PDSCH.
[0305] Optionally, the first PDSCH includes at least two PDSCHs that are consecutive in the time domain, or the at least two PDSCHs occupy at least two consecutive time slots in the time domain.
[0306] Optionally, the first PDSCH is scheduled via a PDCCH, or the first PDSCH corresponds to a PDCCH.
[0307] Optionally, the first PDSCH is a PDSCH scheduled by PDCCH, or the first PDSCH is a semi-persistent scheduling SPSPDSCH.
[0308] Optionally, this third duration is determined based on the PDSCH decoding time value; or, This third duration is based on T proc,1 The processing time is fixed, among which T proc,1 It is determined based on the PDSCH decoding time value; or, The third duration is determined based on the K1 value, or it is determined based on the time-domain location 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... This third duration is based on K. offset The value is determined, or the third duration is based on K. offset The time-domain location 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 the following: system messages, Radio Resource Control (RRC) messages, Media Access Control (MAC) control elements (CE) and DCI; or, The third duration is based on K1+K offset The value is determined, or the third duration is based on K1+K. offset The time-domain location of the PUCCH resource indicated by the value is determined, where K1 or K1+K offset It is indicated through the HARQ feedback timing indication information field in the DCI format, or K1 or K1+K. offset It is provided through the HARQ feedback timing set, or K. offset The value is indicated by the network device through at least one of system messages, RRC messages, MAC CE, and DCI; or, This third duration is determined based on the processing time required for the network device to prepare to send the PDSCH; or, This third duration is determined based on the larger of the PDSCH decoding time value and the processing time value for the network device to prepare to send the PDSCH; or, The third duration is determined based on the smaller of the PDSCH decoding time value and the processing time value for the network device to prepare to send the PDSCH.
[0309] Optionally, the third duration is determined based on the time-domain location of the PUCCH resource, including: This third duration is determined based on the time-domain position corresponding to the first symbol of the PUCCH resource; or, This third duration is determined based on the time-domain position corresponding to the last symbol of the PUCCH resource.
[0310] Optionally, the PDSCH decoding time value is related to the PDSCH subcarrier spacing configuration.
[0311] Optionally, 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 to disable parameters; or, The first downlink HARQ process does not correspond to the uplink hybrid automatic repeat request-response (HARQ-ACK) feedback.
[0312] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.
[0313] It should be understood that the terminal device 700 according to the embodiments of this application may correspond to the terminal device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the terminal device 700 are respectively for implementing Figure 10 The corresponding process of the terminal device in method 400 shown will not be described in detail here for the sake of brevity.
[0314] Figure 17 A schematic block diagram of a network device 800 according to an embodiment of this application is shown. Figure 17 As shown, the network device 800 includes: The communication unit 810 is used to send a Physical Downlink Shared Channel (PDSCH) to the terminal 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.
[0315] Optionally, the network device 800 also includes a processing unit 820.
[0316] 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: The communication unit 810 is also used to send a first PDSCH to the terminal device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; The processing unit 820 is also configured to not use the first downlink HARQ process to send a second PDSCH within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH; or, If the terminal device receives or decodes 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 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, In the 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 duration following 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 receives or decodes the second PDSCH.
[0317] 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: The communication unit 810 is also used to send a first PDSCH to the terminal device using the first downlink HARQ process, wherein the first PDSCH includes at least one PDSCH; The communication unit 810 is also configured to not send a second PDCCH that schedules the first downlink HARQ process to transmit the second PDCCH within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH; or, If, within the third time period following the last symbol of the target PDSCH transmission scheduled in the first PDSCH, the terminal device receives the second PDCCH that the network device is scheduling for the first downlink HARQ process to transmit the second PDSCH, the processing unit 820 is further configured to assume that the terminal device does not receive or decode the second PDSCH; or, If the terminal device receives the second PDCCH that the network device is scheduling to transmit the second PDCCH through the first downlink HARQ process a third time interval after the last symbol of the target PDCCH transmission in the first PDCCH, the processing unit 820 is further configured to assume that the terminal device receives or decodes the second PDCCH.
[0318] Optionally, the communication unit 810 is further configured to send first configuration information to the terminal device, wherein, When the terminal device is configured to receive DRX discontinuously, 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. The third timer is used to indicate a time window in which the terminal device does not expect to receive the second PDCCH, or the third timer is used to indicate a time window in which the terminal device does not expect to receive the second PDSCH. The second PDCCH is used by the network device to schedule the first downlink HARQ process to transmit the second PDSCH.
[0319] Optionally, the communication unit 810 is further configured to send second configuration information to the terminal device, wherein, The second configuration information is used to configure the terminal device to start a fourth timer after the third timer expires. The fourth timer is used to indicate the time window in which the terminal device may receive the second PDCCH or the second PDSCH.
[0320] Optionally, the fourth timer is a DRX downlink retransmission timer, and / or the second configuration information includes the fourth timer.
[0321] Optionally, the duration of the third timer is less than or equal to the third duration.
[0322] Optionally, the third timer is a DRX downlink HARQ round-trip time (RTT) timer, and / or the first configuration information includes the third timer.
[0323] Optionally, the target PDSCH is the first PDSCH in the first PDSCH; or, The target PDSCH is the last PDSCH in this first PDSCH.
[0324] Optionally, the first PDSCH includes at least two PDSCHs that are consecutive in the time domain, or the at least two PDSCHs occupy at least two consecutive time slots in the time domain.
[0325] Optionally, the first PDSCH is scheduled via a PDCCH, or the first PDSCH corresponds to a PDCCH.
[0326] Optionally, the first PDSCH is a PDSCH scheduled by PDCCH, or the first PDSCH is a semi-persistent scheduling SPSPDSCH.
[0327] Optionally, this third duration is determined based on the PDSCH decoding time value; or, This third duration is based on T proc,1 The processing time is fixed, among whichT proc,1 It is determined based on the PDSCH decoding time value; or, The third duration is determined based on the K1 value, or it is determined based on the time-domain location 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... This third duration is based on K. offset The value is determined, or the third duration is based on K. offset The time-domain location 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 the following: system messages, Radio Resource Control (RRC) messages, Media Access Control (MAC) control elements (CE) and DCI; or, The third duration is based on K1+K offset The value is determined, or the third duration is based on K1+K. offset The time-domain location of the PUCCH resource indicated by the value is determined, where K1 or K1+K offset It is indicated through the HARQ feedback timing indication information field in the DCI format, or K1 or K1+K. offset It is provided through the HARQ feedback timing set, or K. offset The value is indicated by the network device through at least one of system messages, RRC messages, MAC CE, and DCI; or, This third duration is determined based on the processing time required for the network device to prepare to send the PDSCH; or, This third duration is determined based on the larger of the PDSCH decoding time value and the processing time value for the network device to prepare to send the PDSCH; or, The third duration is determined based on the smaller of the PDSCH decoding time value and the processing time value for the network device to prepare to send the PDSCH.
[0328] Optionally, the third duration is determined based on the time-domain location of the PUCCH resource, including: This third duration is determined based on the time-domain position corresponding to the first symbol of the PUCCH resource; or, This third duration is determined based on the time-domain position corresponding to the last symbol of the PUCCH resource.
[0329] Optionally, the PDSCH decoding time value is related to the PDSCH subcarrier spacing configuration.
[0330] Optionally, 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 to disable parameters; or, The first downlink HARQ process does not correspond to the uplink hybrid automatic repeat request-response (HARQ-ACK) feedback.
[0331] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.
[0332] It should be understood that the network device 800 according to the embodiments of this application may correspond to the network device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the network device 800 are respectively for implementing Figure 10 The corresponding procedures for network devices in method 400 are not described in detail here for the sake of brevity.
[0333] Figure 18 This is a schematic structural diagram of a communication device 900 provided in an embodiment of this application. Figure 18 The communication device 900 shown includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0334] Optionally, such as Figure 18 As shown, the communication device 900 may further include a memory 920. The processor 910 can retrieve and run computer programs from the memory 920 to implement the methods described in this embodiment.
[0335] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.
[0336] Optionally, such as Figure 18 As shown, the communication device 900 may also include a transceiver 930, which the processor 910 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.
[0337] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of antennas may be one or more.
[0338] Optionally, the communication device 900 may specifically be a network device in the embodiments of this application, and the communication device 900 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0339] Optionally, the communication device 900 may specifically be a mobile terminal / terminal device in the embodiments of this application, and the communication device 900 may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0340] Figure 19 This is a schematic structural diagram of the device according to an embodiment of this application. Figure 19 The illustrated apparatus 1000 includes a processor 1010, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0341] Optionally, such as Figure 19 As shown, the device 1000 may further include a memory 1020. The processor 1010 can retrieve and run computer programs from the memory 1020 to implement the methods described in the embodiments of this application.
[0342] The memory 1020 can be a separate device independent of the processor 1010, or it can be integrated into the processor 1010.
[0343] Optionally, the device 1000 may further include an input interface 1030. The processor 1010 can control the input interface 1030 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.
[0344] Optionally, the device 1000 may further include an output interface 1040. The processor 1010 can control the output interface 1040 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.
[0345] Optionally, the device can be applied to the network device in the embodiments of this application, and the device can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0346] Optionally, the device can be applied to the mobile terminal / terminal device in the embodiments of this application, and the device can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0347] Optionally, the device mentioned in the embodiments of this application can also be a chip. For example, it can be a system-on-a-chip, a system-on-a-chip, a chip system, or a system-on-a-chip, etc.
[0348] Figure 20 This is a schematic block diagram of a communication system 1100 provided in an embodiment of this application. Figure 20As shown, the communication system 1100 includes a terminal device 1110 and a network device 1120.
[0349] 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, these will not be elaborated here.
[0350] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.
[0351] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0352] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be 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 memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.
[0353] This application also provides a computer-readable storage medium for storing computer programs.
[0354] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0355] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0356] This application also provides a computer program product, including computer program instructions.
[0357] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0358] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0359] This application also provides a computer program.
[0360] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0361] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0362] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0363] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0364] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0365] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0366] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0367] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0368] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for channel transmission, characterized in that, include: The terminal device receives a Physical Downlink Shared Channel (PDSCH) sent by the network device using a first downlink Hybrid Automatic Repeat Request (HARQ) process. 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. The third duration is based on... T proc,1 The processing time is fixed, among which T proc,1 It is determined based on the PDSCH decoding time value; wherein, the PDSCH decoding time value is related to the PDSCH subcarrier spacing configuration; wherein, the first downlink HARQ process corresponds to the first state, including: The first downlink HARQ process is a disabled HARQ process; or, The first downlink HARQ process is configured to disable parameters; or, The first downlink HARQ process does not correspond to the uplink hybrid automatic repeat request-response (HARQ-ACK) feedback.
2. The method as described in claim 1, characterized in that, The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process being greater than or equal to a third duration includes: 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 duration following the last symbol of the target PDSCH transmission in the first PDSCH; or... If the terminal device receives or decodes the 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 scheduled in the first PDSCH, the terminal device does not receive or decode the second PDSCH; or, If the terminal device receives or decodes the second PDSCH sent by the network device using the first downlink HARQ process after the third duration following the last symbol of the target PDSCH transmission scheduled in the first PDSCH, the terminal device receives or decodes the second PDSCH.
3. The method as described in claim 1, characterized in that, The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process being greater than or equal to a third duration includes: 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, which is scheduled by the network device to transmit the second PDCCH via the first downlink HARQ process, within the third duration after the last symbol of the target PDSCH transmission in the first PDSCH; or... If the terminal device receives a second PDCCH from the network device within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH, and the network device schedules the first downlink HARQ process to transmit the second PDSCH, the terminal device does not receive or decode the second PDSCH; or, If the terminal device receives the second PDCCH that the network device schedules the first downlink HARQ process to transmit the second PDCCH after the third duration following the last symbol of the target PDCCH transmission in the first PDCCH, the terminal device receives or decodes the second PDCCH.
4. The method as described in claim 2, 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 as described in claim 2, characterized in that, The first PDSCH includes at least two PDSCHs, which are consecutive in the time domain, or the at least two PDSCHs occupy at least two consecutive time slots in the time domain.
6. A method for channel transmission, characterized in that, include: The network device uses a first downlink hybrid automatic repeat request (HARQ) process to send a physical downlink shared channel (PDSCH) to the terminal device. 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. The third duration is based on... T proc,1 The processing time is fixed, among which T proc,1 It is determined based on the PDSCH decoding time value; wherein, the PDSCH decoding time value is related to the PDSCH subcarrier spacing configuration; wherein, the first downlink HARQ process corresponds to the first state, including: The first downlink HARQ process is a disabled HARQ process; or, The first downlink HARQ process is configured to disable parameters; or, The first downlink HARQ process does not correspond to the uplink hybrid automatic repeat request-response (HARQ-ACK) feedback.
7. The method as described in claim 6, characterized in that, The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process being greater than or equal to a third duration includes: The network device uses the first downlink HARQ process to send a first PDSCH to the terminal device, wherein the first PDSCH includes at least one PDSCH. The network device does not use the first downlink HARQ process to send a second PDSCH within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH; or... If the terminal device receives or decodes the 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 scheduled in the first PDSCH, the network device assumes that the terminal device does not receive or decode the second PDSCH; or, If the terminal device receives or decodes the second PDSCH sent by the network device using the first downlink HARQ process after the third duration following the last symbol of the target PDSCH transmission scheduled in the first PDSCH, the network device assumes that the terminal device has received or decoded the second PDSCH.
8. The method as described in claim 6, characterized in that, The time interval between two adjacent PDSCH transmissions corresponding to the first downlink HARQ process being greater than or equal to a third duration includes: The network device uses the first downlink HARQ process to send a first PDSCH to the terminal device, 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 the second PDSCH within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH; or... If the terminal device receives a second PDCCH from the network device within the third duration following the last symbol of the target PDSCH transmission in the first PDSCH, and the network device schedules the first downlink HARQ process to transmit the second PDSCH, the network device assumes that the terminal device does not receive or decode the second PDSCH; or, If the terminal device receives a second PDCCH from the network device after the third duration following the last symbol of the target PDSCH transmission in the first PDSCH, the network device assumes that the terminal device has received or decoded the second PDSCH.
9. The method as described in claim 7, 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.
10. The method as described in claim 7, characterized in that, The first PDSCH includes at least two PDSCHs, which are consecutive in the time domain, or the at least two PDSCHs occupy at least two consecutive time slots in the time domain.
11. A terminal device, characterized in that, include: The communication unit is configured 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; wherein the third duration is based on... T proc,1 The processing time is fixed, among which T proc,1 It is determined based on the PDSCH decoding time value; wherein, the PDSCH decoding time value is related to the PDSCH subcarrier spacing configuration; wherein, the first downlink HARQ process corresponds to the first state, including: The first downlink HARQ process is a disabled HARQ process; or, The first downlink HARQ process is configured to disable parameters; or, The first downlink HARQ process does not correspond to the uplink hybrid automatic repeat request-response (HARQ-ACK) feedback.
12. A network device, characterized in that, include: The communication unit is configured to send a Physical Downlink Shared Channel (PDSCH) to the terminal 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; wherein the third duration is based on... T proc,1 The processing time is fixed, among which T proc,1 It is determined based on the PDSCH decoding time value; wherein, the PDSCH decoding time value is related to the PDSCH subcarrier spacing configuration; wherein, the first downlink HARQ process corresponds to the first state, including: The first downlink HARQ process is a disabled HARQ process; or, The first downlink HARQ process is configured to disable parameters; or, The first downlink HARQ process does not correspond to the uplink hybrid automatic repeat request-response (HARQ-ACK) feedback.
13. A terminal device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 5.
14. A network device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 6 to 10.
15. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 5.
16. A chip, characterized in that, Includes: a processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 6 to 10.
17. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1 to 5.
18. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 6 to 10.
19. A computer program product, characterized in that, It includes computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 5.
20. A computer program product, characterized in that, It includes computer program instructions that cause a computer to perform the method as described in any one of claims 6 to 10.
