WO2023035251A1 - Wireless communication method and communication device - Google Patents

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first device receiving first control information, wherein the first control information corresponds to a plurality of configured SLIVs, the plurality of configured SLIVs comprise an invalid SLIV, and the invalid SLIV corresponds to an HARQ process number and/or HARQ-ACK information, or, the invalid SLIV does not correspond to the HARQ process number and/or the HARQ-ACK information. The embodiments of the present application clarify a processing mode of the invalid SLIV, thereby preventing disorderly communication caused due to two parties, which are in communication with each other, having an inconsistent understanding of the processing mode of the invalid SLIV.

Description

Method and communication device for wireless communication technical field

The present application relates to the technical field of communication, and more specifically, to a wireless communication method and a communication device.

Background technique

Certain communication systems support scheduling of multiple physical channels with one control message. In this scenario, one control message usually corresponds to multiple start length indicators (start&length indicator, SLIV). The multiple SLIVs may contain invalid SLIVs.

If multiple SLIVs corresponding to a certain control information contain invalid SLIVs, how to deal with the invalid SLIVs is currently no suitable solution. If the two communicating parties have different understandings on how to deal with invalid SLIVs, it may lead to communication confusion.

Contents of the invention

The present application provides a wireless communication method and communication equipment, so as to avoid communication confusion between the two communicating parties.

In a first aspect, a wireless communication method is provided, including: a first device receives first control information, the first control information corresponds to multiple configuration SLIVs, and the multiple configuration SLIVs include invalid SLIVs; wherein the invalid SLIV corresponds to hybrid automatic repeat request (hybrid automatic repeat reQuest, HARQ) process number and/or hybrid automatic repeat request-acknowledgment (hybrid automatic repeat request-acknowledgement, HARQ-ACK) information; or, the invalid SLIV does not correspond to HARQ Process number and/or HARQ-ACK information.

In a second aspect, a wireless communication method is provided, including: the second device sends first control information, the first control information corresponds to multiple configuration SLIVs, and the multiple configuration SLIVs include invalid SLIVs; wherein the invalid The SLIV corresponds to the HARQ process number and/or the HARQ-ACK information; or, the invalid SLIV does not correspond to the HARQ process number and/or the HARQ-ACK information.

In a third aspect, a communication device is provided, the communication device is a first device, and the first device includes: a receiving module, configured to receive first control information, where the first control information corresponds to multiple configuration SLIVs, so The multiple configured SLIVs include invalid SLIVs; wherein, the invalid SLIVs correspond to HARQ process numbers and/or HARQ-ACK information; or, the invalid SLIVs do not correspond to HARQ process numbers and/or HARQ-ACK information.

In a fourth aspect, a communication device is provided, the communication device is a second device, and the second device includes: a sending module, configured to send first control information, the first control information corresponds to a plurality of configuration SLIVs, and the The multiple configured SLIVs include invalid SLIVs; wherein, the invalid SLIVs correspond to HARQ process numbers and/or HARQ-ACK information; or, the invalid SLIVs do not correspond to HARQ process numbers and/or HARQ-ACK information.

In a fifth aspect, there is provided a communication device, including a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in the first aspect or the second aspect method.

In a sixth aspect, an apparatus is provided, including a processor, configured to call a program from a memory, so as to execute the method as described in the first aspect or the second aspect.

In a seventh aspect, a chip is provided, including a processor, configured to call a program from a memory, so that a device installed with the chip executes the method described in the first aspect or the second aspect.

In an eighth aspect, a computer-readable storage medium is provided, on which a program is stored, and the program causes a computer to execute the method described in the first aspect or the second aspect.

In a ninth aspect, a computer program product is provided, including a program, the program causes a computer to execute the method described in the first aspect or the second aspect.

In a tenth aspect, a computer program is provided, the computer program causes a computer to execute the method described in the first aspect or the second aspect.

In this embodiment of the present application, the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information; or, the invalid SLIV does not correspond to the HARQ process number and/or the HARQ-ACK information. It can be seen that the embodiment of the present application clarifies the processing method of the invalid SLIV, thereby avoiding the communication confusion caused by the inconsistency of understanding of the processing method of the invalid SLIV by the communicating parties.

Description of drawings

1A-1C are exemplary diagrams of a communication system to which the embodiments of the present application can be applied.

Fig. 2 is an example diagram of one DCI scheduling multiple SLIVs.

FIG. 3 is an example diagram of invalid SLIVs among multiple SLIVs scheduled by a DCI.

Fig. 4 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

Fig. 5 is an example diagram of a possible processing manner of an invalid SLIV provided by an embodiment of the present application.

Fig. 6 is an example diagram of a processing manner of an invalid SLIV provided by another embodiment of the present application.

FIG. 7 is an example diagram of a scheduling sequence of physical channels corresponding to DCI and SLIV according to an embodiment of the present application.

Fig. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.

Fig. 9 is a schematic structural diagram of a communication device provided by another embodiment of the present application.

Fig. 10 is a schematic structural diagram of the device provided by the embodiment of the present application.

Detailed ways

The technical solution of the embodiment of the present application can be applied to various communication systems, such as: global system of mobile communication (global system of mobile communication, GSM) system, code division multiple access (code division multiple access, CDMA) system, broadband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (GPRS), long term evolution (long term evolution, LTE) system, advanced long term evolution (advanced long term evolution, LTE-A) system , new radio (new radio, NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum unlicensed spectrum (NR-U) system, NTN system, universal mobile telecommunications system (UMTS), wireless local area network (wireless local area networks, WLAN), wireless fidelity (wireless fidelity, WiFi), fifth generation communication (5th-generation, 5G) system or other communication systems, such as future communication systems, such as the sixth-generation mobile communication system, and satellite communication systems.

Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, device to device (device to device, D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. , the embodiments of the present application may also be applied to these communication systems.

The communication system in the embodiment of the present application may be applied to a carrier aggregation (carrier aggregation, CA) scenario, may also be applied to a dual connectivity (dual connectivity, DC) scenario, and may also be applied to an independent (standalone, SA) network deployment scenario.

The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to a licensed spectrum, wherein the licensed spectrum can also be Considered a dedicated spectrum.

The embodiments of the present application may be applied to an NTN system, and may also be applied to a terrestrial communication network (terrestrial networks, TN) system. By way of example and not limitation, the NTN system includes an NR-based NTN system and an IoT-based NTN system.

Embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment may also be called user equipment (user equipment, UE), access terminal, user unit, user station, mobile station, mobile station (mobile station, MS), mobile terminal (mobile Terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

In the embodiment of the present application, the terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) stations, personal digital assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as NR networks The terminal equipment in the network, or the terminal equipment in the public land mobile network (public land mobile network, PLMN) network that will evolve in the future, etc.

In this embodiment of the application, a terminal device can be a device that provides voice and/or data connectivity to users, and can be used to connect people, things and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, and the like. The terminal device in the embodiment of the present application can be mobile phone (mobile phone), tablet computer (Pad), notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc. Optionally, UE can be used to act as a base station. For example, a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cell phone and an automobile communicate with each other using sidelink signals. Communication between cellular phones and smart home devices without relaying communication signals through base stations.

In the embodiment of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) superior).

In the embodiment of the present application, the terminal device may be a mobile phone, a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home. The terminal equipment involved in the embodiments of the present application may also be referred to as terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station , remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE agent or UE device, etc. Terminal equipment can also be fixed or mobile.

As an example but not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

The network device in this embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be called an access network device or a wireless access network device, for example, the network device may be a base station. The network device in this embodiment of the present application may refer to a radio access network (radio access network, RAN) node (or device) that connects a terminal device to a wireless network. The base station can broadly cover various names in the following, or replace with the following names, such as: Node B (NodeB), evolved base station (evolved NodeB, eNB), next generation base station (next generation NodeB, gNB), relay station, Access point, transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), primary station MeNB, secondary station SeNB, multi-standard wireless (MSR) node, home base station, network controller, access node , wireless node, access point (access point, AP), transmission node, transceiver node, base band unit (base band unit, BBU), remote radio unit (remote radio unit, RRU), active antenna unit (active antenna unit) , AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning nodes, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, a modem or a chip configured in the aforementioned equipment or device. The base station can also be a mobile switching center, a device that undertakes the function of a base station in D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication, and a device in a 6G network. Network-side equipment, equipment that assumes base station functions in future communication systems, etc. Base stations can support networks of the same or different access technologies. The embodiment of the present application does not limit the specific technology and specific device form adopted by the network device.

Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or drone may be configured to serve as a device in communication with another base station.

In some deployments, the network device in this embodiment of the present application may refer to a CU or a DU, or, the network device includes a CU and a DU. A gNB may also include an AAU.

Network equipment and terminal equipment can be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the air. In the embodiment of the present application, the scenarios where the network device and the terminal device are located are not limited.

As an example but not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. For example, the satellite can be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geosynchronous earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite. ) Satellite etc. In some embodiments of the present application, the network device may also be a base station installed on land, in water, and other locations.

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

