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

Abstract

Provided in the 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 receiving configuration 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 an uplink and a second frequency domain resource is used for a downlink, and the second time domain resource is outside the first time domain resource; receiving a configured grant (CG) configuration, wherein for a CG, whether a CG PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and the terminal device sending one or more CG PUSCHs having a corresponding HARQ process ID.

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, and when a limited or small uplink time period is allocated, there will be problems of small coverage range, small capacity and large latency of uplink. For a frequency division duplex (FDD) frequency band, uplink transmission can only occur in an uplink carrier, and when a limited or small uplink carrier is allocated, there will also be problems of small coverage range, small capacity and large latency of uplink.

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

[0004] SUMMARY

[0005] In order to improve the capacity and coverage of uplink transmission and reduce the latency of uplink transmission, in a TDD frequency band or a downlink frequency band of an FDD frequency band, a network device can work in a full duplex mode at certain time positions, for example, the network device simultaneously receives and transmits in different frequency domain resources in a corresponding carrier (of the TDD frequency band or the downlink frequency band of the FDD frequency band). This working mode is referred to as sub-band non-overlapping full duplex (SBFD) for example, but is not limited thereto. For the convenience of description, the time domain resources in this working mode are referred to as first time domain resources (or also referred to as SBFD symbols), and other time domain resources are referred to as second time domain resources (or also referred to as non-SBFD symbols).

[0006] On the other hand, a plurality of Physical Uplink Shared Channels (PUSCHs) can be scheduled by Configured Grant (CG) information, for example, can be Type 1 CG PUSCH or Type 2 CG PUSCH, and the terminal device can be provided with one or more CG PUSCH configurations, each of which can correspond to a plurality of PUSCHs. For the terminal device, the scheduled PUSCHs can be in SBFD symbols or non-SBFD symbols, and there is currently no solution for how to allocate Hybrid Automatic Repeat reQuest (HARQ) process IDs and how to send / receive these PUSCHs.

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

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

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

[0010] The terminal device receives Configured Grant (CG) configuration, wherein for a Configured Grant, whether one Configured Grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0011] The terminal device sends one or more of the Configured Grant PUSCHs with the corresponding HARQ process ID.

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

[0013] The receiver receives configuration information at least for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource; receives Configured Grant (CG) configuration, wherein for a Configured Grant, whether one Configured Grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0014] a transmitter configured to transmit one or more configured grant PUSCHs with corresponding HARQ process IDs.

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

[0016] a network device configured to transmit configuration 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;

[0017] the network device configured to transmit configured grant (CG) configuration, wherein, for a configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0018] the network device configured to receive one or more configured grant PUSCHs with corresponding HARQ process IDs.

[0019] According to another aspect of embodiments of the present application, a PUSCH receiving apparatus is provided, comprising:

[0020] a transmitter configured to transmit configuration 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 transmit configured grant (CG) configuration, wherein, for a configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0021] a receiver configured to receive one or more configured grant PUSCHs with corresponding HARQ process IDs.

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

[0023] A terminal device receives configuration information at least for configuring a first time domain resource and / or a second time domain resource; wherein at the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is out of the first time domain resource; receives a configured grant (CG) configuration, wherein for a configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and transmits one or more of the configured grant PUSCHs with the corresponding HARQ process ID;

[0024] A network device transmits configuration information at least for configuring a first time domain resource and / or a second time domain resource; transmits a configured grant (CG) configuration; and receives at least one PUSCH from the terminal device.

[0025] One of the beneficial effects of the embodiments of the present application is that the terminal device transmits one or more of the configured grant PUSCHs with the corresponding HARQ process ID; wherein for a configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. Thus, the network device can work in full duplex mode (receiving and transmitting at the same time), and the terminal device can also utilize the corresponding resources to transceive signals when the network device works in full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the flexibility of resource allocation and resource utilization.

[0026] 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. It will be understood that the application is not limited in scope to the specific embodiments disclosed, and that the application is applicable to other embodiments that are within its principles and scope.

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

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

[0029] Elements and features depicted in one drawing or embodiment of the application can be combined with elements and features depicted in one or more other drawings or embodiments, as

[0030] 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 taken without departing from the scope of the application, and that the drawings are merely representative and are not intended as an definition of the limits of the application. In the drawings:

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

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

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

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

[0035] FIG. 5 is another example diagram of uplink available PRBs according to an embodiment of the application;

[0036] FIG. 6 is another example diagram of uplink available PRBs according to an embodiment of the application;

[0037] FIG. 7 is an example diagram of downlink available PRBs according to an embodiment of the application;

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

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

[0040] FIG. 10 is an example diagram of PUSCH scheduling according to an embodiment of the application;

[0041] FIG. 11 is another example diagram of PUSCH scheduling according to an embodiment of the application;

[0042] FIG. 12 is another example diagram of PUSCH scheduling according to an embodiment of the application;

[0043] FIG. 13 is another example diagram of PUSCH scheduling according to an embodiment of the application;

[0044] FIG. 14 is an example diagram of PUSCH transmission according to an embodiment of the application;

[0045] FIG. 15 is another example diagram of PUSCH being transmitted according to an embodiment of the present application;

[0046] FIG. 16 is another example diagram of PUSCH being transmitted according to an embodiment of the present application;

[0047] FIG. 17 is another example diagram of PUSCH being transmitted according to an embodiment of the present application;

[0048] FIG. 18 is another example diagram of PUSCH being transmitted according to an embodiment of the present application;

[0049] FIG. 19 is another example diagram of PUSCH being transmitted according to an embodiment of the present application;

[0050] FIG. 20 is another example diagram of PUSCH being transmitted according to an embodiment of the present application;

[0051] FIG. 21 is another example diagram of PUSCH being transmitted according to an embodiment of the present application;

[0052] FIG. 22 is a schematic diagram of a method for receiving PUSCH according to an embodiment of the present application;

[0053] FIG. 23 is a schematic diagram of a device for transmitting PUSCH according to an embodiment of the present application;

[0054] FIG. 24 is a schematic diagram of a device for receiving PUSCH according to an embodiment of the present application;

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

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

[0057] The foregoing and other features of the present application will become apparent to those skilled in the art upon consideration of the following description of specific embodiments of the present application, taken in conjunction with the accompanying drawings. In the description of embodiments of the present application, specific terminology is employed for the sake of clarity. However, the application is not intended to be limited to the specific embodiments described, but rather, is intended to include all modifications, equivalents, and alternatives that fall within the scope of the appended claims.

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

[0059] In the embodiments of the present application, the singular form "a", "an" and "the" include the plural form, should be broadly understood as "one" or "a kind of", and not limited to the meaning of "one"; in addition, the term "said" should be understood to include 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.

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

[0061] 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 protocol.

[0062] In the 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), etc.

[0063] A base station can include, but is not limited to, a NodeB (or NB), an evolved NodeB (or eNB), and a 5G base station (or gNB), an 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 (e.g., a femto, a pico, and the like). Also, the term "base station" can include some or all functions of them, 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.

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

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

[0066] For another example, in an Internet of Things (IoT) scenario or the like, the terminal equipment can also be a machine or device that performs monitoring or measurement, which can include, but is not limited to, the following devices: a machine type communication (MTC) terminal, a vehicle-mounted communication terminal, a device to device (D2D) terminal, a machine to machine (M2M) terminal, and the like.

[0067] 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 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 above. In this article, "device" can refer to network device or terminal device without special indication.

[0068] In the following description, the terms "uplink control signal" and "uplink control information (UCI, Uplink Control Information)" or "physical uplink control channel (PUCCH, Physical Uplink Control Channel)" can be interchangeable without causing confusion, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH, Physical Uplink Shared Channel)" can be interchangeable;

[0069] The terms "downlink control signal" and "downlink control information (DCI, Downlink Control Information)" or "physical downlink control channel (PDCCH, Physical Downlink Control Channel)" can be interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH, Physical Downlink Shared Channel)" can be interchangeable.

[0070] In addition, the uplink signal can include uplink data signal and / or uplink control signal and / or PRACH and / or SRS, etc., and can also be referred to as uplink transmission (UL transmission) or uplink information or 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 downlink data signal and / or downlink control signal and / or synchronization signal (SS, such as PSS / SSS) and / or broadcast channel (PBCH) and / or SSB (SS / PBCH block, including PSS, SSS and PBCH and its DMRS) and / or CSI-RS, etc., and can also be referred to as downlink transmission (DL transmission) or downlink information or downlink channel. Transmitting / receiving the downlink transmission on the downlink resource can be understood as transmitting / receiving the downlink transmission using the downlink resource.

[0071] In embodiments of the present application, the high layer signaling may, for example, be radio resource control (RRC) signaling; the RRC signaling may, for example, include RRC messages (RRC message), such as broadcast / common RRC messages / signaling (e.g., master information block (MIB), system information), dedicated RRC messages / signaling; or RRC information elements (RRC IE); or information fields included in the RRC messages or RRC information elements (or information fields included in the information fields). The high layer signaling may, for example, also be medium access control (MAC) signaling; or be referred to as a MAC control element (MAC CE). However, the present application is not limited thereto. The names of the signaling (e.g., RRC messages, information element (IE), information field, high layer parameter, etc.) used in embodiments of the present application are merely examples, and other names may also be used, and embodiments of the present application are not limited thereto.

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

[0073] In 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 directly or indirectly configured / indicated by a network device through high layer signaling and / or physical layer signaling. The configuration / indication may, for example, be configured / indicated by introducing a high layer parameter in the high layer signaling, where the high layer parameter means a field and / or information element / unit / element (IE) in the high layer signaling. The physical layer signaling may, for example, be control information (DCI) carried by a physical downlink control channel or control information carried by a sequence, but is not limited thereto.

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

[0075] The scenarios of the embodiments of the present application are described below by way of examples, but the present application is not limited thereto.

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

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

[0078] 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., so that the terminal device 102 can confirm the end of the transmission process, or can further perform new data transmission, or can perform data retransmission.

[0079] Among them, the network device 101 can use unicast or groupcast or broadcast mode to send data to the terminal device 102 and / or the terminal device 103. The terminal device 102 can receive data sent by one or more network devices (such as dual connectivity or multi-connectivity) through the downlink or the terminal device 103 through the sidelink.

[0080] 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 while the other terminal device 103 is outside the coverage of the network device 101.

[0081] In the following description, transmitting or receiving a PUCCH can be understood as transmitting or receiving uplink control information carried by the PUCCH; transmitting or receiving a PUSCH can be understood as transmitting or receiving uplink data carried by the PUSCH. In addition, the content in the brackets is explanatory or optional, " / " means "and / or", and the application is not limited thereto. Various embodiments of the embodiments of the application will be described below in conjunction with the accompanying drawings. These embodiments are only exemplary and not limiting to the application.

[0082] Embodiments of the first aspect

[0083] Embodiments of the application provide a PUSCH transmission method, which is described from the terminal device side.

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

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

[0086] 202, the terminal device receives a configuration grant (CG) configuration, wherein for a configuration grant, whether one configuration grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0087] 203, the terminal device transmits one or more configuration grant PUSCHs with a corresponding HARQ process ID.

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

[0089] In some embodiments, the terminal device can be an SBFD-aware device; the application is not limited thereto. For example, in the initial access process and / or in the random access process and / or in the capability information reporting, the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE).

[0090] For example, the SBFD-aware UE has capability related to SBFD operation, including one or more of the following: capable of knowing SBFD configuration, e.g., configuration of SBFD time domain resource (e.g., SBFD symbol) and frequency domain resource (e.g., UL subband / UL usable RBs, DL subband / DL usable RBs); capable of transmitting uplink signal on (DL) SBFD symbol.

[0091] The time domain resource related to the embodiments of the present application is first schematically described below.

[0092] In some embodiments, the first time domain resource is a time domain resource for (supporting) full duplex (e.g., SBFD) operation, the second time domain resource is a time domain resource not for (supporting) full duplex operation (or, not for full duplex operation, e.g., non-SBFD), and the time locations of the first time domain resource and the second time domain resource are different.

[0093] In some embodiments, in the first time domain resource, the network device simultaneously receives and transmits in different frequency domain resources in a corresponding carrier (of a TDD frequency band or a downlink frequency band of an FDD frequency band), and in the second time domain resource, the network device only receives or transmits in the carrier.

[0094] In some embodiments, the first time domain resource refers to a time domain resource with / corresponding to SBFD subbands, or a time domain resource in which SBFD subbands are located, and the second time domain resource refers to a time domain resource without / corresponding to SBFD subbands. The SBFD subbands include DL subband(s) and / or uplink subband(s), for example.

[0095] In some embodiments, the time resource unit includes, but is not limited to, a symbol, a slot, a sub-slot, a mini-slot, a symbol group, a slot group, a subframe, a frame, a ms, a s, etc. For example, the number of symbols included in a sub-slot or a mini-slot is less than or equal to the number of slots included in a slot, a symbol group includes one or more (continuous or discontinuous) symbols, and a slot group includes one or more (continuous or discontinuous) slots, but is not limited thereto.

