Pdsch reception method and apparatus, pdsch sending method and apparatus, and communication system

Abstract

Provided in the embodiments of the present application are a PDSCH reception method and apparatus, a PDSCH sending method and apparatus, and a communication system. The method comprises: a terminal device receiving one or more SPS configurations (SPS-Config) and information that is at least used 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 an uplink and a second frequency-domain resource is used for a downlink, and the second time-domain resource is outside of the first time-domain resource; and receiving an SPS PDSCH, which corresponds to at least one of the one or more SPS configurations.

Description

PDSCH receiving and transmitting method, apparatus 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 latency 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 latency 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 a corresponding carrier in 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 can be semi-persistently scheduled. However, in the case of supporting the above working mode, there is no solution for how to semi-persistently schedule PDSCH.

[0007] To solve at least one of the above problems, embodiments of the present application provide a PDSCH receiving and transmitting method, apparatus and communication system.

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

[0009] The terminal device receives one or more SPS configurations and information at least 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

[0010] Receiving an SPS PDSCH corresponding to at least one SPS configuration in the one or more SPS configurations;

[0011] wherein for a SPS PDSCH corresponding to one of the at least one SPS configuration: no SPS PDSCH is received which overlaps with the first time domain resource, or no SPS PDSCH is received which overlaps with the second time domain resource, or for a SPS PDSCH which overlaps with the first time domain resource, frequency domain resources within the second frequency domain resources are valid.

[0012] According to another aspect of embodiments of the present application, a PDSCH receiving method is provided, comprising:

[0013] receiving one or more SPS configurations and information at least 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

[0014] receiving a SPS PDSCH corresponding to at least one of the one or more SPS configurations;

[0015] wherein for a SPS PDSCH corresponding to one of the at least one SPS configuration: no SPS PDSCH is received which overlaps with the first time domain resource, or no SPS PDSCH is received which overlaps with the second time domain resource, or for a SPS PDSCH which overlaps with the first time domain resource, frequency domain resources within the second frequency domain resources are valid.

[0016] According to another aspect of embodiments of the present application, a PDSCH receiving method is provided, comprising:

[0017] receiving one or more SPS configurations and information at least 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

[0018] receiving a SPS PDSCH corresponding to at least one of the one or more SPS configurations;

[0019] wherein for a SPS PDSCH corresponding to one of the at least one SPS configuration: no SPS PDSCH is received which overlaps with the first time domain resource, or no SPS PDSCH is received which overlaps with the second time domain resource, or for a SPS PDSCH which overlaps with the first time domain resource, frequency domain resources within the second frequency domain resources are valid.

[0020] According to another aspect of the embodiments of the present application, a PDSCH sending device is provided, comprising:

[0021] a transmitter configured to transmit one or more SPS configurations and information used at least 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 transmit a SPS PDSCH corresponding to at least one SPS configuration of the one or more SPS configurations;

[0022] a receiver configured to receive one or more SPS configurations and information used at least for configuring a first time domain resource and / or a second time domain resource; and receive a SPS PDSCH corresponding to at least one SPS configuration of the one or more SPS configurations;

[0023] wherein for the SPS PDSCH corresponding to one SPS configuration of the at least one SPS configuration: no SPS PDSCH overlapping with the first time domain resource is transmitted, or no SPS PDSCH overlapping with the second time domain resource is transmitted, or for the SPS PDSCH overlapping with the first time domain resource, frequency domain resources within the second frequency domain resource allocated are valid.

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

[0025] a network device configured to transmit one or more SPS configurations and information used at least 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 transmit a SPS PDSCH corresponding to at least one SPS configuration of the one or more SPS configurations;

[0026] a terminal device configured to receive one or more SPS configurations and information used at least for configuring a first time domain resource and / or a second time domain resource; and receive a SPS PDSCH corresponding to at least one SPS configuration of the one or more SPS configurations;

[0027] wherein for the SPS PDSCH corresponding to one SPS configuration of the at least one SPS configuration: no SPS PDSCH overlapping with the first time domain resource is received, or no SPS PDSCH overlapping with the second time domain resource is received, or for the SPS PDSCH overlapping with the first time domain resource, frequency domain resources within the second frequency domain resource allocated are valid.

[0028] One of the beneficial effects of the embodiments of the present application is that the terminal device receives the SPS PDSCH corresponding to at least one SPS configuration (SPS-Config), and receives the SPS PDSCH at a proper time-frequency location according to the first / second time domain resource. In this way, when the network device works in the full duplex mode, the terminal device can receive the SPS PDSCH, avoid using the resource for uplink, reduce the interference on the resource for uplink, thereby improving the capacity and coverage of uplink transmission, reducing the time delay of uplink transmission, and improving the resource allocation flexibility and resource utilization.

[0029] Specific embodiments of the application are disclosed herein, indicating the ways in which the principles of the application can be employed. It is understood that the embodiments of the application are not limited in scope to the specific embodiments described herein. Embodiments of the application include many alterations, modifications and equivalents.

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

[0031] 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

[0032] Elements and features of one or more embodiments of the application described in the specification and / or one or more figures can be combined with elements and features of one or more other embodiments in the specification and / or one or more figures. In addition, in the drawings, like reference numerals refer to items of like functionality, and the singular articles "a", "an" and "the" as used in the application and its

[0033] The accompanying drawings, which are included to provide a further understanding 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. In the drawings:

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

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

[0036] FIG. 3 is an example diagram of a time domain resource according to an embodiment of the present application;

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

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

[0039] FIG. 6 is an example diagram of excluding PDSCH according to an embodiment of the present application;

[0040] FIG. 7 is a schematic diagram of a PDSCH sending method according to an embodiment of the present application;

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

[0042] FIG. 9 is a schematic diagram of a PDSCH sending apparatus according to an embodiment of the present application;

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

[0044] FIG. 11 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 apparent to those skilled in the art upon consideration of the following description of specific embodiments of the present application, taken in conjunction with the accompanying drawings. In the description of embodiments of the present application, specific terminology is employed for the sake of clarity. However, the application is not intended to be limited to the specific embodiments described, but rather, is intended to include all modifications, equivalents, and alternatives 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, but do not indicate the spatial arrangement or the 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, refer to the existence 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 forms "a", "an", and "the" include the plural forms, and should be broadly understood as "one" or "one kind" rather than 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 conforming to any communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.

[0049] In addition, the communication between devices in the communication system can be performed according to any phase 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, and the like, and / or other currently known or to be developed communication protocols.

[0050] In the embodiments of the present application, the term "network device" refers to a device that accesses a terminal device to a communication network and provides services for the terminal device in the communication system, for example. 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: 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 remote radio head (RRH), remote radio unit (RRU), relay, or low-power node (such as femto, pico, and the like). In addition, 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 the embodiments of the present application, the term "user equipment" (UE) refers to 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 smart phone, a smart watch, a digital camera, and the like.

[0054] For another example, in an Internet of Things (IoT) scenario or the like, the terminal equipment can also be a machine or device that performs monitoring or measurement, which can include, but is not limited to, the following devices: 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 one 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 equipment side" refers to one 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 document, "device" can refer to a network device or a terminal device unless otherwise specified.

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

