Processing method, communication device and storage medium

Abstract

Disclosed in the present application are a processing method, a communication device and a storage medium. The processing method comprises: a terminal device determining a HARQ-ACK feedback on the basis of the symbol type of a symbol where a PDSCH occasion is located. By means of the technical solution of the present application, in a scenario where a plurality of PDSCH occasions and an SBFD configuration 1 are scheduled by means of a single piece of DCI, it is possible to avoid determining the feedback of the plurality of PDSCH occasions as NACK.

Description

Processing method, communication device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a processing method, communication equipment and storage medium. Background Art

[0002] In existing protocols, when a single DCI (Downlink Control Information) schedules multiple PDSCH (Physical Downlink Shared Channel) opportunities, in the SBFD (Subband Full Duplex) configuration 1 scenario, PDSCH opportunities with invalid symbol types will be discarded.

[0003] During the process of conceiving and implementing this application, the inventors discovered at least the following problems:

[0004] If the HARQ-ACK (Hybrid Automatic RepeatreQuest-ACKnowledgement) codebook construction rules of the existing protocol are followed when configuring time domain bundling, when the terminal device does not receive a PDSCH of an invalid symbol type, the terminal device will generate a NACK (Negative ACKnowledgment). After applying a binary AND operation, the feedback of multiple PDSCH opportunities will be determined as NACK, resulting in invalid feedback.

[0005] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Technical Solutions

[0006] The main purpose of the present application is to provide a processing method, a communication device and a storage medium, which can avoid determining the feedback of multiple PDSCH opportunities as NACK in the scenario of single DCI scheduling multiple PDSCH opportunities and SBFD configuration 1.

[0007] This application provides a processing method that can be applied to a terminal device (such as a mobile phone), comprising the following steps:

[0008] S1: Determine HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity lies.

[0009] Optionally, the method further comprises at least one of the following:

[0010] The PDSCH opportunity is at least one group;

[0011] A set of PDSCH opportunities is determined by time-domain hybrid automatic repeat request-bundling type 1;

[0012] HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities;

[0013] The symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0014] Optionally, the method further comprises at least one of the following:

[0015] Invalid symbol types include SBFD symbols or non-SBFD symbols;

[0016] Valid symbol types include SBFD symbol or non-SBFD symbol;

[0017] Determine the symbol type of the symbol where the first PDSCH is located in a single DCI scheduling multiple PDSCH opportunities as a valid symbol type;

[0018] A symbol type different from the symbol type of the symbol where the first PDSCH in an opportunity of scheduling multiple PDSCHs by a single DCI is located is determined as an invalid symbol type.

[0019] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0020] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0021] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0022] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0023] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0024] Optionally, determining HARQ-ACK feedback includes at least one of the following:

[0025] Determine a HARQ-ACK information bit by performing an AND operation on the binary value of the HARQ-ACK information bit at the PDSCH opportunity;

[0026] Determine a group of HARQ-ACK information bits for a single DCI scheduled PDSCH opportunity, and determine one HARQ-ACK information bit through an AND operation based on the binary values ​​of the HARQ-ACK information bits for the group of PDSCH opportunities.

[0027] Optionally, the method further comprises: generating an ACK value for a PDSCH opportunity that only includes overlaps and / or partial overlaps with invalid symbols.

[0028] The present application also provides a processing method, which can be applied to a network device (such as a base station or a satellite), comprising the steps of:

[0029] S2: Receive HARQ-ACK feedback, which is determined by the terminal device based on the symbol type of the symbol where the PDSCH opportunity is located.

[0030] Optionally, the method further comprises at least one of the following:

[0031] The PDSCH opportunity is at least one group;

[0032] A set of PDSCH opportunities is determined by time-domain hybrid automatic repeat request-bundling type 1;

[0033] HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities;

[0034] The symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0035] Optionally, the method further comprises at least one of the following:

[0036] Invalid symbol types include SBFD symbols or non-SBFD symbols;

[0037] Valid symbol types include SBFD symbol or non-SBFD symbol;

[0038] Determine the symbol type of the symbol where the first PDSCH is located in a single DCI scheduling multiple PDSCH opportunities as a valid symbol type;

[0039] A symbol type different from the symbol type of the symbol where the first PDSCH in an opportunity of scheduling multiple PDSCHs by a single DCI is located is determined as an invalid symbol type.

[0040] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0041] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0042] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0043] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0044] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0045] Optionally, the terminal device determines HARQ-ACK feedback, including at least one of the following:

[0046] The terminal device determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity;

[0047] The terminal device determines a group of HARQ-ACK information bits of PDSCH opportunities scheduled by a single DCI, and determines a HARQ-ACK information bit according to the binary AND operation of the HARQ-ACK information bits of the group of PDSCH opportunities.

[0048] Optionally, the method further includes: for a PDSCH opportunity that only includes overlap and / or partial overlap with invalid symbols, the terminal device generates an ACK value.

[0049] The present application also provides a processing device, comprising:

[0050] The determination module is configured to determine HARQ-ACK feedback based on a symbol type of a symbol where a PDSCH opportunity is located.

[0051] The present application also provides a processing device, comprising:

[0052] The sending module is used to receive HARQ-ACK feedback, where the HARQ-ACK feedback is determined by the terminal device based on the symbol type of the symbol where the PDSCH opportunity is located.

[0053] The present application also provides a communication device, comprising: a memory, a processor, and a processing program stored in the memory and executable on the processor, wherein the processing program implements the steps of any of the above-described processing methods when executed by the processor.

[0054] The communication device in this application can be a terminal device (such as a mobile phone), a network device (such as a satellite), or a chip (such as an SOC or a baseband chip with communication functions, etc.). The specific reference needs to be clarified in the context.

[0055] The present application also provides a computer-readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, the steps of any of the processing methods described above are implemented.

[0056] In the technical solution of the present application, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located. In the scenario where a single DCI schedules multiple PDSCH opportunities and SBFD configuration 1, it can avoid determining the feedback of multiple PDSCH opportunities as NACK. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work.

[0058] FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0059] FIG2 is a diagram of a communication network system architecture provided by an embodiment of the present application;

[0060] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application;

[0061] FIG4 is a schematic diagram of the hardware structure of a network node 150 provided in this application;

[0062] FIG5 is a schematic flow chart of a processing method according to the first embodiment of the present application;

[0063] FIG6 is a schematic flow chart of a processing method according to a fourth embodiment of the present application;