[0096] In some embodiments, the first time domain resource, for example, can also be referred to as SBFD resource, and the second time domain resource, for example, can also be referred to as non-SBFD resource. The SBFD resource, for example, includes SBFD time resource units, such as SBFD time slots and / or symbols, and the non-SBFD resource, for example, includes non-SBFD time resource units, such as non-SBFD time slots and / or symbols.

[0097] In some embodiments, a downlink symbol, for example, is a symbol configured as downlink by tdd-UL-DL-ConfigurationCommon, an uplink symbol, for example, is a symbol configured as uplink by tdd-UL-DL-ConfigurationCommon, a flexible symbol, for example, is a symbol neither configured as downlink nor configured as uplink by tdd-UL-DL-ConfigurationCommon, or is a symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, or is a symbol configured as flexible by tdd-UL-DL-ConfigurationCommon when tdd-UL-DL-ConfigurationCommon is provided, or is all symbols when tdd-UL-DL-ConfigurationCommon is not provided (no uplink / downlink subband is configured).

[0098] In some embodiments, a SBFD symbol, for example, is a symbol with SBFD / DL / UL subbands, for example, including DL SBFD symbol and / or Flexible SBFD symbol, but not limited thereto. For example, when only one TDD-UL-DL pattern is configured, the period is the same as the TDD-UL-DL pattern period configured by dl-UL-Transmission Periodicity in TDD-UL-DL-ConfigCommon; when two TDD-UL-DL patterns are configured, the period is the same as the sum of the two TDD-UL-DL pattern periods configured by dl-UL-Transmission Periodicity in TDD-UL-DL-ConfigCommon.

[0099] In some embodiments, the non-SBFD symbol is a symbol other than the SBFD symbol, or, a symbol other than the SBFD symbol and the first gap symbol, e.g., a symbol without SBFD / DL / UL subbands. For example, including a Full-DL symbol, and / or, a Full-UL symbol, and / or, a Full-flexible symbol, and / or, the first gap symbol; wherein the first gap symbol is a gap symbol between the non-SBFD symbol and the SBFD symbol, but not limited thereto.

[0100] In some embodiments, the DL SBFD symbol / SBFD DL symbol is a SBFD symbol configured within a DL symbol, or, a SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon.

[0101] In some embodiments, the Flexible SBFD symbol / SBFD Flexible symbol is a SBFD symbol configured within a Flexible symbol, or, a SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon.

[0102] In some embodiments, the Full-DL symbol / DL-only symbol / DL non-SBFD symbol / non-SBFD DL symbol is a non-SBFD symbol configured within a DL symbol, or, a non-SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon.

[0103] In some embodiments, the Full-UL symbol is equivalent to a UL symbol, assuming that a SBFD symbol will not be configured in a UL symbol.

[0104] In some embodiments, the Full-UL symbol / UL-only symbol / UL non-SBFD symbol / non-SBFD UL symbol is a non-SBFD symbol configured within a UL symbol, or, a non-SBFD symbol configured as uplink by tdd-UL-DL-ConfigurationCommon.

[0105] In some embodiments, a Full-flexible symbol / Flexible-only symbol / Flexible non-SBFD symbol / non-SBFD Flexible symbol is a symbol that is configured within a flexible symbol, or a non-SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, or a non-SBFD symbol that is neither configured as downlink by tdd-UL-DL-ConfigurationCommon nor configured as uplink by tdd-UL-DL-ConfigurationCommon, or a non-SBFD symbol configured as flexible. The meaning of flexible symbol can also refer to the aforementioned embodiments.

[0106] In some embodiments, a slot can include SBFD symbols and non-SBFD symbols, or only SBFD symbols, or only non-SBFD symbols.

[0107] 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. FIG. 3 exemplarily illustrates time domain resources according to embodiments of the present disclosure, but is not limited thereto.

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

[0109] In the first time domain resource, the first frequency domain resource is for uplink and the second frequency domain resource is for downlink. For example, the first frequency domain resource is an uplink subband (UL subband) in a SBFD symbol, and the second frequency domain resource is a downlink subband (DL subband) in the SBFD symbol. The terms "subband" and "frequency domain resource unit set" can be interchangeable.

[0110] In some embodiments, the first frequency domain resource and the second frequency domain resource are in a time division duplex (TDD) frequency band (or uppaired spectrum), or in a downlink frequency band of a frequency division duplex (FDD) frequency band (paired spectrum), or in an uplink frequency band of the FDD frequency band, or in a supplementary uplink (SUL) frequency band.

[0111] In some embodiments, for UL, the cell-specific frequency location of UL subband, or in other words, the cell-specific UL subband, can be configured separately for each SCS (in SCS-SpecificCarrierList for UL). For each SCS configuration, the reference starting PRB is the PRB determined by the SCS configuration and offsetToCarrier corresponding to this subcarrier spacing, for example, one / at most one UL subband can be configured, but not limited thereto.

[0112] In some embodiments, for UL BWP, the uplink usable PRBs / RBs can be determined as the intersection between the (cell-specific) UL subband and the UL BWP (in SBFD symbols), i.e., implicitly configured, for example, referred to as first uplink usable PRBs.

[0113] In some embodiments, for one UL BWP, the uplink usable PRBs are determined according to the UL subband configured for the same SCS as the SCS of the UL BWP. For example, if the SCS of one UL BWP is 15 kHz, the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband configured for 15 kHz SCS. If the SCS of one UL BWP is 30 kHz, the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband configured for 30 kHz SCS.

[0114] FIG. 4 is an example diagram of uplink usable PRBs according to an embodiment of the present application. As shown in FIG. 4, the UL BWP and the UL subband overlap, and the UL usable PRBs are the intersection between the two (in SBFD symbols).

[0115] FIG. 5 is another example diagram of uplink usable PRBs according to an embodiment of the present application. As shown in FIG. 5, the UL BWP includes the UL subband in the frequency domain, and the UL usable PRBs are the intersection between the two (in SBFD symbols).

[0116] In FIGS. 4 and 5, the UL subband therein represents, for example, the uplink subband configured for the SCS corresponding to the UL BWP, but the present application is not limited thereto.

[0117] In some embodiments, for UL BWP, the uplink usable PRBs / RBs can be explicitly configured in the UL BWP (in SBFD symbols), for example, referred to as second uplink usable PRBs.

[0118] In some embodiments, when configured with both the first uplink available PRBs and the second uplink available PRBs, the second uplink available PRBs are employed.

[0119] In some embodiments, the second uplink available PRBs are configured based on the first uplink available PRBs. For example, the second uplink available PRBs include PRBs other than unavailable PRBs in the first uplink available PRBs. For another example, the second uplink available PRBs include the first uplink available PRBs and other available PRBs other than the first uplink available PRBs.

[0120] FIG. 6 is another example diagram of uplink available PRBs according to embodiments of the present disclosure. As shown in FIG. 6, the UL usable PRBs are explicitly configured in the UL BWP.

[0121] In some embodiments, for DL, the cell-specific frequency locations of DL subbands can be configured separately for each SCS (in SCS-SpecificCarrierList), or in other words, the cell-specific UL subbands are configured separately for each SCS. For each SCS configuration, the reference starting PRB is the PRB determined by the SCS configuration and the offsetToCarrier corresponding to the subcarrier spacing, and for example, one / two DL subbands can be configured, but the disclosure is not limited thereto.

[0122] In some embodiments, for the downlink available PRBs / RBs (DL usable PRBs / RBs) of a DL BWP, the intersection between the (cell-specific) DL subbands and the DL BWP (in SBFD symbols) can be determined, or in other words, the DL usable PRBs are implicitly configured, for example, referred to as the first downlink available PRBs.

[0123] In some embodiments, the downlink available PRBs of a DL BWP are determined according to the UL subbands configured for the same SCS as the SCS of the DL BWP. For example, if the SCS of a DL BWP is 15 kHz, the corresponding DL available PRBs are the intersection between the DL BWP and the downlink subbands configured for the SCS of 15 kHz. If the SCS of a DL BWP is 30 kHz, the corresponding DL available PRBs are the intersection between the DL BWP and the downlink subbands configured for the SCS of 30 kHz.

[0124] FIG. 7 is an example diagram of downlink usable PRBs in an embodiment of the present application, as shown in FIG. 7, the DL BWP and the DL subband overlap, and the DL usable PRBs are the intersection between the two (in the SBFD symbol).

[0125] FIG. 8 is another example diagram of downlink usable PRBs in an embodiment of the present application, as shown in FIG. 8, the DL BWP includes the DL subband in the frequency domain, and the DL usable PRBs are the intersection between the two (in the SBFD symbol).

[0126] In FIG. 7 and FIG. 8, the DL subband therein represents, for example, a downlink subband configured with a SCS corresponding to the DL BWP, but the present application is not limited thereto.

[0127] In some embodiments, for the downlink usable PRBs / RBs of the DL BWP, the second downlink usable PRBs can be explicitly configured in the DL BWP (in the SBFD symbol), for example, referred to as the second downlink usable PRBs.

[0128] In some embodiments, when the first downlink usable PRBs and the second downlink usable PRBs are configured at the same time, the second downlink usable PRBs are adopted.

[0129] In some embodiments, the second downlink usable PRBs are configured based on the first downlink usable PRBs. For example, the PRBs that are not available in the first downlink usable PRBs are configured, and the second downlink usable PRBs include the PRBs in the first downlink usable PRBs except the PRBs that are not available. For another example, other available PRBs in addition to the first downlink usable PRBs are configured, and the second downlink usable PRBs include the first downlink usable PRBs and the other available PRBs.

[0130] FIG. 9 is another example diagram of downlink usable PRBs in an embodiment of the present application, as shown in FIG. 9, the DL usable PRBs are explicitly configured in the DL BWP.

[0131] The time-frequency resources are described above, and the PUSCH in an embodiment of the present application is described below.

[0132] In an embodiment 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 and periodically or semi-persistently schedules the 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, but the present application is not limited thereto.

