Communication method, device, equipment, chip, storage medium, product and program

By defining the scheduling time range of terminal equipment and network equipment in the NTN system, the problem of PDSCH scheduling restrictions is solved, and the disordered situation when terminal equipment receives PDSCH is avoided, and channel efficiency is improved.

CN118921148APending Publication Date: 2024-11-08GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202411333905.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-12-17
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In non-terrestrial network (NTN) systems, the prior art has failed to effectively solve the problem of physical downlink shared channel (PDSCH) scheduling restrictions, resulting in out-of-order situations when terminal devices receive PDSCH.

Method used

By establishing a specific time range between the terminal device and the network device, it is not expected to receive or transmit scheduling information, specifically including that the terminal device does not expect to receive the second PDSCH or PDCCH after receiving the first PDSCH scheduled by the network device, After sending the first PDSCH, the network device does not expect to send the second PDSCH or PDCCH to limit the scheduling of the PDSCH.

Benefits of technology

It effectively avoids the situation where the terminal device is out of order when receiving the PDSCH, improves the channel scheduling efficiency, and avoids waste of resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921148A_ABST
    Figure CN118921148A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a communication method and device, equipment, a chip, a storage medium, a product and a program. The method comprises the steps that terminal equipment receives a first physical downlink shared channel (PDSCH) transmitted by a first hybrid automatic repeat request (HARQ) process scheduled by network equipment; the terminal equipment does not expect to receive a second PDSCH transmitted by the first HARQ process scheduled by the network equipment in a first time range, or does not expect to receive a first physical downlink control channel (PDCCH), and the first PDCCH is used for the network equipment to schedule the first HARQ process to transmit the second PDSCH.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2021 / 139287 with an application date of December 17, 2021, which entered the Chinese national phase with Chinese patent application number 202180104854.2 and the invention name "Communication methods, devices, equipment, chips, storage media, products and programs". Technical Field

[0002] The embodiments of the present application relate to the field of communication technology, and specifically to a communication method, apparatus, device, chip, storage medium, product and program. Background Art

[0003] Currently, the 3rd Generation Partnership Project (3GPP) is studying the Non-Terrestrial Networks (NTN) technology. NTN generally uses satellite communications to provide communication services to ground users.

[0004] In the NTN system, the art has not paid attention to how to perform scheduling restrictions on the Physical Downlink Shared Channel (PDSCH). Summary of the invention

[0005] Embodiments of the present application provide a communication method, apparatus, device, chip, storage medium, product, and program.

[0006] In a first aspect, an embodiment of the present application provides a communication method, the method comprising:

[0007] The terminal device receives a first physical downlink shared channel PDSCH scheduled by the network device for transmission in a first hybrid automatic repeat request HARQ process;

[0008] The terminal device does not expect to receive the second PDSCH scheduled by the network device for transmission of the first HARQ process within the first time range, or does not expect to receive the first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process to transmit the second PDSCH.

[0009] In a second aspect, an embodiment of the present application provides a communication method, the method comprising:

[0010] The network device sends a first physical downlink shared channel PDSCH for scheduling transmission of a first hybrid automatic repeat request HARQ process to the terminal device;

[0011] The network device does not expect to send a second PDSCH for scheduling the transmission of the first HARQ process to the terminal device within a second time range, or does not expect to send a first physical downlink control channel PDCCH to the terminal device, wherein the first PDCCH is used by the network device to schedule the transmission of the second PDSCH by the first HARQ process.

[0012] In a third aspect, an embodiment of the present application provides a communication device, the communication device comprising:

[0013] A transceiver unit, configured to receive a first physical downlink shared channel PDSCH for a first hybrid automatic repeat request HARQ process transmission scheduled by a network device;

[0014] The transceiver unit is also used for not expecting to receive a second PDSCH scheduled by the network device for transmission of the first HARQ process within a first time range, or not expecting to receive a first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process to transmit a second PDSCH.

[0015] In a fourth aspect, an embodiment of the present application provides a communication device, the communication device comprising:

[0016] A transceiver unit, configured to send a first physical downlink shared channel PDSCH for scheduling transmission of a first hybrid automatic repeat request HARQ process to a terminal device;

[0017] The transceiver unit is also used for not expecting to send a second PDSCH for scheduling the transmission of the first HARQ process to the terminal device within a second time range, or not expecting to send a first physical downlink control channel PDCCH to the terminal device, wherein the first PDCCH is used to schedule the transmission of the second PDSCH by the first HARQ process.

[0018] In a fifth aspect, an embodiment of the present application provides a terminal device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the communication method as described in the first aspect.

[0019] In a sixth aspect, an embodiment of the present application provides a network device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the communication method as described in the second aspect.

[0020] In the seventh aspect, an embodiment of the present application provides a chip, comprising: a processor, for calling and running a computer program from a memory, so that a device equipped with the chip executes the communication method as described in the first aspect, or, so that a device equipped with the chip executes the communication method as described in the second aspect.

[0021] In an eighth aspect, an embodiment of the present application provides a computer storage medium for storing a computer program, wherein the computer program enables a terminal device to execute the communication method as described in the first aspect, or the computer program enables a network device to execute the communication method as described in the second aspect.

[0022] In a ninth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, wherein the computer program instructions enable a terminal device to execute the communication method as described in the first aspect, or the computer program instructions enable a network device to execute the communication method as described in the second aspect.

[0023] In the tenth aspect, an embodiment of the present application provides a computer program, which enables a terminal device to execute the communication method as described in the first aspect, or the computer program enables a network device to execute the communication method as described in the second aspect.

[0024] In an embodiment of the present application, a terminal device receives a first physical downlink shared channel PDSCH scheduled by a network device for transmission of a first hybrid automatic repeat request HARQ process; the terminal device does not expect to receive a second PDSCH scheduled by the network device for transmission of the first HARQ process within a first time range, or does not expect to receive a first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process to transmit the second PDSCH. In this way, the scheduling of the PDSCH can be restricted to avoid the terminal device from being out of order when receiving the PDSCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0026] Figure 1 A schematic diagram of an application scenario of an embodiment of the present application;

[0027] Figure 2 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0028] Figure 3 A schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0029] Figure 4 A schematic diagram of an NTN scenario based on a transparent forwarding satellite provided in an embodiment of the present application;

[0030] Figure 5 A schematic diagram of an NTN scenario based on a regenerative forwarding satellite provided in an embodiment of the present application;

[0031] Figure 6 A schematic diagram of transmission of HARQ-ACK feedback information provided in an embodiment of the present application;

[0032] Figure 7 A schematic diagram of another transmission of HARQ-ACK feedback information provided in an embodiment of the present application;

[0033] Figure 8 A flow chart of a communication method provided in an embodiment of the present application;

[0034] Fig. 9 A flow chart of a communication method provided in an embodiment of the present application

[0035] Fig.10 A schematic diagram of a scheduling restriction of a first HARQ process provided in an embodiment of the present application;

[0036] Fig.11 A schematic diagram of another scheduling restriction of a first HARQ process provided in an embodiment of the present application;

[0037] Fig.12 A schematic diagram of another scheduling restriction of a first HARQ process provided in an embodiment of the present application;

[0038] Fig.13 A schematic diagram of a scheduling restriction of a first HARQ process provided in another embodiment of the present application;

[0039] Fig.14 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0040] Fig.15 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0041] Fig.16 A schematic structural diagram of a communication device provided in an embodiment of the present application;

[0042] Fig.17 This is a schematic structural diagram of a chip according to an embodiment of the present application. DETAILED DESCRIPTION

[0043] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. The technical solutions recorded in the embodiments of the present application can be combined arbitrarily without conflict. In the description of the present application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically limited.

[0044] Figure 1 A schematic diagram of an application scenario of an embodiment of the present application.

[0045] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0046] It should be understood that the embodiments of the present application are only exemplified by the communication system 100, but the embodiments of the present application are not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine Type Communications (eMTC) system, 5G communication system (also called New Radio (NR) communication system), or future communication systems (such as 6G, 7G and other communication systems), etc.

[0047] exist Figure 1 In the communication system 100 shown, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area, and may communicate with the terminal device 110 located in the coverage area.

[0048] The terminal device in this application can be called user equipment (UE), mobile station (MS), mobile terminal (MT), user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device. The terminal device may include one of the following or a combination of at least two of the following: Internet of Things (IoT) devices, satellite terminals, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, servers, mobile phones, tablet computers (Pad), computers with wireless transceiver functions, handheld computers, desktop computers, personal digital assistants, portable media players, smart speakers, navigation devices, smart watches, smart glasses, smart necklaces and other wearable devices, pedometers, digital TVs, Virtual Reality (VR) terminal devices, Augmented Reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. The invention relates to wireless terminals in a connected home and vehicles, vehicle-mounted devices, vehicle-mounted modules, wireless modems, handheld devices, customer premises equipment (CPE), and smart home appliances in a connected vehicle system.

[0049] The network device 120 in the embodiment of the present application may include an access network device 121 and / or a core network device 122 .

[0050] The access network equipment 121 may include one of the following or a combination of at least two: an evolved base station (eNB or eNodeB) in a Long Term Evolution (LTE) system, a next generation radio access network (NG RAN) device, a base station (gNB) in an NR system, a small station, a micro station, a wireless controller in a cloud radio access network (CRAN), an access point for wireless fidelity (Wi-Fi), a transmission reception point (TRP), a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network device in a future evolved public land mobile network (PLMN), etc.

[0051] The core network device 122 may be a 5G core network (5G Core, 5GC) device, and the core network device 122 may include one of the following or a combination of at least two: Access and Mobility Management Function (AMF), Authentication Server Function (AUSF), User Plane Function (UPF), Session Management Function (SMF), Location Management Function (LMF). In other embodiments, the core network device may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a Session Management Function + Core Packet Gateway (SMF + PGW-C) device of the core network. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can implement. In the process of network evolution, the above-mentioned core network device 122 may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited to the embodiments of the present application.

[0052] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0053] The terminal device 110 may be used for device-to-device (D2D) communication.

[0054] The functional units in the communication system 100 may also establish connections through next generation (NG) network interfaces to achieve communication.

[0055] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (N4 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (N11 for short); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).

