Information feedback method, information receiving method and device

Abstract

The embodiments of the present invention provide an information receiving method, an information transmitting method, and an information feedback method and device, which includes a first receiving unit (1101) for receiving downlink control information for scheduling a PDSCH transmitted by a network device, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs, and a second receiving unit (1102) for receiving one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present invention relates to the field of communications technology. [Background technology]

[0002] A Physical Downlink Shared Channel (PDSCH) is one of the physical downlink channels in a wireless communication system, and carries downlink data. The PDSCH may be scheduled by downlink control information (DCI). The DCI for scheduling the PDSCH includes at least information indicating a resource of the PDSCH. In the current new radio (NR) system, multiple DCI formats for scheduling the PDSCH are defined, such as DCI format 1_0 (PDSCH), DCI format 1_1 (PDSCH), and DCI format 1_2 (PDSCH). To meet different scheduling requirements, specific information and / or sizes included in the DCI of different DCI formats are different.

[0003] Also, the PDSCH may be semi-statically configured or semi-persistently scheduled. In the new radio NR, the semi-statically configured or semi-persistently scheduled PDSCH is referred to as, for example, a semi-statically scheduled (Semi-Persistent Scheduling (SPS)) PDSCH (SPS PDSCH). In some cases, after the network device provides the SPS configuration via radio resource control (RRC) signaling, the network device needs to activate the SPS configuration by DCI before the terminal device receives the SPS PDSCH accordingly. In addition to scheduling the PDSCH and activating the SPS, the DCI may also be used to deactivate the SPS, idle cells, etc.

[0004] In order to allow a network device to determine whether the terminal device has successfully received downlink data and / or control information, the terminal device generally needs to feed back Hybrid Automatic Repeat Request (HARQ) feedback information (e.g., ACK / NACK). Depending on the scheduling of the network device, the HARQ feedback information can be carried by a Physical Uplink Control Channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH). Generally, one PUCCH or PUSCH can carry one HARQ feedback codebook, which includes one or more HARQ feedback information bits.

[0005] The above description of the background art is merely for the purpose of more clearly and completely explaining the configurations of the present invention and for the understanding of those skilled in the art, and should not be construed as meaning that these configurations are well known to those skilled in the art just because they are described in the background art of the present invention. Summary of the Invention [Problem to be solved by the invention]

[0006] Currently, the NR system supports multiple transmit / receive points (TRPs), and in the scenario of multiple TRPs, different TRPs support repeatedly transmitting the same transmission block (TB). Figure 1 is a schematic diagram of a scenario of two TRPs, and as shown in Figure 1, TRP0 and TRP1 transmit the same TB0 to a terminal device. The repetition transmission scheme for the TB can support multiple repetition (also called repetition) schemes, such as "fdmSchemeA", "fdmSchemeB", and "tdmSchemeA", including space division (SDM), frequency division (FDM), intra-slot time division (TDM), and inter-slot time division (TDM). The specific repetition scheme is configurable, for example, via a parameter repetitionScheme in higher layer signaling, and if repetitionScheme is set to "tdmSchemeA", the repetition scheme adopts "tdmSchemeA".

[0007] The following further explains "tdmSchemeA".

[0008] If "tdmSchemeA" is configured, assuming that two transmission configuration indication (TCI) states are indicated in the DCI, the terminal device should receive two PDSCH transmission occasions, each corresponding to a different TCI state, where the first PDSCH transmission occasion corresponds to the first TCI state and the second PDSCH transmission occasion corresponds to the second TCI state.

[0009] FIG. 2 is a schematic diagram of the two PDSCH transmission occasions. As shown in FIG. 2, the two PDSCH transmission occasions are in the same slot and do not overlap. stThe symbols of the second PDSCH transmission occasion (2 nd The number of symbols of the first PDSCH transmission occasion (StartingSymbolOffsetK) is the same as the number of symbols of the first PDSCH transmission occasion, and the first symbol is determined based on an offset value relative to the last symbol of the first PDSCH transmission occasion. Specifically, the first symbol starts after the offset value symbols from the last symbol of the first PDSCH transmission occasion. The offset value may be configured by radio resource control (RRC) signaling (StartingSymbolOffsetK), and if not configured, the default is 0. As shown in FIG. 2, the offset value=0.

[0010] Currently, the NR system supports scheduling of multiple PDSCHs via one DCI (PDCCH) (multi-PDSCH scheduling). However, the above multi-TRP repetition scheme is based on the fact that one DCI can schedule only one PDSCH, and does not take into account the case where one DCI schedules multiple PDSCHs. In addition, the multi-TRP repetition scheme and / or the HARQ feedback method for multi-PDSCH scheduling are not clarified.

[0011] In view of at least one of the above problems, embodiments of the present invention provide an information receiving method, a transmitting method, and a feedback method and apparatus. [Means for solving the problem]

[0012] One aspect of an embodiment of the present invention provides an information receiving device, which is applied to a terminal device, including: a first receiving unit that receives downlink control information (DCI) for scheduling a PDSCH transmitted by a network device, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; and a second receiving unit that receives one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

[0013] Another aspect of an embodiment of the present invention provides an information feedback device, applicable to a terminal device, comprising: a second determination unit that determines a set of candidate PDSCH receiving occasions based on a symbol corresponding to a first PDSCH transmission occasion and / or a symbol corresponding to a second PDSCH transmission occasion and / or based on a first allocation table, the first allocation table being related to an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion; and a second processing unit that generates and transmits a HARQ-ACK codebook, the HARQ-ACK codebook including HARQ-ACK information corresponding to the set of candidate PDSCH receiving occasions.

[0014] Another aspect of an embodiment of the present invention provides an information transmission device, applicable to a network device, comprising: a first transmission unit configured to transmit downlink control information for scheduling a PDSCH to a terminal device, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; and a second transmission unit configured to transmit one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

[0015] One of the advantageous effects of the embodiment of the present invention is as follows: Even if one DCI supports scheduling multiple PDSCHs, a multi-TRP repetition scheme can be supported, so that the number of times that a terminal device monitors a PDCCH can be reduced, thereby reducing the complexity and power consumption of the terminal device monitoring the PDCCH, and the resource overhead for transmitting downlink control signaling (DCI) can be reduced, thereby improving data throughput.

[0016] One of the advantageous effects of the embodiment of the present invention is as follows: HARQ feedback (i.e. feedback of HARQ-ACK information) in the case of multi-TRP repetition scheme and / or multi-PDSCH scheduling can be supported, which can reduce the burden of PDCCH monitoring by the UE and reduce the power loss and UE complexity.

[0017] As shown in the following description and drawings, specific embodiments of the present invention are disclosed in detail to show how the principles of the present invention can be employed. However, the scope of the embodiments of the present invention is not limited to these. The embodiments of the present invention include modifications, alterations, and equivalents within the spirit and scope of the appended claims.

[0018] Features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments and may be combined with or substituted for features in the other embodiments.

[0019] It should be noted that in this text, the term "including / having" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief description of the drawings]

[0020] Elements and features depicted in one drawing and one embodiment of the present invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may designate corresponding elements in multiple drawings and may designate corresponding elements used in more than one embodiment. [Figure 1] FIG. 1 is a schematic diagram of a multi-TRP scenario. [Diagram 2] 2 is a schematic diagram of two PDSCH transmission occasions; [Diagram 3] 1 is a schematic diagram of a communication system according to an embodiment of the present invention. [Figure 4] 1 is a schematic diagram of an example of an information receiving method according to an embodiment of the present invention; [Diagram 5] 2 is a schematic diagram of a PDSCH transmission occasion according to an embodiment of the present invention; [Figure 6A] 2 is a schematic diagram of a PDSCH transmission occasion according to an embodiment of the present invention; [Figure 6B] 2 is a schematic diagram of a PDSCH transmission occasion according to an embodiment of the present invention; [Figure 7A] 2 is a schematic diagram of a PDSCH transmission occasion according to an embodiment of the present invention; [Figure 7B] 2 is a schematic diagram of a PDSCH transmission occasion according to an embodiment of the present invention; [Figure 8A] 2 is a schematic diagram of a PDSCH transmission occasion according to an embodiment of the present invention; [Figure 8B] 2 is a schematic diagram of a PDSCH transmission occasion according to an embodiment of the present invention; [Figure 9] 1 is a schematic diagram of an example of an information transmission method according to an embodiment of the present invention; [Figure 10] 2 is a schematic diagram of an example of an information feedback method according to an embodiment of the present invention; [Figure 11] 1 is a schematic diagram of an example of an information receiving device according to an embodiment of the present invention; [Figure 12] 1 is a schematic diagram of an example of an information transmitting device according to an embodiment of the present invention; [Figure 13]1 is a schematic diagram of an example of an information feedback device according to an embodiment of the present invention; [Figure 14] 1 is a schematic diagram of a network device according to an embodiment of the present invention; [Figure 15] FIG. 2 is a schematic diagram of a terminal device according to an embodiment of the present invention. [Figure 16A] FIG. 13 is a schematic diagram of candidate PDSCH reception occasions when time domain bundling is configured. [Figure 16B] FIG. 13 is a schematic diagram of candidate PDSCH reception occasions when time domain bundling is not configured; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be adopted are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims. Each embodiment of the present invention will be described below with reference to the drawings. These embodiments are merely illustrative and do not limit the present invention.

[0022] In embodiments of the present invention, the terms "first", "second", etc. are used in the title to distinguish different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "including", "comprising", "having", etc. refer to the presence of listed features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0023] In the embodiments of the present invention, the singular forms "a", "the", etc., include the plural forms and should be understood broadly as "one kind" or "a class", and are not limited to "one". In addition, the term "said" should be understood to include both the singular and the plural forms, unless the context clearly indicates otherwise. In addition, the term "described in" should be understood to mean "described at least in part", and the term "based on" should be understood to mean "based at least in part on", unless the context clearly indicates otherwise.

[0024] In an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as, for example, Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0025] Additionally, communications between devices in a communication system may occur according to any stage of communication protocols, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G, New Radio (NR), and / or other currently known or future developed communication protocols.

[0026] In the embodiment of the present invention, the term "network device" refers to a device in a communication system, for example, allowing a terminal device to access the communication system and providing a service to the terminal device. The network device may include, but is not limited to, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0027] Here, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), etc., as well as a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay, or a low power node (e.g., femto, pico, etc.). Also, the term "base station" may include some or all of these functions, and each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and / or its coverage area depending on the context in which the term is used.

[0028] In the embodiment of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to an apparatus that accesses a communication network and receives a network service via, for example, a network device. The terminal apparatus may be fixed or mobile, and may be called a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.

[0029] Here, the terminal device may include, but is not limited to, a cellular phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a smartphone, a smart watch, a digital camera, and the like.

[0030] Also, for example, in a scenario such as the Internet of Things (IoT), the user equipment may be a monitoring or measuring instrument or device, and may include, but is not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, an industrial wireless device, a surveillance camera, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, and the like.