[0133] 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 (configuredGrantConfig including 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 an active DCI (used to activate the second configured grant) after receiving a second higher layer parameter (configuredGrantConfig not including rrc-Configured UplinkGrant).

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

[0135] In some embodiments, for Type1 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.

[0136] The following is described for one CG PUSCH configuration. The positions of CG PUSCHs in the same or different periods corresponding to one CG PUSCH configuration can be divided into the following cases:

[0137] --all in SBFD symbols, i.e., none overlapping with non-SBFD symbols;

[0138] --all in non-SBFD symbols, i.e., none overlapping with SBFD symbols;

[0139] -- the PUSCH in SBFD symbols and the PUSCH in non-SBFD symbols, excluding the PUSCH that is overlapped with both SBFD symbols and non-SBFD symbols;

[0140] -- the PUSCH that is overlapped with both SBFD symbols and non-SBFD symbols, including or excluding the PUSCH in SBFD symbols and / or the PUSCH in non-SBFD symbols.

[0141] It is worth noting that the above division is made for the convenience of description, but the present application is not limited thereto. For example, only part of the above cases can be included, two or more cases can be combined, and other cases can be added.

[0142] In some embodiments, frequency domain resource allocation (FDRA) can be provided separately for the PUSCH that is overlapped with SBFD symbols and the PUSCH in non-SBFD symbols. Among them, the PUSCH that is overlapped with SBFD symbols includes the PUSCH in SBFD symbols and / or the PUSCH that part of which is in SBFD symbols and part of which is in non-SBFD symbols.

[0143] For example, separate FDRA configurations / indications / interpretations can be provided for SBFD symbols and non-SBFD symbols, respectively. For example, for CG Type1, one frequencyDomainAllocation field is included in the CG configuration, and for CG Type2, one FDRA field is included in the DCI used to activate the CG, and accordingly, the UE determines the frequency domain resources of the PUSCH that is overlapped with SBFD symbols and the frequency domain resources of the PUSCH in non-SBFD symbols according to the same information field. For another example, for CG Type1, two frequencyDomainAllocation fields are included in the CG configuration, and for CG Type2, two FDRA fields are included in the DCI used to activate the CG, and the two fields respectively indicate the frequency domain resources of the PUSCH that is overlapped with SBFD symbols and the frequency domain resources of the PUSCH in non-SBFD symbols.

[0144] For example, a FDRA configuration / indication is provided for one symbol type (SBFD symbol or non-SBFD symbol), and RB offset(s) configuration / indication / determination is used to determine the resource for other symbol type(s). For example, for CG Type1, a frequencyDomainAllocation field is included in the CG configuration, and for CG Type2, a FDRA field is included in the DCI used to activate the CG to indicate the frequency domain resource for PUSCH in non-SBFD symbol. For PUSCH overlapping with SBFD symbol, the UE determines the frequency domain resource according to the RB offset(s) between the (start PRB of) UL usable PRBs and the (start PRB of) corresponding UL BWP. Or, the UE determines the frequency domain resource for PUSCH overlapping with SBFD symbol according to the RB offset(s) between the (start PRB of) PUSCH overlapping with SBFD symbol and the (start PRB of) frequency domain resource for PUSCH in non-SBFD symbol, which is indicated by the base station (e.g. through higher layer signaling or the DCI).

[0145] For example, a common FDRA configuration / indication is provided, and for PUSCH overlapping with RBs outside of UL usable PRBs in SBFD symbol, only the allocated PRBs within UL usable PRBs are considered valid. For example, for CG Type1, a frequencyDomainAllocation field is included in the CG configuration, and for CG Type2, a FDRA field is included in the DCI used to activate the CG, which is applied to all PUSCH corresponding to the corresponding CG configuration, that is, the same frequency domain resource is indicated for all CG PUSCH, but for PUSCH overlapping with SBFD symbol, the part of resource outside of UL usable PRBs is invalid.

[0146] For example, a common FDRA configuration / indication is provided, and for PUSCH overlapping with RBs outside of UL usable PRBs in SBFD symbol, only the allocated PRBs within UL usable PRBs are considered valid. For example, for CG Type1, a frequencyDomainAllocation field is included in the CG configuration, and for CG Type2, a FDRA field is included in the DCI used to activate the CG, which is applied to all PUSCH corresponding to the corresponding CG configuration, that is, the same frequency domain resource is indicated for all CG PUSCH, but for PUSCH overlapping with SBFD symbol, the part of resource outside of UL usable PRBs is invalid.

[0147] Figure 11 is another example diagram of PUSCH scheduling according to embodiments of the present application. As shown in Figure 11, for example, the resources of PUSCH 1 to PUSCH 4 can all be provided by FDRA configuration / indications, but the part of resources of PUSCH 2 and PUSCH 3 outside the UL available PRBs are invalid.

[0148] In some embodiments, a common frequency domain resource allocation (FDRA) can be provided for PUSCHs overlapping with SBFD symbols and PUSCHs in non-SBFD symbols. For example, for CG Type1, a frequencyDomainAllocation field is included in the CG configuration, and for CG Type2, a FDRA field is included in the DCI used to activate the CG, which applies to all PUSCHs corresponding to the corresponding CG configuration, that is, the frequency domain resources indicated for all CG PUSCHs are the same.

[0149] For example, the gNB does not schedule any PUSCH in the SBFD symbols of a slot to overlap with PRBs outside the UL available PRBs, or the UE does not expect any PUSCH in the SBFD symbols of a slot to overlap with PRBs outside the UL available PRBs.

[0150] Figure 12 is another example diagram of PUSCH scheduling according to embodiments of the present application. As shown in Figure 12, none of the PUSCHs (e.g., PUSCH 2 and PUSCH 3) in the SBFD symbols overlap with PRBs outside the UL available PRBs.

[0151] For another example, the gNB can schedule the PUSCHs overlapping with the SBFD symbols to overlap with PRBs outside the UL available PRBs.

[0152] Figure 13 is another example diagram of PUSCH scheduling according to embodiments of the present application. As shown in Figure 13, the PUSCHs (e.g., PUSCH 2 and PUSCH 3) in the SBFD symbols are scheduled to overlap with PRBs outside the UL available PRBs. Whether these PUSCHs are actually transmitted or not, for example, can be determined by the terminal device.

[0153] The above illustrates PUSCH scheduling schematically, and the following further illustrates how the terminal device transmits the PUSCH. In the following description, the terminal device side “transmits the PUSCH” is taken as an example for illustration, and the network device side “receives the PUSCH” can also be taken as an example for illustration.

[0154] In the embodiments of the present application, the X information can be used to indicate the link direction (DL / UL) of the SBFD symbol, and can be tdd-UL-DL-ConfigurationDedicated, but is not limited thereto, and can also be other information, for example. The Y information can be used to indicate the link direction of the (flexible) non-SBFD symbol, and can be tdd-UL-DL-ConfigurationDedicated, but is not limited thereto, and can also be other information, for example.

[0155] In some embodiments, the PUSCH transmission is restricted in the first time domain resource (SBFD symbol), and the terminal device can only send the PUSCH in the first time domain resource, and cannot / is not allowed to send the PUSCH overlapping the second time domain resource in the multiple PUSCHs, and the PUSCH (in the PUSCH with the corresponding HARQ-process ID) overlapping the second time domain resource cannot / is not allowed to be sent. For example, the PUSCH transmissions are restricted to SBFD symbols only (hereinafter referred to as case 1). For this case, the terminal device can perform operation 1 as follows.

[0156] Operation 1:

[0157] The terminal device sends the PUSCH as follows: not overlapping with the SSB symbol, and / or not overlapping with the second time domain resource (non-SBFD symbol), and / or in the first time domain resource (SBFD symbol) and not overlapping with the PRB outside the uplink available PRB (UL usable PRB) (or the first frequency domain resource), and / or not overlapping with the symbol indicated as downlink by the indicated information (X information),

[0158] and / or,

[0159] The terminal device does not send the PUSCH as follows: overlapping with the SSB symbol, and / or overlapping with the second time domain resource (non-SBFD symbol), and / or in the first time domain resource (SBFD symbol) and overlapping with the PRB outside the uplink available PRB (UL usable PRB), and / or overlapping with the symbol indicated as downlink by the indicated information (X information);

[0160] and / or,

[0161] The terminal device does not expect PUSCH in the first time-domain resource (SBFD symbol) overlapping with PRBs outside of the uplink usable PRBs (UL usable PRBs), and / or, the terminal device does not expect PUSCH overlapping both the first time-domain resource (SBFD symbol) and the second time-domain resource (non-SBFD symbol).

[0162] For example, assuming that PUSCH in SBFD symbols can overlap with RBs outside of the UL usable RBs, the UE does not transmit PUSCH overlapping SSB and / or non-SBFD symbols, and / or, PUSCH overlapping SBFD symbols and RBs outside of the UL usable RBs (including PUSCH in SBFD symbols and overlapping SSB), and / or, the UE only transmits PUSCH in SBFD symbols and not overlapping SSB and not overlapping RBs outside of the UL usable RBs.

[0163] For another example, assuming that PUSCH in SBFD symbols must be within the UL usable RBs (e.g., gNB does not schedule PUSCH overlapping SBFD symbols and RBs outside of the UL usable RBs, or, the UE does not expect PUSCH overlapping SBFD symbols and RBs outside of the UL usable RBs), the UE does not transmit PUSCH overlapping SSB and / or non-SBFD symbols, and / or, the UE only transmits PUSCH in SBFD symbols and not overlapping SSB.

[0164] FIG. 14 is an example diagram of PUSCH transmissions according to an embodiment of the present application. As shown in FIG. 14, the terminal device only transmits PUSCH in SBFD symbols and not overlapping SSB (i.e., PUSCH 2), and PUSCH 1, PUSCH 3 and PUSCH 4 are not transmitted.

[0165] In some embodiments, the PUSCH transmissions are restricted in the second time-domain resource (non-SBFD symbols), that is, the terminal device can only transmit PUSCH in the second time-domain resource, and is not allowed to transmit PUSCH overlapping the first time-domain resource, (of the PUSCHs with corresponding HARQ-process IDs) the PUSCH overlapping the first time-domain resource is not allowed to be transmitted. For example, the PUSCH transmissions are restricted to non-SBFD symbols only (hereinafter referred to as case 2). For this case, the terminal device can perform the following operation 2.

[0166] Operation 2:

[0167] The terminal device transmits PUSCH as follows: not overlapping with SSB, and / or, not overlapping with the first time domain resource (SBFD symbol), and / or, not overlapping with the second time domain resource (non-SBFD symbol) for downlink, and / or, not overlapping with the symbol indicated as downlink by the indicated information (Y information);

[0168] and / or,

[0169] The terminal device does not transmit PUSCH as follows: overlapping with SSB, and / or, overlapping with the first time domain resource (SBFD symbol), and / or, overlapping with the second time domain resource (non-SBFD symbol) for downlink, and / or, overlapping with the symbol indicated as downlink by the indicated information (Y information);

[0170] and / or,

[0171] The terminal device does not expect there to be PUSCH overlapping both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0172] For example, the UE does not transmit PUSCH overlapping with SBFD symbol and / or SSB and / or DL non-SBFD symbol and / or the symbol indicated as downlink by Y information, and / or, the UE only transmits PUSCH in non-SBFD symbol and not overlapping with SSB and / or DL non-SBFD symbol and / or the symbol indicated as downlink by Y information.

[0173] FIG. 15 is another example diagram of PUSCH being transmitted according to an embodiment of the present application, as shown in FIG. 15, the terminal device transmits PUSCH (i.e., PUSCH 4) in non-SBFD symbol and not overlapping with SSB and / or DL non-SBFD symbol and / or the symbol indicated as downlink by Y information, while PUSCH 1, PUSCH 2 and PUSCH 3 are not transmitted.

[0174] In some embodiments, the multiple PUSCH transmissions can be in the first time domain resources and the second time domain resources, that is, among the multiple PUSCHs, the terminal device can / is allowed to transmit the PUSCHs (if any) in the first time domain resources and / or the PUSCHs (if any) in the second time domain resources, and is not allowed to transmit the PUSCHs (if any) that overlap both the first time domain resources and the second time domain resources, (among the PUSCHs with corresponding HARQ-process IDs) the PUSCHs that overlap both the first time domain resources and the second time domain resources cannot / be not allowed to be transmitted. For example, the PUSCHs transmissions can be across SBFD symbols and non-SBFD symbols and each has either all SBFD or all non-SBFD symbols (hereinafter referred to as case 3). For this case, the terminal device can perform operation 3 as follows.

[0175] Operation 3:

[0176] The terminal device transmits the PUSCHs that do not overlap with the SSB and / or the second time domain resources for downlink (DL non-SBFD symbols), and / or do not overlap both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or are in the first time domain resources (SBFD symbols) and do not overlap the PRBs other than the uplink usable PRBs (UL usable PRBs) (or the first frequency domain resources), and / or do not overlap the symbols indicated by the indicated information as downlink;

[0177] and / or,

[0178] The terminal device does not transmit the PUSCHs that overlap with the SSB, and / or overlap with the second time domain resources for downlink (DL non-SBFD symbols), and / or overlap both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or are in the first time domain resources (SBFD symbols) and overlap the PRBs other than the uplink usable PRBs (UL usable PRBs) (or the first frequency domain resources), and / or overlap the symbols indicated by the indicated information as downlink;

[0179] and / or,

[0180] The terminal device does not expect PUSCH that overlaps with PRBs outside of the uplink usable PRBs (UL usable PRBs) in the first time domain resource (SBFD symbol) and / or PUSCH that overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0181] For example, assuming that PUSCH in SBFD symbols can overlap with RBs outside of the UL usable RBs, and PUSCH can overlap with both SBFD symbols and non-SBFD symbols, the UE does not transmit PUSCH that overlaps with SSB and / or non-SBFD symbols and / or PUSCH in SBFD symbols and outside of the UL usable RBs (including PUSCH in SBFD symbols and overlapping with SSB) and / or PUSCH that overlaps with both SBFD symbols and non-SBFD symbols, and / or the UE only transmits PUSCH that does not overlap with SSB and / or DL non-SBFD symbols, does not overlap with both SBFD symbols and non-SBFD symbols, and does not overlap with RBs outside of the UL usable RBs when overlapping with SBFD symbols.

[0182] FIG. 16 is another example diagram of PUSCH transmission according to an embodiment of the present application. As shown in FIG. 16, the terminal device only transmits PUSCH (i.e., PUSCH 4) that does not overlap with SSB and / or DL non-SBFD symbols, does not overlap with both SBFD symbols and non-SBFD symbols, and does not overlap with RBs outside of the UL usable RBs when overlapping with SBFD symbols, while PUSCH 1, PUSCH 2, and PUSCH 3 are not transmitted.

[0183] For another example, assuming that PUSCH in SBFD symbols must be within the UL usable RBs (e.g., the gNB does not schedule PUSCH that overlaps with SBFD symbols and outside of the UL usable RBs, or the UE does not expect PUSCH that overlaps with SBFD symbols and outside of the UL usable RBs), and PUSCH can overlap with both SBFD symbols and non-SBFD symbols, the UE does not transmit PUSCH that overlaps with SSB and / or non-SBFD symbols and / or PUSCH that overlaps with both SBFD symbols and non-SBFD symbols, and / or the UE only transmits PUSCH that does not overlap with SSB and / or DL non-SBFD symbols and does not overlap with both SBFD symbols and non-SBFD symbols.

[0184] FIG. 17 is another example diagram of PUSCHs being transmitted according to embodiments of the application, as shown in FIG. 17, the terminal device only transmits PUSCH 2 and PUSCH 4, where part of the RBs of PUSCH 2 are considered invalid; and neither PUSCH 1 nor PUSCH 3 is transmitted.

[0185] For yet another example, assuming that a PUSCH in a SBFD symbol is always within the UL usable RBs (e.g., the gNB does not schedule a PUSCH that overlaps with a SBFD symbol and RBs outside of the UL usable RBs, or the UE does not expect a PUSCH that overlaps with a SBFD symbol and RBs outside of the UL usable RBs), the PUSCH does not overlap with both a SBFD symbol and a non-SBFD symbol (e.g., the UE does not expect a PUSCH that overlaps with both a SBFD symbol and a non-SBFD symbol), the UE does not transmit a PUSCH that overlaps with an SSB and / or a non-SBFD symbol, and / or the UE only transmits a PUSCH that does not overlap with an SSB and / or a DL non-SBFD symbol.