[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 the 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 layer (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 the embodiments of the present application are only examples, and other names can also be used, and the embodiments of the present application are not limited thereto.

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

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

[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 μ” 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 the 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 the embodiments of the present application are not limited thereto.

[0065] In the embodiments of the present application, the network device 101 and the terminal devices 102 and 103 can perform existing services or future implementable services. For example, the 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), and the like.

[0066] 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, for example, ACK / NACK information, etc. The terminal device 102 can confirm the end of the transmission process according to the feedback information, or can perform new data transmission again, or can perform data retransmission.

[0067] The network device 101 can send data to the terminal device 102 and / or the terminal device 103 using a unicast or groupcast or broadcast mode. The terminal device 102 can receive data sent 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 bracketed expression or limitation can be added in some embodiments, or the bracketed expression or limitation can be ignored in other embodiments, “ / ” represents “and / or”, and the present application is not limited thereto. The various embodiments of the embodiments of the present application are described below in conjunction with the accompanying drawings. These embodiments are only exemplary and are not limiting to the present application.

[0071] Embodiments of the first aspect

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

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

[0074] 201, the terminal device receives one or more SPS configurations and information at least 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;

[0075] 202, the terminal device receives the SPS PDSCH corresponding to at least one SPS configuration (SPS-Config) in the one or more SPS configurations;

[0076] Wherein, for the SPS PDSCH corresponding to one SPS configuration (or for one SPS configuration) in the at least one SPS configuration: do not receive (drop) the SPS PDSCH overlapping with the first time domain resource (or the SPS PDSCH in the first time domain resource), or do not receive the SPS PDSCH overlapping with the second time domain resource (or the SPS PDSCH in the second time domain resource), or for the SPS PDSCH overlapping with the first time domain resource, the frequency domain resource allocated (only) within the second frequency domain resource is valid.

[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 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 content, 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.

[0079] For example, in the initial access process (from RRC_IDLE to RRC_Connected state, including CBRA) and / or in the random access process (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).

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

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

[0082] The following first describes the time domain resources related to the embodiments of the present application.

[0083] In some embodiments, for one cell or carrier, in the first time domain resource, different frequency domain resources are respectively used (only) for (receiving) uplink (e.g. corresponding to the following first frequency domain resource) and (only) for (transmitting) downlink (e.g. corresponding to the following second frequency domain resource), for example, the network device can simultaneously receive (uplink signals) on the frequency domain resource used (only) for uplink and transmit (downlink signals) on the frequency domain resource used (only) for downlink; 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 frequency domain resources used (only) for uplink and frequency domain resources used (only) for downlink, and the network device does not simultaneously receive and transmit.

[0084] 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.

[0085] 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 UL-DL Configuration (TDD-UL-DL-ConfigCommon) IE (in TDD UL-DL Pattern (TDD-UL-DL-Pattern) IE)), and / or, the high layer parameter for configuring SBFD symbols is optionally present in Serving Cell Configuration (ServingCellConfig).

[0086] In some embodiments, a cell / carrier can be configured with one or more (e.g. 2) TDD UL-DL patterns, when configured with multiple patterns, different patterns are with or without corresponding SBFD symbols respectively, different patterns are independently configured with corresponding SBFD symbols.

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

[0088] 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, from the starting symbol of the starting slot to the ending symbol of the ending slot are SBFD symbols. The slot index is the numbering of the slots included in the period, which, for example, starts from 0 or 1 and increases by 1 in turn. For example, when the starting slot index is 0, the starting slot is the first slot in the period, 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 numbering of the symbols in the slot. Among them, the above-mentioned slots / symbols are configured with SCS by the reference Subcarrier Spacing field of the Common TDD UL-DL Configuration (TDD-UL-DL-ConfigCommon) IE.

[0089] For example, each / different pattern is configured with a period independently, e.g., configured with a dl-UL-TransmissionPeriodicity (in the (TDD-UL-DL-Pattern) IE) respectively. Wherein, when configured with only one pattern, the period of SBFD symbols is the same as the period of the pattern, and when configured with multiple (e.g., 2) patterns, the period of SBFD symbols is the same as the sum of the periods of all patterns.

[0090] In some embodiments, a downlink symbol is a symbol indicated as downlink by a first uplink-downlink configuration, an uplink symbol is a symbol indicated as uplink by the first uplink-downlink configuration, and a flexible symbol is a symbol neither indicated as downlink nor indicated as uplink by the first uplink-downlink configuration, or a symbol indicated as flexible by the first uplink-downlink configuration. Wherein, the first uplink-downlink configuration is used to provide a cell-specific uplink-downlink configuration, e.g., a tdd-UL-DL-ConfigurationCommon or a (TDD-UL-DL-ConfigCommon) IE or a (TDD-UL-DL-Pattern) IE, without limitation.

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

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

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

[0094] In some embodiments, the SBFD / non-SBFD symbol refers to the SBFD / non-SBFD symbol configured based on the reference SubcarrierSpacing or the SBFD / non-SBFD symbol corresponding to the BWP.

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

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

[0097] In some embodiments, the SBFD symbol overlaps with the downlink symbol or the flexible symbol, or in other words, the SBFD symbol is configured within the range of the downlink symbol and / or the flexible symbol.

[0098] In some embodiments, the SBFD symbol includes the DL SBFD symbol and / or the Flexible SBFD symbol, and the non-SBFD symbol includes the Full-DL symbol and / or the Full-Flexible symbol and / or the Full-UL symbol (or the UL symbol), and each type of symbol can also be represented in other ways, which are not limited thereto.

[0099] FIG. 3 is an example diagram of time domain resources according to embodiments of the present application. As shown in FIG. 3, a period can include a plurality of different symbols. Among them, the SBFD symbol is within the range of the downlink symbol and the flexible symbol, the SBFD symbol overlapping with the DL symbol is denoted as the DL SBFD symbol, the SBFD symbol overlapping with the flexible symbol is denoted as the Flexible SBFD symbol, the downlink symbol not overlapping with the SBFD symbol is denoted as the Full-DL symbol, the flexible symbol not overlapping with the SBFD symbol is denoted as the Full-Flexible symbol, and the UL symbol not overlapping with the SBFD symbol is denoted as the 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 application, but is not limited thereto.

[0100] The frequency domain resources involved in embodiments of the present application are schematically described below.

[0101] For a cell and / or a carrier, the first time domain resource, the first frequency domain resource is (only) for uplink and the second frequency domain resource is (only) for downlink, that is, the frequency domain resources are divided into the first frequency domain resource (only) for uplink and the second frequency domain resource (only) for downlink. The second time domain resource is outside the first time domain resource, that is, in the second time domain resource, the above-mentioned division of the frequency domain resources is not performed.

[0102] For example, the first frequency domain resource includes uplink subband (UL subband) and / or uplink available PRBs, and the second frequency domain resource includes downlink subband (DL subband) and / or downlink available PRBs, other names can also be used, which are not limited thereto.

[0103] 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.

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

[0105] The higher layer parameters for configuring DL subband are optionally present in the (DownlinkConfigCommon IE (in the FrequencyInfoDL IE (in the SCS-SpecificCarrier IE) in the ServingCellConfigCommon IE (in the CommonDownlinkConfig IE (in the ServingCellConfig IE))), e.g. the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > DownlinkConfig Common > FrequencyInfoDL > SCS-SpecificCarrier, and / or, optionally present in the ServingCellConfig. That is, the higher layer parameters for configuring DL subband can optionally be present in any one of the above parameters.

[0106] For another example, the higher layer parameters for configuring UL subband are optionally present in the (SCS-SpecificCarrier IE (in the FrequencyInfoUL-SIB IE (in the UplinkConfigCommonSIB IE (in the ServingCellConfigCommonSIB IE (in the CommonUplinkConfig IE (in the ServingCellConfig IE))))) in the SIB1, e.g. the inclusion relationship of the above parameters can be represented as: SIB1 > ServingCellConfig CommonSIB > UplinkConfigCommonSIB > FrequencyInfoUL-SIB > SCS-SpecificCarrier, and / or,

[0107] The higher layer parameters for configuring UL subband are optionally present in the common serving cell configuration (ServingCellConfigCommon) IE (in the uplink configuration common (UplinkConfigCommon) IE (in the frequency information UL (FrequencyInfoUL) IE (in the SCS-specific carrier (SCS-SpecificCarrier) IE))), e.g. the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > UplinkConfigCommon > FrequencyInfoUL > SCS-SpecificCarrier, and / or, optionally present in the serving cell configuration (ServingCellConfig). Namely, the higher layer parameters for configuring UL subband can optionally be present in any one of the above parameters.

[0108] In some embodiments, the higher layer parameters for configuring UL subband and the higher layer parameters for configuring DL subband comprise one or more parameters for providing resource indication value (RIV) 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.

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

[0110] Table 1

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

[0112] 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.

[0113] For example, different / each SCS configuration in the UL scs-SpecificCarrierList is respectively configured with one UL subband, or in other words, respectively corresponds to one UL subband, for example, respectively corresponds to an independent above-mentioned higher layer parameter for configuring UL subband. Different / each SCS configuration in the DL scs-SpecificCarrierList is respectively configured with one or more (e.g. 2) DL subbands, or in other words, respectively corresponds to one or more DL subbands, for example, respectively corresponds to an 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.

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

[0115] In some embodiments, the uplink available 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 available 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 available PRBs are the intersection between the UL BWP and the uplink subband corresponding to SCS = 15 kHz.

[0116] FIG. 4 is an example diagram of uplink available 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, for example, represents the uplink subband corresponding to the SCS of the UL BWP, but the present application is not limited thereto.

[0117] In some embodiments, the downlink available 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 = 15 kHz, then its corresponding DL available PRB is the intersection between the DL BWP and the downlink subband corresponding to SCS = 15 kHz. If the SCS of one DL BWP = 30 kHz, then its corresponding DL available PRB is the intersection between the DL BWP and the downlink subband corresponding to SCS = 15 kHz.

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

[0119] The time-frequency resources are described above, and the SPS PDSCH according to embodiments of the present application is described below.

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

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

[0122] In embodiments of the present application, the terminal device can be provided with one or more SPS configurations (SPS-Config), and each SPS configuration independently provides time-frequency domain resource allocation to semi-persistently schedule PDSCH, but the present application is not limited thereto. The one or more SPS configurations include SPS configurations for unicast and / or SPS configurations for multicast.

[0123] In some embodiments, the SPS configuration for unicast is (directly) included in the BWP-DownlinkDedicated IE, and the SPS configuration for multicast is included in the CFR-Config Multicast IE (in the BWP-DownlinkDedicated IE).

[0124] In some embodiments, the SPS is activated by a DCI or provided with a DL assignment by the activating DCI. The activating DCI is, for example, DCI format 1_0 / 1_1 / 1_2 / 4_0 / 4_1 / 4_2, but not limited to. For example, for the SPS for unicast, the activating DCI is DCI format 1_0 / 1_1 / 1_2 with CRC scrambled by CS-RNTI. For example, for the SPS for multicast, the activating DCI is DCI format 4_0 / 4_1 / 4_2 with CRC scrambled by G-CS-RNTI.

[0125] In some embodiments, the (TDRA field of the) activating DCI indicates a row from a (time domain) resource allocation table, which corresponds to one SLIV or directly the start symbol S and the allocation length L (corresponding to a symbol allocation), one (PDSCH) mapping type, one slot offset K0. The time domain resource indicated by the activating DCI includes, for example, the symbols allocated in the slot (e.g., referred to as the first slot) determined by the slot offset K0.

[0126] For example, the slot determined by the slot offset K0 includes, for example, the slot where n is the slot with the scheduling DCI, μ PDSCH and μ PDCCH are the subcarrier spacing configurations for PDSCH and PDCCH, respectively.

[0127] In some embodiments, the first SPS PDSCH is, for example, the PDSCH in the slot determined by the slot offset K0. The first SPS PDSCH can also be referred to as the PDSCH scheduled by the corresponding activating DCI or the (first) SPS PDSCH associated with the corresponding activating DCI.

[0128] In some embodiments, for the SPS, after being configured / provided with a DL assignment, the UE determines the (first) slot where the SPS PDSCH (in one period) is located according to the periodicity provided in the SPS configuration.

[0129] For example, Table 2 shows an example:

[0130] Table 2

[0131] In some embodiments, in a period, SPS PDSCH is only in one slot (SPS PDSCH without repetition).

[0132] In some embodiments, (in a period, ) SPS PDSCH is repeated in multiple consecutive slots (SPS PDSCH with repetition) (starting from the first slot mentioned above), the same symbol allocation / SLIV is applied to the multiple slots (that is, the multiple slots correspond to the same symbols (indices) for transmitting the TB), different repetitions (or called transmission opportunities) correspond to, for example, different redundancy versions, but not limited to. The number of repetitions or the number of slots included in the multiple slots is determined by pdsch-AggregationFactor (in SPS configuration or PDSCH configuration) or repetitionNumber (corresponding to the row indicated by the TDRA field of the activation DCI).

[0133] For example, for PDSCH activated by DCI format 1_1 or DCI format 1_2 (activated PDSCH) or PDSCH scheduled by the activation DCI, if pdsch-AggregationFactor is included in the SPS configuration, the number is determined by pdsch-AggregationFactor in the SPS configuration, otherwise, it is determined by pdsch-Aggregation Factor in the PDSCH configuration (pdsch-config) (for example, equal to the number configured by the pdsch-AggregationFactor). For PDSCH activated by DCI format 4_1 or DCI format 4_2 (activated PDSCH) or PDSCH scheduled by the activation DCI, if pdsch-AggregationFactor is included in the SPS configuration, the number is determined by pdsch-AggregationFactor in the SPS configuration, otherwise, repetitionNumber corresponding to the row indicated by the TDRA field of the activation DCI determines.

[0134] In some embodiments, in case of repetition (SPS PDSCH with repetition), (in one period, ) (one downlink assignment corresponds to one SPS PDSCH), an SPS PDSCH includes multiple repetitions, i.e., the repetitions in different slots corresponding to the same TB are considered as one SPS PDSCH.

[0135] In some embodiments, in case of repetition (SPS PDSCH with repetition), (in one period, ) (one downlink assignment corresponds to multiple SPS PDSCHs), one SPS PDSCH includes one repetition, i.e., the repetitions in different slots corresponding to the same TB are considered as one SPS PDSCH, respectively.

[0136] In some embodiments, for PDSCH, one repetition can also be referred to as / correspond to one PDSCH reception (occasion).

[0137] In some embodiments, repetition and SPS PDSCH can be interchangeable. For example, SPS PDSCH can be replaced by repetition “repetition”, and then the corresponding description is applicable to the case of repetition.

[0138] In some embodiments, different SPS PDSCHs (in one period) correspond to independent HARQ process IDs and / or TBs. In some examples, the HARQ process IDs corresponding to different SPS PDSCHs (in one period) can be the same, or, in other examples, the HARQ process IDs corresponding to different SPS PDSCHs (in one period) can be different.

[0139] In some embodiments, the allocated frequency domain resources include PRBs indicated / allocated by the FDRA field in the activation DCI, e.g., these PRBs can be referred to as assigned / allocated PRBs. The allocated frequency domain resources within the second frequency domain resources include / are determined as the intersection (of PRBs) between the above-mentioned assigned / allocated frequency domain resources 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 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 where the PDSCH is located, but not limited thereto.

[0140] For example, the TBS is determined according to the above-mentioned frequency domain resources, including: the TBS is determined according to the number of PRBs included in the frequency domain resources, e.g., in the process of determining the TBS, the UE needs to determine the number of REs (within a slot), e.g., 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 assigned PRBs or the number of assigned PRBs within DL usable PRBs (or DL subband), N′ RE is the number of REs allocated for PDSCH within a PRB.

[0141] In the embodiments of the present application, for the SPS PDSCH corresponding to one (one / a) SPS configuration in the at least one SPS configuration (or for one SPS configuration): the SPS PDSCH overlapping with the first time domain resources is not received (dropped), or the SPS PDSCH overlapping with the second time domain resources is not received, or for the SPS PDSCH overlapping with the first time domain resources, the frequency domain resources (PRBs) within the (only) second frequency domain resources allocated are valid (the frequency domain resources outside the allocated second frequency domain resources are invalid).

[0142] Thus, the PDSCH / repetition selected by the terminal device does not exist PDSCH / repetition overlapping with the invalid time domain resource type, which can avoid selecting PDSCH / repetition overlapping with the invalid time domain resource type, and for PDSCH overlapping with SBFD symbol, it can avoid using the frequency domain resource for uplink, thereby improving the data transmission rate.

[0143] In some embodiments, for one SPS configuration corresponding SPS PDSCH (or for one SPS configuration):

[0144] When the SBFD symbol is the invalid time domain resource type (or, when (only) the non-SBFD symbol is the valid time domain resource type), the SPS PDSCH (for SPS PDSCH without repetition or with repetition) / repetition (for SPS PDSCH with repetition) overlapping with the SBFD symbol is not received (dropped); and / or,

[0145] When the non-SBFD symbol is the invalid time domain resource type (or, when (only) the SBFD symbol is the valid time domain resource type), the SPS PDSCH (for SPS PDSCH without repetition or with repetition) / repetition (for SPS PDSCH with repetition) overlapping with the non-SBFD symbol is not received; and / or,

[0146] When the SBFD symbol is not the invalid time domain resource type, for the SPS PDSCH (for SPS PDSCH without repetition or with repetition) / repetition (for SPS PDSCH with repetition) overlapping with the SBFD symbol, the frequency domain resource within the (only) non-SBFD symbol allocated is valid.

[0147] For example, (in the case of case 1) for the first resource allocation type, when case 1-1 and one allocated RBG overlaps with the sub-band boundary, only the PRB within the DL usable PRB is considered valid for PDSCH reception. The UE does not expect to be allocated RBG for PDSCH completely outside the DL usable PRB, or RBG for PUSCH completely outside the UL usable PRB.

[0148] For example, (in case 1), for the second resource allocation type, (when the PRG (precoding resource block group) granularity is determined as one of {2, 4}), when the valid symbol type is SBFD symbol, only the PRBs within the allocated DL usable PRBs are considered valid for PDSCH. The PRBs outside the allocated DL usable PRBs are considered invalid and not used for PDSCH resource mapping.

[0149] In some embodiments, the SBFD symbol is not invalid time domain resource type includes: not having invalid time domain resource type (case 2), and / or, the second time domain resource is invalid time domain resource type (case 1-2).

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

[0151] For example, in resource allocation type 0, the FDRA field (or referred to as resource block assignment information) in DCI includes a bitmap indicating RBGs, which is described as follows: the bitmap is of size N RBG bits 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. Where, N RBG is the number of RBGs in the UL BWP.

[0152] For example, in resource allocation type 1, the FDRA field (or referred to as resource block assignment information) in 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.

[0153] In some embodiments, after excluding SPS PDSCHs overlapping with invalid time domain resource type (processing / resolving the overlap with invalid time domain resource), and / or, after excluding SPS PDSCHs overlapping with time domain resource indicated as uplink (processing / resolving the overlap with time domain resource indicated as uplink), and / or, after excluding SPS PDSCHs not having valid frequency domain resource or the ratio of valid frequency domain resource to allocated frequency domain resource is less than or not greater than a first specific value (predefined / configured) (processing / resolving the SPS PDSCHs not having valid frequency domain resource or the ratio of valid frequency domain resource to allocated frequency domain resource is less than or not greater than a first specific value), and / or, after excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource (processing the SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource), and / or, after excluding SPS PDSCHs overlapping with the inactive period of cell DTX (processing / resolving the overlap with the inactive period of cell DTX), one or more PDSCHs are selected and received from the more than one SPS PDSCHs in a slot (if there are more than one SPS PDSCHs in a slot).

[0154] In some examples, after excluding SPS PDSCHs overlapping with invalid time domain resource type, one PDSCH is selected and received from the more than one SPS PDSCHs (if there are) in a slot. Or, after processing / resolving the overlap with invalid time domain resource, one PDSCH is selected and received from the more than one SPS PDSCHs (if there are) in a slot.

[0155] In some examples, after excluding SPS PDSCHs overlapping with time domain resource indicated as uplink (e.g. by the first uplink-downlink configuration / second uplink-downlink configuration / third uplink-downlink configuration), one PDSCH is selected and received from the more than one SPS PDSCHs (if there are) in a slot. Or, after processing / resolving the overlap with time domain resource indicated as uplink, one PDSCH is selected and received from the more than one SPS PDSCHs (if there are) in a slot.

[0156] For example, the second uplink-downlink configuration is used to provide UE-specific / dedicated uplink-downlink configuration, e.g. tdd-UL-DL-ConfigurationDedicated, without limitation. For example, the third uplink-downlink configuration is dedicated to indicate the uplink-downlink of SBFD symbol, which is different from the first uplink-downlink configuration / second uplink-downlink configuration.

[0157] For another example, the second uplink-downlink configuration is used for configuring uplink-downlink of SBFD symbols and / or non-SBFD symbols.

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

[0159] In some examples, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after excluding the SPS PDSCHs that do not have valid frequency domain resources. Or, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after excluding the SPS PDSCHs that have a ratio of valid frequency domain resources to allocated frequency domain resources less than or not greater than a first specific value (predefined / configured). Or, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after processing / resolving the SPS PDSCHs that do not have valid frequency domain resources. Or, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after processing / resolving the SPS PDSCHs that have a ratio of valid frequency domain resources to allocated frequency domain resources less than or not greater than a first specific value.

[0160] In some examples, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after excluding the SPS PDSCHs that overlap with both the first time domain resource and the second time domain resource. Or, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after processing the SPS PDSCHs that overlap with both the first time domain resource and the second time domain resource.

[0161] In some examples, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after excluding the SPS PDSCHs that overlap with the inactive period of cell DTX. Or, one PDSCH is selected and received from the more than one SPS PDSCH (if any) in a slot after processing / resolving the SPS PDSCHs that overlap with the inactive period of cell DTX.

[0162] The above conditions for selecting and receiving SPS PDSCH are illustrative, but not limited thereto.

[0163] In some embodiments, selecting and receiving one or more SPS PDSCHs from the plurality of SPS PDSCHs comprises:

[0164] Step 0: Set a first parameter = 0; wherein the first parameter is the number of selected PDSCHs, the first set is a set of the plurality of SPS PDSCHs;

[0165] Step 1: Receive the (one) PDSCH in the first set with the lowest SPS configuration index (the PDSCH is designated as survivor PDSCH), the first parameter plus 1;

[0166] Step 2: Exclude the (one) PDSCH (survivor PDSCH) in the step 1 and PDSCH(s) even partially overlapping with the PDSCH from the first set;

[0167] Step 3: Repeat step 1 and 2 until the first set is empty or the first parameter equals to the number of PDSCHs in one slot supported by the terminal device.

[0168] In some embodiments, each SPS PDSCH in the plurality of SPS PDSCHs respectively corresponds to a different SPS configuration in the at least one SPS configuration. For example, any 2 SPS configurations are different.

[0169] In some embodiments, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink comprises:

[0170] For SPS PDSCHs overlapping with the first time domain resources, excluding SPS PDSCHs overlapping with the (first) time domain resources indicated as uplink by the second uplink-downlink configuration or the third uplink-downlink configuration, and / or,

[0171] For SPS PDSCHs overlapping with the second time domain resources, excluding SPS PDSCHs overlapping with the (second) time domain resources indicated as uplink by the first uplink-downlink configuration or the second uplink-downlink configuration.

[0172] In some embodiments, for the first time domain resources, the terminal device ignores / does not apply the second uplink-downlink configuration (e.g., tdd-UL-DL-ConfigurationDedicated).

[0173] For example, even if the second uplink-downlink configuration indicates one SBFD symbol as uplink or downlink, the terminal device does not consider the SBFD symbol as indicated as uplink or downlink, but determines whether to transmit uplink or receive downlink or not to transmit and receive in the SBFD symbol according to other indications or predefined rules.

[0174] In some embodiments, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink by the first uplink-downlink configuration or the second uplink-downlink configuration, comprises:

[0175] For SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration),

[0176] If the first time domain resource is an invalid time domain resource type, excluding SPS PDSCHs or repetitions (for PDSCH with repetition) overlapping with the (second) time domain resource indicated as uplink by the first uplink-downlink configuration or the second uplink-downlink configuration, and / or,

[0177] If the second time domain resource is an invalid time domain resource type, excluding SPS PDSCHs or repetitions (for PDSCH with repetition) overlapping with the (first) time domain resource indicated as uplink by the second uplink-downlink configuration or the third uplink-downlink configuration, and / or,

[0178] If there is no invalid time domain resource type:

[0179] For SPS PDSCHs overlapping with the first time domain resource, excluding SPS PDSCHs or repetitions (for PDSCH with repetition) overlapping with the (first) time domain resource indicated as uplink by the second uplink-downlink configuration or the third uplink-downlink configuration, and / or, for SPS PDSCHs overlapping with the second time domain resource, excluding SPS PDSCHs or repetitions (for PDSCH with repetition) overlapping with the (second) time domain resource indicated as uplink by the first uplink-downlink configuration or the second uplink-downlink configuration.

[0180] In some embodiments, excluding SPS PDSCHs not having valid frequency domain resources or having a ratio of valid frequency domain resources to allocated frequency domain resources less than or not greater than a first specific value, comprises:

[0181] For SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration), if the first time domain resource is not an invalid time domain resource type, and SPS PDSCHs overlapping with the first time domain resource do not have valid frequency domain resources or have a ratio of valid frequency domain resources to allocated frequency domain resources less than or not greater than a first specific value, excluding SPS PDSCHs or repetitions (for PDSCH with repetition) overlapping with the first time domain resource.

[0182] In some embodiments, excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource, comprises:

[0183] For a SPS configuration corresponding to a SPS PDSCH (or for a SPS configuration), if there is no invalid time domain resource type, exclude the SPS PDSCH or repetition (for PDSCH with repetition) that overlaps with both the first time domain resource and the second time domain resource.

[0184] In some embodiments, the plurality of SPS PDSCHs include a first SPS PDSCH associated with a corresponding activation DCI and / or a PDSCH without a corresponding PDCCH transmission; or

[0185] The plurality of SPS PDSCHs include a PDSCH without a corresponding PDCCH transmission, which includes a first SPS PDSCH (and subsequent SPS PDSCHs) associated with a corresponding activation DCI.

[0186] Table 3 exemplarily illustrates the above partial embodiments, but is not limited thereto.

[0187] Table 3

[0188] FIG. 6 is an example diagram of excluding PDSCHs according to an embodiment of the present application, which exemplarily illustrates the case of some embodiments.

[0189] As shown in FIG. 6, it is assumed that for the SPS configuration (corresponding to SPS PDSCH) of SPS configuration index = 0 and the SPS configuration (corresponding to SPS PDSCH) of SPS configuration index = 3, the SBFD symbols are invalid time domain resource types, for the SPS configuration (corresponding to SPS PDSCH) of SPS configuration index = 1, the non-SBFD symbols are invalid time domain resource types, and for the SPS configuration (corresponding to SPS PDSCH) of SPS configuration index = 2, there is no invalid time domain resource type.

[0190] In slot 1 and slot 5, after excluding the SPS PDSCHs overlapping with the invalid time domain resource types, there are still 3 SPS PDSCHs, if the UE can only receive one PDSCH in a slot, the SPS PDSCH corresponding to the SPS configuration of SPS configuration index = 0 is selected and received, if 2 PDSCHs can be received, the SPS PDSCH corresponding to the SPS configuration of SPS configuration index = 0 and the SPS PDSCH corresponding to the SPS configuration of SPS configuration index = 3 are selected and received.

[0191] In slot 3, after excluding SPS PDSCHs overlapping with invalid time domain resource type, there are still 2 SPS PDSCHs, if UE can only receive one PDSCH in a slot, the SPS PDSCH corresponding to SPS configuration with index = 2 is selected and received, if 2 PDSCHs can be received, the 2 SPS PDSCHs are selected and received.

[0192] In slot 2 and slot 4, after excluding SPS PDSCHs overlapping with invalid time domain resource type, there is only 1 SPS PDSCH, UE does not need to select, directly receives the 1 SPS PDSCH.

[0193] The above only describes some cases of the embodiments of the present application, and Figure 6 does not show the case where SPS PDSCH needs to be excluded due to other reasons. For other reasons, please refer to the related art. In addition, Figure 6 combines some examples for convenience of description, and the present application is not limited thereto. For example, one or more of the examples can be implemented alone, or in combination with other embodiments.

[0194] The above describes how to receive SPS PDSCH when there are multiple SPS configurations corresponding to SPS PDSCH. The following describes how to configure and determine invalid time domain resource type and / or valid time domain resource type.

[0195] In some embodiments, invalid time domain resource type and / or valid time domain resource type is determined based on time domain resource (e.g., symbol in the first slot) indicated by the first information and / or the second information and / or the first reference SPS PDSCH (of the first reference repetition (for the case of repetition)) and / or the corresponding activation DCI (in the TDRA field).

[0196] In some embodiments, time domain resource type includes, for example, slot type and / or symbol type, for example, time domain resource is divided into 2 types, the above-mentioned SBFD symbol and non-SBFD symbol.

[0197] - case 1: with invalid time domain resource type, for example, one of SBFD symbol and non-SBFD symbol is invalid, and the other is valid, PDSCH transmission is limited in SBFD symbol (when SBFD symbol is valid, non-SBFD symbol is invalid) or limited in non-SBFD symbol (when non-SBFD symbol is valid, SBFD symbol is invalid).

[0198] -- Case 1-1: SBFD symbols are invalid symbol type, or 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 the valid symbol type is non-SBFD symbols (e.g., the valid symbol type is non-SBFD symbols, or non-SBFD symbols are valid).

[0199] -- Case 1-2: SBFD symbols are valid symbol type, or 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 the invalid symbol type is non-SBFD symbols (e.g., the invalid symbol type is non-SBFD symbols, or non-SBFD symbols are invalid)

[0200] - Case 2: No invalid symbol type (e.g., no invalid symbol type), e.g., both SBFD symbols and non-SBFD symbols are valid, PDSCH transmission can cross SBFD symbols and non-SBFD symbols, e.g., for PDSCHs in a plurality of PDSCHs, PDSCHs overlapping with SBFD symbols or non-SBFD symbols can be received. For PDSCHs with repetition, repetitions overlapping with SBFD symbols or non-SBFD symbols can be received.

[0201] 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 symbol type (i.e., case 2) and / or to indicate having invalid symbol type (i.e., case 1).

[0202] For example, (when the first information is only used to indicate case 2, or the first information is used to indicate case 1 also indicates 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.

[0203] For example, (when the first information is only used to indicate case 1, or the first information is used to indicate case 1 also indicates 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. The UE determines whether it is case 1-1 or Case 1-2 according to the second information and / or the first reference SPS PDSCH. The second information is included in DCI for example, but not limited thereto.

[0204] For example, if the first reference SPS PDSCH is in non-SBFD symbols, it is case 1-1; if the first reference SPS PDSCH overlaps with SBFD symbols, it is case 1-2. For example, the first reference SPS PDSCH is the first SPS PDSCH.

[0205] The above exemplary first information / second information is described, and how to configure / indicate is further described below.

[0206] In some embodiments, the first information is used to indicate that there is no invalid time domain resource type and / or is used to indicate that there is invalid time domain resource type.

[0207] For example, at least one of the first time domain resource and the second time domain resource is an invalid time domain resource type;

[0208] The first information (optionally) exists outside the SPS configuration (e.g. is included in PDSCH-Config or PDSCH-ConfigCommon), the first information applies to all or part of the at least one SPS configuration, or the first information (optionally) exists in the SPS configuration, the first information applies to the SPS configuration where it is located.

[0209] In some embodiments, the first information also applies to other PDSCH scheduling (e.g. DCI scheduling multiple PDSCH and / or DCI scheduling PDSCH repetition) and / or CSI-RS (e.g. periodic CSI-RS and / or semi-persistent CSI-RS).

[0210] In some embodiments, the second information is used to indicate the invalid time domain resource type and / or the valid time domain resource type.

[0211] For example, the second information is used to indicate that the first time domain resource is the invalid time domain resource type and / or used to indicate that the second time domain resource is the invalid time domain resource type, or the second information is used to indicate that the first time domain resource is the valid time domain resource type and / or used to indicate that the second time domain resource is the valid time domain resource type; the second information (optionally) exists in the SPS configuration, and the second information is applied to the SPS configuration where the second information exists.

[0212] In some embodiments, determining the invalid time domain resource type and / or the valid time domain resource type based on the first reference SPS PDSCH (of the first reference repetition) comprises: the valid time domain resource type is the time domain resource type of the first reference SPS PDSCH (of the first reference repetition).

[0213] For example, if the first reference SPS PDSCH (of the first reference repetition) overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource;

[0214] For example, if the first reference SPS PDSCH (of the first reference repetition) overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource.

[0215] For example, the terminal device does not expect the first reference SPS PDSCH (of the first reference repetition) to overlap with both the first time domain resource and the second time domain resource.

[0216] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the first reference SPS PDSCH to overlap with only the first time domain resource or to overlap with only the second time domain resource.

[0217] In some embodiments, the valid time domain resource type or the time domain resource type of the first reference SPS PDSCH is the time domain resource type of the first reference repetition (e.g., the first repetition) of the first reference SPS PDSCH.

[0218] For example, if it overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource;

[0219] For example, if it overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource.

[0220] For example, the first reference repetition is not expected to overlap with both the first time domain resource and the second time domain resource.

[0221] In some embodiments, determining the valid time domain resource type and / or the invalid time domain resource type based on the time domain resources indicated by the activation DCI comprises:

[0222] If the time domain resources indicated by the activation DCI overlap with only the first time domain resource, the valid time domain resource type is the first time domain resource, and / or, the invalid time domain resource type is the second time domain resource.

[0223] If the time domain resources indicated by the activation DCI overlap with only the second time domain resource, the valid time domain resource type is the second time domain resource, and / or, the invalid time domain resource type is the first time domain resource.

[0224] In some embodiments, when the first information is used to indicate that there is no invalid time domain resource type:

[0225] The first information and the second information do not exist at the same time (when the first information exists, the second information does not exist, and vice versa); or,

[0226] When the first information and the second information exist at the same time, the first information is not applied to the SPS configuration including the second information, and / or, is applied to the SPS configuration not including the second information.

[0227] For example, for one SPS configuration including the second information, the first time domain resource or the second time domain resource is an invalid time domain resource (determined by the terminal device according to the second information);

[0228] For another example, for one SPS configuration not including the second information, neither the first time domain resource nor the second time domain resource is an invalid time domain resource (determined by the terminal device according to the first information).

[0229] In some embodiments, when the terminal device is not provided with the first information (for example, assuming that at this time at least one of the first time domain resource and the second time domain resource is an invalid time domain resource type by default), the second information is included in the SPS configuration (must), or when the first information indicates that there is an invalid time domain resource type, the second information is included in the SPS configuration (must).

[0230] In some embodiments, for the SPS configuration not including the second information:

[0231] The terminal device determines the type of invalid time domain resource and / or the type of valid time domain resource based on the first reference SPS PDSCH or the time domain resource indicated by the activation DCI, or the terminal device considers that the first time domain resource or the second time domain resource is the type of invalid time domain resource.

[0232] In some embodiments, for the SPS PDSCH corresponding to one SPS configuration, the allocated frequency domain resource is indicated by the FDRA field in the corresponding activation DCI.

[0233] For example, when the at least one SPS configuration includes more than one SPS configuration, the activation DCI corresponding to different SPS configurations is different, and the activation DCI includes information for indicating the SPS configuration index.

[0234] In some embodiments, for the SPS PDSCH corresponding to one SPS configuration, when the second time domain resource is the type of invalid time domain resource, the terminal device expects that the allocated frequency domain resource is within the second frequency domain resource.

[0235] For example, when the non-SBFD symbol is the type of invalid time domain resource, the terminal device expects that the allocated frequency domain resource is within the second frequency domain resource in the SBFD symbol.

[0236] In some embodiments, for the SPS PDSCH corresponding to one SPS configuration:

[0237] The first time domain resource is not the type of invalid time domain resource,

[0238] The terminal device does not expect the SPS PDSCH overlapping with the first time domain resource to have a valid frequency domain resource, or the terminal device does not expect the ratio of the valid frequency domain resource to the allocated frequency domain resource to be less than or not greater than a first specific value, or

[0239] If the SPS PDSCH overlapping with the first time domain resource has no valid frequency domain resource, or if the ratio of the valid frequency domain resource to the allocated frequency domain resource is less than or not greater than the first specific value, the terminal device does not receive the SPS PDSCH overlapping with the first time domain resource.

[0240] In some embodiments, for the SPS PDSCH corresponding to one SPS configuration:

[0241] When the first time domain resource is the type of invalid time domain resource, the terminal device does not receive the SPS PDSCH overlapping with the (second) time domain resource indicated as uplink by the first uplink-downlink configuration or the second uplink-downlink configuration; and / or,

[0242] When the second time domain resource is the invalid time domain resource type, the terminal device does not receive the SPS PDSCH overlapping the (first) time domain resource indicated as uplink by the second or third uplink-downlink configuration; and / or,

[0243] When there is no invalid time domain resource type:

[0244] For the SPS PDSCH overlapping the first time domain resource, the terminal device does not receive the SPS PDSCH overlapping the (first) time domain resource indicated as uplink by the second or third uplink-downlink configuration, and / or, for the SPS PDSCH overlapping the second time domain resource, the terminal device does not receive the SPS PDSCH overlapping the (second) time domain resource indicated as uplink by the first or second uplink-downlink configuration.

[0245] In some embodiments, (when there is no invalid time domain resource type (not limited thereto),) the terminal device does not expect the SPS PDSCH to overlap both the first time domain resource and the second time domain resource, or the terminal device does not receive the SPS PDSCH overlapping both the first time domain resource and the second time domain resource.

[0246] For example, for the SPS PDSCH corresponding to one SPS configuration (not limited thereto, and it can also be for any SPS configuration): when there is no invalid time domain resource type, the terminal device does not expect the SPS PDSCH / repetition to overlap both the first time domain resource and the second time domain resource, or the terminal device does not receive the SPS PDSCH / repetition overlapping both the first time domain resource and the second time domain resource.

[0247] The following further illustrates the case of transport block size (TBS).

[0248] In some embodiments, the terminal device determines the TBS based on the frequency domain resource within the allocated second frequency domain resource or determines the TBS based on the allocated frequency domain resource.

[0249] In some embodiments, the determination of the transport block size according to the frequency domain resource within the second frequency domain resource or the allocated frequency domain resource is related to the valid time domain resource type and / or the invalid time domain resource type and / or the second reference SPS PDSCH (of the second reference repetition) and / or the time domain resource indicated by the activation DCI and / or the number of repetitions overlapping the first time domain resource and / or the number of repetitions overlapping the second time domain resource.

[0250] In some embodiments, the TBS is determined according to the frequency domain resources within the second frequency domain resources for the SPS PDSCH corresponding to one SPS configuration; or the TBS is determined according to the allocated frequency domain resources for the SPS PDSCH corresponding to one SPS configuration.

[0251] In some embodiments, the TBS is determined according to the frequency domain resources within the second frequency domain resources for the SPS PDSCH corresponding to at least one SPS configuration.

[0252] For one SPS PDSCH overlapping with the first time domain resources, the terminal device determines the transport block size (TBS) according to the frequency domain resources within the allocated second frequency domain resources (e.g., according to the number of corresponding PRBs); for one SPS PDSCH overlapping with the second time domain resources, the terminal device determines the TBS according to the allocated frequency domain resources (e.g., according to the number of corresponding PRBs); or,

[0253] For one SPS PDSCH overlapping with the first time domain resources and one SPS PDSCH overlapping with the second time domain resources, the terminal device determines the TBS according to the allocated frequency domain resources.

[0254] In some embodiments, the TBS is determined according to the frequency domain resources within the second frequency domain resources for the SPS PDSCH corresponding to one SPS configuration; or the TBS is determined according to the allocated frequency domain resources for the SPS PDSCH corresponding to one SPS configuration.

[0255] When the first time domain resources are invalid time domain resource types, the terminal device determines the TBS according to the allocated frequency domain resources; and / or,

[0256] When the second time domain resources are invalid time domain resource types, the terminal device determines the TBS according to the frequency domain resources within the allocated second frequency domain resources or the allocated frequency domain resources.

[0257] In some embodiments, when there is no invalid time domain resource type,

[0258] The terminal device determines the TBS according to the frequency domain resources within the allocated second frequency domain resources or the allocated frequency domain resources (the determined TBS is applied to the SPS PDSCH overlapping with the first time domain resources and the SPS PDSCH overlapping with the second time domain resources); or,

[0259] The terminal device determines the TBS based on a second reference SPS PDSCH (e.g., the first SPS PDSCH associated with the activation DCI or the SPS PDSCH corresponding to slot n+k0) (the determined TBS is applied to the SPS PDSCH overlapping with the first time domain resources and the SPS PDSCH overlapping with the second time domain resources); or,

[0260] For the SPS PDSCH overlapping with the first time domain resource, the terminal device determines the TBS according to the frequency domain resource within the allocated second frequency domain resource, and for the SPS PDSCH overlapping with the second time domain resource, the terminal device determines the TBS according to the allocated frequency domain resource.

[0261] In some embodiments, if the second reference SPS PDSCH overlaps with the first time domain resource, the terminal device determines the TBS according to the frequency domain resource within the allocated second frequency domain resource; if the second reference SPS PDSCH overlaps with the second time domain resource, the terminal device determines the TBS according to the allocated frequency domain resource.

[0262] For example, the second reference SPS PDSCH is the first SPS PDSCH associated with the activation DCI or the SPS PDSCH corresponding to slot n+k0.

[0263] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the second reference SPS PDSCH to (only) overlap with the first time domain resource or (only) overlap with the second time domain resource,

[0264] Or, if the corresponding reference repetition (e.g., the first / first-time repetition) of the second reference SPS PDSCH overlaps with the first time domain resource, the terminal device considers the second reference SPS PDSCH to overlap with the first time domain resource,

[0265] Or, if the corresponding reference repetition (e.g., the first / first-time repetition) of the second reference SPS PDSCH overlaps with the second time domain resource, the terminal device considers the second reference SPS PDSCH to overlap with the second time domain resource.

[0266] In some embodiments, in the case of repetition,

[0267] If the second reference repetition of the second reference SPS PDSCH overlaps with the first time domain resource, the terminal device determines the TBS according to the frequency domain resource within the allocated second frequency domain resource;

[0268] If the second reference repetition of the second reference SPS PDSCH overlaps with the second time domain resource, the terminal device determines the TBS according to the allocated frequency domain resource.

[0269] For example, the second reference repetition is the first / first-time repetition, or the second reference repetition is the repetition located in the first time slot (of the SPS PDSCH corresponding to the first time slot).

[0270] In some embodiments, the second reference repetition is the same as the first reference repetition. For example, when the second reference SPS PDSCH is the same as the first reference SPS PDSCH, both are for different SPS PDSCHs, and if both also correspond to the same repetition (e.g., the first repetition), then both are the same.

[0271] In some embodiments, the second reference repetition is different from the first reference repetition. For example, when the second reference SPS PDSCH is different from the first reference SPS PDSCH, both are for different SPS PDSCHs, and thus are different.

[0272] In some embodiments, in the case of repetition, the SPS PDSCH that overlaps with the first time domain resource or the second time domain resource refers to the SPS PDSCH whose corresponding third reference repetition (e.g., the first / first-time repetition) overlaps with the first time domain resource or the second time domain resource, or the SPS PDSCH whose corresponding any repetition overlaps with the first time domain resource or the second time domain resource.

[0273] For example, for different SPS PDSCHs in different periods, the TBS is determined according to the corresponding third reference repetition, respectively. For example, if the third reference repetition overlaps with the first time domain resource, the TBS is determined according to the frequency domain resource within the allocated second frequency domain resource; if it overlaps with the second time domain resource, the TBS is determined according to the allocated frequency domain resource.

[0274] In some embodiments, whether the terminal device determines the TBS according to the frequency domain resource within the allocated second frequency domain resource or according to the allocated frequency domain resource is related to the third information (carried by the higher layer signaling or the corresponding activation DCI).

[0275] For example, the third information is used to indicate that the terminal device adopts one of the above methods, including indicating whether to determine the TBS according to the frequency domain resource within the allocated second frequency domain resource or according to the allocated frequency domain resource.

[0276] In some embodiments, if the time domain resource indicated by the activation DCI only overlaps with the first time domain resource, the terminal device determines the TBS according to the frequency domain resource within the allocated second frequency domain resource; and / or

[0277] If the time domain resource indicated by the activation DCI only overlaps with the second time domain resource, the terminal device determines the TBS according to the allocated frequency domain resource.

[0278] In some embodiments, for the corresponding SPS PDSCH of one SPS configuration:

[0279] The first time domain resource is not an invalid time domain resource type, and the terminal device determines the TBS according to the frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource based on a second specific value (predefined / configured).

[0280] For example, when the ratio of the frequency domain resource within the allocated second frequency domain resource to the allocated frequency domain resource is less than or not greater than the second specific value, the terminal device determines the TBS according to the frequency domain resource within the allocated second frequency domain resource, otherwise, the TBS is determined according to the allocated frequency domain resource.

[0281] 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.

[0282] 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.

[0283] As can be seen from the above embodiments, the terminal device receives the SPS PDSCH corresponding to at least one SPS configuration (SPS-Config), and receives the SPS PDSCH at the appropriate time-frequency position according to the first / second time domain resource. Thus, when the network device works in the full duplex mode, the terminal device can receive the SPS PDSCH and avoid using the resource for uplink, reducing the interference to the resource for uplink, thereby improving the capacity and coverage of uplink transmission, reducing the latency of uplink transmission, and improving the resource allocation flexibility and resource utilization.

[0284] Embodiments of the second aspect

[0285] The embodiments of the present application provide a PDSCH transmission method, which is described from the network device side. The same content as the embodiments of the first aspect will not be described again.

[0286] FIG. 7 is a schematic diagram of a PDSCH transmission method according to an embodiment of the present application. As shown in FIG. 7, the method includes the following steps.

[0287] 701. The network device transmits one or more SPS configurations and information for configuring at least 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; and

[0288] 702, the network device sends a SPS PDSCH corresponding to at least one SPS configuration (SPS-Config) in the one or more SPS configurations;

[0289] wherein, for a SPS PDSCH corresponding to one (a) SPS configuration (or for one SPS configuration) in the at least one SPS configuration: no SPS PDSCH overlapping (or in) the first time domain resource is sent (dropped), or no SPS PDSCH overlapping (or in) the second time domain resource is sent, or for a SPS PDSCH overlapping the first time domain resource, only frequency domain resources within the second frequency domain resource are valid.

[0290] It is worth noting that the above FIG. 7 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 based on the above description, and the present application is not limited to the above FIG. 7.

[0291] In some embodiments, the one or more SPS configurations and / or the at least one SPS configuration includes an SPS configuration for unicast and / or an SPS configuration for multicast.

[0292] In some embodiments, for a SPS PDSCH corresponding to the one SPS configuration (or for one SPS configuration):

[0293] When the first time domain resource is an invalid time domain resource type (or, when (only) the second time domain resource is a valid time domain resource type), no SPS PDSCH overlapping the first time domain resource is sent (dropped); and / or,

[0294] When the second time domain resource is an invalid time domain resource type (or, when (only) the first time domain resource is a valid time domain resource type), no SPS PDSCH overlapping the second time domain resource is sent; and / or,

[0295] When the first time domain resource is not an invalid time domain resource type, for a SPS PDSCH overlapping the first time domain resource, only frequency domain resources within the second frequency domain resource are valid.

[0296] In some embodiments, the first time domain resource is not the invalid time domain resource type includes: not having the invalid time domain resource type (neither the first time domain resource nor the second time domain resource is the invalid time domain resource type, or, both the first time domain resource and the second time domain resource are valid time domain resources), and / or, the second time domain resource is the invalid time domain resource type.

[0297] In some embodiments, after excluding the SPS PDSCHs overlapping with the invalid time domain resource type (processing / resolving the overlapping with the invalid time domain resource), and / or, after excluding the SPS PDSCHs overlapping with the time domain resource indicated as uplink (processing / resolving the overlapping with the time domain resource indicated as uplink), and / or, after excluding the SPS PDSCHs not having the valid frequency domain resource or the ratio of the valid frequency domain resource to the allocated frequency domain resource is less than or not greater than the first specific value (predefined / configured) (processing / resolving the SPS PDSCHs not having the valid frequency domain resource or the ratio of the valid frequency domain resource to the allocated frequency domain resource is less than or not greater than the first specific value), and / or, after excluding the SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource (processing the overlapping with both the first time domain resource and the second time domain resource), and / or, after excluding the SPS PDSCHs overlapping with the inactive period of cell DTX (processing / resolving the overlapping with the inactive period of cell DTX), one or more PDSCHs are selected and transmitted from the more than one SPS PDSCHs (if any) in a slot.

[0298] In some embodiments, selecting and transmitting one or more SPS PDSCHs from the more than one SPS PDSCHs includes:

[0299] Step 0: set a first parameter = 0; wherein the first parameter is the number of selected PDSCHs, and a first set is the set of the more than one SPS PDSCHs;

[0300] Step 1: transmit the PDSCH (the PDSCH is designated as the survivor PDSCH) with the lowest SPS configuration index in the first set, and the first parameter is increased by 1;

[0301] Step 2: exclude the PDSCH (the survivor PDSCH) in the step 1 and the PDSCH(s) even partially overlapping with the PDSCH from the first set;

[0302] Step 3: Repeat steps 1 and 2 until the first set is empty or the first parameter equals the number of PDSCHs in one slot supported by the terminal device.

[0303] In some embodiments, each of the plurality of SPS PDSCHs respectively corresponds to a different SPS configuration (e.g., any 2 are different) of the at least one SPS configuration.

[0304] In some embodiments, excluding SPS PDSCHs overlapping with invalid time domain resource types includes:

[0305] For SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration),

[0306] If the first time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with the first time domain resource; if the second time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with the second time domain resource.

[0307] In some embodiments, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink includes:

[0308] For SPS PDSCHs overlapping with the first time domain resource, excluding SPS PDSCHs overlapping with the (first) time domain resource indicated as uplink by the second uplink-downlink configuration (dedicated) or the third uplink-downlink configuration (other), and / or, for SPS PDSCHs overlapping with the second time domain resource, excluding SPS PDSCHs overlapping with the (second) time domain resource indicated as uplink by the first uplink-downlink configuration (common) or the second uplink-downlink configuration.

[0309] In some embodiments, the network device ignores / does not apply the second uplink-downlink configuration for the first time domain resource.

[0310] For example, even if the second uplink-downlink configuration indicates one SBFD symbol as uplink or downlink, the network device does not consider the SBFD symbol as indicated as uplink or downlink, but determines whether to transmit downlink or receive uplink or not to transmit and receive in the SBFD symbol according to other indications or predefined rules.

[0311] In some embodiments, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink includes:

[0312] For SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration),

[0313] if the first time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with the (second) time domain resource indicated as uplink by the first or second uplink-downlink configuration, and / or,

[0314] if the second time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with the (first) time domain resource indicated as uplink by the second or third uplink-downlink configuration, and / or,

[0315] if none of the time domain resources has an invalid time domain resource type:

[0316] for SPS PDSCHs overlapping with the first time domain resource, excluding SPS PDSCHs overlapping with the (first) time domain resource indicated as uplink by the second or third uplink-downlink configuration, and / or, for SPS PDSCHs overlapping with the second time domain resource, excluding SPS PDSCHs overlapping with the (second) time domain resource indicated as uplink by the first or second uplink-downlink configuration.

[0317] In some embodiments, excluding SPS PDSCHs not having a valid frequency domain resource or a ratio of a valid frequency domain resource to an allocated frequency domain resource being less than or not greater than a first specific value comprises:

[0318] for SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration), if the first time domain resource is not an invalid time domain resource type and SPS PDSCHs overlapping with the first time domain resource do not have a valid frequency domain resource or a ratio of a valid frequency domain resource to an allocated frequency domain resource being less than or not greater than a first specific value, excluding the SPS PDSCHs overlapping with the first time domain resource.

[0319] In some embodiments, excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource comprises:

[0320] for SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration), if none of the time domain resources has an invalid time domain resource type, excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource.