[0056] Figure 1 A base station, a core network device and two terminal devices are shown exemplarily. In some embodiments, the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0057] 3GPP is studying the technology of non-terrestrial network equipment (NTN). NTN generally uses satellite communication to provide communication services to ground users. Compared with ground cellular network communication, satellite communication has many unique advantages. First, satellite communication is not limited by the user's geographical location. For example, general land communication cannot cover areas such as oceans, mountains, deserts, etc. where communication equipment cannot be set up or where communication coverage is not provided due to sparse population. For satellite communication, since one satellite can cover a large area of ​​land, and satellites can orbit around the earth, in theory, every corner of the earth can be covered by satellite communication. Secondly, satellite communication has great social value. Satellite communication can cover remote mountainous areas, poor and backward countries or regions at a low cost, so that people in these areas can enjoy advanced voice communication and mobile Internet technology, which is conducive to narrowing the digital divide with developed areas and promoting the development of these areas. Thirdly, satellite communication has a long distance, and the cost of communication does not increase significantly as the communication distance increases; finally, satellite communication has high stability and is not restricted by natural disasters.

[0058] NTN technology can be combined with various communication systems. For example, NTN technology can be combined with NR system to form NR-NTN system. For another example, NTN technology can be combined with Internet of Things (IoT) system to form IoT-NTN system. As an example, IoT-NTN system can include NB-IoT-NTN system and eMTC-NTN system.

[0059] Figure 2 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application.

[0060] like Figure 2 As shown, it includes a terminal device 201 and a satellite 202, and wireless communication can be performed between the terminal device 201 and the satellite 202. The network formed between the terminal device 201 and the satellite 202 can also be called an NTN. Figure 2 In the architecture of the communication system shown, the satellite 202 may have the function of a base station, and the terminal device 201 and the satellite 202 may communicate directly. In the system architecture, the satellite 202 may be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 202, and each network device 202 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0061] Figure 3 A schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0062] like Figure 3As shown, it includes terminal equipment 301, satellite 302 and base station 303. The terminal equipment 301 and satellite 302 can communicate wirelessly, and the satellite 302 and base station 303 can communicate. The network formed by the terminal equipment 301, satellite 302 and base station 303 can also be called NTN. Figure 3 In the architecture of the communication system shown, the satellite 302 may not have the function of a base station, and the communication between the terminal device 301 and the base station 303 needs to be transferred through the satellite 302. In this system architecture, the base station 303 can be called a network device. In some embodiments of the present application, the communication system may include multiple network devices 303, and each network device 303 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application. The network device 303 may be Figure 1 The network device 120 in.

[0063] It should be understood that the satellite 1102 or satellite 302 includes but is not limited to:

[0064] Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, High Elliptical Orbit (HEO) satellites, etc. Satellites can use multiple beams to cover the ground. For example, a satellite can form dozens or even hundreds of beams to cover the ground. In other words, a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers to ensure satellite coverage and improve the system capacity of the entire satellite communication system.

[0065] As an example, the altitude range of LEO satellites can be 500 km to 1500 km, the corresponding orbital period can be about 1.5 hours to 2 hours, the signal propagation delay of single-hop communication between users can generally be less than 20 milliseconds, the maximum satellite visibility time can be 20 minutes, the signal propagation distance of LEO satellites is short and the link loss is small, and the transmission power requirements of user terminals are not high. The orbital altitude of GEO satellites can be 35786 km, the rotation period around the earth can be 24 hours, and the signal propagation delay of single-hop communication between users can generally be 250 milliseconds.

[0066] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0067] It should be noted that Figures 1 to 3It is only to illustrate the system to which the present application is applicable in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems. In addition, the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiment of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "correspondence" mentioned in the embodiment of the present application can mean that there is a direct or indirect correspondence relationship between the two, or it can mean that there is an association relationship between the two, or it can mean that there is an indication and being indicated, configuration and being configured, etc. It should also be understood that the "predefined", "protocol agreed", "predetermined" or "predefined rules" mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method. For example, predefined may refer to the definition in the protocol. It should also be understood that in the embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, such as LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

[0068] Satellites can be divided into two types based on the functions they provide: transparent payload and regenerative payload. For transparent payload satellites, they only provide wireless frequency filtering, frequency conversion and amplification functions, and only provide transparent forwarding of signals without changing the waveform signal they forward. For regenerative payload satellites, in addition to providing wireless frequency filtering, frequency conversion and amplification functions, they can also provide demodulation / decoding, routing / conversion, encoding / modulation functions, and have some or all of the functions of a base station.

[0069] In the NTN, one or more gateways may be included for communication between satellites and terminals.

[0070] Figure 4 and Figure 5 Schematic diagrams of NTN scenarios based on transparent forwarding satellites and regenerative forwarding satellites are shown respectively.

[0071] like Figure 4 As shown in FIG, for NTN scenarios based on transparent forwarding satellites, the gateway and the satellite communicate through a feeder link, and the satellite and the terminal can communicate through a service link. Figure 5 As shown, for the NTN scenario based on regenerative forwarding satellites, satellites communicate with each other through interstar links, gateways and satellites communicate with each other through feeder links, and satellites and terminals communicate with each other through service links.

[0072] Each serving cell corresponding to the terminal device has its own Hybrid Automatic Repeat reQuest (HARQ) entity. Each HARQ entity maintains a set of parallel downlink HARQ processes and a set of parallel uplink HARQ processes. Each HARQ process may correspond to a HARQ process ID.

[0073] For downlink transmission: the terminal device detects the DCI according to the configured downlink control information (DCI) format 1_0, DCI format 1_1 or DCI format 1_2 and performs PDSCH decoding according to the DCI scheduling. In some embodiments, for scheduling downlink transmission using a specific HARQ process ID, the following restrictions apply during scheduling:

[0074] The terminal device does not expect to receive another PDSCH for a given HARQ process until after the expected transmission of a Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK) for the HARQ process is completed.

[0075] In other words, if the terminal device receives the first PDSCH for the first HARQ process transmission scheduled by the network device, before the terminal device completes the transmission of the first HARQ-ACK feedback information corresponding to the first PDSCH to the network device, the terminal device does not expect to receive the second PDSCH for the first HARQ process transmission scheduled by the network device again. The transmission timing of the first HARQ-ACK feedback information sent by the terminal device to the network device is determined based on at least one of the HARQ feedback timing set and the HARQ feedback timing value K1, wherein the HARQ feedback timing set may be preset or configured by the network device, and the HARQ feedback timing value K1 is a value in the HARQ feedback timing set.

[0076] Figure 6 A schematic diagram of transmission of HARQ-ACK feedback information provided in an embodiment of the present application, such as Figure 6 As shown, HARQ ID x corresponds to the first HARQ process. When the terminal device receives the first PDSCH scheduled by the network device to transmit HARQ ID x corresponding to the first HARQ process, the terminal device sends the HARQ-ACK feedback information corresponding to the first PDSCH to the network device through the transmission timing K1. The time when the HARQ-ACK feedback information transmission is completed is the earliest time when HARQ ID x can be reused. After the time when the HARQ-ACK feedback information transmission is completed, the terminal device can receive the second PDSCH scheduled by the network device to transmit HARQ ID x corresponding to the first HARQ process. Figure 6 It can be seen from the figure that the time when the HARQ-ACK feedback information transmission is completed is the earliest time when the HARQ ID x can be reused.

[0077] In the NTN system, the downlink HARQ process of the terminal device can be configured into two modes, which correspond to HARQ-ACK feedback enabling or HARQ-ACK feedback disabling, respectively. In the case where a downlink HARQ process of the terminal device is configured with HARQ-ACK feedback disabling, the terminal device may not feedback the HARQ-ACK information corresponding to the downlink HARQ process for the transmission scheduled by the downlink (DownLink, DL) HARQ process. In some embodiments of the present application, the downlink HARQ process configured with HARQ-ACK feedback disabling is also referred to as a downlink HARQ process with HARQ feedback disabled. Accordingly, for the downlink HARQ process configured with HARQ-ACK feedback disabling, the following restrictions are imposed during scheduling:

[0078] Assume that the first HARQ process is configured to disable HARQ-ACK feedback. If the terminal device receives the first PDSCH scheduled by the network device for transmission by the first HARQ process, from the end time of the reception of the first PDSCH to the end of the first duration, the terminal device does not expect to receive the first physical downlink control channel (PDCCH) scheduled by the network device for transmission of the second PDSCH using the first HARQ process again.

[0079] Optionally, the length of the first duration is T_proc,1, and T_proc,1 is determined according to a PDSCH decoding time N1 value (in symbols).

[0080] The first PDSCH may be one PDSCH or a group of slot-aggregated PDSCHs.

[0081] The second PDSCH may be one PDSCH or a group of time slot aggregated PDSCHs.

[0082] The transport blocks (Transport Block, TB) of the first PDSCH and the second PDSCH may be the same or different.

[0083] The processing capability 1 and the processing capability 2 of the UE correspond to different processing capabilities, or in other words, the N1 value corresponding to the processing capability 1 of the UE is different from the N1 value corresponding to the processing capability 2 of the UE. The value of N1 is different under different subcarrier spacings.

[0084] By way of example and not limitation, T proc,1 =(N1+d 1,1 +d2)(2048+144)·κ2 -μ ·T C +T ext It should be noted that T proc,1 The same understanding is given to T_proc,1. The calculation method of T_proc,1 may be specified by the protocol, or may be specified according to the evolved protocol. The embodiment of the present application does not limit the calculation method of T_proc,1.

[0085] Figure 7 A schematic diagram of another transmission of HARQ-ACK feedback information provided in an embodiment of the present application, such as Figure 7 As shown, HARQ ID x corresponds to the first HARQ process, and when the terminal device receives the first PDSCH scheduled by the network device for HARQ ID x to be transmitted by the first HARQ process, the time from the end time of receiving the first PDSCH to the end time of the first duration, such as T_proc,1, is the earliest time when the DCI scheduled for HARQ ID x can be received. After the end time of the first duration, the terminal device can receive the first DCI and determine that the HARQ ID x scheduled by the first DCI corresponds to the second PDSCH transmitted by the first HARQ process.

[0086] In the NTN system, the HARQ-ACK feedback corresponding to the activation of the Semi-Persistent Scheduling (SPS) configuration may be enabled by the network device through the Radio Resource Control (RRC) configuration.

[0087] In some embodiments, when the network device enables the HARQ-ACK feedback corresponding to the SPS configuration activation through RRC configuration, regardless of whether the HARQ process corresponding to the first SPS PDSCH after the SPS configuration is activated is configured as HARQ-ACK feedback enabled or HARQ-ACK feedback disabled, the terminal device needs to report the ACK or NACK information corresponding to the first SPS PDSCH after the SPS configuration is activated.

