Communication method and related products

Abstract

An embodiment of this application provides a communication method and related products. Among them, the method includes: A network device sends an SPS release request to a terminal through at least two PD CCHs on the same time slot, and the SPS release request is used to indicate the release of SPS PD SCH transmission; The transmission end time unit of the PD CCH that earliest transmits the SPS release request among the at least two PD CCHs is before the transmission end time unit of the SPS PD SCH transmission; The terminal receives an SPS release request from the network device through at least two PD CCHs on the same time slot. By adopting the embodiment of this application, when multi-TRP transmission enhancement is performed on the PD CCH for transmitting SPS release, the restriction of the network device on downlink resource scheduling can be relaxed, the scheduling flexibility of the network device can be improved, and the reliability of PD CCH transmission can be ensured.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a communication method and related products. Background Art

[0002] In an Ultra-reliable Low Latency Communications (URLLC) system, when the transmission of a Physical Downlink Control Channel (PDCCH) released by Semi-Persistent Scheduling (SPS) supports transmission enhancement for Multiple Tx / Rx Point (Multi-TRP), the corresponding relationship between the transmission time of the PDCCH and the transmission time of the corresponding Semi-Persistent Scheduling Physical Downlink Shared Channel (SPS PDSCH) has not been discussed. If the method based on 3GPP Rel-16 is followed, the scheduling flexibility is very low. The base station may not be able to find the downlink resources corresponding to multiple PDCCHs within one time slot, and the reliability of PDCCH transmission cannot be guaranteed either. Summary of the Invention

[0003] Embodiments of this application disclose a communication method and related products. When the transmission of a PDCCH released by SPS performs multi-TRP transmission enhancement, it can relax the restrictions on downlink resource scheduling by the network device, improve the scheduling flexibility of the network device, and ensure the reliability of PDCCH transmission.

[0004] In a first aspect, an embodiment of this application discloses a communication method applied to a network device. The method includes: sending a semi-persistent scheduling (SPS) release request to a terminal through at least two physical downlink control channels (PDCCHs) on the same time slot, where the SPS release request is used to indicate the release of the transmission of the semi-persistent scheduling physical downlink shared channel (SPS PDSCH); the transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

[0005] It can be seen that in this embodiment, the SPS release request is sent to the terminal through at least two PDCCHs in the same time slot, and the SPS release request is used to indicate the release of SPS PDSCH transmission; since when the PDCCH for transmitting SPS release performs multi-TRP transmission enhancement, the network device sends the SPS release request to the terminal through at least two PDCCHs in the same time slot, thus ensuring the reliability of PDCCH transmission; and only the transmission end time unit of the earliest PDCCH transmitting the SPS release request among the at least two PDCCHs needs to be before the transmission end time unit of the SPS PDSCH transmission, thereby relaxing the restriction on the downlink resource scheduling of the network device and improving the scheduling flexibility of the network device.

[0006] In an exemplary implementation manner, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same physical uplink control channel PUCCH, and the method further includes: receiving the hybrid automatic repeat request acknowledgement HARQ-ACK information of the SPS release request fed back from the terminal.

[0007] It can be seen that in this example, if the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same PUCCH, the network device only receives the HARQ-ACK information of the SPS release request fed back from the terminal, that is, the terminal only feeds back the HARQ-ACK information of the SPS release request, thereby ensuring that the terminal can successfully receive the SPS release request.

[0008] In an exemplary implementation manner, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs, and the method further includes: receiving the HARQ-ACK information of the SPS release request fed back from the terminal.

[0009] It can be seen that in this example, if the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs, the network device can receive the HARQ-ACK information of the SPS release request fed back from the terminal through the PUCCH for feeding back the SPS release request, that is, the terminal can feed back the HARQ-ACK information of the SPS release request through the PUCCH for feeding back the SPS release request, thereby ensuring that the terminal can successfully receive the SPS release request.

[0010] In an exemplary embodiment, the method further includes: receiving HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; receiving non-acknowledgment NACK information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request.

[0011] It can be seen that in this example, since different PUCCHs are used for the feedback of the SPS release request and the feedback of the SPS PDSCH transmission, the terminal can feed back the SPS release request through the PUCCH for feedback of the SPS release request, and can also feed back the SPS PDSCH transmission through the PUCCH for feedback of the SPS PDSCH transmission; thus, the network device can receive the HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; and the network device can receive the non-acknowledgment NACK information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request; which is beneficial to ensuring the reliability of the SPS PDSCH transmission while ensuring that the terminal can successfully receive the SPS release request.

[0012] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH, where a transmission end time unit of the first PDCCH is before a transmission end time unit of the SPS PDSCH, and a transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0013] It can be seen that in this example, when multi-TRP transmission enhancement is performed on the PDCCH for transmitting the SPS release, the network device sends the SPS release request to the terminal through the first PDCCH and the second PDCCH on the same time slot. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH, thereby relaxing the restriction on the downlink resource scheduling of the network device and improving the scheduling flexibility of the network device.

[0014] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH. The transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0015] It can be seen that in this example, when enhancing multi-TRP transmission for the PDCCH of SPS release, on the same time slot, the network device sends an SPS release request to the terminal through the first PDCCH and the second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH. The transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH. Thus, the restriction on the downlink resource scheduling of the network device is relaxed, and the scheduling flexibility of the network device is improved.

[0016] The second aspect of the embodiments of the present application discloses a communication method applied to a terminal. The method includes: receiving an SPS release request from a network device through at least two PDCCHs on the same time slot, where the SPS release request is used to indicate the release of SPS PDSCH transmission; the transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

