Information receiving method and apparatus, information sending method and apparatus, and communication system

Abstract

Provided in the embodiments of the present application are an information receiving method and apparatus, an information sending method and apparatus, and a communication system. The information receiving method comprises: a terminal device receiving information for configuring a first time-domain resource and / or a second time-domain resource, wherein in the first time-domain resource, a first frequency-domain resource is used for uplink and a second frequency-domain resource is used for downlink, and the second time-domain resource is outside the first time-domain resource; and receiving first DCI for scheduling a PDSCH and / or second DCI for scheduling a PUSCH.

Description

Information receiving and sending method, device and communication system TECHNICAL FIELD

[0001] The present application relates to the field of communication technology. BACKGROUND

[0002] In the prior art, for a time division duplex (TDD) frequency band, uplink transmission can only occur in an uplink time period. When a limited or small uplink time period is allocated, there will be problems of small coverage, capacity and large delay of uplink.

[0003] It should be noted that the above introduction to the technical background is only for the convenience of clearly and completely describing the technical solutions of the present application and facilitating the understanding of those skilled in the art. The above technical solutions cannot be considered as known to those skilled in the art merely because they are described in the background section of the present application.

[0004] SUMMARY

[0005] In order to improve the capacity and coverage of uplink transmission and reduce the delay of uplink transmission, in a TDD frequency band, a network device can work in a full duplex mode at certain time positions, for example, at the time positions, the network device simultaneously receives and transmits in different frequency domain resources in the corresponding carrier of the TDD frequency band. This working mode is referred to as sub-band non-overlapping full duplex (SBFD) for example, but is not limited thereto.

[0006] On the other hand, PDSCH / PUSCH can be scheduled by downlink control information (DCI). However, in the case of supporting the above working mode, there is no solution for how to schedule PDSCH / PUSCH by DCI and how UE receives / transmits PDSCH / PUSCH scheduled by DCI.

[0007] To solve at least one of the above problems, embodiments of the present application provide an information receiving and sending method, device and communication system.

[0008] According to an aspect of embodiments of the present application, an information receiving method is provided, comprising:

[0009] receiving information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0010] receiving a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0011] receiving a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0012] According to another aspect of embodiments of the present application, there is provided an information receiving method, comprising:

[0013] receiving information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is outside the first time domain resource;

[0014] receiving a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0015] receiving a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition or and / or multi-slot TB, a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0016] According to another aspect of embodiments of the present application, there is provided an information receiving method, comprising:

[0017] receiving information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is outside the first time domain resource;

[0018] transmit a first DCI for scheduling PDSCHs; wherein the first DCI schedules multiple PDSCHs or the PDSCHs have repetition, a transport block size (TBS) corresponding to the PDSCHs is determined by a frequency domain resource indicated by the first DCI within the second frequency domain resource or a frequency domain resource indicated by the first DCI; and / or,

[0019] transmit a second DCI for scheduling PUSCHs; wherein the second DCI schedules multiple PUSCHs or the PUSCHs have repetition and / or multi-slot TBs, a TBS corresponding to the PUSCHs is determined by a frequency domain resource indicated by the second DCI within the first frequency domain resource or a frequency domain resource indicated by the second DCI.

[0020] According to another aspect of embodiments of the present application, there is provided an information transmitting apparatus, comprising:

[0021] a transmitter that transmits information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is outside the first time domain resource;

[0022] the transmitter transmits a first DCI for scheduling PDSCHs; wherein the first DCI schedules multiple PDSCHs or the PDSCHs have repetition, a transport block size (TBS) corresponding to the PDSCHs is determined by a frequency domain resource indicated by the first DCI within the second frequency domain resource or a frequency domain resource indicated by the first DCI; and / or,

[0023] the transmitter transmits a second DCI for scheduling PUSCHs; wherein the second DCI schedules multiple PUSCHs or the PUSCHs have repetition and / or multi-slot TBs, a TBS corresponding to the PUSCHs is determined by a frequency domain resource indicated by the second DCI within the first frequency domain resource or a frequency domain resource indicated by the second DCI.

[0024] According to another aspect of embodiments of the present application, there is provided a communication system, comprising:

[0025] a network device that transmits information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is outside the first time domain resource; and transmits a first DCI for scheduling PDSCHs and / or a second DCI for scheduling PUSCHs;

[0026] a terminal device that receives information for configuring a first time domain resource and / or a second time domain resource; and

[0027] receiving a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0028] receiving a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0029] One of the beneficial effects of the embodiments of the present application is that the terminal device receives the first DCI for scheduling the PDSCH and / or the second DCI for scheduling the PUSCH, and determines the corresponding TBS according to the frequency domain resource corresponding to the PDSCH / PUSCH. In this way, the network device can work in a full-duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resource to transceive signals when the network device works in the full-duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0030] Specific embodiments of the application are disclosed herein, and represented in the accompanying drawings, illustrating the principles of the application in a manner that is best suited to the understanding of its principles and the best mode presently contemplated for its practical application. It is understood that the scope of the application is not to be limited by the specific embodiments disclosed and that modifications can be made to the embodiments without departing from the spirit and scope of the application. Other aspects of the application will become apparent to those skilled in the art upon consideration of the detailed description and accompanying drawings.

[0031] Features described and / or illustrated with respect to one implementation can be used in one or more other implementations in the same or similar manner, in combination with or in place of features in other implementations.

[0032] It should be emphasized that the term "comprises / comprising" when used in this specification is taken to mean the presence of stated features, integers, steps or components but not the exclusion of one or more other features, integers, steps, components or groups thereof. BRIEF DESCRIPTION OF DRAWINGS

[0033] Elements and features of the embodiments of the application described in one or more attachments or implementations can be combined with elements and features illustrated in one or more other attachments or implementations. Also, in the drawings, like reference numerals designate corresponding parts throughout the several views, and can be used to designate like components in more than one implementation.

[0034] The accompanying drawings, which are included to provide a further understanding of the embodiments of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the principles of the application. It is understood that the drawings are solely for purposes of illustration and are not intended to limit the application. It is understood that the drawings included herewith are illustrative and are non-limiting examples of the application. For the purpose of clarity, not all of the various components of the application are shown in each of the drawings. It is understood that the drawings are not to scale.

[0035] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0036] FIG. 2 is a schematic diagram of a method for receiving information according to an embodiment of the present application;

[0037] FIG. 3 is an example diagram of time domain resources according to an embodiment of the present application;

[0038] FIG. 4 is an example diagram of uplink available PRBs according to an embodiment of the present application;

[0039] FIG. 5 is an example diagram of downlink available PRBs according to an embodiment of the present application;

[0040] FIG. 6 is a schematic diagram of a method for transmitting information according to an embodiment of the present application;

[0041] FIG. 7 is a schematic diagram of an information receiving apparatus according to an embodiment of the present application;

[0042] FIG. 8 is a schematic diagram of an information transmitting apparatus according to an embodiment of the present application;

[0043] FIG. 9 is a schematic diagram of a network device according to an embodiment of the present application;

[0044] FIG. 10 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] The foregoing and other features of the present application will become more apparent from the following description and accompanying drawings. In the description and drawings, particular embodiments of the application have been disclosed in detail as being illustrative. It should be understood that the application is not limited to the particular embodiments described but includes variations and modifications that fall within the scope of the appended claims.

[0046] In the embodiments of the present application, the terms "first", "second" and the like are used to distinguish different elements from each other, but do not indicate spatial arrangement or time sequence of the elements, and the elements should not be limited by these terms. The term "and / or" includes any one and all combinations of the associated listed terms. The terms "comprise", "include", "have" and the like mean the presence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0047] In the embodiments of the present application, the singular form "a", "an" and the like includes the plural form, should be understood broadly as "one" or "a kind of", and not limited to the meaning of "one"; in addition, the term "said" should be understood as including both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least partially according to", and the term "based on" should be understood as "at least partially based on", unless the context clearly indicates otherwise.

[0048] In the embodiments of the present application, the term "communication network" or "wireless communication network" can refer to a network that conforms to any communication standard, such as Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.

[0049] In addition, the communication between devices in the communication system can be carried out according to any stage communication protocol, which can include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, New Radio (NR), 6G, etc., and / or other currently known or future to be developed communication protocols.

[0050] In embodiments of the present application, the term "network device" refers to, for example, a device that accesses a terminal device into a communication network and provides services for the terminal device in a communication system. The network device can include, but is not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), and the like.

[0051] The base station can include, but is not limited to, the following devices: node B (NodeB or NB), evolved node B (eNodeB or eNB), and 5G base station (gNB), IAB donor, and the like, and can further include a remote radio head (RRH), a remote radio unit (RRU), a relay, or a low-power node (such as a femto, a pico, and the like). The term "base station" can include some or all functions thereof, and each base station can provide communication coverage for a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0052] In embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, which can also be referred to as "terminal equipment" (TE). The terminal equipment can be fixed or mobile, and can also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, a mobile terminal (MT), and the like.

[0053] The terminal equipment can include, but is not limited to, the following devices: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a machine type communication device, a laptop computer, a cordless phone, a smartphone, a smartwatch, a digital camera, and the like.

[0054] For another example, in scenarios such as Internet of Things (IoT), a terminal device can also be a machine or an apparatus that performs monitoring or measurement, for example, can include but is not limited to: a machine type communication (MTC) terminal, a vehicle-mounted communication terminal, a device-to-device (D2D) terminal, a machine-to-machine (M2M) terminal, and the like.

[0055] In addition, the term "network side" or "network device side" refers to the side of the network, which can be a certain base station, or can include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the side of the user or terminal, which can be a certain UE, or can include one or more terminal devices as described above. In this article, "device" can refer to a network device or a terminal device without special indication.

[0056] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" can be interchangeable without causing confusion, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" can be interchangeable;

[0057] The terms "downlink control signal" and "downlink control information (DCI)" or "physical downlink control channel (PDCCH)" can be interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH)" can be interchangeable.

[0058] In addition, the uplink signal can include an uplink data signal and / or an uplink control signal and / or a PRACH and / or an SRS, etc., and can also be referred to as an uplink transmission (UL transmission) or uplink information or an uplink channel. Transmitting / receiving the uplink transmission on the uplink resource can be understood as transmitting / receiving the uplink transmission using the uplink resource. The downlink signal can include a downlink data signal and / or a downlink control signal and / or a synchronization signal (SS, for example, PSS / SSS) and / or a broadcast channel (PBCH) and / or an SSB (SS / PBCH block, including PSS, SSS, and PBCH and its DMRS) and / or a CSI-RS, etc., and can also be referred to as a downlink transmission (DL transmission) or downlink information or a downlink channel. Transmitting / receiving the downlink transmission on the downlink resource can be understood as transmitting / receiving the downlink transmission using the downlink resource.

[0059] In embodiments of the present application, the higher layer signaling can be, for example, radio resource control (RRC) signaling; the RRC signaling can include, for example, an RRC message, such as a broadcast / common RRC message / signaling (for example, a master information block (MIB), system information), a dedicated RRC message / signaling; or an RRC information element (RRC IE); or information fields included in the RRC message or the RRC information element (or information fields included in the information fields). The higher layer signaling can also be, for example, medium access control (MAC) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto. The names of the signaling (such as RRC messages, information element IEs, information fields, higher layer parameters, etc.) used in embodiments of the present application are only examples, and other names can also be used, and embodiments of the present application are not limited thereto.

[0060] In embodiments of the present application, multiple means at least two, or two or more.

[0061] In embodiments of the present application, predefined means defined by a protocol or determined according to rules defined by a protocol, without additional configuration. Configuration / indication means direct or indirect configuration / indication by a network device through higher layer signaling and / or physical layer signaling. The configuration / indication can be configured / indicated by introducing a higher layer parameter in the higher layer signaling, where the higher layer parameter refers to fields and / or information elements / units / members (IEs) in the higher layer signaling, etc. The physical layer signaling can be, for example, control information carried by a physical downlink control channel (DCI) or sequence, but is not limited thereto.

[0062] For ease of description, the following describes a base station as an example of an access network device. In the following description, “if”, “in the case of” and “when” can be used interchangeably without causing confusion. For resources in the frequency domain, “carrier” and “resource grid” can be interchangeable, “subcarrier spacing configuration (SCS) μ” and “subcarrier spacing (SCS) Δf” can be interchangeable. “Subcarrier spacing” and “numerology” can be interchangeable. “Resource block”, “RB” and “PRB”, “physical resource block”, “common resource block (CRB)” can be interchangeable. Configuration / indication / provision / given can be interchangeable. “Index” and “ID” can be interchangeable.

[0063] The following describes scenarios of embodiments of the present application by way of examples, but the present application is not limited thereto.

[0064] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a case taking a terminal device and a network device as examples. As shown in FIG. 1, the communication system 100 can include a network device 101 and terminal devices 102 and 103. For simplicity, FIG. 1 illustrates only two terminal devices and one network device as examples, but embodiments of the present application are not limited thereto.

[0065] In embodiments of the present application, the network device 101 and the terminal devices 102 and 103 can perform existing services or future implementable services transmission. For example, these services can include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC) and ultra-reliable and low-latency communication (URLLC), etc.

[0066] Among them, the terminal device 102 can send data to the network device 101, for example, using a licensed or unlicensed transmission mode. The network device 101 can receive data sent by one or more terminal devices 102, and feed back information to the terminal device 102, such as acknowledgement (ACK) / non-acknowledgement (NACK) information, etc., and the terminal device 102 can confirm the end of the transmission process according to the feedback information, or can also perform new data transmission, or can perform data retransmission.

[0067] The network device 101 can transmit data to the terminal device 102 and / or the terminal device 103 in a unicast or groupcast or broadcast manner. The terminal device 102 can receive data transmitted by one or more network devices (for example, dual connectivity or multi-connectivity) through a downlink or the terminal device 103 through a sidelink.

[0068] It is worth noting that FIG. 1 shows that both terminal devices 102 and 103 are within the coverage of the network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 can be outside the coverage of the network device 101, or one terminal device 102 is within the coverage of the network device 101 and the other terminal device 103 is outside the coverage of the network device 101.

[0069] In the following description, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH; transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH.

[0070] In addition, the content in the brackets is explanatory or exemplary or optional, for example, the expression or limitation in the brackets can be added in some embodiments, or the expression or limitation in the brackets can be ignored in other embodiments, " / " represents "and / or", and the present application is not limited thereto. Various embodiments of the embodiments of the present application will be described below in conjunction with the accompanying drawings. These embodiments are only exemplary and not limiting.

[0071] Embodiments of the first aspect

[0072] The embodiments of the present application provide an information receiving method, which is described from the side of a terminal device.

[0073] FIG. 2 is a schematic diagram of an information receiving method according to an embodiment of the present application. As shown in FIG. 2, the method comprises:

[0074] 201, the terminal device receives information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0075] 202, the terminal device receives a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, and a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0076] receiving a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, the TBS of the PUSCH is determined by the frequency domain resource within the first frequency domain resource indicated by the second DCI or the frequency domain resource indicated by the second DCI.

[0077] It is worth noting that the above FIG. 2 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications according to the above description, and the present application is not limited to the above FIG. 2.

[0078] In some embodiments, the terminal device can be an SBFD-aware device; the present application is not limited thereto. For example, in the initial access procedure (from RRC_IDLE to RRC_Connected state, including CBRA) and / or in the random access procedure (such as CBRA) and / or in the RRCSetupComplete message and / or in the capability information, the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE).

[0079] For example, in the random access procedure, the terminal device is indicated to be an SBFD-aware device through the RO for sending the preamble and / or the sent preamble and / or Msg3. For example, when some ROs and / or preambles are available only for SBFD-aware devices, thereby, when the UE uses these ROs and / or preambles, it can be known that the UE is an SBFD-aware device. For example, in the Msg3 and / or RRCSetupComplete message and / or capability information, information for indicating that the UE is an SBFD-aware device is included.

[0080] For example, the SBFD-aware UE has the capability related to SBFD operation, including one or more of the following: being able to know the SBFD configuration, such as the first time domain resource and / or the second time domain resource and / or the first frequency domain resource and / or the second frequency domain resource configuration; being able to transmit and receive signals according to the SBFD configuration; being able to transmit uplink signals in the (DL) SBFD symbol.

[0081] The time domain resource related to the embodiments of the present application is first schematically described as follows.

[0082] In some embodiments, for one cell or carrier, in the first time domain resource, different frequency domain resources are respectively (only) used for (receiving) uplink (e.g. corresponding to the first frequency domain resource described below) and (only) used for (transmitting) downlink (e.g. corresponding to the second frequency domain resource described below), for example, the network device can simultaneously receive (uplink signal) on the (only) uplink frequency domain resource and transmit (downlink signal) on the (only) downlink frequency domain resource; the second time domain resource is outside the first time domain resource, for example, in the second time domain resource, different frequency domain resources are used for uplink or downlink, that is, the frequency domain resources are not divided into (only) uplink frequency domain resources and (only) downlink frequency domain resources, and the network device does not simultaneously receive and transmit.

[0083] In some embodiments, the first time domain resource includes, for example, SBFD slots and / or SBFD symbols, and the second time domain resource includes, for example, non-SBFD slots and / or non-SBFD symbols. Among them, the SBFD slot refers to a slot in which all symbols are SBFD symbols, and the non-SBFD slot refers to a slot in which all symbols are non-SBFD symbols. For ease of description, the following uses SBFD symbols and non-SBFD symbols for description.

[0084] In some embodiments, the information for configuring SBFD symbols and / or non-SBFD symbols is provided by high layer signaling. For example, the high layer parameter for configuring SBFD symbols is optionally present in SIB1 and / or SIB Common Serving Cell Configuration (ServingCellConfigCommonSIB) IE and / or Common Serving Cell Configuration (ServingCellConfigCommon) IE (in Common TDD Uplink-Downlink Configuration (TDD-UL-DL-ConfigCommon) IE (in TDD Uplink-Downlink Pattern (TDD-UL-DL-Pattern) IE)), and / or the high layer parameter for configuring SBFD symbols is optionally present in Serving Cell Configuration (ServingCellConfig).