[0088] In other embodiments, when the network device does not enable the HARQ-ACK feedback corresponding to the SPS configuration activation through RRC configuration, or the network device does not enable the HARQ-ACK feedback corresponding to the SPS configuration activation through RRC configuration, when the HARQ process corresponding to the first SPS PDSCH after the SPS configuration is activated is configured to enable HARQ-ACK feedback, the terminal device reports the ACK or NACK information corresponding to the first SPS PDSCH after the SPS configuration is activated; when the HARQ process corresponding to the first SPS PDSCH after the SPS configuration is activated is configured to disable HARQ-ACK feedback, the terminal device does not report the ACK or NACK information corresponding to the first SPS PDSCH after the SPS configuration is activated.

[0089] After the SPS configuration is activated, for other SPS PDSCHs except the first SPS PDSCH, when the HARQ process corresponding to the SPS PDSCH is configured to enable HARQ-ACK feedback, the terminal device reports the ACK or NACK information corresponding to the SPS PDSCH; when the HARQ process corresponding to the SPS PDSCH is configured to disable HARQ-ACK feedback, the terminal device does not report the ACK or NACK information corresponding to the SPS PDSCH.

[0090] However, in the NTN system, since the first SPS PDSCH may feedback the corresponding HARQ-ACK information in some cases, but may not feedback the corresponding HARQ-ACK information in other cases, how to determine the scheduling restriction of the SPS PDSCH is a problem to be solved.

[0091] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above-mentioned solutions can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0092] Figure 8 A flow chart of a communication method provided in an embodiment of the present application is shown as follows: Figure 8 As shown, the method includes:

[0093] S801. A terminal device receives a first physical downlink shared channel PDSCH scheduled by a network device for transmission in a first hybrid automatic repeat request HARQ process.

[0094] In some embodiments, the first PDSCH is the first PDSCH after the semi-persistent scheduling SPS configuration is activated. In this case, the first PDSCH may be activated by the PDCCH, or it can be said that the first PDSCH is an SPS PDSCH corresponding to or associated with the PDCCH.

[0095] In some embodiments, the first PDSCH is scheduled by PDCCH.

[0096] In some embodiments, the first PDSCH is an SPS PDSCH that does not correspond to a PDCCH. In this case, the resources of the first PDSCH may be preconfigured, and the first PDSCH does not correspond to or is not associated with a PDCCH, or in other words, the first PDSCH is not the first PDSCH after the SPS configuration is activated.

[0097] It should be noted that, for the activated SPS configuration, the first PDSCH after the SPS configuration is activated may be a PDSCH corresponding to or associated with a PDCCH, and other PDSCHs except the first PDSCH are not PDSCHs corresponding to or associated with a PDCCH, or it can be said that other PDSCHs except the first PDSCH are SPS PDSCHs not corresponding to a PDCCH. For example, other PDSCHs except the first PDSCH may correspond to or be associated with an RRC.

[0098] Optionally, the first HARQ process may be configured as hybrid automatic repeat request-acknowledgement HARQ-ACK feedback enabled, or the first HARQ process may be configured as HARQ-ACK feedback disabled.

[0099] In some implementations, the HARQ-ACK may include an ACK and a negative acknowledgement (Negative ACK acknowledgement, NACK), or the HARQ-ACK may include one of an ACK and a NACK.

[0100] S803: The terminal device does not expect to receive the second PDSCH scheduled by the network device for transmission of the first HARQ process within the first time range, or does not expect to receive the first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process to transmit the second PDSCH.

[0101] In some embodiments, an implementation of S803 may include: the terminal device does not monitor or cannot monitor or cannot detect the second PDSCH or the first PDCCH sent by the network device within the first time range.

[0102] In this way, when the network device sends the first PDSCH to the terminal device, the network device will not send the second PDSCH or the first PDCCH to the terminal device within the second time range, and the terminal device does not listen to or cannot listen to or detect the second PDSCH or the first PDCCH sent by the network device within the first time range, thereby avoiding the situation where the network device schedules the second PDSCH or the first PDCCH to the terminal device when the terminal device does not expect to receive the second PDSCH or the first PDCCH, thereby causing a waste of resources.

[0103] In other embodiments, an implementation of S803 may include: the terminal device may monitor or detect a first PDCCH sent by a network device within a first time range, but the terminal device may not receive a second PDSCH scheduled by the monitored or detected first PDCCH, or the terminal device may not respond to or ignore the monitored or detected second PDSCH or first PDCCH.

[0104] In this way, when the network device sends the first PDSCH to the terminal device, the network device will also send the second PDSCH or the first PDCCH to the terminal device within the second time range, so that the terminal device can monitor or detect that the network device has sent the second PDSCH or the first PDCCH within the first time range, but the terminal device may not receive the second PDSCH, thereby eliminating the need to change the configuration of the network device to send the second PDSCH or the first PDCCH.

[0105] In an embodiment of the present application, a terminal device receives a first physical downlink shared channel PDSCH that is scheduled by a network device for a first hybrid automatic repeat request HARQ process transmission; the terminal device does not expect to receive a second PDSCH that is scheduled by the network device for the first HARQ process transmission within a first time range, or does not expect to receive a first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process transmission of the second PDSCH. In this way, the scheduling of the PDSCH can be restricted to avoid the terminal device from receiving the PDSCH out of order.

[0106] In some embodiments, the starting time of the first time range is: the end time of the reception of the first PDSCH. In some embodiments, the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device. Optionally, in this case, the terminal device sends the first HARQ-ACK feedback information corresponding to the first PDSCH to the network device. That is, when the terminal device receives the first PDSCH, it sends the HARQ-ACK feedback information corresponding to the first PDSCH to the network device.

[0107] Optionally, the transmission end time of the HARQ-ACK feedback information can be determined based on the timing advance (TA). For example, the terminal device receives the first PDSCH at time n, and the terminal device can determine to feed back the first HARQ-ACK feedback information corresponding to the first PDSCH at a time interval of a specified duration T0 at time n. Considering TA, the terminal device can send the HARQ-ACK feedback information corresponding to the first PDSCH at time n+T0-TA. Optionally, the time n, the time interval of a specified duration T0 at time n, and the time n+T0-TA here may refer to a symbol, a time slot, a mini-time slot, a subframe, or a radio frame.

[0108] Optionally, the transmission end time of the HARQ-ACK feedback information is determined based on the uplink timing of the terminal device.

[0109] Optionally, the HARQ-ACK feedback information may be referred to as HARQ-ACK feedback, HARQ feedback, or HARQ process feedback, etc. in other embodiments.

[0110] In some embodiments, the first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

[0111] The following examples illustrate the first time range corresponding to the first HARQ process being configured with HARQ-ACK feedback disabling or HARQ-ACK feedback enabling:

[0112] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback disabled, the starting time of the first time range is: the ending time of the first PDSCH reception, and the ending time of the first time range is: the ending time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0113] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback disabled, regardless of whether the terminal device is configured to enable semi-persistent scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0114] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback enabled, the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0115] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback enabled, regardless of whether the terminal device is configured to enable semi-persistent scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0116] In some embodiments, it is necessary to consider not only whether the first HARQ process is configured to enable HARQ-ACK feedback or to disable HARQ-ACK feedback, but also whether the terminal device is configured to enable SPS configuration activation corresponding to HARQ-ACK feedback or is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback.

[0117] In some embodiments, if the terminal device is configured to enable at least one of the SPS configuration activation corresponding HARQ-ACK feedback and the first HARQ process corresponding HARQ-ACK feedback enablement, the terminal device determines that it needs to send the first HARQ-ACK feedback information to the network device, so that the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-confirmation HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0118] In some embodiments, if the terminal device is configured to enable semi-continuous scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled, the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0119] In other embodiments, if the terminal device is configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured to disable HARQ-ACK feedback, the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0120] In some further embodiments, if the terminal device is not configured to enable the SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured to enable HARQ-ACK feedback, the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0121] In some further embodiments, if the first PDSCH corresponds to a first HARQ-ACK feedback, the starting time of the first time range is: the ending time of the reception of the first PDSCH, and the ending time of the first time range is: the ending time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0122] Optionally, the first PDSCH corresponds to the first HARQ-ACK feedback, which can be understood as the terminal device needs to send the first HARQ-ACK feedback information to the network device. The first PDSCH is transmitted through the first HARQ process, and the first HARQ-ACK feedback information can be determined by the terminal device according to the decoding result of the first PDSCH, or a preset value configured by the network device to the terminal device, such as ACK or NACK.

[0123] Optionally, the transmission timing of the first HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device may be pre-configured by the terminal device, or may be configured by the network device, or may be specified by the protocol, or may be calculated by the terminal device, or may be calculated by the network device and configured to the terminal device. The terminal device may determine the end time of the first time range based on the transmission timing of the first HARQ-ACK feedback information.

[0124] In some embodiments, the transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device may be determined by the terminal device. For example, the transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined according to at least one of the following: a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1.

[0125] Optionally, the transmission timing of the first HARQ-ACK feedback information may be a value minus the time advance, for example, the transmission timing of the first HARQ-ACK feedback information may be the above-mentioned duration T0-TA, or, may be a value without subtracting the time advance, for example, the transmission timing of the first HARQ-ACK feedback information may be the above-mentioned duration T0.

[0126] Optionally, the HARQ feedback timing set may be preset by the terminal device, configured by the network device, or specified by the protocol. The HARQ feedback timing set may include one or more HARQ feedback timing values ​​K1, and the unit of each timing in the one or more timings may be a subframe, a time slot, a mini-time slot, or a symbol, etc.

[0127] Optionally, the offset value Koffset is a value configured by the NTN network. The offset value Koffset may be a common offset value of a cell, which may be broadcast by a network device, or the offset value Koffset may be a dedicated offset value of a terminal device, which may be configured by the network device to the terminal device, or the dedicated offset value of the terminal device may be determined by the terminal device based on an offset value increment configured by the network device.

[0128] Optionally, the HARQ feedback timing value K1 may be configured by the network device to the terminal device, or preset by the terminal device, or agreed upon by a protocol, or calculated by the terminal device, or calculated by the network device and configured to the terminal device.

[0129] In some other embodiments, the starting time of the first time range is: the ending time of the first PDSCH reception; the duration corresponding to the first time range is the first duration. Optionally, in this case, the terminal device does not send the first HARQ-ACK feedback information corresponding to the first PDSCH to the network device.

[0130] Optionally, the first duration may be the above-mentioned T_proc,1.

[0131] In some embodiments, the first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

[0132] The following examples illustrate the first time range corresponding to the first HARQ process being configured with HARQ-ACK feedback disabling or HARQ-ACK feedback enabling:

[0133] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback disabled, the starting time of the first time range is: the ending time of the first PDSCH reception; and the duration corresponding to the first time range is the first duration.

[0134] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback disabled, regardless of whether the terminal device is configured to enable semi-persistent scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the first time range is: the end time of the first PDSCH reception; the duration corresponding to the first time range is the first duration.

[0135] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback enabled, the starting time of the first time range is: the ending time of the first PDSCH reception; and the duration corresponding to the first time range is the first duration.

[0136] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback enabled, regardless of whether the terminal device is configured to enable semi-continuous scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the first time range is: the end time of the first PDSCH reception; the duration corresponding to the first time range is the first duration.

[0137] In some embodiments, it is necessary to consider not only whether the first HARQ process is configured to enable HARQ-ACK feedback or to disable HARQ-ACK feedback, but also whether the terminal device is configured to enable SPS configuration activation corresponding to HARQ-ACK feedback or is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback.

[0138] In some embodiments, if the terminal device is not configured to enable the SPS configuration to activate the corresponding HARQ-ACK feedback and the first HARQ process is not configured to require HARQ-ACK feedback, the terminal device can determine that it is not necessary to send the first HARQ-ACK feedback information to the network device, so that the starting time of the first time range is: the end time of the first PDSCH reception; the duration corresponding to the first time range is the first duration.

[0139] In some embodiments, if the terminal device is not configured to enable the SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured to disable the HARQ-ACK feedback, the starting time of the first time range is: the end time of the first PDSCH reception; the duration corresponding to the first time range is the first duration.

[0140] In some other embodiments, if the first PDSCH does not correspond to the first HARQ-ACK feedback, the starting time of the first time range is: the ending time of the first PDSCH reception; and the duration corresponding to the first time range is the first duration.

[0141] Optionally, the first PDSCH does not correspond to the first HARQ-ACK feedback, which can be understood as the terminal device does not need to send the first HARQ-ACK feedback information to the network device. The first PDSCH does not correspond to the first HARQ-ACK feedback, which can be determined by the terminal device itself or configured by the network device to the terminal device.

[0142] In some other feasible embodiments, if one of the terminal device and the first HARQ process is configured to require HARQ-ACK feedback and the other is not configured to require HARQ-ACK feedback, the terminal device determines that it is not necessary to send the first HARQ-ACK feedback information to the network device, so that the starting time of the first time range is: the end time of the first PDSCH reception; the duration corresponding to the first time range is the first duration.

[0143] Optionally, one of the terminal device and the first HARQ process is configured to require HARQ-ACK feedback, and the other is not configured to require HARQ-ACK feedback, which may include: the terminal device is configured to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured to disable HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured to enable HARQ-ACK feedback.

[0144] In some embodiments, the first duration is determined based on at least one of the following: a processing capability of the terminal device, a subcarrier spacing, and a decoding duration of the first PDSCH.

[0145] Optionally, the unit of the decoding duration N1 of the first PDSCH may be a symbol. Optionally, the decoding duration N1 of the first PDSCH corresponding to terminal devices with different processing capabilities may be different. Exemplarily, the processing capability 1 and the processing capability 2 of the terminal device correspond to different processing capabilities, and the N1 value corresponding to the processing capability 1 of the terminal device is different from the N1 value corresponding to the processing capability 2 of the terminal device. Optionally, the decoding duration N1 of the first PDSCH corresponding to different subcarrier spacings may be different.

[0146] Optionally, the decoding duration of the first PDSCH may be preset by the terminal device, or configured by the network device to the terminal device, or specified by a protocol, or calculated by the terminal device, or calculated by the network device and configured to the terminal device.

[0147] In some implementations, enabling the SPS configuration to activate the corresponding HARQ-ACK feedback may be configured by RRC. The network device may enable the SPS configuration to activate the corresponding HARQ-ACK feedback through a radio resource control RRC configuration.

[0148] Optionally, the terminal device is configured to enable SPS configuration to activate corresponding HARQ-ACK feedback, including: the terminal device is configured by the network device to enable SPS configuration to activate corresponding HARQ-ACK feedback through RRC.

[0149] Optionally, the terminal device is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback, including: the terminal device is disenabled by the network device through RRC configuration to enable SPS configuration activation corresponding to HARQ-ACK feedback; or, the terminal device is not configured by the network device to enable RRC signaling for SPS configuration activation corresponding to HARQ-ACK feedback.

[0150] In this way, the network device can enable the SPS configuration to activate the corresponding HARQ-ACK feedback through RRC configuration. The feedback of the HARQ process associated with the SPS PDSCH can be enabled or disabled through each SPS configuration (RRC configuration per SPS configuration) configured by RRC. Among them, activating the corresponding HARQ-ACK feedback may include: enabling HARQ-ACK feedback or disabling HARQ-ACK feedback; enabling HARQ-ACK feedback may correspond to HARQ-ACK feedback enabling, and disabling HARQ-ACK feedback may correspond to HARQ-ACK feedback disabling.

[0151] In some embodiments, the not expecting to receive the second PDSCH scheduled by the network device for transmission by the first HARQ process includes: when the terminal device is scheduled by the network device to receive the second PDSCH using the first HARQ process within the first time range, the terminal device does not receive the second PDSCH. In this case, the terminal device is able to monitor or detect the first PDCCH that schedules the second PDSCH or can know through pre-configuration that the first time range includes resources for transmitting the second PDSCH, but the terminal device does not receive the second PDSCH.

[0152] In some other embodiments, the not expecting to receive the first physical downlink control channel PDCCH includes: when the terminal device is scheduled by the network device to receive the first PDCCH within the first time range, the terminal device does not receive the second PDSCH scheduled by the first PDCCH. In this case, the terminal device is able to monitor or detect the first PDCCH, but the terminal device does not receive the second PDSCH scheduled by the first PDCCH.

[0153] In some embodiments, the second PDSCH is scheduled by PDCCH.

[0154] In some embodiments, the second PDSCH is an SPS PDSCH that does not correspond to a PDCCH. In this case, the second PDSCH may be pre-configured, and the second PDSCH is not the first PDSCH after the SPS configuration is activated.

[0155] In some embodiments, the method further comprises:

[0156] In a case where the second HARQ process is configured with HARQ-ACK feedback enabled, the terminal device receives a third PDSCH for the network device to schedule transmission of the second HARQ process; the third PDSCH is an SPS PDSCH that does not correspond to the PDCCH;

[0157] Starting from the end time of receiving the third PDSCH to the end time of sending the second HARQ-ACK feedback information corresponding to the third PDSCH to the network device, the terminal device does not expect to receive the fourth PDSCH scheduled by the network device for transmission of the second HARQ process, or does not expect to receive the second PDCCH, wherein the second PDCCH is used by the network device to schedule the second HARQ process to transmit the fourth PDSCH.

[0158] In some embodiments, the method further comprises:

[0159] When the second HARQ process is configured with HARQ-ACK feedback disabled, the terminal device receives a third PDSCH scheduled by the network device for transmission of the second HARQ process; the third PDSCH is an SPS PDSCH that does not correspond to the PDCCH;

[0160] From the end moment of receiving the third PDSCH to the end of the second time period, the terminal device does not expect to receive the fourth PDSCH scheduled by the network device for transmission of the second HARQ process, or does not expect to receive the second PDCCH, wherein the second PDCCH is used by the network device to schedule the second HARQ process to transmit the fourth PDSCH.

[0161] In some embodiments, the first duration and the second duration are the same duration.

[0162] In some embodiments, the first time range and the second time range are the same time range.

[0163] Optionally, the second HARQ process may be a HARQ process subsequent to the first HARQ process.

[0164] Optionally, the second HARQ process in the embodiment of the present application may be a HARQ process corresponding to at least one other SPS PDSCH except the first SPS PDSCH after the SPS configuration is activated.

[0165] Optionally, the first time range may be a continuous time range. The starting moment of the first time range may be the first moment, the ending moment (or end moment) of the first time range may be the second moment after the first moment, and the duration between the second moment and the first moment may be a specific duration. The first moment may be included in the first time range, or the first moment may not be included in the first time range. The second moment may be included in the first time range, or the second moment may not be included in the first time range.

[0166] Optionally, the start time of the first time range may be the end time of the first PDSCH reception. The specific duration corresponding to the first time range may be one of the following: preset by the terminal device, configured by the network device to the terminal device, specified by the protocol, calculated by the terminal device, calculated by the network device and configured to the terminal device.

[0167] Optionally, the terminal device may start or restart a timer with a specific duration at a first moment, during which the terminal device does not expect to receive the second PDSCH or does not expect to receive the first PDCCH.

[0168] Optionally, the second time range may be a continuous time range, the start time of the second time range may be the third time, the end time (or end time) of the second time range may be the fourth time after the third time, and the duration between the fourth time and the third time may be the target duration. In some embodiments, the target duration corresponding to the second time range may be the same as the specific duration corresponding to the first time range, or the target duration corresponding to the second time range may be greater than the specific duration corresponding to the first time range. The third time may be included in the second time range, or the third time may not be included in the second time range. The fourth time may be included in the second time range, or the fourth time may not be included in the second time range.

[0169] Optionally, the start time and / or end time of the first time range and / or the second time range may be represented by at least one of the following: symbol, time slot or subframe. For example, the start time of the first time range and / or the second time range may be one of the following: start symbol, start time slot or start subframe, and the end time of the first time range and / or the second time range may be one of the following: end symbol, end time slot or end subframe. Exemplarily, the start time of the first time range and / or the second time range may be the start symbol, and the end time of the first time range and / or the second time range may be the end symbol.

[0170] The following describes the communication methods corresponding to network devices:

[0171] Fig. 9A flow chart of a communication method provided in an embodiment of the present application is shown as follows: Fig. 9 As shown, the method includes:

[0172] S901. A network device sends a first physical downlink shared channel PDSCH for scheduling transmission of a first hybrid automatic repeat request HARQ process to a terminal device.

[0173] In some embodiments, the first PDSCH is the first PDSCH after the semi-persistent scheduling SPS configuration is activated.

[0174] In some embodiments, the first PDSCH is scheduled by PDCCH.

[0175] In some embodiments, the first PDSCH is a SPS PDSCH that does not correspond to a PDCCH.

[0176] S903: The network device does not expect to send a second PDSCH for scheduling the transmission of the first HARQ process to the terminal device within a second time range, or does not expect to send a first physical downlink control channel PDCCH to the terminal device, wherein the first PDCCH is used by the network device to schedule the transmission of the second PDSCH by the first HARQ process.

