Pusch sending method and apparatus, pusch receiving method and apparatus, and communication system

Abstract

Provided in embodiments of the present application are a PUSCH sending method and apparatus, a PUSCH receiving method and apparatus, and a communication system. The PUSCH sending method comprises: a terminal device receives a CG configuration and information 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 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 the terminal device sends a PUSCH corresponding to the CG configuration, wherein the PUSCH has a repetition and / or a multi-slot TB, and the repetition includes a first-type repetition or a second-type repetition, or the PUSCH does not have a repetition and a multi-slot TB.

Description

PUSCH transmission and reception 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 delay of uplink.

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

[0004] SUMMARY

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

[0006] On the other hand, a physical uplink shared channel (PUSCH) can be scheduled by configured grant (CG) information, for example, it can be a Type 1 CG PUSCH or a Type 2 CG PUSCH. A terminal device can be provided with one or more CG configurations, and each CG configuration provides time-frequency resources of a PUSCH. However, in the case of supporting the above working mode, how the UE transmits the CG PUSCH, especially when the CG PUSCH has repetition and / or TBoMS, there is no solution.

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

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

[0009] The terminal device receives a CG configuration 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 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

[0010] The terminal device transmits a PUSCH corresponding to the CG configuration; wherein, the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A or Type B, or the PUSCH has no repetition and multi-slot TB.

[0011] According to another aspect of embodiments of the present application, a PUSCH transmission device is provided, comprising:

[0012] The receiver receives a CG configuration 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 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

[0013] The transmitter transmits a PUSCH corresponding to the CG configuration; wherein, the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A or Type B, or the PUSCH has no repetition and multi-slot TB.

[0014] According to another aspect of embodiments of the present application, a PUSCH transmission method is provided, comprising:

[0015] The network device transmits a CG configuration 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 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

[0016] The network device receives a PUSCH corresponding to the CG configuration; wherein, the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A or Type B, or the PUSCH has no repetition and multi-slot TB.

[0017] According to another aspect of embodiments of the present application, a PUSCH reception device is provided, comprising:

[0018] a transmitter that transmits a CG configuration 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

[0019] a receiver that receives a PUSCH corresponding to the CG configuration; wherein, the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A or Type B, or the PUSCH has no repetition and multi-slot TB.

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

[0021] a network device that transmits a CG configuration and information at least for configuring a first time domain resource and / or a second time domain resource; and receives a PUSCH corresponding to the CG configuration; 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;

[0022] a terminal device that receives a CG configuration and information at least for configuring a first time domain resource and / or a second time domain resource; and transmits a PUSCH corresponding to the CG configuration; wherein, the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A or Type B, or the PUSCH has no repetition and multi-slot TB.

[0023] One of the beneficial effects of the embodiments of the present application is that a terminal device receives a CG configuration and information at least for configuring a first time domain resource and / or a second time domain resource; and transmits a PUSCH corresponding to the CG configuration. Thus, the network device can work in full duplex mode (receiving and transmitting at the same time), and the terminal device can also use the corresponding resources to transceive signals when the network device works in full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the flexibility of resource allocation and resource utilization.

[0024] Specific embodiments of the application are disclosed herein, and represented in the accompanying drawings, illustrating the principles of the application in a manner that is best suited to the understanding of its principles and operation. It will be understood that the application is not limited in scope to the specific implementations disclosed, and that the application is applicable to other implementations and modifications apparent to those skilled in the art.

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

[0026] 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 does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. BRIEF DESCRIPTION OF DRAWINGS

[0027] Elements and features described with respect to one drawing or implementation of an embodiment can be combined with elements and features of one or more other drawings or implementations in any manner.

[0028] The accompanying drawings are included to provide a further understanding of embodiments of the application, and are incorporated in and constitute a part of this specification, illustrate embodiments of the application, and together with the description serve to explain the principles of the application. It is to be understood that other embodiments can be utilized, and structural and functional modifications can be made without departing from the scope of the present application. In the drawings, like reference numerals refer to like elements throughout the several views, which can be used to illustrate the more than one implementation of the application.

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

[0030] FIG. 2 is a schematic diagram of a PUSCH transmission method according to an embodiment of the present application;

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

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

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

[0034] FIG. 6 is a schematic diagram of a PUSCH reception method according to an embodiment of the present application;

[0035] FIG. 7 is a schematic diagram of a PUSCH transmission apparatus according to an embodiment of the present application;

[0036] FIG. 8 is a schematic diagram of a PUSCH reception apparatus according to an embodiment of the present application;

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

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

[0039] 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 application, taken in conjunction with the accompanying drawings. In the description of embodiments of the application, specific terminology is employed for the sake of clarity. However, the application is not intended to be limited to the specific terminology so selected. A person skilled in the art will recognize that the principles of the application can be employed in any device that employs principles of the application.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0053] 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 (MAC) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto. The names of the signaling (such as the RRC message, the information element, the information field, the higher layer parameter, 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.

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

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

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

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

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

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

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

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

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

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

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

[0065] Embodiments of the first aspect

[0066] The embodiments of the present application provide a PUSCH transmission method, which is described from the terminal device side.

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

[0068] 201. The terminal device receives a configured grant configuration (configuredGrantConfig) 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

[0069] 202, the terminal device sends a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A repetition or Type B repetition, or the PUSCH has no repetition and multi-slot TB.

[0070] 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 according to the above description, and the present application is not limited to the above FIG. 2.

[0071] In some embodiments, the terminal device can be an SBFD-aware device; the present application is not limited thereto. For example, in the initial access 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).

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

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

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

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

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

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

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

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

[0080] For example, the starting and ending slots are the first and last slots including SBFD symbols, respectively, and the starting and ending symbols are the first and last SBFD symbols in the starting and ending slots, respectively, and all the symbols from the starting symbol of the starting slot to the ending symbol of the ending slot are SBFD symbols. The slot index is the number of the slot included in the period, which is, for example, sequentially increased by 1 starting from 0 or 1. For example, when the starting slot index is 0, the starting slot is the first slot in the period, and when the starting slot index is 1, the starting slot is the second slot in the period, and so on. Similarly, the symbol index is the number of the symbol in the slot. Among them, the above-mentioned slot / symbol is configured with the SCS of the reference Subcarrier Spacing field of the TDD-UL-DL-Config Common IE.

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

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

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

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

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

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

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

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

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

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

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

[0092] The frequency domain resources involved in embodiments of the present disclosure are further described below.

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

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

[0095] 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 each include an integer number of PRBs, and the information for configuring the UL subband and the DL subband each includes information for indicating a corresponding starting PRB and a bandwidth.

[0096] In some embodiments, the information for configuring the UL subband and the DL subband is provided by high layer signaling.

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

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

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

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