[0321] In some embodiments, the plurality of SPS PDSCHs comprises a first SPS PDSCH associated with a corresponding activation DCI and / or a PDSCH without a corresponding PDCCH transmission; or

[0322] The plurality of SPS PDSCHs include PDSCHs without corresponding PDCCH transmissions, the PDSCHs without corresponding PDCCH transmissions include a first SPS PDSCH (and subsequent SPS PDSCHs) associated with a respective activation DCI.

[0323] In some embodiments, 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 time domain resources (e.g., symbols in slot n+k0) indicated by the TDRA field in the first reference SPS PDSCH and / or the respective activation DCI.

[0324] In some embodiments, the first information is used to indicate no invalid time domain resource type and / or is used to indicate with invalid time domain resource type (e.g., at least one of the first time domain resource and the second time domain resource is an invalid time domain resource type);

[0325] The first information is (optionally) present outside of the SPS configuration (e.g., included in PDSCH-Config or PDSCH-ConfigCommon), the first information applies to all or part of the at least one SPS configuration, or the first information is (optionally) present in the SPS configuration, the first information applies to the SPS configuration in which it is present.

[0326] In some embodiments, the first information also applies to other PDSCH scheduling (e.g., DCI scheduling multiple PDSCHs and / or DCI scheduling PDSCH repetition) and / or CSI-RS (e.g., periodic CSI-RS and / or semi-persistent CSI-RS).