[0177] Not expecting to send the second PDSCH for scheduling the transmission of the first HARQ process to the terminal device, or not expecting to send the first physical downlink control channel PDCCH to the terminal device, may include the following two situations:

[0178] The first type: the network device may not send the second PDSCH that schedules the transmission of the first HARQ process to the terminal device within the second time range, or may not send the first PDCCH to the terminal device, when sending the first PDSCH to the terminal device. The starting time of the second time range may be the ending time of the sending of the first PDSCH. In this way, not expecting to send the second PDSCH that schedules the transmission of the first HARQ process to the terminal device, or not expecting to send the first PDCCH to the terminal device in S903, includes: not sending the second PDSCH that schedules the transmission of the first HARQ process to the terminal device, or not sending the first PDCCH to the terminal device.

[0179] The second type: the network device may send a second PDSCH for scheduling the transmission of the first HARQ process to the terminal device within a second time range, or send a first PDCCH to the terminal device when sending a first PDSCH to the terminal device, but the terminal device does not receive the second PDSCH or the first PDCCH when monitoring or detecting the second PDSCH or the first PDCCH. The network device may send the second PDSCH or the first PDCCH to the terminal device within the second time range based on pre-configuration or protocol provisions. In this way, not expecting to send the second PDSCH for scheduling the transmission of the first HARQ process to the terminal device, or not expecting to send the first PDCCH to the terminal device in S903, includes: sending the second PDSCH for scheduling the transmission of the first HARQ process to the terminal device, or sending the first PDCCH to the terminal device, but the network device does not expect to receive the third HARQ-ACK feedback information corresponding to the second PDSCH. That is, when the network device sends the second PDSCH or the first PDCCH to the terminal device, the terminal device does not receive the second PDSCH or the first PDCCH, so that the terminal device does not send the third HARQ-ACK feedback information corresponding to the second PDSCH to the network device, so that the network device cannot receive the third HARQ-ACK feedback information corresponding to the second PDSCH.

[0180] In some embodiments, the start time of the second time range is: the end time of the first PDSCH transmission. In some embodiments, the end time of the second time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0181] Optionally, the transmission end time of the HARQ-ACK feedback information is determined based on the uplink timing of the network device.

[0182] In some embodiments, the start time of the second time range is: the end time of the first PDSCH transmission. In some embodiments, the end time of the second time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device determined by the network device.

[0183] Optionally, the transmission end time of the HARQ-ACK feedback information is determined based on the uplink timing of the terminal device.

[0184] In some embodiments, the first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

[0185] The following examples illustrate the second time range corresponding to the first HARQ process being configured with HARQ-ACK feedback disabled or HARQ-ACK feedback enabled:

[0186] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback disabled, the starting time of the second time range is: the ending time of the sending of the first PDSCH; the ending time of the second time range is: the ending time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0187] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback disabled, regardless of whether the terminal device is configured to enable semi-persistent scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the second time range is: the end time of the first PDSCH transmission; the end time of the second time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0188] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback enabled, the starting time of the second time range is: the end time of the first PDSCH sending; the end time of the second time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0189] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback enabled, regardless of whether the terminal device is configured to enable semi-persistent scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the second time range is: the end time of the first PDSCH sending; the end time of the second time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0190] In some embodiments, it is necessary to consider not only whether the first HARQ process is configured to enable HARQ-ACK feedback or to disable HARQ-ACK feedback, but also whether the terminal device is configured to enable SPS configuration activation corresponding to HARQ-ACK feedback or is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback.

[0191] In some embodiments, if the network device configures the terminal device to enable semi-persistent scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled, the starting time of the second time range is: the end time of the first PDSCH sending, and the end time of the second time range is: the end time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0192] In other embodiments, if the network device configures the terminal device to enable SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured to disable HARQ-ACK feedback, the starting time of the second time range is: the end time of sending the first PDSCH, and the end time of the second time range is: the end time of transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0193] In some further embodiments, if the network device does not configure the terminal device to enable SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled, the starting time of the second time range is: the end time of sending the first PDSCH, and the end time of the second time range is: the end time of transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0194] In some further embodiments, if the first PDSCH corresponds to a first HARQ-ACK feedback, the starting time of the second time range is: the ending time of sending the first PDSCH, and the ending time of the second time range is: the ending time of transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0195] In some embodiments, the transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined based on at least one of the following: a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1.

[0196] In some embodiments, the start time of the second time range is: the end time of the first PDSCH transmission; the duration corresponding to the second time range is the first duration. The first duration may be the above-mentioned T_proc,1.

[0197] In some embodiments, the first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

[0198] The following examples illustrate the second time range corresponding to the first HARQ process being configured with HARQ-ACK feedback disabled or HARQ-ACK feedback enabled:

[0199] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback disabled, the starting time of the second time range is: the ending time of the first PDSCH transmission; and the duration corresponding to the second time range is the first duration.

[0200] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback disabled, regardless of whether the terminal device is configured to enable semi-continuous scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the second time range is: the end time of the first PDSCH transmission; the duration corresponding to the second time range is the first duration.

[0201] In some embodiments, when the first HARQ process is configured with HARQ-ACK feedback enabled, the starting time of the second time range is: the ending time of the first PDSCH transmission; and the duration corresponding to the second time range is the first duration.

[0202] Exemplarily, when the first HARQ process is configured with HARQ-ACK feedback enabled, regardless of whether the terminal device is configured to enable semi-continuous scheduling SPS configuration to activate the corresponding HARQ-ACK feedback, or the terminal device is not configured to enable SPS configuration to activate the corresponding HARQ-ACK feedback, the starting time of the second time range is: the end time of the first PDSCH transmission; the duration corresponding to the second time range is the first duration.

[0203] In some embodiments, it is necessary to consider not only whether the first HARQ process is configured to enable HARQ-ACK feedback or to disable HARQ-ACK feedback, but also whether the terminal device is configured to enable SPS configuration activation corresponding to HARQ-ACK feedback or is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback.

[0204] In some embodiments, if the network device does not configure the terminal device to enable SPS configuration to activate the corresponding HARQ-ACK feedback, and the first HARQ process is configured to disable HARQ-ACK feedback, the starting time of the second time range is: the end time of the first PDSCH transmission; the duration corresponding to the second time range is the first duration.

[0205] In some other embodiments, if the first PDSCH does not correspond to the first HARQ-ACK feedback, the starting time of the second time range is: the ending time of the first PDSCH sending; and the duration corresponding to the second time range is the first duration.

[0206] In other embodiments of the present application, if the network device configures the terminal device to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured to disable HARQ-ACK feedback, or if the network device does not configure the terminal device to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured to enable HARQ-ACK feedback, the starting time of the second time range is: the end time of the first PDSCH sending; the duration corresponding to the second time range is the first duration.

[0207] In some embodiments, the first duration is determined based on at least one of the following: a processing capability of the terminal device, a subcarrier spacing, and a decoding duration of the first PDSCH.

[0208] In some embodiments, the not expecting to send the second PDSCH scheduling the transmission of the first HARQ process to the terminal device includes: when the network device sends the second PDSCH scheduling the transmission of the first HARQ process to the terminal device within the second time range, the network device does not receive the third HARQ-ACK feedback information corresponding to the second PDSCH.

[0209] In some embodiments, not expecting to send the first physical downlink control channel PDCCH to the terminal device includes: when the network device sends the first PDCCH to the terminal device within the second time range, the network device does not receive the third HARQ-ACK feedback information corresponding to the second PDSCH.

[0210] Optionally, the network device does not receive the third HARQ-ACK feedback information corresponding to the second PDSCH, which may be that the network device cannot receive the third HARQ-ACK feedback information corresponding to the second PDSCH. The network device may not receive the third HARQ-ACK feedback information corresponding to the second PDSCH at any time after sending the second PDSCH or the first PDCCH to the terminal device.

[0211] In some embodiments, the second PDSCH is scheduled by PDCCH.

[0212] In some embodiments, the second PDSCH is a SPS PDSCH that does not correspond to a PDCCH.

[0213] In some embodiments, the method further comprises:

[0214] In a case where the second HARQ process is configured with HARQ-ACK feedback enabled, the network device sends a third PDSCH for scheduling transmission of the second HARQ process to the terminal device; the third PDSCH is an SPS PDSCH that does not correspond to the PDCCH;

[0215] Starting from the end time of sending the third PDSCH to the end time of receiving the transmission of the second HARQ-ACK feedback information corresponding to the third PDSCH sent by the terminal device, the network device does not expect to send the fourth PDSCH for scheduling the transmission of the second HARQ process to the terminal device, or does not expect to send the second PDCCH to the terminal device, wherein the second PDCCH is used by the network device to schedule the second HARQ process to transmit the fourth PDSCH.

[0216] In some embodiments, the method further comprises:

[0217] In a case where the second HARQ process is configured with HARQ-ACK feedback disabled, the network device sends a third PDSCH for scheduling transmission of the second HARQ process to the terminal device; the third PDSCH is an SPS PDSCH that does not correspond to the PDCCH;

[0218] The network device does not expect to send the fourth PDSCH for scheduling the transmission of the second HARQ process to the terminal device, or does not expect to send the second PDCCH to the terminal device, wherein the second PDCCH is used by the network device to schedule the transmission of the fourth PDSCH by the second HARQ process, before the end of the second time period.

[0219] In some embodiments, the first duration and the second duration are the same duration.

[0220] In some embodiments, the first time range and the second time range are the same time range.

[0221] Some embodiments of the communication method of the present application are described below:

[0222] It should be noted that in the following embodiments, the first HARQ process is the HARQ process corresponding to the first SPS PDSCH after the SPS configuration is activated. The second HARQ process is the HARQ process corresponding to at least one other SPS PDSCH except the first SPS PDSCH after the SPS configuration is activated.

[0223] In some embodiments, when the network device enables SPS configuration activation corresponding HARQ-ACK feedback through RRC configuration, the scheduling constraints of the first HARQ process satisfy:

[0224] If a terminal device receives a first PDSCH for a first HARQ process to be transmitted scheduled by a network device, before the terminal device completes the transmission of the first HARQ-ACK feedback information corresponding to the first PDSCH to the network device, the terminal device does not expect to receive a second PDSCH for a first HARQ process to be transmitted scheduled by the network device again, or the terminal device does not expect to receive a PDCCH (i.e., the first PDCCH mentioned above) for a second PDSCH to be transmitted by the network device again. The transmission timing of the first HARQ-ACK feedback information to be transmitted by the terminal device to the network device is determined based on at least one of a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1, wherein the HARQ feedback timing set may be preset or configured by a network device, and the HARQ feedback timing value K1 is a value in the HARQ feedback timing set.