[0101] In some embodiments, the high layer parameters for configuring UL subband and the high layer parameters for configuring DL subband include one or more parameters for providing 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.

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

[0103] Table 1

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

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

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

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

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

[0109] FIG. 4 is an example diagram of uplink usable PRBs according to embodiments of the present disclosure. 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 disclosure is not limited thereto.

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

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

[0112] The above describes the time-frequency resources in a schematic manner. The following describes embodiments of the present disclosure in a schematic manner.

[0113] In embodiments of the present disclosure, overlapping with the first time-domain resource includes partial overlap (i.e., one part is within the first time-domain resource, and another part 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., one part is within the second time-domain resource, and another part 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).

[0114] In some embodiments, the above-mentioned partial overlap is included in the overlap with the first time-domain resource and is not included in the overlap with the second time-domain resource, for example, if the overlap with the first time-domain resource includes the partial overlap, the overlap with the second time-domain resource does not include the partial overlap, and vice versa; the present application is not limited thereto.

[0115] In the embodiments of the present application, the terminal device can be provided with one or more CG PUSCH configurations (or CG configurations), each of which independently provides time-frequency domain resource allocation to periodically or semi-persistently schedule PUSCH. The configured grant PUSCH (CG PUSCH) can also be referred to as a configured uplink grant or a configured PUSCH grant, and the CG configuration is, for example, ConfiguredGrantConfig, and the present application is not limited thereto.

[0116] In some embodiments, the configured grant includes a first configured grant (configured grant Type 1) and / or a second configured grant (configured grant Type 2). For the first configured grant, the PUSCH transmission is semi-statically configured to be performed after receiving a first higher layer parameter (rrc-Configured UplinkGrant) without detecting an uplink grant in a DCI; for the second configured grant, the PUSCH transmission is semi-persistently scheduled by an uplink grant in a valid activation DCI (for activating the second grant configuration) after receiving a second higher layer parameter (rrc-Configured UplinkGrant).

[0117] In some embodiments, the configured grant has multiple consecutive configured grant PUSCHs in a period, and / or the configured grant has multiple non-consecutive configured grant PUSCHs in a period. For example, the configured grant is a Multi-PUSCH configured grant, which can be the first configured grant or the second configured grant described above. In the corresponding CG PUSCH configuration, information for indicating the number of configured grant PUSCHs in a period (or Number of consecutive slots for CG PUSCH transmission occasions in a period) is included, which is, for example, nrofSlotsInCG-Period.

[0118] In some embodiments, for Type 1 CG PUSCH, frequency domain resource allocation (FDRA) can be provided by RRC; for Type 2 CG PUSCH, frequency domain resource allocation (FDRA) can be provided by RRC and / or MAC CE and / or DCI. The present application is not limited thereto.

[0119] In some embodiments, a CG configured PUSCH can be referred to as CG PUSCH; for example, the PUSCH has repetition and / or multi-slot TB(s), the repetition includes PUSCH repetition type A or PUSCH repetition type B, or the PUSCH has no repetition and multi-slot TB(s).

[0120] The following is described for CG PUSCH.

[0121] In some embodiments, different PUSCHs (in the same / different period) correspond to / have independent HARQ process ID and TB.

[0122] In some embodiments, for Type 1 CG, the repetition type is configured by higher layer parameter. For Type 2 CG, the repetition type is determined by PUSCH repetition type associated with the UL grant received on the (activation) DCI. For example, as described in Table 2:

[0123] Table 2

[0124] In some embodiments, the transport block size (TBS) of the PUSCH is determined according to the allocated frequency domain resource within the first frequency domain resource or according to the allocated frequency domain resource.

[0125] For example, determining the TBS according to the above frequency domain resource includes determining the TBS according to the number of PRBs included in the frequency domain resource, for example, in the process of determining the TBS, the UE needs to determine the number of REs (within a slot), for example, a UE determines the total number of REs allocated for PUSCH (N RE )by N RE =N*min(156,N' RE )·n PRB (for the case of TBoMS), or N RE =min(156,N'RE )·n PRB (For other cases, without TboMS), where n PRB is the number of allocated PRBs or the number of allocated PRBs within UL usable PRBs (or UL subband), N' RE is the number of REs allocated for PUSCH within a PRB, N is the number of (slots) for TBS determination indicated by numberOfSlotsTBoMS.

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

[0127] In some embodiments, for PUSCH overlapping with SBFD symbols, the effective frequency domain resources are determined according to the allocated frequency domain resources (e.g. assigned / allocated PRBs within UL usable PRBs) within the first frequency domain resources, for PUSCH overlapping with non-SBFD symbols, the TBS is determined according to the allocated frequency domain resources (e.g. assigned / allocated PRBs); or,

[0128] For both PUSCH overlapping with SBFD symbols and PUSCH overlapping with non-SBFD symbols, the TBS is determined according to the allocated frequency domain resources.

[0129] In some embodiments, the TBS is determined according to the allocated frequency domain resources within the first frequency domain resources or the allocated frequency domain resources, in relation to the type of valid time domain resources and / or the type of invalid time domain resources and / or the resource allocation type.

[0130] For example, for PUSCH of Type 2 CG, in relation to the type of valid time domain resources and / or the type of invalid time domain resources and / or the reference repetition (in the reference CG PUSCH) and / or the corresponding (allocated) symbols in the first slot.

[0131] For example, the reference PUSCH is the first CG PUSCH associated with the corresponding activation DCI or the PUSCH scheduled by the activation DCI, and / or the first slot is the slot determined by the slot offset indicated by the activation DCI. The slot offset is for example the slot offset K2.

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

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

[0134] In some embodiments, (for Type 1 CG,) the reference repetition is the first (for repetition Type B: nominal / actual) repetition of (the first CG PUSCH).

[0135] In some embodiments, (for Type 1 / 2 CG,) the reference repetition is the first (for repetition Type B: nominal / actual) repetition of (the CG PUSCH), respectively, with the CG PUSCH in different periodicities.

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

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

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

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

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

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

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

[0143] In some embodiments, corresponding to case 2, it can also be said that PUSCH transmission can be across SBFD symbols and non-SBFD symbols. Both PUSCH / repetitions overlapping with SBFD symbols or non-SBFD symbols can be transmitted.

[0144] The following is an illustrative description of the above various cases respectively.

[0145] In some embodiments, when SBFD symbols are invalid symbol type (case 1-1), TBS is determined according to allocated frequency domain resources; and / or,

[0146] When SBFD symbols are not invalid symbol type, TBS is determined according to allocated frequency domain resources within the first frequency domain resources or allocated frequency domain resources.

[0147] In some embodiments, SBFD symbols are not invalid symbol type, including: case 1-2 and / or case 2 described above.