[0031] Furthermore, the term "network side" or "network device side" refers to the side of a network, which may be a base station or may include one or more of the network devices mentioned above. The term "user side" or "terminal side" or "terminal device side" refers to the side of a user or terminal, which may be a UE or may include one or more of the terminal devices mentioned above. In this specification, unless otherwise specified, "device" may refer to a network device or may refer to a terminal device.

[0032] In the embodiment of the present invention, the time unit may be a subframe, a slot, or a set including at least one time domain symbol. The set of at least one time domain symbol may be referred to as a mini-slot or a non-slot. For example, the subframe and the slot in the embodiment of the present invention may be replaced with each other, and the "slot" may be replaced with the "subframe". The present invention is not limited thereto, and the "slot" is described below as an example for convenience of explanation, but may be replaced with other time units. In addition, the terms "time domain resource" and "resource" may be replaced with each other.

[0033] In the following description, unless confusion arises, the terms "uplink control signal" and "uplink control information (UCI)" or "Physical Uplink Control Channel (PUCCH)" may be interchanged, and the terms "uplink data signal" and "uplink data information" or "Physical Uplink Shared Channel (PUSCH)" may be interchanged.

[0034] The terms "downlink control signal" and "downlink control information (DCI)" or "Physical Downlink Control Channel (PDCCH)" may be interchanged, and the terms "downlink data signal" and "downlink data information" or "Physical Downlink Shared Channel (PDSCH)" may be interchanged.

[0035] Also, transmitting or receiving a PUSCH may be understood as transmitting or receiving uplink data carried by the PUSCH, transmitting or receiving a PUCCH may be understood as transmitting or receiving uplink information (e.g., UCI) carried by the PUCCH, transmitting or receiving a PRACH may be understood as transmitting or receiving a preamble carried by the PRACH, transmitting or receiving a PDSCH may be understood as transmitting or receiving downlink data carried by the PDSCH, and transmitting or receiving a PDCCH may be understood as transmitting or receiving downlink information (e.g., DCI) carried by the PDCCH.

[0036] In the embodiment of the present invention, the higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, and may be, for example, referred to as an RRC message, and may include, for example, a Master Information Block (MIB), system information, and a dedicated RRC message, or may be, for example, referred to as an RRC information element (RRC IE). The higher layer signaling may be, for example, a Medium Access Control (MAC) signaling, and may be, for example, referred to as a MAC control element (MAC CE). However, the present invention is not limited thereto.

[0037] The following describes an embodiment scenario of the present invention with reference to an example, but the present invention is not limited thereto.

[0038] Fig. 3 is a schematic diagram of a communication system according to an embodiment of the present invention, and shows an example of a terminal device and a network device. As shown in Fig. 3, a communication system 100 may include a network device 101 and terminal devices 102 and 103. For convenience of explanation, Fig. 3 shows an example of two terminal devices and one network device, but the embodiment of the present invention is not limited thereto.

[0039] In the embodiment of the present invention, existing services or services that can be implemented in the future can be performed between the network device 101 and the terminal devices 102 and 103. For example, these services include, but are not limited to, enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC).

[0040] 3 shows that both of the two terminal devices 102 and 103 are located within the coverage area of ​​the network device 101, but the present invention is not limited to this. Both of the two terminal devices 102 and 103 may not be located within the coverage area of ​​the network device 101, or one of the terminal devices 102 may be located within the coverage area of ​​the network device 101 and the other terminal device 103 may be located outside the coverage area of ​​the network device 101.

[0041] In an embodiment of the present invention, the transport blocks carried by different PDSCHs are the same or different. Therefore, in the following, "multiple PDSCHs (more than one PDSCH)" or "at least two PDSCHs" refers to different PDSCHs carrying different transport blocks. More specifically, the transport blocks carried by different PDSCHs may correspond to the same or different HARQ processes, where the different HARQ processes are identified by different HARQ process identifiers.

[0042] In some embodiments, a PDSCH time domain resource allocation (TDRA) table (also referred to as a TDRA table) includes at least one row. Hereinafter, for convenience of description, one row is referred to as one PDSCH TDRA configuration (also referred to as a TDRA configuration), that is, the PDSCH TDRA table includes at least one PDSCH TDRA configuration. One PDSCH TDRA configuration includes at least one PDSCH time domain resource configuration (also referred to as a time domain resource configuration), and the PDSCH time domain resource configuration includes at least a symbol position in a slot (start symbol + length) configuration. In addition, one PDSCH TDRA configuration may further include at least one slot offset K0 configuration, where K0 represents a slot offset between the PDSCH and the PDCCH, and the K0 configuration is included in the PDSCH time domain resource configuration or is not included in the PDSCH time domain resource configuration. The one PDSCH TDRA configuration may further include other information, which may be included in the PDSCH time domain resource configuration or may not be included in the PDSCH time domain resource configuration. The embodiment of the present invention is not limited thereto. Here, the symbol position configuration in the slot may include, for example, a start and length indicator SLIV, which corresponds to a valid combination of a starting symbol (S) and a length (L), or may correspond to, for example, a starting symbol configuration and a length configuration, which is a valid combination.

[0043] The following describes a method for supporting a repetitive transmission scheme of multiple TRPs when supporting multi-PDSCH scheduling with reference to embodiment 1 and embodiment 2. With reference to embodiment 3, a HARQ feedback method for the repetitive transmission scheme of multiple TRPs and / or multi-PDSCH scheduling is described.

[0044] <Example 1> The embodiment of the present invention provides an information receiving method, which is described from the terminal device side.

[0045] 4 is a schematic diagram of an example of an information receiving method according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps:

[0046] Step 401: A terminal device receives downlink control information for scheduling a PDSCH sent by a network device, the downlink control information indicating a first number of TCI states, where the first number is an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information include multiple SLIVs.

[0047] Step 402: The terminal device receives one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

[0048] In some embodiments, the network device may pre-configure a set of channel condition associations through higher layer signaling, with each association identified by one TCI state. A maximum of 128 groups of TCI states may be configured for the PDSCH channel, and a maximum of 64 groups of TCI states may be configured for the PDCCH channel. Each TCI state includes parameters configuring an approximate positional relationship between a DMRS antenna port in the PDSCH / PDCCH and a downlink reference signal (DL RS), which may be a CSI-RS or an SSB. The terminal device dynamically evaluates the PDCCH / PDSCH channel transmission conditions based on the TCI states.

[0049] In some embodiments, the DCI received in step 401 is DCI format 1_1.

[0050] In some embodiments, the DCI received in step 401 may include a TCI field that may include an index value that may correspond to a first number of TCI states in a predefined TCI state table, the first number being an integer greater than one.

[0051] In some embodiments, the DCI may include a first information field. The first information field may be a time domain resource assignment field. The first information field indicates a PDSCH time domain resource by indicating an index (row index, e.g., the value of row index is equal to or greater than 1) corresponding to a PDSCH TDRA configuration in a PDSCH TDRA table that applies to the DCI. In other words, the DCI schedules a PDSCH by indicating a PDSCH TDRA configuration in a PDSCH TDRA table that applies to the DCI, hereinafter referred to as a DCI-scheduled PDSCH, i.e., a PDSCH indicated by a DCI. For example, a value m (assuming m is an integer equal to or greater than 0) of the first information field of the DCI corresponds to a PDSCH TDRA configuration whose index is m+1 (i.e., the m+1-th row) in a PDSCH TDRA table that applies to the DCI.

[0052] In some embodiments, a PDSCH TDRA table may be predefined or configured by higher layer signaling, and the table supports scheduling multiple PDSCHs via one DCI, i.e., one or more rows in the table include multiple time domain resource configurations (SLIVs), for example, supporting scheduling multiple PDSCHs via one DCI, where a DCI may indicate / schedule one PDSCH (e.g., the row of the TDRA table indicated by the first information field in the DCI includes only one SLIV) or indicate / schedule multiple PDSCHs (e.g., the row of the TDRA table indicated by the first information field in the DCI includes multiple SLIVs) when applying the table.

[0053] In some embodiments, to support mutli-PDSCH scheduling over one DCI, RRC signaling (e.g., pdsch-TimeDomainAllocationListForMultiPDSCH or pdsch-TimeDomainAllocationListForMultiPDSCH-r17) may support configuring a TDRA table for supporting scheduling multiple (i.e., more than one) PDSCHs over one DCI. The TDRA table includes at least one time domain resource allocation configuration for scheduling multiple (more than one) PDSCHs / PUSCHs, and the time domain resource allocation configuration includes, for example, multiple SLIVs, each SLIV corresponding to one PDSCH / PUSCH.

[0054] In some embodiments, when the above TDRA table is configured, the TDRA table applies / supports DCI format 1_1.

[0055] In some embodiments, the terminal device determines a first number of PDSCH transmission occasions for each PDSCH among the PDSCHs scheduled by the downlink control information. Each PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. The terminal device receives or does not receive a PDSCH at each PDSCH transmission occasion. The following exemplarily describes a method for determining the first number of PDSCH transmission occasions and whether to receive or not receive a PDSCH at each PDSCH transmission occasion.

[0056] In some embodiments, the DCI indicates / schedules a plurality of PDSCHs, each PDSCH of the plurality of PDSCHs corresponding to a first number of PDSCH transmission occasions, the first number of PDSCH transmission occasions corresponding to one PDSCH carrying the same transport block and corresponding to a first number of TCI states, respectively. The number of symbols of each PDSCH transmission occasion of the first number of PDSCH transmission occasions is the same. A first PDSCH transmission occasion of the first number of PDSCH transmission occasions is determined based on a time domain resource configuration (e.g., SLIV) corresponding to the one PDSCH indicated / scheduled by the DCI, and a first symbol of a next PDSCH transmission occasion is determined based on an offset value relative to the last symbol of the first PDSCH transmission occasion. Specifically, the first symbol starts after the offset value symbols from the last symbol of the first PDSCH transmission occasion. The offset value may be configured by radio resource control RRC signaling (StartingSymbolOffsetK) and defaults to 0 if not configured.

[0057] FIG. 5 is a schematic diagram of PDSCH transmission occasions. As shown in FIG. 5, take the first number equal to 2 as an example, DCI indicates two TCI states and indicates / schedules two PDSCHs (shown by arrows in FIG. 4), and each PDSCH corresponds to two PDSCH transmission occasions. The two PDSCH transmission occasions correspond to the two indicated TCI states, i.e., can be regarded as corresponding to TRP1 and TRP2, respectively. The number of symbols of the second PDSCH transmission occasion is the same as the number of symbols of the first PDSCH transmission occasion, and its first symbol is determined based on an offset value from the last symbol of the first PDSCH transmission occasion. Specifically, its first symbol starts after the offset value symbols from the last symbol of the first PDSCH transmission occasion. The offset value=1.