Exemplarily, FIG. 1A is a schematic structural diagram of a communication system provided by an embodiment of the present application. As shown in FIG. 1A , a communication system 100 may include a network device 110, and the network device 110 may be a device for communicating with a terminal device 120 (or called a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area, and can communicate with terminal devices located in the coverage area.

FIG. 1A exemplarily shows one network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within the coverage area. The device is not limited in the embodiment of this application.

Exemplarily, FIG. 1B is a schematic structural diagram of another communication system provided by an embodiment of the present application. Referring to FIG. 1B , a terminal device 1101 and a satellite 1102 are included, and wireless communication can be performed between the terminal device 1101 and the satellite 1102 . The network formed between the terminal device 1101 and the satellite 1102 may also be referred to as NTN. In the architecture of the communication system shown in FIG. 1B , the satellite 1102 may function as a base station, and the terminal device 1101 and the satellite 1102 may communicate directly. Under the system architecture, the satellite 1102 can be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 1102, and the coverage of each network device 1102 may include other numbers of terminal devices, which is not limited in this embodiment of the present application.

Exemplarily, FIG. 1C is a schematic structural diagram of another communication system provided by an embodiment of the present application. Referring to FIG. 1C , it includes a terminal device 1201 , a satellite 1202 and a base station 1203 , wireless communication can be performed between the terminal device 1201 and the satellite 1202 , and communication can be performed between the satellite 1202 and the base station 1203 . The network formed among the terminal equipment 1201, the satellite 1202 and the base station 1203 may also be referred to as NTN. In the architecture of the communication system shown in FIG. 1C , the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be relayed through the satellite 1202 . Under this system architecture, the base station 1203 may be called a network device. In some embodiments of the present application, the communication system may include multiple network devices 1203, and the coverage of each network device 1203 may include other numbers of terminal devices, which is not limited in this embodiment of the present application.

It should be noted that Fig. 1A-Fig. 1C are only illustrations of the systems to which this application is applicable. Of course, the methods shown in the embodiments of this application can also be applied to other systems, for example, 5G communication systems, LTE communication systems, etc. , which is not specifically limited in this embodiment of the present application.

In some embodiments of the present application, the wireless communication system shown in FIG. 1A-FIG. 1C may further include a mobility management entity (mobility management entity, MME), an access and mobility management function (access and mobility management function, AMF) and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1A as an example, the communication equipment may include a network equipment 110 and a terminal equipment 120 with communication functions, and the network equipment 110 and the terminal equipment 120 may be the specific equipment described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.

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

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.

The "configuration" in the embodiment of the present application may include configuring through at least one of system messages, radio resource control (radio resource control, RRC) signaling, and media access control element (MAC CE) .

The "semi-static parameter" in this embodiment of the present application may include at least one of system information, radio resource control (radio resource control, RRC) signaling, and media access control element (media access control control element, MAC CE).

In some embodiments of the present application, "predefined" or "preset" may be pre-saved in devices (for example, including terminal devices and network devices) with corresponding codes, tables or other methods that can be used to indicate related information implementation, and the present application does not limit the specific implementation manner. For example, the predefined ones may refer to those defined in the protocol.

In some embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include the LTE protocol, the NR protocol, and related protocols applied to future communication systems, which is not limited in the present application.

For ease of understanding, some relevant technical knowledge involved in the embodiments of the present application is introduced first. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them belong to the protection scope of the embodiments of the present application. The embodiment of the present application includes at least part of the following contents.

high frequency system

With the evolution of communication systems, new frequency bands with higher frequencies may be introduced in some communication systems. For example, the NR system may include the following frequency bands: 52.6GHz-71GHz or 71GHz-114.25GHz.

The new frequency band may include licensed spectrum or unlicensed spectrum. Alternatively, the new frequency bands may include dedicated spectrum as well as shared spectrum.

The unlicensed spectrum is a kind of spectrum allocated by the country and region that can be used for radio equipment communication. Unlicensed spectrum is generally considered to be shared. That is to say, as long as communication equipment in different communication systems meets the regulatory requirements set by the country or region on the unlicensed spectrum, it can use the unlicensed spectrum without applying for a dedicated spectrum authorization from the government.

In order to enable various communication devices that use unlicensed spectrum for wireless communication to coexist friendly on the unlicensed spectrum, some countries or regions stipulate principles or regulatory requirements that must be met when using unlicensed spectrum. For example, on unlicensed spectrum, communication devices need to follow the principle of "listen before talk (LBT)". For example, a communication device needs to perform a channel access process first. After accessing the channel of the unlicensed spectrum, if the communication device wishes to transmit signals on the channel, it needs to perform channel monitoring or channel sensing (channel sensing) first. Only when the channel monitoring is successful, the communication device can send signals on the channel. If the communication device fails to monitor the channel on the channel, the communication device cannot perform signal transmission.

Channel listening success is also referred to as LBT success or channel listening idle. For example, in the monitoring time slot for monitoring the channel, if the detected signal energy is lower than the energy detection threshold, it indicates that the channel monitoring is successful.

Channel listening failure is also known as LBT failure or channel listening busy. For example, in the monitoring time slot for monitoring the channel, if the detected signal energy is higher than or equal to the energy detection threshold, it indicates that the channel monitoring fails.

The subcarrier spacing of the new frequency band can be larger than the subcarrier spacing currently supported by the communication system (such as the NR system). For example, the candidate subcarrier intervals currently being considered for introduction in the new frequency band include at least one of the following subcarrier intervals: 240 kHz, 480 kHz, 960 kHz, 1.92 MHz, and 3.84 MHz. Different subcarrier intervals may correspond to different numerology. For example, one or more of the following parameters corresponding to different subcarriers may be different: symbol length, normal cyclic prefix (normal cyclic prefix, NCP) length, symbol band NCP length, and time slot length. As an example, the parameter sets (numerology) corresponding to some candidate subcarrier spacings are shown in Table 1 below.

Table 1: Parameter sets corresponding to candidate subcarrier spacing

subcarrier spacing	symbol length	NCP length	Symbol with NCP length	slot length
240kHz	4.16μs	0.292μs	4.452μs	62.5μs
480kHz	2.08μs	0.146μs	2.226μs	31.25μs
960kHz	1.04μs	0.073μs	1.113μs	15.625μs

codebook feedback

For a terminal device with downlink services, the network device can schedule transmission of a physical downlink shared channel (PDSCH) for the terminal device through downlink control information (DCI).

After the terminal device receives the PDSCH, the terminal device may perform hybrid automatic repeat request-acknowledgment (HARQ) feedback on the decoding result of the PDSCH. For example, the terminal device may feed back the decoding result of the PDSCH to the network device through a physical uplink control channel (physical uplink control channel, PUCCH) resource based on the HARQ feedback timing. The decoding result may also be referred to as HARQ-ACK information. The HARQ-ACK information may include, for example, acknowledgment (acknowledgment, ACK) information and negative acknowledgment (negative acknowledgment, NACK) information. HARQ-ACK information may also sometimes be referred to as feedback bits.

Certain communication systems (such as NR systems) support dynamic determination of HARQ feedback timing. For example, the network device can schedule the terminal device to receive the PDSCH through the DCI. The DCI may include indication information of the PUCCH resource used to transmit the HARQ-ACK information corresponding to the PDSCH.

The PUCCH resource indication information may include a PUCCH resource indication (PUCCH resource indicator) and a HARQ feedback timing indication (PDSCH-to-HARQ_feedback timing indicator).

The PUCCH resource indication can be used to determine the PUCCH resource for transmitting the HARQ-ACK information corresponding to the PDSCH, such as determining the frequency domain and/or code domain position of the PUCCH resource. The HARQ feedback timing indication information can be used to dynamically determine the time-domain position (such as the time slot of the HARQ feedback resource) of the HARQ feedback resource (such as the PUCCH resource). The HARQ feedback resource indication information is usually represented by K ₁ . K ₁ may indicate a time slot offset value between a PDSCH and a PUCCH or a physical uplink shared channel (physical uplink shared channel, PUSCH) carrying HARQ-ACK information corresponding to the PDSCH.

The HARQ feedback timing indication information may be used to indicate the value in the HARQ feedback timing set. The HARQ feedback timing set may be a preset HARQ feedback timing set (such as predefined by the protocol), or a HARQ feedback timing set configured by the network device. The HARQ feedback timing set may include at least one K ₁ value.

If the HARQ feedback timing set includes only one K ₁ value, the DCI may not include the HARQ feedback timing indication. In this case, the time domain position of the HARQ feedback resource can be determined according to the K ₁ value in the HARQ feedback timing set.

As an example, the HARQ feedback timing set may be a preset HARQ feedback timing set. The values in the preset HARQ feedback timing set are all preset values. The preset HARQ feedback timing set may include 8 preset values {1, 2, 3, 4, 5, 6, 7, 8}. The HARQ feedback timing indication information in the DCI may include 3 bits, and the 3-bit indication information is mapped to the 8 preset values one by one. For example, when the HARQ feedback timing indication information is 000, it means K ₁ =1; when the HARQ feedback timing indication information is 001, it means K ₁ =2, and so on. Optionally, if the HARQ feedback timing set is a preset HARQ feedback timing set, the DCI format corresponding to the DCI may be a fallback DCI format. For example, the DCI format corresponding to the DCI may be DCI format 1_0.

As another example, the HARQ feedback timing set may be the HARQ feedback timing set configured by the network device. For the HARQ feedback timing set configured by the network device, the number of bits included in the HARQ feedback timing indication information in the DCI may be determined according to the number of values included in the HARQ feedback timing set. As an example, the HARQ feedback timing set configured by the network device may include 4 values. Correspondingly, the HARQ feedback timing indication information in the DCI may include 2 bits. For example, when the HARQ feedback timing indication information is 00, it may indicate the first value in the HARQ feedback timing set; when the HARQ feedback timing indication information is 01, it may indicate the second value in the HARQ feedback timing set, etc. wait. The HARQ feedback timing set configured by the network device may sometimes include invalid K ₁ . For example, the HARQ feedback timing set configured by the network device includes a K ₁ value of -1. When the HARQ feedback timing indication information in the DCI indicates the invalid K ₁ , it may indicate that the time slot where the PUCCH resource is located is temporarily uncertain. Optionally, if the HARQ feedback timing set is the HARQ feedback timing set configured by the network device, the DCI format corresponding to the DCI may be a non-fallback DCI format. For example, the DCI format corresponding to the DCI may be DCI format 1_1 or DCI format 1_2.

Some communication systems (such as NR systems) support HARQ feedback based on the HARQ-ACK codebook. The HARQ-ACK codebook can be a semi-static codebook or a dynamic codebook. In other words, the terminal device can perform HARQ feedback based on a semi-static codebook, or perform HARQ feedback based on a dynamic codebook. The semi-static codebook may include, for example, a Type-1 HARQ-ACK codebook and/or a Type-3 HARQ-ACK codebook. The dynamic codebook may include, for example, a Type-2 HARQ-ACK codebook and/or an eType-2 HARQ-ACK codebook.

Take the Type-1 HARQ-ACK codebook as an example. If the terminal device is configured with a Type-1 HARQ-ACK codebook, the Type-1 HARQ-ACK codebook can include a set of candidate PDSCH receivers corresponding to a feedback time unit (such as a feedback time slot). ACK information. The number of bits included in the Type-1 HARQ-ACK codebook may be fixed.

Take the Type-3 HARQ-ACK codebook as an example. If the terminal device is configured with a Type-3 HARQ-ACK codebook, the Type-3 HARQ-ACK codebook may include HARQ-ACK information corresponding to all HARQ processes on all configured carriers in a PUCCH group. The number of bits included in the Type-3 HARQ-ACK codebook may be fixed. In some cases, the Type-3 HARQ-ACK codebook can also be called one-shot HARQ-ACK codebook. The Type-3 HARQ-ACK codebook can include two types of HARQ-ACK codebooks. One type of HARQ-ACK codebook is a one-shot HARQ-ACK codebook carrying a new data indicator (NDI). Another type of HARQ-ACK codebook is a one-shot HARQ-ACK codebook that does not carry NDI. The network device can configure whether the terminal device needs to carry NDI when performing HARQ-ACK feedback through radio resource control (radio resource control, RRC) signaling. In addition, for a cell configured with code block group (CBG) transmission and CBG feedback in the PUCCH group, the Type-3 HARQ-ACK codebook can include HARQ-ACK information corresponding to each HARQ process in the cell . The number of bits occupied by the HARQ-ACK information may be determined according to the length of the CBG corresponding to the cell, or the number of bits occupied by the HARQ-ACK information may be determined according to the length of the transport block (transport block, TB) corresponding to the cell.

Take Type-2 or eType-2 HARQ-ACK codebook as an example. If the terminal device is configured with a Type-2 or eType-2 HARQ-ACK codebook, the order and number of bits included in the Type-2 or eType-2 HARQ-ACK codebook can be assigned according to the downlink index in DCI (downlink assignment index, DAI) count (counter DAI or C-DAI) information and/or total DAI (total DAI or T-DAI) information is determined. In other words, the number of bits included in the Type-2 or eType-2 HARQ-ACK codebook can be determined according to the indication information in the DCI. The difference between the Type-2 HARQ-ACK codebook and the eType-2 HARQ-ACK codebook is that the eType-2 HARQ-ACK codebook supports packet feedback on the basis of the Type-2 HARQ-ACK codebook. That is to say, for the HARQ feedback based on the eType-2 HARQ-ACK codebook, the network device can group the scheduled PDSCH. For example, the DCI (the format of the DCI may be, for example, DCI format 1_1) in which the network device schedules the terminal device to receive the PDSCH may include indication information of a PDSCH group index (PDSCH group index) and a new feedback indicator (new feedback indicator, NFI). Instructions. In some embodiments, a maximum of 2 packets may be supported. When the network device triggers the terminal device to perform HARQ feedback, it may trigger the terminal device to perform the HARQ feedback of one of the groups, and may also trigger the HARQ feedback of the two groups at the same time. For example, the DCI information may include an information field (Number of requested PDSCH group(s)) of the number of feedback request groups. If the terminal device receives the DCI sent by the network device, and the feedback request group number information field in the DCI is a preset value (the preset value may be 1, for example), then the terminal device can perform HARQ feedback of two groups or, if the terminal device receives the DCI sent by the network device, and the feedback request group number information field in the DCI is another preset value (the preset value can be 0, for example), then the terminal device can perform a group (such as the current scheduling group) HARQ-ACK feedback.

One DCI schedules multiple physical channels

In some communication systems, one DCI can schedule multiple physical channels (or multiple physical channel transmissions). The physical channel mentioned here may be PDSCH or PUSCH, for example. Therefore, one DCI scheduling multiple physical channels may also be referred to as one DCI scheduling multiple downlink transmissions, or one DCI scheduling multiple uplink transmissions. The embodiment of the present application does not specifically limit the type of a communication system that supports one DCI to schedule multiple physical channels. The following takes the high-frequency system mentioned above as an example to describe the manner in which one DCI schedules multiple physical channels.

As mentioned above, in the high-frequency system, sub-carriers with relatively large sub-carrier spacing are introduced. Since the interval between subcarriers is large, the time length occupied by each time slot is relatively short. In this case, if the physical channel scheduling method based on each time slot in the low-frequency system is used, the terminal device needs to detect a physical downlink control channel (physical downlink control channel, PDCCH) in each time slot. Since the time slots of the high-frequency system are relatively short, in order to detect the PDCCH in each time slot, the terminal equipment is required to have strong processing capability, which undoubtedly increases the cost of the terminal equipment. In order to reduce the processing capacity requirements of the terminal equipment, it may be considered to introduce a scheduling mode in which one DCI schedules multiple physical channels.

In order to support one DCI to schedule multiple physical channels, a row or some rows in the time domain resource assignment (TDRA) table may correspond to row indexes of multiple SLIVs. One SLIV can correspond to one physical channel (either PDSCH or PUSCH). For example, a SLIV may indicate the time-domain resource location of a physical channel. For example, a SLIV can be used to indicate the starting symbol and the number of occupied symbols of a physical channel.

If the row index indicated by the TDRA information in the DCI received by the terminal device is the row index corresponding to multiple SLIVs (or in other words, one DCI corresponds to multiple SLIVs), it means that the network device schedules the multiple SLIVs corresponding to the multiple SLIVs for the terminal device. transmission over a physical channel. Different physical channels can be used to transmit different TBs. In some special cases, different physical channels can also be used to transmit the same TB.

A specific example is given below in conjunction with Table 2 and FIG. 2 .

Table 2 shows a TDRA table configured by the network device for the terminal device (different SLIVs in Table 2 may correspond to different TBs). The values of the row index I in the TDRA table are 0 and 1. Row index 0 corresponds to a SLIV. If the TDRA information in the DCI received by the terminal device indicates row index 0, it means that the DCI schedules a physical channel. Row index 1 corresponds to 4 SLIVs. If the TDRA information in the DCI received by the terminal device indicates that the row index is 1, it means that the DCI schedules 4 physical channels.

Assuming that the TDRA information in the DCI received by the terminal device indicates row index 1 in Table 2, and the HARQ process number (HARQ process number, HPN) in the DCI indicates 2, then the terminal device can determine 4 according to the row index The time domain position of a physical channel (such as the start symbol and length of the time domain position). In addition, the terminal device can determine the HPNs corresponding to the 4 SLIVs according to HPN=2. For example, referring to Figure 2, the terminal device can determine that HPN=2 corresponding to SLIV 1-0, and the terminal device adds 1 to 2 in order to obtain the remaining SLIV 1-1, SLIV 1-2, and SLIV 1-3 The corresponding HPNs are 3,4,5 respectively. It should be noted that if the number of HARQ processes configured on the terminal device is 16, the value range of the corresponding HPN is 0 to 15. In this example, assuming that the HPN corresponding to SLIV 1-0=14, the HPNs corresponding to the remaining SLIV 1-1, SLIV 1-2, and SLIV 1-3 are 15, 0, 1 respectively, that is, when a certain SLIV corresponds to When the HPN reaches the maximum value, the value of the HPN corresponding to the subsequent SLIV can be recalculated from HPN=0 (of course, if the initial HPN is 1, it can be recalculated from HPN=1).

Table 2: TDRA form

row index I	SLIV configuration
0	SLIV 0-0
1	SLIV 1-0; SLIV 1-1; SLIV 1-2; SLIV 1-3

It should be noted that, the above only uses a high-frequency system as an example to illustrate the manner in which one DCI schedules multiple physical channels. The embodiment of the present application can be applied to any scenario where one DCI is used to schedule multiple physical channels, and is not limited to the high-frequency system mentioned above.

In the case that one DCI schedules multiple physical channels, one DCI can correspond to multiple SLIVs. The multiple SLIVs sometimes contain invalid SLIVs. See Figure 3, one DCI corresponds to 4 SLIVs, namely SLIV 1-0, SLIV 1-1, SLIV 1-2, and SLIV 1-3. Among the 4 SLIVs, SLIV 1-0, SLIV 1-1, and SLIV 1-3 are valid SLIVs, and SLIV 1-2 are invalid SLIVs. If multiple SLIVs corresponding to one DCI contain an invalid SLIV, there is no suitable solution for how the terminal device should handle the invalid SLIV.

In addition, in addition to the communication scenario between the terminal device and the network device, the scenario where two terminal devices communicate through the side link may also have a control information (such as side link control information) to schedule multiple physical channels (such as multiple physical sidelinks). line shared channel). In this scenario, the plurality of SLIVs may also include an invalid SLIV. At this time, how the terminal device should handle the invalid SLIV is also a problem to be solved urgently.