[0148] In some embodiments, when the non-SBFD symbol is a type of invalid time domain resource (case 1-2), for a first type of resource allocation (Type 0), the TBS is determined according to the allocated frequency domain resources within the first frequency domain resources, and / or, for a second type of resource allocation (Type 1), the TBS is determined according to the allocated frequency domain resources; and / or,

[0149] When there is no type of invalid time domain resource (case 2), the TBS is determined according to the allocated frequency domain resources.

[0150] In some embodiments, when there is no type of invalid time domain resource, for PUSCHs overlapping with the first time domain resources, the TBS is determined according to the allocated frequency domain resources within the first frequency domain resources or the allocated frequency domain resources, and for PUSCHs overlapping with the second time domain resources, the TBS is determined according to the allocated frequency domain resources.

[0151] In some embodiments, when there is no type of invalid time domain resource, for PUSCHs overlapping with the first time domain resources,

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

[0153] In some embodiments, when the second time domain resource type is a type of invalid time domain resource, for a first type of resource allocation (Type 0), the TBS is determined according to the allocated frequency domain resources within the first frequency domain resources, and / or, for a second type of resource allocation (Type 1), the TBS is determined according to the allocated frequency domain resources; and / or,

[0154] When there is no type of invalid time domain resource, if the reference repetition and / or the allocated symbol in the first slot and / or a certain number of repetitions (in the second time domain resource or) overlap with the second time domain resource, the TBS is determined according to the allocated frequency domain resources; and / or, if the reference repetition and / or the allocated symbol in the first slot and / or a certain number of repetitions (in the first time domain resource or) overlap with the first time domain resource, the TBS is determined according to the allocated frequency domain resources within the first frequency domain resources.

[0155] In some embodiments, (when there is no type of invalid time domain resource,) if the reference repetition (only for repetitions) and / or the allocated symbol in the first slot (applicable to both repetitions and multi-slot TBs) and / or a certain number of repetitions (in the second time domain resource or) overlap with the second time domain resource, the TBS is determined according to the allocated frequency domain resources, and / or,

[0156] If the reference repetition (only for repetition) and / or the allocated symbol in the first time slot (applicable for both repetition and multi-slot TB) and / or a number of repetitions (in the first time domain resource or) overlap with the first time domain resource, the TBS is determined according to the allocated frequency domain resource within the first frequency domain resource.

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

[0158] 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 the time domain resource indicated by the reference PUSCH and / or the corresponding activated DCI (in the TDRA field).

[0159] 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 that there is no invalid time domain resource type (i.e. case 2) and / or to indicate that there is an invalid time domain resource type (i.e. case 1).

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

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

[0162] For multi-PUSCH, the UE determines whether it is case 1-1 or Case 1-2 according to the second information and / or the reference PUSCH and / or the allocated symbol in the first time slot, and / or, for PUSCH repetition, the UE determines whether it is Case 1-1 or Case 1-2 according to the second information and / or the reference repetition and / or the allocated symbol in the first time slot. The second information is included in the DCI, for example, but is not limited thereto.

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

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

[0165] 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 invalid time domain resource type);

[0166] The first information is (optionally) outside of CG configurations (e.g., included in PUSCH-Config or PUSCH-ConfigCommon), the first information applies to all or part of the CG configurations, or the first information is (optionally) inside of CG configurations, the first information applies to the CG configuration where the first information is.

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

[0168] 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 invalid time domain resource type and / or is used to indicate that the second time domain resource is invalid time domain resource type, or the second information is used to indicate that the first time domain resource is valid time domain resource type and / or is used to indicate that the second time domain resource is valid time domain resource type);

[0169] The second information is (optionally) inside of CG configurations, the second information applies to the CG configuration where the second information is.

[0170] In some embodiments, determining invalid time domain resource type and / or valid time domain resource type based on resource allocation type comprises:

[0171] The valid time domain resource type is the time domain resource type of the resource allocation type;

[0172] If the resource allocation type overlaps (only) with the first time domain resource, the valid time domain resource type is the first time domain resource, if the resource allocation type overlaps (only) with the second time domain resource, the valid time domain resource type is the second time domain resource, or the terminal device does not expect the resource allocation type to overlap with both the first time domain resource and the second time domain resource.

[0173] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the resource allocation type to overlap (only) with the first time domain resource or overlap (only) with the second time domain resource, or the valid time domain resource type or the time domain resource type of the resource allocation type is the time domain resource type of the reference repetition of the resource allocation type.

[0174] 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 includes:

[0175] 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;

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

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

[0178] 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,

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

[0180] In some embodiments, when the terminal device is not provided with the first information or when the first information indicates that there is an invalid time domain resource type, the second information is (must be) included in the CG configuration; or,

[0181] For the CG configuration not including the second information:

[0182] The terminal device determines the invalid time domain resource type and / or the valid time domain resource type based on the resource allocation type or the time domain resource indicated by the activation DCI, or the terminal device considers the first time domain resource or the second time domain resource to be the invalid time domain resource type.

[0183] In some embodiments, the terminal device does not expect to be configured with or apply the AvailableSlotCounting for the first type of repetition.

[0184] In some embodiments, the not applying the AvailableSlotCounting comprises that, when the AvailableSlotCounting is enabled, the AvailableSlotCounting is not applied to the PUSCH.

[0185] In some embodiments, the repetition comprises nominal repetition(s) and / or actual repetition(s) for the second type of repetition.

[0186] In some embodiments, the PUSCH with the first type of repetition without being configured with (or without being enabled with) the AvailableSlotCounting, or the PUSCH with the second type of repetition:

[0187] When the SBFD symbol is the invalid type of time domain resource, the PUSCH or (for repetition Type B: nominal / actual) repetition overlapping with the SBFD symbol is not transmitted (dropped), and when the non-SBFD symbol is the invalid type of time domain resource, the PUSCH or (for repetition Type B: nominal / actual) repetition overlapping with the non-SBFD symbol is not transmitted (dropped).

[0188] wherein the repetition comprises nominal repetition(s) and / or actual repetition(s) for the PUSCH with the PUSCH repetition Type B or for the PUSCH repetition Type B, that is, when the SBFD symbol is the invalid type of time domain resource, the nominal repetition(s) overlapping with the SBFD symbol is not transmitted (dropped), and when the non-SBFD symbol is the invalid type of time domain resource, the nominal repetition(s) overlapping with the non-SBFD symbol is not transmitted (dropped), or, when the SBFD symbol is the invalid type of time domain resource, the actual repetition(s) overlapping with the SBFD symbol is not transmitted (dropped), and when the non-SBFD symbol is the invalid type of time domain resource, the actual repetition(s) overlapping with the non-SBFD symbol is not transmitted (dropped).

[0189] In some embodiments, the UE determines the actual repetition(s) from the nominal repetition(s), which is exemplarily illustrated as follows.

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