[0064] FIG7 is a schematic diagram of the interaction flow between a network device and a terminal device according to a processing method according to a fifth embodiment of the present application;

[0065] FIG8 is a first structural diagram of a processing device provided in an embodiment of the present application;

[0066] FIG9 is a second structural diagram of a processing device provided in an embodiment of the present application;

[0067] FIG10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.

[0068] The purpose of this application, its features, and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and the accompanying text are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of this application to those skilled in the art by reference to specific embodiments.

[0069] Implementation Methods of the Application

[0070] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0071] It should be noted that, in this document, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element, and / or, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0072] It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are used solely to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if," as used herein, may be interpreted as "upon," "when," or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the recited features, steps, operations, elements, components, items, types, and / or groups, but do not preclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used herein, may be interpreted as inclusive, meaning any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”; and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0073] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0074] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0075] It should be noted that in this article, step codes such as S1 and S2 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial restriction on the order. When implementing the step, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the scope of protection of this application.

[0076] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0077] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0078] The communication device in this application can be a terminal device (such as a mobile phone), a network device (such as a base station), or a chip (such as an SOC or a baseband chip with communication functions, etc.). The specific reference needs to be clarified according to the context.

[0079] The terminal device may be implemented in various forms. For example, the terminal device described in this application may include intelligent terminal devices such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, and other fixed terminal devices such as digital TVs and desktop computers.

[0080] The subsequent description will be made using a mobile terminal as an example. Those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the configuration according to the embodiments of the present application can also be applied to fixed-type terminal devices.

[0081] Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application. The mobile terminal 100 may include components such as an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will understand that the mobile terminal structure shown in Figure 1 does not limit the mobile terminal. The mobile terminal may include more or fewer components than shown, or may combine certain components, or arrange the components differently.

[0082] The following is a detailed introduction to the various components of the mobile terminal in conjunction with Figure 1:

[0083] The RF unit 101 can be used to send and receive information or receive signals during calls. Specifically, it receives downlink information from the base station and transmits it to the processor 110 for processing. It also transmits uplink data to the base station. Typically, the RF unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and / or other components. Furthermore, the RF unit 101 can communicate with the network and other devices via wireless communication. The above-mentioned wireless communications can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G and 6G, etc.

[0084] WiFi is a short-range wireless transmission technology. A mobile terminal, through WiFi module 102, enables users to send and receive emails, browse web pages, and access streaming media, providing wireless broadband Internet access. Although FIG1 illustrates WiFi module 102, it is understood that it is not a required component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

[0085] The audio output unit 103 can convert audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Furthermore, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, or the like.

[0086] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos captured by an image capture device (e.g., a camera) in video capture mode or image capture mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the GPU 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the RF unit 101 or the WiFi module 102. The microphone 1042 may receive sound (audio data) in operating modes such as a phone call mode, a recording mode, and a voice recognition mode, and may process such sound into audio data. In the phone call mode, the processed audio (voice) data may be converted into a format that can be transmitted to a mobile communication base station via the RF unit 101. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0087] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be described here.

[0088] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0089] The user input unit 107 can be used to receive input digital or character information and generate key signal input related to user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can collect user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any other suitable object or accessory on or near the touch panel 1071) and drive corresponding connected devices according to a pre-set program. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch direction and detects the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 110. It can also receive and execute commands sent by the processor 110. And / or, the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, power keys, etc.), a trackball, a mouse, a joystick, etc., and the specifics are not limited here.

[0090] Optionally, the touch panel 1071 may overlay the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. The processor 110 then provides a corresponding visual output on the display panel 1061 based on the type of touch event. Although in FIG1 , the touch panel 1071 and the display panel 1061 are shown as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited to this specific embodiment.

[0091] The interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

[0092] Memory 109 can be used to store software programs and various data. Memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store an operating system and at least one application required for a function (such as a sound playback function or an image playback function); the data storage area may store data generated based on the use of the mobile phone (such as audio data, a phone book, etc.). Furthermore, / or, memory 109 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0093] Processor 110 is the control center of the mobile terminal, connecting all components of the mobile terminal using various interfaces and circuits. By running or executing software programs and / or modules stored in memory 109 and accessing data stored in memory 109, it executes various functions of the mobile terminal and processes data, thereby providing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, processor 110 may integrate an application processor and a modem processor. Optionally, the application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 110.

[0094] The mobile terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0095] Although not shown in FIG. 1 , the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

[0096] To facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

[0097] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of the present application. The communication network system is an NR (New Radio) system of universal mobile communication technology. The NR system includes UE (User Equipment) 201, E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, EPC (Evolved Packet Core) 203 and the operator's IP service 204, which are connected in sequence.

[0098] Optionally, UE201 may be the above-mentioned terminal device 100, which will not be described in detail here.

[0099] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 . Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface). eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide access from UE 201 to EPC 203 .

[0100] EPC 203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gate Way) 2034, a PGW (PDN Gate Way) 2035, and a PCRF (Policy and Charging Rules Function) 2036. Optionally, MME 2031 is a control node that processes signaling between UE 201 and EPC 203, providing bearer and connection management. HSS 2032 provides registers for managing functions such as the Home Location Register (not shown) and stores user-specific information such as service features and data rates. All user data can be sent through SGW2034, PGW2035 can provide IP address allocation and other functions for UE 201, PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources, and it selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

[0101] The IP service 204 may include the Internet, an intranet, an IMS (IP Multimedia Subsystem), or other IP services.

[0102] Although the above introduction takes the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but can also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., which are not limited here.

[0103] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0104] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0105] Figure 4 is a schematic diagram of the hardware structure of a network node 150 provided in this application. Network node 150 includes: a memory 1501 and a processor 1502. Memory 1501 is used to store program instructions, and processor 1502 is used to call the program instructions in memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0106] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0107] The integrated modules implemented in the form of software function modules can be stored in a computer-readable storage medium. The software function modules stored in a storage medium include a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute some of the steps of the methods of various embodiments of the present application.

[0108] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive solid state disk, SSD), etc.

[0109] Based on the above-mentioned mobile terminal hardware structure and communication network system, various embodiments of the present application are proposed.

[0110] Technical terms involved in this embodiment:

[0111] PDSCH: Physical Downlink Shared CHannel, physical downlink shared channel;

[0112] PDCCH: Physical Downlink Control CHannel, physical downlink control channel;

[0113] PRB: Physical Resource Block, physical resource block;

[0114] SBFD: SubBand Full-Duplex, sub-band full-duplex;