[0058] In some embodiments, in step 402, the terminal device determines whether to receive each PDSCH among the multiple PDSCHs indicated / scheduled by the DCI. The terminal device may determine whether to receive a PDSCH at each PDSCH transmission occasion (in other words, whether to receive the transmission occasion of the corresponding PDSCH) based on whether each PDSCH transmission occasion collides with a semi-statically configured uplink symbol. Collision between a PDSCH transmission occasion and a semi-statically configured uplink symbol means that at least one of the symbols corresponding to the PDSCH transmission occasion overlaps with a semi-statically configured uplink symbol, in other words, at least one of the symbols corresponding to the PDSCH transmission occasion is semi-statically configured as an uplink symbol. Non-collision between a PDSCH transmission occasion and a semi-statically configured uplink symbol means that none of the symbols corresponding to the PDSCH transmission occasion overlaps with a semi-statically configured uplink symbol, in other words, none of the symbols corresponding to the PDSCH transmission occasion is semi-statically configured as an uplink symbol.

[0059] In some embodiments, as an example 1, if there is a PDSCH transmission occasion that collides with a semi-statically configured uplink symbol for a PDSCH, the terminal device does not receive the PDSCH, and if there is no PDSCH transmission occasion that collides with a semi-statically configured uplink symbol for a PDSCH, the terminal device receives the PDSCH. If any of the PDSCH transmission occasions corresponding to a PDSCH collides with a semi-statically configured uplink symbol, the terminal device does not receive the PDSCH (in other words, does not receive all of the first few PDSCH transmission occasions corresponding to the PDSCH, or in other words, does not receive the first few PDSCH transmission occasions). In the opposite case, if none of the PDSCH transmission occasions corresponding to a PDSCH collides with a semi-statically configured uplink symbol, the terminal device receives the PDSCH (in other words, receives the PDSCH in the first few PDSCH transmission occasions corresponding to the PDSCH).

[0060] 6A and 6B are schematic diagrams of PDSCH transmission occasions. As shown in FIG. 6A and FIG. 6B, if one (the second) PDSCH transmission occasion of the two PDSCH transmission occasions corresponding to the first PDSCH indicated / scheduled by DCI collides with a semi-statically configured uplink symbol, the first PDSCH is not received (in other words, not received at all in the two PDSCH transmission occasions corresponding to the first PDSCH). If neither PDSCH transmission occasion corresponding to the second PDSCH indicated / scheduled by DCI collides with a semi-statically configured uplink symbol, the PDSCH is received (in other words, the PDSCH is received at the two PDSCH transmission occasions corresponding to the second PDSCH).

[0061] In some embodiments, as an example 2, if there is a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for a PDSCH, the terminal device receives the PDSCH, for example, the terminal device receives the PDSCH at a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol. If there is no PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for a PDSCH, the terminal device does not receive the PDSCH. If any of the PDSCH transmission occasions corresponding to a PDSCH do not collide with a semi-statically configured uplink symbol, the terminal device receives the PDSCH (in other words, receives the PDSCH at a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol corresponding to the PDSCH, or receives a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol). Conversely, if any PDSCH transmission occasions corresponding to the PDSCH collide with a semi-statically configured uplink symbol, the PDSCH is not received (in other words, the first few PDSCH transmission occasions corresponding to the PDSCH are not received at all, or in other words, the first few PDSCH transmission occasions are not received).

[0062] 7A and 7B are schematic diagrams of PDSCH transmission occasions. As shown in FIG. 7A and FIG. 7B, when one (the second) PDSCH transmission occasion of two PDSCH transmission occasions corresponding to the first PDSCH indicated / scheduled by DCI collides with a semi-statically configured uplink symbol, the first PDSCH is received (in other words, the first PDSCH is received at the first PDSCH transmission occasion corresponding to the first PDSCH, and not received at the second PDSCH transmission occasion). When one (the first) PDSCH transmission occasion of two PDSCH transmission occasions corresponding to the first PDSCH indicated / scheduled by DCI collides with a semi-statically configured uplink symbol, the first PDSCH is received (in other words, the second PDSCH transmission occasion corresponding to the first PDSCH, and not received at the first PDSCH transmission occasion).

[0063] In some embodiments, as an example 3, if the first PDSCH transmission occasion of a PDSCH does not collide with a semi-statically configured uplink symbol, the terminal device receives the PDSCH, and if the first PDSCH transmission occasion of a PDSCH collide with a semi-statically configured uplink symbol, the terminal device does not receive the PDSCH. If the first PDSCH transmission occasion corresponding to a PDSCH (in other words, the time domain resource configuration (SLIV) of the PDSCH indicated by the DCI) does not collide with a semi-statically configured uplink symbol, the terminal device may receive the PDSCH regardless of whether the subsequent other PDSCH transmission occasions collide with the semi-statically configured uplink symbol (in other words, receive the PDSCH at the first PDSCH transmission occasion or receive a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol). Conversely, if the first PDSCH transmission occasion corresponding to the PDSCH collides with a semi-statically configured uplink symbol, the PDSCH is not received (in other words, the first few PDSCH transmission occasions corresponding to the PDSCH are not received at all, or in other words, the first few PDSCH transmission occasions are not received).

[0064] 8A and 8B are schematic diagrams of PDSCH transmission occasions. As shown in FIG. 8A, if the first PDSCH transmission occasion of the two PDSCH transmission occasions corresponding to the first PDSCH indicated / scheduled by DCI collides with a semi-statically configured uplink symbol, the first PDSCH is not received (in other words, not received at all in the two PDSCH transmission occasions corresponding to the first PDSCH, in other words, not received at the two PDSCH transmission occasions). As shown in FIG. 8B, if the first PDSCH transmission occasion of the two PDSCH transmission occasions corresponding to the first PDSCH indicated / scheduled by DCI does not collide with a semi-statically configured uplink symbol, the first PDSCH is received (in other words, received at the first PDSCH transmission occasion corresponding to the first PDSCH, not received at the second PDSCH transmission occasion).

[0065] In some embodiments, the DCI may further include a second information field, and the second information field (e.g., "HARQ process number") is used to indicate a HARQ process identifier. For each PDSCH among the multiple PDSCHs indicated / scheduled by the DCI, all PDSCHs may have corresponding HARQ processes, or only a part of the PDSCHs may have corresponding HARQ processes. The method may further include, as step S1, a step in which the terminal device determines a HARQ process identifier of the PDSCH scheduled by the DCI. The terminal device may determine whether to assign a HARQ process identifier (HARQ process ID) for the PDSCH based on whether each PDSCH transmission occasion collides with a semi-statically configured uplink symbol. In the following, "process" and "process ID" may be replaced. Note that the method may not include step 202, and may include only step 201 and step S1, but the embodiment of the present invention is not limited thereto.

[0066] In some embodiments, if there is a PDSCH transmission occasion that collides with a semi-statically configured uplink symbol for a PDSCH, the PDSCH does not have a corresponding HARQ process ID, and if there is no PDSCH transmission occasion that collides with a semi-statically configured uplink symbol for a PDSCH, the PDSCH has a corresponding HARQ process ID. If any of the PDSCH transmission occasions corresponding to a PDSCH collides with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process identifier, in other words, the terminal device skips the PDSCH when determining a HARQ process identifier, in other words, does not assign a HARQ process identifier to the PDSCH. Otherwise, the PDSCH has a corresponding HARQ process identifier, in other words, the terminal device does not skip the PDSCH when determining a HARQ process identifier, in other words, assigns a HARQ process identifier to the PDSCH. The HARQ process identifier corresponding to the PDSCH may be determined based on the HARQ process identifier indicated by the DCI, and the details may refer to the prior art, and the description thereof is omitted here. The method may be implemented in combination with the above example 1, for example, as shown in Figures 6A and 6B, the first PDSCH does not have a corresponding HARQ process identifier, and the second PDSCH has a corresponding HARQ process identifier.

[0067] In some embodiments, if there is a PDSCH transmission occasion that does not collide with the semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID, and if there is no PDSCH transmission occasion that does not collide with the semi-statically configured uplink symbol for the PDSCH, the PDSCH does not have a corresponding HARQ process ID. If any of the PDSCH transmission occasions corresponding to the PDSCH does not collide with the semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process identifier, in other words, the terminal device does not skip the PDSCH when determining the HARQ process identifier, in other words, assigns a HARQ process identifier to the PDSCH. The HARQ process identifier corresponding to the PDSCH may be determined based on the HARQ process identifier indicated by the DCI, and details may refer to the prior art, and the description thereof will be omitted here. Otherwise, the PDSCH does not have a corresponding HARQ process identifier, in other words, the terminal device skips the PDSCH when determining the HARQ process identifier, in other words, does not assign a HARQ process identifier to the PDSCH. The method may be implemented in combination with the above Example 1, Example 2 or Example 3, for example, as shown in Figure 8A, the first PDSCH does not have a corresponding HARQ process identifier, and as shown in Figures 7A, 7B and 8B, the first PDSCH has a corresponding HARQ process identifier.

[0068] In some embodiments, if the first PDSCH transmission occasion of a PDSCH does not collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process ID, and if the first PDSCH transmission occasion of a PDSCH collide with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process ID. If the first PDSCH transmission occasion corresponding to a PDSCH (in other words, the time domain resource configuration (SLIV) of the PDSCH indicated by the DCI) does not collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process ID regardless of whether other subsequent PDSCH transmission occasions collide with a semi-statically configured uplink symbol, in other words, the terminal device does not skip the PDSCH when determining a HARQ process identifier, in other words, assigns a HARQ process identifier to the PDSCH. The HARQ process identifier corresponding to the PDSCH may be determined based on the HARQ process identifier indicated by the DCI, and details may refer to the prior art, and the description thereof will be omitted here. Otherwise, the PDSCH does not have a corresponding HARQ process identifier, in other words, the terminal device skips the PDSCH when determining the HARQ process identifier, in other words, does not assign a HARQ process identifier to the PDSCH. The method may be implemented in combination with the above example 1 or example 3, for example, as shown in Figure 8A, the first PDSCH does not have a corresponding HARQ process identifier, and as shown in Figure 8B, the first PDSCH has a corresponding HARQ process identifier.

[0069] In some embodiments, the DCI indicates / schedules only one PDSCH. A table applied to the DCI supports scheduling multiple PDSCHs (one or more rows of the table include multiple SLIVs) via one DCI. For example, although multiple PDSCHs are supported for scheduling via one DCI, only one PDSCH is indicated / scheduled when the DCI applies the table (e.g., the row of the TDRA table indicated by the first information field in the DCI includes only one SLIV). In other words, even if the DCI format corresponding to the DCI can indicate / schedule multiple PDSCHs, the DCI indicates / schedules only one PDSCH PDSCH, and the one PDSCH PDSCH corresponds to two PDSCH transmission occasions. The terminal device receives the PDSCH in the first number of PDSCH transmission occasions, or the terminal device receives the PDSCH in one or more PDSCH transmission occasions of the first number of PDSCH transmission occasions depending on whether it collides with a semi-statically configured uplink symbol. In other words, the terminal device can receive two PDSCH transmission occasions, or receive one or more PDSCH transmission occasions depending on whether it collides with a semi-statically configured uplink symbol. For example, the terminal device receives a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol.