[0191] determines the actual repetition(s) from the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the (first / second / third) uplink-downlink configuration and / or the SSB. For example, invalid symbols are determined from the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the (first / second / third) uplink-downlink configuration and / or the SSB, and the remaining / other symbols are considered as (potential) valid symbols from which the actual repetition(s) are determined (e.g., in the manner shown in Table 3).

[0192] Table 3

[0193] 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 the SBFD symbol, which is different from the first / second uplink-downlink configuration.

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

[0195] determines the slots corresponding to the PUSCH from the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the (first / second / third) uplink-downlink configuration and / or the SSB.

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

[0197] determines the actual repetition(s) from the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the (first / second / third) uplink-downlink configuration and / or the SSB.

[0198] In some embodiments, (for determining the actual repetition,) the first time-domain resource and / or the second time-domain resource and / or invalid time-domain resource type and / or valid time-domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB are used to determine invalid symbols.

[0199] In some embodiments, when there is no invalid time-domain resource type, no actual repetition is transmitted that overlaps both the first time-domain resource and the second time-domain resource.

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

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

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

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

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

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

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

[0207] In some embodiments, for PUSCH repetition Type A / B, N = 1.

[0208] In some embodiments, for the first repetition type and / or TBoMS, the symbol allocation can be determined as follows, i.e., the same symbol allocation is applied in N*K slots.

[0209] Table 4

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

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

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

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

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

[0215] In some embodiments, the slots in N·K slots meet a second condition. The second condition is the same for case 1 / case 1-1 / case 1-2 / case 2. In other embodiments, the slots in N·K slots meet a second condition. The second condition is different for case 1 / case 1-1 / case 1-2 / case 2.

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

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

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

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

[0220] In some embodiments, if the symbols corresponding to one slot do not satisfy the above-mentioned second condition, it is not counted in N·K slots.

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

[0222] For example, Table 9 exemplarily shows an example of how to determine the slots corresponding to PUSCH for PUSCH repetition type A, for example, applicable to Type 1 CG, but not limited thereto.

[0223] Table 5

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

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

[0226] For example, Table 6 exemplarily shows another example of how to determine the slots corresponding to PUSCH for PUSCH repetition type A. Table 7 exemplarily shows an example of how to determine the slots corresponding to PUSCH for TBoMS. For example, it is applicable to Type 2 CG, but is not limited thereto

[0227] Table 6

[0228] Table 7

[0229] The frequency resource allocation of PUSCH is further exemplarily described below, and the present application is not limited thereto.

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

[0231] In some embodiments, for the second time-domain resource, a first starting RB (the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1) indicated by the third information is applied; for the first time-domain resource, a second starting RB is applied.

[0232] The third information comprises, for example, Type 1 CG, information (frequency Domain Allocation) in rrc-ConfiguredUplinkGrant, Type 2 CG, FDRA in activation DCI; the application is not limited thereto, and the following is described by taking DCI as an example.

[0233] In some embodiments, the second starting RB is the same as the first starting RB.

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

[0235] In some embodiments, the first starting RB is, for example, the first PRB in the frequency domain resource (i.e., the allocated frequency domain resource) (PRB) indicated by the third information, or the PRB with the lowest frequency domain position or the smallest index.

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

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

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

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

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

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

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

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

[0244] The following is a schematic description of how to support PUSCH frequency hopping.

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

[0246] In some embodiments, for CG, frequency hopping is configured by frequencyHopping or frequencyHoppingPUSCH-RepTypeB-r16 provided in configuredGrantConfig. For example, for the first repetition type / TBoMS, it can be intra-slot hopping or inter-slot hopping. For the second repetition type, it can be inter-repetition hopping or inter-slot hopping

[0247] In some embodiments, for Type 1 CG, frequency hopping offset (e.g. corresponding to first frequency hopping offset) is configured by frequencyHoppingOffset provided in configuredGrantConfig.

[0248] In some embodiments, for PUSCH activated by DCI format 0_1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-Config (e.g. corresponding to first FH offset list below).

[0249] In some embodiments, for PUSCH activated by DCI format 0_2, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetListsDCI-0-2 in pusch-Config (e.g. corresponding to first FH offset list below)

[0250] In some embodiments, the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG) can be referred to as being for non-SBFD symbols, but not limited thereto.

[0251] In some embodiments, the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG) can be for / applied to SBFD symbols and / or non-SBFD symbols.

[0252] In some embodiments, the UE can be high layer signaling configured with a second FH offset list (Type 2 CG) and / or a second FH offset (Type 1 CG) for SBFD symbols.

[0253] For example, the UE can be provided with a high layer parameter for configuring the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG). Where different DCI formats, e.g. DCI format 0_1 and 0_2 or 0_3, can correspond to common or independent high layer parameters for configuring the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG). For example, the high layer parameter for configuring the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG) is optionally present in pusch-Config / PUSCH-Config, but not limited thereto. The high layer parameter is, for example, frequencyHoppingOffsetListsSBFD (e.g. for DCI format 0_1 and 0_3), frequencyHoppingOffsetListsDCI-0-2-SBFD, (e.g. for DCI format 0_2).

[0254] In some embodiments, the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG) is configured only if the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG) is configured, that is, when the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG) is not configured, the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG) is not configured.

[0255] In some embodiments, the number of FH offsets in the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG) should not be greater than or must be equal to the number of FH offsets in the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG).

[0256] In some embodiments, the number of FH offsets in the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG) and the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG) is limited by the bandwidth of the BWP. For example, when the bandwidth of the corresponding BWP is less than 50 PRBs, 2 are included, otherwise, 4 are included.

[0257] In some embodiments, the number of FH offsets in the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG) is limited by the bandwidth of the BWP. The number of FH offsets in the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG) is limited by the bandwidth of the UL usable PRBs. For example, when the bandwidth of the corresponding UL usable PRBs is less than 50 PRBs, 2 are included, otherwise, 4 are included.

[0258] In some embodiments, the UE can be enabled / disabled for frequency hopping for SBFD symbols by higher layer signaling. For example, the UE can be provided with a higher layer parameter for enabling / disabling frequency hopping for SBFD symbols (in the case of (being configured with the first FH offset list (Type 2 CG) and / or the first FH offset (Type 1 CG) but) not being configured with the second FH offset list (Type 2 CG) and / or the second FH offset (Type 1 CG) or the DCI does not indicate the second offset). Where different DCI formats, such as DCI formats 0_1 and 0_2 or 0_3, can correspond to common or independent higher layer parameters for enabling / disabling frequency hopping for SBFD symbols. For example, the higher layer parameter for enabling / disabling frequency hopping for SBFD symbols is optionally present in pusch-Config / PUSCH-Config, but is not limited thereto.