[0115] HARQ-ACK: Hybrid Automatic RepeatreQuest-ACKnowledgement, hybrid automatic repeat request-acknowledgement;

[0116] Type-1 HARQ-ACK codebook: Type 1 hybrid automatic repeat request-acknowledgement codebook;

[0117] Type-2 HARQ-ACK codebook: Type 2 hybrid automatic repeat request-acknowledgement codebook;

[0118] timeDomainHARQ-BundlingType1: time domain hybrid automatic repeat request-bundling type 1;

[0119] nrofHARQ-BundlingGroups: number of hybrid automatic repeat request bundling groups;

[0120] DCI: Downlink Control Information, downlink control information;

[0121] UL: UpLink, uplink;

[0122] DL: DownLink, downlink.

[0123] First embodiment

[0124] 5 , which is a flow chart of a processing method according to a first embodiment of the present application, the processing method according to the embodiment of the present application can be applied to a terminal device (such as a mobile phone), and includes the following steps:

[0125] S1: The terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located.

[0126] This embodiment takes into account that for SBFD (sub-band full-duplex) configuration 1, PDSCH opportunities of invalid symbol types will be discarded. If the HARQ-ACK codebook construction rules of the existing protocol are followed when configuring time domain bundling, when the terminal device does not receive the PDSCH of the invalid symbol type, the terminal device will generate a NACK. After applying the binary AND operation, the feedback of multiple PDSCHs will be determined as NACK, resulting in invalid feedback.

[0127] Therefore, in the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located, so that in the scenario of single DCI scheduling multiple PDSCH opportunities and SBFD configuration 1, it is possible to avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0128] Optionally, the PDSCH opportunity may be at least one group.

[0129] Optionally, in the case where the PDSCH opportunities are a group, the group of PDSCH opportunities is determined by time domain hybrid automatic repeat request-bundling type 1.

[0130] Optionally, a set of PDSCH opportunities is configured by RRC signaling.

[0131] Optionally, the HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities.

[0132] Optionally, the type 1 HARQ-ACK feedback is a type 1 HARQ-ACK codebook.

[0133] Optionally, the symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0134] Optionally, the invalid symbol type includes an SBFD symbol or a non-SBFD symbol.

[0135] Optionally, the valid symbol type includes a non-SBFD symbol or a SBFD symbol.

[0136] Optionally, the symbol type of the symbol where the first PDSCH is located in the occasion where a single DCI schedules multiple PDSCHs is determined as a valid symbol type.

[0137] Optionally, a symbol type different from the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0138] Optionally, the symbol type of the time slot where the first PDSCH in the single DCI scheduling multiple PDSCH opportunities is located is determined as the valid symbol type.

[0139] Optionally, a symbol type different from the symbol type of the time slot where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0140] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0141] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0142] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0143] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0144] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0145] Optionally, determining HARQ-ACK feedback includes at least one of the following:

[0146] The terminal device determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity;

[0147] The terminal device determines a group of HARQ-ACK information bits of PDSCH opportunities scheduled by a single DCI, and determines one HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bits of the group of PDSCH opportunities.

[0148] Optionally, for configuration 1, for type 1 HARQ-ACK feedback for multiple PDSCH opportunities scheduled by a single DCI, if timeDomainHARQ-BundlingType1 is provided, the HARQ-ACK information bits for multiple PDSCH opportunities scheduled by a single DCI are determined as follows:

[0149] PDSCH timing that does not overlap with uplink symbols;

[0150] PDSCH opportunities that do not overlap or partially overlap with invalid symbol types.

[0151] Optionally, for type 1 HARQ-ACK feedback of multiple PDSCH opportunities scheduled by a single DCI, the terminal device determines, based on the symbol type of the symbol in which the PDSCH opportunity is located, that the HARQ-ACK feedback includes at least one of the following:

[0152] For a PDSCH opportunity that does not overlap with an uplink symbol and / or a PDSCH opportunity that does not overlap or partially overlaps with an invalid symbol type, the binary HARQ-ACK information bits of the above PDSCH opportunity are ANDed to determine one HARQ-ACK information bit;

[0153] For PDSCH opportunities that only contain overlap and / or partial overlap with invalid symbols, an ACK value is generated.

[0154] Optionally, the terminal device sends the determined HARQ-ACK feedback to the network device.

[0155] Optionally, the network device may be a base station or the like.

[0156] Through the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located. In the scenario where a single DCI schedules multiple PDSCH opportunities and SBFD configuration 1, it can avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0157] Second embodiment

[0158] Based on the first embodiment of the present application, the second embodiment of the present application further elaborates on the HARQ-ACK feedback determination method.

[0159] In the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located, so that in the scenario of single DCI scheduling multiple PDSCH opportunities and SBFD configuration 1, it is possible to avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0160] Optionally, there may be multiple PDSCH opportunities or the PDSCH opportunities may constitute a group.

[0161] Optionally, in the case where the PDSCH opportunities constitute a group, the group of PDSCH opportunities is determined by time domain hybrid automatic repeat request-bundling type 1.

[0162] Optionally, a set of PDSCH opportunities is configured by RRC signaling.

[0163] Optionally, the HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities.

[0164] Optionally, the symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0165] Optionally, the invalid symbol type includes an SBFD symbol or a non-SBFD symbol.

[0166] Optionally, the valid symbol type includes a non-SBFD symbol or a SBFD symbol.

[0167] Optionally, the symbol type of the symbol where the first PDSCH is located in the occasion where a single DCI schedules multiple PDSCHs is determined as a valid symbol type.

[0168] Optionally, a symbol type different from the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0169] Optionally, the symbol type of the time slot where the first PDSCH in the single DCI scheduling multiple PDSCH opportunities is located is determined as the valid symbol type.

[0170] Optionally, a symbol type different from the symbol type of the time slot where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0171] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0172] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0173] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0174] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0175] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0176] Optionally, determining HARQ-ACK feedback includes at least one of the following:

[0177] The terminal device determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity;

[0178] The terminal device determines a HARQ-ACK information bit for a group of PDSCH opportunities scheduled by a single DCI, and determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bits for the group of PDSCH opportunities.

[0179] Optionally, for configuration 1, for type 1 HARQ-ACK feedback for multiple PDSCH opportunities scheduled by a single DCI, if timeDomainHARQ-BundlingType1 is provided, the HARQ-ACK information bits for multiple PDSCH opportunities scheduled by a single DCI are determined as follows:

[0180] For PDSCH opportunities that do not overlap with uplink symbols, and / or PDSCH opportunities that do not overlap or do not partially overlap with invalid symbol types, the binary HARQ-ACK information bits of the above PDSCH opportunities are ANDed to determine a HARQ-ACK information bit, which corresponds to the HARQ-ACK information of a group of PDSCH opportunities determined by timeDomainHARQ-BundlingType1.

[0181] Optionally, for PDSCH opportunities that do not overlap with uplink symbols, and / or PDSCH opportunities that do not overlap or partially overlap with invalid symbol types, the terminal device generates corresponding HARQ-ACK information bits based on the reception result and / or decoding result of the PDSCH. Optionally, the terminal device then determines a HARQ-ACK information bit through an AND operation of the binary values ​​of these HARQ-ACK information bits, and the information bit corresponds to the HARQ-ACK information of a group of PDSCH opportunities determined by timeDomainHARQ-BundlingType1.

[0182] Optionally, for PDSCH opportunities that overlap with uplink symbols and / or PDSCH opportunities that overlap or partially overlap with invalid symbol types, the terminal device ignores these PDSCH opportunities.

[0183] Optionally, the terminal device determines the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunity is located as a valid symbol type, and the corresponding other symbol type is an invalid symbol type. For example, if the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunity is located is an SBFD symbol, then the SBFD symbol is a valid symbol and the non-SBFD symbol is an invalid symbol.

[0184] Optionally, the terminal device determines the type 1 HARQ-ACK codebook for transmission on the PUCCH according to the following pseudo code: HARQ-ACK information bits, a total of O ACK HARQ-ACK information bits: set c = 0 - serving cell index: the subscript corresponds to the subscript RRC index of the corresponding cell, including (if applicable) cells in set S0 and set S1;

[0185] Set j = 0 - HARQ-ACK information bit index;

[0186] set up The number of service cells configured by the upper layer for the terminal;

[0187] While

[0188] Set m=0 – the timing index of candidate PDSCH reception, SPS PDSCH release or TCI status update;

[0189] While m <M c ;

[0190] If timeDomainHARQ-BundlingType1 is provided for serving cell c, and the PDSCH associated with time instance m is scheduled by a DCI format indicating a TDRA row containing multiple SLIV entries;

[0191] If harq-ACK-SpatialBundlingPUCCH is not provided and the terminal is configured with maxNrofCodeWordsScheduledByDCI, it receives two transport blocks of the active DL BWP of serving cell c;

[0192] if PDSCH is associated with the last SLIV in the TDRA row;

[0193] = Binary AND operation of the HARQ-ACK information bits corresponding to the first transport block in PDSCH reception, where these HARQ-ACK information bits do not overlap with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated scheduled by the serving cell c DCI format, or do not overlap or partially overlap with invalid symbol types;

[0194] j=j+1;

[0195] = Perform a binary AND operation on the HARQ-ACK information bits corresponding to the second transport block in PDSCH reception, where these HARQ-ACK information bits do not overlap with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated scheduled by the serving cell c DCI format, or do not overlap or partially overlap with invalid symbol types;

[0196] else

[0197] =NACK;

[0198] j=j+1;

[0199] =NACK;

[0200] end if

[0201] j=j+1;

[0202] elseif harq-ACK-SpatialBundlingPUCCH is provided and the terminal is configured by maxNrofCodeWordsScheduledByDCI, it receives two transport blocks of the active DL BWP of serving cell c;

[0203] if PDSCH is associated with the last SLIV in the TDRA row;

[0204] = Perform a binary AND operation on the HARQ-ACK information bits corresponding to all transport blocks in the PDSCH scheduled by the DCI format of serving cell c that do not overlap with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or do not overlap or partially overlap with invalid symbol types;

[0205] If the terminal receives a transport block, the terminal device generates an ACK for the second transport block;

[0206] else

[0207] =NACK;

[0208] end if

[0209] j=j+1;

[0210] else

[0211] if PDSCH is associated with the last SLIV in the TDRA row;

[0212] = Perform a binary AND operation on the HARQ-ACK information bits corresponding to all transport blocks in the PDSCH scheduled by the DCI format of serving cell c that do not overlap with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or do not overlap or partially overlap with invalid symbol types;

[0213] else

[0214] =NACK;

[0215] end if

[0216] j=j+1;

[0217] end if

[0218] end if

[0219] m=m+1;

[0220] end while

[0221] c=c+1;

[0222] end while.

[0223] Optionally, the terminal device sends the determined HARQ-ACK feedback to the network device.

[0224] Optionally, the network device may be a base station or a satellite, etc.

[0225] Through the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located. In the scenario where a single DCI schedules multiple PDSCH opportunities and SBFD configuration 1, it can avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0226] Third embodiment

[0227] Based on any of the above embodiments of the present application, the third embodiment of the present application further elaborates on the HARQ-ACK feedback determination method.

[0228] In the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located, so that in the scenario of single DCI scheduling multiple PDSCH opportunities and SBFD configuration 1, it is possible to avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0229] Optionally, the PDSCH occasions may be multiple or a group.

[0230] Optionally, in the case where the PDSCH opportunities are a group, the group of PDSCH opportunities is determined by time domain hybrid automatic repeat request-bundling type 1.

[0231] Optionally, a set of PDSCH opportunities is configured by RRC signaling.

[0232] Optionally, the HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities.

[0233] Optionally, the symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0234] Optionally, the invalid symbol type includes an SBFD symbol or a non-SBFD symbol.

[0235] Optionally, the valid symbol type includes a non-SBFD symbol or a SBFD symbol.

[0236] Optionally, the symbol type of the symbol where the first PDSCH is located in the occasion where a single DCI schedules multiple PDSCHs is determined as a valid symbol type.

[0237] Optionally, a symbol type different from the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0238] Optionally, the symbol type of the time slot where the first PDSCH in the single DCI scheduling multiple PDSCH opportunities is located is determined as the valid symbol type.

[0239] Optionally, a symbol type different from the symbol type of the time slot where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0240] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0241] The symbols of a group of PDSCH opportunities do not overlap with uplink symbols;

[0242] A set of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0243] The symbols of a group of PDSCH opportunities do not overlap or partially do not overlap with invalid symbol types;

[0244] A group of symbols where PDSCH opportunities are located overlaps with valid symbol types.

[0245] Optionally, determining HARQ-ACK feedback includes at least one of the following:

[0246] The terminal device determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity;

[0247] The terminal device determines the HARQ-ACK information bits of a group of PDSCH opportunities for a single DCI-scheduled PDSCH opportunity, and determines one HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bits of the group of PDSCH opportunities.

[0248] For PDSCH opportunities that only contain overlap with invalid symbols, the terminal device generates an ACK value.

[0249] Optionally, for configuration 1, for type 1 HARQ-ACK feedback for multiple PDSCH opportunities scheduled by a single DCI, if timeDomainHARQ-BundlingType1 is provided, the HARQ-ACK information bits for multiple PDSCH opportunities scheduled by a single DCI are determined as follows:

[0250] For PDSCH opportunities that do not overlap with uplink symbols, the binary HARQ-ACK information bits of the PDSCH opportunity are ANDed together to determine a HARQ-ACK information bit, which corresponds to the HARQ-ACK information of a group of PDSCH opportunities determined by timeDomainHARQ-BundlingType1. For PDSCH opportunities that only contain overlaps with invalid symbols, the terminal device generates an ACK value.

[0251] Optionally, for PDSCH opportunities that do not overlap with uplink symbols, and / or PDSCH opportunities that do not overlap or partially overlap with invalid symbol types, the terminal device generates corresponding HARQ-ACK information bits based on the reception result and / or decoding result of the PDSCH.

[0252] Optionally, for PDSCH occasions that overlap or partially overlap with an invalid symbol type, the terminal device generates an ACK value.

[0253] Optionally, the terminal device further performs an AND operation on the binary values ​​of these HARQ-ACK information bits to determine a HARQ-ACK information bit, which corresponds to the HARQ-ACK information of a group of PDSCH timings determined by timeDomainHARQ-BundlingType1.

[0254] Optionally, the terminal device determines the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located as a valid symbol type, and the corresponding other symbol type is an invalid symbol type. For example, if the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is an SBFD symbol, the SBFD symbol is a valid symbol, and the non-SBFD symbol is an invalid symbol.

[0255] The terminal device determines the type 1 HARQ-ACK codebook for transmission on the PUCCH according to the following pseudo code: HARQ-ACK information bits, a total of O ACK HARQ-ACK information bits: set c = 0 - serving cell index: the subscript corresponds to the subscript RRC index of the corresponding cell, including (if applicable) cells in set S0 and set S1;

[0256] Set j = 0 - HARQ-ACK information bit index;

[0257] set up The number of service cells configured by the upper layer for the terminal;

[0258] While

[0259] Set m=0 – the timing index of candidate PDSCH reception, SPS PDSCH release or TCI status update;

[0260] While m <M c ;

[0261] If timeDomainHARQ-BundlingType1 is provided for serving cell c, and the PDSCH associated with time m

[0262] Scheduled by the DCI format, indicating a TDRA row containing multiple SLIV entries;

[0263] If harq-ACK-SpatialBundlingPUCCH is not provided and the terminal is configured with maxNrofCodeWordsScheduledByDCI, it receives two transport blocks of the active DL BWP of serving cell c;

[0264] if PDSCH is associated with the last SLIV in the TDRA row;

[0265] = Binary AND operation of the HARQ-ACK information bits corresponding to the first transport block in PDSCH reception, where these HARQ-ACK information bits do not overlap with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated scheduled in the serving cell c DCI format. For PDSCH opportunities that only contain overlap with invalid symbols, the terminal device generates an ACK value for that PDSCH;

[0266] j=j+1;

[0267] = Perform a binary AND operation on the HARQ-ACK information bits corresponding to the second transport block in the PDSCH reception, where these HARQ-ACK information bits do not overlap with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated scheduled by the serving cell c DCI format. For PDSCH opportunities that only contain overlap with invalid symbols, the terminal device generates an ACK value for that PDSCH;

[0268] else

[0269] =NACK;

[0270] j=j+1;

[0271] =NACK;

[0272] end if

[0273] j=j+1;

[0274] elseif harq-ACK-SpatialBundlingPUCCH is provided and the terminal is configured by maxNrofCodeWordsScheduledByDCI, it receives two transport blocks of the active DL BWP of serving cell c;

[0275] if PDSCH is associated with the last SLIV in the TDRA row;

[0276] = Perform a binary AND operation on the HARQ-ACK information bits corresponding to all transport blocks in the PDSCH scheduled by the DCI format of serving cell c that do not overlap with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. For PDSCH opportunities that only contain overlaps with invalid symbols, the terminal device generates an ACK value for that PDSCH;

[0277] If the terminal receives a transport block, the terminal device generates an ACK value for the second transport block;

[0278] else

[0279] =NACK;

[0280] end if

[0281] j=j+1;

[0282] else

[0283] if PDSCH is associated with the last SLIV in the TDRA row;

[0284] =Perform a binary AND operation on the HARQ-ACK information bits corresponding to all transport blocks in the PDSCH scheduled by the DCI format of the serving cell c and not overlapping with the uplink symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. For the PDSCH moments that only contain overlaps with invalid symbols, the terminal device generates an ACK value for the PDSCH.

[0285] else

[0286] =NACK;

[0287] end if

[0288] j=j+1;

[0289] end if

[0290] end if

[0291] m=m+1;

[0292] end while

[0293] c=c+1;

[0294] end while.

[0295] Through the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located. In the scenario where a single DCI schedules multiple PDSCH opportunities and SBFD configuration 1, it can avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0296] Fourth embodiment

[0297] 6 , which is a flow chart of a processing method according to a fourth embodiment of the present application, the processing method according to the embodiment of the present application can be applied to a network device (such as a base station), and includes the following steps:

[0298] S2: The network device receives HARQ-ACK feedback, where the HARQ-ACK feedback is determined by the terminal device based on the symbol type of the symbol where the PDSCH opportunity is located.

[0299] The technical solution of this embodiment can avoid determining the feedback of multiple PDSCH opportunities as NACK in the scenario where a single DCI schedules multiple PDSCH opportunities and SBFD configuration 1.

[0300] Optionally, the PDSCH opportunity may be at least one group.

[0301] Optionally, in the case where the PDSCH opportunities are a group, the group of PDSCH opportunities is determined by time domain hybrid automatic repeat request-bundling type 1.

[0302] Optionally, a set of PDSCH opportunities is configured by RRC signaling.

[0303] Optionally, the HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities.

[0304] Optionally, the type 1 HARQ-ACK feedback is a type 1 HARQ-ACK codebook.