[0186] FIG. 18 is another example diagram of PUSCHs being transmitted according to embodiments of the application, as shown in FIG. 18, the terminal device only transmits PUSCH 2, PUSCH 3, and PUSCH 4, and does not transmit PUSCH 1.

[0187] For yet another example, assuming that a PUSCH in a SBFD symbol can overlap with RBs outside of the UL usable RBs, the PUSCH does not overlap with both a SBFD symbol and a non-SBFD symbol (e.g., the UE does not expect a PUSCH that overlaps with both a SBFD symbol and a non-SBFD symbol), the UE does not transmit a PUSCH that overlaps with an SSB and / or a non-SBFD symbol and / or is in a SBFD symbol and overlaps with RBs outside of the UL usable RBs (including a PUSCH that is in a SBFD symbol and overlaps with an SSB), and / or the UE only transmits a PUSCH that does not overlap with an SSB and / or a DL non-SBFD symbol, when overlapping with a SBFD symbol, does not overlap with RBs outside of the UL usable RBs.

[0188] FIG. 19 is another example diagram of PUSCHs being transmitted according to embodiments of the application, as shown in FIG. 19, the terminal device only transmits PUSCH 3 and PUSCH 4, and does not transmit PUSCH 1, PUSCH 2.

[0189] In some embodiments, the plurality of PUSCH transmissions can be in the first time domain resources and the second time domain resources, and include a case that the PUSCH transmissions overlap with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), or in other words, the PUSCHs in the plurality of PUSCHs that overlap with both the first time domain resources and the second time domain resources can be transmitted. That is, among the plurality of PUSCHs, the terminal device can be allowed to transmit the PUSCHs in the first time domain resources (if any), and / or the PUSCHs in the second time domain resources (if any), and / or the PUSCHs that overlap with both the first time domain resources and the second time domain resources (if any). For example, the PUSCH transmissions can be across SBFD symbols and non-SBFD symbols, include a PUSCH overlapping with both SBFD symbols and non-SBFD symbols (hereinafter referred to as case 4). For this case, the terminal device can perform operation 4 as follows.

[0190] Operation 4:

[0191] The terminal device transmits the PUSCHs that do not overlap with SSBs and / or the second time domain resources for downlink (DL non-SBFD symbols), and / or overlap with the first time domain resources (SBFD symbols) and do not overlap with PRBs other than the uplink usable PRBs (UL usable PRBs), and / or do not overlap with the symbols indicated by the indicated information as downlink;

[0192] and / or,

[0193] The terminal device does not transmit the PUSCHs that overlap with SSBs, and / or overlap with the second time domain resources for downlink (DL non-SBFD symbols), and / or overlap with the first time domain resources (SBFD symbols) and overlap with PRBs other than the uplink usable PRBs (UL usable PRBs), and / or overlap with the symbols indicated by the indicated information as downlink;

[0194] and / or,

[0195] The terminal device does not expect to exist the PUSCHs that overlap with the first time domain resources (SBFD symbols) and overlap with PRBs other than the uplink usable PRBs (UL usable PRBs).

[0196] For example, assuming that PUSCHs overlapping with SBFD symbols can overlap with RBs outside of UL usable RBs (e.g., alternatively, overlap with the boundaries of UL usable RBs), the UE does not transmit PUSCHs overlapping with SSBs and / or DL non-SBFD symbols and / or overlapping with SBFD symbols and overlapping with RBs outside of UL usable RBs, and / or, the UE only transmits PUSCHs not overlapping with SSBs and / or DL non-SBFD symbols and, when overlapping with SBFD symbols, not overlapping with RBs outside of UL usable RBs.

[0197] FIG. 20 is another example diagram of PUSCHs being transmitted according to embodiments of the application, as shown in FIG. 20, the terminal device only transmits PUSCH 4, and PUSCH 1, PUSCH 2, and PUSCH 3 are not transmitted.

[0198] For example, assuming that PUSCHs overlapping with SBFD symbols must be within UL usable RBs (e.g., gNB does not schedule PUSCHs overlapping with SBFD symbols and overlapping with RBs outside of UL usable RBs, or alternatively, the UE does not expect PUSCHs overlapping with SBFD symbols and overlapping with RBs outside of UL usable RBs to exist), the UE does not transmit PUSCHs overlapping with SSBs and / or DL non-SBFD symbols, and / or, the UE only transmits PUSCHs not overlapping with SSBs and / or DL non-SBFD symbols.

[0199] FIG. 21 is another example diagram of PUSCHs being transmitted according to embodiments of the application, as shown in FIG. 21, the terminal device only transmits PUSCH 2, PUSCH 3, and PUSCH 4, where part of the RBs of PUSCH 2 and PUSCH 3 are considered invalid; and PUSCH 1 is not transmitted.

[0200] The above illustrates the cases in which PUSCHs are transmitted, where case 1 to case 4 and operation 1 to operation 4 are only classifications for convenience of explanation, and the application is not limited to these classifications. The application is further described below.

[0201] In some embodiments, the capability of the terminal device includes whether one or more of case 1 to case 4 or one or more of operation 1 to operation 4 is supported. For example, the terminal device supports case 1 and case 2, or alternatively, operation 1 and operation 2, and optionally supports case 3 and / or case 4, or alternatively, operation 3 and / or operation 4. When the terminal device supports operation 3 and / or operation 4, the corresponding capability information is reported, otherwise it is not reported.

[0202] In some embodiments, the capability of the terminal device includes whether to support transmitting PUSCH or uplink signal overlapping both SBFD symbol and non-SBFD symbol. For example, the terminal device optionally supports transmitting PUSCH or uplink signal overlapping both SBFD symbol and non-SBFD symbol. When the terminal device supports, the corresponding capability information is reported, otherwise, it is not reported. When not supported, the corresponding case 4 / operation 4 is also not supported.

[0203] In some embodiments, which case (e.g., case 1 to case 4 as mentioned above) is allowed / applied can be predefined. For example, when the CG PUSCH configuration includes PUSCH overlapping both SBFD symbol and RBs outside UL usable RBs, case 2 is applied and operation 2 as mentioned above is performed. For another example, the base station can indicate which case as mentioned above is allowed / applied, e.g., configured / indicated by RRC signaling and / or MAC CE and / or DCI.

[0204] For another example, which case (e.g., case 1 to case 4 as mentioned above) is allowed / applied is limited by the capability of the UE, e.g., if the terminal device does not support case 3 / operation 3, case 3 / operation 3 is not allowed / applied, if the terminal device does not support case 4 / operation 4 or does not support transmitting PUSCH or uplink signal overlapping both SBFD symbol and non-SBFD symbol, case 4 / operation 4 is not allowed / applied.

[0205] In some embodiments, the terminal device determines the PUSCH(s) with corresponding HARQ process ID(s) from the plurality of PUSCHs according to the higher layer signaling and / or DCI and / or reference PUSCH and / or capability of the terminal device, and / or transmits one or more PUSCH(s) from the PUSCH(s) with corresponding HARQ process ID(s) from the plurality of PUSCHs.

[0206] In some embodiments, the reference PUSCH is a predetermined or indicated one from the CG PUSCH, or a predetermined or indicated one from the PUSCHs as follows: PUSCH not overlapping with SSB and / or second time domain resource for downlink (DL non-SBFD symbol), and / or PUSCH not overlapping with both first time domain resource (SBFD symbol) and second time domain resource (non-SBFD symbol), and / or PUSCH overlapping with first time domain resource (SBFD symbol) and not overlapping with PRB outside uplink usable PRB (UL usable PRB), and / or PUSCH not overlapping with symbol indicated by indicated information as downlink.

[0207] For example, the reference PUSCH is predefined as: the first PUSCH in CG PUSCH, or, the first PUSCH which does not overlap with SSB and / or DL non-SBFD symbol, and / or does not overlap with both SBFD symbol and non-SBFD symbol, and / or does not overlap with RBs outside of UL usable PRBs when overlapping with SBFD symbol.

[0208] For example, if the reference PUSCH is in SBFD symbol, the PUSCH which overlaps with non-SBFD symbol does not have HARQ process ID, and / or, (determined as case 1), the aforementioned operation 1 is performed.

[0209] For another example, if the reference PUSCH is in non-SBFD symbol, the PUSCH which overlaps with SBFD symbol does not have HARQ process ID, and / or, (determined as case 2), the aforementioned operation 2 is performed.

[0210] For yet another example, if the reference PUSCH overlaps with both SBFD symbol and non-SBFD symbol or starts from SBFD symbol to end at non-SBFD symbol, (determined as case 4), the aforementioned operation 4 is performed.

[0211] In some embodiments, the terminal device does not expect the reference PUCSH to overlap with both SBFD symbol and non-SBFD symbol.

[0212] The following first illustrates an optional mode 1 (option 1) of the embodiments of the present application.

[0213] It is worth noting that in the following description, each configuration will be described as an example. The first configuration to the fourth configuration can be carried by the same signaling together with the configuration information shown in FIG. 2, can be carried by different signaling (including high layer signaling and / or DCI) respectively, or can not be carried by signaling (for example, it is a default configuration); the present application is not limited to this.

[0214] In some embodiments, when the following configurations or information are carried by high layer signaling, they are respectively included in an IE (e.g., ServingCellConfigCommonSIB) or an IE (e.g., ServingCellConfigCommon) for configuring cell-specific parameters of a cell, and / or an IE (e.g., ServingCellConfig) for configuring a cell, and / or an IE (e.g., BWP-UplinkCommon) for configuring common parameters of a UL BWP, and / or an IE (e.g., BWP-UplinkDedicated) for configuring dedicated (UE specific) parameters of a UL BWP, and / or an IE (e.g., PUSCH-Config) for configuring UE-specific (applicable to one BWP) PUSCH parameters, and / or the above-mentioned CG configuration IE (ConfiguredGrantConfig).

[0215] In some embodiments, the terminal device receives a first configuration or a second configuration from the network device; the first configuration indicates that the PUSCH transmissions are all in the first time domain resources or all in the second time domain resources, and the second configuration indicates that the PUSCH transmissions can be in the first time domain resources and the second time domain resources.

[0216] In some embodiments, when the second configuration is not received and / or the terminal device does not support case 3 / operation 3 (and / or case 4 / operation 4), the first configuration is used by default.

[0217] For example, the first configuration indicates that the PUSCH transmissions are restricted to SBFD symbols only or non-SBFD symbols only, and the second configuration indicates that the PUSCH transmissions can be in SBFD symbols and non-SBFD symbols.

[0218] Among them, since the first configuration includes the aforementioned case 1 and case 2, the terminal device needs to uniquely determine whether operation 1 or operation 2 should be adopted for CG PUSCH. Since the second configuration includes the aforementioned case 3 and case 4, the terminal device needs to uniquely determine whether operation 3 or operation 4 should be adopted for CG PUSCH.

[0219] In some embodiments, in the case of the first configuration, for example, the terminal device is provided with the first configuration by high layer signaling or adopts the first configuration by default, according to the reference PUSCH and / or the first information provided by the MAC signaling and / or DCI, (determine whether it is case 1 or case 2), and then determine the PUSCH with the corresponding HARQ process ID in the plurality of PUSCH (if the conditions that the PUSCH with the corresponding HARQ process ID should meet for case 1 and case 2 are different), and / or, the PUSCH that will be transmitted or not transmitted in the plurality of PUSCH (that is, operation 1 or operation 2 is adopted),

[0220] Wherein, the first configuration indication indicates that the terminal device does not transmit the PUSCH in the plurality of PUSCHs that overlaps with the first time domain resource (that is, the PUSCH transmission is in the first time domain resource, corresponding to case 1) or does not transmit the PUSCH that overlaps with the second time domain resource (that is, the PUSCH transmission is in the second time domain resource, corresponding to case 2).

[0221] For example, if the reference PUSCH is in the SBFD symbol, the PUSCH that overlaps with the non-SBFD symbol does not have a HARQ process ID, and / or (determined as case 2,) the aforementioned operation 1 is performed.

[0222] For another example, if the reference PUSCH is in the non-SBFD symbol, the PUSCH that overlaps with the SBFD symbol does not have a HARQ process ID, and / or (determined as case 2,) the aforementioned operation 2 is performed.

[0223] For another example, if the first information indicates that the terminal device does not transmit the PUSCH in the plurality of PUSCHs that overlaps with the first time domain resource, the aforementioned operation 1 is performed, and if the first information indicates that the terminal device does not transmit the PUSCH in the plurality of PUSCHs that overlaps with the second time domain resource, the aforementioned operation 2 is performed.