[0259] In some embodiments, a frequency hopping flag field (for indicating whether the PUSCH it schedules performs frequency hopping or not, such as shown in Table 8 below) is included in the DCI (when frequency hopping is configured).

[0260] Table 8

[0261] In some embodiments, the DCI includes 2 frequency hopping flag fields, e.g., for SBFD symbols and non-SBFD symbols, respectively, for indicating whether frequency hopping is applied for SBFD symbols and non-SBFD symbols, respectively.

[0262] In some embodiments, (when frequency hopping is configured,) information for indicating frequency offset is included in the DCI, which includes, e.g., N UL,hop MSB bits in the FDRA field.

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

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

[0265] Table 9

[0266] In some embodiments, for non-SBFD symbols, the first FH offset is applied; for SBFD symbols, the first FH offset or the second FH offset or no FH offset (i.e., no frequency hopping) is applied.

[0267] In some embodiments, for SBFD symbols, when no second FH offset list (Type 2 CG) and / or second FH offset (Type 1 CG) is configured or the DCI does not indicate the second FH offset (e.g., the value corresponding to the information for indicating frequency offset in the DCI does not correspond to the second FH offset), the first FH offset (indicated by the information for indicating frequency offset in the DCI) is applied or no FH offset is applied; for example, if the value (e.g., 10 / 11 in the above table) corresponding to the information for indicating frequency offset in the DCI (corresponding to the first FH offset but) does not correspond to the second FH offset, for SBFD symbols, the first FH offset corresponding to the value is applied or no FH offset is applied.

[0268] In some embodiments, for SBFD symbols, when no second FH offset list (Type 2 CG) and / or second FH offset (Type 1 CG) is configured or the DCI does not indicate the second FH offset, and the FH is not enabled (e.g., by higher layer signaling or DCI, as described above), the first FH offset (indicated by the information for indicating frequency offset in the DCI) is applied.

[0269] In some embodiments, for SBFD symbols, when no second FH offset list (Type 2 CG) and / or second FH offset (Type 1 CG) is configured or the DCI does not indicate the second FH offset, and the FH is enabled (e.g., by higher layer signaling or DCI, as described above), the first FH offset (indicated by the information for indicating frequency offset in the DCI) is applied.

[0270] In some embodiments, for SBFD symbols, when the second FH offset is indicated (by the FH flag in the DCI and) (by the information for indicating frequency offset in the DCI), the second FH offset is applied.

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

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

[0273] In some embodiments, for SBFD symbols, when no second FH offset is indicated by (information in DCI for indicating frequency offset) or no second FH offset list is configured (Type 2 CG) and / or no second FH offset is configured (Type 1 CG), and FH is not enabled (e.g. by (higher layer signaling or DCI, as described above)), no FH offset is applied.

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

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

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

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

[0278] Table 10 exemplarily shows an example for intra-slot FH, to which the application is not limited. Wherein, if the symbol allocation in a slot (only) overlaps with non-SBFD symbols (or in other words, for PUSCH transmission (only) overlapping with non-SBFD symbols), RB start is the first starting RB, RB offset is the first FH offset as described above, is the bandwidth / size of the (UL) BWP, RB start (i = 1) is the third starting RB as described above. If the symbol allocation in a slot (only) overlaps with SBFD symbols (or in other words, for PUSCH transmission (only) overlapping with SBFD symbols), (when applying FH), RB start is the second starting RB, RB offset is the first FH offset or the second FH offset (determined according to the aforementioned method which one to apply), is the bandwidth / size of the UL usable PRBs, RB start (i = 1) is the fourth starting RB as described above.

[0279] Table 10

[0280] In some embodiments, for PUSCH repetition Type A and for TB processing over multiple slots, the slots or repetitions are counted independently, and it has been determined that the corresponding frequency domain resources of the slots / repetitions.

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

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

[0283] Table 11 exemplarily shows one example for inter-slot FH, the present application is not limited thereto.

[0284] Table 11

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

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

[0287] Table 12 exemplarily shows one example for inter-slot FH, the present application is not limited thereto.

[0288] Table 12

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

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

[0291] Table 13 exemplarily shows one example for inter-repetition FH, the present application is not limited thereto.

[0292] Table 13

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

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

[0295] From the above embodiments, the terminal device receives the CG configuration (configuredGrantConfig) and information at least for configuring the first time domain resource and / or the second time domain resource; and transmits the PUSCH corresponding to the CG configuration. Therefore, the network device can work in the full duplex mode (simultaneous reception and transmission), and the terminal device can also utilize the corresponding resources to transceive signals when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0296] Embodiments of the second aspect

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

[0298] FIG. 6 is a schematic diagram of a PUSCH receiving method according to an embodiment of the present application. As shown in FIG. 6, the method includes the following steps.

[0299] 601, the network device transmits a CG configuration (configuredGrantConfig) and information at least for configuring a first time domain resource and / or a 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

[0300] 602, the network device receives the PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A repetition or Type B repetition, or the PUSCH does not have repetition and multi-slot TB.

[0301] It is noticeable that the above Fig. 6 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 properly adjusted, and furthermore, some operations can be added or some operations can be reduced. Those skilled in the art can properly modify based on the above description, and the present application is not limited to the above Fig. 6.

[0302] In some embodiments, the PUSCH has repetition:

[0303] When the first time domain resource is an invalid time domain resource type, the repetition overlapping with the first time domain resource is not transmitted, and / or,

[0304] When the second time domain resource is an invalid time domain resource type, the repetition overlapping with the second time domain resource is not transmitted.

[0305] 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 the resource allocation type and / or the time domain resource (e.g., symbol in slot n+k0) indicated by the TDRA field in the corresponding activation DCI.

[0306] 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 an 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);

[0307] The first information is (optionally) present outside the CG configuration (e.g., included in PUSCH-Config or PUSCH-ConfigCommon), the first information applies to all or part of the CG configuration, or the first information is (optionally) present in the CG configuration, and the first information applies to the CG configuration where it is present.

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

[0309] In some embodiments, the second information is used to indicate an invalid time domain resource type and / or a 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 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 used to indicate that the second time domain resource is a valid time domain resource type); the second information (optionally) exists in a CG configuration, and the second information is applied to the CG configuration where the second information exists.

[0310] In some embodiments, determining the invalid time domain resource type and / or the valid time domain resource type based on the resource allocation type comprises:

[0311] The valid time domain resource type is a time domain resource type of the resource allocation type;

[0312] wherein, if the resource allocation type overlaps with only the first time domain resource, the valid time domain resource type is the first time domain resource, if the resource allocation type overlaps with only the second time domain resource, the valid time domain resource type is the second time domain resource, or the terminal device does not expect the resource allocation type to overlap with both the first time domain resource and the second time domain resource.