[0305] Optionally, the symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0306] Optionally, the invalid symbol type includes an SBFD symbol or a non-SBFD symbol.

[0307] Optionally, the valid symbol type includes a non-SBFD symbol or a SBFD symbol.

[0308] Optionally, the symbol type of the symbol where the first PDSCH is located in the occasion where a single DCI schedules multiple PDSCHs is determined as a valid symbol type.

[0309] Optionally, a symbol type different from the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0310] Optionally, the symbol type of the time slot where the first PDSCH in the single DCI scheduling multiple PDSCH opportunities is located is determined as the valid symbol type.

[0311] Optionally, a symbol type different from the symbol type of the time slot where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0312] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0313] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0314] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0315] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0316] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0317] Optionally, determining HARQ-ACK feedback includes at least one of the following:

[0318] The terminal device determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity;

[0319] The terminal device determines a group of HARQ-ACK information bits of PDSCH opportunities scheduled by a single DCI, and determines one HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bits of the group of PDSCH opportunities.

[0320] Optionally, for configuration 1, for type 1 HARQ-ACK feedback for multiple PDSCH opportunities scheduled by a single DCI, if timeDomainHARQ-BundlingType1 is provided, the HARQ-ACK information bits for multiple PDSCH opportunities scheduled by a single DCI are determined as follows:

[0321] PDSCH timing that does not overlap with uplink symbols;

[0322] PDSCH opportunities that do not overlap or partially overlap with invalid symbol types.

[0323] Optionally, for type 1 HARQ-ACK feedback of multiple PDSCH opportunities scheduled by a single DCI, the terminal device determines, based on the symbol type of the symbol in which the PDSCH opportunity is located, that the HARQ-ACK feedback includes at least one of the following:

[0324] For a PDSCH opportunity that does not overlap with an uplink symbol and / or a PDSCH opportunity that does not overlap or partially overlaps with an invalid symbol type, the binary HARQ-ACK information bits of the above PDSCH opportunity are ANDed to determine one HARQ-ACK information bit;

[0325] For PDSCH opportunities that only contain overlap and / or partial overlap with invalid symbols, an ACK value is generated.

[0326] Optionally, the terminal device sends the determined HARQ-ACK feedback to the network device.

[0327] Optionally, the network device receives HARQ-ACK feedback sent by the terminal device.

[0328] Through the technical solution of this embodiment, the network device receives HARQ-ACK feedback, and the HARQ-ACK feedback is determined by the terminal device based on the symbol type of the symbol where the PDSCH opportunity is located. In the scenario of single DCI scheduling multiple PDSCH opportunities and SBFD configuration 1, it is possible to avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0329] Fifth embodiment

[0330] 7 , which is a schematic diagram of an interaction flow between a network device and a terminal device according to a processing method according to a fifth embodiment, the fifth embodiment of the present application proposes a processing method, including the following steps:

[0331] S1: The terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located;

[0332] S2: The network device receives HARQ-ACK feedback, where the HARQ-ACK feedback is determined by the terminal device based on the symbol type of the symbol where the PDSCH opportunity is located.

[0333] In the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located, so that in the scenario of single DCI scheduling multiple PDSCH opportunities and SBFD configuration 1, it is possible to avoid determining the feedback of multiple PDSCH opportunities as NACK.

[0334] Optionally, the PDSCH opportunity may be at least one group.

[0335] Optionally, in the case where the PDSCH opportunities are a group, the group of PDSCH opportunities is determined by time domain hybrid automatic repeat request-bundling type 1.

[0336] Optionally, a set of PDSCH opportunities is configured by RRC signaling.

[0337] Optionally, the HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities.

[0338] Optionally, the type 1 HARQ-ACK feedback is a type 1 HARQ-ACK codebook.

[0339] Optionally, the symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0340] Optionally, the invalid symbol type includes an SBFD symbol or a non-SBFD symbol.

[0341] Optionally, the valid symbol type includes a non-SBFD symbol or a SBFD symbol.

[0342] Optionally, the symbol type of the symbol where the first PDSCH is located in the occasion where a single DCI schedules multiple PDSCHs is determined as a valid symbol type.

[0343] Optionally, a symbol type different from the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0344] Optionally, the symbol type of the time slot where the first PDSCH in the single DCI scheduling multiple PDSCH opportunities is located is determined as the valid symbol type.

[0345] Optionally, a symbol type different from the symbol type of the time slot where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located is determined as an invalid symbol type.

[0346] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0347] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0348] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0349] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0350] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0351] Optionally, determining HARQ-ACK feedback includes at least one of the following:

[0352] The terminal device determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity;

[0353] The terminal device determines a group of HARQ-ACK information bits of PDSCH opportunities scheduled by a single DCI, and determines one HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bits of the group of PDSCH opportunities.

[0354] Optionally, for configuration 1, for type 1 HARQ-ACK feedback for multiple PDSCH opportunities scheduled by a single DCI, if timeDomainHARQ-BundlingType1 is provided, the HARQ-ACK information bits for multiple PDSCH opportunities scheduled by a single DCI are determined as follows:

[0355] PDSCH timing that does not overlap with uplink symbols;

[0356] PDSCH opportunities that do not overlap or partially overlap with invalid symbol types.

[0357] Optionally, for type 1 HARQ-ACK feedback of multiple PDSCH opportunities scheduled by a single DCI, the terminal device determines, based on the symbol type of the symbol in which the PDSCH opportunity is located, that the HARQ-ACK feedback includes at least one of the following:

[0358] For a PDSCH opportunity that does not overlap with an uplink symbol and / or a PDSCH opportunity that does not overlap or partially overlaps with an invalid symbol type, the binary HARQ-ACK information bits of the above PDSCH opportunity are ANDed to determine one HARQ-ACK information bit;

[0359] For PDSCH opportunities that only contain overlap and / or partial overlap with invalid symbols, an ACK value is generated.

[0360] Optionally, the terminal device sends the determined HARQ-ACK feedback to the network device.

[0361] Optionally, the network device may be a base station or the like.

[0362] In the technical solution of this embodiment, the terminal device determines the HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located, and the network device receives the HARQ-ACK feedback, thereby avoiding determining the feedback of multiple PDSCH opportunities as NACK in the scenario of single DCI scheduling multiple PDSCH opportunities and SBFD configuration 1.

[0363] Sixth embodiment

[0364] Please refer to FIG8 , which is a structural diagram of a processing device according to an embodiment of the present application. The device may be mounted on or be the terminal device in the above method embodiment. As shown in FIG8 , the device 160 includes:

[0365] The determination module 1601 is configured to determine HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located.

[0366] Optionally, the device further comprises at least one of the following:

[0367] The PDSCH opportunity is at least one group;

[0368] A set of PDSCH opportunities is determined by time-domain hybrid automatic repeat request-bundling type 1;

[0369] HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities;

[0370] The symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0371] Optionally, the device further comprises at least one of the following:

[0372] Invalid symbol types include SBFD symbols or non-SBFD symbols;

[0373] Valid symbol types include SBFD symbol or non-SBFD symbol;

[0374] Determine the symbol type of the symbol where the first PDSCH is located in a single DCI scheduling multiple PDSCH opportunities as a valid symbol type;

[0375] A symbol type different from the symbol type of the symbol where the first PDSCH in an opportunity of scheduling multiple PDSCHs by a single DCI is located is determined as an invalid symbol type.

[0376] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0377] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0378] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0379] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0380] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0381] Optionally, determining HARQ-ACK feedback includes at least one of the following:

[0382] Determine a HARQ-ACK information bit by performing an AND operation on the binary value of the HARQ-ACK information bit at the PDSCH opportunity;

[0383] Determine a group of HARQ-ACK information bits for a single DCI scheduled PDSCH opportunity, and determine one HARQ-ACK information bit through an AND operation based on the binary values ​​of the HARQ-ACK information bits for the group of PDSCH opportunities.

[0384] Optionally, the apparatus further comprises: generating an ACK value for a PDSCH opportunity that only includes overlaps and / or partial overlaps with invalid symbols.

[0385] The processing device provided in the embodiment of the present application has similar implementation principles and beneficial effects to the technical solutions shown in the above-mentioned corresponding method embodiments, and will not be described in detail here.

[0386] Seventh embodiment

[0387] Please refer to FIG. 9 , which is a second structural diagram of a processing device provided in an embodiment of the present application. The device may be mounted on or be the network device in the above method embodiment. As shown in FIG. 9 , the device 170 includes:

[0388] The receiving module 1701 is used to receive HARQ-ACK feedback, where the HARQ-ACK feedback is determined by the terminal device based on the symbol type of the symbol where the PDSCH opportunity is located.

[0389] Optionally, the device further comprises at least one of the following:

[0390] The PDSCH opportunity is at least one group;

[0391] A set of PDSCH opportunities is determined by time-domain hybrid automatic repeat request-bundling type 1;

[0392] HARQ-ACK feedback is type 1 HARQ-ACK feedback for a single DCI scheduling multiple PDSCH opportunities;

[0393] The symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

[0394] Optionally, the device further comprises at least one of the following:

[0395] Invalid symbol types include SBFD symbols or non-SBFD symbols;

[0396] Valid symbol types include SBFD symbol or non-SBFD symbol;

[0397] Determine the symbol type of the symbol where the first PDSCH is located in a single DCI scheduling multiple PDSCH opportunities as a valid symbol type;

[0398] A symbol type different from the symbol type of the symbol where the first PDSCH in an opportunity of scheduling multiple PDSCHs by a single DCI is located is determined as an invalid symbol type.

[0399] Optionally, the PDSCH opportunity satisfies at least one of the following:

[0400] The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols;

[0401] A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols;

[0402] The symbols where a group of PDSCH opportunities are located do not overlap or partially do not overlap with the invalid symbol type;

[0403] A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

[0404] Optionally, the terminal device determines HARQ-ACK feedback, including at least one of the following:

[0405] The terminal device determines a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity;

[0406] The terminal device determines a group of HARQ-ACK information bits of PDSCH opportunities scheduled by a single DCI, and determines a HARQ-ACK information bit according to the binary AND operation of the HARQ-ACK information bits of the group of PDSCH opportunities.

[0407] Optionally, the apparatus further comprises: for a PDSCH opportunity that only includes overlap and / or partial overlap with invalid symbols, the terminal device generates an ACK value.

[0408] The processing device provided in the embodiment of the present application has similar implementation principles and beneficial effects to the technical solutions shown in the above-mentioned corresponding method embodiments, and will not be described in detail here.

[0409] FIG10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in FIG10 , the communication device 180 described in this embodiment can be the terminal device (or a component that can be used for a terminal device) or the network device (or a component that can be used for a network device) mentioned in the aforementioned method embodiment. The communication device 180 can be used to implement the methods corresponding to the terminal device or network device described in the aforementioned method embodiment. For details, please refer to the description of the aforementioned method embodiment.

[0410] The communication device 180 may include one or more processors 1801, also referred to as processing units, which may implement certain control or processing functions. Processor 1801 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, while the central processing unit may be used to control the communication device, execute software programs, and process software program data.

[0411] Optionally, the processor 1801 may also store instructions 1803 or data (eg, intermediate data). Optionally, the instructions 1803 may be executed by the processor 1801, so that the communication device 180 executes the method corresponding to the terminal device or network device described in the above method embodiment.

[0412] Optionally, the communication device 180 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments.

[0413] Optionally, the communication device 180 may include one or more memories 1802 , on which instructions 1804 may be stored. The instructions may be executed on the processor 1801 , so that the communication device 180 performs the method described in the above method embodiment.

[0414] Optionally, data may also be stored in the memory 1802. The processor 1801 and the memory 1802 may be provided separately or integrated together.

[0415] Optionally, the communication device 180 may further include a transceiver 1805 and / or an antenna 1806. The processor 1801 may be referred to as a processing unit, and controls the communication device 180 (terminal device, core network device, or wireless access network device). The transceiver 1805 may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, and is used to implement the transceiver functions of the communication device 180.

[0416] Optionally, if the communication device 180 is used to implement operations corresponding to the terminal device in the above embodiments, for example, the transceiver 1805 can send HARQ-ACK feedback.

[0417] Optionally, the specific implementation process of the processor 1801 and the transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0418] Optionally, if the communication device 180 is used to implement operations corresponding to the network devices in the above embodiments, for example, the transceiver 1805 may receive HARQ-ACK feedback.