[0224] In some embodiments, in case of the second configuration, e.g., the terminal device is provided with the second configuration by high layer signaling, according to the reference PUSCH and / or the second information provided by high layer signaling and / or DCI, (determine whether case 3 or case 4), and then determine the PUSCH with the corresponding HARQ process ID in the plurality of PUSCHs (if the conditions that the PUSCH with the corresponding HARQ process ID should meet are different for case 3 and case 4), and / or, the PUSCHs to be transmitted or not to be transmitted in the plurality of PUSCHs (that is, operation 3 or operation 4 is adopted),

[0225] The second configuration is used to indicate the terminal device to transmit the PUSCHs in the plurality of PUSCHs that overlap with both the first time domain resource and the second time domain resource (if any), or to indicate the terminal device not to transmit the PUSCHs in the plurality of PUSCHs that overlap with both the first time domain resource and the second time domain resource (if any).

[0226] For example, if the second information indicates the terminal device not to transmit the PUSCHs in the plurality of PUSCHs that overlap with both the first time domain resource and the second time domain resource (if any), operation 3 is performed, and if the first information indicates the terminal device to transmit the PUSCHs in the plurality of PUSCHs that overlap with both the first time domain resource and the second time domain resource (if any), operation 4 is performed.

[0227] The following further illustrates an optional mode 2 (option 2) of the embodiments of the present application.

[0228] In some embodiments, the terminal device receives the first configuration or the second configuration from the network device; the first configuration indicates that the PUSCH transmission is in the first time domain resource or in the second time domain resource, and the second configuration indicates that the PUSCH transmission can be in the first time domain resource and the second time domain resource, and each PUSCH transmission is in the first time domain resource or in the second time domain resource.

[0229] For example, the first configuration is the same as the first configuration in Option 1, and the second configuration includes case 3. For the first configuration, the method described in Option 1 can be referred to, and for the second configuration, operation 3 is performed.

[0230] The following further illustrates an optional mode 3 (option 3) of the embodiments of the present application.

[0231] In some embodiments, the terminal device receives a first configuration, a second configuration, or a third configuration from the network device; the first configuration indicates that the PUSCH transmissions are all in the first time domain resource, the second configuration indicates that the PUSCH transmissions are all in the second time domain resource, and the third configuration indicates that the PUSCH transmissions can be in the first time domain resource and the second time domain resource.

[0232] For example, for the first configuration (corresponding to the aforementioned case 1), the terminal device performs the aforementioned operation 1, and for the second configuration (corresponding to the aforementioned case 2), the terminal device performs the aforementioned operation 2. The third configuration is the same as the second configuration in Option 1, and for the third configuration, the method described in Option 1 for the corresponding second configuration can be referred to.

[0233] The following further illustrates an optional mode 4 (option 4) of the embodiments of the present application.

[0234] The terminal device receives a first configuration, a second configuration, a third configuration, or a fourth configuration from the network device; the first configuration indicates that the PUSCH transmissions are all in the first time domain resource, the second configuration indicates that the PUSCH transmissions are all in the second time domain resource, the third configuration indicates that the PUSCH transmissions can be in the first time domain resource and the second time domain resource and each PUSCH transmission is either in the first time domain resource or in the second time domain resource, and the fourth configuration indicates that multiple PUSCH transmissions can be in the first time domain resource and the second time domain resource and the PUSCH (if any) that overlaps with both the first time domain resource and the second time domain resource can be transmitted.

[0235] For example, for the first configuration (corresponding to the aforementioned case 1), the terminal device performs the aforementioned operation 1, and for the second configuration (corresponding to the aforementioned case 2), the terminal device performs the aforementioned operation 2. For the third configuration (corresponding to the aforementioned case 3), the terminal device performs the aforementioned operation 3, and for the second configuration (corresponding to the aforementioned case 4), the terminal device performs the aforementioned operation 4.

[0236] The above illustrates various embodiments of the present application, but the present application is not limited thereto. For example, in each option, if the UE is not signaled with a certain configuration, one of the other configurations can be used by default. For another example, the above optional modes can be partially combined. For another example, other embodiments can also be used as needed. The above is a simple description of options 2 to 5 for the sake of simplicity, and the present application is not limited thereto, and specific implementations can also refer to Option 1 and the aforementioned embodiments.

[0237] The following further illustrates the HARQ process ID.

[0238] In some embodiments, the terminal device allocates a HARQ process ID for the transmitted configured grant PUSCH. In addition, a HARQ process ID can be allocated for the non-transmitted configured grant PUSCH, or no HARQ process ID can be allocated for the non-transmitted configured grant PUSCH.

[0239] For example, for case 1, the PUSCH overlapping with the second time domain resource is not transmitted, which can be allocated or not allocated a HARQ process ID, that is, has or does not have a HARQ process ID. For example, for case 2, the PUSCH overlapping with the first time domain resource is not transmitted, which can be allocated or not allocated a HARQ process ID, that is, has or does not have a HARQ process ID.

[0240] In some embodiments, among the plurality of configured grant PUSCHs, the configured grant PUSCH transmitted by the terminal device has a corresponding HARQ process ID, and the configured grant PUSCH not transmitted by the terminal device does not have a corresponding HARQ process ID.

[0241] For example, for case 1, the PUSCH transmitted in operation 1 has a corresponding HARQ process ID, and the non-transmitted PUSCH does not have a corresponding HARQ process ID. For example, for case 2, the PUSCH transmitted in operation 2 has a corresponding HARQ process ID, and the non-transmitted PUSCH does not have a corresponding HARQ process ID.

[0242] In some embodiments, whether a configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource, including:

[0243] If a configured grant PUSCH overlaps with the second time domain resource (DL non-SBFD symbol) for downlink, the configured grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0244] If a configured grant PUSCH overlaps with the first time domain resource (SBFD symbol), the configured grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0245] If a configured grant PUSCH overlaps with the second time domain resource (non-SBFD symbol), the configured grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0246] If one configured grant PUSCH overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), the configured grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0247] If one configured grant PUSCH overlaps with the first time domain resource (SBFD symbol) and overlaps with a frequency domain resource other than the uplink usable PRB (UL usable PRB), the configured grant PUSCH does not have a corresponding HARQ process ID.

[0248] In some embodiments, the terminal device determines the HARQ process ID associated (corresponding) to the configured grant PUSCH (the first symbol of the corresponding uplink transmission) according to at least the first time domain resource and / or the second time domain resource, which can include: determining the HARQ process ID of the first configured grant PUSCH (the first symbol of the corresponding uplink transmission) in a period and each subsequent valid configured grant PUSCH (the first symbol of the corresponding uplink transmission).

[0249] In some embodiments, the PUSCH with a corresponding HARQ process ID is a PUSCH that:

[0250] does not overlap with an SSB, and / or, does not overlap with the second time domain resource for downlink (DL non-SBFD symbol), and / or, does not overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or, overlaps with the first time domain resource (SBFD symbol) and does not overlap with a PRB other than the uplink usable PRB (UL usable PRB), and / or, does not overlap with a symbol indicated by the indicated information as downlink.

[0251] For example, for the configured grant PUSCH that the UE needs to send, a corresponding HARQ process ID must be allocated, for the configured grant PUSCH that the UE does not send, a HARQ process ID can be allocated or not allocated.

[0252] For another example, the PUSCH allocated with the HARQ process ID at least does not overlap with SSBs and / or DL non-SBFD symbols, and / or does not overlap with symbols indicated as downlink by Y information when the PUSCH is within non-SBFD symbols, and / or does not overlap with RBs other than UL usable RBs and / or symbols indicated as downlink by X information and / or SBFD symbols and non-SBFD symbols when the PUSCH overlaps and / or is within SBFD symbols.

[0253] For another example, the PUSCH allocated with the HARQ process ID includes the first PUSCH in each period, and the PUSCHs after the first PUSCH that do not overlap with SSBs and / or DL non-SBFD symbols, and / or do not overlap with symbols indicated as downlink by Y information when the PUSCH is within non-SBFD symbols, and / or do not overlap with RBs other than UL usable RBs and / or symbols indicated as downlink by X information and / or SBFD symbols and non-SBFD symbols when the PUSCH overlaps and / or is within SBFD symbols.

[0254] In some embodiments, the terminal device further determines the HARQ process ID corresponding to the configured grant PUSCH according to a PUSCH transmission restriction corresponding to the configured grant.

[0255] In some examples, the PUSCH transmission restriction includes that the terminal device does not transmit the configured grant PUSCH overlapping with the second time domain resource (e.g., corresponding to the aforementioned case 1, but not limited thereto), and / or the terminal device does not transmit the configured grant PUSCH overlapping with the first time domain resource (e.g., corresponding to the aforementioned case 2, but not limited thereto), and / or the terminal device does not transmit the configured grant PUSCH overlapping with both the first time domain resource and the second time domain resource (e.g., corresponding to the aforementioned case 1 / case 2 / case 3, but not limited thereto).

[0256] In some embodiments, the PUSCH transmission restriction is indicated and / or determined according to at least one of the following: RRC signaling, MAC signaling, DCI, reference PUSCH, or capability of the terminal device. The specific method may, for example, refer to the aforementioned configurations and information, but is not limited thereto.

[0257] In some embodiments, the conditions that the configured grant PUSCH with corresponding HARQ process ID needs to satisfy are the same under different PUSCH transmission restrictions. For example, the conditions that the configured grant PUSCH with corresponding HARQ process ID needs to satisfy can be the same (or said to be defined the same) for 2 or more of the aforementioned case 1 to case 4, e.g., satisfying the intersection of the conditions corresponding to the transmitted PUSCH in the corresponding operation (including not overlapping with SSB, etc.).

[0258] In some embodiments, the conditions that the configured grant PUSCH with corresponding HARQ process ID needs to satisfy are different under different PUSCH transmission restrictions. For example, the conditions that the configured grant PUSCH with corresponding HARQ process ID needs to satisfy are different (or said to be defined differently) for 2 of the aforementioned case 1 to case 4, e.g., respectively satisfying the conditions corresponding to the transmitted PUSCH in the corresponding operation (including not overlapping with SSB, etc.).

[0259] In some embodiments, the terminal device determines the HARQ process ID corresponding to the configured grant PUSCH and / or transmits one or more of the configured grant PUSCH with corresponding HARQ process ID according to the RRC signaling and / or MAC signaling and / or DCI and / or reference PUSCH and / or capability of the terminal device.

[0260] In some embodiments, the HARQ process ID associated with the configured grant PUSCH (corresponding to the first symbol of the uplink transmission) is determined according to a first parameter (e.g., ID OFFSET); wherein the first parameter = 0 for the first configured grant PUSCH in a period, and the first parameter = K (1≤K<nrofSlotsInCG-Period) for the valid configured grant PUSCH after the first configured grant PUSCH in the same period, nrofSlotsInCG-Period is the number of configured grant PUSCH in a period.

[0261] Table 1 shows an example of the embodiments of the present application regarding the HARQ process ID, which includes an example of how to determine the HARQ process ID associated with the configured grant PUSCH (corresponding to the first symbol of the uplink transmission) according to the first parameter.

[0262] Table 1

[0263] The conditions in Table 1 may include, for example: no overlap with SSB and / or DL non-SBFD symbols, and / or no overlap with symbols indicated by the Yth information as downlink when the PUSCH is within the non-SBFD symbols, and / or no overlap with RBs other than UL usable RBs and / or no overlap with symbols indicated by the Xth information as downlink and / or no overlap with both SBFD symbols and non-SBFD symbols when the PUSCH overlaps with and / or is within the SBFD symbols.

[0264] Table 2 / Table 3 / Table 4 show further examples of HARQ process ID according to embodiments of the present application, each including one specific definition example of the valid configured PUSCH grant described in Table 1.

[0265] Table 2

[0266] Table 3

[0267] Table 4

[0268] Table 1 to Table 4 exemplarily illustrate the HARQ process ID according to embodiments of the present application, but are not limited thereto.

[0269] In some embodiments, the valid configured grant PUSCH does not overlap with SSB symbols, and / or does not overlap with the second time domain resources (DL non-SBFD symbols) for downlink, and / or does not overlap with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or overlaps with the first time domain resources (SBFD symbols) and does not overlap with the frequency domain resources other than the uplink usable PRBs (UL usable PRBs) (or the first frequency domain resources), and / or does not overlap with the symbols indicated by the indicated information (x / y) as downlink, and / or starts from the SBFD symbols and ends at the non-SBFD symbols, and / or starts from the non-SBFD symbols and ends at the SBFD symbols.

[0270] In some embodiments, the configured grant PUSCH in the period that does not overlap with the SSB symbol, and / or does not overlap with the second time domain resource (DL non-SBFD symbol) for downlink, and / or overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or overlaps with the first time domain resource (SBFD symbol) and the frequency domain resource other than the uplink available PRB (UL usable PRB) (or the first frequency domain resource), and / or overlaps with the symbol indicated by the indicated information as downlink, and / or does not start from the SBFD symbol and ends at the non-SBFD symbol, and / or does not start from the non-SBFD symbol and ends at the SBFD symbol, is not a valid configured grant PUSCH.

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

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

[0273] As can be seen from the above embodiments, the terminal device transmits one or more configured grant PUSCHs with corresponding HARQ process IDs; wherein for the configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. Thus, the network device can work in 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 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.