[0313] In some embodiments, in the case of repetition, the terminal device expects all repetitions of the resource allocation type to overlap with only the first time domain resource or to overlap with only the second time domain resource, or the valid time domain resource type or the time domain resource type of the resource allocation type is a time domain resource type of a reference repetition of the resource allocation type.

[0314] 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:

[0315] if the time domain resource indicated by the activation DCI overlaps 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;

[0316] if the time domain resource indicated by the activation DCI overlaps 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.

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

[0318] 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,

[0319] When the first information and the second information exist simultaneously, the first information is not applied to the CG configuration including the second information, and / or, is applied to the CG configuration not including the second information.

[0320] In some embodiments, when the terminal device is not provided with the first information or when the first information indicates invalid time domain resource type, the second information is (must be) included in the CG configuration; or,

[0321] For the CG configuration not including the second information:

[0322] The terminal device determines the invalid time domain resource type and / or the valid time domain resource type based on the resource allocation type or the time domain resource indicated by the activation DCI, or the terminal device considers the first time domain resource or the second time domain resource as the invalid time domain resource type.

[0323] In some embodiments, for the first type of repetition, the terminal device does not expect to be configured with the available slot count or does not apply the available slot count.

[0324] In some embodiments, the available slot count is not applied, including: when the available slot count is enabled, the available slot count is not applied to the PUSCH.

[0325] In some embodiments, for the second type of repetition, the repetition includes nominal repetition and / or actual repetition.

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

[0327] The slots corresponding to the PUSCH are determined according to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB.

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

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

[0330] In some embodiments, (for determining the actual repetition,) the first time-domain resource and / or the second time-domain resource and / or invalid time-domain resource type and / or valid time-domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB are used to determine invalid symbols.

[0331] In some embodiments, when there is no invalid time-domain resource type, no actual repetition is transmitted that overlaps both the first time-domain resource and the second time-domain resource.

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

[0333] In some embodiments, for the first time-domain resource, a first starting RB indicated by the third information (Type 1 CG, information in rrc-ConfiguredUplinkGrant, Type 2 CG, activation DCI) is applied.

[0334] For the second time-domain resource, a first starting RB indicated by the third information (the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1) is applied or a second starting RB determined according to a RB offset (predefined or indicated) and / or the first starting RB is applied.

[0335] In some embodiments, (when a first FH offset is indicated,) for the second time-domain resource, the first FH offset is applied; and / or, for the first time-domain resource, the first FH offset or a second FH offset or no FH offset (i.e., no frequency hopping) is applied.

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

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

[0338] In some embodiments, a transport block size (TBS) corresponding to the PUSCH is determined according to the allocated frequency domain resource within the first frequency domain resource or according to the allocated frequency domain resource.

[0339] In some embodiments, the TBS is determined according to the allocated frequency domain resource within the first frequency domain resource or the allocated frequency domain resource, in relation to the valid time domain resource type and / or the invalid time domain resource type and / or the resource allocation type.

[0340] In some embodiments, when the first time domain resource is the invalid time domain resource type, the TBS is determined according to the allocated frequency domain resource within the first frequency domain resource or according to the allocated frequency domain resource, and / or, when the first time domain resource is not the invalid time domain resource type, the TBS is determined according to the allocated frequency domain resource.

[0341] In some embodiments, when the first time domain resource is the invalid time domain resource type,

[0342] For the first resource allocation type (frequency resource allocation Type 0), the TBS is determined according to the allocated frequency domain resource within the first frequency domain resource, and for the second resource allocation type (frequency resource allocation Type 1), the TBS is determined according to the allocated frequency domain resource.

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

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

[0345] From the above embodiments, the network device transmits a CG configuration (configuredGrantConfig) and information at least for configuring a first time domain resource and / or a second time domain resource, and receives a PUSCH corresponding to the CG configuration. In this way, the network device can work in a full-duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to transceive signals when the network device works in the full-duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0346] Embodiments of the third aspect

[0347] Embodiments of the present application provide a PUSCH sending 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 repeated.

[0348] FIG. 7 is a schematic diagram of a PUSCH 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 embodiments of the first aspect, the specific implementation can refer to the embodiments of the first aspect, and the same content will not be repeated. As shown in FIG. 7, the PUSCH sending device 700 includes a receiver 701 and a transmitter 702, and can further include a processor 703.

[0349] The receiver 701 receives a CG configuration (configuredGrantConfig) and information at least for configuring a first time domain resource and / or a 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

[0350] The transmitter 702 transmits a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A repetition or Type B repetition, or the PUSCH has no repetition and multi-slot TB.

[0351] In some embodiments, for the PUSCH having repetition:

[0352] When the first time domain resource is an invalid time domain resource type, the repetition overlapping with the first time domain resource is not transmitted, and / or,

[0353] When the second time domain resource is an invalid time domain resource type, the repetition overlapping with the second time domain resource is not transmitted.

[0354] 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 the time-domain resource indicated by the resource allocation type and / or the TDRA field in the corresponding activation DCI (e.g., the symbol in slot n+k0).

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

[0356] The first information is (optionally) present outside the CG configuration (e.g., included in PUSCH-Config or PUSCH-ConfigCommon), the first information is applied to all or part of the CG configurations, or the first information is (optionally) present in the CG configuration, the first information is applied to the CG configuration where the first information is present.

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

[0358] 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 invalid time-domain resource type and / or is used to indicate that the second time-domain resource is invalid time-domain resource type, or the second information is used to indicate that the first time-domain resource is valid time-domain resource type and / or is used to indicate that the second time-domain resource is valid time-domain resource type); the second information is (optionally) present in the CG configuration, the second information is applied to the CG configuration where the second information is present.

[0359] In some embodiments, determining the invalid time-domain resource type and / or the valid time-domain resource type based on the resource allocation type comprises:

[0360] The valid time-domain resource type is the time-domain resource type of the resource allocation type;

[0361] Wherein, if the resource allocation type only overlaps with the first time-domain resource, the valid time-domain resource type is the first time-domain resource, if the resource allocation type only overlaps with the second time-domain resource, the valid time-domain resource type is the second time-domain resource, or the terminal device does not expect the resource allocation type to overlap with both the first time-domain resource and the second time-domain resource.

[0362] In some embodiments, in case of repetition, the terminal device expects all repetitions of the resource allocation type 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 resource allocation type is the time domain resource type of the reference repetition of the resource allocation type.

[0363] 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:

[0364] 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;

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

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

[0367] 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,

[0368] when the first information and the second information exist at the same time, the first information is not applied to the CG configuration including the second information, and / or is applied to the CG configuration not including the second information.

[0369] In some embodiments, when the terminal device is not provided with the first information or when the first information indicates that there is an invalid time domain resource type, the second information is (must be) included in the CG configuration; or,

[0370] for the CG configuration not including the second information:

[0371] the terminal device determines the invalid time domain resource type and / or the valid time domain resource type based on the resource allocation type 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 invalid time domain resource type.