[0070] In some embodiments, the terminal device determines the first number of PDSCH transmission occasions for valid PDSCHs among the PDSCHs scheduled by the downlink control information. Each valid PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. The terminal device does not determine the first number of PDSCH transmission occasions for invalid PDSCHs among the PDSCHs scheduled by the downlink control information. The terminal device receives or does not receive a PDSCH at each PDSCH transmission occasion. In other words, only valid PDSCHs have corresponding PDSCH transmission occasions, and invalid PDSCHs have no corresponding PDSCH transmission occasions. Here, similarly applying Example 3 above, assuming that the first PDSCH is determined to be valid, the first PDSCH corresponds to two PDSCH transmission occasions, and the terminal device receives the first PDSCH at the first PDSCH transmission occasion corresponding to the first PDSCH, and does not receive the first PDSCH at the second PDSCH transmission occasion corresponding to the first PDSCH.

[0071] In some embodiments, the DCI indicates / schedules only one valid PDSCH, and the valid PDSCH is a PDSCH whose corresponding time domain resource configuration (e.g., SLIV) does not collide with an uplink symbol that is semi-statically configured. The DCI can schedule one or more PDSCHs, of which there is only one valid PDSCH. For example, a table applied to the DCI supports scheduling multiple PDSCHs via one DCI (one or more rows of the table include multiple SLIVs). For example, a table supports scheduling multiple PDSCHs via one DCI, but indicates / schedules only one PDSCH when the DCI applies the table (e.g., the row of the TDRA table indicated by the first information field in the DCI includes only one SLIV), and the one PDSCH is a valid PDSCH. Or, a table is applied to the DCI indicates / schedules multiple PDSCHs, and the multiple PDSCHs include only one valid PDSCH. In other words, even if the DCI format corresponding to the DCI can indicate / schedule multiple PDSCHs, the DCI indicates / schedules only one valid PDSCH.

[0072] In some embodiments, the valid PDSCH corresponds to two PDSCH transmission occasions. In other words, the terminal device determines whether to apply the multi-TRP repetition transmission scheme "tdmSchemeA" based on the number of valid PDSCHs indicated / scheduled in the DCI. If the number of valid PDSCHs is one, the multi-TRP repetition transmission scheme "tdmSchemeA" is applied. The terminal device receives the valid PDSCH in the first number of PDSCH transmission occasions, or the terminal device receives the valid PDSCH in one or more PDSCH transmission occasions of the first number of PDSCH transmission occasions depending on whether it collides with a semi-statically configured uplink symbol, for example, receives the valid PDSCH in a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol. In other words, the terminal device may receive two PDSCH transmission occasions, or may receive one or more PDSCH transmission occasions depending on whether it collides with a semi-statically configured uplink symbol. For example, receiving PDSCH transmission occasions that do not collide with semi-statically configured uplink symbols.

[0073] In some embodiments, the first number of PDSCH transmission occasions includes a first PDSCH transmission occasion and a second PDSCH transmission occasion, and the method may further include the following steps (not shown): The terminal device determines a set of candidate PDSCH reception occasions based on a symbol corresponding to the first PDSCH transmission occasion and / or a symbol corresponding to the second PDSCH transmission occasion and / or based on a first allocation table. The first allocation table is related to an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion. The terminal device generates and transmits a HARQ-ACK codebook. The codebook includes HARQ-ACK information corresponding to the set of candidate PDSCH reception occasions. In other words, the terminal device generates and transmits HARQ feedback information for PDSCHs received or not received in step 402 to a network device. The method of generating and transmitting the feedback information is described in the third embodiment, and the description thereof is omitted here. In other words, the first embodiment and the third embodiment may be implemented alone or in combination, and the embodiments of the present invention are not limited thereto.

[0074] According to this embodiment, even if one DCI supports scheduling of multiple PDSCHs, a multi-TRP repetition scheme can be supported, so that the number of times the terminal device monitors the PDCCH can be reduced, thereby reducing the complexity and power consumption of the terminal device monitoring the PDCCH, and the resource overhead for transmitting downlink control signaling (DCI) can be reduced, thereby improving data throughput.

[0075] <Example 2> The embodiment of the present invention provides an information transmission method, which is described from the network device side.

[0076] 9 is a schematic diagram of an example of an information transmission method according to an embodiment of the present invention. As shown in FIG. 9, the method includes the following steps:

[0077] Step 901: A network device sends downlink control information for scheduling a PDSCH to a terminal device, the downlink control information indicating a first number of TCI states, where the first number is an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information include multiple SLIVs.

[0078] Step 902: The network device transmits one or more PDSCHs scheduled by the downlink control information.

[0079] In some aspects, steps 901 and 902 correspond to steps 401 and 402 in the first embodiment, and a description of the overlapping contents will be omitted.

[0080] According to this embodiment, even if one DCI supports scheduling of multiple PDSCHs, a multi-TRP repetition scheme can be supported, so that the number of times the terminal device monitors the PDCCH can be reduced, thereby reducing the complexity and power consumption of the terminal device monitoring the PDCCH, and the resource overhead for transmitting downlink control signaling (DCI) can be reduced, thereby improving data throughput.

[0081] <Example 3> The embodiment of the present invention provides an information feedback method and is described from the terminal device side.

[0082] 10 is a schematic diagram of an example of an information feedback method according to an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps:

[0083] Step 1001: The terminal device determines a set of candidate PDSCH receiving occasions based on a symbol corresponding to a first PDSCH transmission occasion and / or a symbol corresponding to a second PDSCH transmission occasion and / or based on a first allocation table, the first allocation table being associated with an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion.

[0084] Step 1002: The terminal device generates and sends a HARQ-ACK codebook, where the HARQ-ACK codebook includes HARQ-ACK information corresponding to the candidate PDSCH receiving occasion set.

[0085] In some embodiments, the terminal device needs to perform HARQ-ACK feedback for the received PDSCH (e.g., PDSCH scheduled by DCI or PDSCH of SPS) or DCI (e.g., DCI for deactivating SPS). The HARQ-ACK feedback information may be carried through a HARQ-ACK codebook (e.g., also referred to as a Type-1 HARQ-ACK codebook or a semi-static HARQ-ACK codebook), and the codebook may include HARQ-ACK information bits of one or more serving cells. The following only describes a method for determining the HARQ-ACK information bits of a serving cell. When the codebook includes HARQ-ACK information bits of multiple serving cells, the method for determining the HARQ-ACK information bits of each serving cell is similar to the above method for determining the HARQ-ACK information bits of one serving cell, and the HARQ-ACK information bits of multiple serving cells are arranged in a certain order in the codebook, but the description thereof is omitted here. Hereinafter, "HARQ-ACK", "HARQ feedback", and "HARQ-ACK feedback" may be interchangeable.

[0086] In some embodiments, the codebook includes HARQ-ACK information bits corresponding to a second number (A) of candidate PDSCH reception occasions, the second number being a natural number, where the second number (A) of candidate PDSCH reception occasions correspond to a same serving cell (i.e., the serving cell), i.e., the second number (A) of candidate PDSCH reception occasions are included in a candidate PDSCH reception occasion set M of the serving cell. A,c In the prior art, since only one PDSCH scheduling by one DCI is supported, each PDSCH TDRA configuration includes only one PDSCH time domain resource configuration, and further, when determining the candidate PDSCH reception occasion set, only the case where each PDSCH TDRA configuration includes only one PDSCH time domain resource configuration (i.e., the configuration of the symbol position (start symbol + length) in the slot, e.g., SLIV) is considered. In addition, the prior art does not consider the same TB repeated transmission scheme (e.g., "tdmSchemeA") in the multi-TRP scenario. In the present invention, in order to support the scheduling of multiple PDSCHs by one DCI and / or the same TB repeated transmission scheme (e.g., "tdmSchemeA") in a multi-TRP scenario, when determining a candidate PDSCH receiving occasion set, the symbol corresponding to the first PDSCH transmission occasion and / or the symbol corresponding to the second PDSCH transmission occasion are considered, and / or the candidate PDSCH receiving occasion set is determined based on a first allocation table related to an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion. By considering the above factors, it is possible to support HARQ information feedback in the case of the scheduling of multiple PDSCHs by one DCI and / or the same TB repeated transmission scheme (e.g., "tdmSchemeA") in a multi-TRP scenario, thereby reducing the burden of PDCCH monitoring by the UE, and reducing power loss and UE complexity. The following will explain each of them.

[0087] In some embodiments, before determining the candidate PDSCH reception occasion, the terminal device needs to determine the HARQ-ACK information feedback timing (in other words, the terminal needs to determine the slot (uplink slot) for transmitting the HARQ-ACK information).

[0088] In some embodiments, the method may further include the following steps (not shown): A terminal device receives a DCI, and the terminal device determines a slot in which HARQ-ACK information needs to be transmitted based on a third information field (PDSCH-to-HARQ_feedback timing indicator field) for indicating HARQ-ACK information feedback timing in the DCI. For example, the DCI may be the DCI in step 401 of the first embodiment, which indicates a first number of TCI states and schedules at least one PDSCH, where the first number is an integer greater than 1. Each PDSCH of the at least one PDSCHs corresponds to a first number of PDSCH transmission occasions. An aspect of the DCI may refer to the first embodiment, and the description thereof will be omitted here.

[0089] In some embodiments, HARQ-ACK information (i.e., HARQ-ACK codebook) is carried by PUCCH or PUSCH. The following describes HARQ-ACK feedback timing by taking HARQ-ACK information carried by PUCCH as an example. Note that, the following PUCCH may be replaced with PUSCH, but the present invention is not limited thereto.

[0090] In some embodiments, the DCI may include a fourth information field, the fourth information field being a HARQ acknowledgement (HARQ-ACK) feedback timing indication (i.e., a PDSCH-to-HARQ_feedback timing indicator) field, and the fourth information field indicating feedback timing k of the HARQ acknowledgement (HARQ-ACK) information. Alternatively, the DCI may not include a fourth information field, and the terminal device receives second configuration information (e.g., dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 for DCI format 1_2) configured by higher layer signaling, and the second configuration information indicates feedback timing k of the HARQ acknowledgement (HARQ-ACK) information. Alternatively, the terminal device receives second configuration information (e.g., dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 HARQ-ACK_2) configured by higher layer signaling, and the second configuration information is used to configure feedback timing k of multiple HARQ acknowledgement (HARQ-ACK) information. The DCI may include a fourth information field, and the second information field indicates feedback timing k of one HARQ acknowledgement (HARQ-ACK) information from the multiple feedback timings configured by the second configuration information.

[0091] For example, HARQ-ACK information corresponding to one or more PDSCHs scheduled by the DCI may be fed back in the same PUCCH, or HARQ-ACK information corresponding to one or more PDSCHs scheduled by the DCI may be fed back in a different (slot) PUCCH.