[0274] Embodiments of the second aspect

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

[0276] FIG. 22 is a schematic diagram of a PUSCH receiving method according to an embodiment of the present application. As shown in FIG. 22, the method includes:

[0277] 2201, the network device sends configuration information used for at least configuring the first time domain resource and / or the second time domain resource; wherein, in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0278] 2202, the network device sends configuration grant (CG) configuration; wherein, for the configuration grant, whether one configuration grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0279] 2203, the network device receives one or more configuration grant PUSCHs with corresponding HARQ process IDs.

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

[0281] In some embodiments, in the first time domain resource, the network device can send a downlink signal to one terminal device on the first frequency domain resource, receive an uplink signal sent by another terminal device on a frequency domain resource other than the first frequency domain resource, and / or receive an uplink signal sent by one terminal device on the second frequency domain resource, and send a downlink signal to another terminal device on a frequency domain resource other than the second frequency domain resource. So that the network device supports the simultaneous existence / occurrence / conduct of downlink and uplink.

[0282] In some embodiments, the network device can also send various configuration information / indication information to the terminal device, and the network device can also receive feedback information / reporting information from the terminal device, but the present application is not limited thereto.

[0283] In some embodiments, the configuration grant has a plurality of consecutive configuration grant PUSCHs in a period, and / or the configuration grant has a plurality of non-consecutive configuration grant PUSCHs in a period.

[0284] In some embodiments, the network device determines the HARQ process ID of the first configuration grant PUSCH and each subsequent valid configuration grant PUSCH in the period.

[0285] In some embodiments, the valid configured grant PUSCH does not overlap with SSB symbols, and / or, does not overlap with the second time domain resources for downlink (DL non-SBFD symbols), and / or, does not overlap with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or, overlaps with the first time domain resources (SBFD symbols) and does not overlap with the frequency domain resources other than the uplink usable PRBs (UL usable PRBs) (or the first frequency domain resources), and / or, does not overlap with the symbols indicated as downlink by the indicated information (x / y), and / or, starts from the SBFD symbols and ends at the non-SBFD symbols, and / or, starts from the non-SBFD symbols and ends at the SBFD symbols.

[0286] In some embodiments, the configured grant PUSCH in a period that: overlaps with SSB symbols, and / or, overlaps with the second time domain resources for downlink (DL non-SBFD symbols), and / or, overlaps with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or, overlaps with the first time domain resources (SBFD symbols) and overlaps with the frequency domain resources other than the uplink usable PRBs (UL usable PRBs) (or the first frequency domain resources), and / or, overlaps with the symbols indicated as downlink by the indicated information, and / or, does not start from the SBFD symbols and ends at the non-SBFD symbols, and / or, does not start from the non-SBFD symbols and ends at the SBFD symbols, is not a valid configured grant PUSCH.

[0287] In some embodiments, the configured grant PUSCH is determined according to a first parameter; wherein the first parameter is zero for a first configured grant PUSCH in a period, and the first parameter is a value greater than or equal to 1 and less than a number of configured grant PUSCHs in the period for valid configured grant PUSCHs after the first configured grant PUSCH in the same period.

[0288] In some embodiments, the network device further determines the valid configured grant PUSCH according to a PUSCH transmission restriction corresponding to the configured grant.

[0289] In some embodiments, the PUSCH transmission restriction comprises:

[0290] The terminal device does not transmit the configured grant PUSCH overlapping with the second time domain resources (alternatively, the network device does not receive the PUSCH in the plurality of PUSCHs overlapping with the second time domain resources); and / or

[0291] The terminal device does not transmit a configured grant PUSCH that overlaps with the first time domain resource (alternatively, the terminal device does not receive a PUSCH of the plurality of PUSCHs that overlaps with the first time domain resource); and / or

[0292] The terminal device does not transmit a configured grant PUSCH that overlaps with both the first time domain resource and the second time domain resource (the network device does not receive a PUSCH of the plurality of PUSCHs that overlaps with both the first time domain resource and the second time domain resource).

[0293] In some embodiments, the PUSCH transmission restriction is determined according to at least one of: RRC signaling, MAC signaling, DCI, a reference PUSCH, or a capability of the terminal device.

[0294] In some embodiments, under different PUSCH transmission restrictions, the configured grant PUSCHs with corresponding HARQ process IDs need to satisfy the same conditions.

[0295] In some embodiments, under different PUSCH transmission restrictions, the configured grant PUSCHs with corresponding HARQ process IDs need to satisfy different conditions.

[0296] In some embodiments, the configured grant PUSCH that overlaps with the second time domain resource is not transmitted;

[0297] The network device receives a configured grant PUSCH that does not overlap with an SSB symbol, and / or does not overlap with the second time domain resource (non-SBFD symbol), and / or is in the first time domain resource (SBFD symbol) and does not overlap with a PRB outside of an uplink usable PRB (UL usable PRB) (or the first frequency domain resource), and / or does not overlap with a symbol indicated as downlink by indicated information (x information),

[0298] and / or,

[0299] The network device does not receive a configured grant PUSCH that overlaps with an SSB symbol, and / or overlaps with the second time domain resource (non-SBFD symbol), and / or is in the first time domain resource (SBFD symbol) and overlaps with a PRB outside of an uplink usable PRB (UL usable PRB) (or the first frequency domain resource), and / or overlaps with a symbol indicated as downlink by indicated information (x information);

[0300] and / or,

[0301] The terminal device does not expect (alternatively, the network device does not schedule) a PUSCH that exists in the first time domain resource (SBFD symbol) and overlaps with PRBs other than the uplink usable PRBs (UL usable PRBs) (or the first frequency domain resource), and / or the terminal device does not expect (alternatively, the network device does not schedule) a configured grant PUSCH that overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0302] In some embodiments, the configured grant PUSCH that overlaps with the first time domain resource is not transmitted;

[0303] The network device receives a configured grant PUSCH that does not overlap with an SSB, and / or does not overlap with the first time domain resource (SBFD symbol), and / or does not overlap with the second time domain resource (non-SBFD symbol) for downlink, and / or does not overlap with a symbol indicated as downlink by the indicated information (y information);

[0304] and / or,

[0305] The network device does not receive a configured grant PUSCH that overlaps with an SSB, and / or overlaps with the first time domain resource (SBFD symbol), and / or overlaps with the second time domain resource (non-SBFD symbol) for downlink, and / or overlaps with a symbol indicated as downlink by the indicated information (y information);

[0306] and / or,

[0307] The terminal device does not expect (alternatively, the network device does not schedule) a configured grant PUSCH that overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0308] In some embodiments, the configured grant PUSCH that overlaps with both the first time domain resource and the second time domain resource is not transmitted;

[0309] The network device receives a configured grant PUSCH that does not overlap with an SSB and / or the second time domain resource (DL non-SBFD symbol) for downlink, and / or does not overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or is in the first time domain resource (SBFD symbol) and does not overlap with PRBs other than the uplink usable PRBs (UL usable PRBs) (or the first frequency domain resource), and / or does not overlap with a symbol indicated as downlink by the indicated information;

[0310] and / or,

[0311] The network device does not receive a configured grant PUSCH that overlaps with an SSB, and / or that overlaps with a second time domain resource for downlink (DL non-SBFD symbol), and / or that overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or that is in the first time domain resource (SBFD symbol) and overlaps with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency domain resource), and / or that overlaps with a symbol indicated as downlink by the indicated information.

[0312] and / or,

[0313] The terminal device does not expect (alternatively, the network device does not schedule) a PUSCH that is in the first time domain resource (SBFD symbol) and overlaps with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency domain resource), and / or the terminal device does not expect (alternatively, the network device does not schedule) a configured grant PUSCH that overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0314] In some embodiments, a configured grant PUSCH that overlaps with both the first time domain resource and the second time domain resource can be transmitted;

[0315] The network device receives a configured grant PUSCH that does not overlap with an SSB and / or a second time domain resource for downlink (DL non-SBFD symbol), and / or that overlaps with the first time domain resource (SBFD symbol) and does not overlap with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency domain resource), and / or that does not overlap with a symbol indicated as downlink by the indicated information.

[0316] and / or,

[0317] The network device does not receive a configured grant PUSCH that overlaps with an SSB, and / or that overlaps with a second time domain resource for downlink (DL non-SBFD symbol), and / or that overlaps with the first time domain resource (SBFD symbol) and overlaps with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency domain resource), and / or that overlaps with a symbol indicated as downlink by the indicated information.

[0318] and / or,

[0319] The terminal device does not expect (alternatively, the network device does not schedule) a configured grant PUSCH that overlaps with the first time domain resource (SBFD symbol) and overlaps with a PRB other than an uplink usable PRB (UL usable PRB).

[0320] In some embodiments, the configured grant PUSCHs received by the network device have corresponding HARQ process IDs, and the configured grant PUSCHs received by the network device do not have corresponding HARQ process IDs.

[0321] In some embodiments, the network device determines the HARQ process IDs corresponding to the configured grant PUSCHs according to RRC signaling and / or MAC signaling and / or DCI and / or reference PUSCHs and / or the capability of the terminal device, and / or receives one or more of the configured grant PUSCHs with corresponding HARQ process IDs.

[0322] In some embodiments, the network device, in a case that a first configuration is provided by RRC signaling and / or MAC signaling, determines the configured grant PUSCHs with corresponding HARQ process IDs according to reference PUSCHs and / or first information provided by MAC signaling and / or DCI, and / or the configured grant PUSCHs to be transmitted or not to be transmitted,

[0323] wherein the first configuration indicates that the configured grant PUSCHs are all transmitted in the first time domain resources or the second time domain resources, and the first information indicates that the terminal device does not transmit (alternatively, the network device does not receive) the configured grant PUSCHs overlapping with the first time domain resources or the configured grant PUSCHs overlapping with the second time domain resources.

[0324] In some embodiments, the reference PUSCHs are predetermined or indicated ones of the configured grant PUSCHs, or predetermined or indicated ones of the following PUSCHs:

[0325] PUSCHs not overlapping with SSBs and / or second time domain resources for downlink (DL non-SBFD symbols), and / or PUSCHs not overlapping with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or PUSCHs overlapping with the first time domain resources (SBFD symbols) and not overlapping with PRBs other than uplink usable PRBs (UL usable PRBs) (or the first frequency domain resources), and / or PUSCHs not overlapping with symbols indicated by the indicated information as downlink.

[0326] In some embodiments, the network device determines, according to the reference PUSCH and / or the second information provided by the RRC signaling and / or the MAC signaling and / or the DCI, a configured grant PUSCH with a corresponding HARQ process ID, and / or a configured grant PUSCH to be transmitted or not to be transmitted, in the case that the second configuration is provided by the RRC signaling and / or the MAC signaling,

[0327] The second configuration indicates that the configured grant PUSCH transmission can be in the first time domain resource and / or the second time domain resource; and the second information is used to indicate the terminal device to transmit (alternatively, the network device to receive) the configured grant PUSCH that overlaps with both the first time domain resource and the second time domain resource, or to indicate the terminal device not to transmit (alternatively, the network device not to receive) the configured grant PUSCH that overlaps with both the first time domain resource and the second time domain resource.

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

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

[0330] As can be seen from the above embodiments, the network device receives one or more configured grant PUSCHs with a corresponding HARQ process ID; wherein, for the configured grant, whether a configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. Thus, 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.

[0331] Embodiments of the third aspect

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

[0333] FIG. 23 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 embodiment of the first aspect, the specific implementation can be referred to the embodiment of the first aspect, and the same content will not be repeated. As shown in FIG. 23, the PUSCH sending device 2300 includes a receiver 2301 and a transmitter 2302, and can further include a processor 2303.

[0334] In some embodiments, the receiver 2301 receives configuration information used at least for configuring the first time domain resource and / or the second time domain resource; wherein, in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource; receives a configuration grant (CG) configuration; wherein, for the configuration grant, whether one configuration grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0335] The transmitter 2302 transmits one or more of the configuration grant PUSCHs with the corresponding HARQ process ID.

[0336] In some embodiments, whether one configuration grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource, including:

[0337] If one configuration grant PUSCH overlaps with the second time domain resource (DL non-SBFD symbol) used for downlink, the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0338] If one configuration grant PUSCH overlaps with the first time domain resource (SBFD symbol), the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0339] If one configuration grant PUSCH overlaps with the second time domain resource (non-SBFD symbol), the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0340] If one configuration grant PUSCH overlaps with the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or,

[0341] If a configured grant PUSCH overlaps with the first time domain resource (SBFD symbol) and overlaps with the frequency domain resource other than the uplink usable PRB (UL usable PRB), the configured grant PUSCH does not have the corresponding HARQ process ID.

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

[0343] In some embodiments, the processor 2303 determines the HARQ process ID of the first configured grant PUSCH and each subsequent valid configured grant PUSCH in the period.