[0085] In some embodiments, the cell / carrier can be configured with one or more (e.g. 2) TDD uplink-downlink patterns, when multiple patterns are configured, different patterns have or do not have corresponding SBFD symbols respectively, and different patterns are independently configured with corresponding SBFD symbols.

[0086] For example, for each pattern with SBFD symbols, the SBFD symbols are consecutive in the period corresponding to the pattern. The above-mentioned higher layer parameter for configuring SBFD symbols, for example, includes one or more parameters for configuring SBFD symbols in the period, for example: a starting slot index, a starting symbol index (in the starting slot), an ending slot index, an ending symbol index (in the ending slot).

[0087] For example, the starting and ending slots are the first and last slots including SBFD symbols, respectively, and the starting and ending symbols are the first and last SBFD symbols in the starting and ending slots, respectively, and the SBFD symbols are from the starting symbol of the starting slot to the ending symbol of the ending slot. The slot index is the number of the slot included in the period, which is, for example, sequentially increased by 1 starting from 0 or 1. For example, when the starting slot index is 0, the starting slot is the first slot in the period, and when the starting slot index is 1, the starting slot is the second slot in the period, and so on. Similarly, the symbol index is the number of the symbol in the slot. Among them, the above-mentioned slot / symbol is configured with the SCS of the reference subcarrier spacing (reference SubcarrierSpacing) field of the common TDD uplink-downlink configuration (TDD-UL-DL-ConfigCommon) IE.

[0088] For example, each / different pattern is independently configured with a period, for example, respectively configured by dl-UL-TransmissionPeriodicity in the corresponding (TDD-UL-DL-Pattern) IE. Among them, when only one pattern is configured, the period of the SBFD symbol is the same as the period corresponding to the pattern, and when multiple (for example, 2) patterns are configured, the period of the SBFD symbol is the same as the sum of the periods corresponding to all patterns.

[0089] In some embodiments, the downlink symbol is, for example, a symbol indicated as downlink (downlink) by the first uplink-downlink configuration, the uplink symbol is, for example, a symbol indicated as uplink (uplink) by the first uplink-downlink configuration, the flexible symbol (Flexible symbol) is, for example, a symbol neither indicated as downlink nor indicated as uplink by the first uplink-downlink configuration, or a symbol indicated as flexible by the configuration. Among them, the first uplink-downlink configuration is used to provide a cell-specific uplink-downlink configuration, for example, tdd-UL-DL-ConfigurationCommon or common TDD uplink-downlink configuration (TDD-UL-DL-ConfigCommon) IE or (TDD-UL-DL-Pattern) IE, not limited thereto.

[0090] In some embodiments, the UE determines the DL / UL / Flexible symbols corresponding to the BWP according to the DL / UL / Flexible symbols configured based on the referenceSubcarrierSpacing (and assuming NCP). For example, it determines the DL / UL / Flexible symbols corresponding to the BWP according to the referenceSubcarrierSpacing and the SCS and / or CP type (NCP or ECP) of the BWP.

[0091] In some embodiments, the DL / UL / Flexible symbols refer to the DL / UL / Flexible symbols configured based on the referenceSubcarrierSpacing or the DL / UL / Flexible symbols corresponding to the BWP.

[0092] In some embodiments, the UE determines the SBFD / non-SBFD symbols corresponding to the BWP according to the SBFD / non-SBFD symbols configured based on the referenceSubcarrierSpacing (and assuming NCP). For example, it determines the SBFD / non-SBFD symbols corresponding to the BWP according to the referenceSubcarrierSpacing and the SCS and / or CP type (NCP or ECP) of the BWP.

[0093] In some embodiments, the SBFD / non-SBFD symbols refer to the SBFD / non-SBFD symbols configured based on the referenceSubcarrierSpacing or the SBFD / non-SBFD symbols corresponding to the BWP.

[0094] In some embodiments, the UE does not expect the CP type of the BWP to be ECP.

[0095] In some embodiments, the UE does not expect the SBFD symbols configured by the above-mentioned higher layer parameter to overlap with the uplink symbols, or if the SBFD symbols configured by the above-mentioned higher layer parameter overlap with the uplink symbols, the UE considers the SBFD symbols overlapping with the uplink symbols to be non-SBFD symbols in practice.

[0096] In some embodiments, the SBFD symbols overlap with the downlink symbols or the flexible symbols, or in other words, the SBFD symbols are configured within the range of the downlink symbols and / or the flexible symbols.

[0097] In some embodiments, the SBFD symbol includes a DL SBFD symbol and / or a Flexible SBFD symbol, and the non-SBFD symbol includes a Full-DL symbol and / or a Full-Flexible symbol and / or a Full-UL symbol (or UL symbol). The symbols can also be represented in other ways, and are not limited thereto.

[0098] FIG. 3 is an example diagram of time domain resources according to embodiments of the present disclosure. As shown in FIG. 3, a period can include a plurality of different symbols. Among them, the SBFD symbol is within the range of downlink symbols and flexible symbols, the SBFD symbol overlapping with the downlink symbol is denoted as a DL SBFD symbol, the SBFD symbol overlapping with the flexible symbol is denoted as a Flexible SBFD symbol, the downlink symbol not overlapping with the SBFD symbol is denoted as a Full-DL symbol, the flexible symbol not overlapping with the SBFD symbol is denoted as a Full-Flexible symbol, and the UL symbol not overlapping with the SBFD symbol is denoted as a Full-UL symbol (assuming that the UL symbol cannot be used as the SBFD symbol, and the Full-UL symbol is equivalent to the UL symbol). FIG. 3 exemplarily illustrates the time domain resources according to embodiments of the present disclosure, but is not limited thereto.

[0099] The frequency domain resources according to embodiments of the present disclosure are further exemplarily described below.

[0100] For a cell and / or a carrier, in the first time domain resource, the first frequency domain resource is (only) used for uplink and the second frequency domain resource is (only) used for downlink, that is, the frequency domain resources are divided into the first frequency domain resource (only) used for uplink and the second frequency domain resource (only) used for downlink. The second time domain resource is outside the first time domain resource, that is, in the second time domain resource, the frequency domain resources are not divided as described above.

[0101] For example, the first frequency domain resource includes an uplink subband (UL subband) and / or uplink available PRBs, and the second frequency domain resource includes a downlink subband (DL subband) and / or downlink available PRBs, which can also be represented in other ways, and are not limited thereto.

[0102] In some embodiments, the UE receives information for configuring the UL subband and the DL subband. For example, the uplink subband and the downlink subband respectively include an integer number of PRBs, and the information for configuring the UL subband and the DL subband respectively includes information for indicating the corresponding starting PRB and bandwidth.