[0419] Optionally, the specific implementation process of the processor 1801 and the transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0420] The processor 1801 and transceiver 1805 described in this application can be implemented on an IC (Integrated Circuit), an analog integrated circuit, an RFIC (Radio Frequency Integrated Circuit), a mixed-signal integrated circuit, an ASIC (Application Specific Integrated Circuit), a PCB (Printed Circuit Board), an electronic device, etc. The processor 1801 and transceiver 1805 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N Metal-Oxide-Semiconductor), PMOS (Positive Channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0421] In this application, a communication device may be a terminal device (such as a mobile phone) or a network device (such as a base station), and the specific definition needs to be determined based on the context. In addition, the terminal device can be implemented in various forms. For example, the terminal devices described in this application may include mobile terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0422] Although the communication device is described above by taking a terminal device or a network device as an example, the scope of the communication device described in this application is not limited to the above-mentioned terminal device or network device, and the structure of the communication device may not be limited to Figure 10. The communication device may be an independent device or may be part of a larger device.

[0423] An embodiment of the present application further provides a communication system, including: a terminal device as in any of the above embodiments; and a network device as in any of the above embodiments.

[0424] An embodiment of the present application also provides a communication device, including a memory and a processor, wherein a processing program is stored in the memory, and when the processing program is executed by the processor, the steps of the processing method in any of the above embodiments are implemented.

[0425] The communication device in this application can be a terminal device (such as a mobile phone), a network device (such as a satellite), or a chip (such as an SOC or a baseband chip with communication functions, etc.). The specific reference needs to be clarified based on the context.

[0426] An embodiment of the present application further provides a computer-readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, the steps of the processing method in any of the above embodiments are implemented.

[0427] In the embodiments of the communication device and storage medium provided in the embodiments of the present application, all technical features of any of the above-mentioned processing method embodiments may be included. The expanded and explained contents of the specification are basically the same as those of the embodiments of the above-mentioned methods and will not be repeated here.

[0428] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer executes the methods in the various possible implementation modes described above.

[0429] An embodiment of the present application also provides a chip, including a memory and a processor, wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that a device equipped with the chip executes the methods in the various possible implementation modes as described above.

[0430] It is understood that the above scenarios are merely examples and do not limit the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, those skilled in the art will appreciate that with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems.

[0431] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0432] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0433] The units in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0434] In this application, the same or similar terminology, technical solutions and / or application scenario descriptions are generally only described in detail the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, for the same or similar terminology, technical solutions and / or application scenario descriptions that are not described in detail later, you can refer to the previous relevant detailed descriptions.

[0435] In this application, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0436] The various technical features of the technical solution of this application can be combined arbitrarily. In order to make the description concise, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0437] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the method of each embodiment of the present application.

[0438] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)).

[0439] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the description and drawings of this application, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A processing method, wherein: Applied to terminal equipment, including the steps of: S1: Determine HARQ-ACK feedback based on the symbol type of the symbol where the PDSCH opportunity is located.

2. The method according to claim 1, wherein: Also includes at least one of the following: The PDSCH opportunity is at least one group; A set of PDSCH opportunities is determined by time domain hybrid automatic repeat request-bundling type 1; HARQ-ACK feedback is type 1 HARQ-ACK feedback for single DCI scheduling of multiple PDSCH opportunities; The symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

3. The method according to claim 2, wherein: Also includes at least one of the following: Invalid symbol types include SBFD symbols or non-SBFD symbols; Valid symbol types include SBFD symbol or non-SBFD symbol; Determine the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located as a valid symbol type; Determine a symbol type different from the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located as an invalid symbol type; The PDSCH timing meets at least one of the following conditions: The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols; A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols; A group of symbols where PDSCH opportunities are located do not overlap or partially do not overlap with invalid symbol types; A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

4. The method according to claim 1, wherein: Determine HARQ-ACK feedback, including at least one of the following: Determine a HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bit of the PDSCH opportunity; Determine a group of HARQ-ACK information bits of a PDSCH opportunity scheduled by a single DCI, and determine one HARQ-ACK information bit through an AND operation according to the binary of the HARQ-ACK information bits of a group of PDSCH opportunities.

5. The method according to claim 4, wherein: Also includes: For PDSCH opportunities that only contain overlaps and / or partial overlaps with invalid symbols, an ACK value is generated.

6. A processing method, wherein: Applied to network equipment, including the steps of: S2: Receive HARQ-ACK feedback, which is determined by the terminal device based on the symbol type of the symbol where the PDSCH opportunity is located.

7. The method according to claim 6, wherein: Also includes at least one of the following: The PDSCH opportunity is at least one group; A set of PDSCH opportunities is determined by time domain hybrid automatic repeat request-bundling type 1; HARQ-ACK feedback is type 1 HARQ-ACK feedback for single DCI scheduling of multiple PDSCH opportunities; The symbol type of the symbol where the PDSCH opportunity is located includes at least one of an uplink symbol, a flexible symbol, a downlink symbol, a valid symbol, and an invalid symbol.

8. The method according to claim 7, wherein: Also includes at least one of the following: Invalid symbol types include SBFD symbols or non-SBFD symbols; Valid symbol types include SBFD symbol or non-SBFD symbol; Determine the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located as a valid symbol type; Determine a symbol type different from the symbol type of the symbol where the first PDSCH in a single DCI scheduling multiple PDSCH opportunities is located as an invalid symbol type; The PDSCH timing meets at least one of the following conditions: The symbols where a group of PDSCH opportunities are located do not overlap with uplink symbols; A group of symbols where PDSCH opportunities are located overlaps with downlink symbols and / or flexible symbols; A group of symbols where PDSCH opportunities are located do not overlap or partially do not overlap with invalid symbol types; A group of PDSCH opportunities are located on symbols that overlap with valid symbol types.

9. The method according to claim 6, wherein: The terminal device determines HARQ-ACK feedback, including at least one of the following: The terminal device determines a HARQ-ACK information bit through an AND operation according to the binary of the HARQ-ACK information bit of the PDSCH opportunity; The terminal device determines a group of HARQ-ACK information bits of PDSCH opportunities scheduled by a single DCI, and the terminal device determines one HARQ-ACK information bit through an AND operation based on the binary of the HARQ-ACK information bits of the group of PDSCH opportunities.

10. The method according to claim 9, wherein: Also includes: For PDSCH opportunities that only contain overlaps and / or partial overlaps with invalid symbols, the terminal device generates an ACK value.

11. A communication device, wherein: include: A memory and a processor, wherein a processing program is stored in the memory, and when the processing program is executed by the processor, the processing method according to claim 1 or 6 is implemented.

12. A computer-readable storage medium, wherein: The computer-readable storage medium stores a processing program, and when the processing program is executed by a processor, the processing method according to claim 1 or 6 is implemented.

Images