[0344] In some embodiments, a valid configured grant PUSCH does not overlap with the SSB symbol, and / or does not overlap with the second time domain resource for downlink (DL non-SBFD symbol), and / or does not overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or overlaps with the first time domain resource (SBFD symbol) and does not overlap with the frequency domain resource other than the uplink usable PRB (UL usable PRB) (or the first frequency domain resource), and / or does not overlap with the symbol indicated as downlink by the indicated information (x / y), and / or starts from the SBFD symbol and ends at the non-SBFD symbol, and / or starts from the non-SBFD symbol and ends at the SBFD symbol.

[0345] In some embodiments, the configured grant PUSCH in the period that: overlaps with the SSB symbol, and / or overlaps with the second time domain resource for downlink (DL non-SBFD symbol), and / or overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or overlaps with the first time domain resource (SBFD symbol) and overlaps with the frequency domain resource other than the uplink usable PRB (UL usable PRB), and / or overlaps with the symbol indicated as downlink by the indicated information, and / or does not start from the SBFD symbol and end at the non-SBFD symbol, and / or does not start from the non-SBFD symbol and end at the SBFD symbol, is not a valid configured grant PUSCH.

[0346] In some embodiments, the configured grant PUSCH is determined according to a first parameter; wherein the first parameter is zero for a first configured grant PUSCH in a period, and the first parameter is a value greater than or equal to 1 and less than a number of configured grant PUSCHs in the period for a valid configured grant PUSCH after the first configured grant PUSCH in the period.

[0347] In some embodiments, the processor 2303 further determines the HARQ process ID corresponding to the configured grant PUSCH according to a PUSCH transmission restriction corresponding to the configured grant;

[0348] The PUSCH transmission restriction comprises:

[0349] The terminal device does not transmit the configured grant PUSCH overlapping with the second time domain resource; and / or

[0350] The terminal device does not transmit the configured grant PUSCH overlapping with the first time domain resource; and / or

[0351] The terminal device does not transmit the configured grant PUSCH overlapping with both the first time domain resource and the second time domain resource.

[0352] In some embodiments, the PUSCH transmission restriction is determined according to at least one of the following: RRC signaling, MAC signaling, DCI, reference PUSCH, or capability of the terminal device.

[0353] In some embodiments, under different PUSCH transmission restrictions, the configured grant PUSCHs with corresponding HARQ process IDs need to satisfy the same conditions.

[0354] In some embodiments, under different PUSCH transmission restrictions, the configured grant PUSCHs with corresponding HARQ process IDs need to satisfy different conditions.

[0355] In some embodiments, the configured grant PUSCH overlapping with the second time domain resource is not transmitted;

[0356] The transmitter 2302 transmits the PUSCHs that do not overlap with SSB symbols, and / or do not overlap with the second time domain resource (non-SBFD symbols), and / or are in the first time domain resource (SBFD symbols) and do not overlap with PRBs other than the uplink available PRBs (UL usable PRBs) (or the first frequency domain resource), and / or do not overlap with symbols indicated as downlink by the indicated information (x information),

[0357] and / or,

[0358] The transmitter 2302 does not transmit a PUSCH that overlaps with an SSB symbol, and / or, overlaps with a second time-domain resource (non-SBFD symbol), and / or, is in a first time-domain resource (SBFD symbol) and overlaps with a PRB other than an uplink usable PRB (or the first frequency-domain resource), and / or, overlaps with a symbol indicated as downlink by indicated information (x information);

[0359] and / or,

[0360] The terminal device does not expect a PUSCH that is in a first time-domain resource (SBFD symbol) and overlaps with a PRB other than an uplink usable PRB (or the first frequency-domain resource), and / or, overlaps with both the first time-domain resource (SBFD symbol) and a second time-domain resource (non-SBFD symbol) to exist.

[0361] In some embodiments, a configured grant PUSCH that overlaps with the first time-domain resource is not transmitted;

[0362] The transmitter 2302 transmits a PUSCH that does not overlap with an SSB, and / or, does not overlap with a first time-domain resource (SBFD symbol), and / or, does not overlap with a second time-domain resource (non-SBFD symbol) for downlink, and / or, does not overlap with a symbol indicated as downlink by indicated information (y information);

[0363] and / or,

[0364] The transmitter 2302 does not transmit a PUSCH that overlaps with an SSB, and / or, overlaps with a first time-domain resource (SBFD symbol), and / or, overlaps with a second time-domain resource (non-SBFD symbol) for downlink, and / or, overlaps with a symbol indicated as downlink by indicated information (y information);

[0365] and / or,

[0366] The terminal device does not expect a PUSCH that overlaps with both a first time-domain resource (SBFD symbol) and a second time-domain resource (non-SBFD symbol) to exist.

[0367] In some embodiments, a configured grant PUSCH that overlaps with both the first time-domain resource and the second time-domain resource is not transmitted;

[0368] The transmitter 2302 transmits a PUSCH that does not overlap with an SSB and / or a second time-domain resource for downlink (DL non-SB FD symbol), and / or, does not overlap with both the first time-domain resource (SB FD symbol) and the second time-domain resource (non-SB FD symbol), and / or, is in the first time-domain resource (SB FD symbol) and does not overlap with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency-domain resource), and / or, does not overlap with a symbol indicated as downlink by indicated information;

[0369] and / or,

[0370] The transmitter 2302 does not transmit a PUSCH that overlaps with an SSB, and / or, overlaps with a second time-domain resource for downlink (DL non-SB FD symbol), and / or, overlaps with both the first time-domain resource (SB FD symbol) and the second time-domain resource (non-SB FD symbol), and / or, is in the first time-domain resource (SB FD symbol) and overlaps with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency-domain resource), and / or, overlaps with a symbol indicated as downlink by indicated information;

[0371] and / or,

[0372] The terminal device does not expect a PUSCH that is in the first time-domain resource (SB FD symbol) and overlaps with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency-domain resource), and / or, the terminal device does not expect a PUSCH that overlaps with both the first time-domain resource (SB FD symbol) and the second time-domain resource (non-SB FD symbol).

[0373] In some embodiments, a configured grant PUSCH that overlaps with both the first time-domain resource and the second time-domain resource can be transmitted;

[0374] The transmitter 2302 transmits a PUSCH that does not overlap with an SSB and / or a second time-domain resource for downlink (DL non-SB FD symbol), and / or, overlaps with the first time-domain resource (SB FD symbol) and does not overlap with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency-domain resource), and / or, does not overlap with a symbol indicated as downlink by indicated information;

[0375] and / or,

[0376] The transmitter 2302 does not transmit a PUSCH that overlaps with an SSB, and / or overlaps with a second time-domain resource (DL non-SB FD symbol) used for downlink, and / or overlaps with a first time-domain resource (SB FD symbol) and overlaps with a PRB other than an uplink usable PRB (UL usable PRB) (or the first frequency-domain resource), and / or overlaps with a symbol indicated by the indicated information as downlink.

[0377] and / or,

[0378] The terminal device does not expect a PUSCH that overlaps with the first time-domain resource (SB FD symbol) and overlaps with a PRB other than the uplink usable PRB (UL usable PRB).

[0379] In some embodiments, the transmitted configured grant PUSCH has a corresponding HARQ process ID, and the non-transmitted configured grant PUSCH does not have a corresponding HARQ process ID.

[0380] In some embodiments, the processor 2303 determines the HARQ process ID corresponding to the configured grant PUSCH according to the RRC signaling and / or the MAC signaling and / or the DCI and / or the reference PUSCH and / or the capability of the terminal device, and / or the transmitter 2302 transmits one or more configured grant PUSCHs with the corresponding HARQ process ID.

[0381] In some embodiments, the determiner 2303, in a case where the first configuration is provided by the RRC signaling and / or the MAC signaling, determines the configured grant PUSCH with the corresponding HARQ process ID according to the reference PUSCH and / or the first information provided by the MAC signaling and / or the DCI, and / or the configured grant PUSCH to be transmitted or not to be transmitted,

[0382] wherein the first configuration indicates that the configured grant PUSCHs to be transmitted are all in the first time-domain resource or in the second time-domain resource, and the first information indicates that the terminal device does not transmit the configured grant PUSCH that overlaps with the first time-domain resource or the configured grant PUSCH that overlaps with the second time-domain resource.

[0383] In some embodiments, the reference PUSCH is a predetermined or indicated one of the configured grant PUSCHs, or a predetermined or indicated one of the PUSCHs as follows:

[0384] PUSCHs that do not overlap with the SSB and / or the second time-domain resource for downlink (DL non-SB FD symbol), and / or, PUSCHs that do not overlap with both the first time-domain resource (SB FD symbol) and the second time-domain resource (non-SB FD symbol), and / or, PUSCHs that overlap with the first time-domain resource (SB FD symbol) and do not overlap with PRBs other than the uplink usable PRBs (or the first frequency-domain resource), and / or, PUSCHs that do not overlap with symbols indicated by the indicated information as downlink.

[0385] In some embodiments, the processor 2303 determines, in a case where the second configuration is provided by RRC signaling and / or MAC signaling, a configured grant PUSCH with a corresponding HARQ process ID according to the reference PUSCH and / or the second information provided by the RRC signaling and / or the MAC signaling and / or the DCI, and / or, the configured grant PUSCH to be transmitted or not to be transmitted,

[0386] The second configuration indicates that the configured grant PUSCH transmission is capable in the first time-domain resource and / or the second time-domain resource; and the second information is used to indicate the terminal device to transmit the configured grant PUSCH overlapping with both the first time-domain resource and the second time-domain resource, or to indicate the terminal device not to transmit the configured grant PUSCH overlapping with both the first time-domain resource and the second time-domain resource.

[0387] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The PUSCH transmission device 2300 of the embodiments of the present application can also include other components or modules, and the specific content of these components or modules can be referred to the related art.

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

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

[0390] From the above embodiments, the terminal device transmits one or more configured grant PUSCHs with corresponding HARQ process IDs; wherein for a configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. In this way, 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.

[0391] Embodiments of the fourth aspect

[0392] Embodiments of the present application provide a PUSCH receiving device. The device may, for example, be a network device, or one or more components or assemblies configured in the network device. The same content as the embodiments of the third aspect will not be described again.

[0393] FIG. 24 is a schematic diagram of a PUSCH receiving device according to an embodiment of the present application. Since the principle of solving the problem of the device is the same as that of the method of the first and second aspects, the specific implementation can refer to the embodiments of the first and second aspects, and the same content will not be described again.

[0394] As shown in FIG. 24, the PUSCH receiving device 2400 includes:

[0395] a transmitter 2401 configured to transmit configuration information used at least for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource; and transmit a configured grant (CG) configuration; wherein for the configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0396] a receiver 2402 configured to receive one or more configured grant PUSCHs with corresponding HARQ process IDs.

[0397] 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 device 2400 of the embodiments of the present application can also include other components or modules (for example, a processor, etc.), and the specific content of these components or modules can refer to related technologies.

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

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

[0400] As can be seen from the above embodiments, the network device transmits one or more PUSCHs with corresponding HARQ process IDs; wherein, for configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. In this way, the network device can work in full duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to transceive signals when the network device works in full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0401] Embodiments of the fifth aspect

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

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

[0404] The terminal device receives configuration information at least for configuring the first time domain resource and / or the second time domain resource; wherein, in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource; receives configured grant (CG) configuration, wherein, for configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and transmits one or more of the configured grant PUSCHs with corresponding HARQ process IDs;

[0405] The network device transmits configuration information at least for configuring the first time domain resource and / or the second time domain resource; transmits configured grant (CG) configuration; and receives PUSCH from the terminal device.

[0406] The embodiment of the present application further provides a network device, which can be a base station, but the present application is not limited thereto, and can also be other network devices.

[0407] Fig. 25 is a structural schematic diagram of a network device according to the embodiment of the present application. As shown in Fig. 25, the network device 2500 can include a processor 2510 (for example, a central processing unit, CPU) and a memory 2520, wherein the memory 2520 is coupled to the processor 2510. The memory 2520 can store various data, and further store a program 2530 for information processing, and execute the program 2530 under the control of the processor 2510.

[0408] For example, the processor 2510 can be configured to execute the program to implement the method according to the embodiment of the second aspect.

[0409] In addition, as shown in Fig. 25, the network device 2500 can further include a transceiver 2540, an antenna 2550, etc., wherein the functions of the above components are similar to those in the prior art, and will not be described here. It is worth noting that the network device 2500 does not necessarily include all the components shown in Fig. 25; in addition, the network device 2500 can also include components not shown in Fig. 25, which can be referred to the prior art.

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

[0411] Fig. 26 is a schematic diagram of a terminal device according to the embodiment of the present application. As shown in Fig. 26, the terminal device 2600 can include a processor 2610 and a memory 2620, wherein the memory 2620 stores data and programs, and is coupled to the processor 2610. It is worth noting that the figure is exemplary; other types of structures can also be used to supplement or replace the structure to achieve telecommunication functions or other functions.

[0412] For example, the processor 2610 can be configured to execute the program to implement the method according to the embodiment of the first aspect.