[0103] In some embodiments, the information for configuring the UL subband and the DL subband is provided by higher layer signaling. For example, the higher layer parameters for configuring the DL subband are optionally present in SIB1 (in SIB Common Serving Cell Configuration (ServingCellConfigCommonSIB) IE (in SIB Common Downlink Configuration (DownlinkConfigCommonSIB) IE (in SIB Downlink Frequency Info (FrequencyInfoDL-SIB) IE (in SCS-Specific Carrier (SCS-SpecificCarrier) IE))), for example, the inclusion relationship of the above parameters can be represented as: SIB1 > ServingCellConfigCommonSIB > DownlinkConfigCommonSIB > FrequencyInfoDL-SIB > SCS-SpecificCarrier; and / or,

[0104] The higher layer parameters for configuring the DL subband are optionally present in Common Serving Cell Configuration (ServingCellConfigCommon) IE (in Common Downlink Configuration (DownlinkConfigCommon) IE (in Downlink Frequency Info (FrequencyInfoDL) IE (in SCS-Specific Carrier (SCS-SpecificCarrier) IE))), for example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > DownlinkConfigCommon > FrequencyInfoDL > SCS-SpecificCarrier, and / or, optionally present in Serving Cell Configuration (ServingCellConfig). That is, the higher layer parameters for configuring the DL subband can be optionally present in one or more of the above parameters.

[0105] For example, the high layer parameters for configuring UL subband are optionally present in SIB1 (in SIB Common Serving Cell Config (ServingCellConfigCommonSIB) IE (in SIB Common Uplink Config (UplinkConfigCommonSIB) IE (in SIB Uplink Frequency Info (FrequencyInfoUL-SIB) IE (in SCS-SpecificCarrier IE))), and the inclusion relationship of the above parameters can be represented as: SIB1 > ServingCellConfigCommonSIB > UplinkConfigCommonSIB > FrequencyInfoUL-SIB > SCS-SpecificCarrier, and / or,

[0106] The high layer parameters for configuring UL subband are optionally present in Common Serving Cell Config (ServingCellConfigCommon) IE (in Common Uplink Config (UplinkConfigCommon) IE (in Uplink Frequency Info (FrequencyInfoUL) IE (in SCS-SpecificCarrier IE))), and the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > UplinkConfigCommon > FrequencyInfoUL > SCS-SpecificCarrier, and / or, optionally present in Serving Cell Config (ServingCellConfig). That is, the high layer parameters for configuring UL subband can optionally be present in one or more of the above parameters.

[0107] In some embodiments, the high layer parameters for configuring UL subband and the high layer parameters for configuring DL subband include one or more parameters for providing RIV (resource indication value) and / or SCS (corresponding to UL / DL subband), that is, respectively indicating the starting RB (RB start ) and bandwidth (including the number of RBs, L RBs ) of UL subband and DL subband based on RIV.

[0108] For example, the resource indication value can be defined as in Table 1 below.

[0109] Table 1

[0110] For example, for DL / UL subband: assume in Table 1 In addition, the first PRB (RB start The PRB corresponding to the minimum value (0 or 1) of the RB set of the first PRB can be determined as follows: the first PRB is determined by the PRB determined by the corresponding subcarrierSpacing and offsetToCarrier in ServingCellConfigCommon / ServingCellConfigCommonSIB (configured in the corresponding SCS-SpecificCarrier in FrequencyInfoDL (for DL subband) / RequencyInfoUL (for UL subband) / FequencyInfoUL-SIB (for UL subband) / HequencyInfoDL-SIB (for DL subband)).

[0111] In some embodiments, in a cell, the scs-SpecificCarrierList for UL and DL respectively can include one or more SCS-SpecificCarrier IE, each SCS-SpecificCarrier IE respectively corresponds to / includes one SCS configuration (subcarrierSpacing), that is, the scs-SpecificCarrierList for UL and DL respectively can include one or more SCS configurations.

[0112] For example, different / each SCS configuration in UL scs-SpecificCarrierList is respectively configured with / corresponds to one UL subband, for example, respectively corresponds to independent above-mentioned higher layer parameter for configuring UL subband. Different / each SCS configuration in DL scs-SpecificCarrierList is respectively configured with / corresponds to one or more (for example, 2) DL subbands, for example, respectively corresponds to independent above-mentioned higher layer parameter for configuring DL subband, wherein if one SCS configuration is configured with multiple DL subbands, the corresponding higher layer parameter for configuring DL subband includes multiple above-mentioned RIV.

[0113] In some embodiments, the UE does not expect the DL subband and the UL subband to overlap (in the frequency domain).

[0114] In some embodiments, the uplink usable PRBs include PRBs in the intersection between (PRBs in) the (activated) UL BWP and (PRBs in) the (corresponding) UL subband. For example, for one UL BWP, the intersection is determined according to the uplink subband corresponding to the SCS of the UL BWP. For example, if the SCS of one UL BWP is 15 kHz, then the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband corresponding to SCS = 15 kHz. If the SCS of one UL BWP is 30 kHz, then the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband corresponding to SCS = 15 kHz.

[0115] FIG. 4 is an example diagram of uplink usable PRBs according to embodiments of the present application. As shown in FIG. 4, the UL BWP and the UL subband overlap, and the UL usable PRBs are the intersection between the two. The UL subband therein may, for example, represent the uplink subband corresponding to the SCS of the UL BWP, but the present application is not limited thereto.

[0116] In some embodiments, the downlink usable PRBs include PRBs in the intersection between (PRBs in) the (activated) DL BWP and (PRBs in) the (corresponding) DL subband. For example, for one DL BWP, the intersection is determined according to the downlink subband corresponding to the SCS of the DL BWP. For example, if the SCS of one DL BWP is 15 kHz, then the corresponding DL usable PRBs are the intersection between the DL BWP and the downlink subband corresponding to SCS = 15 kHz. If the SCS of one DL BWP is 30 kHz, then the corresponding DL usable PRBs are the intersection between the DL BWP and the uplink subband corresponding to SCS = 15 kHz.

[0117] FIG. 5 is an example diagram of downlink usable PRBs according to embodiments of the present application. As shown in FIG. 5, the DL BWP and the DL subband overlap, and the DL usable PRBs are the intersection between the two. The DL subband therein may, for example, represent the downlink subband corresponding to the SCS of the DL BWP, but the present application is not limited thereto.

[0118] The above has been a schematic description of time-frequency resources, and the following is a schematic description of embodiments of the present application.

[0119] In embodiments of the present application, for PDSCH, one repetition can also be referred to as / correspond to one PDSCH reception (occasion), and for PUSCH, one (for Type B: nominal / actual) repetition or one (of N*K) slots (of allocated symbols) can also be referred to as / correspond to one PUSCH transmission (occasion).

[0120] In the embodiments of the present application, the overlapping with the first time domain resource includes partial overlapping (i.e., part of the time domain resource is within the first time domain resource, and part of the time domain resource is within the second time domain resource) and / or complete overlapping (at this time, it can also be said that it is within the first time domain resource). The overlapping with the second time domain resource includes partial overlapping (i.e., part of the time domain resource is within the second time domain resource, and part of the time domain resource is within the first time domain resource) and / or complete overlapping (at this time, it can also be said that it is within the second time domain resource).

[0121] In some embodiments, the overlapping with the first time domain resource and the overlapping with the second time domain resource do not include the above-mentioned partial overlapping at the same time, for example, if the overlapping with the first time domain resource includes partial overlapping, the overlapping with the second time domain resource does not include partial overlapping, and vice versa, but the present application is not limited thereto.

[0122] The following is described first for PDSCH.

[0123] In some embodiments, the DCI used to schedule PDSCH is referred to as first DCI, for example, which is DCI format 1_0, or DCI format 1_1, or DCI format 1_2, or DCI format 1_3, or DCI format 4_0, or DCI format 4_1 or DCI format 4_2 or other format, not limited thereto.

[0124] In some embodiments, the first DCI schedules multiple PDSCHs (multi-PDSCHs), and different PDSCHs in the multiple PDSCHs correspond to / have one or more of independent SLIVs mapping type, slot offset K0, HARQ process ID and TB. Among them, the DCI used to schedule multiple PDSCHs is DCI format 1_1, but not limited thereto.

[0125] In some embodiments, when the UE is provided with a high-layer parameter for configuring SBFD symbols and / or a high-layer parameter for configuring DL subbands and / or a high-layer parameter for configuring UL subbands: the operation as described in Table 2 can be performed:

[0126] Table 2

[0127] In some embodiments, the first DCI schedules a PDSCH with repetition, the PDSCH with repetition corresponds to one SLIV, one mapping type, one slot offset, one HARQ process ID and one TB. Wherein, the DCI used to schedule the PDSCH with repetition is for example DCI format 1_1 or DCI format 1_2, or DCI format 1_3, or DCI format 4_0, or DCI format 4_1 or DCI format 4_2, but not limited thereto.

[0128] In some embodiments, the PDSCH with repetition corresponds to a TB which is repeated in multiple consecutive slots, the same symbol allocation / SLIV is applied to the multiple slots (that is to say, the multiple slots correspond to the same symbols (indices) used to transmit the TB), different repetitions (or referred to as transmission opportunities) correspond to for example different redundancy versions, but not limited thereto. The number of repetitions or the number of slots included in the above-mentioned multiple slots is determined by pdsch-AggregationFactor or repetitionNumber (corresponding to the row indicated by the TDRA field of the first DCI).

[0129] For example, for DCI format 1_1 or DCI format 1_2, or DCI format 1_3 (scheduling PDSCH) with CRC scrambled by C-RNTI or MCS-RNTI or CS-RNTI (with NDI = 1), the number is determined by pdsch-AggregationFactor or repetitionNumber (corresponding to the row indicated by the TDRA field of the first DCI) in the PDSCH configuration (pdsch-config) (for example, equal to the number configured by the pdsch-AggregationFactor / repetitionNumber), wherein if the UE is configured with repetitionNumber, pdsch-AggregationFactor is not expected to be configured.

[0130] For CRC scrambled by G-RNTI for broadcast, the number is determined by pdsch-AggregationFactor in the first PTM PDSCH configuration (PDSCH-ConfigPTM) (e.g., equal to the number configured by this pdsch-AggregationFactor), for CRC scrambled by G-RNTI for multicast, the number is determined by pdsch-AggregationFactor in the MBS RNTI specific configuration (MBS-RNTI-SpecificConfig) (e.g., equal to the number configured by this pdsch-AggregationFactor), for CRC scrambled by G-RNTI for multicast in RRC_INACTIVE state, the number is determined by pdsch-AggregationFactor in the second PTM PDSCH configuration (PDSCH-ConfigPTM-r18) (e.g., equal to the number configured by this pdsch-AggregationFactor).

[0131] In some embodiments, the frequency domain resources indicated by the first DCI include PRBs indicated / allocated by the FDRA field in the first DCI, e.g., these PRBs can be referred to as assigned / allocated PRBs. The frequency domain resources indicated by the first DCI within the second frequency domain resources include / are determined as the intersection (of PRBs) between the frequency domain resources indicated by the first DCI and the second frequency domain resources, e.g., these PRBs can be referred to as assigned / allocated PRBs within DL usable PRBs (or DL subband). Where the second frequency domain resources refer to a DL subband, the DL subband corresponding to the SCS of the PDSCH scheduled by the first DCI should be used, e.g., the SCS of the PDSCH is / equals the SCS of the DL BWP in which it is located, but not limited thereto.

[0132] For example, determining TBS according to the frequency domain resource includes: determining TBS according to the number of PRBs included in the frequency domain resource, for example, in the process of determining TBS, the UE needs to determine the number of REs (within a slot), for example, a UE determines the total number of REs allocated for PDSCH (N RE )by N RE =min(156,N' RE )·n PRB , where n PRB is the number of allocated PRBs or the number of allocated PRBs within DL usable PRBs (or DL subband), N′ RE is the number of REs allocated for PDSCH within a PRB.

[0133] In some embodiments, for a PDSCH in the plurality of PDSCHs:

[0134] For a PDSCH overlapping with SBFD symbols, determining transport block size (TBS) according to the frequency domain resource (e.g. assigned / allocated PRBs within DL usable PRBs) within the second frequency domain resource indicated by the first DCI, for a PDSCH overlapping with non-SBFD symbols, determining TBS according to the frequency domain resource (e.g. assigned / allocated PRBs) indicated by the first DCI; or,

[0135] For both a PDSCH overlapping with SBFD symbols and a PDSCH overlapping with non-SBFD symbols, determining TBS according to the frequency domain resource indicated by the first DCI.

[0136] In some embodiments, for a PDSCH:

[0137] Determining TBS according to the frequency domain resource within the second frequency domain resource indicated by the first DCI or the frequency domain resource indicated by the first DCI, in relation to the valid time domain resource type and / or the invalid time domain resource type and / or the reference repetition and / or the corresponding (assigned) symbol in the first slot and / or the number of repetitions overlapping with the first time domain resource and / or the number of repetitions overlapping with the second time domain resource.

[0138] For example, for a PDSCH among the multiple PDSCHs, it is related to the valid time domain resource type and / or invalid time domain resource type and / or corresponding (allocated) symbol in the first slot, for a PDSCH with repetition, it is related to the valid time domain resource type and / or invalid time domain resource type and / or reference repetition and / or corresponding (allocated) symbol in the first slot and / or number of repetitions overlapping with the first time domain resource and / or number of repetitions overlapping with the second time domain resource.

[0139] For example, the first reference repetition is the first repetition of the first DCI or the first repetition meeting the first condition, and / or the first slot is the first PDSCH (for multi-PDSCH) or the slot corresponding to the first reference repetition or the first repetition or the slot determined by the first time slot offset indicated by the first DCI. Wherein, for the case of repetition, the first time slot offset is, for example, the time slot offset K0.

[0140] For example, the slot determined by the time slot offset K0 includes, for example, the slot Wherein, n is the slot with the scheduling DCI (i.e. the first DCI mentioned above), μ HCSDP And μ PDCCH Are the subcarrier spacing configurations for PDSCH and PDCCH, respectively.

[0141] For example, the first condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as uplink (by the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or not overlapping with both SBFD symbols and non-SBFD symbols.

[0142] For example, the second uplink-downlink configuration is used to provide UE-specific / dedicated uplink-downlink configuration, for example, tdd-UL-DL-ConfigurationDedicated, and the present application is not limited thereto. For example, the third uplink-downlink configuration is dedicated to indicating the uplink-downlink of SBFD symbols, which is different from the first uplink-downlink configuration / second uplink-downlink configuration.

[0143] In some embodiments, the second uplink-downlink configuration is used to configure the uplink-downlink of SBFD symbols and / or non-SBFD symbols.

[0144] In some embodiments, the second uplink-downlink configuration is only for configuring uplink / downlink of non-SBFD symbols. For example, the UE does not expect a symbol indicated as uplink / downlink by the second uplink-downlink configuration to overlap with SBFD symbols, or, when a symbol indicated as uplink / downlink by the second uplink-downlink configuration overlaps with SBFD symbols, the UE ignores the indication for that symbol.

[0145] In some embodiments, for multi-PDSCH and PDSCH with repetition, each PDSCH / repetition is respectively within SBFD symbols or non-SBFD symbols, or respectively has full SBFD symbols or full non-SBFD symbols, e.g., the UE does not expect (first DCI scheduled) any PDSCH / repetition to overlap with both SBFD symbols and non-SBFD symbols. Or, the first PDSCH / first repetition / reference PDSCH / first reference repetition / second reference repetition is within SBFD symbols or non-SBFD symbols, or has full SBFD symbols or full non-SBFD symbols, e.g., the UE does not expect the first PDSCH / first repetition / reference PDSCH / first reference repetition / second reference repetition to overlap with both SBFD symbols and non-SBFD symbols.

[0146] In some embodiments, the time domain resource type e.g., includes slot type and / or symbol type, e.g., time domain resources are divided into 2 types, the above SBFD symbols and non-SBFD symbols.

[0147] -Case 1: with invalid time domain resource type, e.g., one of SBFD symbols and non-SBFD symbols is invalid, and the other is valid.

[0148] --case 1-1: SBFD symbols are invalid time domain resource type, or in other words, the invalid time domain resource type is SBFD symbols (e.g., the invalid symbol type is SBFD symbols, or SBFD symbols are invalid), and non-SBFD symbols are valid time domain resource type, or in other words, the valid time domain resource type is non-SBFD symbols (e.g., the valid symbol type is non-SBFD symbols, or non-SBFD symbols are valid).

[0149] --case 1-2: the valid symbol type is SBFD symbols, or SBFD symbols are valid, the invalid symbol type is non-SBFD symbols, or non-SBFD symbols are invalid

[0150] --case 2: no invalid symbol type, e.g., SBFD symbols and non-SBFD symbols are both valid.

[0151] In some embodiments, for PDSCH, corresponding to case 1, it can also be said that PDSCH reception is limited to SBFD symbols only (when SBFD symbols are valid, non-SBFD symbols are invalid, case 1-2) or limited to non-SBFD symbols only (when non-SBFD symbols are valid, SBFD symbols are invalid, case 1-1). For example, for a PDSCH among multiple PDSCHs, only the PDSCH that overlaps with SBFD symbols is received or only the PDSCH that overlaps with non-SBFD symbols is received. For a PDSCH with repetitions, only the repetitions that overlap with SBFD symbols are received or only the repetitions that overlap with non-SBFD symbols are received.

[0152] In some embodiments, for PDSCH, corresponding to case 2, it can also be said that PDSCH reception can be across SBFD symbols and non-SBFD symbols. For a PDSCH among multiple PDSCHs, both the PDSCH that overlaps with SBFD symbols and the PDSCH that overlaps with non-SBFD symbols can be received. For a PDSCH with repetitions, both the repetitions that overlap with SBFD symbols and the repetitions that overlap with non-SBFD symbols can be received.

[0153] The following is illustratively described for the above various cases, respectively.

[0154] In some embodiments, for a PDSCH among multiple PDSCHs or a PDSCH with repetitions:

[0155] when the SBFD symbols are invalid symbol type, determine TBS according to the frequency domain resource indicated by the first DCI; and / or,

[0156] When the SBFD symbol is not the invalid time domain resource type, the TBS is determined according to the frequency domain resources within the second frequency domain resources indicated by the first DCI or the frequency domain resources indicated by the first DCI.

[0157] In some embodiments, the SBFD symbol is not the invalid time domain resource type, including: the case 1-2 and / or case 2 described above.

[0158] In some embodiments, for a PDSCH in the plurality of PDSCHs:

[0159] When there is no invalid time domain resource type, for the PDSCHs overlapping with the SBFD symbol, the TBS is determined according to the frequency domain resources within the second frequency domain resources indicated by the first DCI, and for the PDSCHs overlapping with the non-SBFD symbol, the TBS is determined according to the frequency domain resources indicated by the first DCI.

[0160] In some embodiments, for a PDSCH with repetition:

[0161] When there is no invalid time domain resource type,

[0162] If the first reference repetition (e.g., the first time repetition) and / or the allocated symbol in the first slot and / or a certain number of repetitions overlap with the non-SBFD symbol, the TBS is determined according to the frequency domain resources indicated by the first DCI; and / or,

[0163] If the first reference repetition and / or the allocated symbol in the first slot and / or a certain number of repetitions overlap with the SBFD symbol, the TBS is determined according to the frequency domain resources within the second frequency domain resources indicated by the first DCI.

[0164] In some embodiments, for a PDSCH with repetition:

[0165] If the first reference repetition or the allocated symbol in the first slot and / or a certain number of repetitions overlap with the non-SBFD symbol, the TBS is determined according to the frequency domain resources indicated by the first DCI, and / or,

[0166] If the first reference repetition or the allocated symbol in the first slot and / or a certain number of repetitions overlap with the SBFD symbol, the TBS is determined according to the frequency domain resources within the second frequency domain resources indicated by the first DCI.

[0167] In some embodiments, for a PDSCH:

[0168] When the SBFD symbol is of invalid time domain resource type, the PDSCH (for multi-PDSCH) or repetition (for PDSCH with repetition) overlapping with the SBFD symbol is not received (dropped),

[0169] When the non-SBFD symbol is of invalid time domain resource type, the PDSCH (for multi-PDSCH) or repetition (for PDSCH with repetition) overlapping with the non-SBFD symbol is not received (dropped).

[0170] In some embodiments, for PDSCH:

[0171] (When the SBFD symbol is not of invalid time domain resource type, ) for PDSCH and / or repetition overlapping with the SBFD symbol, the frequency domain resources outside the second frequency domain resources indicated by the first DCI (e.g. assigned / allocated PRBs outside DL usable PRBs) are invalid, that is, only the frequency domain resources within the second frequency domain resources indicated are valid.

[0172] In some embodiments, for PDSCH, the resource allocation type includes a first resource allocation type (resource allocation type 0) or a second resource allocation type (resource allocation type 1).

[0173] For example, in resource allocation type 0, the FDRA field (or referred to as resource block assignment information) in the first DCI includes a bitmap indicating RBGs, which is described as follows: the bitmap is of size N RBGbits with one bitmap bit per RBG such that each RBG (in the (active) DL BWP) is addressable. The RBGs shall be indexed in the order of increasing frequency of the bandwidth part and starting at the lowest frequency. The order of RBG bitmap is such that RBG 0 to RBG N RBG -1 are mapped from MSB to LSB of the bitmap. The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise. Where N RBG is the number of RBGs in the DL BWP.

[0174] For example, in resource allocation type 1, the FDRA field (or referred to as resource block assignment information) in the first DCI includes a resource indication value (RIV) indicating a set of contiguously allocated non-interleaved virtual resource blocks within the active bandwidth part. For example, the RIV corresponds to a starting virtual resource block (RB start ) and a length in terms of contiguously allocated resource blocks L RBs , where the definition of RIV is as previously described, for PDSCH scheduling, is the number of PRBs in the (active) DL BWP.

[0175] The following further describes how to configure and determine invalid time-domain resource types and / or valid time-domain resource types.

[0176] In some embodiments, for PDSCH:

[0177] The invalid time-domain resource type and / or the valid time-domain resource type is determined based on the first information and / or the second information and / or the reference PDSCH and / or the second reference repetition and / or the allocated symbols in the second slot.

[0178] For example, the first information is used to determine which one of case 1 and case 2 corresponds. For example, the first information is used to indicate no invalid time-domain resource type (i.e., case 2) and / or to indicate with invalid time-domain resource type (i.e., case 1).

[0179] For example, (when the first information is only used to indicate case 2, or the first information is used to indicate case 1 also to indicate case 2,) if the first information indicates Case 2, or, (when the first information is only used to indicate case 1,) if the first information is not provided, or, (when the first information is only used to indicate case 2,) if the first information is provided, it is case 2.

[0180] For example, (when the first information is only used to indicate case 1, or the first information is used to indicate case 1 also to indicate case 2,) if the first information indicates Case 1, or, (when the first information is only used to indicate case 2,) if the first information is not provided, or, (when the first information is only used to indicate case 1,) if the first information is provided: (it is case 1.) For multi-PDSCH, the UE determines whether it is case 1-1 or Case 1-2 according to the second information and / or the reference PDSCH and / or the allocated symbols in the second slot, and / or, for PDSCH repetition, the UE determines whether it is Case 1-1 or Case 1-2 according to the second information and / or the second reference repetition and / or the allocated symbols in the second slot. The second information is included in the first DCI, for example, without limitation.

[0181] For example, for Multi-PDSCH, if the reference PDSCH is in non-SBFD symbols, it is case 1-1; if the reference PDSCH overlaps with SBFD symbols, it is case 1-2.

[0182] For example, for PDSCH with repetition, if the second reference repetition overlaps with non-SBFD symbols, it is case 1-1; if the second reference repetition overlaps with SBFD symbols, it is case 1-2.

[0183] For example, the reference PDSCH is the first PDSCH scheduled by the first DCI, or the first PDSCH satisfying the first condition, and / or, the second reference repetition is the first repetition scheduled by the first DCI, or the repetition satisfying the first condition, and / or, the second slot is the slot corresponding to the first PDSCH or the first repetition, or the reference PDSCH or the second reference repetition, or a slot determined by a first slot offset indicated by the first DCI.

[0184] In some embodiments, the second reference repetition is the same as the aforementioned first reference repetition, e.g., the first condition is the same (thus, corresponding to the same repetition) for both the first reference repetition and the second reference repetition. In other embodiments, the first reference repetition and the second reference repetition are different, e.g., the first conditions corresponding to the two are different (thus, possibly corresponding to the same or different repetitions).

[0185] For example, the first condition is, for both, not overlapping with non-SBFD symbols indicated as uplink. For another example, the first condition is, for both, not overlapping with both SBFD symbols and non-SBFD symbols.

[0186] For another example, the first condition is, for the first reference repetition, not overlapping with non-SBFD symbols indicated as uplink, and, for the second reference repetition, not overlapping with both SBFD symbols and non-SBFD symbols. For yet another example, the first condition is, for the first reference repetition, not overlapping with both SBFD symbols and non-SBFD symbols, and, for the second reference repetition, not overlapping with non-SBFD symbols indicated as uplink.

[0187] In some embodiments, the first slot and the second slot are the same. In other embodiments, the first slot and the second slot are different.

[0188] The following is further explained for PUSCH.

[0189] In some embodiments, the DCI used for scheduling PUSCH is referred to as second DCI, e.g., the DCI is DCI format 0_1, or DCI format 0_2, or DCI format 0_3, or other formats, not limited thereto.

[0190] In some embodiments, the second DCI schedules multi-PUSCHs, different PUSCHs of the multi-PUSCHs correspond / have one or more of independent SLIVs mapping type, slot offset K2, HARQ process ID and TB. Wherein, the DCI for scheduling multi-PUSCHs is, for example, DCI format 0_1, but not limited thereto.

[0191] In some embodiments, when the UE is provided with the higher layer parameter for configuring SBFD symbols and / or the higher layer parameter for configuring DL subband and / or the higher layer parameter for configuring UL subband: the operation as described in Table 3 can be performed.

[0192] Table 3

[0193] In some embodiments, the PUSCH scheduled by the second DCI has repetition and / or TBoMS (PUSCH with repetition / TBoMS), the PUSCH corresponds to one SLIV, one mapping type, one slot offset, one HARQ process ID and one TB. Wherein, the DCI for scheduling PUSCH with repetition and / or TBoMS is, for example, DCI format 0_1 or DCI format 0_2, or DCI format 0_3, but not limited thereto.

[0194] In some embodiments, the repetition includes a first repetition type and / or a second repetition type. The first repetition type is, for example, PUSCH repetition type A, the first repetition type is, for example, PUSCH repetition type B, but not limited thereto.

[0195] In some embodiments, the PUSCH scheduled by different DCI formats correspond to independent repetition type configuration, and then the corresponding repetition type can be determined respectively. For example, for the PUSCH scheduled by DCI format 0_1 or DCI format 0_2, if the higher layer parameter pusch-RepTypeIndicatorDCI-0-1 (corresponding to DCI format 0_1) or pusch-RepTypeIndicatorDCI-0-2 (corresponding to DCI format 0_2) is set to 'pusch-RepTypeB', the UE applies the PUSCH repetition type B procedure, otherwise the UE applies the PUSCH repetition type A procedure. Wherein, the above-mentioned higher layer parameter exists in PUSCH-Config IE for example, but not limited thereto.

[0196] In some embodiments, for the PUSCH scheduled by DCI format 0_1 or DCI format 0_2 or DCI format 0_3, if the higher layer parameter numberOfSlotsTBoMS exists and is greater than 1, the UE applies the TB processing over multiple slots procedure. Wherein, the above-mentioned higher layer parameter is included in PUSCH-Allocation-r16 for example, but not limited thereto.

[0197] In some embodiments, the frequency domain resources indicated by the FDRA field in the second DCI include the PRBs indicated / allocated by the FDRA field in the second DCI, which can be referred to as assigned / allocated PRBs for short. The frequency domain resources indicated by the FDRA field in the second DCI within the first frequency domain resources include / are determined as the intersection (PRBs) between the frequency domain resources indicated by the FDRA field in the second DCI and the first frequency domain resources, which can be referred to as assigned / allocated PRBs within UL usable PRBs (or UL subband) for short. Wherein, when the first frequency domain resources refer to UL subband, the UL subband corresponding to the SCS of the PUSCH scheduled by the second DCI should be used, and the SCS of the PUSCH is / equals to the SCS of the UL BWP where the PUSCH is located for example, but not limited thereto.

[0198] For example, determining the TBS based on the aforementioned frequency domain resources includes: determining the TBS based on the number of PRBs included in the frequency domain resources. For example, in the process of determining the TBS, the UE needs to determine the number of REs (within the time slot). For example, a UE determines the total number of REs allocated for PUSCH(N). RE by N RE =N*min(156,N′) RE )·n PRB (For the case of TBoMS), or N RE =min(156,N') RE )·n PRB (For other cases where TboMS is not available), where n PRB It refers to the number of allocated PRBs or the number of allocated PRBs within UL usable PRBs (or UL subband), N R ′ E N is the number of REs allocated for PUSCH within a PRB, and N is the number of slots (time slots) used for TBS determination, indicated by numberOfSlotsTBoMS.

[0199] In some embodiments, for PUSCH, the resource allocation type includes a first resource allocation type (resource allocation type 0) or a second resource allocation type (resource allocation type 1).

[0200] For example, in resource allocation type 0, the FDRA field (or resource block assignment information) in the second DCI includes a bitmap indicating RBGs, the relevant description of which is as follows: the bitmap is of size N RBGbits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be indexed in the order of increasing frequency of the bandwidth part and starting at the lowest frequency. The order of RBG bitmap is such that RBG 0 to RBG N RBG -1 are mapped from MSB to LSB of the bitmap. The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise. wherein, N RBG is the number of RBGs in the UL BWP.

[0201] For example, in resource allocation type 1, the FDRA field (or referred to as resource block assignment information) in the second DCI includes a resource indication value (RIV) indicating a set of contiguously allocated non-interleaved virtual resource blocks within the active bandwidth part. For example, the RIV corresponds to a starting virtual resource block (RB start ) and a length in terms of contiguously allocated resource blocks L RBs , wherein the definition of RIV is as previously described for PUSCH scheduling, is the number of PRBs in the (active) UL BWP.

[0202] For example, for PUSCH scheduled by DCI format 0_2 / 0_3, RIV corresponds to a starting resource block group RBG start = 0, 1, …, N RBG -1 and a length in terms of virtually contiguously allocated resource block groups L RBGs = 1, …, N RBG where the RIV is defined as follows:

[0203] Table 4

[0204] where, for RIV and the above bitmap, N RBG has the same or different values. For example, for RIV and the above bitmap, the parameter P used to determine N RBG has different higher layer parameters. For example, for DCI format 0_2 and 0_3, the parameter P used to determine N RBG has different higher layer parameters.

[0205] In some embodiments, for a PUSCH of the plurality of PUSCHs:

[0206] For PUSCHs overlapping with SBFD symbols, TBS is determined according to the frequency domain resources (e.g. assigned / allocated PRBs within UL usable PRBs) indicated by the second DCI within the first frequency domain resources, and for PUSCHs overlapping with non-SBFD symbols, TBS is determined according to the frequency domain resources (e.g. assigned / allocated PRBs) indicated by the second DCI; or,

[0207] For both PUSCHs overlapping with SBFD symbols and PUSCHs overlapping with non-SBFD symbols, TBS is determined according to the frequency domain resources indicated by the second DCI.

[0208] In some embodiments, for a PUSCH:

[0209] The TBS is determined based on the frequency domain resources within the first frequency domain resources indicated by the second DCI or the frequency domain resources indicated by the second DCI, in relation to the valid time domain resource type and / or the invalid time domain resource type and / or the (frequency domain) resource allocation type and / or the third reference repetition and / or the corresponding (allocated) symbol in the third slot and / or the number of repetitions overlapping with SBFD symbols and / or the number of repetitions overlapping with non-SBFD symbols.

[0210] For example, for PUSCHs in multi-PUSCH, in relation to the valid time domain resource type and / or the invalid time domain resource type and / or the (frequency domain) resource allocation type and / or the corresponding (allocated) symbol in the third slot, for PUSCHs with repetition and / or TBoMS, in relation to the valid time domain resource type and / or the invalid time domain resource type and / or the (frequency domain) resource allocation type and / or the third reference repetition and / or the corresponding (allocated) symbol in the third slot and / or the number of repetitions overlapping with SBFD symbols and / or the number of repetitions overlapping with non-SBFD symbols.

[0211] For example, the third reference repetition is the first repetition scheduled by the second DCI or the first repetition satisfying a second condition, and / or the third slot is the first PUSCH (for multi-PUSCH) or the slot corresponding to the first repetition or the third reference repetition or the slot determined by a second slot offset indicated by the second DCI. For the case of repetition, the second slot offset is for example a slot offset K2.

[0212] For example, the slot determined by the slot offset K2 includes for example slots

[0213] (where K offset is a parameter configured by higher layer,and where is the subcarrier spacing configuration for K offset with a value of 0for frequency range 1 and for FR2-NTN,n is the slot with the scheduling DCI,K2 is based on the numerology of PUSCH,and μ PUSCH andμ PDCCHare the subcarrier spacing configurations for PUSCH and PDCCH, respectively).

[0214] For example, the second condition includes, but is not limited to, not overlapping with non-SBFD symbols indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols.

[0215] In some embodiments, for multi-PUSCH and PUSCH with repetition, each PUSCH / (nominal / actual) repetition (for Reptition Type B) is within SBFD symbols or non-SBFD symbols, respectively, or, has full SBFD symbols or full non-SBFD symbols, respectively, e.g., UE does not expect any of the (second DCI scheduled) PUSCH / (nominal / actual) repetition (for Reptition Type B) to overlap with both SBFD symbols and non-SBFD symbols. Or, the first PUSCH / first (nominal / actual) repetition (for Reptition Type B) / reference PUSCH / third reference (nominal / actual) repetition / fourth reference (nominal / actual) repetition is within SBFD symbols or non-SBFD symbols, or, has full SBFD symbols or full non-SBFD symbols, e.g., UE does not expect the first PUSCH / first (nominal / actual) repetition (for Reptition Type B) / reference PUSCH / third reference (nominal / actual) repetition / fourth reference (nominal / actual) repetition to overlap with both SBFD symbols and non-SBFD symbols.

[0216] In some embodiments, time domain resource type includes, for example, slot type and / or symbol type, e.g., time domain resources are divided into 2 types, the above SBFD symbols and non-SBFD symbols.

[0217] -Case 1: with invalid time domain resource type, e.g., one of SBFD symbols and non-SBFD symbols is invalid, and the other is valid.

[0218] -- case 1-1: SBFD symbols are invalid symbol type, or in other words, the invalid symbol type is SBFD symbols (e.g., the invalid symbol type is SBFD symbols, or SBFD symbols are invalid), non-SBFD symbols are valid symbol type, or in other words, the valid symbol type is non-SBFD symbols (e.g., the valid symbol type is non-SBFD symbols, or non-SBFD symbols are valid).

[0219] -- case 1-2: SBFD symbols are valid symbol type, or in other words, the valid symbol type is SBFD symbols (e.g., the valid symbol type is SBFD symbols, or SBFD symbols are valid), non-SBFD symbols are invalid symbol type, or in other words, the invalid symbol type is non-SBFD symbols (e.g., the invalid symbol type is non-SBFD symbols, or non-SBFD symbols are invalid).

[0220] - case 2: no invalid symbol type (e.g., no invalid symbol type), e.g., both SBFD symbols and non-SBFD symbols are valid.

[0221] In some embodiments, for PUSCH, for case 1, it can also be said that PUSCH transmission is limited to SBFD symbols only (when SBFD symbols are valid, non-SBFD symbols are invalid, case 1-2) or limited to non-SBFD symbols only (when non-SBFD symbols are valid, SBFD symbols are invalid, case 1-1). For example, for PUSCHs in a plurality of PUSCHs, only PUSCHs overlapping with SBFD symbols are transmitted or only PUSCHs overlapping with non-SBFD symbols are received. For PUSCHs with repetition, only repetitions (for repetition Type B: actual) overlapping with SBFD symbols are transmitted or only repetitions (for repetition Type B: actual) overlapping with non-SBFD symbols are transmitted.

[0222] In some embodiments, for PDSCH, corresponding to case 2, also said, PUSCH transmission can cross SBFD symbol and non-SBFD symbol. For PUSCH in multiple PUSCHs, PUSCHs overlapping with SBFD symbol or non-SBFD symbol can be received. For PDSCH with repetition, (actual) repetitions overlapping with SBFD symbol or non-SBFD symbol can be received for repetition Type B.

[0223] The following is illustratively described for the above various cases, respectively.

[0224] In some embodiments, for PUSCH in multiple PUSCHs or PUSCH with repetition or PUSCH with multi-slot TB (also referred to as PUSCH scheduling with TBoMS):

[0225] When SBFD symbol is invalid time domain resource type (case 1-1), TBS is determined according to frequency domain resource indicated by the second DCI; and / or,

[0226] When SBFD symbol is not invalid time domain resource type, TBS is determined according to frequency domain resource within the first frequency domain resource indicated by the second DCI or frequency domain resource indicated by the second DCI.

[0227] In some embodiments, SBFD symbol is not invalid time domain resource type, including: the above case 1-2 and / or the above case 2.

[0228] In some embodiments, for PUSCH in multiple PUSCHs or PUSCH with repetition and / or multi-slot TB:

[0229] When non-SBFD symbol is invalid time domain resource type (case 1-2), for first type resource allocation (Type 0), TBS is determined according to frequency domain resource within the first frequency domain resource indicated by the second DCI, and / or, for second type resource allocation (Type 1), TBS is determined according to frequency domain resource indicated by the second DCI; and / or,

[0230] When not having invalid time domain resource type (case 2), TBS is determined according to frequency domain resource indicated by the second DCI.

[0231] In some embodiments, when there is no invalid time domain resource type, for PUSCH overlapping with SBFD symbols, TBS is determined according to the frequency domain resources within the first frequency domain resources indicated by the second DCI or the frequency domain resources indicated by the second DCI, and for PUSCH overlapping with non-SBFD symbols, TBS is determined according to the frequency domain resources indicated by the second DCI.

[0232] In some embodiments, when there is no invalid time domain resource type, for PUSCH overlapping with SBFD symbols,

[0233] for a first type of resource allocation, TBS is determined according to the frequency domain resources within the first frequency domain resources indicated by the second DCI, and / or, for a second type of resource allocation, TBS is determined according to the frequency domain resources indicated by the second DCI.

[0234] In some embodiments, for PUSCH with repetition and / or multi-slot TB:

[0235] for a first type of resource allocation (Type 0), TBS is determined according to the frequency domain resources within the first frequency domain resources indicated by the second DCI, and / or, for a second type of resource allocation (Type 1), TBS is determined according to the frequency domain resources indicated by the second DCI; and / or,

[0236] when there is no invalid time domain resource type, if the allocated symbols in the third reference repetition and / or the third slot and / or a certain number of repetitions overlap with non-SBFD symbols, TBS is determined according to the frequency domain resources indicated by the second DCI; and / or, if the allocated symbols in the third reference repetition and / or the third slot and / or a certain number of repetitions overlap with SBFD symbols, TBS is determined according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0237] In some embodiments, for PUSCH with repetition and / or multi-slot TB:

[0238] if the allocated symbols in the third reference repetition (only for repetition) and / or the third slot (applicable to both repetition and multi-slot TB) and / or a certain number of repetitions (in non-SBFD symbols or) overlap with non-SBFD symbols, TBS is determined according to the frequency domain resources indicated by the second DCI, and / or,

[0239] If the third reference repetition (only for repetition) and / or the allocated symbols in the third slot (applicable for both repetition and multi-slot TB) and / or a number of repetitions (in SBFD symbols or not) overlap with the SBFD symbols, the TBS is determined according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0240] The following further describes how to configure and determine the invalid time domain resource type and / or the valid time domain resource type.

[0241] In some embodiments, for PUSCH:

[0242] The invalid time domain resource type and / or the valid time domain resource type is determined based on the third information and / or the fourth information and / or the reference PUSCH and / or the fourth reference repetition and / or the allocated symbols in the fourth slot.

[0243] For example, the third information is used to determine which one of case 1 and case 2 corresponds. For example, the third information is used to indicate no invalid time domain resource type (i.e. case 2) and / or to indicate with invalid time domain resource type (i.e. case 1).

[0244] For example, if the third information indicates Case 2, or, if no third information is provided, or, if the third information is provided: it is case 2, (when the third information is only used to indicate case 2, or the third information is used to indicate case 1 also indicates case 2).

[0245] For example, if the third information indicates Case 1, or, if no third information is provided, or, if the third information is provided: it is case 1, (when the third information is only used to indicate case 1, or the third information is used to indicate case 1 also indicates case 2).

[0246] For multi-PUSCH, the UE determines whether it is case 1-1 or Case 1-2 according to the fourth information and / or the reference PUSCH and / or the allocated symbols in the fourth slot, and / or, for PUSCH repetition, the UE determines whether it is case 1-1 or Case 1-2 according to the fourth information and / or the fourth reference repetition and / or the allocated symbols in the fourth slot. The fourth information is for example included in the second DCI, without being limited thereto.

[0247] For example, for Multi-PUSCH, if the reference PUSCH is in non-SBFD symbols, it is case 1-1; if the reference PUSCH overlaps with SBFD symbols, it is case 1-2.

[0248] For example, for Multi-PUSCH, if the reference PUSCH is in non-SBFD symbols, it is case 1-1; if the reference PUSCH overlaps with SBFD symbols, it is case 1-2.

[0249] For example, the reference PUSCH is the first PUSCH scheduled by the second DCI or the first PUSCH satisfying the second condition, and / or, the fourth reference repetition is the first repetition scheduled by the second DCI or the first repetition satisfying the second condition, and / or, the fourth slot is the slot corresponding to the first PDSCH or the first repetition or the reference PUSCH or the fourth reference repetition or a slot determined by a second slot offset indicated by the second DCI. Wherein, for a PUSCH with the second type of repetition: the repetition includes a nominal repetition and / or an actual repetition.

[0250] In some embodiments, the fourth reference repetition is the same as the aforementioned third reference repetition, for example, for the third reference repetition and the fourth reference repetition, the second condition is the same (thus, corresponding to the same repetition). In other embodiments, the third reference repetition and the fourth reference repetition are different, for example, the second conditions corresponding to the two are different (thus, possibly corresponding to the same or different repetitions).

[0251] For example, for the third reference repetition and the fourth reference repetition, the second condition is: not overlapping with non-SBFD symbols indicated as downlink. For another example, for the third reference repetition and the fourth reference repetition, the second condition is: not overlapping with both SBFD symbols and non-SBFD symbols.

[0252] For another example, for the third reference repetition, the second condition is: not overlapping with non-SBFD symbols indicated as downlink; for the fourth reference repetition, the second condition is: not overlapping with both SBFD symbols and non-SBFD symbols. For yet another example, for the third reference repetition, the second condition is: not overlapping with both SBFD symbols and non-SBFD symbols; for the fourth reference repetition, the second condition is: not overlapping with non-SBFD symbols indicated as downlink.

[0253] In some embodiments, the third slot and the fourth slot are the same. In other embodiments, the third slot and the fourth slot are different.

[0254] In some examples, the first information / third information can be defined jointly or separately for different types of scheduling.

[0255] For example, PDSCH scheduling and PUSCH scheduling correspond to independent first information and third information, respectively. For example, for PDSCH scheduling, the first information is provided in PDSCH-Config or PDSCH-ConfigCommon. For PUSCH scheduling, the third information is provided in PUSCH-Config or PUSCH-ConfigCommon. For example, mutli-PDSCH scheduling and PDSCH repetition scheduling correspond to independent first information, respectively. For example, different DCI formats for scheduling PDSCH can correspond to different / independent first information. For example, 2 or more of mutli-PUSCH, PUSCH repetition type A, PUSCH reptition type B, TBoMS scheduling correspond to independent third information, respectively. For example, different DCI formats for scheduling PUSCH can correspond to different / independent third information. For example, PDSCH scheduling and PUSCH scheduling correspond to the same information.

[0256] The above is for convenience of description, taking the use of first information / second information for PDSCH and the use of third information / fourth information for PUSCH as an example, and the present application is not limited thereto. For example, the first information and the third information can be the same information, and the second information and the fourth information can be the same information.

[0257] In some embodiments, for PUSCHs in the plurality of PUSCHs, or, PUSCHs with the first type of repetition without being configured with available slot counting (or, without being enabled with available slot counting), or, PUSCHs with the second type of repetition:

[0258] When SBFD symbols are invalid time domain resource type, PUSCH or (for repetition Type B: nominal / actual) repetitions overlapping with SBFD symbols are not transmitted (dropped), when non-SBFD symbols are invalid time domain resource type, PUSCH or (for repetition Type B: nominal / actual) repetitions overlapping with non-SBFD symbols are not transmitted (dropped).

[0259] In some embodiments, for PUSCH with PUSCH repetition Type B or for PUSCH repetition Type B, the above repetitions include nominal repetitions and / or actual repetitions, that is, when SBFD symbols are invalid time domain resource type, nominal repetitions overlapping with SBFD symbols are not transmitted (dropped), when non-SBFD symbols are invalid time domain resource type, nominal repetitions overlapping with non-SBFD symbols are not transmitted (dropped), or, when SBFD symbols are invalid time domain resource type, actual repetitions overlapping with SBFD symbols are not transmitted (dropped), when non-SBFD symbols are invalid time domain resource type, actual repetitions overlapping with non-SBFD symbols are not transmitted (dropped).

[0260] In some embodiments, for repetition Type B, the number of nominal repetitions is provided by numberOfRepetitions (corresponding to the row of TDRA field in the second DCI), for example, the (start / end) slot and (start / end) symbol corresponding to a nominal repetition are as described in Table 5 below:

[0261] Table 5

[0262] In some embodiments, the UE determines actual repetitions according to nominal repetitions, and the following is an illustrative description of how to determine actual repetitions.

[0263] In some embodiments, for PUSCH with PUSCH repetition Type B or for PUSCH repetition Type B:

[0264] According to the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration (e.g., the first uplink-downlink configuration and / or the second uplink-downlink configuration and / or the third uplink-downlink configuration) and / or the SSB, determine the actual repetition. For example, according to the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration (e.g., the first uplink-downlink configuration and / or the second uplink-downlink configuration and / or the third uplink-downlink configuration) and / or the SSB, determine the invalid symbols, the remaining / other symbols are considered as (potential) valid symbols, according to which the actual repetition is determined (e.g., in the manner shown in Table 6).

[0265] Table 6

[0266] In some embodiments, the UE determines a symbol that meets a third condition as an invalid symbol. For example, the third condition includes, but is not limited to: (for / applicable to case 1-1 / case 1-2 / case 2,) a non-SBFD symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, (for case 1-1,) a symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, (for case 1-2 / case 2,) a SBFD symbol indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, (for case 1-1 / case 1-2 / case 2,) a symbol (for receiving) an SSB, and / or, (for case 1-1,) a SBFD symbol, and / or, (for case 1-2,) a non-SBFD symbol.

[0267] For example, for case 1-1, the third condition includes, but is not limited to: a non-SBFD symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, a symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, a symbol (for receiving) an SSB, and / or, (for case 1-1,) a SBFD symbol.

[0268] For another example, for case 1-2, the third condition includes, but is not limited to: a non-SBFD symbol indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, a SBFD symbol indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, a symbol (for receiving) an SSB, and / or, (for case 1-1,) a SBFD symbol, and / or, a non-SBFD symbol.

[0269] For example, for case 1, the third condition includes but is not limited to: a non-SBFD symbol (indicated as downlink by (the first and / or second uplink-downlink configuration)), and / or a SBFD symbol (indicated as downlink by (the second and / or third uplink-downlink configuration)), and / or a symbol of (for reception of) SSB.

[0270] In some embodiments, (when the SBFD symbol and the non-SBFD symbol are not invalid time domain resource types), the UE does not transmit (drop) an actual repetition that overlaps with both the SBFD symbol and the non-SBFD symbol. For example, after the UE determines the actual repetitions according to the valid symbols, if one actual repetition overlaps with both the SBFD symbol and the non-SBFD symbol, the UE does not transmit (drop / omit) the actual repetition.

[0271] In some embodiments, (when the SBFD symbol and the non-SBFD symbol are not invalid time domain resource types), if one nominal repetition overlaps with both the SBFD symbol and the non-SBFD symbol, the nominal repetition corresponds to an actual repetition that overlaps with the SBFD symbol and an actual repetition that overlaps with the non-SBFD symbol, for example, the UE divides the nominal repetition and / or the actual repetition according to the (boundaries / borders of) the SBFD symbol and the non-SBFD symbol, for example, after the UE determines the actual repetitions according to the valid symbols, if one actual repetition overlaps with both the SBFD symbol and the non-SBFD symbol, the UE further divides the actual repetition into 2 or more actual repetitions, each of which includes all SBFD symbols (i.e., overlaps only with the SBFD symbol) or all non-SBFD symbols (overlaps only with the non-SBFD symbol).

[0272] In some embodiments, (when the SBFD symbol and non-SBFD symbol are not invalid time domain resource type, ) if one nominal repetition overlaps with both SBFD symbol and non-SBFD symbol, there is no corresponding actual repetition for the nominal repetition (or, drop / omit the nominal repetition). For example, for the nominal repetition, the number of (potentially) valid symbols is 0, and thus there is no corresponding actual repetition.

[0273] In some embodiments, for PUSCH with PUSCH repetition Type A, or, for PUSCH repetition Type A, the number of corresponding slots (N K slots) can be determined as described in Table 7, etc.:

[0274] Table 7

[0275] In some embodiments, for PUSCH with TBoMS, or for TBoMS, the number of corresponding slots (N K slots) can be determined as described in Table 8, etc.:

[0276] Table 8

[0277] In some embodiments, for the first repetition type and / or TBoMS, the symbol allocation can be determined as follows, i.e., the number of symbols allocated in one slot.

[0278] Table 9

[0279] For repetition Type A and TBoMS, the following is illustratively described how to determine the corresponding N K slots for PUSCH.

[0280] In some embodiments, for PUSCH with the first type of repetition with available slot counting enabled / configured, or, for PUSCH with multi-slot TB (whether or not with repetition at the same time):

[0281] The (N K) slots corresponding to the PUSCH are related to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or uplink / downlink configuration and / or SSB.

[0282] For example, the (N·K) slots corresponding to the PUSCH can be determined according to the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration (e.g., the first uplink-downlink configuration and / or the second uplink-downlink configuration and / or the third uplink-downlink configuration) and / or the SSB.

[0283] In some embodiments, for PUSCH repetition type A, without being configured with available slot count, the UE determines N·K consecutive slots for a PUSCH transmission of a PUSCH repetition type A scheduled by DCI format 0_1, 0_2 or 0_3, based on the TDRA information field value in the DCI format 0_1, 0_2 or 0_3.

[0284] In some embodiments, the slots in N·K slots satisfy the fourth condition, which is the same for case 1 / case 1-1 / case 1-2 / case 2. In some other embodiments, the slots in N·K slots satisfy the fourth condition, which is different for case 1 / case 1-1 / case 1-2 / case 2.

[0285] For example, the fourth condition includes but is not limited to: (for (applicable to) case 1-1 / case 1-2 / case 2,) not overlapping with non-SBFD symbols indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, (for case 1-1,) not overlapping with downlink symbols indicated by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, (for case 1-2 / case 2,) not overlapping with SBFD symbols indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, (for case 1-1 / case 1-2 / case 2,) not overlapping with SSB, and / or, (for case 1-1 / case 1-2 / case 2,) not overlapping with both SBFD symbols and non-SBFD symbols, and / or, (for case 1-1,) not overlapping with SBFD symbols, (for case 1-2,) not overlapping with non-SBFD symbols, and / or, (for case 1,) not overlapping with invalid time domain resource type.

[0286] For example, for case 1-1, the fourth condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, not overlapping with SBFD symbols indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols, and / or, not overlapping with non-SBFD symbols.

[0287] For example, for case 1-2, the fourth condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, not overlapping with SBFD symbols indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols, and / or, not overlapping with non-SBFD symbols.

[0288] For example, for case 2, the fourth condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (the first uplink-downlink configuration and / or the second uplink-downlink configuration), and / or, not overlapping with SBFD symbols indicated as downlink by (the second uplink-downlink configuration and / or the third uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols.

[0289] In some embodiments, if the symbols corresponding to one slot do not satisfy the fourth condition described above, it is not counted in the N·K slots.

[0290] In some embodiments, (for case 1 / case 1-1 / case 1-2 / case 2,) the fourth condition required for the first slot and other slots in the N·K slots is the same.

[0291] For example, Table 10 exemplarily shows one example of how to determine the slots corresponding to PUSCH for PUSCH repetition type A.

[0292] Table 10

[0293] In some embodiments, (for case 1,) the fourth condition required for the first slot and other slots in the N·K slots is different, for example, when determining the valid / invalid time domain resource type based on the fourth reference repetition.

[0294] In some embodiments, the first slot of the N·K slots is the same as the slot determined by the slot offset K2. For example, (for case 1,) the UE expects the slot determined by the slot offset K2 to satisfy one or more of the fourth conditions. For example, the UE expects the slot determined by the slot offset K2 to not overlap with non-SBFD symbols indicated as downlink by (the first and / or second uplink-downlink configurations), and not overlap with SSBs. For another example, the UE expects the slot determined by the slot offset K2 to not overlap with non-SBFD symbols indicated as downlink by (the first and / or second uplink-downlink configurations), not overlap with SBFD symbols indicated as downlink by (the second and / or third uplink-downlink configurations), not overlap with SSBs (not overlap with both SBFD symbols and non-SBFD symbols).

[0295] For example, Table 11 exemplarily shows another example of how to determine the slots corresponding to PUSCH for PUSCH repetition type A. Table 12 exemplarily shows an example of how to determine the slots corresponding to PUSCH for TBoMS.

[0296] Table 11

[0297] Table 12

[0298] The following further illustrates the frequency resource allocation of PUSCH, and the present application is not limited thereto.

[0299] In some embodiments, for PUSCH: the same starting RB and / or frequency hopping offset (FH offset) is applied for the first time-domain resource and the second time-domain resource.

[0300] In some embodiments, for PUSCH: different starting RB and / or frequency hopping offset (FH offset) is applied for the first time-domain resource and the second time-domain resource.

[0301] In some embodiments, for the second time-domain resource (for PUSCH overlapping with the first time-domain resource or (for repetition Type B: nominal and / or actual) repetition), a first starting RB (the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1) is applied for the second DCI indication, and for the first time-domain resource (for PUSCH overlapping with the second time-domain resource or repetition), a second starting RB is applied.

[0302] In some embodiments, the second starting RB and the first starting RB are the same.

[0303] In some embodiments, the second starting RB is determined from a first RB offset (predefined or indicated) and / or the first starting RB and / or the bandwidth of the (active) (UL) BWP and / or the bandwidth of the UL usable PRBs.

[0304] In some embodiments, the above-mentioned first starting RB is, for example, the first PRB in the frequency domain resource (PRBs) indicated by the aforementioned second DCI / the PRB with the lowest frequency domain position / the PRB with the smallest index.

[0305] In some embodiments, the second starting RB is determined, for example, according to a modulo value and / or a scaling factor related to the first RB offset and / or the first starting RB and / or the bandwidth of the (active) (UL) BWP and / or the bandwidth of the UL usable PRBs. In some embodiments, the second starting RB is determined according to the first RB offset (RB' offset ) without being determined according to the first starting RB, for example, the first RB offset is an offset relative to the starting RB (the first PRB / the PRB with the lowest frequency domain position / the PRB with the smallest index) of the UL usable PRBs, when RB' offset = 0, the second starting RB is the first PRB / the PRB with the lowest frequency domain position / the PRB with the smallest index in the UL usable PRBs, when RB' offset = 1, the second starting RB is the second PRB / the PRB with the second lowest frequency domain position / the PRB with the second smallest index in the UL usable PRBs, and so on. For example, or corresponds to the PRB index in the UL usable PRBs, the PRBs in the UL usable PRBs are numbered in ascending order from 0 to high by frequency, for example. indicates the size of UL usable PRBs, i.e., the number of PRBs it includes.

[0306] In some embodiments, the first RB offset is determined by the first starting RB and / or the size of the BWP and / or the size of UL usable PRBs, and in turn, the UE determines the second starting RB according to the first RB offset (e.g., using the above method). For example, wherein, is the first starting RB. is a scaling factor, for example.

[0307] In some embodiments, the second starting RB is determined according to the first RB offset and the first starting RB, for example,

[0308] In some embodiments, the first RB offset is indicated by the higher layer signaling and / or the FDRA field or other field in the second DCI.

[0309] In some embodiments, when the first RB offset is not indicated by the higher layer signaling / the FDRA field or other field in the second DCI, the second starting RB is the same as the first starting RB, or in other words, the first starting RB is applied for SBFD symbols.

[0310] In some embodiments, when the first RB offset is not indicated by the higher layer signaling and / or the FDRA field or other field in the second DCI, by default, the first RB offset = 0.

[0311] In some embodiments, (when the first RB offset is applied), the number of PRBs is the same for PUSCH transmissions in SBFD symbols and PUSCH transmissions in non-SBFD symbols.

[0312] In some embodiments, the first RB offset is applied for case 1 and / or case 2. For example, when the first RB offset is only applied for case 2, not for case 1, then for case 1-1 and resource allocation type Type 0, the frequency domain resources outside the first frequency domain resources indicated by the second DCI are invalid, and / or, the UE determines the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0313] The following is illustratively described how to support PUSCH frequency hopping.

[0314] In some embodiments, frequency hopping is only for / applied to the second resource allocation type, but not limited thereto.

[0315] In some embodiments, for PUSCH scheduled by DCI format 0_1, frequency hopping (e.g., intra-slot frequency hopping or inter-slot frequency hopping) is configured by frequencyHopping provided in pusch-Config for the case of the first repetition type and / or TBoMS, and frequency hopping (e.g., inter-repetition frequency hopping or inter-slot frequency hopping) is configured by frequencyHoppingDCI-0-1 provided in pusch-Config for the case of the second repetition type. And, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-Config (e.g., corresponding to the first FH offset list described below).

[0316] In some embodiments, for PUSCH scheduled by DCI format 0_2, frequency hopping (e.g., intra-slot frequency hopping or inter-slot frequency hopping) is configured by the higher layer parameter frequencyHoppingDCI-0-2 in pusch-Config for the case of the first repetition type, and frequency hopping (e.g., inter-repetition frequency hopping or inter-slot frequency hopping) is configured by the higher layer parameter frequencyHoppingDCI-0-2 in pusch-Config for the case of the second repetition type. And, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetListsDCI-0-2 in pusch-Config (e.g., corresponding to the first FH offset list described below).

[0317] In some embodiments, the first FH offset list can be referred to as being for non-SBFD symbols, but not limited thereto. In some embodiments, the first FH offset list can be for / applied to SBFD symbols and / or non-SBFD symbols.

[0318] In some embodiments, the UE can be configured by higher layer signaling a second FH offset list for SBFD symbols. For example, the UE can be provided a higher layer parameter for configuring the second FH offset list. Where different DCI formats, e.g., DCI format 0_1 and 0_2 or 0_3, can correspond to common or independent higher layer parameters for configuring the second FH offset list. For example, the higher layer parameter for configuring the second FH offset list is optionally present in pusch-Config / PUSCH-Config, but not limited thereto. The higher layer parameter is, for example, frequencyHoppingOffsetListsSBFD (e.g., for DCI format 0_1 and 0_3), frequencyHoppingOffsetListsDCI-0-2-SBFD, (e.g., for DCI format 0_2).

[0319] In some embodiments, the second FH offset list is configured only if the first FH offset list is configured, that is, when the first FH offset list is not configured, the second FH offset list is not configured.

[0320] In some embodiments, the number of FH offsets in the second FH offset list should not be greater than or must be equal to the number of FH offsets in the first FH offset list.

[0321] In some embodiments, the number of FH offsets in the first FH offset list and the second FH offset list are both limited to the bandwidth of the BWP. For example, when the bandwidth of the corresponding BWP is less than 50 PRBs, 2 are included, otherwise, 4 are included.

[0322] In some embodiments, the number of FH offsets in the first FH offset list is limited to the bandwidth of the BWP. The number of FH offsets in the second FH offset list is limited to the bandwidth of the UL usable PRBs. For example, when the bandwidth of the corresponding UL usable PRBs is less than 50 PRBs, 2 are included, otherwise, 4 are included.

[0323] In some embodiments, the UE can be enabled / disabled by higher layer signaling to hop for SBFD symbols. For example, the UE can be provided with a higher layer parameter to enable / disable hopping for SBFD symbols (in the case that (is configured with the first FH offset list but) is not configured with the second FH offset list or the second DCI does not indicate the second offset). Where different DCI formats, e.g., DCI format 0_1 and 0_2 or 0_3, can correspond to common or independent higher layer parameters to enable / disable hopping for SBFD symbols. For example, the higher layer parameter to enable / disable hopping for SBFD symbols is optionally present in pusch-Config / PUSCH-Config, but not limited thereto.

[0324] In some embodiments, (when is configured with hopping), the second DCI includes one frequency hopping flag field (to indicate whether the scheduled PUSCH is hopped or not, e.g., as shown in Table 13 below).

[0325] Table 13

[0326] In some embodiments, the second DCI includes 2 frequency hopping flag fields, e.g., for SBFD symbols and non-SBFD symbols respectively, to indicate whether hopping is performed for SBFD symbols and non-SBFD symbols respectively.

[0327] In some embodiments, (when is configured with hopping), the second DCI includes information to indicate the frequency offset, which information includes, for example, N UL,hop MSB bits in the FDRA field.

[0328] In some embodiments, N UL,hop is determined by the number of FH offsets in the first FH offset list. For example, when the first FH offset list includes 2 offsets, then N UL,hop = 1, when including 4 offsets, then N UL,hop = 2.

[0329] In some embodiments, when one value of the information to indicate the frequency offset corresponds to one first FH offset (i.e., offset in the first FH offset list) and / or one second FH offset (i.e., offset in the second FH offset list), e.g., as shown in Table 14 below (where the number of offsets are assumed to be 4 and 2 respectively).

[0330] Table 14

[0331] In some embodiments, for non-SBFD symbols, apply the first FH offset; for the SBFD symbols, apply the first FH offset or the second FH offset or do not apply FH offset (i.e., do not hop).

[0332] In some embodiments, for SBFD symbols, when no second FH offset list is configured or no second FH offset is indicated by the second DCI (e.g., the information in the second DCI for indicating frequency offset corresponding to a value that does not correspond to a second FH offset), apply the first FH offset (indicated by the information in the second DCI for indicating frequency offset) or do not apply FH offset; for example, if the information in the second DCI for indicating frequency offset corresponding to a value (e.g., 10 / 11 in the above table) that corresponds to a first FH offset but does not correspond to a second FH offset, for SBFD symbols, apply the first FH offset corresponding to the value or do not apply FH offset.

[0333] In some embodiments, for SBFD symbols, when no second FH offset list is configured or no second FH offset is indicated by the second DCI, and FH is not enabled (e.g., by higher layer signaling or the second DCI, as described above), apply the first FH offset (indicated by the information in the second DCI for indicating frequency offset).

[0334] In some embodiments, for SBFD symbols, when no second FH offset list is configured or no second FH offset is indicated by the second DCI, and FH is enabled (e.g., by higher layer signaling or the second DCI, as described above), apply the first FH offset (indicated by the information in the second DCI for indicating frequency offset).

[0335] In some embodiments, for SBFD symbols, when FH is enabled (the FH flag in the second DCI enables FH, and) a second FH offset is indicated (by the information in the second DCI for indicating frequency offset), apply the second FH offset.

[0336] In some embodiments, for SBFD symbols, when no second FH offset is indicated by (the information for indicating frequency offset in the second DCI) or no second FH offset list is configured, and FH is disabled by (higher layer signaling or the second DCI, as described above), no FH offset is applied.

[0337] In some embodiments, for SBFD symbols, when no second FH offset is indicated by (the information for indicating frequency offset in the second DCI) or no second FH offset list is configured, and FH is disabled by (for example, by (higher layer signaling or the second DCI, as described above)), no FH offset is applied; for example, if the second DCI includes 2 frequency hopping flag fields, for SBFD symbols, when the value of the frequency hopping flag field for SBFD symbols is 0 (disabled), no FH offset is applied.

[0338] In some embodiments, for SBFD symbols, when no second FH offset is indicated by (the information for indicating frequency offset in the second DCI) or no second FH offset list is configured, and FH is not enabled by (for example, by (higher layer signaling or the second DCI, as described above)), no FH offset is applied.

[0339] In some embodiments, for the second time-domain resource, the third starting RB corresponding to the FH offset (the first FH offset) is determined according to the first starting RB and the bandwidth / size of the BWP.

[0340] In some embodiments, for the first time-domain resource, (in the case of applying the FH offset) the fourth starting RB corresponding to the FH offset (the first FH offset or the second FH offset) is determined according to the second starting RB and the bandwidth / size of the first frequency-domain resource.

[0341] The following is schematically described in connection with various types of frequency hopping.

[0342] In some embodiments, for PUSCH repetition Type A and for TB processing over multiple slots, in case of intra-slot FH, if the symbol allocation in a slot (only) overlaps with non-SBFD symbols, the first hop in the slot corresponds to the first starting RB, and the second hop corresponds to the third starting RB. If the symbol allocation in a slot (only) overlaps with SBFD symbols, the first hop in the slot corresponds to the second starting RB, and the second hop corresponds to the fourth starting RB.

[0343] Table 15 exemplarily shows examples for intra-slot FH, without limitation. Wherein, if the symbol allocation in a slot (only) overlaps with non-SBFD symbols (or in other words, for PUSCH transmission (only) overlapping with non-SBFD symbols), the RB start is the first starting RB, and the RB offset is the first FH offset as mentioned above, is the bandwidth / size of the (UL) BWP, RB start (i=1) is the third starting RB as mentioned above. If the symbol allocation in a slot (only) overlaps with non-SBFD symbols (or in other words, for PUSCH transmission (only) overlapping with SBFD symbols), (when FH is applied), the RB start is the second starting RB, and the RB offset is the first FH offset or the second FH offset (determined according to the aforementioned method which one to apply), is the bandwidth / size of the UL usable PRBs, RB start (i=1) is the fourth starting RB as mentioned above.

[0344] Table 15

[0345] In some embodiments, for PUSCH repetition Type A and for TB processing over multiple slots, the slots or repetitions are counted independently, and the frequency domain resources corresponding to the slots / repetitions have been determined.

[0346] For example, in case of inter-slot FH, the slots containing SBFD symbols and the slots containing non-SBFD symbols are numbered separately for the slots in a frame. For example, if a slot contains both SBFD symbols and non-SBFD symbols, in numbering: the slot is counted in both the slots containing SBFD symbols and the slots containing non-SBFD symbols; or, the slot is treated as 2 slots, one containing only SBFD symbols and one containing only non-SBFD symbols, and is counted in the slots containing SBFD symbols and the slots containing non-SBFD symbols respectively.

[0347] For example, for the slots containing non-SBFD symbols, the first hop corresponds to the first starting RB and the second hop corresponds to the third starting RB. For the slots containing SBFD symbols, the first hop corresponds to the second starting RB and the second hop corresponds to the fourth starting RB.

[0348] Table 16 exemplarily shows an example for inter-slot FH, without limitation.

[0349] Table 16

[0350] For example, for for PUSCH repetition Type A and for TB processing over multiple slots, in case of inter-slot FH, the repetitions or PUSCH transmission (occasions) overlapping (only) with SBFD symbols and the repetitions or PUSCH transmission (occasions) overlapping (only) with non-SBFD symbols are numbered separately.

[0351] For example, for the repetitions or PUSCH transmission (occasions) overlapping with non-SBFD symbols, the first hop corresponds to the first starting RB and the second hop corresponds to the third starting RB. For the repetitions or PUSCH transmission (occasions) overlapping with SBFD symbols, the first hop corresponds to the second starting RB and the second hop corresponds to the fourth starting RB.

[0352] Table 17 exemplarily shows an example for inter-slot FH, without limitation.

[0353] Table 17

[0354] For example, in the inter-repetition FH case, the nominal repetitions overlapping with only SBFD symbols and the nominal repetitions overlapping with only non-SBFD symbols are numbered respectively.

[0355] For example, for the nominal repetitions overlapping with non-SBFD symbols, the first hop corresponds to the first starting RB, and the second hop corresponds to the third starting RB. For the nominal repetitions overlapping with SBFD symbols, the first hop corresponds to the second starting RB, and the second hop corresponds to the fourth starting RB.

[0356] Table 18 exemplarily shows one example of the inter-repetition FH, and the present application is not limited thereto.

[0357] Table 18

[0358] The above only describes the steps or processes related to the present application, but the present application is not limited thereto. The method of the embodiments of the present application can also include other steps or processes, and the specific content of these steps or processes can be referred to the related art.

[0359] The above embodiments only exemplarily describe the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0360] As can be seen from the above embodiments, the terminal device receives the first DCI for scheduling the PDSCH and / or the second DCI for scheduling the PUSCH, and determines the corresponding TBS according to the frequency domain resources corresponding to the PDSCH / PUSCH. Therefore, the network device can work in the full duplex mode (simultaneous reception and transmission), and the terminal device can also utilize the corresponding resources to transceive signals when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0361] Embodiments of the second aspect

[0362] The embodiments of the present application provide an information sending method, which is described from the network device side. The same content as the embodiments of the first aspect will not be described again.

[0363] FIG. 6 is a schematic diagram of an information sending method according to an embodiment of the present application. As shown in FIG. 6, the method includes:

[0364] 601, the network device sends information for configuring the first time domain resource and / or the second time domain resource; wherein, in the first time domain resource, the first frequency domain resource is for uplink and the second frequency domain resource is for downlink, and the second time domain resource is outside the first time domain resource; and

[0365] 602, the network device sends a first DCI for scheduling a PDSCH; wherein, the first DCI schedules multiple PDSCHs or the PDSCH has repetition, and a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0366] sends a second DCI for scheduling a PUSCH; wherein, the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, and a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0367] It is worth noting that the above Figure 6 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the present application is not limited to the description of the above Figure 6.