[0327] In some embodiments, the second information is used to indicate invalid time domain resource type and / or valid time domain resource type (e.g., the second information is used to indicate that the first time domain resource is an invalid time domain resource type and / or is used to indicate that the second time domain resource is an invalid time domain resource type, or the second information is used to indicate that the first time domain resource is a valid time domain resource type and / or is used to indicate that the second time domain resource is a valid time domain resource type);

[0328] The second information is (optionally) present in the SPS configuration, the second information applies to the SPS configuration in which it is present.

[0329] In some embodiments, determining the invalid time domain resource type and / or the valid time domain resource type based on the first reference SPS PDSCH includes that the valid time domain resource type is the time domain resource type of the first reference SPS PDSCH.

[0330] For example, if the first reference SPS PDSCH overlaps (only) with the first time domain resource, the valid time domain resource type is the first time domain resource, if the first reference SPS PDSCH overlaps (only) with the second time domain resource, the valid time domain resource type is the second time domain resource, or the network device does not expect the first reference SPS PDSCH to overlap with both the first time domain resource and the second time domain resource.

[0331] In some embodiments, in case of repetition, the network device expects all repetitions of the first reference SPS PDSCH to overlap (only) with the first time domain resource or (only) with the second time domain resource, or the valid time domain resource type or the time domain resource type of the first reference SPS PDSCH is the time domain resource type of the first reference repetition (e.g., the first repetition) of the first reference SPS PDSCH.