[0372] In some embodiments, for the first type of repetition, the terminal device does not expect to be configured with the available slot count or does not apply the available slot count.

[0373] In some embodiments, the available slot counting is not applied, including: when enabled, the available slot counting is not applied to the PUSCH.

[0374] In some embodiments, for the second type repetition, the repetition includes nominal repetition and / or actual repetition.

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

[0376] According to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB, determine the slots corresponding to the PUSCH.

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

[0378] According to the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB, determine the actual repetition.

[0379] In some embodiments, (for determining the actual repetition,) the first time domain resource and / or the second time domain resource and / or invalid time domain resource type and / or valid time domain resource type and / or (first / second / third) uplink-downlink configuration and / or SSB are used to determine invalid symbols.

[0380] In some embodiments, when there is no invalid time domain resource type, no actual repetition is transmitted that overlaps both the first time domain resource and the second time domain resource.

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

[0382] In some embodiments, for the second time domain resource, a first starting RB indicated by the third information (Type 1 CG, information in rrc-ConfiguredUplinkGrant, Type 2 CG, activation DCI) is applied.

[0383] applying a second starting RB for the first time-domain resource, the second starting RB being same as the first starting RB or determined by the first RB offset (pre-defined or indicated) and / or the first starting RB and / or uplink BWP bandwidth and / or bandwidth of uplink available resources.

[0384] In some embodiments, (when the first FH offset is indicated,) applying the first FH offset for the second time-domain resource; and / or, applying the first FH offset or the second FH offset or no FH offset (i.e., no frequency hopping) for the first time-domain resource.

[0385] In some embodiments, determining, for the second time-domain resource, a third starting RB corresponding to the frequency hopping offset (the first FH offset or the second FH offset) according to the first starting RB and the bandwidth / size of the BWP.

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

[0387] In some embodiments, determining a transport block size (TBS) corresponding to the PUSCH according to the allocated frequency-domain resource within the first frequency-domain resource or according to the allocated frequency-domain resource.

[0388] In some embodiments, determining the TBS according to the allocated frequency-domain resource within the first 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 resource allocation type.

[0389] In some embodiments, when the first time-domain resource is the invalid time-domain resource type, determining the TBS according to the allocated frequency-domain resource within the first frequency-domain resource or according to the allocated frequency-domain resource, and / or, when the first time-domain resource is not the invalid time-domain resource type, determining the TBS according to the allocated frequency-domain resource.

[0390] In some embodiments, when the first time-domain resource is the invalid time-domain resource type,

[0391] For the first frequency resource allocation type (frequency resource allocation Type 0), the TBS is determined according to the allocated frequency domain resource within the first frequency domain resource, and for the second frequency resource allocation type (frequency resource allocation Type 1), the TBS is determined according to the allocated frequency domain resource.

[0392] 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 PUSCH sending device 700 of the embodiments of the present application can also include other components or modules, and the specific content of these components or modules can be referred to related technologies.

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

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

[0395] As can be seen from the above embodiments, the terminal device receives a configured grant configuration (configuredGrantConfig) and information at least for configuring a first time domain resource and / or a second time domain resource; and transmits a PUSCH corresponding to the CG configuration. Therefore, the network device can work in a full duplex mode (simultaneous reception and transmission), and the terminal device can also utilize the corresponding resources to transceive signals when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0396] Embodiments of the fourth aspect

[0397] The embodiments of the present application provide a PUSCH receiving device. The device may, for example, be a network device, or a certain component or component group configured in the network device, and the same content as the embodiments of the third aspect will not be repeated.

[0398] FIG. 8 is a schematic diagram of a PUSCH 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 first and second embodiments, the specific implementation can refer to the first and second embodiments, and the same content will not be repeated. As shown in FIG. 8, the PUSCH receiving apparatus 800 includes a transmitter 801 and a receiver 802, and can further include a processor 803.

[0399] The transmitter 801 transmits a configured grant configuration (CG configuration) and information used at least for configuring a first time domain resource and / or a second time domain resource; wherein the first time domain resource is used for uplink and the second time domain resource is used for downlink.

[0400] The receiver 802 receives a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A repetition or Type B repetition, or the PUSCH has no repetition and multi-slot TB.

[0401] 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 PUSCH receiving apparatus 800 of the embodiments of the present application can further include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0402] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 8, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processor, memory, transmitter, receiver, etc.; the implementation of the present application is not limited thereto.

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

[0404] From the above embodiments, the network device transmits a CG configuration (configuredGrantConfig) and information at least for configuring the first time domain resource and / or the second time domain resource, and receives a PUSCH corresponding to the CG configuration. In this way, the network device can work in a full-duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to transceive signals when the network device works in the full-duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0405] Embodiments of the fifth aspect

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

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

[0408] The network device transmits a CG configuration (configuredGrantConfig) and information at least for configuring the first time domain resource and / or the second time domain resource, and receives a PUSCH corresponding to the CG configuration; 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.

[0409] The terminal device receives a CG configuration (configuredGrantConfig) and information at least for configuring the first time domain resource and / or the second time domain resource, and transmits a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A repetition or Type B repetition, or the PUSCH does not have repetition and multi-slot TB.

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

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

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

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

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

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

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

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

[0418] The embodiments of the present application also provide a computer readable program, which, when executed in a network device, causes a computer to execute the method according to the embodiments of the second aspect in the network device.

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

[0420] The embodiments of the present application also provide a computer readable program, which, when executed in a terminal device, causes a computer to execute the method according to the embodiments of the first aspect in the terminal device.

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

[0422] The apparatuses and methods described above can be implemented by hardware, or by software and hardware combined. The present application relates to a computer-readable program, which, when executed by a logic component, can cause the logic component to implement the above-described apparatuses or constituent components, or to implement the above-described various methods or steps. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, or the like. The 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.

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

[0424] 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 the storage medium and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and the storage medium can be located in an ASIC. The software modules can be stored in a memory of a mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if a device (such as a mobile terminal) uses a MEGA-SIM card or a large-capacity flash memory device, the software modules can be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0425] 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, a discrete gate or transistor logic device, a discrete hardware component, 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.

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

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

[0428] 1. A PUSCH transmission method, comprising:

[0429] A terminal device receives a configured grant configuration (CG configuration) 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 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

[0430] The terminal device transmits a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A or Type B, or the PUSCH has no repetition and multi-slot TB.

[0431] 2. A PUSCH reception method, comprising:

[0432] A network device transmits a configured grant configuration (CG configuration) 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 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

[0433] The network device receives a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes Type A or Type B, or the PUSCH has no repetition and multi-slot TB.

[0434] 3. A terminal device comprising a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the PUSCH transmission method as in Note 1.

[0435] 4. A network device comprising a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the PUSCH reception method as in Note 2.