[0092] For example, HARQ-ACK information for multiple PDSCHs may be fed back in one PUCCH. μDL-μULTaking θ = 1 as an example, the terminal device transmits HARQ-ACK information in a slot with index n + k (slot n + k), where the slot with index n (slot n) is the end slot of the last PDSCH among the multiple PDSCHs, and n and k are integers greater than 0, that is, the end slot of the last PDSCH is n, and k is the offset between the feedback slot of the HARQ-ACK information and slot n. The relationship between the downlink end slot n of the PDSCH and the index of the corresponding uplink slot may be determined based on the subcarrier interval of the uplink and downlink, and the details may refer to the prior art, and the description thereof will be omitted here.

[0093] In some embodiments, after determining the time domain position or slot that needs to feed back HARQ-ACK information, the terminal device may determine candidate PDSCH receiving occasions and generate a corresponding codebook. The following describes a method for determining candidate PDSCH receiving occasions.

[0094] In some embodiments, to determine the set of candidate PDSCH receiving occasions, it is necessary to determine downlink slots that may contain (or correspond to) candidate PDSCH receiving occasions.

[0095] In some embodiments, the downlink slot is determined based on a slot timing value K1.

[0096] For example, the slot in which the HARQ-ACK information needs to be transmitted, e.g., slot n u Based on a set of slot timing values ​​K1 associated with the activated uplink fractional bandwidth UL BWP, one or more downlink slots n corresponding to each K1 in the set of K1 are D where K1 is the HARQ-ACK information feedback slot n DIt represents the offset value of the PDSCH with respect to each K1. When determining one or more downlink slots corresponding to each K1, preferably, the subcarrier interval of the partial bandwidth of the uplink and downlink may be further considered, and one K1 may correspond to multiple downlink slots. For details, please refer to the prior art, and the embodiments of the present invention are not limited thereto.

[0097] In some embodiments, the determination of the set of K1 associated with the activated uplink partial bandwidth UL BWP may refer to the prior art. For example, d For each downlink slot, determine a PDSCH time domain resource configuration corresponding to the slot (downlink slot), and determine whether the slot has a corresponding candidate PDSCH receiving occasion, thereby determining a candidate PDSCH receiving occasion set. Note that, the above determination of each downlink slot and the determination of the PDSCH time domain resource configuration corresponding to the slot may be performed sequentially or simultaneously, and the present invention is not limited thereto.

[0098] For example, in the prior art, when determining whether there is a corresponding candidate PDSCH reception occasion, only consider whether the PDSCH time domain resource configuration (e.g., SLIV configuration) collides with a semi-statically configured uplink symbol. The following description will be made with reference to Figures 16A and 16B.

[0099] As shown in FIG. 16A, when time domain bundling is configured for the HARQ feedback codebook (e.g., enableTimeDomainHARQ-Bundling is conveyed via RRC signaling and the HARQ feedback codebook enables time domain bundling), reserve a row in the TDRA table if the row contains a SLIV that does not collide with the semi-static configuration. In other words, reserve the corresponding candidate PDSCH reception occasion if at least one row in the TDRA table contains a SLIV that does not collide with the semi-static configuration. HARQ feedback slot n u Assume that the TDRA table has only two rows, row 0 and row 1, where row 0 includes two PDSCH time domain resource configurations SLIV 0_0, SLIV 0_1, row 1 includes three PDSCH time domain resource configurations SLIV 1_0, SLIV 1_1, SLIV 1_2, and the K1 set includes {1, 2}, where symbols in slots Slot n-2,n are all uplink symbols (semi-static configuration), some symbols in slot Slot n-1 are uplink symbols and some symbols are downlink (DL) symbols, and symbols in the remaining slots are all downlink (DL) symbols. Thus, for K1=1, SLIV0_1 and SLIV1_0 are valid PDSCHs, and for K1=2, SLIV0_0, SLIV1_0, and SLIV1_1 are valid PDSCHs, in which case there is a candidate PDSCH receiving occasion 1 corresponding to K1=1 and a candidate PDSCH receiving occasion 0 corresponding to K1=2, respectively.

[0100] As shown in FIG. 16B, when time domain bundling is not configured for the HARQ feedback codebook, the HARQ feedback slot n uAssume that the TDRA table has only two rows, row 0 and row 1, where row 0 includes two PDSCH time domain resource configurations SLIV 0_0 and SLIV 0_1, row 1 includes three PDSCH time domain resource configurations SLIV 1_0, SLIV 1_1, and SLIV 1_2, and the set K1 includes {1, 2} and may further include {3, 4} by extension of the prior art, where all symbols in slots Slot n-2,n are uplink symbols (semi-static configuration), some symbols in slot Slot n-1 are uplink symbols and some symbols are downlink (DL) symbols, and all symbols in the remaining slots are downlink (DL) symbols. Therefore, for K1=1 (slot n-1), SLIV0_1 is a valid PDSCH, for K1=2 (slot n-2), there is no valid PDSCH, for K1'=3 (slot n-3), SLIV0_0 and SLIV1_1 are valid PDSCH, and for K1'=4 (slot n-4), SLIV0_1 is a valid PDSCH. In this case, there are candidate PDSCH receiving occasions 2 corresponding to K1=1, 1 corresponding to K1'=3, and 0 corresponding to K1'=4.

[0101] Unlike the prior art, the present invention may further take into account symbols corresponding to the first PDSCH transmission occasion and / or symbols corresponding to the second PDSCH transmission occasion and / or may perform processing based on a first allocation table relating to an offset value between the first and second PDSCH transmission occasions.

[0102] In some embodiments, the first PDSCH transmission occasion and the second PDSCH transmission occasion correspond to the same PDSCH of the at least one PDSCH scheduled by the DCI. For example, if each PDSCH of the at least one PDSCH is associated with a first number of PDSCH transmission occasions, the first PDSCH transmission occasion of the first number of PDSCHs is referred to as the first PDSCH transmission occasion, and the second or last PDSCH transmission occasion of the first number of PDSCHs is referred to as the second PDSCH transmission occasion. The first PDSCH transmission occasion and the second PDSCH transmission occasion correspond to different TCI states (TRPs) but carry the same TB. The first PDSCH transmission occasion is determined based on the SLIV indicated by the DCI, and the second PDSCH transmission occasion is determined based on the first PDSCH transmission occasion and an offset value. For example, the offset value is a time domain offset value between the last symbol of the first PDSCH transmission occasion and the first symbol of the second PDSCH transmission occasion. The method of determining the offset value may refer to the first embodiment, and the description thereof is omitted here.

[0103] In some embodiments, to support scheduling multiple PDSCHs via one DCI and / or a repetitive transmission scheme of the same TB in a multi-TRP scenario (e.g., "tdmSchemeA"), a slot (downlink slot) is determined to have a corresponding candidate PDSCH reception occasion based on whether a symbol corresponding to a first PDSCH transmission occasion and / or a second PDSCH transmission occasion of a PDSCH time domain resource configuration corresponding to the slot collides with a semi-statically configured uplink symbol. For example, if a symbol corresponding to a first PDSCH transmission occasion and / or a second PDSCH transmission occasion collides with a semi-statically configured uplink symbol, it is determined that there is no candidate PDSCH reception occasion corresponding to the slot, and otherwise it is determined that there is a corresponding candidate PDSCH reception occasion.

[0104] In some embodiments, the first allocation table is used to determine candidate PDSCH reception occasions and / or is used to schedule the PDSCH.

[0105] In some embodiments, the PDSCH TDRA configuration and / or the index corresponding to the configuration may be included in a first allocation table. For example, the first allocation table may be determined based on an applicable PDSCH TDRA table (which supports scheduling multiple PDSCHs via one DCI, and details may refer to embodiment 1) for each DCI format, and the PDSCH time domain resource configuration may be determined based on the first allocation table. The first allocation table is also associated with the activated DL BWP. The first allocation table is a union of time domain resource allocation tables of DCI formats that need to be monitored that are configured in the serving cell c by the terminal device. For example, the first allocation table may include a union of all rows of the PDSCH TDRA table that apply to the DCI formats that need to be monitored, and the configuration of each row is the same as the PDSCH TDRA table, for example, for a specific activated DL BWP, Table 1 is an example of the first allocation table, and as shown in Table 1 below, one PDSCH TDRA configuration (corresponding to one row of the first allocation table) includes at least one PDSCH time domain resource configuration, and the PDSCH time domain resource configuration includes at least a symbol position in a slot (start symbol + length) configuration. Also, preferably, one PDSCH TDRA configuration may further include at least one slot offset K0 configuration, where K0 represents the slot offset of PDSCH and PDCCH. Also, one PDSCH TDRA configuration may further include other information (e.g., a mapping scheme), and the other information configuration is included in the PDSCH time domain resource configuration or is not included in the PDSCH time domain resource configuration. Also, when ReferenceofSLIV-ForDCIFormat1_2 is configured for the terminal device, it is necessary to add a new row based on the PDSCH TDRA table of DCI format 1_2. Here, an example is omitted, and the details may refer to the prior art.

[0106] [Table 1] In some embodiments, the first allocation table (Table 1) may be expanded based on the offset value, for example, by taking each existing SLIV in the first allocation table as a first PDSCH transmission occasion, determining a second PDSCH transmission occasion corresponding to each SLIV based on the offset value, and adding the second PDSCH transmission occasion to the first allocation table (such as adding a row index and / or adding a SLIV corresponding to each row).

[0107] In some embodiments, the candidate PDSCH receiving occasion is determined based on whether the PDSCH time domain resource configuration (e.g., SLIV) of each row in the extended first allocation table (the first allocation table extended based on the offset value, in other words, the first allocation table is related to the offset value) collides with an uplink symbol. For example, when time domain bundling is configured, for one K1, when the SLIV of at least one row in the first allocation table does not collide with a semi-statically configured uplink symbol, it is determined that there is a corresponding candidate PDSCH receiving occasion, and otherwise, it is determined that there is no corresponding candidate PDSCH receiving occasion. Since the SLIV of the at least one row may be a first PDSCH transmission occasion and may be a second PDSCH transmission occasion, it may be considered that if the symbol of the at least one first PDSCH transmission occasion and / or the second PDSCH transmission occasion does not collide with a semi-statically configured uplink symbol, it is determined that there is a corresponding candidate PDSCH reception occasion, and if not, it is determined that there is no corresponding candidate PDSCH reception occasion. If time domain bundling is not configured, if at least one SLIV corresponding to a slot corresponding to one K1 in the first allocation table does not collide with a semi-statically configured uplink symbol, it is determined that there is a corresponding candidate PDSCH reception occasion, and if not, it is determined that there is no corresponding candidate PDSCH reception occasion.