[0332] For example, if the first reference repetition overlaps (only) with the first time domain resource, the valid time domain resource type is the first time domain resource, if the first reference repetition overlaps (only) with the second time domain resource, the valid time domain resource type is the second time domain resource. The network device does not expect the first reference repetition to overlap with both the first time domain resource and the second time domain resource.

[0333] In some embodiments, determining the invalid time domain resource type and / or the valid time domain resource type based on the time domain resource indicated by the activation DCI comprises:

[0334] If the time domain resource indicated by the activation DCI overlaps (only) with the first time domain resource, the valid time domain resource type is the first time domain resource, and / or the invalid time domain resource type is the second time domain resource;

[0335] If the time domain resource indicated by the activation DCI overlaps (only) with the second time domain resource, the valid time domain resource type is the second time domain resource, and / or the invalid time domain resource type is the first time domain resource.

[0336] In some embodiments, when the first information is (only) used to indicate that there is no invalid time domain resource type:

[0337] The first information and the second information do not exist at the same time (when the first information exists, the second information does not exist, and vice versa); or when the first information and the second information exist at the same time, the first information is not applied to the SPS configuration including the second information, and / or is applied to the SPS configuration not including the second information.

[0338] For example, for one SPS configuration including the second information, the first time domain resource or the second time domain resource is (determined by the network device according to the second information) an invalid time domain resource, and / or,