[0436] 5. A computer program product comprising at least a computer program which, when executed by a processor, causes a terminal device to perform the PUSCH transmission method according to any one of the preceding claims.

[0437] 6. A computer program product comprising at least a computer program which, when executed by a processor, causes a network device to perform the PUSCH reception method according to any one of the preceding claims.

Claims

1. A PUSCH transmitting apparatus, comprising: a receiver configured to receive a CG configuration 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 a transmitter configured to transmit a PUSCH corresponding to the CG configuration; wherein, the PUSCH has repetition and / or multi-slot TB, the repetition comprises a first type of repetition or a second type of repetition, or the PUSCH has no repetition and multi-slot TB.

2. The apparatus of claim 1, wherein, For the PUSCH having repetition: when the first time domain resource is an invalid time domain resource type, no repetition overlapping with the first time domain resource is transmitted, and / or when the second time domain resource is an invalid time domain resource type, no repetition overlapping with the second time domain resource is transmitted.

3. The apparatus of claim 2, wherein, The invalid time domain resource type and / or valid time domain resource type is determined based on first information and / or second information and / or resource allocation type and / or time domain resource indicated by corresponding activation DCI.

4. The apparatus of claim 3, wherein, The first information is used to indicate no invalid time domain resource type and / or to indicate having invalid time domain resource type; The first information exists outside the CG configuration, the first information applies to all or part of the CG configuration in the CG configuration, or the first information exists in the CG configuration, and the first information applies to the CG configuration where it exists.

5. The apparatus of claim 3, wherein, The second information is used to indicate invalid time domain resource type and / or valid time domain resource type; The second information exists in the CG configuration, and the second information applies to the CG configuration where it exists.

6. The apparatus of claim 3, wherein, Determining the invalid time domain resource type and / or valid time domain resource type based on the resource allocation type comprises: The valid time domain resource type is the time domain resource type of the resource allocation type; wherein, if the resource allocation type overlaps with the first time domain resource, the valid time domain resource type is the first time domain resource, if the resource allocation type overlaps with the second time domain resource, the valid time domain resource type is the second time domain resource, or the terminal device does not expect the resource allocation type to overlap with both the first time domain resource and the second time domain resource; In the case of repetition, the terminal device expects all repetitions of the resource allocation type to overlap with the first time domain resource or the second time domain resource, or the valid time domain resource type or the time domain resource type of the resource allocation type is the time domain resource type of the reference repetition of the resource allocation type. Determining the invalid time domain resource type and / or valid time domain resource type based on the time domain resource indicated by the activation DCI comprises:

7. The apparatus of claim 3, wherein, if the time domain resource indicated by the activation DCI overlaps 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; if the time domain resource indicated by the activation DCI overlaps 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. ​ 8. The apparatus of claim 3, wherein, When the first information is used to indicate not having invalid time domain resource type: The first information and the second information do not exist simultaneously; or, When the first information and the second information exist simultaneously, the first information is not applied to the CG configuration including the second information, and / or, is applied to the CG configuration not including the second information.

9. The apparatus of claim 3, wherein, When the terminal device is not provided with the first information or when the first information indicates having invalid time domain resource type, the second information is included in the CG configuration; or, For the CG configuration not including the second information: The terminal device determines the invalid time domain resource type and / or the valid time domain resource type based on the resource allocation type 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 invalid time domain resource type.

10. The apparatus of claim 1, wherein, For the first type of repetition, the terminal device does not expect to be configured with the available slot count or does not apply the available slot count; The not applying the available slot count includes that when the available slot count is enabled, the available slot count is not applied to the PUSCH; For the second type of repetition, the repetition includes nominal repetition and / or actual repetition.

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

12. The apparatus of claim 1, wherein, For the PUSCH having the second type of repetition: The actual repetition is determined according to the first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration and / or the SSB; The first time domain resource and / or the second time domain resource and / or the invalid time domain resource type and / or the valid time domain resource type and / or the uplink-downlink configuration and / or the SSB are used to determine the invalid time domain resource; When not having the invalid time domain resource type, the actual repetition overlapping both the first time domain resource and the second time domain resource is not transmitted.

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

14. The apparatus of claim 13, wherein, For the second time domain resource, a first starting RB indicated by third information is applied; For the first time domain resource, a second starting RB is applied, the second starting RB is the same as the first starting RB or is offset from the first starting RB and / or determined by the first starting RB and / or the uplink BWP bandwidth and / or the bandwidth of the uplink available resource.

15. The apparatus of claim 13, wherein, For the second time domain resource, a first frequency hopping offset is applied; and / or, for the first time domain resource, the first frequency hopping offset or a second frequency hopping offset is applied or no frequency hopping offset is applied.

16. The apparatus of claim 15, wherein, For the second time-domain resource, a third starting RB corresponding to the frequency hopping offset is determined according to the first starting RB and the bandwidth / size of the BWP; For the first time-domain resource, a fourth starting RB corresponding to the frequency hopping offset is determined according to the second starting RB and the bandwidth / size of the first frequency-domain resource.

17. The apparatus of claim 1, wherein, A transport block size corresponding to the PUSCH is determined according to the allocated frequency-domain resource within the first frequency-domain resource or according to the allocated frequency-domain resource. The transport block size is determined according to the allocated frequency-domain resource within the first frequency-domain resource or according to the allocated frequency-domain resource. The transport block size is related to the valid time-domain resource type and / or the invalid time-domain resource type and / or the resource allocation type.

18. The apparatus of claim 17, wherein, The transport block size is determined according to the allocated frequency-domain resource within the first frequency-domain resource or according to the allocated frequency-domain resource when the first time-domain resource is the invalid time-domain resource type, and / or the transport block size is determined according to the allocated frequency-domain resource when the first time-domain resource is not the invalid time-domain resource type. And / or The transport block size is determined according to the allocated frequency-domain resource within the first frequency-domain resource for the first resource allocation type and according to the allocated frequency-domain resource for the second resource allocation type when the first time-domain resource is the invalid time-domain resource type.

19. A PUSCH receiving apparatus, comprising: a transmitter that transmits a CG configuration 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 a receiver that receives a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes a first type of repetition or a second type of repetition, or the PUSCH has no repetition and multi-slot TB.

20. A communication system, comprising: a network device that transmits a CG configuration and information at least for configuring a first time-domain resource and / or a second time-domain resource; and receives a PUSCH corresponding to the CG configuration; 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; a terminal device that receives a CG configuration and information at least for configuring a first time-domain resource and / or a second time-domain resource; and transmits a PUSCH corresponding to the CG configuration; wherein the PUSCH has repetition and / or multi-slot TB, the repetition includes a first type of repetition or a second type of repetition, or the PUSCH has no repetition and multi-slot TB.

Images