In order to solve the above problem, the following describes the embodiment of the present application in detail with reference to FIG. 4 .

Fig. 4 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application. The method in FIG. 4 may be executed by the first device and the second device. Both the first device and the second device are communication devices or radio devices. In some embodiments, the first device and the second device may be a terminal device and a network device respectively. For example, the first device may be the terminal device 120 in FIG. 1 , and the second device may be the network device 110 in FIG. 1 . In other embodiments, the first device and the second device may be two devices communicating via a sidelink.

Referring to FIG. 4, in step S410, the first device receives first control information.

In some embodiments, the first control information may be DCI. In other embodiments, the first control information may be side traffic control information.

The first control information may schedule transmission of the first physical channel. The first physical channel may include one or more physical channels. When the first physical channel includes multiple physical channels, the transmission directions of the multiple physical channels may be the same or different. For example, the first physical channel may include one of the following physical channels: one or more downlink physical channels, one or more uplink physical channels, and one or more sidelink physical channels. The downlink physical channel may be PDSCH, for example. The uplink physical channel may be PUSCH, for example. The sidelink physical channel may be, for example, a physical sidelink shared channel (physical sidelink shared channel, PSSCH).

The first control information may correspond to multiple SLIVs (SLIVs mentioned in this embodiment of the application may also be referred to as configuration SLIVs). In other words, the first control information may contain information for determining the plurality of SLIVs. For example, the first control information may include TDRA information. The TDRA information indicates a row index in the TDRA table, and the row index is a row index corresponding to a plurality of SLIVs. For example, the row index may be row index 1 in table 2.

The first control information may correspond to the first control information format. The first device may be configured with the first control information format. Taking the first control information format as DCI format 1_1 as an example, the first control information may be DCI corresponding to DCI format 1_1.

The maximum number M of physical channels that can be scheduled by the first control information format may be greater than or equal to 2. Alternatively, the maximum number M of time slots that can be scheduled by the first control information format may be greater than or equal to 2. Correspondingly, the first physical channel scheduled by the first control information may include S physical channels. S can be greater than or equal to 1 and less than or equal to M. Each of the S physical channels may correspond to one SLIV.

In some embodiments, the first control information may correspond to the first HARQ-ACK codebook. The first HARQ-ACK codebook may correspond to the first feedback resource. In some embodiments, the first device may send the first HARQ-ACK codebook through the first feedback resource.

Optionally, for downlink transmission, the first feedback resources include physical uplink control channel (physical uplink control channel PUCCH) resources or PUSCH resources, or, the first HARQ-ACK codebook is transmitted through PUCCH or PUSCH.

Optionally, for uplink transmission, the first feedback resources include PDCCH resources, or the first HARQ-ACK codebook is transmitted through the PDCCH.

Optionally, for sidelink transmission, the first feedback resource includes a physical sidelink feedback channel (physical sidelink feedback channel, PSFCH) resource, or, the first HARQ-ACK codebook is transmitted through the PSFCH.

The multiple SLIVs corresponding to the first control information may include valid SLIVs and/or invalid SLIVs.

An active SLIV may correspond to a first physical channel transmission. For example, the first control information corresponds to S effective SLIVs, and the first physical channel includes S physical channels corresponding to the S effective SLIVs one-to-one.

The effective SLIV can be based on the transmission direction of the symbol corresponding to the SLIV (in some embodiments, the transmission direction of the uplink symbol is uplink or flexible, and/or, the transmission direction of the downlink symbol is downlink or flexible, and/or, the sidelink symbol The transmission direction of the symbol is flexible; in some embodiments, the transmission direction of the symbol can also be replaced by the direction of the symbol) to determine. For example, the valid SLIV may be one of the multiple SLIVs that satisfies the following condition: the transmission direction of symbols (part or all symbols) corresponding to the SLIV is the same as the transmission manner of the first physical channel. For example, assuming that the first physical channel is a downlink physical channel, if the transmission mode of all symbols corresponding to a certain SLIV among the multiple SLIVs is downlink, then the SLIV is an effective SLIV. For another example, assuming that the first physical channel is an uplink physical channel, if the transmission mode of all symbols corresponding to a certain SLIV among the multiple SLIVs is uplink, then the SLIV is an effective SLIV.

The invalid SLIV may include a SLIV that does not correspond to transmission on the first physical channel among the plurality of SLIVs. In some embodiments, the invalid SLIV is a SLIV except the last SLIV among the multiple SLIVs corresponding to a row of SLIVs. For example, an invalid SLIV may refer to an SLIV that satisfies at least one of the following conditions among the plurality of SLIVs: the transmission direction of at least one symbol corresponding to the SLIV (for example, part or all of the symbols corresponding to the SLIV) is the same as that of the first physical channel The transmission methods are different; part or all of the symbols corresponding to SLIV are symbols in the time-frequency resources used for rate matching; and/or, part or all of the frequency domain resources corresponding to SLIV are frequency domains in the time-frequency resources used for rate matching resource. It should be understood that in this embodiment of the present application, the time-frequency resources used for rate matching are not used for physical channel transmission. Invalid SLIVs can be determined in a variety of ways. For example, the manner of determining the invalid SLIV may include determining based on semi-static configuration parameters and/or determining based on dynamic scheduling parameters. An invalid SLIV determined based on semi-static configuration parameters may also be referred to as an invalid SLIV determined by a semi-static configuration. An invalid SLIV determined based on dynamic scheduling parameters may also be referred to as an SLIV determined by dynamic scheduling.

In some embodiments, the invalid SLIV determined based on the dynamic scheduling parameters may include: the transmission direction of at least one first symbol (for example, some or all symbols corresponding to the SLIV) corresponding to the SLIV and the transmission direction of the first physical channel different. In this embodiment, the transmission direction of the at least one first symbol may be determined based on a dynamic scheduling parameter. Taking the first control information as the first DCI as an example, the dynamic scheduling parameter may, for example, be transmitted through the first DCI, or may also be transmitted through the second DCI received by the first device in a DCI format of DCI format 2_0 of. Wherein, the time slot format indication information in DCI format 2_0 may be used to indicate the transmission direction of symbols.

Take the downlink transmission as an example for description. In downlink transmission, the first device is a terminal device, the second device is a network device, the first control information is the first DCI, and the TDRA information in the first DCI indicates multiple SLIVs in the TDRA table. If the terminal device receives the dynamic scheduling parameter of the network device, and determines according to the dynamic scheduling parameter that the transmission direction of at least one symbol corresponding to at least one SLIV in the plurality of SLIVs is uplink or flexible, then the terminal device determines that the at least one SLIV is Invalid SLIV determined based on dynamic scheduling parameters. For example, the dynamic scheduling parameter may be transmitted through the first DCI, or the dynamic scheduling parameter may also be transmitted through the second DCI whose DCI format is DCI format 2_0.

The uplink transmission is taken as an example for description. In uplink transmission, the first device is a terminal device, the second device is a network device, the first control information is the first DCI, and the TDRA information in the first DCI indicates multiple SLIVs in the TDRA table. If the terminal device receives the dynamic scheduling parameter of the network device, and the dynamic scheduling parameter indicates that the transmission direction of at least one symbol corresponding to at least one SLIV in the multiple SLIVs is downlink or flexible, then the terminal device determines that the at least one SLIV is based on Invalid SLIV as determined by dynamic dispatch parameters. For example, the dynamic scheduling parameter may be transmitted through the first DCI, or the dynamic scheduling parameter may also be transmitted through the second DCI whose DCI format is DCI format 2_0.

In some embodiments, the invalid SLIV determined based on the dynamic scheduling parameters may include: some or all symbols corresponding to the SLIV are symbols in the time-frequency resource used for rate matching.