[0017] In an exemplary embodiment, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same PUCCH. The method further includes: feeding back HARQ-ACK information of the SPS release request to the network device.

[0018] In an exemplary embodiment, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The method further includes: feeding back HARQ-ACK information of the SPS release request to the network device.

[0019] In an exemplary embodiment, the method further includes: before successfully receiving the SPS release request, feeding back HARQ-ACK information of the SPS PDSCH transmission to the network device; after successfully receiving the SPS release request, feeding back NACK information of the SPS PDSCH transmission to the network device.

[0020] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. A transmission end time unit of the first PDCCH is before a transmission end time unit of the SPS PDSCH, and a transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0021] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. A transmission end time unit of the first PDCCH is before a transmission end time unit of the SPS PDSCH, a transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and a transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0022] A third aspect of the embodiments of the present application discloses a communication device applied to a network device. The device includes: a sending unit, configured to send a semi-persistent scheduling (SPS) release request to a terminal through at least two physical downlink control channels (PDCCHs) on the same time slot, where the SPS release request is used to indicate releasing the transmission of a physical downlink shared channel (SPS PDSCH) scheduled semi-persistently; and a transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before a transmission end time unit of the SPS PDSCH transmission.

[0023] In an exemplary embodiment, feedback of the SPS release request and feedback of the SPS PDSCH transmission use the same physical uplink control channel (PUCCH). The device further includes: a receiving unit, configured to receive hybrid automatic repeat request acknowledgement (HARQ-ACK) information of the SPS release request fed back from the terminal.

[0024] In an exemplary embodiment, feedback of the SPS release request and feedback of the SPS PDSCH transmission use different PUCCHs. The device further includes: a receiving unit, configured to receive HARQ-ACK information of the SPS release request fed back from the terminal.

[0025] In an exemplary embodiment, the receiving unit is further configured to: receive the HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; receive the negative acknowledgment NACK information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request.

[0026] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0027] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, the transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0028] A fourth aspect of the embodiments of the present application discloses a communication device applied to a terminal. The device includes: a receiving unit, configured to receive an SPS release request from a network device through at least two PDCCHs on the same time slot, where the SPS release request is used to indicate the release of the SPS PDSCH transmission; the transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

[0029] In an exemplary embodiment, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same PUCCH. The device further includes: a sending unit, configured to feed back the HARQ-ACK information of the SPS release request to the network device.

[0030] In an exemplary embodiment, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The device further includes: a sending unit, configured to feed back the HARQ-ACK information of the SPS release request to the network device.

[0031] In an exemplary embodiment, the sending unit is further configured to: before successfully receiving the SPS release request, feedback the HARQ-ACK information of the SPS PDSCH transmission to the network device; after successfully receiving the SPS release request, feedback the NACK information of the SPS PDSCH transmission to the network device.

[0032] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0033] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, the transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0034] A fifth aspect of the embodiments of the present application discloses a network device, including a processor, a memory, a communication interface, and one or more programs. The one or more programs are stored in the memory and are configured to be executed by the processor. The programs include instructions for performing the steps in the method according to any one of the first aspects above.

[0035] A sixth aspect of the embodiments of the present application discloses a terminal, including a processor, a memory, a communication interface, and one or more programs. The one or more programs are stored in the memory and are configured to be executed by the processor. The programs include instructions for performing the steps in the method according to any one of the second aspects above.

[0036] A seventh aspect of the embodiments of the present application discloses a chip, characterized by including: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of the first aspect or the second aspect above.

[0037] An eighth aspect of the embodiments of the present application discloses a computer-readable storage medium, which stores a computer program for electronic data exchange. When the computer program runs on a computer, the computer is enabled to execute the method according to any one of the first aspect or the second aspect above.

[0038] The ninth aspect of the embodiments of the present application discloses a computer program product, including a computer program, which when running on a computer causes the computer to execute the method described in any one of the above first aspect or second aspect. Description of the Drawings

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0040] Figure 1 It is a timing relationship diagram of PDCCH and SPS PDSCH for SPS release within the same time slot provided by the embodiments of the present application;

[0041] Figure 2 It is a timing relationship diagram of two PDCCHs and SPS PDSCH for SPS release within the same time slot provided by the embodiments of the present application;

[0042] Figure 3 It is a schematic diagram of a communication system provided by the embodiments of the present application;

[0043] Figure 4 It is a schematic flowchart of a communication method provided by the embodiments of the present application;

[0044] Figure 5 It is a timing relationship diagram of two PDCCHs and SPS PDSCH corresponding to time division multiplexing for SPS release within the same time slot provided by the embodiments of the present application;

[0045] Figure 6 It is a timing relationship diagram of two PDCCHs and SPS PDSCH corresponding to frequency division multiplexing for SPS release within the same time slot provided by the embodiments of the present application;

[0046] Figure 7 It is another timing relationship diagram of two PDCCHs and SPS PDSCH corresponding to time division multiplexing for SPS release within the same time slot provided by the embodiments of the present application;

[0047] Figure 8 It is another timing relationship diagram of two PDCCHs and SPS PDSCH corresponding to frequency division multiplexing for SPS release within the same time slot provided by the embodiments of the present application;

[0048] Figure 9 It is a schematic structural diagram of a communication device provided by the embodiments of the present application;

[0049] Figure 10 It is a schematic structural diagram of another communication device provided by an embodiment of the present application;

[0050] Figure 11 It is a schematic structural diagram of a network device provided by an embodiment of the present application;

[0051] Figure 12 It is a schematic structural diagram of a terminal provided by an embodiment of the present application. Detailed implementation manners

[0052] The embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