[0413] As shown in Fig. 26, the terminal device 2600 can further include a communication module 2630, an input device 2640, a display 2650, and a power supply 2660. The functions of the above components are similar to those in the prior art, and will not be described here. It is worth noting that the terminal device 2600 does not necessarily include all the components shown in Fig. 26, and the above components are not essential; in addition, the terminal device 2600 can also include components not shown in Fig. 26, which can be referred to the prior art.

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

[0415] The embodiments of the present application further provide a storage medium storing a computer readable program, wherein the computer readable program enables a computer to execute the method of the embodiments of the second aspect when the program is executed in the network device.

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

[0417] The embodiments of the present application further provide a storage medium storing a computer readable program, wherein the computer readable program enables a computer to execute the method of the embodiments of the first aspect when the program is executed in the terminal device.

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

[0419] The method / apparatus described in combination with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figures and / or a combination of one or more of the functional block diagrams can correspond to each software module of the computer program flow, and can also correspond to each hardware module. The software modules can respectively correspond to each step shown in the figures. These hardware modules can be implemented by, for example, fixing the software modules using a field programmable gate array (FPGA).

[0420] The software modules can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The software modules can be stored in a memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if the device (e.g., mobile terminal) is 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.

[0421] One or more of the functional blocks described in the accompanying drawings and / or one or more combinations of the functional blocks can be implemented as a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any appropriate combination thereof, for performing the functions described in this application. One or more of the functional blocks described in the accompanying drawings and / or one or more combinations 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 conjunction with a DSP core, or any other such configuration.

[0422] The application has been described in connection with certain embodiments. However, one of ordinary skill in the art will readily recognize from the disclosure herein that changes and modifications can be made thereto without departing from the scope of the present application. Accordingly, nothing in the present application should be construed as a limitation on the scope of the present application, but is intended to cover all possible modifications and equivalents.

[0423] With respect to the embodiments including the above embodiments, the following supplementary notes are also disclosed:

[0424] 1. A PUSCH transmission method comprising:

[0425] The terminal device receives configuration 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;

[0426] The terminal device receives a configuration grant (CG) configuration, wherein for a configuration grant, whether a corresponding HARQ process ID of one configuration grant PUSCH is related to the first time domain resource and / or the second time domain resource; and

[0427] The terminal device transmits one or more configured grant PUSCHs with corresponding HARQ process IDs.

[0428] 2. A PUSCH receiving method, comprising:

[0429] The network device transmits configuration information at least for configuring the first time domain resource and / or the 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.

[0430] The network device transmits configured grant (CG) configuration, wherein whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource for the configured grant.

[0431] The network device transmits one or more configured grant PUSCHs with corresponding HARQ process IDs.

[0432] 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 transmitting method according to the appended item 1.

[0433] 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 receiving method according to the appended item 2.

[0434] 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 transmitting method according to the appended item 1.

[0435] 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 receiving method according to the appended item 2.

Claims

1. A PUSCH transmitting apparatus, comprising: a receiver configured to receive configuration 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; receive a configuration grant configuration, wherein for a configuration grant, whether one configuration grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and a transmitter configured to transmit one or more of the configuration grant PUSCHs with the corresponding HARQ process ID.

2. The apparatus of claim 1, wherein, Whether one configuration grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource, comprising: if one configuration grant PUSCH overlaps with the second time domain resource for downlink, the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or, if one configuration grant PUSCH overlaps with the first time domain resource, the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or, if one configuration grant PUSCH overlaps with both the first time domain resource and the second time domain resource, the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or, if one configuration grant PUSCH overlaps with both the first time domain resource and the second time domain resource, the configuration grant PUSCH does not have a corresponding HARQ process ID, and / or, if one configuration grant PUSCH overlaps with the first time domain resource and overlaps with a frequency domain resource outside uplink available PRBs, the configuration grant PUSCH does not have a corresponding HARQ process ID.

3. The apparatus of claim 1, wherein, The configuration grant has a plurality of consecutive configuration grant PUSCHs in a period, and / or the configuration grant has a plurality of non-consecutive configuration grant PUSCHs in a period; the apparatus further comprising: a processor configured to determine a HARQ process ID of a first configuration grant PUSCH and each subsequent valid configuration grant PUSCH in the period.

4. The apparatus of claim 3, wherein, The valid configuration grant PUSCH does not overlap with an SSB symbol, and / or does not overlap with the second time domain resource for downlink, and / or does not overlap with both the first time domain resource and the second time domain resource, and / or overlaps with the first time domain resource and does not overlap with a frequency domain resource outside uplink available PRBs, and / or does not overlap with a symbol indicated as downlink by indicated information, and / or starts from an SBFD symbol and ends at a non-SBFD symbol, and / or starts from a non-SBFD symbol and ends at an SBFD symbol.

5. The apparatus of claim 3, wherein, The configured grant PUSCH in the period that overlaps with an SSB symbol, and / or overlaps with the second time domain resource for downlink, and / or overlaps with both the first time domain resource and the second time domain resource, and / or overlaps with the first time domain resource and overlaps with a frequency domain resource other than the PRB available for uplink, and / or overlaps with a symbol indicated as downlink by the indicated information, and / or does not start from an SBFD symbol and ends at a non-SBFD symbol, and / or does not start from a non-SBFD symbol and ends at an SBFD symbol, is not a valid configured grant PUSCH.

6. The apparatus of claim 3, wherein, The HARQ process ID of the configured grant PUSCH is determined according to a first parameter; wherein the first parameter is zero for a first configured grant PUSCH in a period, and the first parameter is a value greater than or equal to 1 and less than the number of configured grant PUSCHs in the period for a valid configured grant PUSCH after the first configured grant PUSCH in the same period.

7. The apparatus of claim 3, wherein, The processor further determines the valid configured grant PUSCH according to a PUSCH transmission restriction corresponding to the configured grant, The PUSCH transmission restriction comprises: The terminal device does not transmit a configured grant PUSCH that overlaps with the second time domain resource; and / or The terminal device does not transmit a configured grant PUSCH that overlaps with the first time domain resource; and / or The terminal device does not transmit a configured grant PUSCH that overlaps with both the first time domain resource and the second time domain resource.

8. The apparatus of claim 7, wherein, The PUSCH transmission restriction is indicated and / or determined according to at least one of the following: RRC signaling, MAC signaling, downlink control information, reference PUSCH, or the capability of the terminal device.

9. The apparatus of claim 7, wherein, Under different PUSCH transmission restrictions, the configured grant PUSCHs with corresponding HARQ process IDs need to meet the same conditions, Or, Under different PUSCH transmission restrictions, the configured grant PUSCHs with corresponding HARQ process IDs need to meet different conditions.

10. The apparatus of claim 1, wherein, The configured grant PUSCH that overlaps with the second time domain resource is not transmitted; The transmitter transmits the configured grant PUSCH that does not overlap with an SSB symbol, and / or does not overlap with the second time domain resource, and / or is in the first time domain resource and does not overlap with a PRB other than the PRB available for uplink, and / or does not overlap with a symbol indicated as downlink by the indicated information, And / or, The transmitter does not transmit the configured grant PUSCH that overlaps with an SSB symbol, and / or overlaps with the second time domain resource, and / or is in the first time domain resource and overlaps with a PRB other than the PRB available for uplink, and / or overlaps with a symbol indicated as downlink by the indicated information; And / or, The terminal device does not expect to exist a PUSCH that is in the first time domain resource and overlaps with a PRB other than the PRB available for uplink, and / or the terminal device does not expect to exist a configured grant PUSCH that overlaps with both the first time domain resource and the second time domain resource.

11. The apparatus of claim 1, wherein, The configured grant PUSCH that overlaps with the first time domain resource is not transmitted; The transmitter transmits the configured grant PUSCH which does not overlap with the SSB, and / or does not overlap with the first time domain resource, and / or does not overlap with the second time domain resource for downlink, and / or does not overlap with the symbol indicated as downlink by the indicated information; and / or, The transmitter does not transmit the configured grant PUSCH which overlaps with the SSB, and / or overlaps with the first time domain resource, and / or overlaps with the second time domain resource for downlink, and / or overlaps with the symbol indicated as downlink by the indicated information; and / or, The terminal device does not expect the configured grant PUSCH which overlaps with both the first time domain resource and the second time domain resource.

12. The apparatus of claim 1, wherein, The configured grant PUSCH which overlaps with both the first time domain resource and the second time domain resource is not transmitted; The transmitter transmits the configured grant PUSCH which does not overlap with the SSB and / or the second time domain resource for downlink, and / or does not overlap with both the first time domain resource and the second time domain resource, and / or is in the first time domain resource and does not overlap with the PRB outside the uplink available PRB, and / or does not overlap with the symbol indicated as downlink by the indicated information; and / or, The transmitter does not transmit the configured grant PUSCH which overlaps with the SSB, and / or overlaps with the second time domain resource for downlink, and / or overlaps with both the first time domain resource and the second time domain resource, and / or is in the first time domain resource and overlaps with the PRB outside the uplink available PRB, and / or overlaps with the symbol indicated as downlink by the indicated information; and / or, The terminal device does not expect the PUSCH which is in the first time domain resource and overlaps with the PRB outside the uplink available PRB, and / or the terminal device does not expect the configured grant PUSCH which overlaps with both the first time domain resource and the second time domain resource.

13. The apparatus of claim 1, wherein, The configured grant PUSCH which overlaps with both the first time domain resource and the second time domain resource can be transmitted; The transmitter transmits the configured grant PUSCH which does not overlap with the SSB and / or the second time domain resource for downlink, and / or overlaps with the first time domain resource and does not overlap with the PRB outside the uplink available PRB, and / or does not overlap with the symbol indicated as downlink by the indicated information; and / or, The transmitter does not transmit the configured grant PUSCH which overlaps with the SSB, and / or overlaps with the second time domain resource for downlink, and / or overlaps with the first time domain resource and overlaps with the PRB outside the uplink available PRB, and / or overlaps with the symbol indicated as downlink by the indicated information; and / or, The terminal device does not expect the configured grant PUSCH which overlaps with the first time domain resource and overlaps with the PRB outside the uplink available PRB.

14. The apparatus of claim 1, wherein, The transmitted configured grant PUSCH has the corresponding HARQ process ID, and the non-transmitted configured grant PUSCH does not have the corresponding HARQ process ID.

15. The apparatus of claim 1, wherein, The apparatus further comprises: a processor which determines the HARQ process ID corresponding to the configured grant PUSCH according to the high layer signaling and / or the downlink control information and / or the reference PUSCH and / or the capability of the terminal device, and / or, The transmitter transmits one or more of the configured grant PUSCHs with the corresponding HARQ process ID.

16. The apparatus of claim 15, wherein, The processor determines, in a case that a first configuration is provided by higher layer signaling, the configured grant PUSCHs with the corresponding HARQ process ID according to a reference PUSCH and / or a first information provided by MAC signaling and / or downlink control information, and / or the configured grant PUSCHs to be transmitted or not to be transmitted, wherein the first configuration indicates that the configured grant PUSCHs are all transmitted in the first time domain resource or the second time domain resource, and the first information indicates that the terminal device does not transmit the configured grant PUSCHs overlapping with the first time domain resource or the configured grant PUSCHs overlapping with the second time domain resource.

17. The apparatus of claim 15, wherein, The reference PUSCH is a predetermined or indicated one of the configured grant PUSCHs, or a predetermined or indicated one of the following PUSCHs: a PUSCH not overlapping with an SSB and / or a second time domain resource for downlink, and / or a PUSCH not overlapping with both the first time domain resource and the second time domain resource, and / or a PUSCH overlapping with the first time domain resource and not overlapping with a PRB other than an uplink available PRB, and / or a PUSCH not overlapping with a symbol indicated by the indicated information as downlink.

18. The apparatus of claim 15, wherein, The processor determines, in a case that a second configuration is provided by higher layer signaling, the configured grant PUSCHs with the corresponding HARQ process ID according to a reference PUSCH and / or a second information provided by RRC signaling and / or MAC signaling and / or downlink control information, and / or the configured grant PUSCHs to be transmitted or not to be transmitted, wherein the second configuration indicates that the configured grant PUSCHs can be transmitted in the first time domain resource and / or the second time domain resource; and the second information is used to indicate that the terminal device transmits the configured grant PUSCHs overlapping with both the first time domain resource and the second time domain resource, or to indicate that the terminal device does not transmit the configured grant PUSCHs overlapping with both the first time domain resource and the second time domain resource.

19. A PUSCH receiving apparatus, comprising: a transmitter configured to transmit configuration 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 other than the first time domain resource; and transmit a configured grant configuration, wherein for a configured grant, whether a configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and a receiver configured to receive one or more of the configured grant PUSCHs with the corresponding HARQ process ID.

20. A communication system, comprising: A terminal device receives configuration 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, the second time domain resource is out of the first time domain resource; receives a configuration of a configured grant, wherein, for a configured grant, whether one configured grant PUSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and transmits one or more of the configured grant PUSCHs with the corresponding HARQ process ID. A network device transmits configuration information for configuring at least a first time domain resource and / or a second time domain resource; transmits a configuration of a configured grant; and receives at least one PUSCH from the terminal device.

Images