[0108] Alternatively, instead of extending the first allocation table based on the offset value, each existing SLIV in the first allocation table may be a first PDSCH transmission occasion, and a candidate PDSCH reception occasion may be determined based on whether the PDSCH time domain resource configuration (e.g., SLIV) of each row in the first allocation table that is not extended based on the offset value collides with an uplink symbol. For example, when time domain bundling is configured, for one K1, when the SLIV of at least one row in the first allocation table that is not extended based on the offset value does not collide with a semi-statically configured uplink symbol, it is determined that there is a corresponding candidate PDSCH reception occasion, and otherwise, it is determined that there is no corresponding candidate PDSCH reception occasion. Since each SLIV corresponds to a first PDSCH transmission occasion, it may be considered that when the symbol of at least one first PDSCH transmission occasion does not collide with a semi-statically configured uplink symbol, it is determined that there is a corresponding candidate PDSCH reception occasion, and otherwise, it is determined that there is no corresponding candidate PDSCH reception occasion. When time domain bundling is not configured, when at least one SLIV corresponding to a slot corresponding to one K1 in the first allocation table that is not extended based on an offset value does not collide with a semi-statically configured uplink symbol, it is determined that there is a corresponding candidate PDSCH receiving occasion, and otherwise it is determined that there is no corresponding candidate PDSCH receiving occasion.

[0109] In some embodiments, after determining the candidate PDSCH receiving occasion set in step 1002, further generate a HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH receiving occasion set. The following further describes a method for generating the codebook based on the candidate PDSCH receiving occasion set.

[0110] In some embodiments, the size of the codebook does not change dynamically according to the actual data scheduling situation, but is pre-configured (e.g., configured by higher layer signaling) or determined based on a pre-defined parameter. The following only describes how to determine the HARQ-ACK information bit of the serving cell.

[0111] In some embodiments, when time domain bundling is not configured, the number of HARQ-ACK information bits corresponding to the candidate PDSCH reception occasions of the serving cell is related to the HARQ spatial bundling parameters (harq-ACK-SpatialBundlingPUCCH), the code block group (CBG) configuration parameters (PDSCH-CodeBlockGroupTransmission), and the maximum supported words parameter (maxNrofCodeWordsScheduledByDCI) configured by the cell. As an example, Table 2 below shows the HARQ-ACK information feedback in PUCCH.

[0112] [Table 2] The above is merely an example, and the method of determining the number of bits and the bit value of the HARQ-ACK information corresponding to the candidate PDSCH reception occasion of the serving cell is not limited to this. For example, when time domain bundling is configured, the logical sum of the bit values ​​of the HARQ feedback information corresponding to the (valid) PDSCH related to the candidate PDSCH reception occasion may be obtained, and the value of the logical sum may be set as the bit value of the HARQ-ACK information corresponding to the candidate PDSCH reception occasion. When there is no PDSCH corresponding to the candidate PDSCH reception occasion, the bit value of the corresponding HARQ-ACK information may be set to NACK. Here, the description is omitted. As shown in FIG. 16A, the bit value of the HARQ-ACK information corresponding to the candidate PDSCH reception occasion 0 is the logical sum of the bit values ​​of the HARQ-ACK information corresponding to SLIV 1_0 and SLIV 1_1, and the bit value of the HARQ-ACK information corresponding to the candidate PDSCH reception occasion 0 is NACK. As shown in FIG. 16B, the bit value of the HARQ-ACK information corresponding to candidate PDSCH reception occasion 0 is the bit value of the HARQ-ACK information of the PDSCH corresponding to SLIV 1_0, the bit value of the HARQ-ACK information corresponding to candidate PDSCH reception occasion 1 is the bit value of the HARQ-ACK information of the PDSCH corresponding to SLIV 1_1, and the bit value of the HARQ-ACK information corresponding to candidate PDSCH reception occasion 2 is NACK.

[0113] In some embodiments, since one candidate PDSCH reception occasion corresponds to one PDSCH, the HARQ-ACK information bits corresponding to each candidate PDSCH reception occasion are rearranged in the order of the second number of candidate PDSCH reception occasions in the candidate PDSCH reception occasion set, and the HARQ-ACK information bit of one serving cell is obtained. As described above, when the codebook includes the HARQ-ACK information bit of one serving cell, the HARQ-ACK information bit of the one serving cell is fed back as a codebook, and when the codebook includes the HARQ-ACK information bits of multiple serving cells, the method of determining the HARQ-ACK information bit of each serving cell is the same as the method of determining the HARQ-ACK information bit of one serving cell, but when specifically determining, other parameters such as the PDSCH TDRA configuration corresponding to each serving cell may be the same or different. For example, the above parameters may be configured individually for each serving cell, but the embodiment is not limited thereto. The HARQ-ACK information bits corresponding to each serving cell may be sequentially sorted in ascending order of the serving cell index to generate a codebook for feedback.

[0114] In addition, the method may further include the following steps: A terminal device receives higher layer signaling sent by a network device, and the higher layer signaling (e.g., a repetitionScheme parameter in RRC signaling) is used to configure a repetition transmission scheme of the same TB (e.g., to "tdmSchemeA") in a multi-TRP scenario. In other words, the aspect in step 1001 is used when determining a candidate PDSCH receiving occasion set only when "tdmSchemeA" and / or multi-PDSCH scheduling is configured for the terminal device, but the embodiment of the present invention is not limited thereto.

[0115] According to this embodiment, it is possible to support HARQ feedback in the case of multi-TRP repetition scheme and / or multi-PDSCH scheduling, thereby reducing the burden of PDCCH monitoring on the UE and reducing power loss and UE complexity.

[0116] It should be noted that the above-mentioned Figures 4, 9, and 10 are merely schematic illustrations of the embodiments of the present invention, and the present invention is not limited thereto. For example, the execution order between various steps may be appropriately adjusted, some other steps may be added, and some steps may be removed. Those skilled in the art may make appropriate modifications based on the above contents, and are not limited to the description of the above-mentioned Figures 4, 9, and 10.

[0117] The above-mentioned embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments may be used alone, or one or more of the above-mentioned embodiments may be used in combination.

[0118] <Example 4> An embodiment of the present invention provides an information receiving device. The device may be, for example, a terminal device, or one or more components configured in the terminal device. Descriptions of contents similar to those in the first embodiment will be omitted.

[0119] 11 is a schematic diagram of an example of an information receiving device according to an embodiment of the present invention. As shown in FIG. 11, an information receiving device 1100 includes the following units.

[0120] The first receiving unit 1101 receives downlink control information for scheduling a PDSCH, sent by a network device, where the downlink control information indicates a first number of TCI states, where the first number is an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information include a plurality of SLIVs.

[0121] A second receiving unit 1102 receives one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

[0122] In some embodiments, the terminal device may further include a third determination unit (not shown). The third determination unit determines the first number of PDSCH transmission occasions for each PDSCH among the PDSCHs scheduled by the downlink control information. Each PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. The second receiving unit receives or does not receive a PDSCH at each PDSCH transmission occasion. The following exemplarily describes the first number of PDSCH transmission occasions and a method for determining whether to receive a PDSCH at each PDSCH transmission occasion.

[0123] In some embodiments, the DCI schedules multiple PDSCHs.

[0124] In some embodiments, if there is a PDSCH transmission occasion that collides with an uplink symbol that is semi-statically configured for the PDSCH, the second receiver does not receive the PDSCH, and if there is no PDSCH transmission occasion that collides with an uplink symbol that is semi-statically configured for the PDSCH, the second receiver receives the PDSCH.

[0125] In some embodiments, if there is a PDSCH transmission occasion that does not collide with an uplink symbol that is semi-statically configured for the PDSCH, the second receiver receives the PDSCH, and if there is no PDSCH transmission occasion that does not collide with an uplink symbol that is semi-statically configured for the PDSCH, the second receiver does not receive the PDSCH.

[0126] In some embodiments, the second receiver receives the PDSCH on PDSCH transmission occasions that do not collide with semi-statically configured uplink symbols.

[0127] In some embodiments, if the first PDSCH transmission occasion of the PDSCH does not collide with a semi-statically configured uplink symbol, the second receiver receives the PDSCH, and if the first PDSCH transmission occasion of the PDSCH collide with a semi-statically configured uplink symbol, the second receiver does not receive the PDSCH.

[0128] In some embodiments, the apparatus may further include a fifth determining unit (not shown). The fifth determining unit determines a HARQ process identifier of a PDSCH scheduled by a DCI. The apparatus may not include a second receiving unit, but may include a first receiving unit and a fifth determining unit.

[0129] In some embodiments, if there is a PDSCH transmission occasion that collides with a semi-statically configured uplink symbol for the PDSCH, the PDSCH does not have a corresponding HARQ process ID, and if there is no PDSCH transmission occasion that collides with a semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID.

[0130] In some embodiments, if there is a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID, and if there is no PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for the PDSCH, the PDSCH does not have a corresponding HARQ process ID.

[0131] In some embodiments, if the first PDSCH transmission occasion of a PDSCH does not collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process ID, and if the first PDSCH transmission occasion of a PDSCH collides with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process ID.

[0132] In some embodiments, the DCI schedules one PDSCH.

[0133] In some embodiments, the second receiver receives the PDSCH at the first number of PDSCH transmission occasions, or the second receiver receives the PDSCH at one or more PDSCH transmission occasions of the first number of PDSCH transmission occasions depending on whether or not it collides with a semi-statically configured uplink symbol.

[0134] In some embodiments, the terminal device may further include a fourth determination unit (not shown). The fourth determination unit determines the first number of PDSCH transmission occasions for valid PDSCHs among the PDSCHs scheduled by the downlink control information. Each valid PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. The second determination unit does not determine the first number of PDSCH transmission occasions for invalid PDSCHs among the PDSCHs scheduled by the downlink control information. The second receiving unit receives or does not receive a PDSCH at each PDSCH transmission occasion.

[0135] In some embodiments, the DCI schedules one or more PDSCHs, where the one or more PDSCHs include only one valid PDSCH, where the valid PDSCH corresponds to the first number of PDSCH transmission occasions.

[0136] In some embodiments, the valid PDSCH is a PDSCH whose corresponding time domain resource configuration does not collide with an uplink symbol that is semi-statically configured.

[0137] In some embodiments, the second receiver receives the valid PDSCH in the first number of PDSCH transmission occasions, or the second receiver receives the valid PDSCH in one or more PDSCH transmission occasions of the first number of PDSCH transmission occasions depending on whether it collides with a semi-statically configured uplink symbol.

[0138] In some embodiments, the first number of PDSCH transmission occasions includes a first PDSCH transmission occasion and a second PDSCH transmission occasion.The apparatus further includes the following units (not shown).

[0139] A first determiner determines a set of candidate PDSCH receiving occasions based on a symbol corresponding to the first PDSCH transmission occasion and / or a symbol corresponding to the second PDSCH transmission occasion and / or based on a first allocation table, the first allocation table relating to an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion.

[0140] The first processing unit generates and sends a HARQ-ACK codebook, the HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH receiving occasion set.

[0141] In some embodiments, the aspects of the first receiving unit 1101 and the second receiving unit 1102 may refer to steps 401 and 402 in the first embodiment, and a description of the overlapping contents will be omitted.