[0339] For one SPS configuration not including the second information, the first time domain resource and the second time domain resource are not invalid time domain resources (determined by the network device according to the first information).

[0340] In some embodiments, when the first information is not provided (for example, it is assumed that at this time at least one of the first time domain resource and the second time domain resource is an invalid time domain resource type by default) or when the first information indicates an invalid time domain resource type, the second information is included (must be included) in the SPS configuration.

[0341] In some embodiments, for one SPS configuration not including the second information:

[0342] The network device determines the invalid time domain resource type and / or the valid time domain resource type based on the first reference SPS PDSCH or the time domain resource indicated by the activation DCI, or the network device considers that the first time domain resource or the second time domain resource is an invalid time domain resource type.

[0343] In some embodiments, for one SPS PDSCH corresponding to one SPS configuration, the allocated frequency domain resource is indicated by the FDRA field in the corresponding activation DCI.

[0344] For example, when the at least one SPS configuration includes more than one SPS configuration, the activation DCI corresponding to different SPS configurations is different, and the activation DCI includes information for indicating the SPS configuration index.

[0345] In some embodiments, for one SPS PDSCH corresponding to one SPS configuration: when the second time domain resource is an invalid time domain resource type, the network device expects the allocated frequency domain resource to be within the second frequency domain resource.

[0346] In some embodiments, for one SPS PDSCH corresponding to one SPS configuration:

[0347] The first time domain resource is not an invalid time domain resource type,

[0348] The network device does not expect the SPS PDSCH overlapping with the first time domain resource to have a valid frequency domain resource or a ratio of the valid frequency domain resource to the allocated frequency domain resource is less than or not greater than a first specific value, or

[0349] If the SPS PDSCH overlapping with the first time domain resource has no valid frequency domain resource or the ratio of the valid frequency domain resource to the allocated frequency domain resource is less than or not greater than the first specific value, the network device does not send the SPS PDSCH overlapping with the first time domain resource.

[0350] In some embodiments, for a SPS PDSCH corresponding to one SPS configuration:

[0351] When the first time domain resource is an invalid time domain resource type, the network device does not transmit a SPS PDSCH that overlaps with the (first) time domain resource indicated as uplink by the second uplink configuration or the third uplink configuration; and / or,

[0352] When the second time domain resource is an invalid time domain resource type, the network device does not transmit a SPS PDSCH that overlaps with the (second) time domain resource indicated as uplink by the first uplink configuration or the second uplink configuration; and / or,

[0353] When there is no invalid time domain resource type: for a SPS PDSCH that overlaps with the first time domain resource, the network device does not transmit a SPS PDSCH that overlaps with the (first) time domain resource indicated as uplink by the second uplink configuration or the third uplink configuration, and / or, for a SPS PDSCH that overlaps with the second time domain resource, the network device does not transmit a SPS PDSCH that overlaps with the (second) time domain resource indicated as uplink by the first uplink configuration or the second uplink configuration.

[0354] In some embodiments, (for a SPS PDSCH corresponding to one SPS configuration (not limited to this, it is also possible for any SPS configuration: when there is no invalid time domain resource type, not limited to this), the network device does not expect a SPS PDSCH to overlap with both the first time domain resource and the second time domain resource, or the network device does not transmit a SPS PDSCH that overlaps with both the first time domain resource and the second time domain resource.

[0355] In some embodiments, the network device determines the TBS based on the frequency domain resources within the allocated second frequency domain resource or determines the TBS based on the allocated frequency domain resources.

[0356] In some embodiments, (for a SPS PDSCH corresponding to at least one SPS configuration) for one SPS PDSCH that overlaps with the first time domain resource, the network device determines the transport block size (TBS) according to the frequency domain resources within the allocated second frequency domain resource (for example, according to the number of corresponding PRBs), and for one SPS PDSCH that overlaps with the second time domain resource, the network device determines the TBS according to the allocated frequency domain resources (for example, according to the number of corresponding PRBs); or,

[0357] For one SPS PDSCH that overlaps with the first time domain resource and one SPS PDSCH that overlaps with the second time domain resource, the network device determines the TBS according to the allocated frequency domain resources.

[0358] In some embodiments, for a SPS configuration corresponding SPS PDSCH:

[0359] When the first time domain resource is invalid time domain resource type, the network device determines the TBS according to the allocated frequency domain resource; and / or,

[0360] When the second time domain resource is invalid time domain resource type, the network device determines the TBS according to the allocated frequency domain resource within the second frequency domain resource or the allocated frequency domain resource; and / or,

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

[0362] The network device determines the TBS according to the allocated frequency domain resource within the second frequency domain resource or the allocated frequency domain resource (the determined TBS is applied to the SPS PDSCH overlapping with the first time domain resource and the SPS PDSCH overlapping with the second time domain resource); or,

[0363] The network device determines the TBS based on the second reference SPS PDSCH (for example, the first SPS PDSCH associated with the activation DCI or the SPS PDSCH corresponding to slot n+k0) (the determined TBS is applied to the SPS PDSCH overlapping with the first time domain resource and the SPS PDSCH overlapping with the second time domain resource); or,

[0364] For the SPS PDSCH overlapping with the first time domain resource, the network device determines the TBS according to the allocated frequency domain resource within the second frequency domain resource, and for the SPS PDSCH overlapping with the second time domain resource, the network device determines the TBS according to the allocated frequency domain resource.

[0365] In some embodiments, if the second reference SPS PDSCH overlaps with the first time domain resource, the network device determines the TBS according to the allocated frequency domain resource within the second frequency domain resource; if the second reference SPS PDSCH overlaps with the second time domain resource, the network device determines the TBS according to the allocated frequency domain resource.

[0366] In some embodiments, in case of repetition, the network device expects all repetitions of the second reference SPS PDSCH to overlap (only) with the first time-domain resources or (only) with the second time-domain resources, or, if a respective reference repetition (e.g., the first / first-time repetition) of the second reference SPS PDSCH overlaps with the first time-domain resources, the network device considers the second reference SPS PDSCH to overlap with the first time-domain resources, or, if a respective reference repetition (e.g., the first / first-time repetition) of the second reference SPS PDSCH overlaps with the second time-domain resources, the network device considers the second reference SPS PDSCH to overlap with the second time-domain resources.

[0367] In some embodiments, the second reference SPS PDSCH is the same as the first reference SPS PDSCH.

[0368] In some embodiments, the second reference SPS PDSCH is different from the first reference SPS PDSCH.

[0369] In some embodiments, in case of repetition,

[0370] If a second reference repetition (e.g., the first / first-time repetition, the repetition at slot n+k0 of the SPS PDSCH corresponding to slot n+k0) of the second reference SPS PDSCH overlaps with the first time-domain resources, the network device determines the TBS according to the frequency-domain resources within the second frequency-domain resources allocated; if the second reference repetition of the second reference SPS PDSCH overlaps with the second time-domain resources, the network device determines the TBS according to the frequency-domain resources allocated.

[0371] In some embodiments, in case of repetition, the SPS PDSCH overlapping with the first time-domain resources or the second time-domain resources refers to the SPS PDSCH whose respective third reference repetition (e.g., the first / first-time repetition) overlaps with the first time-domain resources or the second time-domain resources, or the SPS PDSCH whose any repetition overlaps with the first time-domain resources or the second time-domain resources.

[0372] In some embodiments, whether the network device determines the TBS according to the frequency-domain resources within the second frequency-domain resources allocated or according to the frequency-domain resources allocated is related to the third information (carried by higher layer signaling or a corresponding activation DCI).

[0373] For example, the third information is used to indicate one of the above methods, including being used to indicate according to the frequency-domain resources within the second frequency-domain resources allocated or according to the frequency-domain resources allocated.

[0374] In some embodiments,

[0375] If the time domain resources indicated by the activation DCI overlap with only the first time domain resources, the network device determines the TBS according to the frequency domain resources within the allocated second frequency domain resources;

[0376] If the time domain resources indicated by the activation DCI overlap with only the second time domain resources, the network device determines the TBS according to the allocated frequency domain resources.

[0377] In some embodiments, for one SPS configuration, a corresponding SPS PDSCH is transmitted:

[0378] The first time domain resources are not invalid time domain resource types, and the network device determines the TBS according to the frequency domain resources within the allocated second frequency domain resources or the allocated frequency domain resources based on a second specific value (predefined / configured).

[0379] For example, when the ratio of the frequency domain resources within the allocated second frequency domain resources to the allocated frequency domain resources is less than or not greater than a second specific value, the network device determines the TBS according to the frequency domain resources within the allocated second frequency domain resources, otherwise, the network device determines the TBS according to the allocated frequency domain resources.

[0380] The above only describes each step or process 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.

[0381] 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.

[0382] As can be seen from the above embodiments, the network device transmits a SPS PDSCH corresponding to at least one SPS configuration (SPS-Config), and transmits the SPS PDSCH at an appropriate time-frequency location according to the first / second time domain resources. In this way, the network device can transmit the SPS PDSCH when working in the full duplex mode, and avoid using resources for uplink, reduce interference to resources for uplink, thereby improving the capacity and coverage of uplink transmission, reducing the latency of uplink transmission, and improving the resource allocation flexibility and resource utilization.

[0383] Embodiments of the third aspect

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

[0385] FIG. 8 is a schematic diagram of a PDSCH 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 thereof can be referred to the embodiment of the first aspect, and the same content will not be repeated. As shown in FIG. 8, the PDSCH receiving apparatus 800 includes a receiver 801, and further includes a processor 802 and a transmitter 803.

[0386] The receiver 801 receives one or more SPS configurations and information used for configuring at least 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 receives an SPS PDSCH corresponding to at least one SPS configuration in the one or more SPS configurations;

[0387] For the SPS PDSCH corresponding to one SPS configuration (or for one SPS configuration) in the at least one SPS configuration: SPS PDSCHs overlapping with the first time domain resource (or SPS PDSCHs in the first time domain resource) are not received (dropped), or SPS PDSCHs overlapping with the second time domain resource (or SPS PDSCHs in the second time domain resource) are not received, or for SPS PDSCHs overlapping with the first time domain resource, only frequency domain resources within the second frequency domain resource are valid.

[0388] In some embodiments, the one or more SPS configurations and / or the at least one SPS configuration include SPS configurations for unicast and / or SPS configurations for multicast.

[0389] In some embodiments, for the SPS PDSCH corresponding to the one SPS configuration (or for one SPS configuration):

[0390] When the first time domain resource is an invalid time domain resource type (or when only the second time domain resource is a valid time domain resource type), SPS PDSCHs overlapping with the first time domain resource are not received (dropped); and / or,

[0391] When the second time domain resource is an invalid time domain resource type (or when only the first time domain resource is a valid time domain resource type), SPS PDSCHs overlapping with the second time domain resource are not received; and / or,

[0392] When the first time domain resource is not the invalid time domain resource type, the allocated (only) the second frequency domain resource within the second frequency domain resource is valid for the SPS PDSCH overlapping with the first time domain resource.

[0393] In some embodiments, the first time domain resource is not the invalid time domain resource type includes: not having the invalid time domain resource type (neither the first time domain resource nor the second time domain resource is the invalid time domain resource type, or, both the first time domain resource and the second time domain resource are valid time domain resources), and / or, the second time domain resource is the invalid time domain resource type.

[0394] In some embodiments, after excluding the SPS PDSCH overlapping with the invalid time domain resource type (processing / resolving the overlapping with the invalid time domain resource), and / or, after excluding the SPS PDSCH overlapping with the time domain resource indicated as uplink (processing / resolving the overlapping with the time domain resource indicated as uplink), and / or, after excluding the SPS PDSCH not having the valid frequency domain resource or the ratio of the valid frequency domain resource to the allocated frequency domain resource is less than or not greater than the first specific value (predefined / configured) (processing / resolving the SPS PDSCH not having the valid frequency domain resource or the ratio of the valid frequency domain resource to the allocated frequency domain resource is less than or not greater than the first specific value), and / or, after excluding the SPS PDSCH overlapping with both the first time domain resource and the second time domain resource (processing the overlapping with both the first time domain resource and the second time domain resource), and / or, after excluding the SPS PDSCH overlapping with the inactive period of cell DTX (processing / resolving the overlapping with the inactive period of cell DTX), one or more PDSCHs are selected and received from the more than one SPS PDSCH (if any) in one slot.

[0395] In some embodiments, each of the more than one SPS PDSCH respectively corresponds to a different SPS configuration (any 2 are different) in the at least one SPS configuration.

[0396] In some embodiments, excluding the SPS PDSCH overlapping with the invalid time domain resource type includes:

[0397] for the SPS PDSCH corresponding to one SPS configuration (or for one SPS configuration),

[0398] if the first time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with the first time domain resource; and / or, if the second time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with the second time domain resource.

[0399] In some embodiments, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink, comprises:

[0400] For SPS PDSCHs overlapping with the first time domain resource, excluding SPS PDSCHs overlapping with (first) time domain resources indicated as uplink by the second or third uplink-downlink configuration, and / or, for SPS PDSCHs overlapping with the second time domain resource, excluding SPS PDSCHs overlapping with (second) time domain resources indicated as uplink by the first or second uplink-downlink configuration.

[0401] In some embodiments, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink, comprises:

[0402] For SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration),