[0053] To facilitate those skilled in the art to understand the present application, some terms in the present application will be explained herein first, and relevant technical knowledge related to the embodiments of the present application will be introduced.

[0054] Multiple Tx / Rx Point (Multi-TRP), a scenario based on multiple transmission and reception points serving a certain user, and each transmission and reception point includes a set of transmission and reception antennas.

[0055] Transmission Reception Point (TRP).

[0056] Enhanced Mobile Broadband (EMBB).

[0057] Physical Downlink Control Channel (PDCCH), used to carry downlink control messages.

[0058] Downlink Control Information (DCI), which consists of multiple parameter fields and is sent to the user through the PDCCH.

[0059] User Equipment (UE).

[0060] Physical Downlink Shared Channel (PDSCH), used to carry downlink data messages.

[0061] Physical Uplink Control Channel (PUCCH), used to carry uplink control messages.

[0062] Semi-Persistent Scheduling (SPS) means that the scheduling of resources is pre-configured and periodic.

[0063] SPS release, which is for semi-persistent scheduling release and can also be called SPS PDCCH release.

[0064] Frequency Division Multiplexing (FDM) is to divide the total bandwidth used for the transmission channel into several sub-bands (or sub-channels), and each sub-channel transmits one signal.

[0065] Time Division Multiplexing (TDM) uses different time periods of the same physical connection to transmit different signals, and can also achieve the purpose of multiplexing; time division multiplexing uses time as the parameter for signal segmentation, so it is necessary to ensure that the signals of each path do not overlap on the time axis.

[0066] In the downlink transmission of NR, the base station can perform downlink data transmission by scheduling SPS PDSCH. SPS PDSCH is configured with a transmission period and a configuration index by RRC, and performs periodic transmission after being activated by DCI. In the 3GPP Rel-16 version, up to 16 groups of SPS PDSCH can be configured simultaneously.

[0067] During the transmission of SPS PDSCH, the release of the SPS PDSCH configuration can be indicated by the SPS PDCCH release. In 3GPP Rel-16, one SPS release DCI can release one or more groups of SPS PDSCH simultaneously.

[0068] In the RAN1#101-e meeting, the agreement reached on the UE behavior when SPS release and SPS PDSCH reception are in the same time slot is as follows:

[0069] As Figure 1 shown, in the same time slot (slot), the UE's reception of the SPS release needs to be before the end of the SPS PDSCH reception corresponding to the same SPS configuration index, and when the SPS release and SPS PDSCH use the same PUCCH resource for feedback; the UE only reports 1-bit HARQ-ACK for the SPS release and does not expect to receive the SPS PDSCH. And it does not support the UE's reception of the SPS release in the same slot after the end of the SPS PDSCH reception corresponding to the same SPS configuration index. Among them, in Figure 1Among them, SPS reception represents SPS PDSCH transmission, and SPS release represents the transmission of SPS release.

[0070] Whether it supports feedback of SPS release and SPS PDSCH with the same configuration index through different PUCCH resources is still pending. According to the current standardization progress, it is more likely to support this feature.

[0071] In the standardization process of New Radio Access Technology (NR), a similar multi-point cooperative transmission technology is called multi-TRP transmission. In the 3GPP Rel-15 version, multi-TRP transmission only enhances the PDSCH transmission of the URLLC and EMBB systems, and does not enhance the PDCCH transmission of the URLLC and EMBB systems; the 3GPP Rel-17 version has clearly stated that it will perform multi-TRP enhancement on the PDCCH transmission of URLLC.

[0072] For PDCCH enhancement, the solutions that the protocol may currently support include time division multiplexing (TDM), frequency division multiplexing (FDM), and space division multiplexing (SDM), etc. And for the time division multiplexed PDCCH transmission, PDCCH transmission based on repetition and multi-chance PDCCH transmission can be adopted.

[0073] When performing multi-TRP transmission enhancement on the PDCCH for transmitting SPS release, how to design the timing relationship between SPS PDSCH and the PDCCH for transmitting SPS release is a problem, and it has not been discussed in the current protocol.

[0074] An intuitive solution is that the end of receiving the latest PDCCH for transmitting SPS release needs to be earlier than the end of receiving SPS PDSCH. For example, Figure 2 As shown, an SPS release has 2 TDM PDCCH transmissions in a slot, and the reception of the last PDCCH needs to be earlier than the termination symbol of SPS PDSCH. This method has better compatibility with the Rel-16 version, but it is more difficult to implement in an actual system. For example, when there are multiple service types in the URLLC system, the base station needs to configure multiple SPS PDSCH and dynamically scheduled PDSCH, and the period of SPS PDSCH will be relatively small. At this time, the available downlink resources will be relatively limited. Therefore, it is very difficult for the base station to find 2 or more PDCCH resources that meet the time requirements to transmit SPS release requests. Among them, in Figure 2In this application and other attached drawings, SPS represents SPS PDSCH transmission, Rel.1 represents the first PDCCH resource transmission of the SPS release request, and Rel.2 represents the second PDCCH resource transmission of the SPS release request.

[0075] The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, future 5th generation (5G) system or New Radio (NR), etc.

[0076] The terminal in the embodiments of this application may refer to a user equipment, an access terminal, a user unit, a user station, a mobile station, a mobile terminal, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The terminal may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, a relay device, a vehicle-mounted device, a wearable device, a terminal in the future 5G network or a terminal in the future evolved Public Land Mobile Network (PLMN), etc. The embodiments of this application are not limited thereto.