In this embodiment, the time-frequency resource (or pattern of rate matching) for rate matching may be determined according to semi-static configuration parameters and/or dynamic scheduling parameters.

Optionally, the resource set corresponding to the rate-matched time-frequency resource is a resource set corresponding to a resource block (resource block, RB)-symbol, or in other words, the unit of the resource set in the time domain is one or more symbols, in A unit in the frequency domain is one or more RBs.

Optionally, the first device may be configured with a resource set corresponding to the time-frequency resource for rate matching by, for example, a semi-static parameter. This set of resources can be considered as time-frequency resources for rate matching. The corresponding resource element (resource element, RE) in the resource set is not used for physical channel such as PDSCH transmission.

Optionally, the first device may be configured with rate matching pattern set 1 or rate matching pattern set 2. When the control information received by the first device does not include rate matching indication information, the first device should assume that rate matching pattern group 1 or rate matching pattern group 2 is not used for physical channel transmission. That is, the rate matching pattern group 1 or the rate matching pattern group 2 can be regarded as time-frequency resources for rate matching. For example, when the received PDSCH is scheduled using DCI format 1_0, or is a semi-persistent scheduling (SPS) PDSCH activated using DCI format 1_0, or is scheduled for DCI format 1_1 (or DCI format 1_2) and the DCI format When the rate matching indication information is not included in 1_1 (or DCI format 1_2), the first device shall assume that rate matching pattern group 1 or rate matching pattern group 2 is not used for PDSCH transmission.

Optionally, when the control information received by the first device includes rate matching indication information, the first device determines whether rate matching pattern group 1 or rate matching pattern group 2 is used for physical channel transmission according to the rate matching indication information. That is, the rate matching indication information is used to dynamically indicate whether the configured rate matching pattern group 1 or rate matching pattern group 2 is used for physical channel transmission. For example, DCI format 1_1 or DCI format 1_2 includes rate matching indication information, and the rate matching indication information is used to dynamically indicate whether the configured rate matching pattern group 1 or rate matching pattern group 2 is used for PDSCH transmission. Assume that the rate matching indication information includes 2 bits, wherein the first bit corresponds to rate matching pattern group 1, and the second bit corresponds to rate matching pattern group 2. If the bit in the rate matching indication information is 1, it indicates the rate matching pattern corresponding to this bit The resources in the group are not used for PDSCH transmission. For resources in the resource set that do not belong to rate matching pattern group 1 and rate matching pattern group 2, when the received PDSCH is scheduled using DCI format 1_1 or DCI format 1_2, the first device shall assume that the resource is not used for PDSCH transmission .

In some embodiments, the invalid SLIV determined based on the dynamic scheduling parameters may include: some or all of the frequency domain resources corresponding to the SLIV are frequency domain resources within the time-frequency resources used for rate matching. The first control information may include frequency domain resource assignment (frequency domain resource assignment, FDRA) information, and the frequency domain resource corresponding to the SLIV may be determined according to the FDRA. For example, in combination with the FDRA information and TDRA information, one or more time-frequency resources (such as physical resource blocks (PRB)) corresponding to the SLIV can be determined, and then the frequency domain corresponding to the one or more time-frequency resources The resource can be understood as the frequency domain resource corresponding to the SLIV. In this embodiment, the dynamic scheduling parameter may be transmitted through the first control information (such as the first DCI), for example, the dynamic scheduling parameter includes TDRA information and FDRA information. The time-frequency resource (or pattern of rate matching) for rate matching may be semi-statically configured and/or dynamically indicated.

In some embodiments, the invalid SLIV determined based on the dynamic scheduling parameters may include: some or all of the time-frequency resources corresponding to the SLIV are time-frequency resources for rate matching. For example, the first device may be configured with time-frequency resources (or rate matching patterns) for rate matching, and the first device determines that time-domain resources and frequency-domain resources corresponding to one or more SLIVs among the multiple SLIVs are used for If there are resources in the rate-matched time-frequency resources (the rate-matching pattern), the first device determines that the one or more SLIVs are invalid SLIVs.

As an example, if all time-frequency resources corresponding to a SLIV are time-frequency resources for rate matching, the SLIV is an invalid SLIV. For example, according to the rate matching pattern, the first device determines that the time-frequency domain resources corresponding to a certain SLIV are time-frequency resources for rate matching (that is, according to the rate matching pattern, it is determined that the time-frequency domain resources corresponding to a certain SLIV are not used for data transmission), Then the first device may determine that the SLIV is an invalid SLIV determined based on the dynamic scheduling parameter. In this embodiment, the dynamic scheduling parameter may be transmitted through the first control information (such as the first DCI), for example, the dynamic scheduling parameter includes TDRA information and FDRA information. The time-frequency resource (or pattern of rate matching) for rate matching may be semi-statically configured and/or dynamically indicated.

Take the downlink transmission as an example for description. In downlink transmission, the first device is a terminal device, and the second device is a network device. The first control information is DCI, and the TDRA information in the DCI indicates multiple SLIVs in the TDRA table. The TDD pattern of the semi-static configuration of the network device received by the terminal device (for example, the TDD pattern configured by the high layer parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) indicates that at least one of the multiple SLIVs is in the SLIV The transmission direction of at least some symbols is flexible, the terminal device is configured to receive DCI format 2_0 and the terminal device has not received the transmission direction of symbols dynamically indicated by the network device (for example, the terminal device has not received DCI format 2_0), or, the terminal device receives If the received DCI format 2_0 indicates that the transmission direction of at least some symbols corresponding to the at least one SLIV is not downlink (for example, uplink or flexible), then the terminal device determines that the at least one SLIV is an invalid SLIV determined based on dynamic scheduling parameters.

The uplink transmission is taken as an example for description. In uplink transmission, the first device is a terminal device, and the second device is a network device. The first control information is DCI, and the TDRA information in the DCI indicates multiple SLIVs in the TDRA table. The TDD pattern of the semi-static configuration of the network device received by the terminal device (for example, the TDD pattern configured by the high layer parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) indicates that at least one of the multiple SLIVs is in the SLIV The transmission direction of at least some symbols is flexible, the terminal device is configured to receive DCI format 2_0 and the terminal device has not received the transmission direction of symbols dynamically indicated by the network device (for example, the terminal device has not received DCI format 2_0), or, the terminal device receives If the received DCI format 2_0 indicates that the transmission direction of at least some symbols corresponding to the at least one SLIV is not uplink (for example, downlink or flexible), then the terminal device determines that the at least one SLIV is an invalid SLIV determined based on dynamic scheduling parameters.

In some embodiments, the invalid SLIV determined based on the semi-static configuration parameters may include: the transmission direction of at least one second symbol corresponding to the invalid SLIV (for example, some or all symbols corresponding to the invalid SLIV) and the transmission direction of the first physical channel The direction is different. In this embodiment, the transmission direction of the at least one second symbol may be determined based on semi-static configuration parameters. In addition, in this embodiment, the semi-static configuration parameters may include, for example, a TDD pattern configured based on semi-static parameters.

Take the downlink transmission as an example for description. In downlink transmission, the first device is a terminal device, and the second device is a network device. The first control information is DCI, and the TDRA information in the DCI indicates multiple SLIVs in the TDRA table. The TDD pattern of the semi-static configuration of the network device received by the terminal device (for example, the TDD pattern configured by the high layer parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) indicates that at least one of the multiple SLIVs is in the SLIV If the transmission direction of at least part of the symbols is uplink, the terminal device determines that the at least one SLIV is an invalid SLIV determined based on semi-static configuration parameters.

The uplink transmission is taken as an example for description. In downlink transmission, the first device is a terminal device, and the second device is a network device. The first control information is DCI, and the TDRA information in the DCI indicates multiple SLIVs in the TDRA table. The TDD pattern of the semi-static configuration of the network device received by the terminal device (for example, the TDD pattern configured by the high layer parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) indicates that at least one of the multiple SLIVs is in the SLIV If the transmission direction of at least part of the symbols is downlink, the terminal device determines that the at least one SLIV is an invalid SLIV determined based on semi-static configuration parameters.

Referring again to FIG. 4, in step S420, the first device determines (or assumes) that the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information; or, the first device determines that the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information.

The HARQ process number corresponding to the first device may refer to the HARQ process number corresponding to the invalid SLIV determined by the first device. The fact that the first device does not correspond to the HARQ process ID may mean that the first device does not need to determine the HARQ process ID corresponding to the invalid SLIV.

The HARQ-ACK information corresponding to the first device may mean that the first device feeds back the HARQ-ACK information corresponding to the invalid SLIV. For example, the first HARQ-ACK codebook fed back by the first device includes the HARQ-ACK information corresponding to the invalid SLIV. In other words, the first HARQ-ACK codebook fed back by the first device includes the HARQ-ACK information corresponding to the invalid SLIV. The fact that the first device does not correspond to the HARQ-ACK information may mean that the first device does not feed back the HARQ-ACK information corresponding to the invalid SLIV. In other words, the HARQ-ACK codebook fed back by the first device does not include the HARQ-ACK information corresponding to the invalid SLIV.

When the invalid SLIV corresponds to HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV may refer to the ACK information corresponding to the invalid SLIV, or may refer to the NACK information corresponding to the invalid SLIV. Exemplarily, the HARQ-ACK information corresponding to the invalid SLIV may refer to the NACK information corresponding to the invalid SLIV.

The embodiment of the present application clarifies the processing method of the invalid SLIV, thereby avoiding the communication disorder caused by the inconsistent understanding of the processing method of the invalid SLIV by the first device and the second device.

In some embodiments, the processing manner of the invalid SLIV (that is, whether the invalid SLIV corresponds to the HARQ process ID and/or the HARQ-ACK information) may be associated with one or more types of information. For example, how an invalid SLIV is handled may depend on one or more conditions. Under the same conditions, invalid SLIVs can be handled in the same way. Invalid SLIVs can be handled in the same or different ways under different conditions.

In some embodiments, the invalid SLIV processing method may be associated with at least one of the following information: the invalid SLIV determination method (for example, may include the aforementioned determination based on semi-static configuration parameters and/or based on dynamic scheduling parameters Determination); the transmission direction of the first physical channel; the type of the HARQ-ACK codebook configured for the first device; and whether the first device is configured with a bundling-based HARQ-ACK information generation method.

In the following, the manner of associating the invalid SLIV with other information will be illustrated in detail with reference to the embodiments.

Embodiment 1: Whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the invalid SLIV determined

In some embodiments, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination of the invalid SLIV, which may include at least one of the following situations: If the invalid SLIV is determined based on semi-static configuration parameters invalid SLIV, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information; if Invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, and the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to the HARQ process number and/or or HARQ-ACK information; if the invalid SLIV is determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and the invalid SLIV corresponds to the HARQ-ACK information.

It should be understood that, on the premise of no conflict, the above situations can be combined arbitrarily. As an example, for an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and HARQ-ACK information; for an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to the HARQ process number and NACK information. As another example, no matter for an invalid SLIV determined based on semi-static configuration parameters or an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and HARQ-ACK information.

A specific example is given below by taking the first physical channel as the PDSCH, the first device as the terminal device, and the second device as the network device as examples.

First, the network device may configure the TDRA table shown in Table 2 above for the terminal device, and different SLIVs correspond to different TBs.

When the terminal device receives the first DCI (corresponding to the first control information above), and the row index I indicated by the TDRA information in the first DCI is 1. Referring to Table 2 above, the terminal device can determine that the first DCI schedules 4 SLIVs according to the row index. In addition, the HARQ process number indication in the first DCI is 2.

Further, in this example, the terminal device determines that SLIVs 1-2 among the four SLIVs are invalid SLIVs determined based on semi-static configuration parameters. For example, the terminal device determines the transmission direction of symbols corresponding to SLIV1-2 and the first Physical The transmission direction of the channel is different. In this case, as shown in Figure 5, the terminal device determines that the invalid SLIV 1-2 does not correspond to the HARQ process number and the HARQ-ACK information. In other words, the terminal device does not need to determine the HARQ process number corresponding to the invalid SLIV 1-2, and does not feed back the HARQ-ACK information corresponding to the invalid SLIV 1-2.