[0403] if the first time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with (second) time domain resources indicated as uplink by the first or second uplink-downlink configuration, and / or,

[0404] if the second time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with (first) time domain resources indicated as uplink by the second or third uplink-downlink configuration, and / or,

[0405] if there is no invalid time domain resource type:

[0406] For SPS PDSCHs overlapping with the first time domain resource, excluding SPS PDSCHs overlapping with (first) time domain resources indicated as uplink by the second or third uplink-downlink configuration, and / or, for SPS PDSCHs overlapping with the second time domain resource, excluding SPS PDSCHs overlapping with (second) time domain resources indicated as uplink by the first or second uplink-downlink configuration.

[0407] In some embodiments, excluding SPS PDSCHs not having valid frequency domain resources or having a ratio of valid frequency domain resources to allocated frequency domain resources less than or not greater than a first specific value, comprises:

[0408] For SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration), exclude SPS PDSCHs overlapping with the first time domain resource if the first time domain resource is not an invalid time domain resource type, and the SPS PDSCHs overlapping with the first time domain resource do not have valid frequency domain resources or a ratio of valid frequency domain resources to allocated frequency domain resources is less than or not greater than a first specific value.

[0409] In some embodiments, excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource comprises:

[0410] For SPS PDSCHs corresponding to one SPS configuration (or for one SPS configuration), exclude SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource if the SPS PDSCHs do not have an invalid time domain resource type.

[0411] In some embodiments, the plurality of SPS PDSCHs comprises a first SPS PDSCH associated with a corresponding activation DCI and / or a PDSCH without a corresponding PDCCH transmission; or

[0412] The plurality of SPS PDSCHs comprises a PDSCH without a corresponding PDCCH transmission, the PDSCH without a corresponding PDCCH transmission comprising a first SPS PDSCH (and subsequent SPS PDSCHs) associated with a corresponding activation DCI.

[0413] In some embodiments, the processor 802 determines the TBS based on frequency domain resources within the allocated second frequency domain resources or determines the TBS based on allocated frequency domain resources.

[0414] In some embodiments, for one SPS PDSCH overlapping with the first time domain resource, the processor 802 determines a transport block size (TBS) according to frequency domain resources within the allocated second frequency domain resources, and for one SPS PDSCH overlapping with the second time domain resource, the processor 802 determines the TBS according to allocated frequency domain resources; or,

[0415] For one SPS PDSCH overlapping with the first time domain resource and one SPS PDSCH overlapping with the second time domain resource, the processor 802 determines the TBS according to allocated frequency domain resources.

[0416] In some embodiments, for SPS PDSCHs corresponding to one SPS configuration:

[0417] when the first time domain resource is an invalid time domain resource type, the processor determines the TBS according to the allocated frequency domain resource; and / or,

[0418] when the second time domain resource is an invalid time domain resource type, the processor determines the TBS according to the allocated frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource; and / or,

[0419] when there is no invalid time domain resource type,

[0420] the processor determines the TBS according to the allocated frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource (the determined TBS is applied to the SPS PDSCH overlapping with the first time domain resource and the SPS PDSCH overlapping with the second time domain resource); or,

[0421] the processor determines the TBS based on a second reference SPS PDSCH (e.g., the first SPS PDSCH associated with the activation DCI or the SPS PDSCH corresponding to slot n+k0) (the determined TBS is applied to the SPS PDSCH overlapping with the first time domain resource and the SPS PDSCH overlapping with the second time domain resource); or,

[0422] for the SPS PDSCH overlapping with the first time domain resource, the processor determines the TBS according to the allocated frequency domain resource within the allocated second frequency domain resource, and for the SPS PDSCH overlapping with the second time domain resource, the processor determines the TBS according to the allocated frequency domain resource.

[0423] In some embodiments, if the second reference SPS PDSCH overlaps with the first time domain resource, the processor determines the TBS according to the allocated frequency domain resource within the allocated second frequency domain resource; if the second reference SPS PDSCH overlaps with the second time domain resource, the processor determines the TBS according to the allocated frequency domain resource.

[0424] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the second reference SPS PDSCH to (only) overlap with the first time domain resource or (only) overlap with the second time domain resource, or if the corresponding reference repetition (e.g., the first / first-time repetition) of the second reference SPS PDSCH overlaps with the first time domain resource, the second reference SPS PDSCH is considered to overlap with the first time domain resource, or if the corresponding reference repetition (e.g., the first / first-time repetition) of the second reference SPS PDSCH overlaps with the second time domain resource, the second reference SPS PDSCH is considered to overlap with the second time domain resource.

[0425] In some embodiments, in case of repetition,

[0426] If the second reference repetition (e.g., the first / first-time repetition) of the second reference SPS PDSCH (e.g., the SPS PDSCH located at slot n+k0) overlaps with the first time domain resource, the processor determines the TBS according to the frequency domain resource within the allocated second frequency domain resource; if the second reference repetition of the second reference SPS PDSCH overlaps with the second time domain resource, the processor determines the TBS according to the allocated frequency domain resource.

[0427] In some embodiments, in case of repetition, the SPS PDSCH overlapping with the first time domain resource or the second time domain resource refers to the SPS PDSCH whose corresponding third reference repetition (e.g., the first / first-time repetition) overlaps with the first time domain resource or the second time domain resource, or the SPS PDSCH whose any repetition overlaps with the first time domain resource or the second time domain resource.

[0428] In some embodiments, whether the processor determines the TBS according to the frequency domain resource within the allocated second frequency domain resource or according to the allocated frequency domain resource is related to the third information (carried by the higher layer signaling or the corresponding activation DCI);

[0429] and / or

[0430] If the time domain resource indicated by the activation DCI (only) overlaps with the first time domain resource, the processor determines the TBS according to the frequency domain resource within the allocated second frequency domain resource; if the time domain resource indicated by the activation DCI (only) overlaps with the second time domain resource, the processor determines the TBS according to the allocated frequency domain resource.

[0431] and / or

[0432] For the corresponding SPS PDSCH of one SPS configuration: the first time domain resource is not an invalid time domain resource type, the processor determines to determine the TBS according to the frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource based on the second specific value (predefined / configured).

[0433] 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 PDSCH receiving 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.

[0434] In addition, for the sake of simplicity, only the connection relationship or signal direction between each component or module 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 adopted. Each component or module described above can be implemented by hardware facilities such as processor, memory, transmitter, receiver, etc., and the implementation of the present application is not limited thereto.

[0435] The above embodiments are only exemplarily described, 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.

[0436] As can be seen from the above embodiments, the terminal device receives the SPS PDSCH corresponding to at least one SPS configuration (SPS-Config), and receives the SPS PDSCH at an appropriate time-frequency location according to the first / second time-domain resource. In this way, when the network device works in the full-duplex mode, the terminal device can receive the SPS PDSCH, avoid using the resource for uplink, reduce the interference to the resource for uplink, thereby improving the capacity and coverage of uplink transmission, reducing the latency of uplink transmission, and improving the resource allocation flexibility and resource utilization.

[0437] Embodiments of the fourth aspect

[0438] The embodiments of the present application provide a PDSCH 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 described again.

[0439] FIG. 9 is a schematic diagram of a PDSCH 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 embodiments of the first and second aspects, and the same content will not be described again. As shown in FIG. 9, the PDSCH sending device 900 includes a transmitter 901, and can further include a processor 902 and a receiver 903.

[0440] The transmitter 901 transmits one or more SPS configurations and information for configuring at least the first time-domain resource and / or the second time-domain resource; wherein the first frequency-domain resource is used for uplink and the second frequency-domain resource is used for downlink in the first time-domain resource, and the second time-domain resource is outside the first time-domain resource; and transmits the SPS PDSCH corresponding to at least one SPS configuration (SPS-Config) in the one or more SPS configurations;

[0441] For one (a) SPS configuration corresponding to the at least one SPS configuration, no SPS PDSCH overlapping with the first time domain resource (or SPS PDSCH in the first time domain resource) is transmitted (or dropped), or no SPS PDSCH overlapping with the second time domain resource (or SPS PDSCH in the second time domain resource) is transmitted, or for SPS PDSCH overlapping with the first time domain resource, only frequency domain resources within the second frequency domain resource are valid.

[0442] 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 PDSCH sending device 900 of the embodiments of the present application can also include other components or modules. For specific content of these components or modules, please refer to the related technology.

[0443] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 9, 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.

[0444] The above embodiments are only exemplarily described, 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.

[0445] As can be seen from the above embodiments, the network device transmits SPS PDSCH corresponding to at least one SPS configuration (SPS-Config), and transmits the SPS PDSCH at an appropriate time-frequency location according to the first / second time domain resource. Therefore, the network device can transmit SPS PDSCH when working in full duplex mode, avoid using resources for uplink, reduce interference on resources for uplink, thereby improving the capacity and coverage of uplink transmission, reducing the latency of uplink transmission, and improving the resource allocation flexibility and resource utilization.

[0446] Embodiments of the fifth aspect

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

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

[0449] a network device, which transmits one or more SPS configurations and information at least 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 out of the first time domain resource; and transmits an SPS PDSCH corresponding to at least one SPS configuration in the one or more SPS configurations;

[0450] a terminal device, which receives the one or more SPS configurations and the information at least for configuring the first time domain resource and / or the second time domain resource; and receives an SPS PDSCH corresponding to at least one SPS configuration in the one or more SPS configurations;

[0451] wherein, for the SPS PDSCH corresponding to one SPS configuration in the at least one SPS configuration (or for one SPS configuration): SPS PDSCHs overlapping with the first time domain resource (or SPS PDSCHs in the first time domain resource) are not received (or dropped), or SPS PDSCHs overlapping with the second time domain resource (or SPS PDSCHs in the second time domain resource) are not received, or for SPS PDSCHs overlapping with the first time domain resource, only frequency domain resources within the second frequency domain resource are valid.

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