[0368] In some embodiments, for a PDSCH in the multiple PDSCHs:

[0369] for one PDSCH overlapping (including partially overlapping (i.e., the part is within the first time domain resource, and the other part is within the second time domain resource) and / or completely overlapping (at this time, it can also be said that within the first time domain resource)) the first time domain resource, the TBS is determined according to the frequency domain resource within the second frequency domain resource indicated by the first DCI, and for one PDSCH overlapping (including partially overlapping and / or completely overlapping (at this time, it can also be said that within the second time domain resource)) the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI; or,

[0370] for one PDSCH overlapping the first time domain resource and one SPS PDSCH overlapping the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI.

[0371] In some embodiments, for the PDSCH:

[0372] The TBS is determined according to the frequency domain resource indicated by the first DCI within the second frequency domain resource or the frequency domain resource indicated by the first DCI, in association with the valid time domain resource type and / or the invalid time domain resource type and / or the first reference repetition (e.g., the first repetition) and / or the corresponding (allocated) symbol in the first slot and / or the number of repetitions overlapping with the first time domain resource and / or the number of repetitions overlapping with the second time domain resource.

[0373] In some embodiments, the first reference repetition is the first repetition scheduled by the first DCI or the first repetition satisfying a first condition, and / or the first slot is the slot corresponding to the first PDSCH or the first repetition or the first reference repetition or the slot determined by the first slot offset indicated by the first DCI.