Or, further, in this example, the terminal device determines that SLIVs 1-2 among the 4 SLIVs are invalid SLIVs determined based on dynamic configuration parameters. For example, the terminal device is configured with time-frequency resources (or a rate matching pattern) for rate matching, and the terminal device determines that the time domain resources and frequency domain resources corresponding to SLIV1-2 are the resources in the rate matching pattern. For another example, the terminal device determines that the transmission direction of at least one symbol corresponding to SLIV 1-2 is flexible, The terminal device is configured to receive the second DCI whose DCI format is DCI format 2_0, and the terminal device has not received the second DCI, or the terminal device has received the second DCI, wherein the second DCI indicates that the SLIV 1-2 corresponds to The transmission direction of at least one symbol is not downlink (or the second DCI indicates that the transmission direction of at least one symbol corresponding to the SLIV 1-2 is uplink or flexible). In this case, as shown in Figure 6, the terminal device determines that the invalid SLIV 1-2 corresponds to the HARQ process number and HARQ-ACK information. In other words, the terminal device needs to determine the HARQ process number corresponding to the invalid SLIV 1-2, and feed back the HARQ-ACK information corresponding to the invalid SLIV 1-2.

Embodiment 2: Whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is based on the transmission of the first physical channel directional

In some embodiments, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel, including at least one of the following situations: if the first physical channel is an uplink physical channel , the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the first physical channel is a sidelink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the first physical channel is For the downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device.

If the first physical channel is a downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device, including at least one of the following situations kind:

If the first physical channel is a downlink physical channel, and the first device is configured with the first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the invalid SLIV determination method ;

If the first physical channel is a downlink physical channel, and the first device is not configured with the first type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; and

If the first physical channel is a downlink physical channel and the first device is configured with the second type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or the HARQ-ACK information.

In some embodiments, the first type of HARQ-ACK codebook mentioned in this embodiment may include a Type-1 HARQ-ACK codebook.

In some embodiments, the second type of HARQ-ACK codebook mentioned in this embodiment may include Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK codebook at least one of .

In some embodiments, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel and the determination method of the invalid SLIV.

As an example, if the first physical channel is an uplink physical channel, and the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, then the invalid SLIV does not correspond to the HARQ process number.

As another example, if the first physical channel is an uplink physical channel, and the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, then the invalid SLIV corresponds to the HARQ process number.

As yet another example, if the first physical channel is an uplink physical channel, and the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, then the invalid SLIV does not correspond to the HARQ process number.

As yet another example, if the first physical channel is an uplink physical channel, and the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, then the invalid SLIV corresponds to the HARQ process number.

As yet another example, if the first physical channel is a downlink physical channel, and the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process ID and/or HARQ-ACK information.

As yet another example, if the first physical channel is a downlink physical channel, and the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, then the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information.

As yet another example, if the first physical channel is a downlink physical channel, and the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or the HARQ-ACK information.

As yet another example, if the first physical channel is a downlink physical channel, and the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, then the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information.

In the case of no conflict, the above situations can be combined arbitrarily. For example, if the first physical channel is an uplink physical channel, the invalid SLIV does not correspond to the HARQ process number; if the first physical channel is a downlink physical channel, and the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, then the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information; if the first physical channel is a downlink physical channel, and the invalid SLIV is an invalid SLIV determined based on semi-persistent scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information.

Embodiment 3: Whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is configured based on the first device The type of HARQ-ACK codebook is determined

In some embodiments, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device, including at least one of the following situations:

If the first device is not configured with the first type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or the HARQ-ACK information; and

If the first device is configured with the second type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or the HARQ-ACK information.

In some embodiments, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured by the first device, and may also include: whether the invalid SLIV corresponds to the HARQ process number and /or the HARQ-ACK information is determined based on the first device being configured with the first type of HARQ-ACK codebook and the manner of determining the invalid SLIV.

As an example, when the first device is configured with different types of HARQ-ACK codebooks, the invalid SLIV determined based on semi-static configuration parameters and the invalid SLIV determined based on dynamic scheduling parameters may be handled in different ways.

As yet another example, when the first device is configured with different types of HARQ-ACK codebooks, the invalid SLIV determined based on the dynamic scheduling parameters may be handled differently.

In some embodiments, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured by the first device, and may also include: if the first device is configured with the first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the invalid SLIV determination method.

As an example, if the first device is configured with a first type of HARQ-ACK codebook, and the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; And/or, if the first device is configured with the first type of HARQ-ACK codebook, and the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information.

As another example, if the first device is configured with the first type of HARQ-ACK codebook, and the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number, and the invalid SLIV corresponds to the HARQ-ACK information.

In some embodiments, the first type of HARQ-ACK codebook mentioned in this embodiment may include a Type-1 HARQ-ACK codebook.

In some embodiments, the second type of HARQ-ACK codebook mentioned in this embodiment may include Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK codebook at least one of .

A specific example is given below by taking the first physical channel as the PDSCH, the first device as the terminal device, and the second device as the network device as examples.

First, the network device can configure the TDRA table shown in Table 2 above for the terminal device, and different SLIVs correspond to different TBs.

When the terminal device receives the DCI (corresponding to the first control information above), and the row index I indicated by the TDRA information in the DCI is 1. Referring to Table 2 above, the terminal device can determine that the DCI schedules 4 SLIVs according to the row index. In addition, the HARQ process number indicated in the DCI is 2.

Further, in this example, the terminal device determines that SLIVs 1-2 among the 4 SLIVs are invalid SLIVs determined based on dynamic scheduling parameters. For example, the terminal device is configured with time-frequency resources (or rate matching patterns) for rate matching, and the terminal device determines that the time domain resources and frequency domain resources corresponding to SLIV 1-2 are the resources in the rate matching pattern. For another example, the terminal device determines that the transmission direction of at least one symbol corresponding to SLIV 1-2 is flexible based on a TDD pattern configured with a semi-static configuration parameter (such as a high-level parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). The terminal device is configured to receive the second DCI whose DCI format is DCI format 2_0, and the terminal device does not receive the second DCI. Or, the terminal device receives the second DCI, wherein the second DCI indicates that the transmission direction of at least one symbol corresponding to the SLIV 1-2 is not downlink (or the second DCI indicates at least one symbol corresponding to the SLIV 1-2 The direction of transmission is uplink or flexible).

When the terminal device is configured with Type-1 HARQ-ACK codebook feedback, as shown in Figure 6, the invalid SLIV 1-2 corresponds to the HARQ process number and/or HARQ-ACK information.

When the terminal device is configured with Type-2 HARQ-ACK codebook or eType-2 HARQ-ACK codebook or Type-3 HARQ-ACK codebook, as shown in Figure 5, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information.

Embodiment 4: Whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information and whether the first device is configured based on The generation method of the bound HARQ-ACK information has an association relationship

The bundling mentioned in this embodiment of the present application may include at least one of the following types of bundling: time domain bundling, physical channel bundling, and air domain bundling.

For ease of understanding, physical channel bonding, time domain bonding (time domain bonding can be understood as physical channel bonding in the time domain, in some cases, physical channel bonding can be equivalent to time domain bonding) and Airspace binding is introduced.

In some embodiments, the first device may be configured with a method of generating HARQ-ACK information based on physical channel bundling or time-domain bundling (for ease of description, the method of generating HARQ-ACK information based on physical channel bundling is referred to as bonding feedback for physical channels).

If the first device is configured with physical channel binding feedback, for the first control information to schedule multiple physical channels, the first device may be configured with one control information (such as DCI) to schedule the multiple physical channels, each physical channel The number of bits corresponding to the channel is fixed; or, when the first device may be configured with one piece of control information (such as DCI) to schedule multiple physical channels, the number of bits corresponding to the control information is fixed.

In this embodiment of the present application, physical channel bundling feedback can be understood as HARQ-ACK information bundling of N candidate physical channel receivers, that is, only the HARQ-ACK information corresponding to the N candidate physical channel receivers is ACK, then The feedback information after binding of the N candidate physical channel receivers is ACK; if the HARQ-ACK information corresponding to any one of the N candidate physical channel receivers is NACK, then the N candidate physical channel receivers The feedback information after the channel receiver is bound is NACK. N is a positive integer greater than or equal to 2.

Optionally, in a case where physical channel bonding feedback is configured, the first device performs physical channel bonding feedback.

Optionally, for a candidate physical channel receiver that is scheduled for physical channel reception, the HARQ-ACK information corresponding to the candidate physical channel receiver is decoding information after the corresponding physical channel is received.

Optionally, for a candidate physical channel receiver that is not received by the scheduled physical channel, the HARQ-ACK information corresponding to the candidate physical channel receiver is ACK.

Optionally, N is predefined, or N is determined according to configuration parameters of network devices such as physical channel bonding feedback parameters.

Optionally, the N candidate physical channel receivers respectively correspond to the N SLIVs corresponding to the TDRA information in the first control information (such as DCI).

In some embodiments, the first device may also be configured with a manner of generating HARQ-ACK information based on airspace bundling (for ease of description, the manner of generating HARQ-ACK information based on airspace bundling is referred to as airspace bundling feedback hereinafter).

In the embodiment of the present application, the spatial domain bundling feedback can be understood as the bundling of HARQ-ACK information of two codewords, that is, only the HARQ-ACK information corresponding to two codewords is ACK, then the bounded HARQ-ACK information of two codewords is The feedback information is ACK; if the HARQ-ACK information corresponding to any one of the two codewords is NACK, the information to be fed back after the two codewords are bundled is NACK. If only one codeword is scheduled, for another unscheduled codeword, it is assumed that its corresponding HARQ-ACK information is ACK.

In some embodiments, when physical channel bonding feedback and air domain bonding feedback are configured, the bundling feedback mode of the first device is: first perform air domain bonding, and then perform physical channel bonding.

In some embodiments, when the physical channel bundling feedback is configured, when the TB feedback length configured for the first device is greater than 1, the bundling feedback method of the first device is: first perform air domain bundling, and then perform Physical channel bonding. That is to say, if the first device is configured with physical channel bundling feedback and air domain bundling feedback, or the first device is configured with physical channel bundling feedback but not configured with air domain bundling feedback, when the physical When the TB feedback length corresponding to the channel is greater than 1 (or the number of codewords corresponding to the physical channel to be bundled and fed back is greater than 1), the first device needs to perform spatial domain bundling feedback to obtain the HARQ-ACK information corresponding to the physical channel, and then, the first device needs to perform physical channel bundling feedback on the HARQ-ACK information corresponding to different physical channels.

When the first device is configured with a binding-based HARQ-ACK information generation method, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is related to whether the first device is configured with a binding-based HARQ-ACK information generation method connection relation.

In some embodiments, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information has an association with whether the first device is configured to generate binding-based HARQ-ACK information may include: when the invalid SLIV corresponds to the HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV is associated with whether the first device is configured to generate HARQ-ACK information based on binding. For example, when the invalid SLIV corresponds to the HARQ-ACK information, if the first device is not configured with a bundling-based HARQ-ACK information generation manner, the invalid SLIV may correspond to the NACK information. For another example, when the invalid SLIV corresponds to the HARQ-ACK information, if the first device is configured to generate HARQ-ACK information based on binding, the invalid SLIV may correspond to the ACK information.

In some embodiments, when the first device is configured with bundling feedback (which may be at least one of time domain bundling feedback, physical channel bundling feedback, and air domain bundling feedback), the first device performs bundling When determining the feedback, it is assumed that the HARQ-ACK information corresponding to the candidate physical channel receiver corresponding to the invalid SLIV is ACK information. The invalid SLIV mentioned in this embodiment may be, for example, an invalid SLIV determined based on dynamic scheduling parameters.

In some embodiments, when the first device is configured with bundling feedback (which may be at least one of time domain bundling feedback, physical channel bundling feedback, and air domain bundling feedback), the first device performs bundling When determining the feedback, the HARQ-ACK information corresponding to the candidate physical channel receiver corresponding to the invalid SLIV may not be considered. The invalid SLIV mentioned in this embodiment may be, for example, an invalid SLIV determined based on semi-static configuration parameters.