[0225] In a feasible implementation manner of this embodiment, the first HARQ process is configured with HARQ-ACK feedback disabled.

[0226] In a feasible implementation manner of this embodiment, the first HARQ process is configured with HARQ-ACK feedback enabled.

[0227] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0228] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0229] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0230] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0231] Fig.10 A schematic diagram of a scheduling restriction of a first HARQ process provided in an embodiment of the present application is shown as follows: Fig.10 As shown, the network device can send the first SPS PDSCH after the SPS configuration is activated to the terminal device, as well as other SPS PDSCHs except the first SPS PDSCH. The first SPS PDSCH can be the one that schedules the transmission of the first HARQ process (HARQ ID n). When the terminal device receives the first SPS PDSCH, it can send HARQ-ACK feedback information corresponding to the first SPS PDSCH to the network device. In some embodiments, the first SPS PDSCH can be the first PDSCH mentioned above. Within the time range corresponding to the end time when the terminal device receives the first SPS PDSCH to the end time when the HARQ-ACK feedback information is sent, the terminal device does not expect to receive another PDSCH that schedules the transmission of the first HARQ process. Fig.10 After the time corresponding to the dotted line, the terminal device can receive the DCI scheduled for HARQ ID n, or receive the SPS PDSCH corresponding to HARQ ID n.

[0232] In some embodiments, when the network device enables SPS configuration activation corresponding HARQ-ACK feedback through RRC configuration, the scheduling constraints of the first HARQ process satisfy:

[0233] When the first HARQ process is configured with HARQ-ACK feedback enabled, if the terminal device receives the first PDSCH scheduled by the network device for transmission of the first HARQ process, before the terminal device completes the transmission of the first HARQ-ACK feedback information corresponding to the first PDSCH to the network device, the terminal device does not expect to receive the second PDSCH scheduled by the network device for transmission of the first HARQ process again, or the terminal device does not expect to receive the PDCCH that the network device schedules the first HARQ process to transmit the second PDSCH again. The transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined based on at least one of the HARQ feedback timing set, the offset value Koffset, and the HARQ feedback timing value K1, wherein the HARQ feedback timing set may be preset or configured by the network device, and the HARQ feedback timing value K1 is a value in the HARQ feedback timing set. And / or,

[0234] When the first HARQ process is configured with HARQ-ACK feedback disabled, if the terminal device receives the first PDSCH scheduled by the network device for transmission using the first HARQ process, from the end moment of reception of the first PDSCH to the end of the first time period, the terminal device does not expect to receive the first PDCCH scheduled by the network device for transmission of the second PDSCH using the first HARQ process again, or the terminal device does not expect to receive the second PDSCH transmitted by the network device using the first HARQ process again.

[0235] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0236] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0237] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0238] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0239] Fig.11 A schematic diagram of another scheduling restriction of the first HARQ process provided in an embodiment of the present application is shown as follows: Fig.11As shown, the network device can send the first SPS PDSCH after the SPS configuration is activated, as well as other SPS PDSCHs except the first SPS PDSCH to the terminal device. The first SPS PDSCH can be used to schedule the transmission of the first HARQ process (HARQ ID n).

[0240] When the first HARQ process is configured with HARQ-ACK feedback enable, the terminal device can send the HARQ-ACK feedback information corresponding to the first SPS PDSCH to the network device when receiving the first SPS PDSCH. In some embodiments, the first SPS PDSCH can be the above-mentioned first PDSCH. Within the time range corresponding to the end time of the terminal device receiving the first SPS PDSCH to the end time of sending the HARQ-ACK feedback information, the terminal device does not expect to receive another PDSCH scheduled for transmission by the first HARQ process. That is, when HARQ ID n is configured with HARQ-ACK feedback enable, the DCI scheduling HARQ ID n can be received after the dotted line, or the SPS PDSCH corresponding to HARQ ID n can be received.

[0241] When the first HARQ process is configured with HARQ-ACK feedback disabled, the terminal device may not send the HARQ-ACK feedback information corresponding to the first SPS PDSCH to the network device when receiving the first SPS PDSCH. Within the time range corresponding to the end moment when the terminal device receives the first SPS PDSCH to the first duration T_proc,1, the terminal device does not expect to receive another PDSCH scheduled for transmission by the first HARQ process. That is, when HARQ ID n is configured with HARQ-ACK feedback enabled, the DCI scheduling HARQ ID n can be received after the dotted line, or the SPS PDSCH corresponding to HARQ ID n can be received.

[0242] In some embodiments, when the network device enables SPS configuration activation corresponding HARQ-ACK feedback through RRC configuration, the scheduling constraints of the first HARQ process satisfy:

[0243] If a terminal device receives a first PDSCH scheduled by a network device for transmission using a first HARQ process, from the end moment of reception of the first PDSCH to the end of the first time period, the terminal device does not expect to receive again the first PDCCH scheduled by the network device for transmission of a second PDSCH using the first HARQ process, or the terminal device does not expect to receive again the second PDSCH transmitted by the network device using the first HARQ process.

[0244] In a feasible implementation manner of this embodiment, the first HARQ process is configured with HARQ-ACK feedback disabled.

[0245] In a feasible implementation manner of this embodiment, the first HARQ process is configured with HARQ-ACK feedback enabled.

[0246] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0247] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0248] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0249] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0250] Fig.12 A schematic diagram of another scheduling restriction of the first HARQ process provided in an embodiment of the present application is shown as follows: Fig.12 As shown, the network device can send the first SPS PDSCH after the SPS configuration is activated, as well as other SPS PDSCHs except the first SPS PDSCH to the terminal device. The first SPS PDSCH can be used to schedule the transmission of the first HARQ process (HARQ ID n).

[0251] When the terminal device receives the first SPS PDSCH, it may not send the HARQ-ACK feedback information corresponding to the first SPS PDSCH to the network device. In the time range from the end time when the terminal device receives the first SPS PDSCH to the first duration T_proc,1, the terminal device does not expect to receive another PDSCH scheduled for the first HARQ process transmission. Fig.12 After the time corresponding to the dotted line, the terminal device can receive the DCI scheduled for HARQ ID n, or receive the SPS PDSCH corresponding to HARQ ID n.

[0252] In some embodiments, when the network device does not enable SPS configuration activation corresponding HARQ-ACK feedback through RRC configuration:

[0253] When the first HARQ process is configured with HARQ-ACK feedback enabled, the scheduling constraints of the first HARQ process satisfy:

[0254] If a terminal device receives a first PDSCH for a first HARQ process to be transmitted scheduled by a network device, before the terminal device completes the transmission of the first HARQ-ACK feedback information corresponding to the first PDSCH to the network device, the terminal device does not expect to receive a second PDSCH for a first HARQ process to be transmitted scheduled by the network device again, or the terminal device does not expect to receive a PDCCH for a second PDSCH to be transmitted by the network device again. The transmission timing of the first HARQ-ACK feedback information to be transmitted by the terminal device to the network device is determined based on at least one of a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1, wherein the HARQ feedback timing set may be preset or configured by a network device, and the HARQ feedback timing value K1 is a value in the HARQ feedback timing set.

[0255] When the first HARQ process is configured with HARQ-ACK feedback disabled, the scheduling constraints of the first HARQ process satisfy:

[0256] If a terminal device receives a first PDSCH scheduled by a network device for transmission using a first HARQ process, from the end time of receiving the first PDSCH to the end of the first duration, the terminal device does not expect to receive a first PDCCH scheduled by the network device for transmission of a second PDSCH using the first HARQ process, or the terminal device does not expect to receive a second PDSCH scheduled by the network device for transmission using the first HARQ process. The length of the first duration may be T_proc,1.

[0257] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0258] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0259] In a feasible implementation manner of this embodiment, the first PDSCH is scheduled by the PDCCH, and the second PDSCH is scheduled by the PDCCH.

[0260] In a feasible implementation manner of this embodiment, the first PDSCH is not scheduled by the PDCCH, and the second PDSCH is not scheduled by the PDCCH.

[0261] The embodiment of the present application also provides a communication method for scheduling restriction of the second HARQ process:

[0262] When the second HARQ process is configured with HARQ-ACK feedback enabled, the scheduling constraints of the second HARQ process satisfy:

[0263] If the terminal device receives the third PDSCH scheduled by the network device for the second HARQ process transmission, before the terminal device sends the second HARQ-ACK feedback information corresponding to the third PDSCH to the network device, the terminal device does not expect to receive the fourth PDSCH scheduled by the network device for the second HARQ process transmission again, or the terminal device does not expect to receive the PDCCH (i.e., the above-mentioned second PDCCH) for the network device to schedule the fourth PDSCH for the second HARQ process transmission again. The transmission timing of the terminal device sending the second HARQ-ACK feedback information to the network device is determined according to at least one of the HARQ feedback timing set, the offset value Koffset, and the HARQ feedback timing value K1, wherein the HARQ feedback timing set may be preset or configured by the network device, and the HARQ feedback timing value K1 is a value in the HARQ feedback timing set. For example, the transmission timing of the terminal device sending the second HARQ-ACK feedback information to the network device may be determined according to the following: the HARQ feedback timing set, the offset value Koffset, and the HARQ feedback timing value K1. The HARQ feedback timing value K1 is carried by the PDCCH, and the HARQ feedback timing value K1 indicates a value in the HARQ feedback timing set. The offset value Koffset is configured by the network device.

[0264] When the second HARQ process is configured with HARQ-ACK feedback disabled, the scheduling constraints of the second HARQ process satisfy:

[0265] If the terminal device receives the third PDSCH scheduled by the network device for transmission by the second HARQ process, from the end moment of reception of the third PDSCH to the end of the second duration, the terminal device does not expect to receive the first PDCCH scheduled by the network device for transmission of the fourth PDSCH using the second HARQ process again, or the terminal device does not expect to receive the fourth PDSCH transmitted by the network device using the second HARQ process again. The length of the second duration is T_proc,1. In some embodiments, the second duration may be the same as the first duration, or the second duration may be different from the first duration. The second duration may be determined based on at least one of the following: the processing capability of the terminal device, the subcarrier spacing, and the decoding duration of the first PDSCH.

[0266] In a feasible implementation manner of this embodiment, the third PDSCH is not scheduled by the PDCCH, and / or the fourth PDSCH is not scheduled by the PDCCH.