[0077] The network device in the embodiments of the present application may be a device for communicating with a terminal. The network device may be a base transceiver station (BTS) in a global system for mobile communications (GSM) system or a code division multiple access (CDMA) system, or a NodeB (NB) in a wideband code division multiple access (WCDMA) system, or an evolved NodeB (eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (CRAN) scenario, or the network device may be a relay device, an access point, a vehicle-mounted device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network, one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or, alternatively, a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc. The embodiments of the present application do not limit this.

[0078] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and the functions of the packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, thus, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU + AAU. It can be understood that the network device may be a device including one or more of the CU node, the DU node, and the AAU node. In addition, the CU may be classified as a network device in the radio access network (RAN), or the CU may be classified as a network device in the core network (CN), and this application does not make a limitation on this.

[0079] In the embodiments of the present application, a terminal or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also known as main memory). The operating system can be any one or more computer operating systems that implement service processing through processes. For example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system, etc. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided by the embodiments of the present application. As long as it can communicate according to the method provided by the embodiments of the present application by running a program that records the code of the method provided by the embodiments of the present application. For example, the execution subject of the method provided by the embodiments of the present application can be a terminal, or a functional module in the terminal that can call and execute the program.

[0080] The technical solutions provided by the present application will be introduced in detail below in conjunction with specific embodiments.

[0081] Please refer to Figure 3 , Figure 3 which is a schematic diagram of a communication system provided by the embodiments of the present application. Figure 3 The communication system 300 in [[ ]] may include at least one terminal 310 (such as terminal 1, terminal 2, terminal 3, etc.) and a network device 320. The network device 320 is used to provide communication services for the terminal 310 and access the core network. The terminal 310 can access the network by searching for synchronization signals, broadcast signals, etc. sent by the network device 320, so as to communicate with the network. The terminal 310 can receive configuration information or system information, etc. from the network device 320. It should be understood that the network device 320 included in this communication system can be one or more. One network device 320 can send data or control signaling to one or more terminals 310. Multiple network devices 320 can also send data or control signaling to one or more terminals 310 simultaneously.

[0082] Please refer to Figure 4 , Figure 4 which is a communication method provided by the embodiments of the present application. Among them, this method can be applied to Figure 3 the communication system shown in [[ ]], and this method includes but is not limited to the following steps:

[0083] Step 401: The network device sends a semi-persistent scheduling (SPS) release request to the terminal via at least two physical downlink control channels (PDCCHs) in the same time slot, where the SPS release request is used to indicate the release of the physical downlink shared channel (SPS PDSCH) transmission under semi-persistent scheduling; the transmission end time unit of the earliest PDCCH that transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

[0084] Among them, releasing the physical layer downlink shared channel (SPS PDSCH) transmission under semi-persistent scheduling means releasing the information carried on the physical layer downlink shared channel (SPS PDSCH) under semi-persistent scheduling.

[0085] Among them, the time unit can be a symbol. For example, the transmission end time unit can be a transmission termination symbol or a transmission end symbol, or the transmission start time unit can be a transmission start symbol or a transmission begin symbol.

[0086] Step 402: The terminal receives the SPS release request from the network device via at least two PDCCHs in the same time slot.

[0087] It can be seen that in this embodiment, the SPS release request is sent to the terminal via at least two PDCCHs in the same time slot, and this SPS release request is used to indicate the release of the SPS PDSCH transmission; since when the PDCCH for transmitting the SPS release undergoes multi-TRP transmission enhancement, the network device sends the SPS release request to the terminal via at least two PDCCHs in the same time slot, thus ensuring the reliability of the PDCCH transmission; and only the transmission end time unit of the earliest PDCCH that transmits the SPS release request among the at least two PDCCHs needs to be before the transmission end time unit of the SPS PDSCH transmission, thereby relaxing the restrictions on the network device's downlink resource scheduling and improving the scheduling flexibility of the network device.

[0088] In an exemplary implementation, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same physical uplink control channel (PUCCH), and the method further includes: receiving the hybrid automatic repeat request acknowledgment (HARQ-ACK) information of the SPS release request fed back from the terminal.

[0089] It can be seen that in this example, if the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same PUCCH, then the network device only receives the HARQ-ACK information of the SPS release request fed back from the terminal, that is, the terminal only feeds back the HARQ-ACK information of the SPS release request, thereby ensuring that the terminal can successfully receive the SPS release request.

[0090] In an exemplary embodiment, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs, and the method further includes: receiving the HARQ-ACK information of the SPS release request fed back from the terminal.

[0091] It can be seen that in this example, if the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs, the network device can receive the HARQ-ACK information of the SPS release request fed back from the terminal through the PUCCH for feedback of the SPS release request, that is, the terminal can feedback the HARQ-ACK information of the SPS release request through the PUCCH for feedback of the SPS release request, so as to ensure that the terminal can successfully receive the SPS release request.

[0092] In an exemplary embodiment, the method further includes: receiving the HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; receiving the negative acknowledgment NACK information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request.

[0093] It can be seen that in this example, since the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs, the terminal can feedback the SPS release request through the PUCCH for feedback of the SPS release request, and can also feedback the SPS PDSCH transmission through the PUCCH for feedback of the SPS PDSCH transmission; thus, the network device can receive the HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; and the network device can receive the negative acknowledgment NACK information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request; while ensuring that the terminal can successfully receive the SPS release request, it is also beneficial to ensure the reliability of the SPS PDSCH transmission.

[0094] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. A transmission end time unit of the first PDCCH is before a transmission end time unit of the SPS PDSCH, and a transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0095] It can be seen that in this example, when enhancing multi-TRP transmission of the PDCCH for SPS release, on the same time slot, the network device sends an SPS release request to the terminal through the first PDCCH and the second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH, thereby relaxing the restrictions on the network device's downlink resource scheduling and improving the scheduling flexibility of the network device.