In some embodiments, if the first device is configured with bundling feedback (which may be at least one of time domain bundling feedback, physical channel bundling feedback, and air domain bundling feedback), the invalid For SLIV, the first device assumes that the HARQ-ACK information corresponding to the invalid SLIV is ACK information; or, the first device may not consider the HARQ-ACK information corresponding to the invalid SLIV when performing codebook generation based on bundling feedback.

In some embodiments, if the first device is configured with bundling feedback (it may be at least one of time domain bundling feedback, physical channel bundling feedback, and air domain bundling feedback), for the invalid SLIV determined by the dynamic scheduling parameter, The first device may assume that the HARQ-ACK information corresponding to the invalid SLIV is ACK information; or, the first device may not consider the HARQ-ACK information corresponding to the invalid SLIV when performing codebook generation based on bundling feedback.

In some embodiments, if the first device is configured with bundling feedback (it may be at least one of time domain bundling feedback, physical channel bundling feedback, and air domain bundling feedback), for invalid SLIV, the first device may assume that The HARQ-ACK information corresponding to the invalid SLIV is ACK information; or, the first device may not consider the HARQ-ACK information corresponding to the invalid SLIV when performing codebook generation based on bundling feedback.

In some embodiments, for downlink transmission, each of the multiple SLIVs included in the configured TDRA table of the first device corresponds to a K ₀ value.

Optionally, the K ₀ value is used to indicate the number of time units between the time slot where the DCI is located and the time slot where the symbol corresponding to each SLIV in the multiple SLIVs is located.

Optionally, the K ₀ value is used to indicate the number of time units between the time unit of the DCI and the time unit of each of the multiple SLIVs.

Optionally, for the first SLIV, the K ₀ value is used to indicate the number of time units between the time slot where the DCI is located and the time slot where the SLIV is located; for other SLIVs except the first SLIV, the K ₀ value is used for Indicates the number of time units between the time slot where the previous SLIV of the SLIV is located and the time slot where the SLIV is located.

Optionally, for the first SLIV, the K ₀ value is used to indicate the number of time units between the time unit where the DCI is located and the time unit where the SLIV is located; for other SLIVs except the first SLIV, the K ₀ value is used for Indicates the number of time units between the time unit of the previous SLIV of the SLIV and the time unit of the SLIV.

In some embodiments, for uplink transmission, each of the multiple SLIVs included in the configured TDRA table of the first device corresponds to a K ₂ value.

Optionally, the _K2 value is used to indicate the number of time units between the time slot where the DCI is located and the time slot where each of the multiple SLIVs is located.

Optionally, the _K2 value is used to indicate the number of time units between the time unit of the DCI and the time unit of each of the multiple SLIVs.

Optionally, for the first SLIV, the K ₂ value is used to indicate the number of time units between the time slot where the DCI is located and the time slot where the SLIV is located; for other SLIVs except the first SLIV, the K ₂ value is used for Indicates the number of time units between the time slot where the previous SLIV of the SLIV is located and the time slot where the SLIV is located.

Optionally, for the first SLIV, the K ₂ value is used to indicate the number of time units between the time unit where the DCI is located and the time unit where the SLIV is located; for other SLIVs except the first SLIV, the K ₂ value is used for Indicates the number of time units between the time unit of the previous SLIV of the SLIV and the time unit of the SLIV.

In some embodiments, for downlink transmission, the scheduled DCI of the first device corresponds to one or more K ₁ values.

Optionally, the K ₁ value is used to indicate the number of time units between the time slot where the physical channel reception end position corresponding to the last configured SLIV among the multiple SLIVs corresponding to the DCI is located and the PUCCH feedback time slot corresponding to the DCI .

Optionally, the K ₁ value is used to indicate the number of time units between the end position of the receiving end position of the physical channel corresponding to the last configured SLIV among the multiple SLIVs corresponding to the DCI and the PUCCH feedback time unit corresponding to the DCI .

Optionally, the K ₁ value is used to indicate the number of time units between the time slot where the physical channel reception end position corresponding to the last effective SLIV among the multiple SLIVs corresponding to the DCI is located and the PUCCH feedback time slot corresponding to the DCI.

Optionally, the K ₁ value is used to indicate the number of time units between the end position of physical channel reception corresponding to the last valid SLIV among the multiple SLIVs corresponding to the DCI and the PUCCH feedback time unit corresponding to the DCI.

Optionally, in the case where the last SLIV among the multiple SLIVs corresponding to the DCI is an invalid SLIV determined by dynamic scheduling parameters, the K ₁ value is used to indicate that the time slot where the physical channel reception end position corresponding to the invalid SLIV is located is the same as the The number of time units between PUCCH feedback slots corresponding to the DCI.

Optionally, in the case where the last SLIV among the multiple SLIVs corresponding to the DCI is an invalid SLIV of the dynamic scheduling parameter, the K ₁ value is used to indicate that the time unit of the end position of the physical channel reception corresponding to the invalid SLIV is the same as the DCI The number of time units between corresponding PUCCH feedback time units.

Optionally, when the last SLIV among the multiple SLIVs corresponding to the DCI is an invalid SLIV determined semi-statically, the K ₁ value is used to indicate that the time slot where the physical channel reception end position corresponding to the invalid SLIV is located is the same as the DCI The number of time units between corresponding PUCCH feedback slots.

Optionally, in the case that the last SLIV among the multiple SLIVs corresponding to the DCI is an invalid SLIV determined semi-statically, the K ₁ value is used to indicate that the time unit of the end position of the physical channel reception corresponding to the invalid SLIV is the same as the DCI The number of time units between corresponding PUCCH feedback time units.

In this embodiment of the application, the time unit includes one of the following: one or more time slots, one or more symbols, one or more sub-slots, one or more sub-frames, one or more milliseconds, one or more Seconds wait.

In some embodiments, different subcarrier intervals correspond to different time units, or the time unit is determined according to the subcarrier interval. For example, when the subcarrier spacing is 480kHz, the time unit is 4 time slots; when the subcarrier spacing is 960kHz, the time unit is 8 time slots.

In some embodiments, the starting position of the time unit is determined according to the time slot in which the first control information is received. Alternatively, the starting position of the time unit is a relative position. For example, assuming that the time unit is 4 time slots, and the time slot receiving the first control information is time slot n, the first time unit includes time slot n to time slot n+3; the second time unit includes time slot From n+4 to time slot n+7, the mth time unit includes time slot n+4*(m-1) to time slot n+3+4*(m-1), and so on.

In some embodiments, the start position of the time unit is determined according to the start position of the radio frame. Alternatively, the starting position of the time unit is an absolute position. For example, assuming that the time unit is 4 time slots, then time slot 0 to time slot 3 in the radio frame is a time unit, time slot 4 to time slot 7 is a time unit, and so on.

In some embodiments, the subcarrier spacing corresponding to the time unit is a configured subcarrier spacing. For example, the subcarrier spacing corresponding to the time unit is the subcarrier spacing configured on the active BWP.

Taking PDSCH transmission as an example for schematic illustration, it is assumed that the information in the TDRA table configured by the network device for the first device is as shown in Table 3, wherein the K ₀ value is used to indicate the time unit where the DCI is located and each of the multiple SLIVs The number of time units between time units where a SLIV is located. Here, it is assumed that the time unit is 2 time slots. When the first device receives DCI on time slot n, the row index I indicated by the TDRA information in the DCI is 1, and the HARQ process number in the DCI indicates 1, the PDSCH received by the first device is shown in Figure 7 shown.

Table 3: TDRA form

The method embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 7 , and the device embodiment of the present application is described in detail below in conjunction with FIG. 8 to FIG. 10 . It should be understood that the descriptions of the method embodiments correspond to the descriptions of the device embodiments, therefore, for parts not described in detail, reference may be made to the foregoing method embodiments.

Fig. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device 800 in FIG. 8 may be the aforementioned first device. The communication device 800 may include a receiving module 810 . The receiving module 810 is configured to receive first control information. The first control information corresponds to multiple configuration SLIVs, and the multiple configuration SLIVs include invalid SLIVs; wherein, the invalid SLIVs correspond to HARQ process numbers and/or HARQ-ACK information; or, the invalid SLIVs do not correspond to HARQ processes number and/or HARQ-ACK information.

Optionally, the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters or an invalid SLIV determined based on semi-static configuration parameters.

Optionally, the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, including: the transmission direction of at least one first symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, wherein the first The physical channel is a physical channel scheduled by the first control information, and the transmission direction of the at least one first symbol is determined based on a dynamic scheduling parameter.

Optionally, the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, including: some or all symbols corresponding to the invalid SLIV are symbols in time-frequency resources used for rate matching; and/or, the invalid Part or all of the frequency domain resources corresponding to the SLIV are frequency domain resources within the time-frequency resources used for rate matching.

Optionally, the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, including: the transmission direction of at least one second symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, wherein the first A physical channel is a physical channel scheduled by the first control information, and the transmission direction of the at least one second symbol is determined based on semi-static configuration parameters.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information has an association relationship with at least one of the following information: the method of determining the invalid SLIV, wherein the method of determining the invalid SLIV includes Determined based on semi-static configuration parameters and/or determined based on dynamic scheduling parameters; the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information; the first device is configured The type of the HARQ-ACK codebook; and whether the first device is configured with a bundling-based HARQ-ACK information generation method.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the manner of determining the invalid SLIV.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination of the invalid SLIV, including at least one of the following situations: if the invalid SLIV is based on a semi-static If the invalid SLIV determined by configuration parameters does not correspond to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, then the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is based on dynamic scheduling The invalid SLIV determined by the parameters, the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and the The above invalid SLIV corresponds to HARQ-ACK information.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel, including at least one of the following situations: if the first physical channel is an uplink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the first physical channel is a sidelink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; - ACK information; if the first physical channel is a downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is based on the type of the HARQ-ACK codebook configured for the first device definite.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured on the first device.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device, including at least one of the following situations: if The first device is configured with a first type of HARQ-ACK codebook, and whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination method of the invalid SLIV; if the first A device is not configured with the first type of HARQ-ACK codebook, then the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the first device is configured with the second type of HARQ-ACK codebook , the invalid SLIV does not correspond to the HARQ process ID and/or HARQ-ACK information.

Optionally, if the first device is configured with the first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is based on the determination method of the invalid SLIV Determined, including: if the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; and/or, if the invalid SLIV is based on If the invalid SLIV is determined by the dynamic scheduling parameter, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information.

Optionally, if the first device is configured with the first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is based on the determination method of the invalid SLIV The determined includes: if the invalid SLIV is determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number, and the invalid SLIV corresponds to HARQ-ACK information.

Optionally, the first type of HARQ-ACK codebook includes a Type-1 HARQ-ACK codebook.

Optionally, the second type of HARQ-ACK codebook includes at least one of Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK codebook.

Optionally, when the invalid SLIV corresponds to HARQ-ACK information, the invalid SLIV corresponds to HARQ-ACK information, including: the invalid SLIV corresponds to NACK information.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is related to whether the first device is configured to generate binding-based HARQ-ACK information, including: when the invalid SLIV When corresponding to HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV has an association relationship with whether the first device is configured to generate HARQ-ACK information based on bundling.

Optionally, when the invalid SLIV corresponds to HARQ-ACK information, if the first device is not configured to generate HARQ-ACK information based on bundling, then the invalid SLIV corresponds to NACK information.

Optionally, when the invalid SLIV corresponds to HARQ-ACK information, if the first device is configured to generate HARQ-ACK information based on bundling, then the invalid SLIV corresponds to ACK information.

Optionally, the bundling includes at least one of time domain bundling, physical channel bundling, and air domain bundling.

Optionally, the invalid SLIV includes a configuration SLIV among the plurality of configuration SLIVs that does not correspond to transmission of a first physical channel, and the first physical channel is a physical channel scheduled by the first control information.

Optionally, the first control information is downlink control information DCI or sidelink control information.

Fig. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device 900 in FIG. 9 may be the aforementioned second device. The communication device 900 may include a sending module 910 . The sending module 910 may be configured to send first control information, where the first control information corresponds to multiple configuration SLIVs, and the multiple configuration SLIVs include invalid SLIVs; wherein, the invalid SLIVs correspond to HARQ process numbers and/or HARQ-ACK information ; Or, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information.