[0267] The embodiment of the present application also provides a communication method for scheduling restrictions of a HARQ process requiring feedback of HARQ-ACK information:

[0268] For the HARQ process that needs to feedback HARQ-ACK information, the scheduling restrictions are as follows:

[0269] For the first HARQ process that expects the terminal device to provide HARQ-ACK information, if the terminal device receives the first PDSCH scheduled by the network device for transmission of the first HARQ process, before the terminal device completes the transmission of the first HARQ-ACK feedback information corresponding to the first PDSCH to the network device, the terminal device does not expect to receive the second PDSCH scheduled by the network device for transmission of the first HARQ process again, or the terminal device does not expect to receive the PDCCH that the network device schedules the first HARQ process to transmit the second PDSCH again. The transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined based on at least one of the HARQ feedback timing set, the offset value Koffset, and the HARQ feedback timing value K1, wherein the HARQ feedback timing set may be preset or configured by the network device, and the HARQ feedback timing value K1 is a value in the HARQ feedback timing set.

[0270] The embodiment of the present application also provides a communication method for scheduling restrictions of a HARQ process that does not require feedback of HARQ-ACK information:

[0271] For HARQ processes that do not require feedback of HARQ-ACK information, the scheduling restrictions are as follows:

[0272] For the first HARQ process that does not expect the terminal device to provide HARQ-ACK information, if the terminal device receives the first PDSCH scheduled by the network device for transmission by the second HARQ process, from the end time of reception of the first PDSCH to the end of the first time duration, the terminal device does not expect to receive the first PDCCH scheduled by the network device for transmission of the second PDSCH using the second HARQ process again, or the terminal device does not expect to receive the second PDSCH transmitted by the network device using the second HARQ process again.

[0273] The embodiment of the present application also provides a communication method for scheduling restrictions of a first HARQ process corresponding to a first SPS PDSCH:

[0274] Fig.13A schematic diagram of a scheduling restriction of a first HARQ process provided in another embodiment of the present application is shown as follows: Fig.13 As shown, the network device can send the first SPS PDSCH after the SPS configuration is activated, as well as other SPS PDSCHs except the first SPS PDSCH to the terminal device. The first SPS PDSCH can be used to schedule the transmission of the first HARQ process (HARQ ID n).

[0275] In the case where the first HARQ process corresponding to the first SPS PDSCH needs to perform HARQ-ACK feedback, the scheduling restriction of the first HARQ process satisfies the following: if the terminal device receives the first SPS PDSCH scheduled by the network device for transmission of the first HARQ process, before the terminal device completes the transmission of the first HARQ-ACK feedback information corresponding to the first SPS PDSCH to the network device, the terminal device does not expect to receive the second PDSCH scheduled by the network device for transmission of the first HARQ process again. When the terminal device is configured to receive the SPS PDSCH using the first HARQ process before the transmission of the first HARQ-ACK feedback information is completed, the terminal device may not receive the SPS PDSCH. Fig.13 After the dotted line in , the DCI scheduling HARQ ID n can be received, or the SPS PDSCH corresponding to HARQ ID n can be received.

[0276] Through the communication method in the embodiment of the present application, for the first HARQ process used for the first SPS PDSCH transmission, the scheduling restrictions of the first SPS PDSCH and non-first SPS PDSCH can be standardized, thereby avoiding the situation where the terminal device is out of order when receiving SPS PDSCH and / or DCI-scheduled PDSCH.

[0277] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in the various embodiments described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the protection scope of the present application.

[0278] It should also be understood that in various method embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. In addition, in the embodiment of the present application, the terms "downlink", "uplink" and "side" are used to indicate the transmission direction of the signal or data, wherein "downlink" is used to indicate that the transmission direction of the signal or data is the first direction sent from the site to the user equipment of the cell, "uplink" is used to indicate that the transmission direction of the signal or data is the second direction sent from the user equipment of the cell to the site, and "side" is used to indicate that the transmission direction of the signal or data is the third direction sent from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the front and back associated objects are in an "or" relationship.

[0279] Fig.14 A schematic diagram of the structure of a communication device provided in an embodiment of the present application can be applied to a terminal device, such as Fig.14As shown, the communication device 1400 includes: a transceiver unit 1401, used to receive a first physical downlink shared channel PDSCH scheduled by a network device for a first hybrid automatic repeat request HARQ process transmission; the transceiver unit 1401 is also used to not expect to receive a second PDSCH scheduled by the network device for the first HARQ process transmission within a first time range, or not expect to receive a first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process to transmit the second PDSCH.

[0280] In some implementations, the communication device 1400 may further include a determining unit, where the determining unit is configured to determine the first time range.

[0281] In some embodiments, the starting time of the first time range is: the ending time of the reception of the first PDSCH; and / or, the ending time of the first time range is: the ending time of the transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

[0282] In some embodiments, the transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined based on at least one of the following: a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1.

[0283] In some embodiments, the starting time of the first time range is: the ending time of the first PDSCH reception; the duration corresponding to the first time range is the first duration.

[0284] In some embodiments, the first duration is determined based on at least one of the following: a processing capability of the terminal device, a subcarrier spacing, and a decoding duration of the first PDSCH.

[0285] In some embodiments, the first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

[0286] In some embodiments, the terminal device is configured to enable semi-persistent scheduling SPS configuration activation corresponding HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, the terminal device is configured to enable SPS configuration activation corresponding HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback disabled; or, the terminal device is not configured to enable SPS configuration activation corresponding HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, the first PDSCH corresponds to the first HARQ-ACK feedback.

[0287] In some embodiments, the terminal device is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured to disable HARQ-ACK feedback; or, the first PDSCH does not correspond to the first HARQ-ACK feedback.

[0288] In some embodiments, the first PDSCH is the first PDSCH after the semi-persistent scheduling SPS configuration is activated; or, the first PDSCH is scheduled by the PDCCH; or, the first PDSCH is an SPS PDSCH that does not correspond to the PDCCH.

[0289] In some embodiments, the transceiver unit 1401 is further configured to not receive the second PDSCH when the terminal device is scheduled by the network device to receive the second PDSCH using the first HARQ process within the first time range; or,

[0290] The transceiver unit 1401 is further configured to not receive the first PDCCH when the terminal device is scheduled by the network device to receive the first PDCCH within the first time range.

[0291] In some embodiments, the second PDSCH is scheduled by the PDCCH; or, the second PDSCH is an SPS PDSCH that does not correspond to the PDCCH.

[0292] In some embodiments, the transceiver unit 1401 is also used to receive a third PDSCH for scheduling the second HARQ process to be transmitted by the network device when the second HARQ process is configured with HARQ-ACK feedback enabled; the third PDSCH is an SPS PDSCH that does not correspond to a PDCCH; the transceiver unit 1401 is also used to not expect to receive a fourth PDSCH for scheduling the second HARQ process to be transmitted by the network device, or not expect to receive a second PDCCH, from the end time of receiving the third PDSCH to the end time of sending the second HARQ-ACK feedback information corresponding to the third PDSCH to the network device, starting from the end time of transmitting the second HARQ-ACK feedback information to the network device, wherein the second PDCCH is used by the network device to schedule the second HARQ process to transmit the fourth PDSCH.

[0293] In some embodiments, the transceiver unit 1401 is also used for, when the second HARQ process is configured with HARQ-ACK feedback disabled, the terminal device receives the third PDSCH scheduled by the network device for transmission of the second HARQ process; the third PDSCH is an SPS PDSCH that does not correspond to the PDCCH; the transceiver unit 1401 is also used for, from the end moment of reception of the third PDSCH to the end of the second time period, not expecting to receive the fourth PDSCH scheduled by the network device for transmission of the second HARQ process, or not expecting to receive the second PDCCH, wherein the second PDCCH is used by the network device to schedule the second HARQ process to transmit the fourth PDSCH.

[0294] Fig.15 The structural composition diagram of another communication device provided in the embodiment of the present application can be applied to terminal equipment, such as Fig.15 As shown, the communication device 1500 includes: a transceiver unit 1501, used to send a first physical downlink shared channel PDSCH for scheduling the transmission of a first hybrid automatic repeat request HARQ process to a terminal device; the transceiver unit 1501 is also used to not expect to send a second PDSCH for scheduling the transmission of the first HARQ process to the terminal device within a second time range, or not expect to send a first physical downlink control channel PDCCH to the terminal device, wherein the first PDCCH is used to schedule the transmission of the second PDSCH by the first HARQ process.

[0295] In some implementations, the communication device 1500 may further include a determining unit, and the determining unit is configured to determine the second time range.

[0296] In some embodiments, the starting time of the second time range is: the ending time of sending the first PDSCH; and / or, the ending time of the second time range is: the ending time of transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

[0297] In some embodiments, the transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined based on at least one of the following: a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1.

[0298] In some embodiments, the starting time of the second time range is: the ending time of the first PDSCH transmission; and the duration corresponding to the second time range is the first duration.

[0299] In some embodiments, the first duration is determined based on at least one of the following: a processing capability of the terminal device, a subcarrier spacing, and a decoding duration of the first PDSCH.

[0300] In some embodiments, the first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

[0301] In some embodiments, the network device configures the terminal device to enable semi-persistent scheduling SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, the network device configures the terminal device to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback disabled; or, the network device does not configure the terminal device to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, the first PDSCH corresponds to the first HARQ-ACK feedback.

[0302] In some embodiments, the network device does not configure the terminal device to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback disabled; or, the first PDSCH does not correspond to the first HARQ-ACK feedback.

[0303] In some embodiments, the first PDSCH is the first PDSCH after the semi-persistent scheduling SPS configuration is activated; or, the first PDSCH is scheduled by the PDCCH; or, the first PDSCH is an SPS PDSCH that does not correspond to the PDCCH.

[0304] In some embodiments, the transceiver unit 1501 is also used for not receiving the third HARQ-ACK feedback information corresponding to the second PDSCH when the network device sends the second PDSCH scheduling the transmission of the first HARQ process to the terminal device within the second time range; or, the transceiver unit 1501 is also used for not receiving the third HARQ-ACK feedback information corresponding to the second PDSCH when the network device sends the first PDCCH to the terminal device within the second time range.

[0305] In some embodiments, the second PDSCH is scheduled by the PDCCH; or, the second PDSCH is an SPS PDSCH that does not correspond to the PDCCH.