[0142] <Example 5> An embodiment of the present invention provides an information transmission device. The device may be, for example, a network device, or one or more elements or components configured in the network device. Descriptions of the same contents as those in the second embodiment will be omitted.

[0143] 12 is a schematic diagram of an example of an information transmission device according to an embodiment of the present invention. As shown in FIG. 12, an information transmission device 1200 includes the following units.

[0144] The first transmitting unit 1201 transmits downlink control information for scheduling a PDSCH to a terminal device, the downlink control information indicating a first number of TCI states, where the first number is an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information include multiple SLIVs.

[0145] The second transmitting unit 1202 transmits one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

[0146] In some embodiments, the first transmitting unit 1201 and the second transmitting unit 1202 may refer to steps 901 to 902 in the second embodiment, and a description of the overlapping contents will be omitted.

[0147] According to this embodiment, even if one DCI supports scheduling of multiple PDSCHs, a multi-TRP repetition scheme can be supported, so that the number of times the terminal device monitors the PDCCH can be reduced, thereby reducing the complexity and power consumption of the terminal device monitoring the PDCCH, and the resource overhead for transmitting downlink control signaling (DCI) can be reduced, thereby improving data throughput.

[0148] <Example 6> An embodiment of the present invention provides an information feedback device. The device may be, for example, a terminal device, or one or more components configured in the terminal device. The description of the same contents as those in the third embodiment will be omitted.

[0149] 13 is a schematic diagram of an example of an information feedback device according to an embodiment of the present invention. As shown in FIG. 13, the information feedback device 1300 includes the following units:

[0150] The second determining unit 1301 determines a set of candidate PDSCH receiving occasions based on the symbols corresponding to the first PDSCH transmission occasions and / or the symbols corresponding to the second PDSCH transmission occasions and / or based on a first allocation table, which is related to an offset value between the first PDSCH transmission occasions and the second PDSCH transmission occasions.

[0151] The second processing unit 1302 generates and sends a HARQ-ACK codebook, where the HARQ-ACK codebook includes HARQ-ACK information corresponding to the candidate PDSCH receiving occasion set.

[0152] In some embodiments, the apparatus may further include the following units (not shown):

[0153] The third receiver receives downlink control information sent by the network device, the downlink control information indicating a first number of TCI states, the first PDSCH transmission occasion and the second PDSCH transmission occasion corresponding to one PDSCH, and the first PDSCH transmission occasion and the second PDSCH transmission occasion corresponding to different TCI states, respectively.

[0154] In some embodiments, the offset value is a time domain offset value between the last symbol of the first PDSCH transmission occasion and the first symbol of the second PDSCH transmission occasion.

[0155] In some embodiments, the second determination unit 1301 and the second processing unit 1302 may refer to steps 1001 to 1002 in the third embodiment, and a description of the overlapping contents will be omitted.

[0156] According to this embodiment, it is possible to support feedback of HARQ information for a multi-TRP repetition scheme and support a method of scheduling multiple PDSCHs through one DCI, thereby reducing the burden of PDCCH monitoring on the UE and reducing power loss and UE complexity.

[0157] The above-mentioned embodiments are merely illustrative of the embodiments of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments may be used alone, or one or more of the above-mentioned embodiments may be used in combination.

[0158] Although only the components or modules related to the present invention have been described above, the present invention is not limited thereto. Each of the devices in Figs. 11 to 13 may further include other components or modules. For specific contents of these components or modules, reference may be made to the related art.

[0159] 11 to 13 only exemplarily show the connection relationships or signal directions between various components or modules, but it is clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned various components or modules may be implemented by hardware devices such as a processor, a memory, a transmitter, and a receiver, and the present invention is not limited thereto.

[0160] The above-mentioned fourth and sixth embodiments may be implemented alone or in combination, and the embodiments of the present invention are not limited thereto.

[0161] <Example 7> The embodiment of the present invention further provides a communication system, and may refer to FIG. 3. Description of the same contents as those of the first to sixth embodiments will be omitted.

[0162] In some embodiments, the communication system 100 may include at least a terminal device 102 and a network device 101 .

[0163] In some embodiments, the aspects of the terminal device 102 may refer to the terminal device 1500, and the aspects of the network device may refer to the network device 1400, and the description thereof will be omitted here.

[0164] An embodiment of the present invention further provides a network device, which may be, for example, a base station, but the present invention is not limited thereto and may be other network devices.

[0165] Fig. 14 is a schematic diagram of a network device according to an embodiment of the present invention. As shown in Fig. 14, the network device 1400 may include a processor 1410 (e.g., a central processing unit (CPU)) and a memory 1420, and the memory 1420 is connected to the processor 1410. The memory 1420 may store various data, and further stores an information processing program 1430, and executes the program 1430 under the control of the processor 1410.

[0166] For example, the processor 1410 may execute a program to realize the information transmission method described in the second embodiment.

[0167] Also, as shown in Fig. 14, the network device 1400 may further include a transceiver 1440 and an antenna 1450. The functions of the above members are similar to those of the prior art, and the description thereof will be omitted here. It is not necessary for the network device 1400 to include all the units shown in Fig. 14. Also, the network device 1400 may further include units not shown in Fig. 14, and may refer to the prior art.

[0168] The embodiment of the present invention further provides a terminal device, but the present invention is not limited thereto and may be other devices.

[0169] Fig. 15 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in Fig. 15, the terminal device 1500 may include a processor 1510 and a memory 1520, where the memory 1520 stores data and programs and is connected to the processor 1510. It should be noted that this diagram is exemplary, and other types of structures may be used to supplement or replace this structure to realize communication functions or other functions.

[0170] For example, the processor 1510 may execute a program to realize the information receiving method described in the first embodiment or the information feedback method described in the third embodiment.

[0171] Also, as shown in Fig. 15, the terminal device 1500 may further include a communication module 1530, an input unit 1540, a display 1550, and a power source 1560. Here, the functions of the above units are similar to those of the conventional technology, and the description thereof will be omitted here. It is not necessary for the terminal device 1500 to include all the units shown in Fig. 15. Also, the terminal device 1500 may further include units not shown in Fig. 15, and may refer to the conventional technology.

[0172] In an embodiment of the present invention, there is further provided a computer-readable program, which, when executed in a terminal device, causes the terminal device to execute the information receiving method according to the first embodiment.

[0173] An embodiment of the present invention further provides a storage medium having a computer-readable program stored therein, the storage medium causing a terminal device to execute the information receiving method described in embodiment 1 when the program is executed.

[0174] An embodiment of the present invention further provides a computer-readable program, which, when executed in a network device, causes the network device to perform the information transmitting method according to the second embodiment.

[0175] An embodiment of the present invention further provides a storage medium having a computer-readable program stored thereon, the storage medium causing a network device to execute the information transmission method described in embodiment 2 when the program is executed.

[0176] An embodiment of the present invention further provides a computer-readable program, which, when executed in a terminal device, causes the terminal device to perform the information feedback method according to the third embodiment.

[0177] An embodiment of the present invention further provides a storage medium having a computer-readable program stored thereon, the storage medium causing a terminal device to execute the information feedback method described in embodiment 3 when the program is executed.

[0178] The above-mentioned apparatus and method of the present invention may be realized by hardware or by a combination of hardware and software.The present invention relates to a computer readable program which, when executed by a logic unit, causes the logic unit to realize the above-mentioned apparatus or components, or to realize the above-mentioned various methods or steps.The present invention relates to a storage medium for storing the above-mentioned program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0179] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in the drawings, or one or more combinations of the functional block diagrams, may correspond to each software module in the flow of a computer program, or each hardware module. These software modules may correspond to each step shown in the drawings. These hardware modules may be realized by implementing these software modules in hardware, for example, using a field programmable gate array (FPGA).

[0180] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor so that the processor reads information from the storage medium or writes information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal, or in a memory card inserted in the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a MEGA-SIM card or a large capacity flash memory device with a relatively large capacity, the software module may be stored in the MEGA-SIM card or the large capacity flash memory device.

[0181] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof to perform the functions described herein. One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0182] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.