Optionally, the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters or an invalid SLIV determined based on semi-static configuration parameters.

Optionally, the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, including: the transmission direction of at least one first symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, wherein the first The physical channel is a physical channel scheduled by the first control information, and the transmission direction of the at least one first symbol is determined based on a dynamic scheduling parameter.

Optionally, the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, including: some or all symbols corresponding to the invalid SLIV are symbols in time-frequency resources used for rate matching; and/or, the invalid Part or all of the frequency domain resources corresponding to the SLIV are frequency domain resources within the time-frequency resources used for rate matching.

Optionally, the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, including: the transmission direction of at least one second symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, wherein the first A physical channel is a physical channel scheduled by the first control information, and the transmission direction of the at least one second symbol is determined based on semi-static configuration parameters.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information has an association relationship with at least one of the following information: the method of determining the invalid SLIV, wherein the method of determining the invalid SLIV includes Determined based on semi-static configuration parameters and/or determined based on dynamic scheduling parameters; the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information; the first device is configured The type of the HARQ-ACK codebook; and whether the first device is configured with a bundling-based HARQ-ACK information generation method.

Optionally, whether the invalid SLIV corresponds to the HARQ process ID and/or the HARQ-ACK information is determined based on the manner of determining the invalid SLIV.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination of the invalid SLIV, including at least one of the following situations: if the invalid SLIV is based on a semi-static If the invalid SLIV determined by configuration parameters does not correspond to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, then the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the invalid SLIV is based on dynamic scheduling The invalid SLIV determined by the parameters, the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information; if the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and the The above invalid SLIV corresponds to HARQ-ACK information.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel, including at least one of the following situations: if the first physical channel is an uplink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the first physical channel is a sidelink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; - ACK information; if the first physical channel is a downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is based on the type of the HARQ-ACK codebook configured for the first device definite.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device, including at least one of the following situations: if The first device is configured with a first type of HARQ-ACK codebook, and whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination method of the invalid SLIV; if the first A device is not configured with the first type of HARQ-ACK codebook, then the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; if the first device is configured with the second type of HARQ-ACK codebook , the invalid SLIV does not correspond to the HARQ process ID and/or HARQ-ACK information.

Optionally, if the first device is configured with the first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is based on the determination method of the invalid SLIV Determined, including: if the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; and/or, if the invalid SLIV is based on If the invalid SLIV is determined by the dynamic scheduling parameter, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information.

Optionally, if the first device is configured with the first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is based on the determination method of the invalid SLIV The determined includes: if the invalid SLIV is determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number, and the invalid SLIV corresponds to HARQ-ACK information.

Optionally, the first type of HARQ-ACK codebook includes a Type-1 HARQ-ACK codebook.

Optionally, the second type of HARQ-ACK codebook includes at least one of Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK codebook.

Optionally, when the invalid SLIV corresponds to HARQ-ACK information, the invalid SLIV corresponds to HARQ-ACK information, including: the invalid SLIV corresponds to NACK information.

Optionally, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is related to whether the first device is configured to generate binding-based HARQ-ACK information, including: when the invalid SLIV When corresponding to HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV has an association relationship with whether the first device is configured to generate HARQ-ACK information based on bundling.

Optionally, when the invalid SLIV corresponds to HARQ-ACK information, if the first device is not configured to generate HARQ-ACK information based on bundling, then the invalid SLIV corresponds to NACK information.

Optionally, when the invalid SLIV corresponds to HARQ-ACK information, if the first device is configured to generate HARQ-ACK information based on bundling, then the invalid SLIV corresponds to ACK information.

Optionally, the bundling includes at least one of time domain bundling, physical channel bundling, and air domain bundling.

Optionally, the invalid SLIV includes a configuration SLIV among the plurality of configuration SLIVs that does not correspond to transmission of a first physical channel, and the first physical channel is a physical channel scheduled by the first control information.

Optionally, the first control information is downlink control information DCI or sidelink control information.

Fig. 10 is a schematic structural diagram of a device according to an embodiment of the present application. The dashed line in Figure 10 indicates that the unit or module is optional. The apparatus 1000 may be used to implement the methods described in the foregoing method embodiments. The apparatus 1000 may be a chip, a terminal device or a network device.

Apparatus 1000 may include one or more processors 1010 . The processor 1010 can support the device 1000 to implement the methods described in the foregoing method embodiments. The processor 1010 may be a general purpose processor or a special purpose processor. For example, the processor may be a central processing unit (central processing unit, CPU). Alternatively, the processor can also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), off-the-shelf programmable gate arrays (field programmable gate arrays, FPGAs) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

Apparatus 1000 may also include one or more memories 1020 . A program is stored in the memory 1020, and the program can be executed by the processor 1010, so that the processor 1010 executes the methods described in the foregoing method embodiments. The memory 1020 may be independent of the processor 1010 or may be integrated in the processor 1010 .

The apparatus 1000 may also include a transceiver 1030 . The processor 1010 can communicate with other devices or chips through the transceiver 1030 . For example, the processor 1010 may send and receive data with other devices or chips through the transceiver 1030 .

The embodiment of the present application also provides a computer-readable storage medium for storing programs. The computer-readable storage medium can be applied to the terminal or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program product. The computer program product includes programs. The computer program product can be applied to the terminal or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or the network device provided in the embodiments of the present application, and the computer program enables the computer to execute the methods performed by the terminal or the network device in the various embodiments of the present application.

It should be understood that in this embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

It should be understood that the term "and/or" in this article is only an association relationship describing associated objects, which means that there may be three relationships, for example, A and/or B may mean: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

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

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

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

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may 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 the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be read by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (digital video disc, DVD)) or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) )wait.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims (98)

1. A method for wireless communication, comprising:

   The first device receives first control information, where the first control information corresponds to multiple configuration start length indication SLIVs, and the multiple configuration SLIVs include invalid SLIVs;

   Wherein, the invalid SLIV corresponds to the hybrid automatic repeat request HARQ process number and/or hybrid automatic repeat request-confirmation HARQ-ACK information; or,

   The invalid SLIV does not correspond to the HARQ process ID and/or HARQ-ACK information.
2. The method according to claim 1, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters or an invalid SLIV determined based on semi-static configuration parameters.
3. The method according to claim 2, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, comprising:

   The transmission direction of the at least one first symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one first The transmission direction of symbols is determined based on dynamic scheduling parameters.
4. The method according to claim 2 or 3, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, including:

   Part or all of the symbols corresponding to the invalid SLIV are symbols in time-frequency resources used for rate matching; and/or,

   Part or all of the frequency-domain resources corresponding to the invalid SLIV are frequency-domain resources within the time-frequency resources used for rate matching.
5. The method according to claim 2, wherein the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, including:

   The transmission direction of at least one second symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one second symbol The direction of transmission of symbols is determined based on semi-static configuration parameters.
6. The method according to any one of claims 1-5, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is associated with at least one of the following information:

   The method of determining the invalid SLIV, wherein the method of determining the invalid SLIV includes determining based on semi-static configuration parameters and/or determining based on dynamic scheduling parameters;

   The transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information;

   The type of the HARQ-ACK codebook configured for the first device; and

   Whether the first device is configured with a bundling-based HARQ-ACK information generation manner.
7. The method according to claim 6, wherein whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on a determination manner of the invalid SLIV.
8. The method according to claim 7, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination of the invalid SLIV, including at least one of the following situations:

   If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

   If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information;

   If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

   If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information;

   If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and the invalid SLIV corresponds to HARQ-ACK information.
9. The method according to claim 6, wherein whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the transmission direction of the first physical channel.
10. The method according to claim 9, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel, including at least one of the following situations kind:

    If the first physical channel is an uplink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a sidelink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device.
11. The method according to claim 6, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the configured HARQ-ACK codebook of the first device.
12. The method according to claim 10 or 11, wherein whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is determined based on the type of the configured HARQ-ACK codebook of the first device , including at least one of the following:

    If the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the invalid SLIV determination method;

    If the first device is not configured with the first type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first device is configured with the second type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process ID and/or the HARQ-ACK information.
13. The method according to claim 12, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is determined based on the manner in which the invalid SLIV is determined, including:

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; and/or,

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to the HARQ process ID and/or HARQ-ACK information.
14. The method according to claim 12, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is determined based on the manner in which the invalid SLIV is determined, including:

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process ID, and the invalid SLIV corresponds to HARQ-ACK information.
15. The method according to any one of claims 12-14, wherein the HARQ-ACK codebook of the first type comprises a Type-1 HARQ-ACK codebook.
16. The method according to claim 12, wherein the second type of HARQ-ACK codebook includes Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK codebook at least one of these.
17. The method according to any one of claims 1-16, wherein when the invalid SLIV corresponds to HARQ-ACK information, the invalid SLIV corresponds to HARQ-ACK information, including: the invalid SLIV corresponds to NACK information .
18. The method according to claim 6, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is associated with whether the first device is configured to generate binding-based HARQ-ACK information relationships, including:

    When the invalid SLIV corresponds to HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV has an association relationship with whether the first device is configured to generate HARQ-ACK information based on binding.
19. The method according to claim 6 or 18, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is not configured with a bundling-based HARQ-ACK information generation method, then the An invalid SLIV corresponds to a NACK message.
20. The method according to claim 6 or 18, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is configured with binding-based HARQ-ACK information generation, the invalid SLIV corresponds to ACK information.
21. The method according to any one of claims 6, 18-20, wherein the bundling includes at least one of time domain bundling, physical channel bundling and air domain bundling.
22. The method according to any one of claims 1-21, wherein the invalid SLIV includes a configuration SLIV among the plurality of configuration SLIVs that does not correspond to the transmission of the first physical channel, and the first physical channel is A physical channel scheduled by the first control information.
23. The method according to any one of claims 1-22, wherein the first control information is downlink control information DCI or sidelink control information.
24. A method for wireless communication, comprising:

    The second device sends first control information, where the first control information corresponds to multiple configuration start length indication SLIVs, and the multiple configuration SLIVs include invalid SLIVs;

    Wherein, the invalid SLIV corresponds to the hybrid automatic repeat request HARQ process number and/or HARQ-ACK information; or,

    The invalid SLIV does not correspond to the HARQ process ID and/or HARQ-ACK information.
25. The method according to claim 24, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters or an invalid SLIV determined based on semi-static configuration parameters.
26. The method according to claim 25, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, comprising:

    The transmission direction of the at least one first symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one first The transmission direction of symbols is determined based on dynamic scheduling parameters.
27. The method according to claim 25 or 26, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, comprising:

    Part or all of the symbols corresponding to the invalid SLIV are symbols in time-frequency resources used for rate matching; and/or,

    Part or all of the frequency-domain resources corresponding to the invalid SLIV are frequency-domain resources within the time-frequency resources used for rate matching.
28. The method according to claim 25, wherein the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, comprising:

    The transmission direction of at least one second symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one second symbol The direction of transmission of symbols is determined based on semi-static configuration parameters.
29. The method according to any one of claims 24-28, characterized in that whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is associated with at least one of the following information:

    The method of determining the invalid SLIV, wherein the method of determining the invalid SLIV includes determining based on semi-static configuration parameters and/or determining based on dynamic scheduling parameters;

    The transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information;

    The type of the HARQ-ACK codebook configured for the first device; and

    Whether the first device is configured with a bundling-based HARQ-ACK information generation manner.
30. The method according to claim 29, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determining manner of the invalid SLIV.
31. The method according to claim 30, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination of the invalid SLIV, including at least one of the following situations:

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and the invalid SLIV corresponds to HARQ-ACK information.
32. The method according to claim 29, wherein whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the transmission direction of the first physical channel.
33. The method according to claim 32, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel, including at least one of the following situations kind:

    If the first physical channel is an uplink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a sidelink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device.
34. The method according to claim 29, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the configured HARQ-ACK codebook of the first device.
35. The method according to claim 33 or 34, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device , including at least one of the following:

    If the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the invalid SLIV determination method;

    If the first device is not configured with the first type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first device is configured with the second type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process ID and/or the HARQ-ACK information.