[0374] In some embodiments, the first condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as uplink by (first / second uplink-downlink configuration), and / or not overlapping with both SBFD symbols and non-SBFD symbols.

[0375] In some embodiments, for a PDSCH in the plurality of PDSCHs or a PDSCH with repetition:

[0376] When the first time domain resource is an invalid time domain resource type, the TBS is determined according to the frequency domain resource indicated by the first DCI; and / or,

[0377] When the first time domain resource is not an invalid time domain resource type, the TBS is determined according to the frequency domain resource indicated by the first DCI within the second frequency domain resource or the frequency domain resource indicated by the first DCI.

[0378] In some embodiments, the first time domain resource is not an invalid time domain resource type includes that: the second time domain resource type is an invalid resource type, and / or does not have an invalid time domain resource type.

[0379] In some embodiments, for a PDSCH in the plurality of PDSCHs:

[0380] When there is no invalid time domain resource type, for a PDSCH overlapping with the first time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI within the second frequency domain resource, and for a PDSCH overlapping with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI.

[0381] In some embodiments, for a PDSCH with repetition:

[0382] when the time domain resource type is invalid,

[0383] if the first reference repetition (e.g., the first time repetition) and / or the allocated symbol in the first slot and / or the certain number of repetitions (in the second time domain resource or) overlap with the second time domain resource, determine the TBS according to the frequency domain resource indicated by the first DCI in the second frequency domain resource; and / or,