[0096] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. A transmission end time unit of the first PDCCH is before a transmission end time unit of the SPS PDSCH, a transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and a transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0097] It can be seen that in this example, when enhancing multi-TRP transmission of the PDCCH for SPS release, on the same time slot, the network device sends an SPS release request to the terminal through the first PDCCH and the second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, the transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH, thereby relaxing the restrictions on the network device's downlink resource scheduling and improving the scheduling flexibility of the network device.

[0098] The technical solution provided by the present application will be introduced in detail below with specific examples.

[0099] Example 1. Please refer to Figure 5 , Figure 5 which is a timing relationship diagram of two PDCCHs corresponding to time division multiplexing for SPS release and SPS PDSCH within the same time slot provided by an embodiment of the present application. As Figure 5As shown in the figure, the PDCCH transmission configuration for SPS release based on TDM within one time slot, where the feedback for SPS release and SPS PDSCH uses the same PUCCH resource. Only the reception of the first PDCCH needs to be earlier than the termination symbol of the corresponding SPS PDSCH, and there is no restriction on the transmission timing of the subsequent PDCCHs. The behavior of the corresponding UE is that the UE only feeds back HARQ-ACK for the PDCCH transmitting the SPS release and does not feed back for the SPS PDSCH.

[0100] Specifically, the base station configures the transmission termination symbol of the SPS PDSCH transmission as symbol 6 within one time slot; the base station configures the transmission symbols occupied by the 2 PDCCHs used for transmitting the SPS release as symbols 2-5 and 8-11 respectively, that is, the transmission of PDCCH1 is before the SPS PDSCH transmission, and the transmission of PDCCH2 is after the SPS PDSCH transmission, and these 2 PDCCHs are transmitted by different TRPs respectively. At this time, the UE only receives and decodes the PDCCH for SPS release and reports HARQ-ACK, and the UE does not report HARQ-ACK for the SPS PDSCH.

[0101] Example 2, please refer to Figure 6 , Figure 6 is a timing relationship diagram of 2 PDCCHs for SPS release corresponding to frequency division multiplexing and SPS PDSCH within the same time slot provided by an embodiment of the present application. As Figure 6 shown in the figure, the PDCCH transmission configuration for SPS release based on FDM within one time slot, where the feedback for SPS release and SPS PDSCH uses the same PUCCH resource. Only the reception of the PDCCH with the earliest termination symbol needs to be earlier than the termination symbol of the SPS PDSCH, and there is no restriction on the transmission timing of the remaining PDCCHs. The behavior of the corresponding UE is that the UE only feeds back HARQ-ACK for the PDCCH transmitting the SPS release and does not feed back for the SPS PDSCH. Among them, Missdetection means missed detection or undetected.

[0102] Specifically, the base station configures the transmission termination symbol of the SPS PDSCH transmission as symbol 6 within one time slot; the base station configures the 2 PDCCHs used for transmitting the SPS release to occupy different frequency bands, and the occupied transmission symbols are symbols 2-5 and 4-7 respectively, that is, the transmission of PDCCH1 is before the SPS PDSCH transmission, and the transmission termination symbol of PDCCH2 is after the transmission termination symbol of the SPS PDSCH, and these 2 PDCCHs are transmitted by different TRPs respectively. At this time, the UE only receives and decodes the PDCCH for transmitting the SPS release and reports HARQ-ACK, and the UE does not report HARQ-ACK for the SPS PDSCH.

[0103] Example 3, please refer to Figure 7 , Figure 7 which is a timing relationship diagram of another two PDCCHs corresponding to time division multiplexing and SPS PDSCH in the same time slot provided by the embodiments of the present application. As Figure 7 shown, in a time slot, the PDCCH transmission configuration for SPS release based on TDM, and different PUCCH resources are used for the feedback of SPS release and SPS PDSCH. Only the reception of the first PDCCH needs to be earlier than the transmission termination symbol of SPS PDSCH transmission, and there is no restriction on the transmission timing of the subsequent PDCCHs. The behavior of the corresponding UE is: before the successful reception of the PDCCH for SPS release, the UE can receive SPS PDSCH and give feedback; after the successful reception of the PDCCH for SPS release, the UE does not receive SPS PDSCH and gives NACK feedback.

[0104] Specifically, the base station configures the transmission termination symbol of SPS PDSCH transmission as symbol 6 in a time slot; the transmission symbols occupied by the two PDCCHs used for transmitting SPS release configured by the base station are symbols 2 - 5 and 8 - 11 respectively, that is, the transmission of PDCCH1 is before the transmission of SPS PDSCH, and the transmission of PDCCH2 is after the transmission of SPS PDSCH, and these two PDCCHs are transmitted by different TRPs respectively, and SPS PDSCH and SPS release feedback are sent to different PUCCH resources. At this time, before the successful reception of the PDCCH for SPS release, the UE can receive SPS PDSCH and give feedback. After the successful reception of the PDCCH for SPS release, the UE does not receive SPS PDSCH and gives NACK feedback.

[0105] Example 4, please refer to Figure 8 , Figure 8 which is a timing relationship diagram of another two PDCCHs corresponding to frequency division multiplexing and SPS PDSCH in the same time slot provided by the embodiments of the present application. As Figure 8 shown, in a time slot, the PDCCH transmission configuration for SPS release based on FDM, and different PUCCH resources are used for the feedback of SPS release and SPS PDSCH. Only the reception of the PDCCH with the earliest termination symbol needs to be earlier than the transmission termination symbol of SPS PDSCH transmission, and there is no restriction on the transmission timing of the subsequent PDCCHs. The behavior of the corresponding UE is: before the successful reception of the PDCCH for SPS release, the UE can receive SPS PDSCH and give feedback; after the successful reception of the PDCCH for SPS release, the UE does not receive SPS PDSCH and gives NACK feedback.