36. The method according to claim 35, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is determined based on the manner in which the invalid SLIV is determined, including:

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; and/or,

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to the HARQ process ID and/or HARQ-ACK information.
37. The method according to claim 35, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is determined based on the manner in which the invalid SLIV is determined, including:

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process ID, and the invalid SLIV corresponds to HARQ-ACK information.
38. The method according to any one of claims 35-37, wherein the first type of HARQ-ACK codebook comprises a Type-1 HARQ-ACK codebook.
39. The method according to claim 35, wherein the second type of HARQ-ACK codebook includes Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK codebook at least one of these.
40. The method according to any one of claims 24-39, wherein when the invalid SLIV corresponds to HARQ-ACK information, the invalid SLIV corresponds to HARQ-ACK information, including: the invalid SLIV corresponds to NACK information .
41. The method according to claim 29, wherein whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is associated with whether the first device is configured to generate HARQ-ACK information based on binding relationships, including:

    When the invalid SLIV corresponds to HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV has an association relationship with whether the first device is configured to generate HARQ-ACK information based on binding.
42. The method according to claim 29 or 41, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is not configured with binding-based HARQ-ACK information generation, then the An invalid SLIV corresponds to a NACK message.
43. The method according to claim 29 or 41, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is configured with binding-based HARQ-ACK information generation, the invalid SLIV corresponds to ACK information.
44. The method according to any one of claims 29, 41-43, wherein the bundling includes at least one of time domain bundling, physical channel bundling and air domain bundling.
45. The method according to any one of claims 24-44, wherein the invalid SLIV includes a configuration SLIV among the plurality of configuration SLIVs that does not correspond to the transmission of the first physical channel, and the first physical channel is A physical channel scheduled by the first control information.
46. The method according to any one of claims 24-45, wherein the first control information is downlink control information DCI or sidelink control information.
47. A communication device, characterized in that the communication device is a first device, and the first device includes:

    A receiving module, configured to receive first control information, where the first control information corresponds to a plurality of configuration start length indication SLIVs, and the plurality of configuration SLIVs include invalid SLIVs;

    Wherein, the invalid SLIV corresponds to the hybrid automatic repeat request HARQ process number and/or HARQ-ACK information; or,

    The invalid SLIV does not correspond to the HARQ process ID and/or HARQ-ACK information.
48. The communication device according to claim 47, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters or an invalid SLIV determined based on semi-static configuration parameters.
49. The communication device according to claim 48, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, comprising:

    The transmission direction of the at least one first symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one first The transmission direction of symbols is determined based on dynamic scheduling parameters.
50. The communication device according to claim 48 or 49, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, including:

    Part or all of the symbols corresponding to the invalid SLIV are symbols in time-frequency resources used for rate matching; and/or,

    Part or all of the frequency-domain resources corresponding to the invalid SLIV are frequency-domain resources within the time-frequency resources used for rate matching.
51. The communication device according to claim 48, wherein the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, including:

    The transmission direction of at least one second symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one second symbol The direction of transmission of symbols is determined based on semi-static configuration parameters.
52. The communication device according to any one of claims 47-51, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information has an association relationship with at least one of the following information:

    The method of determining the invalid SLIV, wherein the method of determining the invalid SLIV includes determining based on semi-static configuration parameters and/or determining based on dynamic scheduling parameters;

    The transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information;

    The type of the HARQ-ACK codebook configured for the first device; and

    Whether the first device is configured with a bundling-based HARQ-ACK information generation manner.
53. The communication device according to claim 52, wherein whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on a manner of determining the invalid SLIV.
54. The communication device according to claim 53, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination of the invalid SLIV, including at least one of the following situations :

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and the invalid SLIV corresponds to HARQ-ACK information.
55. The communication device according to claim 52, wherein whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the transmission direction of the first physical channel.
56. The communication device according to claim 55, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel, including at least one of the following situations A sort of:

    If the first physical channel is an uplink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a sidelink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device.
57. The communication device according to claim 52, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device.
58. The communication device according to claim 56 or 57, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device , including at least one of the following:

    If the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the invalid SLIV determination method;

    If the first device is not configured with the first type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first device is configured with the second type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process ID and/or the HARQ-ACK information.
59. The communication device according to claim 58, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK Information is determined based on the manner in which the invalid SLIV was determined, including:

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; and/or,

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to the HARQ process ID and/or HARQ-ACK information.
60. The communication device according to claim 58, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK Information is determined based on the manner in which the invalid SLIV was determined, including:

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process ID, and the invalid SLIV corresponds to HARQ-ACK information.
61. The communication device according to any one of claims 58-60, wherein the first type of HARQ-ACK codebook comprises a Type-1 HARQ-ACK codebook.
62. The communication device according to claim 58, wherein the second type of HARQ-ACK codebook includes Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK at least one of the codebooks.
63. The communication device according to any one of claims 47-62, wherein when the invalid SLIV corresponds to HARQ-ACK information, the invalid SLIV corresponds to HARQ-ACK information, including: the invalid SLIV corresponds to NACK information.
64. The communication device according to claim 52, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is related to whether the first device is configured to generate binding-based HARQ-ACK information Relationships, including:

    When the invalid SLIV corresponds to HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV has an association relationship with whether the first device is configured to generate HARQ-ACK information based on binding.
65. The communication device according to claim 52 or 64, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is not configured with a bundling-based HARQ-ACK information generation method, then the The above invalid SLIV corresponds to NACK information.
66. The communication device according to claim 52 or 64, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is configured to generate HARQ-ACK information based on binding, then the Invalid SLIV corresponds to ACK information.
67. The communication device according to any one of claims 52, 64-66, wherein the bundling includes at least one of time domain bundling, physical channel bundling and air domain bundling.
68. The communication device according to any one of claims 47-67, wherein the invalid SLIV includes a configuration SLIV among the plurality of configuration SLIVs that does not correspond to the transmission of the first physical channel, and the first physical channel A physical channel scheduled for the first control information.
69. The communication device according to any one of claims 47-68, wherein the first control information is downlink control information DCI or sidelink control information.
70. A communication device, characterized in that the communication device is a second device, and the second device includes:

    A sending module, configured to send first control information, where the first control information corresponds to multiple configuration start length indication SLIVs, and the multiple configuration SLIVs include invalid SLIVs;

    Wherein, the invalid SLIV corresponds to the hybrid automatic repeat request HARQ process number and/or HARQ-ACK information; or,

    The invalid SLIV does not correspond to the HARQ process ID and/or HARQ-ACK information.
71. The communication device according to claim 70, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters or an invalid SLIV determined based on semi-static configuration parameters.
72. The communication device according to claim 71, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, comprising:

    The transmission direction of the at least one first symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one first The transmission direction of symbols is determined based on dynamic scheduling parameters.
73. The communication device according to claim 71 or 72, wherein the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, including:

    Part or all of the symbols corresponding to the invalid SLIV are symbols in time-frequency resources used for rate matching; and/or,

    Part or all of the frequency-domain resources corresponding to the invalid SLIV are frequency-domain resources within the time-frequency resources used for rate matching.
74. The communication device according to claim 71, wherein the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, including:

    The transmission direction of at least one second symbol corresponding to the invalid SLIV is different from the transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information, and the at least one second symbol The direction of transmission of symbols is determined based on semi-static configuration parameters.
75. The communication device according to any one of claims 70-74, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information has an association relationship with at least one of the following information:

    The method of determining the invalid SLIV, wherein the method of determining the invalid SLIV includes determining based on semi-static configuration parameters and/or determining based on dynamic scheduling parameters;

    The transmission direction of the first physical channel, where the first physical channel is a physical channel scheduled by the first control information;

    The type of the HARQ-ACK codebook configured for the first device; and

    Whether the first device is configured with a bundling-based HARQ-ACK information generation manner.
76. The communication device according to claim 75, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the manner of determining the invalid SLIV.
77. The communication device according to claim 76, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the determination of the invalid SLIV, including at least one of the following situations :

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information;

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process number and the invalid SLIV corresponds to HARQ-ACK information.
78. The communication device according to claim 75, wherein whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the transmission direction of the first physical channel.
79. The communication device according to claim 78, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the transmission direction of the first physical channel, including at least one of the following situations A sort of:

    If the first physical channel is an uplink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a sidelink physical channel, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first physical channel is a downlink physical channel, whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the HARQ-ACK codebook configured for the first device.
80. The communication device according to claim 75, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the configured HARQ-ACK codebook of the first device.
81. The communication device according to claim 79 or 80, wherein whether the invalid SLIV corresponds to the HARQ process number and/or the HARQ-ACK information is determined based on the type of the configured HARQ-ACK codebook of the first device , including at least one of the following:

    If the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to a HARQ process number and/or HARQ-ACK information is determined based on the invalid SLIV determination method;

    If the first device is not configured with the first type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information;

    If the first device is configured with the second type of HARQ-ACK codebook, the invalid SLIV does not correspond to the HARQ process ID and/or the HARQ-ACK information.
82. The communication device according to claim 81, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK Information is determined based on the manner in which the invalid SLIV was determined, including:

    If the invalid SLIV is an invalid SLIV determined based on semi-static configuration parameters, the invalid SLIV does not correspond to the HARQ process number and/or HARQ-ACK information; and/or,

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV corresponds to the HARQ process ID and/or HARQ-ACK information.
83. The communication device according to claim 81, wherein if the first device is configured with a first type of HARQ-ACK codebook, whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK Information is determined based on the manner in which the invalid SLIV was determined, including:

    If the invalid SLIV is an invalid SLIV determined based on dynamic scheduling parameters, the invalid SLIV does not correspond to the HARQ process ID, and the invalid SLIV corresponds to HARQ-ACK information.
84. The communication device according to any one of claims 81-83, wherein the first type of HARQ-ACK codebook comprises a Type-1 HARQ-ACK codebook.
85. The communication device according to claim 81, wherein the second type of HARQ-ACK codebook includes Type-2 HARQ-ACK codebook, eType-2 HARQ-ACK codebook and Type-3 HARQ-ACK at least one of the codebooks.
86. The communication device according to any one of claims 70-85, wherein when the invalid SLIV corresponds to HARQ-ACK information, the invalid SLIV corresponds to HARQ-ACK information, including: the invalid SLIV corresponds to NACK information.
87. The communication device according to claim 75, wherein whether the invalid SLIV corresponds to the HARQ process number and/or HARQ-ACK information is related to whether the first device is configured to generate binding-based HARQ-ACK information Relationships, including:

    When the invalid SLIV corresponds to HARQ-ACK information, the HARQ-ACK information corresponding to the invalid SLIV has an association relationship with whether the first device is configured to generate HARQ-ACK information based on binding.
88. The communication device according to claim 75 or 87, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is not configured with a bundling-based HARQ-ACK information generation method, then the The above invalid SLIV corresponds to NACK information.
89. The communication device according to claim 75 or 87, wherein when the invalid SLIV corresponds to HARQ-ACK information, if the first device is configured to generate HARQ-ACK information based on binding, then the Invalid SLIV corresponds to ACK information.
90. The communication device according to any one of claims 75, 87-89, wherein the bundling includes at least one of time domain bundling, physical channel bundling and air domain bundling.
91. The communication device according to any one of claims 70-90, wherein the invalid SLIV includes a configuration SLIV among the plurality of configuration SLIVs that does not correspond to the transmission of the first physical channel, and the first physical channel A physical channel scheduled for the first control information.
92. The communication device according to any one of claims 70-91, wherein the first control information is downlink control information DCI or sidelink control information.
93. A communication device, characterized in that it includes a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory to execute any one of claims 1-46 Methods.
94. An apparatus, characterized by comprising a processor, configured to call a program from a memory to execute the method according to any one of claims 1-46.
95. A chip, characterized by comprising a processor, configured to call a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-46.
96. A computer-readable storage medium, characterized in that a program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1-46.
97. A computer program product, characterized by comprising a program, the program causes a computer to execute the method according to any one of claims 1-46.
98. A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1-46.

Images