[0183] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above examples. (Appendix 1) An information receiving method, comprising: A step of receiving, by a terminal device, downlink control information (DCI) for scheduling a PDSCH, transmitted by a network device, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; and receiving, by the terminal device, one or more PDSCHs among the PDSCHs scheduled by the downlink control information. (Appendix 2) The method of claim 1, wherein the terminal device determines the first number of PDSCH transmission occasions for each PDSCH among the PDSCHs scheduled by the downlink control information. (Appendix 3) 3. The method of claim 1 or 2, wherein each PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. (Appendix 4) The method according to claim 2 or 3, wherein the terminal device receives or does not receive a PDSCH at each PDSCH transmission occasion. (Appendix 5) 5. The method of claim 1, wherein the DCI schedules multiple PDSCHs. (Appendix 6) If there is a PDSCH transmission occasion that conflicts with an uplink symbol semi-statically configured for a PDSCH, the terminal device does not receive the PDSCH; The method according to claim 5, wherein if there is no PDSCH transmission occasion that conflicts with an uplink symbol semi-statically configured for the PDSCH, the terminal device receives the PDSCH. (Appendix 7) If there is a PDSCH transmission occasion that does not collide with an uplink symbol semi-statically configured for the PDSCH, the terminal device receives the PDSCH; The method according to claim 5, wherein if there is no PDSCH transmission occasion that does not collide with an uplink symbol semi-statically configured for a PDSCH, the terminal device does not receive the PDSCH. (Appendix 8) The method of claim 5, wherein the terminal device receives a PDSCH in a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol. (Appendix 9) If the first PDSCH transmission occasion of the PDSCH does not collide with a semi-statically configured uplink symbol, the terminal device receives the PDSCH; The method according to claim 5, wherein if a first PDSCH transmission occasion of a PDSCH collides with a semi-statically configured uplink symbol, the terminal device does not receive the PDSCH. (Appendix 10) If there is a PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for a PDSCH, the PDSCH does not have a corresponding HARQ process ID; 7. The method of claim 6, wherein if there is no PDSCH transmission occasion that conflicts with an uplink symbol semi-statically configured for a PDSCH, the PDSCH has a corresponding HARQ process ID. (Appendix 11) If there is a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID; 10. The method of any of claims 6 to 9, wherein if there is no PDSCH transmission occasion that does not collide with an uplink symbol semi-statically configured for the PDSCH, the PDSCH does not have a corresponding HARQ process ID. (Appendix 12) If the first PDSCH transmission occasion of a PDSCH does not collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process ID; 10. The method according to claim 6 or 9, wherein if a first PDSCH transmission occasion of a PDSCH collides with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process ID. (Appendix 13) 5. The method of claim 2, wherein the DCI schedules one PDSCH. (Appendix 14) The terminal device receives the PDSCH in the first number of PDSCH transmission occasions, or The method of claim 13, wherein the terminal device receives the PDSCH on one or more PDSCH transmission occasions of the first number of PDSCH transmission occasions depending on whether or not it collides with a semi-statically configured uplink symbol. (Appendix 15) The method of claim 1, wherein the terminal device determines the first number of PDSCH transmission occasions for valid PDSCHs among PDSCHs scheduled by the downlink control information. (Appendix 16) 16. The method of claim 1 or 15, wherein each valid PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. (Appendix 17) 17. The method according to claim 15 or 16, wherein the terminal device receives or does not receive a PDSCH at each PDSCH transmission occasion. (Appendix 18) 18. The method of claim 17, further comprising: the terminal device determining, for an invalid PDSCH among the PDSCHs scheduled by the downlink control information, the first number of PDSCH transmission occasions. (Appendix 19) 19. The method of any of Supplementary Notes 1 and 15 to 18, wherein the DCI schedules one or more PDSCHs, the one or more PDSCHs including only one valid PDSCH, the valid PDSCH corresponding to the first number of PDSCH transmission occasions. (Appendix 20) 20. The method of claim 15, wherein the valid PDSCH is a PDSCH whose corresponding time domain resource configuration does not collide with an uplink symbol that is semi-statically configured. (Appendix 21) The terminal device receives the valid PDSCH in the first number of PDSCH transmission occasions, or 21. The method of claim 15, wherein the terminal device receives the valid PDSCH on one or more PDSCH transmission occasions of the first number of PDSCH transmission occasions depending on whether or not it collides with a semi-statically configured uplink symbol. (Appendix 22) the first number of PDSCH transmission occasions includes a first PDSCH transmission occasion and a second PDSCH transmission occasion; The method comprises: determining a set of candidate PDSCH reception occasions based on a symbol corresponding to the first PDSCH transmission occasion and / or a symbol corresponding to the second PDSCH transmission occasion and / or based on a first allocation table, the first allocation table relating to an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion; The method of any one of Supplementary Notes 1 to 21, further comprising a step of the terminal device generating and transmitting a HARQ-ACK codebook, the HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH receiving occasion set. (Appendix 23) 1. A method for transmitting information, comprising: A step of a network device transmitting downlink control information for scheduling a PDSCH to a terminal device, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; and transmitting, by the network device, one or more of the PDSCHs scheduled by the downlink control information. (Appendix 24) 1. An information feedback method, comprising: determining a set of candidate PDSCH reception occasions based on a symbol corresponding to a first PDSCH transmission occasion and / or a symbol corresponding to a second PDSCH transmission occasion and / or based on a first allocation table, the first allocation table relating to an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion; The method includes a step of the terminal device generating and transmitting a HARQ-ACK codebook, the HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH receiving occasion set. (Appendix 25) 25. The method of claim 24, further comprising: a step of receiving, by the terminal device, downlink control information transmitted by a network device, the downlink control information indicating a first number of TCI states, the first PDSCH transmission occasion and the second PDSCH transmission occasion corresponding to one PDSCH, and the first PDSCH transmission occasion and the second PDSCH transmission occasion corresponding to different TCI states, respectively. (Appendix 26) 26. The method of claim 24 or 25, wherein the offset value is a time-domain offset value between a last symbol of the first PDSCH transmission occasion and a first symbol of the second PDSCH transmission occasion. (Appendix 27) An information receiving method, comprising: A step of receiving downlink control information DCI for scheduling a PDSCH, the downlink control information being sent by a network device, by a terminal device, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; and a step by the terminal device of determining a HARQ process identifier corresponding to the scheduled PDSCH. (Appendix 28) 28. The method of claim 27, wherein the terminal device determines the first number of PDSCH transmission occasions for each PDSCH among the PDSCHs scheduled by the downlink control information. (Appendix 29) 29. The method of claim 27 or 28, wherein each PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. (Appendix 30) 30. The method of claim 27, wherein the DCI schedules multiple PDSCHs. (Appendix 31) If there is a PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for a PDSCH, the PDSCH does not have a corresponding HARQ process ID; 31. The method of any of claims 27 to 30, wherein if there is no PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID. (Appendix 32) If there is a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID; 31. The method of any of claims 27 to 30, wherein if there is no PDSCH transmission occasion that does not collide with an uplink symbol semi-statically configured for the PDSCH, the PDSCH does not have a corresponding HARQ process ID. (Appendix 33) If the first PDSCH transmission occasion of a PDSCH does not collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process ID; 31. The method of any of claims 27 to 30, wherein if a first PDSCH transmission occasion of a PDSCH collides with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process ID. (Appendix 34) A network device comprising: a memory having a computer program stored therein; and a processor, the processor configured to execute the computer program to realize the information transmission method described in Supplementary Note 23. (Appendix 35) A terminal device including a memory in which a computer program is stored and a processor, the processor being configured to execute the computer program to realize a method according to any one of appendices 1 to 22 and appendices 24 to 33. (Appendix 36) A communication system including a terminal device according to claim 35 and / or a network device according to claim 34. (Appendix 37) An information receiving device applied to a terminal device, comprising: A first receiver for receiving downlink control information (DCI) for scheduling a PDSCH, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; and a fifth determination unit for determining a HARQ process identifier corresponding to the scheduled PDSCH. (Appendix 38) The apparatus of claim 37, wherein the terminal device determines the first number of PDSCH transmission occasions for each PDSCH among PDSCHs scheduled by the downlink control information. (Appendix 39) 39. The apparatus of claim 37 or 38, wherein each PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions. (Appendix 40) 40. The apparatus of claim 37, wherein the DCI schedules multiple PDSCHs. (Appendix 41) If there is a PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for a PDSCH, the PDSCH does not have a corresponding HARQ process ID; 41. The apparatus of any of claims 37 to 40, wherein if there is no PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID. (Appendix 42) If there is a PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for the PDSCH, the PDSCH has a corresponding HARQ process ID; 41. The apparatus of any of claims 37 to 40, wherein if there is no PDSCH transmission occasion that does not collide with an uplink symbol semi-statically configured for the PDSCH, the PDSCH does not have a corresponding HARQ process ID. (Appendix 43) If the first PDSCH transmission occasion of a PDSCH does not collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process ID; 41. The apparatus of any of claims 37 to 40, wherein if a first PDSCH transmission occasion of a PDSCH collides with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process ID.

Claims

1. An information receiving device applied to a terminal device, comprising: A first receiver for receiving downlink control information (DCI) for scheduling a PDSCH, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; a second receiver for receiving one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

2. 2. The apparatus of claim 1, wherein each PDSCH among the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions.

3. The apparatus of claim 2 , wherein the DCI schedules multiple PDSCHs.

4. If there is a PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for the PDSCH, the second receiver does not receive the PDSCH; The apparatus of claim 3 , wherein the second receiver receives the PDSCH if there is no PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for the PDSCH.

5. If there is a PDSCH transmission occasion that does not collide with an uplink symbol that is semi-statically configured for the PDSCH, the second receiving unit receives the PDSCH; 4. The apparatus of claim 3, wherein if there is no PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for a PDSCH, the second receiver does not receive the PDSCH.

6. 4. The apparatus of claim 3, wherein the second receiver receives the PDSCH on PDSCH transmission occasions that do not collide with semi-statically configured uplink symbols.

7. If a first PDSCH transmission occasion of a PDSCH does not collide with a semi-statically configured uplink symbol, the second receiving unit receives the PDSCH; 4. The apparatus of claim 3, wherein the second receiver does not receive a PDSCH if a first PDSCH transmission occasion of the PDSCH collides with a semi-statically configured uplink symbol.

8. If there is a PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for the PDSCH, the PDSCH does not have a corresponding HARQ process ID; 5. The apparatus of claim 4, wherein if there is no PDSCH transmission occasion that conflicts with a semi-statically configured uplink symbol for a PDSCH, the PDSCH has a corresponding HARQ process ID.

9. If there is a PDSCH transmission occasion that does not collide with an uplink symbol semi-statically configured for the PDSCH, the PDSCH has a corresponding HARQ process ID; 5. The apparatus of claim 4, wherein if there is no PDSCH transmission occasion that does not collide with a semi-statically configured uplink symbol for the PDSCH, the PDSCH does not have a corresponding HARQ process ID.

10. If the first PDSCH transmission occasion of the PDSCH does not collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process ID; The apparatus of claim 4 , wherein if a first PDSCH transmission occasion of a PDSCH collides with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process ID.

11. The apparatus of claim 2 , wherein the DCI schedules one PDSCH.

12. The second receiver receives the PDSCH in the first number of PDSCH transmission occasions, or 12. The apparatus of claim 11, wherein the second receiver receives the PDSCH on one or more PDSCH transmission occasions of the first number of PDSCH transmission occasions depending on whether or not it collides with a semi-statically configured uplink symbol.

13. The apparatus of claim 1 , further comprising: a fourth determiner configured to determine the first number of PDSCH transmission occasions for valid PDSCHs among PDSCHs scheduled by the downlink control information.

14. 14. The apparatus of claim 13, wherein each valid one of the PDSCHs scheduled by the downlink control information corresponds to the first number of PDSCH transmission occasions.

15. 14. The apparatus of claim 13, wherein the DCI schedules one or more PDSCHs, the one or more PDSCHs including only one valid PDSCH, the valid PDSCH corresponding to the first number of PDSCH transmission occasions.

16. The apparatus of claim 13, wherein the valid PDSCH is a PDSCH whose corresponding time domain resource configuration does not collide with a semi-statically configured uplink symbol.

17. An information transmitting device applied to a network device, comprising: A first transmitter that transmits downlink control information for scheduling a PDSCH to a terminal device, the downlink control information indicating a first number of TCI states, the first number being an integer greater than 1, and one or more rows in a TDRA table corresponding to the downlink control information including a plurality of SLIVs; and a second transmitter configured to transmit one or more PDSCHs among the PDSCHs scheduled by the downlink control information.

18. An information feedback device applied to a terminal device, comprising: a second determination unit configured to determine a set of candidate PDSCH receiving occasions based on a symbol corresponding to a first PDSCH transmission occasion and / or a symbol corresponding to a second PDSCH transmission occasion and / or based on a first allocation table, the first allocation table relating to an offset value between the first PDSCH transmission occasion and the second PDSCH transmission occasion; a second processing unit configured to generate and transmit a HARQ-ACK codebook, the HARQ-ACK codebook including HARQ-ACK information corresponding to the candidate PDSCH reception occasion set;

19. 20. The apparatus of claim 18, further comprising: a third receiver for receiving downlink control information transmitted by a network device, the downlink control information indicating a first number of TCI states, the first PDSCH transmission occasion and the second PDSCH transmission occasion corresponding to one PDSCH, the first PDSCH transmission occasion and the second PDSCH transmission occasion corresponding to different TCI states, respectively.

20. 20. The apparatus of claim 18, wherein the offset value is a time-domain offset value between a last symbol of the first PDSCH transmission occasion and a first symbol of the second PDSCH transmission occasion.

Images