[0384] if the first reference repetition and / or the allocated symbol in the first slot and / or the certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, determine the TBS according to the frequency domain resource indicated by the first DCI in the second frequency domain resource.

[0385] In some embodiments, for the PDSCH with repetition:

[0386] if the first reference repetition or the allocated symbol in the first slot and / or the certain number of repetitions (in the second time domain resource or) overlap with the second time domain resource, determine the TBS according to the frequency domain resource indicated by the first DCI, and / or,

[0387] if the first reference repetition or the allocated symbol in the first slot and / or the certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, determine the TBS according to the frequency domain resource indicated by the first DCI in the second frequency domain resource.

[0388] In some embodiments, for the PDSCH:

[0389] The invalid time domain resource type and / or the valid time domain resource type is determined based on the first information and / or the second information and / or the reference PDSCH (for multi-PDSCH, e.g., the first PDSCH scheduled by the first DCI) and / or the second reference repetition (for PDSCH repetition) and / or the allocated symbol in the second slot (both apply).

[0390] In some embodiments, the reference PDSCH is the first PDSCH scheduled by the first DCI or the first PDSCH meeting the first condition, and / or the second reference repetition is the first repetition scheduled by the first DCI or the first eligible repetition, and / or the second slot is the slot corresponding to the first PDSCH or the first repetition or the reference PDSCH or the second reference repetition or the slot determined by the first slot offset indicated by the first DCI,

[0391] In some embodiments, the first condition includes, but is not limited to, not overlapping with non-SBFD symbols indicated as uplink by (first / second uplink-downlink configuration), and / or not overlapping with both SBFD symbols and non-SBFD symbols.

[0392] In some embodiments, for the PDSCH:

[0393] When the first time domain resource is an invalid time domain resource type, the PDSCH (for multi-PDSCH) or repetition (for PDSCH repetition) overlapping with the first time domain resource is not transmitted (dropped),

[0394] When the second time domain resource is an invalid time domain resource type, the PDSCH or repetition overlapping with the second time domain resource is not transmitted (dropped).

[0395] In some embodiments, for the PDSCH:

[0396] The frequency domain resource outside the second frequency domain resource indicated by the first DCI is invalid for the PDSCH and / or repetition overlapping with the first time domain resource (when the first time domain resource is not an invalid time domain resource type).

[0397] In some embodiments, for the PUSCH, the repetition includes a first type repetition (Type A) and / or a second type repetition (Type B).

[0398] In some embodiments, for a PUSCH in the plurality of PUSCHs:

[0399] For one PUSCH overlapping (including partially overlapping (i.e., the part is within the first time domain resource, and the other part is within the second time domain resource) and / or completely overlapping (at this time, it can also be said that it is within the first time domain resource)) with the first time domain resource, the TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI, and for one PUSCH overlapping (including partially overlapping and / or completely overlapping (at this time, it can also be said that it is within the second time domain resource)) with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the second DCI; or,

[0400] For one PDSCH overlapping with the first time domain resource and one PUSCH overlapping with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the second DCI.

[0401] In some embodiments, for the PUSCH:

[0402] The TBS is determined according to the frequency domain resources indicated by the second DCI within the first frequency domain resources or the frequency domain resources indicated by the second DCI, in association with the valid time domain resource type and / or the invalid time domain resource type and / or the frequency domain resource allocation type and / or the third reference repetition (e.g., the first repetition) and / or the symbols allocated in the third slot and / or the number of repetitions overlapping with the first time domain resources and / or the number of repetitions overlapping with the second time domain resources.

[0403] In some embodiments, the third reference repetition is the first repetition scheduled by the second DCI or the first repetition satisfying the second condition, and / or, the third slot is the slot corresponding to the first PUSCH or the first repetition or the third reference repetition or the slot determined by the second slot offset indicated by the second DCI.

[0404] In some embodiments, the second condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (first / second uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols.

[0405] In some embodiments, for a PUSCH in the plurality of PUSCHs or a PUSCH with repetition or a PUSCH with multi-slot TB:

[0406] When the first time domain resource is the invalid time domain resource type, the TBS is determined according to the frequency domain resources indicated by the second DCI; and / or,

[0407] When the first time domain resource is not the invalid time domain resource type, the TBS is determined according to the frequency domain resources indicated by the second DCI within the first frequency domain resources or the frequency domain resources indicated by the second DCI.

[0408] In some embodiments, the first time domain resource is not the invalid time domain resource type includes: the second time domain resource type is the invalid resource type, and / or, does not have the invalid time domain resource type.

[0409] In some embodiments, for a PUSCH in the plurality of PUSCHs:

[0410] When the second time domain resource type is the invalid time domain resource type, for a first type resource allocation (Type 0), the TBS is determined according to the frequency domain resources indicated by the second DCI within the first frequency domain resources, and / or, for a second type resource allocation (Type 1), the TBS is determined according to the frequency domain resources indicated by the second DCI; and / or,

[0411] When not having invalid time domain resource type, TBS is determined according to the frequency domain resource indicated by the second DCI.

[0412] In some embodiments, for a PUSCH of the plurality of PUSCHs:

[0413] When not having invalid time domain resource type, for a PUSCH overlapping with the first time domain resource, TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI or the frequency domain resource indicated by the second DCI, and for a PUSCH overlapping with the second time domain resource, TBS is determined according to the frequency domain resource indicated by the second DCI.

[0414] In some embodiments, when not having invalid time domain resource type, for a PUSCH overlapping with the first time domain resource,

[0415] For a first type of resource allocation, TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI, and / or, for a second type of resource allocation, TBS is determined according to the frequency domain resource indicated by the second DCI.

[0416] In some embodiments, for a PUSCH with repetition:

[0417] When the second time domain resource type is an invalid resource type, for a first type of resource allocation (Type 0), TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI, and / or, for a second type of resource allocation (Type 1), TBS is determined according to the frequency domain resource indicated by the second DCI; and / or,

[0418] When not having invalid time domain resource type, if a third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or a certain number of repetitions (in the second time domain resource or) overlap with the second time domain resource, TBS is determined according to the frequency domain resource indicated by the second DCI; and / or, if a third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or a certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI.

[0419] In some embodiments, for a PUSCH with repetition:

[0420] if the third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or the certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0421] if the third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or the certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0422] In some embodiments, for the PUSCH with multi-slot TB:

[0423] if the second time domain resource type is an invalid resource type, for a first type of resource allocation (Type 0), determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI, and / or, for a second type of resource allocation (Type 1), determine the TBS according to the frequency domain resources indicated by the second DCI; and / or,

[0424] if there is no invalid time domain resource type, if the allocated symbols in the second slot are in the second time domain resource, determine the TBS according to the frequency domain resources indicated by the second DCI; and / or, if the allocated symbols in the second slot are in or overlap with the first time domain resource, determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0425] In some embodiments, for the PUSCH with multi-slot TB:

[0426] if the third slot is in the second time domain resource, determine the TBS according to the frequency domain resources indicated by the second DCI, and / or,

[0427] if the third slot is in or overlaps with the first time domain resource, determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0428] In some embodiments, for the PUSCH:

[0429] the invalid time domain resource type and / or the valid time domain resource type are determined based on the third information and / or the fourth information and / or a reference PUSCH (for multi-PUSCH, e.g., the first PUSCH scheduled by the second DCI) and / or the fourth reference repetition (for PUSCH repetition) and / or the allocated symbols in the fourth slot (all apply).

[0430] In some embodiments, the reference PUSCH is the first PUSCH scheduled by the second DCI or the first PUSCH satisfying the second condition, and / or, the fourth reference repetition is the first repetition scheduled by the second DCI or the first repetition satisfying the second condition, and / or, the fourth slot is the slot corresponding to the first PDSCH or the first repetition or the reference PUSCH or the fourth reference repetition or a slot determined by a second slot offset indicated by the second DCI,