[0106] Specifically, the transmission termination symbol for the SPS PDSCH configured by the base station is symbol 6 within a time slot; the transmission symbols occupied by the 2 PDCCHs configured for transmitting the SPS release are symbol 2 - 5 and 4 - 7 respectively, that is, the transmission of PDCCH1 is before the SPS PDSCH, the transmission termination symbol of PDCCH2 is after the transmission termination symbol of the SPS PDSCH, and these 2 PDCCHs are transmitted by different TRPs respectively, and the SPS PDSCH and the SPS release are fed back to different PUCCH resources. At this time, before the successful reception of the PDCCH for transmitting the SPS release, the UE can receive the SPS PDSCH and give feedback; after the successful reception of the PDCCH for transmitting the SPS release, the UE does not receive the SPS PDSCH and gives a NACK feedback.

[0107] Please refer to Figure 9 , Figure 9 FIG. Figure 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device 900 is applied to a network device. The communication device 900 may include a sending unit 901. The detailed descriptions of each unit are as follows:

[0108] The sending unit 901 is configured to send a semi - persistent scheduling (SPS) release request to a terminal through at least two physical downlink control channels (PDCCHs) on the same time slot, where the SPS release request is used to indicate the release of the transmission of the physical downlink shared channel (SPS PDSCH) scheduled semi - persistently; the transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

[0109] In an exemplary implementation manner, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same physical uplink control channel (PUCCH). The device further includes: a receiving unit 902, configured to receive the hybrid automatic repeat request acknowledgment (HARQ - ACK) information of the SPS release request fed back from the terminal.

[0110] In an exemplary implementation manner, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The device further includes: a receiving unit 902, configured to receive the HARQ - ACK information of the SPS release request fed back from the terminal.

[0111] In an exemplary embodiment, the receiving unit 902 is further configured to: receive the HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; receive the negative acknowledgment NACK information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request.

[0112] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0113] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, the transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0114] It should be noted that the implementation of each unit can also correspond to the corresponding description in the method embodiment shown in Figure 4 Of course, the communication device 900 provided in the embodiments of the present application includes but is not limited to the above unit modules. For example, the communication device 900 may further include a storage unit 903. The storage unit 903 may be used to store the program code and data of the communication device 900.

[0115] In Figure 9 In the described communication device 900, an SPS release request is sent to the terminal through at least two PDCCHs in the same time slot, and the SPS release request is used to indicate the release of the SPS PDSCH transmission; since when the PDCCH for transmitting the SPS release performs multi-TRP transmission enhancement, the network device sends the SPS release request to the terminal through at least two PDCCHs in the same time slot, thereby ensuring the reliability of the PDCCH transmission; and only the transmission end time unit of the earliest PDCCH that transmits the SPS release request among the at least two PDCCHs needs to be before the transmission end time unit of the SPS PDSCH transmission, thereby relaxing the restriction on the downlink resource scheduling of the network device and improving the scheduling flexibility of the network device.

[0116] Please refer to Figure 10 , Figure 10 which is a schematic structural diagram of another communication device provided by an embodiment of the present application. The communication device 1000 is applied to a terminal. The communication device 1000 may include a receiving unit 1001. The detailed descriptions of each unit are as follows:

[0117] The receiving unit 1001 is configured to receive an SPS release request from a network device through at least two PDCCHs in the same time slot, where the SPS release request is used to indicate the release of SPS PDSCH transmission; the transmission end time unit of the earliest-transmitted PDCCH among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

[0118] In an exemplary embodiment, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same PUCCH. The device further includes: a sending unit 1002, configured to feedback HARQ-ACK information of the SPS release request to the network device.

[0119] In an exemplary embodiment, the feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The device further includes: a sending unit 1002, configured to feedback HARQ-ACK information of the SPS release request to the network device.

[0120] In an exemplary embodiment, the sending unit 1002 is further configured to: before successfully receiving the SPS release request, feedback HARQ-ACK information of the SPS PDSCH transmission to the network device; after successfully receiving the SPS release request, feedback NACK information of the SPS PDSCH transmission to the network device.

[0121] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0122] In an exemplary embodiment, the at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH. The transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

[0123] It should be noted that the implementation of each unit can also correspond to the corresponding description in the Figure 4 method embodiment shown. Of course, the communication device 1000 provided in the embodiments of the present application includes but is not limited to the above unit modules. For example, the communication device 1000 may further include a storage unit 1003. The storage unit 1003 can be used to store the program code and data of the communication device 1000.

[0124] In Figure 10 the described communication device 1000, an SPS release request is sent to the terminal through at least two PDCCHs on the same time slot. The SPS release request is used to indicate the release of the SPS PDSCH transmission. Since when the PDCCH for transmitting the SPS release performs multi-TRP transmission enhancement, the network device sends the SPS release request to the terminal through at least two PDCCHs on the same time slot, thereby ensuring the reliability of the PDCCH transmission. And only the transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs needs to be before the transmission end time unit of the SPS PDSCH transmission, thereby relaxing the restriction on the downlink resource scheduling of the network device and improving the scheduling flexibility of the network device.

[0125] Please refer to Figure 11 , Figure 11 which is a schematic structural diagram of a network device 1110 provided in the embodiments of the present application. As Figure 11 shown, the network device 1110 includes a communication interface 1111, a processor 1112, a memory 1113, and at least one communication bus 1114 for connecting the communication interface 1111, the processor 1112, and the memory 1113.