[0306] In some embodiments, the transceiver unit 1501 is further configured to send a third PDSCH for scheduling transmission of the second HARQ process to the terminal device when the second HARQ process is configured with HARQ-ACK feedback enabled; the third PDSCH is an SPS PDSCH that does not correspond to the PDCCH;

[0307] The transceiver unit 1501 is also used for not expecting to send a fourth PDSCH for scheduling the transmission of the second HARQ process to the terminal device, or not expecting to send a second PDCCH to the terminal device, starting from the end time of sending the third PDSCH to the end time of receiving the transmission of the second HARQ-ACK feedback information corresponding to the third PDSCH sent by the terminal device, wherein the second PDCCH is used by the network device to schedule the transmission of the fourth PDSCH by the second HARQ process.

[0308] In some embodiments, the transceiver unit 1501 is further configured to send a third PDSCH for scheduling transmission of the second HARQ process to the terminal device when the second HARQ process is configured with HARQ-ACK feedback disabled; the third PDSCH is an SPS PDSCH that does not correspond to the PDCCH;

[0309] The transceiver unit 1501 is also used for not expecting to send a fourth PDSCH for scheduling the transmission of the second HARQ process to the terminal device, or not expecting to send a second PDCCH to the terminal device, from the end time of sending the third PDSCH to the end of the second time duration, wherein the second PDCCH is used by the network device to schedule the transmission of the fourth PDSCH by the second HARQ process.

[0310] Those skilled in the art should understand that the relevant description of the above-mentioned communication device in the embodiment of the present application can be understood by referring to the relevant description of the communication method in the embodiment of the present application.

[0311] Fig.16 A schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device may be a terminal device or a network device. Fig.16 The communication device 1600 shown includes a processor 1610 and a memory 1620, the memory 1620 is used to store a computer program, and the processor 1610 is used to call and run the computer program stored in the memory 1620 to execute the communication method described in any of the above embodiments. For example, the communication method executed by the terminal device in any of the above embodiments is executed, or the communication method executed by the network device in any of the above embodiments is executed.

[0312] The memory 1620 may be a separate device independent of the processor 1610 , or may be integrated into the processor 1610 .

[0313] In some embodiments, Fig.16 As shown, the communication device 1600 may further include a transceiver 1630, and the processor 1610 may control the transceiver 1630 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 1630 may include a transmitter and a receiver. The transceiver 1630 may further include an antenna, and the number of antennas may be one or more.

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

[0315] In some embodiments, the communication device 1600 may specifically be a terminal device of an embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0316] Fig.17This is a schematic structural diagram of a chip according to an embodiment of the present application. Fig.17 The chip 1700 shown includes a processor 1710, which can call and run a computer program from a memory 1720, so that a terminal device or a network device equipped with the chip 1700 executes the communication method executed by the terminal device or the network device in any of the above embodiments.

[0317] In some embodiments, Fig.17 As shown, the chip 1700 may further include a memory 1720. The processor 1710 may call and run a computer program from the memory 1720 to implement the method in the embodiment of the present application.

[0318] The memory 1720 may be a separate device independent of the processor 1710 , or may be integrated into the processor 1710 .

[0319] In some embodiments, the chip 1700 may further include an input interface 1730. The processor 1710 may control the input interface 1730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0320] In some embodiments, the chip 1700 may further include an output interface 1740. The processor 1710 may control the output interface 840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0321] In some embodiments, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0322] In some embodiments, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0323] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0324] An embodiment of the present application also provides a computer storage medium for storing a computer program, wherein the computer program enables a terminal device to execute the communication method executed by the terminal device in any of the above embodiments, or the computer program enables a network device to execute the communication method executed by the network device in any of the above embodiments.

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

[0326] In some embodiments, the computer storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the terminal device to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0327] An embodiment of the present application also provides a computer program product, including computer program instructions, wherein the computer program instructions enable a terminal device to execute the communication method executed by the terminal device in any of the above embodiments, or the computer program instructions enable a network device to execute the communication method executed by the network device in any of the above embodiments.

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

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

[0330] An embodiment of the present application also provides a computer program, which enables a terminal device to execute the communication method executed by the terminal device in any of the above embodiments, or the computer program enables a network device to execute the communication method executed by the network device in any of the above embodiments.

[0331] In some embodiments, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0332] In some embodiments, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0333] The processor, communication device or chip of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware or software instructions in a processor, communication device or chip. The above-mentioned processor, communication device or chip may include any one or more of the following integrations: general-purpose processor, application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), digital signal processor (Digital Signal Processor, DSP), digital signal processing device (Digital Signal Processing Device, DSPD), programmable logic device (Programmable Logic Device, PLD), field programmable gate array (Field Programmable Gate Array, FPGA), central processing unit (Central Processing Unit, CPU), graphics processing unit (Graphics Processing Unit, GPU), embedded neural network processor (neural-network processing units, NPU), controller, microcontroller, microprocessor, programmable logic device, discrete gate or transistor logic device, discrete hardware component. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

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

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

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

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

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

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

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

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

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

Claims

1. A communication method, the method comprising: The terminal device receives a first physical downlink shared channel PDSCH scheduled by the network device for transmission in a first hybrid automatic repeat request HARQ process; The terminal device does not expect to receive the second PDSCH scheduled by the network device for transmission of the first HARQ process within the first time range, or does not expect to receive the first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process to transmit the second PDSCH.

2. The method according to claim 1, wherein: The starting time of the first time range is: the ending time of the first PDSCH reception; and / or, The end time of the first time range is: the end time of transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

3. The method according to claim 2, wherein: The transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined according to at least one of the following: a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1.

4. The method according to claim 2 or 3, wherein: The first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

5. The method according to claim 2 or 3, wherein: The terminal device is configured to enable semi-persistent scheduling SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, The terminal device is configured to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured to disable HARQ-ACK feedback; or, The terminal device is not configured to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, The first PDSCH corresponds to a first HARQ-ACK feedback.

6. The method according to claim 2, wherein: If the terminal device is configured to enable at least one of the HARQ-ACK feedback corresponding to the SPS configuration activation and the HARQ-ACK feedback enablement corresponding to the first HARQ process, the terminal device determines that it is necessary to send the first HARQ-ACK feedback information to the network device, and the starting time of the first time range is: the end time of the first PDSCH reception, and the end time of the first time range is: the end time of the transmission of the first HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device to the network device.

7. The method according to any one of claims 1, 2, 3 and 6, wherein: The first PDSCH is the first PDSCH after the semi-persistent scheduling SPS configuration is activated; or, The first PDSCH is scheduled by the PDCCH; or, The first PDSCH is an SPS PDSCH that does not correspond to the PDCCH.

8. A communication method, the method comprising: The network device sends a first physical downlink shared channel PDSCH for scheduling transmission of a first hybrid automatic repeat request HARQ process to the terminal device; The network device does not expect to send a second PDSCH for scheduling the transmission of the first HARQ process to the terminal device within a second time range, or does not expect to send a first physical downlink control channel PDCCH to the terminal device, wherein the first PDCCH is used by the network device to schedule the transmission of the second PDSCH by the first HARQ process.

9. The method according to claim 8, wherein: The starting time of the second time range is: the ending time of the first PDSCH transmission; and / or, The end time of the second time range is: the end time of transmission of the first hybrid automatic repeat request-acknowledgement HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

10. The method according to claim 9, wherein: The transmission timing of the terminal device sending the first HARQ-ACK feedback information to the network device is determined according to at least one of the following: a HARQ feedback timing set, an offset value Koffset, and a HARQ feedback timing value K1.

11. The method according to claim 9 or 10, wherein: The first HARQ process is configured with HARQ-ACK feedback disabled, or the first HARQ process is configured with HARQ-ACK feedback enabled.

12. The method according to claim 9 or 10, wherein: The network device configures the terminal device to enable semi-persistent scheduling (SPS) configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, The network device configures the terminal device to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback disabled; or, The network device does not configure the terminal device to enable SPS configuration activation corresponding to HARQ-ACK feedback, and the first HARQ process is configured with HARQ-ACK feedback enabled; or, The first PDSCH corresponds to a first HARQ-ACK feedback.

13. The method according to claim 9, wherein: If the network device configures the terminal device to enable at least one of SPS configuration activation corresponding to HARQ-ACK feedback and enabling HARQ-ACK feedback corresponding to the first HARQ process, the starting time of the second time range is: the end time of sending the first PDSCH, and the end time of the second time range is: the end time of transmission of the first HARQ-ACK feedback information corresponding to the first PDSCH sent by the terminal device received by the network device.

14. The method according to any one of claims 8, 9, 10 and 13, wherein: The first PDSCH is the first PDSCH after the semi-persistent scheduling SPS configuration is activated; or, The first PDSCH is scheduled by the PDCCH; or, The first PDSCH is an SPS PDSCH that does not correspond to the PDCCH.

15. A communication device, comprising: A transceiver unit, configured to receive a first physical downlink shared channel PDSCH for transmission of a first hybrid automatic repeat request HARQ process scheduled by a network device; The transceiver unit is also used for not expecting to receive a second PDSCH scheduled by the network device for transmission of the first HARQ process within a first time range, or not expecting to receive a first physical downlink control channel PDCCH, wherein the first PDCCH is used by the network device to schedule the first HARQ process to transmit a second PDSCH.

16. A communication device, comprising: A transceiver unit, configured to send a first physical downlink shared channel PDSCH for scheduling transmission of a first hybrid automatic repeat request HARQ process to a terminal device; The transceiver unit is also used for not expecting to send a second PDSCH for scheduling the transmission of the first HARQ process to the terminal device within a second time range, or not expecting to send a first physical downlink control channel PDCCH to the terminal device, wherein the first PDCCH is used to schedule the transmission of the second PDSCH by the first HARQ process.

17. A terminal device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and execute the communication method according to any one of claims 1 to 7.

18. A network device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the communication method as claimed in any one of claims 8 to 14.

19. A chip, comprising: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip executes a communication method as described in any one of claims 1 to 7, or a device equipped with the chip executes a communication method as described in any one of claims 8 to 14.

20. A computer storage medium for storing a computer program, wherein the computer program enables a terminal device to execute the communication method according to any one of claims 1 to 7, or the computer program enables a network device to execute the communication method according to any one of claims 8 to 14.

Citation Information

Patent Citations

  • Wireless communication method, network equipment, terminal equipment and readable storage medium

    CN110149174A

  • Wireless communication method, terminal device, and network device

    CN113412595A

  • Data transmission method, terminal device, and network device

    CN113615272A

  • Data transmission method, terminal device, and network device

    WO2021073021A1