[0431] In some embodiments, the second condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (first / second uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols.

[0432] In some embodiments, for the PUSCH with the second type of repetition:

[0433] The first repetition includes a first nominal repetition and / or a first actual repetition.

[0434] In some embodiments, for the PUSCH in the plurality of PUSCHs, or, the PUSCH with the first type of repetition without being configured with the available slot count, or, the PUSCH with the second type of repetition:

[0435] When the first time-domain resource is an invalid time-domain resource type, a PUSCH or a repetition overlapping with the first time-domain resource is not received (dropped). When the second time-domain resource is an invalid time-domain resource type, a PUSCH or a repetition overlapping with the second time-domain resource is not received (dropped).

[0436] In some embodiments, for the PUSCH with the second type of repetition, the repetition includes a nominal repetition and / or an actual repetition.

[0437] In some embodiments, for the PUSCH with the second type of repetition:

[0438] When the first time-domain resource and the second time-domain resource are both not invalid time-domain resources: if a nominal repetition overlaps with both the first time-domain resource and the second time-domain resource, the nominal repetition corresponds to an actual repetition overlapping with the first time-domain resource and an actual repetition overlapping with the second time-domain resource; or, the nominal repetition has no corresponding actual repetition, or, an actual repetition overlapping with both the first time-domain resource and the second time-domain resource is not received (dropped).

[0439] In some embodiments, for PUSCH with the second type of repetition:

[0440] The actual repetition is determined according to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB.

[0441] In some embodiments, for PUSCH with the first type of repetition with enabled available slot counting, or, PUSCH with multi-slot TB:

[0442] The slot corresponding to the PUSCH is related to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB.

[0443] For example, the slot corresponding to the PUSCH is determined according to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB.

[0444] In some embodiments, for the PUSCH: the same starting RB and / or frequency hopping offset (FH offset) is applied for the first time domain resource and the second time domain resource.

[0445] In some embodiments, for the PUSCH: different starting RB and / or frequency hopping offset (FH offset) is applied.

[0446] In some embodiments, for the second time domain resource, the first starting RB (the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1) indicated by the second DCI is applied, and for the first time domain resource, a second starting RB is applied, which is the same as the first starting RB or determined by a first RB offset (predefined or indicated) and / or the first starting RB and / or uplink BWP bandwidth and / or bandwidth of uplink available resources.

[0447] In some embodiments, a first FH offset (or referred to as a first frequency offset or a second RB offset) is applied for the second time domain resource; the first FH offset or a second FH offset (or referred to as a second frequency offset or a third RB offset) or no FH offset (i.e., no frequency hopping) is applied for the first time domain resource.

[0448] In some embodiments, for the second time domain resource, a third starting RB corresponding to the first FH offset is determined according to a first starting RB and a bandwidth / size of the BWP.

[0449] In some embodiments, for the first time domain resource, (in the case of applying the FH offset) a fourth starting RB corresponding to the first FH offset or the second FH offset is determined according to a second starting RB and a bandwidth / size of the first frequency domain resource.

[0450] The above only describes the steps or processes related to the present application, but the present application is not limited thereto. The method of the embodiments of the present application can also include other steps or processes, and the specific content of these steps or processes can be referred to the related art.

[0451] The above embodiments only exemplarily describe the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above embodiments. For example, the above embodiments can be used alone or one or more of the above embodiments can be combined.

[0452] As can be seen from the above embodiments, the network device transmits the first DCI for scheduling the PDSCH and / or the second DCI for scheduling the PUSCH, and determines the corresponding TBS according to the frequency domain resource corresponding to the PDSCH / PUSCH. Thus, the network device can work in the full duplex mode (simultaneous reception and transmission), and the terminal device can also receive and transmit signals using the corresponding resources when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0453] Embodiments of the third aspect

[0454] The embodiments of the present application provide an information receiving device. The device may, for example, be a terminal device, or one or more components or assemblies configured in the terminal device, and the same content as the embodiments of the first aspect will not be described again.

[0455] FIG. 7 is a schematic diagram of an information receiving apparatus according to an embodiment of the present application. Since the principle of solving the problem of the apparatus is the same as that of the method of the embodiment of the first aspect, the specific implementation can refer to the embodiment of the first aspect, and the same content will not be repeated. As shown in FIG. 7, the information receiving apparatus 700 includes a receiver 701, and can further include a processor 702 and a transmitter 703.

[0456] The receiver 701 receives information for configuring the first time domain resource and / or the second time domain resource; wherein in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0457] The receiver 701 receives the first DCI for scheduling the PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, and the transport block size (TBS) corresponding to the PDSCH is determined by the frequency domain resource within the second frequency domain resource indicated by the first DCI or the frequency domain resource indicated by the first DCI; and / or,

[0458] The receiver 701 receives the second DCI for scheduling the PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, and the TBS corresponding to the PUSCH is determined by the frequency domain resource within the first frequency domain resource indicated by the second DCI or the frequency domain resource indicated by the second DCI.

[0459] In some embodiments, for a PDSCH in the multiple PDSCHs:

[0460] For one PDSCH overlapping (including partially overlapping (i.e., the part is within the first time domain resource, and the other part is within the second time domain resource) and / or completely overlapping (at this time, it can also be said that it is within the first time domain resource)) with the first time domain resource, the TBS is determined according to the frequency domain resource within the second frequency domain resource indicated by the first DCI, and for one PDSCH overlapping (including partially overlapping and / or completely overlapping (at this time, it can also be said that it is within the second time domain resource)) with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI; or,

[0461] For one PDSCH overlapping with the first time domain resource and one SPS PDSCH overlapping with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI.

[0462] In some embodiments, for the PDSCH:

[0463] The TBS is determined according to the frequency domain resource indicated by the first DCI within the second frequency domain resource or the frequency domain resource indicated by the first DCI, in association with the valid time domain resource type and / or the invalid time domain resource type and / or the first reference repetition (e.g., the first repetition) and / or the allocated symbols in the first slot and / or the number of repetitions overlapping with the first time domain resource and / or the number of repetitions overlapping with the second time domain resource.

[0464] In some embodiments, the first reference repetition is the first repetition scheduled by the first DCI or the first repetition satisfying a first condition, and / or the first slot is the slot corresponding to the first PDSCH or the first repetition or the first reference repetition or the slot determined by the first slot offset indicated by the first DCI.

[0465] In some embodiments, the first condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as uplink by (first / second uplink-downlink configuration), and / or not overlapping with both SBFD symbols and non-SBFD symbols.

[0466] In some embodiments, for a PDSCH in the plurality of PDSCHs or a PDSCH with repetition:

[0467] When the first time domain resource is an invalid time domain resource type, the TBS is determined according to the frequency domain resource indicated by the first DCI; and / or,

[0468] When the first time domain resource is not an invalid time domain resource type, the TBS is determined according to the frequency domain resource indicated by the first DCI within the second frequency domain resource or the frequency domain resource indicated by the first DCI.

[0469] In some embodiments, the first time domain resource is not an invalid time domain resource type includes that: the second time domain resource type is an invalid resource type, and / or there is no invalid time domain resource type.

[0470] In some embodiments, for a PDSCH in the plurality of PDSCHs:

[0471] When there is no invalid time domain resource type, for a PDSCH overlapping with the first time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI within the second frequency domain resource, and for a PDSCH overlapping with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI.

[0472] In some embodiments, for a PDSCH with repetition:

[0473] When there is no invalid time domain resource type,

[0474] If the first reference repetition (e.g., the first time repetition) and / or the allocated symbol in the first time slot and / or a number of repetitions (in the second time domain resource or) overlap with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI; and / or,

[0475] If the first reference repetition and / or the allocated symbol in the first time slot and / or a number of repetitions (in the first time domain resource or) overlap with the first time domain resource, the TBS is determined according to the frequency domain resource within the second frequency domain resource indicated by the first DCI.

[0476] In some embodiments, for PDSCH with repetition:

[0477] If the first reference repetition or the allocated symbol in the first time slot and / or a number of repetitions (in the second time domain resource or) overlap with the second time domain resource, the TBS is determined according to the frequency domain resource indicated by the first DCI, and / or,

[0478] If the first reference repetition or the allocated symbol in the first time slot and / or a number of repetitions (in the first time domain resource or) overlap with the first time domain resource, the TBS is determined according to the frequency domain resource within the second frequency domain resource indicated by the first DCI.

[0479] In some embodiments, for the PDSCH:

[0480] The invalid time domain resource type and / or the valid time domain resource type is determined based on the first information and / or the second information and / or a reference PDSCH (for multi-PDSCH, e.g., the first PDSCH scheduled by the first DCI) and / or a second reference repetition (for PDSCH repetition) and / or an allocated symbol in a second time slot (both apply).

[0481] In some embodiments, the reference PDSCH is the first PDSCH scheduled by the first DCI or the first PDSCH meeting the first condition, and / or the second reference repetition is the first repetition scheduled by the first DCI or the first qualified repetition, and / or the second time slot is the time slot corresponding to the first PDSCH or the first repetition or the reference PDSCH or the second reference repetition or the time slot determined by the first time slot offset indicated by the first DCI,

[0482] In some embodiments, the first condition includes, but is not limited to, not overlapping with non-SBFD symbols indicated as uplink by (first / second uplink-downlink configuration), and / or not overlapping with both SBFD symbols and non-SBFD symbols.

[0483] In some embodiments, for the PDSCH:

[0484] When the first time-domain resource is an invalid time-domain resource type, the receiver 701 does not receive (drops) the PDSCH (for multi-PDSCH) or repetition (for PDSCH repetition) overlapping with the first time-domain resource,

[0485] When the second time-domain resource is an invalid time-domain resource type, the receiver 701 does not receive (drops) the PDSCH or repetition overlapping with the second time-domain resource.

[0486] In some embodiments, for the PDSCH:

[0487] For the PDSCH and / or repetition overlapping with the first time-domain resource, the frequency-domain resource other than the second frequency-domain resource indicated by the first DCI is invalid.

[0488] In some embodiments, for the PUSCH, the repetition includes a first type repetition (Type A) and / or a second type repetition (Type B).

[0489] In some embodiments, for a PUSCH of the plurality of PUSCHs:

[0490] For one PUSCH overlapping (including partially overlapping (i.e., the part is within the first time-domain resource, and the other part is within the second time-domain resource) and / or completely overlapping (at this time, it can also be said that within the first time-domain resource)) with the first time-domain resource, the TBS is determined according to the frequency-domain resource within the first frequency-domain resource indicated by the second DCI, and for one PUSCH overlapping (including partially overlapping and / or completely overlapping (at this time, it can also be said that within the second time-domain resource)) with the second time-domain resource, the TBS is determined according to the frequency-domain resource indicated by the second DCI; or,

[0491] For one PDSCH overlapping with the first time-domain resource and one PUSCH overlapping with the second time-domain resource, the TBS is determined according to the frequency-domain resource indicated by the second DCI.

[0492] In some embodiments, for the PUSCH:

[0493] The TBS is determined according to the frequency domain resources indicated by the second DCI within the first frequency domain resources or the frequency domain resources indicated by the second DCI, in association with the valid time domain resource type and / or the invalid time domain resource type and / or the frequency domain resource allocation type and / or the third reference repetition (e.g., the first repetition) and / or the symbols allocated in the third slot and / or the number of repetitions overlapping with the first time domain resources and / or the number of repetitions overlapping with the second time domain resources.

[0494] In some embodiments, the third reference repetition is the first repetition scheduled by the second DCI or the first repetition satisfying a second condition, and / or the third slot is the slot corresponding to the first PUSCH or the first repetition or the third reference repetition or the slot determined by the second slot offset indicated by the second DCI.

[0495] In some embodiments, the second condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (first / second uplink-downlink configuration), and / or not overlapping with SSB, and / or not overlapping with both SBFD symbols and non-SBFD symbols.

[0496] In some embodiments, for a PUSCH in the plurality of PUSCHs or a PUSCH with repetition or a PUSCH with multi-slot TB:

[0497] When the first time domain resource is the invalid time domain resource type, the TBS is determined according to the frequency domain resources indicated by the second DCI; and / or,

[0498] When the first time domain resource is not the invalid time domain resource type, the TBS is determined according to the frequency domain resources indicated by the second DCI within the first frequency domain resources or the frequency domain resources indicated by the second DCI.

[0499] In some embodiments, the first time domain resource is not the invalid time domain resource type, including: the second time domain resource type is the invalid resource type, and / or does not have the invalid time domain resource type.

[0500] In some embodiments, for a PUSCH in the plurality of PUSCHs:

[0501] When the second time domain resource type is the invalid time domain resource type, for a first type resource allocation (Type 0), the TBS is determined according to the frequency domain resources indicated by the second DCI within the first frequency domain resources, and / or for a second type resource allocation (Type 1), the TBS is determined according to the frequency domain resources indicated by the second DCI; and / or,

[0502] When not having invalid time domain resource type, TBS is determined according to the frequency domain resource indicated by the second DCI.

[0503] In some embodiments, for a PUSCH of the plurality of PUSCHs:

[0504] When not having invalid time domain resource type, for a PUSCH overlapping with the first time domain resource, TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI or the frequency domain resource indicated by the first DCI, and for a PUSCH overlapping with the second time domain resource, TBS is determined according to the frequency domain resource indicated by the first DCI.

[0505] In some embodiments, when not having invalid time domain resource type, for a PUSCH overlapping with the first time domain resource,

[0506] For a first type of resource allocation, TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI, and / or, for a second type of resource allocation, TBS is determined according to the frequency domain resource indicated by the second DCI.

[0507] In some embodiments, for a PUSCH with repetition:

[0508] When the second time domain resource type is an invalid resource type, for a first type of resource allocation (Type 0), TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI, and / or, for a second type of resource allocation (Type 1), TBS is determined according to the frequency domain resource indicated by the second DCI; and / or,

[0509] When not having invalid time domain resource type, if a third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or a certain number of repetitions (in the second time domain resource or) overlap with the second time domain resource, TBS is determined according to the frequency domain resource indicated by the second DCI; and / or, if a third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or a certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, TBS is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI.

[0510] In some embodiments, for a PUSCH with repetition:

[0511] if the third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or the certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0512] if the third reference repetition (e.g., the first repetition) and / or the allocated symbols in the third slot and / or the certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0513] In some embodiments, for the PUSCH with multi-slot TB:

[0514] if the second time domain resource type is an invalid time domain resource type, determine the TBS according to the frequency domain resources indicated by the second DCI for a first type of resource allocation (Type 0) within the first frequency domain resources, and / or determine the TBS according to the frequency domain resources indicated by the second DCI for a second type of resource allocation (Type 1); and / or,

[0515] if there is no invalid time domain resource type, determine the TBS according to the frequency domain resources indicated by the second DCI if the allocated symbols in the second slot are in the second time domain resource, and / or determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI if the allocated symbols in the second slot are in or overlap with the first time domain resource.

[0516] In some embodiments, for the PUSCH with multi-slot TB:

[0517] if the third slot is in the second time domain resource, determine the TBS according to the frequency domain resources indicated by the second DCI, and / or,

[0518] if the third slot is in or overlaps with the first time domain resource, determine the TBS according to the frequency domain resources within the first frequency domain resources indicated by the second DCI.

[0519] In some embodiments, for the PUSCH:

[0520] the invalid time domain resource type and / or the valid time domain resource type are determined based on the third information and / or the fourth information and / or a reference PUSCH (for multi-PUSCH, e.g., the first PUSCH scheduled by the second DCI) and / or a fourth repetition (for PUSCH repetition) and / or allocated symbols in a fourth slot (all apply).

[0521] In some embodiments, the reference PUSCH is the first PUSCH scheduled by the second DCI or the first PUSCH satisfying the second condition, and / or, the fourth reference repetition is the first repetition scheduled by the second DCI or the first repetition satisfying the second condition, and / or, the fourth slot is the slot corresponding to the first PDSCH or the first repetition or the reference PUSCH or the fourth reference repetition or a slot determined by a second slot offset indicated by the second DCI,

[0522] In some embodiments, the second condition includes but is not limited to: not overlapping with non-SBFD symbols indicated as downlink by (first / second uplink-downlink configuration), and / or, not overlapping with SSB, and / or, not overlapping with both SBFD symbols and non-SBFD symbols.

[0523] In some embodiments, for the PUSCH with the second type of repetition: the first repetition includes a first nominal repetition and / or a first actual repetition.

[0524] In some embodiments, for a PUSCH in the plurality of PUSCHs, or, a PUSCH with the first type of repetition without being configured with a usable slot count, or, a PUSCH with the second type of repetition:

[0525] When the first time-domain resource is an invalid time-domain resource type, a PUSCH or a repetition overlapping with the first time-domain resource is not transmitted (dropped), and when the second time-domain resource is an invalid time-domain resource type, a PUSCH or a repetition overlapping with the second time-domain resource is not transmitted (dropped).

[0526] In some embodiments, for the PUSCH with the second type of repetition, the repetition includes a nominal repetition and / or an actual repetition.

[0527] In some embodiments, for the PUSCH with the second type of repetition:

[0528] When the first time-domain resource and the second time-domain resource are both not invalid time-domain resources: if a nominal repetition overlaps with both the first time-domain resource and the second time-domain resource, the nominal repetition corresponds to an actual repetition overlapping with the first time-domain resource and an actual repetition overlapping with the second time-domain resource; or, the nominal repetition has no corresponding actual repetition, or, an actual repetition overlapping with both the first time-domain resource and the second time-domain resource is not transmitted (dropped).

[0529] In some embodiments, for the PUSCH with the second type of repetition:

[0530] The actual repetition is determined according to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB.

[0531] In some embodiments, for the PUSCH with the first type of repetition in the case of enabled available slot count, or, the PUSCH with multi-slot TB:

[0532] The slot corresponding to the PUSCH is related to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB.

[0533] For example, the slot corresponding to the PUSCH is determined according to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB.

[0534] In some embodiments, for the PUSCH:

[0535] The same starting RB and / or frequency hopping offset (FH offset) is applied for the first time domain resource and the second time domain resource, or different starting RB and / or frequency hopping offset (FH offset) is applied.

[0536] In some embodiments, for the second time domain resource, the first starting RB indicated by the second DCI is applied, and for the first time domain resource, the second starting RB is applied, the second starting RB is the same as the first starting RB or is determined by the first RB offset and / or the first starting RB and / or uplink BWP bandwidth and / or bandwidth of uplink available resources.