[0126] The memory 1113 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or a compact disc read-only memory (CD-ROM), and the memory 1113 is used for relevant instructions and data.

[0127] The communication interface 1111 is used for receiving and sending data.

[0128] The processor 1112 can be one or more central processing units (CPUs). In the case where the processor 1112 is a single CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0129] The processor 1112 in the network device 1110 is configured to read one or more program codes stored in the memory 1113 and perform the following operations: sending a semi-persistent scheduling (SPS) release request to a terminal via at least two physical downlink control channels (PDCCHs) in the same time slot, where the SPS release request is used to indicate the release of the physical downlink shared channel (SPS PDSCH) transmission of the semi-persistent scheduling; the transmission end time unit of the earliest-transmitted PDCCH among the at least two PDCCHs that transmits the SPS release request is before the transmission end time unit of the SPS PDSCH transmission.

[0130] It should be noted that the implementation of each operation can also be correspondingly referred to Figure 4 the corresponding description in the method embodiment shown.

[0131] In Figure 11 the described network device 1110, an SPS release request is sent to a terminal via at least two PDCCHs in the same time slot, and the SPS release request is used to indicate the release of the SPS PDSCH transmission; since when multi-TRP transmission enhancement is performed for the PDCCH that transmits the SPS release, the network device sends the SPS release request to the terminal via at least two PDCCHs in the same time slot, thereby ensuring the reliability of the PDCCH transmission; and only the transmission end time unit of the earliest-transmitted PDCCH among the at least two PDCCHs that transmits the SPS release request needs to be before the transmission end time unit of the SPS PDSCH transmission, thereby relaxing the restriction on the downlink resource scheduling of the network device and improving the scheduling flexibility of the network device.

[0132] Please refer to Figure 12, Figure 12 is a schematic structural diagram of a terminal 1210 provided by an embodiment of the present application. As Figure 12 shown, the terminal 1210 includes a communication interface 1211, a processor 1212, a memory 1213, and at least one communication bus 1214 for connecting the communication interface 1211, the processor 1212, and the memory 1213.

[0133] The memory 1213 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a compact disc read-only memory (CD-ROM). The memory 1213 is used for relevant instructions and data.

[0134] The communication interface 1211 is used to receive and send data.

[0135] The processor 1212 may be one or more central processing units (CPUs). When the processor 1212 is a single CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0136] The processor 1212 in the terminal 1210 is configured to read one or more program codes stored in the memory 1213 and perform the following operations: receiving, on the same time slot, an SPS release request from a network device through at least two PDCCHs, where the SPS release request is used to indicate the release of SPS PDSCH transmission; and the transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

[0137] It should be noted that the implementation of each operation may also correspond to the corresponding description in the Figure 4 method embodiment shown.

[0138] In Figure 12In the described terminal 1210, an SPS release request is sent to the terminal through at least two PDCCHs on the same time slot, and the SPS release request is used to indicate the release of SPS PDSCH transmission; since when multi-TRP transmission enhancement is performed on the PDCCH for transmitting the SPS release, the network device sends the SPS release request to the terminal through at least two PDCCHs on the same time slot, thus ensuring the reliability of PDCCH transmission; and, only the transmission end time unit of the earliest PDCCH that transmits the SPS release request among the at least two PDCCHs needs to be before the transmission end time unit of the SPS PDSCH transmission, thereby relaxing the restriction on the network device's downlink resource scheduling and improving the scheduling flexibility of the network device.

[0139] An embodiment of this application also provides a chip, which includes at least one processor, a memory, and an interface circuit. The memory, the transceiver, and the at least one processor are interconnected by lines, and a computer program is stored in the at least one memory; when the computer program is executed by the processor, Figure 4 the method flow in the method embodiment shown is implemented.

[0140] An embodiment of this application also provides a computer-readable storage medium, in which a computer program is stored. When it runs on a computer, Figure 4 the method flow in the method embodiment shown is implemented.

[0141] An embodiment of this application also provides a computer program product, including a computer program. When the computer program runs on a computer, Figure 4 the method flow in the method embodiment shown is implemented.

[0142] It should be understood that the processor mentioned in the embodiments of this application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0143] It should also be understood that the memory mentioned 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 ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (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 but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0144] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.

[0145] It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

[0146] It should also be understood that the first, second, third, fourth, and various digital numbers involved herein are only for the convenience of description and are not used to limit the scope of the present application.

[0147] It should be understood that the term "and / or" herein is only an association relationship describing associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects before and after.

[0148] It should be understood that in various embodiments of the present application, the sequence numbers of the above processes do not imply 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 to the implementation process of the embodiments of the present application.

[0149] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0150] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0151] In several embodiments provided by 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 merely illustrative. For example, the above division of units is only a logical function division, and there can be other division methods in actual implementation. For example, 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 displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of devices or units can be in an electrical, mechanical or other form.

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

[0153] In addition, the functional units in various embodiments of the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0154] If the above 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 this application, in essence, or the part that contributes to the prior art or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods shown in various embodiments of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0155] The steps in the method of the embodiments of this application can be adjusted, combined, and deleted according to actual needs.

[0156] The modules in the device of the embodiments of this application can be combined, divided, and deleted according to actual needs.

[0157] The above, the above embodiments are only used to illustrate the technical solutions of this application, rather than to limit it; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the various embodiments of this application.

Claims

1. A communication method, characterized in that, Applied to a network device, the method includes: Sending a semi-persistent scheduling (SPS) release request to a terminal via at least two physical downlink control channels (PDCCHs) in the same time slot, where the SPS release request is used to indicate the release of the physical downlink shared channel (SPS PDSCH) transmission of the semi-persistent scheduling; The transmission end time unit of the PDCCH that first transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