[0453] FIG. 10 is a schematic diagram of a network device according to an embodiment of the present application. As shown in FIG. 10, the network device 1000 can include a processor 1010 (such as a central processing unit CPU) and a memory 1020; the memory 1020 is coupled to the processor 1010. The memory 1020 can store various data; in addition, it also stores a program 1030 for information processing, and executes the program 1030 under the control of the processor 1010.

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

[0455] In addition, as shown in FIG. 10, the network device 1000 can also include a transceiver 1040, an antenna 1050, 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 1000 does not necessarily include all the components shown in FIG. 10; in addition, the network device 1000 can also include components not shown in FIG. 10, which can be referred to the prior art.

[0456] The embodiment of the present application further provides a terminal device, but the present application is not limited thereto, and other devices can also be used.

[0457] Fig. 11 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Fig. 11, the terminal device 1100 can include a processor 1110 and a memory 1120. The memory 1120 stores data and programs and is coupled to the processor 1110. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunications functions or other functions.

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

[0459] As shown in Fig. 11, the terminal device 1100 can further include a communication module 1130, an input device 1140, a display 1150, and a power supply 1160. 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 1100 does not necessarily include all the components shown in Fig. 11, and the above components are not essential. In addition, the terminal device 1100 can also include components not shown in Fig. 11, and reference can be made to the prior art.

[0460] The embodiment of the present application further provides 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.

[0461] The embodiment of the present application further provides 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.

[0462] The embodiment of the present application further provides 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.

[0463] The embodiment of the present application further provides 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.

[0464] The apparatuses and methods described above can be implemented by hardware, or by software and hardware in combination. The present application relates to a computer-readable program that, when executed by a logic component, causes the logic component to implement the above-described apparatuses or constituent components, or causes the logic component 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 present 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.

[0465] The methods / apparatuses described in connection with the embodiments of the present 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 each software module of a computer program flow, or to each hardware module. The software modules can correspond to each step 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).

[0466] 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 a processor, so that the processor can read information from, and write information to, the storage medium; or the storage medium can be integral to the processor. The processor and the storage medium can be located in an ASIC. The software modules can be stored in the memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if the device (e.g., the 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.

[0467] 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 present 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.

[0468] 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.

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

[0470] 1. A PDSCH receiving method, comprising:

[0471] A terminal device receives one or more SPS configurations and information at least 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

[0472] Receiving a SPS PDSCH corresponding to at least one SPS configuration (SPS-Config) in the one or more SPS configurations;

[0473] Wherein for a SPS PDSCH corresponding to one / a SPS configuration in the at least one SPS configuration (or for one SPS configuration): not receiving (dropping) a SPS PDSCH overlapping with the first time domain resource (or a SPS PDSCH in the first time domain resource), or not receiving a SPS PDSCH overlapping with the second time domain resource (or a SPS PDSCH in the second time domain resource), or for a SPS PDSCH overlapping with the first time domain resource, only frequency domain resources within the second frequency domain resource are valid.

[0474] 2. A PDSCH transmitting method, comprising:

[0475] A network device transmits one or more SPS configurations and information at least 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

[0476] Transmitting a SPS PDSCH corresponding to at least one SPS configuration (SPS-Config) in the one or more SPS configurations;

[0477] Among them, for one (a) SPS configuration corresponding to the SPS PDSCH in the at least one SPS configuration (or for one SPS configuration): do not send (drop) the SPS PDSCH overlapping with the first time domain resource (or the SPS PDSCH in the first time domain resource), or do not send the SPS PDSCH overlapping with the second time domain resource (or the SPS PDSCH in the second time domain resource), or for the SPS PDSCH overlapping with the first time domain resource, the frequency domain resource allocated (only) within the second frequency domain resource is valid.

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

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

[0480] 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 PDSCH receiving method of clause 1.

[0481] 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 PDSCH transmitting method of clause 2.

Claims

1. A PDSCH receiving apparatus, comprising: a receiver configured to receive one or more SPS configurations and information at least 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 receive a SPS PDSCH corresponding to at least one SPS configuration of the one or more SPS configurations; wherein, for a SPS PDSCH corresponding to one SPS configuration of the at least one SPS configuration: no SPS PDSCH overlapping with the first time domain resource is received, or no SPS PDSCH overlapping with the second time domain resource is received, or for a SPS PDSCH overlapping with the first time domain resource, frequency domain resources within the second frequency domain resource allocated are valid.

2. The apparatus of claim 1, wherein, the one or more SPS configurations and / or the at least one SPS configuration comprises SPS configurations for unicast and / or SPS configurations for multicast.

3. The apparatus of claim 1, wherein, for a SPS PDSCH corresponding to the one SPS configuration: when the first time domain resource is a type of invalid time domain resource, no SPS PDSCH overlapping with the first time domain resource is received; and / or, when the second time domain resource is a type of invalid time domain resource, no SPS PDSCH overlapping with the second time domain resource is received; and / or, when the first time domain resource is not a type of invalid time domain resource, for a SPS PDSCH overlapping with the first time domain resource, frequency domain resources within the second frequency domain resource allocated are valid; wherein the first time domain resource is not a type of invalid time domain resource comprises: not having a type of invalid time domain resource, and / or the second time domain resource is a type of invalid time domain resource. 4.The apparatus of claim 1, wherein, after excluding SPS PDSCHs overlapping with a type of invalid time domain resource, and / or after excluding SPS PDSCHs overlapping with a time domain resource indicated as uplink, and / or after excluding SPS PDSCHs not having valid frequency domain resources or a ratio of valid frequency domain resources to allocated frequency domain resources being less than or not greater than a first specific value, and / or after excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource, and / or after excluding SPS PDSCHs overlapping with a non-activation period of cell DTX, one or more PDSCHs are selected and received from more than one SPS PDSCHs in a time slot.

5. The apparatus of claim 4, wherein, each of the more than one SPS PDSCHs respectively corresponds to a different SPS configuration of the at least one SPS configuration.

6. The apparatus of claim 4, wherein, excluding SPS PDSCHs overlapping with a type of invalid time domain resource comprises: for a SPS PDSCH corresponding to one SPS configuration, if the first time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with the first time domain resource; 7. The apparatus of claim 4, wherein, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink, including: for SPS PDSCHs overlapping with the first time domain resource, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink by the second or third uplink-downlink configuration, and / or, for SPS PDSCHs overlapping with the second time domain resource, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink by the first or second uplink-downlink configuration.

8. The apparatus of claim 4, wherein, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink, including: for SPS PDSCHs corresponding to one SPS configuration, if the first time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink by the first or second uplink-downlink configuration, and / or, if the second time domain resource is an invalid time domain resource type, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink by the second or third uplink-downlink configuration, and / or, if there is no invalid time domain resource type: for SPS PDSCHs overlapping with the first time domain resource, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink by the second or third uplink-downlink configuration, and / or, for SPS PDSCHs overlapping with the second time domain resource, excluding SPS PDSCHs overlapping with time domain resources indicated as uplink by the first or second uplink-downlink configuration.

9. The apparatus of claim 4, wherein, excluding SPS PDSCHs without valid frequency domain resources or with a ratio of valid frequency domain resources to allocated frequency domain resources less than or not greater than a first specific value, including: for SPS PDSCHs corresponding to one SPS configuration, if the first time domain resource is not an invalid time domain resource type, and SPS PDSCHs overlapping with the first time domain resource do not have valid frequency domain resources or have a ratio of valid frequency domain resources to allocated frequency domain resources less than or not greater than a first specific value, excluding SPS PDSCHs overlapping with the first time domain resource. excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource, including:

10. The apparatus of claim 4, wherein, for SPS PDSCHs corresponding to one SPS configuration, if there is no invalid time domain resource type, excluding SPS PDSCHs overlapping with both the first time domain resource and the second time domain resource. the plurality of SPS PDSCHs include a first SPS PDSCH associated with a corresponding activation DCI and / or a PDSCH without a corresponding PDCCH transmission; or 11. The apparatus of claim 4, wherein, the plurality of SPS PDSCHs include a first SPS PDSCH associated with a corresponding activation DCI and / or a PDSCH without a corresponding PDCCH transmission; or The plurality of SPS PDSCHs include a PDSCH without a corresponding PDCCH transmission, the PDSCH without the corresponding PDCCH transmission including a first SPS PDSCH associated with a respective activation DCI.

12. The apparatus of claim 1, wherein, The apparatus further includes: The processor determines a transport block size based on a frequency domain resource within the allocated second frequency domain resource or based on the allocated frequency domain resource.

13. The apparatus of claim 12, wherein, For one SPS PDSCH overlapping the first time domain resource, the processor determines a transport block size based on a frequency domain resource within the allocated second frequency domain resource, and for one SPS PDSCH overlapping the second time domain resource, the processor determines a TBS based on the allocated frequency domain resource; or, For one SPS PDSCH overlapping the first time domain resource and one SPS PDSCH overlapping the second time domain resource, the processor determines a transport block size based on the allocated frequency domain resource.

14. The apparatus of claim 12, wherein, For one SPS PDSCH corresponding to the SPS configuration: When the first time domain resource is an invalid time domain resource type, the processor determines a transport block size based on the allocated frequency domain resource; and / or, When the second time domain resource is an invalid time domain resource type, the processor determines a transport block size based on a frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource; and / or, When there is no invalid time domain resource type, the processor determines a transport block size based on a frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource; or, the processor determines a transport block size based on a second reference SPS PDSCH; or, For one SPS PDSCH overlapping the first time domain resource, the processor determines a transport block size based on a frequency domain resource within the allocated second frequency domain resource, and for one SPS PDSCH overlapping the second time domain resource, the processor determines a transport block size based on the allocated frequency domain resource.

15. The apparatus of claim 14, wherein, If the second reference SPS PDSCH overlaps the first time domain resource, the processor determines a transport block size based on a frequency domain resource within the allocated second frequency domain resource, and if the second reference SPS PDSCH overlaps the second time domain resource, the processor determines a transport block size based on the allocated frequency domain resource.

16. The apparatus of claim 14, wherein, In case of repetition, If a second reference repetition of the second reference SPS PDSCH overlaps the first time domain resource, the processor determines a transport block size based on a frequency domain resource within the allocated second frequency domain resource, and if the second reference repetition of the second reference SPS PDSCH overlaps the second time domain resource, the processor determines a transport block size based on the allocated frequency domain resource.

17. The apparatus of claim 14, wherein, In the case of repetition, the SPS PDSCH overlapping with the first time domain resource or the second time domain resource refers to the SPS PDSCH whose corresponding third reference repetition overlaps with the first time domain resource or the second time domain resource, or the SPS PDSCH whose any repetition overlaps with the first time domain resource or the second time domain resource.

18. The apparatus of claim 12, wherein, The processor determines the transport block size according to the frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource in relation to the third information; And / or If the time domain resource indicated by the activation DCI overlaps with the first time domain resource, the processor determines the transport block size according to the frequency domain resource within the allocated second frequency domain resource; if the time domain resource indicated by the activation DCI overlaps with the second time domain resource, the processor determines the transport block size according to the allocated frequency domain resource; And / or For the corresponding SPS PDSCH of one SPS configuration: the first time domain resource is not an invalid time domain resource type, the processor determines the transport block size according to the frequency domain resource within the allocated second frequency domain resource or the allocated frequency domain resource based on the second specific value.

19. A PDSCH sending device, comprising: a transmitter that transmits one or more SPS configurations and information for configuring at least 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 transmits the corresponding SPS PDSCH of at least one SPS configuration in the one or more SPS configurations; wherein for the corresponding SPS PDSCH of one SPS configuration in the at least one SPS configuration: does not transmit the SPS PDSCH overlapping with the first time domain resource, or does not transmit the SPS PDSCH overlapping with the second time domain resource, or for the SPS PDSCH overlapping with the first time domain resource, the frequency domain resource within the allocated second frequency domain resource is valid.

20. A communication system, comprising: a network device that transmits one or more SPS configurations and information for configuring at least 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 transmits the corresponding SPS PDSCH of at least one SPS configuration in the one or more SPS configurations; a terminal device that receives the one or more SPS configurations and the information for configuring at least the first time domain resource and / or the second time domain resource; and receives the corresponding SPS PDSCH of at least one SPS configuration in the one or more SPS configurations; Among them, for the SPS PDSCH corresponding to one of the at least one SPS configuration: do not receive the SPS PDSCH overlapping with the first time domain resource, or do not receive the SPS PDSCH overlapping with the second time domain resource, or for the SPS PDSCH overlapping with the first time domain resource, the frequency domain resource within the second frequency domain resource allocated is valid.

Images