[0537] In some embodiments, for the second time domain resource, the first frequency hopping offset (or referred to as the second RB offset) is applied, and for the first time domain resource, the first frequency hopping offset is applied or the second frequency hopping offset (or referred to as the third RB offset) is applied or no frequency hopping offset is applied.

[0538] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The information receiving device 700 of the embodiments of the present application can also include other components or modules, and the specific content of these components or modules can be referred to related technologies.

[0539] In addition, for the sake of simplicity, only the connection relationship or signal direction between each component or module is exemplarily shown in FIG. 7, but it should be clear to those skilled in the art that various related technologies such as bus connection can be adopted. Each component or module described above can be implemented by hardware facilities such as processor, memory, transmitter, receiver, etc.; the implementation of the present application is not limited thereto.

[0540] The above embodiments are only exemplarily described for the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, each of the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0541] As can be seen from the above embodiments, the terminal device receives the first DCI for scheduling the PDSCH and / or the second DCI for scheduling the PUSCH, and determines the corresponding TBS according to the frequency domain resources corresponding to the PDSCH / PUSCH. Thus, the network device can work in full duplex mode (simultaneous reception and transmission), and the terminal device can also utilize the corresponding resources to transceive signals when the network device works in full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0542] Embodiments of the fourth aspect

[0543] The embodiments of the present application provide an information sending device. The device can be a network device, or one or more components or components configured in the network device, and the same content as the embodiments of the third aspect will not be repeated.

[0544] FIG. 8 is a schematic diagram of an information sending device according to an embodiment of the present application. Since the principle of solving the problem of the device is the same as that of the method of the first and second aspects, the specific implementation can refer to the first and second aspects, and the same content will not be repeated. As shown in FIG. 8, the information sending device 800 includes a transmitter 801, and can further include a processor 802 and a receiver 803.

[0545] The transmitter 801 transmits information for configuring the first time domain resource and / or the second time domain resource; wherein in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0546] The transmitter 801 transmits a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, and a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0547] The transmitter 801 transmits a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, and a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0548] It is worth noting that only the components or modules related to the present application are described above, but the present application is not limited thereto. The information sending device 800 of the embodiments of the present application can also include other components or modules, and the specific content of these components or modules can be referred to the related technology.

[0549] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 8, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0550] The above embodiments only exemplarily illustrate the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0551] As can be seen from the above embodiments, the network device transmits a first DCI for scheduling a PDSCH and / or a second DCI for scheduling a PUSCH, and determines the corresponding TBS according to the frequency domain resource corresponding to the PDSCH / PUSCH. In this way, the network device can work in full duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to receive and transmit signals when the network device works in full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0552] Embodiments of the fifth aspect

[0553] The embodiments of the present application also provide a communication system, which can be referred to FIG. 1, and the same content as the embodiments of the first to fourth aspects will not be described herein.

[0554] In some embodiments, the communication system 100 can at least include:

[0555] a network device, configured to send information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is out of the first time domain resource; and send a first DCI for scheduling PDSCH and / or a second DCI for scheduling PUSCH;

[0556] a terminal device, configured to receive information for configuring a first time domain resource and / or a second time domain resource; and

[0557] receive a first DCI for scheduling PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0558] receive a second DCI for scheduling PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0559] Embodiments of the present application also provide a network device, for example, can be a base station, but the present application is not limited thereto, and can also be other network devices.

[0560] FIG. 9 is a schematic diagram of a network device according to an embodiment of the present application. As shown in FIG. 9, the network device 900 can include a processor 910 (for example, a central processing unit CPU) and a memory 920; the memory 920 is coupled to the processor 910. The memory 920 can store various data; in addition, it also stores a program 930 for information processing, and executes the program 930 under the control of the processor 910.

[0561] For example, the processor 910 can be configured to execute the program to implement the method according to the embodiments of the second aspect.

[0562] In addition, as shown in FIG. 9, the network device 900 can also include a transceiver 940, an antenna 950, etc.; wherein the functions of the above-mentioned components are similar to those of the prior art, and will not be described here. It is worth noting that the network device 900 does not necessarily include all the components shown in FIG. 9; in addition, the network device 900 can also include components not shown in FIG. 9, which can be referred to the prior art.

[0563] The embodiments of the present application further provide a terminal device, but the present application is not limited thereto, and other devices can also be provided.

[0564] FIG. 10 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 10, the terminal device 1000 can include a processor 1010 and a memory 1020. The memory 1020 stores data and programs and is coupled to the processor 1010. It is worth noting that the diagram is exemplary; other types of structures can also be used to supplement or replace the structure to implement telecommunications functions or other functions.

[0565] For example, the processor 1010 can be configured to execute programs to implement the method according to the embodiments of the first aspect.

[0566] As shown in FIG. 10, the terminal device 1000 can further include a communication module 1030, an input device 1040, a display 1050, and a power supply 1060. The functions of the above components are similar to those of the prior art, and will not be described here. It is worth noting that the terminal device 1000 does not necessarily include all the components shown in FIG. 10, and the above components are not essential. In addition, the terminal device 1000 can also include components not shown in FIG. 10, and can refer to the prior art.

[0567] The embodiments of the present application further provide a computer readable program, wherein when the program is executed in a network device, the program causes the computer to execute the method according to the embodiments of the second aspect in the network device.

[0568] The embodiments of the present application further provide a storage medium storing a computer readable program, wherein the computer readable program causes the computer to execute the method according to the embodiments of the second aspect in the network device.

[0569] The embodiments of the present application further provide a computer readable program, wherein when the program is executed in a terminal device, the program causes the computer to execute the method according to the embodiments of the first aspect in the terminal device.

[0570] The embodiments of the present application further provide a storage medium storing a computer readable program, wherein the computer readable program causes the computer to execute the method according to the embodiments of the first aspect in the terminal device.

[0571] The apparatuses and methods described above can be implemented by hardware, or by software and / or firmware. The application relates to computer readable program, which, when executed by a logic component, enables the logic component to implement the above-described apparatuses or components, or to implement the above-described various methods or steps. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, or the like. The application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, or the like.

[0572] The methods / apparatuses described in connection with the embodiments of the application can be directly embodied in hardware, software modules executed by a processor, or a combination thereof. For example, one or more of the functional blocks shown in the figures and / or a combination of one or more of the functional blocks can correspond to individual software modules of a computer program flow, or to individual hardware modules. The software modules can correspond to individual steps shown in the figures, respectively. The hardware modules can be implemented by, for example, fixing the software modules using a field programmable gate array (FPGA).

[0573] The software modules can 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 disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and the storage medium can be located in an ASIC. The software modules can be stored in a memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a MEGA-SIM card or a large-capacity flash memory device, the software modules can be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0574] One or more of the functional blocks shown in the figures and / or a combination of one or more of the functional blocks can be implemented as 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, discrete gate or transistor logic, discrete hardware components, or any appropriate combination thereof, for performing the functions described in the application. One or more of the functional blocks shown in the figures and / or a combination of one or more of the functional blocks can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0575] The present application is described above in connection with specific embodiments, but those skilled in the art will understand that the description is merely exemplary and is not intended to limit the scope of the application. Those skilled in the art can make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are within the scope of the present application.

[0576] In connection with the embodiments including the above embodiments, the following supplementary notes are also disclosed:

[0577] 1. An information receiving method, comprising:

[0578] receiving information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is outside the first time domain resource;

[0579] receiving a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0580] receiving a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0581] 2. An information transmitting method, comprising:

[0582] transmitting information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is outside the first time domain resource;

[0583] transmitting a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, a transport block size (TBS) corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or,

[0584] transmit a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, a TBS of the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

[0585] 3. A terminal device comprising a memory and a processor, the memory storing a computer program, the processor configured to execute the computer program to implement the information receiving method of clause 1.

[0586] 4. A network device comprising a memory and a processor, the memory storing a computer program, the processor configured to execute the computer program to implement the information transmitting method of clause 2.

[0587] 5. A computer program product comprising at least a computer program, the computer program being executed by a processor to cause a terminal device to execute the information receiving method of clause 1.

[0588] 6. A computer program product comprising at least a computer program, the computer program being executed by a processor to cause a network device to execute the information transmitting method of clause 2.

Claims

1. An information receiving apparatus, comprising: a receiver configured to receive information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, and the second time domain resource is outside the first time domain resource; the receiver configured to receive a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, and a transport block size corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or, the receiver configured to receive a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, and a TBS corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

2. The apparatus of claim 1, wherein, for a PDSCH of the multiple PDSCHs: for a PDSCH overlapping with the first time domain resource, a transport block size is determined according to a frequency domain resource within the second frequency domain resource indicated by the first DCI, and for a PDSCH overlapping with the second time domain resource, a transport block size is determined according to a frequency domain resource indicated by the first DCI; or, for a PDSCH overlapping with the first time domain resource and a SPS PDSCH overlapping with the second time domain resource, a transport block size is determined according to a frequency domain resource indicated by the first DCI.

3. The apparatus of claim 1, wherein, for the PDSCH: whether a transport block size is determined according to a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI, is related to a valid time domain resource type and / or an invalid time domain resource type and / or a first reference repetition and / or a symbol corresponding to a first slot and / or a number of repetitions overlapping with the first time domain resource and / or a number of repetitions overlapping with the second time domain resource; wherein the first reference repetition is a first repetition scheduled by the first DCI or a first repetition satisfying a first condition, and / or the first slot is a slot corresponding to the first PDSCH or the first repetition or the first reference repetition or a slot determined by a first slot offset indicated by the first DCI; wherein the first condition comprises: not overlapping with the second time domain resource indicated as uplink, and / or not overlapping with both the first time domain resource and the second time domain resource.

4. The apparatus of claim 3, wherein, for a PDSCH of the multiple PDSCHs or a PDSCH having repetition: when the first time domain resource is an invalid time domain resource type, a transport block size is determined according to a frequency domain resource indicated by the first DCI; and / or, when the first time domain resource is not an invalid time domain resource type, a transport block size is determined according to a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI. The first time domain resource is not an invalid time domain resource type, including: the second time domain resource type is an invalid resource type, and / or does not have an invalid time domain resource type.

5. The apparatus of claim 4, wherein, For the PDSCH in the plurality of PDSCHs: When there is no invalid time domain resource type, for the PDSCH overlapping with the first time domain resource, the frequency domain resource within the second frequency domain resource indicated by the first DCI is used to determine the transport block size, and for the PDSCH overlapping with the second time domain resource, the frequency domain resource indicated by the first DCI is used to determine the transport block size.

6. The apparatus of claim 3, wherein, For the PDSCH with repetition: If the first reference repetition or the allocated symbol in the first slot and / or a certain number of repetitions overlap with the second time domain resource, the frequency domain resource indicated by the first DCI is used to determine the transport block size, and / or, If the first reference repetition or the allocated symbol in the first slot and / or a certain number of repetitions overlap with the first time domain resource, the frequency domain resource within the second frequency domain resource indicated by the first DCI is used to determine the transport block size.

7. The apparatus of claim 1, wherein, For the PDSCH: The invalid time domain resource type and / or the valid time domain resource type is determined based on the first information and / or the second information and / or the reference PDSCH and / or the second reference repetition and / or the allocated symbol in the second slot; Wherein, the reference PDSCH is the first PDSCH scheduled by the first DCI or the first PDSCH meeting the first condition, and / or the second reference repetition is the first repetition scheduled by the first DCI or the first repetition meeting the first condition, and / or the second slot is the slot corresponding to the first PDSCH or the first repetition or the reference PDSCH or the second reference repetition or the slot determined by the first time slot offset indicated by the first DCI, Wherein, the first condition includes: not overlapping with the second time domain resource indicated as uplink, and / or not overlapping with both the first time domain resource and the second time domain resource.

8. The apparatus of claim 1, wherein, For the PDSCH: When the first time domain resource is an invalid time domain resource type, the PDSCH or repetition overlapping with the first time domain resource is not received, when the second time domain resource is an invalid time domain resource type, the PDSCH or repetition overlapping with the second time domain resource is not received, and / or For the PDSCH and / or repetition overlapping with the first time domain resource, the frequency domain resource outside the second frequency domain resource indicated by the first DCI is invalid.

9. The apparatus of claim 1, wherein, For the PUSCH: The transport block size is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI or the frequency domain resource indicated by the second DCI, which is related to the valid time domain resource type and / or the invalid time domain resource type and / or the frequency domain resource allocation type and / or the third reference repetition and / or the allocated symbol in the third slot and / or the number of repetitions overlapping with the first time domain resource and / or the number of repetitions overlapping with the second time domain resource. The third reference repetition is a first repetition of the second DCI or a first repetition meeting a second condition, and / or the third slot is a first PUSCH or a slot corresponding to the first repetition or the third reference repetition or a slot determined by a second slot offset indicated by the second DCI. The second condition includes: not overlapping with the second time domain resource indicated as downlink, and / or not overlapping with SSB, and / or not overlapping with both the first time domain resource and the second time domain resource.

10. The apparatus of claim 9, wherein, For a PUSCH or a PUSCH with repetition or a PUSCH with multi-slot TB in the plurality of PUSCHs: When the first time domain resource is an invalid time domain resource type, the transport block size is determined according to the frequency domain resource indicated by the second DCI; and / or, When the first time domain resource is not an invalid time domain resource type, the transport block size is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI or the frequency domain resource indicated by the second DCI. The first time domain resource is not an invalid time domain resource type, including: the second time domain resource type is an invalid resource type, and / or does not have an invalid time domain resource type.

11. The apparatus of claim 10, wherein, For a PUSCH or a PUSCH with repetition and / or multi-slot TB in the plurality of PUSCHs: When the second time domain resource type is an invalid time domain resource type, for a first type resource allocation, the transport block size is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI, and / or, For a second type resource allocation, the transport block size is determined according to the frequency domain resource indicated by the second DCI; and / or, when there is no invalid time domain resource type, the transport block size is determined according to the frequency domain resource indicated by the second DCI.

12. The apparatus of claim 9, wherein, For a PUSCH with repetition and / or multi-slot TB: If the third reference repetition and / or the allocated symbols in the third slot and / or a certain number of repetitions overlap with the second time domain resource, the transport block size is determined according to the frequency domain resource indicated by the second DCI, and / or, If the third reference repetition and / or the allocated symbols in the third slot and / or a certain number of repetitions overlap with the first time domain resource, the transport block size is determined according to the frequency domain resource within the first frequency domain resource indicated by the second DCI.

13. The apparatus of claim 1, wherein, For the PUSCH: The invalid time domain resource type and / or the valid time domain resource type is determined based on third information and / or fourth information and / or allocated symbols in a reference PUSCH and / or a fourth reference repetition and / or a fourth slot; wherein, The reference PUSCH is the first PUSCH scheduled by the second DCI or the first PUSCH meeting a second condition, and / or the fourth reference repetition is the first repetition scheduled by the second DCI or the first repetition meeting the second condition, and / or the fourth slot is a slot corresponding to the first PUSCH or the first repetition or the reference PUSCH or the fourth reference repetition or a slot determined by a second slot offset indicated by the second DCI, The second condition includes: not overlapping with the second time domain resource indicated as downlink, and / or not overlapping with SSB, and / or not overlapping with both the first time domain resource and the second time domain resource.

14. The apparatus of claim 1, wherein, For PUSCH in the plurality of PUSCHs, or PUSCH with first type repetition without being configured with available slot count, or PUSCH with second type repetition: When the first time domain resource is an invalid time domain resource type, the PUSCH or repetition overlapping with the first time domain resource is not transmitted, and when the second time domain resource is an invalid time domain resource type, the PUSCH or repetition overlapping with the second time domain resource is not transmitted.

15. The apparatus of claim 1, wherein, For PUSCH with first type repetition with enabled available slot count, or PUSCH with multi-slot TB: The slot corresponding to the PUSCH is related to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or uplink / downlink configuration and / or SSB.

16. The apparatus of claim 1, wherein, For PUSCH with second type repetition, the actual repetition is determined according to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or uplink / downlink configuration and / or SSB.

17. The apparatus of claim 1, wherein, For the PUSCH: The same starting RB and / or frequency hopping offset is applied for the first time domain resource and the second time domain resource, or different starting RB and / or frequency hopping offset is applied.

18. The apparatus of claim 1, wherein, For the PUSCH: For the second time domain resource, the first starting RB indicated by the second DCI is applied, and for the first time domain resource, the second starting RB is applied, the second starting RB is the same as the first starting RB or is determined by the first RB offset and / or the first starting RB and / or uplink BWP bandwidth and / or bandwidth of uplink available resources; and / or For the second time domain resource, the first frequency hopping offset is applied, and for the first time domain resource, the first frequency hopping offset or the second frequency hopping offset is applied or no frequency hopping offset is applied.

19. An information sending device, comprising: a transmitter that transmits information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, and the second time domain resource is outside the first time domain resource; The transmitter transmits a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, and a transport block size corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or, The transmitter transmits a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, and a transport block size corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

20. A communication system comprising: a network device that transmits information for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, and the second time domain resource is outside the first time domain resource; and transmits a first DCI for scheduling a PDSCH and / or a second DCI for scheduling a PUSCH; a terminal device that receives information for configuring a first time domain resource and / or a second time domain resource; and receives a first DCI for scheduling a PDSCH; wherein the first DCI schedules multiple PDSCHs or the PDSCH has repetition, and a transport block size corresponding to the PDSCH is determined by a frequency domain resource within the second frequency domain resource indicated by the first DCI or a frequency domain resource indicated by the first DCI; and / or, receives a second DCI for scheduling a PUSCH; wherein the second DCI schedules multiple PUSCHs or the PUSCH has repetition and / or multi-slot TB, and a transport block size corresponding to the PUSCH is determined by a frequency domain resource within the first frequency domain resource indicated by the second DCI or a frequency domain resource indicated by the second DCI.

Images