2. The method according to claim 1, characterized in that, The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same physical uplink control channel (PUCCH). The method further includes: Receiving the hybrid automatic repeat request acknowledgement (HARQ-ACK) information of the SPS release request fed back from the terminal.

3. The method according to claim 1, characterized in that, The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The method further includes: Receiving the HARQ-ACK information of the SPS release request fed back from the terminal.

4. The method according to claim 3, characterized in that, The method further includes: Receiving the HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; Receiving the negative acknowledgement (NACK) information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request.

5. The method according to any one of claims 1-4, characterized in that The at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

6. The method according to any one of claims 1-4, characterized in that, The at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, the transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

7. A communication method, characterized in that, Applied to a terminal, the method includes: Receiving an SPS release request from a network device via at least two PDCCHs in the same time slot, where the SPS release request is used to indicate the release of the SPS PDSCH transmission; The transmission end time unit of the PDCCH that first transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

8. The method according to claim 7, characterized in that The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same PUCCH. The method further includes: Feedback the HARQ-ACK information of the SPS release request to the network device.

9. The method according to claim 7, characterized in that, The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The method further includes: Feedback the HARQ-ACK information of the SPS release request to the network device.

10. The method according to claim 9, wherein The method further includes: Before successfully receiving the SPS release request, feedback the HARQ-ACK information of the SPS PDSCH transmission to the network device; After successfully receiving the SPS release request, feedback the NACK information of the SPS PDSCH transmission to the network device.

11. The method according to any one of claims 7 to 10, characterized in that The at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

12. The method according to any one of claims 7-10, characterized in that, The at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, the transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

13. A communication device, characterized in that, Applied to a network device, the apparatus includes: A sending unit, configured to send a semi-static scheduling (SPS) release request to a terminal through at least two physical downlink control channels (PDCCHs) on the same time slot, where the SPS release request is used to indicate the release of the physical downlink shared channel (SPS PDSCH) transmission of semi-static scheduling; The transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

14. The device according to claim 13, characterized in that, The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same physical uplink control channel (PUCCH). The apparatus further includes: A receiving unit, configured to receive the hybrid automatic repeat request acknowledgement (HARQ-ACK) information of the SPS release request fed back from the terminal.

15. The device according to claim 13, characterized in that, The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The apparatus further includes: A receiving unit, configured to receive the HARQ-ACK information of the SPS release request fed back from the terminal.

16. The device according to claim 15, characterized in that, The receiving unit is further configured to: Receive the HARQ-ACK information of the SPS PDSCH transmission fed back from the terminal, where the HARQ-ACK information of the SPS PDSCH transmission is sent by the terminal before successfully receiving the SPS release request; Receiving the negative acknowledgment NACK information of the SPS PDSCH transmission fed back from the terminal, where the NACK information of the SPS PDSCH transmission is sent by the terminal after successfully receiving the SPS release request.

17. The device according to any one of claims 13-16, characterized in that, The at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

18. The device according to any one of claims 13-16, characterized in that, The at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, the transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

19. A communication device, characterized in that, Applied to a terminal, the apparatus includes: A receiving unit, configured to receive an SPS release request from a network device through at least two PDCCHs on the same time slot, where the SPS release request is used to indicate releasing the SPS PDSCH transmission; The transmission end time unit of the PDCCH that earliest transmits the SPS release request among the at least two PDCCHs is before the transmission end time unit of the SPS PDSCH transmission.

20. The device according to claim 19, characterized in that, The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use the same PUCCH. The apparatus further includes: A sending unit, configured to feed back the HARQ-ACK information of the SPS release request to the network device.

21. The device according to claim 19, characterized in that, The feedback of the SPS release request and the feedback of the SPS PDSCH transmission use different PUCCHs. The apparatus further includes: A sending unit, configured to feed back the HARQ-ACK information of the SPS release request to the network device.

22. The device according to claim 21, wherein, The sending unit is further configured to: Before successfully receiving the SPS release request, feed back the HARQ-ACK information of the SPS PDSCH transmission to the network device; After successfully receiving the SPS release request, feed back the NACK information of the SPS PDSCH transmission to the network device.

23. The device according to any one of claims 19-22, characterized in that, The at least two PDCCHs include a first PDCCH and a second PDCCH. The transmission end time unit of the first PDCCH is before the transmission end time unit of the SPS PDSCH, and the transmission start time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

24. The device according to any one of claims 19-22, characterized in that, The at least two PDCCHs include a first PDCCH and a second PDCCH. A transmission end time unit of the first PDCCH is before a transmission end time unit of the SPS PDSCH. A transmission start time unit of the second PDCCH is before the transmission end time unit of the SPS PDSCH, and a transmission end time unit of the second PDCCH is after the transmission end time unit of the SPS PDSCH.

25. A network device, characterized in that, Comprising a processor, a memory, a communication interface, and one or more programs, the one or more programs being stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps in the method according to any one of claims 1-6.

26. A terminal, characterized in that, Comprising a processor, a memory, a communication interface, and one or more programs, the one or more programs being stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps in the method according to any one of claims 7-12.

27. A chip, characterized in that, Comprising: A processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-6 or 7-12.

28. A computer-readable storage medium, characterized in that, It stores a computer program for electronic data exchange, wherein when the computer program runs on a computer, the computer is caused to execute the method according to any one of claims 1-6 or 7-12.

29. A computer program product, characterized in that, Including a computer program, which when running on a computer causes the computer to execute the method according to any one of claims 1-6 or 7-12.

Images